Transmission configuration method and apparatus, and device, readable storage medium and computer program product

Abstract

The present application belongs to the technical field of communications, and particularly relates to a transmission configuration method and apparatus, and a device, a readable storage medium and a computer program product. The method comprises: a terminal receiving a first configuration from a network-side device; and the terminal determining a one-to-many mapping relationship between a data stream and a plurality of transmission channels on the basis of the first configuration.

Description

Transmission configuration methods, apparatus, devices, readable storage media, and computer program products

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411647672.1, filed on November 18, 2024, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] This application belongs to the field of communication technology, specifically relating to a transmission configuration method, apparatus, device, readable storage medium, and computer program product. Background Technology

[0004] In existing technologies, the mapping relationship between Quality of Service (QoS) flow and Data Radio Bearer (DRB) bearers and transmission channels is semi-static. Furthermore, a QoS flow can only be fixedly mapped to one DRB, making it impossible to dynamically adjust the mapping relationship and obtain flexible transmission attributes. In the later stages of 5G, with the deepening research into Extended Reality (XR) services, although the concept and targeted operations of Protocol Data Unit (PDU) sets have been introduced—marking several data packets with related attributes in XR services as a PDU set and requiring that data packets within the same PDU set be treated as a whole—the overall PDU set-based processing approach still relies on the most basic semi-static mapping relationship between 5G QoS flow and a fixed DRB. This cannot provide more flexible and high-quality service guarantees for XR and emerging services. Summary of the Invention

[0005] This application provides a transmission configuration method, apparatus, device, readable storage medium, and computer program product that can solve the problem that the existing fixed mapping relationship between QoS flow and DRB cannot provide more flexible and high-quality service guarantees.

[0006] Firstly, a transmission configuration method is provided, including:

[0007] The terminal receives the first configuration from the network-side device;

[0008] The terminal determines a one-to-many mapping relationship between the data stream and multiple transmission channels based on the first configuration.

[0009] Secondly, a transmission configuration method is provided, including:

[0010] The network-side device sends the first configuration to the terminal;

[0011] The first configuration is used to configure a one-to-many mapping relationship between the data stream and multiple transmission channels.

[0012] Thirdly, a transmission configuration device is provided, comprising:

[0013] The first receiving module is used to receive the first configuration from the network-side device;

[0014] The first processing module is used to determine a one-to-many mapping relationship between the data stream and multiple transmission channels based on the first configuration.

[0015] Fourthly, a transmission configuration apparatus is provided, comprising:

[0016] The second sending module is used to send the first configuration to the terminal;

[0017] The first configuration is used to configure a one-to-many mapping relationship between the data stream and multiple transmission channels.

[0018] Fifthly, a transmission configuration apparatus is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0019] In a sixth aspect, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0020] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used for the terminal to receive a first configuration from a network-side device; and the processor is used for the terminal to determine a one-to-many mapping relationship between a data stream and multiple transmission channels according to the first configuration.

[0021] Eighthly, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0022] In a ninth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used by the network-side device to send a first configuration to a terminal; wherein the first configuration is used to configure a one-to-many mapping relationship between a data stream and multiple transmission channels.

[0023] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0024] Eleventhly, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method as described in the first aspect, and the network-side device can be used to perform the steps of the method as described in the second aspect.

[0025] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0026] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0027] In this embodiment, the terminal determines a one-to-many mapping relationship between the data stream and multiple transmission channels based on the network-side configuration. Compared with the existing one-to-one transmission mapping, this achieves a more flexible transmission mapping, enhancing data transmission performance while ensuring system efficiency. Attached Figure Description

[0028] Figure 1a is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0029] Figure 1b is a schematic diagram of the existing QoS mechanism;

[0030] Figure 1c is a schematic diagram of the existing bearer mapping;

[0031] Figure 1d is a schematic diagram of the existing user plane protocol stack;

[0032] Figure 2 is a flowchart illustrating one of the transmission configuration methods provided in an embodiment of this application;

[0033] Figure 3 is one of the application example diagrams provided in the embodiments of this application;

[0034] Figure 4 is a flowchart illustrating one of the transmission configuration methods provided in an embodiment of this application;

[0035] Figure 5 is a second schematic diagram of an application example provided in the embodiments of this application;

[0036] Figure 6 is a schematic diagram of one of the transmission configuration devices provided in an embodiment of this application;

[0037] Figure 7 is a second schematic diagram of the transmission configuration device provided in an embodiment of this application;

[0038] Figure 8 is a schematic diagram of the structure of the communication device provided in an embodiment of this application;

[0039] Figure 9 is a schematic diagram of the structure of the terminal provided in an embodiment of this application;

[0040] Figure 10 is one of the structural schematic diagrams of the network-side device provided in the embodiments of this application;

[0041] Figure 11 is a second schematic diagram of the network-side device provided in an embodiment of this application. Detailed Implementation

[0042] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0043] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0044] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0045] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0046] Figure 1a shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.The term "base station" can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0047] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support. The core network functions include: BSF (Block Network Function), Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), and Network Data Analytics Function (NWDAF). It should be noted that this application embodiment only uses core network equipment in the NR system as an example and does not limit the specific type of core network equipment. If the name of the core network equipment mentioned in this application embodiment changes in subsequent protocol versions (e.g., 6G), it will still be within the scope of protection of this application.

[0048] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0049] To better understand the technical solution of this application, the following will be introduced first:

[0050] Existing NR QoS mechanism

[0051] The existing QoS mechanisms and bearer mappings are shown in Figures 1b and 1c, respectively. For uplink and downlink data packets, the UE and the core network UPF node map the data streams to different QoS flows according to their characteristics. A QoS flow can be viewed as a collection of data flows with specific QoS attributes. During the service establishment phase, the QoS flow undergoes semi-static bearer establishment and mapping configuration through the control plane (CP) process. For example, the base station can map QoS flows with the same or similar core attributes to the same DRB for air interface transmission based on QoS attributes. Once the mapping configuration and establishment are completed, the mapping of subsequent QoS flows to the DRB remains unchanged unless reconfigured, and a QoS flow can only be mapped to one DRB. In this way, by configuring different transmission parameters of the DRB, the transmission requirements of different QoS flows can be met.

[0052] QoS attributes include the following parameters:

[0053] (1) 5G Quality of Service Identifier (5QI)

[0054] (1.1) Priority level;

[0055] (1.2) Packet Delay Budget (PDB);

[0056] (1.3) Packet Error Rate;

[0057] (1.4) Averaging window;

[0058] (1.5) Maximum Data Burst Volume in the window;

[0059] (2) Allocation and Retention Priority (ARP);

[0060] (3) Guaranteed Flow Bit Rate (GFBR) & Maximum Flow Bit Rate (MFBR);

[0061] (4) Maximum Packet Loss Rate;

[0062] (5) Delay-Critical Resource Type;

[0063] (6) QoS negotiation notification control;

[0064] (7) RQA Reflective QoS Attribute.

[0065] In existing NR networks, the user plane protocol stack mainly includes the Medium Access Control (MAC) layer, the Radio Link Control (RLC) layer, the Packet Data Convergence Protocol (PDCP) layer, the Service Data Adaptation Protocol (SDAP) layer, and the Physical (PHY) layer, as shown in Figure 1d.

[0066] The SDAP layer provides a mapping of QoS flows to radio bearers and marks uplink and downlink data packets with QoS flow identifiers (QoS flow IDs, QFIs).

[0067] In existing technologies, the mapping relationship between QoS flow and DRB bearer / transmission channel is semi-static, and a QoS flow can only be fixedly mapped to one DRB, making it impossible to dynamically adjust the mapping relationship and obtain flexible transmission attributes. In the later stages of 5G, with the deepening research on XR services, the concept of PDU sets and targeted operations were introduced. This involves marking several data packets with related attributes in XR services as a PDU set, requiring that data packets within the same PDU set be treated as a whole, defining PDU Set Delay Budget, PDU Set Error Rate, and Integrated Handling Information. For example, if any data packet fails or times out, other data packets can be deleted or abandoned. Alternatively, a transmission delay can be defined for the entire PDU set, using the earliest arriving data packet in the set as the starting reference for the discard timer, and the transmission of the last data packet as the marker for the end or stop of the discard timer. For data packets about to time out, some simple measures are taken to speed up transmission. However, the overall PDU set-based processing approach is still based on the most basic semi-static QoS flow of 5G and a fixed mapping relationship to a DRB, which cannot provide more flexible and high-quality service guarantees for XR and emerging services.

[0068] Furthermore, in the early stages of 6G, various emerging applications, such as XR, virtual reality, and robotics, have placed more precise and demanding requirements on data transmission and service attribute identification. Multimodal needs have also emerged. For example, in virtual reality services, various signals such as sound, image, touch, and taste are collected remotely, aggregated, and transmitted to the other end. To recreate an immersive experience, in addition to traditional data transmission QoS requirements, strict synchronization of all data types is also necessary.

[0069] These new requirements cannot be adequately met or implemented using the existing 5G QoS architecture, thus necessitating the consideration of a new QoS architecture.

[0070] The transmission configuration method provided in this application will be described in detail below with reference to the accompanying drawings, through some embodiments and application scenarios.

[0071] Referring to Figure 2, this embodiment of the application provides a transmission configuration method, the execution subject of which is a terminal, and the method includes:

[0072] Step 201: The terminal receives the first configuration from the network-side device;

[0073] Step 202: The terminal determines the one-to-many mapping relationship between the data stream and multiple transmission channels according to the first configuration.

[0074] It is understandable that the acquisition of the first configuration mentioned above can be achieved through signaling procedures during the CP process.

[0075] It should be noted that the transmission channel can also be called a channel, transmission pipe, pipe, etc.

[0076] In this embodiment, the terminal determines a one-to-many mapping relationship between the data stream and multiple transmission channels based on the network-side configuration. Compared with the existing one-to-one transmission mapping, this achieves a more flexible transmission mapping, enhancing data transmission performance while ensuring system efficiency.

