Parameter configuration method, communication device and storage medium

Abstract

The present application provides a parameter configuration method, a communication device and a storage medium, the parameter configuration method for a first communication node includes: receiving a frame format of a packet data unit (PDU) session sent by a second communication node, the frame format of the PDU session including at least one indication information of an application layer data packet identification information, an application layer data unit (ADU) identification information, a sub-flow identifier of a QoS flow and a sub-priority of a QoS flow; and determining 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.

Description

[Technical Field]

[0001] The present application relates to the field of communications, for example, to a parameter configuration method, a communications device, and a storage medium. [Background technology]

[0002] In a New Radio (NR) network, the core network configures the service Quality of Service (QoS) parameters in the base station via control plane signaling, and configures them according to the Packet Data Unit Session (PDU Session) ---> Quality of Service flow (QoS flow) level. One QoS flow has only one QoS priority, and there is no correlation between data packets of different QoS flows. Summary of the Invention [Problem to be solved by the invention]

[0003] However, in business such as Extended Reality (XR), different PDUs have different priorities and there are dependencies between different PDUs. [Means for solving the problem]

[0004] An embodiment of the present application provides a parameter configuration method for use in a first communication node, the method comprising: receiving a frame format of a packet data unit (PDU) session transmitted by a second communication node, where the frame format of the PDU session includes at least one indication of an application layer data packet identification, an application layer data unit (ADU) identification, a sub-flow identifier of a quality of service (QoS) flow, and a sub-priority of a QoS flow.

[0005] An embodiment of the present application provides a parameter configuration method for use in a third communication node, the method comprising: Receiving configuration information transmitted by the first communication node. Here, the configuration information includes a subflow identifier of a QoS flow or a subpriority of a QoS flow. The configuration information includes at least one of Service Data Adaptation Protocol (SDAP) configuration information, radio bearer configuration information, logical channel configuration information, and radio link control configuration information.

[0006] An embodiment of the present application provides a parameter configuration method for use in a second communication node, the method comprising: and transmitting a frame format of a PDU session to a first communication node, the frame format of the PDU session including at least one indication of an application layer data packet identification information, an ADU identification information, a sub-flow identifier of a QoS flow, and a sub-priority of a QoS flow.

[0007] An embodiment of the present application provides a communication device, which includes a communication module, a memory, and one or more processors. the communication module is configured to communicate with other communication nodes; the memory is configured to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of the above embodiments.

[0008] An embodiment of the present application provides a storage medium, which stores a computer program, which, when executed by a processor, implements the method according to any one of the above embodiments. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating the structure relationship between an application layer data unit, an application layer data packet, and an Internet Protocol (IP) packet according to one embodiment. [Figure 2] A schematic diagram of the structure of a frame format of a PDU session according to one embodiment. [Figure 3] 1 is a flowchart of a parameter configuration method according to an embodiment of the present application. [Figure 4] 1 is a flowchart of another parameter configuration method according to an embodiment of the present application. [Figure 5] 10 is a flowchart of yet another parameter configuration method according to an embodiment of the present application. [Figure 6] A schematic diagram of the structure of a frame format of another PDU session according to an embodiment of the present application. [Figure 7] FIG. 1 is a structural schematic diagram of adding a QoS sub-flow to a QoS flow according to an embodiment of the present application. [Figure 8] FIG. 1 is a structural schematic diagram of adding a QoS sub-flow to another QoS flow according to an embodiment of the present application. [Figure 9] A schematic diagram of the structure of a frame format of another PDU session according to an embodiment of the present application. [Figure 10] FIG. 10 is a schematic diagram of a configuration for instructing PDUs corresponding to the same ADU based on a transmission start instruction according to an embodiment of the present application; [Figure 11] FIG. 10 is a schematic diagram of a configuration for indicating PDUs corresponding to the same ADU based on a transmission end instruction according to an embodiment of the present application; [Figure 12] A schematic diagram of the structure of a frame format of another PDU session according to an embodiment of the present application. [Figure 13] A schematic diagram of the structure of a frame format of a further PDU session according to an embodiment of the present application. [Figure 14]A schematic diagram of the structure of a frame format of a further PDU session according to an embodiment of the present application. [Figure 15] A schematic diagram of the structure of a frame format of a further PDU session according to an embodiment of the present application. [Figure 16] A schematic diagram of the structure of a frame format of a further PDU session according to an embodiment of the present application. [Figure 17] FIG. 2 is a schematic diagram illustrating an indication of the number of packet losses that can be decoded in an application layer data unit according to an embodiment of the present application; [Figure 18] FIG. 10 is a schematic diagram illustrating an indication of the number of packet losses that can be decoded in another application layer data unit according to an embodiment of the present application; [Figure 19] FIG. 2 is a diagram illustrating a configuration relationship between a Logical Channel Group (LCG) identifier and a QoS subflow identifier according to an embodiment of the present application. [Figure 20] 1 is a schematic diagram of a Medium Access Control Layer Control Element (MAC CE) structure of a Short Buffer Status Report (Short BSR) according to an embodiment of the present application; FIG. [Figure 21] FIG. 2 is a schematic diagram of a MAC CE structure of a Long Buffer Status Report (Long BSR) according to an embodiment of the present application; [Figure 22] FIG. 2 is a structural block diagram of a parameter configuration device according to an embodiment of the present application; [Figure 23] FIG. 10 is a structural block diagram of another parameter configuration device according to an embodiment of the present application; [Figure 24] FIG. 10 is a structural block diagram of another parameter configuration device according to an embodiment of the present application; [Figure 25] 1 is a structural schematic diagram of a communication device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0010] The following describes the embodiments of the present application in conjunction with the drawings. The following describes the present application in conjunction with the drawings of the embodiments, and the examples given are only used to interpret the present application and are not intended to limit the scope of the present application.

[0011] How to identify the association between user plane data packets (IP packets) and application layer data packets, the association between application layer data packets, and different priorities between application layer data packets mapped to the same QoS Flow are problems that need to be solved quickly.

[0012] In an NR network, service QoS parameters are configured by the core network to the base station via control plane signaling, and are configured according to the PDU Session--->QoS flow level. One user equipment (UE) can establish up to 256 PDU sessions, and one PDU session can include up to 64 QoS flows, with QoS parameters configured according to the QoS flows. QoS parameters include user priority information (Allocation and Retention Priority (ARP)), Guaranteed Bit Rate (GBR) information (GBR QoS flow information), and 5th Generation Mobile Communication Technology Quality of Service Identifier (5QI) description information (5QI index corresponding to service type, service priority, packet delay budget (PDB), etc.).

[0013] For downlink operations, each user plane PDU is transmitted in a corresponding PDU channel (General Packet Radio Service Tunneling Protocol-User Tunnel, GTP-U Tunnel), and the PDU's extension header (i.e., New Radio Radio Access Network Container, NR RAN Container or PDU Session Container) carries a Quality of Service Flow Identifier (QFI) indication, which associates the PDU with QoS parameters and distinguishes QoS Flow-level PDU scheduling priorities.

