WO2023125096A1 - 参数配置方法、通信设备和存储介质 - Google Patents

参数配置方法、通信设备和存储介质 Download PDF

Info

Publication number
WO2023125096A1
WO2023125096A1 PCT/CN2022/139923 CN2022139923W WO2023125096A1 WO 2023125096 A1 WO2023125096 A1 WO 2023125096A1 CN 2022139923 W CN2022139923 W CN 2022139923W WO 2023125096 A1 WO2023125096 A1 WO 2023125096A1
Authority
WO
WIPO (PCT)
Prior art keywords
application layer
layer data
sub
data unit
qos flow
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.)
Ceased
Application number
PCT/CN2022/139923
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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to EP22914350.8A priority Critical patent/EP4451778A4/en
Priority to KR1020247025822A priority patent/KR20240129037A/ko
Priority to JP2024539072A priority patent/JP7827867B2/ja
Publication of WO2023125096A1 publication Critical patent/WO2023125096A1/zh
Priority to US18/757,426 priority patent/US20240373282A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2475—Traffic characterised by specific attributes, e.g. priority or QoS for supporting traffic characterised by the type of applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H04L5/0057—Physical resource allocation for CQI
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/06—Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/327—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the session layer [OSI layer 5]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0205—Traffic management, e.g. flow control or congestion control at the air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information

