Data processing method, apparatus, and system

Abstract

This application provides a method, an apparatus, and a system for implementing service continuity in a data flow switch procedure. In the method, indication information is used to indicate a data flow for which an end marker message is used. In the data flow switch procedure, after receiving the end marker message, a source access network device (600, 900, 1100) can correctly identify, based on the indication information, the data flow on which the end marker message works, and can perform different processing on a data flow switched to a target access network device and a data flow kept on the source access network device (600, 900, 1100). According to the method, an end marker message used for a session is improved as an end marker message used for a data flow.

Description

Data processing methods, apparatus and systems

[0001] This application claims priority to Chinese Patent Application No. 201910819264.2, filed on August 31, 2019, entitled “Data Processing Method, Apparatus and System”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to wireless communication technology, and in particular to methods, apparatus and systems for data processing. Background Technology

[0003] In communication systems, the bandwidth resources and coverage of a single access network device are limited. Utilizing the radio resources of multiple access network devices to provide services to terminal devices through multiple connectivity methods can improve the data throughput, communication performance, and radio resource utilization of the terminal devices.

[0004] In a session established by a terminal device through a first access network device, a portion of the data stream can be switched from the first access network device to a second access network device. The terminal can receive different data streams of the same session from both the first and second access network devices. During this communication process, data stream transmission may be interrupted.

[0005] Summary of the Invention

[0006] This application provides a data processing method, apparatus, and system to avoid service interruption during data stream switching.

[0007] Firstly, a data processing method is provided, the method comprising:

[0008] The first access network device receives an end marker message from the core network element. The end marker message includes indication information, which is used to indicate the first data stream in the first session where the end marker message is active. The first data stream is the data stream switched from the first access network device to the second access network device.

[0009] The first access network device determines, based on the indication information, that the end marker message applies to the first data stream.

[0010] When the first access network device receives the second data packet of the second data stream after the end marker message, the first access network device sends the second data packet to the terminal device; wherein, the second data stream is the data stream maintained by the first access network device.

[0011] Based on this scheme, the first access network device can distinguish the data stream affected by the endmarker through the indication information contained in the endmarker message. Thus, after receiving the endmarker message, the first access network device continues to send data packets of the second data stream that are kept on the first access network device to the terminal device, without discarding the data packets of the second data stream, thereby avoiding the interruption of the transmission of the second data stream and ensuring the continuity of services.

[0012] In addition, if the first access network device receives the first data packet of the first data stream after the end marker message, the first access network device discards the first data packet.

[0013] As another way of describing the data processing method of the first aspect, the method includes:

[0014] The first access network device receives an end marker message from a core network element. The end marker message includes indication information, which indicates the data stream to which the end marker message applies. The data stream to which the end marker message applies is the first data stream during the first session when the device switches from the first access network device to the second access network device. The first access network device determines that the end marker message applies to the first data stream based on the indication information, so that the first access network device does not discard data packets of the second data stream that are held in the first access network device during the first session.

[0015] As another way to describe the data flow affected by the end marker message in the first aspect, the data flow affected by the end marker message can also be described as the data flow corresponding to the end marker message or the data flow associated with the end marker message; it can be understood that the end marker message affects the data flow that the end marker message affects, or the data flow that corresponds to or is associated with the end marker message.

[0016] In one possible implementation, the method further includes:

[0017] The first access network device forwards data packets of the first data stream to the second access network device. When the first access network device has finished forwarding the data packets of the first data stream received by the first access network device before the aforementioned end marker message, the first access network device sends a second end marker message to the second access network device. The second end marker message may be the aforementioned end marker message received by the first access network device; alternatively, the second end marker message may be generated by the second access network device, and may or may not include the aforementioned indication information.

[0018] In another possible implementation, the indication information may include the identifier of the data stream affected by the end marker message, for example, the indication information may include the identifier of a first data stream. When the data stream affected by the end marker message is multiple data streams, it may include the identifiers of multiple data streams. As a variation of this implementation, the indication information may include the identifier of the data stream to which the end marker message is not affected, for example, the indication information may include the identifier of a second data stream. The data stream to which the end marker message is affected can be determined by the identifier of the data stream to which the end marker message is not affected.

[0019] In another possible implementation, the indication information includes a bit sequence in which multiple bits correspond one-to-one with multiple data streams of the first session. The bit values ​​are either a first value or a second value, where the first value indicates that the bit is affected by the aforementioned end marker message, and the second value indicates that the bit is not affected by the aforementioned end marker message. Specifically, the bit corresponding to the first data stream has the first value, and the bit corresponding to the second data stream has the second value.

[0020] Based on this scheme, the indication information establishes a correspondence between multiple bits in a field and multiple data streams, which reduces the storage and transmission resources occupied by the indication information compared with the above-mentioned implementation method of including the identifier of the data stream in the end marker message.

[0021] In another possible implementation, the end marker message includes indication information including: the protocol header of the end marker message includes the aforementioned indication information; or, the content elements of the end marker message include the aforementioned indication information.

[0022] In another possible implementation, the first access network device is the main base station and the second access network device is the auxiliary base station; or, the first access network device is the auxiliary base station and the second access network device is the main base station.

[0023] In another possible implementation, the aforementioned core network element is a user plane function network element.

[0024] In another possible implementation, the aforementioned core network element is a session management function network element.

[0025] Secondly, a data processing method is provided, the method comprising:

[0026] The core network element obtains an end marker message, which includes indication information. This indication information is used to indicate the first data stream in which the end marker message acts in the first session. The first data stream is the data stream that is switched from the first access network device to the second access network device. The core network element sends the end marker message to the first access network device.

[0027] Based on this scheme, the core network element sends the aforementioned end marker message to the first access network device. The first access network device can distinguish the data stream affected by the end marker through the indication information contained in the end marker message. Thus, after receiving the end marker message, the first access network device continues to send data packets of the second data stream that are maintained on the first access network device to the terminal device, without discarding the data packets of the second data stream, thereby avoiding the interruption of the transmission of the second data stream and ensuring the continuity of services.

[0028] As another way to describe the data flow affected by the end marker message in the second aspect, the data flow affected by the end marker message can also be described as the data flow corresponding to the end marker message or the data flow associated with the end marker message; it can be understood that the end marker message affects the data flow that the end marker message affects, or the data flow that corresponds to or is associated with the end marker message.

[0029] In one possible implementation, the core network element obtaining the end marker message includes: the core network element generating the end marker message; or, the core network element receiving the end marker message from a control network element. For example, the core network element may be a user plane function network element, and the control network element may be a session management function network element.

[0030] In another possible implementation, the method further includes: after the end marker message, the core network element continues to send a second data packet of the second data stream in the first session to the first access network device, the second data stream being the data stream maintained at the first access network device.

[0031] In another possible implementation, the indication information may include the identifier of the data stream affected by the end marker message, for example, the indication information may include the identifier of a first data stream. When the data stream affected by the end marker message is multiple data streams, it may include the identifiers of multiple data streams. As a variation of this implementation, the indication information may include the identifier of the data stream to which the end marker message is not affected, for example, the indication information may include the identifier of a second data stream. The data stream to which the end marker message is affected can be determined by the identifier of the data stream to which the end marker message is not affected.

[0032] In another possible implementation, the indication information includes a bit sequence in which multiple bits correspond one-to-one with multiple data streams of the first session. The bit values ​​are either a first value or a second value, where the first value indicates that the bit is affected by the aforementioned end marker message, and the second value indicates that the bit is not affected by the aforementioned end marker message. Specifically, the bit corresponding to the first data stream has the first value, and the bit corresponding to the second data stream has the second value.

[0033] Based on this scheme, the indication information establishes a correspondence between multiple bits in a field and multiple data streams, which reduces the storage and transmission resources occupied by the indication information compared with the above-mentioned implementation method of including the identifier of the data stream in the end marker message.

[0034] In another possible implementation, the end marker message includes indication information, either in the protocol header of the end marker message or in the content elements of the end marker message.

[0035] In another possible implementation, the first access network device is the main base station and the second access network device is the auxiliary base station; or, the first access network device is the auxiliary base station and the second access network device is the main base station.

[0036] For detailed explanations of the implementation methods listed in the second aspect, please refer to the relevant content in the first aspect. The other implementation methods in the first aspect are also applicable to the second aspect.

[0037] Thirdly, a data processing method is provided, the method comprising:

[0038] The first access network device sends an indication message to the first core network element, which is used to indicate the first data stream to be switched in the first session;

[0039] The first access network device receives the end marker message from the second core network element;

[0040] The first access network device determines that the end marker message applies to the first data stream based on the first data stream;

[0041] When the first access network device receives the second data packet of the second data stream in the first session after the end marker message, the first access network device sends the second data packet to the terminal device; wherein, the second data stream is the data stream maintained by the first access network device.

[0042] As another description of the third aspect of the method, the method includes:

