Service processing method and apparatus

Abstract

The present disclosure relates to a service processing method and apparatus. The method comprises: a first access network device sends first indication information to a first network element, wherein the first indication information is used for indicating whether the first access network device supports processing based on a packet data unit (PDU) set. In this way, the first network element can determine whether the first access network device supports processing based on the PDU set, so as to ensure service continuity and improve the quality of service.

Description

Business processing method and device Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a service processing method and device. Background Art

[0002] Mobile media services, cloud AR (augmented reality) / VR (virtual reality) and other XR (extended reality) services, cloud gaming, and video-based remote control of machines or drones are expected to contribute increasingly high traffic volumes to 5G networks. XR services also involve multimodal data streams. This multimodal data can be input from the same device or different devices (including sensors) to describe the same service or application, and may be output to one or more destination devices. The data streams in multimodal data are often correlated, such as the synchronization of audio and video streams, or the synchronization of touch and vision.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide a service processing method and apparatus for solving the problem of how to handle the coexistence of unmarked PDUs and marked PDUs in a QoS flow.

[0005] The embodiments of the present disclosure provide a service processing method and device.

[0006] According to a first aspect of an embodiment of the present disclosure, a service processing method is proposed, including: a first access network device sends a first indication message to a first network element, wherein the first indication message is used to indicate whether the first access network device supports processing based on a packet data unit PDU set; the first access network device determines to process the marked PDU in the forwarded data packet as an unmarked PDU, wherein the first access network device does not support processing based on a PDU set, and the forwarded data packet includes a marked PDU; or the first access network device determines to process the marked PDU in the forwarded data packet as an unmarked PDU before the unmarked PDU processing is completed, wherein the first access network device supports processing based on a PDU set, and the forwarded data packet includes a marked PDU.

[0007] According to a second aspect of an embodiment of the present disclosure, a service processing method is provided, comprising: a first access network device sending first indication information to a first network element, wherein the first indication information is used to indicate whether the first access network device supports processing based on a packet data unit (PDU) set; the first access network device receiving a priority indication sent by the first network element; and performing processing of marked PDUs and unmarked PDUs according to the priority indication;

[0008] The priority indication is used to indicate at least one of the following:

[0009] After receiving the marked PDU, the processing based on PDU set is performed first;

[0010] After receiving the marked PDU, the unmarked PDU will be processed first;

[0011] After receiving the marked PDU, the device executes the PDU based on the local configuration of the first access network device;

[0012] After receiving the marked PDU, it will be executed according to the operation management and maintenance OAM configuration first.

[0013] According to a second aspect of an embodiment of the present disclosure, a storage medium is provided, wherein the storage medium stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the first aspect and the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0015] FIG1 is an architecture diagram of a communication system provided by an embodiment of the present disclosure;

[0016] FIG2 is a schematic diagram of a 5G networking architecture provided by an embodiment of the present disclosure;

[0017] FIG3 is a flow chart of a service processing method provided by an embodiment of the present disclosure;

[0018] FIG4A is a flowchart of another service processing method provided by an embodiment of the present disclosure;

[0019] FIG4B is a flowchart of another service processing method provided by an embodiment of the present disclosure;

[0020] FIG5A is a structural diagram of a communication device provided by an embodiment of the present disclosure;

[0021] FIG5B is a schematic structural diagram of a chip provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0022] In the first aspect, an embodiment of the present disclosure proposes a service processing method, including: a first access network device sends a first indication information to a first network element, wherein the first indication information is used to indicate whether the first access network device supports processing based on a packet data unit PDU set; the first access network device determines to process the marked PDU in the forwarded data packet as an unmarked PDU, wherein the first access network device does not support processing based on a PDU set, and the forwarded data packet includes a marked PDU; or the first access network device determines to process the marked PDU in the forwarded data packet as an unmarked PDU before the unmarked PDU processing is completed, wherein the first access network device supports processing based on a PDU set, and the forwarded data packet includes a marked PDU.

[0023] In a second aspect, an embodiment of the present disclosure provides a service processing method, comprising: a first access network device sending first indication information to a first network element, wherein the first indication information is used to indicate whether the first access network device supports processing based on a packet data unit (PDU) set; the first access network device receives a priority indication sent by the first network element; and performs processing of marked PDUs and unmarked PDUs according to the priority indication;

[0024] The priority indication is used to indicate at least one of the following:

[0025] After receiving the marked PDU, the processing based on PDU set is performed first;

[0026] After receiving the marked PDU, the unmarked PDU will be processed first;

[0027] After receiving the marked PDU, the device executes the PDU based on the local configuration of the first access network device;

[0028] After receiving the marked PDU, it will be executed according to the operation management and maintenance OAM configuration first.

[0029] In a third aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the optional implementation of the first and second aspects.

[0030] In a fourth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation of the first and second aspects.

[0031] In a fifth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first, second and third aspects.

[0032] In a sixth aspect, an embodiment of the present disclosure provides a chip or a chip system, which includes a processing circuit configured to execute the method described in the optional implementation of the first and second aspects above.

[0033] The embodiments of the present disclosure provide a service processing method and apparatus. In some embodiments, the terms service processing method, information processing method, communication method, etc. can be used interchangeably.

[0034] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0035] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0036] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0037] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0038] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0039] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0040] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0041] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0042] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different. For another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0043] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0044] In some embodiments, terms such as "time / frequency" and "time / frequency domain" refer to the time domain and / or the frequency domain.

[0045] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0046] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0047] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0048] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0049] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0050] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0051] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0052] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0053] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0054] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0055] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0056] FIG1 is an architecture diagram of a communication system provided by an embodiment of the present disclosure.

[0057] As shown in FIG1 , a communication system 100 includes a terminal 101 , an access network device 102 , and a core network device 103 .

[0058] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0059] In some embodiments, the terminal may also be referred to as a terminal device, a user device, etc., and the names are interchangeable, and the embodiments of the present disclosure do not impose specific limitations on this.

[0060] In some embodiments, the access network device 102 is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0061] In some embodiments, the access network device 102 may also be a satellite.

[0062] In some embodiments, the core network device 103 may be a device including multiple network elements such as a first network element, a second network element, and a third network element, or may be multiple devices or a group of devices, each including multiple network functions. A network element may also be referred to as a network function, which may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0063] In some embodiments, the first network element is, for example, a session management function (SMF).

[0064] In some embodiments, the second network element is, for example, a user plane function (UPF).

[0065] In some embodiments, the first network element is used to perform packet data unit (PDU) session management on the terminal, execution of PCF control policy, selection of user plane function (UPF) network element, allocation of terminal device IP address when the PDU type is IP type, etc.

[0066] In some embodiments, the second network element is used to implement policy control functions such as session and service flow level billing, QoS bandwidth guarantee and mobility management, and user equipment policy decision-making.

[0067] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0068] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0069] The embodiments of the present disclosure can be applied to long term evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, ultra mobile broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, ultra-wideband (UWB), Bluetooth (registered trademark), public land mobile network (PLMN) networks, device-to-device (D2D) systems, machine-to-machine (M2M) systems, Internet of Things (IoT) systems, vehicle-to-everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0070] FIG2 is a schematic diagram of a 5G networking architecture provided by an embodiment of the present disclosure.

[0071] As shown in Figure 2, the network functions related to the 5G network architecture are introduced as follows:

[0072] Application function (AF): also known as application controller, is mainly used to convey the requirements of the application side to the network side, such as quality of service (QoS) requirements, user status event subscription, etc. AF can be an application function entity of a third-party application, or it can be an application service deployed by an operator, such as an IMS voice call service. Among them, when the application function entity of a third-party application interacts with the core network, it can be authorized through the capability exposure function (NEF). For example, the application function entity of the third-party application directly sends a request message to the NEF, and the NEF verifies whether the AF is allowed to send the request message. If the verification is successful, the request message is forwarded to the corresponding policy control function (PCF) or unified data management function (UDM).

[0073] PCF: Mainly used to implement policy control functions such as session and service flow level billing, QoS bandwidth guarantee and mobility management, and user equipment policy decision-making.

[0074] UDM: Mainly used to implement data management functions such as managing contract information and user access authorization.

[0075] Access and Mobility Management Function (AMF): This function is primarily responsible for implementing terminal mobility management and access authentication / authorization. It is also responsible for communicating user policies between the terminal and the PCF.

[0076] Session management function (SMF): mainly used for packet data unit (PDU) session management for terminals, execution of control policies issued by PCF, selection of user plane function (UPF), and allocation of terminal IP addresses when the PDU type is IP type.

[0077] UPF: Mainly used as the interface between the terminal and the data network, it performs functions such as user plane data forwarding, session / flow-level billing statistics, and bandwidth limitation.

[0078] Unified data repository (UDR): Mainly responsible for the storage and access functions of data such as contract information, policy data, and application data. UDR can interface with UDM, PCF, NEF, etc. to achieve corresponding network element access or call.

[0079] Of course, the core network may also include other network functions besides the network functions described in the above examples, which are not listed here one by one.

[0080] It should be noted that the embodiments of the present disclosure do not limit the names of the corresponding network functions that implement various functions. They can also implement other functions or be integrated with other functional network elements, and can also be called other names.

[0081] In the 5G networking architecture shown in Figure 2, the main functions of some related communication interfaces between network functions and between network functions and devices are described as follows:

[0082] N1 interface: It is the signaling interface between the AMF network element and the terminal. It is independent of the access network and is used to exchange signaling messages between the core network and the terminal. It can be used in processes such as terminal registration, terminal establishment of PDU session, and network side terminal policy configuration.

[0083] N2 interface: It is the interface between the AMF network element and the RAN equipment, used to transmit radio bearer control information from the core network to the RAN equipment.

[0084] ]N3 interface: The interface between (R)AN equipment and UPF network element, used to transmit terminal business data between RAN equipment and UPF network element.

[0085] N4 interface: It is the interface between the SMF network element and the UPF network element, used to transmit information between the control plane and the user plane. It can be used by the control plane terminal to complete the network access operation and other processes according to the contract information with the operator.

[0086] N6 interface: The interface between the UPF network element and the DN, used to transmit terminal service data between the UPF network element and the DN.

[0087] N7 interface: The interface between the PCF network element and the SMF network element, used to deliver information such as PDU session granularity and service data flow granularity control strategy.

[0088] N8 interface: The interface between the AMF network element and the UDM network element, used by the AMF network element to obtain access and mobility management-related contract information and authentication data from the UDM network element, and for the AMF network element to register the terminal's current mobility management-related information to the UDM network element.

[0089] N10 interface: It is the interface between the SMF network element and the UDM network element. It is used by the SMF network element to obtain session management-related contract information from the UDM network element, and for the SMF network element to register terminal current session-related information with the UDM network element.

[0090] N11 interface: It is the interface between the SMF network element and the AMF network element, used to transmit PDU session tunnel information between the RAN device and the UPF network element, control messages sent to the terminal, radio resource control information sent to the RAN device, etc.