[0077] In one alternative implementation, the method further includes:

[0078] (1) The terminal acquires data packets from the data stream, and the data packets contain first information;

[0079] (2) Based on the first information, the terminal sends a PDU set or PDU to the peer communication device using the target transmission channel among multiple transmission channels;

[0080] The first information is used to indicate at least one of the QoS information and service attribute information of the data stream, and each different first information maps to one or more transmission channels.

[0081] In this embodiment, when a data packet arrives, the system dynamically determines which transmission channel to map it to for transmission based on at least one of the QoS information carried by the data packet and the service attribute information of the data stream. That is, the terminal can learn the corresponding PDU set transmission requirement or PDU transmission requirement based on the first information contained in the data packet, and select the corresponding transmission channel for transmission based on that requirement.

[0082] In one alternative implementation, the first information includes at least one of the following:

[0083] (1) A first index and a first indication information, wherein the first index is used to indicate a fixed value of a first QoS parameter and the first indication information is used to indicate a variable value of one or more specific QoS parameters; it is understood that the first index may specifically correspond to one or more fixed values ​​of a first QoS parameter.

[0084] (2) The second index is used to indicate the value of the second QoS parameter and the corresponding PDU set; it can be understood that the second index can specifically correspond to one or more fixed values ​​of the second QoS parameter.

[0085] (3) The third index and the fourth index: the third index indicates the value of the third QoS parameter, and the fourth index indicates the PDU set. It can be understood that the third index specifically corresponds to one or more fixed values ​​of the third QoS parameter;

[0086] In this application embodiment, several implementation methods for data packet carrying information are provided to achieve flexible transmission mapping in the technical solution of this application:

[0087] Method 1: Corresponding to (1) above:

[0088] The data packet carries a first index (also known as the first QoS index). Based on the first index and the pre-configuration in the previous CP process, the fixed values ​​of one or more first QoS parameters can be obtained. The data packet also carries first indication information, which is used for the variable values ​​of one or more specific QoS parameters. That is, for some specific QoS parameters, dynamic and variable values ​​can be provided to correspond to flexible business needs. For example, a special value with higher priority can be carried to indicate that important data packets are processed first, or a special value with a higher block error rate can be carried to better ensure the success rate of important data packet transmission.

[0089] Method 2: Corresponding to (2) above:

[0090] The data packet carries a second index, which is used to jointly indicate the QoS parameters and PDU set. Based on the second index and the pre-configuration of the previous CP process, the value of one or more corresponding second QoS parameters and the corresponding PDU set can be obtained. In this way, the data packet can obtain the value of the corresponding QoS parameter and the corresponding PDU set by carrying a second index, thus realizing a more flexible transmission mapping.

[0091] Method 3: Corresponding to (3) above:

[0092] The data packet carries a third index. Based on the third index and the pre-configuration of the previous CP process, the value of one or more corresponding third QoS parameters can be obtained. The data packet also carries a fourth index. Based on the fourth index and the pre-configuration of the previous CP process, the corresponding PDU set can be obtained. In this way, by carrying the third and fourth indices, the value of the QoS parameters corresponding to the data packet and the corresponding PDU set can be obtained, realizing a more flexible transmission mapping.

[0093] In one alternative implementation, the first configuration is used to configure at least one of the following:

[0094] (1) The fixed value of the first QoS parameter corresponding to each first index, and one or more variable QoS parameter information;

[0095] (2) The value of the second QoS parameter corresponding to each second index, and the same second index corresponds to the same PDU set;

[0096] (3) The value of the third QoS parameter corresponding to each third index, and / or the range of values ​​of the fourth index.

[0097] In this application embodiment, several configuration methods are provided to achieve flexible transmission mapping in the technical solution of this application:

[0098] Method 1: Corresponding to (1) above:

[0099] Configure a fixed value for the first QoS parameter corresponding to each first index, and configure one or more variable QoS parameter information. The variable QoS parameter can be a QoS parameter other than the first QoS parameter, or it can be a certain QoS parameter among the first QoS parameters. That is, some QoS parameters in the first QoS parameter are rewritten from fixed values ​​to optional values ​​to achieve more flexible transmission demand indication.

[0100] Method 2: Corresponding to (2) above:

[0101] Configure the value of the second QoS parameter corresponding to each second index, and configure or default the same second index to correspond to the same PDU set, so that the value of the second QoS parameter and the corresponding PDU set can be obtained based on a second index;

[0102] It should be noted that Method 2 can be used in combination with Method 1. That is, the value of the second QoS parameter corresponding to the second index can be further combined with the value configuration method in Method 1, thereby further increasing the flexibility of transmission demand indication.

[0103] Method 3: Corresponding to (3) above:

[0104] Configure the value of the third QoS parameter corresponding to each third index, and / or the value range of the fourth index, to enable the acquisition of the third QoS parameter value and the corresponding PDU set based on the third and fourth indices. It should be noted that each fourth index dynamically corresponds to one PDU set (0, 1, 2…), and the correspondence between the fourth index and the PDU set is dynamic. The value range of the fourth index, such as 16, 32, or other values, means that a maximum of this many PDU sets can coexist simultaneously for the same QoS parameter value table. Used fourth indices can be wrapped around and reused, simply to distinguish different sets, similar to a sequence number (SN).

[0105] It should be noted that Method 3 can be used in combination with Method 1. That is, the value of the third QoS parameter corresponding to the third index can be further combined with the value configuration method in Method 1, thereby further increasing the flexibility of transmission demand indication.

[0106] It should be noted that the configurations of methods one through three above can be applied to data packets in different data streams respectively. That is, methods one through three above can be used in combination to increase the flexibility of data transmission mapping.

[0107] It should be noted that a data stream can be defined as a collection of data with common QoS characteristics. For example, in methods one through three above, data with the same fixed QoS parameter values ​​can all be considered a single data stream. A user's service data can contain multiple data streams, and the data packets within each data stream may have somewhat different transmission requirements.

[0108] Below are several implementation examples of the configuration methods. It should be noted that the examples are only provided to better understand the technical solution and do not mean that the solution can only be implemented according to the implementation methods shown in the examples:

[0109] Method 1:

[0110] The QoS index = n needs to be configured, which corresponds to 5 QoS parameters Yi (corresponding to specific parameters such as latency and block error rate). The values ​​of each Yi are shown in Table 1:

[0111] Table 1

[0112] In this way, once we obtain QoS index=n, we can directly match it with the specific QoS parameter values ​​in the table above, thereby clarifying the transmission requirements of this service. Subsequent mapping and transmission can then be performed according to the parameters.

[0113] Specifically, a Y6 can be defined within or outside the aforementioned five parameters, or any one of Y1-Y5 can be directly specified, giving it a variable value. This value is dynamically carried by each data packet. For example, the first data packet might have a Y6 parameter value of 10, the second data packet might have a Y6 parameter value of 100, and so on. The value of Y6 represents the actual parameter range, therefore the overhead must be calculated based on the maximum parameter value. For example, if the maximum is 1000, then 10 binary bits are required.

[0114] It is understandable that multiple variable values ​​can be specified from Y1 to Y5, for example, specifying Y2 to Y5 from Y1 to Y5 as variable values.

[0115] To further reduce overhead, the possible values ​​of Y6 can also be encoded to reduce the number of information bits carried, as shown in Table 2:

[0116] Table 2

[0117] If Y1 is variable, then if the variable Y1 field carries a new parameter value, the new parameter value will be used as the actual value of the Y1 parameter of the data packet. If Y1 is defaulted, the default value will be used, that is, the value in the table with index=n.

[0118] On the network side, multiple QoS parameter groups with index=n can be configured or defined, for example, n can be 1 to 128, for use when transmitting data packets.

[0119] Method 2:

[0120] The key point is that both QoS and PDU set need to be reflected in the index;

[0121] A typical approach, where QoS index = 0~9, corresponds to different PDU sets of QoS parameter values ​​as shown in Table 3:

[0122] Table 3

[0123] When a PDU carries QoS index 0, we know that its QoS parameters correspond to Table 3 above. When another PDU carries QoS index 0, we know that its QoS parameters also correspond to Table 3 above, and it belongs to the same set as the previous data packet. Therefore, the transmission of the set needs to be started to meet the requirements.

[0124] The reason for having 10 indices (0-9) is to distinguish different PDU sets, allowing them to appear simultaneously in the cache and be differentiated. If the earliest PDU set at index 0 has already finished transmitting or timed out and been deleted, subsequent data sets can reuse that index 0. That is, 0-9 dynamically indicate each set; the first set uses index 0, the second set uses index 1, and so on. The 10th set uses index 9, and the 11th set can still reuse index 0.

[0125] Indexes 0-9 are not fixedly assigned to any particular set, but are used dynamically to indicate that these sets all meet the QoS parameter table above, and that they are distinguished from each other by their indexes. Once the expiration time has passed, the indexes can be reused cyclically.

[0126] In particular, when defining the parameter table in Method 2, the Y6 dynamic parameter indication method of Method 1 can also be used interchangeably, allowing each PDU set or even each PDU to have its own unique Y6 parameter value;

[0127] When the QoS index is 10 to 50, it corresponds to different PDU sets with QoS parameter values ​​as shown in Table 4:

[0128] Table 4

[0129] The principle is the same as above. Indices 10-50 are used to indicate that these sets all satisfy their own parameter tables and are distinguishable from each other.

[0130] Method 3:

[0131] The key point is that the QoS index and PDU set index are two independent fields;

[0132] Define QoS index = n1, as shown in Tables 5 and 6.

[0133] Table 5

[0134] Table 6

[0135] If the first data packet has a QoS index of n1 and a PDU set index of 0, and the second data packet has a QoS index of n1 and a PDU set index of 0, then these two data packets belong to the same PDU set and have the same QoS parameters. Therefore, they need to meet the QoS transmission requirements and the overall transmission requirements of the set.