[0043] The first access network device receives indication information from the first core network element, which is used to indicate the first data stream switched out from the first access network device in the first session;

[0044] The first access network device determines that the end marker message applies to the first data stream based on the first data stream;

[0045] When the first access network device receives the second data packet of the second data stream in the first session after the end marker message, the first access network device sends the second data packet to the terminal device; wherein, the second data stream is the data stream held by the first access network device. Based on this scheme, the first access network device can correctly distinguish the data stream affected by the end marker message by knowing the data stream switched out from the first access network device. Therefore, after receiving the end marker message, the first access network device continues to send data packets of the second data stream held by the first access network device to the terminal device without discarding the data packets of the second data stream, thus avoiding the interruption of the second data stream transmission and ensuring service continuity.

[0046] The first access network device can learn about the data stream that has been switched out from the first access network device during the data stream switching process, and the specific method of learning is not limited.

[0047] Additionally, if the first access network device receives the first data packet of the first data stream after the end marker message, the first access network device discards the first data packet.

[0048] As another way to describe the data flow affected by the end marker message in the third aspect, the data flow affected by the end marker message can also be described as the data flow corresponding to the end marker message or the data flow associated with the end marker message; it can be understood that the end marker message affects the data flow that the end marker message affects, or the data flow that corresponds to or is associated with the end marker message.

[0049] In one possible implementation, the end marker message includes second indication information, which indicates that the end marker message applies to a portion of the data stream in the first session. The first access network device can determine from the second indication information that the end marker message does not apply to all the data streams in the first session, and therefore the first access network device can determine from the second indication information that the end marker message applies to the first data stream.

[0050] In one possible implementation, the end marker message includes second indication information to indicate a data flow switching scenario. Because a data flow switching scenario means the end marker message applies to a portion of the data flows in the first session, rather than all of them, the first access network device can use the second indication information to identify the data flow switched out from the first access network device as the data flow affected by the end marker message.

[0051] In another possible implementation, the first access network device is the main base station and the second access network device is the auxiliary base station; or, the first access network device is the auxiliary base station and the second access network device is the main base station.

[0052] In another possible implementation, the first core network element is a session management function network element, and the second core network element is a user plane function network element.

[0053] In another possible implementation, the first core network element is an access and mobility management function network element, and the second core network element is a user plane function network element.

[0054] For detailed explanations of the implementation methods listed in the third aspect, please refer to the relevant content in the first aspect. The other implementation methods in the first aspect are also applicable to the third aspect.

[0055] Fourthly, an access network apparatus is provided for implementing the method of the first aspect. The access network apparatus may be the first access network device in the first aspect, or an apparatus including the first access network device. The access network apparatus includes modules, units, or means corresponding to the above-described method, which may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above-described functions.

[0056] Fifthly, a core network apparatus is provided for implementing the method of the second aspect. The core network apparatus may be a core network element in the second aspect, or an apparatus containing the core network element. The core network apparatus includes modules, units, or means corresponding to the above-described method. These modules, units, or means may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above-described functions.

[0057] Sixthly, an access network apparatus is provided for implementing the method of the third aspect. The access network apparatus may be the first access network device in the third aspect, or an apparatus including the first access network device. The access network apparatus includes modules, units, or means corresponding to the above-described method, which may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above-described functions.

[0058] In a seventh aspect, an access network apparatus is provided, the apparatus comprising:

[0059] A processor for reading and executing instructions in memory to implement the method provided in the first aspect.

[0060] Optionally, the access network device may include the memory. Optionally, the access network device may be a base station or a chip.

[0061] Eighthly, a core network apparatus is provided, the apparatus comprising:

[0062] A processor for reading and executing instructions in memory to implement the method provided in the second aspect.

[0063] Optionally, the core network device may include the memory. Optionally, the core network device may be a core network element or a chip.

[0064] Ninthly, an access network apparatus is provided, the apparatus comprising:

[0065] A processor for reading and executing instructions from memory to implement the method provided by the third party.

[0066] Optionally, the access network device may include the memory. Optionally, the access network device may be a base station or a chip.

[0067] In a tenth aspect, a computer storage medium is provided, including instructions, characterized in that, when the instructions are executed on the access network device or the core network device, the device causes the device to implement any of the methods described above.

[0068] Eleventhly, embodiments of this application provide a computer program product, including instructions, characterized in that, when the instructions are executed on the aforementioned access network device or core network device, they cause the device to implement any of the aforementioned methods.

[0069] In the twelfth aspect, a communication system is provided, including an access network device of the fourth or seventh aspect and a core network device of the fifth or eighth aspect.

[0070] In a thirteenth aspect, a communication system is provided, including an access network apparatus as described in the sixth or ninth aspect. Optionally, the communication system may further include user plane function network elements. Optionally, the communication system may further include access and mobility management function network elements or session management function network elements.

[0071] The beneficial effects provided in aspects four through thirteen of this application can be referenced in the relevant content of aspects one through three. Attached Figure Description

[0072] Figure 1 shows a schematic diagram of the architecture of a 5G communication system provided in an embodiment of this application;

[0073] Figure 2 is a schematic diagram of a QoS stream transmission method provided in an embodiment of this application;

[0074] Figure 3 is a flowchart of a data processing method provided in an embodiment of this application;

[0075] Figure 4 shows a schematic diagram of the protocol header of an end marker message provided in an embodiment of this application;

[0076] Figure 5 shows a schematic diagram of the protocol header of another end marker message provided in an embodiment of this application;

[0077] Figure 6 is a schematic diagram of the content elements of an end marker message provided in an embodiment of this application;

[0078] Figure 7 shows a schematic diagram of the content elements of another end marker message provided in an embodiment of this application;

[0079] Figure 8 shows a flowchart of another data processing method provided in an embodiment of this application;

[0080] Figure 9 shows a schematic diagram of the protocol header of another end marker message provided in an embodiment of this application;

[0081] Figure 10 shows a flowchart of another data processing method provided in an embodiment of this application;

[0082] Figure 11 is a flowchart of another data processing method provided in an embodiment of this application;

[0083] Figure 12 shows a flowchart of another data processing method provided in an embodiment of this application;

[0084] Figure 13 is a schematic diagram of the structure of an access network device provided in an embodiment of this application;

[0085] Figure 14 is a schematic diagram of a core network device provided in an embodiment of this application;

[0086] Figure 15 shows a schematic diagram of another access network device provided in an embodiment of this application;

[0087] Figure 16 shows a schematic diagram of another core network device provided in an embodiment of this application;

[0088] Figure 17 shows a schematic diagram of another access network device provided in an embodiment of this application. Detailed Implementation

[0089] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0090] This application describes a technical solution based on a 5G communication system. Those skilled in the art will understand that, with the evolution and changes in communication technology, the solution of this application can also be applied to other communication systems, such as 6G communication systems; this application does not limit this application to such applications.

[0091] For ease of description, Table 1 lists the English abbreviations, their full English names, and their corresponding Chinese names used in this application.

[0092]

[0093]

[0094]

[0095] Table 1

[0096] Figure 1 illustrates a schematic diagram of a 5G communication system architecture, which includes a core network and an access network. The access network can also be called the Radio Access Network (RAN). The core network may include AMF, SMF, UPF, PCF, AUSF, UDM, and NSSF network elements. AF elements can connect to the PCF to provide application services. The UPF can connect to the DN. The UE can access the DN through this communication system.

[0097] An AMF (Access Default Mode) network element is a network element used for access and mobility management. This element is primarily used for access control, mobility management, attach and detach, and SMF (Signal Management Default Mode) element selection. It can also serve as an anchor point for N1 and N2 signaling connections, providing routing for N1 / N2SM messages to the SMF.

[0098] An SMF network element is a network element used for session management. This element primarily provides control plane functions for session management, such as session creation, modification, and release. It can also assign IP addresses to users and select and redirect UPF network elements.

[0099] A UPF (User Plane Processing) network element is a network element used for user plane processing. This element is primarily used for user plane service processing, such as packet routing and forwarding, QoS mapping, and execution. This element can receive user data from the DN (Network Data Center) and transmit it to the UE (User Equipment) through access network equipment; it can also receive user data from the UE through access network equipment and forward it to the DN. The transmission resources and scheduling functions providing services to the UE within this element are managed and controlled by the SMF (User Plane Processing) network element.

[0100] The PCF network element is a network element used for policy control. This element primarily provides a unified policy framework to manage network behavior, delivers policy rules to the control layer network functions, and is also responsible for acquiring user subscription information related to policy decisions.

[0101] The AUSF network element is a network element used for authentication. This network element is mainly used for access authentication.

[0102] A UDM network element is a network element used for data management. This element is primarily used to generate authentication parameters, store and manage the IDs of permanent users in the system, and manage the registration of user service network elements, such as the AMF and SMF currently providing services to terminal devices.