[0091] Mobile media services, cloud AR (augmented reality) / VR (virtual reality) and other XR (extended reality) services, cloud gaming, and video-based remote control of machines or drones are expected to contribute increasingly high traffic volumes to 5G networks. XR services also involve multimodal data streams. This multimodal data can be input from the same device or different devices (including sensors) to describe the same service or application, and may be output to one or more destination devices. The data streams in multimodal data are often correlated, such as the synchronization of audio and video streams, or the synchronization of touch and vision. These media services share common characteristics within their data streams, between data streams, and in terms of the network transmission requirements. Effectively identifying and leveraging these characteristics will facilitate network and service transmission and control, as well as enhance service assurance and user experience.

[0092] XRM (XR and media) services require the fifth-generation mobile communication system (5GS) to comprehensively consider the quality of service (QoS) characteristics of relevant data flows. For example, parameters such as guaranteed bitrate (GBR) data flows, guaranteed flow bitrate (GFBR), packet delay budget (PDB), and maximum data burst volume (MDBV) must be met and coordinated simultaneously. This also involves ensuring the consistency of QoS authorization and execution for multiple XRM data flows within a single terminal and for XRM data flows across multiple terminals.

[0093] In the 5G system, AF supports enhanced processing of XRM service data flows based on each PDU set (Per PDU set). This supports AF's enhanced QoS awareness and assurance of XRM service data flows, as well as enhanced user QoE. This includes AF providing PDU Set-specific QoS features and protocol specifications:

[0094] -PDU Set Delay Budget (PSDB);

[0095] -PDU Set Error Rate (PSER);

[0096] -PDU Set Integrated Processing Information (PSIHI).

[0097] The SMF and UPF can perform the general packet radio service tunneling protocol for the user plane (GTP-U) header extension of the corresponding PDU in the corresponding SDF PDU set in combination with the protocol description and protocol header extension provided by the AF, carrying PDU Set information. The PDU Set information is used by the NG-RAN for QoS processing based on the PDU Set. The PDU Set information includes:

[0098] -PDU Set sequence number.

[0099] -Indication of the last PDU of the PDU Set.

[0100] -PDU sequence number within the PDU Set.

[0101] -PDU Set size (in bytes).

[0102] -PDU Set Importance, used to identify the relative importance of a PDU Set compared to other PDU Sets in a QoS flow.

[0103] The UPF will perform the mapping of AF SDF service data flows to QoS flows based on PDR rules, encapsulate the associated PDUs into PDU sets, and implement relevant Set-related QoS policies such as PDU Set Error Rate (PSER) and PDU Set Delay Budget (PSDB) for the PDU Set within the QoS flow.

[0104] The 5GS system supports QoS processing in which either PDU-based QoS rules and parameter policies or PDU set-based QoS rules and parameter policies are supported within the same QoS flow. This means that only one set of QoS parameters can be activated simultaneously within a QoS flow, either the PDU-based QoS mechanism or the PDU set-based QoS mechanism.

[0105] However, in the actual network, there are NG-RANs with unequal functional support (Non-homogenous support). For example, there are NG-RANs that do not support PDU set processing and NG-RANs that support PDU set processing. Due to the business continuity requirements of XR, data forwarding is required for downlink data in the handover process (such as terminal mobility). (Data forwarding supports direct and indirect modes. In direct mode, the source NG-RAN forwards to the target NG-RAN. In indirect mode, the UPF performs data forwarding to the target-NG-RAN. It should be noted that in indirect mode, the UPF that performs data forwarding is not necessarily the UPF corresponding to the source NG-RAN.

[0106] Among them, when handover (HO) occurs between an NG-RAN that does not support PDU set processing and an NG-RAN that supports PDU set processing, especially when switching from a source NG-RAN that does not support PDU set processing to a target NG-RAN that supports PDU set processing, unmarked PDUs and marked PDUs will exist in the same QoS flow at the same time.

[0107] However, the 5GS system does not support the scenario where unmarked PDUs and marked PDUs coexist in the same QoS flow, and cannot guarantee the QoS of the corresponding QoS flow.

[0108] How to handle the QoS processing of the coexistence of unmarked PDUs and marked PDUs in the QoS flow is a problem that 5GS must solve to ensure XR interactive services such as cloud gaming.

[0109] Based on this, the embodiments of the present disclosure provide a service processing method and apparatus to solve the problem of how to handle the coexistence of unmarked PDUs and marked PDUs in a QoS flow, thereby ensuring service continuity and improving service quality.

[0110] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0111] In some embodiments, terms such as "uplink", "uplink", "physical uplink" can be interchangeable with each other, and terms such as "downlink", "downlink", "physical downlink" can be interchangeable with each other, and terms such as "side", "sidelink", "side communication", "sidelink communication", "direct connection", "direct link", "direct communication", "direct link communication" can be interchangeable with each other.

[0112] In some embodiments, the terms "downlink control information (DCI)", "downlink (DL) assignment", "DL DCI", "uplink (UL) grant", "UL DCI" and the like may be used interchangeably.

[0113] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, and terms such as "physical uplink shared channel (PUSCH)" and "UL data" can be used interchangeably.

[0114] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0115] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0116] In some embodiments, terms such as "resource block (RB)", "physical resource block (PRB)", "sub-carrier group (SCG)", "resource element group (REG)", "PRB pair", "RB pair", "resource element (RE)", and "sub-carrier" can be used interchangeably.

[0117] In some embodiments, terms such as wireless access scheme and waveform may be used interchangeably.

[0118] In some embodiments, terms such as "frame", "radio frame", "subframe", "slot", "sub-slot", "mini-slot", "symbol", "symbol", and "transmission time interval (TTI)" can be used interchangeably.

[0119] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0120] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0121] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0122] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0123] To facilitate understanding of the embodiments of the present disclosure, the following exemplary embodiments are provided.

[0124] The 5GS system supports QoS processing in which either PDU-based QoS rules and parameter policies or PDU set-based QoS rules and parameter policies are supported within the same QoS flow. This means that only one set of QoS parameters can be activated simultaneously within a QoS flow, either the PDU-based QoS mechanism or the PDU set-based QoS mechanism.

[0125] However, in the actual network, there are various types of NG-RAN (Non-homogenous support) with different functional support. For example, there are NG-RANs that do not support PDU set processing and NG-RANs that support PDU set processing. Due to the business continuity requirements of XR, data forwarding is required for downlink data in the handover process (such as terminal mobility). (Data forwarding supports direct and indirect modes. In direct mode, the source NG-RAN forwards to the target NG-RAN. In indirect mode, the UPF performs data forwarding to the target-NG-RAN. It should be noted that in indirect mode, the UPF that performs data forwarding is not necessarily the UPF corresponding to the source NG-RAN.

[0126] Among them, when handover (HO) occurs between an NG-RAN that does not support PDU set processing and an NG-RAN that supports PDU set processing, especially when switching from a source NG-RAN that does not support PDU set processing to a target NG-RAN that supports PDU set processing, unmarked PDUs and marked PDUs will exist in the same QoS flow at the same time.

[0127] However, the 5GS system does not support the scenario where unmarked PDUs and marked PDUs coexist in the same QoS flow, and cannot guarantee the QoS of the corresponding QoS flow.

[0128] How to deal with the coexistence of unmarked PDUs and marked PDUs in QoS flows is a problem that 5GS must solve to ensure XR interactive services such as cloud gaming.

[0129] In the disclosed embodiment, NG-RAN does not support mixed processing of marked PDUs and unmarked PDUs within a QoS flow at the same time. Marked PDUs are processed as unmarked PDUs. This processing can be performed within a specific time, where the specific time can be set according to the configuration, or can be set and executed based on the received end data (End Marker) packet and / or transition processing window, etc., and the transition processing window and other information can be further sent to the SMF. Specific implementation plan:

[0130] During the Xn handover and N2 handover process of NG-RAN, the target NG-RAN provides a first indication information to the SMF to indicate whether the target NG-RAN node supports PDU Set-based processing.

[0131] In some embodiments, the first indication information is included in a path switch request message in an Xn handover process, or the first indication information is included in a handover request confirmation message in an N2 handover process.

[0132] In some embodiments, the source NG-RAN supports PDU Set-based processing, and the target NG-RAN for handover does not support PDU Set-based processing. For the target NG-RAN, if a forwarded data packet is received, such as a data packet directly forwarded by the source NG-RAN or a data packet indirectly forwarded by the UPF, since the source NG-RAN supports PDU Set-based processing, the forwarded data packet may include a marked PDU. After receiving the forwarded data packet, the target NG-RAN may process the marked PDU as an unmarked PDU, ignore the QoS parameters of the PDU Set, execute the PDUQoS parameters, and ignore the protocol extension header (header extensions) used to identify the PDU Set information of the marked PDU.

[0133] In some embodiments, the source NG-RAN does not support PDU Set-based processing, and the target NG-RAN for handover supports PDU Set-based processing. For the target NG-RAN, if a forwarded data packet is received, such as a data packet directly forwarded by the source NG-RAN or a data packet indirectly forwarded by the UPF, since the source NG-RAN does not support PDU Set-based processing, the forwarded data packet may include an unmarked PDU. The target NG-RAN receives the forwarded data packet (the data packet received through the forwarding tunnel before the EndMarker end data packet). Before the processing of the unmarked PDU is completed, the target NG-RAN processes the received marked PDU as an unmarked PDU (so that all PDUs are processed as unmarked PDUs at the same time), ignores the PDU SetQoS parameter of the marked PDU, and uses the PDUQoS parameter, that is, ignores the protocol extension header used to identify the PDU Set information).

[0134] Furthermore, after the processing of the unmarked PDU is completed, the target NG-RAN can process the marked PDU according to the QoS parameters of the PDU Set and the PDU Set information in the extended protocol header (or the PDUset information configured by the UPF, and the PDUset information in the protocol description).

[0135] In some embodiments, the source NG-RAN does not support PDU Set-based processing, and the target NG-RAN of the handover supports PDU Set-based processing. For the target NG-RAN, if a forwarded data packet is received, such as a data packet directly forwarded by the source NG-RAN or a data packet indirectly forwarded by the UPF, since the source NG-RAN does not support PDU Set-based processing, the forwarded data packet may include an unmarked PDU. The target NG-RAN can process the received marked PDU as an unmarked PDU within a specific window (for example, starting a timer) during the timer, ignoring the QoS parameters of the PDU Set. After the timer expires, the target NG-RAN can process the marked PDU according to the QoS parameters of the PDU Set and the PDU Set information in the extended protocol header.

[0136] In one possible implementation, the target NG-RAN starts the above timer after receiving the End Marker packet. The duration of the timer is the duration of the handover window (the marked PDU in the handover process is processed as an unmarked PDU, which can be started before receiving the End Marker packet. The remaining time after receiving the End Marker packet is easier to determine).

