WO2025035341A1 - 业务处理方法及装置 - Google Patents

业务处理方法及装置 Download PDF

Info

Publication number
WO2025035341A1
WO2025035341A1 PCT/CN2023/112777 CN2023112777W WO2025035341A1 WO 2025035341 A1 WO2025035341 A1 WO 2025035341A1 CN 2023112777 W CN2023112777 W CN 2023112777W WO 2025035341 A1 WO2025035341 A1 WO 2025035341A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu
ran
information
processing
target
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/112777
Other languages
English (en)
French (fr)
Inventor
吴锦花
毛玉欣
刘建宁
沈洋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Xiaomi Mobile Software Co Ltd
Original Assignee
Beijing Xiaomi Mobile Software Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Xiaomi Mobile Software Co Ltd filed Critical Beijing Xiaomi Mobile Software Co Ltd
Priority to PCT/CN2023/112777 priority Critical patent/WO2025035341A1/zh
Priority to CN202380010579.7A priority patent/CN117322051A/zh
Publication of WO2025035341A1 publication Critical patent/WO2025035341A1/zh
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a service processing method and device.
  • XR services also involve multimodal data streams, which can be data input from the same device or different devices (including sensors) to describe the same service or application, and these data may be output to one or more destination device terminals.
  • the data streams in multimodal data are often related, such as the synchronization of audio and video streams, and the synchronization of touch and vision.
  • the embodiments of the present disclosure provide a service processing method and device, which are used to solve the problem of how to process the coexistence of unmarked PDUs and marked PDUs in a QoS flow.
  • the embodiments of the present disclosure provide a service processing method and device.
  • a service processing method comprising: 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 a marked PDU in a 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 processing of the unmarked PDU is completed, wherein the first access network device supports processing based on a PDU set, and the forwarded data packet includes a marked PDU.
  • a service processing method including: a first access network device sends 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 according to the priority indication, performs processing of a marked PDU and an unmarked PDU;
  • the unmarked PDU After receiving the marked PDU, the unmarked PDU is processed first;
  • a storage medium stores instructions, and when the instructions are executed on a communication device, the communication device executes the method described in the first aspect or the second aspect.
  • FIG1 is an architecture diagram of a communication system provided by an embodiment of the present disclosure.
  • FIG2 is a schematic diagram of a 5G networking architecture provided by an embodiment of the present disclosure.
  • FIG3 is a flow chart of a service processing method provided by an embodiment of the present disclosure.
  • FIG4A is a flow chart of another service processing method provided by an embodiment of the present disclosure.
  • FIG4B is a flow chart of another service processing method provided by an embodiment of the present disclosure.
  • FIG5A is a structural diagram of a communication device provided by an embodiment of the present disclosure.
  • FIG5B is a schematic diagram of the structure of a chip provided in an embodiment of the present disclosure.
  • 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 a marked PDU in a 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 processing of the unmarked PDU is completed, wherein the first access network device supports processing based on a PDU set, and the forwarded data packet includes a marked PDU.
  • an embodiment of the present disclosure proposes a service processing method, including: a first access network device sends 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 set; the first access network device receives a priority indication sent by the first network element; and according to the priority indication, performs processing of a marked PDU and an unmarked PDU;
  • the unmarked PDU After receiving the marked PDU, the unmarked PDU is processed first;
  • an embodiment of the present disclosure proposes a storage medium, wherein the storage medium stores instructions.
  • the instructions When the instructions are executed on a communication device, the communication device executes the method described in the optional implementation of the first aspect and the second aspect.
  • an embodiment of the present disclosure proposes a program product.
  • the communication device executes the method described in the optional implementation manner of the first aspect and the second 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 aspect, the second aspect, and the third aspect.
  • an embodiment of the present disclosure provides a chip or a chip system.
  • the chip or chip system includes a processing circuit configured to execute the method described in the optional implementation of the first aspect and the second aspect.
  • the embodiments of the present disclosure provide a service processing method and device.
  • the terms service processing method, information processing method, communication method, etc. can be interchangeable.
  • each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined.
  • 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.
  • 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 of the steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.
  • elements expressed in the singular form such as “a”, “an”, “the”, “above”, “said”, “aforementioned”, “this”, etc., may mean “one and only one", or “one or more”, “at least one”, etc.
  • the noun after the article may be understood as a singular expression or a plural expression.
  • plurality refers to two or more.
  • "at least one of A and B", “A and/or B", “A in one case, B in another case”, “in response to one case A, in response to another case B”, etc. may include the following technical solutions according to 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); in some embodiments, A and B (both A and B are executed). When there are more branches such as A, B, C, etc., the above is also similar.
  • the recording method of "A or B” may include the following technical solutions according to 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).
  • A A is executed independently of B
  • B B is executed independently of A
  • execution is selected from A and B (A and B are selectively executed).
  • 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 restrictions on the position, order, priority, quantity or content of the description objects.
  • the statement of the description object refers to the description in the context of the claims or embodiments, and should not constitute unnecessary restrictions due to the use of prefixes.
  • 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”
  • the "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”.
  • 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”.
  • the number of description objects is not limited by the ordinal number, and can be one or more.
  • the number of “devices” can be one or more.
  • the objects modified by different prefixes can be the same or different.
  • the object to be described is “device”
  • “the first device” and “the second device” can be the same device or different devices, and their types can be the same or different.
  • the object to be described is "information”
  • the "first information” and the “second information” may be the same information or different information, and the contents thereof may be the same or different.
  • “including A”, “comprising A”, “used to indicate A”, and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
  • time/frequency refers to the time domain and/or the frequency domain.
  • 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 lower 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”, “no more than”, “lower than”, “lower than or equal to”, “not higher than”, and “below” can be replaced with each other.
  • 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.
  • network may be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).
  • terminal 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 and the like can be used interchangeably.
  • the access network device, the core network device, or the network device can be replaced by a terminal.
  • the various embodiments of the present disclosure can also be applied to a structure in which the access network device, the core network device, or the network device and the communication between the terminals is replaced by the communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.).
  • D2D device-to-device
  • V2X vehicle-to-everything
  • it can also be set as a structure in which the terminal has all or part of the functions of the access network device.
  • terms such as "uplink” and "downlink” can also be replaced by terms corresponding to communication between terminals (for example, "side”).
  • uplink channels, downlink channels, etc. can be replaced by side channels
  • uplinks, downlinks, etc. can be replaced by side links.
  • the terminal may be replaced by an access network device, a core network device, or a network device.
  • the access network device, the core network device, or the network device may also be configured to have a structure that has all or part of the functions of the terminal.
  • acquisition of data, information, etc. may comply with the laws and regulations of the country where the data is obtained.
  • data, information, etc. may be obtained with the user's consent.
  • each element, each row, or each column in the table of the embodiments of the present disclosure may be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns may also be implemented as an independent embodiment.
  • FIG1 is an architecture diagram of a communication system provided by an embodiment of the present disclosure.
  • the communication system 100 includes a terminal 101 , an access network device 102 , and a core network device 103 .
  • 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 (Pad), 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 to these.
  • a mobile phone a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer (Pad), 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
  • 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.
  • 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 Node B (eNB), a next generation evolved Node B (ng-eNB), a next generation Node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (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.
  • eNB evolved Node B
  • ng-eNB next generation evolved Node B
  • gNB next generation Node B
  • the access network device 102 may also be a satellite.
  • the core network device 103 may be a device including a first network element, a second network element, a third network element and a plurality of network elements, or may be a plurality of devices or a group of devices, each including a plurality of network functions.
  • a network element may also be referred to as a network function, and a network function 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).
  • EPC evolved packet core
  • 5GCN 5G core network
  • NGC next generation core
  • the first network element is, for example, a session management function (SMF).
  • SMS session management function
  • the second network element is, for example, a user plane function (UPF).
  • UPF user plane function
  • the first network element is used for performing packet data unit (PDU) session management for the terminal, execution of control policy issued by PCF, selection of user plane function (UPF) network element, allocation of IP address of terminal device when the PDU type is IP type, etc.
  • PDU packet data unit
  • UPF user plane function
  • 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.
  • policy control functions such as session and service flow level billing, QoS bandwidth guarantee and mobility management, and user equipment policy decision making.
  • 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.
  • a person of ordinary skill in the art 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.
  • the following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or part of the subject, but are not limited thereto.
  • the subjects shown in FIG1 are examples, and the communication system may include all or part of the subjects in FIG1 , or may include other subjects other than FIG1 , and the number and form of the subjects are arbitrary, and the subjects may be physical or virtual, and the connection relationship between the subjects is an example, and the subjects may be connected or disconnected, and the connection may be in any manner, and may be a direct connection or an indirect connection, and may be a wired connection or a wireless connection.
  • LTE long term evolution
  • LTE-A LTE-Advanced
  • LTE-B LTE-Beyond
  • SUPER 3G IMT-Advanced
  • the fourth generation mobile communication system (4G) the fifth 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 (FRA), new-radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FRA), new-radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FRA), new-radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FRA), new radio access technology (FRA ...
  • the wireless communication system of the present invention includes the following: wireless communication system of the present invention, such as wireless communication system of the present invention and wireless communication system of the present invention: wireless communication system of the present invention; wireless communication system of the present invention includes the following: wireless communication system of the present invention, wireless communication system of the present invention and ...
  • FIG2 is a schematic diagram of a 5G networking architecture provided in an embodiment of the present disclosure.
  • Application function also known as application controller, it 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 IMS voice call service.
  • the application function entity of a third-party application interacts with the core network, it can be authorized through the network exposure function (NEF).
  • NEF network exposure function
  • 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 (policy control function).
  • PCF policy control function
  • UDM unified data management function
  • 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.
  • UDM Mainly used to implement data management functions such as management of contract information and user access authorization.
  • Access and mobility management function (AMF): mainly used to implement terminal mobility management, access authentication/authorization and other functions.
  • AMF is also responsible for transmitting user policies between the terminal and PCF.
  • Session management function Mainly used for packet data unit (PDU) session management of terminals, execution of control strategies issued by PCF, selection of user plane function (UPF), allocation of terminal IP address when the PDU type is IP type, etc.
  • PDU packet data unit
  • UPF user plane function
  • UPF Mainly used as the interface between the terminal and the data network to complete functions such as user plane data forwarding, session/flow-level billing statistics, and bandwidth limitation.
  • Unified data repository Mainly responsible for the storage and access of contract information, policy data, application data and other types of data. UDR can be interconnected with UDM, PCF, NEF, etc. to achieve access or call of corresponding network elements.
  • 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.
  • 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.
  • 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.
  • ]N3 interface It is the interface between (R)AN equipment and UPF network element, used to transmit terminal service data between RAN equipment and UPF network element.
  • 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 for the control plane terminal to complete the network access operation and other processes according to the contract information with the operator.
  • 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.
  • N7 interface It is the interface between PCF network element and SMF network element, used to send information such as PDU session granularity and service data flow granularity control strategy.
  • N8 interface It is the interface between the AMF network element and the UDM network element. It is used by the AMF network element to obtain the access and mobility management-related contract information and authentication data from the UDM network element, and the AMF network element to register the terminal's current mobility management-related information with the UDM network element.
  • 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 the session management-related contract information from the UDM network element, and the SMF network element to register the terminal's current session-related information with the UDM network element.
  • N11 interface It is the interface between SMF network element and AMF network element, used to transmit PDU session tunnel information between RAN equipment and UPF network element, control messages sent to terminals, radio resource control information sent to RAN equipment, etc.
  • XR services also involve multimodal data streams, which can be data input from the same device or different devices (including sensors) to describe the same service or application, and these data may be output to one or more destination device terminals.
  • the data streams in multimodal data are often related, such as the synchronization of audio and video streams, and the synchronization of touch and vision.
  • the data streams of such media services, the data streams between them, and the network transmission requirements of these service data streams all have some common characteristics. The effective identification and utilization of these characteristics will be more conducive to the transmission and control of networks and services, as well as to service assurance and user experience.
  • XRM (XR and media) services require the 5th generation system (5GS) to comprehensively consider the quality of service (QoS) characteristics of the relevant data flows of the service, such as whether the parameters such as guaranteed bitrate (GBR) data flow with severe delay, guaranteed flow bitrate (GFBR), packet delay budget (PDB), and maximum data burst volume (MDBV) can be met and coordinated at the same time. It involves multiple XRM data flows of a terminal and XRM data flows of multiple terminals, and the consistency of QoS authorization and execution between each other.
  • QoS quality of service
  • the AF is supported to enhance the function of processing XRM service data streams based on each PDU set (Per PDU set). This supports the AF to enhance the QoS perception and guarantee of XRM service data streams, as well as the user's QoE. Including, AF provides PDU Set-specific QoS features and protocol descriptions:
  • PSDB -PDU Set Delay Budget
  • PSIHI Integrated Processing Information
  • PDU Set information is used by NG-RAN for QoS processing based on PDU Set.
  • PDU Set information includes:
  • UPF will perform mapping of AF SDF service data flow to QoS flow based on PDR rules; and encapsulate the associated PDU into PDU set; and execute relevant Set-related QoS policies such as PDU Set Error Rate (PSER) and PDU Set Delay Budget (PSDB) on the PDU Set in the QoS flow.
  • PSER PDU Set Error Rate
  • PSDB PDU Set Delay Budget
  • the QoS processing supported by the 5GS system supports either PDU-based QoS rules and parameter policies or PDU-set-based QoS rules and parameter policies in the same QoS flow. That is, there is only one set of QoS parameters that are activated and processed simultaneously in a QoS flow, which is a PDU-based QoS mechanism or a PDU-set-based QoS mechanism.
  • NG-RANs Non-homogenous support
  • NG-RANs Non-homogenous support
  • NG-RANs Non-homogenous support
  • 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.
  • the 5GS system does not support the scenario where both unmarked PDUs and marked PDUs exist in the same QoS flow, and cannot guarantee the QoS of the corresponding QoS flow.
  • the embodiments of the present disclosure provide a service processing method and device 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.
  • the names of information, etc. are not limited to the names recorded in the embodiments, and terms such as “information”, “message”, “signal”, “signaling”, “report”, “configuration”, “indication”, “instruction”, “command”, “channel”, “parameter”, “domain”, “field”, “symbol”, “symbol”, “code element”, “codebook”, “codeword”, “codepoint”, “bit”, “data”, “program”, and “chip” can be used interchangeably.
  • terms such as “uplink”, “uplink”, “physical uplink” can be interchangeable, and terms such as “downlink”, “downlink”, “physical downlink” can be interchangeable, and terms such as “side”, “sidelink”, “side communication”, “sidelink communication”, “direct connection”, “direct link”, “direct communication”, “direct link communication” can be interchangeable.
  • DCI downlink control information
  • DL downlink
  • UL uplink
  • UL DCI uplink
  • the terms “physical downlink shared channel (PDSCH)”, “DL data” and the like can be interchangeable with each other, and the terms “physical uplink shared channel (PUSCH)”, “UL data” and the like can be interchangeable with each other.
  • radio wireless
  • RAN radio access network
  • AN access network
  • RAN-based and the like
  • terms such as “moment”, “time point”, “time”, and “time position” can be interchangeable, and terms such as “duration”, “period”, “time window”, “window”, and “time” can be interchangeable.
  • RB resource block
  • PRB physical resource block
  • SCG resource element group
  • REG resource element group
  • PRB pair RB pair
  • RE resource element
  • wireless access scheme and waveform may be used interchangeably.
  • frame radio frame
  • subframe slot
  • sub-slot sub-slot
  • mini-slot mini-slot
  • sub-slot sub-slot
  • mini-slot mini-slot
  • obtain can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from high levels, obtaining by self-processing, autonomous implementation, etc.
  • terms such as “certain”, “preset”, “preset”, “set”, “indicated”, “some”, “any”, and “first” can be interchangeable, and "specific A”, “preset A”, “preset A”, “set A”, “indicated A”, “some A”, “any A”, and “first A” can be interpreted as A pre-defined in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., and can also be interpreted as specific A, some A, any A, or first A, etc., but is not limited to this.
  • the determination or judgment can be performed by a value represented by 1 bit (0 or 1), 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 to this.
  • the QoS processing supported by the 5GS system supports either PDU-based QoS rules and parameter policies or PDU-set-based QoS rules and parameter policies in the same QoS flow. That is, there is only one set of QoS parameters that are activated and processed simultaneously in a QoS flow, which is a PDU-based QoS mechanism or a PDU-set-based QoS mechanism.
  • NG-RANs Non-homogenous support
  • NG-RANs Non-homogenous support
  • data forwarding needs to be performed on the downlink data.
  • 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.
  • the 5GS system does not support the scenario where both unmarked PDUs and marked PDUs exist in the same QoS flow, and cannot guarantee the QoS of the corresponding QoS flow.
  • NG-RAN does not support mixed processing of marked PDUs and unmarked PDUs in a QoS flow at the same time, and processes the marked PDU as an unmarked PDU.
  • the processing can be performed within a specific time, wherein the specific time can be set according to the configuration, or can be set and executed according to the received end data (End Marker) packet and/or the transition processing window, etc., and further information such as the transition processing window can be sent to the SMF.
  • End Marker End Marker
  • 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.
  • the first indication information is included in a path switch request message in an Xn switching process, or the first indication information is included in a switching request confirmation message of an N2 switching process.
  • the source NG-RAN supports PDU Set-based processing
  • the target NG-RAN does not support PDU Set-based processing.
  • a forwarded data packet is received, such as a data packet directly forwarded by the source NG-RAN,
  • the forwarded data packets may include marked PDUs.
  • the target NG-RAN can 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.
  • the source NG-RAN does not support PDU Set-based processing
  • the switched target NG-RAN supports PDU Set-based processing.
  • 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).
  • 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 parameters of the marked PDU, and uses the PDUQoS parameters, that is, ignores the protocol extension header used to identify the PDU Set information).
  • 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).
  • the source NG-RAN does not support PDU Set-based processing
  • the target NG-RAN for switching supports PDU Set-based processing.
  • 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
  • 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, and ignore the QoS parameters of the PDU Set. After the timer ends, 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.
  • the target NG-RAN starts the above timer after receiving the End Marker packet.
  • the duration of the timer is the duration of the switching window for continuing to process (the marked PDU in the switching process is processed as an unmarked PDU, which can be started before receiving the EndMarker packet, and the remaining time after receiving the EndMarker packet is easier to determine).
  • 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 switching window for continuing to process (the marked PDU in the switching process is processed as an unmarked PDU, which can be started before the QoS parameters of the PDU Set sent by the SMF are received).
  • the processing switching window duration can be greater than or equal to the time required for the unmarked PDU processing to be completed from the start of the timer set by the target NG-RAN (which can be based on local configuration or OA configuration or the received EndMark packet or the received PDUSet related QoS parameters).
  • the target NG-RAN may send a second indication message to the SMF, where the second indication message 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, and if it accepts the PDU Set QoS parameters, the NG-RAN PDU Set QoS processing function is activated.
  • 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.
  • 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 (related to the start time (or time window) of the QoS parameters of the PDU Set applied). This time may be determined based on the timer used in the target NG-RAN for processing marked PDUs.
  • the SMF configures the PSA UPF to activate/or 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.
  • PDU group identification and marking PDU group-related identification and extended protocol header marking of PDU data packets
  • the PSA UPF sends an End Marker packet to the target NG-RAN at the end of a complete PDU set.
  • the PSA UPF starts to perform PDUset identification and extended protocol header marking from the beginning of a complete PDU set (such as the first packet), and stops or ends performing PDUset identification and extended protocol header marking at the end of a complete PDU set (such as the last packet) (End Marker packets are sent just after the last packet of the PDU set).
  • the PSA UPF identifies and marks PDUs with PDU Set information (e.g., identifies PDUs with RTP or RTCP extended protocol headers, maps the protocol extension headers with PDUSet information into GTP-U protocol extension headers, and carries the PDUSet information to the NG-RAN in the GTP-U extended protocol header). It does this starting from a complete PDU set.
  • PDU Set information e.g., identifies PDUs with RTP or RTCP extended protocol headers, maps the protocol extension headers with PDUSet information into GTP-U protocol extension headers, and carries the PDUSet information to the NG-RAN in the GTP-U extended protocol header. 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 in the new channel), if the end marker packet is not sent at the end of a complete PDU set (e.g., sent in the middle of a PDUSet).
  • the PSA UPF identifies and marks PDUs with PDU Set information (e.g., identifying PDUs with RTP or RTCP extension headers). It maps the protocol extension header with PDUSet information into a GTP-U protocol extension header, and carries the PDUSet information to NG-RAN in the GTP-U extension protocol header). It sends the remaining packets of the PDU set sent through the source forwarding tunnel as individual packets. Then, it starts with a complete PDU set, identifies the packets and marks the PDUset information to the extension 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 PDUSet).
  • PDU Set information e.g., identifying PDUs with RTP or RTCP extension headers. It maps the protocol extension header with PDUSet information into a GTP-U protocol extension header, and carries the PDUSet information to NG-RAN in the GTP-U extension protocol header). It sends the remaining packet
  • 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 taken as an example.
  • 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.
  • N2 Session Management (SM) information Session Management (Secondary RAT usage data)
  • Handover Flag Source to Target Transparent Container
  • 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.
  • 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 to inform that the terminal has moved to the new target cell and provides 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.
  • the N2 Path Switch Request message shall include a list of accepted QoS Flows.
  • the N2 SM information shall include a reference to the satisfied alternative QoS profile.
  • 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.
  • the first indication information is included in a path switch request message in an Xn switching process, or the first indication information is included in a switching request confirmation message of an N2 switching process.
  • the source NG-RAN supports PDU Set-based processing
  • the switched target NG-RAN does not support PDU Set-based processing.
  • 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.
  • 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).
  • the source NG-RAN does not support PDU Set-based processing
  • the switched target NG-RAN supports PDU Set-based processing.
  • 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).
  • 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 parameters of the marked PDU, and uses the PDUQoS parameters, that is, ignores the protocol extension header used to identify the PDU Set information).
  • 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).
  • the source NG-RAN does not support PDU Set-based processing
  • the target NG-RAN for switching supports PDU Set-based processing.
  • 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
  • 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, and ignore the QoS parameters of the PDU Set. After the timer ends, 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.
  • the target NG-RAN starts the above timer after receiving the End Marker packet.
  • the duration of the timer is the duration of the switching window for continuing to process (the marked PDU in the switching process is processed as an unmarked PDU, which can be started before receiving the EndMarker packet, and the remaining time after receiving the EndMarker packet is easier to determine).
  • 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 switching window for continuing to process (the marked PDU in the switching process is processed as an unmarked PDU, which can be started before the QoS parameters of the PDU Set sent by the SMF are received).
  • the duration of the handover window can be greater than or equal to the target NG-RAN (based on local configuration or OA configuration or received).
  • the timer set by the EndMark packet or the received PDU Set-related QoS parameters is started to the time required for the unmarked PDU to be processed.
  • the target NG-RAN may send a second indication message to the SMF, where the second indication message 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, and if it accepts the PDU Set QoS parameters, the NG-RAN PDU Set QoS processing function is activated.
  • 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.
  • 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 (related to the start time (or time window) of the QoS parameters of the PDU Set applied). This time may be determined based on the timer used in the target NG-RAN for processing marked PDUs.
  • the SMF configures the PSA UPF to activate/or 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.
  • PDU group identification and marking PDU group-related identification and extended protocol header marking of PDU data packets
  • Nsmf_PDUSession_UpdateSMContext N2 SM information received in step 1b and N2 SM information from source NG-RAN (secondary RAT usage data), terminal location information, and presence of the terminal in the Local Area Data Network (LADN) service area).
  • the N2 SM information of the source NG-RAN here is the information buffered in step 1a if applicable.
  • 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 indication from step 1 that the target NG-RAN provides the SMF with information on whether PDU Set based processing is supported; 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).
  • the SMF shall initiate the PDU Session Modification procedure to remove the unaccepted QoS flows from the PDU Session.
  • SMF to UPF N4 session modification request (AN tunnel information).
  • 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 no longer provide further data notification messages.
  • the CN tunnel information used to connect to the target NG-RAN and the UPF of the source NG-RAN may be different.
  • the source NG-RAN and the target NG-RAN are located in different IP domains.
  • the SMF may request the UPF to allocate new CN tunnel information and provide the target network instance.
  • UPF to SMF N4 Session Modification Response (CN Tunnel Information).
  • N4 Session Modification Response For the switched PDU session, UPF returns the N4 Session Modification Response message to SMF after the requested PDU session is switched.
  • the tunnel identifier of the uplink traffic is only included in the response.
  • the UPF sends one or more "EndMarker" packets for each N3 tunnel on the old path immediately after switching the path.
  • the UPF starts sending downlink data packets to the target NG-RAN.
  • the PSA UPF sends an End Marker packet to the target NG-RAN at the end of a complete PDU set.
  • the PSA UPF starts to perform PDUset identification and extended protocol header marking from the beginning of a complete PDU set (such as the first packet), and stops or ends performing PDUset identification and extended protocol header marking at the end of a complete PDU set (such as the last packet) (End Marker packets are sent just after the last packet of the PDU set).
  • the PSA UPF identifies and marks PDUs with PDU Set information (e.g., identifies PDUs with RTP or RTCP extended protocol headers, maps the protocol extension headers with PDUSet information into GTP-U protocol extension headers, and carries the PDUSet information to the NG-RAN in the GTP-U extended protocol header). It does this starting from a complete PDU set.
  • PDU Set information e.g., identifies PDUs with RTP or RTCP extended protocol headers, maps the protocol extension headers with PDUSet information into GTP-U protocol extension headers, and carries the PDUSet information to the NG-RAN in the GTP-U extended protocol header. 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 in the new channel), if the end marker packet is not sent at the end of a complete PDU set (e.g., sent in the middle of a PDUSet).
  • the PSA UPF identifies and marks the PDU with PDU Set information (for example, it identifies the PDU with RTP or RTCP extension protocol header, maps the protocol extension header with PDU Set information into the GTP-U protocol extension header, and carries the PDU Set information to the NG-RAN in the GTP-U extension protocol header). It sends the remaining packets of the PDU set sent through the source forwarding tunnel as individual packets. Then, it starts with a complete PDU set and identifies and marks the packets with PDU Set information to the extension header. Protocol header, if the end marker packet is not sent at the end of a complete PDU set (for example, sent in the middle of a PDU set).
  • the SMF Based on the NG-RAN’s indication and/or activation time, the SMF configures the PSA UPF to activate/deactivate the PDU Set identification and markings.
  • the PSA UPF identifies and marks PDUs with PDU Set information in the GTP-U header, it shall do so starting with a complete PDU set.
  • the PDU following the End Marker packet is not the start of a complete PDU set if sent by the source NG-RAN, and a portion of the sent PDUs are overlapped to perform PDU Set encapsulation).
  • the PSA UPF identifies and marks PDUs with PDU Set information in the GTP-U header, starting with 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.
  • Nsmf_PDUSession_UpdateSMContext response N2 SM information
  • 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 PDU session that has been successfully handed over.
  • 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
  • the CN tunnel information of the UPF sent to the AMF is used to establish the N3 tunnel.
  • GLR guaranteed bit rate
  • 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 process based on local configuration.
  • SMF For XR service flows, SMF carries the corresponding PDU set QoS parameters and flow description information in the message to the target NG-RAN. Or SMF subsequently initiates a separate PDU session modification process, carrying the updated PDU set QoS parameters and flow description information.
  • the SMF sends the available alternative QoS profiles to the target NG-RAN on a per QoS flow basis.
  • Step 6 can occur at any time after the SMF receives the N4 Session Modification Response.
  • N2 path switching request confirmation (N2 SM information, unsuccessful PDU session, UE radio capability identification).
  • the target NG-RAN confirms the success of the handover 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.
  • the terminal may initiate the mobility registration update procedure.
  • the 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.
  • the source NG-RAN is S-NG-RAN
  • the source AMF is S-AMF
  • the source UPF is S-UPF
  • the target NG-RAN is T-NG-RAN
  • the target AMF is T-AMF
  • the target UPF is T-UPF.
  • the source NG-RAN 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 switched, the identity of the target NG-RAN and other relevant information.
  • the AMF After receiving the N2 path switching request, the AMF starts preparing for non-Xn switching.
  • the AMF may need to perform some preparation work, such as updating relevant context information and obtaining the status of the target NG-RAN.
  • 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.
  • the source NG-RAN starts preparing for the handover of the terminal based on the confirmation of the AMF.
  • the source NG-RAN can transfer the PDU session information, user data and related context to the target NG-RAN.
  • the target NG-RAN After receiving the handover-related information, the target NG-RAN is ready to accept the terminal.
  • the target NG-RAN can allocate resources, update context information, etc.
  • the source NG-RAN triggers the handover of the terminal.
  • the source NG-RAN can send an instruction to the terminal and send a signal to the terminal to instruct the handover to the target NG-RAN.
  • the terminal starts communicating on the target NG-RAN.
  • the target NG-RAN is responsible for the connection and services of the terminal.
  • S-NG-RAN to S-AMF Handover request (target identifier, source-to-target transparent container, SMN2 information list, PDU session identifier, intra-system handover indication).
  • the source-to-destination transparent container includes the 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.
  • Nsmf_PDUSession_UpdateSMContext response PDU session identifier, N2 SM information, Reason for non-acceptance.
  • the SMF includes the N2 SM information in the Nsmf_PDUSession_UpdateSMContext response, which contains the N3 UP address of the UPF and the UL CN tunnel ID, QoS parameters, TSCAI and user plane security enforcement information of the target NG-RAN.
  • T-AMF supervises the Nsmf_PDUSession_UpdateSMContext response message from the SMF involved.
  • 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).
  • T-AMF determines T-NG-RAN based on the target identifier.
  • T-AMF may allocate a valid 5G-globally unique temporary identity (GUTI) for the terminal in T-AMF and the target Tracking Area Identity (TAI).
  • GUI 5G-globally unique temporary identity
  • the source to target transparent container is forwarded as received from S-NG-RAN.
  • the N2MM information includes security information and mobility restriction list (if available in T-AMF).
  • the N2 SM information list includes the N2 SM information received from the SMF in the Nsmf_PDUSession_UpdateSMContext response message supervised by T-AMF in step 8 within the maximum allowed delay, which are prepared for T-NG-RAN.
  • T-NG-RAN to T-AMF Handover request confirmation (target to source transparent container, list of PDU sessions to be switched with N2 SM information, list of PDU sessions that could not be established, including the reason for failure given in the N2 SM information element).
  • the target NG-RAN provides an indication to the SMF whether the target NG-RAN node supports PDU set based processing; a "PDU set support" indication from the target NG-RAN is provided in the Handover Request Confirmation message (NG Handover).
  • the source NG-RAN supports PDU Set-based processing
  • the switched target NG-RAN does not support PDU Set-based processing.
  • 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.
  • 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.
  • the source NG-RAN does not support PDU Set-based processing
  • the switched target NG-RAN supports PDU Set-based processing.
  • 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).
  • 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 parameters of the marked PDU, and uses the PDUQoS parameters, that is, ignores the protocol extension header used to identify the PDU Set information).
  • 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).
  • the source NG-RAN does not support PDU Set-based processing
  • the target NG-RAN for switching supports PDU Set-based processing.
  • 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
  • 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, and ignore the QoS parameters of the PDU Set. After the timer ends, 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.
  • the target NG-RAN starts the above timer after receiving the End Marker packet.
  • the duration of the timer is the duration of the switching window for continuing to process (the marked PDU in the switching process is processed as an unmarked PDU, which can be started before receiving the EndMarker packet, and the remaining time after receiving the EndMarker packet is easier to determine).
  • 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 switching window for continuing to process (the marked PDU in the switching process is processed as an unmarked PDU, which can be started before the QoS parameters of the PDU Set sent by the SMF are received).
  • the processing switching window duration can be greater than or equal to the time required for the unmarked PDU processing to be completed from the start of the timer set by the target NG-RAN (which can be based on local configuration or OA configuration or the received EndMark packet or the received PDUSet related QoS parameters).
  • 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, and if it is accepted, the NG-RAN PDU Set QoS processing function is activated.
  • 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.
  • 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 (related to the start time (or time window) of the QoS parameters of the PDU Set applied). This time may be determined based on the timer used in the target NG-RAN for processing marked PDUs.
  • the SMF configures the PSA UPF to activate/or 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.
  • PDU group identification and marking PDU group-related identification and extended protocol header marking of PDU data packets
  • 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.
  • N2 SM information may also include:
  • the N3 UP address of the T-NG-RAN and the Tunnel ID of the T-NG-RAN that will receive the forwarded data The T-NG-RAN provides the data forwarding address for each data forwarding tunnel it decides to set up.
  • the target NG-RAN shall include a reference to the satisfied alternative QoS profile.
  • T-AMF exchanges tunnel information with T-NG-RAN, S-UPF, and T-UPF through SMF.
  • 11a and 11f are executed in direct forwarding, and in indirect forwarding, the intermediate process is executed to exchange channel information.
  • T-AMF to SMF Nsmf_PDUSession_UpdateSMContext request (PDU session identifier, N2 SM response received from T-NG-RAN in step 10).
  • T-AMF For each N2 SM response received from T-NG-RAN (N2 SM information contained in the Handover Request Acknowledgement), T-AMF sends the received N2 SM response to the SMF indicated by the corresponding PDU Session ID.
  • the SMF stores the N3 tunnel information of T-NG-RAN in the N2 SM response if T-NG-RAN accepts the N2 handover.
  • 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.
  • Nsmf_PDUSession_UpdateSMContext response N2 SM information
  • SMF sends a Nsmf_PDUSession_UpdateSMContext response message for each PDU session to T-AMF.
  • the SMF 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 markings.
  • 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.
  • the PDU following the End Marker packet is not the start of a complete PDU set if the source NG-RAN sends it, and overlaps a portion of the sent PDUs 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.
  • SMF creates N2 SM information containing DL forwarding tunnel information to be sent by AMF to S-NG-RAN.
  • SMF includes this information in Nsmf_PDUSession_UpdateSMContext response.
  • DL forwarding tunnel information can be one of the following: (SMF sends down session update response message, carried by downlink forwarding information, including direct and indirect.)
  • the SMF includes the T-NG-RAN N3 forwarding information received in step 11a.
  • the SMF includes DL forwarding information from the T-UPF or S-UPF, including the N3 UP address and DL tunnel ID of the UPF.
  • T-AMF to S-AMF Namf_Communication_CreateUEContext response (including the N2 information required for S-AMF to send a switching command to S-NG-RAN, including the target to source transparent container, the list of PDU sessions that could not be established, N2 SM information (N3 downlink forwarding information, PCF ID), [target AMF ID]).
  • the target to source transport container is received by T-NG-RAN.
  • the N2 SM information is received by SMF in step 11f.
  • S-AMF initiates a handover command to S-NG-RAN, notifying that handover preparation is complete and executing handover. It carries all handover session information obtained from S-NG-RAN and N2 SM information of each session, as well as T-NG-RAN N3 forwarding tunnel information in direct forwarding or S-UPF N3 forwarding tunnel information in indirect forwarding.
  • the PSA UPF sends the end data packet (End Marker packets) to the S-NG-RAN after the switching path is completed, and forwards it to the T-NG-RAN. Or the End Marker packets are forwarded to the T-NG-RAN through the indirect forwarding T-UPF.
  • End Marker packets End Marker packets
  • the PSA UPF sends an End Marker packet to the target NG-RAN at the end of a complete PDU set.
  • the PSA UPF starts to perform PDUset identification and extended protocol header marking from the beginning of a complete PDU set (such as the first packet), and stops or ends performing PDUset identification and extended protocol header marking at the end of a complete PDU set (such as the last packet) (End Marker packets are sent just after the last packet of the PDU set).
  • the PSA UPF identifies and marks PDUs with PDU Set information (e.g., identifies PDUs with RTP or RTCP extended protocol headers, maps the protocol extension headers with PDUSet information into GTP-U protocol extension headers, and carries the PDUSet information to the NG-RAN in the GTP-U extended protocol header). It does this starting from a complete PDU set.
  • PDU Set information e.g., identifies PDUs with RTP or RTCP extended protocol headers, maps the protocol extension headers with PDUSet information into GTP-U protocol extension headers, and carries the PDUSet information to the NG-RAN in the GTP-U extended protocol header. 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 in the new channel), if the end marker packet is not sent at the end of a complete PDU set (e.g., sent in the middle of a PDUSet).
  • the PSA UPF identifies and marks the PDU with PDU Set information (for example, identifies the PDU with RTP or RTCP extended protocol header, maps the protocol extension header with 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 packets of the PDU set sent through the source forwarding tunnel as individual packets. Then, it starts from a complete PDU set, identifies the 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 PDUSet).
  • PDU Set information for example, identifies the PDU with RTP or RTCP extended protocol header, maps the protocol extension header with 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.
  • the source NG-RAN node receives one or more GTP-U end marker packets for each PDU session from the UPF and copies the end marker packets to each data forwarding tunnel when user data packets are no longer required to be forwarded on that tunnel.
  • An end marker packet sent over a data forwarding tunnel applies to all QoS flows forwarded over that tunnel.
  • the target NG-RAN node can start considering packets received from NG-U PDU session tunnels for QoS flows associated with that forwarding tunnel.
  • the QoS processing supported by the 5GS system supports either PDU-based QoS rules and parameter policies or PDU-set-based QoS rules and parameter policies in the same QoS flow. That is, there is only one set of QoS parameters that are activated and processed simultaneously in a QoS flow, which is a PDU-based QoS mechanism or a PDU-set-based QoS mechanism.
  • NG-RANs Non-homogenous support
  • NG-RANs Non-homogenous support
  • data forwarding needs to be performed on the downlink data.
  • 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.
  • the 5GS system does not support the scenario where both unmarked PDUs and marked PDUs exist in the same QoS flow, and cannot guarantee the QoS of the corresponding QoS flow.
  • NG-RAN does not support mixed processing of marked PDUs and unmarked PDUs in the same QoS flow at the same time (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.
  • the PDU Set QoS processing function is delayed by SMF to activate, or the PDU Set QoS processing function is activated but delayed to apply, so that the two PDUs are processed at different times.
  • NG-RAN performs corresponding processing according to the notification instructions of SMF to solve the above problems.
  • the SMF notifies the T-NG-RAN of the indication processing, including one or more of the following methods:
  • SMF carries the PDU set activation timer to T-NG-RAN;
  • T-NG-RAN receives the received
  • the marked PDU is processed as an unmarked PDU, and the enhanced header information carrying the PDU set information is ignored;
  • SMF carries the priority indication to T-NG-RAN
  • the unmarked PDU is processed first (ignoring the PDU set information carried by the header enhancement);
  • T-NG-RAN executes a corresponding processing method based on the received priority indication.
  • 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).
  • the SMF 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 delay according to the indicated time or time window);
  • the SMF can carry PDU set QoS parameters to UPF and NG-RAN to activate PDU set based QoS processing.
  • the SMF notifies the UPF to perform delayed PDU Set identification and marking; wherein the SMF may determine the delay time according to local configuration or OAM configuration or NG-RAN notification information; the SMF may set a PDU set activation timer (timer), initiate PDU session modification after the timer times out, and activate QoS processing of 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 packet (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.
  • the time when the two PDUs (marked and unmarked PDUs) arrive at NG-RAN is staggered, so that NG-RAN will only receive the same PDU at the same time, and there will be no mixed state of marked and unmarked PDUs, and NG-RAN does not need to do special processing, or the time when the two PDUs (marked and unmarked PDUs) arrive at NG-RAN is staggered as much as possible.
  • a small amount of mixed PDUs can discard unmatched PDUs according to QoS parameters, or ignore the protocol enhancement header processing according to function.
  • the PSA UPF sends an End Marker packet to the target NG-RAN at the end of a complete PDU set.
  • the PSA UPF starts to perform PDUset identification and extended protocol header marking from the beginning of a complete PDU set (such as the first packet), and stops or ends performing PDUset identification and extended protocol header marking at the end of a complete PDU set (such as the last packet) (End Marker packets are sent just after the last packet of the PDU set).
  • the PSA UPF identifies and marks PDUs with PDU Set information (e.g., identifies PDUs with RTP or RTCP extended protocol headers, maps the protocol extension headers with PDUSet information into GTP-U protocol extension headers, and carries the PDUSet information to the NG-RAN in the GTP-U extended protocol header). It does this starting from a complete PDU set.
  • PDU Set information e.g., identifies PDUs with RTP or RTCP extended protocol headers, maps the protocol extension headers with PDUSet information into GTP-U protocol extension headers, and carries the PDUSet information to the NG-RAN in the GTP-U extended protocol header. 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 in the new channel), if the end marker packet is not sent at the end of a complete PDU set (e.g., sent in the middle of a PDUSet).
  • the PSA UPF identifies and marks the PDU with PDU Set information (for example, identifies the PDU with RTP or RTCP extended protocol header, maps the protocol extension header with 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 packets of the PDU set sent through the source forwarding tunnel as individual packets. Then, it starts from a complete PDU set, identifies the 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 PDUSet).
  • PDU Set information for example, identifies the PDU with RTP or RTCP extended protocol header, maps the protocol extension header with 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.
  • 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 taken as an example.
  • the source NG-RAN node may provide a RAN Usage Data Report (N2 SM Message (Secondary RAT Usage Data), Handover Flag, Source to Target Transparent Container) to the AMF during the Handover Execution Phase.
  • N2 SM Message Secondary RAT Usage Data
  • Handover Flag Source to Target Transparent Container
  • the Handover Flag indicates to the AMF that it should buffer the N2 SM message containing the Usage Data Report before forwarding it.
  • Target NG-RAN to AMF N2 path switching 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).
  • the target NG-RAN sends an N2 Path Switch Request message to the AMF to notify that the UE has moved to a new target cell and provides 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.
  • the N2 Path Switch Request message shall include a list of accepted QoS Flows for the PDU Session to be switched to the target NG-RAN. For each QoS Flow for which an alternative QoS profile was accepted, the N2 SM information shall contain a reference to the satisfied alternative QoS profile.
  • the target NG-RAN in an Xn handover of an NG-RAN, provides an indication to the SMF whether the target NG-RAN node supports PDU Set based processing; the "PDU Set supported" indication from the target NG-RAN will be included in the Path Switch Request message (Xn Handover).
  • AMF sends Nsmf_PDUSession_UpdateSMContext request to SMF (N2 SM information from T-NG-RAN received in step 1b and N2 SM information from source NG-RAN (auxiliary RAT usage data), UE location information, UE presence in LADN service area).
  • N2 SM information from source NG-RAN is buffered in step 1a if applicable.
  • 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.
  • the target NG-RAN Including in 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 Switch).
  • 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 QoS flows that have been transported), or an indication that the PDU Session is to be rejected (along with the rejection reason).
  • 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.
  • the SMF 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.
  • 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.
  • the SMF can ask the UPF to allocate new CN tunnel information and provide the target network instance.
  • UPF For the switched PDU session, UPF returns an N4 session modification response message to 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 the user plane resources and is requested by SMF.
  • the UPF sends one or more “end marker” packets for each N3 tunnel on the old path immediately after switching the path.
  • the UPF starts sending downlink packets to the target NG-RAN.
  • the PSA UPF sends an End Marker packet to the target NG-RAN at the end of a complete PDU set.
  • the PSA UPF starts to perform PDUset identification and extended protocol header marking from the beginning of a complete PDU set (such as the first packet), and stops or ends performing PDUset identification and extended protocol header marking at the end of a complete PDU set (such as the last packet) (End Marker packets are sent just after the last packet of the PDU set).
  • the PSA UPF identifies and marks PDUs with PDU Set information (e.g., identifies PDUs with RTP or RTCP extended protocol headers, maps the protocol extension headers with PDUSet information into GTP-U protocol extension headers, and carries the PDUSet information to the NG-RAN in the GTP-U extended protocol header). It does this starting from a complete PDU set.
  • PDU Set information e.g., identifies PDUs with RTP or RTCP extended protocol headers, maps the protocol extension headers with PDUSet information into GTP-U protocol extension headers, and carries the PDUSet information to the NG-RAN in the GTP-U extended protocol header. 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 in the new channel), if the end marker packet is not sent at the end of a complete PDU set (e.g., sent in the middle of a PDUSet).
  • the PSA UPF identifies and marks the PDU with PDU Set information (for example, identifies the PDU with RTP or RTCP extended protocol header, maps the protocol extension header with 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 packets of the PDU set sent through the source forwarding tunnel as individual packets. Then, it starts from a complete PDU set, identifies the 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 PDUSet).
  • PDU Set information for example, identifies the PDU with RTP or RTCP extended protocol header, maps the protocol extension header with 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.
  • the SMF Based on the NG-RAN’s indication and/or activation time, the SMF configures the PSA UPF to activate/deactivate the PDU Set identification and markings.
  • the PSA UPF identifies and marks PDUs with PDU Set information in the GTP-U header, it shall do so starting with a complete PDU set.
  • the PDU following the End Marker packet is not the start of a complete PDU set if sent by the source NG-RAN, and a portion of the sent PDUs are overlapped to perform PDU Set encapsulation).
  • the PSA UPF identifies and marks PDUs with PDU Set information in the GTP-U header, starting with 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.
  • SMF sends Nsmf_PDUSession_UpdateSMContext response to AMF (N2 SM information)
  • the SMF sends a 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 switched PDU Session.
  • N2 SM Information CN Tunnel Information (CN Tunnel Information, Updated CN PDB for accepted QoS flows, Updated TSCAI for accepted QoS flows)
  • the CN Tunnel Information sent by the UPF to the AMF is used to set up the N3 tunnel.
  • 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 based on local configuration or using a separate PDU Session Modification procedure.
  • Step 6 can occur at any time after the SMF receives the N4 Session Modification Response.
  • NG-RAN does not support mixed processing of marked PDUs and unmarked PDUs in the same QoS flow at the same time (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.
  • the PDU Set QoS processing function is delayed by SMF to activate, or the PDU Set QoS processing function is activated but delayed to apply, so that the two PDUs are processed at different times.
  • NG-RAN performs corresponding processing according to the notification instructions of SMF to solve the above problems.
  • the SMF notifies the T-NG-RAN of the indication processing, including one or more of the following methods:
  • SMF carries the PDU set activation timer to T-NG-RAN; before the timer times out, T-NG-RAN processes the received marked PDU as an unmarked PDU and ignores the enhanced header information carrying the PDU set information;
  • SMF carries the priority indication to T-NG-RAN
  • the unmarked PDU is processed first (ignoring the PDU set information carried by the header enhancement);
  • T-NG-RAN executes a corresponding processing method based on the received priority indication.
  • 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).
  • the SMF 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 delay according to the indicated time or time window);
  • the SMF can carry PDU set QoS parameters to UPF and NG-RAN to activate PDU set based QoS processing.
  • the SMF notifies the UPF to perform delayed PDU Set identification and marking; wherein the SMF may determine the delay time according to local configuration or OAM configuration or NG-RAN notification information; the SMF may set a PDU set activation timer (timer), initiate PDU session modification after the timer times out, and activate QoS processing of 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 packet (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.
  • the time when the two PDUs (marked and unmarked PDUs) arrive at NG-RAN is staggered, so that NG-RAN will only receive the same PDU at the same time, and there will be no mixed state of marked and unmarked PDUs, and NG-RAN does not need to do special processing, or the time when the two PDUs (marked and unmarked PDUs) arrive at NG-RAN is staggered as much as possible.
  • a small amount of mixed PDUs can discard unmatched PDUs according to QoS parameters, or ignore the protocol enhancement header processing according to function.
  • SMF For XR service flows, SMF carries the corresponding PDU set QoS parameters and flow description information in the message to the target NG-RAN. Or SMF subsequently initiates a separate PDU session modification process, carrying the updated PDU set QoS parameters and flow description information.
  • the SMF sends the available alternative QoS profiles to the target NG-RAN on a per QoS flow basis.
  • N2 path switching request confirmation (N2 SM information, unsuccessful PDU session, UE radio capability identification).
  • the target NG-RAN confirms the success of the handover 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.
  • the terminal may initiate the mobility registration update procedure.
  • the 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.
  • the source NG-RAN is S-NG-RAN
  • the source AMF is S-AMF
  • the source UPF is S-UPF
  • the target NG-RAN is T-NG-RAN
  • the target AMF is T-AMF
  • the target UPF is T-UPF.
  • step 10 carries an indication of T-NG-RAN’s PUD set support to the SMF.
  • S-NG-RAN sends a handover request to S-AMF (target ID, source-to-target transparent container, SMN2 information list, PDU session ID, intra-system handover indication).
  • S-AMF target ID, source-to-target transparent container, SMN2 information list, PDU session ID, intra-system handover indication.
  • 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 the data forwarding.
  • Nsmf_PDUSession_UpdateSMContext response PDU session identifier, N2 SM information, reason for non-acceptance.
  • the SMF includes the N2 SM information in the Nsmf_PDUSession_UpdateSMContext response, which contains the N3 UP address of the UPF and the UL CN tunnel ID, QoS parameters, TSCAI and user plane security enforcement information of the target NG-RAN.
  • T-AMF supervises the Nsmf_PDUSession_UpdateSMContext response message from the SMF involved.
  • 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).
  • T-AMF determines T-NG-RAN based on the target identifier.
  • T-AMF may allocate a valid 5G-GUTI for the terminal in T-AMF and target TAI.
  • the source to target transparent container is forwarded as received from S-NG-RAN.
  • the N2MM information includes security information and mobility restriction list (if available in T-AMF).
  • the N2 SM information list includes the N2 SM information received from the SMF in the Nsmf_PDUSession_UpdateSMContext response message supervised by T-AMF in step 8 within the maximum allowed delay, which are prepared for T-NG-RAN.
  • T-NG-RAN to T-AMF Handover request confirmation (target to source transparent container, list of PDU sessions to be switched with N2 SM information, list of PDU sessions that could not be established, including the reason for failure given in the N2 SM information element).
  • T-NG-RAN provides an indication to the SMF whether the T-NG-RAN node supports PDU set based processing; the "PDU set support" indication from T-NG-RAN is provided in the Handover Request Confirm message (NG Handover) (Step 10 message).
  • 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 T-NG-RAN.
  • N2 SM information may also include:
  • the N3 UP address and tunnel ID of the T-NG-RAN to receive the forwarded data.
  • the T-NG-RAN provides the data forwarding address for each data forwarding tunnel it decides to set up.
  • T-NG-RAN shall include a reference to the satisfied alternative QoS configuration.
  • T-AMF exchanges tunnel information with T-NG-RAN, S-UPF, and T-UPF through SMF.
  • 11a and 11f are executed in direct forwarding, and in indirect forwarding, the intermediate process is executed to exchange channel information.
  • T-AMF to SMF Nsmf_PDUSession_UpdateSMContext request (PDU session identifier, N2 SM response received from T-NG-RAN in step 10).
  • T-AMF For each N2 SM response received from T-NG-RAN (N2 SM information contained in the Handover Request Acknowledgement), T-AMF sends the received N2 SM response to the SMF indicated by the corresponding PDU Session ID.
  • the SMF stores the N3 tunnel information of T-NG-RAN in the N2 SM response if T-NG-RAN accepts the N2 handover.
  • the SMF/UPF allocates the N3 UP address and tunnel ID for indirect data forwarding to correspond to the data forwarding tunnel endpoint established by T-NG-RAN.
  • Nsmf_PDUSession_UpdateSMContext response N2 SM information
  • the SMF sends a Nsmf_PDUSession_UpdateSMContext response message to the T-AMF, one for each PDU session.
  • 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 in the form of One of the following: (SMF sends a session update response message, which is carried in the downstream forwarding information, including direct and indirect.)
  • the SMF shall include the T-RNG-AN N3 forwarding information received in step 11a.
  • the SMF shall include the DL forwarding information of the T-UPF or S-UPF containing the N3 UP address and the DL tunnel ID of the UPF.
  • 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 the target to source transparent container, PDU session setup failure list, N2 SM information (N3DL forwarding information, PCF ID), [T-AMF ID]).
  • target to source transparent container This container is received from T-NG-RAN to support the operation of sending Handover Command to S-NG-RAN. It contains NG-RAN information, created by S-NG-RAN for T-NG-RAN, and is transparent to 5GC. It also includes the corresponding QoS flow/DRB information for each PDU session to support data forwarding.
  • PDU session setup failure list lists the PDU sessions that could not be established during the switching process, and the reasons for the failure are given.
  • N3 downlink forwarding information refers to the downlink forwarding tunnel information of the target T-NG-RAN contained in the N2 SM information, including the N3 UP address and downlink tunnel ID.
  • PCF ID is the identifier of the policy control function, indicating the ID of the policy control function.
  • Target AMF ID May contain the identification of the target AMF if required.
  • Namf_Communication_CreateUEContext response provides various information required to send a handover command to support the handover process from S-AMF to S-NG-RAN.
  • step 11f receive N2 SM information from SMF.
  • S-AMF initiates a handover command to S-NG-RAN, notifying that handover preparation is complete and executing handover. It carries all handover session information obtained from S-NG-RAN and N2 SM information of each session, as well as T-NG-RAN N3 forwarding tunnel information in direct forwarding or S-UPF N3 forwarding tunnel information in indirect forwarding.
  • S-NG-RAN S-NG-RAN
  • T-NG-RAN SMF and PSA UPF enhanced processing
  • UPF end data End Marker
  • the enhancement of the main SMF notification indication can be performed in steps 10, 11, and 15, or a separate session modification process can be initiated.
  • the PSA UPF sends the end data packet (End Marker packets) to the S-NG-RAN after the switching path is completed, and forwards it to the T-NG-RAN. Or the End Marker packets are forwarded to the T-NG-RAN through the indirect forwarding T-UPF.
  • End Marker packets End Marker packets
  • the PSA UPF sends an End Marker packet to the target NG-RAN at the end of a complete PDU set.
  • the PSA UPF starts to perform PDUset identification and extended protocol header marking from the beginning of a complete PDU set (such as the first packet), and stops or ends performing PDUset identification and extended protocol header marking at the end of a complete PDU set (such as the last packet) (End Marker packets are sent just after the last packet of the PDU set).
  • the PSA UPF identifies and marks PDUs with PDU Set information (e.g., identifies PDUs with RTP or RTCP extended protocol headers, maps the protocol extension headers with PDUSet information into GTP-U protocol extension headers, and carries the PDUSet information to the NG-RAN in the GTP-U extended protocol header). It does this starting from a complete PDU set.
  • PDU Set information e.g., identifies PDUs with RTP or RTCP extended protocol headers, maps the protocol extension headers with PDUSet information into GTP-U protocol extension headers, and carries the PDUSet information to the NG-RAN in the GTP-U extended protocol header. 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 in the new channel), if the end marker packet is not sent at the end of a complete PDU set (e.g., sent in the middle of a PDUSet).
  • the PSA UPF identifies and marks the PDU with PDU Set information (for example, identifies the PDU with RTP or RTCP extended protocol header, maps the protocol extension header with 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 packets of the PDU set sent through the source forwarding tunnel as individual packets. Then, it starts from a complete PDU set, identifies the 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 PDUSet).
  • PDU Set information for example, identifies the PDU with RTP or RTCP extended protocol header, maps the protocol extension header with 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.
  • the embodiments of the present disclosure also propose a device for implementing any of the above methods, for example, a device is proposed, the above device includes a unit or module for implementing each step performed by the terminal in any of the above methods.
  • a device is also proposed, including a unit or module for implementing each step performed by a network device (such as an access network device, a core network function node, a core network device, etc.) in any of the above methods.
  • a network device such as an access network device, a core network function node, a core network device, etc.
  • the division of the units or modules in the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated.
  • the units or modules in the device can be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, the memory stores instructions, and the processor calls the memory.
  • the instructions stored in the device are used to implement any of the above methods or to implement the functions of each unit or module 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 in the device or a memory outside the device.
  • a general-purpose processor such as a central processing unit (CPU) or a microprocessor
  • the memory is a memory in the device or a memory outside the device.
  • the unit or module in the device can be implemented in the form of a hardware circuit, and the functions of some or all of the units or modules can be implemented by designing the hardware circuit.
  • the above hardware circuit can be understood as one or more processors; for example, in one implementation, the above hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above units or modules are implemented by designing the logical relationship of the components in the circuit; for another example, in another implementation, the above hardware circuit can be implemented by a programmable logic device (PLD), taking a field programmable gate array (FPGA) as an example, which can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured through a configuration file, so as to implement the functions of some or all of the above units or modules. All units or modules of the above devices may be implemented entirely in the form of a processor calling software, or entirely in the form of a hardware circuit, or partially in the form of a processor calling software and the rest in the form of a hardware circuit.
  • the processor is a circuit with signal processing capability.
  • the processor may be a circuit with instruction reading and running capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which may be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor may implement certain functions through the logical relationship of a hardware circuit, and the logical relationship of the above hardware circuit may be fixed or reconfigurable, such as a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the process of the processor loading a configuration document to implement the hardware circuit configuration may be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules.
  • it can also be a hardware circuit designed for artificial intelligence, which can be understood as ASIC, such as Neural Network Processing Unit (NPU), Tensor Processing Unit (TPU), Deep Learning Processing Unit (DPU), etc.
  • ASIC Neural Network Processing Unit
  • NPU Neural Network Processing Unit
  • TPU Tensor Processing Unit
  • DPU Deep Learning Processing Unit
  • FIG5A is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure.
  • the communication device 8100 may be a network device (e.g., an access network device, a core network device, etc.), or a terminal (e.g., a user device, etc.), or 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.
  • the communication device 8100 may be used to implement the method described in the above method embodiment, and the details may refer to the description in the above method embodiment.
  • the communication device 8100 includes one or more processors 8101.
  • the processor 8101 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit.
  • the baseband processor may be used to process the communication protocol and the communication data
  • the central processing unit may 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 the program, and process the data of the program.
  • the communication device 8100 is used to execute any of the above methods.
  • one or more processors 8101 are used to call instructions so that the communication device 8100 executes any of the above methods.
  • the communication device 8100 further 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 method, and the processor 8101 performs at least one of the other steps.
  • the transceiver may include a receiver and/or a transmitter, and the receiver and the transmitter may be separated or integrated.
  • the terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc. may be replaced with each other, the terms such as transmitter, transmission unit, transmitter, transmission circuit, etc. may be replaced with each other, and the terms such as receiver, receiving unit, receiver, receiving circuit, etc. may be replaced with each other.
  • the communication device 8100 further includes one or more memories 8103 for storing data.
  • the memories 8103 may also be outside the communication device 8100.
  • the communication device 8100 may include one or more interface circuits 8104.
  • the interface circuit 8104 is connected to the memory 8102, and the interface circuit 8104 may be used to receive data from the memory 8102 or other devices, and may be used to send data to the memory 8102 or other devices.
  • the interface circuit 8104 may read the data stored in the memory 8102 and send the data to the processor 8101.
  • the communication device 8100 described in the above embodiments 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.
  • 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 and 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, a vehicle-mounted device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.
  • 5B is a schematic diagram of the structure of the chip 8200 proposed in the embodiment of the present disclosure.
  • the communication device 8100 may be a chip or a chip system
  • the chip 8200 includes one or more processors 8201.
  • the chip 8200 is configured to execute any of the above methods.
  • the chip 8200 further includes one or more interface circuits 8202.
  • the terms interface circuit, interface, transceiver pin, etc. can be interchangeable.
  • the chip 8200 further includes one or more memories 8203 for storing data.
  • all or part of the memory 8203 can be outside the chip 8200.
  • the interface circuit 8202 is connected to the memory 8203, and the interface circuit 8202 can be used to receive data from the memory 8203 or other devices, and the interface circuit 8202 can be used to send data to the memory 8203 or other devices.
  • the interface circuit 8202 can read the data stored in the memory 8203 and send the data to the processor 8201.
  • the interface circuit 8202 performs at least one of the communication steps such as sending and/or receiving in the above method.
  • the interface circuit 8202 performs the communication steps such as sending and/or receiving in the above method, for example, means that the interface circuit 8202 performs data interaction between the processor 8201, the chip 8200, the memory 8203 or the transceiver device.
  • the processor 8201 performs at least one of the other steps.
  • modules and/or devices described in the embodiments such as virtual devices, physical devices, chips, etc. can be combined or separated as needed.
  • some or all steps can also be performed by multiple modules and/or devices in collaboration, which is not limited here.
  • the present disclosure also proposes a storage medium, on which instructions are stored, and when the instructions are executed on the communication device 8100, the communication device 8100 executes any of the above methods.
  • the storage medium is an electronic storage medium.
  • the storage medium is a computer-readable storage medium, but is not limited to this, and it can also be a storage medium readable by other devices.
  • the storage medium can be a non-transitory storage medium, but is not limited to this, and it can also be a temporary storage medium.
  • the present disclosure also proposes a program product, which, when executed by the communication device 8100, enables the communication device 8100 to execute any of the above methods.
  • the program product is a computer program product.
  • the present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to execute any one of the above methods.

