WO2020259688A1 - 用户面重路由方法及装置 - Google Patents

用户面重路由方法及装置 Download PDF

Info

Publication number
WO2020259688A1
WO2020259688A1 PCT/CN2020/098561 CN2020098561W WO2020259688A1 WO 2020259688 A1 WO2020259688 A1 WO 2020259688A1 CN 2020098561 W CN2020098561 W CN 2020098561W WO 2020259688 A1 WO2020259688 A1 WO 2020259688A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
session
pdr
message
request message
Prior art date
Application number
PCT/CN2020/098561
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 JP2021576528A priority Critical patent/JP7294578B2/ja
Priority to EP20832946.6A priority patent/EP3979710A4/en
Publication of WO2020259688A1 publication Critical patent/WO2020259688A1/zh
Priority to US17/562,721 priority patent/US11849384B2/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/302—Route determination based on requested QoS
    • H04L45/306—Route determination based on the nature of the carried application
    • 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/70—Routing based on monitoring results
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • 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
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route

Definitions

  • This application relates to the field of network technology, and in particular to a user-plane rerouting method and device.
  • the control plane of the 5G core network and the user plane of the 5G core network exchange messages through corresponding interfaces to implement the user policy issuance from the control plane to the user plane. And the processing of event reporting from the user plane to the control plane. In the actual application process, the user plane path may need to be changed.
  • the application function entity (Application Function, AF) initiates a user plane path change request, and the strategy is triggered by the network capability exposure function entity (Network Exposure Function, NEF) and the unified data cache function entity (Unified Data Repository, UDR)
  • the control function entity Policy Control Function, PCF
  • PCF Policy Control Function
  • SMF Session Management Function
  • AF->NEF->UDR->PCF->SMF which involves many services
  • AF is a functional entity planned by a third-party application (Application, APP). Not within the control of the operator.
  • APP Application, APP
  • operators need to open the service planning inside the operator's network to third-party apps through NEF, which leads to security problems.
  • the embodiments of the present application provide a user-plane rerouting method and device, which improve the security of an operator's network.
  • an embodiment of the present application provides a user plane rerouting method, including:
  • the first network element receives user-plane rerouting trigger information sent by the second network element; wherein the user-plane rerouting trigger information is sent when the second network element detects a preset service packet that matches the packet detection rule PDR
  • the PDR is used to indicate the matching information and execution rules corresponding to the preset service packet that triggers user-plane rerouting;
  • the first network element executes user plane rerouting according to the user plane rerouting trigger information.
  • the user-plane rerouting trigger information sent by the second network element is received through the first network element; wherein the user-plane rerouting trigger information is monitored by the second network element It is sent when a preset service packet matches the packet detection rule PDR; the PDR is used to indicate the matching information and the execution rule corresponding to the preset service packet that triggers user-plane rerouting; further, the first network element
  • the embodiments of the present application can realize the user plane path adjustment of the network elements within the operator's control range based on service perception. Functional entities that do not need third-party APP planning trigger the user plane path change, thereby improving the security of the operator's network.
  • the PDR includes: packet detection information PDI, usage reporting rule URR; wherein, the PDI is used to indicate the matching information corresponding to the preset service packet, and the URR is used to indicate the Preset execution rules corresponding to business messages.
  • the method further includes:
  • the first network element generates the PDR according to a preset policy for triggering user plane rerouting, and sends the PDR to the second network element.
  • the method further includes:
  • the first network element obtains from a third network element a policy preset in the third network element for triggering user plane rerouting;
  • the first network element generates the PDR according to the policy, and sends the PDR to the second network element.
  • the method further includes:
  • the first network element sends an activation message to the second network element, where the activation message is used to instruct to activate the PDR preset in the second network element.
  • the PDR is carried in a first session creation request message sent by the first network element to the second network element, and the first session creation request message is used to instruct the creation of the first network element and The session between the second network element.
  • the activation message is carried in a second session creation request message sent by the first network element to the second network element, and the second session creation request message is used to instruct to create the first network element Session with the second network element.
  • the first network element performs user-plane rerouting according to the user-plane rerouting trigger information, including:
  • the first network element sends a first session request message to the fourth network element, and sends a second session request message to the fifth network element; wherein, the first session request message is used to instruct to create or update the first network element and For a session between the fourth network element, the second session request message is used to instruct to create or update a session between the first network element and the fifth network element, and the second session request message carries the fifth Distributed rules of business packets allocated by network elements; and/or,
  • the first network element sends a session update request message to the second network element, where the session update request message is used to instruct to update the PDR in the second network element.
  • the first network element performs user-plane rerouting according to the user-plane rerouting trigger information, including:
  • the first network element creates a session with the fourth network element
  • the first network element deletes the session with the second network element.
  • the creation of a session between the first network element and the fourth network element includes:
  • the first network element sends a third session creation request message to the fourth network element, where the third session creation request message is used to instruct to create a session between the first network element and the fourth network element.
  • deleting the session between the first network element and the second network element includes:
  • the first network element sends a session deletion request message to the second network element, where the session deletion request message is used to instruct to delete the session between the first network element and the second network element.
  • the method before the first network element performs user-plane rerouting according to the user-plane rerouting trigger information, the method further includes:
  • the first network element sends the user plane rerouting trigger information to the third network element
  • the first network element receives the instruction information sent by the third network element, where the instruction information is used to instruct the first network element to perform user plane rerouting.
  • an embodiment of the present application provides a user-plane rerouting method, including:
  • the first network element monitors the service message according to the message detection rule PDR; where the PDR is used to indicate matching information and execution rules corresponding to the preset service message that triggers user-plane rerouting;
  • the first network element If the first network element detects a preset service packet matching the PDR, the first network element sends user plane rerouting trigger information to the second network element according to the execution rule.
  • the service message is monitored by the first network element according to the message detection rule PDR; if the first network element detects a preset service message matching the PDR At this time, the first network element sends user plane rerouting trigger information to the second network element according to the execution rule, so that the second network element performs user plane rerouting according to the user plane rerouting trigger information.
  • the embodiments of the present application can realize the user plane path adjustment of the network elements within the operator's control range based on service perception. Functional entities that do not need third-party APP planning trigger the user plane path change, thereby improving the security of the operator's network.
  • the PDR includes: packet detection information PDI, usage reporting rule URR; wherein, the PDI is used to indicate the matching information corresponding to the preset service packet, and the URR is used to indicate the Preset execution rules corresponding to business messages.
  • the first network element monitors service packets according to the packet detection rule PDR, including:
  • the first network element determines the attribute information of the service message
  • the first network element matches the attribute information with the PDI
  • the first network element detects that the service packet is a preset service packet matching the PDR; and/or,
  • the first network element detects that the service packet is not a preset service packet matching the PDR.
  • the method further includes:
  • the first network element receives the PDR sent by the second network element, where the PDR is generated by the second network element according to a preset policy for triggering user plane rerouting, or the PDR is the second network
  • the element is generated after obtaining the policy for triggering user plane rerouting from the third network element.
  • the method further includes:
  • the first network element receives an activation message sent by the second network element, where the activation message is used to instruct to activate the PDR preset in the first network element.
  • the PDR is carried in a first session creation request message received by the first network element and sent by the second network element, and the first session creation request message is used to instruct to create the second network.
  • the activation message is carried in a second session creation request message received by the first network element and sent by the second network element, and the second session creation request message is used to instruct to create the second network element.
  • the method further includes:
  • the first network element receives a session update request message sent by the second network element, where the session update request message is used to instruct to update the PDR in the first network element.
  • the method further includes:
  • the first network element receives a session deletion request message sent by the second network element, where the session deletion request message is used to instruct to delete the session between the second network element and the first network element.
  • an embodiment of the present application provides a network element, the network element is a first network element, and the first network element includes:
  • the first receiving module is configured to receive user-plane rerouting trigger information sent by the second network element; wherein the user-plane rerouting trigger information is a preset service report detected by the second network element that matches the packet detection rule PDR
  • the PDR is used to indicate the matching information and execution rules corresponding to the preset service packet that triggers user-plane rerouting;
  • the rerouting module is used to perform user-plane rerouting according to the user-plane rerouting trigger information.
  • the PDR includes: packet detection information PDI, usage reporting rule URR; wherein, the PDI is used to indicate the matching information corresponding to the preset service packet, and the URR is used to indicate the Preset execution rules corresponding to business messages.
  • the first network element further includes:
  • the first generation module is configured to generate the PDR according to a preset strategy for triggering user plane rerouting
  • the first sending module is configured to send the PDR to the second network element.
  • the first network element further includes:
  • An obtaining module configured to obtain a policy preset in the third network element for triggering user plane rerouting from a third network element
  • the second generation module is used to generate the PDR according to the strategy
  • the second sending module is configured to send the PDR to the second network element.
  • the first network element further includes:
  • the third sending module is configured to send an activation message to the second network element, where the activation message is used to instruct to activate the PDR preset in the second network element.
  • the PDR is carried in a first session creation request message sent by the first network element to the second network element, and the first session creation request message is used to instruct the creation of the first network element and The session between the second network element.
  • the activation message is carried in a second session creation request message sent by the first network element to the second network element, and the second session creation request message is used to instruct to create the first network element Session with the second network element.
  • the rerouting module is specifically used for:
  • the second session request message is used to instruct to create or update a session between the first network element and the fifth network element, and the second session request message carries the service allocated for the fifth network element Packet distribution rules; and/or,
  • the rerouting module includes:
  • the creation unit is used to create a session with the fourth network element
  • the deleting unit is used to delete the session with the second network element.
  • the creation unit is specifically used for:
  • deletion unit is specifically used for:
  • the first network element further includes:
  • a fourth sending module configured to send the user plane rerouting trigger information to the third network element
  • the second receiving module is configured to receive the instruction information sent by the third network element, where the instruction information is used to instruct the first network element to perform user plane rerouting.
  • an embodiment of the present application provides a network element, the network element is a first network element, and the first network element includes:
  • the monitoring module is used to monitor the service message according to the message detection rule PDR; where the PDR is used to indicate the matching information and execution rules corresponding to the preset service message that triggers user-plane rerouting;
  • the sending module is configured to send user plane rerouting trigger information to the second network element according to the execution rule when the monitoring module detects a preset service message matching the PDR.
  • the PDR includes: packet detection information PDI, usage reporting rule URR; wherein, the PDI is used to indicate the matching information corresponding to the preset service packet, and the URR is used to indicate the Preset execution rules corresponding to business messages.
  • the monitoring module is specifically used for:
  • the service message is a preset service message matching the PDR.
  • the attribute information does not match the PDI, it is detected that the service message is not a preset service message matching the PDR.
  • the first network element further includes:
  • the first receiving module is configured to receive the PDR sent by the second network element, where the PDR is generated by the second network element according to a preset policy for triggering user plane rerouting, or the PDR is the first Generated after the second network element obtains the policy for triggering user plane rerouting from the third network element.
  • the first network element further includes:
  • the second receiving module is configured to receive an activation message sent by the second network element, where the activation message is used to instruct to activate the PDR preset in the first network element.
  • the PDR is carried in a first session creation request message received by the first network element and sent by the second network element, and the first session creation request message is used to instruct to create the second network.
  • the activation message is carried in a second session creation request message received by the first network element and sent by the second network element, and the second session creation request message is used to instruct to create the second network element.
  • the first network element further includes:
  • the third receiving module is configured to receive a session update request message sent by the second network element, where the session update request message is used to instruct to update the PDR in the first network element.
  • the first network element further includes:
  • the fourth receiving module is configured to receive a session deletion request message sent by the second network element, where the session deletion request message is used to instruct to delete the session between the second network element and the first network element.
  • an embodiment of the present application provides a network element, including: a processor and a memory;
  • the memory is used to store program instructions
  • the processor is used to call and execute the program instructions stored in the memory.
  • the network element is used to execute any one of the implementation methods of the first aspect or the second aspect. The method described.
  • an embodiment of the present application provides a computer-readable storage medium that stores instructions in the computer-readable storage medium.
  • the instructions run on a computer, the computer executes any of the above-mentioned first or second aspects.
  • an embodiment of the present application provides a chip system, which includes a processor and may also include a memory, configured to implement the method described in any implementation manner of the first aspect or the second aspect.
  • the chip system can be composed of chips, or can include chips and other discrete devices.
  • an embodiment of the present application provides a program, when the program is executed by a processor, it is used to execute the method described in any implementation manner of the first aspect or the second aspect.
  • an embodiment of the present application provides a computer program product containing instructions, which when run on a computer, causes the computer to execute the method described in any implementation manner of the first aspect or the second aspect.
  • FIG. 1 is a first schematic diagram of a 5G network architecture provided by an embodiment of this application.
  • Figure 2 is a second schematic diagram of a 5G network architecture provided by an embodiment of this application.
  • Figure 3 is a schematic diagram of a user plane architecture of uplink packet offloading provided by related technologies
  • Figure 4 is a schematic diagram of a user plane architecture of a multi-homed PDU session provided by related technologies
  • Fig. 5 is a schematic diagram of the flow of user plane rerouting triggered by AF provided by related technologies
  • FIG. 6 is a schematic flowchart of a user plane rerouting method provided by an embodiment of this application.
  • FIG. 7 is a schematic flowchart of a user plane rerouting method provided by another embodiment of this application.
  • FIG. 8 is a schematic flowchart of a user plane rerouting method provided by another embodiment of this application.
  • FIG. 9 is a schematic flowchart of a user plane rerouting method provided by another embodiment of this application.
  • FIG. 10 is a schematic structural diagram of a network element provided by an embodiment of this application.
  • FIG. 11 is a schematic structural diagram of a network element provided by another embodiment of this application.
  • FIG. 12 is a schematic structural diagram of a network element provided by another embodiment of this application.
  • FIG. 1 is a first schematic diagram of a 5G network architecture provided by an embodiment of this application.
  • the control plane network elements in the 5G network architecture provide external service interfaces, and the 5G core network control plane and the 5G core network user plane exchange messages through corresponding service interfaces to realize the control plane to the user
  • the user policy issuance of the plane and the event reporting from the user plane to the control plane are processed.
  • the network slice selection function entity (Network Slice Selection Function, NSSF) provides external service-oriented interfaces Nnssf, NEF provides external service-oriented interfaces Nnef, and network storage function entities (Network Repository Function, NRF) provides external service-oriented interfaces Nnrf, PCF external Provides a service-oriented interface Npcf, unified data management (Unified Data Management, UDM) provides external service-oriented interfaces Nudm, AF provides external service-oriented interfaces Naf, and an authentication service function entity (Authentication Server Function, AUSF) provides external service-oriented interfaces Nausf, and access Access and Mobility Management Function entities (Access and Mobility Management Function, AMF) provide external service-oriented interfaces Namf, and SMF provides external service-oriented interfaces Nsmf.
  • NSSF Network Slice Selection Function
  • NEF provides external service-oriented interfaces Nnef
  • network storage function entities (Network Repository Function, NRF) provides external service-oriented interfaces Nnrf
  • the terminal and the AMF are connected through the N1 interface
  • the AMF and the access network (Access Network, AN) are connected through the N2 interface
  • the AN and UPF are connected through the N3 interface
  • the UPF and SMF are connected through the N4 interface.
  • the UPF is connected to the data network (Data Network, DN) through the N6 interface.
  • FIG. 2 is a second schematic diagram of a 5G network architecture provided by an embodiment of this application.
  • the two network elements that need to be interconnected in the 5G network architecture have a one-to-one definition of inter-element interfaces, and the 5G core network control plane and the 5G core network user plane pass through the corresponding inter-element interfaces Perform message interaction to implement user policy issuance from the control plane to the user plane and event reporting from the user plane to the control panel.
  • N1 is the network element interface between the terminal and AMF
  • N2 is the network element interface between AN and AMF
  • N3 is the network element interface between AN and UPF
  • N4 is the network element interface between UPF and SMF.
  • Inter-element interface N5 is the interface between PCF and AF
  • N6 is the interface between UPF and DN
  • N7 is the interface between SMF and PCF
  • N8 is the interface between AMF and UDM
  • the interface between network elements N9 is the interface between UPF
  • N10 is the interface between UDM and SMF
  • N11 is the interface between AMF and SMF
  • N12 is the interface between AMF and AUSF
  • N13 is the interface between AUSF and UDM
  • N14 is the interface between AMF
  • N15 is the interface between AMF and PCF
  • N22 is the interface between NSSF and AMF
  • FIG. 3 is a schematic diagram of the user plane architecture of upstream packet offloading provided by related technologies.
  • IPv4 Internet Protocol version 4, IPv4
  • Multi-home Internet Protocol version 6
  • ULCL Uplink Classifier
  • FIG. 4 is a schematic diagram of the user plane architecture of a multi-homed PDU session provided by related technologies.
  • a single session multi-service path is realized by adding Branch Point (BP)-UPF for Multi-home IPv6 sessions
  • BP Branch Point
  • PSA-UPF1 and PSA-UPF2 can be used for offloading processing.
  • Fig. 5 is a schematic diagram of a flow of user plane rerouting triggered by AF provided by related technologies.
  • the AF in the related technology can perceive the terminal accessing its service and the location information of the terminal, the AF initiates a user plane path change request, and the PCF is triggered through NEF and UDR to notify the SMF to reconfigure the user plane path of the UPF .
  • AF creates an AF request and sends an AF request to NEF so that NEF saves the AF request in the UDR.
  • the AF request may include, but is not limited to: create a message, update a message, or delete a message; further, because the PCF has already The UDR subscribes to the notification service when the AF requests a change. Therefore, the UDR will send a notification message to the PCF so that the PCF can send a policy control update notification message to the SMF, so that the SMF can reconfigure the user plane path of the UPF, thereby making the user plane The path switches to the server closest to the terminal.
  • AF->NEF->UDR->PCF->SMF which involves many services
  • AF is a functional entity planned by a third-party APP and is not within the control of the operator .
  • operators need to open the service planning inside the operator's network to third-party apps through NEF, which leads to security problems.
  • the user plane rerouting method and device monitor service packets according to PDR through a second network element within the control of an operator, and report to the first network element when a preset service packet matching the PDR is detected.
  • the network element sends user-plane rerouting trigger information, so that the first network element can learn that the terminal is accessing a preset service message that triggers user-plane rerouting according to the received user-plane rerouting trigger information, and then perform user-plane rerouting.
  • the embodiments of the present application can realize the user plane path adjustment of the network elements within the operator's control range based on service perception. Functional entities that do not need third-party APP planning trigger the user plane path change, thereby improving the security of the operator's network.
  • 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 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 plural items (a).
  • at least one item (a) of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple .
  • FIG. 6 is a schematic flowchart of a user plane rerouting method provided by an embodiment of this application. As shown in FIG. 6, the method of the embodiment of the present application may include:
  • Step S601 The second network element monitors the service message according to the message detection rule PDR; where the PDR is used to indicate matching information and execution rules corresponding to the preset service message that triggers user-plane rerouting.
  • the second network element involved in the embodiment of the present application may refer to the source anchor point PSA-UPF1 corresponding to the initial session of the terminal.
  • the preset service message involved in the embodiment of the present application refers to a message corresponding to a preset service that triggers user-plane rerouting.
  • the preset service may include, but is not limited to: access service generated by a preset Internet Protocol (IP) address segment of the server, or access service generated by a preset application or APP.
  • IP Internet Protocol
  • PDR Packet Detection Information
  • URR Usage Reporting Rule
  • FAR Forwarding Action Rule
  • PDI is used to indicate the matching information corresponding to the preset service packet.
  • PDI may include, but is not limited to: Full Qualified Tunnel Endpoint Identifier (F-TEID) of the preset packet, source and destination port , Source and destination IP address, IP protocol type, application identification number (Identity document, ID).
  • F-TEID Full Qualified Tunnel Endpoint Identifier
  • URR User Datagram Protocol
  • QoS execution rule and/or FAR are all used to indicate the execution rule corresponding to the preset service message.
  • the second network element when it receives any service message, it first determines the attribute information of the service message.
  • the attribute information of the service message may include but is not limited to: F-TEID of the service message , Source and destination port, source and destination IP address, IP protocol type, application ID.
  • the second network element compares and matches the attribute information with PDI. If the attribute information of the service message matches the PDI, the second network element detects that the service message is a preset service message that matches the PDR; if the attribute information of the service message does not match the PDI, the second network element monitors The arriving service message is not a preset service message matching the PDR.
  • the attribute information of the service message includes: the F-TEID of the service message, source and destination port, source and destination IP address, IP protocol type, if the F-TEID of the service message is the same as the F-TEID of the preset message, the source and destination port of the service message is the same as the source and destination port of the preset message, and the source and destination of the service message
  • the IP address is the same as the source and destination IP addresses of the preset message
  • the IP protocol type of the service message is the same as the IP protocol type of the preset message
  • the second network element determines that the attribute information of the service message matches the PDI, and thus It is detected that the service packet is a preset service packet matching the PDR; otherwise (for example, the F-TEID of the service packet and the F-TEID of the preset packet, the source and destination port of the service packet and the preset packet
  • the first network element generates a PDR according to a preset policy for triggering user plane rerouting, and sends the PDR to the second network element; correspondingly, the second network element receives the transmission from the first network element PDR.
  • the first network element involved in the embodiment of the present application may be an SMF.
  • the preset policies for triggering user plane rerouting involved in the embodiments of the present application may include, but are not limited to, any of the following:
  • the terminal When the terminal accesses the preset service, it needs to select a specific UPF as the offloaded UPF to insert session information, select another specific UPF as the new local anchor point to establish new session information, and send to the offloaded UPF to indicate the service flow ( Including multiple business messages) a strategy of distributing through the source anchor point and the new local anchor point respectively;
  • the terminal accesses the preset service, it needs to select a specific UPF as the new local anchor to establish new session information, and delete the session information on the source anchor;
  • CDN Content Delivery Network
  • the new local anchor point can be used Make a business visit.
  • a policy for triggering user plane rerouting is preset in the first network element, and the first network element may generate a PDR according to the preset policy, and then send the generated PDR to the second network element.
  • the PDR may be carried in a first session creation request message sent by the first network element to the second network element, where the first session creation request message is used to instruct to create a session between the first network element and the second network element;
  • the PDR can also be carried in other messages sent by the first network element to the second network element (for example, a session update request message, etc.).
  • the first network element obtains from the third network element a policy preset in the third network element for triggering user plane rerouting; the first network element generates a PDR according to the policy and sends the PDR to The second network element; correspondingly, the second network element receives the PDR sent by the first network element.
  • the third network element involved in the embodiment of the present application may be a PCF.
  • the third network element is preset with a strategy for triggering user-plane rerouting.
  • the first network element can obtain the strategy preset in the third network element from the third network element, and then generate it according to the obtained strategy PDR, and send the generated PDR to the second network element.
  • the PDR can be carried in the first session creation request message sent by the first network element to the second network element; of course, the PDR can also be carried in other messages sent by the first network element to the second network element (for example, Session update request message, etc.).
  • the first network element sends an activation message to the second network element, and the activation message is used to instruct to activate the PDR preset in the second network element; correspondingly, the second network element receives the transmission from the first network element Activation message.
  • a PDR is preset in the second network element, and the first network element sends an activation message to the second network element to activate the PDR preset in the second network element.
  • the activation message may be carried in a second session creation request message sent by the first network element to the second network element, and the second session creation request message is used to instruct to create a session between the second network element and the first network element ;
  • the activation message can also be carried in other messages sent by the first network element to the second network element (for example, a session update request message, etc.).
  • Step S602 If the second network element detects a preset service packet matching the PDR, the second network element sends user plane rerouting trigger information to the first network element according to the execution rule.
  • the second network element detects a preset service packet matching the PDR, the second network element sends user plane rerouting trigger information to the first network element according to the execution rule in the PDR, so that the first network element
  • the meta can learn that the terminal is accessing the preset service message that will trigger the user-plane rerouting according to the user-plane rerouting trigger information, thereby performing user-plane rerouting.
  • Step S603 The first network element receives the user plane rerouting trigger information sent by the second network element.
  • the first network element receives the user-plane rerouting trigger information sent by the second network element, thereby knowing that the terminal is accessing a preset service message that will trigger user-plane rerouting; wherein the user-plane rerouting trigger information is the first Sent when the second network element detects a preset service message matching the message detection rule PDR.
  • Step S604 The first network element performs user-plane rerouting according to the user-plane rerouting trigger information.
  • the first network element executes the user-plane rerouting operation according to the user-plane rerouting trigger information.
  • the operation of performing user-face rerouting can include, but is not limited to, the following possible implementation methods.
  • the first network element sends a first session request message to the fourth network element, and sends a second session request message to the fifth network element; wherein the first session request message is used to instruct to create or update the A session between a network element and a fourth network element, the second session request message is used to instruct to create or update a session between the first network element and the fifth network element, and the second session request message carries the fifth network element Distribution rules for business packets; and/or,
  • the first network element sends a session update request message to the second network element, where the session update request message is used to instruct to update the PDR in the second network element; correspondingly, the second network element receives the session update request message sent by the first network element.
  • the fourth network element involved in the embodiment of the present application may refer to the new local anchor point PSA-UPF2 corresponding to the new session of the terminal.
  • the fifth network element involved in the embodiments of this application may refer to ULCL-UPF; for Multi-home IPv6 sessions, the embodiments of this application involve The fifth network element may refer to BP-UPF.
  • the first network element may send a first session request message for instructing to create or update a session between the first network element and the fourth network element to the fourth network element, and send a message to the fifth network element A second session request message for instructing to create or update a session between the first network element and the fifth network element; wherein, the second session request message may also carry a service packet distribution rule allocated to the fifth network element to Make the fifth network element distribute the business message according to the business message diversion rule.
  • the first session request message is used to instruct to update the session between the first network element and the fourth network element ; If the first network element does not create a session between the first network element and the fourth network element, the first session request message is used to instruct to create a session between the first network element and the fourth network element.
  • the second session request message is used to instruct to update the session between the first network element and the fifth network element; If the first network element does not create a session between the first network element and the fifth network element, the second session request message is used to instruct to create a session between the first network element and the fifth network element.
  • the first network element may also send a session update request message to the second network element.
  • the second network element receives the session update request message sent by the first network element, where the session update request message is used to indicate Update the PDR in the second network element.
  • the session update request message may be used to instruct to update the interface tunnel information carried in the FAR action of the original PDR to the interface tunnel information between the second network element and the fifth network element (for example, interface address and/or F-TEID).
  • a network element Before performing user-plane rerouting according to the user-plane rerouting trigger information, a network element first sends the user-plane rerouting trigger information to the third network element, so that the third network element can trigger the user-plane rerouting according to the preset
  • the routing strategy sends instruction information for instructing the first network element to perform user plane rerouting to the first network element, and then receives the instruction information sent by the third network element.
  • the first network element creates a session with the fourth network element, and deletes the session with the second network element.
  • the first network element may send to the fourth network element a third session creation request message for instructing to create a session between the first network element and the fourth network element.
  • the fourth network element is receiving After the third session creation request message sent by the first network element, the session creation response message corresponding to the third session creation request message can also be sent to the first network element, so as to create a connection between the first network element and the fourth network element. Conversation.
  • the first network element may send to the second network element a session deletion request message for instructing to delete the session between the first network element and the second network element.
  • the second network element receives the first network element.
  • a session deletion response message corresponding to the session deletion request message may be sent to the first network element, so as to delete the session between the first network element and the second network element.
  • the second network element monitors the service message according to the message detection rule PDR; if the second network element detects a preset service message that matches the PDR, the second network element reports to the first network element according to the execution rule.
  • a network element sends user-plane rerouting trigger information; further, the first network element performs user-plane rerouting according to the received user-plane rerouting trigger information.
  • the second network element within the control of the operator in the embodiment of the present application monitors the service message according to the PDR.
  • the user plane rerouting trigger information is sent to the first network element, so that the first network element can learn that the terminal is accessing and trigger the user plane according to the received user plane rerouting trigger information. Reroute the preset service message, and then perform user-plane rerouting. It can be seen that the embodiments of the present application can implement user plane path adjustment based on service perception for network elements within the operator's control range, and no functional entity planned by a third-party APP triggers the user plane path change, thereby improving the security of the operator's network.
  • FIG. 7 is a schematic flowchart of a user plane rerouting method provided by another embodiment of this application.
  • PSA-UPF1 is used to monitor the service message according to the PDR issued by the SMF, and the user plane rerouting trigger is sent to the SMF when the preset service message matching the PDR is detected Information, taking user-plane rerouting operations such as making SMF perform offloading UPF and PSA-UPF2 session creation and issuing business message offloading rules as an example, the user-plane rerouting method is introduced.
  • the SMF is preset with a policy for triggering user plane rerouting. For example, when a terminal accesses a preset service, it needs to select a specific UPF as the offloaded UPF to insert session information, and select another specific UPF as the new one.
  • the local anchor PSA-UPF2 establishes new session information and sends to the offloading UPF to indicate that the service flow (including multiple service packets) is carried out through the source anchor PSA-UPF1 and the new local anchor PSA-UPF2 respectively Distribution strategy, etc.
  • the SMF can generate a corresponding PDR according to a preset strategy, where the PDR can include but is not limited to: PDI and URR.
  • the offloading UPF involved in the embodiments of this application may refer to ULCL-UPF; for Multi-home IPv6 sessions, the offloading involved in the embodiments of this application UPF may refer to BP-UPF.
  • the method of the embodiment of the present application may include:
  • Step S701 The terminal sends a session establishment request message to the SMF.
  • Step S702 The SMF sends a session creation request message 1 to the PSA-UPF1, where the session creation request message 1 is used to instruct to create a session between the SMF and the PSA-UPF1.
  • the session creation request message 1 carries a PDR generated by the SMF according to a preset policy, where the PDR may include but is not limited to: PDI and URR.
  • Table 1 shows the structure of URR information element (Information Elements, IE) in session creation request message 1
  • reporting triggers are added to the URR information element to indicate triggers for reporting network resource usage to the control plane (CP) functional entity.
  • CP control plane
  • reporting triggers Reporting Triggers
  • the specific format of the reported trigger point can be shown in Table 2.
  • Bit 7-RERT Routing Service
  • Table 2 shows the structure of the reported trigger point
  • the code of Octet 5 can be as follows:
  • Bit 1-Periodic Reporting When set to 1, it means that periodic reporting is requested;
  • Bit 2-Volume Threshold When set to 1, it means that a report is requested when the data usage reaches the usage threshold;
  • TIMTH Bit 3-Time Threshold
  • Bit 4-Quota Holding Time When set to 1, it means that a report is requested when no data packet is received within the time period exceeding the quota holding time;
  • Bit 5-Service Start (Start of Traffic, START): When set to 1, it means that a report is requested when a Service Data Flow (SDF) or application service is detected;
  • SDF Service Data Flow
  • Bit 6-Stop of Traffic (Stop of Traffic, STOPT): When set to 1, it means that a report is requested when SDF or application service stops are detected;
  • Bit 7-Dropped DL Traffic Threshold When set to 1, it means that a report is requested when the dropped downlink traffic reaches the threshold;
  • Bit 8-Linked Usage Reporting When set to 1, it indicates the related usage reporting request. For example, when the associated usage reporting rule initiates usage reporting, it needs to be triggered at the same time Usage reporting request for usage reporting rules;
  • the code of Octet 6 can be as follows:
  • Bit 1-Volume Quota (Volume Quota, VOLQU): When set to 1, it means that a report is requested when the volume quota is exhausted;
  • TIMQU Bit 2-Time Quota
  • MACAR Bit 4-MAC Addresses Reporting
  • Bit 5-Event Threshold When set to 1, it means that a report is requested when the event threshold is reached;
  • Bit 6-Event Quota When set to 1, it means that a report is requested when the event quota is reached;
  • Bit 7-Rerouting of Traffic When set to 1, it means that a report is requested when a rerouting SDF or application service is detected;
  • Step S703 PSA-UPF1 sends a session creation response message 1 to SMF.
  • Step S704 The SMF sends a session establishment response message to the terminal.
  • Step S705 The terminal initiates service access.
  • Step S706 The PSA-UPF1 monitors the service message according to the PDR.
  • step S707 is executed.
  • Step S707 PSA-UPF1 sends a session report request message to SMF.
  • PSA-UPF1 when PSA-UPF1 detects a preset service message matching the PDI in the PDR, it sends a session report request message to the SMF according to the URR in the PDR (including Reporting Triggers for indicating service rerouting), where ,
  • the session report request message carries user plane rerouting trigger information.
  • Table 3 shows the structure of the Usage Report IE in the session report request message
  • the trigger reason for usage report (Usage Report Trigger) is used to indicate the trigger reason for usage report.
  • the trigger reason for rerouting service (Traffic Rerouting Trigger) is added, or it is called user Plane rerouting trigger information.
  • the specific format of the trigger reason for the usage report can be as shown in Table 4.
  • Table 4 is a schematic diagram of the structure of the trigger reason for the usage report
  • the code of Octet 5 can be as follows:
  • Bit 1-PERIO When set to 1, it means periodic report
  • Bit 2-VOLTH When set to 1, it means that the data usage reaches the usage threshold
  • Bit 3-TIMTH When set to 1, it means that the time usage reaches the time threshold
  • Bit 4-QUHTI When set to 1, it means that no data packet has been received within the time period exceeding the quota retention period
  • Bit 5-START When set to 1, it means that the service start is detected
  • Bit 6-STOPT When set to 1, it indicates that the service is stopped
  • Bit 7-DROTH When set to 1, it means that the dropped downlink traffic reaches the threshold
  • Bit 8-Immediate Report refers to the URR report triggered immediately after receiving the CP message: When set to 1, it means that an immediate usage report request is triggered based on the requirements of the CP functional entity;
  • the code of Octet 6 can be as follows:
  • Bit 1-VOLQU When set to 1, it means that the traffic quota has been used up;
  • Bit 2-TIMQU When set to 1, it means that the duration quota has been exhausted
  • Bit 3-LIUSA When set to 1, it means that the associated usage is reported. For example, because of the usage reporting of the associated usage reporting rule, the usage reporting of the usage reporting rule;
  • TERMR Bit 4-Termination Report
  • Bit 5-Monitoring Time (Monitoring Time, MONIT): When set to 1, it means that the URR usage is reported because the monitoring time is reached;
  • Bit 6-ENVCL When set to 1, it means that a usage report is generated when the envelope is closed;
  • Bit 7-MACAR When set to 1, it indicates the usage report of the MAC (Ethernet) address used as the source address of the UL data frame sent by the UE;
  • Bit 8-EVETH When set to 1, it means that a usage report is generated when the event threshold is reached;
  • the code of Octet 7 can be as follows:
  • Bit 1-EVEQU When set to 1, it indicates that the event quota has been exhausted
  • Bit 2-RERT When set to 1, it indicates that there is a rerouting SDF or application service detected
  • Bits 3 to 8 reserved for future use and set to 0.
  • Step S708 The SMF sends a session report response message to PSA-UPF1.
  • Step S709 The SMF determines that user plane rerouting needs to be performed according to the user plane rerouting trigger information in the session report request message.
  • the SMF determines, according to the user plane rerouting trigger information in the session report request message, that the session creation of offloading UPF and PSA-UPF2 and the preset service issued by the business packet offloading rule have been triggered, and the user plane needs to be executed. Rerouting.
  • Step S710 The SMF sends a session creation request message 2 to the PSA-UPF2, where the session creation request message 2 is used to instruct to create a session between the SMF and the PSA-UPF2.
  • Step S711 PSA-UPF2 sends a session creation response message 2 to SMF.
  • Step S712 The SMF sends a session creation request message 3 to the offloaded UPF, where the session creation request message 3 is used to instruct to create a session between the SMF and offloaded UPF.
  • the session creation request message 3 carries the business packet offloading rules allocated for offloading UPF, so that the offloading UPF will pass the business packets through the source anchor point PSA-UPF1 and the new local anchor point according to the business packet offloading rules.
  • PSA-UPF2 is distributed.
  • Step S713 The offloaded UPF sends a session creation response message 3 to the SMF.
  • Step S714 The SMF sends a session update request message to PSA-UPF1, where the session update request message is used to instruct to update the PDR in PSA-UPF1.
  • the session update request message is used to instruct to update the interface tunnel information carried in the FAR action of the original PDR of PSA-UPF1 to the interface tunnel information between PSA-UPF1 and the offloaded UPF (for example, interface address and/or FAR). -TEID).
  • Step S715 PSA-UPF1 sends a session update response message to SMF.
  • Step S716 The offloading UPF forwards the service message sent by the terminal to the DN through PSA-UPF1 and PSA-UPF2 according to the business message offloading rule.
  • the offloaded UPF can offload a preset service message to PSA-UPF2 for data network access according to the business message offloading rule, and other service messages are still forwarded to PSA-UPF1 for continued access.
  • PSA-UPF1 can monitor service messages according to PDR, and send user-plane rerouting trigger information to SMF when it detects a preset service message matching PDR; SMF re-routing trigger information according to user-plane It can be learned that the session creation of offloading UPF and PSA-UPF2 and the preset service issued by the business message offloading rules have been triggered, and then the session establishment process of offloading UPF and PSA-UPF2 is executed to facilitate the offloading of specific service flows to the corresponding The anchor UPF for data network access. It can be seen that the embodiments of the present application can implement user plane path adjustment based on service perception, without the need for a third-party APP planning functional entity to perceive and trigger user plane rerouting, thereby improving the security of the operator's network.
  • FIG. 8 is a schematic flowchart of a user plane rerouting method provided by another embodiment of this application.
  • the embodiment of this application uses PSA-UPF1 to monitor the service message according to the PDR issued by the SMF, and sends user-plane rerouting trigger information to the SMF when the preset service message matching the PDR is detected , Taking the user-plane rerouting operations such as making the SMF perform PSA-UPF2 session creation and PSA-UPF1 session deletion as an example, the user-plane rerouting method is introduced.
  • the SMF is preset with a strategy for triggering user plane rerouting. For example, when the terminal accesses a preset service, it needs to select a specific UPF as the new local anchor PSA-UPF2 to establish new session information, and Delete the session information on the source anchor PSA-UPF1, etc.
  • the SMF can generate a corresponding PDR according to a preset strategy, where the PDR can include but is not limited to: PDI and URR.
  • the method of the embodiment of the present application may include:
  • Step S801 The terminal sends a session establishment request message to the SMF.
  • Step S802 The SMF sends a session creation request message 1 to the PSA-UPF1, where the session creation request message 1 is used to instruct to create a session between the SMF and the PSA-UPF1.
  • the session creation request message 1 carries a PDR generated by the SMF according to a preset policy, where the PDR may include but is not limited to: PDI and URR.
  • Step S803 PSA-UPF1 sends a session creation response message 1 to SMF.
  • Step S804 The SMF sends a session establishment response message to the terminal.
  • Step S805 The terminal initiates service access.
  • Step S806 The PSA-UPF1 monitors the service message according to the PDR.
  • step S807 is executed.
  • Step S807 PSA-UPF1 sends a session report request message to SMF.
  • PSA-UPF1 when PSA-UPF1 detects a preset service message matching the PDI in the PDR, it sends a session report request message to the SMF according to the URR in the PDR (including Reporting Triggers for indicating service rerouting), where ,
  • the session report request message carries user plane rerouting trigger information.
  • Step S808 The SMF sends a session report response message to PSA-UPF1.
  • Step S809 The SMF determines that user plane rerouting needs to be performed according to the user plane rerouting trigger information in the session report request message.
  • the SMF determines, according to the user-plane rerouting trigger information in the session report request message, that the preset services that need to perform PSA-UPF2 session creation and PSA-UPF1 session deletion have been triggered, so that user-plane rerouting needs to be performed.
  • Step S810 The SMF sends a session creation request message 2 to the PSA-UPF2, where the session creation request message 2 is used to instruct to create a session between the SMF and the PSA-UPF2.
  • Step S811 PSA-UPF2 sends a session creation response message 2 to the SMF.
  • Step S812 The SMF sends a session deletion request message to the PSA-UPF1.
  • the session deletion request message is used to instruct to delete the session between the SMF and the PSA-UPF1.
  • Step S813 The PSA-UPF1 sends a session deletion response message to the SMF.
  • Step S814 PSA-UPF2 forwards the service message sent by the terminal.
  • PSA-UPF1 can monitor service messages according to PDR, and send user-plane rerouting trigger information to SMF when it detects a preset service message matching PDR; SMF re-routing trigger information according to user-plane It can be learned that the preset services that need to perform PSA-UPF2 session creation and PSA-UPF1 session deletion have been triggered, and then perform the PSA-UPF2 session establishment and PSA-UPF1 session deletion procedures, so that all service packets sent by the terminal pass PSA-UPF2 performs data network access. It can be seen that the embodiments of the present application can implement user plane path adjustment based on service perception, without the need for a third-party APP planning functional entity to perceive and trigger user plane rerouting, thereby improving the security of the operator's network.
  • FIG. 9 is a schematic flowchart of a user plane rerouting method provided by another embodiment of this application.
  • the embodiment of this application uses the PDR monitoring service message issued by PSA-UPF1 according to the SMF (generated after the SMF obtains the policy for triggering user plane rerouting from the PCF), and then When a preset service message matching the PDR is detected, the user plane rerouting trigger information is sent to the SMF, so that the SMF reports the user plane rerouting trigger information to the PCF, and when the PCF sends the instruction to instruct the SMF to execute the user plane After the instructions for rerouting, perform user-plane rerouting operations such as the creation of offloaded UPF and PSA-UPF2 sessions and the issuance of service packet offloading rules as an example to introduce the user-plane rerouting method.
  • user-plane rerouting operations such as the creation of offloaded UPF and PSA-UPF2 sessions and the issuance of service packet offloading rules as an
  • the PCF is preset with a policy for triggering user plane rerouting. For example, when a terminal accesses a preset service, it needs to select a specific UPF as the offloaded UPF to insert session information, and select another specific UPF as the new one.
  • the local anchor PSA-UPF2 establishes new session information and sends to the offloading UPF to indicate that the service flow (including multiple service packets) is carried out through the source anchor PSA-UPF1 and the new local anchor PSA-UPF2 respectively Distribution strategy, etc.
  • the offloading UPF involved in the embodiments of this application may refer to ULCL-UPF; for Multi-home IPv6 sessions, the offloading involved in the embodiments of this application UPF may refer to BP-UPF.
  • the method of the embodiment of the present application may include:
  • Step S901 The terminal sends a session establishment request message to the SMF.
  • Step S902 The SMF sends a policy control creation request message to the PCF, where the policy control creation request message is used to instruct to obtain a policy for triggering user plane rerouting.
  • Step S903 The PCF sends a policy control creation response message to the SMF, where the policy control creation response message carries a policy for triggering user-plane rerouting; of course, the policy control creation response message can also carry other charging and control policies. Strategy.
  • the policy control creation response message may include policy control request triggering reasons (Policy Control Request Triggers) indication information.
  • Policy Control Request Triggers Policy Control Request Triggers
  • the policy control request trigger reason indication information may include but is not limited to rerouting policy (or called the policy used to trigger user-plane rerouting), which is used to indicate that the SMF detects that the terminal accesses and needs to be executed.
  • the policy control update request is reported during the preset service of user-face rerouting.
  • Table 5 is a schematic table of the indication information of the triggering reason of the policy control request
  • Step S904 The SMF generates a corresponding PDR according to the strategy for triggering user plane rerouting acquired from the PCF, where the PDR may include but is not limited to: PDI and URR.
  • Step S905 The SMF sends a session creation request message 1 to the PSA-UPF1, where the session creation request message 1 is used to instruct to create a session between the SMF and the PSA-UPF1.
  • the session creation request message 1 carries a PDR, where the PDR may include but is not limited to: PDI and URR.
  • Step S906 PSA-UPF1 sends a session creation response message 1 to SMF.
  • Step S907 The SMF sends a session establishment response message to the terminal.
  • Step S908 The terminal initiates service access.
  • Step S909 PSA-UPF1 monitors the service message according to the PDR.
  • step S910 is executed.
  • Step S910 PSA-UPF1 sends a session report request message to SMF.
  • PSA-UPF1 when PSA-UPF1 detects a preset service message matching the PDI in the PDR, it sends a session report request message to the SMF according to the URR in the PDR (including Reporting Triggers for indicating service rerouting), where ,
  • the session report request message carries user plane rerouting trigger information.
  • Step S911 The SMF sends a session report response message to PSA-UPF1.
  • Step S912 The SMF sends a policy control update request message to the PCF.
  • the SMF determines, according to the user plane rerouting trigger information in the session report request message, that the session creation of offloaded UPF and PSA-UPF2 and the preset service issued by the offloading rule of the service packet have been triggered, thereby sending the policy to the PCF A control update request message, where the policy control update request message can carry user plane rerouting trigger information.
  • Step S913 The PCF sends a policy control update response message to the SMF, where the policy control update response message may carry indication information for instructing the SMF to perform user plane rerouting.
  • Step S914 The SMF determines to perform user-plane rerouting according to the received instruction information for instructing the SMF to perform user-plane rerouting.
  • Step S915 The SMF sends a session creation request message 2 to the PSA-UPF2, where the session creation request message 2 is used to instruct to create a session between the SMF and the PSA-UPF2.
  • Step S916 PSA-UPF2 sends a session creation response message 2 to the SMF.
  • Step S917 The SMF sends a session creation request message 3 to the offloaded UPF, where the session creation request message 3 is used to instruct to create a session between the SMF and offloaded UPF.
  • the session creation request message 3 carries the business packet offloading rules allocated for offloading UPF, so that the offloading UPF will pass the business packets through the source anchor point PSA-UPF1 and the new local anchor point according to the business packet offloading rules.
  • PSA-UPF2 is distributed.
  • Step S918 The offloaded UPF sends a session creation response message 3 to the SMF.
  • Step S919 The SMF sends a session update request message to the PSA-UPF1.
  • the session update request message is used to instruct to update the PDR in the PSA-UPF1.
  • the session update request message is used to instruct to update the interface tunnel information carried in the FAR action of the original PDR of PSA-UPF1 to the interface tunnel information between PSA-UPF1 and the offloaded UPF (for example, interface address and/or FAR). -TEID).
  • Step S920 PSA-UPF1 sends a session update response message to SMF.
  • Step S921 The offloading UPF forwards the service message sent by the terminal to the DN through PSA-UPF1 and PSA-UPF2 according to the service message offloading rule.
  • the offloaded UPF can offload a preset service message to PSA-UPF2 for data network access according to the business message offloading rule, and other service messages are still forwarded to PSA-UPF1 for continued access.
  • PSA-UPF1 can monitor service messages according to PDR, and send user-plane rerouting trigger information to SMF when it detects a preset service message matching PDR; SMF re-routing trigger information according to user-plane It can be learned that the session creation that needs to perform offloading UPF and PSA-UPF2 and the preset services issued by the business message offloading rules have been triggered, and reported to the PCF, and then received the PCF sent to instruct the SMF to perform user plane rerouting After the instruction information, the session establishment process of offloading UPF and PSA-UPF2 is executed to facilitate offloading the specific service flow to the corresponding anchor point UPF for data network access. It can be seen that the embodiments of the present application can implement user plane path adjustment based on service perception, without the need for a third-party APP planning functional entity to perceive and trigger user plane rerouting, thereby improving the security of the operator's network.
  • FIG. 10 is a schematic structural diagram of a network element provided by an embodiment of this application.
  • the network element provided in the embodiment of the present application may be the first network element.
  • the network element 100 of the embodiment of the present application may include: a first receiving module 1001 and a rerouting module 1002.
  • the first receiving module 1001 is configured to receive user-plane rerouting trigger information sent by the second network element; wherein, the user-plane rerouting trigger information is the preset that the second network element detects that matches the packet detection rule PDR Sent when a service message is set; the PDR is used to indicate the matching information and execution rules corresponding to the preset service message that triggers user-plane rerouting;
  • the rerouting module 1002 is configured to perform user-plane rerouting according to the user-plane rerouting trigger information.
  • the PDR includes: packet detection information PDI, usage reporting rule URR; wherein, the PDI is used to indicate the matching information corresponding to the preset service packet, and the URR is used to indicate the Preset execution rules corresponding to business messages.
  • the first network element further includes:
  • the first generation module is configured to generate the PDR according to a preset strategy for triggering user plane rerouting
  • the first sending module is configured to send the PDR to the second network element.
  • the first network element further includes:
  • An obtaining module configured to obtain a policy preset in the third network element for triggering user plane rerouting from a third network element
  • the second generation module is used to generate the PDR according to the strategy
  • the second sending module is configured to send the PDR to the second network element.
  • the first network element further includes:
  • the third sending module is configured to send an activation message to the second network element, where the activation message is used to instruct to activate the PDR preset in the second network element.
  • the PDR is carried in a first session creation request message sent by the first network element to the second network element, and the first session creation request message is used to instruct the creation of the first network element and The session between the second network element.
  • the activation message is carried in a second session creation request message sent by the first network element to the second network element, and the second session creation request message is used to instruct to create the first network element Session with the second network element.
  • the rerouting module 1002 is specifically used for:
  • the second session request message is used to instruct to create or update a session between the first network element and the fifth network element, and the second session request message carries the service allocated for the fifth network element Packet distribution rules; and/or,
  • the rerouting module 1002 includes:
  • the creation unit is used to create a session with the fourth network element
  • the deleting unit is used to delete the session with the second network element.
  • the creation unit is specifically used for:
  • deletion unit is specifically used for:
  • the first network element further includes:
  • a fourth sending module configured to send the user plane rerouting trigger information to the third network element
  • the second receiving module is configured to receive the instruction information sent by the third network element, where the instruction information is used to instruct the first network element to perform user plane rerouting.
  • the network element 100 provided in the embodiment of the present application may be used to implement the technical solution of the first network element in the above-mentioned user plane rerouting method embodiment of the present application.
  • the implementation principles and technical effects are similar, and will not be repeated here.
  • FIG. 11 is a schematic structural diagram of a network element provided by another embodiment of this application.
  • the network element provided in the embodiment of the present application may be the first network element.
  • the network element 110 of the embodiment of the present application may include: a monitoring module 1101 and a sending module 1102.
  • the monitoring module 1101 is configured to monitor service messages according to the message detection rule PDR; wherein, the PDR is used to indicate matching information and execution rules corresponding to the preset service messages that trigger user-plane rerouting;
  • the sending module 1102 is configured to send user plane rerouting trigger information to the second network element according to the execution rule when the monitoring module detects a preset service message matching the PDR.
  • the PDR includes: packet detection information PDI, usage reporting rule URR; wherein, the PDI is used to indicate the matching information corresponding to the preset service packet, and the URR is used to indicate the Preset execution rules corresponding to business messages.
  • the monitoring module 1101 is specifically used for:
  • the service message is a preset service message matching the PDR.
  • the attribute information does not match the PDI, it is detected that the service message is not a preset service message matching the PDR.
  • the first network element further includes:
  • the first receiving module is configured to receive the PDR sent by the second network element, where the PDR is generated by the second network element according to a preset policy for triggering user plane rerouting, or the PDR is the first Generated after the second network element obtains the policy for triggering user plane rerouting from the third network element.
  • the first network element further includes:
  • the second receiving module is configured to receive an activation message sent by the second network element, where the activation message is used to instruct to activate the PDR preset in the first network element.
  • the PDR is carried in a first session creation request message received by the first network element and sent by the second network element, and the first session creation request message is used to instruct to create the second network.
  • the activation message is carried in a second session creation request message received by the first network element and sent by the second network element, and the second session creation request message is used to instruct to create the second network element.
  • the first network element further includes:
  • the third receiving module is configured to receive a session update request message sent by the second network element, where the session update request message is used to instruct to update the PDR in the first network element.
  • the first network element further includes:
  • the fourth receiving module is configured to receive a session deletion request message sent by the second network element, where the session deletion request message is used to instruct to delete the session between the second network element and the first network element.
  • the network element 100 provided in the embodiment of the present application may be used to implement the technical solution of the second network element in the above-mentioned user plane rerouting method embodiment of the present application.
  • the implementation principles and technical effects are similar, and will not be repeated here.
  • FIG. 12 is a schematic structural diagram of a network element provided by another embodiment of this application.
  • the network element 120 of this embodiment may include: a processor 1201 and a memory 1202.
  • the network element 120 may further include a transceiver 1203 for sending and receiving information and/or messages.
  • the memory 1202 is used to store program instructions
  • the processor 1201 is used to call and execute the program instructions stored in the memory 1202, and when the processor 1201 executes the program instructions stored in the memory 1202, the network element 120 is used to
  • the implementation principles and technical effects of the technical solutions for the first network element or the second network element in the above-mentioned user plane rerouting method embodiment of this application are similar, and will not be repeated here.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores an instruction, and when the instruction runs on a computer, the computer executes the above-mentioned user-oriented rerouting method in the above-mentioned embodiment of the present application.
  • the implementation principles and technical effects of the technical solutions of the first network element or the second network element are similar, and will not be repeated here.
  • the embodiment of the present application also provides a chip system, which includes a processor and may also include a memory, which is used to implement the technical solution of the first network element or the second network element in the above-mentioned user plane rerouting method embodiment of the present application , Its implementation principle and technical effect are similar, so I won’t repeat it here.
  • the chip system can be composed of chips, or can include chips and other discrete devices.
  • the embodiment of the present application also provides a program, when the program is executed by the processor, it is used to execute the technical solution of the first network element or the second network element in the above-mentioned user plane rerouting method embodiment of the present application, and its implementation principle and The technical effects are similar, so I won’t repeat them here.
  • the embodiment of the present application also provides a computer program product containing instructions, which when run on a computer, causes the computer to execute the technical solution for the first network element or the second network element in the above-mentioned user-face rerouting method embodiment of the present application , Its implementation principle and technical effect are similar, so I won’t repeat it here.
  • the processor involved in the embodiments of the present application may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and may implement or Perform the methods, steps, and logic block diagrams disclosed in the embodiments of the present application.
  • the general-purpose processor may be a microprocessor or any conventional processor.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the memory involved in the embodiment of the present application may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), for example Random-access memory (random-access memory, RAM).
  • the memory is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the disclosed device and method may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • each unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit may be implemented in the form of hardware, or may be implemented in the form of hardware plus software functional units.
  • the size of the sequence number of each process does not mean the order of execution.
  • the order of execution of each process should be determined by its function and internal logic. There should be any limitation to the implementation process of the embodiments of the present application.
  • all or part of it may be implemented 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 instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions 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 instructions may be transmitted from a website, computer, server, or data center.
  • 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 data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Landscapes

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