[0137] In one possible implementation, the target NG-RAN starts the above timer after receiving the QoS parameters of the PDU Set sent by the SMF. The duration of the timer is the duration of the handover window (the marked PDU in the handover process is processed as an unmarked PDU and may have started before receiving the QoS parameters of the PDU Set sent by the SMF).

[0138] Among them, the processing switching window duration can be greater than or equal to the time required for the unmarked PDU processing to be completed when the timer set by the target NG-RAN (which can be based on local configuration or OA configuration or received EndMark packet or received PDUSet related QoS parameters) is started.

[0139] In a possible implementation, after receiving the QoS parameters of the PDU Set sent by the SMF, the target NG-RAN may send a second indication information to the SMF, where the second indication information is used to indicate whether the target NG-RAN accepts (accepts or rejects) the QoS parameters of the received PDU Set, wherein if the NG-RAN rejects the PDU Set QoS parameters, the NG-RAN PDU Set QoS processing function is not activated; if it is accepted, the NG-RAN PDU Set QoS processing function is activated.

[0140] In some embodiments, the SMF may request the target NG-RAN to activate PDU Set-based QoS processing for a given QoS flow, and the target NG-RAN may provide the SMF with an indication of whether to accept (accept or reject) the QoS parameters of the received PDU Set.

[0141] In some embodiments, the NG-RAN may provide the SMF with an indication of whether to activate the QoS parameters of the PDU Set, and the time to delay application, or the time to delay activation (relative to the start time (or time window) of the QoS parameters of the applied PDU Set). This time may be determined based on a timer used in the target NG-RAN to process the marked PDU.

[0142] In some embodiments, the SMF configures the PSA UPF to activate / deactivate / deactivate PDU group identification and marking (PDU group-related identification and extended protocol header marking of PDU data packets) based on the indication of the target NG-RAN or the time of delayed application / delayed activation.

[0143] In some embodiments, the PSA UPF sends End Marker packets to the target NG-RAN at the end of a complete PDU set. In other words, the PSA UPF starts performing PDUset identification and extended protocol header marking at the beginning of a complete PDU set (e.g., the first packet) and stops or ends performing PDUset identification and extended protocol header marking at the end of a complete PDU set (e.g., the last packet) (End Marker packets are sent just after the last packet of the PDU set).

[0144] Alternatively, the PSA UPF identifies and marks PDUs with PDU Set information (e.g., identifying PDUs with RTP or RTCP extended protocol headers, mapping the protocol extension headers with PDUSet information into GTP-U protocol extension headers, and carrying the PDUSet information to the NG-RAN in the GTP-U extended protocol headers). It does this starting from a complete PDU set. The first PDU set includes PDUs that overlap with packets sent through the source forwarding tunnel (here the overlapping packets have been sent on the source channel, but are not the end of a PDUset, such as the first half of the Set, then this part and the unsent second half are taken together as a complete PDUset and sent on the new channel). If the end marker packet is not sent at the end of a complete PDU set (e.g., it is sent in the middle of a PDUSet),

[0145] Alternatively, the PSA UPF identifies and marks the PDU with PDU Set information (for example, it identifies the PDU with the RTP or RTCP extended protocol header, maps the protocol extension header with the PDUSet information into the GTP-U protocol extension header, and carries the PDUSet information to the NG-RAN in the GTP-U extended protocol header). It sends the remaining data packets of the PDU set sent through the source forwarding tunnel as single data packets. Then, it starts from a complete PDU set, identifies the data packets and marks the PDUset information to the extended protocol header, if the end marker packet is not sent at the end of a complete PDU set (for example, it is sent in the middle of the PDUSet).

[0146] In an exemplary embodiment, as shown in Figure 3, the case where the source NG-RAN switches to the target NG-RAN, the AMF is not changed, and the SMF decides to retain the existing UPF and switches the terminal from the source NG-RAN to the target NG-RAN through Xn is used as an example for explanation.

[0147] 1a. If the public land mobile network (PLMN) is configured with secondary Radio Access Technology (RAT) usage reporting, the source NG-RAN node may provide a RAN usage data report (N2 Session Management (SM) information (Secondary RAT usage data), Handover Flag, Source to Target Transparent Container) to the AMF during the handover execution phase. The source NG-RAN node shall provide this report only if the target NG-RAN confirms the handover over the Xn interface. The Handover Flag indicates to the AMF that it shall buffer the N2 SM information containing the usage data report before forwarding it.

[0148] 1b. Target NG-RAN to AMF: N2 Path Switch Request (List of PDU Sessions to be switched, List of PDU Sessions to be switched with N2 SM information, List of PDU Sessions that could not be established based on the failure reason given in the N2 SM information element, Terminal location information). The target NG-RAN sends an N2 Path Switch Request message to the AMF, notifying the terminal that it has moved to the new target cell and providing the list of PDU Sessions to be switched. The AN tunnel information for each PDU Session to be switched is included in the N2 SM information. For PDU Sessions to be switched to the target NG-RAN, the N2 Path Switch Request message shall include a list of accepted QoS flows. For each QoS flow for which an alternative QoS profile has been accepted, the N2 SM information shall include a reference to the satisfied alternative QoS profile.

[0149] During the Xn handover and N2 handover process of NG-RAN, the target NG-RAN provides a first indication information to the SMF to indicate whether the target NG-RAN node supports PDU Set-based processing.

[0150] In some embodiments, the first indication information is included in a path switch request message in an Xn handover process, or the first indication information is included in a handover request confirmation message in an N2 handover process.

[0151] In some embodiments, the source NG-RAN supports PDU Set-based processing, and the target NG-RAN for switching does not support PDU Set-based processing. For the target NG-RAN, if a forwarded data packet is received, such as a data packet directly forwarded by the source NG-RAN or a data packet indirectly forwarded by the UPF, since the source NG-RAN supports PDU Set-based processing, the forwarded data packet may include a marked PDU. After receiving the forwarded data packet, the target NG-RAN may process the marked PDU as an unmarked PDU, ignore the QoS parameters of the PDU Set, execute the PDUQoS parameters, and ignore the protocol extension header (header extensions) used to identify the PDU Set information of the marked PDU.

[0152] In some embodiments, the source NG-RAN does not support PDU Set-based processing, and the target NG-RAN for handover supports PDU Set-based processing. For the target NG-RAN, if a forwarded data packet is received, such as a data packet directly forwarded by the source NG-RAN or a data packet indirectly forwarded by the UPF, since the source NG-RAN does not support PDU Set-based processing, the forwarded data packet may include an unmarked PDU. The target NG-RAN receives the forwarded data packet (the data packet received through the forwarding tunnel before the EndMarker end data packet). Before the processing of the unmarked PDU is completed, the target NG-RAN processes the received marked PDU as an unmarked PDU (so that all PDUs are processed as unmarked PDUs at the same time), ignores the PDU SetQoS parameter of the marked PDU, and uses the PDUQoS parameter, that is, ignores the protocol extension header used to identify the PDU Set information).

[0153] Furthermore, after the processing of the unmarked PDU is completed, the target NG-RAN can process the marked PDU according to the QoS parameters of the PDU Set and the PDU Set information in the extended protocol header (or the PDUset information configured by the UPF, and the PDUset information in the protocol description).

[0154] In some embodiments, the source NG-RAN does not support PDU Set-based processing, and the target NG-RAN of the handover supports PDU Set-based processing. For the target NG-RAN, if a forwarded data packet is received, such as a data packet directly forwarded by the source NG-RAN or a data packet indirectly forwarded by the UPF, since the source NG-RAN does not support PDU Set-based processing, the forwarded data packet may include an unmarked PDU. The target NG-RAN can process the received marked PDU as an unmarked PDU within a specific window (for example, starting a timer) during the timer, ignoring the QoS parameters of the PDU Set. After the timer expires, the target NG-RAN can process the marked PDU according to the QoS parameters of the PDU Set and the PDU Set information in the extended protocol header.

[0155] In one possible implementation, the target NG-RAN starts the above timer after receiving the End Marker packet. The duration of the timer is the duration of the handover window (the marked PDU in the handover process is processed as an unmarked PDU, which can be started before receiving the End Marker packet. The remaining time after receiving the End Marker packet is easier to determine).

[0156] In one possible implementation, the target NG-RAN starts the above timer after receiving the QoS parameters of the PDU Set sent by the SMF. The duration of the timer is the duration of the handover window (the marked PDU in the handover process is processed as an unmarked PDU and may have started before receiving the QoS parameters of the PDU Set sent by the SMF).

[0157] Among them, the processing switching window duration can be greater than or equal to the time required for the unmarked PDU processing to be completed when the timer set by the target NG-RAN (which can be based on local configuration or OA configuration or received EndMark packet or received PDUSet related QoS parameters) is started.

[0158] In a possible implementation, after receiving the QoS parameters of the PDU Set sent by the SMF, the target NG-RAN may send a second indication information to the SMF, where the second indication information is used to indicate whether the target NG-RAN accepts (accepts or rejects) the QoS parameters of the received PDU Set, wherein if the NG-RAN rejects the PDU Set QoS parameters, the NG-RAN PDU Set QoS processing function is not activated; if it is accepted, the NG-RAN PDU Set QoS processing function is activated.

[0159] In some embodiments, the SMF may request the target NG-RAN to activate PDU Set-based QoS processing for a given QoS flow, and the target NG-RAN may provide the SMF with an indication of whether to accept (accept or reject) the QoS parameters of the received PDU Set.

[0160] In some embodiments, the NG-RAN may provide the SMF with an indication of whether to activate the QoS parameters of the PDU Set, and the time to delay application, or the time to delay activation (relative to the start time (or time window) of the QoS parameters of the applied PDU Set). This time may be determined based on a timer used in the target NG-RAN to process the marked PDU.

[0161] In some embodiments, the SMF configures the PSA UPF to activate / deactivate / deactivate PDU group identification and marking (PDU group-related identification and extended protocol header marking of PDU data packets) based on the indication of the target NG-RAN or the time of delayed application / delayed activation.

[0162] 2. AMF to SMF: Nsmf_PDUSession_UpdateSMContext (N2 SM information received in step 1b and N2 SM information (Secondary RAT usage data) from the source NG-RAN, terminal location information, and presence of the terminal in the Local Area Data Network (LADN) service area). The source NG-RAN's N2 SM information is the information buffered in step 1a, if applicable.

[0163] The AMF sends N2 SM information for each PDU Session received in the N2 Path Switch Request by invoking the Nsmf_PDUSession_UpdateSMContext request service operation. This information includes the target NG-RAN providing the SMF with an indication of whether PDU Set-based processing is supported in step 1; the "PDU set support" indication from the target NG-RAN will be included in the Path Switch Request message (Xn Switch). The Nsmf_PDUSession_UpdateSMContext request contains either an indication of the PDU Session to be switched (along with the N3 addressing information to be used and the QoS flow information to be transported), or an indication of the PDU Session to be rejected (along with the rejection reason).

