WO2021147402A1 - 一种数据传输方法及装置 - Google Patents

一种数据传输方法及装置 Download PDF

Info

Publication number
WO2021147402A1
WO2021147402A1 PCT/CN2020/122495 CN2020122495W WO2021147402A1 WO 2021147402 A1 WO2021147402 A1 WO 2021147402A1 CN 2020122495 W CN2020122495 W CN 2020122495W WO 2021147402 A1 WO2021147402 A1 WO 2021147402A1
Authority
WO
WIPO (PCT)
Prior art keywords
data stream
network element
upf
psa
pdu session
Prior art date
Application number
PCT/CN2020/122495
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 华为技术有限公司
Publication of WO2021147402A1 publication Critical patent/WO2021147402A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H04W28/20—Negotiating bandwidth
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0289—Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution

Definitions

  • This application relates to the field of communication technology, and in particular to a data transmission method and device.
  • 5G terminal devices In the 5th generation (5G) mobile communication network, due to the upgrade of air interface technology and chips, the capabilities of terminal devices have been greatly improved, that is, 5G terminal devices have the ability to trigger large-flow data packets, and terminal devices may
  • the uplink data packets are sent to the data network (data network, DN) through different paths.
  • IP anchor PSA PDU (protocol data unit, protocol data unit) session anchor, PDU session anchor) UPF (user plane function, user plane function)
  • IP anchor PSA UPF user plane function, user plane function
  • This application provides a data transmission method and device to provide a solution for reducing the overload of the UPF and PSA caused by the downlink data packet.
  • the present application provides a data transmission method, the method includes: a first user plane network element receives first indication information from a session management network element; the first user plane network element according to the first indication information, The downlink data stream sent by the data network DN to the first terminal device is sent to the first terminal device through at least two target protocol data unit PDU session anchor points; wherein, the at least two target PDU session anchor points are sent to the first terminal device respectively.
  • the first terminal device sends part of the data stream in the downlink data stream.
  • the first user plane network element sends the downlink data stream of the first terminal device to different PDU session anchor points for processing.
  • the first user plane network element may be referred to as a DLCL (downlink classifier, downlink offload) UPF, and the downlink data stream of the first terminal device may be sent to the first terminal device through at least two target PDU session anchor points.
  • the at least two target PDU session anchor points respectively send part of all or part of the downlink data stream to the first terminal device.
  • the downlink traffic load can be shared by at least two PDU session anchor points, which can reduce the network congestion that may be caused by the downlink big data flow, and there is a possible situation.
  • the target PDU session anchor point Load balancing ensures that the PDU session is in a relatively stable state.
  • the first indication information may include at least one sub-indication information, and each sub-indication information is respectively used to indicate the correspondence between the identification information of different downlink data streams and the target PDU session anchor;
  • the first user plane network element sends the downlink data stream sent by the data network DN to the first terminal device to the first terminal device through at least two target PDU session anchor points, including: For each sub-indication information, the first user plane network element sends the downlink data stream matching the identification information contained in the sub-indication information to the target PDU session corresponding to the downlink data stream matching the identification information contained in the sub-indication information Anchor point.
  • the first indication information includes at least one sub-indication information
  • the first user plane network element sends the downlink data stream matching the identification information to the PDU session anchor indicated by the sub-indication information according to the identification information indicated by each sub-indication information.
  • Point that is, the session management network element can flexibly adjust part of the downlink data stream by issuing sub-indication information, and the adjustment method is more flexible.
  • the identification information may include one or more of the following: source address information, destination address information, source port identification, destination port identification or protocol type, etc.
  • the sub-indication information may further include: an IP address used to send the downlink data stream in the first user plane network element, and/or the target PDU session anchor point The IP address used to receive the downlink data stream.
  • the first user plane network element may also receive second indication information from the mobile session management network element; the first user plane network element may receive second indication information from the mobile session management network element according to the second indication information.
  • At least one first PDU session anchor receives the uplink data stream sent by the first terminal device to the data network; wherein, the first PDU session anchor is capable of sending the first terminal device to the data network
  • the first user plane network element can receive the uplink data stream of the first terminal device from the PDU session anchor point according to the second indication information, and the uplink data stream of different PDU session anchor points can be aggregated to the first user plane.
  • the first user plane network element sends the upstream data stream to the data network.
  • a possible scenario For the data network, only the uplink data stream needs to be received from the first user plane, and there is no need to access multiple PDU session anchor points to receive the uplink data stream, which simplifies the data network to receive the uplink data stream. process.
  • the first user plane network element before sending the upstream data stream to the data network, may also generate first downstream routing information, and transfer the first downstream Routing information is sent to the data network; the first downlink routing information is used to instruct the data network to send the downlink data stream sent to the first terminal device to the first user plane network element first, so The destination of the downlink data stream is the first terminal device.
  • the first user plane network element provides the data network with the routing information of the downlink data stream of the first terminal device.
  • the data network does not need to set the IP anchor point of the first terminal device, and the data network side can connect the first terminal device.
  • the downlink data stream of the device is sent to the first user plane to reduce network congestion that may be caused by the downlink big data stream.
  • the present application provides a data transmission method.
  • the method includes: a session management network element generates first indication information, where the first indication information is used to instruct the first user plane network element to send the data network DN to the first
  • the downlink data stream of the terminal device is sent to the terminal device through at least two target protocol data unit PDU session anchor points; wherein the at least two target PDU session anchor points respectively send all or part of the downlink data stream to the first terminal device Part of the data flow in the session management network element sends the first indication information to the first user plane network element.
  • the session management network element generates first indication information, which is used to instruct the first user plane network element to send all or part of the downlink data stream of the first terminal device through at least two target PDU session anchors
  • sharing the downlink traffic load through at least two PDU session anchor points can alleviate the network congestion that may be caused by the downlink big data flow, and there is a possible situation.
  • each PSA UPF The load balancing ensures that the PDU session is in a relatively stable state.
  • the first indication information may further include at least one sub-indication information, and each sub-indication information is respectively used to indicate the correspondence between the identification information of different downlink data streams and the target PDU session anchor.
  • the first indication information contains at least one sub-indication information, and each sub-indication information is used to indicate the corresponding relationship between the identification information of different downlink data streams and the target PDU session anchor point.
  • the session management network element may use the sub-indication information In order to flexibly adjust part of the downlink data stream in granularity, the adjustment method is more flexible.
  • the identification information may, but is not limited to, include one or more of the following: source address information, destination address information, source port identification, destination port identification, or protocol type.
  • the sub-indication information may further include: an Internet Protocol IP address used to send the downlink data stream in the first user plane network element, and/or the target PDU session anchor The IP address used to receive the downstream data stream in the dot.
  • the session management network element before the session management network element generates the first indication information, it may also receive activation indication information, where the activation indication information is used to instruct the session management network element to activate the first user plane.
  • the activation indication information is used to instruct the session management network element to activate the first user plane.
  • Network element or instruct the session management network element to activate the first user plane network element and at least one new PDU session anchor; wherein, the target PDU session anchor is included in the at least one new PDU session anchor Click in.
  • the activation indication information may be sent to the session management network element after at least one second PDU session anchor or mobility management network element detects that the data stream meets the trigger condition; where
  • the trigger condition may include: the service type of the data stream is a preset service type; or the transmission rate of the data stream is not lower than a preset rate threshold.
  • the data stream includes an uplink data stream and/or a downlink data stream, the uplink data stream is a data stream sent by the first terminal device to the data network; the second PDU session anchor is a The PDU session anchor points on the network element from which the first terminal device sends the downlink data stream do not include one of the new PDU session anchor points.
  • the PDU session anchor in the current PDU session detects that the trigger condition is met, the PDU session anchor detects that the data volume of the received data stream is relatively large, for example, the flow rate of the data stream is relatively high, or If the data stream is a video stream, in order to avoid overloading of the PDU session anchor point service, activation indication information can be sent to the session management network element to instruct the session management network element to activate at least one new PDU session anchor point for the PDU session Anchors share data services, avoid network congestion, and maintain the stability of PDU sessions.
  • the session management network element may also receive release indication information from the third PDU session anchor, where the release indication information is used to instruct the session management network element to release the third PDU session anchor point and/or the first user plane network element; wherein, the third PDU session anchor point is one of the PDU session anchor points on the network element capable of sending a downlink data stream to the first terminal device One of the.
  • the session management network element can appropriately release at least one PDU session anchor point according to the service load status of the PDU session anchor point. For example, if the data transmitted in the current PDU session When the flow is small, for example, one PDU session anchor can process all the data flows transmitted in the current PDU session, or at least one of the PDU session anchors has not received the uplink data flow and/or the downlink data flow within the preset time. At this time, other PDU session anchor points and/or the first user plane network element can be released, simplifying the data stream transmission process, and avoiding problems such as low resource utilization due to excessive resource occupation.
  • the release indication information may be sent to the session management network element by the at least one third PDU session anchor after detecting that the release condition is met; the release condition may include: The third PDU session anchor does not receive a data stream within a preset time, and the data stream may include an uplink data stream and/or a downlink data stream.
  • the present application provides a data transmission method, the method includes: a target protocol data unit PDU session anchor receives from a first user plane network element part of a downlink data stream sent by the data network to the first terminal device Downlink data stream; the target PDU session anchor sends the received part of the downlink data stream to the first terminal device.
  • the downlink data stream is sent to the first terminal device through the target PDU session anchor.
  • the target PDU session anchor sends the downlink data stream to the RAN, and then the RAN sends it to the first terminal device.
  • part of the downlink data stream may be part of all the downlink data streams.
  • This application uses at least two PDU session anchor points to share the downlink service load, which can reduce the network congestion that may be caused by the downlink big data flow, and there is a possible situation.
  • the load balance of each PSA UPF can be achieved. Ensure that the PDU session is in a relatively stable state.
  • the target PDU session anchor point is one of at least one new PDU session anchor point activated by the session management network element after receiving the activation indication information.
  • the target PDU session anchor point may also receive third indication information from the session management network element; the target PDU session anchor point receives the third indication information from the second user plane according to the third indication information.
  • the network element receives a part of the upstream data stream in the upstream data stream sent by the first terminal device to the data network, and sends the part of the upstream data stream to the first user plane network element.
  • the target PDU session anchor receives the uplink data from the second user plane network element.
  • the second user plane network element may receive the uplink data stream sent by the terminal device to the data network from the access network device,
  • the upstream data stream is sent to the data network through at least two PDU session anchor points, and the upstream data stream received by each PDU session anchor point is part of the upstream data stream in all the upstream data streams, so as to reduce one of the PDU session anchor points. Point the probability of upstream business overload.
  • the target PDU session anchor may also send release indication information to the session management network element, where the release indication information is used to instruct the session management network element Release the target PDU session anchor point and/or the first user plane network element; wherein, the release condition may include: the target PDU session anchor point does not receive a data stream within a preset time, and the data A stream can include an upstream data stream and/or a downstream data stream.
  • the PDU session anchor points when there are multiple PDU session anchor points, when at least one of the PDU session anchor points does not receive the upstream data stream and/or the downstream data stream within a preset time, it can send a release to the session management network element
  • the indication information is used to instruct the session management network element to release at least one PDU session anchor point and/or the first user plane network element, so as to simplify the data stream transmission process and avoid problems such as low resource utilization due to excessive resource occupation.
  • an embodiment of the present application provides a communication device that has the function of implementing the method described in the first aspect.
  • the function can be implemented by hardware, or by software, or by hardware executing corresponding software.
  • the device includes one or more modules corresponding to the above-mentioned functions, such as a transceiver unit and a processing unit.
  • the device can be a chip or an integrated circuit.
  • the device includes a memory and a processor.
  • the memory is used to store a program or instruction executed by the processor.
  • the program or instruction is executed by the processor, the device can execute the above-mentioned first aspect. Methods.
  • the device may be a DLCL UPF network element.
  • embodiments of the present application provide a communication device that has the function of implementing the method described in the second aspect.
  • the function can be implemented by hardware, or by software, or by hardware executing corresponding software.
  • the device includes one or more modules corresponding to the above-mentioned functions, such as a transceiver unit and a processing unit.
  • the device can be a chip or an integrated circuit.
  • the device includes a memory and a processor.
  • the memory is used to store a program or instruction executed by the processor.
  • the program or instruction is executed by the processor, the device can execute the above-mentioned second aspect. Methods.
  • the device may be a Session Management Function (SMF) network element.
  • SMF Session Management Function
  • embodiments of the present application provide a communication device that has the function of implementing the method described in the third aspect.
  • the function can be implemented by hardware, or by software, or by hardware executing corresponding software.
  • the device includes one or more modules corresponding to the above-mentioned functions, such as a transceiver unit and a processing unit.
  • the device can be a chip or an integrated circuit.
  • the device includes a memory and a processor, and the memory is used to store a program or instruction executed by the processor.
  • the program or instruction is executed by the processor, the device can execute the above-mentioned third aspect. Methods.
  • the device may be a PDU session anchor functional entity.
  • an embodiment of the present application provides a system including the communication device described in the fourth aspect, the communication device described in the fifth aspect, and the communication device described in the sixth aspect.
  • an embodiment of the present application provides a communication device.
  • the communication device includes a processor, a memory, and a communication interface.
  • the communication interface is used to receive signals or send signals; and the memory is used to store programs or instructions. Code; the processor is configured to call the program or instruction code from the memory to execute the method described in the first aspect or the method described in the second aspect or the method described in the third aspect.
  • an embodiment of the present application provides a communication device.
  • the communication device includes a processor and an interface circuit.
  • the interface circuit is configured to receive a program or instruction code and transmit it to the processor; the processor runs The program or instruction code executes the method described in the first aspect or the method described in the second aspect or the method described in the third aspect.
  • an embodiment of the present application provides a computer-readable storage medium, where the computer-readable storage medium is used to store a program or instruction.
  • the program or instruction is executed, the method described in the first aspect or The method described in the second aspect or the method described in the third aspect is implemented.
  • an embodiment of the present application provides a computer program product including instructions that, when the instructions are executed, cause the method described in the first aspect or the method described in the second aspect or the method described in the third aspect to The method is implemented.
  • FIG. 1 is a schematic diagram of an application scenario provided by an embodiment of the application
  • FIGS. 2 to 3 are schematic diagrams of network architectures provided by embodiments of this application.
  • 5 to 7 are schematic diagrams of downlink data transmission scenarios provided by embodiments of this application.
  • FIG. 8 is a schematic flowchart of another data transmission method provided by an embodiment of this application.
  • FIG. 9 is a schematic diagram of an uplink data transmission scenario provided by an embodiment of the application.
  • FIG. 12 is a schematic diagram of a process of releasing a network element according to an embodiment of this application.
  • FIGS. 13-18 are schematic diagrams of the structure of a communication device provided by an embodiment of this application.
  • Terminal equipment also known as user equipment (UE), terminal (Terminal), mobile station (MS), mobile terminal (MT), etc.
  • Terminal devices can be referred to as terminals for short, which can be deployed on land, including indoor, outdoor, and/or handheld or vehicle-mounted; they can also be deployed on water (such as ships, etc.); they can also be deployed in the air (such as airplanes, balloons, and satellites).
  • the terminal device may be a user equipment (UE), and the UE includes a handheld device with a wireless communication function, a vehicle-mounted device, a wearable device, or a computing device.
  • the UE may be a mobile phone, a tablet computer, or a computer with a wireless transceiver function.
  • Terminal equipment can also be virtual reality (VR) terminal equipment, augmented reality (AR) terminal equipment, wireless terminals in industrial control, wireless terminals in unmanned driving, wireless terminals in telemedicine, and smart Wireless terminals in power grids, wireless terminals in smart cities, and/or wireless terminals in smart homes, etc.
  • VR virtual reality
  • AR augmented reality
  • Wireless terminals in power grids, wireless terminals in smart cities, and/or wireless terminals in smart homes, etc.
  • the device for realizing the function of the terminal device may be a terminal device, or a device capable of supporting the terminal device to realize the function, such as a chip system, and the device may be installed in the terminal device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the device used to implement the functions of the terminal is a terminal device as an example to describe the technical solutions provided in the embodiments of the present application.
  • Access network equipment which may be a radio access network (RAN) node that connects terminal equipment to the wireless network.
  • RAN nodes are: next generation NodeB (gNB), transmission reception point (TRP), evolved Node B (eNB), radio network controller (radio network) controller, RNC), node B (Node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (BBU), or wireless fidelity (WiFi) access point (AP), etc.
  • the base station may have many forms, such as macro base stations, micro base stations, relay stations, and access points.
  • the base station involved in the embodiment of the present application may be a base station in a 5G system or a base station in an LTE system, or a future 6th generation (6G) base station in a future communication system.
  • the base station in the 5G system may also be referred to as a transmission reception point (TRP) or a next-generation Node B (gNB or gNodeB).
  • TRP transmission reception point
  • gNB next-generation Node B
  • the device used to implement the function of the access network device may be the access network device, or a device capable of supporting the access network device to implement the function, such as a chip system.
  • the device can be installed in the access network device. Connected to the network equipment.
  • the device used to implement the functions of the access network equipment is the access network equipment as an example to describe the technical solutions provided in the embodiments of the present application.
  • Access and mobility management function (AMF) network element belongs to the core network network element and is mainly responsible for signaling processing, such as access control, mobility management, registration and de-registration, etc. .
  • AMF Access and mobility management function
  • the AMF network element provides services for the session in the UE, it will provide storage resources of the control plane for the session to store the session identifier, the SMF network element identifier associated with the session identifier, and so on.
  • Session management function (SMF) network element responsible for user-plane network element selection, user-plane network element redirection, Internet Protocol (IP) address allocation for interconnection between networks, session establishment, modification and Release and quality of service (quality of service, QoS) control.
  • SMF Session management function
  • UPF User plane function
  • ULCL uplink classifier, uplink offload
  • PSA protocol data unit, protocol data unit
  • DLCL downlink classifier, downlink offload
  • FIG. 1 is only for illustration, and there may be more than one UE, RAN ⁇ , UPF, and DN (not shown in FIG. 1).
  • the interface between the UE and the AMF network element is called the N1 interface
  • the interface between the AMF network element and the RAN device is called the N2 interface
  • the interface between the RAN device and the UPF network element can be called the N3 interface
  • the SMF network element The interface with the UPF network element is called the N4 interface
  • the interface between the UPF network element and the DN is called the N6 interface
  • the interface between different UPF network elements is called the N9 interface.
  • the UPF may also be the UE's PDU session anchor user plane network element (PSA UPF).
  • PSA UPF is used to process the received data stream, such as session management, packet routing and forwarding, lawful monitoring, billing, QoS, and deep packet analysis of the data packets contained in the received data stream. inspection, DPI).
  • PSA UPF1 is the IP anchor of the terminal device, that is, PSA UPF1 is responsible for receiving and processing all uplink data streams sent by the terminal device to the data network, and all downlink data sent by the data network to the terminal device data flow.
  • the implementation process of downlink data stream transmission is as follows:
  • the data network sends all the downstream data streams sent to the terminal device to the PSA UPF1 of the terminal device through the N6 interface.
  • PSA UPF1 needs to process any data message contained in the downstream data stream, and the processed data message It is sent to the access network device through the N3 interface, and the access network device is responsible for forwarding the data message to the terminal device.
  • One possible scenario is when the downlink data stream sent by the data network is large, for example, when the burst throughput of a certain downlink data stream is superimposed on other data streams, it may exceed the processing upper limit of PSA UPF1, causing PSA UPF1 service overload , Causing network congestion, resulting in packet loss in the downstream data stream.
  • Another possible scenario is that due to the movement of the terminal device, the PSA UPF1 cannot cover the terminal device. It is necessary to migrate the uplink data stream of the terminal device on the PSA UPF1 to the PDU session belonging to the terminal device through ULCL UPF The other PSA's UPF.
  • the data network DN will set an IP anchor point for the terminal device, that is, even if there are multiple PDU sessions between the terminal device and the same data network for accessing the data network PSA UPF, but on the data network side, only one of the multiple PSAs UPF is the IP anchor of the terminal device.
  • the IP anchor is PSA UPF1.
  • the data network will send all the downstream data streams to the terminal device. Send to PSA UPF1.
  • the downlink data stream sent by the DN is large, it may cause the downlink data stream service of PSF UPF1 to be overloaded, and problems such as downlink data packet loss may occur.
  • the embodiments of the present application provide a data transmission method.
  • at least one new PSA UPF and DLCL UPF can be activated, and all or part of the downlink data stream sent to a terminal device can be passed through at least two DLCL UPF through DLCL UPF.
  • the PSA UPF is sent to the terminal device, and each PSA UPF is used to process all or part of the downlink data stream. It can also be understood as sharing the original PSA UPF through the at least one new PSA UPF (as shown in Figure 1 PSA UPF1) in the business load.
  • DLCL UPF Since DLCL UPF does not need to process data packets, it is mainly responsible for the distribution of downstream data streams, so it will not cause data streams to be overloaded at DLCL UPF, and multiple PSAs UPF can share the downlink traffic load, which can reduce the downstream big data. Network congestion may be caused by the flow, and there is a possible situation. Through the distribution of DLCL UPF, the load balance of each PSA UPF is ensured to ensure that the PDU session is in a relatively stable state.
  • multiple means two or more than two.
  • exemplary is used to mean serving as an example, illustration, or illustration. Any embodiment or design solution described as an "example” in this application should not be construed as being more preferable or advantageous than other embodiments or design solutions. Rather, the term example is used to present the concept in a concrete way.
  • ordinal numbers such as “first” and “second” mentioned in the embodiments of the present application may be used to distinguish multiple objects, and are not used to limit the order, timing, priority, or importance of multiple objects.
  • the first information and the second information are only for distinguishing different signaling, but do not indicate the difference in content, priority, sending order, or importance of the two types of information.
  • wireless communication between communication devices may include: wireless communication between network devices and terminal devices, wireless communication between terminal devices and terminal devices, and the like.
  • wireless communication can also be simply referred to as “communication”
  • communication can also be described as “data transmission”, “information transmission”, “signal transmission” or “transmission”. Transmission can include sending and/or receiving.
  • the transmission between a network device and a terminal device includes: the network device sends a downlink signal to the terminal device, that is, the terminal device receives a downlink signal from the network device; and/or, the terminal device sends an uplink signal to the network device, that is, the network device sends an uplink signal from the terminal device. Receive uplink signal.
  • the communication between the network device and the terminal device is described as an example.
  • Those skilled in the art can use the technical solution provided in the embodiment of this application to perform wireless communication between other scheduling entities and subordinate entities, for example,
  • the wireless communication between the macro base station and the micro base station is used for the wireless communication between the first terminal device and the second terminal device, which is not limited in the embodiment of this application.
  • FIG. 2 this is a schematic diagram of a network architecture to which the embodiments of this application are applicable.
  • the network architecture adds DLCL UPF and at least one new PSA UPF on the basis of Figure 1, for example, the new PSA UPF is called PSA UPF2.
  • the DLCL UPF which can be called a downlink data offloading user plane network element, is mainly responsible for receiving the downlink data stream from the data network, and sending the downlink data stream to the PSA UPF corresponding to the downlink data stream, or offloading the downlink data stream into Different sub-data streams, and distribute different sub-data streams to different PSA UPFs.
  • the DLCL UPF may determine the PSA UPF corresponding to the downlink data stream according to the first indication information issued by the SMF, or determine to split the downlink data stream into different sub-data streams, and to which PSAs the different sub-data streams are distributed UPF.
  • the SMF is mainly responsible for the establishment, modification, and release of PDU sessions, and manages the transmission tunnel between the wireless network side and the UPF.
  • the session management function is mainly used to select and control the UPF, configure the flow direction of the UPF, and forward the data flow to the appropriate destination.
  • it is also used to generate first indication information, which is used to instruct DLCL UPF to send all or part of the downlink data stream sent to one terminal device to the terminal through at least two PSAs UPF Device, and the downlink data stream received by each PSA UPF is part of all the downlink data streams, so as to reduce the probability of one of the PSA UPF services being overloaded.
  • PSA UPF2 and PSA UPF1 are at least two PSA UPFs in the PDU session established by the terminal device and the data network. They are used to receive part of the downlink data stream sent by the data network to the terminal device, and to receive The data message in the received downlink data stream is processed, and the processed data message is sent to the terminal device.
  • FIG 3 this is a schematic diagram of another network architecture to which the embodiments of this application are applicable. Compared with the network architecture of Figure 2, the main difference is that: on the basis of Figure 2, ULCL UPF is added, which is The network architecture shown in Figure 3 supports ULCL UPF, that is, supports inserting ULCL UPF.
  • ULCL UPF is a user plane network element for upstream data offloading.
  • ULCL UPF can be responsible for removing the terminal equipment from the original PSA UPF when the original PSA UPF cannot be covered by the terminal equipment due to the movement of the terminal equipment. Migrate the upstream data stream to other PSA UPF.
  • the embodiment of the present application also provides a method for uplink data stream transmission based on ULCL UPF, which can be applied to the network architecture shown in FIG. 3, and can also be applied to the network that does not include DLCL UPF in FIG. 3 In the architecture, the embodiment of the present application does not limit this.
  • ULCL UPF can receive from the access network device all the uplink data streams sent by the terminal device to the data network DN, and send all the uplink data streams to the data network DN through at least two PSAs UPF, and each PSA UPF
  • the received upstream data stream is part of the entire upstream data stream, so as to reduce the probability of one of the PSA UPF upstream services being overloaded. That is, in the embodiment of the present application, ULCL UPF can also be used to offload the uplink data stream.
  • SMF in addition to the routing method used to configure the downlink data stream described above, you can also configure the routing method of the uplink data stream.
  • routing method of the uplink data stream please refer to the description of the routing method of the downlink data stream above. The description will not be repeated here.
  • Figures 2 and 3 are only schematic. Figures 2 and 3 only show that one PSA UPF2 is inserted. In fact, multiple PSA UPFs can also be inserted, which is not limited in the embodiment of the present application.
  • part or all of the ULCL functional entity, PSA functional entity, or DLCL functional entity may be deployed on the same UPF, or may be deployed on different UPFs. That is, part or all of ULCL UPF, PSA UPF, or DLCL UPF may be located in the same UPF. If it is deployed on the same UPF, it can be called a unified deployment. If it is deployed on different UPFs, it can be called a separate deployment. It should be noted that Figures 2 and 3 are schematic diagrams of network architectures for separate deployment.
  • the mobility management network element, session management network element, PDU session anchor (PSA), first user plane network element, and second user plane network element in this application may be the AMF network elements shown in FIG. 2 or FIG. 3, respectively , SMF network element, PSA functional entity on the PSA UPF network element, DLCL UPF, ULCL UPF (not shown in Figure 2). It may also be a network element that has the functions of the aforementioned AMF network element, SMF network element, PSA functional entity on the PSA UPF network element, DLCL UPF network element, and ULCL UPF in the future communication system.
  • the mobility management network element, the session management network element, the PDU session anchor user plane network element, the first user plane network element, and the second user plane network element may be the AMF network in Figure 3, respectively.
  • the description will be made as examples for the element, SMF network element, PSA UPF network element, DLCL UPF network element, and ULCL UPF network element.
  • the AMF network element is abbreviated as AMF
  • the SMF network element is abbreviated as SMF
  • the PSA UPF network element is abbreviated as PSA UPF
  • the DLCL UPF network element is abbreviated as DLCL UPF
  • the ULCL UPF network element is abbreviated as ULCL UPF
  • the terminal device is called UE
  • the access network device is called RAN for short.
  • the AMF described later in this application can be replaced with a mobility management network element
  • SMF can be replaced with a session management network element
  • each PSA UPF can be replaced with The PDU session anchor point, DLCL and UPF on each UPF can be replaced with the first user plane network element
  • the UE can be replaced with a terminal device
  • the RAN can be replaced with an access network device.
  • a data transmission method provided by an embodiment of this application can be applied to the network architecture shown in FIG. 2 or FIG. 3.
  • the method includes the following steps:
  • Step S400 SMF generates first indication information
  • the SMF generates the first indication information for the DLCL UPF to indicate the target PSA UPF corresponding to the downlink data stream.
  • the first indication information is used to indicate the correspondence between the downlink data stream and the target PSA UPF. This will be explained in detail below.
  • Step S401 DLCL UPF receives first indication information from SMF
  • the first indication information is used to instruct the DLCL UPF to send the downlink data stream of the DN to the UE to the UE through at least two PSAs and UPFs.
  • DLCL UPF sends all the downlink data streams to the UE through PSA UPF1 and PSA UPF2, where the downlink data streams received by PSA UPF1 and PSA UPF2 are all downlink data streams, respectively
  • the downstream data streams received by PSA UPF1 and PSA UPF2 are different.
  • it may mean that at least two PSAs and UPFs respectively send different received downlink data streams to the RAN, and then the RAN sends them to the UE.
  • all the downlink data streams to be sent to a UE can also be sent to the same PSA UPF for processing.
  • step S402 the DLCL UPF sends the downlink data through at least two PSAs UPF according to the first indication information, where the destination of the downlink data stream is the receiving end UE.
  • step S402 is only for illustration, and does not mean that DLCL UPF sends downlink data streams to at least two PSAs UPF at the same time, nor does it mean that at least two PSA UPFs send downlink data streams to RAN at the same time. limited.
  • each PSA UPF respectively sends a part of the downlink data stream it receives to the RAN.
  • each PSA UPF can also send part of the received downlink data stream to ULCL UPF, which is sent by ULCL UPF to the RAN, and then the RAN sends the downlink data stream.
  • ULCL UPF which is sent by ULCL UPF to the RAN
  • the RAN sends the downlink data stream.
  • step S403 is for illustration only, and does not mean that the RAN simultaneously receives downlink data streams from each PSA UPF, nor does it mean that at least two PSAs UPF simultaneously send downlink data streams to the RAN, which is not limited in the embodiment of the present application.
  • Step S404 The RAN sends the downlink data stream received from each PSA UPF to the UE.
  • step S404 is only for illustration, and is used to instruct the RAN to send the downlink data stream to the UE after receiving the downlink data stream. It does not mean that the UE simultaneously receives each downlink data stream issued by the PSA UPF from the RAN. It does not mean that the RAN sends the downlink data stream to the UE after receiving the downlink data stream issued by each PSA UPF, which is not limited in the embodiment of the present application.
  • the data flow in the embodiment of the present application includes an uplink data flow and a downlink data flow.
  • the uplink data stream is sent by the UE to the data network DN. Specifically, it can be sent to at least one server included in the DN side, that is, the destination of the uplink data stream is at least one service under the DN. equipment.
  • the downlink data stream is sent to the UE by the DN side of the data network, that is, the destination end of the downlink data stream is the UE.
  • the data stream includes at least one data message.
  • the data message may be a GTP message.
  • the data message may include a source IP address and a destination IP address.
  • the source IP address is the IP address of the terminal device that sends the data message
  • the destination IP address is the destination IP address of the data message, that is, the data network DN contains The IP address of a certain server.
  • data can be divided into different data streams.
  • Different data streams can have different identification information.
  • the identification information can be source IP address, destination IP address, source port number, destination port number, and protocol type. One or more items of information.
  • the above-mentioned source IP address, destination IP address, source port number, destination port number, and protocol type information may also be referred to as a data stream quintuple.
  • the method shown in FIG. 4 is applied to the transmission flow diagram of the downlink data stream in the network architecture shown in FIG. 2.
  • the process can include:
  • Step 1 The data network DN sends the downlink data stream to be sent to a receiving end UE to DLCL UPF.
  • Step 2 DLCL UPF sends the downlink data stream to at least two PSA UPFs corresponding to the downlink data stream according to the first indication information received from the SMF.
  • the DLCL UPF sends the downlink data stream to the target PSA UPF corresponding to the downlink data stream through the N9 interface
  • the target PSA UPF in FIG. 5 is PSA UPF1 and PSA UPF2 respectively.
  • the target PSA UPF in this document refers to the PSA UPF corresponding to the data stream that matches the identification information of the PDR entry indicated in the PDR entry. Therefore, the "target PSA UPF of the data stream" and "PSA UPF corresponding to the data stream" in this article can be mixed, and the description will not be repeated below.
  • the first indication information may be a packet detection rule (Packet Detection Rule, PDR), DLCL UPF matches the received downlink data stream with the PDR, and matches the downlink data stream of the PDR (through DLCL UPF with each The N9 interface corresponding to the PSA PDU) is sent to the PSA PDU corresponding to the downlink data stream.
  • PDR Packet Detection Rule
  • the PDR includes at least one PDR table entry, and each PDR table entry is used to indicate a different data stream and a transmission mode of the data stream.
  • Table 1 a specific example of a PDR entry provided in this embodiment of the application.
  • the SDF filter is used to match data packets that meet the identification information.
  • the identification information can be part or all of the five-tuple of the data stream.
  • Local IP is used to indicate the IP address of the interface through which the DLCL UPF sends data packets matching the SDF filter (indicated identification information).
  • DLCL UPF may have multiple N9 interfaces for sending downlink data streams, and the multiple N9 interfaces correspond to multiple PSAs UPF.
  • DLCL UPF has two N9 interfaces.
  • the N9 interface has a one-to-one correspondence with different PSAs UPF, that is, ULCL UPF can send data streams belonging to different PSAs UPF in parallel through multiple N9 interfaces.
  • DLCL UPF may have only one N9 interface for sending the downlink data stream, and this one N9 interface corresponds to multiple PSA UPFs, that is, DLCL UPF transfers different downlink data through the same N9 interface. The stream is sent to different PSAs and UPFs.
  • the PDR entry shown in Table 1 may not indicate the Local IP of DLCL UPF.
  • Outer ip used to indicate the next hop (IP address) of the data packet.
  • the above Table 1 can be interpreted as: the PDR entry shown in Table 1 is used to instruct DLCL UPF to send data packets matching the SDF filter to PSA UPF1 through the N9 interface.
  • the identification information indicated by the SDF filter in different PDR entries should be different, which is used to indicate different data streams.
  • the two downlink data streams sent by the DN to the UE include data stream 1 and data stream 2.
  • the SMF configures routing modes for the two upstream data streams to generate the first PDR entry and the second PDR entry.
  • Table 2 it is a specific example of the first PDR characterization
  • Table 3 is a specific example of the second PDR entry.
  • the DLCL UPF corresponding to PSA UPF1 is the first N9 interface
  • the DLCL UPF corresponding to PSA UPF2 is the second N9 interface.
  • the first PDR entry (Table 2) is used to instruct DLCL UPF to send data stream 1 to PSA UPF1. Specifically, it can also instruct DLCL UPF to send the IP address of data stream 1 and the next data stream 1 Hop, that is, the IP address of the PSA and UPF1 that received the data stream 1.
  • the second PDR entry is used to instruct DLCL UPF to send data stream 2 to PSA UPF2. Specifically, it can also instruct DLCL UPF to send the IP address of data stream 2 and the next hop of data stream 2, namely The IP address of the PSA UPF2 that receives the data stream 2.
  • ULCL UPF determines whether the data stream is data stream 1 or data stream 1 according to the identification information in the PDR entry. For example, the identification information in the first PDR entry is that the source IP address is 10.10.0.1 and the destination IP address is 192.168.0.1. When DLCL UPF detects data stream 1, it determines that the source IP address contained in data stream 1 is also 10.10. 0.1, the destination IP address is 192.168.0.1, then it is determined that data stream 1 matches the first PDR entry.
  • the identification information in the second PDR entry is that the source IP address is 10.10.0.1, and the destination IP address is 192.168.0.2, (where 192.168.0.1 and 192.168.0.1 are the IP addresses of the nodes included on the DN side)
  • DLCL UPF detects data stream 2
  • the above-mentioned PDR table entry is only for illustration, and the IP address can also be identified by other addresses of a network element, node, or device, such as a MAC address, and the PDR table entry used in the embodiment of this application may be the above-mentioned Table 1.
  • the PDR table entry used in the embodiment of this application may be the above-mentioned Table 1.
  • other items that can be added include the identifier used to indicate that the PDR entry indicates the downlink data stream or the uplink data stream.
  • the information such as the operation mode of the data packet is not limited in the embodiment of the present application.
  • DLCL UPF As an example to introduce the way of forwarding data between UPFs.
  • Any UPF including ULCL UPF and PSA UPF, can receive and send data packets based on PDR. Yes, for the same data stream, different UPFs have different PDR entries for the data stream, or are not completely the same.
  • the PDR entry in DLCL UPF indicates the next hop of the data stream (PSA UPF), and the PDR entry in PSA UPF indicates that the next hop of the data stream is (RAN or other UPF).
  • PDR entry in DLCL UPF indicates the next hop of the data stream (PSA UPF)
  • PSA UPF the PDR entry in PSA UPF indicates that the next hop of the data stream is (RAN or other UPF).
  • PDR table For the transmission of data messages for items, please refer to the above description of data transmission by DLCL UPF according to PDR entries, which will not be described in detail here and below.
  • the packet inspection rules are introduced above, and the SMF configuration and the process of sending packet inspection rules are introduced as follows.
  • the SMF generates a PDR entry for the downlink data stream according to the identification information of the different downlink data streams contained in all the downlink data streams sent by the DN to the UE.
  • the PDR entry is used to indicate the downlink data stream with the specified identification information and the PSA UPF To indicate the DLCL UPF to send the downlink data stream matching the specified identification information in the PDR entry to the PSA UPF corresponding to the downlink data stream.
  • the SMF may deliver the sub-indication information at the granularity of the PDR entry, that is, the sub-indication information is the PDR entry.
  • SMF can flexibly adjust the PSA UPF corresponding to a certain downlink data flow by updating the PDR table entries, and can adjust the service load on the PSA UPF in time to avoid PSA UPF service overload.
  • PSA UPF1 detects that the data stream 1 being received is a big data stream
  • PSA UPF1 sends instruction information to the SMF, and the instruction information can also carry the data stream 1.
  • the identification information of is used to instruct the SMF to reconfigure the PDR entry of data stream 1.
  • the reconfigured PDR entry is used to instruct DLCL UPF to send data stream 1 to PSA UPF2.
  • PSA UPF1 may send the instruction information after the data stream 1 currently being received has been processed. It should be understood that the same data stream contains the same identification information, but may be sent at different times, and the same data stream is not granularly divided from the data and/or time contained in the data stream. For example, PSA UPF1 receives data stream 1 at 10:00, and may also receive data stream 1 again at a certain interval, such as 10:30. Therefore, in order to avoid PSA UPF1 from continuously receiving larger data streams (such as data stream 1 ), the SMF can be instructed to send the subsequent data stream 1 to other PSA UPF for processing in a timely manner.
  • SMF can configure PDR entries according to the following principles:
  • the configuration principle may be that each PSA UPF is responsible for receiving and/or processing part of the downlink data stream in all the downlink data streams, and the data received by the same PSA UPF does not overlap, that is, the same downlink data stream is only sent to one PSA UPF.
  • the configuration principle can also be that each PSA UPF is responsible for receiving and/or processing part of the downlink data stream in all the downlink data streams, and the data received by the same PSA UPF can overlap, for example, the same downlink data stream can be sent To multiple PSAs UPF, or send part of the data packets in the same downlink data stream to different PSAs UPF.
  • part or all of the data messages in the same data flow are sent to at least two PSA UPFs, and the two PSA UPFs send part or all of the data messages in the same data flow to the next network element, node Or equipment.
  • PSA UPF1 and PSA UPF2 can send the same part or all of the data packets to the RAN.
  • PSA UPF1 and PSA UPF2 can send the same part Or all data messages are sent to ULCL UPF.
  • the next network element, node or device the same data message can be received through multiple paths to improve the reliability of data transmission.
  • the next network element, node, or device may also perform data processing such as merging and joint decoding on part or all of the same data message, which is not limited in the embodiment of the present application.
  • Step 3 Each PSA UPF sends the downlink data stream received by itself to the RAN;
  • PSA UPF1 and PSA UPF2 process the respective received downlink data streams, and send the processed downlink data streams to the RAN through the N3 interface.
  • PSA UPF1 and PSA UPF2 are also configured with packet inspection rules, and the packet inspection rules are used to indicate the routing mode of the data flow received by each PSA UPF.
  • the PDR rules of each PSA UPF may also be different. For example, the PDR entry of PSA UPF1 is used to instruct PSA UPF1 to send data stream 1 to the RAN, and the PDR entry in PSA UPF2 is used to instruct PSA UPF2 to send data stream 2 to the RAN.
  • Step 4 The RAN sends the received downlink data stream to the UE.
  • steps 2 and 3 are only for illustration, and step 2 does not indicate that DLCL UPF sends downlink data streams to PSA UPF1 and PSA UPF2 at the same time. Step 3 does not indicate that PSA UPF1 and PSA UPF2 simultaneously send the received downlink data streams to the RAN.
  • the embodiment of the present application does not limit the sequence of sending and receiving data that can be transmitted in parallel.
  • FIG. 6 it is a schematic diagram of the transmission process of the method shown in FIG. 4 applied to the downlink data stream in the network architecture shown in FIG. 3.
  • the process can include:
  • Step a The data network DN sends the downlink data stream to be sent to a UE to the DLCL UPF.
  • Step b DLCL UPF sends the downlink data stream to at least two PSAs UPF corresponding to the downlink data stream according to the first indication information obtained from the SMF.
  • the first indication information may be a PDR
  • the sub-indication information is at least one PDR entry in the PDR.
  • the manner in which the DLCL UPF sends the downlink data stream to the PSA UPF corresponding to the downlink data stream according to the first instruction can refer to the related description of step 2 in the foregoing embodiment, and the description will not be repeated here.
  • the first indication information contains part of the sub-indication information, used to indicate part of the downlink data stream sent to PSA UPF1, and the remaining part of the sub-indication information, used to indicate part of the downlink data sent to PSA UPF2 flow. That is, the downlink data streams received by PSA UPF1 and PSA UPF2 are part of all the downlink data streams, and the downlink data streams received by PSA UPF1 and PSA UPF2 are different.
  • Step c PSA UPF1 and PSA UPF2 send the received downlink data stream to ULCL UPF.
  • PSA UPF1 and PSA UPF2 process the respective received downlink data streams, and send the processed downlink data streams to ULCL UPF through the N9 interface.
  • the ULCL UPF sends the downlink data stream.
  • PSA UPF3 etc. in Fig. 7 are only for illustration. In the scenario of Fig. 3, only PSA UPF1 and PSA UPF2 are included.
  • PSA UPF1 and PSA UPF2 send their respective downstream data streams based on their PDR performance.
  • PSA UPF1 and PSA UPF2 send downlink data streams according to PDR entries, please refer to the relevant description above, which will not be repeated here.
  • Step d ULCL UPF sends the received downlink data stream to the RAN through the N3 interface.
  • ULCL UPF sends the downlink data stream to the RAN based on its own packet inspection rules. As shown in Table 4 below, it is a specific indication of the PDR table entries in ULCL UPF.
  • Step 15 The RAN sends the received downlink data stream to the UE.
  • step c to step e another optional method is that PSA UPF1 and/or PSA UPF2 sends the respective received downlink data stream to the RAN, and then forwards it to the UE by the RAN, that is, not ULCL UPF Forward it.
  • steps b and c are only for illustration, and step b does not instruct DLCL UPF to simultaneously send downlink data streams to PSA UPF1 and PSA UPF2.
  • step c does not indicate that PSA UPF1 and PSA UPF2 simultaneously send the respective received downlink data streams to ULCL UPF.
  • the embodiment of the application does not limit this.
  • Step S800 the UE sends the uplink data stream to the RAN;
  • Step S801 The RAN sends the uplink data stream received from the terminal device to the ULCL UPF;
  • step S802 the ULCL UPF receives the uplink data stream from the RAN.
  • Step S803 The ULCL UPF sends the received uplink data to the PSA UPF corresponding to the uplink data flow according to the second indication information.
  • the ULCL UPF has obtained the second indication information, and the obtaining method may be obtained from the SMF.
  • the two indication information may be a packet detection rule of the uplink data flow of the UE.
  • the second indication information is used to instruct the ULCL UPF to send all uplink data streams sent by the UE to the DN to the DN through at least two PSAs UPF. It can be understood that the upstream data stream received by each PSA UPF is part of the upstream data stream in all the upstream data streams, so as to avoid the overload of one of the PSA UPF upstream services causing network congestion.
  • ULCL UPF matches the received upstream data stream with PDR table entries based on the PDR, and sends the upstream data stream matching the PDR (through the N9 interface corresponding to each PSA PDU in ULCL UPF) to the corresponding upstream data stream.
  • PSA PDU For the PDR used to indicate the uplink data stream transmission mode and how to perform data transmission according to the PDR, refer to the above-mentioned related description of the first indication information used to indicate the downlink data stream, and the description will not be repeated here.
  • Step S804 PSA UPF1 and PSA UPF2 receive the uplink data stream from ULCL UPF, and send the received uplink data stream to DLCL UPF;
  • PSA UPF1 and PSA UPF2 process the respective upstream data streams received, and send the processed upstream data streams to DLCL UPF through the N9 interface.
  • DLCL UPF sends the upstream data stream.
  • PSA UPF3 and so on in FIG. 9 are only for illustration. In the scenario of FIG. 3, only PSA UPF1 and PSA UPF2 are included.
  • step S805 the DLCL UPF sends the upstream data stream received from each PSA UPF to the data network DN.
  • PSA UPF1 and/or PSA UPF2 send the respective received upstream data streams to the data network DN.
  • step S804 is only for illustration, and step S804 does not instruct PSA UPF1 and PSA UPF2 to simultaneously send the respective received upstream data streams to DLCL UPF.
  • the embodiment of the application does not limit this.
  • the network architecture shown in Figure 2 or Figure 3 above can be a physical network composed of physical devices, or a virtual network composed of virtual network elements.
  • AMF, SMF, ULCL UPF, DLCL UPF, or PSA UPF can be at least one A functional network element on a virtual machine.
  • the ULCL UPF entity, DLCL UPF entity, or PSA UPF entity may have been built during networking, and in use, different states, such as active state and inactive state, can be switched according to service requirements.
  • the status of the ULCL UPF entity and PSA UPF2 entity can be inactive.
  • the actual working network elements are equivalent to the network architecture shown in Figure 1, and PSA UPF1 is responsible for processing For all upstream data streams and all downstream data streams of this terminal device, if PSA UPF1 detects a higher throughput upstream data stream, it will trigger ULCL through SMF when there is a business requirement that requires ULCL UPF to offload the upstream data stream.
  • UPF and PSA UPF2 switch from inactive state to active state.
  • PSA UPF1 detects a downstream data stream with a large throughput, and a business requirement that requires DLCL UPF for downstream data stream offloading is generated, SMF can trigger DLCL UPF and PSA UPF2 to switch from inactive state to active state. It should be understood that if PSA UPF2 is already activated in the current network, there is no need to reactivate it.
  • the above method realizes the flexible configuration of the physical network that adapts to service requirements.
  • the activated state may be a state in which the entity is activated (or powered on), or a state in which the function of the entity is effective.
  • the inactive state can be a state in which the entity is stopped (or power-off), or a state in which the function of the entity is not effective.
  • the method of creating a virtual network is to add network elements with each virtual core network to at least one virtual machine to form the virtual network.
  • the virtual core network element integrates the functions of the physical core network element, and the virtual core network element includes part or all of AMF, SMF, ULCL UPF, DLCL UPF, or PSA UPF.
  • virtual network elements such as ULCL UPF, DLCL UPF, or PSA UPF can also be configured at any time according to business requirements, and configuration can also be understood as adding or inserting.
  • the original virtual network (such as the network architecture shown in Figure 1) does not contain virtual network elements such as ULCL UPF, DLCL UPF, or PSA UPF2, and ULCL UPF, DLCL UPF or at least A new PSA UPF such as PSA UPF2 to form a new virtual network.
  • virtual network elements such as ULCL UPF, DLCL UPF, or PSA UPF2
  • ULCL UPF, DLCL UPF or at least A new PSA UPF such as PSA UPF2 to form a new virtual network.
  • the networking mode can be divided into first establishing ULCL UPF and then establishing DLCL UPF.
  • the networking processes for establishing the network architecture shown in Figure 3 on the basis of Figure 1 are carried out separately. instruction.
  • Networking method 1 ULCL UPF is established first, then DLCL UPF is established.
  • FIG. 10 it is a schematic flowchart of a networking method provided by an embodiment of this application, and the method includes:
  • Step S1000 SMF selects PSA UPF1 for the UE as the IP anchor point of the PDU session
  • the uplink data flow and downlink data flow of the terminal device will be processed in PSA UPF1.
  • the path of the uplink data flow and the downlink data flow of the terminal equipment includes: RAN, PSA, UPF1, and DN.
  • step S1000 is an optional step, not a mandatory step.
  • step S1001 the SMF receives activation indication information.
  • the activation indication information is used to instruct the SMF to establish a DLCL UPF and at least one new PSA UPF.
  • the following takes the establishment of a new PSA UPF such as PSA UPF2 as an example for introduction.
  • the establishment can be understood as adding, inserting, and configuring.
  • condition for triggering the activation indication information may satisfy one or more of the following triggering conditions:
  • Trigger condition one the flow rate of the data stream is not lower than the preset flow rate threshold.
  • the data stream includes an upstream data stream and a downstream data stream.
  • the following is an example of the upstream data stream to introduce the trigger conditions.
  • PSA UPF1 determines that the trigger condition is met, and sends activation indication information to SMF.
  • the activation indication information is used to instruct SMF to activate DLCL UPF, optional, if only PSA UPF1 exists in the current network architecture, SMF can also choose to activate a new PSA UPF (such as PSA UPF2).
  • the indication information reported by PSA UPF1 to SMF may also include the identification information of the upstream data stream, for example, part or all of the five-tuple of the data stream.
  • the SMF configures the PDR rule for the upstream data stream according to DLCL UPF.
  • the PDR rule contains the identification information of the upstream data flow and the transmission parameters, which are used to instruct the DLCL UPF to migrate the data flow matching the identification information to other PSA UPFs to avoid overloading of the downstream services of the PSA UPF1.
  • Trigger condition 2 The service type of the downlink data stream is a preset service type.
  • the preset service types can be multiple, such as video services. If the upstream data stream received by the PSA UPF is a video stream, it is determined that the trigger conditions are met, and an indication information is sent to the SMF. The indication information is used to instruct the SMF to activate DLCL UPF, or DLCL UPF and at least one new PSA UPF (such as PSA UPF2 ).
  • the above triggering process is only an example, and it may also be that other network elements in the core network detect the trigger condition and trigger the SMF to activate the DLCL UPF and/or the new PSA UPF.
  • the detection is performed by the AMF.
  • the AMF sends indication information to the SMF to instruct the SMF to activate DLCL UPF and/or new PSA UPF.
  • the indication information may be of the same type as the indication information sent when the condition is met. For details, please refer to the above description of the indication information, and the description will not be repeated here.
  • Trigger condition three the original PSA UPF (such as PSA UPF1) has its own service load reaching a preset threshold, then the PSA UPF1 determines to the SMF that the trigger condition is met, and sends activation indication information to the SMF.
  • step S1002 the SMF establishes ULCL UPF and PSA UPF2.
  • step S1001 and step S1002 it can be understood that ULCL UPF and PSA UPF2 are added to the virtual network, but ULCL UPF and PSA UPF2 are not effective in the network, or the status of ULCL UPF and PSA UPF2 is inactive State or not enabled state. That is, at this time, the uplink data stream and the downlink data stream of the UE are still transmitted on the PSA UPF1.
  • the SMF can also configure corresponding uplink data flow packet detection rules and downlink data packet detection rules for ULCL UPF, PSA UPF1, and PSA UPF2.
  • SMF configures ULCL UPF for the first packet detection rule of the uplink data stream.
  • the first packet detection rule includes at least one PDR entry, some of which can be used to indicate that ULCL UPF will receive
  • the uplink data stream matching the PDR table entry is sent to PSA UPF1, and some of the PDR table entries in the remaining PDR table entries can be used to instruct ULCL UPF to send the received uplink data stream matching the PDR table entry to PSA UPF2.
  • SMF can also configure a second packet detection rule for the downlink data stream for ULCL UPF.
  • the second packet detection rule includes an indication of a PDR entry, and some of the PDR entries can be used to indicate that ULCL UPF will receive a matching rule.
  • the downlink data stream of the PDR table entry is sent to PSA UPF1, and some of the PDR table entries in the remaining PDR table entries can be used to instruct ULCL UPF to send the received downlink data stream matching the PDR table entry to PSA UPF2. Among them, different PDR entries are used to indicate different data streams.
  • SMF generates a new PDR entry of the data stream corresponding to the identification information according to the identification information of the data stream reported by PSA UPF1, and the PDR entry is used to indicate ULCL UPF sends the upstream data stream matching the identification information to PSA UPF2. It can be understood that after PSA UPF1 detects a larger upstream data stream, it instructs SMF to allocate the upstream data stream to PSA UPF2 for processing to reduce PSA UPF1 Reduce the risk of network congestion.
  • PSA UPF1 and PSA UPF2 are each responsible for processing part of the entire upstream data stream to avoid overloading of one of the PSA UPF.
  • PSA UPF1 and PSA UPF2 are each responsible for processing part of the entire upstream data stream to avoid overloading of one of the PSA UPF.
  • the data stream whose identification information is the first identification information is sent to PSA UPF1
  • the data stream whose identification information is the second identification information is sent to PSA UPF2.
  • the information contained in the first identification information and the second identification information are completely different or not completely the same. For details, please refer to the relevant description of the packet detection rules above, which will not be repeated here.
  • the second packet detection rule includes at least one PDR entry, and the PDR entry may be used to instruct ULCL UPF to receive downlink data streams from PSA UPF1 and PSA UPF2, and send the received downlink data streams to the RAN.
  • the PDR entry may be used to instruct ULCL UPF to receive downlink data streams from PSA UPF1 and PSA UPF2, and send the received downlink data streams to the RAN.
  • SMF configures the third packet detection rule for the downstream data stream for PSA UPF1.
  • the third packet detection rule includes at least one PDR entry, which can be used to indicate the match that PSA UPF1 will receive
  • the downlink data stream of this PDR entry is sent to ULCL UPF. It should be understood that there are existing upstream packet inspection rules in PSA UPF1. Therefore, it is not necessary to configure new upstream data flow packet inspection rules for PSA UPF1 here.
  • SMF configures the fourth packet detection rule for the downlink data stream for PSA UPF2.
  • the fourth packet detection rule includes at least one PDR entry, which can be used to indicate the match that PSA UPF2 will receive The downlink data stream of this PDR entry is sent to ULCL UPF.
  • the SMF can also configure the fifth packet detection rule for the uplink data stream for PSA UPF2.
  • the fifth packet detection rule includes an indication of a PDR entry.
  • the PDR entry can be used to indicate that PSA UPF2 will receive matching the PDR table.
  • the upstream data stream of the item is sent to the data network DN.
  • Step S1003 The SMF sends the first packet detection rule of the uplink data flow and the second packet detection rule of the downlink data flow to the ULCL UPF.
  • the SMF sends the first packet inspection rule and/or the second packet inspection rule to ULCL UPF through the N4 interface.
  • first packet inspection rule and the second packet inspection rule can be in the same PDR or different PDRs, that is, when the SMF is issued, they can be sent at the same time or separately Specifically, for the transmission of the first packet inspection rule and the second packet inspection rule, SMF may send at least one PDR entry in the first packet inspection rule or the second packet inspection rule. Not limited.
  • step S1004 the SMF is the third packet detection rule of the downstream data stream sent by the PSA UPF1.
  • the SMF sends the third packet detection rule to the PSA UPF1 through the N4 interface, and the PDR entry in the third packet detection rule is used to instruct the PSA UPF1 to send the downlink data stream to the ULCL UPF.
  • the SMF is configured for the PDR entry of the downlink data stream configured for PSA UPF1, which can be configured in combination with the PDR entry of the downlink data stream with the same identification information configured for ULCL UPF, so as to configure a complete configuration of the downlink data stream with the same identification information.
  • Downlink transmission path a certain PDR entry configured by SMF for ULCL UPF may be a downlink data stream whose identification information is the third identification information received from PSA UPF1.
  • a certain PDR entry configured by SMF for PSA UPF1 may be In order to send the downlink data stream whose identification information is the third identification information to ULCL UPF.
  • the current downlink data stream transmission process can be: the downlink data stream is sent from the data network DN side, and sequentially passes through the PSA UPF1, ULDL UPF, and RAN to the UE.
  • the transmission process of the uplink data stream of the UE may be: after the uplink data stream is sent from the UE side, it is still transmitted to the DN side via the PSA UPF1.
  • step S1005 the SMF is the PSA UPF2 sending the fourth packet detection rule for the uplink data flow and the fifth packet detection rule for the downlink data flow.
  • the SMF sends the fourth packet detection rule of the uplink data flow and the fifth packet detection rule of the downlink data flow to the PSA UPF2 through the N4 interface.
  • both the fourth packet detection rule and the fifth packet detection rule may include indicating a PDR entry.
  • the fourth packet inspection rule and the fifth packet inspection rule can be in the same PDR or different PDRs. That is to say, when the SMF is issued, they can be sent at the same time or separately.
  • the SMF may send at least one PDR entry in the fourth packet inspection rule or the fifth packet inspection rule, which is not limited in this embodiment of the application.
  • the core network tunnel information on the RAN side has not been updated, that is, the RAN has not established a tunnel with ULCL UPF, and the RAN still sends the uplink data stream.
  • the RAN has not established a tunnel with ULCL UPF
  • the RAN still sends the uplink data stream.
  • PSA UPF1 and the DN side still sends the downlink data stream to PSA UPF1, so PSA UPF2 cannot receive the downlink data stream either. Therefore, under the current network configuration, the transmission process of the uplink data stream and the transmission process of the downlink data stream may be the same as those introduced in step S1004.
  • step S1006 the SMF sends core network tunnel information to the RAN.
  • the SMF sends the core network tunnel information to the AMF (not shown in FIG. 10), and the AMF sends the core network tunnel information to the RAN through the N1 interface.
  • Step S1006 is only for illustration, and it may also be that the AMF or UPF (for example, PSA UPF1 when connected to the RAN) sends the core network tunnel information to the RAN. The embodiment of the application does not limit this.
  • the core network tunnel information is used to establish a tunnel connection between core network elements, for example, a tunnel connection between ULCL UPF and PSA UPF1 and ULCL UPF and PSA UPF2.
  • the network elements of the core network perform data message transmission based on the tunnel with the peer network element.
  • the SMF may be sent to each core network element, or it may be generated by the core network element itself, which is not limited in the embodiment of the present application.
  • the core network element is based on the tunnel information of the RAN, and the RAN establishes a tunnel connection with the core network element based on the core network tunnel information.
  • SMF sends core network tunnel information to RAN and RAN tunnel information to ULCL UPF to establish a tunnel connection between ULCL UPF and RAN
  • the destination of the uplink data flow of the RAN is ULCL UPF.
  • the core network tunnel information is set as the tunnel header of the N3 interface of the PDU session (including the uplink IP address corresponding to N3 and the uplink GTP-U TEID information), and GTP-U TEID is the GPRS tunnel protocol endpoint Identifier (GPRS Tunnel Protocol Tunnel Endpoint Identifier).
  • the tunnel header is relative to the RAN and refers to the N3 interface on the ULCL UPF.
  • the access network device Based on the core network tunnel information, sends the upstream data stream to the IP address indicated by the core network tunnel information, that is, the N3 interface of ULCL UPF.
  • the UE's uplink data stream transmission process can be: After the uplink data stream is sent from the UE side, a possible situation is that part of the uplink data stream goes through RAN, ULCL UPF, PSA UPF1 to DN in turn . In another possible situation, the remaining part of the uplink data flow passes through RAN, ULCL UPF, PSA UPF2 to DN in sequence. It should be understood that although PSA UPF1 has not updated the packet detection rules of the uplink data flow, the packet detection rules do not limit which network element (or node) the uplink data flow is sent from, so the uplink data flow can still be received from the ULCL UPF.
  • the transmission process of the downlink data stream of the UE may be: after the downlink data stream is sent from the DN side, part of the downlink data stream sequentially passes through the PSA UPF1, ULCL UPF, and RAN to the UE. In another possible situation, the remaining part of the uplink data stream passes through PSA UPF2, ULCL UPF, and RAN to the UE in sequence.
  • Step S1007 SMF establishes DLCL UPF.
  • SMF adds DLCL UPF to the virtual network, or activates DLCL UPF.
  • Step S1008 The SMF sends the sixth packet detection rule of the uplink data flow and the seventh packet detection rule of the downlink data flow to the DLCL UPF.
  • the SMF configures the sixth packet detection rule for the uplink data flow and the seventh packet detection rule for the downlink data flow for the DLCL UPF, and sends the sixth packet detection rule and the seventh packet detection rule to the DLCL UPF.
  • the SMF configures the sixth packet detection rule of the uplink data flow for DLCL UPF, and the sixth packet detection rule includes at least one PDR entry, which can be used to indicate that the DLCL UPF will receive matching the PDR entry
  • the upstream data stream is sent to the DN.
  • the SMF can also configure the seventh packet detection rule for the downlink data stream for DLCL UPF.
  • the seventh packet detection rule contains an indication of a PDR entry, and some of the PDR entries can be used to indicate that the DLCL UPF will receive matching the The downlink data stream of the PDR table entry is sent to PSA UPF1, and some of the PDR table entries in the remaining PDR table entries can be used to instruct DLCL UPF to send the received downlink data stream matching the PDR table entry to PSA UPF2.
  • the use process and configuration method of the sixth packet detection rule and the seventh packet detection rule can be referred to the above description, and will not be repeated here.
  • Step S1009 The DLCL UPF sends downlink routing information to the DN side, and the downlink routing information is used to instruct the DN to send the downlink data stream of the terminal device to the DLCL UPF;
  • the downlink routing information may indicate the next hop of the data packet whose destination IP address is the IP address of the UE, and the next hop may be the IP address of DLCL and UPF.
  • the DN side sends the downlink data stream sent to the UE to the DLCL UPF based on the downlink routing information.
  • the downlink routing information may be carried in the SE message.
  • the UE's downlink data stream transmission process can be as follows: after the downlink data stream is sent from the DN side, part of the downlink data stream sequentially passes through DLCL UPF, PSA UPF1, ULCL UPF, and RAN to the UE. In another possible situation, the remaining part of the uplink data flow passes through DLCL UPF, PSA UPF2, ULCL UPF, and RAN to the UE in sequence.
  • the packet inspection rule is used to instruct PSA UPF1 to send the upstream data stream to DLCL UPF, or instruct PSA UPF2 to send the upstream data stream to DLCL UPF.
  • the transmission process of the UE's uplink data flow under this network configuration can be: After the uplink data flow is sent by the UE side, a possible situation Yes, part of the upstream data flow passes through RAN, ULCL UPF, PSA UPF1, DLCL UPF to DN in sequence. In another possible situation, the remaining part of the uplink data flow passes through RAN, ULCL UPF, PSA UPF2, DLCL UPF to DN in sequence.
  • Networking method 2 Establish ULCL UPF and DLCL UPF at the same time.
  • FIG. 11 it is a schematic flowchart of a networking method provided by an embodiment of this application, and the method includes:
  • step S1100 the SMF selects PSA UPF1 for the UE as the IP anchor point of the PDU session;
  • the uplink data flow and downlink data flow of the terminal device will be processed in PSA UPF1.
  • the path of the uplink data flow and the downlink data flow of the terminal equipment includes: RAN, PSA UPF1, and DN.
  • step S1100 is an optional step and not a necessary step.
  • step S1101 the SMF receives activation indication information.
  • the activation indication information is used to instruct the SMF to establish DLCL UPF, ULCL UPF, and at least one new PSA UPF.
  • the following takes the establishment of a new PSA UPF such as PSA UPF2 as an example for introduction.
  • step S1102 the SMF establishes DLCL UPF, ULCL UPF, and PSA UPF2.
  • step S1101 and step S1102 it can be understood that DLCL UPF, ULCL UPF, and PSA UPF2 are added to the virtual network, but DLCL, PFULCL UPF, and PSA UPF2 are not effective in this network, in other words, ULCL UPF and PSA UPF2
  • the state of is inactive or not enabled. That is, at this time, the uplink data stream and the downlink data stream of the UE are still transmitted on the PSA UPF1.
  • the SMF may also configure corresponding uplink data flow packet detection rules and downlink data packet detection rules for DLCL UPF, ULCL UPF, PSA UPF1, and PSA UPF2.
  • step S1002 For the specific configuration method and method flow, please refer to the relevant description of step S1002 above, which will not be repeated here.
  • the packet inspection rule for the uplink data flow configured with SMF as ULCL UPF is referred to as the first packet inspection rule
  • the packet inspection rule for the downlink data flow configured with SMF as ULCL UPF is referred to as the second packet inspection rule.
  • the packet inspection rule, the packet inspection rule of the downstream data stream configured with SMF of PSA UFP1 is referred to as the third inspection rule
  • the packet inspection rule of the downstream data stream configured with SMF of PSA UFP2 is referred to as the fourth inspection rule
  • the SMF is referred to as PSA
  • the packet inspection rule for the downstream data stream configured by UPF2 is referred to as the fifth packet inspection rule for short
  • the packet inspection rule for the upstream data stream configured by SMF as DLCL UPF is referred to as the sixth packet inspection rule
  • the SMF is referred to as the upstream data stream configured by DLCL UPF
  • the packet inspection rule of ” is referred to as the seventh packet inspection rule for short.
  • the SMF is the seventh packet inspection rule configured by DLCL UPF, which can be Indicate that the PSA UPF corresponding to data stream A is PSA UPF1, or it may indicate that the PSA UPF corresponding to data stream A is PSA UPF2.
  • DLCL UPF the seventh packet inspection rule configured by DLCL UPF
  • Step S1103 The SMF sends the first packet inspection rule and the second packet inspection rule to the ULCL UPF.
  • Step S1104 The SMF sends the sixth packet inspection rule and the seventh packet inspection rule to the DLCL UPF.
  • Step S1105 The DLCL UPF sends downlink routing information to the DN side, and the downlink routing information is used to instruct the DN to send the downlink data stream of the terminal device to the DLCL UPF;
  • step S1105 For the execution flow of step S1105, reference may be made to the relevant description of step S1008 above, which will not be repeated here.
  • step S1103 there is no order restriction between step S1103 and step S1105.
  • the above process is only a kind of process illustration. It can also be that the SMF first sends the sixth packet detection rule and the seventh packet detection rule to DLCL UPF, and then The ULCL UPF sends the execution order of the first packet detection rule and the second packet detection rule, which is not limited in the embodiment of the application.
  • step S1106 the SMF is the third packet detection rule for the PSA UPF1 to send the downlink data stream.
  • the SMF sends the third packet detection rule to the PSA UPF1 through the N4 interface, and the PDR entry in the third packet detection rule is used to instruct the PSA UPF1 to send the downlink data stream to the ULCL UPF.
  • step S1106 For the execution flow of step S1106, reference may be made to the related description of step S1004 above, which will not be repeated here.
  • step S1105 and step S1106 are not limited in order. It can be executed simultaneously or sequentially, and the order of execution is not limited.
  • step S1107 the SMF is the PSA UPF2 sending the fourth packet detection rule for the uplink data flow and the fifth packet detection rule for the downlink data flow.
  • step S1107 For the execution flow of step S1107, reference may be made to the related description of step S1005 above, which will not be repeated here.
  • step S1108 the SMF sends the core network tunnel information to the RAN through the AMF, and sends the RAN tunnel information to the ULCL UPF, so as to establish a tunnel connection between the RAN and the ULCL UPF.
  • the SMF sends the core network tunnel information to the AMF (not shown in FIG. 11), and the AMF sends the core network tunnel information to the RAN through the N1 interface.
  • Step S1108 is only for illustration, and it may also be that the AMF or UPF (for example, PSA UPF1 when connected to the RAN) sends the core network tunnel information to the RAN.
  • the embodiment of the application does not limit this.
  • step S1108 reference may be made to the related description of step S1007 above, which will not be repeated here.
  • FIG. 10 and FIG. 11 are only examples, and multiple PSAs and UPFs can be established in the embodiment of the present application, which are not shown in FIG. 10 and FIG. 11.
  • the above-mentioned manners of establishing ULCL UPF, DLCL UPF and PSA UPF by SMF and updating the uplink and downlink packet detection rules of each UPF are only for illustration, and other nodes or network elements can also execute SMF in the above Figure 10 or Figure 11. Steps are not limited in the embodiment of this application.
  • the "establishment" in the embodiment of the present application may be any of the above-described addition, insertion, creation, configuration, activation, or enabling under possible scenarios.
  • the above content is the method flow for establishing a new core network network element.
  • it can also be based on service requirements. For example, when the data flow of the UE is small, you can Select to release at least one part or all of PSA UPF, DLCL UPF, or ULCL UPF.
  • FIG. 12 it is a schematic flowchart of a method for releasing a network element according to an embodiment of this application.
  • This method can be applied to the network architecture of Fig. 2 or Fig. 3.
  • the following takes Fig. 3 as an example to describe in detail the process of releasing at least one of the PSA UPF, DLCL UPF, or ULCL UPF in Fig. 3.
  • the method can include the following steps:
  • step S1200 the SMF receives release indication information, the release indication information is used to instruct to release part or all of at least one PSA UPF, DLCL UPF or ULCL UPF, the following assumes that the release indication information is used to indicate the release of PSA UPF2, DLCL UPF and ULCL UPF.
  • the release indication information may be sent by at least one of the at least two PSA UPFs of the UE.
  • PSA UPF2 when sent by PSA UFP2, PSA UPF2 sends the release indication information to the SMF when it detects that the release condition is met.
  • the release condition may be satisfied as follows: a data stream is not received within a preset time, and the data stream includes an upstream data stream and/or a downstream data stream. For example, when PSA UPF2 does not receive a downlink data stream within a preset time, the release condition is currently met.
  • step S1201 the SMF updates the RAN side uplink data flow rule through the AMF, including core network tunnel information required to establish a tunnel connection with the PSA UPF1, and instructs the RAN to send the uplink data flow to the PSA UPF1.
  • SMF sends the core network tunnel information required by PSA UPF1 and RAN to establish a tunnel connection to AMF, which is sent to RAN through N2 interface, and sends RAN tunnel information to PSA UPF1 to establish a connection between RAN and PSA UPF1 Tunnel connection.
  • the transmission process of the UE's uplink data stream can be: after the uplink data stream is sent from the UE side, it goes through RAN, PSA UPF1 to DN in turn.
  • the transmission process of the UE's downlink data stream can still be as follows: after the downlink data stream is sent from the DN side, part of the downlink data stream sequentially passes through DLCL UPF, PSA UPF1, ULCL UPF, and RAN to the UE. In another possible situation, the remaining part of the uplink data flow passes through DLCL UPF, PSA UPF2, ULCL UPF, and RAN to the UE in sequence.
  • step S1202 the SMF configures a new packet inspection rule for the downstream data stream to the PSA UPF1.
  • the SMF sends a packet detection rule that can configure a new downlink data stream for PSA UPF1 to PSA UPF1 through the N4 interface, and the packet detection rule is used to instruct PSA UPF1 to send the downlink data stream to the RAN.
  • PSA UPF1 can send uplink and downlink data streams to the corresponding destination.
  • Step S1203 The PSA UPF1 sends second downlink routing information to the DN.
  • the second downlink routing information is used to instruct the DN to send the downlink data stream whose destination IP address is the IP address of the UE to the PSA UPF1.
  • the transmission process of the uplink data stream of the UE can be as follows: after the uplink data stream is sent from the UE side, it sequentially passes through RAN, PSA and UPF1 to DN.
  • the transmission process of the downlink data stream of the UE may be as follows: after the downlink data stream is sent from the DN side, part of the downlink data stream sequentially passes through the PSA UPF1 and the RAN to the UE.
  • the upstream data stream and the downstream data stream are restored to the transmission mode under the network architecture of FIG. 1.
  • ULDL UPF and DLCL UPF are released, there will be no impact on the data stream transmission to the destination.
  • step S1204 the SMF triggers the release of ULCL UPF, DLCL UPF, and PSA UPF2.
  • the data stream transmission mode and network configuration mode are similar to the separate deployment, please refer to the relevant description above
  • the difference is that when deploying in one, such as when DLCL UPF and PSA UPF2 are deployed in one, when DLCL UPF sends a downlink data stream to PSA UPF2, the downlink data stream does not need to traverse IP, which simplifies the transmission method.
  • SMF may not issue PDR to DLCL UPF, and DLCL UPF records the relationship between each data flow and the corresponding PSA UPF.
  • DLCL UPF can adjust and record the correspondence between the data stream and the destination PSA UPF according to the internal PSA's business load status.
  • each network element described above includes hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • an embodiment of the present application further provides a device 1300 for implementing the function of downstream offloading user plane network elements in the above-mentioned method.
  • the device 1300 may exist in the form of software or hardware.
  • the device may be a software module or a chip system.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the apparatus 1300 may include: a processing unit 1301 and a communication unit 1302.
  • the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • the functional modules in the various embodiments of the present application may be integrated in one processor, or may exist alone physically, or two or more modules may be integrated in one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules.
  • the communication unit 1302 is configured to receive first indication information from the session management network element; the processing unit 1301 uses According to the first instruction information, all the downlink data streams sent by the data network DN to the first terminal device through the communication unit 1302 are sent to the first terminal device through at least two target protocol data unit PDU session anchor points ; Wherein, the at least two target PDU session anchor points respectively send part of the data stream in the downlink data stream to the first terminal device.
  • the first indication information includes at least one sub-indication information, and each sub-indication information is used to indicate the correspondence between the identification information of different downlink data streams and the target PDU session anchor;
  • the The processing unit 1301 is configured to, for each sub-indication information, send a downlink data stream matching the identification information contained in the sub-indication information to the corresponding downlink data stream matching the identification information contained in the sub-indication information through the communication unit 1302 The target PDU session anchor point.
  • the identification information may include one or more of the following: source address information, destination address information, source port identification, destination port identification, or protocol type.
  • the sub-indication information may further include: an Internet Protocol IP address used in the first user plane network element to send the downlink data stream, and/or the target PDU session anchor point used to receive the downlink data The IP address of the stream.
  • the communication unit 1302 is configured to receive second indication information from the mobile session management network element; the processing unit 1301 is configured to communicate through the second indication information according to the second indication information.
  • the unit 1302 receives from at least one first PDU session anchor point the uplink data stream sent by the first terminal device to the data network; wherein, the first PDU session anchor point is capable of sending to the data network One of the PDU session anchor points on the network element of the uplink data flow of the first terminal device.
  • processing unit 1301 may also be configured to generate first downlink routing information before sending the uplink data stream to the data network; the communication unit 1302 is configured to transfer the first downlink routing information Information is sent to the data network; the first downlink routing information is used to instruct the data network to send the downlink data stream sent to the first terminal device to the first user plane network element, so The destination of the downlink data stream is the first terminal device.
  • Fig. 14 shows an apparatus 1400 provided by an embodiment of the application, and the apparatus shown in Fig. 14 may be a hardware circuit implementation of the apparatus shown in Fig. 13.
  • the communication device may be suitable for implementing the functions of the downstream offloading user plane network element in the above method embodiment in the flowcharts shown in FIG. 4, FIG. 6, FIG. 8, and FIG. 10 to FIG.
  • FIG. 14 only shows the main components of the communication device.
  • the apparatus 1400 shown in FIG. 14 includes at least one processor 1420, configured to implement the function of downstream offloading user plane network elements in the method provided in the embodiment of the present application.
  • the device 1400 may further include at least one memory 1430 for storing program instructions and/or data.
  • the memory 1430 and the processor 1420 are coupled.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 1420 may operate in cooperation with the memory 1430.
  • the processor 1420 may execute program instructions stored in the memory 1430. At least one of the at least one memory may be included in the processor.
  • the apparatus 1400 may further include a communication interface 1410 for communicating with other devices through a transmission medium, so that the apparatus used in the apparatus 1400 can communicate with other devices.
  • the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.
  • the transceiver may be an independent receiver, an independent transmitter, a transceiver with integrated transceiver functions, or an interface circuit.
  • the processor 1420 uses the communication interface 1410 to send and receive data, and is used to implement the method executed by the downstream offload user plane network element in the embodiment corresponding to the flowcharts shown in FIGS. 4, 6, 8, and 10-12.
  • the communication interface 1410 is configured to receive the first indication information from the session management network element; the processor 1420 is configured to The first indication information is to send all the downlink data streams sent from the data network DN to the first terminal device through the communication interface 1410 to the first terminal device through at least two target protocol data unit PDU session anchor points; wherein, the At least two target PDU session anchor points respectively send part of the data stream in the downlink data stream to the first terminal device.
  • the processor 1420 and the communication interface 1410 reference may be made to the description in the method flow shown in the flowcharts shown in FIG. 4, FIG. 6, FIG. 8, and FIG. 10 to FIG. 12, which will not be repeated here.
  • the embodiment of the present application does not limit the specific connection medium between the communication interface 1410, the processor 1420, and the memory 1430.
  • the memory 1430, the processor 1420, and the communication interface 1410 are connected by a bus 1440.
  • the bus is represented by a thick line in FIG. 14.
  • the connection mode between other components is only for schematic illustration. , Is not limited.
  • the bus can be divided into an address bus, a data bus, a control bus, and so on. For ease of representation, only one thick line is used in FIG. 14, but it does not mean that there is only one bus or one type of bus.
  • an embodiment of the present application further provides an apparatus 1500 for implementing the function of the mobile session management network element in the above-mentioned method.
  • the device 1500 may exist in the form of software or hardware.
  • the device may be a software module or a chip system.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the apparatus 1500 may include: a processing unit 1501 and a communication unit 1502.
  • the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • the functional modules in the various embodiments of the present application may be integrated in one processor, or may exist alone physically, or two or more modules may be integrated in one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules.
  • the processing unit 1501 is configured to generate first indication information, and the first indication information is used to indicate the first indication information.
  • the user plane network element sends all the downlink data streams sent by the data network DN to the first terminal device to the terminal device through at least two target protocol data unit PDU session anchor points; wherein, the at least two target PDU session anchor points respectively send The first terminal device sends part of the data stream in the downlink data stream; the communication unit 1502 is configured to send the first indication information to the first user plane network element.
  • the first indication information may include at least one sub-indication information, and each sub-indication information is respectively used to indicate the correspondence between the identification information of different downlink data streams and the target PDU session anchor.
  • the identification information may include one or more of the following: source address information, destination address information, source port identification, destination port identification, or protocol type.
  • the sub-indication information may further include: an Internet Protocol IP address used to send the downlink data stream in the first user plane network element, and/or the target PDU session anchor The IP address used to receive the downstream data stream in the dot.
  • the communication unit 1502 is further configured to receive activation indication information, where the activation indication information is used to instruct the session management network element to activate the downlink offload user plane network element, or to instruct all
  • the session management network element activates the first user plane network element and at least one new PDU session anchor point, and generates the first indication information; wherein, the target PDU session anchor point includes the at least one new PDU Session anchor.
  • the activation indication information may be sent to the session management network element after at least one second PDU session anchor or mobility management network element detects that the data stream meets the trigger condition;
  • the trigger condition includes: the service type of the data stream is a preset service type; or the transmission rate of the data stream is not lower than a preset rate threshold; wherein, the data stream includes an uplink data stream and/or a downlink data stream ,
  • the uplink data stream is a data stream sent by the first terminal device to the data network; and the second PDU session anchor is a network element that can send a downlink data stream to the first terminal device
  • the PDU session anchor point does not include one of the new PDU session anchor points.
  • the communication unit 1502 is configured to receive release indication information from the third PDU session anchor point, and the release indication information is used to instruct the session management network element to release the third PDU session anchor point and/or the first user plane network element; wherein, the third PDU session anchor point is one of the PDU session anchor points on the network element capable of sending a downlink data stream to the first terminal device One of the.
  • the release indication information is sent to the session management network element after the at least one third PDU session anchor point detects that the release condition is met; the release condition includes: The third PDU session anchor does not receive a data stream within a preset time, and the data stream includes an uplink data stream and/or a downlink data stream.
  • FIG. 16 shows an apparatus 1600 provided by an embodiment of the application.
  • the apparatus shown in FIG. 16 may be a hardware circuit implementation of the apparatus shown in FIG. 15.
  • the communication device can be adapted to implement the functions of the mobile session management network element in the above method embodiment in the flowcharts shown in Figs. 4, 6, 8, and 10 to 12.
  • FIG. 16 only shows the main components of the communication device.
  • the apparatus 1600 shown in FIG. 16 includes at least one processor 1620, configured to implement the function of the mobile session management network element in the method provided in the embodiment of the present application.
  • the device 1600 may further include at least one memory 1630 for storing program instructions and/or data.
  • the memory 1630 and the processor 1620 are coupled.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 1620 may operate in cooperation with the memory 1630.
  • the processor 1620 may execute program instructions stored in the memory 1630. At least one of the at least one memory may be included in the processor.
  • the apparatus 1600 may further include a communication interface 1610 for communicating with other devices through a transmission medium, so that the apparatus used in the apparatus 1600 can communicate with other devices.
  • the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.
  • the transceiver may be an independent receiver, an independent transmitter, a transceiver with integrated transceiver functions, or an interface circuit.
  • the processor 1420 uses the communication interface 1610 to send and receive data, and is used to implement the method executed by the mobile session management network element in the embodiment corresponding to the flowcharts shown in FIGS. 4, 6, 8, and 10-12.
  • the processor 1420 is configured to generate first indication information, and the first indication information is used to indicate the first indication information.
  • the user plane network element sends all the downlink data streams sent by the data network DN to the first terminal device to the terminal device through at least two target protocol data unit PDU session anchor points; wherein, the at least two target PDU session anchor points respectively send Sending part of the data stream in the downlink data stream by the first terminal device;
  • the communication interface 1610 is configured to send the first indication information to the first user plane network element.
  • the embodiment of the present application does not limit the specific connection medium between the aforementioned communication interface 1610, the processor 1620, and the memory 1630.
  • the memory 1630, the processor 1620, and the communication interface 1610 are connected by a bus 1640 in FIG. 16.
  • the bus is represented by a thick line in FIG. 16, and the connection modes between other components are only for schematic illustration. , Is not limited.
  • the bus can be divided into an address bus, a data bus, a control bus, and so on. For ease of representation, only one thick line is used in FIG. 16, but it does not mean that there is only one bus or one type of bus.
  • an embodiment of the present application further provides a device 1700 for implementing the function of PSA and UPF in the above-mentioned method.
  • the device 1700 may exist in the form of software or hardware.
  • the device may be a software module or a chip system.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the apparatus 1700 may include: a processing unit 1701 and a communication unit 1702.
  • the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • the functional modules in the various embodiments of the present application may be integrated in one processor, or may exist alone physically, or two or more modules may be integrated in one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules.
  • the communication unit 1702 is configured to receive the data network DN from the first user plane network element and send it to the first terminal device. Part of the downstream data stream in the downstream data stream; the communication unit 1702 is further configured to send the received part of the downstream data stream to the first terminal device.
  • the target PDU session anchor point is one of at least one new PDU session anchor point activated by the session management network element after receiving the activation indication information.
  • the communication unit 1702 is configured to receive the third indication information from the session management network element; the processing unit 1701 is configured to receive the third indication information from the second user plane according to the third indication information.
  • the network element receives a part of the upstream data stream in the upstream data stream sent by the first terminal device to the data network DN, and sends the part of the upstream data stream to the first user plane network element.
  • the processing unit 1701 is configured to send release instruction information to the session management network element after detecting that the release condition is met, and the release instruction information is used to instruct the session management network The element releases the target PDU session anchor point and/or the first user plane network element.
  • FIG. 18 shows an apparatus 1800 provided by an embodiment of the application.
  • the apparatus shown in FIG. 18 may be a hardware circuit implementation of the apparatus shown in FIG. 17.
  • the communication device may be suitable for implementing the functions of PSA and UPF in the above method embodiments in the flowcharts shown in FIGS. 4, 6, 8, and 10 to 12.
  • FIG. 18 only shows the main components of the communication device.
  • the apparatus 1800 shown in FIG. 18 includes at least one processor 1820, which is configured to implement the function of PSA and UPF in the method provided in the embodiment of the present application.
  • the device 1800 may also include at least one memory 1830 for storing program instructions and/or data.
  • the memory 1830 and the processor 1820 are coupled.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 1820 may operate in cooperation with the memory 1830.
  • the processor 1820 may execute program instructions stored in the memory 1830. At least one of the at least one memory may be included in the processor.
  • the apparatus 1800 may further include a communication interface 1810 for communicating with other devices through a transmission medium, so that the apparatus used in the apparatus 1800 can communicate with other devices.
  • the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.
  • the transceiver may be an independent receiver, an independent transmitter, a transceiver with integrated transceiver functions, or an interface circuit.
  • the processor 1420 uses the communication interface 1810 to send and receive data, and is used to implement the method executed by the PSA UPF in the embodiment corresponding to the flowchart shown in FIG. 4, FIG. 6, FIG. 8, and FIG. 10 to FIG.
  • the communication interface 1810 is used to receive the data from the first user plane network element that the data network sends to the first terminal device. Part of the downstream data stream in the downstream data stream; for another example, the communication interface 1810 is further configured to send the received part of the downstream data stream to the first terminal device.
  • the processor 1820 and the communication interface 1810 reference may be made to the description in the method flow shown in the flowcharts shown in FIG. 4, FIG. 6, FIG. 8, and FIG. 10 to FIG. 12, which will not be repeated here.
  • the embodiment of the present application does not limit the specific connection medium between the communication interface 1810, the processor 1820, and the memory 1830.
  • the memory 1830, the processor 1820, and the communication interface 1810 are connected by a bus 1840.
  • the bus is represented by a thick line in FIG. 18.
  • the connection mode between other components is only for schematic illustration. , Is not limited.
  • the bus can be divided into an address bus, a data bus, a control bus, and so on. For ease of presentation, only one thick line is used in FIG. 18 to represent, but it does not mean that there is only one bus or one type of bus.
  • the processor may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware
  • the components can implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present application.
  • the general-purpose processor may be a microprocessor or any conventional processor or the like.
  • the steps of the method disclosed in combination with 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 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 to this.
  • the memory in the embodiments of the present application may also be a circuit or any other device capable of realizing a storage function for storing program instructions and/or data.
  • the methods provided in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software When implemented by 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, network equipment, user equipment, 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. For example, 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 a 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 digital video disc (digital video disc, DVD for short)), or a semiconductor medium (for example, SSD).
  • the embodiments can be mutually cited.
  • the methods and/or terms between the method embodiments can be mutually cited, such as the functions and/or functions between the device embodiments.
  • Or terms may refer to each other, for example, functions and/or terms between the device embodiment and the method embodiment may refer to each other.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供一种数据传输方法及装置，其中方法包括：第一用户面网元从会话管理网元接收第一指示信息，并根据该第一指示信息，将数据网络DN发送给第一终端设备的全部下行数据流通过至少两个目标PDU话锚点发送给第一终端设备，其中，所述至少两个目标PDU会话锚点分别向所述第一终端设备发送所述下行数据流中的部分数据流。也可以理解为，当通过至少两个PDU话锚点共同分担下行业务负载，以减轻下行数据流可能造成的网络拥塞，以保证该终端设备的PDU会话处于一种比较稳定的状态。