[0014] For uplink operations, user plane PDUs are associated with QoS Flows. The base station can map different QoS flows to different Data Radio Bearers (DRBs), and different DRBs correspond to different LCGs. The UE carries a Logical Channel Group Identifier (LCG ID) in the BSR request. The base station allocates uplink scheduling resources based on the BSR information to realize PDU scheduling priority differentiation at the QoS Flow level.

[0015] One QoS flow has only one QoS priority, and there is no correlation between data packets of different QoS flows. However, in services such as XR, different PDUs may have different priorities, but there is a dependency between the PDUs. For example, one video sequence has multiple I-frames, P-frames, and B-frames, where the decoding of the P-frames and B-frames depends on the I-frame. Each frame is also composed of multiple IP packets (PDUs). Figure 1 is a diagram showing the structural relationship between application layer data units, application layer data packets, and IP packets according to one embodiment. As shown in Figure 1, one application layer data unit (video coding unit) is composed of 12 video frames (i.e., application layer data packets / application layer data frames). The 12 video frames are I1B2B3P4B5B6P7B8B9P 10 B 11 B 12 (When an I-frame (I13) appears, it represents the start of a new application layer data unit). Each video frame is also made up of multiple IP packets (i.e., user plane data packets or PDUs). (An I1-frame is made up of n IP packets I 11 I 12 ...I 1n B2 consists of m IP packets B 21 B 22 ...B 2m ...), where the IP data packet may be a User Datagram Protocol (UDP) data packet or an Ethernet data packet.

[0016] 2 is a schematic diagram illustrating the configuration of a frame format of a PDU session according to one embodiment. In this embodiment, the core network transmits the frame format of the PDU session shown in FIG. 2 to the base station. The frame format of the PDU SESSION is carried in an extension header of the GTP-U PDU (i.e., an NR RAN Container or a PDU Session Container) and transmitted over the GTP-U Tunnel.

[0017] The base station can know the QoS Flow Identifier and Down Link Quality of Service Flow Identifier Sequence Number (DL QFI Sequence Number) corresponding to the PDU from the frame format of this PDU SESSION. The base station can know the Priority Level corresponding to the QoS Flow Identifier based on the signaling of the S1 Application Protocol (S1AP) interface and the NG Application Protocol (NGAP) interface.

[0018] However, a base station cannot distinguish between the association relationship between IP packets (i.e., user plane data packets) and application layer data packets (which may also be called application layer data frames), the association relationship between application layer data frames, and different priorities between application layer data frames mapped to the same QoS Flow. Therefore, how to enhance the frame format of a PDU SESSION is an issue that needs to be resolved quickly.

[0019] In one embodiment, Figure 3 is a flowchart of a parameter configuration method according to an embodiment of the present application. This embodiment may be performed by a first communication node. Here, the first communication node is a base station. As shown in Figure 3, this embodiment includes steps S310 to S320.

[0020] In S310, a frame format of a PDU session transmitted by a second communication node is received.

[0021] The frame format of the PDU session includes at least one indication of an application layer data packet identification, an application layer data unit ADU identification, a subflow identifier of a QoS flow, and a subpriority of a QoS flow.

[0022] In an embodiment, the application layer data packet identification information is used to indicate application layer data packet information corresponding to a user plane data packet. The application layer data packet identification information may indicate application layer data packet information corresponding to a user plane data packet from different dimensions. Exemplarily, the application layer data packet information may be indicated by the application layer data packet type. For example, the application layer data packet type includes an I frame data packet, a B frame data packet, and a P frame data packet. The application layer data packet information may also be indicated by the importance of the application layer data packet. For example, the importance of the application layer data packet is divided into a main packet and a sub-packet.

[0023] In an embodiment, the ADU identification information is used to indicate at least two of an application layer data unit transmission start instruction, a transmission end instruction, an application layer data unit sequence number, and the total number of user plane data packets included in the application layer data unit, and the ADU identification information is further used to implicitly indicate that the higher the application layer data packet in the ADU, the higher the priority.

[0024] In an embodiment, the subflow identifier of a QoS flow is the identifier of each QoS subflow included in the QoS flow, and the subpriority of a QoS flow is the priority of each QoS subflow included in the QoS flow. In one embodiment, the subflow identifier of a QoS flow and the subpriority of a QoS flow may be expressed using a QoS flow subpriority. That is, the QoS flow subpriority includes not only the identifier of a QoS subflow but also the priority of the QoS subflow.

[0025] At S320, the scheduling priorities or resource allocation weights of different user plane data packets in the same QoS flow are determined according to the frame format of the PDU session.

[0026] In an embodiment, the second communication node transmits a frame format of a PDU session to the first communication node via a user plane. The frame format of the PDU session includes at least one of application layer data packet identification information, ADU identification information, subflow identifiers of QoS flows, and subpriorities of QoS flows, so that the first communication node can identify association relationships between user plane data packets and application layer data packets, association relationships between different application layer data packets, and different priorities between application layer data packets mapped to the same QoS flow according to the frame format of the PDU session. This allows the first communication node to 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, and thus can report a BSR according to the scheduling priorities and the allocated scheduling resources.

[0027] In one embodiment, the parameter configuration method for use in the first communication node further comprises receiving QoS subflow configuration information transmitted by the second communication node, the QoS subflow configuration information comprising a subpriority of the QoS flow and / or a subflow identifier of the QoS flow.

[0028] In an embodiment, before the first communication node receives a frame format of a PDU session transmitted by a second communication node, the first communication node receives QoS subflow configuration information transmitted by the second communication node via control plane signaling. The QoS subflow configuration information carries a subpriority of a QoS flow, or a subpriority of a QoS flow and a subflow identifier of a QoS flow. In an embodiment, when the QoS subflow configuration information carries only a subpriority of a QoS flow, the subpriority of the QoS flow can represent a priority of the QoS subflow or a QoS subflow identifier.

[0029] In one embodiment, the QoS flow configuration information or the QoS subflow configuration information includes one of a maximum total number of packet losses that can be tolerated in an application layer data unit, a maximum total number of consecutive packet losses that can be tolerated in an application layer data unit, a maximum total number of packet losses that can be tolerated within a predefined time period, a maximum total number of consecutive packet losses that can be tolerated within a predefined time period, a maximum total number of application layer data unit losses that can be tolerated within a predefined time period, and a maximum total number of consecutive application layer data unit losses that can be tolerated within a predefined time period. The total number of packet losses is a total number of lost user plane data packets or a total number of lost application layer data packets. In an embodiment, the second communication node transmits the QoS flow configuration information or the QoS subflow configuration information to the first communication node via control plane signaling. In one embodiment, when the second communication node transmits QoS flow configuration information to the first communication node via control plane signaling, the QoS flow configuration information carries a maximum total number of packet losses that can be tolerated in an application layer data unit, or a maximum total number of consecutive packet losses that can be tolerated in an application layer data unit, a maximum total number of packet losses that can be tolerated within a predefined time period, a maximum total number of consecutive packet losses that can be tolerated within a predefined time period, a maximum total number of application layer data unit losses that can be tolerated within a predefined time period, or a maximum total number of consecutive application layer data unit losses that can be tolerated within a predefined time period, wherein the total number of packet losses is a total number of lost user plane data packets or a total number of lost application layer data packets.In one embodiment, when the second communication node transmits QoS subflow configuration information to the first communication node via control plane signaling, the QoS subflow configuration information carries a maximum total number of packet losses that can be tolerated in an application layer data unit, or a maximum total number of consecutive packet losses that can be tolerated in an application layer data unit, a maximum total number of packet losses that can be tolerated within a predefined time period, a maximum total number of consecutive packet losses that can be tolerated within a predefined time period, a maximum total number of application layer data unit losses that can be tolerated within a predefined time period, or a maximum total number of consecutive application layer data unit losses that can be tolerated within a predefined time period, where the total number of packet losses is the total number of lost user plane data packets or the total number of lost application layer data packets.