[0103] The NSSF network element is a network element used to select network slices. This network element is mainly used to determine the network slice instances that the UE is allowed to access.

[0104] Access network equipment is a device that provides wireless communication capabilities for terminal devices. Access network equipment includes, but is not limited to: evolved node B (eNB), radio network controller (RNC), node B (NB), donor evolved node B (DeNB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved node B, or home node B (HNB), base band unit (BBU), access point (AP) in a Wi-Fi system, wireless relay node, wireless backhaul node, transmission point (TP), or transmission and reception point (TRP), etc. It can also be a next-generation NB (gNB) or transmission point (such as TRP or TP) in 5G, such as a new radio (NR) system, an antenna panel of a base station in a 5G system (including multiple antenna panels), or a network node that constitutes a gNB or transmission point, such as a BBU or distributed unit (DU).

[0105] In some deployments, a gNB may include a centralized unit (CU) and a DU. A gNB may also include a radio unit (RU). The CU implements some of the gNB's functions, and the DU implements some of its functions; for example, the CU implements the RRC and PDCP layer functions, while the DU implements functions without the RLC, MAC, and PHY layers. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this architecture, higher-layer signaling, such as RRC or PDCP layer signaling, can also be considered to be sent by the DU, or by the DU+RU. It is understood that network devices can be CU nodes, DU nodes, or devices including both CU and DU nodes. Furthermore, the CU can be classified as a network device in the access network or a network device in the core network (CN); this is not a limitation.

[0106] An AF (Application Provider) network element is a network element used for application services. This element primarily interacts with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side.

[0107] DN is a type of data network. DN is primarily used to provide services to users, such as carrier services, internet access services, and third-party services.

[0108] A terminal device is a device with wireless transceiver capabilities, referred to as a UE in this embodiment. Terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water (such as ships); and they can be deployed in the air (e.g., on airplanes, balloons, and satellites). Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, VR terminals, AR terminals, wireless terminals in industrial control, wireless terminals in autonomous driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.

[0109] Access network equipment is connected to UPF via user plane interface N3 to transmit UE data; access network equipment establishes control plane signaling connection with AMF via control plane interface N2; AMF establishes signaling connection with UE via interface N1; AMF is connected to SMF via interface N11, and AMF acts as the anchor point for N1 and N2 signaling connections to provide routing for SM messages on interface N1 or N2 to SMF; UPF is connected to SMF via interface N4.

[0110] In this application embodiment, the session can be a PDU session in a 5G network; the data flow in this application embodiment can be a QoS flow in a 5G network. In a 5G network, a UE can simultaneously create multiple PDU sessions to access the same or different DNs, with each PDU session accessing one DN. The establishment of a PDU session means that a data transmission channel between the UE and the DN has been established. The smallest QoS distinction granularity in a PDU session is the QoS flow. A PDU session can include multiple QoS flows, and a QFI identifies a QoS flow, which is unique in each PDU session. The transmission unit of a QoS flow is a data packet. Data packets on the same QoS flow receive the same QoS guarantees (such as packet latency, packet error rate, priority, etc.), and different QoS guarantees require different QoS flows to provide them. As shown in Figure 2, a QoS flow can be mapped to a radio bearer, and a radio bearer can carry one or more QoS flows. In a single-connection scenario where the UE establishes a PDU session through an access network device, a PDU session uses one N3 tunnel, and multiple QoS flows in the PDU session share one N3 tunnel. Optionally, the N3 tunnel can be an NG-U tunnel. This tunnel uses the GTP-U protocol, which provides packet transmission and reception services for user plane entities. G-PDU messages containing a GTP-U header and T-PDU, as well as GTP-U signaling messages containing a GTP-U header and cells, can be transmitted through this tunnel. A T-PDU contains a user data packet, which can be an IP datagram.

[0111] A UE may receive signals from multiple access network devices with different frequency bands and strengths. A UE can simultaneously send and receive data on multiple access network devices, which is called multiple connections. Specifically, a UE establishing connections with two access network devices simultaneously and sending and receiving data through both connections is called dual connections. Those skilled in the art should understand that technical solutions applicable to dual-connectivity scenarios can also be applied to multi-connectivity scenarios. In a UE's PDU session, a portion of the QoS flow can be switched from the first access network device to the second access network device, while retaining a portion of the QoS flow in the session on the first access network device, enabling the QoS flow of the PDU session to be distributed across the two access network devices. Optionally, the first access network device can be a primary access network device, and the second access network device can be a secondary access network device. Alternatively, the first access network device can be a secondary access network device, and the second access network device can be a primary access network device. In this embodiment, the first access network device is the primary access network device, and the second access network device is the secondary access network device. For ease of description, the primary access network device is represented by an M-RAN node, and the secondary access network device is represented by an S-RAN node.

[0112] Based on the aforementioned 5G communication system, this application provides various embodiments to describe the technical solutions of this application in detail.

[0113] Example 1

[0114] Example 1 describes a QoS flow handover procedure in a dual-connectivity scenario. After establishing dual connectivity, the UE can use this QoS flow handover procedure to switch a portion of the QoS flow in a PDU session carried on the M-RAN node from the M-RAN node to the S-RAN node. In this procedure, the SMF or UPF generates an end marker message to be sent to the M-RAN node. As shown in Figure 3, it includes:

[0115] S101: The S-RAN node sends the data forwarding address to the M-RAN node.

[0116] M-RAN can forward data to S-RAN based on this forwarding address.

[0117] Optionally, the M-RAN node can forward data packets in the PDU session that are to be switched from the M-RAN node to the S-RAN node and whose QoS flow is cached in the M-RAN node to the S-RAN node; in addition, the M-RAN node can send data packets that are maintained in the M-RAN to the UE.

[0118] In this embodiment, the M-RAN node can be considered as the source node, and the S-RAN node can be considered as the target node.

[0119] S102: The M-RAN node sends N2 interface QoS Flow mobility Indication information to the AMF.

[0120] As an alternative, part S102 can be: the M-RAN node can send PDU session resource modification indication information to the AMF.

[0121] The two types of indication information mentioned above can include PDU Session ID, QFI(s), and AN Tunnel Info. The PDU Session ID indicates the PDU session containing the QoS flow to be switched. The QFI(s) indicates the QoS flow to be switched. The AN Tunnel Info indicates the downlink tunnel endpoint of the S-RAN node.

[0122] As an example, UE A establishes two PDU sessions in the 5G communication system, namely PSession#1 and PSession#2. PSession#1 includes two QoS flows, namely Qflow#1-1 and Qflow#1-2. PSession#2 includes four QoS flows, namely Qflow#2-1, Qflow#2-2, Qflow#2-3, and Qflow#2-4. The IDs of the above PDU sessions and QoS flows are shown in Table 2.

[0123]

[0124] Table 2

[0125] Assume that UE A's Qflow#2-1 and Qflow#2-2 need to switch to an S-RAN node, and the AN Tunnel Info of this S-RAN node is TInfo#02. In the aforementioned N2 interface service quality flow mobility indication information, the PDU Session ID is 010, the QFI is 00000001 and 00000010, and the AN Tunnel Info is TInfo#02.

[0126] For ease of explanation, the examples in the following steps of Embodiment 1 will be based on the above examples.

[0127] S103: AMF sends a PDU session update management context request (Nsmf_PDUSession_UpdateSMContext request) to SMF.

[0128] The request includes the aforementioned PDU Session ID, QFI(s), and AN Tunnel Info.

[0129] S104: SMF sends an N4 interface session modification request to UPF.

[0130] The request includes the aforementioned QFI(s) and AN Tunnel Info, as well as an identifier indicating the aforementioned PDU session information. This identifier can be an N4 interface session endpoint identifier, an N4 interface session identifier, or a PDU session ID. The N4 interface is the interface between the SMF and the UPF.

[0131] Specifically, after receiving the N4 interface session modification request, the UPF switches the QoS flow to be switched to the S-RAN node.

[0132] S105: After the QoS flow to be switched is switched, the UPF sends an N4 interface session modification response to the SMF.

[0133] S106: SMF sends a PDU session update management context response (Nsmf_PDUSession_UpdateSMContext response) to AMF.

[0134] Optionally, after the QoS flow to be switched is switched to the S-RAN node, the UPF can send data packets of the switched QoS flow to the S-RAN node; at the same time, the UPF can send data packets of the QoS flow that is maintained at the M-RAN node to the M-RAN node.

[0135] S107: SMF sends the first end marker message to UPF.

[0136] As an example, after receiving the N4 interface session modification response from the UPF, the SMF learns that the QoS flow to be switched has been switched to S-RAN, and the SMF can send the first end marker message to the UPF.

[0137] The first end marker message is generated by the SMF. This first end marker message includes indication information. This indication information indicates the QoS flow corresponding to the first end marker message (i.e., the QoS flow affected by the end marker message), which in a dual-connectivity scenario is a QoS flow switching from M-RAN to S-RAN. Optionally, the first end marker message may correspond to one or more QoS flows switching from M-RAN to S-RAN.

[0138] In this embodiment of the application, the data stream corresponding to the end marker message and the data stream affected by the end marker message have the same meaning, both indicating that the data stream is affected by the end marker message.

[0139] Optionally, the first end marker message can also be generated by the UPF. In this case, S107 can be expressed as: The UPF generates the first end marker message.

[0140] As an alternative interpretation, carrying the above indication information in the end marker message can be considered as the end marker message acting on the QoS flow indicated by the above indication information, and not on other QoS flows in the PDU session.

[0141] In S107, the QoS flow indicated by the above indication information may be a switched QoS flow.

[0142] S108: UPF sends the first end marker message to the M-RAN node.

[0143] Specifically, the M-RAN node learns from the indication information in the first end marker message that the QoS flow affected by the first end marker message in the above PDU session is a switched QoS flow, such as Qflow#2-1 and Qflow#2-2. Other QoS flows in the above PDU session are QoS flows that are maintained in the M-RAN node, referred to as maintained QoS flows.

[0144] Upon receiving the first end marker message, the M-RAN node may receive data packets of the switched QoS flow or data packets of the maintained QoS flow. Knowing the QoS flow affected by the first end marker message, the M-RAN node can handle data packets of different QoS flows differently, as shown in S108a and S108b (not shown in Figure 3).

[0145] S108a: M-RAN nodes discard packets of switched QoS flows received after the first end marker message.

[0146] After learning the QoS flow affected by the first end marker message, the M-RAN node can discard data packets received after the first end marker message that are part of the switched QoS flow affected by the first end marker message.

[0147] S108b: The M-RAN node continues to send data packets of the maintained data stream to the terminal equipment.

[0148] Since the M-RAN node can correctly distinguish the QoS flows not affected by the first end marker message after learning which QoS flows were affected, it can choose not to discard data packets of QoS flows received after the first end marker message that were not affected by it. In other words, the M-RAN node can continue to send data packets of QoS flows received after the first end marker message that were not affected by it to the UE.

[0149] In this embodiment of the application, for ease of description, the data stream that is switched from the first access network device to the second access network device is referred to as the switched data stream or the switched data stream; the data stream that remains on the first access network device (i.e., the data stream that has not been switched from the first access network device to the second access network device) is referred to as the unswitched data stream or the held data stream.

[0150] Optionally, the UPF can send multiple first end marker messages to the M-RAN node so that the M-RAN node can correctly receive the first end marker messages.

[0151] S109: The M-RAN node sends a second end marker message to the S-RAN node.

[0152] As an example, after the M-RAN node has completed forwarding the data packets of the aforementioned switched QoS flow to the S-RAN node, it can send a second end marker message to the S-RAN node.

[0153] Optionally, the second end marker message can be the first end marker message already received by the M-RAN.

[0154] Optionally, the second end marker message can be generated by the M-RAN node, and the second end marker message may or may not carry the aforementioned indication information.

[0155] The second end marker message is used to indicate that the M-RAN node has stopped forwarding the data packets of the QoS flow that has been switched to the S-RAN node to the S-RAN node. The second end marker message can assist the S-RAN node in reordering the data packets of the switched QoS flow, ensuring that the data packets received by the S-RAN node from the M-RAN node are sent to the UE before the data packets received from the UPF.

[0156] S110: AMF sends QoS handover confirmation information to the M-RAN node.

[0157] Optionally, S110 may be executed at any time after S106, and this embodiment of the application does not limit this.

[0158] In this embodiment, the indication information included in the first end marker message can be designed in three ways. Furthermore, the design of the second end marker message can also refer to the design of the first end marker message.

[0159] The first design: The indication information included in the first end marker message can be the QFI value of a QoS flow that has been switched in the PDU session. In the first design, one indication message corresponds to one QoS flow.

[0160] The second design: The indication information included in the first end marker message can be a QFI list consisting of the QFI values ​​of all switched QoS flows in the PDU session. One indication information can correspond to multiple QoS flows.

[0161] The third design: The indication information included in the first end marker message can be a bit sequence or a bitmap. The bits used in the bit sequence correspond one-to-one with the QoS stream, and different values ​​of the bits indicate whether the first end marker message corresponds to the aforementioned QoS stream.

[0162] As a first alternative implementation, the aforementioned first end marker message can be a GTP-U signaling message, and the aforementioned indication information can be carried in the GTP-U protocol header of the first end marker message.

[0163] Based on the design of the first type of indication information described above, a QFI field is included in the GTP-U protocol header of the first end marker message as the aforementioned indication information, as shown in Figure 4. The number of bits occupied by this QFI field is not limited; this embodiment uses an 8-bit QFI field as an example.

[0164] For example, based on the example of S102 above, in S107 above, the SMF or UPF generates two end marker messages. In the GTP-U protocol header of the first generated end marker message, the tunnel endpoint identifier is set to the tunnel endpoint identifier 0xABCDEF00 assigned by the M-RAN node to PSession#2, and the QFI is set to 00000001; in the protocol header of the second generated end marker message, the tunnel endpoint identifier is set to 0xABCDEF00, and the QFI is set to 00000010.

[0165] In S108, the M-RAN receives the two first end marker messages mentioned above, obtains the values ​​of the tunnel endpoint identifier and QFI field in their protocol headers, and learns that the two end markers are applied to QoS flows Qflow#2-1 and Qflow#2-2 respectively.

[0166] Based on the second design described above, a QFIs list is included in the GTP-U protocol header of the first end marker message as the aforementioned indication information, as shown in Figure 5. The number of bits occupied by this QFIs list is not limited; this embodiment uses 16 bits as an example.

[0167] For example, based on the example in S102 above, in S107 above, the SMF or UPF generates an end marker message. In the GTP-U protocol header of this message, the tunnel endpoint identifier is set to the tunnel endpoint identifier 0xABCDEF00 assigned by the M-RAN node to PSession#2, and the QFIs list contains two values: 00000001 and 00000010.

[0168] In S108, the M-RAN receives the first end marker message mentioned above, obtains the tunnel endpoint identifier and the value contained in the QFIs list in its protocol header, and learns that the end marker applies to QoS flows Qflow#2-1 and Qflow#2-2.

[0169] Based on the third design described above, a QFI field is included in the GTP-U protocol header of the first end marker message as the aforementioned indication information, as shown in Figure 4. The number of bits occupied by this QFI field is not limited; this embodiment uses an 8-bit QFI field as an example. The QFI field is a bit sequence, where the least significant bit corresponds to the QoS flow with the smallest QFI value in the PDU session. The other bits in the bit sequence correspond to other QoS flows in sequence. A bit value of 1 indicates that the first end marker message applies to the QoS flow corresponding to that bit, while a bit value of 0 indicates that the first end marker message does not apply to the QoS flow corresponding to that bit.

[0170] For example, based on the example of S102 above, in S107 above, the SMF generates a first end marker message. In the protocol header of this data packet, the tunnel endpoint identifier is set to the tunnel endpoint identifier 0xABCDEF00 assigned by the M-RAN node to PSession#2, and the QFI field is set to XXXX0011. The number of QoS flows in PSession#2 is less than 8, only 4, so the lower 4 bits of the QFI field are used, and the higher 4 bits can be used for padding (represented by X).

[0171] In S107, the M-RAN receives the aforementioned end marker message, obtains the values ​​of the tunnel endpoint identifier and QFI field in the protocol header of the data packet, and learns that the end marker applies to both Qflow#2-1 and Qflow#2-2.

[0172] As a second alternative implementation, the first end marker message can be a GTP-U signaling message, and the indication information can be carried in the content information element (Content IE) of the first end marker message.

[0173] Based on the first design described above, a QFI field is included in the content cell of the first end marker message as the aforementioned indication information, as shown in Figure 6. The number of bits occupied by this QFI field is not limited.

[0174] Based on the second design described above, a QFIs list is included in the content cell of the first end marker message as the aforementioned indication information, as shown in Figure 7. The number of bits occupied by this QFIs list is not limited.

[0175] Based on the third design described above, a QFI field is included in the content element of the first end marker message as the aforementioned indication information, as shown in Figure 6.

[0176] Those skilled in the art will recognize that the first design described above can be modified accordingly. For example, in the first design, the indication information included in the first end marker message can be the QFI value of the QoS flow that has not been switched in the PDU session. Through modifications to the first design, the M-RAN node can also correctly distinguish the QoS flow in the PDU session that has been switched to the S-RAN node.

[0177] Through S108 described above, the M-RAN node can distinguish the QoS flow of the PDU session to which the end marker operates based on the indication information included in the first end marker message. After knowing the QoS flow in the PDU session to which the end marker operates, when the M-RAN node receives a data packet of the QoS flow that has not been switched to the S-RAN node after the end marker message, it will not discard the data packet of the QoS flow that has not been switched to the S-RAN node, but will instead send the data packet of the QoS flow that has not been switched to the S-RAN node to the UE. In this way, the data packets of the QoS flow that have not been switched to the S-RAN node received after the end marker message will not be erroneously discarded, thus ensuring service continuity.

[0178] Example 2

[0179] Example 2 describes another QoS flow switching procedure in a dual-connectivity scenario. Similar to Example 1, after establishing dual connectivity, the UE can use this QoS flow switching procedure to switch a portion of the QoS flow in a PDU session carried on the M-RAN node from the M-RAN node to the S-RAN node. Unlike Example 1, the end marker message in Example 2 may not include the indication information found in Example 1. Instead, the M-RAN node determines the QoS flow corresponding to the end marker message based on the QoS flow information stored on the M-RAN. As shown in Figure 8, it includes:

[0180] S201: The S-RAN node sends the data forwarding address to the M-RAN node.

[0181] For details, please refer to S101.

[0182] S202: The M-RAN node sends the N2 interface service quality flow movement indication information to the AMF.

[0183] For details, please refer to S102.

[0184] Optionally, the M-RAN node stores QoS flow information. This QoS flow information is used to indicate the QoS flow to be switched in the session. The design of this QoS flow information can refer to the three designs of the indication information included in the first end marker message in Embodiment 1. Optionally, the QoS flow information can also be stored on other network elements, and the M-RAN node can obtain the above-mentioned QoS flow information when needed.

[0185] S203: AMF sends a PDU session update management context request to SMF.

[0186] For details, please refer to S103.

[0187] S204: SMF sends an N4 interface session modification request to UPF.

[0188] For details, please refer to S104.

[0189] S205: After the QoS flow to be switched is switched, the UPF sends an N4 interface session modification response to the SMF.

[0190] For details, please refer to S105.

[0191] S206: SMF sends a PDU session update management context response to AMF.

[0192] For details, please refer to S106.

[0193] S207: SMF sends the first end marker message to UPF.

[0194] For details, please refer to S107. Unlike S107, the first end marker message in Embodiment 2 does not include the indication information in Embodiment 1.

[0195] Optionally, the first end marker message can also be generated by the UPF. In this case, S107 can be expressed as: The UPF generates the first end marker message.

[0196] Optionally, the first end marker message may contain another type of indication information. This indication information is used to indicate whether the first end marker message applies to all QoS flows in the PDU session; or, in a dual-connectivity scenario, it can be understood that the indication information is used to indicate that the first end marker message applies to the data flow being switched. The first access network device determines, based on this indication information, that the end marker message applies to the data flow being switched from the M-RAN node to the S-RAN node. As an example, an indicator field can be included in the GTP-U protocol header of the first end marker message as this indication information, as shown in Figure 9. The number of bits occupied by the indicator field is not limited; in this embodiment, an indicator field occupying 1 bit is used as an example. As an example: when the indicator value is 0, it indicates that the end marker message applies to all QoS flows in the PDU session; when the indicator value is 1, it indicates that the end marker message applies to some QoS flows in the PDU session, not all QoS flows. The examples of indicator values ​​and their meanings in this application are only for better illustration of the scheme and do not constitute a limitation on the indicator values.

[0197] Optionally, the first end marker message may not contain the aforementioned indication information; that is, the first end marker message may use the relevant data structure in communication protocols such as 3GPP TS 29.281 v11.6.0. When the first access network device receives the first end marker message, the M-RAN node can determine which QoS flows are being switched based on the QoS flow information stored in the M-RAN node, and then apply the first end marker message to the switched QoS flows.

[0198] S208: UPF sends the first end marker message to the M-RAN node.

[0199] Specifically, the M-RAN node learns from the QoS flow information in S202 and the first end marker message that the QoS flow affected by the first end marker message in the PDU session is the switched QoS flow, and other QoS flows in the PDU session are QoS flows that are maintained in the M-RAN node, referred to as maintained QoS flows.

[0200] Upon receiving the first end marker message, the M-RAN node may receive data packets of the switched QoS flow or data packets of the maintained QoS flow. Knowing the QoS flow affected by the first end marker message, the M-RAN node can handle data packets of different QoS flows differently, as shown in S208a and S208b (not shown in Figure 8).

[0201] S208a: M-RAN nodes discard packets of switched QoS flows received after the first end marker message.

[0202] After learning the QoS flow affected by the first end marker message, the M-RAN node can discard data packets received after the first end marker message that are part of the switched QoS flow affected by the first end marker message.

[0203] S208b: The M-RAN node continues to send data packets of the maintained data stream to the terminal equipment.

[0204] Since the M-RAN node can correctly distinguish the QoS flows not affected by the first end marker message after learning which QoS flows were affected, it can choose not to discard data packets of QoS flows received after the first end marker message that were not affected by it. In other words, the M-RAN node can continue to send data packets of QoS flows received after the first end marker message that were not affected by it to the UE.

[0205] In this embodiment of the application, for ease of description, the data stream that is switched from the first access network device to the second access network device is referred to as the switched data stream or the switched data stream; the data stream that remains on the first access network device (i.e., the data stream that has not been switched from the first access network device to the second access network device) is referred to as the unswitched data stream or the held data stream.

[0206] Based on the example of S207, when the first end marker message includes the indication information in S207, if the indicator value in the GTP-U protocol header of the end marker message received by the M-RAN node is 0, the M-RAN node directly discards the data packets that arrive after the PDU session in the end marker message; if the indicator value in the GTP-U protocol header of the end marker message received by the M-RAN node is 1, the M-RAN node learns the QoS flow information in S202 and the first end marker message to determine the QoS flow affected by the first end marker message, and executes S208a and / or S208b.

[0207] Optionally, the UPF can send multiple first end marker messages to the M-RAN node so that the M-RAN node can correctly receive the first end marker messages.

[0208] S209: The M-RAN node sends a second end marker message to the S-RAN node.

[0209] For details, please refer to S109.

[0210] S210: AMF sends QoS handover confirmation information to the M-RAN node.

[0211] For details, please refer to S110.

[0212] Optionally, S210 can be executed at any time after S206, and this embodiment of the application does not limit this.

[0213] Optionally, the M-RAN node can save the QoS flow information after receiving the QoS handover confirmation information.

[0214] Using the saved QoS flow information of the QoS flows to be switched in the indication session, in S208, the M-RAN node can distinguish the QoS flows in the PDU session that have been switched to the S-RAN node. After learning that the QoS flows in the PDU session have been switched to the S-RAN node, when the M-RAN node receives data packets of QoS flows that have not been switched to the S-RAN node after the end marker message, it will not discard the data packets of the QoS flows that have not been switched to the S-RAN node, but will instead send the data packets of the QoS flows that have not been switched to the S-RAN node to the UE; in this way, the data packets of QoS flows that have not been switched to the S-RAN node received after the end marker message will not be erroneously discarded, thus ensuring service continuity.

[0215] Example 3

[0216] Example 3, based on Example 1, describes a data processing method provided by this application from the perspective of the source node. As shown in Figure 10, the method includes:

[0217] S301: The first access network device receives the end marker message from the core network element.

[0218] The end marker message includes indication information, which is used to indicate the first data stream in which the end marker message acts in the first session; the first data stream is the first data stream switched from the first access network device to the second access network device.

[0219] The first access network device can be the M-RAN node in Figure 3, the second access network device can be the S-RAN node in Figure 3, the core network element can be the UPF in Figure 3, the end marker message can be the first end marker message in Figure 3, the first session can be the Packet Data Unit Session (PDU Session) in Embodiment 1, the data stream can be the QoS stream in Embodiment 1, and the first data stream can be the switched QoS stream in Figure 3. For detailed explanations, please refer to Embodiment 1, which will not be repeated here.

[0220] For details regarding S301, please refer to the relevant explanations in S108; they will not be repeated here.

[0221] S302: When the first access network device receives the second data packet of the second data stream in the first session after the above end marker message, the first access network device continues to send the second data packet to the terminal device.

[0222] The second data stream is the data stream that is maintained at the first access network device.

[0223] The first access network device can determine that the end marker message applies to the first data stream based on the indication information included in the end marker message. Since the end marker message applies to the first data stream, it does not apply to other data streams in the first session besides the first data stream.

[0224] For details regarding S302, please refer to the relevant explanations of S108, S108a, and S108b; they will not be repeated here.

[0225] Optionally, S302 further includes: when the first access network device receives the first data packet of the first data stream after the aforementioned end marker message, the first access network device discards the first data packet. For details, please refer to the relevant description of S108a, which will not be repeated here.

[0226] Optionally, the above indication information includes: the identifier of the first data stream.

[0227] Optionally, the above indication information includes: a bit sequence, wherein multiple bits in the bit sequence correspond one-to-one with multiple data streams of the first session, and the bit bit takes a first value or a second value, wherein the first value indicates that it is affected by the end marker message, and the second value is used to indicate that it is not affected by the end marker message; wherein the bit bit corresponding to the first data stream takes the first value, and the bit bit corresponding to the second data stream takes the second value.

[0228] The design of the above-mentioned instruction information can refer to the relevant description of the instruction information design in Embodiment 1, which will not be repeated here.

[0229] Optionally, the end marker message may include indication information, such that the protocol header of the end marker message includes the indication information; or, the content elements of the end marker message include the indication information. For details, please refer to the description of the implementation of the end marker message in Embodiment 1, which will not be repeated here.

[0230] In this embodiment, the first access network device can distinguish the data stream that has been switched to the second access network device in the first session based on the indication information included in the first end marker message. After learning that the first data stream in the first session has been switched to the second access network device, when the first access network device receives a data packet of the second data stream that has not been switched to the second access network device after the end marker message, it will not discard the data packet of the second data stream, but will continue to send the data packet of the second data stream to the terminal device; in this way, the data packets of the second data stream received after the end marker message will not be erroneously discarded, thus ensuring the continuity of services.

[0231] Example 4

[0232] Example 4, based on Example 1, describes a data processing method provided by this application from the perspective of core network elements. As shown in Figure 11, the method includes:

[0233] S401: Core network elements obtain end marker messages.

[0234] The end marker message includes indication information, which is used to indicate the first data stream in which the end marker message acts in the first session; the first data stream is the first data stream switched from the first access network device to the second access network device.

[0235] The first access network device can be the M-RAN node in Figure 3, the second access network device can be the S-RAN node in Figure 3, the core network element can be the UPF in Figure 3, the end marker message can be the first end marker message in Figure 3, the first session can be the Packet Data Unit Session (PDU Session) in Embodiment 1, the data stream can be the QoS stream in Embodiment 1, and the first data stream can be the switched QoS stream in Figure 3. For detailed explanations, please refer to Embodiment 1, which will not be repeated here.

[0236] S402: The core network element sends the above end marker message to the first access network device.

[0237] For details regarding S402, please refer to the relevant explanations of S108, S108a, and S108b; they will not be repeated here.

[0238] Optionally, S401 further includes: the core network element generating the end marker message; or, the core network element receiving the end marker message from the control network element. The control network element may be a session management function network element. For details, please refer to the relevant description in S107, which will not be repeated here.

[0239] Optionally, S402 further includes: after the aforementioned end marker message, the core network element continues to send the second data packet of the second data stream of the first session to the first access network device, wherein the second data stream is the data stream maintained at the first access network device. For details, please refer to the relevant description in S108b, which will not be elaborated here.

[0240] Optionally, the above indication information includes: the identifier of the first data stream.

[0241] Optionally, the above indication information includes: a bit sequence, wherein multiple bits in the bit sequence correspond one-to-one with multiple data streams of the first session, and the bit bit takes a first value or a second value, wherein the first value indicates that it is affected by the end marker message, and the second value is used to indicate that it is not affected by the end marker message; wherein the bit bit corresponding to the first data stream takes the first value, and the bit bit corresponding to the second data stream takes the second value.

[0242] The design of the above-mentioned instruction information can refer to the relevant description of the instruction information design in Embodiment 1, which will not be repeated here.

[0243] Optionally, the end marker message may include indication information, such that the protocol header of the end marker message includes the indication information; or, the content elements of the end marker message include the indication information. For details, please refer to the description of the implementation of the end marker message in Embodiment 1, which will not be repeated here.

[0244] Based on this scheme, the core network element sends the aforementioned end marker message to the first access network device. The first access network device can distinguish the data stream affected by the end marker through the indication information contained in the end marker message. Thus, after receiving the end marker message, the first access network device continues to send data packets of the second data stream that are maintained on the first access network device to the terminal device, without discarding the data packets of the second data stream, thereby avoiding the interruption of the transmission of the second data stream and ensuring the continuity of services.

[0245] Example 5

[0246] Example 5, based on Example 2, describes a data processing method provided by this application from the perspective of the source node. As shown in Figure 12, the method includes:

[0247] S501: The first access network device sends an indication message to the first core network element. See S202 for details.

[0248] The indication information is used to indicate the first data stream in the first session that is to be switched to the second access network device.

[0249] The first access network device can be the M-RAN node in Figure 8, the second access network device can be the S-RAN node in Figure 8, the first core network element can be the AMF in Figure 8, the end marker message can be the first end marker message in Figure 8, the first session can be the Packet Data Unit Session (PDU Session) in Embodiment 2, the data stream can be the QoS stream in Embodiment 2, and the first data stream can be the QoS stream to be switched in Embodiment 2.

[0250] For a detailed explanation of S501, please refer to S202; it will not be repeated here.

[0251] S502: The first access network device receives the end marker message from the second core network element.

[0252] The second core network element can be the UPF shown in Figure 8.

[0253] For a detailed explanation of S502, please refer to S208; it will not be repeated here.

[0254] S503: After receiving the second data packet of the second data stream in the first session after the above-mentioned end marker message, the first access network device sends the second data packet to the terminal device.

[0255] The second data stream is the data stream maintained at the first access network device. For a detailed explanation of S505, please refer to S208, S208a, and S208b, which will not be repeated here.

[0256] The first access network device can determine whether the end marker message applies to the first data stream to be switched. Since the end marker message applies to the first data stream, it does not apply to other data streams in the first session besides the first data stream. See S208 for details, which will not be elaborated here.

[0257] Optionally, S501 can also be: the first access network device receives indication information from the first core network element, the indication information being used to indicate the first data stream switched out from the first access network device in the first session. See S210 for details, which will not be elaborated here.

[0258] The first access network device can determine that the end marker message applies to the first data stream that has been switched over. Since the end marker message applies to the first data stream, it does not apply to other data streams in the first session besides the first data stream. See S208 for details, which will not be elaborated here.

[0259] Optionally, S501 further includes: the first access network device can learn about the data flow switched from the first access network device during the data flow switching process, and the specific method of learning is not limited. For details, please refer to S202 and S210, which will not be repeated here.

[0260] Optionally, the aforementioned end marker message includes: second indication information, which is used to indicate a data flow switching scenario. Because a data flow switching scenario means that the end marker message applies to a portion of the data flows in the first session, rather than all the data flows in the first session, the first access network device can use the second indication information to identify the data flows switched out from the first access network device as the data flows affected by the end marker message. For a detailed explanation, please refer to S207, which will not be elaborated upon here.

[0261] Optionally, S503 includes: the first access network device receiving the first data packet of the first data stream after the end marker message, and the first access network device discarding the first data packet. For a detailed explanation, please refer to S208a, which will not be repeated here.

[0262] Based on this scheme, the first access network device can correctly distinguish the data stream affected by the end marker by knowing the data stream switched out from the first access network device. Thus, after receiving the end marker message, the first access network device continues to send data packets of the second data stream that are still on the first access network device to the terminal device, without discarding the data packets of the second data stream, thereby avoiding the interruption of the transmission of the second data stream and ensuring the continuity of services.

[0263] Example 6

[0264] This embodiment provides an access network device that can be used to implement, for example, the function of the M-RAN node in Embodiment 1, or the function of the first access network device in Embodiment 3. Figure 13 shows a schematic diagram of the structure of the access network device 600 provided in this embodiment. The access network device 600 includes an antenna 601, a radio frequency (RF) device 602, and a baseband device 603. The antenna 601 is connected to the RF device 602. In the uplink direction, the RF device 602 receives information sent by the terminal device through the antenna 601 and sends the information sent by the terminal device to the baseband device 603 for processing. In the downlink direction, the baseband device 603 processes the information of the terminal device and sends it to the RF device 602, which then processes the information of the terminal device and sends it to the terminal device through the antenna 601.

[0265] The baseband device 603 may include one or more processing elements 6031, such as a main control CPU and other integrated circuits. Furthermore, the baseband device 603 may also include a storage element 6032 and an interface 6033. The storage element 6032 stores computer execution instructions for implementing the scheme of this application, and its execution is controlled by the processing element 6031. The interface 6033 is used to interact with the radio frequency device 602, and this interface is, for example, a common public radio interface (CPRI). The processing element 6031 executes the computer execution instructions stored in the storage element 6032, thereby realizing the function of the M-RAN node in Embodiment 1 of this application, or the function of the first access network device in Embodiment 3. The computer execution instructions in the embodiments of this application may also be referred to as application code, and this application does not specifically limit this. The methods and / or steps implemented by the M-RAN node in Embodiment 1 or the first access network device in Embodiment 3 can also be implemented by a chip on the baseband device 603. The chip includes at least one processing element and an interface circuit, wherein the processing element is used to execute each step of any of the methods executed by the M-RAN node or the first access network device, and the interface circuit is used to communicate with other devices.

[0266] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0267] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0268] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatus, and methods can be implemented in other ways. The units described as separate components may or may not be physically separate; the components shown as units may or may not be physical units, i.e., they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0269] The access network device 600 described above can be a general-purpose device or a special-purpose device. For example, the access network device 600 can be a network server, a base station, or a device with a similar structure to that shown in Figure 13. This application does not limit the type of access network device 600.