[0164] If some QoS flows of a PDU Session are not accepted by the target NG-RAN, then after the handover procedure is completed, the SMF shall initiate the PDU Session Modification procedure to remove the unaccepted QoS flows from the PDU Session.

[0165] 3. SMF to UPF: N4 Session Modification Request (AN Tunnel Information). For the PDU session modified by the target NG-RAN, the SMF sends an N4 Session Modification Request message to the UPF. The SMF can notify the UPF that initiated the data notification to discard the downlink data of the PDU session and / or not to provide further data notification messages. Depending on the network deployment, the CN tunnel information used to connect to the target NG-RAN and the UPF of the source NG-RAN may be different. For example, the source NG-RAN and the target NG-RAN are located in different IP domains. In this case, the SMF may request the UPF to allocate new CN tunnel information and provide the target network instance.

[0166] 4. UPF to SMF: N4 Session Modification Response (CN Tunnel Information). For a switched PDU session, the UPF returns an N4 Session Modification Response message to the SMF after the requested PDU session is switched. For a PDU session that does not release user plane resources and is requested by the SMF, the tunnel identifier for the uplink traffic is only included in the response.

[0167] 5. To assist the reordering function in the target NG-RAN, the UPF sends one or more "EndMarker" packets for each N3 tunnel on the old path immediately after the handover. The UPF starts sending downlink data packets to the target NG-RAN.

[0168] In some embodiments, the PSA UPF sends End Marker packets to the target NG-RAN at the end of a complete PDU set. In other words, the PSA UPF starts performing PDUset identification and extended protocol header marking at the beginning of a complete PDU set (e.g., the first packet) and stops or ends performing PDUset identification and extended protocol header marking at the end of a complete PDU set (e.g., the last packet) (End Marker packets are sent just after the last packet of the PDU set).

[0169] Alternatively, the PSA UPF identifies and marks PDUs with PDU Set information (e.g., identifying PDUs with RTP or RTCP extended protocol headers, mapping the protocol extension headers with PDUSet information into GTP-U protocol extension headers, and carrying the PDUSet information to the NG-RAN in the GTP-U extended protocol headers). It does this starting from a complete PDU set. The first PDU set includes PDUs that overlap with packets sent through the source forwarding tunnel (here the overlapping packets have been sent on the source channel, but are not the end of a PDUset, such as the first half of the Set, then this part and the unsent second half are taken together as a complete PDUset and sent on the new channel). If the end marker packet is not sent at the end of a complete PDU set (e.g., it is sent in the middle of a PDUSet),

[0170] Alternatively, the PSA UPF identifies and marks the PDU with PDU Set information (for example, it identifies the PDU with the RTP or RTCP extended protocol header, maps the protocol extension header with the PDUSet information into the GTP-U protocol extension header, and carries the PDUSet information to the NG-RAN in the GTP-U extended protocol header). It sends the remaining data packets of the PDU set sent through the source forwarding tunnel as single data packets. Then, it starts from a complete PDU set, identifies the data packets and marks the PDUset information to the extended protocol header, if the end marker packet is not sent at the end of a complete PDU set (for example, it is sent in the middle of the PDUSet).

[0171] Based on the NG-RAN indication and / or activation time, the SMF configures the PSA UPF to activate / deactivate the PDU Set identification and marking.

[0172] In the case where the PSA UPF identifies and marks PDUs with PDU Set information in the GTP-U header, it shall do so starting from a complete PDU set. (In addition, if the source NG-RAN sends, the PDU following the End Marker packet is not the start of a complete PDU set, and a portion of the sent PDUs will be overlapped to perform PDU Set encapsulation.) The PSA UPF identifies and marks PDUs with PDU Set information in the GTP-U header, starting from a complete PDU set. The first PDU set will include PDUs that overlap with packets sent through the source forwarding tunnel if no End Marker packet is sent at the end of a complete PDU set.

[0173] 6. SMF to AMF: Nsmf_PDUSession_UpdateSMContext response (N2 SM information)

[0174] The SMF sends a Nsmf_PDUSession_UpdateSMContext response (N2 SM information (CN tunnel information, updated CN packet delay budget (PDB) for accepted QoS flows, updated time sensitive communication assistance information (TSCAI) for accepted QoS flows) to the AMF for the successfully handed over PDU session. The CN tunnel information of the UPF sent to the AMF is used to establish the N3 tunnel. For each accepted guaranteed bit rate (GBR) QoS flow of delay critical resource type, the SMF may update the dynamic CN PDB and TSCAI and send it to the target NG-RAN. The SMF may update the CN PDB and TSCAI in the response or using a separate PDU session modification procedure based on local configuration.

[0175] For XR service flows, the SMF sends the corresponding PDU set QoS parameters and flow description information in this message to the target NG-RAN. Alternatively, the SMF may subsequently initiate a separate PDU session modification process, carrying the updated PDU set QoS parameters and flow description information.

[0176] If the source NG-RAN does not support alternative QoS profiles and the target NG-RAN supports them, the SMF sends the available alternative QoS profiles to the target NG-RAN on a per QoS flow basis.

[0177] NOTE: Step 6 can occur at any time after the SMF receives the N4 Session Modification Response.

[0178] 7. AMF to NG-RAN: N2 path switching request confirmation (N2 SM information, unsuccessful PDU session, UE radio capability identifier).

[0179] 8. The target NG-RAN confirms the handover success by sending a Release Resources message to the source NG-RAN. The target NG-RAN then triggers the release of resources with the source NG-RAN.

[0180] 9. If one of the triggering conditions of the registration procedure applies, the terminal may initiate the mobility registration update procedure.

[0181] In an exemplary embodiment, as shown in Figures 4A and 4B , a non-Xn handover of the N2 interface of the source NG-RAN to the target NG-RAN includes a preparation phase as shown in Figure 4A and an execution phase as shown in Figure 4B . This description is made using an example where the source NG-RAN is an S-NG-RAN, the source AMF is an S-AMF, the source UPF is an S-UPF, the target NG-RAN is a T-NG-RAN, the target AMF is a T-AMF, and the target UPF is a T-UPF.

[0182] When the source NG-RAN decides to perform a non-Xn handover, it sends an N2 path switch request to the AMF. This request includes the list of PDU sessions to be handed over, the identity of the target NG-RAN and other relevant information.

[0183] After receiving the N2 path switching request, the AMF starts preparing for non-Xn handover. The AMF may need to perform some preparatory work, such as updating relevant context information and obtaining the status of the target NG-RAN.

[0184] Execution phase:

[0185] When the preparation phase is complete, the AMF sends an N2 Path Switch Request Confirmation to the source NG-RAN. This indicates that the AMF is ready to perform the handover.

[0186] The source NG-RAN starts preparing for handover of the terminal based on the confirmation of the AMF. The source NG-RAN can transfer PDU session information, user data and related context to the target NG-RAN.

[0187] After receiving the handover-related information, the target NG-RAN is ready to accept the terminal. It can allocate resources, update context information, etc.

[0188] When the target NG-RAN is ready, the source NG-RAN triggers handover of the terminal. The source NG-RAN can send instructions to the terminal, sending a signal to the terminal to instruct the terminal to switch to the target NG-RAN.

[0189] The terminal starts communicating on the target NG-RAN, which is responsible for the terminal's connection and services.

[0190] As shown in Figure 4A, the preparation stage:

[0191] 1. S-NG-RAN to S-AMF: Handover request (target identifier, source-to-target transparent container, SM N2 information list, PDU session identifier, intra-system handover indication).

[0192] The source-to-destination transparent container includes NG-RAN information created by S-NG-RAN and will be used by T-NG-RAN, transparent to 5GC. It also contains the corresponding QoS flow / DRB information for each PDU session for data forwarding.

[0193] 2-7. Select new AMF and UPF and obtain new UPF tunnel information.

[0194] 7. SMF to T-AMF: Nsmf_PDUSession_UpdateSMContext response (PDU session identifier, N2 SM information, reason for non-acceptance).

[0195] If the N2 handover of the PDU session is accepted, the SMF includes the N2 SM information in the Nsmf_PDUSession_UpdateSMContext response, which contains the N3 UP address and UL CN tunnel ID of the UPF, QoS parameters, TSCAI and user plane security execution information of the target NG-RAN.

[0196] 8. T-AMF supervises the Nsmf_PDUSession_UpdateSMContext response message from the involved SMFs.

[0197] 9. T-AMF to T-NG-RAN: Handover Request (source to target transparent container, N2MM information, N2 SM information list, tracking request, terminal radio capability identifier). The T-AMF determines the T-NG-RAN based on the target identifier. The T-AMF may allocate a valid 5G globally unique temporary identity (GUTI) for the terminal in the T-AMF and target Tracking Area Identity (TAI).

[0198] The source to target transparent container is forwarded as received from the S-NG-RAN. The N2MM information includes security information and mobility restriction list (if available in T-AMF).

[0199] The N2 SM information list includes the N2 SM information received from the SMF within the maximum allowed delay in the Nsmf_PDUSession_UpdateSMContext response message supervised by the T-AMF in step 8, which is prepared for T-NG-RAN.

[0200] 10. T-NG-RAN to T-AMF: Handover Request Acknowledgement (target to source transparent container, list of PDU Sessions to be handed over with N2 SM information, list of PDU Sessions that could not be established with the failure reason given in the N2 SM information element).

[0201] In case of NG-RAN N2 handover, the target NG-RAN provides an indication to the SMF whether the target NG-RAN node supports PDU set based processing; the "PDU set support" indication from the target NG-RAN is provided in the Handover Request Confirm message (NG Handover).

[0202] In some embodiments, the source NG-RAN supports PDU Set-based processing, and the target NG-RAN for switching does not support PDU Set-based processing. For the target NG-RAN, if a forwarded data packet is received, such as a data packet directly forwarded by the source NG-RAN or a data packet indirectly forwarded by the UPF, since the source NG-RAN supports PDU Set-based processing, the forwarded data packet may include a marked PDU. After receiving the forwarded data packet, the target NG-RAN may process the marked PDU as an unmarked PDU, ignore the QoS parameters of the PDU Set, execute the PDUQoS parameters, and ignore the protocol extension header (header extensions) of the marked PDU used to identify the PDU Set information.

[0203] In some embodiments, the source NG-RAN does not support PDU Set-based processing, and the target NG-RAN for handover supports PDU Set-based processing. For the target NG-RAN, if a forwarded data packet is received, such as a data packet directly forwarded by the source NG-RAN or a data packet indirectly forwarded by the UPF, since the source NG-RAN does not support PDU Set-based processing, the forwarded data packet may include an unmarked PDU. The target NG-RAN receives the forwarded data packet (the data packet received through the forwarding tunnel before the EndMarker end data packet). Before the processing of the unmarked PDU is completed, the target NG-RAN processes the received marked PDU as an unmarked PDU (so that all PDUs are processed as unmarked PDUs at the same time), ignores the PDU SetQoS parameter of the marked PDU, and uses the PDUQoS parameter, that is, ignores the protocol extension header used to identify the PDU Set information).