[0030] In one embodiment, application layer data packets of different priorities are mapped to the same QoS flow, and the frame format of the PDU session includes at least ADU identification information. In this embodiment, when application layer data packets of different priorities are mapped to the same QoS flow, the ADU identification information may be carried in the frame format of the PDU session to indicate a transmission start indication and a transmission end indication for the application layer data unit corresponding to each application layer data packet. This may further determine the priority of each application layer data packet in the application layer data unit. Here, the ADU identification information implicitly indicates that the higher the application layer data packet in each ADU, the higher the priority. In one embodiment, the indication bit of the ADU identification information may be 1 bit or 2 bits.

[0031] In one embodiment, the ADU identification information is used to indicate at least two levels of application layer data units. In another embodiment, parameters carried in the ADU identification information may be combined, multiplexed, and multi-leveled to indicate multiple levels of application layer data units. For example, when the ADU identification information is used to indicate two levels of application layer data units, the application layer data unit of level 1 may be one video stream, and the application layer data unit of level 2 may be one video frame.

[0032] In one embodiment, the ADU identification information includes at least one of an application layer data unit transmission start indication and an application layer data unit transmission end indication, where the application layer data unit transmission start indication is used to indicate the location of the first application layer data packet in the same application layer data unit, and the application layer data unit transmission end indication is used to indicate the location of the last application layer data packet in the same application layer data unit.

[0033] In one embodiment, the ADU identification information includes at least one of an application layer data unit sequence number and an application layer data unit transmission end indication. In the embodiment, the application layer data unit sequence number is used to indicate whether user plane data packets correspond to the same application layer data unit, where user plane data packets with the same sequence number in the same QoS flow correspond to the same application layer data unit, and user plane data packets with different sequence numbers correspond to different application layer data units.

[0034] In one embodiment, the ADU identification information includes at least one of a transmission start instruction for the application layer data unit and a total number of user plane data packets included in the application layer data unit. In the embodiment, all consecutive user plane data packets, from the user plane data packet indicated by the transmission start instruction for the application layer data unit to the total number of user plane data packets included in the application layer data unit, belong to the same application layer data unit.

[0035] In one embodiment, application layer data packets of different QoS priorities are mapped to different QoS flows, and the frame format of the PDU session includes one of an associated QoS flow identifier QFI and an associated downlink QFI sequence number.

[0036] The associated QoS flow identifier QFI and the associated downlink QFI sequence number are used to indicate that there is an association relationship, dependency relationship, complementary relationship, master-slave relationship, subordinate relationship or timing relationship between this PDU session frame and the associated QoS flow identifier QFI and the associated downlink QFI sequence number.

[0037] In one embodiment, the frame format of the PDU session includes one of a maximum total number of packet losses allowable in an application layer data unit and a maximum total number of consecutive packet losses allowable in an application layer data unit. The total number of packet losses is the total number of lost user plane data packets or the total number of lost application layer data packets. In an embodiment, the second communication node may transmit the frame format of the PDU session to the first communication node via the user plane, and may carry the maximum total number of packet losses allowable in an application layer data unit or the maximum total number of consecutive packet losses allowable in an application layer data unit in the frame format of the PDU session. The total number of packet losses is the total number of lost user plane data packets or the total number of lost application layer data packets.

[0038] In one embodiment, the frame format of the PDU session further includes an indication to start transmission of the application layer data unit and a total number of user plane data packets included in the application layer data unit. In this embodiment, the total number of user plane data packets included in the application layer data unit is the total number of user plane data packets, i.e., the number of IP packets, included in one application layer data unit, and may also be referred to as the number of PDUs.

[0039] In one embodiment, the application layer data packet identification information may include at least two of an application layer data packet sequence number, an indication to start transmission of the application layer data packet, an indication to end transmission of the application layer data packet, and the total number of user plane data packets included in the application layer data packet. The interpretation of each parameter in the application layer data packet identification information is the same as the interpretation of the corresponding parameter in the ADU identification information, and only involves exchanging the application layer data unit with the application layer data packet.

[0040] In one embodiment, application layer data packets of different priorities are mapped to the same QoS flow, and different subflow identifiers or subpriorities 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. In the embodiment, the first communication node maps different subflow identifiers or subpriorities in the same QoS flow to different LC identifiers and further maps different LC identifiers to different LCG identifiers, thereby realizing mapping of QoS subflows or subpriorities having different priorities in the same QoS flow to different LCG identifiers. In the embodiment, when application layer data packets of different priorities are mapped to the same QoS flow, the first communication node may map different subflow identifiers or subpriorities in the same QoS flow to different DRB identifiers, different LC identifiers, or different LCG identifiers so that a third communication node performs BSR reporting according to the different subflow identifiers or subpriorities.

[0041] In one embodiment, mapping different subflow identifiers or subpriorities of the same QoS flow to different DRB identifiers, different LC identifiers, or different LCG identifiers includes including the subflow identifiers of the QoS flow or the subpriorities of the QoS flow in at least one of Service Data Adaptation Protocol (SDAP) configuration information, Radio Bearer configuration information, Logical Channel configuration information, and Radio Link Control configuration information, which are transmitted to the third communication node.

[0042] The sub-flow identifier of a QoS flow or the sub-priority of a QoS flow is used to map user plane data packets of the same QoS flow to different logical channels.

[0043] In one embodiment, Figure 4 is a flowchart of another parameter configuration method according to an embodiment of the present application. This embodiment may be performed by a third communication node. Here, the third communication node is a user equipment. As shown in Figure 4, this embodiment includes steps S410 to S420.

[0044] In S410, the configuration information transmitted by the first communication node is received.

[0045] In S420, a buffer status report (BSR) is reported based on the configuration information.

[0046] The configuration information includes a subflow identifier of the QoS flow or a subpriority of the QoS flow. The configuration information includes at least one of SDAP configuration information, radio bearer configuration information, logical channel configuration information, and radio link control configuration information.

[0047] In one embodiment, a subflow identifier of a QoS flow or a subpriority of a QoS flow is used to map user plane data packets of the same QoS flow to different logical channels. In this embodiment, the first communication node can map different subflow identifiers or subpriorities in the same QoS flow to different LC identifiers, and further map the different LC identifiers to different LCG identifiers, thereby realizing mapping of QoS subflows or subpriorities with different priorities in the same QoS flow to different LCG identifiers. When the third communication node makes a BSR request based on the LCG identifier, the first communication node may distinguish QoS subflows or subpriorities with different priorities in the same QoS flow in the BSR.

[0048] It should be explained here that the interpretation of each parameter in the parameter configuration method used in the third communication node can refer to the description of the corresponding parameter in the parameter configuration method used in the first communication node in the above embodiment, and the explanation thereof will be omitted here.