[0270] It is understood that the methods and / or steps implemented by the M-RAN node in Embodiment 1 or the first access network device in Embodiment 3 can also be implemented by a chip system that implements the functions of the M-RAN node in Embodiment 1 or the first access network device in Embodiment 3.

[0271] Example 7

[0272] This embodiment provides a core network device that can be used to implement, for example, the UPF function in Embodiment 1, or the core network element function in Embodiment 4. This core network device can be deployed on the core network side. Figure 14 shows a schematic diagram of the structure of the core network device 700 provided in this embodiment. The core network device 700 includes one or more processors 701, communication lines 702, and at least one communication interface (Figure 14 is only an example illustrating the inclusion of a communication interface 703 and a processor 701), and optionally may also include a memory 704.

[0273] The processor 701 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present application.

[0274] Communication line 702 is used to connect different components.

[0275] The communication interface 703 can be a transceiver module used to communicate with other devices, communication equipment, or communication networks, such as Ethernet. For example, the transceiver module can be a network interface card (NIC) or a fiber optic switch. Optionally, the communication interface 703 can also be a transceiver circuit located within the processor 701, used to implement the processor's signal input and signal output.

[0276] The memory 704 can be a device with storage functionality. For example, it can be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions; random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions; electrically erasable programmable read-only memory (EEPROM); compact disc read-only memory (CD-ROM) or other optical disc storage; optical disc storage (including compressed optical discs, laser discs, optical discs, digital versatile optical discs, Blu-ray discs, etc.); magnetic disk storage media or other magnetic storage devices; or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory can exist independently and be connected to the processor via a communication line 702. The memory can also be integrated with the processor.