Definitions

  • the present application relates to the communication field, for example, to a parameter configuration method, a communication device and a storage medium.
  • the quality of service (Quality of Service, QoS) parameters of the business are configured by the core network to the base station through the control plane signaling, which is based on the packet data unit session (Packet Data Unit Session, PDU Session)--->Quality of Service flow (QoS flow) level configuration.
  • a QoS flow has only one QoS priority, and there is no correlation between data packets of different QoS Flows.
  • XR Extended Reality
  • different PDUs have different priorities, and there are dependencies between different PDUs.
  • An embodiment of the present application provides a parameter configuration method applied to a first communication node, including:
  • the frame format of the PDU session includes at least one of the following indication information: application layer data packet identification information, application layer data unit (Application Data Units, ADU) identification information, the sub-flow identifier of the quality of service QoS flow and the sub-priority of the QoS flow.
  • application layer data packet identification information application layer data unit (Application Data Units, ADU) identification information
  • ADU Application Data Units
  • An embodiment of the present application provides a parameter configuration method applied to a third communication node, including:
  • the configuration information includes the sub-flow identifier of the QoS flow or the sub-priority of the QoS flow;
  • the configuration information includes at least one of the following: Service Data Adaptation Protocol (Service Data Adaptation Protocol, SDAP) configuration information, radio bearer configuration information, logical channel configuration information and radio link control configuration information.
  • Service Data Adaptation Protocol Service Data Adaptation Protocol, SDAP
  • An embodiment of the present application provides a parameter configuration method applied to a second communication node, including:
  • the frame format of the PDU session includes at least one of the following indication information: application layer data packet identification information, ADU identification information, sub-flow identification of the QoS flow, and sub-flow identification of the QoS flow subpriority.
  • An embodiment of the present application provides a communication device, including: a communication module, a memory, and one or more processors;
  • the communication module is configured to communicate and interact with other communication nodes
  • the memory configured to store one or more programs
  • the one or more processors When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any of the foregoing embodiments.
  • An embodiment of the present application provides a storage medium, the storage medium stores a computer program, and when the computer program is executed by a processor, the method described in any one of the foregoing embodiments is implemented.
  • Fig. 1 is a configuration relationship diagram between an application layer data unit, an application layer data packet and an Internet Protocol (Internet Protocol, IP) packet provided by an embodiment;
  • IP Internet Protocol
  • FIG. 2 is a schematic configuration diagram of a frame format of a PDU session provided by an embodiment
  • FIG. 3 is a flow chart of a parameter configuration method provided in an embodiment of the present application.
  • Fig. 4 is a flow chart of another parameter configuration method provided by the embodiment of the present application.
  • Fig. 5 is a flow chart of another parameter configuration method provided by the embodiment of the present application.
  • FIG. 6 is a schematic configuration diagram of another frame format of a PDU session provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a configuration of adding a QoS subflow in a QoS flow provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a configuration of adding a QoS sub-flow in another QoS flow provided by an embodiment of the present application.
  • FIG. 9 is a schematic configuration diagram of another frame format of a PDU session provided by an embodiment of the present application.
  • Fig. 10 is a schematic diagram of configuration of a PDU corresponding to the same ADU based on the start of transmission indication provided by the embodiment of the present application;
  • FIG. 11 is a schematic diagram of a configuration of a PDU corresponding to the same ADU based on an end-of-transmission indication provided by an embodiment of the present application;
  • FIG. 12 is a schematic configuration diagram of another frame format of a PDU session provided by an embodiment of the present application.
  • FIG. 13 is a schematic configuration diagram of another PDU session frame format provided by the embodiment of the present application.
  • FIG. 14 is a schematic configuration diagram of another PDU session frame format provided by the embodiment of the present application.
  • FIG. 15 is a schematic configuration diagram of another PDU session frame format provided by the embodiment of the present application.
  • FIG. 16 is a schematic configuration diagram of another PDU session frame format provided by the embodiment of the present application.
  • FIG. 17 is a schematic diagram of an indication of the number of tolerable packet loss for decoding in an application layer data unit provided by an embodiment of the present application.
  • FIG. 18 is a schematic diagram of an indication of the number of tolerable packet loss for decoding in another application layer data unit provided by an embodiment of the present application.
  • FIG. 19 is a configuration relationship diagram between a logical channel group (Logical Channel Group, LCG) identifier and a QoS subflow identifier provided by an embodiment of the present application;
  • LCG Logical Channel Group
  • FIG. 20 is a schematic diagram of a structure of a medium access control layer control unit (Mediu Access Control Control Element, MAC CE) of a short buffer status report (Short Buffer Status Report, Short BSR) provided by an embodiment of the present application;
  • Medium access control layer control unit Medium Access Control Control Element, MAC CE
  • Short BSR Short Buffer Status Report
  • FIG. 21 is a schematic diagram of a MAC CE structure of a Long Buffer Status Report (Long Buffer Status Report, Long BSR) provided by an embodiment of the present application;
  • Fig. 22 is a structural block diagram of a parameter configuration device provided by an embodiment of the present application.
  • Fig. 23 is a structural block diagram of another parameter configuration device provided by the embodiment of the present application.
  • Fig. 24 is a structural block diagram of another parameter configuration device provided by the embodiment of the present application.
  • Fig. 25 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • IP packets user plane data packets
  • application layer data packets the association relationship between application layer data packets, and the different priorities between application layer data packets mapped to the same QoS Flow, is an urgent need solved problem.
  • the QoS parameters of the service are configured by the core network to the base station through the control plane signaling, and are configured according to the PDU Session--->QoS flow level.
  • a user equipment User Equipment, UE
  • UE User Equipment
  • a PDU Session can contain up to 64 QoS flows
  • QoS parameters are configured according to QoS flows.
  • QoS parameters include: user priority information (Allocation and Retention Priority (ARP)), guaranteed bit rate (Guaranteed Bit Rate, GBR) information (GBR QoS flow information), 5th generation mobile communication technology business service quality Identification (5th Generation Mobile Communication Technology Quality of Service Identifier, 5QI) description information (5QI index corresponding to the service type, service priority Priority, service maximum delay (Packet Delay Budget, PDB), etc.).
  • ARP Allocation and Retention Priority
  • GBR Guarantee Bit Rate
  • GBR Guarantee Bit Rate
  • GBR QoS flow information GRR QoS flow information
  • 5th generation mobile communication technology business service quality Identification 5th Generation Mobile Communication Technology Quality of Service Identifier, 5QI
  • 5QI index corresponding to the service type, service priority Priority, service maximum delay (Packet Delay Budget, PDB), etc.
  • the PDU of each user plane is transmitted on the corresponding PDU channel (General Packet Radio Service Tunneling Protocol–User Tunnel (GTP-U Tunnel)), and in the PDU
  • the extension header that is, the New Radio Radio Access Network Container (NR RAN Container) or PDU Session Container
  • QFI Quality of Service Flow Identifier
  • the PDU of the user plane is associated with the QoS Flow, and the base station can map different Qos flows to different data radio bearers (Data Radio Bearer, DRB), and different DRBs correspond to different LCGs.
  • the UE carries the logical channel group identifier (Logical Channel Group Identifier, LCG ID) in the BSR request, and the base station allocates uplink scheduling resources based on the BSR information, thereby realizing the priority distinction of PDU scheduling at the QoS Flow level.
  • LCG ID Logical Channel Group Identifier
  • FIG. 1 is a configuration relationship diagram among an application layer data unit, an application layer data packet and an IP packet provided by an embodiment.
  • an application layer data unit (video coding unit) is composed of 12 video frames (i.e.
  • each video frame is composed of multiple IP packets (that is, user plane data packets or PDU) (I 1 frame is composed of n IP packets I 11 I 12 ... I 1n ; B 2 is composed of m IP packets B 21 B 22 ... B 2m ).
  • the IP data packet may also be a User Datagram Protocol (User Datagram Protocol, UDP) data packet or an Ethernet data packet.
  • UDP User Datagram Protocol
  • Fig. 2 is a schematic configuration diagram of a frame format of a PDU session provided by an embodiment.
  • the core network sends the frame format of the PDU session shown in Figure 2 to the base station, and the frame format of the PDU SESSION is carried in the extension header (extension header of the GTP-U PDU, that is, NR RAN Container or PDU Session Container ) and transmitted on the GTP-U Tunnel.
  • extension header extension header of the GTP-U PDU, that is, NR RAN Container or PDU Session Container
  • the base station can see from the frame format of the PDU SESSION: the QoS Flow Identifier corresponding to the PDU and the downlink service quality flow identifier sequence number (Down Link Quality of Service Flow Identifier Sequence Number, DL QFI Sequence Number); the base station is based on the S1 application protocol (S1 Application Protocol, S1AP) interface signaling and NG Application Protocol (NG Application Protocol, NGAP) interface signaling can know the Priority Level corresponding to the QoS Flow Identifier.
  • S1 Application Protocol S1AP
  • NG Application Protocol NG Application Protocol
  • the base station cannot identify the relationship between IP packets (that is, user plane data packets) and application layer data packets (also called application layer data frames), the relationship between application layer data frames, and the applications mapped to the same QoS Flow. Different priorities between layer data frames. Therefore, how to enhance the frame format of PDU SESSION is an urgent problem to be solved.
  • FIG. 3 is a flowchart of a parameter configuration method provided in an embodiment of the present application. This embodiment may be executed by the first communication node. Wherein, the first communication node is a base station. As shown in FIG. 3, this embodiment includes: S310-S320.
  • the frame format of the PDU session includes at least one of the following indication information: application layer data packet identification information, application layer data unit ADU identification information, sub-flow identifier of QoS flow, and sub-priority of QoS flow.
  • the application layer data packet identification information is used to indicate the application layer data packet information corresponding to the user plane data packet.
  • the application layer data packet identification information may indicate corresponding application layer data packet information for the user plane data packet from different dimensions.
  • the application layer data packet information can be indicated from the application layer data packet type, for example, the application layer data packet type includes: I frame data packet, B frame data packet and P frame data packet; The importance of the package is indicated. For example, the importance of the application layer data package is divided into primary package and secondary package.
  • the ADU identification information is used to indicate at least two of the start transmission indication of the application layer data unit, the end transmission indication, the sequence number of the application layer data unit, and the total number of user plane data packets contained in the application layer data unit, and , the ADU identification information is also used to implicitly indicate that the earlier the application layer data packet in the ADU, the higher the priority.
  • the sub-flow identifier of the QoS flow refers to the identification of each QoS sub-flow contained in the QoS flow; the sub-priority of the QoS flow refers to the priority of each QoS sub-flow contained in the QoS flow. class.
  • the sub-flow identifier of the QoS flow and the sub-priority of the QoS flow can be represented by the QoS flow sub-priority, that is, the QoS flow sub-priority includes both the identification of the QoS sub-flow and the priority of the QoS sub-flow. class.
  • S320 Determine scheduling priorities or resource allocation weights of different user plane data packets in the same QoS flow according to the frame format of the PDU session.
  • the second communication node sends the frame format of the PDU session to the first communication node through the user, and the frame format of the PDU session includes application layer data packet identification information, ADU identification information, subflow identification of the QoS flow, and At least one of the sub-priorities of the QoS flow, so that the first communication node identifies the association relationship between the user plane data packet and the application layer data packet, the association relationship between different application layer data packets according to the frame format of the PDU session, and Different priorities between application layer data packets mapped to the same QoS flow, so that the first communication node can determine the scheduling priority or resource allocation weight of different user plane data packets in the same QoS flow according to the frame format of the PDU session, so that The BSR can be reported according to the scheduling priority and allocated scheduling resources.
  • the parameter configuration method applied to the first communication node further includes: receiving QoS sub-flow configuration information sent by the second communication node, the QoS sub-flow configuration information includes the sub-priority of the QoS flow and/or the QoS flow The substream ID of .
  • the first communication node before the first communication node receives the frame format of the PDU session sent by the second communication node, the first communication node receives the QoS subflow configuration information sent by the second communication node through control plane signaling.
  • the sub-priority of the QoS flow, or the sub-priority of the QoS flow and the sub-flow identifier of the QoS flow are carried in the QoS sub-flow configuration information.
  • the sub-priority of the QoS flow can represent not only the priority of the QoS sub-flow, but also the identification of the QoS sub-flow.
  • the QoS flow configuration information or the QoS subflow configuration information includes one of the following: the maximum total number of packet loss that can be tolerated in the application layer data unit; the maximum total number of continuous packet loss that can be tolerated in the application layer data unit.
  • the maximum tolerable total packet loss within a defined time period, the maximum tolerable total continuous packet loss within a predefined time period, the maximum tolerable total application layer data unit loss within a predefined time period, and the tolerable maximum total packet loss within a predefined time period The maximum total number of consecutive application layer data units lost.
  • the total number of lost packets is the total number of lost user plane data packets or the total number of lost application layer data packets.
  • the second communication node sends the QoS flow configuration information, or the QoS sub-flow configuration information, to the first communication node through control plane signaling.
  • the QoS flow configuration information carries the maximum total number of packets that can be tolerated in the application layer data unit, or the maximum total number of consecutive packet losses that can be tolerated in the application layer data unit, the maximum total number of The maximum total number of application layer data unit losses, the maximum total number of continuous application layer data unit losses that can be tolerated within a predefined period of time.
  • the total number of lost packets is the total number of lost user plane data packets or the total number of lost application layer data packets.
  • the QoS subflow configuration information carries the maximum packet loss that can be tolerated in the application layer data unit The total number, or the maximum total number of consecutive packet losses that can be tolerated in the application layer data unit, the maximum total number of packet losses that can be tolerated within a predefined time period, the maximum total number of The maximum total number of tolerable loss of application layer data units, the maximum total number of continuous loss of application layer data units that can be tolerated within a predefined time period.
  • the total number of lost packets is the total number of lost user plane data packets or the total number of lost application layer data packets.
  • application layer data packets with different priorities are mapped to the same QoS flow; the frame format of the PDU session at least includes: ADU identification information.
  • ADU identification information may be carried in the frame format of the PDU session to indicate the application layer data corresponding to each application layer data packet
  • the start transmission indication and the end transmission indication of the unit can further determine the priority of each application layer data packet in the application layer data unit.
  • the ADU identification information implicitly indicates that the earlier the application layer data packet in each ADU, the higher the priority.
  • the indicator bit of the ADU identification information may be one bit or two bits.
  • ADU identification information is used to indicate at least two levels of application layer data units.
  • the parameters carried in the ADU identification information may be combined, multiplexed and included in multiple levels to indicate multiple levels of application layer data units.
  • the first level application layer data unit may be a video stream
  • the second level application layer data unit may be a video frame.
  • the ADU identification information includes at least one of the following: an indication of the start of transmission of the application layer data unit; an indication of the end of transmission of the application layer data unit.
  • the start transmission indication of the application layer data unit is used to indicate the location of the first application layer data packet in the same application layer data unit; the end transmission indication of the application layer data unit is used to indicate the same The location of the last application layer data packet in the application layer data unit.
  • the ADU identification information includes at least one of the following: application layer data unit sequence number; application layer data unit end transmission indication.
  • the application layer data unit sequence number is used to indicate whether the user plane data packets correspond to the same application layer data unit, and the user plane data packets with the same sequence number in the same QoS flow correspond to the same application layer data unit, and the user plane data packets with different sequence numbers Plane data packets correspond to different application layer data units.
  • the ADU identification information includes at least one of the following: an instruction to start transmission of the application layer data unit; the total number of user plane data packets included in the application layer data unit. In an embodiment, starting from the user plane data packet indicated by the start transmission indication of the application layer data unit, the user plane data packets of the total number of user plane data packets included in the consecutive application layer data units all belong to the same application layer data unit .
  • application layer data packets with different QoS priorities are mapped to different QoS flows;
  • the frame format of the PDU session includes one of the following: an associated QoS flow identifier QFI and an associated downlink QFI sequence number.
  • the associated QoS flow identifier QFI and the associated downlink QFI sequence number are used to represent the association relationship, dependency relationship, supplementary relationship, primary and secondary relationship, subordination or chronological relationship.
  • the frame format of the PDU session includes one of the following: the maximum tolerable total number of packet loss in the application layer data unit; the maximum tolerable total number of consecutive packet loss in the application layer data unit.
  • the total number of lost packets is the total number of lost user plane data packets or the total number of lost application layer data packets.
  • the second communication node may send the frame format of the PDU session to the first communication node through the user, and carry the maximum total number of packet loss tolerable in the application layer data unit in the frame format of the PDU session, or the application layer data The maximum total number of consecutive packet losses that can be tolerated in a cell.
  • the total number of lost packets is the total number of lost user plane data packets or the total number of lost application layer data packets.
  • the frame format of the PDU session further includes: an instruction to start transmission of the application layer data unit; and the total number of user plane data packets included in the application layer data unit.
  • the total number of user plane data packets contained in an application layer data unit refers to the total number of user plane data packets contained in one application layer data unit, that is, the number of IP packets, which may also be referred to as the number of PDUs.
  • the application layer data packet identification information may also include: the application layer data packet sequence number, the start transmission indication of the application layer data packet, the end transmission indication of the application layer data packet, the user plane data contained in the application layer data packet At least two of the total number of packets.
  • the explanation of each parameter in the application layer data packet identification information is the same as that of the corresponding parameter in the ADU identification information, except that the application layer data unit is replaced by the application layer data packet.
  • application layer packets of different priorities are mapped to the same QoS flow; different sub-flow identifiers or sub-priorities in the same QoS flow are mapped to different dedicated radio bearer DRB identifiers and different logical channels (Logical Channel, LC) identifier, or a different logical channel group LCG identifier.
  • the first communication node maps different sub-flow identities or sub-priorities in the same QoS flow to different LC identities, and then maps different LC identities to different LCG identities.
  • QoS sub-flows or sub-priorities with different priorities are mapped to different LCG identifiers.
  • the first communication node may map different sub-flow identifiers or sub-priorities in the same QoS flow to different DRB identifiers and different LCs. ID, or different LCG IDs, so that the third communication node reports the BSR according to different sub-flow IDs or sub-priorities.
  • different sub-flow identifiers or sub-priorities in the same QoS flow are mapped to different DRB identifiers, different LC identifiers, or different LCG identifiers, including: sub-flow identifiers of QoS flows or sub-flow identifiers of QoS flows
  • the priority is included in at least one of the following configuration information sent to the third communication node: SDAP configuration information, radio bearer configuration information, logical channel configuration information, and radio link control configuration information.
  • the sub-flow identifier of the QoS flow or the sub-priority of the QoS flow is used to map the user plane data packets of the same QoS flow to different logical channels.
  • FIG. 4 is a flow chart of another parameter configuration method provided by the embodiment of the present application. This embodiment may be executed by the third communication node. Wherein, the third communication node is a user equipment. As shown in FIG. 4, this embodiment includes: S410-S420.
  • S410 Receive configuration information sent by the first communication node.
  • the configuration information includes the sub-flow identifier of the QoS flow or the sub-priority of the QoS flow; the configuration information includes at least one of the following: SDAP configuration information, radio bearer configuration information, logical channel configuration information, and radio link control configuration information.
  • the sub-flow identifier of the QoS flow or the sub-priority of the QoS flow is used to map user plane data packets of the same QoS flow to different logical channels.
  • the first communication node maps different sub-flow identities or sub-priorities in the same QoS flow to different LC identities, and then maps different LC identities to different LCG identities. QoS sub-flows or sub-priorities with different priorities are mapped to different LCG identifiers.
  • the third communication node performs a BSR request based on the LCG identifier
  • the first communication node may perform BSR differentiation on QoS sub-flows or sub-priorities with different priorities in the same QoS flow.
  • each parameter in the parameter configuration method applied to the third communication node refers to the description of the corresponding parameters in the parameter configuration method applied to the first communication node in the above embodiment, which is not described here. Let me repeat them one by one.
  • FIG. 5 is a flowchart of another parameter configuration method provided in the embodiment of the present application. This embodiment may be executed by the second communication node. Wherein, the second communication node is a core network. As shown in FIG. 5 , this embodiment includes: S510.
  • the frame format of the PDU session includes at least one of the following indication information: application layer data packet identification information, ADU identification information, sub-flow identifier of the QoS flow, and QoS flow. subpriority.
  • the parameter configuration method applied to the second communication node further includes: sending QoS sub-flow configuration information to the first communication node, the QoS sub-flow configuration information includes the sub-priority of the QoS flow and/or the sub-priority of the QoS flow Substream ID.
  • the QoS flow configuration information or the QoS subflow configuration information includes one of the following: the maximum total number of packet losses that can be tolerated in an application layer data unit, the maximum total number of consecutive packet losses that can be tolerated in an application layer data unit, the preset The maximum tolerable total packet loss within a defined time period, the maximum tolerable total continuous packet loss within a predefined time period, the maximum tolerable total application layer data unit loss within a predefined time period, and the tolerable maximum total packet loss within a predefined time period The maximum total number of consecutive application layer data units lost.
  • the total number of lost packets is the total number of lost user plane data packets or the total number of lost application layer data packets.
  • application layer data packets with different priorities are mapped to the same QoS flow; the frame format of the PDU session includes at least one of the following: ADU identification information.
  • ADU identification information is used to indicate at least two levels of application layer data units.
  • the ADU identification information includes at least one of the following: an indication of the start of transmission of the application layer data unit; an indication of the end of transmission of the application layer data unit.
  • the ADU identification information includes at least one of the following: application layer data unit sequence number; application layer data unit end transmission indication.
  • the ADU identification information includes at least one of the following: an instruction to start transmission of the application layer data unit; the total number of user plane data packets included in the application layer data unit.
  • application layer data frames with different QoS priorities are mapped to different QoS flows;
  • the frame format of the PDU session includes one of the following: an associated QoS flow identifier QFI and an associated downlink QFI sequence number.
  • the associated QoS flow identifier QFI and the associated downlink QFI sequence number are used to represent the existence of an association relationship, a dependency relationship, a supplementary relationship, a primary Auxiliary, subordinate, or chronological relationships.
  • the frame format of the PDU session includes one of the following: the maximum tolerable total number of packet loss in the application layer data unit; the maximum tolerable total number of consecutive packet loss in the application layer data unit.
  • the total number of lost packets is the total number of lost user plane data packets or the total number of lost application layer data packets.
  • the frame format of the PDU session further includes: an instruction to start transmission of the application layer data unit; and the total number of user plane data packets included in the application layer data unit.
  • application layer data packets of different priorities are mapped to the same QoS flow; different sub-flow identifiers or sub-priorities in the same QoS flow are mapped to different dedicated radio bearer DRB identifiers, different logical channel LC identifiers, or Different Logical Channel Group LCG identifiers.
  • different sub-flow identifiers or sub-priorities in the same QoS flow are mapped to different dedicated radio bearer DRB identifiers, different logical channel LC identifiers, or different logical channel group LCG identifiers, including: QoS flow
  • the sub-flow identifier or the sub-priority of the QoS flow is included in at least one of the following configuration information sent to the third communication node: service data adaptation protocol SDAP configuration information, radio bearer configuration information, logical channel configuration information, and radio link Road control configuration information.
  • the sub-flow identifier of the QoS flow or the sub-priority of the QoS flow is used to map the user plane data packets of the same QoS flow to different logical channels.
  • each parameter in the parameter configuration method applied to the second communication node refers to the description of the corresponding parameters in the parameter configuration method applied to the first communication node in the above embodiment, which is not described here. Let me repeat them one by one.
  • FIG. 6 is a schematic configuration diagram of another PDU session frame format provided by the embodiment of the present application.
  • the frame format of PDU SESSION carries at least one of the following: application layer packet type, application layer packet sub-priority (Application packet sub-Priority), application layer packet sub-flow identification (Application packet sub-Flow ID).
  • the application layer packet type (Application packet Type) or the priority (Application packet Priority) of the application layer packet (Application packet Priority) is used for the base station to identify PDU (that is, the user plane data packet in the above-mentioned embodiment, or IP Packets) in the transmission process In order to identify the scheduling priority of different PDUs or the weight of resource allocation under the same QoS flow.
  • PDU that is, the user plane data packet in the above-mentioned embodiment, or IP Packets
  • the base station can determine the application layer data packet type corresponding to the PDU, thereby determining the scheduling priority, reliability requirements, or resource allocation weight of the PDU; the application layer data packet type can indicate the IP packet corresponding to The application layer data packet type, for example: indicating the I frame data packet, B frame data packet, and P frame data packet in the video stream; or indicating whether the data packet is a primary packet or a secondary packet, which is used for the base station to identify the importance of the data packet.
  • the base station can judge the priority of the application layer data packet corresponding to the PDU, so as to determine the scheduling priority, reliability requirement or resource allocation weight of the PDU .
  • the sub-priority (Application packet sub-Priority) and/or sub-flow identification (Application packet sub-Flow ID) of the application layer data packet contained in the QoS flow in the S1AP/NGAP signaling from the core network to the base station ) is used by the base station to configure resources with different priorities for data packets of different sub-Priority under the same QoS flow.
  • FIG. 7 is a schematic configuration diagram of adding a QoS subflow in a QoS flow provided by an embodiment of the present application
  • FIG. 8 is a schematic configuration diagram of adding a QoS subflow in another QoS flow provided by an embodiment of the present application.
  • each QoS Flow contains multiple QoS sub-flows
  • each QoS sub-Flow contains: the sub-flow identifier (QoS sub-flow ID) of the QoS flow and the sub-priority of the QoS flow (QoS sub-flow ID) -flow Priority); or, each QoS sub-Flow contains QoS flow sub-priority (QoS sub-Priority).
  • the QoS sub-flow in the QoS Flow may not be reflected, but only: the QoS flow contains multiple QoS sub-Priorities, as shown in Figure 8, and the frame format of the PDU session only includes QoS sub-Priority (that is, Figure 6 Middle); if the QoS sub-flow is reflected in the QoS Flow, the PDU Format also includes the QoS sub-flow ID and QoS sub-flow Priority; or, the PDU Format includes the QoS sub-Priority.
  • the QoS parameters related to QoS sub-flow can be defined based on the QoS parameter difference of QoS Flow.
  • the QOS parameters related to QoS sub-flow only include parameters with different values from the QoS parameters of QoS Flow.
  • application layer data packets of different priorities are mapped to the same QoS Flow, and ADU identification information is introduced into the frame format of the PDU session, and the ADU identification information is used to implicitly indicate that the higher the priority of the data packet in the ADU is, the higher the priority is. .
  • FIG. 9 is a schematic configuration diagram of another frame format of a PDU session provided by an embodiment of the present application.
  • the frame format of the PDU session carries at least one of the following: application layer data unit start transmission indication (Application Data Unit start mark), end transmission indication (Application Data Unit end mark).
  • the indicator bit of the ADU identification information can occupy 2 bits, and the four values of the indicator bit represent at least one of the following: the indicator bit does not exist, the transmission of an application layer data unit starts, the transmission of an application layer data unit ends, and an application layer A data unit has only one PDU.
  • the DL QFI Sequence Number under the same QoS flow is All PDUs in the interval [DL QFI Sequence Number 1, DL QFI Sequence Number 2] correspond to the same application layer data unit.
  • the ADU identification information can imply: the data frame or PDU in the same application layer data unit, the higher the sequence number, the more important (the higher the scheduling priority, the stronger the reliability requirement).
  • the indicator bit of the ADU identification information may occupy 1 bit.
  • the bit is 1, it means that the application layer data unit transmission start indication (start mark) or end transmission indication (end mark) under the same QoS flow (wherein, the new start transmission indication is the old end transmission indication).
  • FIG. 10 is a schematic diagram of a configuration of a PDU corresponding to the same ADU based on a transmission start indication provided by an embodiment of the present application.
  • the value of 1 bit is 1, indicating that an application layer data unit starts to transmit an indication (start mark), until 1 bit is 1 again under the same QoS flow, all PDUs correspond to an application layer data unit.
  • FIG. 11 is a schematic configuration diagram of indicating a PDU corresponding to the same ADU based on an end transmission indication provided by the embodiment of the present application.
  • FIG. 12 is a schematic configuration diagram of another frame format of a PDU session provided by the embodiment of the present application.
  • the frame format of the PDU session carries at least one of the following: the application layer data unit sequence number (Application Data Unit Sequence Number) and the end transmission indication (End mark) of the application layer data unit.
  • the application layer data unit serial number is used by the base station to identify whether the PDU corresponds to the same application layer data unit, and the PDUs with the same application layer data unit serial number under the same QoS flow correspond to the same application layer data unit; the PDUs with different application layer data unit serial numbers correspond to different Application layer data unit.
  • the end transmission indication of the application layer data unit is used to indicate the last PDU corresponding to the same application layer data unit.
  • the base station can judge whether a new application layer data unit PDU starts to transmit and whether different PDUs correspond to the same application layer data unit; based on the end indication of the application layer data unit, the base station can judge an application layer data unit Whether the PDU transmission is over. For example, the value of End mark in Figure 12 is 1, indicating that the PDU transmission of an application layer data unit is completed.
  • the PDUs with the same serial number of the application layer data unit under the same QoS flow correspond to a complete application layer data unit.
  • whether the sequence number of the application layer data unit of the current PDU is the same as that of the next PDU can also be used to identify whether the application layer data unit corresponding to the current PDU ends. If a new application layer data unit starts to be transmitted, it implicitly indicates that the transmission of the previous application layer data unit is completed. The end indication of the application layer data unit is not required at this time.
  • FIG. 13 is a schematic configuration diagram of another frame format of a PDU session provided by the embodiment of the present application.
  • the application layer data unit start transmission indication Start mark
  • the total number of user plane data packets contained in the application layer data unit Packet Total Number in one Application Data Unit.
  • the data packets of the total number of user plane data packets included in the consecutive application layer data units belong to the same application layer data unit.
  • FIG. 14 is a schematic configuration diagram of another frame format of a PDU session provided by the embodiment of the present application.
  • Figures 9, 12 and 13 can be combined, multiplexed, and multi-level included to represent multi-level application layer data units, for example: a first-level application layer data unit is a video stream (i.e.
  • the second-level application layer data unit is a video frame (that is, the application layer data frame/application layer data packet), and the configuration method in Figure 12 is used for the second-level inclusion, and the result is shown in Figure 14 (where: the bits where Fist Level and Second Level are located The location is just an example, and the actual number of occupied bits and the occupied bit position may be different, for example, parameters related to Fist Level and Second Level are placed in the extended bit position of the PDU, or a new PDU format is introduced).
  • the second-level application layer data unit is illustrated as an example: the first-level application layer data unit represents a video stream; the second-level application layer data unit represents a video frame. Corresponding to the information in Figure 1, it can be filled in as the following structure:
  • Second level End mark 1 (I1 frame ends)
  • Second level End mark 1 (end of B2 frame)
  • the application layer packet frames of different QoS Flows are mapped to different QoS flows, and the frame format of the PDU session introduces the dependency relationship between the QoS flow and the PDU sequence number.
  • Fig. 15 is a schematic configuration diagram of another frame format of a PDU session provided by the embodiment of the present application.
  • the associated QoS flow identifier QFI Associated QoS Flow Identifier
  • the associated downlink QFI sequence number Associated DL QFI Sequence Number
  • the PDU corresponding to the QoS Flow Identifier and the Associated DL QFI Sequence Number or the application layer data unit of the corresponding PDU has an association relationship, a dependency relationship, a supplementary relationship, a master-slave relationship, an affiliation relationship or a timing relationship; and/or is used to characterize the PDU and the association
  • the PDUs belong to the same application layer message, belong to the same application layer data unit or belong to the same type of data packet.
  • the PDU or the application layer data unit corresponding to the PDU be solved.
  • FIG. 16 is a schematic configuration diagram of another frame format of a PDU session provided by the embodiment of the present application.
  • the number of tolerable packet loss in the decoding of the application layer data unit includes: the maximum total number of packet loss or the maximum total number of continuous packet loss that can be tolerated in the decoding of the application layer data unit.
  • the total number of lost packets is the total number of lost user plane data packets or the total number of lost application layer data packets. As shown in FIG.
  • the frame format of the PDU session carries one of the following: the maximum tolerable total packet loss in the application layer data unit and the maximum tolerable total continuous packet loss in the application layer data unit.
  • the frame format of the PDU session may also include: an instruction to start transmission of the application layer data unit and the total number of user plane data packets included in the application layer data unit.
  • the total number of lost packets is the total number of lost user plane data packets or the total number of lost application layer data packets.
  • the number of tolerable packet loss for decoding in the application layer data unit may be indicated by the tolerable number of packet loss included in the QoS flow of the S1AP/NGAP signaling from the core network to the base station, or by the number of tolerable packet loss included in the PDU format. An indication of the number of packet losses to tolerate.
  • Maximal Lost packets tolerable in FIG. 16 can indicate the total number of tolerable packet loss in the ADU or the total number of tolerable continuous packet loss. If the number of lost packets is greater than Maximal Lost packets tolerable, the application layer requirements are not met (For example, causing application layer decoding to fail).
  • the number of lost data packets is about to reach Maximal Lost packets tolerable, then improve the reliability of subsequent data packet transmission (such as activating PDCP Duplication or increase the transmission power); if starting from the data packet identified by the Start Mark, in the data packet of the Packet Total Number in one Application Data Unit, the number of lost data packets reaches the Maximal Lost packets tolerable, then discard the Packet Total Number in one Untransmitted data packets in the data packets of the Application Data Unit.
  • Maximal Lost packets tolerable can be defined based on the application layer data unit (such as the first-level application layer data unit in Figure 14), or can be defined based on the data packet type (such as the second-level application layer data unit in Figure 14).
  • FIG. 17 is a schematic diagram of an indication of the number of tolerable packet loss for decoding in an application layer data unit provided in an embodiment of the present application
  • FIG. 18 is a schematic diagram of another application layer data unit provided in an embodiment of the present application. Schematic representation of an indication of the number of tolerable packet losses for decoding.
  • the QoS sub-flow contains the tolerable The maximum total number of packet loss or the maximum total number of consecutive packet loss; as shown in Figure 18, the QoS flow contains the maximum total number of packet loss or the maximum total number of continuous packet loss that can be tolerated in each application layer data unit.
  • the application layer data packet identification information may also include: the application layer data packet sequence number, the start transmission indication of the application layer data packet, the end transmission indication of the application layer data packet, and the user plane data contained in the application layer data packet. At least two of the total number of packets.
  • the explanation of each parameter in the application layer data packet identification information is the same as the description of the corresponding parameters in the ADU identification information, except that the application layer data unit is replaced by the application layer data packet.
  • the drawings for the ADU identification information in the above embodiments are also applicable to the application layer data packet identification information, which will not be repeated here.
  • FIG. 19 is a configuration relationship diagram between an LCG identifier and a QoS subflow identifier provided in an embodiment of the present application.
  • the base station maps QoS Sub-flow IDs or sub-priorities with different priorities in the same QoS Flow to different LC IDs, and then maps different LC IDs to different LCG IDs, thereby achieving the same QoS Flow QoS Sub-flow IDs or sub-priorities with different priorities are mapped to different LCG IDs.
  • SDAP mapping considers QoS Sub-Flow ID, SDAP and Radio Link Control Bearer Configuration (Radio Link Control-BearerConfig, RLC-BearerConfig) are associated with DRB at the same time, so QoS Sub-Flow ID is also mapped to RLC-BearerConfig; and each RLC-BearerConfig is associated to an LCG.
  • QoS Sub-Flow ID is also mapped to RLC-BearerConfig; and each RLC-BearerConfig is associated to an LCG.
  • the BSR can be distinguished for QoS Sub-flow IDs or sub-priorities with different priorities in the same QoS Flow.
  • not only the priority of QoS flow is reflected in the BSR request, but also the priority of QoS sub-flow can be reflected.
  • the QoS Sub-flow ID or sub-priority of different priorities can also be the application layer data packet type shown in FIG. 6, and the application layer data packet type can also be reflected in the BSR.
  • FIG. 20 is a schematic diagram of a MAC CE structure of a Short BSR provided in an embodiment of the present application.
  • a Short BSR contains the LCG identifier and the buffered data size value (Buffer Size).
  • FIG. 21 is a schematic diagram of a MAC CE structure of a Long BSR provided in an embodiment of the present application.
  • a Short BSR contains multiple LCG identifiers and the buffer data size value (Buffer Size) corresponding to each LCG identifier.
  • Buffer Size buffer data size value
  • FIG. 22 is a structural block diagram of a parameter configuration device provided in an embodiment of the present application. This embodiment is applied to the first communication node. As shown in FIG. 22 , the parameter configuration device in this embodiment includes: a first receiver 2210 and a determination module 2220 .
  • the first receiver 2210 is configured to receive the frame format of the packet data unit PDU session sent by the second communication node; wherein, the frame format of the PDU session includes at least one of the following indication information: application layer data packet identification information, application layer data Unit ADU identification information, sub-flow identification of quality of service QoS flow and sub-priority of QoS flow; determining module 2220, configured to determine scheduling priority or resource allocation of different user plane data packets in the same QoS flow according to the frame format of the PDU session Weights.
  • the parameter configuration device applied to the first communication node further includes: a second receiver configured to receive the QoS sub-flow configuration information sent by the second communication node, the QoS sub-flow configuration information includes the sub-flow of the QoS flow Sub-flow identification for priority and/or QoS flows.
  • the QoS flow configuration information or the QoS subflow configuration information includes one of the following: the maximum total number of packet losses that can be tolerated in an application layer data unit, the maximum total number of consecutive packet losses that can be tolerated in an application layer data unit, the preset The maximum total number of packet losses that can be tolerated within a defined time period, the maximum total number of consecutive packet losses that can be tolerated within a predefined time period, the maximum total number of application layer data unit losses that can be tolerated within a predefined time period, and the tolerable maximum total number of lost packets within a predefined time period The maximum total number of contiguous application layer data units lost.
  • application layer data packets with different priorities are mapped to the same QoS flow; the frame format of the PDU session at least includes: ADU identification information.
  • ADU identification information is used to indicate at least two levels of application layer data units.
  • the ADU identification information includes at least one of the following: an indication of the start of transmission of the application layer data unit; an indication of the end of transmission of the application layer data unit.
  • the ADU identification information includes at least one of the following: application layer data unit sequence number; application layer data unit end transmission indication.
  • the ADU identification information includes at least one of the following: an instruction to start transmission of the application layer data unit; the total number of user plane data packets included in the application layer data unit.
  • application layer data packets with different QOS priorities are mapped to different QoS flows;
  • the frame format of the PDU session includes one of the following: an associated QoS flow identifier QFI and an associated downlink QFI sequence number.
  • the associated QoS flow identifier QFI and the associated downlink QFI sequence number are used to represent the association relationship, dependency relationship, supplementary relationship, primary and secondary relationship, subordination or chronological relationship.
  • the frame format of the PDU session includes one of the following: the maximum tolerable total number of packet loss in the application layer data unit; the maximum tolerable total number of consecutive packet loss in the application layer data unit.
  • the frame format of the PDU session further includes: an instruction to start transmission of the application layer data unit; and the total number of user plane data packets included in the application layer data unit.
  • application layer data packets of different priorities are mapped to the same QoS flow; different sub-flow identifiers or sub-priorities in the same QoS flow are mapped to different dedicated data radio bearer DRB identifiers, different logical channel LC identifiers, Or on a different logical channel group LCG identifier.
  • different sub-flow identifiers or sub-priorities in the same QoS flow are mapped to different dedicated DRB identifiers, different LC identifiers, or different LCG identifiers, including: subflow identifiers or QoS flow identifiers of QoS flows
  • the sub-priority is included in at least one of the following configuration information sent to the third communication node: Service Data Adaptation Protocol SDAP configuration information, radio bearer configuration information, logical channel configuration information, radio link control configuration information; QoS flow
  • the sub-flow identifier of the QoS flow or the sub-priority of the QoS flow is used to map the user plane data packets of the same QoS flow to different logical channels.
  • the parameter configuration device provided in this embodiment is configured to implement the parameter configuration method in the embodiment shown in FIG. 3 .
  • the implementation principle and technical effect of the parameter configuration device provided in this embodiment are similar, and details are not repeated here.
  • FIG. 23 is a structural block diagram of another parameter configuration device provided in an embodiment of the present application. This embodiment may be executed by the third communication node. Wherein, the third communication node is a user equipment. As shown in FIG. 23 , the parameter configuration device in this embodiment includes: a third receiver 2310 and a reporting module 2320 .
  • the third receiver 2310 is configured to receive the configuration information sent by the first communication node; the reporting module 2320 is configured to report the buffer status report BSR according to the configuration information; wherein the configuration information includes the sub-flow identifier of the QoS flow or the sub-priority of the QoS flow level; the configuration information includes at least one of the following: SDAP configuration information, radio bearer configuration information, logical channel configuration information, and radio link control configuration information.
  • the sub-flow identifier of the QoS flow or the sub-priority of the QoS flow is used to map user plane data packets of the same QoS flow to different logical channels.
  • the parameter configuration device provided in this embodiment is set to implement the parameter configuration method applied to the embodiment of the third communication node shown in FIG.
  • FIG. 24 is a structural block diagram of another parameter configuration device provided in an embodiment of the present application. This embodiment may be executed by the second communication node. Wherein, the second communication node is a core network. As shown in FIG. 24 , this embodiment includes: a first transmitter 2410 .
  • the first transmitter 2410 is configured to send the frame format of the PDU session to the first communication node, and the frame format of the PDU session includes at least one of the following indication information: application layer data packet identification information, ADU identification information, subflow of QoS flow ID and sub-priority of the QoS flow.
  • the parameter configuration device applied to the second communication node further includes: a second transmitter configured to send QoS sub-flow configuration information to the first communication node, the QoS sub-flow configuration information includes the sub-priority of the QoS flow Class and/or sub-flow identifier of the QoS flow.
  • the QoS flow configuration information or the QoS subflow configuration information includes one of the following: the maximum total number of packet losses that can be tolerated in an application layer data unit, the maximum total number of consecutive packet losses that can be tolerated in an application layer data unit, the preset The maximum tolerable total packet loss within a defined time period, the maximum tolerable total continuous packet loss within a predefined time period, the maximum tolerable total application layer data unit loss within a predefined time period, and the tolerable maximum total packet loss within a predefined time period The maximum total number of consecutive application layer data units lost.
  • application layer data packets with different priorities are mapped to the same QoS flow; the frame format of the PDU session at least includes: ADU identification information.
  • ADU identification information is used to indicate at least two levels of application layer data units.
  • the ADU identification information includes at least one of the following: an indication of the start of transmission of the application layer data unit; an indication of the end of transmission of the application layer data unit.
  • the ADU identification information includes at least one of the following: application layer data unit sequence number; application layer data unit end transmission indication.
  • the ADU identification information includes at least one of the following: an instruction to start transmission of the application layer data unit; the total number of user plane data packets included in the application layer data unit.
  • application layer data frames with different QoS priorities are mapped to different QoS flows;
  • the frame format of the PDU session includes one of the following: an associated QoS flow identifier QFI and an associated downlink QFI sequence number.
  • the associated QoS flow identifier QFI and the associated downlink QFI sequence number are used to represent the association relationship, dependency relationship, supplementary relationship, primary and secondary relationship, subordination or chronological relationship.
  • the frame format of the PDU session includes one of the following: the maximum tolerable total number of packet loss in the application layer data unit; the maximum tolerable total number of consecutive packet loss in the application layer data unit.
  • the frame format of the PDU session further includes: an instruction to start transmission of the application layer data unit; and the total number of user plane data packets included in the application layer data unit.
  • application layer data packets of different priorities are mapped to the same QoS flow; different sub-flow identifiers or sub-priorities in the same QoS flow are mapped to different dedicated radio bearer DRB identifiers, different logical channel LC identifiers, or Different Logical Channel Group LCG identifiers.
  • different sub-flow identifiers or sub-priorities in the same QoS flow are mapped to different dedicated DRB identifiers, different LC identifiers, or different LCG identifiers, including: the sub-flow identifier of the QoS flow or the sub-flow identifier of the QoS flow
  • the sub-priority is included in at least one of the following configuration information sent to the third communication node: Service Data Adaptation Protocol SDAP configuration information, radio bearer configuration information, logical channel configuration information, and radio link control configuration information; QoS flow
  • the sub-flow identifier of the QoS flow or the sub-priority of the QoS flow is used to map the user plane data packets of the same QoS flow to different logical channels.
  • the parameter configuration device provided in this embodiment is set to implement the parameter configuration method applied to the embodiment of the second communication node shown in FIG. 5 .
  • the implementation principle and technical effect of the parameter configuration device provided in this embodiment are similar, and will not be repeated here.
  • Fig. 25 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the device provided by this application includes: a processor 2510 , a memory 2520 and a communication module 2530 .
  • the number of processors 2510 in the device may be one or more, and one processor 2510 is taken as an example in FIG. 25 .
  • the number of storage 2520 in the device may be one or more, and one storage 2520 is taken as an example in FIG. 25 .
  • the processor 2510, the memory 2520, and the communication module 2530 of the device may be connected through a bus or in other ways. In FIG. 25, connection through a bus is taken as an example.
  • the device may be a base station.
  • the memory 2520 can be set to store software programs, computer-executable programs and modules, such as program instructions/modules corresponding to the equipment in any embodiment of the present application (for example, the first receiver in the parameter configuration device Detector and Determination Module).
  • the memory 2520 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to usage of the device, and the like.
  • the memory 2520 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage devices.
  • memory 2520 may include memory located remotely from processor 2510, which remote memory may be connected to the device through a network.
  • Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination of the Internet, an intranet, a local area network, and a mobile communication network.
  • the communication module 2530 is configured to communicate with other communication nodes.
  • the device provided above may be configured to execute the parameter configuration method applied to the first communication node provided in any of the above embodiments, and have corresponding functions and effects.
  • the device provided above may be configured to execute the parameter configuration method applied to the second communication node provided in any of the above embodiments, and have corresponding functions and effects.
  • the device provided above may be configured to execute the parameter configuration method applied to the third communication node provided by any of the above embodiments, and have corresponding functions and effects.
  • the embodiment of the present application also provides a storage medium containing computer-executable instructions.
  • the computer-executable instructions When executed by a computer processor, the computer-executable instructions are used to execute a parameter configuration method applied to the first communication node.
  • the method includes: receiving the first communication node 2.
  • the sub-flow identifier of the flow and the sub-priority of the QoS flow determine the scheduling priority or resource allocation weight of different user plane data packets in the same QoS flow according to the frame format of the PDU session.
  • the embodiment of the present application also provides a storage medium containing computer-executable instructions.
  • the computer-executable instructions When executed by a computer processor, the computer-executable instructions are used to execute a parameter configuration method applied to a third communication node.
  • the method includes: receiving the first Configuration information sent by a communication node; report buffer status report BSR according to the configuration information; wherein, the configuration information includes the sub-flow identifier of the QoS flow or the sub-priority of the QoS flow; the configuration information includes at least one of the following: SDAP configuration information, radio bearer configuration information, logical channel configuration information and radio link control configuration information.
  • the embodiment of the present application also provides a storage medium containing computer-executable instructions.
  • the computer-executable instructions When executed by a computer processor, the computer-executable instructions are used to execute a parameter configuration method applied to the second communication node.
  • the method includes: sending to the second communication node A communication node sends a frame format of a PDU session, and the frame format of the PDU session includes at least one of the following indication information: application layer data packet identification information, ADU identification information, sub-flow identification of a QoS flow, and sub-priority of a QoS flow class.
  • user equipment covers any type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.
  • the various embodiments of the present application can be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.
  • Computer program instructions may be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages source or object code.
  • ISA Instruction Set Architecture
  • Any logic flow block diagrams in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules and functions, or may represent a combination of program steps and logic circuits, modules and functions.
  • Computer programs can be stored on memory.
  • the memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, Read-Only Memory (ROM), Random Access Memory (RAM), Optical Storage devices and systems (Digital Video Disc (DVD) or Compact Disk (CD)), etc.
  • Computer readable media may include non-transitory storage media.
  • Data processors can be of any type suitable for the local technical environment, such as but not limited to general purpose computers, special purpose computers, microprocessors, digital signal processors (Digital Signal Processing, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC ), programmable logic devices (Field-Programmable Gate Array, FPGA), and processors based on multi-core processor architectures.
  • DSP Digital Signal Processing
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • processors based on multi-core processor architectures.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提出一种参数配置方法、通信设备和存储介质。该应用于第一通信节点的参数配置方法包括：接收第二通信节点发送的分组数据单元PDU会话的帧格式；其中，所述PDU会话的帧格式包括下述指示信息至少之一：应用层数据包识别信息，应用层数据单元ADU识别信息，QoS流的子流标识以及QoS流的子优先级；根据所述PDU会话的帧格式确定同一QoS流中不同用户面数据包的调度优先级或资源分配权重。

Description

参数配置方法、通信设备和存储介质 技术领域
本申请涉及通信领域，例如涉及一种参数配置方法、通信设备和存储介质。
背景技术
在新空口(New Radio，NR)网络中，业务的服务质量(Quality of Service，QoS)参数是核心网通过控制面信令配置给基站的，是按照分组数据单元会话(Packet Data Unit Session，PDU Session)--->服务质量流(Quality of Service flow，QoS flow)级别配置的。一个QoS flow只有一个QoS优先级，且不同QoS Flow的数据包之间没有关联关系。但是在扩展现实(Extended Reality，XR)等业务中，不同PDU的优先级不同，并且不同PDU之间有依赖关系。
发明内容
本申请实施例提供一种参数配置方法，应用于第一通信节点，包括：
接收第二通信节点发送的分组数据单元PDU会话的帧格式；其中，所述PDU会话的帧格式包括下述指示信息至少之一：应用层数据包识别信息，应用层数据单元(Application Data Units，ADU)识别信息，服务质量QoS流的子流标识以及QoS流的子优先级。
本申请实施例提供一种参数配置方法，应用于第三通信节点，包括：
接收第一通信节点发送的配置信息；
其中，所述配置信息包含QoS流的子流标识或QoS流的子优先级；
所述配置信息包括如下至少之一：服务数据适配协议(Service Data Adaptation Protocol，SDAP)配置信息，无线承载配置信息，逻辑信道配置信息和无线连路控制配置信息。
本申请实施例提供一种参数配置方法，应用于第二通信节点，包括：
向第一通信节点发送PDU会话的帧格式，所述PDU会话的帧格式包括下述指示信息至少之一：应用层数据包识别信息，ADU识别信息，QoS流的子流标识以及QoS流的的子优先级。
本申请实施例提供一种通信设备，包括：通信模块，存储器，以及一个或多个处理器；
所述通信模块，配置为与其它通信节点之间进行通信交互；
所述存储器，配置为存储一个或多个程序；
当所述一个或多个程序被所述一个或多个处理器执行时，所述一个或多个处理器实现上述任一实施例所述的方法。
本申请实施例提供一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现上述任一实施例所述的方法。
附图说明
图1是一实施例提供的一种应用层数据单元、应用层数据包和网际互联协议(Internet Protocol，IP)包之间的配置关系图；
图2是一实施例提供的一种PDU会话的帧格式的配置示意图；
图3是本申请实施例提供的一种参数配置方法的流程图；
图4是本申请实施例提供的另一种参数配置方法的流程图；
图5是本申请实施例提供的又一种参数配置方法的流程图；
图6是本申请实施例提供的另一种PDU会话的帧格式的配置示意图；
图7是本申请实施例提供的一种QoS流中增加QoS子流的配置示意图；
图8是本申请实施例提供的另一种QoS流中增加QoS子流的配置示意图；
图9是本申请实施例提供的另一种PDU会话的帧格式的配置示意图；
图10是本申请实施例提供的一种基于开始传输指示同一ADU对应的PDU的配置示意图；
图11是本申请实施例提供的一种基于结束传输指示同一ADU对应的PDU的配置示意图；
图12是本申请实施例提供的又一种PDU会话的帧格式的配置示意图；
图13是本申请实施例提供的再一种PDU会话的帧格式的配置示意图；
图14是本申请实施例提供的再一种PDU会话的帧格式的配置示意图；
图15是本申请实施例提供的再一种PDU会话的帧格式的配置示意图；
图16是本申请实施例提供的再一种PDU会话的帧格式的配置示意图；
图17是本申请实施例提供的一种应用层数据单元中解码可容忍的丢包数的指示示意图；
图18是本申请实施例提供的另一种应用层数据单元中解码可容忍的丢包数的指示示意图；
图19是本申请实施例提供的一种逻辑信道组(Logical Channel Group，LCG)标识与QoS子流标识之间的配置关系图；
图20是本申请实施例提供的一种短缓存状态报告(Short Buffer Status Report，Short BSR)的介质访问控制层控制单元(Mediu Access Control Control Element，MAC CE)结构的示意图；
图21是本申请实施例提供的一种长缓存状态报告(Long Buffer Status Report，Long BSR)的MAC CE结构的示意图；
图22是本申请实施例提供的一种参数配置装置的结构框图；
图23是本申请实施例提供的另一种参数配置装置的结构框图；
图24是本申请实施例提供的又一种参数配置装置的结构框图；
图25是本申请实施例提供的一种通信设备的结构示意图。
具体实施方式
下文中将结合附图对本申请的实施例进行说明。以下结合实施例附图对本申请进行描述，所举实例仅用于解释本申请，并非用于限定本申请的范围。
如何识别用户面数据包(IP packets)与应用层数据包的关联关系，应用层数据包之间的关联关系，以及映射到同一QoS Flow的应用层数据包之间的不同优先级，是一个亟待解决的问题。
在NR网络中，业务的QoS参数是核心网通过控制面信令向基站配置的，是按照PDU Session--->QoS flow级别配置的。一个用户设备(User Equipment，UE)可以最多建立256个PDU Session，一个PDU Session可以最多包含64个QoS flow，而QoS参数是按QoS flow进行配置的。QoS参数包括：用户优先级信息(分配保留优先级(Allocation and Retention Priority，ARP))、保证比特速率(Guaranteed Bit Rate，GBR)信息(GBR QoS flow information)、第5代移动通信技术业务服务质量标识(5th Generation Mobile Communication Technology Quality of Service Identifier，5QI)描述信息(业务类型对应的5QI索引、业务优先级Priority、业务最大延迟(Packet Delay Budget，PDB)等)。
对于下行业务，每个用户面的PDU在对应的PDU通道(通用分组无线服务技术通道协议用户面通道(General Packet Radio Service Tunnelling Protocol–User Tunnel，GTP-U Tunnel))上传输，且在PDU的扩展头(extension header，也就是新空口无线接入网容器(New Radio Radio Access Network Container，NR RAN Container)或PDU Session Container)中携带服务质量流标识(Quality of Service Flow Identifier，QFI)指示，从而将PDU与QoS参数相关联，做到了 QoS Flow级别的PDU调度优先级区分。
对于上行业务，用户面的PDU与QoS Flow关联，基站可以将不同Qos flow映射到不同数据无线承载(Data Radio Bearer，DRB)上，不同DRB对应不同的LCG。UE在BSR请求中携带逻辑信道组标识(Logical Channel Group Identifier，LCG ID)，基站基于BSR信息分配上行调度资源，从而实现了QoS Flow级别的PDU调度优先级区分。
一个QoS flow只有一个QoS优先级，且不同QoS Flow的数据包之间没有关联关系。但是在XR等业务中，不同PDU可能优先级不同，但PDU之间有依赖关系，比如一个视频序列有多个I-frame，P-frame和B-frame，其中P-frame和B-frame的解码依赖于I-famre；而每个frame又由多个IP packets(PDU)组成。图1是一实施例提供的一种应用层数据单元、应用层数据包和IP包之间的配置关系图。如图1所示，一个应用层数据单元(视频编码单元)由12个视频帧(即应用层数据包/应用层数据帧)构成，12个视频帧包括I 1B 2B 3P 4B 5B 6P 7B 8B 9P 10B 11B 12(I帧(I 13)出现表示一个新的应用层数据单元开始)，每个视频帧又由多个IP包(即用户面数据包或PDU)构成(I 1帧由n个IP包I 11I 12...I 1n组成；B 2由m个IP包B 21B 22...B 2m组成...)。其中，IP数据包也可以是用户数据包协议(User Datagram Protocol，UDP)数据包或者以太网数据包。
图2是一实施例提供的一种PDU会话的帧格式的配置示意图。在实施例中，核心网向基站发送如图2所示的PDU会话的帧格式，PDU SESSION的帧格式是携带在GTP-U PDU的扩展头(extension header，也就是NR RAN Container或PDU Session Container)里，放在GTP-U Tunnel上传输的。
基站从该PDU SESSION的帧格式可以看出：PDU对应的QoS Flow Identifier和下行链路业务服务质量流标识序号(Down Link Quality of Service Flow Identifier Sequence Number，DL QFI Sequence Number)；基站基于S1应用协议(S1 Application Protocol，S1AP)接口的信令和NG应用协议(NG Application Protocol，NGAP)接口的信令可以知道QoS Flow Identifier对应的Priority Level。
但是基站无法识别IP packets(即用户面数据包)与应用层数据包(也可以称为应用层数据帧)的关联关系、应用层数据帧之间的关联关系，以及映射到同一QoS Flow的应用层数据帧之间的不同优先级。因此，如何对PDU SESSION的帧格式进行增强，是一个亟待解决的问题。
在一实施例中，图3是本申请实施例提供的一种参数配置方法的流程图。本实施例可以由第一通信节点执行。其中，第一通信节点为基站。如图3所示， 本实施例包括：S310-S320。
S310、接收第二通信节点发送的PDU会话的帧格式。
PDU会话的帧格式包括下述指示信息至少之一：应用层数据包识别信息，应用层数据单元ADU识别信息，QoS流的子流标识以及QoS流的子优先级。
在实施例中，应用层数据包识别信息用于指示用户面数据包所对应的应用层数据包信息。应用层数据包识别信息可以从不同维度对用户面数据包指示对应的应用层数据包信息。示例性地，可以从应用层数据包类型对应用层数据包信息进行指示，比如，应用层数据包类型包括：I帧数据包、B帧数据包和P帧数据包；也可以从应用层数据包的重要程度进行指示，比如，应用层数据包重要程度分为主包和次包。
在实施例中，ADU识别信息用于指示应用层数据单元的开始传输指示、结束传输指示、应用层数据单元序号和应用层数据单元所包含的用户面数据包总数量中的至少两个，并且，ADU识别信息还用于隐含指示ADU内应用层数据包越靠前优先级越高。
在实施例中，QoS流的子流标识指的是QoS流中所包含的每个QoS子流的标识；QoS流的子优先级指的是QoS流中所包含的每个QoS子流的优先级。在一实施例中，QoS流的子流标识和QoS流的子优先级可以采用QoS流子优先级表示，即QoS流子优先级中既包含QoS子流的标识，也包含QoS子流的优先级。
S320、根据PDU会话的帧格式确定同一QoS流中不同用户面数据包的调度优先级或资源分配权重。
在实施例中，第二通信节点通过用户面向第一通信节点发送PDU会话的帧格式，并且在PDU会话的帧格式中包含应用层数据包识别信息，ADU识别信息，QoS流的子流标识以及QoS流的子优先级中的至少之一，以使第一通信节点根据PDU会话的帧格式识别用户面数据包与应用层数据包的关联关系、不同应用层数据包之间的关联关系，以及映射到同一QoS流的应用层数据包之间的不同优先级，从而第一通信节点可以按照该PDU会话的帧格式确定同一QoS流中不同用户面数据包的调度优先级或资源分配权重，从而可以按照调度优先级和分配的调度资源进行BSR的上报。
在一实施例中，应用于第一通信节点的参数配置方法，还包括：接收第二通信节点发送的QoS子流配置信息，QoS子流配置信息包含QoS流的子优先级和/或QoS流的子流标识。
在实施例中，在第一通信节点接收第二通信节点发送的PDU会话的帧格式之前，第一通信节点通过控制面信令接收第二通信节点发送的QoS子流配置信 息。在QoS子流配置信息中携带QoS流的子优先级，或者，QOS流的子优先级和QoS流的子流标识。在实施例中，在QoS子流配置信息中只携带QoS流的子优先级的情况下，QoS流的子优先级既可以表征QoS子流的优先级，也可以表征QoS子流的标识。
在一实施例中，QoS流配置信息或QoS子流配置信息包括下述之一：应用层数据单元中可容忍的最大丢包总数；应用层数据单元中可容忍的最大连续丢包总数，预定义时间段内可容忍的最大丢包总数，预定义时间段内可容忍的最大连续丢包总数，预定义时间段内可容忍的最大应用层数据单元丢失总数，预定义时间段内可容忍的最大连续应用层数据单元丢失总数。所述丢包总数为丢失的用户面数据包总数或丢失的应用层数据包总数。在实施例中，第二通信节点通过控制面信令向第一通信节点发送QoS流配置信息，或者，QoS子流配置信息。在一实施例中，在第二通信节点通过控制面信令向第一通信节点发送QoS流配置信息的情况下，在QoS流配置信息中携带应用层数据单元中可容忍的最大丢包总数，或者应用层数据单元中可容忍的最大连续丢包总数，预定义时间段内可容忍的最大丢包总数，预定义时间段内可容忍的最大连续丢包总数，预定义时间段内可容忍的最大应用层数据单元丢失总数，预定义时间段内可容忍的最大连续应用层数据单元丢失总数。所述丢包总数为丢失的用户面数据包总数或丢失的应用层数据包总数。在一实施例中，在第二通信节点通过控制面信令向第一通信节点发送QoS子流配置信息的情况下，在QoS子流配置信息中携带应用层数据单元中可容忍的最大丢包总数，或者应用层数据单元中可容忍的最大连续丢包总数，预定义时间段内可容忍的最大丢包总数，预定义时间段内可容忍的最大连续丢包总数，预定义时间段内可容忍的最大应用层数据单元丢失总数，预定义时间段内可容忍的最大连续应用层数据单元丢失总数。所述丢包总数为丢失的用户面数据包总数或丢失的应用层数据包总数。
在一实施例中，不同优先级的应用层数据包映射到同一个QoS流；PDU会话的帧格式至少包括：ADU识别信息。在实施例中，在不同优先级的应用层数据包映射到同一个QoS流中时，可以在PDU会话的帧格式中携带ADU识别信息，以指示每个应用层数据包所对应的应用层数据单元的开始传输指示和结束传输指示，进而可以确定应用层数据单元内每个应用层数据包的优先级。其中，ADU识别信息隐含指示每个ADU内应用层数据包越靠前优先级越高。在一实施例中，ADU识别信息的指示位可以为一个比特(bit)，也可以为两个bit。
在一实施例中，采用ADU识别信息指示至少两个级别的应用层数据单元。在实施例中，可以对ADU识别信息中所携带的参数进行组合、复用和多级包含，以指示多个级别的应用层数据单元。示例性地，假设采用ADU识别信息指示两个级别的应用层数据单元，一级应用层数据单元可以为一个视频流，二级应用 层数据单元可以为一个视频帧。
在一实施例中，ADU识别信息至少包括下述之一：应用层数据单元的开始传输指示；应用层数据单元的结束传输指示。在实施例中，应用层数据单元的开始传输指示，用于指示同一个应用层数据单元中的第一个应用层数据包所在的位置；应用层数据单元的结束传输指示，用于指示同一个应用层数据单元中的最后一个应用层数据包所在的位置。
在一实施例中，ADU识别信息至少包括下述之一：应用层数据单元序号；应用层数据单元的结束传输指示。在实施例中，应用层数据单元序号用于指示用户面数据包是否对应同一个应用层数据单元，同一个QoS流中相同序号的用户面数据包对应同一个应用层数据单元，不同序号的用户面数据包对应不同的应用层数据单元。
在一实施例中，ADU识别信息至少包括下述之一：应用层数据单元的开始传输指示；应用层数据单元所包含的用户面数据包总数量。在实施例中，从应用层数据单元的开始传输指示所指示的用户面数据包开始，连续应用层数据单元所包含的用户面数据包总数量的用户面数据包均属于同一个应用层数据单元。
在一实施例中，不同QoS优先级的应用层数据包映射到不同的QoS流；PDU会话的帧格式包括下述之一：关联的QoS流标识QFI和关联的下行QFI序号。
所述关联的QoS流标识QFI和关联的下行QFI序号用于表征本PDU会话帧与所述关联的QoS流标识QFI和关联的下行QFI序号之间存在关联关系、依赖关系、补充关系、主辅关系、从属关系或者时序关系。
在一实施例中，PDU会话的帧格式包括下述之一：应用层数据单元中可容忍的最大丢包总数；应用层数据单元中可容忍的最大连续丢包总数。所述丢包总数为丢失的用户面数据包总数或丢失的应用层数据包总数。在实施例中，第二通信节点可以通过用户面向第一通信节点发送PDU会话的帧格式，并在PDU会话的帧格式中携带应用层数据单元中可容忍的最大丢包总数，或者应用层数据单元中可容忍的最大连续丢包总数。所述丢包总数为丢失的用户面数据包总数或丢失的应用层数据包总数。
在一实施例中，PDU会话的帧格式还包括：应用层数据单元的开始传输指示；应用层数据单元所包含的用户面数据包总数量。在实施例中，应用层数据单元所包含的用户面数据包总数量指的是一个应用层数据单元中一共所包含的用户面数据包数量，即IP包数量，也可以称为PDU数量。
在一实施例中，应用层数据包识别信息中也可以包括：应用层数据包序号、 应用层数据包的开始传输指示、应用层数据包的结束传输指示、应用层数据包所包含的用户面数据包总数量中的至少两个。对应用层数据包识别信息中的每个参数的解释同ADU识别信息中对应参数的解释，只是将应用层数据单元更换为应用层数据包。
在一实施例中，不同优先级的应用层数据包映射到同一QoS流；将同一QoS流中不同的子流标识或子优先级映射到不同专用无线承载DRB标识、不同逻辑信道(Logical Channel，LC)标识、或不同的逻辑信道组LCG标识上。在实施例中，第一通信节点将同一QoS流中不同的子流标识或子优先级映射到不同LC标识上，再将不同LC标识映射到不同LCG标识上，进而可以实现将同一QoS流中具有不同优先级的QoS子流或子优先级映射到不同LCG标识上。在实施例中，在不同优先级的应用层数据包映射到同一QoS流的情况下，第一通信节点可以将同一QoS流中不同的子流标识或子优先级映射到不同DRB标识、不同LC标识、或不同的LCG标识上，以使第三通信节点按照不同的子流标识或子优先级进行BSR上报。
在一实施例中，将同一QoS流中不同的子流标识或子优先级映射到不同DRB标识、不同LC标识、或不同的LCG标识上，包括：QoS流的子流标识或QoS流的子优先级包含在发送给第三通信节点的以下至少之一的配置信息中：服务数据适配协议SDAP配置信息，无线承载配置信息，逻辑信道配置信息、无线链路控制配置信息。
QoS流的子流标识或QoS流的子优先级用于将同一QoS流的用户面数据包映射到不同的逻辑信道上。
在一实施例中，图4是本申请实施例提供的另一种参数配置方法的流程图。本实施例可以由第三通信节点执行。其中，第三通信节点为用户设备。如图4所示，本实施例包括：S410-S420。
S410、接收第一通信节点发送的配置信息。
S420、根据配置信息上报缓冲状态报告BSR。
配置信息包含QoS流的子流标识或QoS流的子优先级；配置信息包括如下至少之一：SDAP配置信息，无线承载配置信息，逻辑信道配置信息、无线连路控制配置信息。
在一实施例中，QoS流的子流标识或QoS流的子优先级用于将同一QoS流的用户面数据包映射到不同的逻辑信道上。在实施例中，第一通信节点将同一QoS流中不同的子流标识或子优先级映射到不同LC标识上，再将不同LC标识 映射到不同LCG标识上，进而可以实现将同一QoS流中具有不同优先级的QoS子流或子优先级映射到不同LCG标识上。第三通信节点基于LCG标识进行BSR请求时，第一通信节点可以对同一QoS流中具有不同优先级的QoS子流或子优先级进行BSR区分。
在此需要说明的是，应用于第三通信节点的参数配置方法中对每个参数的解释，可参见上述实施例中应用于第一通信节点的参数配置方法中对应参数的描述，在此不再一一赘述。
在一实施例中，图5是本申请实施例提供的又一种参数配置方法的流程图。本实施例可以由第二通信节点执行。其中，第二通信节点为核心网。如图5所示，本实施例包括：S510。
S510、向第一通信节点发送PDU会话的帧格式，PDU会话的帧格式包括下述指示信息至少之一：应用层数据包识别信息，ADU识别信息，QoS流的子流标识以及QoS流的的子优先级。
在一实施例中，应用于第二通信节点的参数配置方法，还包括：向第一通信节点发送QoS子流配置信息，QoS子流配置信息包含QoS流的子优先级和/或QoS流的子流标识。
在一实施例中，QoS流配置信息或QoS子流配置信息包括下述之一：应用层数据单元中可容忍的最大丢包总数，应用层数据单元中可容忍的最大连续丢包总数，预定义时间段内可容忍的最大丢包总数，预定义时间段内可容忍的最大连续丢包总数，预定义时间段内可容忍的最大应用层数据单元丢失总数，预定义时间段内可容忍的最大连续应用层数据单元丢失总数。所述丢包总数为丢失的用户面数据包总数或丢失的应用层数据包总数。
在一实施例中，不同优先级的应用层数据包映射到同一个QoS流；PDU会话的帧格式至少包括下述之一：ADU识别信息。
在一实施例中，采用ADU识别信息指示至少两个级别的应用层数据单元。
在一实施例中，ADU识别信息至少包括下述之一：应用层数据单元的开始传输指示；应用层数据单元的结束传输指示。
在一实施例中，ADU识别信息至少包括下述之一：应用层数据单元序号；应用层数据单元的结束传输指示。
在一实施例中，ADU识别信息至少包括下述之一：应用层数据单元的开始传输指示；应用层数据单元所包含的用户面数据包总数量。
在一实施例中，不同QoS优先级的应用层数据帧映射到不同的QoS流；PDU会话的帧格式包括下述之一：关联的QoS流标识QFI和关联的下行QFI序号。
所述关联的QoS流标识QFI和关联的下行QFI序号用于表征本PDU会话帧与所述关联的QoS流标识QFI和关联的下行QFI序号之间存在存在关联关系、依赖关系、补充关系、主辅关系、从属关系或者时序关系。
在一实施例中，PDU会话的帧格式包括下述之一：应用层数据单元中可容忍的最大丢包总数；应用层数据单元中可容忍的最大连续丢包总数。其中，丢包总数为丢失的用户面数据包总数或丢失的应用层数据包总数。
在一实施例中，PDU会话的帧格式还包括：应用层数据单元的开始传输指示；应用层数据单元所包含的用户面数据包总数量。
在一实施例中，不同优先级的应用层数据包映射到同一QoS流；将同一QoS流中不同的子流标识或子优先级映射到不同专用无线承载DRB标识、不同逻辑信道LC标识、或不同的逻辑信道组LCG标识上。
在一实施例中，将同一QoS流中不同的子流标识或子优先级映射到不同专用无线承载DRB标识、不同逻辑信道LC标识、或不同的逻辑信道组LCG标识上，包括：QoS流的子流标识或QoS流的子优先级包含在发送给第三通信节点的以下至少之一的配置信息中：服务数据适配协议SDAP配置信息，无线承载配置信息，逻辑信道配置信息，以及无线链路控制配置信息。
QoS流的子流标识或QoS流的子优先级用于将同一QoS流的用户面数据包映射到不同的逻辑信道上。
在此需要说明的是，应用于第二通信节点的参数配置方法中对每个参数的解释，可参见上述实施例中应用于第一通信节点的参数配置方法中对应参数的描述，在此不再一一赘述。
在一实施例中，不同优先级的应用层数据包映射到同一QoS Flow，在PDU会话的帧格式内引入应用层数据包识别信息或优先级指示。其中，应用层数据识别信息为应用层数据包类型(Application packet Type)。以第一通信节点为基站为例，图6是本申请实施例提供的另一种PDU会话的帧格式的配置示意图。如图6所示，PDU SESSION的帧格式中携带如下至少之一：应用层数据包类型、应用层数据包的子优先级(Application packet sub-Priority)、应用层数据包的子流标识(Application packet sub-Flow ID)。其中，应用层数据包类型(Application packet Type)或应用层数据包的优先级(Application packet Priority)用于基站识别PDU(即上述实施例中的用户面数据包，或IP Packets)在传输过程中的重要 程度，从而识别出同一QoS flow下不同PDU的调度优先级或资源分配的权重。
基于应用层数据包类型，基站可以判断PDU对应的应用层数据包类型，从而决定该PDU的调度优先级、可靠性要求高低或资源分配的权重；应用层数据包类型可以指示该IP包对应的应用层数据包类型，比如：指示视频流里I帧数据包、B帧数据包、以及P帧数据包；或者指示数据包是主包还是次包，用于基站识别数据包的主要程度。
基于应用层数据包的子优先级或应用层数据包的子流信息，基站可以判断PDU对应的应用层数据包的优先级，从而决定该PDU的调度优先级、可靠性要求或资源分配的权重。
核心网到基站的S1AP/NGAP信令里的QoS flow里包含的应用层数据包的子优先级(Application packet sub-Priority)和/或应用层数据包的子流标识(Application packet sub-Flow ID)用于基站为同一QoS flow下不同sub-Priority的数据包配置不同优先级的资源。图7是本申请实施例提供的一种QoS流中增加QoS子流的配置示意图；图8是本申请实施例提供的另一种QoS流中增加QoS子流的配置示意图。如图7所示，每个QoS Flow下包含多个QoS sub-flow，每个QoS sub-Flow包含：QoS流的子流标识(QoS sub-flow ID)和QoS流的子优先级(QoS sub-flow Priority)；或者，每个QoS sub-Flow包含QoS流子优先级(QoS sub-Priority)。QoS Flow里的QoS sub-flow也可以不体现，只体现：QoS flow下包含多个QoS sub-Priority，如图8所示，PDU会话的帧格式中也只包含QoS sub-Priority(即图6中)；如果QoS Flow里体现了QoS sub-flow，则PDU Format里也包含QoS sub-flow ID和QoS sub-flow Priority；或者，PDU Format里包含QoS sub-Priority。
QoS sub-flow相关的QoS参数可以基于QoS Flow的QoS参数差分定义，比如：QoS sub-flow相关的QOS参数中只包含与QoS Flow的QoS参数里取值不同的参数。
对于QoS优先级：基站基于QoS flow的优先级和QoS sub-flow的优先级映射逻辑信道优先级。比如QoS的绝对优先级＝QoS flow的优先级+QoS sub-flow的优先级。
在一实施例中，不同优先级的应用层数据包映射到同一QoS Flow，PDU会话的帧格式内引入ADU识别信息，ADU识别信息用于隐含指示ADU内数据包越靠前优先级越高。
图9是本申请实施例提供的另一种PDU会话的帧格式的配置示意图。PDU 会话的帧格式中携带如下至少之一：应用层数据单元的开始传输指示(Application Data Unit start mark)、结束传输指示(Application Data Unit end mark)。其中，ADU识别信息的指示位可占用2bit，指示位的四个取值分别表示如下至少之一：指示位不存在、一个应用层数据单元传输开始、一个应用层数据单元传输结束、一个应用层数据单元只有一个PDU。比如：当2bit为’00’时，表示指示位不存在(不指示应用层数据单元的开始与结束)，无法判断出应用层数据单元的开始与结束，或默认一个应用层数据单元对应一个PDU。
当2bit为’01’时，表示一个应用层数据单元的传输开始；当2bit为’10’时，表示一个应用层数据单元的传输结束；当2bit为’11’时，表示一个应用层数据单元只有一个PDU。
在实施例中，从一个应用层数据单元传输开始指示所在比特的DL QFI Sequence Number 1，到一个应用层数据单元传输结束指示所在比特的DL QFI Sequence Number 2，同一QoS flow下DL QFI Sequence Number在[DL QFI Sequence Number 1，DL QFI Sequence Number 2]区间内的所有PDU对应同一应用层数据单元。ADU识别信息可以隐含：同一应用层数据单元内的数据帧或PDU，序号越靠前越重要(调度优先级越高，可靠性要求越强)。
在一实施例中，ADU识别信息的指示位可占用1bit。在该bit为1的情况下，表示同一QoS flow下的应用层数据单元传输开始指示(start mark)或结束传输指示(end mark)(其中，新的开始传输指示就是旧的结束传输指示)。
在一实施例中，图10是本申请实施例提供的一种基于开始传输指示，指示同一ADU对应的PDU的配置示意图。在实施例中，1bit取值为1，表示一个应用层数据单元开始传输指示(start mark)，直到同一QoS flow下1bit再次为1之前，所有PDU对应一个应用层数据单元。
如图10所示，在PDU1里出现一次StartMark＝1,后续最近一次出现StartMark＝1的是PDU m+1，则PDU1，PDU2，...，PDU m对应同一应用层数据单元。
在一实施例中，图11是本申请实施例提供的一种基于结束传输指示，指示同一ADU对应的PDU的配置示意图。在实施例中，1bit取值为1，表示一个应用层数据单元结束传输指示(End mark)；该End mark对应的PDU及之前同一QoS flow下End mark＝0的连续PDU对应一个应用层数据单元。
如图11所示，在PDU m+1里出现一次EndMark＝1,该PDU及之前End mark＝0的连续PDU(PDU2，...，PDU m，PDU m+1)对应一个应用层数据单元。
在一实施例中，图12是本申请实施例提供的又一种PDU会话的帧格式的配置示意图。如图12所示，PDU会话的帧格式中携带如下至少之一：应用层数据单元序号(Application Data Unit Sequence Number)和应用层数据单元的结束传输指示(End mark)。其中，应用层数据单元序号用于基站识别PDU是否对应于同一应用层数据单元，同一QoS flow下相同应用层数据单元序号的PDU对应同一应用层数据单元；不同应用层数据单元序号的PDU对应不同应用层数据单元。应用层数据单元的结束传输指示用于指示同一应用层数据单元对应的最后一个PDU。
基于应用层数据单元序号，基站可以判断是否一个新的应用层数据单元的PDU开始传输以及不同PDU是否对应同一应用层数据单元；基于应用层数据单元的结束指示，基站可以判断一个应用层数据单元的PDU传输是否结束。例如图12中的End mark取值为1表示一个应用层数据单元的PDU传输结束。
从一个新的应用层数据单元的PDU开始传输，到一个应用层数据单元的PDU传输结束，同一QoS flow下相同应用层数据单元序号的PDU对应一个完整的应用层数据单元。
在一实施例中，也可以用当前PDU的应用层数据单元序号与后一个PDU的序号是否相同来识别当前PDU对应的应用层数据单元是否结束。如果一个新的应用层数据单元开始传输，隐含表示上一个应用层数据单元传输结束。此时不需要应用层数据单元的结束指示。
在一实施例中，图13是本申请实施例提供的再一种PDU会话的帧格式的配置示意图。如图13所示，在PDU会话的帧格式中携带如下至少之一：应用层数据单元开始传输指示(Start mark)、应用层数据单元的所包含的用户面数据包总数量(Packet Total Number in one Application Data Unit)。其中，从包含应用层数据单元开始标识的数据包开始，连续应用层数据单元的包含的用户面数据包总数量的数据包属于同一应用层数据单元。
在一实施例中，图14是本申请实施例提供的再一种PDU会话的帧格式的配置示意图。本实施例可以对图9、12和13进行组合、复用、多级包含来表示多级的应用层数据单元，比如：一级应用层数据单元为一个视频流(即应用层数据单元)，二级应用层数据单元为一个视频帧(即应用层数据帧/应用层数据包)，采用图12的配置方法进行二级包含，结果为图14所示(其中：Fist Level 和Second Level所在比特位置只是示例，实际占用比特数和占用比特位置可能会有差异，比如Fist Level和Second Level相关参数都放在PDU的扩展比特位置，或者引入新的PDU格式)。
如图14所示，对二级的应用层数据单元进行示例说明：第一级应用层数据单元表征视频流；第二级应用层数据单元表征视频帧。对应图1中的信息，可以填写为如下结构：
第一IP包：
First level End mark：0
First level Application Data Unit Sequence Number：1
Second level End mark：0
Second level Application Data Unit Sequence Number：1(I1帧开始)
第二IP包：
First level End mark：0
First level Application Data Unit Sequence Number：1
Second level End mark：0
Second level Application Data Unit Sequence Number：1
...
第n个IP包：
First level End mark：0
First level Application Data Unit Sequence Number：1
Second level End mark：1(I1帧结束)
Second level Application Data Unit Sequence Number：1
第n+1个IP包：
First level End mark：0
First level Application Data Unit Sequence Number：1
Second level End mark：0
Second level Application Data Unit Sequence Number：2(B2帧开始)
第n+2个IP包：
First level End mark：0
First level Application Data Unit Sequence Number：1
Second level End mark：0
Second level Application Data Unit Sequence Number：2
...
第n+m个IP包：
First level End mark：0
First level Application Data Unit Sequence Number：1
Second level End mark：1(B2帧结束)
Second level Application Data Unit Sequence Number：2
第n+m+1个IP包：
First level End mark：0
First level Application Data Unit Sequence Number：1
Second level End mark：0
Second level Application Data Unit Sequence Number：3(B3帧结束)
在一实施例中，不同QoS Flow的应用层数包帧映射到不同QoS flow，PDU会话的帧格式内引入QoS flow及PDU序号的依赖关系。
图15是本申请实施例提供的再一种PDU会话的帧格式的配置示意图。如图15所示，关联的QoS流标识QFI(Associated QoS Flow Identifier)和关联的下行QFI序号(Associated DL QFI Sequence Number)用于表征该PDU或该PDU对应应用层数据单元的解码与QoS Flow Associated QoS Flow Identifier和Associated DL QFI Sequence Number对应的PDU或对应PDU的应用层数据单元有关联关系、依赖关系、补充关系、主辅关系、从属关系或者时序关系；和/或用于表征该PDU与关联的PDU属于同一应用层消息，属于同一应用层数据单元或者属于同一类型的数据包。
比如只有解出QoS Flow Associated QoS Flow Identifier以及Associated DL QFI Sequence Number对应的PDU或对应PDU的应用层数据单元，才可以解出该PDU或该PDU对应应用层数据单元。
在一实施例中，图16是本申请实施例提供的再一种PDU会话的帧格式的 配置示意图。在PDU会话的帧格式中携带应用层数据单元中解码可容忍的丢包数。其中，应用层数据单元中解码可容忍的丢包数包括：应用层数据单元解码可容忍的最大丢包总数或最大连续丢包总数。所述丢包总数为丢失的用户面数据包总数或丢失的应用层数据包总数。如图16所示，PDU会话的帧格式中携带下述之一：应用层数据单元中可容忍的最大丢包总数以及应用层数据单元中可容忍的最大连续丢包总数。PDU会话的帧格式中还可以包括：应用层数据单元的开始传输指示以及应用层数据单元所包含的用户面数据包总数量。所述丢包总数为丢失的用户面数据包总数或丢失的应用层数据包总数。
在实施例中，应用层数据单元中解码可容忍的丢包数可通过核心网到基站的S1AP/NGAP信令的QoS flow包含的可容忍的丢包数指示，或者通过PDU格式里包含的可容忍的丢包数指示。
本实施例中，图16中的Maximal Lost packets tolerable可以指示ADU中可容忍的丢包总数量或可容忍的连续丢包总数量，如果丢包数大于Maximal Lost packets tolerable，则不满足应用层需求(比如导致应用层解码失败)。如果从StartMark标识的数据包开始，在Packet Total Number in one Application Data Unit的数据包内，丢失的数据包数目快要达到Maximal Lost packets tolerable时，则提高后续数据包传输的可靠性(比如激活PDCP Duplication或提高发射功率)；如果从Start Mark标识的数据包开始，在Packet Total Number in one Application Data Unit的数据包内，丢失的数据包数目达到了Maximal Lost packets tolerable时，则丢弃Packet Total Number in one Application Data Unit的数据包内未传输的数据包。
Maximal Lost packets tolerable可以基于应用层数据单元定义(比如图14中的第一级应用层数据单元)，也可以基于数据包类型进行定义(比如图14中的第二级应用层数据单元)。
在一实施例中，图17是本申请实施例提供的一种应用层数据单元中解码可容忍的丢包数的指示示意图；图18是本申请实施例提供的另一种应用层数据单元中解码可容忍的丢包数的指示示意图。核心网到基站的S1AP或NGAP信令的QoS流中所包含的应用层数据单元中解码容忍的丢包数，如图17所示，QoS子流中包含每个应用层数据单元中可容忍的最大丢包总数或最大连续丢包总数；如图18所示，QoS流中包含每个应用层数据单元中可容忍的最大丢包总数或最大连续丢包总数。
在一实施例中，应用层数据包识别信息中也可以包括：应用层数据包序号、应用层数据包的开始传输指示、应用层数据包的结束传输指示以及应用层数据 包所包含的用户面数据包总数量中的至少两个。在此需要说明的是，上述实施例中，对应用层数据包识别信息中的每个参数的解释同ADU识别信息中对应参数的描述，只是将应用层数据单元更换为应用层数据包。并且，上述实施例中对ADU识别信息的附图也适用于应用层数据包识别信息，在此不再一一赘述。
在一实施例中，图19是本申请实施例提供的一种LCG标识与QoS子流标识之间的配置关系图。本实施例以第一通信节点为基站，第三通信节点为UE为例，对不同优先级的数据帧映射到同一QoS Flow时，BSR优先级的区分进行说明。如图19所示，基站将同一QoS Flow里具有不同priority的QoS Sub-flow ID或sub-priority映射到不同LC ID上，再将不同LC ID映射到不同LCG ID，进而可以实现将同一QoS Flow里具有不同priority的QoS Sub-flow ID或sub-priority映射到不同LCG ID上。
在QoS映射时，SDAP映射时考虑了QoS Sub-Flow ID、SDAP与无线链路控制承载配置(Radio Link Control-BearerConfig，RLC-BearerConfig)同时与DRB相关联，所以QoS Sub-Flow ID也映射到RLC-BearerConfig上；而每个RLC-BearerConfig关联到一个LCG。
UE基于LCG ID进行BSR请求的情况下，可以对同一QoS Flow里具有不同priority的QoS Sub-flow ID或sub-priority进行BSR区分。
在一实施例中，BSR请求中不仅体现了QoS flow的优先级，也可以体现QoS sub-flow的优先级。
在一实施例中，不同priority的QoS Sub-flow ID或sub-priority也可以是图6所示的应用层数据包类型，BSR中还可以体现应用层数据包类型。
在一实施例中，图20是本申请实施例提供的一种Short BSR的MAC CE结构的示意图。如图20所示，在一个Short BSR中包含LCG标识和缓冲数据量大小值(Buffer Size)。
在一实施例中，图21是本申请实施例提供的一种Long BSR的MAC CE结构的示意图。如图21所示，在一个Short BSR中包含多个LCG标识和每个LCG标识对应的缓冲数据量大小值(Buffer Size)。
在一实施例中，图22是本申请实施例提供的一种参数配置装置的结构框图。本实施例应用于第一通信节点。如图22所示，本实施例中的参数配置装置包括：第一接收器2210和确定模块2220。
第一接收器2210，配置为接收第二通信节点发送的分组数据单元PDU会话的帧格式；其中，PDU会话的帧格式包括下述指示信息至少之一：应用层数据包识别信息，应用层数据单元ADU识别信息，服务质量QoS流的子流标识以及QoS流的子优先级；确定模块2220，配置为根据PDU会话的帧格式确定同一QoS流中不同用户面数据包的调度优先级或资源分配权重。
在一实施例中，应用于第一通信节点的参数配置装置，还包括：第二接收器，配置为接收第二通信节点发送的QoS子流配置信息，QoS子流配置信息包含QoS流的子优先级和/或QoS流的子流标识。
在一实施例中，QoS流配置信息或QoS子流配置信息包括下述之一：应用层数据单元中可容忍的最大丢包总数，应用层数据单元中可容忍的最大连续丢包总数，预定义时间段内可容忍的最大丢包总数，预定义时间段内可容忍的最大连续丢包总数，预定义时间段内可容忍的最大应用层数据单元丢失总数，和预定义时间段内可容忍的最大连续应用层数据单元丢失总数。
在一实施例中，不同优先级的应用层数据包映射到同一个QoS流；PDU会话的帧格式至少包括：ADU识别信息。
在一实施例中，采用ADU识别信息指示至少两个级别的应用层数据单元。
在一实施例中，ADU识别信息至少包括下述之一：应用层数据单元的开始传输指示；应用层数据单元的结束传输指示。
在一实施例中，ADU识别信息至少包括下述之一：应用层数据单元序号；应用层数据单元的结束传输指示。
在一实施例中，ADU识别信息至少包括下述之一：应用层数据单元的开始传输指示；应用层数据单元所包含的用户面数据包总数量。
在一实施例中，不同QOS优先级的应用层数据包映射到不同的QoS流；PDU会话的帧格式包括下述之一：关联的QoS流标识QFI和关联的下行QFI序号。
所述关联的QoS流标识QFI和关联的下行QFI序号用于表征本PDU会话帧与所述关联的QoS流标识QFI和关联的下行QFI序号之间存在关联关系、依赖关系、补充关系、主辅关系、从属关系或者时序关系。
在一实施例中，PDU会话的帧格式包括下述之一：应用层数据单元中可容忍的最大丢包总数；应用层数据单元中可容忍的最大连续丢包总数。
在一实施例中，PDU会话的帧格式还包括：应用层数据单元的开始传输指示；应用层数据单元所包含的用户面数据包总数量。
在一实施例中，不同优先级的应用层数据包映射到同一QoS流；将同一QoS 流中不同的子流标识或子优先级映射到不同专用数据无线承载DRB标识、不同逻辑信道LC标识、或不同的逻辑信道组LCG标识上。
在一实施例中，将同一QoS流中不同的子流标识或子优先级映射到不同专用DRB标识、不同LC标识、或不同的LCG标识上，包括：将QoS流的子流标识或QoS流的子优先级包含在发送给第三通信节点的以下至少之一的配置信息中：服务数据适配协议SDAP配置信息，无线承载配置信息，逻辑信道配置信息、无线链路控制配置信息；QoS流的子流标识或QoS流的子优先级用于将同一QoS流的用户面数据包映射到不同的逻辑信道上。
本实施例提供的参数配置装置设置为实现图3所示实施例的参数配置方法，本实施例提供的参数配置装置实现原理和技术效果类似，此处不再赘述。
在一实施例中，图23是本申请实施例提供的另一种参数配置装置的结构框图。本实施例可以由第三通信节点执行。其中，第三通信节点为用户设备。如图23所示，本实施例中的参数配置装置包括：第三接收器2310和上报模块2320。
第三接收器2310，配置为接收第一通信节点发送的配置信息；上报模块2320，配置为根据配置信息上报缓冲状态报告BSR；其中，配置信息包含QoS流的子流标识或QoS流的子优先级；配置信息包括如下至少之一：SDAP配置信息，无线承载配置信息，逻辑信道配置信息，和无线连路控制配置信息。
在一实施例中，QoS流的子流标识或QoS流的子优先级用于将同一QoS流的用户面数据包映射到不同的逻辑信道上。
本实施例提供的参数配置装置设置为实现图4所示应用于第三通信节点的实施例的参数配置方法，本实施例提供的参数配置装置实现原理和技术效果类似，此处不再赘述。
在一实施例中，图24是本申请实施例提供的又一种参数配置装置的结构框图。本实施例可以由第二通信节点执行。其中，第二通信节点为核心网。如图24所示，本实施例包括：第一发送器2410。
第一发送器2410，配置为向第一通信节点发送PDU会话的帧格式，PDU会话的帧格式包括下述指示信息至少之一：应用层数据包识别信息，ADU识别信息，QoS流的子流标识以及QoS流的的子优先级。
在一实施例中，应用于第二通信节点的参数配置装置，还包括：第二发送器，配置为向第一通信节点发送QoS子流配置信息，QoS子流配置信息包含QoS 流的子优先级和/或QoS流的子流标识。
在一实施例中，QoS流配置信息或QoS子流配置信息包括下述之一：应用层数据单元中可容忍的最大丢包总数，应用层数据单元中可容忍的最大连续丢包总数，预定义时间段内可容忍的最大丢包总数，预定义时间段内可容忍的最大连续丢包总数，预定义时间段内可容忍的最大应用层数据单元丢失总数，预定义时间段内可容忍的最大连续应用层数据单元丢失总数。
在一实施例中，不同优先级的应用层数据包映射到同一个QoS流；PDU会话的帧格式至少包括：ADU识别信息。
在一实施例中，采用ADU识别信息指示至少两个级别的应用层数据单元。
在一实施例中，ADU识别信息至少包括下述之一：应用层数据单元的开始传输指示；应用层数据单元的结束传输指示。
在一实施例中，ADU识别信息至少包括下述之一：应用层数据单元序号；应用层数据单元的结束传输指示。
在一实施例中，ADU识别信息至少包括下述之一：应用层数据单元的开始传输指示；应用层数据单元所包含的用户面数据包总数量。
在一实施例中，不同QoS优先级的应用层数据帧映射到不同的QoS流；PDU会话的帧格式包括下述之一：关联的QoS流标识QFI和关联的下行QFI序号。
所述关联的QoS流标识QFI和关联的下行QFI序号用于表征本PDU会话帧与所述关联的QoS流标识QFI和关联的下行QFI序号之间存在关联关系、依赖关系、补充关系、主辅关系、从属关系或者时序关系。
在一实施例中，PDU会话的帧格式包括下述之一：应用层数据单元中可容忍的最大丢包总数；应用层数据单元中可容忍的最大连续丢包总数。
在一实施例中，PDU会话的帧格式还包括：应用层数据单元的开始传输指示；应用层数据单元所包含的用户面数据包总数量。
在一实施例中，不同优先级的应用层数据包映射到同一QoS流；将同一QoS流中不同的子流标识或子优先级映射到不同专用无线承载DRB标识、不同逻辑信道LC标识、或不同的逻辑信道组LCG标识上。
在一实施例中，将同一QoS流中不同的子流标识或子优先级映射到不同专用DRB标识、不同LC标识、或不同的LCG标识上，包括：QoS流的子流标识或QoS流的子优先级包含在发送给第三通信节点的以下至少之一的配置信息中：服务数据适配协议SDAP配置信息，无线承载配置信息，逻辑信道配置信息，以及无线链路控制配置信息；QoS流的子流标识或QoS流的子优先级用于 将同一QoS流的用户面数据包映射到不同的逻辑信道上。
本实施例提供的参数配置装置设置为实现图5所示应用于第二通信节点的实施例的参数配置方法，本实施例提供的参数配置装置实现原理和技术效果类似，此处不再赘述。
图25是本申请实施例提供的一种通信设备的结构示意图。如图25所示，本申请提供的设备，包括：处理器2510、存储器2520和通信模块2530。该设备中处理器2510的数量可以是一个或者多个，图25中以一个处理器2510为例。该设备中存储器2520的数量可以是一个或者多个，图25中以一个存储器2520为例。该设备的处理器2510、存储器2520和通信模块2530可以通过总线或者其他方式连接，图25中以通过总线连接为例。在该实施例中，该设备为可以为基站。
存储器2520作为一种计算机可读存储介质，可设置为存储软件程序、计算机可执行程序以及模块，如本申请任意实施例的设备对应的程序指令/模块(例如，参数配置装置中的第一接收器和确定模块)。存储器2520可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据设备的使用所创建的数据等。此外，存储器2520可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器2520可包括相对于处理器2510远程设置的存储器，这些远程存储器可以通过网络连接至设备。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及互联网、企业内部网、局域网、移动通信网的组合。
通信模块2530，配置为与其它通信节点进行通信交互。
在通信设备为第一通信节点的情况下，上述提供的设备可设置为执行上述任意实施例提供的应用于第一通信节点的参数配置方法，具备相应的功能和效果。
在通信设备为第二通信节点的情况下，上述提供的设备可设置为执行上述任意实施例提供的应用于第二通信节点的参数配置方法，具备相应的功能和效果。
在通信设备为第三通信节点的情况下，上述提供的设备可设置为执行上述任意实施例提供的应用于第三通信节点的参数配置方法，具备相应的功能和效果。
本申请实施例还提供一种包含计算机可执行指令的存储介质，计算机可执行指令在由计算机处理器执行时用于执行一种应用于第一通信节点的参数配置方法，该方法包括：接收第二通信节点发送的分组数据单元PDU会话的帧格式；其中，所述PDU会话的帧格式包括下述指示信息至少之一：应用层数据包识别信息，应用层数据单元ADU识别信息，服务质量QoS流的子流标识以及QoS流的子优先级；根据所述PDU会话的帧格式确定同一QoS流中不同用户面数据包的调度优先级或资源分配权重。
本申请实施例还提供一种包含计算机可执行指令的存储介质，计算机可执行指令在由计算机处理器执行时用于执行一种应用于第三通信节点的参数配置方法，该方法包括：接收第一通信节点发送的配置信息；根据所述配置信息上报缓冲状态报告BSR；其中，所述配置信息包含QoS流的子流标识或QoS流的子优先级；所述配置信息包括如下至少之一：SDAP配置信息，无线承载配置信息，逻辑信道配置信息和无线连路控制配置信息。
本申请实施例还提供一种包含计算机可执行指令的存储介质，计算机可执行指令在由计算机处理器执行时用于执行一种应用于第二通信节点的参数配置方法，该方法包括：向第一通信节点发送PDU会话的帧格式，所述PDU会话的帧格式包括下述指示信息至少之一：应用层数据包识别信息，ADU识别信息，QoS流的子流标识以及QoS流的的子优先级。
本领域内的技术人员应明白，术语用户设备涵盖任何类型的无线用户设备，例如移动电话、便携数据处理装置、便携网络浏览器或车载移动台。
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。
本申请的实施例可以通过移动装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，通过硬件，或者通过软件和硬件的组合来实现。计算机程序指令可以是汇编指令、指令集架构(Instruction Set Architecture，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(Read-Only Memory，ROM)、随机访问存储器(Random Access  Memory，RAM)、光存储器装置和系统(数码多功能光碟(Digital Video Disc，DVD)或光盘(Compact Disk，CD))等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑器件(Field-Programmable Gate Array，FPGA)以及基于多核处理器架构的处理器。

Claims (18)

  1. 一种参数配置方法，应用于第一通信节点，包括：
    接收第二通信节点发送的分组数据单元PDU会话的帧格式；其中，所述PDU会话的帧格式包括下述指示信息至少之一：应用层数据包识别信息，应用层数据单元ADU识别信息，服务质量QoS流的子流标识以及QoS流的子优先级。
  2. 根据权利要求1所述的方法，还包括：
    接收第二通信节点发送的QoS子流配置信息，所述QoS子流配置信息包含所述QoS流的子优先级和所述QoS流的子流标识中的至少之一。
  3. 根据权利要求2所述的方法，其中，QoS流配置信息或所述QoS子流配置信息包括下述之一：应用层数据单元中可容忍的最大丢包总数，应用层数据单元中可容忍的最大连续丢包总数，预定义时间段内可容忍的最大丢包总数，预定义时间段内可容忍的最大连续丢包总数，预定义时间段内可容忍的最大应用层数据单元丢失总数，和预定义时间段内可容忍的最大连续应用层数据单元丢失总数。
  4. 根据权利要求1所述的方法，其中，不同优先级的应用层数据包映射到同一个QoS流；所述PDU会话的帧格式至少包括：ADU识别信息。
  5. 根据权利要求4所述的方法，其中，采用ADU识别信息指示至少两个级别的应用层数据单元。
  6. 根据权利要求4所述的方法，其中，所述ADU识别信息至少包括下述之一：应用层数据单元的开始传输指示和应用层数据单元的结束传输指示。
  7. 根据权利要求4所述的方法，其中，所述ADU识别信息至少包括下述之一：应用层数据单元序号和应用层数据单元的结束传输指示。
  8. 根据权利要求4所述的方法，其中，所述ADU识别信息至少包括下述之一：应用层数据单元的开始传输指示和应用层数据单元所包含的用户面数据包 总数量。
  9. 根据权利要求1所述的方法，其中，不同QoS优先级的应用层数据包映射到不同的QoS流；所述PDU会话的帧格式包括下述之一：关联的QoS流标识服务质量流标识QFI和关联的下行QFI序号。
  10. 根据权利要求1所述的方法，其中，所述PDU会话的帧格式包括下述之一：应用层数据单元中可容忍的最大丢包总数和应用层数据单元中可容忍的最大连续丢包总数。
  11. 根据权利要求10所述的方法，其中，所述PDU会话的帧格式还包括：应用层数据单元的开始传输指示和应用层数据单元所包含的用户面数据包总数量。
  12. 根据权利要求1所述的方法，其中，不同优先级的应用层数据包映射到同一QoS流；将同一QoS流中不同的子流标识或子优先级映射到不同专用数据无线承载DRB标识、不同逻辑信道LC标识、或不同的逻辑信道组LCG标识上。
  13. 根据权利要求12所述的方法，其中，所述将同一QoS流中不同的子流标识或子优先级映射到不同专用DRB标识、不同LC标识、或不同的LCG标识上，包括：将QoS流的子流标识或QoS流的子优先级包含在发送给第三通信节点的以下至少之一的配置信息中：服务数据适配协议SDAP配置信息，无线承载配置信息，逻辑信道配置信息，和无线链路控制配置信息；
    所述QoS流的子流标识或QoS流的子优先级用于将同一QoS流的用户面数据包映射到不同的逻辑信道上。
  14. 一种参数配置方法，应用于第三通信节点，包括：
    接收第一通信节点发送的配置信息；
    根据所述配置信息上报缓冲状态报告BSR；
    其中，所述配置信息包含QoS流的子流标识或QoS流的子优先级；
    所述配置信息包括如下至少之一：SDAP配置信息，无线承载配置信息，逻辑信道配置信息，和无线连路控制配置信息。
  15. 根据权利要求14所述的方法，其中，所述QoS流的子流标识或QoS流的子优先级用于将同一QoS流的用户面数据包映射到不同的逻辑信道上。
  16. 一种参数配置方法，应用于第二通信节点，包括：
    向第一通信节点发送PDU会话的帧格式，所述PDU会话的帧格式包括下述指示信息至少之一：应用层数据包识别信息，ADU识别信息，QoS流的子流标识以及QoS流的的子优先级。
  17. 一种通信设备，包括：通信模块，存储器，以及至少一个处理器；
    所述通信模块，配置为与其它通信节点进行通信交互；
    所述存储器，配置为存储至少一个程序；
    当所述至少一个程序被所述至少一个或多个处理器执行时，所述至少一个处理器实现如上述权利要求1-13、14-15或16中任一项所述的方法。
  18. 一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现如上述权利要求1-13、14-15或16中任一项所述的方法。
PCT/CN2022/139923 2021-12-31 2022-12-19 参数配置方法、通信设备和存储介质 Ceased WO2023125096A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP22914350.8A EP4451778A4 (en) 2021-12-31 2022-12-19 PARAMETER CONFIGURATION METHOD, COMMUNICATION DEVICE AND STORAGE MEDIUM
KR1020247025822A KR20240129037A (ko) 2021-12-31 2022-12-19 파라미터 구성 방법, 통신 디바이스, 및 저장 매체
JP2024539072A JP7827867B2 (ja) 2021-12-31 2022-12-19 パラメータ構成方法、通信機器と記憶媒体
US18/757,426 US20240373282A1 (en) 2021-12-31 2024-06-27 Parameter configuration method, communication device, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111673802.5 2021-12-31
CN202111673802.5A CN115884417A (zh) 2021-12-31 2021-12-31 参数配置方法、通信设备和存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/757,426 Continuation US20240373282A1 (en) 2021-12-31 2024-06-27 Parameter configuration method, communication device, and storage medium

Publications (1)

Publication Number Publication Date
WO2023125096A1 true WO2023125096A1 (zh) 2023-07-06

Family

ID=85756873

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/139923 Ceased WO2023125096A1 (zh) 2021-12-31 2022-12-19 参数配置方法、通信设备和存储介质

Country Status (6)

Country Link
US (1) US20240373282A1 (zh)
EP (1) EP4451778A4 (zh)
JP (1) JP7827867B2 (zh)
KR (1) KR20240129037A (zh)
CN (2) CN115884417A (zh)
WO (1) WO2023125096A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025168238A1 (en) * 2024-10-16 2025-08-14 Lenovo International Coöperatief U.A. Data packet handling in a wireless communication network

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024005334A1 (en) * 2022-07-01 2024-01-04 Lg Electronics Inc. Method and apparatus for configuring multiple sub quality of service flows belonging to quality of service flow in wireless communication system
CN119485476A (zh) * 2023-08-09 2025-02-18 华为技术有限公司 数据包的处理方法和通信装置
CN118827836B (zh) * 2023-09-14 2026-01-16 中国移动通信有限公司研究院 一种数据传输方法、装置、通信设备和存储介质
CN119728568A (zh) * 2023-09-28 2025-03-28 华为技术有限公司 通信方法及相关装置
CN119945646A (zh) * 2023-11-03 2025-05-06 华为技术有限公司 一种基于协议数据单元集的通信方法以及相关装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017201677A1 (zh) * 2016-05-24 2017-11-30 华为技术有限公司 数据传输的方法及装置
CN110636544A (zh) * 2018-06-22 2019-12-31 华为技术有限公司 一种数据传输方法及装置
CN110769438A (zh) * 2018-07-27 2020-02-07 展讯通信（上海）有限公司 Ebi的分配、请求方法及装置、存储介质、网络设备、终端
CN115175251A (zh) * 2021-04-01 2022-10-11 中兴通讯股份有限公司 服务质量流传输方法、装置、基站、终端和存储介质

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150215840A1 (en) * 2014-01-30 2015-07-30 Intel IP Corporation Systems, methods and devices for application specific routing in dual connectivity
CN109274474B (zh) * 2017-05-05 2019-11-19 华为技术有限公司 一种基于反转服务流特性的通信方法及装置
US11310707B2 (en) * 2018-04-13 2022-04-19 Qualcomm Incorporated Facilitating quality of service flow remapping utilizing a service data adaptation protocol layer
CN113543216B (zh) * 2020-04-22 2023-03-17 华为技术有限公司 媒体报文的传输方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017201677A1 (zh) * 2016-05-24 2017-11-30 华为技术有限公司 数据传输的方法及装置
CN110636544A (zh) * 2018-06-22 2019-12-31 华为技术有限公司 一种数据传输方法及装置
CN110769438A (zh) * 2018-07-27 2020-02-07 展讯通信（上海）有限公司 Ebi的分配、请求方法及装置、存储介质、网络设备、终端
CN115175251A (zh) * 2021-04-01 2022-10-11 中兴通讯股份有限公司 服务质量流传输方法、装置、基站、终端和存储介质

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
MEDIATEK INC.: "SDAP header design for reflective QoS indication and QoS flow remapping", 3GPP TSG-RAN WG2 MEETING #99 R2-1708260, 20 August 2017 (2017-08-20), XP051318160 *
See also references of EP4451778A4 *
VIVO: "Capture latest agreements on SDAP", 3GPP TSG-RAN WG2 MEETING #110-E R2-2006431, 25 June 2020 (2020-06-25), XP051906280 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025168238A1 (en) * 2024-10-16 2025-08-14 Lenovo International Coöperatief U.A. Data packet handling in a wireless communication network

Also Published As

Publication number Publication date
JP2024547143A (ja) 2024-12-26
KR20240129037A (ko) 2024-08-27
JP7827867B2 (ja) 2026-03-10
CN115884417A (zh) 2023-03-31
US20240373282A1 (en) 2024-11-07
CN118647091A (zh) 2024-09-13
EP4451778A4 (en) 2025-03-26
EP4451778A1 (en) 2024-10-23

Similar Documents

Publication Publication Date Title
WO2023125096A1 (zh) 参数配置方法、通信设备和存储介质
US12075413B2 (en) Data transmission method and apparatus
CN104247541B (zh) 传输数据处理方法及设备
CN110831033B (zh) 服务质量监测方法、设备及系统
CN112423340B (zh) 一种用户面信息上报方法及装置
JP4474422B2 (ja) 移動通信システムにおける制御情報伝送装置及び方法
WO2020192624A1 (zh) 一种确定传输优先级的方法、装置和计算机可读存储介质
CN107770085B (zh) 一种网络负载均衡方法、设备及系统
CN110115060A (zh) 基站以及无线区段的QoS控制方法
WO2016177221A1 (zh) 一种缓冲区状态报告的上报方法、装置及系统
KR102327904B1 (ko) 사용자 평면을 분리하기 위한 서비스 품질 구현들
WO2018032991A1 (zh) 一种数据处理方法及装置
CN116746264A (zh) 一种通信方法及装置
US20250211542A1 (en) Protocol data unit set transmission method and apparatus
WO2021069552A1 (en) Identifying time sensitive network streams within a 3gpp qos flow
CN112019363B (zh) 确定业务传输需求的方法、设备及系统
WO2024055871A1 (zh) 一种通信系统中传输数据的方法和通信装置
CN121002911A (zh) 通过控制面确定网络能力的系统及方法
CN116156576A (zh) 一种服务质量QoS管理方法以及装置
WO2024060991A1 (zh) 一种多路径的数据流引流方法及装置
WO2023185402A1 (zh) 通信方法及装置
CN115175242A (zh) 一种通信方法、网络设备及计算机可读存储介质
CN112135329B (zh) 参数传输方法、装置及系统
WO2023217009A1 (zh) 数据传输方法、装置及通信设备
RU2842693C2 (ru) Способ конфигурации параметров, устройство связи и носитель данных

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2024539072

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 2022914350

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022914350

Country of ref document: EP

Effective date: 20240718

ENP Entry into the national phase

Ref document number: 20247025822

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2024119591

Country of ref document: RU

NENP Non-entry into the national phase

Ref country code: DE

WWG Wipo information: grant in national office

Ref document number: 2024119591

Country of ref document: RU