[0049] In one embodiment, Figure 5 is a flowchart of another parameter configuration method according to an embodiment of the present application. This embodiment may be performed by a second communication node. Here, the second communication node is a core network. As shown in Figure 5, this embodiment includes S510.

[0050] At S510, a frame format of a PDU session is sent to the first communication node, and the frame format of the PDU session includes at least one indication information of application layer data packet identification information, ADU identification information, a subflow identifier of a QoS flow, and a subpriority of a QoS flow.

[0051] In one embodiment, the parameter configuration method for use in the second communication node further comprises transmitting QoS subflow configuration information to the first communication node, the QoS subflow configuration information comprising a subpriority of the QoS flow and / or a subflow identifier of the QoS flow.

[0052] In one embodiment, the QoS flow configuration information or the QoS subflow configuration information includes one of a maximum allowable total number of packet losses in an application layer data unit, a maximum allowable total number of consecutive packet losses in an application layer data unit, a maximum allowable total number of packet losses within a predefined time period, a maximum allowable total number of consecutive packet losses within a predefined time period, a maximum allowable total number of application layer data unit losses within a predefined time period, and a maximum allowable total number of consecutive application layer data unit losses within a predefined time period, wherein the total number of packet losses is a total number of lost user plane data packets or a total number of lost application layer data packets.

[0053] In one embodiment, application layer data packets of different priorities are mapped to the same QoS flow, and the frame format of the PDU session includes at least one of the ADU identification information.

[0054] In one embodiment, ADU identification information is employed to indicate at least two levels of application layer data units.

[0055] In one embodiment, the ADU identification information includes at least one of an indication to start transmitting an application layer data unit and an indication to end transmitting an application layer data unit.

[0056] In one embodiment, the ADU identification information includes at least one of an application layer data unit sequence number and an end of transmission indication for the application layer data unit.

[0057] In one embodiment, the ADU identification information includes at least one of an indication 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.

[0058] In one embodiment, application layer data frames of different QoS priorities are mapped to different QoS flows, and the frame format of the PDU session includes one of an associated QoS flow identifier QFI and an associated downlink QFI sequence number.

[0059] The associated QoS flow identifier QFI and the associated downlink QFI sequence number are used to indicate that there is an association relationship, dependency relationship, complementary relationship, master-slave relationship, subordinate relationship or timing relationship between this PDU session frame and the associated QoS flow identifier QFI and the associated downlink QFI sequence number.

[0060] In one embodiment, the frame format of the PDU session includes one of a maximum total number of packet losses allowable in an application layer data unit and a maximum total number of consecutive packet losses allowable in an application layer data unit, where the total number of packet losses is the total number of lost user plane data packets or the total number of lost application layer data packets.

[0061] In one embodiment, the frame format of the PDU session further includes an indication of the start of transmission of the application layer data unit and the total number of user plane data packets included in the application layer data unit.

[0062] In one embodiment, application layer data packets of different priorities are mapped to the same QoS flow, and different subflow identifiers or subpriorities 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.

[0063] In one embodiment, mapping different subflow identifiers or subpriorities of the same QoS flow to different dedicated radio bearer DRB identifiers, different logical channel LC identifiers, or different logical channel group LCG identifiers comprises including the subflow identifiers of the QoS flow or the subpriorities of the QoS flow in at least one of configuration information among Service Data Adaptation Protocol (SDAP) configuration information, radio bearer configuration information, logical channel configuration information, and radio link control configuration information, which is transmitted to the third communication node.

[0064] The sub-flow identifier of a QoS flow or the sub-priority of a QoS flow is used to map user plane data packets of the same QoS flow to different logical channels.

[0065] It should be explained here that the interpretation of each parameter in the parameter configuration method used in the second communication node can be referred to the description of the corresponding parameter in the parameter configuration method used in the first communication node in the above embodiment, and the explanation thereof will be omitted here.

[0066] In one embodiment, application layer data packets of different priorities are mapped to the same QoS Flow, and application layer data packet identification information or priority indication is introduced into the frame format of the PDU session. Here, the application layer data identification information is an application layer data packet type. Taking the first communication node as an example, FIG. 6 is a schematic diagram of the structure of another frame format of a PDU session according to an embodiment of the present application. As shown in FIG. 6, the frame format of the PDU SESSION carries at least one of an application layer data packet type, an application layer data packet sub-priority, and an application layer data packet sub-flow ID. Here, the application layer data packet type or the application layer data packet priority is used by the base station to identify the importance of the PDU (i.e., user plane data packets or IP packets in the above embodiment) in the transmission process, thereby identifying the scheduling priority or resource allocation weight of different PDUs under the same QoS Flow.

[0067] Based on the application layer data packet type, the base station can determine the application layer data packet type corresponding to the PDU, thereby determining the scheduling priority, reliability requirement level, or resource allocation weight of the PDU. The application layer data packet type can indicate the application layer data packet type corresponding to the IP packet. For example, it can indicate an I-frame data packet, a B-frame data packet, or a P-frame data packet in a video stream. Alternatively, the application layer data packet type can indicate whether the data packet is a main packet or a sub-packet, so that the base station can identify the importance of the data packet.

[0068] Based on the sub-priority of the application layer data packet or the sub-flow information of the application layer data packet, the base station can determine the priority of the application layer data packet corresponding to the PDU, and thereby determine the scheduling priority, reliability requirement, or resource allocation weight of the PDU.

[0069] The application layer data packet sub-priority and / or application layer data packet sub-flow ID included in the QoS flow in S1AP / NGAP signaling from the core network to the base station are used by the base station to configure different priority resources for data packets of different sub-priorities under the same QoS flow. FIG. 7 is a schematic diagram of a configuration for adding a QoS sub-flow to a QoS flow according to an embodiment of the present application. FIG. 8 is a schematic diagram of a configuration for adding a QoS sub-flow to another QoS flow according to an embodiment of the present application. As shown in FIG. 7, each QoS flow includes multiple QoS sub-flows, and each QoS sub-flow includes a QoS sub-flow ID and a QoS sub-flow priority, or each QoS sub-flow includes a QoS sub-priority. The QoS sub-flow in the QoS Flow may not be reflected, and only the multiple QoS sub-priorities included under the QoS flow may be reflected, and as shown in Figure 8 (i.e., in Figure 6), only the QoS sub-priority is included in the frame format of the PDU session. When a QoS sub-flow is reflected in the QoS Flow, the PDU Format also includes the QoS sub-flow ID and the QoS sub-flow Priority, or the PDU Format includes the QoS sub-priority.

[0070] The QoS parameters associated with the QoS sub-flow may be defined based on the QoS parameter differential of the QoS flow, e.g., the QoS parameters associated with the QoS sub-flow include only parameters that differ from the values ​​of the QoS parameters of the QoS flow.

[0071] Regarding QoS priority, the base station maps logical channel priorities based on the priority of the QoS flow and the priority of the QoS sub-flow, for example, absolute QoS priority = priority of the QoS flow + priority of the QoS sub-flow.

[0072] In one embodiment, 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 data packet in the ADU, the higher the priority.