[0277] The memory 704 stores computer execution instructions for implementing the scheme of this application, and the processor 701 controls the execution. The processor 701 executes the computer execution instructions stored in the memory 704 to realize the function of the UPF in Embodiment 1 of this application, or the function of the core network element in Embodiment 4. The computer execution instructions in the embodiments of this application can also be referred to as application code, and this application does not specifically limit this.

[0278] In a specific implementation, as one example, processor 701 may include one or more CPUs, such as CPU0 and CPU1 in FIG14.

[0279] In a specific implementation, as one embodiment, the communication device 700 may include multiple processors, such as processors 701 and 705 in FIG. 14. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. Here, a processor may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0280] The core network device 700 described above can be a general-purpose device or a special-purpose device. For example, the core network device 700 can be a network server, an embedded device, or a device with a similar structure to that in Figure 14. This application does not limit the type of core network device 700.

[0281] It is understood that the methods and / or steps implemented by the UPF in Embodiment 1 above, or the methods and / or steps implemented by the core network element in Embodiment 3 above, can also be implemented by the chip system that implements the functions of the UPF or core network element described above.

[0282] Example 8

[0283] This embodiment provides an access network device that can be used to implement, for example, the function of the M-RAN node in Embodiment 2, or the function of the first access network device in Embodiment 5. A schematic diagram of the access network device provided in this embodiment can be found in Figure 13.