[0136] For example, if the first data packet has a QoS index of n1 and a PDU set index of 0, and the second data packet has a QoS index of n2 and a PDU set index of 0, then these two data packets belong to the same PDU set, but have different QoS parameters. Therefore, they need to meet their respective QoS transmission requirements while also meeting the overall transmission requirements of the set.

[0137] In particular, when defining the parameter table in Method 3, the Y6 dynamic parameter indication method of Method 1 can also be used interchangeably, allowing each PDU set or even each PDU to have its own unique Y6 parameter value.

[0138] In one alternative implementation, the multiple transmission channels include at least one of the following:

[0139] (1) Multiple transmission channels corresponding to multiple different PDCP entities, one of which corresponds to one RLC entity; referred to as mapping method 1;

[0140] (2) Multiple transmission channels corresponding to multiple different RLC entities, where one PDCP entity corresponds to multiple RLC entities; referred to as mapping method 2;

[0141] In this application embodiment, two methods for dividing transmission channels and corresponding processing methods are given, wherein mapping method 1 and mapping method 2 are shown in Figure 3.

[0142] Mapping method 1:

[0143] SDAP or a new service adaptation layer entity is responsible for parsing data packets from higher layers based on at least one of their carried QoS and service attribute information. According to configured rules, it determines the multiple transmission channels that the packet can be mapped to, and selects one of these channels based on rules or algorithms to map the data packet to. In this approach, multiple transmission channels are represented by multiple PDCP entities, i.e., multiple DRBs. Each channel can be configured with different transmission parameters, such as different RLC transmission modes (AM or UM), RLC transmission parameters (SN length, timer length, etc.), and different transmission priorities. Based on the transmission requirements of each data packet or set of data packets, it determines which DRB or PDCP entity to map them to. Furthermore, once the initial mapping is completed, changes to the mapping relationship are generally not allowed midway.

[0144] Mapping method 2:

[0145] SDAP or a new service adaptation layer entity is responsible for parsing data packets from higher layers based on at least one of their carried QoS and service attribute information. According to configured rules, it determines the multiple transmission channels that can be mapped to the packet and selects one of these channels based on rules or algorithms. For example, this could be a PDCP entity, corresponding to a DRB. In this approach, multiple transmission channels can be represented as multiple PDCP entities (i.e., multiple DRBs), or as multiple RLC entities under a single PDCP entity, or even a combination of both, where multiple RLC entities under multiple PDCP entities each correspond to a specific channel. Alternatively, a two-level channel selection can be used: first, a PDCP-level channel is selected based on core transmission requirements; then, from the secondary channels of the multiple RLC entities corresponding to the PDCP entity, the channel that best meets the transmission requirements and current situation, and provides a better transmission experience, is selected. Each channel can be configured with different transmission parameters, such as different RLC transmission modes (AM or UM), RLC transmission parameters (SN length, timer length, etc.), and different transmission priorities. Based on the transmission requirement characteristics of each data packet or set of data packets, it determines which PDCP and RLC entities they are mapped to. This method is more complex than mapping method 1 because it involves two levels of pipeline mapping, but it also offers greater flexibility. After the initial mapping is completed, the RLC entity can be selected or swapped again based on the current transmission status, remaining PDB, and other factors.

[0146] It should be noted that the number of entities in Figure 3 is only an example.

[0147] In one alternative implementation, the method further includes:

[0148] The terminal determines the target transmission channel from multiple transmission channels based on the first rule pre-configured or configured by the network-side device;

[0149] The first rule includes at least one of the following:

[0150] (1) If the data packet has one or more variable values ​​of specific QoS parameters as determined by the first information, the data packet is mapped to the transmission channel corresponding to the specific QoS parameter; even if the QoS indicators are the same, but the data packet is identified as having a more important role, such as some special frames in XR video frames that carry additional control information, the pipeline with better transmission parameters can be directly selected for mapping according to the configuration rules.

[0151] (2) If multiple data packets are determined to belong to the same PDU set and have the same QoS parameters based on the first information, the multiple data packets are mapped to the same transmission channel; when determining resources in Logical Channel Prioritization (LCP), a set can be treated as a whole for unified calculation. For example, according to LCP priority and token bucket rules, when it is the turn of the channel to transmit data, the entire set is treated as a whole for resource calculation and allocation at the same time, so that it can be transmitted together or in succession as much as possible;

[0152] (3) If multiple data packets belong to the same PDU set and have different QoS parameters according to the first information, the multiple data packets are mapped to different transmission channels according to their respective QoS parameters. In this way, data packets belonging to the same set are mapped to different channels. When allocating and processing LCP resources, attention should be paid to their correlation, such as ensuring set delay, ensuring set error block, and the overall packet loss mechanism of the set. This is also to ensure that they can be transmitted together or sequentially, and to avoid high priority being transmitted successfully first, while low priority is deleted due to timeout, which would make the set meaningless and waste the resources consumed by the previously successfully transmitted data.

[0153] (4) If, based on the first information, multiple data packets belong to the same PDU set and have different QoS parameters, the multiple data packets are mapped to the same transmission channel according to the second rule, wherein the second rule is associated with at least one of the QoS parameter priority and QoS parameter value. For example, the transmission channel is selected according to the most important data packet or the highest priority QoS attribute, or according to the lowest priority QoS attribute, or the median QoS attribute, or according to a combination of QoS attributes (the combination method can be selecting the highest, lowest, average, etc. for each parameter), or according to a specified QoS.

[0154] In one alternative implementation, the method further includes:

[0155] The terminal sets the total priority bit rate (PBR) of multiple logical channels corresponding to the data stream based on the data stream configuration information;

[0156] The total PBR of the multiple logical channels corresponding to the data stream satisfies any one of the following:

[0157] (1) When the QoS parameters corresponding to the data stream include the guaranteed stream bit rate GFBR, the first PBR is determined according to the GFBR, and the first PBR is determined as the total PBR of multiple logical channels corresponding to the first information.

[0158] (2) If the QoS parameters corresponding to the data stream do not include the GFBR, the second PBR is determined according to the preset value, and the second PBR is determined as the total PBR of the multiple logical channels corresponding to the first information.

[0159] In one alternative implementation, the method further includes:

[0160] (1) The terminal obtains the target resource based on the total PBR of multiple logical channels corresponding to the first information;

[0161] (2) The terminal allocates target resources in descending order of priority of multiple logical channels.

[0162] After obtaining the first configuration as described above, the PBR is determined because the PBR is based on the GFBR in the QoS parameters, and it is not dynamically changed every time a packet is transmitted.

[0163] If GFBR=x1 is present in the QoS parameters, it means that the data stream represented by this QoS needs to have a guaranteed bit rate as a whole. If the data of this QoS stream is configured to be mapped to 3 logical channels, then the total PBR of these 3 logical channels should be set to x1. If there is another QoS stream with GFBR=x2, which is also configured to be mapped to the same 3 logical channels, then the total PBR of these 3 logical channels should be set to x1+x2.

[0164] Another approach is that if the QoS parameters do not include GFBR, it indicates that the data stream represented by this QoS does not require overall bit rate guarantee. In this case, if the data of this QoS stream is configured to be mapped to 3 logical channels, the total PBR of these 3 logical channels can be set to z (this z is the implementation of the base station algorithm, a small value to avoid starving the non-GBR service). If there is another QoS stream, also belonging to non-GBR, and also configured to be mapped to the same 3 logical channels, then the total PBR of these 3 logical channels should be set to 2*z, or z1+z2, etc., all of which are implemented by the base station.

[0165] Once configured, the PBR of the logical channel group is a fixed value. If it needs to be modified, it can be achieved through reconfiguration, that is, by going through the CP (Control Plane) process again.

[0166] Each time a packet is sent, each data packet is mapped to one of the logical channels based on the first information. Therefore, it must also comply with the overall PBR (Priority Requirement Ratio) of the logical channel group to which that logical channel belongs. That is, multiple logical channels are treated as a whole and compete for resources with other logical channel groups based on the PBR parameters. This resource competition process can use existing methods, the difference being that existing methods allocate resources to each logical channel based on its individual PBR and the LCP (Logical Channel Prioritization) algorithm. In this application, multiple logical channels are treated as a whole, and the LCP algorithm is run to allocate resources for the entire group. After obtaining resources, within the multiple logical channels, resources are acquired sequentially according to priority from highest to lowest.

[0167] In one alternative implementation, the method further includes:

[0168] The terminal sends the first capability information to the network-side device;

[0169] The first capability information is used to indicate whether the terminal supports a one-to-many mapping relationship between data streams and multiple transmission channels.

[0170] Whether a UE supports flexible QoS mapping is a UE capability. For example, a separate capability indicator can be set to indicate whether the function is supported, or even more detailed indicators can be added to indicate whether the function is supported. These can be reported as UE capability content, or they can be bound to the UE version information. For example, 6G UEs support it, while 5G and earlier UEs do not. Not only does the RAN need this capability to determine the air interface configuration, but the CN also needs this capability to determine the QoS configuration of the interaction and the details of the information carried by the data packets. Therefore, the relevant capability needs to be reported to the RAN and CN and stored in the CN, similar to other existing UE capability information.

[0171] In one alternative implementation, the method further includes:

[0172] The terminal receives the second configuration from the network-side device;

[0173] The second configuration is used to reconfigure the one-to-many mapping relationship between the data stream and multiple transmission channels.

[0174] In practical use, reconfiguration is allowed. For example, if there are changes in services or service composition / requirements, or changes in network status, the mapping method needs to be reconfigured. For example, the configuration of 3 (QoS or service attributes) to 3 (transmission pipes) can be changed to 3 to 1, or 2 to 2, etc. The simplest way to reconfigure is to release first and then add, which is the simplest, but the effect is not good and may cause packet loss and service continuity issues. If you want to ensure service continuity to a certain extent, you can delete the reduced pipes and keep the status of the retained pipes, or perform certain retransmission or recovery operations to ensure service continuity.