[0073] 9 is a schematic diagram of the structure of a frame format of another PDU session according to an embodiment of the present application. The frame format of the PDU session carries at least one of an application data unit transmission start indicator (ADU start mark) and an application data unit transmission end indicator (ADU end mark). Here, the indicator bit of the ADU identification information can occupy two bits, and the four values ​​of the indicator bit respectively represent at least one of the following: no indicator bit, the start of transmission of one application layer data unit, the end of transmission of one application layer data unit, and only one PDU per application layer data unit. For example, if the two bits are '00', it indicates that no indicator bit is present (does not indicate the start or end of an application layer data unit), and the start and end of an application layer data unit cannot be determined, or it indicates that one application layer data unit corresponds to one PDU by default.

[0074] If the 2 bits are '01', it indicates the start of transmission of one application layer data unit. If the 2 bits are '10', it indicates the end of transmission of one application layer data unit. If the 2 bits are '11', it indicates that there is only one PDU in one application layer data unit.

[0075] In this embodiment, all PDUs in the [DL QFI Sequence Number 1, DL QFI Sequence Number 2] section of DL QFI Sequence Numbers under the same QoS flow, from DL QFI Sequence Number 1, where an indication of the start of transmission of one application layer data unit is located, to DL QFI Sequence Number 2, where an indication of the end of transmission of one application layer data unit is located, correspond to the same application layer data unit. The ADU identification information may implicitly indicate that the higher the sequence number, the more important the data frame or PDU in the same application layer data unit (the higher the scheduling priority, the stronger the reliability requirement).

[0076] In one embodiment, the indicator bit of the ADU identification information may occupy 1 bit. When this bit is 1, it indicates the start mark or end mark of the application layer data unit transmission under the same QoS flow (where a new start mark is the old end mark).

[0077] 10 is a schematic diagram illustrating a structure for indicating PDUs corresponding to the same ADU based on a transmission start indication according to an embodiment of the present application. In this embodiment, the value of 1 bit is 1, which represents a transmission start indication (start mark) for one application layer data unit, and all PDUs under the same QoS flow correspond to one application layer data unit until the 1 bit becomes 1 again.

[0078] As shown in FIG. 10, if StartMark=1 appears once in PDU1 and the nearest subsequent occurrence of StartMark=1 is PDU m+1, then PDU1, PDU2, ..., PDU m correspond to the same application layer data unit.

[0079] 11 is a schematic diagram illustrating a configuration for indicating PDUs corresponding to the same ADU based on a transmission end indication according to an embodiment of the present application. In this embodiment, the value of 1 bit is 1, which represents an application layer data unit transmission end indication (End mark), and the PDU corresponding to this End mark and the previous consecutive PDUs with End mark=0 under the same QoS flow correspond to one application layer data unit.

[0080] As shown in FIG. 11, EndMark=1 appears once in PDU m+1, and this PDU and the consecutive PDUs (PDU2, . . . , PDU m, PDU m+1) with the previous EndMark=0 correspond to one application layer data unit.

[0081] In one embodiment, Figure 12 is a schematic diagram of the structure of another PDU session frame format according to an embodiment of the present application. As shown in Figure 12, the PDU session frame format carries at least one of an application layer data unit sequence number (ADL) and an end mark for the application layer data unit. Here, the ADL sequence number is used by the base station to identify whether PDUs correspond to the same application layer data unit. PDUs with the same ADL sequence number under the same QoS flow correspond to the same application layer data unit, and PDUs with different ADL sequence numbers correspond to different application layer data units. The end mark for the application layer data unit is used to indicate the last PDU corresponding to the same application layer data unit.

[0082] Based on the application layer data unit sequence number, the base station can determine whether a new PDU transmission of an application layer data unit has started or whether different PDUs correspond to the same application layer data unit. Based on the application layer data unit end indication, the base station can determine whether a PDU transmission of an application layer data unit has ended. For example, in Figure 12, the value of the End mark is 1, which indicates that a PDU transmission of an application layer data unit has ended.

[0083] From the start of PDU transmission of a new application layer data unit to the end of PDU transmission of an application layer data unit, PDUs with the same application layer data unit sequence number under the same QoS flow correspond to one complete application layer data unit.

[0084] In one embodiment, whether the application layer data unit corresponding to the current PDU has ended can be determined based on whether the application layer data unit sequence number of the current PDU is the same as the sequence number of the next PDU. When a new application layer data unit transmission starts, it implicitly indicates that the previous application layer data unit transmission has ended. In this case, an end of application layer data unit indication is not required.

[0085] In one embodiment, Figure 13 is a structural schematic diagram of a frame format of a PDU session according to an embodiment of the present application. As shown in Figure 13, the frame format of the PDU session carries at least one of an application layer data unit transmission start indication (Start mark) and the total number of user plane data packets included in the application layer data unit (Packet Total Number in one Application Data Unit). Here, consecutive data packets up to the total number of user plane data packets included in the application layer data unit, starting from the data packet including the application layer data unit start identifier, belong to the same application layer data unit.

[0086] In one embodiment, Figure 14 is a schematic diagram of a frame format configuration of a PDU session according to an embodiment of the present application. This embodiment can represent multi-level application layer data units by combining, multiplexing, and multi-level inclusion of Figures 9, 12, and 13. For example, a level 1 application layer data unit is one video stream (i.e., application layer data unit), and a level 2 application layer data unit is one video frame (i.e., application layer data frame / application layer data packet). When two-level inclusion is performed using the configuration method of Figure 12, the result is as shown in Figure 14. (Note that the bit positions where the first level and second level are located are merely examples, and there may be differences between the actual number of occupied bits and the occupied bit positions. For example, the parameters related to the first level and second level are all placed in the extended bit positions of the PDU, or a new PDU format is introduced.)

[0087] As shown in Figure 14, two levels of application layer data units are illustratively described. The first level application layer data unit represents a video stream, and the second level application layer data unit represents a video frame. Corresponding to the information in Figure 1, it may be filled in with the following structure:

[0088] First IP packet: 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 (start of I1 frame) Second IP packet: 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 ... nth IP packet: First level End mark:0 First level Application Data Unit Sequence Number:1 Second level End mark: 1 (end of I1 frame) Second level Application Data Unit Sequence Number:1 (n+1)th IP packet: 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 (start of B2 frame) (n+2)th IP packet: 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)th IP packet: First level End mark:0 First level Application Data Unit Sequence Number:1 Second level End mark: 1 (end of B2 frame) Second level Application Data Unit Sequence Number:2 (n+m+1)th IP packet: 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 (end of B3 frame) In one embodiment, application layer data packet frames of different QoS flows are mapped to different QoS flows, and a dependency between the QoS flow and the PDU sequence number is introduced into the frame format of the PDU session.

[0089] 15 is a schematic diagram illustrating the configuration of a frame format of a PDU session according to an embodiment of the present application. As shown in FIG. 15, an associated QoS Flow Identifier (QFI) and an associated DL QFI Sequence Number (DL QFI Sequence Number) are used to indicate that there is an association, dependency, complementary, master-slave, subordinate, or timing relationship between the decoding of this PDU or the application layer data unit corresponding to this PDU and the PDU or the application layer data unit of the corresponding PDU corresponding to the QoS Flow Associated QoS Flow Identifier and the Associated DL QFI Sequence Number, and / or that this PDU and the associated PDU belong to the same application layer message, the same application layer data unit, or the same type of data packet.