[0204] Furthermore, after the processing of the unmarked PDU is completed, the target NG-RAN can process the marked PDU according to the QoS parameters of the PDU Set and the PDU Set information in the extended protocol header (or the PDUset information configured by the UPF, and the PDUset information in the protocol description).

[0205] In some embodiments, the source NG-RAN does not support PDU Set-based processing, and the target NG-RAN of the handover supports PDU Set-based processing. For the target NG-RAN, if a forwarded data packet is received, such as a data packet directly forwarded by the source NG-RAN or a data packet indirectly forwarded by the UPF, since the source NG-RAN does not support PDU Set-based processing, the forwarded data packet may include an unmarked PDU. The target NG-RAN can process the received marked PDU as an unmarked PDU within a specific window (for example, starting a timer) during the timer, ignoring the QoS parameters of the PDU Set. After the timer expires, the target NG-RAN can process the marked PDU according to the QoS parameters of the PDU Set and the PDU Set information in the extended protocol header.

[0206] In one possible implementation, the target NG-RAN starts the above timer after receiving the End Marker packet. The duration of the timer is the duration of the handover window (the marked PDU in the handover process is processed as an unmarked PDU, which can be started before receiving the End Marker packet. The remaining time after receiving the End Marker packet is easier to determine).

[0207] In one possible implementation, the target NG-RAN starts the above timer after receiving the QoS parameters of the PDU Set sent by the SMF. The duration of the timer is the duration of the handover window (the marked PDU in the handover process is processed as an unmarked PDU and may have started before receiving the QoS parameters of the PDU Set sent by the SMF).

[0208] Among them, the processing switching window duration can be greater than or equal to the time required for the unmarked PDU processing to be completed when the timer set by the target NG-RAN (which can be based on local configuration or OA configuration or received EndMark packet or received PDUSet related QoS parameters) is started.

[0209] In a possible implementation, after receiving the QoS parameters of the PDU Set sent by the SMF, the target NG-RAN may send a second indication information to the SMF, where the second indication information is used to indicate whether the target NG-RAN accepts (accepts or rejects) the QoS parameters of the received PDU Set, wherein if the NG-RAN rejects the PDU Set QoS parameters, the NG-RAN PDU Set QoS processing function is not activated; if it is accepted, the NG-RAN PDU Set QoS processing function is activated.

[0210] In some embodiments, the SMF may request the target NG-RAN to activate PDU Set-based QoS processing for a given QoS flow, and the target NG-RAN may provide the SMF with an indication of whether to accept (accept or reject) the QoS parameters of the received PDU Set.

[0211] In some embodiments, the NG-RAN may provide the SMF with an indication of whether to activate the QoS parameters of the PDU Set, and the time to delay application, or the time to delay activation (relative to the start time (or time window) of the QoS parameters of the applied PDU Set). This time may be determined based on a timer used in the target NG-RAN to process the marked PDU.

[0212] In some embodiments, the SMF configures the PSA UPF to activate / deactivate / deactivate PDU group identification and marking (PDU group-related identification and extended protocol header marking of PDU data packets) based on the indication of the target NG-RAN or the time of delayed application / delayed activation.

[0213] In the N2 SM information in the list of PDU sessions to be switched, each PDU session ID includes the T-NG-RAN N3 addressing information, i.e. the N3 UP address and tunnel ID of the T-NG-RAN used for the PDU session.

[0214] N2 SM information may also include:

[0215] - If the PDU session has at least one QoS flow that requires data forwarding, it includes the N3 UP address of the T-NG-RAN and the tunnel ID of the T-NG-RAN that receives the forwarded data. The T-NG-RAN provides the data forwarding address for each data forwarding tunnel it decides to set up.

[0216] - For each QoS flow accepted using an alternative QoS profile, the target NG-RAN shall include a reference to the satisfied alternative QoS profile.

[0217] 11a-f, T-AMF exchanges tunnel information with T-NG-RAN, S-UPF, and T-UPF through SMF. 11a and 11f are executed during direct forwarding, while intermediate processes are executed during indirect forwarding to exchange channel information.

[0218] 11a. T-AMF to SMF: Nsmf_PDUSession_UpdateSMContext request (PDU session identifier, N2 SM response received from T-NG-RAN in step 10).

[0219] For each N2 SM response received from T-NG-RAN (N2 SM information contained in the Handover Request Acknowledgement), the T-AMF sends the received N2 SM response to the SMF indicated by the corresponding PDU Session ID.

[0220] If no new T-UPF is selected, the SMF stores the N3 tunnel information of the T-NG-RAN in the N2 SM response if the T-NG-RAN accepts the N2 handover.

[0221] The SMF / UPF allocates N3 UP addresses and tunnel IDs to the data forwarding tunnel endpoints established by T-NG-RAN for indirect data forwarding.

[0222] 11f. SMF to T-AMF: Nsmf_PDUSession_UpdateSMContext response (N2 SM information).

[0223] The SMF sends the Nsmf_PDUSession_UpdateSMContext response message for each PDU session to the T-AMF.

[0224] Based on the NG-RAN’s instructions and / or activation time, the SMF configures the PSA UPF to activate / deactivate the PDU Set identification and marking.

[0225] In the case where the PSA UPF identifies and marks PDUs with PDU Set information in the GTP-U header, it shall do so starting from a complete PDU set. (In addition, if the source NG-RAN sends a PDU that follows an End Marker packet and is not the start of a complete PDU set, a portion of the sent PDUs will be overlapped to perform PDU Set encapsulation.) The PSA UPF identifies and marks PDUs with PDU Set information in the GTP-U header and shall do so starting from a complete PDU set. The first PDU set will include PDUs that overlap with packets sent through the source forwarding tunnel if no End Marker packet is sent at the end of a complete PDU set.

[0226] The SMF creates an N2 SM message containing the DL forwarding tunnel information for the AMF to send to the S-NG-RAN. The SMF includes this information in the Nsmf_PDUSession_UpdateSMContext response. The DL forwarding tunnel information can be one of the following: (The SMF sends a Session Update Response message, which is carried in the downlink forwarding information, including direct and indirect.)

[0227] If direct forwarding is applied, the SMF includes the T-NG-RAN N3 forwarding information received in step 11a.

[0228] If an indirect forwarding tunnel is set up in step 11b or 11d, the SMF includes the DL forwarding information of the T-UPF or S-UPF, including the N3 UP address and DL tunnel ID of the UPF.

[0229] 12. Response message of step 3, T-AMF to S-AMF: Namf_Communication_CreateUEContext response (including the N2 information required by S-AMF to send a handover command to S-NG-RAN, including the target to source transparent container, the list of PDU sessions that failed to be established, N2 SM information (N3 downlink forwarding information, PCF ID), [target AMF ID]).

[0230] The target to source transport container is received by T-NG-RAN. The N2 SM information is received by the SMF in step 11f.

[0231] As shown in Figure 4B, during the execution phase:

[0232] After the above preparation stage,

[0233] 1. The S-AMF initiates a handover command to the S-NG-RAN, notifying it of the completion of handover preparation and executing the handover. The command carries all handover session information obtained from the S-NG-RAN, the N2 SM information for each session, and the T-NG-RAN N3 forwarding tunnel information for direct forwarding or the S-UPF N3 forwarding tunnel information for indirect forwarding.

[0234] 2 to 15b, enhanced processing of S-NG-RAN, T-NG-RAN, SMF and PSA UPF, and UPF end data (End Marker) packet processing.

[0235] Among them, 10a and 10b, after the data forwarding is completed, the PSA UPF sends end data packets (End Marker packets) to the S-NG-RAN after the handover path is completed, and forwarded to the T-NG-RAN. Or the End Marker packets are forwarded to the T-NG-RAN through the indirect forwarding T-UPF.

[0236] In some embodiments, the PSA UPF sends End Marker packets to the target NG-RAN at the end of a complete PDU set. In other words, the PSA UPF starts performing PDUset identification and extended protocol header marking at the beginning of a complete PDU set (e.g., the first packet) and stops or ends performing PDUset identification and extended protocol header marking at the end of a complete PDU set (e.g., the last packet) (End Marker packets are sent just after the last packet of the PDU set).

[0237] Alternatively, the PSA UPF identifies and marks PDUs with PDU Set information (e.g., identifying PDUs with RTP or RTCP extended protocol headers, mapping the protocol extension headers with PDUSet information into GTP-U protocol extension headers, and carrying the PDUSet information to the NG-RAN in the GTP-U extended protocol headers). It does this starting from a complete PDU set. The first PDU set includes PDUs that overlap with packets sent through the source forwarding tunnel (here the overlapping packets have been sent on the source channel, but are not the end of a PDUset, such as the first half of the Set, then this part and the unsent second half are taken together as a complete PDUset and sent on the new channel). If the end marker packet is not sent at the end of a complete PDU set (e.g., it is sent in the middle of a PDUSet),

[0238] Alternatively, the PSA UPF identifies and marks the PDU with PDU Set information (for example, it identifies the PDU with the RTP or RTCP extended protocol header, maps the protocol extension header with the PDUSet information into the GTP-U protocol extension header, and carries the PDUSet information to the NG-RAN in the GTP-U extended protocol header). It sends the remaining data packets of the PDU set sent through the source forwarding tunnel as single data packets. Then, it starts from a complete PDU set, identifies the data packets and marks the PDUset information to the extended protocol header, if the end marker packet is not sent at the end of a complete PDU set (for example, it is sent in the middle of the PDUSet).

[0239] In some embodiments, the source NG-RAN node receives one or more GTP-U end marker packets per PDU session from the UPF and copies the end marker packets into each data forwarding tunnel when user data packets are no longer required to be forwarded on that tunnel.

[0240] An end marker packet sent over a data forwarding tunnel applies to all QoS flows forwarded over that tunnel. After an end marker packet has been received over a forwarding tunnel, the target NG-RAN node can start considering packets received over NG-U PDU session tunnels for QoS flows associated with that forwarding tunnel.

[0241] To facilitate understanding of the embodiments of the present disclosure, the following exemplary embodiments are provided.

[0242] The 5GS system supports QoS processing in which either PDU-based QoS rules and parameter policies or PDU set-based QoS rules and parameter policies are supported within the same QoS flow. This means that only one set of QoS parameters can be activated simultaneously within a QoS flow, either the PDU-based QoS mechanism or the PDU set-based QoS mechanism.