Abstract

本申请实施例提供一种用户面重路由方法及装置，该方法包括：第一网元接收第二网元发送的用户面重路由触发信息；其中，该用户面重路由触发信息为该第二网元监测到与报文检测规则PDR匹配的预设业务报文时发送的；该PDR用于指示触发用户面重路由的预设业务报文对应的匹配信息以及执行规则；进一步地，该第一网元根据该用户面重路由触发信息，执行用户面重路由。可见，本申请实施例可以实现运营商控制范围内的网元基于业务感知的用户面路径调整，无需第三方APP规划的功能实体触发用户面路径改变，从而提高了运营商网络的安全性。

Description

用户面重路由方法及装置
本申请要求于2019年6月28日提交中国专利局、申请号为201910578953.9、申请名称为“用户面重路由方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及网络技术领域，尤其涉及一种用户面重路由方法及装置。
背景技术
第五代移动通信5G(5th-generation，5G)网络架构中，5G核心网控制面与5G核心网用户面之间通过相应的接口进行消息交互，以实现控制面到用户面的用户策略下发以及用户面到控制面的事件上报等处理。在实际运用过程中，可能需要更改用户面路径。
相关技术中，由应用功能实体(Application Function，AF)发起用户面路径改变请求，通过网络能力开放功能实体(Network Exposure Function，NEF)和统一数据缓存功能实体(Unified Data Repository，UDR)来触发策略控制功能实体(Policy Control Function，PCF)通知会话管理功能实体(Session Management Function，SMF)重配置用户面功能实体(User Plane Function，UPF)的用户面路径。
但相关技术中，通过AF->NEF->UDR->PCF->SMF的业务触发路径实现的，其中涉及的服务较多，且AF属于第三方应用程序(Application，APP)规划的功能实体，不在运营商控制范围内。为了实现合理的路径规划，运营商需要通过NEF将运营商网络内部的业务规划开放给第三方APP，导致存在安全方面的问题。
发明内容
本申请实施例提供一种用户面重路由方法及装置，提高了运营商网络的安全性。
第一方面，本申请实施例提供一种用户面重路由方法，包括：
第一网元接收第二网元发送的用户面重路由触发信息；其中，该用户面重路由触发信息为该第二网元监测到与报文检测规则PDR匹配的预设业务报文时发送的；该PDR用于指示触发用户面重路由的预设业务报文对应的匹配信息以及执行规则；
该第一网元根据该用户面重路由触发信息，执行用户面重路由。
第一方面提供的用户面重路由触发信息方法中，通过第一网元接收第二网元发送的用户面重路由触发信息；其中，该用户面重路由触发信息为该第二网元监测到与报文检测规则PDR匹配的预设业务报文时发送的；该PDR用于指示触发用户面重路由的预设业务报文对应的匹配信息以及执行规则；进一步地，该第一网元根据该用户面 重路由触发信息，执行用户面重路由。可见，相对于相关技术中通过非运营商的第三方APP规划的功能实体触发用户面路径改变的方式，本申请实施例可以实现运营商控制范围内的网元基于业务感知的用户面路径调整，无需第三方APP规划的功能实体触发用户面路径改变，从而提高了运营商网络的安全性。
在一种可能的实现方式中，该PDR中包括：报文检测信息PDI、使用量上报规则URR；其中，该PDI用于指示该预设业务报文对应的匹配信息，该URR用于指示该预设业务报文对应的执行规则。
在一种可能的实现方式中，该方法还包括：
该第一网元根据预置的用于触发用户面重路由的策略生成该PDR，并将该PDR发送给该第二网元。
在一种可能的实现方式中，该方法还包括：
该第一网元从第三网元获取该第三网元中预置的用于触发用户面重路由的策略；
该第一网元根据该策略生成该PDR，并将该PDR发送给该第二网元。
在一种可能的实现方式中，该方法还包括：
该第一网元向该第二网元发送激活消息，该激活消息用于指示激活该第二网元中预置的该PDR。
在一种可能的实现方式中，该PDR携带于该第一网元向该第二网元发送的第一会话创建请求消息，该第一会话创建请求消息用于指示创建该第一网元与该第二网元之间的会话。
在一种可能的实现方式中，该激活消息携带于该第一网元向该第二网元发送的第二会话创建请求消息，该第二会话创建请求消息用于指示创建该第一网元与该第二网元之间的会话。
在一种可能的实现方式中，该第一网元根据该用户面重路由触发信息，执行用户面重路由，包括：
该第一网元向第四网元发送第一会话请求消息，以及向第五网元发送第二会话请求消息；其中，该第一会话请求消息用于指示创建或更新该第一网元与该第四网元之间的会话，该第二会话请求消息用于指示创建或更新该第一网元与该第五网元之间的会话，该第二会话请求消息中携带为该第五网元分配的业务报文分流规则；和/或，
该第一网元向该第二网元发送会话更新请求消息，该会话更新请求消息用于指示更新该第二网元中的PDR。
在一种可能的实现方式中，该第一网元根据该用户面重路由触发信息，执行用户面重路由，包括：
该第一网元创建与第四网元之间的会话；
该第一网元删除与该第二网元之间的会话。
在一种可能的实现方式中，该第一网元创建与第四网元之间的会话，包括：
该第一网元向该第四网元发送第三会话创建请求消息，该第三会话创建请求消息用于指示创建该第一网元与该第四网元之间的会话。
在一种可能的实现方式中，该第一网元删除与该第二网元之间的会话，包括：
该第一网元向该第二网元发送会话删除请求消息，该会话删除请求消息用于指示 删除该第一网元与该第二网元之间的会话。
在一种可能的实现方式中，该第一网元根据该用户面重路由触发信息，执行用户面重路由之前，该方法还包括：
该第一网元将该用户面重路由触发信息发送给该第三网元；
该第一网元接收该第三网元发送的指示信息，其中，该指示信息用于指示该第一网元执行用户面重路由。
第二方面，本申请实施例提供一种用户面重路由方法，包括：
第一网元根据报文检测规则PDR对业务报文进行监测；其中，该PDR用于指示触发用户面重路由的预设业务报文对应的匹配信息以及执行规则；
若该第一网元监测到与该PDR匹配的预设业务报文时，该第一网元根据该执行规则向第二网元发送用户面重路由触发信息。
第二方面提供的用户面重路由触发信息方法中，通过第一网元根据报文检测规则PDR对业务报文进行监测；若该第一网元监测到与该PDR匹配的预设业务报文时，该第一网元根据该执行规则向第二网元发送用户面重路由触发信息，以使第二网元根据用户面重路由触发信息执行用户面重路由。可见，相对于相关技术中通过非运营商的第三方APP规划的功能实体触发用户面路径改变的方式，本申请实施例可以实现运营商控制范围内的网元基于业务感知的用户面路径调整，无需第三方APP规划的功能实体触发用户面路径改变，从而提高了运营商网络的安全性。
在一种可能的实现方式中，该PDR中包括：报文检测信息PDI、使用量上报规则URR；其中，该PDI用于指示该预设业务报文对应的匹配信息，该URR用于指示该预设业务报文对应的执行规则。
在一种可能的实现方式中，该第一网元根据报文检测规则PDR对业务报文进行监测，包括：
该第一网元确定该业务报文的属性信息；
该第一网元将该属性信息与该PDI进行匹配；
若该属性信息与该PDI匹配，则该第一网元监测到该业务报文是与该PDR匹配的预设业务报文；和/或，
若该属性信息与该PDI不匹配，则该第一网元监测到该业务报文不是与该PDR匹配的预设业务报文。
在一种可能的实现方式中，该方法还包括：
该第一网元接收该第二网元发送的该PDR，其中，该PDR为该第二网元根据预置的用于触发用户面重路由的策略生成的，或者该PDR为该第二网元在从第三网元获取到用于触发用户面重路由的策略后所生成的。
在一种可能的实现方式中，该方法还包括：
该第一网元接收该第二网元发送的激活消息，该激活消息用于指示激活该第一网元中预置的该PDR。
在一种可能的实现方式中，该PDR携带于该第一网元接收到的该第二网元发送的第一会话创建请求消息，该第一会话创建请求消息用于指示创建该第二网元与该第一网元之间的会话。
在一种可能的实现方式中，该激活消息携带于该第一网元接收到的该第二网元发送的第二会话创建请求消息，该第二会话创建请求消息用于指示创建该第二网元与该第一网元之间的会话。
在一种可能的实现方式中，该方法还包括：
该第一网元接收该第二网元发送的会话更新请求消息，该会话更新请求消息用于指示更新该第一网元中的该PDR。
在一种可能的实现方式中，该方法还包括：
该第一网元接收该第二网元发送的会话删除请求消息，该会话删除请求消息用于指示删除该第二网元与该第一网元之间的会话。
第三方面，本申请实施例提供一种网元，该网元为第一网元，该第一网元包括：
第一接收模块，用于接收第二网元发送的用户面重路由触发信息；其中，该用户面重路由触发信息为该第二网元监测到与报文检测规则PDR匹配的预设业务报文时发送的；该PDR用于指示触发用户面重路由的预设业务报文对应的匹配信息以及执行规则；
重路由模块，用于根据该用户面重路由触发信息，执行用户面重路由。
在一种可能的实现方式中，该PDR中包括：报文检测信息PDI、使用量上报规则URR；其中，该PDI用于指示该预设业务报文对应的匹配信息，该URR用于指示该预设业务报文对应的执行规则。
在一种可能的实现方式中，该第一网元还包括：
第一生成模块，用于根据预置的用于触发用户面重路由的策略生成该PDR；
第一发送模块，用于将该PDR发送给该第二网元。
在一种可能的实现方式中，该第一网元还包括：
获取模块，用于从第三网元获取该第三网元中预置的用于触发用户面重路由的策略；
第二生成模块，用于根据该策略生成该PDR；
第二发送模块，用于将该PDR发送给该第二网元。
在一种可能的实现方式中，该第一网元还包括：
第三发送模块，用于向该第二网元发送激活消息，该激活消息用于指示激活该第二网元中预置的该PDR。
在一种可能的实现方式中，该PDR携带于该第一网元向该第二网元发送的第一会话创建请求消息，该第一会话创建请求消息用于指示创建该第一网元与该第二网元之间的会话。
在一种可能的实现方式中，该激活消息携带于该第一网元向该第二网元发送的第二会话创建请求消息，该第二会话创建请求消息用于指示创建该第一网元与该第二网元之间的会话。
在一种可能的实现方式中，该重路由模块具体用于：
向第四网元发送第一会话请求消息，以及向第五网元发送第二会话请求消息；其中，该第一会话请求消息用于指示创建或更新该第一网元与该第四网元之间的会话，该第二会话请求消息用于指示创建或更新该第一网元与该第五网元之间的会话，该第 二会话请求消息中携带为该第五网元分配的业务报文分流规则；和/或，
向该第二网元发送会话更新请求消息，该会话更新请求消息用于指示更新该第二网元中的PDR。
在一种可能的实现方式中，该重路由模块包括：
创建单元，用于创建与第四网元之间的会话；
删除单元，用于删除与该第二网元之间的会话。
在一种可能的实现方式中，该创建单元具体用于：
向该第四网元发送第三会话创建请求消息，该第三会话创建请求消息用于指示创建该第一网元与该第四网元之间的会话。
在一种可能的实现方式中，该删除单元具体用于：
向该第二网元发送会话删除请求消息，该会话删除请求消息用于指示删除该第一网元与该第二网元之间的会话。
在一种可能的实现方式中，该第一网元还包括：
第四发送模块，用于将该用户面重路由触发信息发送给该第三网元；
第二接收模块，用于接收该第三网元发送的指示信息，其中，该指示信息用于指示该第一网元执行用户面重路由。
第四方面，本申请实施例提供一种网元，该网元为第一网元，该第一网元包括：
监测模块，用于根据报文检测规则PDR对业务报文进行监测；其中，该PDR用于指示触发用户面重路由的预设业务报文对应的匹配信息以及执行规则；
发送模块，用于若该监测模块监测到与该PDR匹配的预设业务报文时，根据该执行规则向第二网元发送用户面重路由触发信息。
在一种可能的实现方式中，该PDR中包括：报文检测信息PDI、使用量上报规则URR；其中，该PDI用于指示该预设业务报文对应的匹配信息，该URR用于指示该预设业务报文对应的执行规则。
在一种可能的实现方式中，该监测模块具体用于：
确定该业务报文的属性信息；
将该属性信息与该PDI进行匹配；
若该属性信息与该PDI匹配，则监测到该业务报文是与该PDR匹配的预设业务报文；和/或，
若该属性信息与该PDI不匹配，则监测到该业务报文不是与该PDR匹配的预设业务报文。
在一种可能的实现方式中，该第一网元还包括：
第一接收模块，用于接收该第二网元发送的该PDR，其中，该PDR为该第二网元根据预置的用于触发用户面重路由的策略生成的，或者该PDR为该第二网元在从第三网元获取到用于触发用户面重路由的策略后所生成的。
在一种可能的实现方式中，该第一网元还包括：
第二接收模块，用于接收该第二网元发送的激活消息，该激活消息用于指示激活该第一网元中预置的该PDR。
在一种可能的实现方式中，该PDR携带于该第一网元接收到的该第二网元发送的 第一会话创建请求消息，该第一会话创建请求消息用于指示创建该第二网元与该第一网元之间的会话。
在一种可能的实现方式中，该激活消息携带于该第一网元接收到的该第二网元发送的第二会话创建请求消息，该第二会话创建请求消息用于指示创建该第二网元与该第一网元之间的会话。
在一种可能的实现方式中，该第一网元还包括：
第三接收模块，用于接收该第二网元发送的会话更新请求消息，该会话更新请求消息用于指示更新该第一网元中的该PDR。
在一种可能的实现方式中，该第一网元还包括：
第四接收模块，用于接收该第二网元发送的会话删除请求消息，该会话删除请求消息用于指示删除该第二网元与该第一网元之间的会话。
第五方面，本申请实施例提供一种网元，包括：处理器和存储器；
其中，该存储器，用于存储程序指令；
该处理器，用于调用并执行该存储器中存储的程序指令，当该处理器执行该存储器存储的程序指令时，该网元用于执行上述第一方面或第二方面的任一实现方式所述的方法。
第六方面，本申请实施例提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该指令在计算机上运行时，使得计算机执行上述第一方面或第二方面的任一实现方式所述的方法。
第七方面，本申请实施例提供一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现上述第一方面或第二方面的任一实现方式所述的方法。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第八方面，本申请实施例提供一种程序，该程序在被处理器执行时用于执行上述第一方面或第二方面的任一实现方式所述的方法。
第九方面，本申请实施例提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面或第二方面的任一实现方式所述的方法。
附图说明
图1为本申请实施例提供的5G网络架构的示意图一；
图2为本申请实施例提供的5G网络架构的示意图二；
图3为相关技术提供的上行报文分流的用户面架构示意图；
图4为相关技术提供的多宿主PDU会话的用户面架构示意图；
图5为相关技术提供的由AF触发用户面重路由的流程示意图；
图6为本申请一实施例提供的用户面重路由方法的流程示意图；
图7为本申请另一实施例提供的用户面重路由方法的流程示意图；
图8为本申请另一实施例提供的用户面重路由方法的流程示意图；
图9为本申请另一实施例提供的用户面重路由方法的流程示意图；
图10为本申请一实施例提供的网元的结构示意图；
图11为本申请另一实施例提供的网元的结构示意图；
图12为本申请另一实施例提供的网元的结构示意图。
具体实施方式
首先，对本申请实施例所涉及的网络架构和部分词汇进行解释说明。
图1为本申请实施例提供的5G网络架构的示意图一。如图1所示，5G网络架构中的控制面网元对外提供服务化接口，5G核心网控制面与5G核心网用户面之间通过相应的服务化接口进行消息交互，以实现控制面到用户面的用户策略下发以及用户面到控制面的事件上报等处理。
例如，网络切片选择功能实体(Network Slice Selection Function，NSSF)对外提供服务化接口Nnssf、NEF对外提供服务化接口Nnef、网络存储功能实体(Network Repository Function，NRF)对外提供服务化接口Nnrf、PCF对外提供服务化接口Npcf、统一数据管理(Unified Data Management，UDM)对外提供服务化接口Nudm、AF对外提供服务化接口Naf、认证服务功能实体(Authentication Server Function，AUSF)对外提供服务化接口Nausf、接入和移动性管理功能实体(Access and Mobility Management Function，AMF)对外提供服务化接口Namf、SMF对外提供服务化接口Nsmf。另外，终端与AMF之间通过N1接口连接，AMF与接入网(Access Network，AN)之间通过N2接口连接，AN与UPF之间通过N3接口连接，UPF与SMF之间通过N4接口连接，UPF与数据网络(Data Network，DN)之间通过N6接口连接。
图2为本申请实施例提供的5G网络架构的示意图二。如图2所示，5G网络架构中需要互联的两个网元之间具有一对一定义的网元间接口，5G核心网控制面与5G核心网用户面之间通过相应的网元间接口进行消息交互，以实现控制面到用户面的用户策略下发以及用户面到控制面板的事件上报等处理。
例如，N1为终端与AMF之间的网元间接口、N2为AN与AMF之间的网元间接口、N3为AN与UPF之间的网元间接口、N4为UPF与SMF之间的网元间接口、N5为PCF与AF之间的网元间接口、N6为UPF与DN之间的网元间接口、N7为SMF与PCF之间的网元间接口、N8为AMF与UDM之间的网元间接口、N9为UPF之间的网元间接口、N10为UDM与SMF之间的网元间接口、N11为AMF与SMF之间的网元间接口、N12为AMF与AUSF之间的网元间接口、N13为AUSF与UDM之间的网元间接口、N14为AMF之间的网元间接口、N15为AMF与PCF之间的网元间接口、N22为NSSF与AMF之间的网元间接口。
相关技术中定义了一个协议数据单元(Protocol Data Unit，PDU)会话(Session)可以支持多个PDU会话锚点(PDU Session Anchor，PSA)的场景。图3为相关技术提供的上行报文分流的用户面架构示意图，如图3所示，通过增加针对网际协议版本4(Internet Protocol version 4，IPv4)会话和非多宿主(Multi-home)的互联网协议第6版(Internet Protocol Version 6，IPv6)会话的上行报文分流(Uplink Classifier，ULCL)-UPF来实现单一会话多业务路径的分流处理，例如可以通过PSA-UPF1和PSA-UPF2进行分流处理。
图4为相关技术提供的多宿主PDU会话的用户面架构示意图，如图4所示，通过增加针对Multi-home的IPv6会话的分支节点(Branch Point，BP)-UPF来实现单一 会话多业务路径的分流处理，例如，可以通过PSA-UPF1和PSA-UPF2进行分流处理。
图5为相关技术提供的由AF触发用户面重路由的流程示意图。如图5所示，相关技术中的AF可以感知到访问其业务的终端以及终端的位置信息，由AF发起用户面路径改变请求，通过NEF和UDR来触发PCF通知SMF重配置UPF的用户面路径。例如，AF创建AF请求，并向NEF发送AF请求，以便NEF将AF请求保存到UDR中，其中，AF请求中可以包括但不限于：创建消息、更新消息或删除消息；进一步地，由于PCF已经向UDR订阅了AF请求变更时的通知服务，因此，UDR会向PCF发送通知消息，以便于PCF向SMF发送策略控制更新通知消息，以使SMF重配置UPF的用户面路径，从而使得将用户面路径切换到与终端最近的服务器。
但相关技术中，通过AF->NEF->UDR->PCF->SMF的业务触发路径实现的，其中涉及的服务较多，且AF属于第三方APP规划的功能实体，不在运营商控制范围内。为了实现合理的路径规划，运营商需要通过NEF将运营商网络内部的业务规划开放给第三方APP，导致存在安全方面的问题。
本申请实施例提供的用户面重路由方法及装置，通过运营商控制范围内的第二网元根据PDR对业务报文进行监测，在监测到与PDR匹配的预设业务报文时向第一网元发送用户面重路由触发信息，使得第一网元根据接收到的用户面重路由触发信息可以获知终端正在访问会触发用户面重路由的预设业务报文，进而执行用户面重路由。可见，相对于相关技术中通过非运营商的第三方APP规划的功能实体触发用户面路径改变的方式，本申请实施例可以实现运营商控制范围内的网元基于业务感知的用户面路径调整，无需第三方APP规划的功能实体触发用户面路径改变，从而提高了运营商网络的安全性。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，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可以是单个，也可以是多个。
下面以具体地实施例对本申请的技术方案进行详细说明。下面这几个具体的实施例可以相互结合，对于相同或相似的概念或过程可能在某些实施例中不再赘述。
图6为本申请一实施例提供的用户面重路由方法的流程示意图。如图6所示，本申请实施例的方法可以包括：
步骤S601、第二网元根据报文检测规则PDR对业务报文进行监测；其中，PDR用于指示触发用户面重路由的预设业务报文对应的匹配信息以及执行规则。
示例性地，本申请实施例中涉及的第二网元可以是指终端的初始会话对应的源锚点PSA-UPF1。
本申请实施例中涉及的预设业务报文是指会触发用户面重路由的预设业务对应的报文。示例性地，预设业务可以包括但不限于：预设的服务器互联网协议(Internet  Protocol，IP)地址段发生的访问业务，或者，预设应用或APP发生的访问业务。
本申请实施例中涉及的PDR中可以包括但不限于：报文检测信息(Packet Detection Information，PDI)、使用量上报规则(Usage Reporting Rule，URR)；PDR中还可以包括QoS执行规则(QoS Enforcement Rule，QER)和/或转发动作规则(Forwarding Action Rule，FAR)。
示例性地，PDI用于指示预设业务报文对应的匹配信息，例如PDI可以包括但不限于：预设报文的全量隧道端点标识(Full Qualified Tunnel Endpoint Identifier，F-TEID)、源目的端口、源目的IP地址、IP协议类型、应用身份标识号(Identity document，ID)。
示例性地，URR、QoS执行规则和/或FAR均用于指示预设业务报文对应的执行规则。
可选地，本步骤中第二网元在接收到任意业务报文时，首先确定业务报文的属性信息，例如，业务报文的属性信息可以包括但不限于：业务报文的F-TEID、源目的端口、源目的IP地址、IP协议类型、应用ID。其次，第二网元将属性信息与PDI进行对比匹配。若业务报文的属性信息与PDI匹配，则第二网元监测到业务报文是与PDR匹配的预设业务报文；若业务报文的属性信息与PDI不匹配，则第二网元监测到业务报文不是与PDR匹配的预设业务报文。
例如，假设PDI包括：预设报文的F-TEID、源目的端口、源目的IP地址、IP协议类型，业务报文的属性信息包括：业务报文的F-TEID、源目的端口、源目的IP地址、IP协议类型，若业务报文的F-TEID与预设报文的F-TEID相同、业务报文的源目的端口与预设报文的源目的端口相同、业务报文的源目的IP地址与预设报文的源目的IP地址相同，以及业务报文的IP协议类型与预设报文的IP协议类型相同，则第二网元确定业务报文的属性信息与PDI匹配，从而监测到业务报文是与PDR匹配的预设业务报文；否则(例如，业务报文的F-TEID与预设报文的F-TEID、业务报文的源目的端口与预设报文的源目的端口、业务报文的源目的IP地址与预设报文的源目的IP地址、业务报文的IP协议类型与预设报文的IP协议类型中的任意不相同)，第二网元确定业务报文的属性信息与PDI不匹配，从而监测到业务报文不是与PDR匹配的预设业务报文。
本申请下述实施例对第二网元中的PDR的获取方式进行介绍。
一种可能的实现方式，第一网元根据预置的用于触发用户面重路由的策略生成PDR，并将PDR发送给第二网元；对应地，第二网元接收第一网元发送的PDR。
示例性地，本申请实施例中涉及的第一网元可以是SMF。
本申请实施例中涉及的预置的用于触发用户面重路由的策略可以包括但不限于以下任一项：
终端访问预设业务时需要选择一个特定的UPF作为分流UPF插入会话信息、选择另一个特定的UPF作为新的本地锚点建立新的会话信息，以及向分流UPF下发用于指示将业务流(包括多个业务报文)分别通过源锚点和新的本地锚点进行分发的策略；
终端访问预设业务时需要选择一个特定的UPF作为新的本地锚点建立新的会话信息，以及删除源锚点上的会话信息；
若新的本地锚点的第一预设距离范围内部署了内容分发网络(Content Delivery Network，CDN)服务器，则可以将预设业务的业务流通过新的本地锚点进行分发，从而可以直接访问CDN服务器以提高服务质量以及业务访问效率的策略；
若车辆服务器部署在自动驾驶车辆的第二预设距离范围内的新的本地锚点所对应的DN网络内，则在自动驾驶车辆中的终端访问预设业务时，可以通过新的本地锚点进行业务访问。
本实现方式中，第一网元中预置有用于触发用户面重路由的策略，第一网元可以根据预置的策略生成PDR，然后将生成的PDR发送给第二网元。示例性地，PDR可以携带于第一网元向第二网元发送的第一会话创建请求消息，第一会话创建请求消息用于指示创建第一网元与第二网元之间的会话；当然，PDR还可以携带于第一网元向第二网元发送的其它消息中(例如，会话更新请求消息等)。
另一种可能的实现方式，第一网元从第三网元获取第三网元中预置的用于触发用户面重路由的策略；第一网元根据策略生成PDR，并将PDR发送给第二网元；对应地，第二网元接收第一网元发送的PDR。
示例性地，本申请实施例中涉及的第三网元可以是PCF。
本实现方式中，第三网元中预置有用于触发用户面重路由的策略，第一网元可以从第三网元中获取第三网元中预置的策略，然后根据获取的策略生成PDR，并将生成的PDR发送给第二网元。示例性地，PDR可以携带于第一网元向第二网元发送的第一会话创建请求消息；当然，PDR还可以携带于第一网元向第二网元发送的其它消息中(例如，会话更新请求消息等)。
另一种可能的实现方式，第一网元向第二网元发送激活消息，激活消息用于指示激活第二网元中预置的PDR；对应地，第二网元接收第一网元发送的激活消息。
本实现方式中，第二网元中预先设置有PDR，第一网元通过向第二网元发送激活消息，以激活第二网元中预置的PDR。示例性地，激活消息可以携带于第一网元向第二网元发送的第二会话创建请求消息，第二会话创建请求消息用于指示创建第二网元与第一网元之间的会话；当然，激活消息还可以携带于第一网元向第二网元发送的其它消息中(例如，会话更新请求消息等)。
步骤S602、若第二网元监测到与PDR匹配的预设业务报文时，第二网元根据执行规则向第一网元发送用户面重路由触发信息。
本步骤中，若第二网元监测到与PDR匹配的预设业务报文时，第二网元根据PDR中的执行规则向第一网元发送用户面重路由触发信息，以使第一网元根据用户面重路由触发信息可以获知终端正在访问会触发用户面重路由的预设业务报文，从而执行用户面重路由。
步骤S603、第一网元接收第二网元发送的用户面重路由触发信息。
本步骤中，第一网元接收第二网元发送的用户面重路由触发信息，从而获知终端正在访问会触发用户面重路由的预设业务报文；其中，用户面重路由触发信息为第二网元监测到与报文检测规则PDR匹配的预设业务报文时发送的。
步骤S604、第一网元根据用户面重路由触发信息，执行用户面重路由。
本步骤中，第一网元根据用户面重路由触发信息，执行用户面重路由的操作。具 体的，执行用户面重路由的操作可以包括但不限于以下几种可实现方式。
一种可能的实现方式，第一网元向第四网元发送第一会话请求消息，以及向第五网元发送第二会话请求消息；其中，第一会话请求消息用于指示创建或更新第一网元与第四网元之间的会话，第二会话请求消息用于指示创建或更新第一网元与第五网元之间的会话，第二会话请求消息中携带为第五网元分配的业务报文分流规则；和/或，
第一网元向第二网元发送会话更新请求消息，会话更新请求消息用于指示更新第二网元中的PDR；对应地，第二网元接收第一网元发送的会话更新请求消息。
示例性地，本申请实施例中涉及的第四网元可以是指终端的新建会话对应的新的本地锚点PSA-UPF2。
示例性地，针对IPv4会话和/或非Multi-home的IPv6会话，本申请实施例中涉及的第五网元可以是指ULCL-UPF；针对Multi-home的IPv6会话，本申请实施例中涉及的第五网元可以是指BP-UPF。
本实现方式中，第一网元可以向第四网元发送用于指示创建或更新第一网元与第四网元之间的会话的第一会话请求消息，以及向第五网元发送用于指示创建或更新第一网元与第五网元之间的会话的第二会话请求消息；其中，第二会话请求消息中还可以携带为第五网元分配的业务报文分流规则，以使第五网元根据业务报文分流规则对业务报文进行分发。
需要说明的是，若第一网元已创建了第一网元与第四网元之间的会话，则第一会话请求消息用于指示更新第一网元与第四网元之间的会话；若第一网元未创建第一网元与第四网元之间的会话，则第一会话请求消息用于指示创建第一网元与第四网元之间的会话。和/或，若第一网元已创建了第一网元与第五网元之间的会话，则第二会话请求消息用于指示更新第一网元与第五网元之间的会话；若第一网元未创建第一网元与第五网元之间的会话，则第二会话请求消息用于指示创建第一网元与第五网元之间的会话。
本实现方式中，第一网元还可以向第二网元发送会话更新请求消息，对应地，第二网元接收第一网元发送的会话更新请求消息，其中，会话更新请求消息用于指示更新第二网元中的PDR。
示例性地，会话更新请求消息可以用于指示将原有PDR的FAR动作中携带的接口隧道信息更新为第二网元与第五网元之间的接口隧道信息(例如，接口地址和/或F-TEID)。
可选地，若第二网元中的PDR为第一网元在从第三网元获取到用于触发用户面重路由的策略后所生成的，并发送给第二网元的，则第一网元在根据用户面重路由触发信息，执行用户面重路由之前，首先将用户面重路由触发信息发送给第三网元，以使第三网元根据预置的用于触发用户面重路由的策略向第一网元发送用于指示第一网元执行用户面重路由的指示信息，其次接收第三网元发送的指示信息。
另一种可能的实现方式，第一网元创建与第四网元之间的会话，并删除与第二网元之间的会话。
示例性地，第一网元可以通过向第四网元发送用于指示创建第一网元与第四网元之间的会话的第三会话创建请求消息，对应地，第四网元在接收到第一网元发送的第 三会话创建请求消息后，还可以向第一网元发送第三会话创建请求消息对应的会话创建响应消息，以实现创建第一网元与第四网元之间的会话。
示例性地，第一网元可以通过向第二网元发送用于指示删除第一网元与第二网元之间的会话的会话删除请求消息，对应地，第二网元在接收到第一网元发送的会话删除请求消息后，还可以向第一网元发送会话删除请求消息对应的会话删除响应消息，以实现删除第一网元与第二网元之间的会话。
本申请实施例中，第二网元根据报文检测规则PDR对业务报文进行监测；若第二网元监测到与PDR匹配的预设业务报文时，第二网元根据执行规则向第一网元发送用户面重路由触发信息；进一步地，第一网元根据接收到的用户面重路由触发信息执行用户面重路由。相对于相关技术中通过非运营商的第三方APP规划的功能实体触发用户面路径改变的方式，本申请实施例中通过运营商控制范围内的第二网元根据PDR对业务报文进行监测，在监测到与PDR匹配的预设业务报文时向第一网元发送用户面重路由触发信息，使得第一网元根据接收到的用户面重路由触发信息可以获知终端正在访问会触发用户面重路由的预设业务报文，进而执行用户面重路由。可见，本申请实施例可以实现运营商控制范围内的网元基于业务感知的用户面路径调整，无需第三方APP规划的功能实体触发用户面路径改变，从而提高了运营商网络的安全性。
图7为本申请另一实施例提供的用户面重路由方法的流程示意图。在上述实施例的基础上，本申请实施例中以PSA-UPF1根据SMF下发的PDR监测业务报文，并在监测到与PDR匹配的预设业务报文时向SMF发送用户面重路由触发信息，以使得SMF执行分流UPF和PSA-UPF2的会话新建以及业务报文分流规则下发等用户面重路由操作为例，对用户面重路由方法进行介绍。
本申请实施例中，SMF中预置有用于触发用户面重路由的策略，例如，终端访问预设业务时需要选择一个特定的UPF作为分流UPF插入会话信息、选择另一个特定的UPF作为新的本地锚点PSA-UPF2建立新的会话信息，以及向分流UPF下发用于指示将业务流(包括多个业务报文)分别通过源锚点PSA-UPF1和新的本地锚点PSA-UPF2进行分发的策略等。
本实施例中，SMF可以根据预置的策略生成对应的PDR，其中，PDR中可以包括但不限于：PDI和URR。
示例性地，针对IPv4会话和/或非Multi-home的IPv6会话，本申请实施例中涉及的分流UPF可以是指ULCL-UPF；针对Multi-home的IPv6会话，本申请实施例中涉及的分流UPF可以是指BP-UPF。
如图7所示，本申请实施例的方法可以包括：
步骤S701、终端向SMF发送会话建立请求消息。
步骤S702、SMF向PSA-UPF1发送会话创建请求消息1，其中，会话创建请求消息1用于指示创建SMF与PSA-UPF1之间的会话。
示例性地，会话创建请求消息1中携带有SMF根据预置的策略所生成的PDR，其中，PDR中可以包括但不限于：PDI和URR。
表1为会话创建请求消息1中URR信息元素(Information Elements，IE)的结构 示意表
Figure PCTCN2020098561-appb-000001
如表1所示，URR信息元素中增加了上报的触发点(Reporting Triggers)，用于指示向控制面(Control Plane，CP)功能实体报告网络资源使用量的触发点。其中，上报的触发点的具体格式可以如表2所示，当八位组(Octet)6的位(Bit)7-RERT(重路由业务)设置为1时，表示在检测到存在重路由业务流时发送报告请求。
表2为上报的触发点的结构示意表
Figure PCTCN2020098561-appb-000002
Octet 5的编码可以如下：
位1-周期上报(Periodic Reporting，PERIO)：当设置为1时，表示请求定期报告；
位2-流量阈值(Volume Threshold，VOLTH)：当设置为1时，表示数据使用量达到使用量阈值时请求报告；
位3-时长阈值(Time Threshold，TIMTH)：当设置为1时，表示当时间使用达到时间阈值时请求报告；
位4-配额保持时长(Quota Holding Time，QUHTI)：当设置为1时，表示在超过配额保持时长的时间段内没有接收到数据包时请求报告；
位5-业务开始(Start of Traffic，START)：当设置为1时，表示在检测到业务数据流(Service Data Flow，SDF)或应用业务开始时请求报告；
位6-业务停止(Stop of Traffic，STOPT)：当设置为1时，表示在检测到SDF或应用业务停止时请求报告；
位7-丢弃下行业务的阈值(Dropped DL Traffic Threshold，DROTH)：当设置为1时，表示当丢弃的下行业务达到阈值时请求报告；
位8-关联的使用量上报事件(Linked Usage Reporting，LIUSA)：当设置为1时，表示关联的使用量上报请求，例如，当关联的使用量上报规则发起使用量上报时，需要同时触发该使用量上报规则的使用量上报请求；
Octet 6的编码可以如下：
位1-流量配额(Volume Quota，VOLQU)：当设置为1时，表示在流量配额耗尽时请求报告；
位2-时长配额(Time Quota，TIMQU)：当设置为1时，表示在时长配额用尽时请求报告；
位3-信封关闭(Envelope Closure，ENVCL)：当设置为1时，表示满足信封关闭条件时请求报告；
位4-MAC地址上报(MAC Addresses Reporting，MACAR)：当设置为1时，指示MAC(以太网)地址用作UE发送的上行(Uplink，UL)数据帧的源地址时请求报告；
位5-事件阈值(Event Threshold，EVETH)：当设置为1时，表示达到事件阈值时请求报告；
位6-事件配额(Event Quota，EVEQU)：当设置为1时，表示在达到事件配额时请求报告；
位7-重路由业务(Rerouting of Traffic，RERT)：当设置为1时，表示在检测到存在重路由的SDF或应用业务时请求报告；
位8：备用，供将来使用并设置为0。
步骤S703、PSA-UPF1向SMF发送会话创建响应消息1。
步骤S704、SMF向终端发送会话建立响应消息。
步骤S705、终端发起业务访问。
步骤S706、PSA-UPF1根据PDR对业务报文进行监测。
示例性地，若PSA-UPF1监测到与PDR中的PDI匹配的预设业务报文时，则执行步骤S707。
步骤S707、PSA-UPF1向SMF发送会话报告请求消息。
示例性地，PSA-UPF1在监测到与PDR中的PDI匹配的预设业务报文时，根据PDR中的URR(包含用于指示业务重路由的Reporting Triggers)向SMF发送会话报告请求消息，其中，会话报告请求消息中携带用户面重路由触发信息。
表3为会话报告请求消息中使用量上报(Usage Report)IE的结构示意表
Figure PCTCN2020098561-appb-000003
如表3所示，使用量上报的触发原因(Usage Report Trigger)用于指示使用量上报的触发原因，本申请实施例中增加了重路由业务触发原因(Traffic Rerouting Trigger)，或者称之为用户面重路由触发信息。其中，使用量上报的触发原因的具体格式可以如表4所示，当八位组7的位2-RERT设置为1时，表示检测到存在重路由业务流(即重路由业务触发原因，或者用户面重路由触发信息)。
表4为使用量上报的触发原因的结构示意表
Figure PCTCN2020098561-appb-000004
Octet 5的编码可以如下：
位1-PERIO：当设置为1时，表示定期报告；
位2-VOLTH：设置为1时，表示数据使用量达到使用量阈值；
位3-TIMTH)：设置为1时，表示时间使用达到时间阈值；
位4-QUHTI：当设置为1时，表示在超过配额保持时长的时间段内没有收到任何数据包；
位5-START：当设置为1时，表示检测到业务开始；
位6-STOPT：当设置为1时，表示检测到业务停止；
位7-DROTH：当设置为1时，表示丢弃的下行业务达到阈值；
位8-立即上报(Immediate Report，IMMER)(指收到CP的消息后，立即触发的URR上报)：当设置为1时，表示基于CP功能实体的要求触发一个即时的使用量上报请求；
Octet 6的编码可以如下：
位1-VOLQU：设置为1时，表示流量配额已用尽；
位2-TIMQU：设置为1时，表示时长配额已用尽；
位3-LIUSA：当设置为1时，表示关联的使用量上报，例如，由于关联的使用量 上报规则的使用量上报，因此，该使用量上报规则的使用量上报；
位4-终止报告(Termination Report，TERMR)：当设置为1时，表示由于PFCP会话终止而导致使用量上报(在PFCP会话删除响应中)，或者由于移除了URR而导致使用量上报(在PFCP会话修改响应中)；
位5-监视时间(Monitoring Time，MONIT)：当设置为1时，表示由于达到监视时间而报告URR的使用量上报；
位6-ENVCL：当设置为1时，表示信封关闭时生成使用量上报；
位7-MACAR：当设置为1时，指示MAC(以太网)地址用作UE发送的UL数据帧的源地址的使用量上报；
位8-EVETH：当设置为1时，表示达到事件阈值时生成使用量上报；
Octet 7的编码可以如下：
位1-EVEQU：当设置为1时，表示事件配额已用尽；
位2-RERT：当设置为1时，表示在检测到存在重路由的SDF或应用业务；
位3到8：备用，以备将来使用并设置为0。
步骤S708、SMF向PSA-UPF1发送会话报告响应消息。
步骤S709、SMF根据会话报告请求消息中的用户面重路由触发信息，确定需要执行用户面重路由。
示例性地，SMF根据会话报告请求消息中的用户面重路由触发信息确定需要执行分流UPF和PSA-UPF2的会话新建以及业务报文分流规则下发的预设业务已经触发，从而需要执行用户面重路由。
步骤S710、SMF向PSA-UPF2发送会话创建请求消息2，其中，会话创建请求消息2用于指示创建SMF与PSA-UPF2之间的会话。
步骤S711、PSA-UPF2向SMF发送会话创建响应消息2。
步骤S712、SMF向分流UPF发送会话创建请求消息3，其中，会话创建请求消息3用于指示创建SMF与分流UPF之间的会话。
示例性地，会话创建请求消息3中携带有为分流UPF分配的业务报文分流规则，以使分流UPF根据业务报文分流规则将业务报文通过源锚点PSA-UPF1和新的本地锚点PSA-UPF2进行分发。
步骤S713、分流UPF向SMF发送会话创建响应消息3。
步骤S714、SMF向PSA-UPF1发送会话更新请求消息，会话更新请求消息用于指示更新PSA-UPF1中的PDR。
示例性地，会话更新请求消息用于指示将PSA-UPF1原有PDR的FAR动作中携带的接口隧道信息更新为PSA-UPF1与分流UPF之间的接口隧道信息(例如，接口地址和/或F-TEID)。
步骤S715、PSA-UPF1向SMF发送会话更新响应消息。
步骤S716、分流UPF根据业务报文分流规则将终端发送的业务报文通过PSA-UPF1和PSA-UPF2转发到DN。
示例性地，分流UPF根据业务报文分流规则可以将预设业务报文分流到PSA-UPF2进行数据网络访问，其他业务报文仍然转发至PSA-UPF1继续进行访问。
本申请实施例中，PSA-UPF1可以根据PDR对业务报文进行监测，在监测到与PDR匹配的预设业务报文时向SMF发送用户面重路由触发信息；SMF根据用户面重路由触发信息可以获知需要执行分流UPF和PSA-UPF2的会话新建以及业务报文分流规则下发的预设业务已经触发，进而执行分流UPF和PSA-UPF2的会话建立流程，以便于将特定业务流分流到相应的锚点UPF进行数据网络访问。可见，本申请实施例可以实现基于业务感知的用户面路径调整，无需第三方APP规划的功能实体感知和触发用户面重路由，从而提高了运营商网络的安全性。
图8为本申请另一实施例提供的用户面重路由方法的流程示意图。在上述实施例的基础上，本申请实施例以PSA-UPF1根据SMF下发的PDR监测业务报文，并在监测到与PDR匹配的预设业务报文时向SMF发送用户面重路由触发信息，以使得SMF执行PSA-UPF2的会话新建和PSA-UPF1的会话删除等用户面重路由操作为例，对用户面重路由方法进行介绍。
本申请实施例中，SMF中预置有用于触发用户面重路由的策略，例如，终端访问预设业务时需要选择一个特定的UPF作为新的本地锚点PSA-UPF2建立新的会话信息，以及删除源锚点PSA-UPF1上的会话信息等。
本实施例中，SMF可以根据预置的策略生成对应的PDR，其中，PDR中可以包括但不限于：PDI和URR。
如图8所示，本申请实施例的方法可以包括：
步骤S801、终端向SMF发送会话建立请求消息。
步骤S802、SMF向PSA-UPF1发送会话创建请求消息1，其中，会话创建请求消息1用于指示创建SMF与PSA-UPF1之间的会话。
示例性地，会话创建请求消息1中携带有SMF根据预置的策略所生成的PDR，其中，PDR中可以包括但不限于：PDI和URR。
其中，会话创建请求消息1中URR信息元素的结构如表1和表2所示，此处不再赘述。
步骤S803、PSA-UPF1向SMF发送会话创建响应消息1。
步骤S804、SMF向终端发送会话建立响应消息。
步骤S805、终端发起业务访问。
步骤S806、PSA-UPF1根据PDR对业务报文进行监测。
示例性地，若PSA-UPF1监测到与PDR中的PDI匹配的预设业务报文时，则执行步骤S807。
步骤S807、PSA-UPF1向SMF发送会话报告请求消息。
示例性地，PSA-UPF1在监测到与PDR中的PDI匹配的预设业务报文时，根据PDR中的URR(包含用于指示业务重路由的Reporting Triggers)向SMF发送会话报告请求消息，其中，会话报告请求消息中携带用户面重路由触发信息。
其中，会话报告请求消息中使用量上报(Usage Report)IE的结构如表3和表4所示，此处不再赘述。
步骤S808、SMF向PSA-UPF1发送会话报告响应消息。
步骤S809、SMF根据会话报告请求消息中的用户面重路由触发信息，确定需要执行用户面重路由。
示例性地，SMF根据会话报告请求消息中的用户面重路由触发信息确定需要执行PSA-UPF2的会话新建和PSA-UPF1的会话删除的预设业务已经触发，从而需要执行用户面重路由。
步骤S810、SMF向PSA-UPF2发送会话创建请求消息2，其中，会话创建请求消息2用于指示创建SMF与PSA-UPF2之间的会话。
步骤S811、PSA-UPF2向SMF发送会话创建响应消息2。
步骤S812、SMF向PSA-UPF1发送会话删除请求消息，会话删除请求消息用于指示删除SMF与PSA-UPF1之间的会话。
步骤S813、PSA-UPF1向SMF发送会话删除响应消息。
步骤S814、PSA-UPF2对终端发送的业务报文进行转发处理。
本申请实施例中，PSA-UPF1可以根据PDR对业务报文进行监测，在监测到与PDR匹配的预设业务报文时向SMF发送用户面重路由触发信息；SMF根据用户面重路由触发信息可以获知需要执行PSA-UPF2的会话新建和PSA-UPF1的会话删除的预设业务已经触发，进而执行PSA-UPF2的会话建立和PSA-UPF1的会话删除流程，使得终端发送的所有业务报文通过PSA-UPF2进行数据网络访问。可见，本申请实施例可以实现基于业务感知的用户面路径调整，无需第三方APP规划的功能实体感知和触发用户面重路由，从而提高了运营商网络的安全性。
图9为本申请另一实施例提供的用户面重路由方法的流程示意图。在上述实施例的基础上，本申请实施例以PSA-UPF1根据SMF下发的PDR监测业务报文(为SMF从PCF获取到用于触发用户面重路由的策略后所生成的)，并在监测到与PDR匹配的预设业务报文时向SMF发送用户面重路由触发信息，以使得SMF将用户面重路由触发信息上报给PCF，并在接收到PCF发送的用于指示SMF执行用户面重路由的指示信息后，执行分流UPF和PSA-UPF2的会话新建以及业务报文分流规则下发等用户面重路由操作为例，对用户面重路由方法进行介绍。
本申请实施例中，PCF中预置有用于触发用户面重路由的策略，例如，终端访问预设业务时需要选择一个特定的UPF作为分流UPF插入会话信息、选择另一个特定的UPF作为新的本地锚点PSA-UPF2建立新的会话信息，以及向分流UPF下发用于指示将业务流(包括多个业务报文)分别通过源锚点PSA-UPF1和新的本地锚点PSA-UPF2进行分发的策略等。
示例性地，针对IPv4会话和/或非Multi-home的IPv6会话，本申请实施例中涉及的分流UPF可以是指ULCL-UPF；针对Multi-home的IPv6会话，本申请实施例中涉及的分流UPF可以是指BP-UPF。
如图9所示，本申请实施例的方法可以包括：
步骤S901、终端向SMF发送会话建立请求消息。
步骤S902、SMF向PCF发送策略控制创建请求消息，其中，策略控制创建请求消息用于指示获取用于触发用户面重路由的策略。
步骤S903、PCF向SMF发送策略控制创建响应消息，其中，策略控制创建响应消息中携带用于触发用户面重路由的策略；当然，策略控制创建响应消息中还可以携带计费与控制策略等其它策略。
示例性地，策略控制创建响应消息中可以包括策略控制请求触发原因(Policy Control Request Triggers)指示信息。如表5所示，策略控制请求触发原因指示信息中可以包括但不限于重路由策略(或者称之为用于触发用户面重路由的策略)，用于指示当SMF监测到终端访问了需要执行用户面重路由的预设业务时上报策略控制更新请求。
表5为策略控制请求触发原因指示信息的示意表
Figure PCTCN2020098561-appb-000005
步骤S904、SMF根据从PCF获取的用于触发用户面重路由的策略生成对应的PDR，其中，PDR中可以包括但不限于：PDI和URR。
步骤S905、SMF向PSA-UPF1发送会话创建请求消息1，其中，会话创建请求消息1用于指示创建SMF与PSA-UPF1之间的会话。
示例性地，会话创建请求消息1中携带有PDR，其中，PDR中可以包括但不限于：PDI和URR。
其中，会话创建请求消息1中URR信息元素的结构如表1和表2所示，此处不再赘述。
步骤S906、PSA-UPF1向SMF发送会话创建响应消息1。
步骤S907、SMF向终端发送会话建立响应消息。
步骤S908、终端发起业务访问。
步骤S909、PSA-UPF1根据PDR对业务报文进行监测。
示例性地，若PSA-UPF1监测到与PDR中的PDI匹配的预设业务报文时，则执行步骤S910。
步骤S910、PSA-UPF1向SMF发送会话报告请求消息。
示例性地，PSA-UPF1在监测到与PDR中的PDI匹配的预设业务报文时，根据PDR中的URR(包含用于指示业务重路由的Reporting Triggers)向SMF发送会话报告请求消息，其中，会话报告请求消息中携带用户面重路由触发信息。
其中，会话报告请求消息中使用量上报(Usage Report)IE的结构如表3和表4所示，此处不再赘述。
步骤S911、SMF向PSA-UPF1发送会话报告响应消息。
步骤S912、SMF向PCF发送策略控制更新请求消息。
示例性地，SMF根据会话报告请求消息中的用户面重路由触发信息确定需要执行分流UPF和PSA-UPF2的会话新建以及业务报文分流规则下发的预设业务已经触发，从而向PCF发送策略控制更新请求消息，其中，策略控制更新请求消息中可以携带用户面重路由触发信息。
步骤S913、PCF向SMF发送策略控制更新响应消息，其中，策略控制更新响应消息中可以携带用于指示SMF执行用户面重路由的指示信息。
步骤S914、SMF根据收到的用于指示SMF执行用户面重路由的指示信息，确定执行用户面重路由。
步骤S915、SMF向PSA-UPF2发送会话创建请求消息2，其中，会话创建请求消息2用于指示创建SMF与PSA-UPF2之间的会话。
步骤S916、PSA-UPF2向SMF发送会话创建响应消息2。
步骤S917、SMF向分流UPF发送会话创建请求消息3，其中，会话创建请求消息3用于指示创建SMF与分流UPF之间的会话。
示例性地，会话创建请求消息3中携带有为分流UPF分配的业务报文分流规则，以使分流UPF根据业务报文分流规则将业务报文通过源锚点PSA-UPF1和新的本地锚点PSA-UPF2进行分发。
步骤S918、分流UPF向SMF发送会话创建响应消息3。
步骤S919、SMF向PSA-UPF1发送会话更新请求消息，会话更新请求消息用于指示更新PSA-UPF1中的PDR。
示例性地，会话更新请求消息用于指示将PSA-UPF1原有PDR的FAR动作中携带的接口隧道信息更新为PSA-UPF1与分流UPF之间的接口隧道信息(例如，接口地址和/或F-TEID)。
步骤S920、PSA-UPF1向SMF发送会话更新响应消息。
步骤S921、分流UPF根据业务报文分流规则将终端发送的业务报文通过PSA-UPF1和PSA-UPF2转发到DN。
示例性地，分流UPF根据业务报文分流规则可以将预设业务报文分流到PSA-UPF2进行数据网络访问，其他业务报文仍然转发至PSA-UPF1继续进行访问。
本申请实施例中，PSA-UPF1可以根据PDR对业务报文进行监测，在监测到与PDR匹配的预设业务报文时向SMF发送用户面重路由触发信息；SMF根据用户面重路由触发信息可以获知需要执行分流UPF和PSA-UPF2的会话新建以及业务报文分流规则下发的预设业务已经触发，并上报给PCF，进而在接收到PCF发送的用于指示SMF执行用户面重路由的指示信息后，执行分流UPF和PSA-UPF2的会话建立流程，以便于将特定业务流分流到相应的锚点UPF进行数据网络访问。可见，本申请实施例可以实现基于业务感知的用户面路径调整，无需第三方APP规划的功能实体感知和触发用户面重路由，从而提高了运营商网络的安全性。
图10为本申请一实施例提供的网元的结构示意图。可选地，本申请实施例提供的网元可以为第一网元。如图10所示，本申请实施例的网元100可以包括：第一接收模块1001以及重路由模块1002。
其中，第一接收模块1001，用于接收第二网元发送的用户面重路由触发信息；其中，该用户面重路由触发信息为该第二网元监测到与报文检测规则PDR匹配的预设业务报文时发送的；该PDR用于指示触发用户面重路由的预设业务报文对应的匹配信息以及执行规则；
重路由模块1002，用于根据该用户面重路由触发信息，执行用户面重路由。
在一种可能的实现方式中，该PDR中包括：报文检测信息PDI、使用量上报规则URR；其中，该PDI用于指示该预设业务报文对应的匹配信息，该URR用于指示该预设业务报文对应的执行规则。
在一种可能的实现方式中，该第一网元还包括：
第一生成模块，用于根据预置的用于触发用户面重路由的策略生成该PDR；
第一发送模块，用于将该PDR发送给该第二网元。
在一种可能的实现方式中，该第一网元还包括：
获取模块，用于从第三网元获取该第三网元中预置的用于触发用户面重路由的策略；
第二生成模块，用于根据该策略生成该PDR；
第二发送模块，用于将该PDR发送给该第二网元。
在一种可能的实现方式中，该第一网元还包括：
第三发送模块，用于向该第二网元发送激活消息，该激活消息用于指示激活该第二网元中预置的该PDR。
在一种可能的实现方式中，该PDR携带于该第一网元向该第二网元发送的第一会话创建请求消息，该第一会话创建请求消息用于指示创建该第一网元与该第二网元之间的会话。
在一种可能的实现方式中，该激活消息携带于该第一网元向该第二网元发送的第二会话创建请求消息，该第二会话创建请求消息用于指示创建该第一网元与该第二网元之间的会话。
在一种可能的实现方式中，该重路由模块1002具体用于：
向第四网元发送第一会话请求消息，以及向第五网元发送第二会话请求消息；其中，该第一会话请求消息用于指示创建或更新该第一网元与该第四网元之间的会话，该第二会话请求消息用于指示创建或更新该第一网元与该第五网元之间的会话，该第二会话请求消息中携带为该第五网元分配的业务报文分流规则；和/或，
向该第二网元发送会话更新请求消息，该会话更新请求消息用于指示更新该第二网元中的PDR。
在一种可能的实现方式中，该重路由模块1002包括：
创建单元，用于创建与第四网元之间的会话；
删除单元，用于删除与该第二网元之间的会话。
在一种可能的实现方式中，该创建单元具体用于：
向该第四网元发送第三会话创建请求消息，该第三会话创建请求消息用于指示创建该第一网元与该第四网元之间的会话。
在一种可能的实现方式中，该删除单元具体用于：
向该第二网元发送会话删除请求消息，该会话删除请求消息用于指示删除该第一网元与该第二网元之间的会话。
在一种可能的实现方式中，该第一网元还包括：
第四发送模块，用于将该用户面重路由触发信息发送给该第三网元；
第二接收模块，用于接收该第三网元发送的指示信息，其中，该指示信息用于指示该第一网元执行用户面重路由。
本申请实施例提供的网元100，可以用于执行本申请上述用户面重路由方法实施例中关于第一网元的技术方案，其实现原理和技术效果类似，此处不再赘述。
图11为本申请另一实施例提供的网元的结构示意图。可选地，本申请实施例提供的网元可以为第一网元。如图11所示，本申请实施例的网元110可以包括：监测模块1101以及发送模块1102。
监测模块1101，用于根据报文检测规则PDR对业务报文进行监测；其中，该PDR用于指示触发用户面重路由的预设业务报文对应的匹配信息以及执行规则；
发送模块1102，用于若该监测模块监测到与该PDR匹配的预设业务报文时，根据该执行规则向第二网元发送用户面重路由触发信息。
在一种可能的实现方式中，该PDR中包括：报文检测信息PDI、使用量上报规则URR；其中，该PDI用于指示该预设业务报文对应的匹配信息，该URR用于指示该预设业务报文对应的执行规则。
在一种可能的实现方式中，该监测模块1101具体用于：
确定该业务报文的属性信息；
将该属性信息与该PDI进行匹配；
若该属性信息与该PDI匹配，则监测到该业务报文是与该PDR匹配的预设业务报文；和/或，
若该属性信息与该PDI不匹配，则监测到该业务报文不是与该PDR匹配的预设业务报文。
在一种可能的实现方式中，该第一网元还包括：
第一接收模块，用于接收该第二网元发送的该PDR，其中，该PDR为该第二网元根据预置的用于触发用户面重路由的策略生成的，或者该PDR为该第二网元在从第三网元获取到用于触发用户面重路由的策略后所生成的。
在一种可能的实现方式中，该第一网元还包括：
第二接收模块，用于接收该第二网元发送的激活消息，该激活消息用于指示激活该第一网元中预置的该PDR。
在一种可能的实现方式中，该PDR携带于该第一网元接收到的该第二网元发送的第一会话创建请求消息，该第一会话创建请求消息用于指示创建该第二网元与该第一网元之间的会话。
在一种可能的实现方式中，该激活消息携带于该第一网元接收到的该第二网元发送的第二会话创建请求消息，该第二会话创建请求消息用于指示创建该第二网元与该第一网元之间的会话。
在一种可能的实现方式中，该第一网元还包括：
第三接收模块，用于接收该第二网元发送的会话更新请求消息，该会话更新请求消息用于指示更新该第一网元中的该PDR。
在一种可能的实现方式中，该第一网元还包括：
第四接收模块，用于接收该第二网元发送的会话删除请求消息，该会话删除请求消息用于指示删除该第二网元与该第一网元之间的会话。
本申请实施例提供的网元100，可以用于执行本申请上述用户面重路由方法实施例中关于第二网元的技术方案，其实现原理和技术效果类似，此处不再赘述。
图12为本申请另一实施例提供的网元的结构示意图。如图12所示，本实施例的网元120可以包括：处理器1201和存储器1202。可选地，该网元120还可以包括用于收发信息和/或消息的收发器1203。其中，该存储器1202用于存储程序指令，该处理器1201用于调用并执行该存储器1202中存储的程序指令，当该处理器1201执行该存储器1202存储的程序指令时，该网元120用于执行本申请上述用户面重路由方法实施例中关于第一网元或第二网元的技术方案，其实现原理和技术效果类似，此处不再赘述。
本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该指令在计算机上运行时，使得计算机执行本申请上述用户面重路由方法实施例中关于第一网元或第二网元的技术方案，其实现原理和技术效果类似，此处不再赘述。
本申请实施例还提供一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现本申请上述用户面重路由方法实施例中关于第一网元或第二网元的技术方案，其实现原理和技术效果类似，此处不再赘述。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
本申请实施例还提供一种程序，该程序在被处理器执行时用于执行本申请上述用户面重路由方法实施例中关于第一网元或第二网元的技术方案，其实现原理和技术效果类似，此处不再赘述。
本申请实施例还提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行本申请上述用户面重路由方法实施例中关于第一网元或第二网元的技术方案，其实现原理和技术效果类似，此处不再赘述。
本申请实施例中涉及的处理器可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
本申请实施例中涉及的存储器可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元 的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
本领域普通技术人员可以理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
在上述各实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。