[0090] For example, only if the PDU or the application layer data unit corresponding to this PDU corresponding to the QoS Flow Associated QoS Flow Identifier and the Associated DL QFI Sequence Number is successfully decoded can this PDU or the application layer data unit corresponding to this PDU be decoded.

[0091] In one embodiment, Figure 16 is a structural schematic diagram of a frame format of a PDU session according to an embodiment of the present application. The frame format of the PDU session carries a number of tolerable packet losses in decoding an application layer data unit. Here, the number of tolerable packet losses in decoding an application layer data unit includes a maximum total number of tolerable packet losses or a maximum total number of consecutive packet losses in decoding an application layer data unit. The total number of packet losses is the total number of lost user plane data packets or the total number of lost application layer data packets. As shown in Figure 16, the frame format of the PDU session carries one of a maximum total number of tolerable packet losses in an application layer data unit and a maximum total number of consecutive packet losses in an application layer data unit. The frame format of the PDU session may further include an indication to start transmission of the application layer data unit and a total number of user plane data packets included in the application layer data unit. The total number of packet losses is the total number of lost user plane data packets or the total number of lost application layer data packets.

[0092] In an embodiment, the number of tolerable packet losses in decoding an application layer data unit may be indicated by the number of tolerable packet losses included in the QoS flow of S1AP / NGAP signaling from the core network to the base station, or may be indicated by the number of tolerable packet losses included in the PDU format.

[0093] In this embodiment, the Maximum Lost Packets Tolerable in FIG. 16 can indicate the total number of packet losses that can be tolerated in an ADU or the total number of consecutive packet losses that can be tolerated. If the number of packet losses is greater than the Maximum Lost Packets Tolerable, the demands of the application layer will not be met (e.g., application layer decoding will fail). If the number of lost data packets within the data packets with the Packet Total Number in one Application Data Unit from the data packet identified by the Start Mark is about to reach the Maximum Lost Packets Tolerable, the reliability of subsequent data packet transmissions will be improved (e.g., PDCP Duplication will be activated or the transmission power will be increased). If the number of lost data packets within the data packets with the Packet Total Number in one Application Data Unit from the data packet identified by the Start Mark reaches the Maximum Lost Packets Tolerable, untransmitted data packets within the data packets with the Packet Total Number in one Application Data Unit will be discarded.

[0094] The Maximal Lost Packets Tolerable may be defined based on the application layer data unit (e.g., the first-level application layer data unit in FIG. 14) or based on the data packet type (e.g., the second-level application layer data unit in FIG. 14).

[0095] In one embodiment, Figure 17 is a schematic diagram of an indication of the number of packet losses that can be tolerated in decoding an application layer data unit according to an embodiment of the present application. Figure 18 is a schematic diagram of another indication of the number of packet losses that can be tolerated in decoding an application layer data unit according to an embodiment of the present application. Regarding the number of packet losses that can be tolerated in decoding an application layer data unit included in a QoS flow of S1AP or NGAP signaling from a core network to a base station, as shown in Figure 17, the QoS subflow includes the maximum total number of packet losses or the maximum total number of consecutive packet losses that can be tolerated in the application layer data unit, and as shown in Figure 18, the QoS flow includes the maximum total number of packet losses or the maximum total number of consecutive packet losses that can be tolerated in each application layer data unit.

[0096] In one embodiment, the application layer data packet identification information may include at least two of an application layer data packet sequence number, an indication to start transmission of the application layer data packet, an indication to end transmission of the application layer data packet, and the total number of user plane data packets included in the application layer data packet. It should be noted here that in the above embodiment, the interpretation of each parameter in the application layer data packet identification information is the same as the description of the corresponding parameter in the ADU identification information, and only the application layer data unit is exchanged with the application layer data packet. And the illustration of the ADU identification information in the above embodiment also applies to the application layer data packet identification information, and the description thereof will be omitted here.

[0097] In one embodiment, Figure 19 is a diagram illustrating the configuration relationship between LCG identifiers and QoS subflow identifiers according to an embodiment of the present application. This embodiment takes as an example a case where the first communication node is a base station and the third communication node is a UE to describe how to distinguish BSR priorities when data frames with different priorities are mapped to the same QoS Flow. As shown in Figure 19, the base station maps QoS Subflow IDs or sub-priorities with different priorities in the same QoS Flow to different LC IDs, and then maps the different LC IDs to different LCG IDs, thereby realizing the mapping of QoS Subflow IDs or sub-priorities with different priorities in the same QoS Flow to different LCG IDs.

[0098] During QoS mapping, the QoS Sub-Flow ID, SDAP, and Radio Link Control Bearer Config (RLC-Bearer Config) are simultaneously associated with the DRB during SDAP mapping, so the QoS Sub-Flow ID is also mapped to the RLC-Bearer Config. Each RLC-Bearer Config is associated with one LCG.

[0099] When the UE makes a BSR request based on the LCG ID, the BSR may distinguish between QoS sub-flow IDs or sub-priorities that have different priorities in the same QoS flow.

[0100] In one embodiment, the BSR request may reflect not only the priority of the QoS flow but also the priority of the QoS sub-flow.

[0101] In one embodiment, the QoS sub-flow IDs or sub-priorities of different priorities may be application layer data packet types as shown in Figure 6. The BSR may reflect the application layer data packet type.

[0102] In one embodiment, Figure 20 is a schematic diagram of a MAC CE structure of a Short BSR according to an embodiment of the present application. As shown in Figure 20, one Short BSR includes an LCG identifier and a buffer size.

[0103] In one embodiment, Figure 21 is a schematic diagram of a MAC CE structure of a Long BSR according to an embodiment of the present application. As shown in Figure 21, one Short BSR includes multiple LCG identifiers and buffer sizes corresponding to each LCG identifier.

[0104] In one embodiment, Figure 22 is a structural block diagram of a parameter configuration device according to an embodiment of the present application. This embodiment is used in a first communication node. As shown in Figure 22, the parameter configuration device in this embodiment includes a first receiver 2210 and a determination module 2220.

[0105] The first receiver 2210 is configured to receive a frame format of a packet data unit (PDU) session transmitted by the second communication node, where the frame format of the PDU session includes at least one indication of an application layer data packet identification, an application layer data unit (ADU) identification, a sub-flow identifier of a quality of service (QoS) flow, and a sub-priority of the QoS flow. The determining module 2220 is configured to 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.

[0106] In one embodiment, the parameter configuration device for use in the first communication node further comprises a second receiver configured to receive QoS subflow configuration information transmitted by the second communication node, the QoS subflow configuration information comprising a subpriority of the QoS flow and / or a subflow identifier of the QoS flow.

[0107] In one embodiment, the QoS flow configuration information or QoS subflow configuration information includes one of a maximum allowable total number of packet losses in an application layer data unit, a maximum allowable total number of consecutive packet losses in an application layer data unit, a maximum allowable total number of packet losses within a predefined time period, a maximum allowable total number of consecutive packet losses within a predefined time period, a maximum allowable total number of application layer data unit losses within a predefined time period, and a maximum allowable total number of consecutive application layer data unit losses within a predefined time period.