[0175] Referring to Figure 4, this application embodiment provides a transmission configuration method, the execution subject of which is a network-side device, including:

[0176] Step 401: The network-side device sends the first configuration to the terminal;

[0177] The first configuration is used to configure the one-to-many mapping relationship between the data stream and multiple transmission channels.

[0178] It should be noted that, as the counterpart device interacting with the terminal, the execution steps and interactive information content involved in the method of the network-side device should be understood in the same way as those of the terminal side. Therefore, the understanding of the various technical features in the network-side method can refer to the relevant content on the terminal side, and the embodiments of this application will not repeat them here.

[0179] In one alternative implementation, the first configuration is used to configure at least one of the following:

[0180] The fixed value of the first QoS parameter corresponding to each first index, and one or more variable QoS parameter information;

[0181] The value of the second QoS parameter corresponding to each second index, and the same second index corresponds to the same PDU set;

[0182] The value of the third QoS parameter corresponding to each third index, and / or the range of values ​​for the fourth index.

[0183] In one alternative implementation, the multiple transmission channels include at least one of the following:

[0184] Each PDCP entity corresponds to a different transmission channel, and one PDCP entity corresponds to one RLC entity.

[0185] Each PDCP entity corresponds to multiple transmission channels of multiple different RLC entities, with one PDCP entity corresponding to multiple RLC entities.

[0186] In one alternative implementation, the method further includes:

[0187] The network-side device configures the first rule for the terminal;

[0188] The first rule includes at least one of the following:

[0189] If it is determined from the first information that the data packet has one or more variable values ​​of a specific QoS parameter, the data packet is mapped to the transmission channel corresponding to the specific QoS parameter.

[0190] If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have the same QoS parameters, the multiple data packets are mapped to the same transmission channel.

[0191] If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have different QoS parameters, the multiple data packets are mapped to different transmission channels according to their respective QoS parameters.

[0192] If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have different QoS parameters, the multiple data packets are mapped to the same transmission channel according to the second rule, wherein the second rule is associated with at least one of the QoS parameter priority and the QoS parameter value;

[0193] The first piece of information is used to indicate at least one of the QoS information and the service attribute information of the data stream.

[0194] In one alternative implementation, the method further includes:

[0195] Network-side devices receive first capability information from the terminal;

[0196] The first capability information is used to indicate the one-to-many mapping relationship between the data stream and multiple transmission channels.

[0197] In one alternative implementation, the method further includes:

[0198] The network-side device receives the second configuration from the terminal;

[0199] The second configuration is used to reconfigure the one-to-many mapping relationship between the data stream and multiple transmission channels.

[0200] In one alternative implementation, the method further includes:

[0201] During cell handover, the source cell sends data streams to the target cell, and there is a one-to-many mapping relationship between multiple transmission channels.

[0202] In handover scenarios, when both the originating and target cells support flexible QoS mapping, the originating cell's configuration can be easily transferred to the target cell during handover preparation. The target cell can refer to this configuration to maximize handover continuity. Simultaneously, L2 operations at all levels can be referenced, such as PDCP entity UM reset, AM reconstruction, and support for certain data forwarding and retransmission mechanisms. If the originating cell supports flexible QoS mapping but the target cell does not, the target cell essentially deletes its original configuration and reconfigures it, the L2 entity deletes its state, and new operations are re-established. If the originating cell does not support flexible QoS mapping but the target cell does, the target cell can perform a new configuration, again the L2 entity deletes its original state, and new, more channels and entities are re-established.

[0203] The technical solutions of the embodiments of this application are further described below:

[0204] Example 1: Configuration

[0205] This embodiment focuses on explaining the principles, mechanisms, and configuration process of the new QoS architecture and data mapping function.

[0206] In the existing QoS flow to DRB mapping, a QoS flow can only be semi-statically mapped to one DRB. That is, once the RRC configuration mapping relationship takes effect, all data of that QoS flow can only be mapped to this configured DRB for first-in-first-out transmission. This mapping method limits the flexibility in ensuring the diverse needs of service data.

[0207] With the further maturation of applications such as XR, virtual reality, and robotics, more diverse and flexible demands have emerged for data classification and integration, as well as the transmission of business data. For example, in XR frames, some important data frames require higher transmission specifications, while ordinary frames can prioritize resource efficiency. In this case, for data from the same source, the QoS requirements are basically the same, although important data frames may require a block error rate of 10^-4, while ordinary frames can tolerate a block error rate of 10^-3. In traditional QoS models, these two types of data are usually mapped to the same QoS flow and the same DRB, making it impossible to differentiate between them. Alternatively, a very small number of important frames may be mapped to separate QoS flows and separate DRBs to ensure slightly differentiated transmission treatment. However, this significantly increases the consumption of the transmission pipeline and imposes heavier transmission overhead on the air interface. In emerging businesses, for example, data requirements are more precisely segmented. Based on the characteristics and needs of the business sources, specific metrics need to be defined for certain PDUs or PDU sets. Even the QoS requirements of the PDUs that make up these sets may differ. A typical example is immersive virtual reality, where image, sound, smell, and tactile data collected from a remote environment need to be synchronously transmitted to the other end and recreated as a realistic scene. The original transmission requirements for these data are different, but they also need to be correlated and synchronized, which cannot be achieved using existing QoS models.

[0208] This proposal suggests a dynamic mapping method that redefines the granularity and dimensions of QoS. It flexibly maps data packets carrying at least one of QoS and service information to the air interface transmission channel, while fully considering existing transmission capabilities to better meet precise transmission requirements. The main ideas include at least one of the following:

[0209] First, introduce packet classification and QoS parameters, as well as service information carrying mechanisms, that are finer than the QoS flow granularity. For example:

[0210] (1) Combining QoS index with incremental information, the QoS index can be semi-statically configured. Each QoS index corresponds to a set of complete or partial QoS parameter values. For example, if the QoS parameter set consists of 10 parameters, a QoS index configuration can give default values ​​for all 10 parameters, or give default values ​​for 8 of them. In the actual transmission of data packets, if a data packet or PDU set only carries the QoS index, its transmission requirement is the default 10 QoS parameter values. If another data packet or PDU set carries the QoS index and also carries one or more special values ​​for QoS parameters, its transmission requirement is the default QoS parameter values ​​plus the additional special values. If there are duplicate parameters, the special values ​​will always replace the default values. In this way, QoS parameters can be carried more flexibly. For example, higher priority special values ​​can be carried to indicate that important data packets are processed first, or higher error rate special values ​​can be carried to better ensure the success rate of important data packet transmission. Both can even be combined to improve the transmission rate simultaneously.

[0211] (2) The QoS index and PDU set are jointly indicated. For example, indexes 0-9 indicate different PDUs or different PDU sets with the same QoS parameter set 1, indexes 10-12 indicate different PDUs or different PDU sets with another QoS parameter set 2, and index 13 indicates a PDU or PDU set with QoS parameter set 3. In this case, if a data packet carries index 0, we can know its corresponding QoS parameter set 1, and map it to the transmission pipe according to QoS parameter set 1. Then another data packet carries index 0. These two data packets should belong to the same PDU set, and they are processed uniformly according to the parameters of the PDU set. The reason for reserving different numbers of indexes when corresponding to the same QoS parameter set is that parameter set 1 reserves 10 indexes, parameter set 2 reserves 3 indexes, and parameter set 3 reserves only one index. This is also based on the number and probability of concurrent PDU sets in each parameter set. In principle, after a PDU set is successfully sent or deleted after timeout, the received data packet can reuse the previous index without causing confusion.

[0212] (3) PDU sets are formed across QoS requirements. Since multiple data may belong to different QoS attributes, such as sound, image, touch, and taste, which have different transmission index requirements and can have different QoS attributes, but these data may serve the same scenario at the same time, it is necessary to classify data with different QoS attributes into the same PDU set for certain collaborative processing. At this time, two pieces of information can be used to accomplish this purpose. One is the QoS index, which indicates the QoS attributes required by the data packet and corresponds to a specific QoS parameter set. The other is the PDU set index. For example, data packets belonging to the same PDU set carry the same PDU set index mark, so that the transmission end can know that they need to apply the PDU set index to meet some transmission performance requirements.

[0213] Secondly, it is necessary to configure the transmission channels corresponding to these service data packets, such as DRB and DRB parameters, or RLC channel / RLC bearer, etc. Generally speaking, in order to achieve flexible dynamic mapping, multiple channels need to be configured, and these channels have different transmission parameters, such as different RLC transmission modes, different RLC transmission parameters, different MAC transmission priorities, different MAC transmission parameters, etc., so that different data can be flexibly mapped to different channels for more refined transmission treatment, or for some remaining packets in the PDU set that are about to time out, they can be flexibly mapped to higher priority channels to temporarily increase their priority and ensure the overall success of the entire PDU set.

[0214] In addition, for at least one of the data packets carrying different QoS information and service information, the mapping relationship between the transmission channel DRB or RLC channel / RLC bearer can be implemented by the network algorithm for downlink. However, for uplink, since the mapping is performed by the UE, in order to avoid poor or uncontrolled implementation by the UE, the network side can also configure some rules at the same time. For example, data packets that meet feature 1 can be flexibly mapped to channel 1 and channel 2, data packets that meet feature 2 cannot be mapped to channel 1, data packets that do not meet feature 3 can only be mapped to channel 3, data packets that meet feature 4 cannot be mapped to channels 3 and 4, etc., so as to constrain the UE to perform flexible mapping within the allowed range.