Description

一种数据传输方法及装置
相关申请的交叉引用
本申请要求在2020年01月21日提交中国专利局、申请号为202010072666.3、申请名称为“一种数据传输方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种数据传输方法及装置。
背景技术
在第五代(5th generation，5G)移动通信网络中，由于空口技术和芯片的升级，终端设备的能力有较大的提高，也就是，5G终端设备有能力触发大流量数据包，终端设备可能通过不同的路径将上行数据包发送至数据网络(data network，DN)。
目前，DN侧会设置一个默认的互联网协议(internet protocol，IP)锚点PSA(PDU(protocol data unit，协议数据单元)session anchor，PDU会话锚点)UPF(user plane function，用户面功能)，数据网络在发送反馈数据包时，会将针对同一源地址的上行数据包的反馈数据发送至该IP锚点PSA UPF，从而有可能导致该IP锚点PSA UPF出现过载，进而导致大量数据包丢失。
发明内容
本申请提供一种数据传输方法及装置，用以提供一种减轻下行数据包导致UPF PSA过载的方案。
第一方面，本申请提供一种数据传输方法，该方法包括：第一用户面网元从会话管理网元接收第一指示信息；所述第一用户面网元根据所述第一指示信息，将数据网络DN发送给第一终端设备的下行数据流通过至少两个目标协议数据单元PDU会话锚点发送给所述第一终端设备；其中，所述至少两个目标PDU会话锚点分别向所述第一终端设备发送下行数据流中的部分数据流。
通过上述方法，第一用户面网元将第一终端设备的下行数据流发送到不同的PDU会话锚点中进行处理。示例性地，第一用户面网元可以称为DLCL(downlink classifier，下行分流)UPF，可以将第一终端设备的下行数据流通过至少两个目标PDU会话锚点发送给第一终端设备，可以理解为，该至少两个目标PDU会话锚点分别向第一终端设备发送全部或部分下行数据流中的部分数据流。以此通过至少两个PDU会话锚点共同分担下行业务负载，可以减轻下行大数据流可能造成的网络拥塞，并存在一种可能的情况，通过DLCL UPF的分流，使得各目标PDU会话锚点的负载均衡，保证该PDU会话处于一种较稳定的状态。
在一种可能的实现方法中，所述第一指示信息可以包含至少一个子指示信息，各子指示信息分别用于指示不同的下行数据流的标识信息与目标PDU会话锚点的对应关系；所 述第一用户面网元根据所述第一指示信息，将数据网络DN发送给第一终端设备的下行数据流通过至少两个目标PDU会话锚点发送给所述第一终端设备，包括：针对每个子指示信息，所述第一用户面网元将匹配该子指示信息包含的标识信息的下行数据流，发送至匹配该子指示信息包含的标识信息的下行数据流对应的所述目标PDU会话锚点。
通过上述方法，第一指示信息包含至少一个子指示信息，第一用户面网元根据各子指示信息指示的标识信息将匹配该标识信息的下行数据流发送至该子指示信息指示的PDU会话锚点，也就是，会话管理网元可以通过下发子指示信息灵活调整下行数据流其中的部分下行数据流，调整方式更加灵活。
在一种可能的实现方法中，所述标识信息可以包括下列中的一项或多项：源地址信息、目的地址信息、源端口标识、目的端口标识或协议类型等。
在一种可能的实现方法中，所述子指示信息还可以包括：所述第一用户面网元中用于发送所述下行数据流的IP地址，和/或所述目标PDU会话锚点中用于接收所述下行数据流的IP地址。
在一种可能的实现方法中，所述第一用户面网元还可以从所述移动会话管理网元接收第二指示信息；所述第一用户面网元根据所述第二指示信息，从至少一个第一PDU会话锚点接收所述第一终端设备发送至所述数据网络的上行数据流；其中，所述第一PDU会话锚点为能够向所述数据网络发送所述第一终端设备的上行数据流的网元上的PDU会话锚点中的其中一个。
通过上述方法，第一用户面网元可以根据第二指示信息从PDU会话锚点接收第一终端设备的上行数据流，可以实现不同PDU会话锚点的上行数据流汇聚到第一用户面，由第一用户面网元将上行数据流发送至数据网络。一种可能的场景，对于数据网络而言，仅需要从第一用户面接收上行数据流，不需要接入多个PDU会话锚点来接收上行数据流，简化了数据网络接收上行数据流的接收流程。
在一种可能的实现方法中，所述第一用户面网元在将所述上行数据流发送至所述数据网络之前，还可以生成第一下行路由信息，并将所述第一下行路由信息发送至所述数据网络；所述第一下行路由信息用于指示所述数据网络将发送至所述第一终端设备的下行数据流先发送至所述第一用户面网元，所述下行数据流的目的端为所述第一终端设备。
通过上述方法，第一用户面网元为数据网络提供了第一终端设备的下行数据流的路由信息，数据网络不需要再设置第一终端设备的IP锚点，数据网络侧可以将第一终端设备的下行数据流发送至第一用户面，减轻下行大数据流可能造成的网络拥塞。
第二方面，本申请提供一种数据传输方法，该方法包括：会话管理网元生成第一指示信息，所述第一指示信息用于指示第一用户面网元将数据网络DN发送给第一终端设备的下行数据流通过至少两个目标协议数据单元PDU会话锚点发送给终端设备；其中，所述至少两个目标PDU会话锚点分别向所述第一终端设备发送全部或部分下行数据流中的部分数据流所述会话管理网元向所述第一用户面网元发送所述第一指示信息。
通过上述方法，会话管理网元生成第一指示信息，该第一指示信息用于指示第一用户面网元将第一终端设备的全部或部分下行数据流通过至少两个目标PDU会话锚点发送至第一终端设备，通过至少两个PDU会话锚点共同分担下行业务负载，可以减轻下行大数据流可能造成的网络拥塞，并存在一种可能的情况，通过DLCL UPF的分流，使得各PSA UPF的负载均衡，保证该PDU会话处于一种较稳定的状态。
在一种可能的实现方法中，所述第一指示信息还可以包含至少一个子指示信息，各子指示信息分别用于指示不同的下行数据流的标识信息与目标PDU会话锚点的对应关系。
通过上述方法，第一指示信息包含至少一个子指示信息，各子指示信息分别用于指示不同的下行数据流的标识信息与目标PDU会话锚点的对应关系，会话管理网元可以以子指示信息为粒度灵活调整下行数据流其中的部分下行数据流，调整方式更加灵活。
在一种可能的实现方法中，所述标识信息可以但不限于包括下列中的一项或多项：源地址信息、目的地址信息、源端口标识、目的端口标识或协议类型。
在一种可能的实现方法中，所述子指示信息还可以包括：所述第一用户面网元中用于发送所述下行数据流的互联网协议IP地址，和/或所述目标PDU会话锚点中用于接收所述下行数据流的IP地址。
在一种可能的实现方法中，所述会话管理网元生成第一指示信息之前，还可以接收激活指示信息，所述激活指示信息用于指示所述会话管理网元激活所述第一用户面网元，或指示所述会话管理网元激活所述第一用户面网元和至少一个新的PDU会话锚点；其中，所述目标PDU会话锚点包含在所述至少一个新的PDU会话锚点中。
在一种可能的实现方法中，所述激活指示信息可以为至少一个第二PDU会话锚点或移动性管理网元在检测到数据流满足触发条件后发送给所述会话管理网元的；其中，所述触发条件可以包括：所述数据流的业务类型为预设业务类型；或所述数据流的传输速率不低于预设速率阈值。其中，所述数据流包括上行数据流和/或下行数据流，所述上行数据流为所述第一终端设备发送至所述数据网络的数据流；所述第二PDU会话锚点为能够向所述第一终端设备发送下行数据流的网元上的PDU会话锚点中不包含所述新的PDU会话锚点的其中一个。
通过上述方法，若当前PDU会话中的PDU会话锚点检测到满足触发条件时，该PDU会话锚点检测到接收到的数据流的数据量较大，例如，该数据流的流速较高，或该数据流为视频流，则为了避免该PDU会话锚点业务过载，可以向会话管理网元发送激活指示信息，用以指示会话管理网元激活至少一个新的PDU会话锚点，以为该PDU会话锚点分担数据业务，避免网络拥塞，保持PDU会话的稳定性。
在一种可能的实现方法中，所述会话管理网元还可以从所述第三PDU会话锚点接收释放指示信息，所述释放指示信息用于指示所述会话管理网元释放所述第三PDU会话锚点和/或所述第一用户面网元；其中，所述第三PDU会话锚点为能够向所述第一终端设备发送下行数据流的网元上的PDU会话锚点中的其中一个。
通过上述方法，当存在多个PDU会话锚点时，会话管理网元可以根据PDU会话锚点的业务负载状态，适当释放至少一个PDU会话锚点，示例性地，若当前PDU会话中传输的数据流较小时，例如，可以通过一个PDU会话锚点处理当前PDU会话中传输的全部数据流，或者其中的至少一个PDU会话锚点在预设时间内未接收到上行数据流和/或下行数据流时，则可以释放其他PDU会话锚点和/或第一用户面网元，简化数据流传输流程，避免占用过多资源导致资源利用率低等问题。
在一种可能的实现方法中，所述释放指示信息可以为所述至少一个第三PDU会话锚点在检测到满足释放条件后发送给所述会话管理网元的；所述释放条件可以包括：所述第三PDU会话锚点在预设时间内未接收到数据流，所述数据流可以包括上行数据流和/或下行数据流。
第三方面，本申请提供一种数据传输方法，该方法包括：目标协议数据单元PDU会话锚点从第一用户面网元接收所述数据网络发送给第一终端设备的下行数据流中的部分下行数据流；所述目标PDU会话锚点将接收的所述部分下行数据流发送给所述第一终端设备。
通过上述方法，通过目标PDU会话锚点将下行数据流发送至第一终端设备，具体的，可以是指由目标PDU会话锚点将下行数据流发送至RAN，再由RAN发送至第一终端设备。本申请实施例中可以全部下行数据流中的部分下行数据流。本申请通过至少两个PDU会话锚点共同分担下行业务负载，可以减轻下行大数据流可能造成的网络拥塞，并存在一种可能的情况，通过DLCL UPF的分流，使得各PSA UPF的负载均衡，保证该PDU会话处于一种较稳定的状态。
在一种可能的实现方法中，所述目标PDU会话锚点为所述会话管理网元在接收到激活指示信息后激活的至少一个新的PDU会话锚点中的其中一个。
在一种可能的实现方法中，所述目标PDU会话锚点还可以接收来自会话管理网元的第三指示信息；所述目标PDU会话锚点根据所述第三指示信息，从第二用户面网元接收到所述第一终端设备发送至所述数据网络的上行数据流中的部分上行数据流，并将所述部分上行数据流发送至所述第一用户面网元。
通过上述方法，目标PDU会话锚点接收来自第二用户面网元的上行数据，示例性地，第二用户面网元可以从接入网设备接收该终端设备发送至数据网络的上行数据流，并将该上行数据流通过至少两个PDU会话锚点发送至数据网络，每个PDU会话锚点接收到的上行数据流为全部上行数据流中的部分上行数据流，以降低其中一个PDU会话锚点上行业务过载的几率。
在一种可能的实现方法中，所述目标PDU会话锚点在检测到满足释放条件后，还可以向会话管理网元发送释放指示信息，所述释放指示信息用于指示所述会话管理网元释放所述目标PDU会话锚点和/或所述第一用户面网元；其中，所述释放条件可以包括：所述目标PDU会话锚点在预设时间内未接收到数据流，所述数据流可以包含上行数据流和/或下行数据流。
通过上述方法，当存在多个PDU会话锚点时，其中的至少一个PDU会话锚点在预设时间内未接收到上行数据流和/或下行数据流时，则可以向会话管理网元发送释放指示信息，用于指示会话管理网元释放至少一个PDU会话锚点和/或第一用户面网元，以简化数据流传输流程，避免占用过多资源导致资源利用率低等问题。
第四方面，本申请实施例提供一种通信装置，该装置具有实现第一方面所述的方法的功能，所述功能可以通过硬件实现，也可以通过软件实现，或者通过硬件执行相应的软件实现。所述装置包括一个或多个与上述功能相对应的模块，比如包括收发单元和处理单元。
在一个可能的设计中，该装置可以是芯片或者集成电路。
在一个可能的设计中，该装置包括存储器和处理器，存储器用于存储所述处理器执行的程序或指令，当程序或指令被处理器执行时，所述装置可以执行上述第一方面所述的方法。
在一个可能的设计中，该装置可以为DLCL UPF网元。
第五方面，本申请实施例提供一种通信装置，该装置具有实现第二方面所述的方法的功能，所述功能可以通过硬件实现，也可以通过软件实现，或者通过硬件执行相应的软件 实现。所述装置包括一个或多个与上述功能相对应的模块，比如包括收发单元和处理单元。
在一个可能的设计中，该装置可以是芯片或者集成电路。
在一个可能的设计中，该装置包括存储器和处理器，存储器用于存储所述处理器执行的程序或指令，当程序或指令被处理器执行时，所述装置可以执行上述第二方面所述的方法。
在一个可能的设计中，该装置可以为会话管理网元(Session Management Function，SMF)网元。
第六方面，本申请实施例提供一种通信装置，该装置具有实现第三方面所述的方法的功能，所述功能可以通过硬件实现，也可以通过软件实现，或者通过硬件执行相应的软件实现。所述装置包括一个或多个与上述功能相对应的模块，比如包括收发单元和处理单元。
在一个可能的设计中，该装置可以是芯片或者集成电路。
在一个可能的设计中，该装置包括存储器和处理器，存储器用于存储所述处理器执行的程序或指令，当程序或指令被处理器执行时，所述装置可以执行上述第三方面所述的方法。
在一个可能的设计中，该装置可以为PDU会话锚点功能实体。
第七方面，本申请实施例提供了一种系统，所述系统包括第四方面所述的通信装置、第五方面所述的通信装置和第六方面所述的通信装置。
第八方面，本申请实施例提供一种通信装置，所述通信装置包括处理器、存储器和通信接口，所述通信接口，用于接收信号或者发送信号；所述存储器，用于存储程序或指令代码；所述处理器，用于从所述存储器调用所述程序或指令代码以执行如第一方面所述的方法或第二方面所述的方法或第三方面所述的方法。
第九方面，本申请实施例提供一种通信装置，所述通信装置包括处理器和接口电路，所述接口电路，用于接收程序或指令代码并传输至所述处理器；所述处理器运行所述程序或指令代码以执行如第一方面所述的方法或第二方面所述的方法或第三方面所述的方法。
第十方面，本申请实施例提供一种计算机可读存储介质，所述计算机可读存储介质用于存储程序或指令，当所述程序或指令被执行时，使得第一方面所述的方法或第二方面所述的方法或第三方面所述的方法被实现。
第十一方面，本申请实施例提供一种包括指令的计算机程序产品，当所述指令被执行时，使得第一方面所述的方法或第二方面所述的方法或第三方面所述的方法被实现。
附图说明
图1为本申请实施例提供的一应用场景示意图；
图2～图3为本申请实施例提供的网络架构示意图；
图4为本申请实施例提供的一种数据传输方法的流程示意图；
图5～图7为本申请实施例提供的下行数据传输的场景示意图；
图8为本申请实施例提供的另一种数据传输方法的流程示意图；
图9为本申请实施例提供的上行数据传输的场景示意图；
图10～图11为本申请实施例提供的网络配置的流程示意图；
图12为本申请实施例提供的一种释放网元的流程示意图；
图13-图18为本申请实施例提供的通信装置结构示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。方法实施例中的具体操作方法也可以应用于设备实施例或系统实施例中，也就是说，本申请中方法实施例和装置实施例、设备实施例以及系统实施例可以相互引见和参照，重复之处不再予以详尽描述。如图1所示，为一种5G网络架构。下面对架构包括的部分网元及各网元的功能分别简单介绍。
1)终端设备，又称之为用户设备(user equipment，UE)、终端(Terminal)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等，可以是一种具有无线收发功能的设备。终端设备可以简称为终端，其可以部署在陆地上，包括室内、室外、和/或手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。终端设备可以是用户设备(user equipment，UE)，UE包括具有无线通信功能的手持式设备、车载设备、可穿戴设备或计算设备。示例性地，UE可以是手机(mobile phone)、平板电脑或带无线收发功能的电脑。终端设备还可以是虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制中的无线终端、无人驾驶中的无线终端、远程医疗中的无线终端、智能电网中的无线终端、智慧城市(smart city)中的无线终端、和/或智慧家庭(smart home)中的无线终端等等。
本申请实施例中，用于实现终端设备的功能的装置可以是终端设备，也可以是能够支持终端设备实现该功能的装置，例如芯片系统，该装置可以被安装在终端设备中。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。本申请实施例提供的技术方案中，以用于实现终端的功能的装置是终端设备为例，描述本申请实施例提供的技术方案。
2)接入网设备，可以是将终端设备接入到无线网络的无线接入网(radio access network，RAN)节点。目前，一些RAN节点的举例为：下一代基站(next generation NodeB，gNB)、传输接收点(transmission reception point，TRP)、演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station,BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(base band unit，BBU)，或无线保真(wireless fidelity，WiFi)接入点(access point，AP)等。其中，基站可能有多种形式，比如宏基站、微基站、中继站和接入点等。本申请实施例涉及到的基站可以是5G系统中的基站或LTE系统中的基站，或未来的通信系统中未来的第六代(6th generation，6G)基站。其中，5G系统中的基站还可以称为发送接收点(transmission reception point，TRP)或下一代节点B(generation Node B，gNB或gNodeB)。
本申请实施例中，用于实现接入网设备的功能的装置可以是接入网设备，也可以是能够支持接入网设备实现该功能的装置，例如芯片系统，该装置可以被安装在接入网设备中。在本申请实施例提供的技术方案中，以用于实现接入网设备的功能的装置是接入网设备为例，描述本申请实施例提供的技术方案。
3)接入与移动性管理功能(access and mobility management function，AMF)网元：属于核心网网元，主要负责信令处理部分，例如：接入控制、移动性管理、注册与去注册等功能。AMF网元为UE中的会话提供服务的情况下，会为该会话提供控制面的存储资源，以存储会话标识、与会话标识关联的SMF网元标识等。
4)会话管理(session management function，SMF)网元：负责用户面网元选择，用户面网元重定向，网络之间互连的协议(Internet Protocol，IP)地址分配，会话的建立、修改和释放以及服务质量(quality of service,QoS)控制。
5)用户面功能(user plane function，UPF)网元：负责终端设备的用户数据的转发和接收。可以从数据网络(data network，DN)接收用户数据，通过接入网设备传输给终端设备；UPF网元还可以通过接入网设备从终端设备接收用户数据，转发到数据网络。UPF网元中为终端设备提供服务的传输资源和调度功能由SMF网元管理控制的。
其中，UPF上可以部署不同的功能实体，例如，ULCL(uplink classifier，上行分流)、PSA(PDU(protocol data unit，协议数据单元)session anchor，PDU会话锚点)或DLCL(downlink classifier，下行分流)，为方便下文描述，若ULCL功能实体部署于UPF上，则可以简称ULCL UPF，若PSA功能实体部署于UPF上，则可以简称为PSA UPF，若DLCL功能实体部署于UPF上，则可以简称为DLCL UPF。
应理解，图1仅为示意，上述UE、RAN·、UPF和DN均可能为多个(图1中未示出)。其中，UE与AMF网元之间的接口称为N1接口，AMF网元与RAN设备之间的接口称为N2接口，RAN设备与UPF网元之间的接口可以称为N3接口，SMF网元与UPF网元之间的接口称为N4接口，UPF网元与DN之间的接口称为N6接口，不同UPF网元之间的接口称为N9接口。
在图1的网络架构中，UPF还可以是UE的PDU会话锚点用户面网元(PSA UPF)。PSA UPF用于对接收到的数据流进行处理，例如，会话管理、分组路由和转发、合法监听、计费、QoS以及对接收到的数据流包含的数据报文进行深度报文解析(deep packet inspection，DPI)。在图1的场景中，PSA UPF1为该终端设备的IP锚点，即PSA UPF1负责接收并处理该终端设备发送至数据网络的所有上行数据流，以及该数据网络发送至该终端设备的所有下行数据流。
作为一种示例，在图1的网络架构下，下行数据流传输的实现过程如下：
数据网络通过N6接口将发送给该终端设备的全部下行数据流发送至该终端设备的PSA UPF1，PSA UPF1需要对下行数据流包含的任一数据报文进行处理，并将处理后的数据报文通过N3接口发送至接入网设备，该接入网设备则负责将数据报文转送至该终端设备。
一种可能的场景为，数据网络发送的下行数据流较大时，例如当某一条下行数据流突发的吞吐量叠加其他数据流时，可能会超出PSA UPF1的处理上限，导致PSA UPF1业务过载，造成网络拥塞，从而造成下行数据流丢包。
另一种可能的场景为，由于终端设备的移动，导致PSA UPF1无法覆盖到该终端设备，需要通过ULCL UPF将该终端设备在PSA UPF1上的上行数据流迁移至属于该终端设备的PDU会话上的其他PSA UPF上。也就是说，在该场景下的网络架构中，存在至少两个PSA UPF，用于调整上行数据流的传输。在存在多个PSA UPF的网络架构中，数据网络DN会设置该终端设备的一个IP锚点，也就是，即使该终端设备与同一数据网络的PDU会话中存在多个用于接入数据网络的PSA UPF，但在数据网络侧，该多个PSA UPF中只有一个是该终端设备的IP锚点，例如IP锚点为PSA UPF1，这样，数据网络会将发送给该终端设备的全部下行数据流发送至PSA UPF1上，同样若DN发送的下行数据流较大时，可能导致PSF UPF1的下行数据流业务过载，出现下行数据丢包等问题。
为了避免下行数据流过大造成的网络拥塞，如何进行下行数据流的传输是亟待解决的问题。鉴于此，本申请实施例提供了一种数据传输方法，例如，可以通过激活至少一个新的PSA UPF和DLCL UPF，通过DLCL UPF将发送给一个终端设备的全部或部分下行数据流通过至少两个PSA UPF发送至该终端设备，每个PSA UPF用于处理全部或部分下行数据流中的部分下行数据流，也可以理解为，通过该至少一个新的PSA UPF分担对原PSA UPF(如图1中的PSA UPF1)的业务负载。由于DLCL UPF不需要对数据报文进行处理，主要负责对下行数据流进行分发，因此不会引起数据流在DLCL UPF处过载，并且通过多个PSA UPF共同分担下行业务负载，可以减轻下行大数据流可能造成的网络拥塞，并存在一种可能的情况，通过DLCL UPF的分流，使得各PSA UPF的负载均衡，保证该PDU会话处于一种较稳定的状态。
下面将详细对本申请实施例的具体实现过程进行描述，其中，在本申请的描述中，除非另有说明，“多个”的含义是两个或两个以上。在本申请实施例中，“示例的”一词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。可选地，本申请实施例提及“第一”、“第二”等序数词可以用于对多个对象进行区分，不用于限定多个对象的顺序、时序、优先级或者重要程度。例如，第一信息和第二信息，只是为了区分不同的信令，而并不是表示这两种信息的内容、优先级、发送顺序或者重要程度等的不同。
本申请实施例中，通信设备间的无线通信可以包括：网络设备和终端设备间的无线通信、终端设备和终端设备间的无线通信等。其中，在本申请实施例中，术语“无线通信”还可以简称为“通信”，术语“通信”还可以描述为“数据传输”、“信息传输”、“信号传输”或“传输”。传输可以包括发送和/或接收。例如，网络设备和终端设备间的传输包括：网络设备向终端设备发送下行信号，即终端设备从网络设备接收下行信号；和/或，终端设备向网络设备发送上行信号，即网络设备从终端设备接收上行信号。
本申请实施例中以网络设备和终端设备之间的通信为例进行描述，本领域技术人员可以将本申请实施例提供的技术方案用于进行其它调度实体和从属实体间的无线通信，例如用于宏基站和微基站之间的无线通信，例如用于第一终端设备和第二终端设备间的无线通信，本申请实施例不做限制。
如图2所示，为本申请实施例所适用的一种网络架构示意图，该网络架构在图1的基础上，增加了DLCL UPF和至少一个新的PSA UPF，例如将新的PSA UPF称为PSA UPF2。
DLCL UPF，可以称之为下行数据分流用户面网元，主要负责从数据网络接收下行数据流，并将该下行数据流发送至该下行数据流对应的PSA UPF，或者将该下行数据流分流成不同的子数据流，并将不同的子数据流分发给不同的PSA UPF。具体的，DLCL UPF可以根据SMF下发的第一指示信息确定下行数据流对应的PSA UPF，或者确定将该下行数据流分流成不同的子数据流，并将不同的子数据流分发给哪些PSA UPF。
SMF，主要负责PDU会话的建立、修改、释放，管理无线网络侧和UPF之间的传输隧道。在本申请中主要利用其会话管理功能，选择和控制UPF，配置UPF的流量定向，将数据流转发至合适的目的端。具体的，在本申请实施例中还用于生成第一指示信息，该第一指示信息用于指示DLCL UPF将发送给一个终端设备的全部或部分下行数据流通过至少两个PSA UPF发送至终端设备，并且每个PSA UPF接收到的下行数据流为全部下行数据 流中的部分，以降低其中一个PSA UPF业务过载的几率。
PSA UPF2和PSA UPF1，为该终端设备与该数据网络建立的PDU会话上的至少两个PSA UPF，分别用于接收数据网络发送至终端设备的下行数据流中的部分下行数据流，并对接收到的下行数据流中的数据报文进行处理，以及将处理后的数据报文发送给终端设备。
如图3所示，为本申请实施例所适用的另一种网络架构示意图，与图2的网络架构相比，其主要区别在于：在图2的基础上，新增了ULCL UPF，也就是图3所示的网络架构支持ULCL UPF，即支持插入ULCL UPF。
ULCL UPF，是上行数据分流用户面网元，一方面，如前所述，ULCL UPF可负责将由于终端设备的移动，导致原PSA UPF不能覆盖到该终端设备时，将该终端设备在原PSA UPF上的上行数据流迁移至其他PSA UPF上。另一方面，本申请实施例提还提供了一种基于ULCL UPF进行上行数据流传输的方法，可应用于图3所示的网络架构中，也可以应用于图3中不包括DLCL UPF的网络架构中，本申请实施例对此不作限定。图3中，ULCL UPF可以从接入网设备接收该终端设备发送至数据网络DN的全部上行数据流，并将全部上行数据流通过至少两个PSA UPF发送至数据网络DN，并且每个PSA UPF接收到的上行数据流为全部上行数据流中的部分上行数据流，以降低其中一个PSA UPF上行业务过载的几率。也就是，在本申请实施例中，ULCL UPF还可以用于对上行数据流进行分流。
SMF，除上文所述的用于配置下行数据流的路由方式外，还可以配置上行数据流的路由方式，配置上行数据流的路由方式可以参见上述配置下行数据流的路由方式的描述，此处不再重复说明。
应理解的是，上述图2和图3仅为示意，图2和图3中仅示出插入了一个PSA UPF2，实际上，还可以插入多个PSA UPF，本申请实施例对此不作限定。
本申请实施例中，ULCL功能实体、PSA功能实体或DLCL功能实体中的部分或全部可以部署于同一UPF上，也可以部署于不同UPF上。即ULCL UPF、PSA UPF或DLCL UPF中的部分或全部可以位于同一UPF中。若部署于同一UPF上，则可称为合一部署，若部署于不同UPF上，则可以称为分离部署，需要说明的是，图2和图3均为分离部署的网络架构示意图。
本申请中的移动性管理网元、会话管理网元、PDU会话锚点(PSA)、第一用户面网元、第二用户面网元可以分别是图2或图3所示的AMF网元、SMF网元、PSA UPF网元上的PSA功能实体、DLCL UPF、ULCL UPF(图2中未示出)。也可以是未来通信系统中的具有上述AMF网元、SMF网元、PSA UPF网元上的PSA功能实体、DLCL UPF网元、ULCL UPF的功能的网元。
为方便说明，本申请后续以移动性管理网元、会话管理网元、PDU会话锚点用户面网元、第一用户面网元、第二用户面网元可以分别为图3中的AMF网元、SMF网元、PSA UPF网元、DLCL UPF网元、ULCL UPF网元为例进行说明。进一步地，将AMF网元简称为AMF，将SMF网元简称为SMF，将PSA UPF网元简称为PSA UPF，将DLCL UPF网元简称为DLCL UPF，将ULCL UPF网元简称为ULCL UPF以及将终端设备称为UE，将接入网设备简称为RAN，即本申请后续所描述的AMF均可替换为移动性管理网元，SMF均可替换为会话管理网元，各PSA UPF均可替换为各UPF上的PDU会话锚点，DLCL UPF均可替换为第一用户面网元，UE均可替换为终端设备，RAN均可以替换为接入网设备。
接下来以分离部署，以及一个DN与一个UE之间的数据流为例，介绍本申请技术方 案。
如图4所示，为本申请实施例提供的一种数据传输方法，该方法可以应用于如图2或图3所示的网络架构中，该方法包括如下步骤：
步骤S400，SMF生成第一指示信息；
示例性地，SMF为DLCL UPF生成用于指示下行数据流对应的目标PSA UPF的第一指示信息。具体的，该第一指示信息用于指示下行数据流与目标PSA UPF的对应关系。下文将会进行详细说明。
步骤S401，DLCL UPF从SMF接收第一指示信息；
该第一指示信息用于指示DLCL UPF将DN发送至UE的下行数据流通过至少两个PSA UPF发送至UE。例如，在图2或图3的网络架构中，DLCL UPF将该全部下行数据流通过PSA UPF1和PSA UPF2发送至UE，其中，PSA UPF1和PSA UPF2接收到的下行数据流分别为全部下行数据流中的部分、且PSA UPF1和PSA UPF2接收到的下行数据流不相同。具体的，可以是指由至少两个PSA UPF分别将接收到的不同下行数据流发送至RAN，再由RAN发送至UE。一种可选的场景，在不超过其中一个PSA UPF的业务负载时，也可以将要发送给一个UE的全部下行数据流均发送至同一PSA UPF上处理。
步骤S402，DLCL UPF根据第一指示信息，将下行数据通过至少两个PSA UPF发送出去，其中，下行数据流的目的端为接收端UE。
应理解的是，步骤S402仅为示意，并非指DLCL UPF同时向至少两个PSA UPF发送下行数据流，也并非指至少两个PSA UPF同时向RAN发送下行数据流，本申请实施例对此不作限定。
步骤S403，各PSA UPF分别将各自接收到的部分下行数据流发送至RAN。
可选的，若应用于图3所示的网络架构时，各PSA UPF还可以将各自接收到的部分下行数据流发送至ULCL UPF，由ULCL UPF发送至RAN，再由RAN将下行数据流发送给UE。
应理解的是，步骤S403仅为示意，并非指RAN同从各PSA UPF接收下行数据流，也并非指至少两个PSA UPF同时向RAN发送下行数据流，本申请实施例对此不作限定。
步骤S404，RAN将从各PSA UPF接收的下行数据流发送至UE。
应理解的是，步骤S404仅为示意，用于指示RAN在接收到下行数据流后，将该下行数据流发送至UE，并非指UE从RAN同时接收到PSA UPF下发的各下行数据流，也并非指RAN在接收到各PSA UPF下发的下行数据流后再向UE发送下行数据流，本申请实施例对此不作限定。
接下来通过具体示例对上述图4的方式进行详细说明。
首先对本申请实施例中的术语“数据流”进行介绍。本申请实施例中的数据流包括上行数据流和下行数据流。如前所述，上行数据流为UE发送至数据网络DN的，具体的，可以是发送至DN侧包含的至少一个服务设备(server)，即上行数据流的目的端为DN下的至少一个服务设备。下行数据流为数据网络DN侧发送给该UE的，即下行数据流的目的端为该UE。
其中，数据流中包含至少一个数据报文，示例性的，该数据报文可以是GTP报文。该数据报文可以包括源IP地址和目的IP地址，源IP地址为发送该数据报文的终端设备的IP地址，目的IP地址为该数据报文的目的端IP地址，即数据网络DN中包含的某server的 IP地址。按照不同的划分方式，可以将数据划分为不同的数据流，不同的数据流可以具有不同的标识信息，该标识信息可以是源IP地址、目的IP地址、源端口号、目的端口号、协议类型信息中的一项或多项。上述源IP地址、目的IP地址、源端口号、目的端口号和协议类型信息也可以称为数据流五元组。
作为一种示例，如图5所示，为图4所示的方法应用于在图2所示的网络架构中下行数据流的传输流程示意图。该流程可以包括：
步骤1，数据网络DN将要发送给一个接收端UE的下行数据流发送至DLCL UPF。
步骤2，DLCL UPF根据从SMF接收到的第一指示信息，将下行数据流发送至该下行数据流对应的至少两个PSA UPF。
具体的，DLCL UPF通过N9接口将下行数据流发送至该下行数据流对应的目标PSA UPF(图5中目标PSA UPF分别为PSA UPF1和PSA UPF2)。本文中的目标PSA UPF是指PDR表项中指示的匹配该PDR表项的标识信息的数据流对应的PSA UPF。因此，本文中“数据流的目标PSA UPF”与“数据流对应的PSA UPF”可以混用，下文不再重复说明。
假设在此过程之前，DLCL UPF已获得SMF下发的第一指示信息。示例性的，该第一指示信息可以是包检测规则(Packet Detection Rule，PDR)，DLCL UPF将接收到的下行数据流与PDR进行匹配，将匹配PDR的下行数据流(通过DLCL UPF中与各PSA PDU对应的N9接口)发送至该下行数据流对应的PSA PDU。下文将会对获取PDR的流程进行详细说明。
示例性的，该PDR包含至少一个PDR表项，每个PDR表项分别用于指示不同的数据流，以及该数据流的传输方式。如下表1所示，为本申请实施例提供的一个PDR表项的具体示例。
表1
Figure PCTCN2020122495-appb-000001
SDF filter(过滤器)，用于匹配符合该标识信息的数据报文，如前所述，标识信息可以是数据流五元组中的部分或全部。
Local IP，用于指示DLCL UPF将匹配SDF filter(指示的标识信息)的数据报文发送出去的接口的IP地址。
示例性地，对于下行数据流，DLCL UPF可能具有多个用于发送下行数据流的N9接口，该多个N9接口与多个PSA UPF对应，例如，DLCL UPF具有两个N9接口，该两个N9接口与不同的PSA UPF一一对应，即ULCL UPF可以通过多个N9接口并行发送属于不同PSA UPF的数据流。
再示例性地，对于下行数据流，DLCL UPF可能仅具有一个用于发送下行数据流的N9接口，该一个N9接口与多个PSA UPF对应，即DLCL UPF通过同一个N9接口将不同的下行数据流发送至不同PSA UPF。显然，在该示例下，由于DLCL UPF仅有一个用于发送下行数据流的N9接口，因此表1所示PDR表项可以不指示DLCL UPF的Local IP。
Outer ip，用于指示该数据报文的下一跳(IP地址)。
上述表1可以解读为：表1所示的PDR表项用于指示DLCL UPF将匹配SDF filter的数据报文，通过N9接口发送至PSA UPF1。其中，不同的PDR表项中的SDF filter指示的 标识信息应不同，用于指示不同的数据流。
下面举例来说，如图5所示，假设DN发送至UE的两条下行数据流包括数据流1和数据流2。SMF为该两条上行数据流配置路由方式，以生成第一PDR表项和第二PDR表项。如下表2所示，为第一PDR表征的一具体示例，表3为第二PDR表项的一具体示例。
表2
Figure PCTCN2020122495-appb-000002
表3
Figure PCTCN2020122495-appb-000003
假设DLCL UPF与PSA UPF的接口一一对应，DLCL UPF上与PSA UPF1对应的为第一N9接口，DLCL UPF与PSA UPF2对应的为第二N9接口。
其中，第一PDR表项(表2)用于指示DLCL UPF将数据流1发送至PSA UPF1，具体的，还可以指示DLCL UPF发送该数据流1的IP地址，以及该数据流1的下一跳，即接收该数据流1的PSA UPF1的IP地址。同样的，第二PDR表项用于指示DLCL UPF将数据流2发送至PSA UPF2，具体的，还可以指示DLCL UPF发送该数据流2的IP地址，以及该数据流2的下一跳，即接收该数据流2的PSA UPF2的IP地址。
对应的，DLCL UPF接收到数据流1后，根据第一PDR表项将数据流1发送至PSA UPF1，发送端口为与PSA UPF1对应的第一N9接口。同样的，ULCL UPF接收到数据流2后，根据第二PDR表项将数据流2发送至PSA UPF2，发送端口为与PSA UPF2对应的第二N9接口。
应理解的是，ULCL UPF根据PDR表项中的标识信息确定该数据流是数据流1还是数据流1。例如，第一PDR表项中的标识信息为源IP地址为10.10.0.1，目的IP地址为192.168.0.1，DLCL UPF在检测数据流1时，确定数据流1中包含的源IP地址也是10.10.0.1，目的IP地址为192.168.0.1，则确定数据流1匹配第一PDR表项。又例如，第二PDR表项中的标识信息为源IP地址为10.10.0.1，目的IP地址为192.168.0.2，(其中，192.168.0.1和192.168.0.1均为DN侧包含的节点的IP地址)，DLCL UPF在检测数据流2时，确定数据流2中包含的源IP地址也是10.10.0.1，目的IP地址为192.168.0.2，则确定数据流2匹配第二PDR表项。
可选的，上述PDR表项仅为示意，其中的IP地址也可以通过个网元、节点、设备的其他地址如MAC地址来标识，并且本申请实施例应用的PDR表项可以是上述表1中的部分项或在上表1的基础上增加其他项信息后的PDR表项，例如，可以增加的其他项包括，用于表征该PDR表项指示的为下行数据流或上行数据流的标识，对该数据报文的操作方式等信息，本申请实施例对此并不限定。
上述以DLCL UPF为例，对UPF之间转发数据的方式进行了介绍，一种可选的情况，任一UPF，包括ULCL UPF和PSA UPF都可以基于PDR来接收和发送数据报文，不同的是，针对同一条数据流，不同UPF对该数据流的PDR表项是不同的，或不完全相同。例如，DLCL UPF中的PDR表项指示该数据流的下一跳(PSA UPF)，而PSA UPF中的PDR 表项指示该数据流的下一跳为(RAN或其他UPF)，如何根据PDR表项进行数据报文的传输可以参见上述对DLCL UPF根据PDR表项进行数据传输的描述，此处以及下文将不再详细说明。
上述介绍了包检测规则，如下介绍SMF配置以及发送包检测规则的过程。
SMF根据DN发送至UE的全部下行数据流中包含的不同的下行数据流的标识信息，生成该下行数据流的PDR表项，该PDR表项用于指示指定标识信息的下行数据流与PSA UPF的对应关系，以指示DLCL UPF将匹配PDR表项中的指定标识信息的下行数据流发送至该下行数据流对应的PSA UPF。
一种可选的方式，SMF可以以PDR表项的粒度下发子指示信息，即子指示信息为PDR表项。SMF可以通过更新PDR表项灵活调整某一条下行数据流对应的PSA UPF，能够及时调整PSA UPF上的业务负载，避免PSA UPF业务过载。
举例来说，以图2所示的网络架构为例，若PSA UPF1检测到正在接收的数据流1为大数据流，则PSA UPF1向SMF发送指示信息，该指示信息还可以携带该数据流1的标识信息，用于指示SMF重新配置数据流1的PDR表项，例如，重新配置的PDR表项用于指示DLCL UPF将数据流1发送至PSA UPF2。
可选的，PSA UPF1可以在当前正在接收的数据流1处理完成后再发送指示信息。应理解的是，同一条数据流包含相同的标识信息，但可以是在不同时间发送的，同一条的数据流并不与数据流包含的数据和/或时间为粒度划分。例如，PSA UPF1在10:00接收到数据流1，还可能在间隔一段时间，例如10:30再次接收数据流1，因此，为了避免PSA UPF1持续接收到较大的数据流(如数据流1)则可以适时指示SMF将后续的数据流1发送至其他PSA UPF上处理。
其中，SMF可以根据如下原则配置PDR表项：
示例性地，该配置原则可以是，各PSA UPF负责接收和/或处理全部下行数据流中的部分下行数据流，同一PSA UPF接收到的数据未重叠，即同一下行数据流只发送给一个PSA UPF。
再示例性地，该配置原则还可以是，各PSA UPF负责接收和/或处理全部下行数据流中的部分下行数据流，同一PSA UPF接收到的数据可以重叠，例如，同一下行数据流可以发送给多个PSA UPF，或将同一下行数据流中的部分数据报文发送给不同的PSA UPF。在该示例中，将同一数据流中的部分或全部数据报文发送给至少两个PSA UPF，该两个PSA UPF将该同一数据流中的部分或全部数据报文发送下一网元、节点或设备，例如，在图2的网络架构中，PSA UPF1和PSA UPF2可以将相同的部分或全部数据报文发送至RAN，在图3的网络架构中，PSA UPF1和PSA UPF2可以将相同的部分或全部数据报文发送至ULCL UPF。对于由该下一网元、节点或设备而言，可以通过多条路径接收该相同的数据报文，以提高数据传输的可靠度。可选的，该下一网元、节点或设备还可以对相同的部分或全部数据报文进行合并、联合译码等数据处理，本申请实施例对此不作限定。
步骤3，各PSA UPF将自身接收到的下行数据流发送至RAN；
具体的，PSA UPF1和PSA UPF2对各自接收到的下行数据流进行处理，并将处理后的下行数据流通过N3接口将发送至RAN。
应理解的是，PSA UPF1和PSA UPF2内也配置有包检测规则，该包检测规则用于指示各PSA UPF接收到的数据流的路由方式。示例性地，由于PSA PDR接收到的数据流不 同，因此每个PSA UPF的PDR规则可能也有所不同。例如，PSA UPF1的PDR表项用于指示PSA UPF1将数据流1发送至RAN，PSA UPF2内的PDR表项用于指示PSA UPF2将数据流2发送至RAN。
步骤4，RAN将接收到的下行数据流发送至UE。
需要说明的是，步骤2和步骤3仅为示意，步骤2并非指示DLCL UPF同时向PSA UPF1和PSA UPF2发送下行数据流。步骤3并非指示PSA UPF1和PSA UPF2同时向RAN发送各自接收到的下行数据流。本申请实施例对可以并行传输的数据的收发顺序此不作限定。
上述介绍了图4所示方式应用于图2所示网络架构的一种下行数据流传输的具体方法流程，接下来当图4所示方式介绍应用于图3所示网络架构下另一种下行数据流传输的具体方法流程。
作为另一种示例，如图6所示，为图4所示的方法应用于在图3所示的网络架构中下行数据流的传输流程示意图。该流程可以包括：
步骤a，数据网络DN将要发送给一个UE的下行数据流发送至DLCL UPF。
步骤b，DLCL UPF根据从SMF获得的第一指示信息，将下行数据流发送至该下行数据流对应的至少两个PSA UPF。
如前所示，该第一指示信息可以为PDR，子指示信息为该PDR中的至少一个PDR表项。具体的，DLCL UPF根据第一指示将下行数据流发送至该下行数据流对应的PSA UPF的方式可以参见上述实施例中步骤2的相关描述，此处不再重复说明。
在图3的场景下，假设第一指示信息中包含部分子指示信息，用于指示发送至PSA UPF1的部分下行数据流，其余的部分子指示信息，用于指示发送至PSA UPF2的部分下行数据流。也就是，PSA UPF1和PSA UPF2接收的下行数据流为全部下行数据流中的部分、且PSA UPF1和PSA UPF2接收的下行数据流不相同。
步骤c，PSA UPF1和PSA UPF2将各自接收到下行数据流发送至ULCL UPF。
具体的，PSA UPF1和PSA UPF2对各自接收到的下行数据流进行处理，并将处理后的下行数据流通过N9接口将发送至ULCL UPF。如图7所示，下行数据流经由DLCL UPF分发后，再汇聚到ULCL UPF后，ULCL UPF将下行数据流发送出去。其中，图7中PSA UPF3等仅为示意，在图3的场景下，仅包含PSA UPF1和PSA UPF2。
示例性地，PSA UPF1和PSA UPF2基于各自的PDR表现发送各自的下行数据流。PSA UPF1和PSA UPF2如何根据PDR表项发送下行数据流的方式请参见上文的相关描述，此处不再赘述。
步骤d，ULCL UPF通过N3接口将接收到的下行数据流发送至RAN。
示例性地，ULCL UPF基于自身的包检测规则将下行数据流发送至RAN。如下表4所示，为ULCL UPF中的PDR表项的具体示意。
表4
Figure PCTCN2020122495-appb-000004
步骤15，RAN将接收到的下行数据流发送至UE。
上述仅为流程举例，对于步骤c～步骤e，另一种可选的方式为，PSA UPF1和/或PSA UPF2将各自接收到下行数据流发送至RAN，由RAN转发给UE，即不由ULCL UPF进行 转发。
需要说明的是，步骤b和步骤c仅为示意，步骤b并非指示DLCL UPF同时向PSA UPF1和PSA UPF2发送下行数据流。步骤c并非指示PSA UPF1和PSA UPF2同时向ULCL UPF发送各自接收到的下行数据流。本申请实施例对此不作限定。
上述为通过DLCL UPF对下行数据流进行分流传输的方法流程介绍，对于图3所示的网络架构，本申请还提供一种上行数据流的传输方法，如图8所示，为本申请实施例提供的一种数据传输方法流程示意图。该方法可以包括如下步骤：
步骤S800，UE将上行数据流发送至RAN；
步骤S801，RAN将从终端设备处接收到的上行数据流发送至ULCL UPF；
步骤S802，ULCL UPF从RAN接收上行数据流。
步骤S803，ULCL UPF根据第二指示信息，将接收到的上行数据发送至该上行数据流对应的PSA UPF。
在此过程之前，假设ULCL UPF已获取到第二指示信息，获取方式可以是从SMF处获取。示例性的，该二指示信息可以是该UE的上行数据流的包检测规则。该第二指示信息用于指示ULCL UPF将UE发送至DN的全部上行数据流通过至少两个PSA UPF发送至DN。可以理解为，每个PSA UPF接收到的上行数据流为全部上行数据流中的部分上行数据流，避免其中一个PSA UPF上行业务过载造成网络拥塞。具体的，ULCL UPF基于该PDR将接收到的上行数据流与PDR表项进行匹配，将匹配PDR的上行数据流(通过ULCL UPF中与各PSA PDU对应的N9接口)发送至该上行数据流对应的PSA PDU。对于用于指示上行数据流传输方式的PDR以及如何根据该PDR进行数据传输的方式，可以参见上述对用于指示下行数据流的第一指示信息的相关描述，此处不再重复说明。
如下表5所示，为本申请实施例提供的第二指示信息包含的PDR表项的一具体示例。
表5
Figure PCTCN2020122495-appb-000005
步骤S804，PSA UPF1和PSA UPF2从ULCL UPF接收上行数据流，并将各自接收到上行数据流发送至DLCL UPF；
具体的，PSA UPF1和PSA UPF2对各自接收到的上行数据流进行处理，并将处理后的上行数据流通过N9接口将发送至DLCL UPF。如图9所示，上行数据流经由ULCL UPF分发后，再汇聚到DLCL UPF后，DLCL UPF将上行数据流发送出去。其中，图9中PSA UPF3等仅为示意，在图3的场景下，仅包含PSA UPF1和PSA UPF2。
步骤S805，DLCL UPF将从各PSA UPF接收到的上行数据流发送至数据网络DN。
上述仅为流程举例，对于步骤S804～步骤S805的另一种可选的方式为，PSA UPF1和/或PSA UPF2将各自接收到上行数据流发送至数据网络DN。
需要说明的是，步骤S804仅为示意，步骤S804并非指示PSA UPF1和PSA UPF2同时向DLCL UPF发送各自接收到的上行数据流。本申请实施例对此不作限定。
上述图2或图3所示的网络架构，可以是实体设备组成的实体网络，也可以是虚拟网元组成的虚拟网络，例如，AMF、SMF、ULCL UPF、DLCL UPF或PSA UPF可以为至少一台虚拟机上的功能网元。
如果是实体网络，则ULCL UPF实体、DLCL UPF实体或PSA UPF实体可以在组网时已搭建，在使用中，根据业务需求切换不同的状态，例如，激活态和非激活态。
下面举例来说，在图3所示的实体网络中，ULCL UPF实体和PSA UPF2实体的状态可以是未激活态，实际的工作的网元等同于图1所示的网络架构，PSA UPF1负责处理该终端设备的全部上行数据流和全部下行数据流，若PSA UPF1检测到吞吐量较大的上行数据流时，即产生需要通过ULCL UPF进行上行数据流分流的业务需求时，可以通过SMF触发ULCL UPF和PSA UPF2从非激活态切换为激活态。相似的，若PSA UPF1检测到吞吐量较大的下行数据流时，即产生需要通过DLCL UPF进行下行数据流分流的业务需求时，可以通过SMF触发DLCL UPF和PSA UPF2从非激活态切换为激活态，应理解的，若当前网络中已激活PSA UPF2，则无须重复激活，上述方式实现了适应于业务需求的实体网络的灵活配置。
其中，激活态可以是该实体处于启动(或者说上电)的状态，或该实体的功能生效的状态。非激活态则可以是该实体处于停止(或者说失电)的状态，或者该实体的功能未生效的状态。
如果是虚拟网络，本申请实施例提供的一种创建虚拟网络的方式，在至少一台虚拟机上添加具备各虚拟核心网网元以组建该虚拟网络。该虚拟核心网网元集成了实体核心网络网元的功能，虚拟核心网网元包括AMF、SMF、ULCL UPF、DLCL UPF或PSA UPF的部分或全部。
与实体网络不同的是，在虚拟网络中添加虚拟网元的方式更加简易快捷，因此，除了在组网时预先将各虚拟网元添加至虚拟网络中，并且把不需要运行的虚拟网元设置为未激活态(或者说未使能态)之外，还可以根据业务需求随时配置ULCL UPF、DLCL UPF或PSA UPF等虚拟网元，配置也可以理解为添加或插入。示例性地，一种可能的场景，原始虚拟网络(例如图1所示的网络架构)中不包含ULCL UPF、DLCL UPF或PSA UPF2等虚拟网元，根据业务需求添加ULCL UPF、DLCL UPF或至少一个新的PSA UPF如PSA UPF2，以组成新的虚拟网络。
接下来以虚拟网络为例，对组网过程进行介绍。其中，还可以根据网络状态将组网方式分为先建立ULCL UPF再建立DLCL UPF。以及同时建立ULCL UPF和DLCL UPF等几种组网方式，下面以图1所示的网络架构为例，对在图1的基础上建立图3所示的网络架构的几种组网流程分别进行说明。
组网方式一：先建立ULCL UPF再建立DLCL UPF。
如图10所示，为本申请实施例提供的一种组网的方法流程示意图，该方法包括：
步骤S1000，SMF为UE选择PSA UPF1作为PDU会话的IP锚点；
也就是，该终端设备的上行数据流和下行数据流会在PSA UPF1进行处理。该终端设备的上行数据流和下行数据流的路径包括：RAN、PSA UPF1、DN。
需要说明的是，步骤S1000是可选的步骤，不是必须执行的步骤。
步骤S1001，SMF接收激活指示信息，该激活指示信息用于指示SMF建立DLCL UPF和至少一个新的PSA UPF，下文以建立一个新的PSA UPF如PSA UPF2为例，进行介绍。
其中，该建立可以理解为添加、插入、配置。
示例性地，在图10的场景中，触发激活指示信息的条件可以满足如下触发条件中的一个或多个：
触发条件一，数据流的流速不低于预设流速阈值。
该数据流包含上行数据流和下行数据流，下面以上行数据流为例对触发条件进行介绍。在图1的场景中，PSA UPF1接收到的上行数据流的流速等于或超过预设流速阈值时，PSA UPF1确定满足触发条件，向SMF发送激活指示信息，该激活指示信息用于指示SMF激活DLCL UPF，可选的，若当前网络架构中仅存在PSA UPF1，SMF还可以选择激活一个新的PSA UPF(如PSA UPF2)。其中，PSA UPF1上报给SMF的指示信息中还可以包括该上行数据流的标识信息，例如，数据流五元组中的部分或全部，SMF根据为DLCL UPF配置该上行数据流的PDR规则，该PDR规则中包含该上行数据流的标识信息，以及传输参数，用于指示DLCL UPF将匹配该标识信息的数据流迁移至其他PSA UPF上，避免PSA UPF1的下行业务过载。
触发条件二，下行数据流的业务类型为预设业务类型。
其中，预设业务类型可以为多种，例如视频业务。若PSA UPF接收到的上行数据流为视频流，则确定满足触发条件，向SMF发送指示信息，该指示信息用于指示SMF激活DLCL UPF，或DLCL UPF和至少一个新的PSA UPF(如PSA UPF2)。
上述触发流程仅为举例，还可以是由核心网中的其他网元进行触发条件的检测，并触发SMF激活DLCL UPF和/或新的PSA UPF。示例性地，由AMF进行检测，例如，AMF检测到下行数据流为视频流时，AMF向SMF发送指示信息，指示SMF激活DLCL UPF和/或新的PSA UPF。其中，该指示信息与上述满足条件一时发送的指示信息的类型可以相同，具体请参见上述对指示信息的介绍，此处不再重复说明。
触发条件三，原PSA UPF(如PSA UPF1)自身的业务负载达到预设阈值，则PSA UPF1向SMF确定满足触发条件，向SMF发送激活指示信息。
步骤S1002，SMF建立ULCL UPF和PSA UPF2。
对于步骤S1001以及步骤S1002，可以理解为在该虚拟网络中添加了ULCL UPF和PSA UPF2，但ULCL UPF和PSA UPF2并未在该网络中生效，或者说，ULCL UPF和PSA UPF2的状态为未激活态或未使能态。也就是，此时该UE的上行数据流和下行数据流依然在PSA UPF1上传输。
具体的，在建立ULCL UPF和PSA UPF2后，SMF还可以为ULCL UPF、PSA UPF1和PSA UPF2配置对应的上行数据流包检测规则和下行数据流包检测规则。
对于ULCL UPF，示例性地，SMF为ULCL UPF配置上行数据流的第一包检测规则，该第一包检测规则包含至少一个PDR表项，其中的部分PDR表项可用于指示ULCL UPF将接收到的匹配该PDR表项的上行数据流发送至PSA UPF1，剩余的PDR表项中的部分PDR表项可用于指示ULCL UPF将接收到的匹配该PDR表项的上行数据流发送至PSA UPF2。同样的，SMF还可以为ULCL UPF配置下行数据流的第二包检测规则，该第二包检测规则包含指示一个PDR表项，其中的部分PDR表项可用于指示ULCL UPF将接收到的匹配该PDR表项的下行数据流发送至PSA UPF1，剩余的PDR表项中的部分PDR表项可用于指示ULCL UPF将接收到的匹配该PDR表项的下行数据流发送至PSA UPF2。其中，不同PDR表项用于指示不同的数据流。
举例来说，以上述触发方式一或触发方式二为例，SMF根据PSA UPF1上报的数据流的标识信息，生成该标识信息对应的数据流的新的PDR表项，该PDR表项用于指示ULCL UPF将匹配该标识信息的上行数据流发送至PSA UPF2，可以理解为，PSA UPF1检测到 较大的上行数据流后，指示SMF将该上行数据流分配到PSA UPF2上处理，以减少PSA UPF1的业务负载，降低网络拥塞风险。
除了PSA UPF1上报的标识信息对应的数据流之外，SMF还可以为PSA UPF2分配其他上行数据流，其分配的基本思想仍然是将该UE的全部上行数据流通过PSA UPF1和PSA UPF2发送至数据网络，PSA UPF1和PSA UPF2各负责处理该全部上行数据流中的部分数据流，避免其中一个PSA UPF产生过载问题。例如，将标识信息为第一标识信息的数据流发送至PSA UPF1，将标识信息为第二标识信息的数据流发送至PSA UPF2。其中，第一标识信息与第二标识信息包含的信息完全不同，或不完全相同。具体的，可以参见上文中的对于包检测规则相关描述，此处不再赘述。
同样的，第二包检测规则包含至少一个PDR表项，该PDR表项可以是，用于指示ULCL UPF从PSA UPF1和PSA UPF2接收下行数据流，以及将接收到的下行数据流发送至RAN。具体的，可以参见对第一包检测规则的描述，此处不再赘述。
对于PSA UPF1，示例性地，SMF为PSA UPF1配置下行数据流的第三包检测规则，该第三包检测规则包含至少一个PDR表项，该PDR表项可用于指示PSA UPF1将接收到的匹配该PDR表项的下行数据流发送至ULCL UPF。应理解的是，当前PSA UPF1中已有上行数据流的包检测规则，因此，此处可以不为PSA UPF1配置新的上行数据流包检测规则。
对于PSA UPF2，示例性地，SMF为PSA UPF2配置下行数据流的第四包检测规则，该第四包检测规则包含至少一个PDR表项，该PDR表项可用于指示PSA UPF2将接收到的匹配该PDR表项的下行数据流发送至ULCL UPF。同样的，SMF还可以为PSA UPF2配置上行数据流的第五包检测规则，该第五包检测规则包含指示一个PDR表项，该PDR表项可用于指示PSA UPF2将接收到的匹配该PDR表项的上行数据流发送至数据网络DN。
步骤S1003，SMF向ULCL UPF发送上行数据流的第一包检测规则和下行数据流的第二包检测规则。
SMF通过N4接口将第一包检测规则和/或第二包检测规则发送至ULCL UPF。
应理解的，此处虽然更新了ULCL UPF的上行数据流和下行数据流的包检测规则，但PSA UPF1的上行数据流的包检测规则和PSA UPF2的上、下行数据流的包检测规则都未更新，因此，该场景下，ULCL UPF和PSA UPF2仍未参与数据流传输。上行数据流和下行数据流仍然可以经由PSA UPF1传输。
需要说明的，第一包检测规则和第二包检测规则可以位于同一PDR中，也可以是不同的PDR，也就是说，在SMF下发时，可以是同时发送的，也可以是分开发送的，具体的，对于第一包检测规则和第二包检测规则的传输，SMF发送的可以是以第一包检测规则或第二包检测规则中的至少一个PDR表项，本申请实施例对此不作限定。
步骤S1004，SMF为PSA UPF1发送下行数据流的第三包检测规则。
SMF通过N4接口向PSA UPF1发送第三包检测规则，该第三包检测规则中的PDR表项用于指示PSA UPF1将下行数据流发送至ULCL UPF。
其中，SMF为PSA UPF1配置的下行数据流的PDR表项可以是结合为ULCL UPF配置的同一标识信息的下行数据流的PDR表项配置的，以为同一标识信息的下行数据流的配置一条完整的下行传输路径。例如，在步骤S1004中，SMF为ULCL UPF配置的某PDR表项可以为，从PSA UPF1接收标识信息为第三标识信息的下行数据流，对应的，SMF 为PSA UPF1配置的某PDR表项可以为，将标识信息为第三标识信息的下行数据流发送至ULCL UPF。
也就是说，通过上述步骤，当前下行数据流的传输过程可以是：下行数据流从数据网络DN侧发送出，依次经过PSA UPF1、ULDL UPF，RAN至UE。
应理解的是，由于还未更新PSA UPF1的上行数据流的包检测规则，因此，对于正在PSA UPF1处理的或即将要发送至PSA UPF1处理的上行数据报文，依然可以按照PSA UPF1中的上行数据流PDR表项的指示，将该上行数据流发送至数据网络DN。
示例性地，该UE的上行数据流的传输过程可以为：上行数据流从UE侧发出后，仍然经由PSA UPF1传输至DN侧。
步骤S1005，SMF为PSA UPF2发送上行数据流的第四包检测规则和下行数据流的第五包检测规则。
SMF通过N4接口向PSA UPF2发送上行数据流的第四包检测规则和下行数据流的第五包检测规则。其中，第四包检测规则和第五包检测规则均可以包含指示一个PDR表项。第四包检测规则和第五包检测规则可以位于同一PDR中，也可以是不同的PDR，也就是说，在SMF下发时，可以是同时发送的，也可以是分开发送的，具体的，对于第一包检测规则和第二包检测规则的传输，SMF发送的可以是以第四包检测规则或第五包检测规则中的至少一个PDR表项，本申请实施例对此不作限定。具体的，可以参见上述对于第一包检测规则和第二包检测规则的描述，以及上述对于包检测规则的相关介绍，此处不再赘述。
应理解的是，虽然更新了PSA UPF2的上、下行数据流的包检测规则，但RAN侧的核心网隧道信息还未更新，也即RAN未与ULCL UPF建立隧道，RAN仍将上行数据流发送至PSA UPF1，并且DN侧仍将下行数据流发送至PSA UPF1，因此PSA UPF2也无法接收下行数据流。因此，当前网络配置下，上行数据流的传输过程和下行数据流的传输过程可以与步骤S1004中介绍的相同。
步骤S1006，SMF向RAN发送核心网隧道信息。
示例性地，SMF将核心网隧道信息发送至AMF(图10中未示出)，AMF通过N1接口向RAN发送核心网隧道信息。步骤S1006仅为示意，还可以是由AMF或UPF(例如与RAN连接时的PSA UPF1)向RAN发送核心网隧道信息。本申请实施例对此不作限定。
核心网隧道信息用于建立核心网网元之间的隧道连接，例如，ULCL UPF和PSA UPF1以及ULCL UPF和PSA UPF2之间的隧道连接。核心网网元之间基于与对端网元之间的隧道进行数据报文传输。其中，对于核心网隧道信息，可以是SMF发送给各核心网网元的，也可以是核心网网元自身生成的，本申请实施例对此不作限定。
核心网网元基于RAN的隧道信息，以及RAN基于核心网隧道信息与核心网网元建立隧道连接。示例性地，在图3所示的网络架构中，ULCL UPF与RAN建立隧道之前，SMF向RAN发送核心网隧道信息，向ULCL UPF发送RAN隧道信息，以建立ULCL UPF与RAN之间的隧道连接，此处，RAN的上行数据流的目的端为ULCL UPF。
举例来说，在该场景中，该核心网隧道信息设置为PDU会话的N3接口的隧道头(包括N3对应的上行IP地址和上行GTP-U TEID信息)，GTP-U TEID是GPRS隧道协议端点标识(GPRS TunnelProtocol Tunnel Endpoint Identifier)的缩写，隧道头是相对于RAN而言的，是指ULCL UPF上的N3接口。接入网设备基于该核心网隧道信息将上行数据流发 送至该核心网隧道信息指示的IP地址处，即ULCL UPF的N3接口。
在当前网络配置下，该UE的上行数据流的传输过程可以为：上行数据流由UE侧发出后，一种可能的情况为，其中部分上行数据流依次经由RAN、ULCL UPF、PSA UPF1至DN。另一种可能的情况，其中剩余的部分上行数据流依次经由RAN、ULCL UPF、PSA UPF2至DN。应理解的是，PSA UPF1虽未更新上行数据流的包检测规则，但包检测规则并不限定该上行数据流由哪个网元(或节点)发出，因此仍可以从ULCL UPF接收上行数据流。
该UE的下行数据流的传输过程可以为：下行数据流由DN侧发出后，其中部分下行数据流依次经由PSA UPF1、ULCL UPF、RAN至UE。另一种可能的情况，其中剩余的部分上行数据流依次经由PSA UPF2、ULCL UPF、RAN至UE。
步骤S1007，SMF建立DLCL UPF。
具体的，SMF在该虚拟网络中添加DLCL UPF，或激活DLCL UPF。
步骤S1008，SMF向DLCL UPF发送上行数据流的第六包检测规则和下行数据流的第七包检测规则。
具体的，SMF为该DLCL UPF配置上行数据流的第六包检测规则，和下行数据流的第七包检测规则，并将该第六包检测规则和第七包检测规则发送至DLCL UPF。
示例性地，SMF为DLCL UPF配置上行数据流的第六包检测规则，该第六包检测规则包含至少一个PDR表项，该PDR表项可用于指示DLCL UPF将接收到的匹配该PDR表项的上行数据流发送至DN。同样的，SMF还可以为DLCL UPF配置下行数据流的第七包检测规则，该第七包检测规则包含指示一个PDR表项，其中的部分PDR表项可用于指示DLCL UPF将接收到的匹配该PDR表项的下行数据流发送至PSA UPF1，剩余的PDR表项中的部分PDR表项可用于指示DLCL UPF将接收到的匹配该PDR表项的下行数据流发送至PSA UPF2。具体的，对于第六包检测规则和第七包检测规则的使用流程和配置方式可以参见上述描述，此处不再赘述。
步骤S1009，DLCL UPF向DN侧发送下行路由信息，该下行路由信息用于指示DN将该终端设备的下行数据流发送至DLCL UPF；
具体的，该下行路由信息可以指示目的IP地址为该UE的IP地址的数据报文的下一跳，该下一跳可以为DLCL UPF的IP地址。DN侧基于该下行路由信息将发送给该UE的下行数据流发送至DLCL UPF。示例性地，该下行路由信息可以承载于SE消息中。
在该网络配置下，该UE的下行数据流的传输过程可以为：下行数据流由DN侧发出后，其中部分下行数据流依次经由DLCL UPF、PSA UPF1、ULCL UPF、RAN至UE。另一种可能的情况，其中剩余的部分上行数据流依次经由DLCL UPF、PSA UPF2、ULCL UPF、RAN至UE。
可选的，还可以根据DLCL UPF接收上行数据流的构思，更新PSA UPF1和/或PSA UPF2的上行数据流的包检测规则。例如，该包检测规则用于指示PSA UPF1将上行数据流发送至DLCL UPF，或指示PSA UPF2将上行数据流发送至DLCL UPF。
若更新了PSA UPF1和PSA UPF2的上行数据流的包检测规则时，在该网络配置下，该UE的上行数据流的传输过程可以为：上行数据流由UE侧发出后，一种可能的情况为，其中部分上行数据流依次经由RAN、ULCL UPF、PSA UPF1、DLCL UPF至DN。另一种可能的情况，其中剩余的部分上行数据流依次经由RAN、ULCL UPF、PSA UPF2、DLCL  UPF至DN。
组网方式二：同时建立ULCL UPF和DLCL UPF。
以图1所示的网络架构为例，对在图1的基础上建立图3所示的网络架构的组网流程进行介绍。
如图11所示，为本申请实施例提供的一种组网的方法流程示意图，该方法包括：
步骤S1100，SMF为UE选择PSA UPF1作为PDU会话的IP锚点；
也就是，该终端设备的上行数据流和下行数据流会在PSA UPF1进行处理。该终端设备的上行数据流和下行数据流的路径包括：RAN、PSA UPF1、DN。
需要说明的是，步骤S1100是可选的步骤，不是必须执行的步骤。
步骤S1101，SMF接收激活指示信息，该激活指示信息用于指示SMF建立DLCL UPF、ULCL UPF和至少一个新的PSA UPF，下文以建立一个新的PSA UPF如PSA UPF2为例，进行介绍。
其中，对于触发激活指示信息的触发条件和方法流程请参见上述步骤S1001中的相关描述，此处不再赘述。
步骤S1102，SMF建立DLCL UPF、ULCL UPF和PSA UPF2。
对于步骤S1101以及步骤S1102，可以理解为在该虚拟网络中添加了DLCL UPF、ULCL UPF和PSA UPF2，但DLCL、PFULCL UPF和PSA UPF2并未在该网络中生效，或者说，ULCL UPF和PSA UPF2的状态为未激活态或未使能态。也就是，此时该UE的上行数据流和下行数据流依然在PSA UPF1上传输。
具体的，在建立DLCL UPF、ULCL UPF和PSA UPF2后，SMF还可以为DLCL UPF、ULCL UPF、PSA UPF1和PSA UPF2配置对应的上行数据流包检测规则和下行数据流包检测规则。
具体的配置方式和方法流程请参见上文步骤S1002的相关描述，此处不再赘述。
为了方便描述，在该实施例中，将SMF为ULCL UPF配置的上行数据流的包检测规则简称为第一包检测规则，将SMF为ULCL UPF配置的下行数据流的包检测规则简称为第二包检测规则，将SMF为PSA UFP1配置的下行数据流的包检测规则简称为第三检测规则，将SMF为PSA UFP2配置的下行数据流的包检测规则简称为第四检测规则，将SMF为PSA UPF2配置的下行数据流的包检测规则简称为第五包检测规则，将SMF为DLCL UPF配置的上行数据流的包检测规则简称为第六包检测规则，将SMF为DLCL UPF配置的上行数据流的包检测规则简称为第七包检测规则。需要说明的是，此处相同名称的包检测规则所具有的内容可以不同，例如，以图2或图3所示的网络架构为例，SMF为DLCL UPF配置的第七包检测规则，可以是指示数据流A对应的PSA UPF为PSA UPF1，也可以是指示数据流A对应的PSA UPF为PSA UPF2。本申请实施例对此不作限定。
需要说明的是，上述简称仅用于区分不同网元之间的包检测规则，并非指示不同实施例中SMF为同一网元配置的包检测规则相同。
步骤S1103，SMF向ULCL UPF发送第一包检测规则和第二包检测规则。
步骤S1104，SMF向DLCL UPF发送第六包检测规则和第七包检测规则。
步骤S1105，DLCL UPF向DN侧发送下行路由信息，该下行路由信息用于指示DN将该终端设备的下行数据流发送至DLCL UPF；
具体的，对于步骤S1105的执行流程可以参见上述步骤S1008的相关描述，此处不再 赘述。
需要说明的是，步骤S1103～步骤S1105之间并没有顺序限制，上述流程仅为一种流程示意，也可以是由SMF先向DLCL UPF发送第六包检测规则和第七包检测规则，再向ULCL UPF发送第一包检测规则和第二包检测规则等执行顺序，本申请实施例对此不作限定。
步骤S1106，SMF为PSA UPF1发送下行数据流的第三包检测规则。
SMF通过N4接口向PSA UPF1发送第三包检测规则，该第三包检测规则中的PDR表项用于指示PSA UPF1将下行数据流发送至ULCL UPF。
具体的，对于步骤S1106的执行流程可以参见上述步骤S1004的相关描述，此处不再赘述。
需要说明的是，步骤S1105和步骤S1106没有顺序限定。可以是同时执行的，也可以是顺序执行的，执行顺序没有限定。
步骤S1107，SMF为PSA UPF2发送上行数据流的第四包检测规则和下行数据流的第五包检测规则。
具体的，对于步骤S1107的执行流程可以参见上述步骤S1005的相关描述，此处不再赘述。
步骤S1108，SMF通过AMF向RAN发送核心网隧道信息，向ULCL UPF发送RAN隧道信息，以使RAN与ULCL UPF之间建立隧道连接。
示例性地，SMF将核心网隧道信息发送至AMF(图11中未示出)，AMF通过N1接口向RAN发送核心网隧道信息。步骤S1108仅为示意，还可以是由AMF或UPF(例如与RAN连接时的PSA UPF1)向RAN发送核心网隧道信息。本申请实施例对此不作限定。具体的，对于步骤S1108的执行流程可以参见上述步骤S1007的相关描述，此处不再赘述。
需要说明的是，上述图10和图11所示的方法仅为举例，本申请实施例可以建立多个PSA UPF，图10和图11未示出。另外上述为由SMF建立ULCL UPF、DLCL UPF和PSA UPF以及更新各UPF的上行、下行包检测规则的方式仅为示意，还可以由其他节点或网元执行SMF在上述图10或图11的执行步骤，本申请实施例对此不作限定。
可替代地，本申请实施例中的“建立”可以是上文描述的在可能的场景下的添加、插入、创建、配置、激活或使能中的任一种。
上述内容为建立新的核心网网元的方法流程，作为一种优化方式，对于图2或图3所示的网络架构，还可以根据业务需求，例如，该UE的数据流的较小时，可以选择释放至少一个PSA UPF、DLCL UPF或ULCL UPF中的部分或全部。
如图12所示，为本申请实施例提供的一种释放网元的方式流程示意图。该方法可以应用于图2或图3的网络架构中，下面以图3为例，对释放图3中至少一个PSA UPF、DLCL UPF或ULCL UPF中的部分或全部的方法流程进行详细介绍，该方法可以包括如下步骤：
步骤S1200，SMF接收释放指示信息，该释放指示信息用于指示释放至少一个PSA UPF、DLCL UPF或ULCL UPF中的部分或全部，下文假设该释放指示信息用于指示释放PSA UPF2、DLCL UPF和ULCL UPF。
具体的，该释放指示信息可以由该UE的至少两个PSA UPF中的至少一个PSA UPF发送，例如，由PSA UFP2发送时，PSA UPF2在检测到满足释放条件时向SMF发送释放指示信息，该释放条件可以满足下：在预设时间内未接收到数据流，该数据流包含上行数 据流和/或下行数据流。示例性，PSA UPF2在预设时间内未接收到下行数据流时，当前满足释放条件。
步骤S1201，SMF通过AMF更新RAN侧上行数据流规则，包括与PSA UPF1建立隧道连接所需的核心网隧道信息，指示RAN发送上行数据流的目的端为PSA UPF1。
具体的，SMF将PSA UPF1与RAN建立隧道连接所需的核心网隧道信息发送至AMF，由AMF通过N2接口发送至RAN，将RAN的隧道信息发送至PSA UPF1，以建立RAN与PSA UPF1之间的隧道连接。
假设上行数据流由PSA UPF1直接发送至DN，在该网络配置下，该UE的上行数据流的传输过程可以为：上行数据流从UE侧发出后，依次经由RAN、PSA UPF1至DN。
该UE的下行数据流的传输过程仍然可以为：下行数据流由DN侧发出后，其中部分下行数据流依次经由DLCL UPF、PSA UPF1、ULCL UPF、RAN至UE。另一种可能的情况，其中剩余的部分上行数据流依次经由DLCL UPF、PSA UPF2、ULCL UPF、RAN至UE。
步骤S1202，SMF向PSA UPF1配置新的下行数据流的包检测规则。
具体的，SMF通过N4接口将可以为PSA UPF1配置新的下行数据流的包检测规则发送至PSA UPF1，该包检测规则用于指示PSA UPF1将下行数据流发送至RAN。
上述方式，当释放DLCL UPF和ULCL UPF和PSA UPF2之后，PSA UPF1能够将上、下行数据流发送至对应的目的端。
步骤S1203，PSA UPF1向DN发送第二下行路由信息，该第下行二路由信息用于指示DN将目的IP地址为该UE的IP地址的下行数据流发送至PSA UPF1。
在该网络配置下，该UE的上行数据流的传输过程可以为：上行数据流从UE侧发出后，依次经由RAN、PSA UPF1至DN。
该UE的下行数据流的传输过程可以为：下行数据流由DN侧发出后，其中部分下行数据流依次经由PSA UPF1、RAN至UE。
此时，上行数据流和下行数据流又恢复为图1的网络架构下的传输方式。也就是说，ULDL UPF和DLCL UPF释放后对数据流传输至目的端不会产生影响。
步骤S1204，SMF触发释放ULCL UPF、DLCL UPF和PSA UPF2。
对于合一部署的情况，即ULCL UPF、DLCL UPF或PSA UPF2中的部分或全部部署于同一UPF上时，对于数据流的传输方式和网络的配置方式与分离部署相似，可以参见上文相关描述，不同的是，合一部署时，例如DLCL UPF和PSA UPF2合一部署时，DLCL UPF向PSA UPF2发送下行数据流时，该下行数据流不需要穿越IP，简化了传输方式。
可选的，在合一部署场景中，例如DLCL UPF、PSA UPF1和PSA UPF2合一部署时，SMF可以不向DLCL UPF下发PDR，由DLCL UPF记录各数据流与对应的PSA UPF的关系，DLCL UPF可以根据内部的PSA的业务负载状况，调整并记录数据流与目的PSA UPF的对应关系。
需要说明的是，上述各个消息的名称仅仅是作为示例，随着通信技术的演变，上述任意消息均可能改变其名称，但不管其名称如何发生变化，只要其含义与本申请上述消息的含义相同，则均落入本申请的保护范围之内。
上述主要从各个网元之间交互的角度对本申请提供的方案进行了介绍。可以理解的是，上述实现各网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。 本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
与上述构思相同，如图13所示，本申请实施例还提供一种装置1300用于实现上述方法中下行分流用户面网元的功能。该装置1300可以以软件或硬件的形式存在。例如，该装置可以为软件模块或者芯片系统。本申请实施例中，芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。该装置1300可以包括：处理单元1301和通信单元1302。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
示例性地，当该装置1300实现上述任一实施例中的下行分流用户面网元的功能时，所述通信单元1302，用于从会话管理网元接收第一指示信息；处理单元1301，用于根据所述第一指示信息，通过所述通信单元1302将数据网络DN发送给第一终端设备的全部下行数据流通过至少两个目标协议数据单元PDU会话锚点发送给所述第一终端设备；其中，所述至少两个目标PDU会话锚点分别向所述第一终端设备发送下行数据流中的部分数据流。
在一种可能的实现方法中，所述第一指示信息包含至少一个子指示信息，各子指示信息分别用于指示不同的下行数据流的标识信息与目标PDU会话锚点的对应关系；所述处理单元1301，用于针对每个子指示信息，将匹配该子指示信息包含的标识信息的下行数据流，通过所述通信单元1302发送至匹配该子指示信息包含的标识信息的下行数据流对应的所述目标PDU会话锚点。
示例性的，所述标识信息可以包括下列中的一项或多项：源地址信息、目的地址信息、源端口标识、目的端口标识或协议类型。
所述子指示信息还可以包括：所述第一用户面网元中用于发送所述下行数据流的互联网协议IP地址，和/或所述目标PDU会话锚点中用于接收所述下行数据流的IP地址。
在又一种可能的实现方法中，所述通信单元1302，用于从所述移动会话管理网元接收第二指示信息；所述处理单元1301，用于根据第二指示信息，通过所述通信单元1302从至少一个第一PDU会话锚点接收所述第一终端设备发送至所述数据网路的上行数据流；其中，其中，所述第一PDU会话锚点为能够向所述数据网络发送所述第一终端设备的上行数据流的网元上的PDU会话锚点中的其中一个。
此外，所述处理单元1301还可以用于在将所述上行数据流发送至所述数据网络之前，生成第一下行路由信息；所述通信单元1302，用于将所述第一下行路由信息发送至所述数据网络；所述第一下行路由信息用于指示所述数据网络将所述发送至所述第一终端设备的下行数据流发送至所述第一用户面网元，所述下行数据流的目的端为所述第一终端设备。
处理单元1301和通信单元1302执行的其它方法可以参考图4、图6、图8、图10～图12所示的方法流程中下行分流用户面网元的相关描述，这里不再赘述。
如图14所示为本申请实施例提供的装置1400，图14所示的装置可以为图13所示的 装置的一种硬件电路的实现方式。该通信装置可适用于实现图4、图6、图8、图10～图12所示出的流程图中，执行上述方法实施例中下行分流用户面网元的功能。为了便于说明，图14仅示出了该通信装置的主要部件。
图14所示的装置1400包括至少一个处理器1420，用于实现本申请实施例提供的方法中下行分流用户面网元的功能。装置1400还可以包括至少一个存储器1430，用于存储程序指令和/或数据。存储器1430和处理器1420耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器1420可能和存储器1430协同操作。处理器1420可能执行存储器1430中存储的程序指令。所述至少一个存储器中的至少一个可以包括于处理器中。
装置1400还可以包括通信接口1410，用于通过传输介质和其它设备进行通信，从而用于装置1400中的装置可以和其它设备进行通信。在本申请实施例中，通信接口可以是收发器、电路、总线、模块或其它类型的通信接口。在本申请实施例中，收发器可以为独立的接收器、独立的发射器、集成收发功能的收发器、或者是接口电路。处理器1420利用通信接口1410收发数据，并用于实现图4、图6、图8、图10～图12所示出的流程图对应的实施例中下行分流用户面网元所执行的方法。
示例性地，当该装置1400实现上述任一实施例中下行分流用户面网元的功能时，通信接口1410，用于从会话管理网元接收第一指示信息；处理器1420，用于根据所述第一指示信息，通过通信接口1410将数据网络DN发送给第一终端设备的全部下行数据流通过至少两个目标协议数据单元PDU会话锚点发送给所述第一终端设备；其中，所述至少两个目标PDU会话锚点分别向所述第一终端设备发送下行数据流中的部分数据流。处理器1420和通信接口1410执行的其它方法可以参考图4、图6、图8、图10～图12所示出的流程图所示的方法流程中的描述，这里不再赘述。
本申请实施例中不限定上述通信接口1410、处理器1420以及存储器1430之间的具体连接介质。本申请实施例在图14中以存储器1430、处理器1420以及通信接口1410之间通过总线1440连接，总线在图14中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图14中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
与上述构思相同，如图15所示，本申请实施例还提供一种装置1500用于实现上述方法中移动会话管理网元的功能。该装置1500可以以软件或硬件的形式存在。例如，该装置可以为软件模块或者芯片系统。本申请实施例中，芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。该装置1500可以包括：处理单元1501和通信单元1502。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
示例性地，当该装置1500实现上述任一实施例中的移动会话管理网元的功能时，所述处理单元1501，用于生成第一指示信息，所述第一指示信息用于指示第一用户面网元将数据网络DN发送给第一终端设备的全部下行数据流通过至少两个目标协议数据单元PDU会话锚点发送给终端设备；其中，所述至少两个目标PDU会话锚点分别向所述第一终端设备发送下行数据流中的部分数据流；所述通信单元1502，用于向所述第一用户面网元发 送所述第一指示信息。
在一种可能的实现方法中，所述第一指示信息可以包含至少一个子指示信息，各子指示信息分别用于指示不同的下行数据流的标识信息与目标PDU会话锚点的对应关系。
在一种可能的实现方法中；所述标识信息可以包括下列中的一项或多项：源地址信息、目的地址信息、源端口标识、目的端口标识或协议类型。
在一种可能的实现方法中，所述子指示信息还可以包括：所述第一用户面网元中用于发送所述下行数据流的互联网协议IP地址，和/或所述目标PDU会话锚点中用于接收所述下行数据流的IP地址。
在一种可能的实现方法中，所述通信单元1502，还用于接收激活指示信息，所述激活指示信息用于指示所述会话管理网元激活所述下行分流用户面网元，或指示所述会话管理网元激活所述第一用户面网元和至少一个新的PDU会话锚点，并生成所述第一指示信息；其中，所述目标PDU会话锚点包含所述至少一个新的PDU会话锚点。
在一种可能的实现方法中，所述激活指示信息可以为至少一个第二PDU会话锚点或移动性管理网元在检测到数据流满足触发条件后发送给所述会话管理网元的；所述触发条件包括：所述数据流的业务类型为预设业务类型；或所述数据流的传输速率不低于预设速率阈值；其中，所述数据流包括上行数据流和/或下行数据流，所述上行数据流为所述第一终端设备发送至所述数据网络的数据流；，所述第二PDU会话锚点为能够向所述第一终端设备发送下行数据流的网元上的PDU会话锚点中不包含所述新的PDU会话锚点的其中一个。
在一种可能的实现方法中，所述通信单元1502，用于从所述第三PDU会话锚点接收释放指示信息，所述释放指示信息用于指示所述会话管理网元释放所述第三PDU会话锚点和/或所述第一用户面网元；其中，所述第三PDU会话锚点为能够向所述第一终端设备发送下行数据流的网元上的PDU会话锚点中的其中一个。
在一种可能的实现方法中，所述释放指示信息为所述至少一个第三PDU会话锚点在检测到满足释放条件后发送给所述会话管理网元的；所述释放条件包括：所述第三PDU会话锚点在预设时间内未接收到数据流，所述数据流包括上行数据流和/或下行数据流。
处理单元1501和通信单元1502执行的其它方法可以参考图4、图6、图8、图10～图12所示的方法流程中移动会话管理网元的相关描述，这里不再赘述。
如图16所示为本申请实施例提供的装置1600，图16所示的装置可以为图15所示的装置的一种硬件电路的实现方式。该通信装置可适用于实现图4、图6、图8、图10～图12所示出的流程图中，执行上述方法实施例中移动会话管理网元的功能。为了便于说明，图16仅示出了该通信装置的主要部件。
图16所示的装置1600包括至少一个处理器1620，用于实现本申请实施例提供的方法中移动会话管理网元的功能。装置1600还可以包括至少一个存储器1630，用于存储程序指令和/或数据。存储器1630和处理器1620耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器1620可能和存储器1630协同操作。处理器1620可能执行存储器1630中存储的程序指令。所述至少一个存储器中的至少一个可以包括于处理器中。
装置1600还可以包括通信接口1610，用于通过传输介质和其它设备进行通信，从而用于装置1600中的装置可以和其它设备进行通信。在本申请实施例中，通信接口可以是 收发器、电路、总线、模块或其它类型的通信接口。在本申请实施例中，收发器可以为独立的接收器、独立的发射器、集成收发功能的收发器、或者是接口电路。处理器1420利用通信接口1610收发数据，并用于实现图4、图6、图8、图10～图12所示出的流程图对应的实施例中移动会话管理网元所执行的方法。
示例性地，当该装置1600实现上述任一实施例所示的流程中移动会话管理网元的功能时，处理器1420，用于生成第一指示信息，所述第一指示信息用于指示第一用户面网元将数据网络DN发送给第一终端设备的全部下行数据流通过至少两个目标协议数据单元PDU会话锚点发送给终端设备；其中，所述至少两个目标PDU会话锚点分别向所述第一终端设备发送下行数据流中的部分数据流；
再示例性地，通信接口1610，用于向所述第一用户面网元发送所述第一指示信息。
处理器1620和通信接口1610执行的其它方法可以参考图4、图6、图8、图10～图12所示出的流程图所示的方法流程中的描述，这里不再赘述。
本申请实施例中不限定上述通信接口1610、处理器1620以及存储器1630之间的具体连接介质。本申请实施例在图16中以存储器1630、处理器1620以及通信接口1610之间通过总线1640连接，总线在图16中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图16中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
与上述构思相同，如图17所示，本申请实施例还提供一种装置1700用于实现上述方法中PSA UPF的功能。该装置1700可以以软件或硬件的形式存在。例如，该装置可以为软件模块或者芯片系统。本申请实施例中，芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。该装置1700可以包括：处理单元1701和通信单元1702。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
示例性地，当该装置1700实现上述任一实施例中的PSA UPF的功能时，所述通信单元1702，用于从第一用户面网元接收所述数据网络DN发送给第一终端设备的下行数据流中的部分下行数据流；所述通信单元1702，还用于将接收的所述部分下行数据流发送给所述第一终端设备。
在一种可能的实现方法中，所述目标PDU会话锚点为所述会话管理网元在接收到激活指示信息后激活的至少一个新的PDU会话锚点中的其中一个。
在一种可能的实现方法中，所述通信单元1702，用于接收来自会话管理网元的第三指示信息；所述处理单元1701，用于根据所述第三指示信息，从第二用户面网元接收到所述第一终端设备发送至所述数据网络DN的上行数据流中的部分上行数据流，并将所述部分上行数据流发送至所述第一用户面网元。
在一种可能的实现方法中，所述处理单元1701，用于在检测到满足释放条件后，向所述会话管理网元发送释放指示信息，所述释放指示信息用于指示所述会话管理网元释放所述目标PDU会话锚点和/或所述第一用户面网元。
处理单元1701和通信单元1702执行的其它方法可以参考图4、图6、图8、图10～图12所示的方法流程中PSA UPF的相关描述，这里不再赘述。
如图18所示为本申请实施例提供的装置1800，图18所示的装置可以为图17所示的装置的一种硬件电路的实现方式。该通信装置可适用于实现图4、图6、图8、图10～图12所示出的流程图中，执行上述方法实施例中PSA UPF的功能。为了便于说明，图18仅示出了该通信装置的主要部件。
图18所示的装置1800包括至少一个处理器1820，用于实现本申请实施例提供的方法中PSA UPF的功能。
装置1800还可以包括至少一个存储器1830，用于存储程序指令和/或数据。存储器1830和处理器1820耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器1820可能和存储器1830协同操作。处理器1820可能执行存储器1830中存储的程序指令。所述至少一个存储器中的至少一个可以包括于处理器中。
装置1800还可以包括通信接口1810，用于通过传输介质和其它设备进行通信，从而用于装置1800中的装置可以和其它设备进行通信。在本申请实施例中，通信接口可以是收发器、电路、总线、模块或其它类型的通信接口。在本申请实施例中，收发器可以为独立的接收器、独立的发射器、集成收发功能的收发器、或者是接口电路。处理器1420利用通信接口1810收发数据，并用于实现图4、图6、图8、图10～图12所示出的流程图对应的实施例中PSA UPF所执行的方法。
示例性地，当该装置1800实现上述任一实施例所示的流程中PSA UPF的功能时，通信接口1810，用于从第一用户面网元接收所述数据网络发送给第一终端设备的下行数据流中的部分下行数据流；再示例性地，通信接口1810，还用于将接收的所述部分下行数据流发送给所述第一终端设备。处理器1820和通信接口1810执行的其它方法可以参考图4、图6、图8、图10～图12所示出的流程图所示的方法流程中的描述，这里不再赘述。
本申请实施例中不限定上述通信接口1810、处理器1820以及存储器1830之间的具体连接介质。本申请实施例在图18中以存储器1830、处理器1820以及通信接口1810之间通过总线1840连接，总线在图18中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图18中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
需要说明的是，在本申请实施例中，处理器可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
在本申请实施例中，存储器可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本申请实施例中的存储器还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。
本申请实施例提供的方法中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计 算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、用户设备或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，简称DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机可以存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，数字视频光盘(digital video disc，简称DVD))、或者半导体介质(例如，SSD)等。
在本申请实施例中，在无逻辑矛盾的前提下，各实施例之间可以相互引用，例如方法实施例之间的方法和/或术语可以相互引用，例如装置实施例之间的功能和/或术语可以相互引用，例如装置实施例和方法实施例之间的功能和/或术语可以相互引用。
本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (30)

  1. 一种数据传输方法，其特征在于，包括：
    第一用户面网元从会话管理网元接收第一指示信息；
    所述第一用户面网元根据所述第一指示信息，将数据网络DN发送给第一终端设备的下行数据流通过至少两个目标协议数据单元PDU会话锚点发送给所述第一终端设备；其中，所述至少两个目标PDU会话锚点分别向所述第一终端设备发送下行数据流中的部分数据流。
  2. 如权利要求1所述的方法，其特征在于，所述第一指示信息包含至少一个子指示信息，各子指示信息分别用于指示不同的下行数据流的标识信息与目标PDU会话锚点的对应关系；
    所述第一用户面网元根据所述第一指示信息，将数据网络DN发送给第一终端设备的下行数据流通过至少两个目标PDU会话锚点发送给所述第一终端设备，包括：
    针对每个子指示信息，所述第一用户面网元将匹配该子指示信息包含的标识信息的下行数据流，发送至匹配该子指示信息包含的标识信息的下行数据流对应的所述目标PDU会话锚点。
  3. 如权利要求2所述的方法，其特征在于，所述标识信息包括下列中的一项或多项：
    源地址信息、目的地址信息、源端口标识、目的端口标识或协议类型。
  4. 如权利要求2或3所述的方法，其特征在于，所述子指示信息还包括：所述第一用户面网元中用于发送所述下行数据流的互联网协议IP地址，和/或所述目标PDU会话锚点中用于接收所述下行数据流的IP地址。
  5. 如权利要求1-4任一项所述的方法，其特征在于，还包括：
    所述第一用户面网元从所述会话管理网元接收第二指示信息；
    所述第一用户面网元根据所述第二指示信息，从至少一个第一PDU会话锚点接收所述第一终端设备发送至所述数据网络的上行数据流；
    其中，所述第一PDU会话锚点为能够向所述数据网络发送所述第一终端设备的上行数据流的网元上的PDU会话锚点中的其中一个。
  6. 如权利要求5所述的方法，其特征在于，还包括：
    所述第一用户面网元在将所述上行数据流发送至所述数据网络之前，生成第一下行路由信息，并将所述第一下行路由信息发送至所述数据网络；所述第一下行路由信息用于指示所述数据网络将所述发送至所述第一终端设备的下行数据流发送至所述第一用户面网元，所述下行数据流的目的端为所述第一终端设备。
  7. 一种数据传输方法，其特征在于，包括：
    会话管理网元生成第一指示信息，所述第一指示信息用于指示第一用户面网元将数据网络DN发送给第一终端设备的下行数据流通过至少两个目标协议数据单元PDU会话锚点发送给终端设备；其中，所述至少两个目标PDU会话锚点分别向所述第一终端设备发送下行数据流中的部分数据流；
    所述会话管理网元向所述第一用户面网元发送所述第一指示信息。
  8. 如权利要求7所述的方法，其特征在于，所述第一指示信息包含至少一个子指示 信息，各子指示信息分别用于指示不同的下行数据流的标识信息与目标PDU会话锚点的对应关系。
  9. 如权利要求8所述的方法，其特征在于，所述标识信息包括下列中的一项或多项：
    源地址信息、目的地址信息、源端口标识、目的端口标识或协议类型。
  10. 如权利要求8或9所述的方法，其特征在于，所述子指示信息还包括：
    所述第一用户面网元中用于发送所述下行数据流的互联网协议IP地址，和/或所述目标PDU会话锚点中用于接收所述下行数据流的IP地址。
  11. 如权利要求7-10任一项所述的方法，其特征在于，所述会话管理网元生成第一指示信息之前，还包括：
    所述会话管理网元接收激活指示信息，所述激活指示信息用于指示所述会话管理网元激活所述第一用户面网元和至少一个新的PDU会话锚点；
    其中，所述目标PDU会话锚点包含在所述至少一个新的PDU会话锚点中。
  12. 如权利要求11所述的方法，其特征在于，所述激活指示信息为至少一个第二PDU会话锚点或移动性管理网元在检测到数据流满足触发条件后发送给所述会话管理网元的；
    所述触发条件包括：
    所述数据流的业务类型为预设业务类型；或
    所述数据流的传输速率不低于预设速率阈值；
    其中，所述数据流包括上行数据流和/或下行数据流，所述上行数据流为所述第一终端设备发送至所述数据网络的数据流；所述第二PDU会话锚点为能够向所述第一终端设备发送下行数据流的网元上的PDU会话锚点中不包含所述新的PDU会话锚点的其中一个。
  13. 如权利要求11或12所述的方法，其特征在于，还包括：
    所述会话管理网元从第三PDU会话锚点接收释放指示信息，所述释放指示信息用于指示所述会话管理网元释放所述第三PDU会话锚点和/或所述第一用户面网元；
    其中，所述第三PDU会话锚点为能够向所述第一终端设备发送下行数据流的网元上的PDU会话锚点中的其中一个。
  14. 如权利要求13所述的方法，其特征在于，所述释放指示信息为所述至少一个第三PDU会话锚点在检测到满足释放条件后发送给所述会话管理网元的；
    所述释放条件包括：
    所述第三PDU会话锚点在预设时间内未接收到数据流，所述数据流包括上行数据流和/或下行数据流。
  15. 一种数据传输方法，其特征在于，包括：
    目标协议数据单元PDU会话锚点从第一用户面网元接收所述数据网络DN发送给第一终端设备的下行数据流中的部分下行数据流；
    所述目标PDU会话锚点将接收的所述部分下行数据流发送给所述第一终端设备。
  16. 如权利要求15所述的方法，其特征在于，所述目标PDU会话锚点为所述会话管理网元在接收到激活指示信息后激活的至少一个新的PDU会话锚点中的其中一个。
  17. 如权利要求15或16所述的方法，其特征在于，还包括：
    所述目标PDU会话锚点接收来自会话管理网元的第三指示信息；
    所述目标PDU会话锚点根据所述第三指示信息，从第二用户面网元接收到所述第一 终端设备发送至所述数据网络DN的上行数据流中的部分上行数据流，并将所述部分上行数据流发送至所述第一用户面网元。
  18. 如权利要求15或16所述的方法，其特征在于，还包括：
    所述目标PDU会话锚点在检测到满足释放条件后，向会话管理网元发送释放指示信息，所述释放指示信息用于指示所述会话管理网元释放所述目标PDU会话锚点和/或所述第一用户面网元；
    其中，所述释放条件包括：
    所述目标PDU会话锚点在预设时间内未接收到数据流，所述数据流包括上行数据流和/或下行数据流。
  19. 一种通信装置，其特征在于，用于实现如权利要求1-6中任一项所述的方法。
  20. 一种通信装置，其特征在于，包括处理器和存储器，所述存储器和所述处理器耦合，所述存储器中存储有计算机程序指令，所述处理器执行所述计算机程序指令时如权利要求1-6中的任一项所述的方法被执行。
  21. 一种通信装置，其特征在于，包括收发单元和处理单元；
    所述收发单元，用于收发数据；
    所述处理单元，用于通过所述收发单元，执行如权利要求1-6中的任一项所述的方法。
  22. 一种通信装置，其特征在于，用于实现如权利要求7-14中任一项所述的方法。
  23. 一种通信装置，其特征在于，包括处理器和存储器，所述存储器和所述处理器耦合，所述存储器中存储有计算机程序指令，所述处理执行所述计算机程序指令时如权利要求7-14中的任一项所述的方法被执行。
  24. 一种通信装置，其特征在于，包括收发单元和处理单元；
    所述收发单元，用于收发数据；
    所述处理单元，用于通过所述收发单元，执行如权利要求7-14中的任一项所述的方法。
  25. 一种通信装置，其特征在于，用于实现如权利要求15-18中任一项所述的方法。
  26. 一种通信装置，其特征在于，包括处理器和存储器，所述存储器和所述处理器耦合，所述存储器中存储有计算机程序指令，所述处理执行所述计算机程序指令时如权利要求15-18中的任一项所述的方法被执行。
  27. 一种通信装置，其特征在于，包括收发单元；
    所述收发单元，用于收发数据；
    所述处理单元，用于通过所述收发单元，执行如权利要求15-18中的任一项所述的方法。
  28. 一种通信系统，其特征在于，包括权利要求19-21任一项所述的通信装置，权利要求22-24任一项所述的通信装置，和权利要求25-27任一项所述的通信装置。
  29. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机程序或指令，当所述计算机程序或指令被一个或多个处理器执行时，实现如权利要求1-18中任一项所述的方法。
  30. 一种计算机程序产品，其特征在于，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1-18中任一项所述的方法。