[0108] In one embodiment, application layer data packets of different priorities are mapped to the same QoS flow, and the frame format of the PDU session includes at least ADU identification information.

[0109] In one embodiment, ADU identification information is employed to indicate at least two levels of application layer data units.

[0110] In one embodiment, the ADU identification information includes at least one of an indication to start transmitting an application layer data unit and an indication to end transmitting an application layer data unit.

[0111] In one embodiment, the ADU identification information includes at least one of an application layer data unit sequence number and an end of transmission indication for the application layer data unit.

[0112] In one embodiment, the ADU identification information includes at least one of an indication 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.

[0113] In one embodiment, application layer data packets of different QOS priorities are mapped to different QoS flows, and the frame format of the PDU session includes one of an associated QoS flow identifier (QFI) and an associated downlink QFI sequence number.

[0114] The associated QoS flow identifier (QFI) and the associated downlink QFI sequence number are used to indicate that there is an association relationship, dependency relationship, complementary relationship, master-slave relationship, subordinate relationship, or timing relationship between this PDU session frame and the associated QoS flow identifier (QFI) and the associated downlink QFI sequence number.

[0115] In one embodiment, the frame format of the PDU session includes one of a maximum total number of packet losses that can be tolerated in an application layer data unit and a maximum total number of consecutive packet losses that can be tolerated in an application layer data unit.

[0116] In one embodiment, the frame format of the PDU session further includes an indication of the start of transmission of the application layer data unit and the total number of user plane data packets included in the application layer data unit.

[0117] In one embodiment, application layer data packets of different priorities are mapped to the same QoS flow, and different subflow identifiers or subpriorities within the same QoS flow are mapped to different dedicated data radio bearer (DRB) identifiers, different logical channel (LC) identifiers, or different logical channel group (LCG) identifiers.

[0118] In one embodiment, mapping different subflow identifiers or subpriorities of the same QoS flow to different dedicated DRB identifiers, different LC identifiers, or different LCG identifiers includes including the subflow identifiers or subpriorities of the QoS flow in at least one of configuration information among Service Data Adaptation Protocol (SDAP) configuration information, Radio Bearer configuration information, Logical channel configuration information, and Radio Link Control configuration information, which is transmitted to the third communication node, where the subflow identifiers or subpriorities of the QoS flow are used to map user plane data packets of the same QoS flow to different logical channels.

[0119] The parameter configuration device according to this embodiment is configured to realize the parameter configuration method of the embodiment shown in FIG. 3, and the principles and technical effects of the implementation of the parameter configuration device according to this embodiment are also similar to those of the parameter configuration method, and will not be further described here.

[0120] In one embodiment, Figure 23 is a structural block diagram of another parameter configuration device according to an embodiment of the present application. This embodiment may be performed by a third communication node. Here, the third communication node is a user equipment. As shown in Figure 23, the parameter configuration device in this embodiment includes a third receiver 2310 and a reporting module 2320.

[0121] The third receiver 2310 is configured to receive configuration information transmitted by the first communication node. The reporting module 2320 is configured to report a buffer status report (BSR) based on the configuration information, where the configuration information includes a subflow identifier of the QoS flow or a subpriority of the QoS flow. The configuration information includes at least one of SDAP configuration information, radio bearer configuration information, logical channel configuration information, and radio link control configuration information.

[0122] In one embodiment, the sub-flow identifier of a QoS flow or the sub-priority of a QoS flow is used to map user plane data packets of the same QoS flow to different logical channels.

[0123] The parameter configuration device according to this embodiment is configured to realize the parameter configuration method of the embodiment used in the third communication node shown in Figure 4, and the principles and technical effects of realizing the parameter configuration device according to this embodiment are also similar to the parameter configuration method, and will not be further described here.

[0124] In one embodiment, Figure 24 is a structural block diagram of another parameter configuration device according to an embodiment of the present application. This embodiment may be performed by a second communication node. Here, the second communication node is a core network. As shown in Figure 24, this embodiment includes a first transmitter 2410.

[0125] The first transmitter 2410 is configured to transmit a frame format of a PDU session to a first communication node, the frame format of the PDU session including at least one indication of an application layer data packet identification information, an ADU identification information, a subflow identifier of a QoS flow, and a subpriority of a QoS flow.

[0126] In one embodiment, the parameter configuration device for use in the second communication node further comprises a second transmitter configured to transmit QoS subflow configuration information to the first communication node, the QoS subflow configuration information comprising a subpriority of the QoS flow and / or a subflow identifier of the QoS flow.

[0127] In one embodiment, the QoS flow configuration information or QoS subflow configuration information includes one of a maximum allowable total number of packet losses in an application layer data unit, a maximum allowable total number of consecutive packet losses in an application layer data unit, a maximum allowable total number of packet losses within a predefined time period, a maximum allowable total number of consecutive packet losses within a predefined time period, a maximum allowable total number of application layer data unit losses within a predefined time period, and a maximum allowable total number of consecutive application layer data unit losses within a predefined time period.

[0128] In one embodiment, application layer data packets of different priorities are mapped to the same QoS flow. The frame format of the PDU session includes at least ADU identification information.

[0129] In one embodiment, ADU identification information is employed to indicate at least two levels of application layer data units.

[0130] In one embodiment, the ADU identification information includes at least one of an indication to start transmitting an application layer data unit and an indication to end transmitting an application layer data unit.

[0131] In one embodiment, the ADU identification information includes at least one of an application layer data unit sequence number and an end of transmission indication for the application layer data unit.

[0132] In one embodiment, the ADU identification information includes at least one of an indication 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.

[0133] In one embodiment, application layer data frames of different QoS priorities are mapped to different QoS flows. The frame format of a PDU session includes one of an associated QoS flow identifier (QFI) and an associated downlink QFI sequence number.

[0134] The associated QoS flow identifier (QFI) and the associated downlink QFI sequence number are used to indicate that there is an association relationship, dependency relationship, complementary relationship, master-slave relationship, subordinate relationship, or timing relationship between this PDU session frame and the associated QoS flow identifier (QFI) and the associated downlink QFI sequence number.

[0135] In one embodiment, the frame format of the PDU session includes one of a maximum total number of packet losses that can be tolerated in an application layer data unit and a maximum total number of consecutive packet losses that can be tolerated in an application layer data unit.

[0136] In one embodiment, the frame format of the PDU session further includes an indication of the start of transmission of the application layer data unit and the total number of user plane data packets included in the application layer data unit.

[0137] In one embodiment, application layer data packets of different priorities are mapped to the same QoS flow, and different subflow identifiers or subpriorities within 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.

[0138] In one embodiment, mapping different subflow identifiers or subpriorities of the same QoS flow to different dedicated DRB identifiers, different LC identifiers, or different LCG identifiers includes including the subflow identifiers or subpriorities of the QoS flow in at least one of configuration information among Service Data Adaptation Protocol (SDAP) configuration information, Radio Bearer configuration information, Logical channel configuration information, and Radio Link Control configuration information, which is transmitted to the third communication node, where the subflow identifiers or subpriorities of the QoS flow are used to map user plane data packets of the same QoS flow to different logical channels.