[0215] The flexible mapping rules and configurations described above can be summarized as configuring multiple transmission channels for at least one of various QoS information and service attributes. These channels have a many-to-many mapping relationship, and additional mapping rules can be configured for uplink. The ultimate goal is to dynamically and flexibly schedule and utilize multiple transmission channels to better meet transmission requirements for more refined QoS and service attribute needs, as shown in Figure 5 (where DRB is used as an example channel, and different fills represent different channels).

[0216] Additionally, it should be noted that the flexible and dynamic new mapping method can coexist with the traditional QoS mapping method. Within a base station, some UEs adopt the flexible and dynamic new mapping method, while other traditional UEs adopt the traditional QoS mapping method. Alternatively, within a UE, some traditional services, due to their lack of flexibility, can be configured with the traditional QoS mapping method, while the flexible and dynamic new mapping method can be configured for new services. The two methods operate independently.

[0217] Example 2: Transmission Pipeline

[0218] This embodiment provides a method for dividing different transmission channels and corresponding processing methods.

[0219] Figure 3 shows two typical examples of multiple transmission channels.

[0220] Method 1:

[0221] In mapping method 1 on the left side of Figure 3, SDAP or a new service adaptation layer entity is responsible for parsing data packets from higher layers according to at least one of their carried QoS information and service attribute information. Based on configured rules, it determines the multiple transmission channels that can be mapped, and selects one channel according to rules or algorithms to map the data packet. In this method, multiple transmission channels are represented by multiple PDCP entities, i.e., multiple DRBs. Each channel can be configured with different transmission parameters, such as different RLC transmission modes (AM or UM), RLC transmission parameters (SN length, timer length, etc.), different transmission priorities, etc. Based on the transmission requirements of each data packet or set of data packets, it determines which DRB or PDCP entity to map them to. Moreover, once the initial mapping is completed, it is generally not allowed to change the mapping relationship midway.

[0222] Method 2:

[0223] In mapping method 2 on the right side of Figure 3, SDAP or a new service adaptation layer entity is responsible for parsing data packets from higher layers according to at least one of their carried QoS and service attribute information. Based on the configured rules, it determines the multiple transmission channels that can be mapped and selects one of them according to the rules or algorithm. For example, it could be one of the PDCP entities, corresponding to one of the DRBs. In this method, multiple transmission channels can be represented as multiple PDCP entities (i.e., multiple DRBs), or as multiple RLC entities under one PDCP entity, or even a combination of both, where each of the multiple RLC entities under multiple PDCP entities corresponds to a specific channel. Alternatively, there can be a two-level channel selection: first, a PDCP-level channel is selected based on core transmission requirements; then, among the secondary channels of the multiple RLC entities corresponding to the PDCP entity, the channel that best meets the transmission requirements and current situation, and can better satisfy the transmission experience, is selected. Each pipeline can be configured with different transmission parameters, such as different RLC transmission modes (AM or UM), RLC transmission parameters (SN length, timer length, etc.), and different transmission priorities. Based on the transmission requirements of each data packet or set of data packets, it is determined to map them to the corresponding PDCP entity and RLC entity. This method is more complex than Method 1 because it involves two levels of pipeline mapping, but it also offers greater flexibility. After the initial mapping is completed, the RLC entity can be selected or changed again based on the current transmission status, remaining PDB, and other factors.

[0224] A typical example is that when a service is established, it is configured to correspond to two PDCP entities. The first PDCP entity is configured with RLC UM transmission mode, which can transmit data with short latency and low reliability requirements. The second PDCP entity is configured with RLC AM transmission mode, which can transmit data with low latency but higher reliability requirements.

[0225] The two RLC UM entities connected under the first PDCP entity can correspond to different transmission priorities. RLC UM entity 1 has a lower priority and can be used to transmit regular data, while RLC UM entity 2 has a higher priority and can be used to transmit higher-priority data or data that is about to time out. In a typical application, when data arrives, it is first mapped or pre-mapped to RLC UM entity 1, where the data has not been transmitted. If data is found to be about to time out, especially if the PDU set has already transmitted most of its data and only a small amount remains, in order to avoid wasting the transmission resources in the early stages and ensure the success of the entire set, it can be switched to RLC UM entity 2 to ensure priority transmission as soon as possible.

[0226] The two RLC UM entities connected under the first PDCP entity can also correspond to different transmission carrier groups. RLC UM entity 1 corresponds to regular transmission, while RLC UM entity 2 corresponds to duplication or faster transmission. When ordinary data arrives, it can be mapped to RLC UM entity 1 first. If special high-priority data, high-reliability data, or data that is about to time out are found, a copy of the data in RLC UM entity 1 can be backed up and transmitted in RLC UM entity 2 to speed up the transmission process and improve reliability.

[0227] Furthermore, under the second PDCP entity, two or more RLC AM entities can be connected, each with different transmission parameters, such as different timer lengths or trigger status reports and retransmission parameters. This allows for a comprehensive approach based on service characteristics such as latency, importance, and set, differentiating between the trade-offs between latency and overhead for different service feedback and retransmissions, thus achieving dynamic and flexible control. In the case of the second PDCP entity, if data mapped to the previous RLC AM entity is still in the buffer and has not been transmitted or assigned a SN, it can be switched to the second RLC AM entity for transmission; otherwise, it cannot be switched.

[0228] Example 3: Transmission Operation

[0229] The first two embodiments illustrate the basic mechanism of dynamic mapping and examples of transmission channels. This embodiment explains other issues in specific operations.

[0230] For downlink data, once multiple transmission channels, DRB, PDCP entities, and RLC entities are configured, the arrival of downlink data packets can be mapped to these channels for transmission, and even the mapping relationship can be dynamically adjusted. This can all be done on the network side. Moreover, the network side has a grasp of the status of all UEs and can better balance the data among multiple UEs, avoiding the disruption of overall efficiency and priority due to the data of one UE.

[0231] The more complex and difficult aspect is the dynamic mapping and adjustment of uplink data. Without constraints, this can lead to poor performance on some individual UEs, compromising overall system efficiency and the experience of other users. Therefore, while allowing dynamic mapping and adjustment, better rules need to be configured or defined to facilitate UE implementation, including at least one of the following:

[0232] For data packets carrying special QoS parameters or service source identification information, such as data packets with incremental or overriding new QoS indicators based on the default QoS index, or even data packets with the same QoS index but identified as having a more important role, such as some special frames in XR video frames carrying additional control information, the pipeline with better transmission parameters can be directly selected for mapping according to the configuration rules.

[0233] For packets belonging to the same PDU set, when they have the same QoS attributes, the same pipe can be selected for mapping first. When LCP determines resources, a set can be treated as a whole for unified calculation. For example, according to LCP priority and token bucket rules, when it is the turn of the pipe to transmit data, the entire set is treated as a whole for resource calculation and allocation at the same time, so as to transmit together or in succession as much as possible.

[0234] For data packets belonging to the same PDU set, when they have different QoS attributes, one approach is to perform pipeline mapping according to their respective attributes. In this way, data packets belonging to the same set are mapped to different pipelines. When allocating and processing LCP resources, attention needs to be paid to their correlation, such as ensuring set latency, ensuring set error blocking, and the overall set packet loss mechanism. This also ensures that they can be transmitted together or sequentially, avoiding situations where high-priority packets are successfully transmitted first, while low-priority packets are deleted due to timeouts, causing the entire set to become meaningless and wasting the resources consumed by the previously successfully transmitted data.

[0235] For data packets belonging to the same PDU set, when they have different QoS attributes, a unified mapping rule can be adopted. For example, the pipeline can be selected according to the most important data packet or the highest priority QoS attribute, or according to the lowest priority QoS attribute, or the median QoS attribute, or according to a combination of QoS attributes (the combination method can be the highest, lowest, average, etc. for each parameter), or according to a specified QoS. The above rules can also be configured by the network to configure different methods as needed. After selecting the same pipeline for mapping, when LCP determines resources, a set can be treated as a whole for unified calculation. For example, according to LCP priority and token bucket rules, when it is the pipeline's turn to transmit data, the entire set is treated as a whole for resource calculation and allocation at the same time, so as to transmit together or in succession as much as possible.

[0236] LCP (Local Protocol Configuration) is a crucial rule for the UE to allocate and occupy resources across various channels, directly determining the transmission performance and user experience of each channel. Dynamic mapping and multiple channels will bring changes to LCP rules. For example, traditionally, the CN (Network Controller) distributes GFBR (Guarantee Bit Rate) parameters based on each QoS flow, meaning there is a guaranteed bit rate requirement based on the QoS flow granularity, which can be used as LCP input. When QoS adopts finer-grained attributes, such as per PDU or PDU set carrying differentiated attributes, it is obviously not suitable to define the rate at such a fine granularity as PDU or PDU set, because the rate is an average over a certain time range. Therefore, it is still possible to define GBR (Guarantee Bit Rate) or PBR (Prioritized Bit Rate) at a relatively larger granularity, such as the QoS set corresponding to the PDU set, i.e., all PDU sets that satisfy approximately the same QoS. From the perspective of MAC layer operations, several logical channels with similar priorities may share a single PBR parameter. The processing within these logical channels can be handled by the UE, or the total PBR can be allocated to each logical channel. Ultimately, there are two PBR processing methods for LCP. One is to uniformly allocate PBRs based on logical channel groups with similar QoS. The PBR of each logical channel group allocates resources according to priority rules and token bucket rules, from high to low priority. Resource allocation within the logical channel group is an implementation. Alternatively, each logical channel has its own PBR. Each logical channel allocates resources according to its own priority and token bucket rules, from high to low priority. The former takes into account the overall integrity of similar logical channels and leaves room for dynamic adjustment within the group, while the latter has simpler rules.