[0284] The processing element of the baseband device executes computer execution instructions stored in the storage element of the baseband device, thereby realizing the function of the M-RAN node in Embodiment 2 of this application, or the function of the first access network device in Embodiment 5. The computer execution instructions in this application embodiment can also be referred to as application code, and this application embodiment does not specifically limit this. The methods and / or steps implemented by the M-RAN node in Embodiment 2 or the first access network device in Embodiment 3 can also be implemented by a chip on the baseband device. This chip includes at least one processing element and an interface circuit, wherein the processing element is used to execute the steps of any method executed by the M-RAN node in Embodiment 2 or the first access network device in Embodiment 5, and the interface circuit is used to communicate with other devices.

[0285] It is understood that the methods and / or steps implemented by the M-RAN node in Embodiment 2 or the first access network device in Embodiment 5 can also be implemented by a chip system that implements the functions of the M-RAN node in Embodiment 2 or the first access network device in Embodiment 5.

[0286] Example 9

[0287] This embodiment provides an access network device that can be used to implement, for example, the functions of an M-RAN node in Embodiment 1, or the functions of a first access network device in Embodiment 3. This application embodiment can divide the access network device into functional units according to the above method embodiments. For example, each function can be divided into separate functional units, or two or more units can be integrated into a single processing module. The integrated units can be implemented in hardware or as software functional modules. It should be noted that the unit division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0288] Figure 15 shows a schematic diagram of the structure of an access network device 900 provided in an embodiment of this application. The access network device 900 includes a processing unit 901 and a transceiver unit 902.