[0243] However, in the actual network, there are various types of NG-RAN (Non-homogenous support) with different functional support. For example, there are NG-RANs that do not support PDU set processing and NG-RANs that support PDU set processing. Due to the business continuity requirements of XR, data forwarding is required for downlink data in the handover process (such as terminal mobility). (Data forwarding supports direct and indirect modes. In direct mode, the source NG-RAN forwards to the target NG-RAN. In indirect mode, the UPF performs data forwarding to the target-NG-RAN. It should be noted that in indirect mode, the UPF that performs data forwarding is not necessarily the UPF corresponding to the source NG-RAN.

[0244] Among them, when handover (HO) occurs between an NG-RAN that does not support PDU set processing and an NG-RAN that supports PDU set processing, especially when switching from a source NG-RAN that does not support PDU set processing to a target NG-RAN that supports PDU set processing, unmarked PDUs and marked PDUs will exist in the same QoS flow at the same time.

[0245] However, the 5GS system does not support the scenario where unmarked PDUs and marked PDUs coexist in the same QoS flow, and cannot guarantee the QoS of the corresponding QoS flow.

[0246] How to deal with the coexistence of unmarked PDUs and marked PDUs in QoS flows is a problem that 5GS must solve to ensure XR interactive services such as cloud gaming.

[0247] In the embodiment of the present disclosure, NG-RAN does not simultaneously support mixed processing of marked PDUs and unmarked PDUs in the same QoS flow (only one PDU format is processed at the same time, and only the QoS parameters corresponding to one PDU format are executed. The marked protocol extension header is ignored and processed as an unmarked PDU, according to the PDUQoS parameters. Or vice versa. Or the unprocessed PDU with the marked protocol extension header is discarded. Alternatively, the PDU Set QoS processing function is delayed by SMF, or the PDU Set QoS processing function is activated but delayed to be applied, so that the two PDUs are processed at different times. In this way, only the same PDU will be received in NG-RAN at the same time, and there will be no mixed state of marked and unmarked PDUs, and no special processing is required by NG-RAN). NG-RAN performs corresponding processing according to the notification instructions of SMF to solve the above problems.

[0248] In some embodiments, the SMF notifies the T-NG-RAN of the indication processing, including one or more of the following methods:

[0249] 1) The SMF carries the PDU set activation timer to the T-NG-RAN. Before the timer expires, the T-NG-RAN processes the received marked PDU as an unmarked PDU and ignores the enhanced header information carrying the PDU set information.

[0250] 2) The SMF carries the priority indication to the T-NG-RAN;

[0251] The priority indication may indicate at least one of the following:

[0252] -After receiving the marked PDU, the processing based on PDU set is performed first

[0253] -After receiving the marked PDU, the unmarked PDU is processed first (ignoring the PDU set information carried by the header enhancement);

[0254] -After receiving the marked PDU, it will be executed based on the local configuration of T-NG-RAN first;

[0255] -After receiving the marked PDU, it will be executed according to the OAM configuration first;

[0256] Among them, T-NG-RAN executes the corresponding processing method based on the received priority indication.

[0257] Furthermore, the priority indication information may also include a priority list, which includes the contents of different priority indications and the priorities corresponding to the contents of different priority indications (thereby, NGRANs with different capabilities can be combined with local configuration or OAM configuration combined with the priority list for comprehensive execution).

[0258] 3) After receiving the indication from T-NG-RAN that PDU set-based processing is supported, the SMF delays initiating PDU session modification (or initiates session modification but indicates that the modified new QoS parameters and the new processing of the identification marked packet are executed or applied with a delay according to the indicated time or time window);

[0259] In some embodiments, the SMF can carry PDU set QoS parameters to the UPF and NG-RAN to activate PDU set-based QoS processing.

[0260] In some embodiments, the SMF notifies the UPF to perform delayed PDU Set identification and marking; wherein the SMF may determine the delay time based on local configuration, OAM configuration, or NG-RAN notification information; the SMF may set a PDU set activation timer (timer), initiate a PDU session modification after the timer times out, and activate the QoS processing of the PDU set; or the SMF notifies the UPF to delay the execution of PDU set QoS and PDU identification and marking, and the UPF determines the delay time based on local forwarding data (data forwarding) / end data packets (End marker packets) / time / local configuration / OAM configuration, and delays the execution of PDU set QoS and PDU identification and marking. The UPF and NG-RAN execute according to the SMF notification, including activating PDU set QoS processing and / or performing delayed PDU Set identification and marking.

[0261] In some embodiments, after the above SMF delay activation session modification and QoS parameter update, or delayed application after activation and update, the time when the two PDUs (marked and unmarked PDUs) arrive at the NG-RAN is staggered, so that the NG-RAN will only receive the same PDU at the same time, and there will be no mixed state of marked and unmarked PDUs, without the need for NG-RAN to perform special processing, or the time when the two PDUs (marked and unmarked PDUs) arrive at the NG-RAN is staggered as much as possible. A small amount of mixed PDUs can be discarded according to QoS parameters, or the protocol enhancement header processing can be ignored according to the function.

[0262] In some embodiments, the PSA UPF sends End Marker packets to the target NG-RAN at the end of a complete PDU set. In other words, the PSA UPF starts performing PDUset identification and extended protocol header marking at the beginning of a complete PDU set (e.g., the first packet) and stops or ends performing PDUset identification and extended protocol header marking at the end of a complete PDU set (e.g., the last packet) (End Marker packets are sent just after the last packet of the PDU set).

[0263] Alternatively, the PSA UPF identifies and marks PDUs with PDU Set information (e.g., identifying PDUs with RTP or RTCP extended protocol headers, mapping the protocol extension headers with PDUSet information into GTP-U protocol extension headers, and carrying the PDUSet information to the NG-RAN in the GTP-U extended protocol headers). It does this starting from a complete PDU set. The first PDU set includes PDUs that overlap with packets sent through the source forwarding tunnel (here the overlapping packets have been sent on the source channel, but are not the end of a PDUset, such as the first half of the Set, then this part and the unsent second half are taken together as a complete PDUset and sent on the new channel). If the end marker packet is not sent at the end of a complete PDU set (e.g., it is sent in the middle of a PDUSet),

[0264] Alternatively, the PSA UPF identifies and marks the PDU with PDU Set information (for example, it identifies the PDU with the RTP or RTCP extended protocol header, maps the protocol extension header with the PDUSet information into the GTP-U protocol extension header, and carries the PDUSet information to the NG-RAN in the GTP-U extended protocol header). It sends the remaining data packets of the PDU set sent through the source forwarding tunnel as single data packets. Then, it starts from a complete PDU set, identifies the data packets and marks the PDUset information to the extended protocol header, if the end marker packet is not sent at the end of a complete PDU set (for example, it is sent in the middle of the PDUSet).

[0265] In an exemplary embodiment, as shown in Figure 3, the case where the source NG-RAN switches to the target NG-RAN, the AMF is not changed, and the SMF decides to retain the existing UPF and switches the terminal from the source NG-RAN to the target NG-RAN through Xn is used as an example for explanation.

[0266] 1a. If the PLMN has configured Secondary RAT usage reporting, the source NG-RAN node may provide a RAN usage data report (N2 SM information (Secondary RAT usage data), handover flag, source to target transparent container) to the AMF during the handover execution phase. The source NG-RAN node will only provide this report after the target NG-RAN confirms the handover over the Xn interface. The handover flag indicates to the AMF that it should buffer the N2 SM information containing the usage data report before forwarding it.

[0267] 1b. Target NG-RAN to AMF: N2 path handover request (list of PDU sessions to be switched and N2 SM information, list of PDU sessions that could not be established, where the failure reason is given in the N2 SM information element, UE location information).

[0268] The target NG-RAN sends an N2 Path Switch Request message to the AMF to notify the UE that it has moved to a new target cell and provide a list of PDU sessions to be switched. The AN tunnel information of each PDU session to be switched is included in the N2 SM information.

[0269] For the PDU Session to be handed over to the target NG-RAN, the N2 Path Switch Request message shall include a list of accepted QoS Flows. For each QoS Flow for which an alternative QoS profile was accepted, the N2 SM information shall contain a reference to the alternative QoS profile that was satisfied.

[0270] In some embodiments, in an Xn handover over NG-RAN, the target NG-RAN provides an indication to the SMF whether the target NG-RAN node supports PDU Set based processing; the "PDU Set Support" indication from the target NG-RAN will be included in the Path Switch Request message (Xn Handover).

[0271] 2. The AMF sends an Nsmf_PDUSession_UpdateSMContext request to the SMF (with the N2 SM information from the T-NG-RAN received in step 1b and the N2 SM information from the source NG-RAN (Secondary RAT Usage Data), UE location information, and UE presence in the LADN service area). The N2 SM information from the source NG-RAN is buffered in step 1a, if applicable.

[0272] The AMF sends N2 SM information for each PDU Session received in the N2 Path Switch Request by calling the Nsmf_PDUSession_UpdateSMContext request service operation. These PDU Session lists are received in the N2 Path Switch Request. Including step 1, the target NG-RAN provides an indication to the SMF whether the target NG-RAN node supports PDU Set-based processing; the "PDU set support" indication from the target NG-RAN will be included in the Path Switch Request message (Xn Handover).

[0273] The Nsmf_PDUSession_UpdateSMContext request contains one of the following: an indication that the PDU Session is to be switched (along with information about the N3 addressing to be used and the transported QoS flows), or an indication that the PDU Session is to be rejected (along with the rejection reason).

[0274] If the QoS flows of some PDU Sessions are not accepted by the target NG-RAN, the SMF will initiate the PDU Session Modification procedure after the handover process is completed to remove the unaccepted QoS flows from the PDU Session.

[0275] 3. SMF to UPF: N4 session modification request (AN tunnel information)

[0276] For a PDU Session modified by the target NG-RAN, the SMF sends an N4 Session Modification Request message to the UPF. The SMF may notify the UPF that originally initiated the data notification to discard the downlink data of the PDU Session and / or not to provide further data notification messages.

[0277] Depending on the network deployment, the CN tunnel information used to connect to the target NG-RAN and the UPF connected to the source NG-RAN may be different, for example because the source NG-RAN and the target NG-RAN are in different IP domains. In this case, the SMF can ask the UPF to allocate new CN tunnel information and provide the target network instance.

[0278] 4. UPF to SMF: N4 session modification response (CN tunnel information)

[0279] For the switched PDU Session, the UPF returns an N4 Session Modification Response message to the SMF after the requested PDU Session completes the switch. The tunnel identifier of the UL traffic is included only for the PDU Session that has not released user plane resources and is requested by the SMF.

[0280] 5. To assist the reordering function in the target NG-RAN, the UPF sends one or more “end marker” packets for each N3 tunnel on the old path immediately after the handover. The UPF starts sending downlink packets to the target NG-RAN.

[0281] In some embodiments, the PSA UPF sends End Marker packets to the target NG-RAN at the end of a complete PDU set. In other words, the PSA UPF starts performing PDUset identification and extended protocol header marking at the beginning of a complete PDU set (e.g., the first packet) and stops or ends performing PDUset identification and extended protocol header marking at the end of a complete PDU set (e.g., the last packet) (End Marker packets are sent just after the last packet of the PDU set).