[0237] Dynamic adjustment rules: Dynamic adjustment generally occurs when a data packet is about to exceed its QoS parameters on a channel that meets its own QoS standards, such as due to timeout or loss of the packet causing previous successful transmissions to be wasted. Therefore, it needs to be moved to a channel with better QoS or higher parameter rules. This is equivalent to temporarily using a higher priority or consuming more AM configuration to improve its transmission performance. This behavior is certainly beneficial for the current data packet, the PDU set it represents, and even the current UE. However, because of this temporary upgrade, it actually disrupts the priority system and normal transmission of other data packets or other UEs. Therefore, rules need to be established for this upgrade behavior to prevent misuse. For example, dynamic adjustment to the upgraded channel is only allowed when the remaining PDB is less than a threshold, or when the remaining PDB is less than a percentage of the PDB value; or when congestion occurs on a normal channel, dynamic adjustment of the remaining data packets in the PDU set to the upgraded channel is allowed, etc.

[0238] Example 4: Capabilities, Reconfiguration / Switching Process

[0239] The previous embodiments provided configuration and operation methods. This embodiment describes the impact of flexible QoS mapping methods on UE capabilities, reconfiguration, and handover processes.

[0240] First, whether a UE supports flexible QoS mapping is a UE capability. For example, a separate capability indicator can be set to indicate whether the function is supported, or even more detailed indicators can be added to report as UE capability content. Alternatively, it can be bound to the UE version information, such as 6G UEs supporting it, while 5G and earlier UEs do not. Not only does the RAN side need this capability to determine the air interface configuration, but the CN side also needs this capability to determine the QoS configuration of the interaction and the details of the information carried by the data packets. Therefore, the relevant capability needs to be reported to the RAN and CN and stored in the CN, similar to other existing UE capability information.

[0241] Secondly, the preceding embodiments have provided many examples of flexible QoS mapping methods in a configuration manner. In actual use, reconfiguration is also allowed. For example, if the service or service composition / requirements change, or the network status changes, the mapping method needs to be reconfigured. For example, the configuration of 3 (QoS or service attributes) to 3 (transmission pipes) can be changed to 3 to 1, or 2 to 2, etc. The simplest way to reconfigure is to release first and then add, which is the simplest, but the effect is not good and may cause packet loss and service continuity problems. If service continuity needs to be ensured to a certain extent, the reduced pipes can be deleted, the status of the retained pipes can continue, or certain retransmission or recovery operations can be performed to ensure service continuity.

[0242] Secondly, in handover scenarios, when both the original and target cells support flexible QoS mapping, the original cell's configuration can be easily transferred to the target cell during handover preparation. The target cell can refer to this configuration to maximize handover continuity. Simultaneously, L2 operations at all levels can be referenced, such as PDCP entity UM reset, AM reconstruction, and support for certain data forwarding and retransmission mechanisms. If the original cell supports flexible QoS mapping but the target cell does not, the target cell essentially deletes its original configuration and reconfigures it, the L2 entity deletes its state, and the new operation is rebuilt. If the original cell does not support flexible QoS mapping but the target cell does, the target cell can perform a new configuration, again the L2 entity deletes its original state, and new, more channels and entities are re-established.

[0243] This application provides a transmission configuration device. As an example, the transmission configuration device may be a communication device or a component within a communication device, such as a chip. The communication device may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 11 listed above, and the network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0244] The transmission configuration device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0245] Specifically, referring to Figure 6, when the transmission configuration device is a terminal or a component within a terminal, the transmission configuration device 600 includes:

[0246] The first receiving module 601 is used to receive the first configuration from the network-side device;

[0247] The first processing module 602 is used to determine a one-to-many mapping relationship between the data stream and multiple transmission channels according to the first configuration.

[0248] Optionally, the device further includes:

[0249] The second processing module is used for:

[0250] Acquire data packets from a data stream, the data packets containing first information;

[0251] Based on the first information, a PDU set or PDU is sent to the peer communication device using the target transmission channel among multiple transmission channels;

[0252] The first information is used to indicate at least one of the QoS information and the service attribute information of the data stream, and each different first information maps to one or more transmission channels.

[0253] Optionally, the first information includes at least one of the following:

[0254] A first index and first indication information, wherein the first index is used to indicate a fixed value of a first QoS parameter, and the first indication information is used to indicate a variable value of one or more specific QoS parameters;

[0255] The second index is used to indicate the value of the second QoS parameter and the corresponding PDU set;

[0256] The third index and the fourth index, wherein the third index is used to indicate the value of the third QoS parameter, and the fourth index is used to indicate the PDU set.

[0257] Optionally, the first configuration is used to configure at least one of the following:

[0258] The fixed value of the first QoS parameter corresponding to each first index, and one or more variable QoS parameter information;

[0259] The value of the second QoS parameter corresponding to each second index, and the same second index corresponds to the same PDU set;

[0260] The value of the third QoS parameter corresponding to each of the third indices, and / or the value range of the fourth index.

[0261] Optionally, the plurality of transmission channels include at least one of the following:

[0262] Each PDCP entity corresponds to a different transmission channel, and one PDCP entity corresponds to one RLC entity.

[0263] Each PDCP entity corresponds to multiple transmission channels of multiple different RLC entities, with one PDCP entity corresponding to multiple RLC entities.

[0264] Optionally, the device further includes:

[0265] The third processing module is used to determine the target transmission channel from multiple transmission channels according to a first rule pre-configured or configured by the network-side device.

[0266] The first rule includes at least one of the following:

[0267] If it is determined from the first information that the data packet has one or more variable values ​​of the specific QoS parameter, the data packet is mapped to the transmission channel corresponding to the specific QoS parameter;

[0268] If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have the same QoS parameters, the multiple data packets are mapped to the same transmission channel;

[0269] If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have different QoS parameters, the multiple data packets are mapped to different transmission channels according to their respective QoS parameters.

[0270] If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have different QoS parameters, the multiple data packets are mapped to the same transmission channel according to the second rule, wherein the second rule is associated with at least one of the QoS parameter priority and the QoS parameter value.

[0271] Optionally, the device further includes:

[0272] The fourth processing module is used to set the total PBR of multiple logical channels corresponding to the data stream according to the configuration information of the data stream;

[0273] Wherein, the total PBR of the multiple logical channels corresponding to the data stream satisfies any one of the following:

[0274] If the QoS parameters corresponding to the data stream include GFBR, the first PBR is determined according to the GFBR, and the first PBR is determined as the total PBR of the multiple logical channels corresponding to the first information.

[0275] If the QoS parameters corresponding to the data stream do not include the GFBR, the second PBR is determined according to a preset value, and the second PBR is determined as the total PBR of the multiple logical channels corresponding to the first information.

[0276] Optionally, the device further includes:

[0277] The fifth processing module is used for:

[0278] Based on the total PBR of the multiple logical channels corresponding to the first information, the target resource is obtained;

[0279] The target resources are allocated according to the priority of the plurality of logical channels in descending order.

[0280] Optionally, the device further includes:

[0281] The first sending module is used to send first capability information to the network-side device;

[0282] The first capability information is used to indicate whether the one-to-many mapping relationship between the data stream and multiple transmission channels is supported.

[0283] Optionally, the device further includes:

[0284] The second receiving module is used to receive the second configuration from the network-side device;

[0285] The second configuration is used to reconfigure the one-to-many mapping relationship between the data stream and multiple transmission channels.

[0286] Referring to Figure 7, when the transmission configuration device is a network-side device or a component within a network-side device, the transmission configuration device 700 includes:

[0287] The second sending module 701 is used to send the first configuration to the terminal;

[0288] The first configuration is used to configure a one-to-many mapping relationship between the data stream and multiple transmission channels.

[0289] Optionally, the first configuration is used to configure at least one of the following:

[0290] The fixed value of the first QoS parameter corresponding to each first index, and one or more variable QoS parameter information;

[0291] The value of the second QoS parameter corresponding to each second index, and the same second index corresponds to the same PDU set;

[0292] The value of the third QoS parameter corresponding to each third index, and / or the range of values ​​for the fourth index.

[0293] Optionally, the plurality of transmission channels include at least one of the following:

[0294] Each PDCP entity corresponds to a different transmission channel, and one PDCP entity corresponds to one RLC entity.

[0295] Each PDCP entity corresponds to multiple transmission channels of multiple different RLC entities, with one PDCP entity corresponding to multiple RLC entities.

[0296] Optionally, the device further includes:

[0297] The sixth processing module is used to configure the first rule for the terminal;

[0298] The first rule includes at least one of the following:

[0299] If, based on the first information, it is determined that the data packet has one or more variable values ​​of a specific QoS parameter, the data packet is mapped to the transmission channel corresponding to the specific QoS parameter.

[0300] If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have the same QoS parameters, the multiple data packets are mapped to the same transmission channel;

[0301] If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have different QoS parameters, the multiple data packets are mapped to different transmission channels according to their respective QoS parameters.

[0302] If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have different QoS parameters, the multiple data packets are mapped to the same transmission channel according to the second rule, wherein the second rule is associated with at least one of QoS parameter priority and QoS parameter value;

[0303] The first information is used to indicate at least one of the QoS information and the service attribute information of the data stream.

[0304] Optionally, the device further includes:

[0305] The third receiving module is used to receive first capability information from the terminal;

[0306] The first capability information is used to indicate the one-to-many mapping relationship between the data stream and multiple transmission channels.

[0307] Optionally, the device further includes:

[0308] The fourth receiving module is used to receive the second configuration from the terminal;

[0309] The second configuration is used to reconfigure the one-to-many mapping relationship between the data stream and multiple transmission channels.

[0310] Optionally, the device further includes:

[0311] The seventh processing module is used to send the data stream and the one-to-many mapping relationship between multiple transmission channels from the source cell to the target cell during cell handover.