Claims (30)

  1. 一种用户面重路由方法，其特征在于，包括：
    第一网元接收第二网元发送的用户面重路由触发信息；其中，所述用户面重路由触发信息为所述第二网元监测到与报文检测规则PDR匹配的预设业务报文时发送的；所述PDR用于指示触发用户面重路由的预设业务报文对应的匹配信息以及执行规则；
    所述第一网元根据所述用户面重路由触发信息，执行用户面重路由。
  2. 根据权利要求1所述的方法，其特征在于，所述PDR中包括：报文检测信息PDI、使用量上报规则URR；其中，所述PDI用于指示所述预设业务报文对应的匹配信息，所述URR用于指示所述预设业务报文对应的执行规则。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述第一网元根据预置的用于触发用户面重路由的策略生成所述PDR，并将所述PDR发送给所述第二网元。
  4. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述第一网元从第三网元获取所述第三网元中预置的用于触发用户面重路由的策略；
    所述第一网元根据所述策略生成所述PDR，并将所述PDR发送给所述第二网元。
  5. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述第一网元向所述第二网元发送激活消息，所述激活消息用于指示激活所述第二网元中预置的所述PDR。
  6. 根据权利要求3或4所述的方法，其特征在于，所述PDR携带于所述第一网元向所述第二网元发送的第一会话创建请求消息，所述第一会话创建请求消息用于指示创建所述第一网元与所述第二网元之间的会话。
  7. 根据权利要求5所述的方法，其特征在于，所述激活消息携带于所述第一网元向所述第二网元发送的第二会话创建请求消息，所述第二会话创建请求消息用于指示创建所述第一网元与所述第二网元之间的会话。
  8. 根据权利要求1-7中任一项所述的方法，其特征在于，所述第一网元根据所述用户面重路由触发信息，执行用户面重路由，包括：
    所述第一网元向第四网元发送第一会话请求消息，以及向第五网元发送第二会话请求消息；其中，所述第一会话请求消息用于指示创建或更新所述第一网元与所述第四网元之间的会话，所述第二会话请求消息用于指示创建或更新所述第一网元与所述第五网元之间的会话，所述第二会话请求消息中携带为所述第五网元分配的业务报文分流规则；和/或，
    所述第一网元向所述第二网元发送会话更新请求消息，所述会话更新请求消息用于指示更新所述第二网元中的PDR。
  9. 根据权利要求1-7中任一项所述的方法，其特征在于，所述第一网元根据所述用户面重路由触发信息，执行用户面重路由，包括：
    所述第一网元创建与第四网元之间的会话；
    所述第一网元删除与所述第二网元之间的会话。
  10. 根据权利要求9所述的方法，其特征在于，所述第一网元创建与第四网元之间的会话，包括：
    所述第一网元向所述第四网元发送第三会话创建请求消息，所述第三会话创建请求消息用于指示创建所述第一网元与所述第四网元之间的会话。
  11. 根据权利要求9或10所述的方法，其特征在于，所述第一网元删除与所述第二网元之间的会话，包括：
    所述第一网元向所述第二网元发送会话删除请求消息，所述会话删除请求消息用于指示删除所述第一网元与所述第二网元之间的会话。
  12. 根据权利要求4所述的方法，其特征在于，所述第一网元根据所述用户面重路由触发信息，执行用户面重路由之前，所述方法还包括：
    所述第一网元将所述用户面重路由触发信息发送给所述第三网元；
    所述第一网元接收所述第三网元发送的指示信息，其中，所述指示信息用于指示所述第一网元执行用户面重路由。
  13. 一种用户面重路由方法，其特征在于，包括：
    第一网元根据报文检测规则PDR对业务报文进行监测；其中，所述PDR用于指示触发用户面重路由的预设业务报文对应的匹配信息以及执行规则；
    若所述第一网元监测到与所述PDR匹配的预设业务报文时，所述第一网元根据所述执行规则向第二网元发送用户面重路由触发信息。
  14. 根据权利要求13所述的方法，其特征在于，所述PDR中包括：报文检测信息PDI、使用量上报规则URR；其中，所述PDI用于指示所述预设业务报文对应的匹配信息，所述URR用于指示所述预设业务报文对应的执行规则。
  15. 根据权利要求14所述的方法，其特征在于，所述第一网元根据报文检测规则PDR对业务报文进行监测，包括：
    所述第一网元确定所述业务报文的属性信息；
    所述第一网元将所述属性信息与所述PDI进行匹配；
    若所述属性信息与所述PDI匹配，则所述第一网元监测到所述业务报文是与所述PDR匹配的预设业务报文；和/或，
    若所述属性信息与所述PDI不匹配，则所述第一网元监测到所述业务报文不是与所述PDR匹配的预设业务报文。
  16. 根据权利要求13-15中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网元接收所述第二网元发送的所述PDR，其中，所述PDR为所述第二网元根据预置的用于触发用户面重路由的策略生成的，或者所述PDR为所述第二网元在从第三网元获取到用于触发用户面重路由的策略后所生成的。
  17. 根据权利要求13-15中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网元接收所述第二网元发送的激活消息，所述激活消息用于指示激活所述第一网元中预置的所述PDR。
  18. 根据权利要求16所述的方法，其特征在于，所述PDR携带于所述第一网元接收到的所述第二网元发送的第一会话创建请求消息，所述第一会话创建请求消息用于指示创建所述第二网元与所述第一网元之间的会话。
  19. 根据权利要求17所述的方法，其特征在于，所述激活消息携带于所述第一网元接收到的所述第二网元发送的第二会话创建请求消息，所述第二会话创建请求消息用于指示创建所述第二网元与所述第一网元之间的会话。
  20. 根据权利要求13-19中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网元接收所述第二网元发送的会话更新请求消息，所述会话更新请求消息用于指示更新所述第一网元中的所述PDR。
  21. 根据权利要求13-19中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网元接收所述第二网元发送的会话删除请求消息，所述会话删除请求消息用于指示删除所述第二网元与所述第一网元之间的会话。
  22. 一种网元，其特征在于，所述网元为第一网元，所述第一网元包括：
    第一接收模块，用于接收第二网元发送的用户面重路由触发信息；其中，所述用户面重路由触发信息为所述第二网元监测到与报文检测规则PDR匹配的预设业务报文时发送的；所述PDR用于指示触发用户面重路由的预设业务报文对应的匹配信息以及执行规则；
    重路由模块，用于根据所述用户面重路由触发信息，执行用户面重路由。
  23. 根据权利要求22所述的第一网元，其特征在于，所述PDR中包括：报文检测信息PDI、使用量上报规则URR；其中，所述PDI用于指示所述预设业务报文对应的匹配信息，所述URR用于指示所述预设业务报文对应的执行规则。
  24. 根据权利要求22或23所述的第一网元，其特征在于，所述第一网元还包括：
    第一生成模块，用于根据预置的用于触发用户面重路由的策略生成所述PDR；
    第一发送模块，用于将所述PDR发送给所述第二网元。
  25. 根据权利要求22或23所述的第一网元，其特征在于，所述第一网元还包括：
    获取模块，用于从第三网元获取所述第三网元中预置的用于触发用户面重路由的策略；
    第二生成模块，用于根据所述策略生成所述PDR；
    第二发送模块，用于将所述PDR发送给所述第二网元。
  26. 根据权利要求22或23所述的第一网元，其特征在于，所述第一网元还包括：
    第三发送模块，用于向所述第二网元发送激活消息，所述激活消息用于指示激活所述第二网元中预置的所述PDR。
  27. 一种网元，其特征在于，所述网元为第一网元，所述第一网元包括：
    监测模块，用于根据报文检测规则PDR对业务报文进行监测；其中，所述PDR用于指示触发用户面重路由的预设业务报文对应的匹配信息以及执行规则；
    发送模块，用于若所述监测模块监测到与所述PDR匹配的预设业务报文时，根据所述执行规则向第二网元发送用户面重路由触发信息。
  28. 根据权利要求27所述的第一网元，其特征在于，所述PDR中包括：报文检测信息PDI、使用量上报规则URR；其中，所述PDI用于指示所述预设业务报文对应的匹配信息，所述URR用于指示所述预设业务报文对应的执行规则。
  29. 一种网元，其特征在于，包括：处理器和存储器；
    其中，所述存储器，用于存储程序指令；
    所述处理器，用于调用并执行所述存储器中存储的程序指令，当所述处理器执行所述存储器存储的程序指令时，所述网元用于执行如权利要求1至21中任一项所述的方法。
  30. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有指令，当所述指令在计算机上运行时，使得计算机执行如权利要求1至21中任一项所述的方法。