[0289] Optionally, the processing unit 901 is specifically used for: the function of determining the switched data stream according to the indication information in the end marker message in S108 and S302.

[0290] Optionally, the processing unit 901 is specifically used for: the function of discarding data packets of the switched data stream in S108a and S302.

[0291] Optionally, the transceiver unit 902 is specifically used for: receiving the data forwarding address in S101.

[0292] Optionally, the transceiver unit 902 is specifically used for: sending the buffered data packets of the QoS stream to be switched in S101.

[0293] Optionally, the transceiver unit 902 is specifically used for: sending N2 interface service quality flow movement indication information in S102.

[0294] Optionally, the transceiver unit 902 is specifically used for receiving end marker messages in S108 and S301.

[0295] Optionally, the transceiver unit 902 is specifically used for: sending data packets of the second data stream in S108 and S302.

[0296] Optionally, the transceiver unit 902 is specifically used for: sending the second end marker message in S109.

[0297] Optionally, the transceiver unit 902 is specifically used for: receiving QoS handover confirmation information in S110.

[0298] Specifically, the functions / implementation processes of the transceiver unit 902 and processing unit 901 in Figure 15 can be implemented by the processor 601 in the access network device 600 shown in Figure 13 calling computer execution instructions stored in the memory 604. Alternatively, the functions / implementation processes of the processing unit 901 in Figure 15 can be implemented by the processor 601 in the access network device 600 shown in Figure 13 calling computer execution instructions stored in the memory 604, and the functions / implementation processes of the transceiver unit 902 in Figure 15 can be implemented by the communication interface 603 in the access network device 600 shown in Figure 13.

[0299] Specifically, the functions / implementation processes of the transceiver unit 902 and processing unit 901 in Figure 15 can be implemented by the processing element 6031 of the baseband device 603 in the access network device 600 shown in Figure 13 calling the computer execution instructions stored in the storage element 6032. Alternatively, the functions / implementation processes of the processing unit 901 in Figure 15 can be implemented by the processing element 6031 of the baseband device 603 in the access network device 600 shown in Figure 13 calling the computer execution instructions stored in the storage element 6032, and the functions / implementation processes of the transceiver unit 902 in Figure 15 can be implemented by the interface 6033, the radio frequency device 602, and the antenna 601 in the access network device 600 shown in Figure 13.

[0300] Example 10

[0301] This embodiment provides a core network device that can be used to implement, for example, the UPF function in Embodiment 1, or the core network element function in Embodiment 4. This application embodiment can divide the core network device into functional units according to the above method embodiments. For example, each function can be divided into separate functional units, or two or more units can be integrated into a single processing module. The integrated units can be implemented in hardware or as software functional modules. It should be noted that the unit division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0302] Figure 16 is a schematic diagram of the structure of the access network device 1000 provided in an embodiment of this application. The core network device 1000 includes a processing unit 1001 and a transceiver unit 1002.

[0303] Optionally, the processing unit 1001 is specifically used for: the function of switching the QoS flow to be switched to the S-RAN node in S104.

[0304] Optionally, the processing unit 1001 is specifically used for: generating the end marker message in S107 and S401.

[0305] Optionally, the transceiver unit 1002 is specifically used for: receiving the N4 interface session modification request in S104.

[0306] Optionally, the transceiver unit 1002 is specifically used for: sending the N4 interface session modification response in S105.

[0307] Optionally, the transceiver unit 1002 is specifically used for: receiving the end marker message in S107.

[0308] Optionally, the transceiver unit 1002 is specifically used for: sending the end marker message in S108 and S401.

[0309] Specifically, the functions / implementation processes of the transceiver unit 1002 and processing unit 1001 in Figure 16 can be implemented by the processor 701 in the core network device 700 shown in Figure 14 calling computer execution instructions stored in the memory 704. Alternatively, the functions / implementation processes of the processing unit 1001 in Figure 16 can be implemented by the processor 701 in the core network device 700 shown in Figure 14 calling computer execution instructions stored in the memory 704, and the functions / implementation processes of the transceiver unit 1002 in Figure 16 can be implemented by the communication interface 703 in the access network device 700 shown in Figure 14.