PCT/CN2020/122495 2020-01-21 2020-10-21 一种数据传输方法及装置 WO2021147402A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010072666.3A CN113225770A (zh) 2020-01-21 2020-01-21 一种数据传输方法及装置
CN202010072666.3 2020-01-21

Publications (1)

Publication Number Publication Date
WO2021147402A1 true WO2021147402A1 (zh) 2021-07-29

Family

ID=76991944

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/122495 WO2021147402A1 (zh) 2020-01-21 2020-10-21 一种数据传输方法及装置

Country Status (2)

Country Link
CN (1) CN113225770A (zh)
WO (1) WO2021147402A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114710810A (zh) * 2022-05-31 2022-07-05 新华三技术有限公司 一种数据传输方法、装置及系统
CN116669134A (zh) * 2023-07-07 2023-08-29 中国电信股份有限公司 Smf网元与upf网元适配方法、装置、设备及介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114710811B (zh) * 2022-04-07 2024-10-01 中国联合网络通信集团有限公司 数据流转发方法、装置、电子设备及存储介质
CN117750414A (zh) * 2022-09-13 2024-03-22 中兴通讯股份有限公司 管理边缘psa的方法、电子设备、计算机可读介质
CN118102488A (zh) * 2022-11-28 2024-05-28 中兴通讯股份有限公司 数据转发方法、设备及计算机可读存储介质
CN118316878A (zh) * 2023-01-09 2024-07-09 中国移动通信有限公司研究院 一种网络拥塞控制方法及装置、通信设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103826276A (zh) * 2012-11-19 2014-05-28 中国联合网络通信集团有限公司 数据传输方法、基站、管理控制中心和系统
WO2015055496A1 (en) * 2013-10-15 2015-04-23 Telefonaktiebolaget L M Ericsson (Publ) Performing an action on certain media streams in a multimedia communications network
CN107920372A (zh) * 2016-10-10 2018-04-17 电信科学技术研究院 一种信息指示方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3311606B1 (en) * 2015-06-16 2022-05-11 Telefonaktiebolaget LM Ericsson (PUBL) Handling a service chain for a ue which roams into a visited network
CN108632904B (zh) * 2017-03-24 2019-09-17 电信科学技术研究院 一种通信方法及设备
WO2018205775A1 (zh) * 2017-05-11 2018-11-15 华为技术有限公司 缓存数据的方法和会话管理功能实体
CN109660464A (zh) * 2017-10-12 2019-04-19 中兴通讯股份有限公司 一种下行报文处理方法、upf设备和存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103826276A (zh) * 2012-11-19 2014-05-28 中国联合网络通信集团有限公司 数据传输方法、基站、管理控制中心和系统
WO2015055496A1 (en) * 2013-10-15 2015-04-23 Telefonaktiebolaget L M Ericsson (Publ) Performing an action on certain media streams in a multimedia communications network
CN107920372A (zh) * 2016-10-10 2018-04-17 电信科学技术研究院 一种信息指示方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15)", 3GPP STANDARD ; TECHNICAL SPECIFICATION ; 3GPP TS 23.501, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V1.4.0, 28 September 2017 (2017-09-28), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 151, XP051337397 *
HUAWEI, HISILICON, SAMSUNG?, SK TELECOM?: "OI#18 TS 23.501: Interaction between SMF and UPF on N4 Reference Point", 3GPP DRAFT; S2-177868 WAS7565-PCR-OI#18 23501_INTERACTION BETWEEN SMF AND UPF_R4, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Ljubljana, Slovenia; 20171023 - 20171027, 27 October 2017 (2017-10-27), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051346684 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114710810A (zh) * 2022-05-31 2022-07-05 新华三技术有限公司 一种数据传输方法、装置及系统
CN114710810B (zh) * 2022-05-31 2023-04-25 新华三技术有限公司 一种数据传输方法、装置及系统
CN116669134A (zh) * 2023-07-07 2023-08-29 中国电信股份有限公司 Smf网元与upf网元适配方法、装置、设备及介质
CN116669134B (zh) * 2023-07-07 2023-11-07 中国电信股份有限公司 Smf网元与upf网元适配方法、装置、设备及介质