[0312] The apparatus provided in this application embodiment can implement the various processes implemented in the method embodiments of Figures 2 to 5 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0313] As shown in Figure 8, this application embodiment also provides a communication device 800, including a processor 801 and a memory 802. The memory 802 stores programs or instructions that can run on the processor 801. For example, when the communication device 800 is a terminal, the program or instructions executed by the processor 801 implement the various steps of the above method embodiments and achieve the same technical effect. When the communication device 800 is a network-side device, the program or instructions executed by the processor 801 implement the various steps of the above method embodiments and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0314] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG2. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal can be the device shown in FIG6. Specifically, FIG9 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0315] The terminal 900 includes, but is not limited to, at least some of the following components: radio frequency unit 901, network module 902, audio output unit 903, input unit 904, sensor 905, display unit 906, user input unit 907, interface unit 908, memory 909, and processor 910.

[0316] Those skilled in the art will understand that the terminal 900 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the processor 910 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 9 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0317] It should be understood that, in this embodiment, the input unit 904 may include a graphics processor 9041 and a microphone 9042. The graphics processor 9041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 906 may include a display panel 9061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 907 includes at least one of a touch panel 9071 and other input devices 9072. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include a touch detection device and a touch controller. Other input devices 9072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0318] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 901 can transmit it to the processor 910 for processing; in addition, the radio frequency unit 901 can send uplink data to the network-side device. Typically, the radio frequency unit 901 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0319] The memory 909 can be used to store software programs or instructions, as well as various data. The memory 909 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 909 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 909 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0320] Processor 910 may include one or more processing units; optionally, processor 910 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 910.

[0321] The processor 910 is used to receive the first configuration from the network-side device;

[0322] Processor 910 is configured to determine, based on the first configuration, a one-to-many mapping relationship between the data stream and multiple transmission channels.

[0323] Optionally, the processor 910 is used for:

[0324] Acquire data packets from a data stream, the data packets containing first information;

[0325] Based on the first information, a PDU set or PDU is sent to the peer communication device using the target transmission channel among multiple transmission channels;

[0326] The first information is used to indicate at least one of the QoS information and the service attribute information of the data stream, and each different first information maps to one or more transmission channels.

[0327] Optionally, the first information includes at least one of the following:

[0328] A first index and first indication information, wherein the first index is used to indicate a fixed value of a first QoS parameter, and the first indication information is used to indicate a variable value of one or more specific QoS parameters;

[0329] The second index is used to indicate the value of the second QoS parameter and the corresponding PDU set;

[0330] The third index and the fourth index, wherein the third index is used to indicate the value of the third QoS parameter, and the fourth index is used to indicate the PDU set.

[0331] Optionally, the first configuration is used to configure at least one of the following:

[0332] The fixed value of the first QoS parameter corresponding to each first index, and one or more variable QoS parameter information;

[0333] The value of the second QoS parameter corresponding to each second index, and the same second index corresponds to the same PDU set;

[0334] The value of the third QoS parameter corresponding to each of the third indices, and / or the value range of the fourth index.

[0335] Optionally, the plurality of transmission channels include at least one of the following:

[0336] Each PDCP entity corresponds to a different transmission channel, and one PDCP entity corresponds to one RLC entity.

[0337] Each PDCP entity corresponds to multiple transmission channels of multiple different RLC entities, with one PDCP entity corresponding to multiple RLC entities.

[0338] Optionally, the processor 910 is configured to determine the target transmission channel among multiple transmission channels according to a first rule pre-configured or configured by the network-side device;

[0339] The first rule includes at least one of the following:

[0340] If it is determined from the first information that the data packet has one or more variable values ​​of the specific QoS parameter, the data packet is mapped to the transmission channel corresponding to the specific QoS parameter;

[0341] If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have the same QoS parameters, the multiple data packets are mapped to the same transmission channel;

[0342] If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have different QoS parameters, the multiple data packets are mapped to different transmission channels according to their respective QoS parameters.

[0343] If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have different QoS parameters, the multiple data packets are mapped to the same transmission channel according to the second rule, wherein the second rule is associated with at least one of the QoS parameter priority and the QoS parameter value.

[0344] Optionally, the processor 910 is configured to set the total PBR of multiple logical channels corresponding to the data stream according to the configuration information of the data stream;

[0345] Wherein, the total PBR of the multiple logical channels corresponding to the data stream satisfies any one of the following:

[0346] If the QoS parameters corresponding to the data stream include GFBR, the first PBR is determined according to the GFBR, and the first PBR is determined as the total PBR of the multiple logical channels corresponding to the first information.

[0347] If the QoS parameters corresponding to the data stream do not include the GFBR, the second PBR is determined according to a preset value, and the second PBR is determined as the total PBR of the multiple logical channels corresponding to the first information.

[0348] Optionally, the processor 910 is used for:

[0349] Based on the total PBR of the multiple logical channels corresponding to the first information, the target resource is obtained;

[0350] The target resources are allocated according to the priority of the plurality of logical channels in descending order.

[0351] Optionally, the processor 910 is configured to send first capability information to the network-side device;

[0352] The first capability information is used to indicate whether the one-to-many mapping relationship between the data stream and multiple transmission channels is supported.

[0353] Optionally, the processor 910 is configured to receive a second configuration from the network-side device;

[0354] The second configuration is used to reconfigure the one-to-many mapping relationship between the data stream and multiple transmission channels.

[0355] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be described again here.

[0356] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiment shown in FIG4. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0357] Specifically, this application embodiment also provides a network-side device, which can be the device shown in FIG. 7. As shown in FIG. 10, the network-side device 1000 includes: an antenna 101, a radio frequency device 102, a baseband device 103, a processor 104, and a memory 105. The antenna 101 is connected to the radio frequency device 102. In the uplink direction, the radio frequency device 102 receives information through the antenna 101 and sends the received information to the baseband device 103 for processing. In the downlink direction, the baseband device 103 processes the information to be transmitted and sends it to the radio frequency device 102. The radio frequency device 102 processes the received information and transmits it through the antenna 101.

[0358] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 103, which includes a baseband processor.

[0359] The baseband device 103 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG10. One of the chips is, for example, a baseband processor, which is connected to the memory 105 via a bus interface to call the program in the memory 105 and execute the network device operation shown in the above method embodiment.

[0360] The network-side device may also include a network interface 106, such as a Common Public Radio Interface (CPRI).

[0361] Specifically, the network-side device 1000 in this application embodiment further includes: instructions or programs stored in memory 105 and executable on processor y4. The processor 104 calls the instructions or programs in memory 105 to execute the methods executed by each module shown in the figure and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0362] Specifically, this application also provides a network-side device. As shown in FIG11, the network-side device 1100 includes a processor 1101, a network interface 1102, and a memory 1103. The network-side device may be the device shown in FIG7. The network interface 1102 is, for example, a Common Public Radio Interface (CPRI).

[0363] Specifically, the network-side device 1100 in this application embodiment further includes: instructions or programs stored in memory 1103 and executable on processor 1101. Processor 1101 calls the instructions or programs in memory 1103 to execute the methods executed by each module shown in FIG7 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0364] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0365] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0366] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0367] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0368] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0369] This application also provides a wireless communication system, including: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the terminal-side method as described above, and the network-side device can be used to perform the steps of the network-side method as described above.

[0370] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0371] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0372] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A transmission configuration method, comprising: The terminal receives the first configuration from the network-side device; The terminal determines a one-to-many mapping relationship between the data stream and multiple transmission channels based on the first configuration.

2. The method according to claim 1, wherein, The method further includes: The terminal acquires data packets from the data stream, the data packets containing first information; Based on the first information, the terminal sends a PDU set or PDU to the peer communication device using a target transmission channel among multiple transmission channels. The first information is used to indicate at least one of the Quality of Service (QoS) information and the service attribute information of the data stream, and each different first information maps to one or more transmission channels.

3. The method according to claim 2, wherein, The first information includes at least one of the following: A first index and first indication information, wherein the first index is used to indicate a fixed value of a first QoS parameter, and the first indication information is used to indicate a variable value of one or more specific QoS parameters; The second index is used to indicate the value of the second QoS parameter and the corresponding PDU set; The third index and the fourth index, wherein the third index is used to indicate the value of the third QoS parameter, and the fourth index is used to indicate the PDU set.

4. The method according to any one of claims 1-3, wherein, The first configuration is used to configure at least one of the following: The fixed value of the first QoS parameter corresponding to each first index, and one or more variable QoS parameter information; The value of the second QoS parameter corresponding to each second index, and the same second index corresponds to the same PDU set; The value of the third QoS parameter corresponding to each third index, and / or the value range of the fourth index.

5. The method according to any one of claims 1 to 4, wherein, The plurality of transmission channels includes at least one of the following: Each PDCP entity corresponds to a different transmission channel, and one PDCP entity corresponds to one RLC entity. Each PDCP entity corresponds to multiple transmission channels of multiple different RLC entities, with one PDCP entity corresponding to multiple RLC entities.

6. The method according to claim 3, wherein, The method further includes: The terminal determines the target transmission channel from multiple transmission channels according to a first rule pre-configured or configured by the network-side device; The first rule includes at least one of the following: If it is determined from the first information that the data packet has one or more variable values ​​of the specific QoS parameter, the data packet is mapped to the transmission channel corresponding to the specific QoS parameter; If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have the same QoS parameters, the multiple data packets are mapped to the same transmission channel; If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have different QoS parameters, the multiple data packets are mapped to different transmission channels according to their respective QoS parameters. If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have different QoS parameters, the multiple data packets are mapped to the same transmission channel according to the second rule, wherein the second rule is associated with at least one of the QoS parameter priority and the QoS parameter value.

7. The method according to claim 1, wherein, The method further includes: The terminal sets the total priority bit rate (PBR) of the multiple logical channels corresponding to the data stream according to the configuration information of the data stream. Wherein, the total PBR of the multiple logical channels corresponding to the data stream satisfies any one of the following: When the QoS parameters corresponding to the data stream include the Guaranteed Stream Bit Rate (GFBR), the first PBR is determined based on the GFBR, and the first PBR is determined as the total PBR of the multiple logical channels corresponding to the data stream. If the QoS parameters corresponding to the data stream do not include the GFBR, the second PBR is determined according to a preset value, and the second PBR is determined as the total PBR of the multiple logical channels corresponding to the data stream.