[0310] Example 11

[0311] This embodiment provides an access network device that can be used to implement, for example, the functions of the M-RAN node in Embodiment 2, or the functions of the first access network device in Embodiment 5. This application embodiment can divide the access network device into functional units according to the above method embodiments. For example, each function can be divided into separate functional units, or two or more units can be integrated into a single processing module. The integrated units can be implemented in hardware or as software functional modules. It should be noted that the unit division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0312] Figure 17 is a schematic diagram of the structure of the access network device 1100 provided in an embodiment of this application. The access network device 1100 includes a processing unit 1101 and a transceiver unit 1102.

[0313] Optionally, the processing unit 1101 is specifically used for: the function of determining the switched data stream according to the indication information in the end marker message in S208 and S503.

[0314] Optionally, the processing unit 1101 is specifically used for: the function of discarding data packets of the switched data stream in S208a and S503.

[0315] Optionally, the transceiver unit 1102 is specifically used for: receiving the data forwarding address in S201.

[0316] Optionally, the transceiver unit 1102 is specifically used for: sending data packets of the buffered QoS flow to be switched in S201.

[0317] Optionally, the transceiver unit 1102 is specifically used for: sending indication information in S202 and S501.

[0318] Optionally, the transceiver unit 1102 is specifically used for receiving end marker messages in S208 and S502.

[0319] Optionally, the transceiver unit 1102 is specifically used for: sending data packets of the second data stream in S208 and S503.

[0320] Optionally, the transceiver unit 1102 is specifically used for: sending the second end marker message in S209.

[0321] Optionally, the transceiver unit 1102 is specifically used for: receiving QoS handover confirmation information in S210.

[0322] Specifically, the functions / implementation processes of the transceiver unit 1102 and processing unit 1101 in Figure 17 can be implemented by the processing element of the baseband device in the access network device of Embodiment 8 calling the computer execution instructions stored in the storage element. Alternatively, the functions / implementation processes of the processing unit 1101 in Figure 17 can be implemented by the processing element of the baseband device in the access network device of Embodiment 8 calling the computer execution instructions stored in the storage element, and the functions / implementation processes of the transceiver unit 1102 in Figure 17 can be implemented by the interface, radio frequency device, and antenna in the access network device of Embodiment 8.

[0323] Example 12

[0324] This embodiment provides a communication system, which may include the access network device in Embodiment 6 or the access network device in Embodiment 9, and may also include the core network device in Embodiment 7 or the core network device in Embodiment 10.

[0325] Example 13

[0326] This embodiment provides a communication system, which may include the access network device in Embodiment 8 or the access network device in Embodiment 11.

[0327] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)). In this embodiment, the computer may include the aforementioned apparatus.

[0328] In the description of this application, unless otherwise stated, " / " indicates that the objects before and after it are in an "or" relationship. For example, A / B can represent A or B; where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Additionally, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first," "second," etc., are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or execution order, and the terms "first," "second," etc., do not necessarily imply difference. In this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being better or more advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0329] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

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

Claims

1. A data processing method, characterized in that, Including: The first access network device receives an end marker message from a core network element. The end marker message includes indication information for indicating a first data stream in a first session to which the end marker message applies. The first data stream is a data stream that is switched from the first access network device to a second access network device. The first access network device determines, according to the indication information, that the end marker message applies to the first data stream. When the first access network device receives a second data packet of a second data stream in the first session after the end marker message, the first access network device sends the second data packet to a terminal device. Wherein, the second data stream is a data stream that remains at the first access network device.

2. The method according to claim 1, characterized in that, Also including: When the first access network device receives a first data packet of the first data stream after the end marker message, the first access network device discards the first data packet.

3. The method according to claim 1 or 2, characterized in that, The indication information includes: An identifier of the first data stream.

4. The method according to claim 1 or 2, characterized in that, The indication information includes: A bit sequence. Multiple bit positions in the bit sequence correspond one-to-one to multiple data streams in the first session. The value of each bit position is a first value or a second value. The first value indicates being applied by the end marker message, and the second value indicates not being applied by the end marker message. Among them, the value of the bit position corresponding to the first data stream is the first value, and the value of the bit position corresponding to the second data stream is the second value.

5. The method according to any one of claims 1-4, characterized in that, The end marker message includes the indication information, including: The protocol header of the end marker message includes the indication information; or, The content cell of the end marker message includes the indication information.

6. The method according to any one of claims 1-5, characterized in that, The first access network device is a master base station, and the second access network device is a secondary base station; or, The first access network device is a secondary base station, and the second access network device is a master base station.

7. The method according to any one of claims 1-6, characterized in that, The first session is a Packet Data Unit (PDU) Session, and the data stream is a Quality of Service (QoS) flow.

8. The method according to any one of claims 1-7, characterized in that, The core network element is a User Plane Function (UPF) network element.

9. A data processing method, characterized in that, Including: A core network element obtains an end marker message. The end marker message includes indication information for indicating a first data stream in a first session to which the end marker message applies. The first data stream is a data stream that is switched from a first access network device to a second access network device. The core network element sends the end marker message to the first access network device.

10. The method according to claim 9, characterized in that, The core network element obtains the end marker message, including: The core network element generates the end marker message; or, The core network element receives the end marker message from a control network element.

11. The method according to claim 9 or 10, characterized in that, Also including: After the end marker message, the core network element continues to send the second data packet of the second data stream of the first session to the first access network device, where the second data stream is the data stream maintained at the first access network device.

12. The method according to any one of claims 9-11, characterized in that,The indication information includes: The identifier of the first data stream.

13. The method according to claim 11, wherein, The indication information includes: A bit sequence, where multiple bits in the bit sequence correspond one-to-one to multiple data streams of the first session. The value of each bit is a first value or a second value. The first value indicates being affected by the end marker message, and the second value indicates not being affected by the end marker message. Among them, the value of the bit corresponding to the first data stream is the first value, and the value of the bit corresponding to the second data stream is the second value.

14. The method according to any one of claims 9 - 13, wherein, The end marker message includes the indication information, including: The protocol header of the end marker message includes the indication information; or, The content cell of the end marker message includes the indication information.

15. The method according to any one of claims 9 - 14, wherein, The first access network device is the master base station, and the second access network device is the secondary base station; or, The first access network device is the secondary base station, and the second access network device is the master base station.

16. The method according to any one of claims 9 - 15, wherein, The first session is a Packet Data Unit Session (PDU Session), and the data stream is a Quality of Service flow (QoS flow).

17. A data processing method, wherein, It includes: The first access network device sends indication information to the first core network element, where the indication information is used to indicate the first data stream to be switched in the first session; The first access network device receives an end marker message from the second core network element; The first access network device determines that the end marker message affects the first data stream according to the first data stream; When the first access network device receives the second data packet of the second data stream in the first session after the end marker message, the first access network device sends the second data packet to the terminal device; Among them, the second data stream is the data stream maintained at the first access network device.

18. The method according to claim 17, wherein, It further includes: The end marker message includes second indication information, where the second indication information is used to indicate that the end marker message affects some data streams in the first session; The first access network device determines that the end marker message affects the first data stream according to the second indication information.

19. The method according to claim 17 or 18, wherein, It further includes: When the first access network device receives the first data packet of the first data stream after the end marker message, the first access network device discards the first data packet.

20. The method according to any one of claims 17 - 19, wherein, The first access network device is the master base station, and the second access network device is the secondary base station; or, The first access network device is the secondary base station, and the second access network device is the master base station.

21. The method according to any one of claims 17 - 20, wherein, The first session is a Packet Data Unit Session (PDU Session), and the data stream is a Quality of Service flow (QoS flow).

22. The method according to any one of claims 17 - 21, wherein, The first core network element is a session management function network element, and the second core network element is a user plane function network element.

23. An access network device, wherein, It includes: A processor for reading and running instructions in a memory to implement the method according to any one of claims 1-7.

24. A core network device, characterized in that, It includes: A processor for reading and running instructions in a memory to implement the method according to any one of claims 9-16.

25. An access network device, characterized in that, It includes: A processor for reading and running instructions in a memory to implement the method according to any one of claims 17-21.

26. A computer storage medium for storing instructions, which, when run on a communication device, are used to implement the method according to any one of claims 1-22.

27. A computer program product comprising instructions, which, when run on a communication device, are used to implement the method according to any one of claims 1-22.

28. A communication system, characterized in that, It includes the access network device according to claim 23 and the core network device according to claim 24.

29. A communication system, characterized in that, It includes the access network device according to claim 25 and a user plane function network element.

30. The system according to claim 29, characterized in that, It further includes: An access and mobility management function network element; or, A session management function network element.