Landscapes

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

Abstract

本公开涉及一种业务处理方法及装置，其中，方法包括：第一接入网设备向第一网元发送第一指示信息，其中，所述第一指示信息用于指示第一接入网设备是否支持基于分组数据单元PDU集set的处理。由此，第一网元可以确定第一接入网设备是否支持基于PDU set的处理，以保障业务连续性和提高服务质量。

Description

业务处理方法及装置 技术领域
本公开涉及通信技术领域，尤其涉及一种业务处理方法及装置。
背景技术
移动媒体类服务、云AR(augmented reality，增强现实)/VR(virtual reality，虚拟现实)等XR(extended reality，扩展现实)业务、云游戏、基于视频的机器或无人机远程控制等业务，预计将为5G网络贡献越来越高的流量。XR业务还涉及多模态数据流，这些多模态数据，可以是描述同一业务或应用的从同一个设备或不同设备(包括传感器)输入的数据，这些数据可能会输出到一个或多个目的设备终端。多模态数据中的各数据流往往具有相关性，比如音频流和视频流的同步，触觉和视觉的同步等。
发明内容
本公开实施例提供一种业务处理方法及装置，用于解决QoS流中未标记(unmarked)PDUs和标记(marked)PDUs共存时，如何处理的问题。
本公开实施例提出了一种业务处理方法及装置。
根据本公开实施例的第一方面，提出了业务处理方法，包括：第一接入网设备向第一网元发送第一指示信息，其中，所述第一指示信息用于指示第一接入网设备是否支持基于分组数据单元PDU集set的处理；所述第一接入网设备确定将转发数据包中的标记PDU作为未标记PDU进行处理，其中，所述第一接入网设备不支持基于PDU set的处理，所述转发数据包中包括标记PDU；或者所述第一接入网设备确定在未标记PDU处理结束之前，将转发数据包中的标记PDU作为未标记PDU进行处理，其中，所述第一接入网设备支持基于PDU set的处理，所述转发数据包中包括标记PDU。
根据本公开实施例的第二方面，提出了业务处理方法，包括：第一接入网设备向第一网元发送第一指示信息，其中，所述第一指示信息用于指示第一接入网设备是否支持基于分组数据单元PDU集set的处理；第一接入网设备接收第一网元发送的优先指示；根据所述优先指示，执行标记PDU和非标记PDU的处理；
其中，所述优先指示用于指示以下至少一项：
收到标记PDU后优先执行基于PDU set的处理；
收到标记PDU后优先执行非标记PDU的处理；
收到标记PDU后优先基于所述第一接入网设备的本地配置自行执行；
收到标记PDU后优先根据操作管理和维护OAM配置执行。
根据本公开实施例的第二方面，提供一种存储介质，存储介质存储有指令，当指令在通信设备上运行时，使得通信设备执行如第一方面、第二方面所述的方法。
附图说明
为了更清楚地说明本公开实施例中的技术方案，以下对实施例描述所需的附图进行介绍，以下附图仅仅是本公开的一些实施例，不对本公开的保护范围造成具体限制。
图1是本公开实施例提供的一种通信系统的架构图；
图2是本公开实施例提供的一种5G组网架构的示意图；
图3是本公开实施例提供的一种业务处理方法的流程图；
图4A是本公开实施例提供的另一种业务处理方法的流程图；
图4B是本公开实施例提供的又一种业务处理方法的流程图；
图5A是本公开实施例提供的一种通信设备的结构图；
图5B是本公开实施例提供的一种芯片的结构示意图。
具体实施方式
第一方面，本公开实施例提出了一种业务处理方法，包括：第一接入网设备向第一网元发送第一指示信息，其中，所述第一指示信息用于指示第一接入网设备是否支持基于分组数据单元PDU集set的处理；所述第一接入网设备确定将转发数据包中的标记PDU作为未标记PDU进行处理，其中，所述第一接入网设备不支持基于PDU set的处理，所述转发数据包中包括标记PDU；或者所述第一接入网设备确定在未标记PDU处理结束之前，将转发数据包中的标记PDU作为未标记PDU进行处理，其中，所述第一接入网设备支持基于PDU set的处理，所述转发数据包中包括标记PDU。
第二方面，本公开实施例提出了一种业务处理方法，包括：第一接入网设备向第一网元发送第一指示信息，其中，所述第一指示信息用于指示第一接入网设备是否支持基于分组数据单元PDU集set的处理；第一接入网设备接收第一网元发送的优先指示；根据所述优先指示，执行标记PDU和非标记PDU的处理；
其中，所述优先指示用于指示以下至少一项：
收到标记PDU后优先执行基于PDU set的处理；
收到标记PDU后优先执行非标记PDU的处理；
收到标记PDU后优先基于所述第一接入网设备的本地配置自行执行；
收到标记PDU后优先根据操作管理和维护OAM配置执行。
第三方面，本公开实施例提出了存储介质，上述存储介质存储有指令，当上述指令在通信设备上运行时，使得上述通信设备执行如第一方面、第二方面的可选实现方式所描述的方法。
第四方面，本公开实施例提出了程序产品，上述程序产品被通信设备执行时，使得上述通信设备执行如第一方面、第二方面的可选实现方式所描述的方法。
第五方面，本公开实施例提出了计算机程序，当其在计算机上运行时，使得计算机执行如第一方面、第二方面和第三方面的可选实现方式所描述的方法。
第六方面，本公开实施例提供了一种芯片或芯片系统。该芯片或芯片系统包括处理电路，被配置为执行根据上述第一方面、第二方面的可选实现方式所描述的方法。
本公开实施例提出了一种业务处理方法及装置。在一些实施例中，业务处理方法与信息处理方法、通信方法等术语可以相互替换。
本公开实施例并非穷举，仅为部分实施例的示意，不作为对本公开保护范围的具体限制。在不矛盾的情况下，某一实施例中的每个步骤均可以作为独立实施例来实施，且各步骤之间可以任意组合，例如，在某一实施例中去除部分步骤后的方案也可以作为独立实施例来实施，且在某一实施例中各步骤的顺序可以任意交换，另外，某一实施例中的可选实现方式可以任意组合；此外，各实施例之间可以任意组合，例如，不同实施例的部分或全部步骤可以任意组合，某一实施例可以与其他实施例的可选实现方式任意组合。
在各本公开实施例中，如果没有特殊说明以及逻辑冲突，各实施例之间的术语和/或描述具有一致性，且可以互相引用，不同实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本公开实施例中所使用的术语只是为了描述特定实施例的目的，而并非作为对本公开的限制。
在本公开实施例中，除非另有说明，以单数形式表示的元素，如“一个”、“一种”、“该”、“上述”、“所述”、“前述”、“这一”等，可以表示“一个且只有一个”，也可以表示“一个或多个”、“至少一个”等。例如，在翻译中使用如英语中的“a”、“an”、“the”等冠词(article)的情况下，冠词之后的名词可以理解为单数表达形式，也可以理解为复数表达形式。
在本公开实施例中，“多个”是指两个或两个以上。
在一些实施例中，“至少一者(至少一项、至少一个)(atleastoneof)”、“一个或多个(one or more)”、“多个(a plurality of)”、“多个(multiple)等术语可以相互替换。
在一些实施例中，“A、B中的至少一者”、“A和/或B”、“在一情况下A，在另一情况下B”、“响应于一情况A，响应于另一情况B”等记载方式，根据情况可以包括以下技术方案：在一些实施例中A(与B无关地执行A)；在一些实施例中B(与A无关地执行B)；在一些实施例中从A和B中选择执行(A和B被选择性执行)；在一些实施例中A和B(A和B都被执行)。当有A、B、C等更多分支时也类似上述。
在一些实施例中，“A或B”等记载方式，根据情况可以包括以下技术方案：在一些实施例中A(与B无关地执行A)；在一些实施例中B(与A无关地执行B)；在一些实施例中从A和B中选择执行(A和B被选择性执行)。当有A、B、C等更多分支时也类似上述。
本公开实施例中的“第一”、“第二”等前缀词，仅仅为了区分不同的描述对象，不对描述对象的位置、顺序、优先级、数量或内容等构成限制，对描述对象的陈述参见权利要求或实施例中上下文的描述，不应因为使用前缀词而构成多余的限制。例如，描述对象为“字段”，则“第一字段”和“第二字段”中“字段”之前的序数词并不限制“字段”之间的位置或顺序，“第一”和“第二”并不限制其修饰的“字段”是否在同一个消息中，也不限制“第一字段”和“第二字段”的先后顺序。再如，描述对象为“等级”，则“第一等级”和“第二等级”中“等级”之前的序数词并不限制“等级”之间的优先级。再如，描述对象的数量并不受序数词的限制，可以是一个或者多个，以“第一装置”为例，其中“装置”的数量可以是一个或者多个。此外，不同前缀词修饰的对象可以相同或不同，例如，描述对象为“装置”，则“第一装置”和“第二装置”可以是相同的装置或者不同的装置，其类型可以相同或不同；再如，描述对象为“信息”， 则“第一信息”和“第二信息”可以是相同的信息或者不同的信息，其内容可以相同或不同。
在一些实施例中，“包括A”、“包含A”、“用于指示A”、“携带A”，可以解释为直接携带A，也可以解释为间接指示A。
在一些实施例中，“时频(time/frequency)”、“时频域”等术语是指时域和/或频域。
在一些实施例中，“响应于……”、“响应于确定……”、“在……的情况下”、“在……时”、“当……时”、“若……”、“如果……”等术语可以相互替换。
在一些实施例中，“大于”、“大于或等于”、“不小于”、“多于”、“多于或等于”、“不少于”、“高于”、“高于或等于”、“不低于”、“以上”等术语可以相互替换，“小于”、“小于或等于”、“不大于”、“少于”、“少于或等于”、“不多于”、“低于”、“低于或等于”、“不高于”、“以下”等术语可以相互替换。
在一些实施例中，装置等可以解释为实体的、也可以解释为虚拟的，其名称不限定于实施例中所记载的名称，“装置”、“设备(equipment)”、“设备(device)”、“电路”、“网元”、“节点”、“功能”、“单元”、“部件(section)”、“系统”、“网络”、“芯片”、“芯片系统”、“实体”、“主体”等术语可以相互替换。
在一些实施例中，“网络”可以解释为网络中包含的装置(例如，接入网设备、核心网设备等)。
在一些实施例中，“接入网设备(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)”、“服务小区”、“载波(carrier)”、“分量载波(component carrier)”、“带宽部分(bandwidth part，BWP)”等术语可以相互替换。
在一些实施例中，“终端(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)等术语可以相互替换。
在一些实施例中，接入网设备、核心网设备、或网络设备可以被替换为终端。例如，针对将接入网设备、核心网设备、或网络设备以及终端间的通信置换为多个终端间的通信(例如，设备对设备(device-to-device，D2D)、车联网(vehicle-to-everything，V2X)等)的结构，也可以应用本公开的各实施例。在该情况下，也可以设为终端具有接入网设备所具有的全部或部分功能的结构。此外，“上行”、“下行”等术语也可以被替换为与终端间通信对应的术语(例如，“侧行(side)”)。例如，上行信道、下行信道等可以被替换为侧行信道，上行链路、下行链路等可以被替换为侧行链路。
在一些实施例中，终端可以被替换为接入网设备、核心网设备、或网络设备。在该情况下，也可以设为接入网设备、核心网设备、或网络设备具有终端所具有的全部或部分功能的结构。
在一些实施例中，获取数据、信息等可以遵照所在地国家的法律法规。
在一些实施例中，可以在得到用户同意后获取数据、信息等。
此外，本公开实施例的表格中的每一元素、每一行、或每一列均可以作为独立实施例来实施，任意元素、任意行、任意列的组合也可以作为独立实施例来实施。
图1是本公开实施例提供的一种通信系统的架构图。
如图1所示，通信系统100包括终端(terminal)101、接入网设备102、核心网设备103。
在一些实施例中，终端101例如包括手机(mobile phone)、可穿戴设备、物联网设备、具备通信功能的汽车、智能汽车、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self-driving)中的无线终端设备、远程手术(remote medical surgery)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备、智慧家庭(smart home)中的无线终端设备中的至少一者，但不限于此。
在一些实施例中，终端还可以称之为终端设备、用户设备等，其名称可互换，本公开实施例对此不作具体限制。
在一些实施例中，接入网设备102例如是将终端接入到无线网络的节点或设备，接入网设备可以包括5G通信系统中的演进节点B(evolved NodeB，eNB)、下一代演进节点B(next generation eNB，ng-eNB)、下一代节点B(next generation NodeB，gNB)、节点B(node B，NB)、家庭节点B(home node B，HNB)、家庭演进节点B(home evolved nodeB，HeNB)、无线回传设备、无线网络控制器(radio network controller，RNC)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、基带单元(base band unit，BBU)、移动交换中心、6G通信系统中的基站、开放型基站(Open RAN)、云基站(Cloud RAN)、其他通信系统中的基站、Wi-Fi系统中的接入节点中的至少一者，但不限于此。
在一些实施例中，接入网设备102还可以为卫星。
在一些实施例中，核心网设备103可以是一个设备，包括第一网元、第二网元、第三网元等多个网元，也可以是多个设备或设备群，分别包括多个网络功能。网元又可以称为网络功能，网络功能可以是虚拟的，也可以是实体的。核心网例如包括演进分组核心(evolved packet core，EPC)、5G核心网络(5G core network，5GCN)、下一代核心(next generation core，NGC)中的至少一者。
在一些实施例中，第一网元例如是会话管理功能(session management function，SMF)。
在一些实施例中，第二网元例如是用户面功能(user planefunction，UPF)。
在一些实施例中，第一网元用于用于对终端进行分组数据单元(packet data unit，PDU)会话管理、PCF下发控制策略的执行、用户面功能(user plane function，UPF)网元的选择、PDU类型为IP类型时终端设备IP地址的分配等。
在一些实施例中，第二网元用于实现针对会话、业务流级别进行计费、QoS带宽保障及移动性管理、用户设备策略决策等策略控制功能。
可以理解的是，本公开实施例描述的通信系统是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提出的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本公开实施例提出的技术方案对于类似的技术问题同样适用。
下述本公开实施例可以应用于图1所示的通信系统100、或部分主体，但不限于此。图1所示的各主体是例示，通信系统可以包括图1中的全部或部分主体，也可以包括图1以外的其他主体，各主体数量和形态为任意，各主体可以是实体的也可以是虚拟的，各主体之间的连接关系是例示，各主体之间可以不连接也可以连接，其连接可以是任意方式，可以是直接连接也可以是间接连接，可以是有线连接也可以是无线连接。
本公开各实施例可以应用于长期演进(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(注册商标))、CDMA2000、超移动宽带(ultra mobile broadband，UMB)、IEEE 802.11(Wi-Fi(注册商标))、IEEE 802.16(WiMAX(注册商标))、IEEE 802.20、超宽带(ultra-wideband，UWB)、蓝牙(bluetooth(注册商标))、陆上公用移动通信网(public land mobile network，PLMN)网络、设备到设备(device-to-device，D2D)系统、机器到机器(machine to machine，M2M)系统、物联网(internet of things，IoT)系统、车联网(vehicle-to-everything，V2X)、利用其他通信方法的系统、基于它们而扩展的下一代系统等。此外，也可以将多个系统组合(例如，LTE或者LTE-A与5G的组合等)应用。
图2是本公开实施例提供的一种5G组网架构的示意图。
如图2所示，该5G组网架构相关的网络功能的介绍如下：
应用功能(application function，AF)：也称为应用控制器(applicationcontroller)，主要用于传递应用侧对网络侧的需求，例如服务质量(quality of service，QoS)需求、用户状态事件订阅等。AF可以是第三方应用的应用功能实体，也可以是运营商部署的应用服务，如IMS语音呼叫业务。其中，第三方应用的应用功能实体与核心网进行交互时可经由能力开放功能(network exposure function，NEF)进行授权处理，例如第三方应用的应用功能实体直接向NEF发送请求消息，NEF验证AF是否被允许发送该请求消息，若验证通过，则转发该请求消息至对应的策略控制功能(policy controlfunction， PCF)或统一数据管理功能(unified data management，UDM)。
PCF：主要用于实现针对会话、业务流级别进行计费、QoS带宽保障及移动性管理、用户设备策略决策等策略控制功能。
UDM：主要用于实现管理签约信息、用户接入授权等数据管理功能。
接入和移动性管理功能(access and mobility management function，AMF)：主要用于实现对终端进行移动性管理、接入鉴权/授权等功能。此外，AMF还负责在终端与PCF间传递用户策略。
会话管理功能(session management function，SMF)：主要用于对终端进行分组数据单元(packet data unit，PDU)会话管理、PCF下发控制策略的执行、用户面功能(user plane function，UPF)的选择、PDU类型为IP类型时终端IP地址的分配等。
UPF：主要用于作为终端和数据网络的接口，完成用户面数据转发、基于会话/流级的计费统计、带宽限制等功能。
统一数据仓库(unified data repository，UDR)：主要负责签约信息、策略数据、应用数据等类型的数据的存取功能，UDR可以与UDM、PCF、NEF等进行接口互联，以实现对应网元访问或调用。
当然，核心网中也可以包括除以上示例说明的网络功能之外的其它网络功能，这里不再一一列举。
需要说明的是，本公开实施例对实现各功能的对应网络功能的名称并不限定，其还可以实现其他功能或与其他功能网元进行融合，并且还可以称为其他名称。
在图2所示的5G组网架构中，网络功能与网络功能、网络功能与设备间的一些相关通信接口的主要功能介绍如下：
N1接口：为AMF网元与终端之间的信令面接口，与接入网无关，用于核心网与终端之间交换信令消息，可用于终端注册入网、终端建立PDU会话、网络侧配置终端策略等流程中。
N2接口：为AMF网元与RAN设备之间的接口，用于传递核心网至RAN设备的无线承载控制信息等。
]N3接口:为(R)AN设备与UPF网元之间的接口，用于在RAN设备和UPF网元之间传递终端的业务数据。
N4接口：为SMF网元与UPF网元之间的接口，用于传递控制面与用户面之间的信息，可用于控制面终端根据与运营商的签约信息完成入网操作等流程中。
N6接口：为UPF网元与DN之间的接口，用于在UPF网元和DN之间传递终端的业务数据。
N7接口：为PCF网元与SMF网元之间的接口，用于下发PDU会话粒度以及业务数据流粒度控制策略等信息。
N8接口：为AMF网元与UDM网元之间的接口，用于AMF网元从UDM网元获取接入与移动性管理相关签约信息与鉴权数据，以及AMF网元向UDM网元注册终端当前移动性管理相关信息等。
N10接口：为SMF网元与UDM网元之间的接口，用于SMF网元从UDM网元获取会话管理相关签约信息，以及SMF网元向UDM网元注册终端当前会话相关信息等。
N11接口：为SMF网元与AMF网元之间的接口，用于传递RAN设备和UPF网元之间的PDU会话隧道信息、发送给终端的控制消息、发送给RAN设备的无线资源控制信息等。
移动媒体类服务、云AR(augmented reality，增强现实)/VR(virtual reality，虚拟现实)等XR(extended reality，扩展现实)业务、云游戏、基于视频的机器或无人机远程控制等业务，预计将为5G网络贡献越来越高的流量。XR业务还涉及多模态数据流，这些多模态数据，可以是描述同一业务或应用的从同一个设备或不同设备(包括传感器)输入的数据，这些数据可能会输出到一个或多个目的设备终端。多模态数据中的各数据流往往具有相关性，比如音频流和视频流的同步，触觉和视觉的同步等。这类媒体业务的数据流本身，各数据流之间，以及这些业务数据流对网络传输的需求，都存在一些共性特征，这些特性的有效识别和利用将更有助于网络和业务的传输、控制，也更有助于业务保障和用户体验。
XRM(XR and media)业务需要第五代移动通信系统(the 5th generation system，5GS)综合考虑业务的相关数据流服务质量(quality of service，QoS)特性，例如延迟严重保证比特率(guaranteed bitrate，GBR)数据流，保证流比特率(guaranteed flow bit rate，GFBR)，包时延预算(packet delay budget，PDB)，违约最大数据突发量(maximum data burstvolume，MDBV)等参数是否能同时满足并协同一致。涉及一个终端的多个XRM数据流，和多个终端的XRM数据流，彼此的QoS授权与执行的一致性保障。
在5G系统中，支持AF对XRM业务数据流基于每一个PDU集(Per PDU set)处理的功能增强。来支持AF对XRM业务数据流的QoS感知和保障增强，以及用户的QoE增强。包括，AF提供PDU  Set特定的QoS特性和协议说明：
-PDU集合延迟预算(PDU Set Delay Budget，PSDB)；
-PDU Set错误率(PDU Set Error Rate，PSER)；
-PDU Set集成处理信息(PSIHI)。
SMF和UPF可结合AF提供的协议说明和协议头扩展执行相应SDF PDU set中相应PDU的通用分组无线业务用户面隧道协议(general packet radio service tunnellingprotocol for the user plane，GTP-U)头扩展，携带PDU Set信息。其中，PDU Set信息由NG-RAN用于基于PDU Set的QoS处理。PDU Set信息包括：
-PDU Set序列号。
-PDU Set的最后一个PDU的指示。
-PDU Set内部的PDU序列号。
-PDU Set大小(以字节为单位)。
-PDU Set重要性，用于标识在QoS流中与其他PDU Set相比的相对重要性。
UPF将基于PDR规则执行AF SDF业务数据流到QoS流(flow)的映射；并将关联PDU封装为PDU set；对该QoS flow内的PDU Set执行PDU集合错误率(PDU Set Error Rate，PSER)和PDU集合延迟预算(PDU Set Delay Budget，PSDB)等相关Set相关QoS策略。
5GS系统支持的QoS处理，同一个QoS flow中要么支持基于PDU的QoS规则和参数策略，要么支持基于PDU set的QoS规则和参数策略。即一个QoS flow中同时激活处理的QoS参数只有一套，为基于PDU的QoS机制，或基于PDU set的QoS机制。
而实际网络中，存在功能支持不对等的的NG-RAN(Non-homogenous support)。比如不支持PDU set处理的NG-RAN，和支持PDU set处理的NG-RAN。由于XR的业务连续性需求，在切换(Handover)流程中(例如终端移动性)，需要对下行数据执行数据转发(Data forwarding)。(Data forwarding支持直接和间接模式，直接模式中，源(Source)NG-RAN转发到目标(target)NG-RAN，间接模式中，由UPF执行data forwarding给target-NG-RAN。需要说明的是，在间接模式中，执行数据转发的UPF不一定是源NG-RAN对应的UPF。
其中，当切换(Handover，HO)发生在不支持PDU set处理的NG-RAN和支持PDU set处理的NG-RAN之间时，尤其是从不支持PDU set处理的源(source)NG-RAN切换到支持PDU set处理的目标(Target)NG-RAN，同一个QoS流中会同时存在未标记(unmarked)PDUs和标记(marked)PDUs。
但是，5GS系统不支持同一个QoS流中同时存在未标记(unmarked)PDUs和标记(marked)PDUs的场景，无法保障相应QoS流的QoS。
如何处理QoS流中未标记(unmarked)PDUs和标记(marked)PDUs共存的QoS处理，是5GS保障云游戏等XR交互类业务必须要解决的问题。
基于此，本公开实施例提供一种业务处理方法及装置，以解决QoS流中未标记(unmarked)PDUs和标记(marked)PDUs共存时如何处理的问题，保障业务连续性和提高服务质量。
在一些实施例中，信息等的名称不限定于实施例中所记载的名称，“信息(information)”、“消息(message)”、“信号(signal)”、“信令(signaling)”、“报告(report)”、“配置(configuration)”、“指示(indication)”、“指令(instruction)”、“命令(command)”、“信道”、“参数(parameter)”、“域”、“字段”、“符号(symbol)”、“码元(symbol)”、“码本(codebook)”、“码字(codeword)”、“码点(codepoint)”、“比特(bit)”、“数据(data)”、“程序(program)”、“码片(chip)”等术语可以相互替换。
在一些实施例中，“上行”、“上行链路”、“物理上行链路”等术语可以相互替换，“下行”、“下行链路”、“物理下行链路”等术语可以相互替换，“侧行(side)”、“侧行链路(sidelink)”、“侧行通信”、“侧行链路通信”、“直连”、“直连链路”、“直连通信”、“直连链路通信”等术语可以相互替换。
在一些实施例中，“下行链路控制信息(downlink control information，DCI)”、“下行链路(downlink，DL)分配(assignment)”、“DL DCI”、“上行链路(uplink，UL)许可(grant)”、“UL DCI”等术语可以相互替换。
在一些实施例中，“物理下行链路共享信道(physical downlink shared channel，PDSCH)”、“DL数据”等术语可以相互替换，“物理上行链路共享信道(physical uplink shared channel，PUSCH)”、“UL数据”等术语可以相互替换。
在一些实施例中，“无线(radio)”、“无线(wireless)”、“无线接入网(radio access network，RAN)”、“接入网(access network，AN)”、“基于RAN的(RAN-based)”等术语可以相互替换。
在一些实施例中，“时刻”、“时间点”、“时间”、“时间位置”等术语可以相互替换，“时长”、“时段”、“时间窗口”、“窗口”、“时间”等术语可以相互替换。
在一些实施例中，“资源块(resource block，RB)”、“物理资源块(physical resource block，PRB)”、“子载波组(sub-carrier group，SCG)”、“资源元素组(resource element group，REG)”、“PRB对”、“RB对”、“资源元素(resource element，RE)”、“子载波(sub-carrier)”等术语可以相互替换。
在一些实施例中，无线接入方案(wireless access scheme)、波形(waveform)等术语可以相互替换。
在一些实施例中，“帧(frame)”、“无线帧(radio frame)”、“子帧(subframe)”、“时隙(slot)”、“子时隙(sub-slot)”、“迷你时隙(mini-slot)”、“符号(symbol)”、“码元(symbol)”、“发送时间间隔(transmission time interval，TTI)”等术语可以相互替换。
在一些实施例中，“获取”、“获得”、“得到”、“接收”、“传输”、“双向传输”、“发送和/或接收”可以相互替换，其可以解释为从其他主体接收，从协议中获取，从高层获取，自身处理得到、自主实现等多种含义。
在一些实施例中，“发送”、“发射”、“上报”、“下发”、“传输”、“双向传输”、“发送和/或接收”等术语可以相互替换。
在一些实施例中，“特定(certain)”、“预定(preseted)”、“预设”、“设定”、“指示(indicated)”、“某一”、“任意”、“第一”等术语可以相互替换，“特定A”、“预定A”、“预设A”、“设定A”、“指示A”、“某一A”、“任意A”、“第一A”可以解释为在协议等中预先规定的A，也可以解释为通过设定、配置、或指示等得到的A，也可以解释为特定A、某一A、任意A、或第一A等，但不限于此。
在一些实施例中，判定或判断可以通过以1比特表示的值(0或1)来进行，也可以通过以真(true)或者假(false)表示的真假值(布尔值(boolean))来进行，也可以通过数值的比较(例如，与预定值的比较)来进行，但不限于此。
为方便理解本公开实施例，提供如下示例性实施例。
5GS系统支持的QoS处理，同一个QoS flow中要么支持基于PDU的QoS规则和参数策略，要么支持基于PDU set的QoS规则和参数策略。即一个QoS flow中同时激活处理的QoS参数只有一套，为基于PDU的QoS机制，或基于PDU set的QoS机制。
而实际网络中，存在各类功能支持差异的NG-RAN(Non-homogenous support)。比如不支持PDU set处理的NG-RAN，和支持PDU set处理的NG-RAN。由于XR的业务连续性需求，在切换(Handover)流程中(例如终端移动性)，需要对下行数据执行数据转发(Data forwarding)。(Data forwarding支持直接和间接模式，直接模式中，源(Source)NG-RAN转发到目标(target)NG-RAN，间接模式中，由UPF执行data forwarding给target-NG-RAN。需要说明的是，在间接模式中，执行数据转发的UPF不一定是源NG-RAN对应的UPF。
其中，当切换(Handover，HO)发生在不支持PDU set处理的NG-RAN和支持PDU set处理的NG-RAN之间时，尤其是从不支持PDU set处理的源(source)NG-RAN切换到支持PDU set处理的目标(Target)NG-RAN，同一个QoS流中会同时存在未标记(unmarked)PDUs和标记(marked)PDUs。
但是，5GS系统不支持同一个QoS流中同时存在未标记(unmarked)PDUs和标记(marked)PDUs的场景，无法保障相应QoS流的QoS。
如何处理QoS流中未标记(unmarked)PDUs和标记(marked)PDUs共存的问题，是5GS保障云游戏等XR交互类业务必须要解决的问题。
本公开实施例中，NG-RAN不同时支持一个QoS流内的标记PDUs和未标记PDUs的混合处理，将标记PDU按未标记PDU处理，该处理可以是特定时间内执行，其中特定时间可根据配置设定，或可依据收到的结束数据(End Marker)包和/或过渡处理窗口等来设定执行，进一步可将过渡处理窗口等信息发送给SMF。具体实现方案：
在NG-RAN的Xn切换和N2切换过程中，目标NG-RAN向SMF提供一个第一指示信息，用于指示目标NG-RAN节点是否支持基于PDU Set的处理。
在一些实施例中，第一指示信息包含在Xn切换过程中的路径切换请求消息中，或者第一指示信息包含在N2切换的切换请求确认消息中。
在一些实施例中，源NG-RAN支持基于PDU Set的处理，切换的目标NG-RAN不支持基于PDU Set的处理，其中，对于目标NG-RAN，若接收到转发数据包，例如源NG-RAN直接转发过来的数 据包，或UPF间接转发过来的数据包，由于源NG-RAN支持基于PDU Set的处理，所转发的转发数据包中可能包括标记PDU，目标NG-RAN接收到转发数据包之后，可将标记PDU作为未标记PDU进行处理，忽略PDU Set的QoS参数，执行PDUQoS参数，忽略标记PDU的用于标识用于标识PDU Set信息的协议扩展头头(header extensions))。
在一些实施例中，源NG-RAN不支持基于PDU Set的处理，切换的目标NG-RAN支持基于PDU Set的处理，其中，对于目标NG-RAN，若接收到转发数据包，例如源NG-RAN直接转发过来的数据包，或UPF间接转发过来的数据包，由于源NG-RAN不支持基于PDU Set的处理，所转发的转发数据包中可能包括未标记PDU，目标NG-RAN接收到转发数据包(通过转发隧道接收到的在EndMarker结束数据包之前的数据包)，在未标记PDU的处理结束之前，目标NG-RAN将接收到的标记PDU作为未标记PDU进行处理(这样在同一时间所有PDU均作为未标记PDU处理)，忽略标记PDU的PDU SetQoS参数，使用PDUQoS参数，即忽略用于标识PDU Set信息的协议扩展头)。
并且，在未标记PDU处理结束之后，目标NG-RAN可以根据PDU Set的QoS参数和扩展协议头中的PDU Set信息(或者UPF配置的PDUset信息，以及协议描述中的PDUset信息)处理标记PDU。
在一些实施例中，源NG-RAN不支持基于PDU Set的处理，切换的目标NG-RAN支持基于PDU Set的处理，其中，对于目标NG-RAN，若接收到转发数据包，例如源NG-RAN直接转发过来的数据包，或UPF间接转发过来的数据包，由于源NG-RAN不支持基于PDU Set的处理，所转发的转发数据包中可能包括未标记PDU，目标NG-RAN可以在一个特定窗口内(比如启动一个定时器)，定时器计时期间，目标NG-RAN将接收到的标记PDU作为未标记PDU进行处理，忽略PDU Set的QoS参数，在定时器结束后，目标NG-RAN可以根据PDU Set的QoS参数和扩展协议头中的PDU Set信息处理标记PDU。
在一种可能的实现方式中，目标NG-RAN在接收到结束数据(End Marker)包后启动上述定时器，定时器的时长为继续处理切换窗口时长(该切换过程中的标记PDU作为未标记PDU处理，可以在接收到EndMarker包之前已经开始，收到EndMarker包之后的剩余时间更容易确定)。
在一种可能的实现方式中，目标NG-RAN在接收到SMF发送的PDU Set的QoS参数后启动上述定时器，定时器的时长为继续处理切换窗口时长(该切换过程中的标记PDU作为未标记PDU处理，可以在接收到SMF发送的PDU Set的QoS参数之前已经开始)。
其中，处理切换窗口时长可以大于等于目标NG-RAN(可根据本地配置或OA配置或收到的EndMark包或收到的PDUSet相关QoS参数)设定的定时器启动到未标记PDU处理完成需要的时长。
在一种可能的实现方式中，目标NG-RAN在接收到SMF发送的PDU Set的QoS参数后，可以向SMF发送一个第二指示信息，第二指示信息用于指示目标NG-RAN是否接受(接受或拒绝)已接收到PDU Set的QoS参数，其中，NG-RAN拒绝该PDUSetQoS参数则NG-RANPDUSetQoS处理功能未激活，接受则NG-RANPDUSetQoS处理功能激活。
在一些实施例中，SMF可以请求目标NG-RAN为给定的QoS流激活基于PDU Set的QoS处理，目标NG-RAN可以向SMF提供是否接受(接受或拒绝)接收到的PDU Set的QoS参数的指示。
在一些实施例中，NG-RAN可以向SMF提供是否激活PDU Set的QoS参数的指示，以及延迟应用的时间，或延迟激活的时间(与应用的PDU Set的QoS参数的开始时间(或时间窗口)相关)。该时间可以根据目标NG-RAN中用于处理标记PDU的定时器来确定。
在一些实施例中，SMF根据目标NG-RAN的指示或延迟应用的时间/延迟激活的时间，将PSA UPF配置为激活/或去激活/停用PDU组识别和标记(对PDU数据包进行PDU组相关的识别和扩展协议头标记)。
在一些实施例中，PSA UPF在完整的PDU set结束时向目标NG-RAN发送结束标记数据包(End Marker packets)。或者说，PSA UPF从一个完整的PDU set的最初(比如第一个数据包)开始执行PDUset的识别和扩展协议头标记，在一个完整的PDU的结束(比如最后一个数据包)停止或结束执行PDUset的识别和扩展协议头标记(End Marker packets就在PDUset的最后一个数据包之后发送)。
或者，PSA UPF识别和标记带有PDU Set信息的PDU(比如识别带有RTP或RTCP扩展协议头的PDU，将其中带有PDUSet信息的协议扩展头映射为GTP-U协议扩展头，将PDUSet信息在GTP-U扩展协议头中携带给NG-RAN)。它从一个完整的PDU set开始这样做。第一个PDU set包括与通过源转发隧道发送的数据包重叠的PDU(这里重叠的数据包已经在源通道发送，但不是一个PDUset的结束，比如Set的前半部分，则将这部分和未发送的后半部分一起作为一个完整的PDUset，在新通道中发送)，如果结束标记数据包不是发送在一个完整的PDU set结束时(比如发送在PDUSet中间)。
或者，PSA UPF识别和标记带有PDU Set信息的PDU(比如识别带有RTP或RTCP扩展协议头 的PDU，将其中带有PDUSet信息的协议扩展头映射为GTP-U协议扩展头，将PDUSet信息在GTP-U扩展协议头中携带给NG-RAN)。它将通过源转发隧道发送的PDU set的剩余数据包，作为单个数据包分别发送。然后，它从一个完整的PDU set开始，进行数据包的识别和标记PDUset信息到扩展协议头，如果结束标记数据包不是发送在一个完整的PDU set结束时(比如发送在PDUSet中间)。
示例性实施例中，如图3所示。以源(Source)NG-RAN切换至目标(Target)NG-RAN，AMF未更改，且SMF决定保留现有的UPF，并通过Xn将终端从源NG-RAN切换至目标NG-RAN的情况为例进行说明。
1a、如果通用陆地移动网络，(public land mobile network，PLMN)配置了次要无线接入技术(Radio Access Technology，RAT)使用情况报告，源NG-RAN节点在切换执行阶段可能会向AMF提供RAN使用情况数据报告(N2会话管理(Session Management，SM)信息(次要RAT使用情况数据)、切换标志、源到目标透明容器)。源NG-RAN节点只有在目标NG-RAN通过Xn接口确认切换时才应提供此报告。切换标志向AMF表明它应在转发之前缓冲包含使用情况数据报告的N2 SM信息。
1b.目标NG-RAN到AMF：N2路径切换请求(要切换的PDU会话列表，附带N2 SM信息的要切换的PDU会话列表，以N2 SM信息元素中给出的失败原因为基础的未能建立的PDU会话列表，终端位置信息)，目标NG-RAN向AMF发送N2路径切换请求消息，通知终端已移动到新的目标小区，并提供要切换的PDU会话列表。每个要切换的PDU会话的AN隧道信息都包含在N2 SM信息中。对于要切换到目标NG-RAN的PDU会话，N2路径切换请求消息应包括接受的QoS流列表。对于每个接受了替代QoS配置文件的QoS流，N2 SM信息应包括对已满足的替代QoS配置文件的引用。
在NG-RAN的Xn切换和N2切换过程中，目标NG-RAN向SMF提供一个第一指示信息，用于指示目标NG-RAN节点是否支持基于PDU Set的处理。
在一些实施例中，第一指示信息包含在Xn切换过程中的路径切换请求消息中，或者第一指示信息包含在N2切换的切换请求确认消息中。
在一些实施例中，源NG-RAN支持基于PDU Set的处理，切换的目标NG-RAN不支持基于PDU Set的处理，其中，对于目标NG-RAN，若接收到转发数据包，例如源NG-RAN直接转发过来的数据包，或UPF间接转发过来的数据包，由于源NG-RAN支持基于PDU Set的处理，所转发的转发数据包中可能包括标记PDU，目标NG-RAN接收到转发数据包之后，可将标记PDU作为未标记PDU进行处理，忽略PDU Set的QoS参数，执行PDUQoS参数，忽略标记PDU的用于标识用于标识PDU Set信息的协议扩展头(header extensions))。
在一些实施例中，源NG-RAN不支持基于PDU Set的处理，切换的目标NG-RAN支持基于PDU Set的处理，其中，对于目标NG-RAN，若接收到转发数据包，例如源NG-RAN直接转发过来的数据包，或UPF间接转发过来的数据包，由于源NG-RAN不支持基于PDU Set的处理，所转发的转发数据包中可能包括未标记PDU，目标NG-RAN接收到转发数据包(通过转发隧道接收到的在EndMarker结束数据包之前的数据包)，在未标记PDU的处理结束之前，目标NG-RAN将接收到的标记PDU作为未标记PDU进行处理(这样在同一时间所有PDU均作为未标记PDU处理)，忽略标记PDU的PDU SetQoS参数，使用PDUQoS参数，即忽略用于标识PDU Set信息的协议扩展头)。
并且，在未标记PDU处理结束之后，目标NG-RAN可以根据PDU Set的QoS参数和扩展协议头中的PDU Set信息(或者UPF配置的PDUset信息，以及协议描述中的PDUset信息)处理标记PDU。
在一些实施例中，源NG-RAN不支持基于PDU Set的处理，切换的目标NG-RAN支持基于PDU Set的处理，其中，对于目标NG-RAN，若接收到转发数据包，例如源NG-RAN直接转发过来的数据包，或UPF间接转发过来的数据包，由于源NG-RAN不支持基于PDU Set的处理，所转发的转发数据包中可能包括未标记PDU，目标NG-RAN可以在一个特定窗口内(比如启动一个定时器)，定时器计时期间，目标NG-RAN将接收到的标记PDU作为未标记PDU进行处理，忽略PDU Set的QoS参数，在定时器结束后，目标NG-RAN可以根据PDU Set的QoS参数和扩展协议头中的PDU Set信息处理标记PDU。
在一种可能的实现方式中，目标NG-RAN在接收到结束数据(End Marker)包后启动上述定时器，定时器的时长为继续处理切换窗口时长(该切换过程中的标记PDU作为未标记PDU处理，可以在接收到EndMarker包之前已经开始，收到EndMarker包之后的剩余时间更容易确定)。
在一种可能的实现方式中，目标NG-RAN在接收到SMF发送的PDU Set的QoS参数后启动上述定时器，定时器的时长为继续处理切换窗口时长(该切换过程中的标记PDU作为未标记PDU处理，可以在接收到SMF发送的PDU Set的QoS参数之前已经开始)。
其中，处理切换窗口时长可以大于等于目标NG-RAN(可根据本地配置或OA配置或收到的 EndMark包或收到的PDUSet相关QoS参数)设定的定时器启动到未标记PDU处理完成需要的时长。
在一种可能的实现方式中，目标NG-RAN在接收到SMF发送的PDU Set的QoS参数后，可以向SMF发送一个第二指示信息，第二指示信息用于指示目标NG-RAN是否接受(接受或拒绝)已接收到PDU Set的QoS参数，其中，NG-RAN拒绝该PDUSetQoS参数则NG-RANPDUSetQoS处理功能未激活，接受则NG-RANPDUSetQoS处理功能激活。
在一些实施例中，SMF可以请求目标NG-RAN为给定的QoS流激活基于PDU Set的QoS处理，目标NG-RAN可以向SMF提供是否接受(接受或拒绝)接收到的PDU Set的QoS参数的指示。
在一些实施例中，NG-RAN可以向SMF提供是否激活PDU Set的QoS参数的指示，以及延迟应用的时间，或延迟激活的时间(与应用的PDU Set的QoS参数的开始时间(或时间窗口)相关)。该时间可以根据目标NG-RAN中用于处理标记PDU的定时器来确定。
在一些实施例中，SMF根据目标NG-RAN的指示或延迟应用的时间/延迟激活的时间，将PSA UPF配置为激活/或去激活/停用PDU组识别和标记(对PDU数据包进行PDU组相关的识别和扩展协议头标记)。
2、AMF到SMF：Nsmf_协议数据单元更新会话管理上下文请求(Nsmf_PDUSession_UpdateSMContext)(从步骤1b中接收的N2 SM信息和来自源NG-RAN的N2 SM信息(次要RAT使用情况数据)、终端位置信息、终端在本地区域数据网络(Local Area Data Network，LADN)服务区域的存在情况)。这里的源NG-RAN的N2 SM信息是在适用的情况下在步骤1a中缓冲的信息。
AMF通过调用Nsmf_PDUSession_UpdateSMContext请求服务操作，为N2路径切换请求中接收到的每个PDU会话发送N2 SM信息。这些信息包括步骤1中的，目标NG-RAN向SMF提供有关是否支持基于PDU Set的处理的指示；来自目标NG-RAN的"PDU set support"指示将包含在路径切换请求消息(Xn切换)中。Nsmf_PDUSession_UpdateSMContext请求要么包含要切换PDU会话的指示(以及要使用的N3寻址信息和传输的QoS流信息)，要么包含要拒绝的PDU会话的指示(以及拒绝原因)。
如果目标NG-RAN未接受某个PDU会话的一些QoS流，那么在切换过程完成后，SMF应启动PDU会话修改过程，从PDU会话中移除未被接受的QoS流。
3、SMF到UPF：N4会话修改请求(AN隧道信息)，对于由目标NG-RAN修改的PDU会话，SMF向UPF发送N4会话修改请求消息。SMF可以通知发起数据通知的UPF丢弃PDU会话的下行数据，和/或不再提供进一步的数据通知消息。根据网络部署的不同，用于连接到目标NG-RAN和源NG-RAN的UPF的CN隧道信息可能不同，例如，源NG-RAN和目标NG-RAN位于不同的IP域中。在这种情况下，SMF可能会要求UPF分配新的CN隧道信息，并提供目标网络实例。
4、UPF到SMF：N4会话修改响应(CN隧道信息)，对于已切换的PDU会话，UPF在请求的PDU会话切换后向SMF返回N4会话修改响应消息。对于未释放用户面资源并且由SMF请求的PDU会话，上行流量的隧道标识仅包括在响应中。
5、为了协助目标NG-RAN中的重新排序功能，UPF在切换路径后立即为旧路径上的每个N3隧道发送一个或多个“结束标记”数据(EndMarker)包。UPF开始向目标NG-RAN发送下行链路数据包。
在一些实施例中，PSA UPF在完整的PDU set结束时向目标NG-RAN发送结束标记数据包(End Marker packets)。或者说，PSA UPF从一个完整的PDU set的最初(比如第一个数据包)开始执行PDUset的识别和扩展协议头标记，在一个完整的PDU的结束(比如最后一个数据包)停止或结束执行PDUset的识别和扩展协议头标记(End Marker packets就在PDUset的最后一个数据包之后发送)。
或者，PSA UPF识别和标记带有PDU Set信息的PDU(比如识别带有RTP或RTCP扩展协议头的PDU，将其中带有PDUSet信息的协议扩展头映射为GTP-U协议扩展头，将PDUSet信息在GTP-U扩展协议头中携带给NG-RAN)。它从一个完整的PDU set开始这样做。第一个PDU set包括与通过源转发隧道发送的数据包重叠的PDU(这里重叠的数据包已经在源通道发送，但不是一个PDUset的结束，比如Set的前半部分，则将这部分和未发送的后半部分一起作为一个完整的PDUset，在新通道中发送)，如果结束标记数据包不是发送在一个完整的PDU set结束时(比如发送在PDUSet中间)。
或者，PSA UPF识别和标记带有PDU Set信息的PDU(比如识别带有RTP或RTCP扩展协议头的PDU，将其中带有PDUSet信息的协议扩展头映射为GTP-U协议扩展头，将PDUSet信息在GTP-U扩展协议头中携带给NG-RAN)。它将通过源转发隧道发送的PDU set的剩余数据包，作为单个数据包分别发送。然后，它从一个完整的PDU set开始，进行数据包的识别和标记PDUset信息到扩展 协议头，如果结束标记数据包不是发送在一个完整的PDU set结束时(比如发送在PDUSet中间)。
基于NG-RAN的指示和/或激活时间，SMF配置PSA UPF来激活/停用PDU Set标识和标记。
对于PSA UPF在GTP-U头中识别和标记带有PDU Set信息的PDU的情况，它应从一个完整的PDU集开始这样做。(此外，如果源NG-RAN发送的话，在End Marker数据包后的PDU不是一个完整的PDU集的开始，则会重叠一部分已发送的PDU执行PDU Set封装)。PSA UPF在GTP-U头中识别和标记带有PDU Set信息的PDU，应从一个完整的PDU集开始。第一个PDU集将包括与通过源转发隧道发送的数据包重叠的PDU，如果在一个完整的PDU集结束时没有发送结束标记数据包。
6、SMF到AMF：Nsmf_PDUSession_UpdateSMContext响应(N2 SM信息)
SMF向AMF发送Nsmf_PDUSession_UpdateSMContext响应(N2 SM信息(CN隧道信息，已接受的QoS流的更新CN包延时估算(packet delay budget，PDB)，已接受的QoS流的更新时延敏感通信辅助信息(time sensitive communication assistance information，TSCAI))，用于已成功切换的PDU会话。发送给AMF的UPF的CN隧道信息用于建立N3隧道。对于每个已接受的时延关键资源类型的保证比特率(guaranteed bit rate，GBR)QoS流，SMF可能会更新动态CN PDB和TSCAI，并将其发送给目标NG-RAN。SMF可以基于本地配置，在响应中或使用单独的PDU会话修改过程中更新CN PDB和TSCAI。
对于XR业务流，SMF在该消息中携带相应PDU set QoS参数以及流描述等信息，给目标NG-RAN。或者SMF后续单独发起一个PDU session会话修改流程，携带更新后的PDU set QoS参数及流描述等信息。
如果源NG-RAN不支持替代QoS配置文件而目标NG-RAN支持它们，SMF会在每个QoS流的基础上向目标NG-RAN发送可用的替代QoS配置文件。
注意：步骤6可以在SMF收到N4会话修改响应后的任何时间发生。
7、AMF到NG-RAN：N2路径切换请求确认(N2 SM信息，未成功的PDU会话，UE无线能力标识)。
8、通过向源NG-RAN发送释放资源消息，目标NG-RAN确认切换成功。然后，目标NG-RAN触发与源NG-RAN的资源释放。
9、如果注册流程的触发条件之一适用，终端可以启动移动性注册更新过程。
示例性实施例中，如图4A和图4B所示，源NG-RAN的N2接口的非Xn切换到目标NG-RAN，包括如图4A所示的准备阶段和图4B所示的执行阶段。以源NG-RAN为S-NG-RAN、源AMF为S-AMF、源UPF为S-UPF、目标NG-RAN为T-NG-RAN、目标AMF为T-AMF、目标UPF为T-UPF为例进行说明。
当源NG-RAN决定执行非Xn切换时，它向AMF发送N2路径切换请求。此请求包括所需切换的PDU会话列表、目标NG-RAN的标识和其他相关信息。
AMF收到N2路径切换请求后，开始准备非Xn切换。AMF可能需要进行一些准备工作，例如更新相关上下文信息、获取目标NG-RAN的状态等。
执行阶段：
当准备阶段完成后，AMF发送N2路径切换请求确认给源NG-RAN。这表明AMF已准备好执行切换。
源NG-RAN根据AMF的确认，开始准备终端的切换。源NG-RAN可以将PDU会话信息、用户数据和相关上下文传输到目标NG-RAN。
目标NG-RAN收到切换相关的信息后，准备好接受终端。目标NG-RAN可以分配资源、更新上下文信息等。
当目标NG-RAN准备就绪时，源NG-RAN触发终端的切换。源NG-RAN可以发送指令给终端，向终端发送指示切换到目标NG-RAN的信号。
终端开始在目标NG-RAN上进行通信。目标NG-RAN负责终端的连接和服务。
如图4A所示，准备阶段：
1、S-NG-RAN到S-AMF：切换请求(目标标识，源到目标透明容器，SM N2信息列表，PDU会话标识，系统内切换指示)。
源到目标透明容器包括由S-NG-RAN创建的NG-RAN信息，将由T-NG-RAN使用，对5GC透明。它还包含了每个PDU会话的相应QoS流/DRB信息，用于数据转发。
2-7、选择新的AMF、UPF，获取新的UPF隧道信息。
7、SMF到T-AMF：Nsmf_PDUSession_UpdateSMContext响应(PDU会话标识，N2 SM信息， 未接受的原因)。
如果PDU会话的N2切换被接受，SMF会在Nsmf_PDUSession_UpdateSMContext响应中包括N2 SM信息，其中包含了UPF的N3 UP地址和UL CN隧道ID、QoS参数、TSCAI以及目标NG-RAN的用户平面安全执行信息。
8、T-AMF监督来自涉及的SMF的Nsmf_PDUSession_UpdateSMContext响应消息。
9、T-AMF到T-NG-RAN：切换请求(源到目标透明容器，N2MM信息，N2 SM信息列表，追踪要求，终端无线能力标识)。T-AMF根据目标标识确定T-NG-RAN。T-AMF可能为终端在T-AMF和目标跟踪区域标识(Tracking Area Identity，TAI)中分配一个有效的5G-全局唯一的临时标识(globally unique temporary identity，GUTI)。
源到目标透明容器按照从S-NG-RAN接收的方式进行转发。N2MM信息包括安全信息和移动限制列表(如果在T-AMF中可用)。
N2 SM信息列表包括从SMF接收的N2 SM信息，这些信息在允许的最大延迟内通过T-AMF在步骤8中监督的Nsmf_PDUSession_UpdateSMContext响应消息中接收，这些消息是为T-NG-RAN准备的。
10、T-NG-RAN到T-AMF：切换请求确认(目标到源透明容器，要切换的PDU会话列表与N2 SM信息，未能建立的PDU会话列表，其中包含在N2 SM信息元素中给出的失败原因)。
在NG-RAN N2切换时，目标NG-RAN向SMF提供目标NG-RAN节点是否支持基于PDU set的处理的指示；在切换请求确认消息(NG切换)中提供来自目标NG-RAN的“PDU set支持”指示。
在一些实施例中，源NG-RAN支持基于PDU Set的处理，切换的目标NG-RAN不支持基于PDU Set的处理，其中，对于目标NG-RAN，若接收到转发数据包，例如源NG-RAN直接转发过来的数据包，或UPF间接转发过来的数据包，由于源NG-RAN支持基于PDU Set的处理，所转发的转发数据包中可能包括标记PDU，目标NG-RAN接收到转发数据包之后，可将标记PDU作为未标记PDU进行处理，忽略PDU Set的QoS参数，执行PDUQoS参数，忽略标记PDU的用于标识PDU Set信息的协议扩展头(header extensions))。
在一些实施例中，源NG-RAN不支持基于PDU Set的处理，切换的目标NG-RAN支持基于PDU Set的处理，其中，对于目标NG-RAN，若接收到转发数据包，例如源NG-RAN直接转发过来的数据包，或UPF间接转发过来的数据包，由于源NG-RAN不支持基于PDU Set的处理，所转发的转发数据包中可能包括未标记PDU，目标NG-RAN接收到转发数据包(通过转发隧道接收到的在EndMarker结束数据包之前的数据包)，在未标记PDU的处理结束之前，目标NG-RAN将接收到的标记PDU作为未标记PDU进行处理(这样在同一时间所有PDU均作为未标记PDU处理)，忽略标记PDU的PDU SetQoS参数，使用PDUQoS参数，即忽略用于标识PDU Set信息的协议扩展头)。
并且，在未标记PDU处理结束之后，目标NG-RAN可以根据PDU Set的QoS参数和扩展协议头中的PDU Set信息(或者UPF配置的PDUset信息，以及协议描述中的PDUset信息)处理标记PDU。
在一些实施例中，源NG-RAN不支持基于PDU Set的处理，切换的目标NG-RAN支持基于PDU Set的处理，其中，对于目标NG-RAN，若接收到转发数据包，例如源NG-RAN直接转发过来的数据包，或UPF间接转发过来的数据包，由于源NG-RAN不支持基于PDU Set的处理，所转发的转发数据包中可能包括未标记PDU，目标NG-RAN可以在一个特定窗口内(比如启动一个定时器)，定时器计时期间，目标NG-RAN将接收到的标记PDU作为未标记PDU进行处理，忽略PDU Set的QoS参数，在定时器结束后，目标NG-RAN可以根据PDU Set的QoS参数和扩展协议头中的PDU Set信息处理标记PDU。
在一种可能的实现方式中，目标NG-RAN在接收到结束数据(End Marker)包后启动上述定时器，定时器的时长为继续处理切换窗口时长(该切换过程中的标记PDU作为未标记PDU处理，可以在接收到EndMarker包之前已经开始，收到EndMarker包之后的剩余时间更容易确定)。
在一种可能的实现方式中，目标NG-RAN在接收到SMF发送的PDU Set的QoS参数后启动上述定时器，定时器的时长为继续处理切换窗口时长(该切换过程中的标记PDU作为未标记PDU处理，可以在接收到SMF发送的PDU Set的QoS参数之前已经开始)。
其中，处理切换窗口时长可以大于等于目标NG-RAN(可根据本地配置或OA配置或收到的EndMark包或收到的PDUSet相关QoS参数)设定的定时器启动到未标记PDU处理完成需要的时长。
在一种可能的实现方式中，目标NG-RAN在接收到SMF发送的PDU Set的QoS参数后，可以向SMF发送一个第二指示信息，第二指示信息用于指示目标NG-RAN是否接受(接受或拒绝)已接收到PDU Set的QoS参数，其中，NG-RAN拒绝该PDUSetQoS参数则NG-RANPDUSetQoS处理功能未激活，接受则NG-RANPDUSetQoS处理功能激活。
在一些实施例中，SMF可以请求目标NG-RAN为给定的QoS流激活基于PDU Set的QoS处理，目标NG-RAN可以向SMF提供是否接受(接受或拒绝)接收到的PDU Set的QoS参数的指示。
在一些实施例中，NG-RAN可以向SMF提供是否激活PDU Set的QoS参数的指示，以及延迟应用的时间，或延迟激活的时间(与应用的PDU Set的QoS参数的开始时间(或时间窗口)相关)。该时间可以根据目标NG-RAN中用于处理标记PDU的定时器来确定。
在一些实施例中，SMF根据目标NG-RAN的指示或延迟应用的时间/延迟激活的时间，将PSA UPF配置为激活/或去激活/停用PDU组识别和标记(对PDU数据包进行PDU组相关的识别和扩展协议头标记)。
在要切换的PDU会话列表中的N2 SM信息中，每个PDU会话ID包括T-NG-RAN N3寻址信息，即用于PDU会话的T-NG-RAN的N3 UP地址和隧道ID。
N2 SM信息还可以包括：
-如果PDU会话至少有一个需要进行数据转发的QoS流，则包括T-NG-RAN的N3 UP地址和接收转发数据的T-NG-RAN的隧道ID。T-NG-RAN为其决定设置的每个数据转发隧道提供数据转发地址。
-对于每个使用替代QoS配置文件接受的QoS流，目标NG-RAN应包括对已满足替代QoS配置文件的引用。
11a-f、T-AMF与T-NG-RAN，S-UPF，T-UPF通过SMF交换隧道信息。直接转发时执行11a和11f，间接转发时，执行中间过程交换通道信息。
11a、T-AMF到SMF：Nsmf_PDUSession_UpdateSMContext请求(PDU会话标识，步骤10中从T-NG-RAN接收到的N2 SM响应)。
对于从T-NG-RAN接收到的每个N2 SM响应(包含在切换请求确认中的N2 SM信息)，T-AMF将接收到的N2 SM响应发送到相应的PDU会话ID所指示的SMF。
如果没有选择新的T-UPF，SMF会在T-NG-RAN接受N2切换的情况下，存储N2 SM响应中T-NG-RAN的N3隧道信息。
SMF/UPF为由T-NG-RAN建立的数据转发隧道端点分配N3 UP地址和隧道ID，以便进行间接数据转发。
11f、SMF到T-AMF:Nsmf_PDUSession_UpdateSMContext响应(N2 SM信息)。
SMF向T-AMF发送每个PDU会话的Nsmf_PDUSession_UpdateSMContext响应消息。
根据NG-RAN的指示和/或激活时间，SMF配置PSA UPF以激活/停用PDU Set标识和标记。
在PSA UPF在GTP-U头中识别和标记带有PDU Set信息的PDU的情况下，它应从一个完整的PDU集开始这样做。(此外，如果源NG-RAN发送的话，在End Marker数据包后的PDU不是一个完整的PDU集的开始，则会重叠一部分已发送的PDU执行PDU Set封装)。PSA UPF在GTP-U头中识别和标记带有PDU Set信息的PDU，应从一个完整的PDU集开始这样做。第一个PDU集将包括与通过源转发隧道发送的数据包重叠的PDU，如果在一个完整的PDU集结束时没有发送结束标记数据包。
SMF创建包含DL转发隧道信息的N2 SM信息，以便由AMF发送给S-NG-RAN。SMF将此信息包含在Nsmf_PDUSession_UpdateSMContext响应中。DL转发隧道信息可以是以下信息之一：(SMF下发会话更新响应消息，下行转发信息携带，包括直接和间接。)
如果应用直接转发，则SMF会包含步骤11a中收到的T-NG-RAN N3转发信息。
如果在步骤11b或11d中设置了间接转发隧道，则SMF会包含包含T-UPF或S-UPF的DL转发信息，其中包括UPF的N3 UP地址和DL隧道ID。
12、步骤3的响应消息，T-AMF到S-AMF：Namf_Communication_CreateUEContext响应(包括S-AMF向S-NG-RAN发送切换指令所需的N2信息，包括目标到源透明容器、未能建立的PDU会话列表、N2 SM信息(N3下行转发信息、PCF ID)、[目标AMF ID])。
目标到源传输容器由T-NG-RAN接收。N2 SM信息由步骤11f中的SMF接收。
如图4B所示，执行阶段：
经过上述准备阶段后，
1、S-AMF向S-NG-RAN发起切换命令，通知切换准备完成，执行切换。携带从S-NG-RAN获取的所有切换会话信息及各会话的N2 SM信息，以及直接转发时T-NG-RAN N3转发隧道信息或者间接转发时S-UPF N3转发隧道信息。
2至15b、S-NG-RAN,T-NG-RAN,SMF及PSA UPF的增强处理，以及UPF结束数据(End Marker)包处理。
其中，10a和10b、转发数据完成后，PSA UPF在切换路径完成后，发送结束数据包(End Marker packets)给S-NG-RAN，转发给T-NG-RAN。或者通过间接转发的T-UPF将End Marker packets转发给T-NG-RAN。
在一些实施例中，PSA UPF在完整的PDU set结束时向目标NG-RAN发送结束标记数据包(End Marker packets)。或者说，PSA UPF从一个完整的PDU set的最初(比如第一个数据包)开始执行PDUset的识别和扩展协议头标记，在一个完整的PDU的结束(比如最后一个数据包)停止或结束执行PDUset的识别和扩展协议头标记(End Marker packets就在PDUset的最后一个数据包之后发送)。
或者，PSA UPF识别和标记带有PDU Set信息的PDU(比如识别带有RTP或RTCP扩展协议头的PDU，将其中带有PDUSet信息的协议扩展头映射为GTP-U协议扩展头，将PDUSet信息在GTP-U扩展协议头中携带给NG-RAN)。它从一个完整的PDU set开始这样做。第一个PDU set包括与通过源转发隧道发送的数据包重叠的PDU(这里重叠的数据包已经在源通道发送，但不是一个PDUset的结束，比如Set的前半部分，则将这部分和未发送的后半部分一起作为一个完整的PDUset，在新通道中发送)，如果结束标记数据包不是发送在一个完整的PDU set结束时(比如发送在PDUSet中间)。
或者，PSA UPF识别和标记带有PDU Set信息的PDU(比如识别带有RTP或RTCP扩展协议头的PDU，将其中带有PDUSet信息的协议扩展头映射为GTP-U协议扩展头，将PDUSet信息在GTP-U扩展协议头中携带给NG-RAN)。它将通过源转发隧道发送的PDU set的剩余数据包，作为单个数据包分别发送。然后，它从一个完整的PDU set开始，进行数据包的识别和标记PDUset信息到扩展协议头，如果结束标记数据包不是发送在一个完整的PDU set结束时(比如发送在PDUSet中间)。
在一些实施例中，源NG-RAN节点从UPF接收每个PDU会话的一个或多个GTP-U结束标记数据包，并在不再需要在该隧道上转发用户数据包时，将结束标记数据包复制到每个数据转发隧道中。
通过数据转发隧道发送的结束标记数据包适用于通过该隧道转发的所有QoS流。在结束标记数据包已经通过一个转发隧道接收后，目标NG-RAN节点可以开始考虑从NG-U PDU会话隧道接收到的与该转发隧道相关的QoS流的数据包。
为方便理解本公开实施例，提供如下示例性实施例。
5GS系统支持的QoS处理，同一个QoS flow中要么支持基于PDU的QoS规则和参数策略，要么支持基于PDU set的QoS规则和参数策略。即一个QoS flow中同时激活处理的QoS参数只有一套，为基于PDU的QoS机制，或基于PDU set的QoS机制。
而实际网络中，存在各类功能支持差异的NG-RAN(Non-homogenous support)。比如不支持PDU set处理的NG-RAN，和支持PDU set处理的NG-RAN。由于XR的业务连续性需求，在切换(Handover)流程中(例如终端移动性)，需要对下行数据执行数据转发(Data forwarding)。(Data forwarding支持直接和间接模式，直接模式中，源(Source)NG-RAN转发到目标(target)NG-RAN，间接模式中，由UPF执行data forwarding给target-NG-RAN。需要说明的是，在间接模式中，执行数据转发的UPF不一定是源NG-RAN对应的UPF。
其中，当切换(Handover，HO)发生在不支持PDU set处理的NG-RAN和支持PDU set处理的NG-RAN之间时，尤其是从不支持PDU set处理的源(source)NG-RAN切换到支持PDU set处理的目标(Target)NG-RAN，同一个QoS流中会同时存在未标记(unmarked)PDUs和标记(marked)PDUs。
但是，5GS系统不支持同一个QoS流中同时存在未标记(unmarked)PDUs和标记(marked)PDUs的场景，无法保障相应QoS流的QoS。
如何处理QoS流中未标记(unmarked)PDUs和标记(marked)PDUs共存的问题，是5GS保障云游戏等XR交互类业务必须要解决的问题。
本公开实施例中，NG-RAN不同时支持同一个QoS流中的标记PDUs和未标记PDUs的混合处理(同一时间只处理一种PDU格式，只执行一种PDU格式对应的QoS参数。将标记协议扩展头忽略作为未标记PDU处理，按PDUQoS参数。或者相反。或者将未处理完的带标记协议扩展头的PDU丢掉。或者，通过SMF延迟激活PDU Set QoS处理功能，或激活但延迟应用PDU Set QoS处理功能，来将两种PDU错开时间处理，这样NG-RAN中同一时间只会收到同一种PDU，不会存在标记和未标记PDU的混合状态，而不需要NG-RAN做特殊处理)。NG-RAN根据SMF的通知指示执行相应的处理，以解决上述问题。
在一些实施例中，SMF通知T-NG-RAN的指示处理，包括以下一种或多种方式：
1)SMF携带PDU set激活定时器(timer)给T-NG-RAN；T-NG-RAN在Timer超时前，对收到 的标记PDU作为非标记PDU处理，忽略携带有PDU set信息的增强头信息；
2)SMF携带优先指示(Priority indication)给T-NG-RAN；
其中优先指示可以指示以下至少一项：
-收到标记PDU后优先执行基于PDU set的处理
-收到标记PDU后优先执行非标记PDU的处理(忽略头增强携带的PDU set信息)；
-收到标记PDU后优先基于T-NG-RAN本地配置自行执行；
-收到标记PDU后优先根据OAM配置执行；
其中，T-NG-RAN基于收到的优先指示执行相应的处理方法。
进一步地，优先指示信息还可能包括优先列表，优先列表中包括不同优先指示的内容以及不同优先指示的内容分别对应的优先级(由此，不同能力的NGRAN可以结合本地配置或OAM配置结合优先列表来综合执行)。
3)收到T-NG-RAN发送的支持基于PDU set的处理的指示后，SMF延时发起PDU会话修改(或者发起会话修改，但指示修改后的新QoS参数以及识别标记包的新处理按指示的时间或时间窗延时执行或延时应用)；
在一些实施例中，SMF可以携带PDU set QoS参数给UPF和NG-RAN，激活基于PDU set的QoS处理。
在一些实施例中，SMF通知UPF执行延时PDU Set识别和标记；其中SMF可根据本地配置或OAM配置或NG-RAN通知信息来确定延时时间；SMF可设置PDU set激活定时器(timer)，timer超时后发起PDU会话修改，激活PDU set的QoS处理；或者SMF通知UPF延时执行PDU set QoS以及PDU识别和标记，UPF基于本地转发数据(data forwarding)/结束数据包(End marker packets)/时间/本地配置/OAM配置确定延时时间，延时执行PDU set QoS以及PDU识别和标记。UPF和NG-RAN按SMF通知执行，包括激活PDU set QoS处理，和/或执行延时PDU Set识别和标记。
在一些实施例中，经过以上的SMF延迟激活会话修改和QoS参数更新，或者激活和更新后延迟应用，将两种PDU(标记和未标记PDU)到达NG-RAN的时间错开了，这样NG-RAN同一时间只会收到同一种PDU，不会存在标记和未标记PDU的混合状态，而不需要NG-RAN做特殊处理，或者尽可能错开了两种PDU(标记和未标记PDU)到达NG-RAN的时间，少量混合存在的PDU，可以根据QoS参数将不匹配的PDU丢弃，或按功能忽略协议增强头处理。
在一些实施例中，PSA UPF在完整的PDU set结束时向目标NG-RAN发送结束标记数据包(End Marker packets)。或者说，PSA UPF从一个完整的PDU set的最初(比如第一个数据包)开始执行PDUset的识别和扩展协议头标记，在一个完整的PDU的结束(比如最后一个数据包)停止或结束执行PDUset的识别和扩展协议头标记(End Marker packets就在PDUset的最后一个数据包之后发送)。
或者，PSA UPF识别和标记带有PDU Set信息的PDU(比如识别带有RTP或RTCP扩展协议头的PDU，将其中带有PDUSet信息的协议扩展头映射为GTP-U协议扩展头，将PDUSet信息在GTP-U扩展协议头中携带给NG-RAN)。它从一个完整的PDU set开始这样做。第一个PDU set包括与通过源转发隧道发送的数据包重叠的PDU(这里重叠的数据包已经在源通道发送，但不是一个PDUset的结束，比如Set的前半部分，则将这部分和未发送的后半部分一起作为一个完整的PDUset，在新通道中发送)，如果结束标记数据包不是发送在一个完整的PDU set结束时(比如发送在PDUSet中间)。
或者，PSA UPF识别和标记带有PDU Set信息的PDU(比如识别带有RTP或RTCP扩展协议头的PDU，将其中带有PDUSet信息的协议扩展头映射为GTP-U协议扩展头，将PDUSet信息在GTP-U扩展协议头中携带给NG-RAN)。它将通过源转发隧道发送的PDU set的剩余数据包，作为单个数据包分别发送。然后，它从一个完整的PDU set开始，进行数据包的识别和标记PDUset信息到扩展协议头，如果结束标记数据包不是发送在一个完整的PDU set结束时(比如发送在PDUSet中间)。
示例性实施例中，如图3所示。以源(Source)NG-RAN切换至目标(Target)NG-RAN，AMF未更改，且SMF决定保留现有的UPF，并通过Xn将终端从源NG-RAN切换至目标NG-RAN的情况为例进行说明。
1a、如果PLMN已配置辅助RAT使用报告，源NG-RAN节点在切换执行阶段可能会向AMF提供RAN使用数据报告(N2 SM信息(辅助RAT使用数据)、切换标志、源到目标透明容器)。源NG-RAN节点只有在目标NG-RAN通过Xn接口确认切换后才会提供此报告。切换标志向AMF指示它应在转发之前缓冲包含使用数据报告的N2 SM信息。
1b、目标NG-RAN到AMF：N2路径切换请求(待切换的PDU会话列表与N2 SM信息，未能建立的PDU会话列表，其中的失败原因在N2 SM信息元素中给出，UE位置信息)。
目标NG-RAN向AMF发送N2路径切换请求消息，通知UE已经移动到一个新的目标小区，并提供待切换的PDU会话列表。每个待切换的PDU会话的AN隧道信息包含在N2 SM信息中。
对于要切换到目标NG-RAN的PDU会话，N2路径切换请求消息应包括接受的QoS流列表。对于每个接受了替代QoS配置文件的QoS流，N2 SM信息应包含对已满足替代QoS配置文件的引用。
在一些实施例中，在NG-RAN的Xn切换中，目标NG-RAN向SMF提供一个指示，表明目标NG-RAN节点是否支持基于PDU Set的处理；来自目标NG-RAN的"PDU set是否支持"指示将包含在路径切换请求消息(Xn切换)中。
2、AMF向SMF发送Nsmf_PDUSession_UpdateSMContext请求(从步骤1b中收到的T-NG-RAN的N2 SM信息和来自源NG-RAN的N2 SM信息(辅助RAT使用数据)、UE位置信息、UE在LADN服务区域的存在情况)。这里来自源NG-RAN的N2 SM信息是在适用的情况下在步骤1a中缓冲的。
AMF通过调用Nsmf_PDUSession_UpdateSMContext请求服务操作，为N2路径切换请求中接收到的每个PDU会话发送N2 SM信息。这些PDU会话列表是在N2路径切换请求中接收的。包括步骤1中的，目标NG-RAN向SMF提供一个指示，表明目标NG-RAN节点是否支持基于PDU Set的处理；来自目标NG-RAN的“PDU set support”指示将包含在路径切换请求消息(Xn切换)中。
Nsmf_PDUSession_UpdateSMContext请求包含以下内容之一：指示PDU会话将被切换(以及有关要使用的N3寻址和已传输的QoS流的信息)，或者指示PDU会话将被拒绝(以及拒绝原因)。
如果一些PDU会话的QoS流未被目标NG-RAN接受，SMF将在切换过程完成后启动PDU会话修改过程，从PDU会话中移除未被接受的QoS流。
3、SMF到UPF：N4会话修改请求(AN隧道信息)
对于由目标NG-RAN修改的PDU会话，SMF向UPF发送一个N4会话修改请求消息。SMF可以通知原始发起数据通知的UPF丢弃PDU会话的下行数据和/或不再提供进一步的数据通知消息。
根据网络部署情况，用于连接到目标NG-RAN和连接到源NG-RAN的UPF的CN隧道信息可能会不同，例如由于源NG-RAN和目标NG-RAN位于不同的IP域。在这种情况下，SMF可以要求UPF分配新的CN隧道信息，并提供目标网络实例。
4、UPF到SMF：N4会话修改响应(CN隧道信息)
对于已切换的PDU会话，UPF在请求的PDU会话完成切换后向SMF返回N4会话修改响应消息。仅为未释放用户面资源且由SMF请求的PDU会话包括UL流量的隧道标识符。
5、为了帮助目标NG-RAN中的重排序功能，UPF在切换路径后立即为旧路径上的每个N3隧道发送一个或多个“结束标记”数据包。UPF开始将下行数据包发送到目标NG-RAN。
在一些实施例中，PSA UPF在完整的PDU set结束时向目标NG-RAN发送结束标记数据包(End Marker packets)。或者说，PSA UPF从一个完整的PDU set的最初(比如第一个数据包)开始执行PDUset的识别和扩展协议头标记，在一个完整的PDU的结束(比如最后一个数据包)停止或结束执行PDUset的识别和扩展协议头标记(End Marker packets就在PDUset的最后一个数据包之后发送)。
或者，PSA UPF识别和标记带有PDU Set信息的PDU(比如识别带有RTP或RTCP扩展协议头的PDU，将其中带有PDUSet信息的协议扩展头映射为GTP-U协议扩展头，将PDUSet信息在GTP-U扩展协议头中携带给NG-RAN)。它从一个完整的PDU set开始这样做。第一个PDU set包括与通过源转发隧道发送的数据包重叠的PDU(这里重叠的数据包已经在源通道发送，但不是一个PDUset的结束，比如Set的前半部分，则将这部分和未发送的后半部分一起作为一个完整的PDUset，在新通道中发送)，如果结束标记数据包不是发送在一个完整的PDU set结束时(比如发送在PDUSet中间)。
或者，PSA UPF识别和标记带有PDU Set信息的PDU(比如识别带有RTP或RTCP扩展协议头的PDU，将其中带有PDUSet信息的协议扩展头映射为GTP-U协议扩展头，将PDUSet信息在GTP-U扩展协议头中携带给NG-RAN)。它将通过源转发隧道发送的PDU set的剩余数据包，作为单个数据包分别发送。然后，它从一个完整的PDU set开始，进行数据包的识别和标记PDUset信息到扩展协议头，如果结束标记数据包不是发送在一个完整的PDU set结束时(比如发送在PDUSet中间)。
基于NG-RAN的指示和/或激活时间，SMF配置PSA UPF来激活/停用PDU Set标识和标记。
对于PSA UPF在GTP-U头中识别和标记带有PDU Set信息的PDU的情况，它应从一个完整的PDU集开始这样做。(此外，如果源NG-RAN发送的话，在End Marker数据包后的PDU不是一个完整的PDU集的开始，则会重叠一部分已发送的PDU执行PDU Set封装)。PSA UPF在GTP-U头中识别和标记带有PDU Set信息的PDU，应从一个完整的PDU集开始。第一个PDU集将包括与通过源转发隧道发送的数据包重叠的PDU，如果在一个完整的PDU集结束时没有发送结束标记数据包。
6、SMF向AMF发送Nsmf_PDUSession_UpdateSMContext响应(N2 SM信息)
SMF向已成功切换的PDU会话发送一个Nsmf_PDUSession_UpdateSMContext响应(N2 SM信息(CN隧道信息，接受的QoS流的更新CN PDB，接受的QoS流的更新TSCAI))。UPF发送给AMF的CN隧道信息用于设置N3隧道。对于每个接受的延迟关键资源类型的GBR QoS流，SMF可能会更新动态CN PDB和TSCAI，并将其发送到目标NG-RAN。SMF可以根据本地配置在响应中更新CN PDB和TSCAI，也可以使用单独的PDU会话修改过程进行更新。
注意：步骤6可以在SMF收到N4会话修改响应后的任何时间发生。
本公开实施例中，NG-RAN不同时支持同一个QoS流中的标记PDUs和未标记PDUs的混合处理(同一时间只处理一种PDU格式，只执行一种PDU格式对应的QoS参数。将标记协议扩展头忽略作为未标记PDU处理，按PDUQoS参数。或者相反。或者将未处理完的带标记协议扩展头的PDU丢掉。或者，通过SMF延迟激活PDU Set QoS处理功能，或激活但延迟应用PDU Set QoS处理功能，来将两种PDU错开时间处理，这样NG-RAN中同一时间只会收到同一种PDU，不会存在标记和未标记PDU的混合状态，而不需要NG-RAN做特殊处理)。NG-RAN根据SMF的通知指示执行相应的处理，以解决上述问题。
在一些实施例中，SMF通知T-NG-RAN的指示处理，包括以下一种或多种方式：
1)SMF携带PDU set激活定时器(timer)给T-NG-RAN；T-NG-RAN在Timer超时前，对收到的标记PDU作为非标记PDU处理，忽略携带有PDU set信息的增强头信息；
2)SMF携带优先指示(Priority indication)给T-NG-RAN；
其中优先指示可以指示以下至少一项：
-收到标记PDU后优先执行基于PDU set的处理
-收到标记PDU后优先执行非标记PDU的处理(忽略头增强携带的PDU set信息)；
-收到标记PDU后优先基于T-NG-RAN本地配置自行执行；
-收到标记PDU后优先根据OAM配置执行；
其中，T-NG-RAN基于收到的优先指示执行相应的处理方法。
进一步地，优先指示信息还可能包括优先列表，优先列表中包括不同优先指示的内容以及不同优先指示的内容分别对应的优先级(由此，不同能力的NGRAN可以结合本地配置或OAM配置结合优先列表来综合执行)。
3)收到T-NG-RAN发送的支持基于PDU set的处理的指示后，SMF延时发起PDU会话修改(或者发起会话修改，但指示修改后的新QoS参数以及识别标记包的新处理按指示的时间或时间窗延时执行或延时应用)；
在一些实施例中，SMF可以携带PDU set QoS参数给UPF和NG-RAN，激活基于PDU set的QoS处理。
在一些实施例中，SMF通知UPF执行延时PDU Set识别和标记；其中SMF可根据本地配置或OAM配置或NG-RAN通知信息来确定延时时间；SMF可设置PDU set激活定时器(timer)，timer超时后发起PDU会话修改，激活PDU set的QoS处理；或者SMF通知UPF延时执行PDU set QoS以及PDU识别和标记，UPF基于本地转发数据(data forwarding)/结束数据包(End marker packets)/时间/本地配置/OAM配置确定延时时间，延时执行PDU set QoS以及PDU识别和标记。UPF和NG-RAN按SMF通知执行，包括激活PDU set QoS处理，和/或执行延时PDU Set识别和标记。
在一些实施例中，经过以上的SMF延迟激活会话修改和QoS参数更新，或者激活和更新后延迟应用，将两种PDU(标记和未标记PDU)到达NG-RAN的时间错开了，这样NG-RAN同一时间只会收到同一种PDU，不会存在标记和未标记PDU的混合状态，而不需要NG-RAN做特殊处理，或者尽可能错开了两种PDU(标记和未标记PDU)到达NG-RAN的时间，少量混合存在的PDU，可以根据QoS参数将不匹配的PDU丢弃，或按功能忽略协议增强头处理。
对于XR业务流，SMF在该消息中携带相应PDU set QoS参数以及流描述等信息，给目标NG-RAN。或者SMF后续单独发起一个PDU session会话修改流程，携带更新后的PDU set QoS参数及流描述等信息。
如果源NG-RAN不支持替代QoS配置文件而目标NG-RAN支持它们，SMF会在每个QoS流的基础上向目标NG-RAN发送可用的替代QoS配置文件。
7、AMF到NG-RAN：N2路径切换请求确认(N2 SM信息，未成功的PDU会话，UE无线能力标识)。
8、通过向源NG-RAN发送释放资源消息，目标NG-RAN确认切换成功。然后，目标NG-RAN触发与源NG-RAN的资源释放。
9、如果注册流程的触发条件之一适用，终端可以启动移动性注册更新过程。
示例性实施例中，如图4A和图4B所示，源NG-RAN的N2接口的非Xn切换到目标NG-RAN，包括如图4A所示的准备阶段和图4B所示的执行阶段。以源NG-RAN为S-NG-RAN、源AMF为S-AMF、源UPF为S-UPF、目标NG-RAN为T-NG-RAN、目标AMF为T-AMF、目标UPF为T-UPF为例进行说明。
准备阶段中，步骤10中携带T-NG-RAN的PUD set支持的指示给SMF。
如图4A所示，准备阶段：
1、S-NG-RAN向S-AMF发送切换要求(目标ID，源到目标的透明容器，SM N2信息列表，PDU会话ID，系统内切换指示)。
源到目标的透明容器包括由S-NG-RAN创建的NG-RAN信息，用于由T-NG-RAN使用，并对5GC透明。对于每个PDU会话，它还包含相应的QoS流/DRB信息，这些信息将受到数据转发的影响。
2-7选择新的AMF、UPF，获取新的UPF隧道信息。
7、SMF到T-AMF：Nsmf_PDUSession_UpdateSMContext响应(PDU会话标识，N2 SM信息，未接受的原因)。
如果PDU会话的N2切换被接受，SMF会在Nsmf_PDUSession_UpdateSMContext响应中包括N2 SM信息，其中包含了UPF的N3 UP地址和UL CN隧道ID、QoS参数、TSCAI以及目标NG-RAN的用户平面安全执行信息。
8、T-AMF监督来自涉及的SMF的Nsmf_PDUSession_UpdateSMContext响应消息。
9、T-AMF到T-NG-RAN：切换请求(源到目标透明容器，N2MM信息，N2 SM信息列表，追踪要求，终端无线能力标识)。T-AMF根据目标标识确定T-NG-RAN。T-AMF可能为终端在T-AMF和目标TAI中分配一个有效的5G-GUTI。
源到目标透明容器按照从S-NG-RAN接收的方式进行转发。N2MM信息包括安全信息和移动限制列表(如果在T-AMF中可用)。
N2 SM信息列表包括从SMF接收的N2 SM信息，这些信息在允许的最大延迟内通过T-AMF在步骤8中监督的Nsmf_PDUSession_UpdateSMContext响应消息中接收，这些消息是为T-NG-RAN准备的。
10、T-NG-RAN到T-AMF：切换请求确认(目标到源透明容器，要切换的PDU会话列表与N2 SM信息，未能建立的PDU会话列表，其中包含在N2 SM信息元素中给出的失败原因)。
在NG-RAN N2切换时，T-NG-RAN向SMF提供T-NG-RAN节点是否支持基于PDUset的处理的指示；在切换请求确认消息(NG切换)中提供来自T-NG-RAN的“PDU set支持”指示。(步骤10消息)。
在“待切换的PDU会话列表”中的N2 SM信息中，包含了每个PDU会话的T-NG-RAN N3寻址信息，即PDU会话的N3 UP地址和T-NG-RAN的隧道ID。
N2 SM信息还可以包括：
-如果PDU会话至少有一个需要进行数据转发的QoS流，则包括用于接收转发数据的T-NG-RAN的N3 UP地址和隧道ID。T-NG-RAN为每个决定设置的数据转发隧道提供数据转发地址。
-对于每个采用替代QoS配置的QoS流，T-NG-RAN应该包括对已满足替代QoS配置的引用。
11a-f、T-AMF与T-NG-RAN，S-UPF，T-UPF通过SMF交换隧道信息。直接转发时执行11a和11f，间接转发时，执行中间过程交换通道信息。
11a、T-AMF到SMF：Nsmf_PDUSession_UpdateSMContext请求(PDU会话标识，步骤10中从T-NG-RAN接收到的N2 SM响应)。
对于从T-NG-RAN接收到的每个N2 SM响应(包含在切换请求确认中的N2 SM信息)，T-AMF将接收到的N2 SM响应发送到相应的PDU会话ID所指示的SMF。
如果没有选择新的T-UPF，SMF会在T-NG-RAN接受N2切换的情况下，存储N2 SM响应中T-NG-RAN的N3隧道信息。
SMF/UPF为间接数据转发分配N3 UP地址和隧道ID，以对应于T-NG-RAN建立的数据转发隧道端点。
11f、SMF到T-AMF:Nsmf_PDUSession_UpdateSMContext响应(N2 SM信息)。
SMF向T-AMF发送Nsmf_PDUSession_UpdateSMContext响应消息，每个PDU会话一个。
SMF会创建一个包含下行(DL)转发隧道信息的N2 SM信息，以便由AMF发送给S-NG-RAN。SMF将此信息包含在Nsmf_PDUSession_UpdateSMContext响应消息中。下行转发隧道信息可以是以 下之一：(SMF下发会话更新响应消息，下行转发信息携带，包括直接和间接。)
-如果应用直接转发，则SMF将包括在步骤11a中接收到的T-RNG-AN N3转发信息。
-如果在步骤11b或11d中设置了间接转发隧道，则SMF将包括T-UPF或S-UPF的DL转发信息，其中包含N3 UP地址和UPF的DL隧道ID。
12、步骤3的响应消息.T-AMF到S-AMF:Namf_Communication_CreateUEContext响应(S-AMF向S-NG-RAN发送切换命令所需的N2信息，包括目标到源透明容器、PDU会话设置失败列表、N2 SM信息(N3DL转发信息、PCF ID)、[T-AMF ID])。
其中，目标到源透明容器：这个容器是从T-NG-RAN接收的，用于支持向S-NG-RAN发送Handover Command的操作。它包含了NG-RAN信息，由S-NG-RAN创建用于T-NG-RAN的，对5GC来说是透明的。它还包括每个PDU会话的相应QoS流/DRB信息，以支持数据转发。
PDU会话设置失败列表：列出了在切换过程中无法建立的PDU会话，以及给出的失败原因。
N2 SM Information(N3下行转发信息、PCF ID)：这些信息是从步骤11f中的SMF接收到的。N3下行转发信息指的是N2 SM信息中包含的目标T-NG-RAN的下行转发隧道信息，包括N3 UP地址和下行隧道ID。PCF ID是策略控制功能的标识，表示策略控制功能的ID。
目标AMF ID：如果需要，可能会包含目标AMF的标识。
T-AMF到S-AMF:Namf_Communication_CreateUEContext响应，提供了发送切换命令所需的各种信息，以支持从S-AMF到S-NG-RAN的切换过程。
从T-NG-RAN接收目标到源传输容器。在步骤11f中，从SMF接收N2 SM信息。
如图4B所示，执行阶段：
经过上述准备阶段后，
1、S-AMF向S-NG-RAN发起切换命令，通知切换准备完成，执行切换。携带从S-NG-RAN获取的所有切换会话信息及各会话的N2 SM信息，以及直接转发时T-NG-RAN N3转发隧道信息或者间接转发时S-UPF N3转发隧道信息。
2至15b、S-NG-RAN,T-NG-RAN,SMF及PSA UPF的增强处理，以及UPF结束数据(End Marker)包处理。主要SMF通知指示的增强，可在步骤10、11、15执行，或单独发起会话修改流程执行。
其中，10a和10b、转发数据完成后，PSA UPF在切换路径完成后，发送结束数据包(End Marker packets)给S-NG-RAN，转发给T-NG-RAN。或者通过间接转发的T-UPF将End Marker packets转发给T-NG-RAN。
在一些实施例中，PSA UPF在完整的PDU set结束时向目标NG-RAN发送结束标记数据包(End Marker packets)。或者说，PSA UPF从一个完整的PDU set的最初(比如第一个数据包)开始执行PDUset的识别和扩展协议头标记，在一个完整的PDU的结束(比如最后一个数据包)停止或结束执行PDUset的识别和扩展协议头标记(End Marker packets就在PDUset的最后一个数据包之后发送)。
或者，PSA UPF识别和标记带有PDU Set信息的PDU(比如识别带有RTP或RTCP扩展协议头的PDU，将其中带有PDUSet信息的协议扩展头映射为GTP-U协议扩展头，将PDUSet信息在GTP-U扩展协议头中携带给NG-RAN)。它从一个完整的PDU set开始这样做。第一个PDU set包括与通过源转发隧道发送的数据包重叠的PDU(这里重叠的数据包已经在源通道发送，但不是一个PDUset的结束，比如Set的前半部分，则将这部分和未发送的后半部分一起作为一个完整的PDUset，在新通道中发送)，如果结束标记数据包不是发送在一个完整的PDU set结束时(比如发送在PDUSet中间)。
或者，PSA UPF识别和标记带有PDU Set信息的PDU(比如识别带有RTP或RTCP扩展协议头的PDU，将其中带有PDUSet信息的协议扩展头映射为GTP-U协议扩展头，将PDUSet信息在GTP-U扩展协议头中携带给NG-RAN)。它将通过源转发隧道发送的PDU set的剩余数据包，作为单个数据包分别发送。然后，它从一个完整的PDU set开始，进行数据包的识别和标记PDUset信息到扩展协议头，如果结束标记数据包不是发送在一个完整的PDU set结束时(比如发送在PDUSet中间)。
本公开实施例还提出用于实现以上任一方法的装置，例如，提出一装置，上述装置包括用以实现以上任一方法中终端所执行的各步骤的单元或模块。再如，还提出另一装置，包括用以实现以上任一方法中网络设备(例如接入网设备、核心网功能节点、核心网设备等)所执行的各步骤的单元或模块。
应理解以上装置中各单元或模块的划分仅是一种逻辑功能的划分，在实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。此外，装置中的单元或模块可以以处理器调用软件的形式实现：例如装置包括处理器，处理器与存储器连接，存储器中存储有指令，处理器调用存储 器中存储的指令，以实现以上任一方法或实现上述装置各单元或模块的功能，其中处理器例如为通用处理器，例如中央处理单元(Central Processing Unit，CPU)或微处理器，存储器为装置内的存储器或装置外的存储器。或者，装置中的单元或模块可以以硬件电路的形式实现，可以通过对硬件电路的设计实现部分或全部单元或模块的功能，上述硬件电路可以理解为一个或多个处理器；例如，在一种实现中，上述硬件电路为专用集成电路(application-specific integrated circuit，ASIC)，通过对电路内元件逻辑关系的设计，实现以上部分或全部单元或模块的功能；再如，在另一种实现中，上述硬件电路为可以通过可编程逻辑器件(programmable logic device，PLD)实现，以现场可编程门阵列(Field Programmable Gate Array，FPGA)为例，其可以包括大量逻辑门电路，通过配置文件来配置逻辑门电路之间的连接关系，从而实现以上部分或全部单元或模块的功能。以上装置的所有单元或模块可以全部通过处理器调用软件的形式实现，或全部通过硬件电路的形式实现，或部分通过处理器调用软件的形式实现，剩余部分通过硬件电路的形式实现。
在本公开实施例中，处理器是具有信号处理能力的电路，在一种实现中，处理器可以是具有指令读取与运行能力的电路，例如中央处理单元(Central Processing Unit，CPU)、微处理器、图形处理器(graphics processing unit，GPU)(可以理解为微处理器)、或数字信号处理器(digital signal processor，DSP)等；在另一种实现中，处理器可以通过硬件电路的逻辑关系实现一定功能，上述硬件电路的逻辑关系是固定的或可以重构的，例如处理器为专用集成电路(application-specific integrated circuit，ASIC)或可编程逻辑器件(programmable logic device，PLD)实现的硬件电路,例如FPGA。在可重构的硬件电路中，处理器加载配置文档，实现硬件电路配置的过程，可以理解为处理器加载指令，以实现以上部分或全部单元或模块的功能的过程。此外，还可以是针对人工智能设计的硬件电路，其可以理解为ASIC，例如神经网络处理单元(Neural Network Processing Unit，NPU)、张量处理单元(Tensor Processing Unit，TPU)、深度学习处理单元(Deep learning Processing Unit，DPU)等。
图5A是本公开实施例提出的通信设备8100的结构示意图。通信设备8100可以是网络设备(例如接入网设备、核心网设备等)，也可以是终端(例如用户设备等)，也可以是支持网络设备实现以上任一方法的芯片、芯片系统、或处理器等，还可以是支持终端实现以上任一方法的芯片、芯片系统、或处理器等。通信设备8100可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
如图5A所示，通信设备8100包括一个或多个处理器8101。处理器8101可以是通用处理器或者专用处理器等，例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行程序，处理程序的数据。可选地，通信设备8100用于执行以上任一方法。可选地，一个或多个处理器8101用于调用指令以使得通信设备8100执行以上任一方法。
在一些实施例中，通信设备8100还包括一个或多个收发器8102。在通信设备8100包括一个或多个收发器8102时，收发器8102执行上述方法中的发送和/或接收等通信步骤中的至少一者，处理器8101执行其他步骤中的至少一者。在可选的实施例中，收发器可以包括接收器和/或发送器，接收器和发送器可以是分离的，也可以集成在一起。可选地，收发器、收发单元、收发机、收发电路、接口电路、接口等术语可以相互替换，发送器、发送单元、发送机、发送电路等术语可以相互替换，接收器、接收单元、接收机、接收电路等术语可以相互替换。
在一些实施例中，通信设备8100还包括用于存储数据的一个或多个存储器8103。可选地，全部或部分存储器8103也可以处于通信设备8100之外。在可选的实施例中，通信设备8100可以包括一个或多个接口电路8104。可选地，接口电路8104与存储器8102连接，接口电路8104可用于从存储器8102或其他装置接收数据，可用于向存储器8102或其他装置发送数据。例如，接口电路8104可读取存储器8102中存储的数据，并将该数据发送给处理器8101。
以上实施例描述中的通信设备8100可以是网络设备或者终端，但本公开中描述的通信设备8100的范围并不限于此，通信设备8100的结构可以不受图5A的限制。通信设备可以是独立的设备或者可以是较大设备的一部分。例如所述通信设备可以是：1)独立的集成电路IC，或芯片，或，芯片系统或子系统；(2)具有一个或多个IC的集合，可选地，上述IC集合也可以包括用于存储数据，程序的存储部件；(3)ASIC，例如调制解调器(Modem)；(4)可嵌入在其他设备内的模块；(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；(6)其他等等。
图5B是本公开实施例提出的芯片8200的结构示意图。对于通信设备8100可以是芯片或芯片系统的情况，可以参见图5B所示的芯片8200的结构示意图，但不限于此。
芯片8200包括一个或多个处理器8201。芯片8200用于执行以上任一方法。
在一些实施例中，芯片8200还包括一个或多个接口电路8202。可选地，接口电路、接口、收发管脚等术语可以相互替换。在一些实施例中，芯片8200还包括用于存储数据的一个或多个存储器8203。可选地，全部或部分存储器8203可以处于芯片8200之外。可选地，接口电路8202与存储器8203连接，接口电路8202可以用于从存储器8203或其他装置接收数据，接口电路8202可用于向存储器8203或其他装置发送数据。例如，接口电路8202可读取存储器8203中存储的数据，并将该数据发送给处理器8201。
在一些实施例中，接口电路8202执行上述方法中的发送和/或接收等通信步骤中的至少一者。接口电路8202执行上述方法中的发送和/或接收等通信步骤例如是指：接口电路8202执行处理器8201、芯片8200、存储器8203或收发器件之间的数据交互。在一些实施例中，处理器8201执行其他步骤中的至少一者。
虚拟装置、实体装置、芯片等各实施例中所描述的各模块和/或器件可以根据情况任意组合或者分离。可选地，部分或全部步骤也可以由多个模块和/或器件协作执行，此处不做限定。
本公开还提出存储介质，上述存储介质上存储有指令，当上述指令在通信设备8100上运行时，使得通信设备8100执行以上任一方法。可选地，上述存储介质是电子存储介质。可选地，上述存储介质是计算机可读存储介质，但不限于此，其也可以是其他装置可读的存储介质。可选地，上述存储介质可以是非暂时性(non-transitory)存储介质，但不限于此，其也可以是暂时性存储介质。
本公开还提出程序产品，上述程序产品被通信设备8100执行时，使得通信设备8100执行以上任一方法。可选地，上述程序产品是计算机程序产品。
本公开还提出计算机程序，当其在计算机上运行时，使得计算机执行以上任一方法。

Claims (10)

  1. 一种业务处理方法，其特征在于，包括：
    第一接入网设备向第一网元发送第一指示信息，其中，所述第一指示信息用于指示第一接入网设备是否支持基于分组数据单元PDU集set的处理。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一接入网设备确定将转发数据包中的标记PDU作为未标记PDU进行处理，其中，所述第一接入网设备不支持基于PDU set的处理，所述转发数据包中包括标记PDU；或者
    所述第一接入网设备确定在未标记PDU处理结束之前，将转发数据包中的标记PDU作为未标记PDU进行处理，其中，所述第一接入网设备支持基于PDU set的处理，所述转发数据包中包括标记PDU。
  3. 如权利要求2所述的方法，其特征在于，所述方法还包括：
    在满足特定条件的情况下，启动定时器；
    在所述定时器计时结束，启动标记PDU的处理，其中，所述定时器的时长为未标记PDU处理的时长。
  4. 如权利要求3所述的方法，其特征在于，所述特定条件，包括以下至少一项：
    接收到结束标记数据包；
    接收到所述第一网元发送的基于PDU set的服务质量QoS参数，并向所述第一网元发送激活响应。
  5. 如权利要求2所述的方法，其特征在于，所述方法还包括：
    所述第一网元向所述第一接入网设备发送激活指示，其中，所述激活指示用于指示所述第一接入网设备激活基于PDU set的处理。
  6. 如权利要求5所述的方法，其特征在于，所述方法还包括：
    所述第一接入网设备向所述第一网元发送激活响应，其中，所述激活响应用于指示以下至少一项：
    基于PDU set的QoS参数是否处于活动状态；
    激活时间；
    延迟激活时间。
  7. 如权利要求2所述的方法，其特征在于，所述方法还包括：
    所述第一接入网设备向所述第一网元发送第二指示信息，其中，所述第二指示信息用于指示未标记PDU处理所需的时长。
    所述第一网元根据所述第二指示信息，确定延迟激活时间；
    所述第一网元在所述延迟激活时间后，向所述第一接入网设备发送激活指示，其中，所述激活指示用于指示所述第一接入网设备激活基于PDU set的处理。
  8. 如权利要求5至7中任一项所述的方法，其特征在于，所述激活指示，包括基于PDU set的QoS参数。
  9. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    第一接入网设备接收第一网元发送的优先指示；
    第一网元根据所述优先指示，执行标记PDU和非标记PDU的处理；
    其中，所述优先指示用于指示以下至少一项：
    收到标记PDU后优先执行基于PDU set的处理；
    收到标记PDU后优先执行非标记PDU的处理；
    收到标记PDU后优先基于所述第一接入网设备的本地配置自行执行；
    收到标记PDU后优先根据操作管理和维护OAM配置执行。
  10. 一种存储介质，所述存储介质存储有指令，其特征在于，当所述指令在通信设备上运行时，使得所述通信设备执行如权利要求1至9中任一项所述的方法。
PCT/CN2023/112777 2023-08-11 2023-08-11 业务处理方法及装置 Pending WO2025035341A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2023/112777 WO2025035341A1 (zh) 2023-08-11 2023-08-11 业务处理方法及装置
CN202380010579.7A CN117322051A (zh) 2023-08-11 2023-08-11 业务处理方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/112777 WO2025035341A1 (zh) 2023-08-11 2023-08-11 业务处理方法及装置

Publications (1)

Publication Number Publication Date
WO2025035341A1 true WO2025035341A1 (zh) 2025-02-20

Family

ID=89250384

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/112777 Pending WO2025035341A1 (zh) 2023-08-11 2023-08-11 业务处理方法及装置

Country Status (2)

Country Link
CN (1) CN117322051A (zh)
WO (1) WO2025035341A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025147828A1 (en) * 2024-01-08 2025-07-17 Zte Corporation Methods, devices, and systems for supporting pdu set based handling in dual connectivity
WO2025147826A1 (en) * 2024-01-08 2025-07-17 Zte Corporation Methods, devices, and systems for supporting pdu set based handling
CN120456111A (zh) * 2024-02-07 2025-08-08 华为技术有限公司 一种通信方法及装置
CN120957194A (zh) * 2024-05-14 2025-11-14 维沃移动通信有限公司 信息处理方法及通信设备
CN121240152A (zh) * 2024-06-30 2025-12-30 华为技术有限公司 信息传输方法及通信装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116250276A (zh) * 2022-12-20 2023-06-09 北京小米移动软件有限公司 QoS管理方法以及装置、通信设备及存储介质
CN116349289A (zh) * 2023-02-10 2023-06-27 北京小米移动软件有限公司 数据处理方法及装置、存储介质
WO2023146584A1 (en) * 2022-01-28 2023-08-03 Qualcomm Incorporated Support for application data unit based quality of service
CN116567730A (zh) * 2022-01-28 2023-08-08 大唐移动通信设备有限公司 一种通信方法及设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023146584A1 (en) * 2022-01-28 2023-08-03 Qualcomm Incorporated Support for application data unit based quality of service
CN116567730A (zh) * 2022-01-28 2023-08-08 大唐移动通信设备有限公司 一种通信方法及设备
CN116250276A (zh) * 2022-12-20 2023-06-09 北京小米移动软件有限公司 QoS管理方法以及装置、通信设备及存储介质
CN116349289A (zh) * 2023-02-10 2023-06-27 北京小米移动软件有限公司 数据处理方法及装置、存储介质

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
LENOVO, TENCENT: "Indication of supporting PDU set handling", 3GPP DRAFT; S2-2305201, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP SA 2, no. Electronic meeting; 20230417 - 20230421, 7 April 2023 (2023-04-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052467383 *
LUO HAIYAN, LENOVO,TENCENT, CATT, XIAOMI, META USA, VODAFONE?: "PDU set handling support indicator", 3GPP DRAFT; S2-2305199; TYPE CR; CR 4522; XRM, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Online; 20230417 - 20230421, 7 April 2023 (2023-04-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052291844 *
QUALCOMM INCORPORATED, GOOGLE, ZTE, LENOVO, META: "PDU Set QoS handling: non-homogenous support (Alternative 2)", 3GPP DRAFT; S2-2308246, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Berlin, Germany; 20230522 - 20230526, 26 May 2023 (2023-05-26), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052382988 *
TENCENT, TENCENT CLOUD: "Update for PDU Set handling support", 3GPP DRAFT; S2-2305148, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP SA 2, no. 20230417 - 20230421, 7 April 2023 (2023-04-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052467331 *

Also Published As

Publication number Publication date
CN117322051A (zh) 2023-12-29

Similar Documents

Publication Publication Date Title
CN114885385B (zh) 一种通信方法及装置
CN109526252B (zh) 无线接入网节点、无线终端、核心网节点及其方法
RU2679417C1 (ru) Способ распространения контекста ключа безопасности, объект управления мобильностью и базовая станция
CN109246747B (zh) 前向接口的建立方法、ue接入方法、ue切换方法及装置
WO2025035341A1 (zh) 业务处理方法及装置
US11937319B2 (en) Integrity protection handling at the gNB-CU-UP
WO2025065618A1 (zh) 业务数据流的处理方法、网络设备、通信设备和存储介质
AU2021308253B2 (en) Communication method and communication apparatus
US20220408317A1 (en) Handover method and communication apparatus
US20230254729A1 (en) Migration method and apparatus for iab-node
WO2025091439A1 (zh) 业务数据流的处理方法、网络设备、通信设备和存储介质
WO2025091436A1 (zh) 通信方法、网元、通信系统和存储介质
WO2024093719A1 (zh) 一种数据传输的方法和装置
WO2024229864A1 (zh) QoS控制方法及装置、通信设备、通信系统、存储介质
CN120434727A (zh) 无线通信方法、终端设备以及网络设备
WO2026081132A1 (zh) 通信方法、通信设备、通信系统、存储介质及程序产品
WO2026081138A1 (zh) 通信方法和装置、通信设备、通信系统及存储介质
WO2025171621A1 (zh) 通信方法和装置、网元、通信系统、存储介质及程序产品
WO2026081134A1 (zh) 通信方法和装置、通信设备、通信系统及存储介质
WO2026073463A1 (zh) 数据传输方法及装置
WO2025091352A1 (zh) 信息处理方法、装置及存储介质
WO2025236258A1 (zh) 通信方法和装置、通信设备、通信系统及存储介质
WO2025065671A1 (zh) 文档更新方法、装置
WO2025065197A1 (zh) 信息传输方法及装置、通信设备、通信系统及存储介质
WO2025179600A1 (zh) 通信方法、通信装置、网络功能和存储介质

Legal Events

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

Ref document number: 23948776

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202617026456

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2023948776

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 202617026456

Country of ref document: IN