[0282] Alternatively, the PSA UPF identifies and marks PDUs with PDU Set information (e.g., identifying PDUs with RTP or RTCP extended protocol headers, mapping the protocol extension headers with PDUSet information into GTP-U protocol extension headers, and carrying the PDUSet information to the NG-RAN in the GTP-U extended protocol headers). It does this starting from a complete PDU set. The first PDU set includes PDUs that overlap with packets sent through the source forwarding tunnel (here the overlapping packets have been sent on the source channel, but are not the end of a PDUset, such as the first half of the Set, then this part and the unsent second half are taken together as a complete PDUset and sent on the new channel). If the end marker packet is not sent at the end of a complete PDU set (e.g., it is sent in the middle of a PDUSet),

[0283] Alternatively, the PSA UPF identifies and marks the PDU with PDU Set information (for example, it identifies the PDU with the RTP or RTCP extended protocol header, maps the protocol extension header with the PDUSet information into the GTP-U protocol extension header, and carries the PDUSet information to the NG-RAN in the GTP-U extended protocol header). It sends the remaining data packets of the PDU set sent through the source forwarding tunnel as single data packets. Then, it starts from a complete PDU set, identifies the data packets and marks the PDUset information to the extended protocol header, if the end marker packet is not sent at the end of a complete PDU set (for example, it is sent in the middle of the PDUSet).

[0284] Based on the NG-RAN indication and / or activation time, the SMF configures the PSA UPF to activate / deactivate the PDU Set identification and marking.

[0285] In the case where the PSA UPF identifies and marks PDUs with PDU Set information in the GTP-U header, it shall do so starting from a complete PDU set. (In addition, if the source NG-RAN sends, the PDU following the End Marker packet is not the start of a complete PDU set, and a portion of the sent PDUs will be overlapped to perform PDU Set encapsulation.) The PSA UPF identifies and marks PDUs with PDU Set information in the GTP-U header, starting from a complete PDU set. The first PDU set will include PDUs that overlap with packets sent through the source forwarding tunnel if no End Marker packet is sent at the end of a complete PDU set.

[0286] 6. SMF sends Nsmf_PDUSession_UpdateSMContext response to AMF (N2 SM information)

[0287] The SMF sends an Nsmf_PDUSession_UpdateSMContext response (N2 SM information (CN tunnel information, updated CN PDB for accepted QoS flows, updated TSCAI for accepted QoS flows)) to the successfully handed over PDU Session. The CN tunnel information sent by the UPF to the AMF is used to set up the N3 tunnel. For each accepted GBR QoS flow of delay critical resource type, the SMF may update the dynamic CN PDB and TSCAI and send them to the target NG-RAN. The SMF may update the CN PDB and TSCAI in the response based on local configuration or use a separate PDU Session Modification procedure to update them.

[0288] NOTE: Step 6 can occur at any time after the SMF receives the N4 Session Modification Response.

[0289] In the embodiment of the present disclosure, NG-RAN does not simultaneously support mixed processing of marked PDUs and unmarked PDUs in the same QoS flow (only one PDU format is processed at the same time, and only the QoS parameters corresponding to one PDU format are executed. The marked protocol extension header is ignored and processed as an unmarked PDU, according to the PDUQoS parameters. Or vice versa. Or the unprocessed PDU with the marked protocol extension header is discarded. Alternatively, the PDU Set QoS processing function is delayed by SMF, or the PDU Set QoS processing function is activated but delayed to be applied, so that the two PDUs are processed at different times. In this way, only the same PDU will be received in NG-RAN at the same time, and there will be no mixed state of marked and unmarked PDUs, and no special processing is required by NG-RAN). NG-RAN performs corresponding processing according to the notification instructions of SMF to solve the above problems.

[0290] In some embodiments, the SMF notifies the T-NG-RAN of the indication processing, including one or more of the following methods:

[0291] 1) The SMF carries the PDU set activation timer to the T-NG-RAN. Before the timer expires, the T-NG-RAN processes the received marked PDU as an unmarked PDU and ignores the enhanced header information carrying the PDU set information.

[0292] 2) The SMF carries the priority indication to the T-NG-RAN;

[0293] The priority indication may indicate at least one of the following:

[0294] -After receiving the marked PDU, the processing based on PDU set is performed first

[0295] -After receiving the marked PDU, the unmarked PDU is processed first (ignoring the PDU set information carried by the header enhancement);

[0296] -After receiving the marked PDU, it will be executed based on the local configuration of T-NG-RAN first;

[0297] -After receiving the marked PDU, it will be executed according to the OAM configuration first;

[0298] Among them, T-NG-RAN executes the corresponding processing method based on the received priority indication.

[0299] Furthermore, the priority indication information may also include a priority list, which includes the contents of different priority indications and the priorities corresponding to the contents of different priority indications (thereby, NGRANs with different capabilities can be combined with local configuration or OAM configuration combined with the priority list for comprehensive execution).

[0300] 3) After receiving the indication from T-NG-RAN that PDU set-based processing is supported, the SMF delays initiating PDU session modification (or initiates session modification but indicates that the modified new QoS parameters and the new processing of the identification marked packet are executed or applied with a delay according to the indicated time or time window);

[0301] In some embodiments, the SMF can carry PDU set QoS parameters to the UPF and NG-RAN to activate PDU set-based QoS processing.

[0302] In some embodiments, the SMF notifies the UPF to perform delayed PDU Set identification and marking; wherein the SMF may determine the delay time based on local configuration, OAM configuration, or NG-RAN notification information; the SMF may set a PDU set activation timer (timer), initiate a PDU session modification after the timer times out, and activate the QoS processing of the PDU set; or the SMF notifies the UPF to delay the execution of PDU set QoS and PDU identification and marking, and the UPF determines the delay time based on local forwarding data (data forwarding) / end data packets (End marker packets) / time / local configuration / OAM configuration, and delays the execution of PDU set QoS and PDU identification and marking. The UPF and NG-RAN execute according to the SMF notification, including activating PDU set QoS processing and / or performing delayed PDU Set identification and marking.

[0303] In some embodiments, after the above SMF delay activation session modification and QoS parameter update, or delayed application after activation and update, the time when the two PDUs (marked and unmarked PDUs) arrive at the NG-RAN is staggered, so that the NG-RAN will only receive the same PDU at the same time, and there will be no mixed state of marked and unmarked PDUs, without the need for NG-RAN to perform special processing, or the time when the two PDUs (marked and unmarked PDUs) arrive at the NG-RAN is staggered as much as possible. A small amount of mixed PDUs can be discarded according to QoS parameters, or the protocol enhancement header processing can be ignored according to the function.

[0304] For XR service flows, the SMF sends the corresponding PDU set QoS parameters and flow description information in this message to the target NG-RAN. Alternatively, the SMF may subsequently initiate a separate PDU session modification process, carrying the updated PDU set QoS parameters and flow description information.

[0305] If the source NG-RAN does not support alternative QoS profiles and the target NG-RAN supports them, the SMF sends the available alternative QoS profiles to the target NG-RAN on a per QoS flow basis.

[0306] 7. AMF to NG-RAN: N2 path switching request confirmation (N2 SM information, unsuccessful PDU session, UE radio capability identifier).

[0307] 8. The target NG-RAN confirms the handover success by sending a Release Resources message to the source NG-RAN. The target NG-RAN then triggers the release of resources with the source NG-RAN.

[0308] 9. If one of the triggering conditions of the registration procedure applies, the terminal may initiate the mobility registration update procedure.

[0309] In an exemplary embodiment, as shown in Figures 4A and 4B , a non-Xn handover of the N2 interface of the source NG-RAN to the target NG-RAN includes a preparation phase as shown in Figure 4A and an execution phase as shown in Figure 4B . This description is made using an example where the source NG-RAN is an S-NG-RAN, the source AMF is an S-AMF, the source UPF is an S-UPF, the target NG-RAN is a T-NG-RAN, the target AMF is a T-AMF, and the target UPF is a T-UPF.

[0310] In the preparation phase, step 10 carries an indication of T-NG-RAN's PUD set support to the SMF.

[0311] As shown in Figure 4A, the preparation stage:

[0312] 1. S-NG-RAN sends a handover request (target ID, source-to-target transparent container, SM N2 information list, PDU session ID, intra-system handover indication) to S-AMF.

[0313] The source-to-destination transparent container includes NG-RAN information created by S-NG-RAN for use by T-NG-RAN and is transparent to 5GC. For each PDU session, it also contains the corresponding QoS flow / DRB information that will be affected by data forwarding.

[0314] 2-7 Select new AMF and UPF and obtain new UPF tunnel information.

[0315] 7. SMF to T-AMF: Nsmf_PDUSession_UpdateSMContext response (PDU session identifier, N2 SM information, reason for non-acceptance).

[0316] If the N2 handover of the PDU session is accepted, the SMF includes the N2 SM information in the Nsmf_PDUSession_UpdateSMContext response, which contains the N3 UP address and UL CN tunnel ID of the UPF, QoS parameters, TSCAI and user plane security execution information of the target NG-RAN.

[0317] 8. T-AMF supervises the Nsmf_PDUSession_UpdateSMContext response message from the involved SMFs.

[0318] 9. T-AMF to T-NG-RAN: Handover Request (source to target transparent container, N2MM information, N2 SM information list, tracking request, terminal radio capability identifier). The T-AMF determines the T-NG-RAN based on the target identifier. The T-AMF may allocate a valid 5G-GUTI for the terminal in the T-AMF and target TAI.

[0319] The source to target transparent container is forwarded as received from the S-NG-RAN. The N2MM information includes security information and mobility restriction list (if available in T-AMF).

[0320] The N2 SM information list includes the N2 SM information received from the SMF within the maximum allowed delay in the Nsmf_PDUSession_UpdateSMContext response message supervised by the T-AMF in step 8, which is prepared for T-NG-RAN.

[0321] 10. T-NG-RAN to T-AMF: Handover Request Acknowledgement (target to source transparent container, list of PDU Sessions to be handed over with N2 SM information, list of PDU Sessions that could not be established with the failure reason given in the N2 SM information element).

[0322] In case of NG-RAN N2 handover, T-NG-RAN provides an indication to the SMF whether the T-NG-RAN node supports PDUset-based processing; the "PDU set support" indication from T-NG-RAN is provided in the Handover Request Confirm message (NG Handover) (Step 10 message).

[0323] The N2 SM information in the "PDU session list to be switched" contains the T-NG-RAN N3 addressing information of each PDU session, namely the N3 UP address of the PDU session and the tunnel ID of the T-NG-RAN.

[0324] N2 SM information may also include:

[0325] - If the PDU session has at least one QoS flow that requires data forwarding, the N3 UP address and tunnel ID of the T-NG-RAN for receiving the forwarded data are included. The T-NG-RAN provides the data forwarding address for each data forwarding tunnel it decides to set up.