PCT/CN2020/098561 2019-06-28 2020-06-28 用户面重路由方法及装置 WO2020259688A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2021576528A JP7294578B2 (ja) 2019-06-28 2020-06-28 ユーザプレーンのリルーティング方法および装置
EP20832946.6A EP3979710A4 (en) 2019-06-28 2020-06-28 METHOD AND DEVICE FOR DIVERSION TO USER LEVEL
US17/562,721 US11849384B2 (en) 2019-06-28 2021-12-27 User plane rerouting method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910578953.9 2019-06-28
CN201910578953.9A CN112152923B (zh) 2019-06-28 2019-06-28 用户面重路由方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/562,721 Continuation US11849384B2 (en) 2019-06-28 2021-12-27 User plane rerouting method and apparatus

Publications (1)

Publication Number Publication Date
WO2020259688A1 true WO2020259688A1 (zh) 2020-12-30

Family

ID=73892032

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/098561 WO2020259688A1 (zh) 2019-06-28 2020-06-28 用户面重路由方法及装置

Country Status (5)

Country Link
US (1) US11849384B2 (zh)
EP (1) EP3979710A4 (zh)
JP (1) JP7294578B2 (zh)
CN (1) CN112152923B (zh)
WO (1) WO2020259688A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114885365A (zh) * 2022-07-07 2022-08-09 中兴通讯股份有限公司 业务规则检测方法、装置、电子设备及存储介质

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4005166A1 (en) * 2019-07-26 2022-06-01 Telefonaktiebolaget LM Ericsson (publ) Traffic monitoring in a network node
US11470505B2 (en) * 2019-08-30 2022-10-11 Parallel Wireless, Inc. Support for linking of packet detection rules (PDR) for optimizing throughput of combined serving gateway (SGW)/packet gateway (PGW) architecture
CN114915649A (zh) * 2021-01-29 2022-08-16 阿里巴巴集团控股有限公司 数据转发方法、系统及非易失性存储介质
CN113543196B (zh) * 2021-07-21 2024-01-05 安科讯(福建)科技有限公司 一种qos流的动态调整方法与系统
CN115915045B (zh) * 2022-11-08 2023-09-22 之江实验室 一种用于降低用户面和控制面信令交互负载的方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180316615A1 (en) * 2017-04-27 2018-11-01 At&T Intellectual Property I, L.P. Method and apparatus for selecting processing paths in a converged network
CN109548063A (zh) * 2017-09-20 2019-03-29 华为技术有限公司 处理报文的方法、装置、设备及存储介质

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8937886B2 (en) * 2010-12-17 2015-01-20 Cisco Technology, Inc. Dynamic reroute scheduling in a directed acyclic graph (DAG)
US8824471B2 (en) * 2011-06-01 2014-09-02 Cisco Technology, Inc. Maintained message delivery during routing domain migration
US8837277B2 (en) * 2011-06-01 2014-09-16 Cisco Technology, Inc. Source routing convergence in constrained computer networks
CN103023770B (zh) * 2011-09-21 2017-09-26 中兴通讯股份有限公司 环网的保护方法及装置
CN102395172B (zh) * 2011-11-16 2013-12-18 武汉大学 一种工业无线网状网络的数据传输方法
CN103973578B (zh) * 2013-01-31 2018-06-19 新华三技术有限公司 一种虚拟机流量重定向的方法及装置
US9538563B2 (en) * 2014-10-13 2017-01-03 At&T Intellectual Property I, L.P. System and methods for managing a user data path
US11146985B2 (en) * 2015-10-28 2021-10-12 Apple Inc. Quality of service provisioning framework for a SDN-based cellular network architecture
CN109756430B (zh) * 2017-11-07 2021-08-03 华为技术有限公司 一种规则的处理方法及装置
US11895033B2 (en) * 2017-11-17 2024-02-06 Huawei Technologies Co., Ltd. Method and apparatus for traffic routing and path optimization for peer-to-peer communications
US10517012B2 (en) * 2018-01-16 2019-12-24 Cisco Technology, Inc. Methods and apparatus for use in adaptively rerouting user plane traffic for mobility using segment routing for IPv6
US11394811B2 (en) * 2018-02-15 2022-07-19 Telefonaktiebolaget Lm Ericsson (Publ) Redirection handling
CN110324388B (zh) * 2018-03-30 2022-05-13 华为技术有限公司 一种重定向的方法及装置
WO2020139696A1 (en) * 2018-12-28 2020-07-02 Weihua Qiao Restrict services and policy control for always-on pdu session
US10924397B2 (en) * 2019-02-22 2021-02-16 Vmware, Inc. Multi-VRF and multi-service insertion on edge gateway virtual machines

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180316615A1 (en) * 2017-04-27 2018-11-01 At&T Intellectual Property I, L.P. Method and apparatus for selecting processing paths in a converged network
CN109548063A (zh) * 2017-09-20 2019-03-29 华为技术有限公司 处理报文的方法、装置、设备及存储介质

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Traffic redirection enhancement", 3GPP DRAFT; C4-183227REDIRECT_PA3, vol. CT WG4, 6 April 2018 (2018-04-06), Kunming, China, pages 1 - 16, XP051412599 *
ERICSSON; CHINA MOBILE: "Traffic redirection enhancement", 3GPP DRAFT; C4-184037REDIRECT_A, vol. CT WG4, 11 May 2018 (2018-05-11), Osaka, Japan, pages 1 - 16, XP051460780 *
See also references of EP3979710A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114885365A (zh) * 2022-07-07 2022-08-09 中兴通讯股份有限公司 业务规则检测方法、装置、电子设备及存储介质
CN114885365B (zh) * 2022-07-07 2022-09-16 中兴通讯股份有限公司 业务规则检测方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
JP2022538111A (ja) 2022-08-31
US11849384B2 (en) 2023-12-19
JP7294578B2 (ja) 2023-06-20
EP3979710A1 (en) 2022-04-06
US20220124601A1 (en) 2022-04-21
CN112152923A (zh) 2020-12-29
CN112152923B (zh) 2021-12-28
EP3979710A4 (en) 2022-07-20