8. The method according to claim 7, wherein, The method further includes: The terminal obtains the target resource based on the total PBR of the multiple logical channels corresponding to the data stream; The terminal allocates the target resources according to the priority of the plurality of logical channels in descending order.

9. The method according to any one of claims 1 to 8, wherein, The method further includes: The terminal sends first capability information to the network-side device; The first capability information is used to indicate whether the terminal supports a one-to-many mapping relationship between the data stream and multiple transmission channels.

10. The method according to any one of claims 1 to 8, wherein, The method further includes: The terminal receives a second configuration from the network-side device; The second configuration is used to reconfigure the one-to-many mapping relationship between the data stream and multiple transmission channels.

11. A transmission configuration method, comprising: The network-side device sends the first configuration to the terminal; The first configuration is used to configure a one-to-many mapping relationship between the data stream and multiple transmission channels.

12. The method according to claim 11, wherein, The first configuration is used to configure at least one of the following: The fixed value of the first QoS parameter corresponding to each first index, and one or more variable QoS parameter information; The value of the second QoS parameter corresponding to each second index, and the same second index corresponds to the same PDU set; The value of the third QoS parameter corresponding to each third index, and / or the range of values ​​for the fourth index.

13. The method according to claim 11 or 12, wherein, The plurality of transmission channels includes at least one of the following: Each PDCP entity corresponds to a different transmission channel, and one PDCP entity corresponds to one RLC entity. Each PDCP entity corresponds to multiple transmission channels of multiple different RLC entities, with one PDCP entity corresponding to multiple RLC entities.

14. The method according to claim 12, wherein, The method further includes: The network-side device configures a first rule for the terminal; The first rule includes at least one of the following: If, based on the first information, it is determined that the data packet has one or more variable values ​​of a specific QoS parameter, the data packet is mapped to the transmission channel corresponding to the specific QoS parameter. If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have the same QoS parameters, the multiple data packets are mapped to the same transmission channel; If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have different QoS parameters, the multiple data packets are mapped to different transmission channels according to their respective QoS parameters. If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have different QoS parameters, the multiple data packets are mapped to the same transmission channel according to the second rule, wherein the second rule is associated with at least one of QoS parameter priority and QoS parameter value; The first information is used to indicate at least one of the QoS information and the service attribute information of the data stream.

15. The method according to any one of claims 10 to 14, wherein, The method further includes: The network-side device receives first capability information from the terminal; The first capability information is used to indicate the one-to-many mapping relationship between the data stream and multiple transmission channels.

16. The method according to any one of claims 10 to 14, wherein, The method further includes: The network-side device receives a second configuration from the terminal; The second configuration is used to reconfigure the one-to-many mapping relationship between the data stream and multiple transmission channels.

17. The method according to any one of claims 10 to 14, wherein, The method further includes: During cell handover, the source cell sends the data stream to the target cell and establishes a one-to-many mapping relationship between multiple transmission channels.

18. A transmission configuration apparatus, comprising: The first receiving module is used to receive the first configuration from the network-side device; The first processing module is used to determine a one-to-many mapping relationship between the data stream and multiple transmission channels based on the first configuration.

19. The apparatus according to claim 18, wherein, The device further includes: The second processing module is used for: Acquire data packets from a data stream, the data packets containing first information; Based on the first information, a PDU set or PDU is sent to the peer communication device using the target transmission channel among multiple transmission channels; The first information is used to indicate at least one of the QoS information and the service attribute information of the data stream, and each different first information maps to one or more transmission channels.

20. The apparatus according to claim 19, wherein, The first information includes at least one of the following: A first index and first indication information, wherein the first index is used to indicate a fixed value of a first QoS parameter, and the first indication information is used to indicate a variable value of one or more specific QoS parameters; The second index is used to indicate the value of the second QoS parameter and the corresponding PDU set; The third index and the fourth index, wherein the third index is used to indicate the value of the third QoS parameter, and the fourth index is used to indicate the PDU set.

21. The apparatus according to any one of claims 18 to 20, wherein, The first configuration is used to configure at least one of the following: The fixed value of the first QoS parameter corresponding to each first index, and one or more variable QoS parameter information; The value of the second QoS parameter corresponding to each second index, and the same second index corresponds to the same PDU set; The value of the third QoS parameter corresponding to each third index, and / or the range of values ​​for the fourth index.

22. The apparatus according to any one of claims 18 to 21, wherein, The plurality of transmission channels includes at least one of the following: Each PDCP entity corresponds to a different transmission channel, and one PDCP entity corresponds to one RLC entity. Each PDCP entity corresponds to multiple transmission channels of multiple different RLC entities, with one PDCP entity corresponding to multiple RLC entities.

23. The apparatus according to claim 20, wherein, The device further includes: The third processing module is used to determine the target transmission channel from multiple transmission channels according to a first rule pre-configured or configured by the network-side device. The first rule includes at least one of the following: If it is determined from the first information that the data packet has one or more variable values ​​of the specific QoS parameter, the data packet is mapped to the transmission channel corresponding to the specific QoS parameter; If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have the same QoS parameters, the multiple data packets are mapped to the same transmission channel; If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have different QoS parameters, the multiple data packets are mapped to different transmission channels according to their respective QoS parameters. If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have different QoS parameters, the multiple data packets are mapped to the same transmission channel according to the second rule, wherein the second rule is associated with at least one of the QoS parameter priority and the QoS parameter value.

24. The apparatus according to claim 19, wherein, The device further includes: The fourth processing module is used to set the total PBR of multiple logical channels corresponding to the data stream according to the configuration information of the data stream; Wherein, the total PBR of the multiple logical channels corresponding to the data stream satisfies any one of the following: If the QoS parameters corresponding to the data stream include GFBR, the first PBR is determined according to the GFBR, and the first PBR is determined as the total PBR of the multiple logical channels corresponding to the first information. If the QoS parameters corresponding to the data stream do not include the GFBR, the second PBR is determined according to a preset value, and the second PBR is determined as the total PBR of the multiple logical channels corresponding to the first information.

25. The apparatus according to claim 24, wherein, The device further includes: The fifth processing module is used for: Based on the total PBR of the multiple logical channels corresponding to the first information, the target resource is obtained; The target resources are allocated according to the priority of the plurality of logical channels in descending order.

26. The apparatus according to any one of claims 18 to 25, wherein, The device further includes: The first sending module is used to send first capability information to the network-side device; The first capability information is used to indicate whether the one-to-many mapping relationship between the data stream and multiple transmission channels is supported.

27. The apparatus according to any one of claims 18 to 25, wherein, The device further includes: The second receiving module is used to receive the second configuration from the network-side device; The second configuration is used to reconfigure the one-to-many mapping relationship between the data stream and multiple transmission channels.

28. A transmission configuration apparatus, comprising: The second sending module is used to send the first configuration to the terminal; The first configuration is used to configure a one-to-many mapping relationship between the data stream and multiple transmission channels.

29. The apparatus according to claim 28, wherein, The first configuration is used to configure at least one of the following: The fixed value of the first QoS parameter corresponding to each first index, and one or more variable QoS parameter information; The value of the second QoS parameter corresponding to each second index, and the same second index corresponds to the same PDU set; The value of the third QoS parameter corresponding to each third index, and / or the range of values ​​for the fourth index.

30. The apparatus according to claim 28 or 29, wherein, The plurality of transmission channels includes at least one of the following: Each PDCP entity corresponds to a different transmission channel, and one PDCP entity corresponds to one RLC entity. Each PDCP entity corresponds to multiple transmission channels of multiple different RLC entities, with one PDCP entity corresponding to multiple RLC entities.

31. The apparatus according to claim 29, wherein, The device further includes: The sixth processing module is used to configure the first rule for the terminal; The first rule includes at least one of the following: If, based on the first information, it is determined that the data packet has one or more variable values ​​of a specific QoS parameter, the data packet is mapped to the transmission channel corresponding to the specific QoS parameter. If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have the same QoS parameters, the multiple data packets are mapped to the same transmission channel; If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have different QoS parameters, the multiple data packets are mapped to different transmission channels according to their respective QoS parameters. If, based on the first information, it is determined that multiple data packets belong to the same PDU set and have different QoS parameters, the multiple data packets are mapped to the same transmission channel according to the second rule, wherein the second rule is associated with at least one of QoS parameter priority and QoS parameter value; The first information is used to indicate at least one of the QoS information and the service attribute information of the data stream.

32. The apparatus according to any one of claims 28 to 31, wherein, The device further includes: The third receiving module is used to receive first capability information from the terminal; The first capability information is used to indicate the one-to-many mapping relationship between the data stream and multiple transmission channels.

33. The apparatus according to any one of claims 28 to 31, wherein, The device further includes: The fourth receiving module is used to receive the second configuration from the terminal; The second configuration is used to reconfigure the one-to-many mapping relationship between the data stream and multiple transmission channels.

34. The apparatus according to any one of claims 28 to 31, wherein, The device further includes: The seventh processing module is used to send the data stream and the one-to-many mapping relationship between multiple transmission channels from the source cell to the target cell during cell handover.

35. A terminal comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the transmission configuration method as claimed in any one of claims 1 to 10.

36. A network-side device, wherein, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the transfer configuration method as described in any one of claims 11 to 17.

37. A readable storage medium, wherein, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the transmission configuration method as described in any one of claims 1 to 10, or implement the steps of the transmission configuration method as described in any one of claims 11 to 17.

38. A computer program product, wherein, It includes computer instructions that, when executed by a processor, implement the steps of the transmission configuration method as described in any one of claims 1 to 10, or implement the steps of the transmission configuration method as described in any one of claims 11 to 17.

Images