[0139] The parameter configuration device according to this embodiment is configured to realize the parameter configuration method of the embodiment used in the second communication node shown in Figure 5, and the principles and technical effects of realizing the parameter configuration device according to this embodiment are also similar to the parameter configuration method, and will not be further described here.

[0140] FIG. 25 is a structural schematic diagram of a communication device according to an embodiment of the present application. As shown in FIG. 25, the device according to the present 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 FIG. 25 takes one processor 2510 as an example. The number of memories 2520 in the device may be one or more, and FIG. 25 takes one memory 2520 as an example. The processor 2510, the memory 2520, and the communication module 2530 of the device may be connected via a bus or other manner, and FIG. 25 takes connection via a bus as an example. In this embodiment, the device may be a base station.

[0141] The memory 2520 may be configured as a computer-readable storage medium to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to any embodiment of the device of the present application (e.g., the first receiver and the determination module in a parameter configuration device). The memory 2520 may include a program storage area and a data storage area. The program storage area may store an operating system and / or application programs required for at least one function, and the data storage area may store data generated in response to use of the device. The memory 2520 may include high-speed random access memory or nonvolatile memory. For example, it may include at least one magnetic disk memory device, flash memory device, or other nonvolatile solid-state memory device. In some embodiments, the memory 2520 may include memory located remotely from the processor 2510. These remote memories may be connected to the device via a network. Examples of such networks include, but are not limited to, the Internet, a corporate intranet, a local area network, a mobile communication network, and a combination of the Internet, the corporate intranet, the local area network, and the mobile communication network.

[0142] The communication module 2530 is configured for communicative interaction with other communication nodes.

[0143] When the communication device is a first communication node, the device according to the above may be configured to execute a parameter configuration method used in a first communication node according to any of the above embodiments and to have the corresponding functions and effects.

[0144] When the communication device is a second communication node, the device according to the above may be configured to execute a parameter configuration method used for a second communication node according to any of the above embodiments and to have the corresponding functions and effects.

[0145] When the communication device is a third communication node, the device according to the above may be configured to execute a parameter configuration method used for a third communication node according to any of the above embodiments and to have the corresponding functions and effects.

[0146] An embodiment of the present application further provides a storage medium including computer-executable instructions, which, when executed by a computer processor, are used to perform a parameter configuration method for use in a first communication node, the method including: receiving a frame format of a packet data unit (PDU) session transmitted by a second communication node, the frame format of the PDU session including at least one indication of an application layer data packet identification, an application layer data unit (ADU) identification, a sub-flow identifier of a Quality of Service QoS flow, and a sub-priority of a QoS flow; and determining scheduling priorities or resource allocation weights of different user plane data packets in the same QoS flow based on the frame format of the PDU session.

[0147] An embodiment of the present application further provides a storage medium including computer-executable instructions. When the computer-executable instructions are executed by a computer processor, the storage medium is used to perform a parameter configuration method for use in a third communication node. The method includes receiving configuration information transmitted by a first communication node and reporting a buffer status report (BSR) based on the configuration information. Here, the configuration information includes a subflow identifier of a QoS flow or a subpriority of a QoS flow. The configuration information includes at least one of SDAP configuration information, radio bearer configuration information, logical channel configuration information, and radio link control configuration information.

[0148] An embodiment of the present application further provides a storage medium including computer-executable instructions, which, when executed by a computer processor, are used to perform a parameter configuration method for use with a second communication node, the method including transmitting a frame format of a PDU session to the first communication node, the frame format of the PDU session including at least one indication of application layer data packet identification information, ADU identification information, a subflow identifier of a QoS flow, and a subpriority of a QoS flow.

[0149] Those skilled in the art should understand that the term user equipment covers any type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable network browser or a vehicle mounted mobile device.

[0150] In general, various embodiments of the present application may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software executable by a controller, microprocessor, or other computing device, but the present application is not limited thereto.

[0151] The embodiments of the present application may be implemented by a data processor of a mobile device executing computer program instructions, for example in a processor entity, in hardware or a combination of software and hardware. The computer program instructions may be assembler instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or target code written in any combination of one or more programming languages.

[0152] Any logic flow block diagrams in the drawings of this application may represent program steps, or interconnected logic circuits, modules and functions, or a combination of program steps, logic circuits, modules and functions. Computer programs may be stored on memory. The memory may be of any type compatible with the local technology 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 Disc (CD)), etc. Computer-readable media may also include non-transitory storage media. Data processors may be of any type compatible with the local technology environment. For example, the processor may be, but is not limited to, a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (Field-Programmable Gate Array, FPGA), and a processor based on a multi-core processor architecture.

Claims

1. receiving, by the first communication node, a frame format for a packet data unit (PDU) session from a second communication node; Wherein the frame format of the PDU session includes application layer data unit (ADU) identification information; The ADU identification information includes at least one of an application layer data unit sequence number, an application layer data unit transmission end indication, and a total number of data packets included in one application layer data unit; How to configure parameters.

2. Application layer data packets of different priorities are mapped to the same Quality of Service (QoS) flow; The method of claim 1.

3. The priority indicates the importance of the corresponding application layer data packet in the same QoS flow. The method of claim 2.

4. The ADU identification information indicates at least two levels of application layer data units; The method of claim 1.

5. The end-of-transmission indication of the application layer data unit indicates whether the corresponding application layer data packet is the last application layer data packet in the same QoS flow; The method of claim 1.

6. the first communication node is a base station having at least one next generation (NG) protocol interface; The method of claim 1.

7. 1. A communications device comprising a processor and a memory for storing instructions, The instructions, when executed by the processor, cause the communication device to receiving, by the first communication node, a frame format of a packet data unit (PDU) session from a second communication node; Wherein the frame format of the PDU session includes application layer data unit (ADU) identification information; The ADU identification information includes at least one of an application layer data unit sequence number, an application layer data unit transmission end indication, and a total number of data packets included in one application layer data unit; Communication equipment.

8. Application layer data packets of different priorities are mapped to the same Quality of Service (QoS) flow; 8. The communication device according to claim 7.

9. The priority indicates the importance of the corresponding application layer data packet in the same QoS flow.

9. The communication device according to claim 8.

10. The ADU identification information indicates at least two levels of application layer data units; 8. The communication device according to claim 7.

11. The end-of-transmission indication of the application layer data unit indicates whether the corresponding application layer data packet is the last application layer data packet in the same QoS flow; 8. The communication device according to claim 7.

12. the first communication node is a base station having at least one next generation (NG) protocol interface; 8. The communication device according to claim 7.

13. transmitting, by the second communication node, a packet data unit (PDU) session frame format to the first communication node; Wherein the frame format of the PDU session includes application layer data unit (ADU) identification information; The ADU identification information includes at least one of an application layer data unit sequence number, an application layer data unit transmission end indication, and a total number of data packets included in one application layer data unit; How to configure parameters.

14. Application layer data packets of different priorities are mapped to the same Quality of Service (QoS) flow; The method of claim 13.

15. Priority indicates the importance of corresponding application layer data packets in the same QoS flow. The method of claim 13.

16. The ADU identification information indicates at least two levels of application layer data units; The method of claim 13.

17. The end-of-transmission indication of the application layer data unit indicates whether the corresponding application layer data packet is the last application layer data packet in the same QoS flow; The method of claim 13.

Images