Similar Documents

Publication Publication Date Title
WO2020259688A1 (zh) 用户面重路由方法及装置
CN114145054B (zh) 用于支持流量导向通过服务功能链的系统和方法
US9497661B2 (en) Implementing EPC in a cloud computer with openflow data plane
WO2018161803A1 (zh) 一种网络切片的选择方法及装置
AU2012303738B2 (en) Implementing a 3G packet core in a cloud computer with openflow data and control planes
WO2021043191A1 (zh) 域名系统服务器的确定方法、请求处理方法和装置、系统
JP7485793B2 (ja) スライスアクセス方法、装置、及びシステム
WO2021037175A1 (zh) 一种网络切片的管理方法及相关装置
US11483279B2 (en) Domain name system as an authoritative source for multipath mobility policy
WO2021042742A1 (zh) 一种通信方法、装置及系统
WO2013144747A1 (en) Implementing epc in a cloud computer with openflow data plane
WO2019101041A1 (zh) 一种通信方法及其装置
WO2021109824A1 (zh) 会话创建方法和装置、会话创建的控制方法和装置、会话创建系统、网元及存储介质
WO2020173430A1 (zh) 一种会话建立方法及装置
WO2019096306A1 (zh) 一种处理请求的方法以及相应实体
WO2021148012A1 (zh) 报告信息的发送方法和通信装置以及通信系统
WO2022021971A1 (zh) 通信方法、第一策略控制网元及通信系统
US20230058366A1 (en) Managing Service Function Chains
WO2021051420A1 (zh) 一种dns缓存记录的确定方法及装置
EP3002916B1 (en) Packet forwarding system, device and method
JP2020506629A (ja) ルーティング方法および装置
WO2022099484A1 (zh) 标识发送方法和通信装置
WO2020211538A1 (zh) 一种数据传输方法及装置
CN109150752B (zh) 缓存控制方法、网元及控制器
US20240114323A1 (en) Apparatus and method for providing service function chaining service exposure in wireless communication system

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: 20832946

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021576528

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020832946

Country of ref document: EP

Effective date: 20211230