Also Published As

Publication number Publication date
CN113225770A (zh) 2021-08-06

Similar Documents

Publication Publication Date Title
WO2021147402A1 (zh) 一种数据传输方法及装置
US11510131B2 (en) Configuration method, data transmission method, and apparatus
CN112106404B (zh) 用于在5g通信网络中通过iab节点路由数据的方法和系统
JP7541162B2 (ja) ルーティング方法及び装置
WO2021032131A1 (zh) 一种用户面信息上报方法及装置
WO2020019764A1 (zh) 信息传输方法、设备及计算机可读存储介质
JP2019533355A (ja) メッセージ送信方法および装置
CN110581778A (zh) 一种路由方法、bsr的生成方法、装置和存储介质
KR20160073227A (ko) 무선 통신 시스템에서 기지국과 단말 간 통신 방법을 결정하는 방법 및 장치
EP4106482A1 (en) Communication method and apparatus
WO2022016948A1 (zh) 一种通信方法及装置
WO2020098747A1 (zh) 传输路径的配置方法及装置
WO2020192654A1 (zh) 配置无线链路控制rlc承载的方法和装置
WO2022033543A1 (zh) 一种中继通信方法及通信装置
WO2021097858A1 (zh) 一种通信方法及装置
WO2021197269A1 (zh) 一种临近服务的数据传输方法、设备及系统
WO2021036910A1 (zh) 数据传输方法及装置
EP3962157B1 (en) Mdbv determining methods and apparatuses
WO2022237505A1 (zh) 一种通信方法、设备及系统
US20240080716A1 (en) Wireless communication method, communication apparatus, and communication system
WO2021204278A1 (zh) 一种流量控制方法和装置
KR20230091908A (ko) 패킷 리라우팅을 위한 방법 및 장치
WO2022082798A1 (zh) 通信方法及装置
WO2021189496A1 (zh) 用于网络切片的数据传输方法及设备
CN113645572B (zh) 一种通信方法、装置及存储介质

Legal Events

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

Ref document number: 20915111

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20915111

Country of ref document: EP

Kind code of ref document: A1