[0326] - For each QoS flow that employs an alternative QoS configuration, T-NG-RAN shall include a reference to the satisfied alternative QoS configuration.

[0327] 11a-f, T-AMF exchanges tunnel information with T-NG-RAN, S-UPF, and T-UPF through SMF. 11a and 11f are executed during direct forwarding, while intermediate processes are executed during indirect forwarding to exchange channel information.

[0328] 11a. T-AMF to SMF: Nsmf_PDUSession_UpdateSMContext request (PDU session identifier, N2 SM response received from T-NG-RAN in step 10).

[0329] For each N2 SM response received from T-NG-RAN (N2 SM information contained in the Handover Request Acknowledgement), the T-AMF sends the received N2 SM response to the SMF indicated by the corresponding PDU Session ID.

[0330] If no new T-UPF is selected, the SMF stores the N3 tunnel information of the T-NG-RAN in the N2 SM response if the T-NG-RAN accepts the N2 handover.

[0331] The SMF / UPF allocates an N3 UP address and tunnel ID for indirect data forwarding to correspond to the data forwarding tunnel endpoint established by T-NG-RAN.

[0332] 11f. SMF to T-AMF: Nsmf_PDUSession_UpdateSMContext response (N2 SM information).

[0333] The SMF sends an Nsmf_PDUSession_UpdateSMContext response message to the T-AMF, one for each PDU session.

[0334] The SMF creates an N2 SM message containing the downlink (DL) forwarding tunnel information for the AMF to send to the S-NG-RAN. The SMF includes this information in the Nsmf_PDUSession_UpdateSMContext response message. The downlink forwarding tunnel information can be one of the following: (The SMF sends a session update response message, which is carried by the downlink forwarding information, including direct and indirect.)

[0335] - If direct forwarding is applied, the SMF shall include the T-RNG-AN N3 forwarding information received in step 11a.

[0336] - If an indirect forwarding tunnel is set up in step 11b or 11d, the SMF shall include the DL forwarding information of the T-UPF or S-UPF, which contains the N3 UP address and the DL tunnel ID of the UPF.

[0337] 12. Response message of step 3. T-AMF to S-AMF: Namf_Communication_CreateUEContext response (S-AMF sends the N2 information required for the handover command to S-NG-RAN, including target to source transparent container, PDU session setup failure list, N2 SM information (N3DL forwarding information, PCF ID), [T-AMF ID]).

[0338] The target-to-source transparent container is received from the T-NG-RAN to support the sending of a Handover Command to the S-NG-RAN. It contains NG-RAN information, created by the S-NG-RAN for use with the T-NG-RAN and transparent to the 5GC. It also includes the corresponding QoS flow / DRB information for each PDU session to support data forwarding.

[0339] PDU session setup failure list: lists the PDU sessions that could not be established during the handover process, and gives the failure reasons.

[0340] N2 SM Information (N3 Downlink Forwarding Information, PCF ID): This information is received from the SMF in step 11f. The N3 Downlink Forwarding Information refers to the target T-NG-RAN downlink forwarding tunnel information contained in the N2 SM information, including the N3 UP address and downlink tunnel ID. The PCF ID is the identifier of the policy control function and represents the ID of the policy control function.

[0341] Target AMF ID: If necessary, it may contain the identifier of the target AMF.

[0342] T-AMF to S-AMF: Namf_Communication_CreateUEContext response provides various information required to send the handover command to support the handover process from S-AMF to S-NG-RAN.

[0343] Receive the target to source transport container from T-NG-RAN. In step 11f, receive N2 SM information from SMF.

[0344] As shown in Figure 4B, during the execution phase:

[0345] After the above preparation stage,

[0346] 1. The S-AMF initiates a handover command to the S-NG-RAN, notifying it of the completion of handover preparation and executing the handover. The command carries all handover session information obtained from the S-NG-RAN, the N2 SM information for each session, and the T-NG-RAN N3 forwarding tunnel information for direct forwarding or the S-UPF N3 forwarding tunnel information for indirect forwarding.

[0347] 2 to 15b, enhanced processing of S-NG-RAN, T-NG-RAN, SMF, and PSA UPF, as well as UPF End Marker packet processing. The enhancement of the main SMF notification indication can be performed in steps 10, 11, and 15, or by initiating a separate session modification process.

[0348] Among them, 10a and 10b, after the data forwarding is completed, the PSA UPF sends end data packets (End Marker packets) to the S-NG-RAN after the handover path is completed, and forwarded to the T-NG-RAN. Or the End Marker packets are forwarded to the T-NG-RAN through the indirect forwarding T-UPF.

[0349] In some embodiments, the PSA UPF sends End Marker packets to the target NG-RAN at the end of a complete PDU set. In other words, the PSA UPF starts performing PDUset identification and extended protocol header marking at the beginning of a complete PDU set (e.g., the first packet) and stops or ends performing PDUset identification and extended protocol header marking at the end of a complete PDU set (e.g., the last packet) (End Marker packets are sent just after the last packet of the PDU set).

[0350] Alternatively, the PSA UPF identifies and marks PDUs with PDU Set information (e.g., identifying PDUs with RTP or RTCP extended protocol headers, mapping the protocol extension headers with PDUSet information into GTP-U protocol extension headers, and carrying the PDUSet information to the NG-RAN in the GTP-U extended protocol headers). It does this starting from a complete PDU set. The first PDU set includes PDUs that overlap with packets sent through the source forwarding tunnel (here the overlapping packets have been sent on the source channel, but are not the end of a PDUset, such as the first half of the Set, then this part and the unsent second half are taken together as a complete PDUset and sent on the new channel). If the end marker packet is not sent at the end of a complete PDU set (e.g., it is sent in the middle of a PDUSet),

[0351] Alternatively, the PSA UPF identifies and marks the PDU with PDU Set information (for example, it identifies the PDU with the RTP or RTCP extended protocol header, maps the protocol extension header with the PDUSet information into the GTP-U protocol extension header, and carries the PDUSet information to the NG-RAN in the GTP-U extended protocol header). It sends the remaining data packets of the PDU set sent through the source forwarding tunnel as single data packets. Then, it starts from a complete PDU set, identifies the data packets and marks the PDUset information to the extended protocol header, if the end marker packet is not sent at the end of a complete PDU set (for example, it is sent in the middle of the PDUSet).

[0352] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0353] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0354] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0355] Figure 5A is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure. Communication device 8100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 8100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0356] As shown in Figure 5A, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 8100 is used to perform any of the above methods. Optionally, one or more processors 8101 are used to call instructions to enable the communication device 8100 to perform any of the above methods.

[0357] In some embodiments, the communication device 8100 further includes one or more transceivers 8102. When the communication device 8100 includes one or more transceivers 8102, the transceiver 8102 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method, and the processor 8101 performs at least one of the other steps. In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0358] In some embodiments, the communication device 8100 further includes one or more memories 8103 for storing data. Alternatively, all or part of the memories 8103 may be located outside the communication device 8100. In alternative embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuits 8104 are connected to the memory 8102 and may be configured to receive data from the memory 8102 or other devices, or to send data to the memory 8102 or other devices. For example, the interface circuits 8104 may read data stored in the memory 8102 and send the data to the processor 8101.

[0359] The communication device 8100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 5A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0360] 5B is a schematic diagram of the structure of the chip 8200 proposed in an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG5B, but the present disclosure is not limited thereto.

[0361] The chip 8200 includes one or more processors 8201. The chip 8200 is configured to execute any of the above methods.

[0362] In some embodiments, chip 8200 further includes one or more interface circuits 8202. Terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 8200 further includes one or more memories 8203 for storing data. Alternatively, all or part of memory 8203 may be located external to chip 8200. Optionally, interface circuit 8202 is connected to memory 8203 and may be used to receive data from memory 8203 or other devices, or may be used to send data to memory 8203 or other devices. For example, interface circuit 8202 may read data stored in memory 8203 and send the data to processor 8201.

[0363] In some embodiments, the interface circuit 8202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 8202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 8202 performs data exchange between the processor 8201, the chip 8200, the memory 8203, or the transceiver device. In some embodiments, the processor 8201 performs at least one of the other steps.

[0364] The modules and / or devices described in various embodiments, such as virtual devices, physical devices, and chips, can be arbitrarily combined or separated according to circumstances. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0365] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto, and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto, and may also be a temporary storage medium.

[0366] The present disclosure also provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0367] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A business processing method, characterized in that: include: The first access network device sends first indication information to the first network element, wherein the first indication information is used to indicate whether the first access network device supports processing based on a packet data unit PDU set.

2. The method according to claim 1, characterized in that The method further comprises: The first access network device determines to process the marked PDU in the forwarded data packet as an unmarked PDU, wherein the first access network device does not support PDU set-based processing, and the forwarded data packet includes the marked PDU; or The first access network device determines to process the marked PDU in the forwarded data packet as an unmarked PDU before the unmarked PDU processing is completed, wherein the first access network device supports PDU set-based processing, and the forwarded data packet includes the marked PDU.

3. The method according to claim 2, characterized in that The method further comprises: When certain conditions are met, a timer is started; When the timer expires, the processing of the marked PDU is started, wherein the duration of the timer is the duration of the processing of the unmarked PDU.

4. The method according to claim 3, characterized in that The specific conditions include at least one of the following: Receive the end marker packet; Receive the quality of service QoS parameters based on PDU set sent by the first network element, and send an activation response to the first network element.

5. The method according to claim 2, characterized in that The method further comprises: The first network element sends an activation indication to the first access network device, wherein the activation indication is used to instruct the first access network device to activate PDU set-based processing.

6. The method according to claim 5, characterized in that The method further comprises: The first access network device sends an activation response to the first network element, wherein the activation response is used to indicate at least one of the following: Whether the QoS parameters based on the PDU set are active; Activation time; Delay activation time.

7. The method according to claim 2, characterized in that The method further comprises: The first access network device sends second indication information to the first network element, wherein the second indication information is used to indicate the time required for processing an unmarked PDU. The first network element determines a delayed activation time according to the second indication information; The first network element sends an activation indication to the first access network device after the delayed activation time, wherein the activation indication is used to instruct the first access network device to activate PDU set-based processing.

8. The method according to any one of claims 5 to 7, characterized in that The activation indication includes QoS parameters based on the PDU set.

9. The method according to claim 1, characterized in that The method further comprises: The first access network device receives a priority indication sent by the first network element; The first network element performs processing of the marked PDU and the unmarked PDU according to the priority indication; The priority indication is used to indicate at least one of the following: After receiving the marked PDU, the processing based on PDU set is performed first; After receiving the marked PDU, the unmarked PDU is processed first; After receiving the marked PDU, it is preferentially executed based on the local configuration of the first access network device; After receiving the marked PDU, it will be executed according to the operation management and maintenance OAM configuration first.

10. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the method according to any one of claims 1 to 9.

Images