TW201836330A - Method for uplink data transmission, terminal, network side equipment, and system - Google Patents

Abstract

Disclosed are an uplink data transmission method, a terminal, a network side device and a system. The method comprises: a terminal transmitting uplink data in a time domain scheduling unit sequence, wherein a mark number of each time domain scheduling unit in the time domain scheduling unit sequence corresponds to one or more quality of service flow identifiers (QoS flow IDs) in a pre-set mapping relationship. The embodiments of the present invention are favourable for reducing the overheads of a QoS flow ID of uplink data and improving the transmission efficiency of the uplink data.

Description

Uplink data transmission method, terminal, network side device and system

The present invention relates to the field of communications technologies, and in particular, to an uplink data transmission method, a terminal, a network side device, and a system.

QoS (Quality of Service) is the quality of service. For network services, the quality of service includes the bandwidth of transmission, the delay of transmission, and the packet loss rate of data. In the network, the quality of service can be improved by ensuring the bandwidth of transmission, reducing the delay of transmission, reducing the packet loss rate of data, and delay jitter. Network resources are always limited, as long as there is a situation of robbing network resources, there will be service quality requirements. The quality of service is relative to the network service. While guaranteeing the service quality of a certain type of service, it may damage the service quality of other services. For example, if the total bandwidth of the network is fixed, if the bandwidth of a certain type of service is more, the bandwidth that other services can use is less, which may affect the use of other services. Therefore, network managers need to properly plan and allocate network resources according to the characteristics of various services, so that network resources can be efficiently utilized.

The QoS of the 5th-Generation (5G) new communication protocol (New Radio, NR) mainly includes two parts: Non-access stratum mapping (NAS Mapping) and access stratum mapping (Access Stratum Mapping). , AS Mapping), which includes the process of mapping data packets from Internet Protocol flow (IP flow) to service quality flow QoS flow, and QoS Flow mapping to Data Radio Bear (DRB). As shown in Figure 1, according to the latest development of the 3rd Generation Partnership Project (3GPP) conference, the QoS of the 5G NR needs to establish a Protocol Data Unit Session (PDU Session), which is a PDU. The Session contains the service flow QoS flow mapped by multiple Internet Protocol flows IP flows, and the packet packets in each QoS flow carry the QoS flow identification ID. For the uplink data, the mapping of the QoS Flow to the data radio bearer DRB is determined according to the downlink data mapping rule, and each packet packet needs to carry the QoS flow ID to complete the mapping. For the uplink data, the receiving end is the slave. The mapping from the DRB to the QoS flow needs to be determined according to the QoS flow ID. This requires carrying the QoS flow ID on each packet. However, carrying the QoS flow ID on each packet obviously increases the extra resource waste.

The embodiments of the present invention provide an uplink data transmission method, a terminal, a network side device, and a system, so as to reduce the overhead of the QoS flow ID of the uplink data and improve the uplink data transmission efficiency.

In a first aspect, an embodiment of the present invention provides an uplink data transmission method, including:

The terminal transmits the uplink data in the time domain scheduling unit sequence, and the label of each time domain scheduling unit in the time domain scheduling unit sequence corresponds to one or more quality of service flow identifiers QoS flow ID in the preset mapping relationship.

It can be seen that, in the embodiment of the present invention, the preset mapping relationship includes the correspondence between the label of the time domain scheduling unit of the uplink data and the QoS flow ID, and the terminal only needs to query the preset mapping by using the label of the scheduling unit as the query identifier. The relationship can be used to know which QoS flow the data in the data packet on the time domain scheduling unit comes from. Therefore, the transmitted data packet does not need to carry the QoS flow ID, which is beneficial to reducing the QoS flow ID overhead of the uplink data and improving the uplink. Data transmission efficiency.

In one possible design, the time domain scheduling unit is any one of the following: a radio frame, a subframe, a time slot, and a symbol.

In a possible design, the preset mapping relationship is a correspondence between a label of a time domain scheduling unit and a QoS flow ID, and the data in the data packet transmitted on the time domain scheduling unit is from a corresponding one or The QoS flow identified by the multiple QoS flow IDs, and the QoS flow identified by the QoS flow ID in the preset mapping relationship is a QoS flow mapped to the data radio bearer DRB of the terminal.

In a possible design, the label of the at least one time domain scheduling unit in the sequence of the time domain scheduling unit corresponds to a plurality of quality of service stream identity QoS flow IDs in the preset mapping relationship, the at least one time domain scheduling The data packet transmitted on the unit includes an indication message, and the indication message is used to indicate one of the multiple QoS flow IDs corresponding to the data packet.

In a possible design, the preset mapping relationship is determined by:

Determined by the reflective mapping of the QoS reflection mapping; or,

The flow mapping is determined according to the flow mapping indicated by the radio resource control RRC signal.

In one possible design, the method further includes:

The terminal sends the preset mapping relationship by using a radio resource control RRC signal.

In a second aspect, an embodiment of the present invention provides an uplink data transmission method, including:

The network side device receives the uplink data in the time domain scheduling unit sequence, and the label of each time domain scheduling unit in the time domain scheduling unit sequence corresponds to one or more quality of service flow identity QoS flow IDs in the preset mapping relationship.

It can be seen that, in the embodiment of the present invention, since the preset mapping relationship includes the correspondence between the label of the time domain scheduling unit of the uplink data and the QoS flow ID, the network side device only needs to query the preamble by using the label of the scheduling unit as the query identifier. By setting the mapping relationship, it can be known which QoS flow the data in the data packet on the time domain scheduling unit comes from, so the transmitted data packet does not need to carry the QoS flow ID, which is beneficial to reducing the QoS flow ID overhead of the uplink data. Improve the efficiency of uplink data transmission.

In one possible design, the time domain scheduling unit is any one of the following: a radio frame, a subframe, a time slot, and a symbol.

In a possible design, the preset mapping relationship is a correspondence between a label of a time domain scheduling unit and a QoS flow ID, and the data in the data packet transmitted on the time domain scheduling unit is from a corresponding one or The QoS flow identified by the multiple QoS flow IDs, and the QoS flow identified by the QoS flow ID in the preset mapping relationship is a QoS flow mapped to the data radio bearer DRB of the terminal.

In a possible design, the label of the at least one time domain scheduling unit in the sequence of the time domain scheduling unit corresponds to a plurality of quality of service stream identity QoS flow IDs in the preset mapping relationship, the at least one time domain scheduling The data packet transmitted on the unit includes an indication message, and the indication message is used to indicate one of the multiple QoS flow IDs corresponding to the data packet.

In a possible design, the preset mapping relationship is determined by:

Determined by the reflective mapping of the QoS reflection mapping; or,

According to the flow mapping flow mapping indicated by the RRC signal.

In one possible design, the method further includes:

The network side device receives the preset mapping relationship by using a radio resource control RRC signal.

In a third aspect, an embodiment of the present invention provides a terminal, where the terminal has a function of implementing behavior of a terminal in the foregoing method design. The functions can be implemented by hardware or by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a possible design, the terminal includes a processing unit and a communication unit,

The processing unit is configured to transmit, by using the communication unit, uplink data in a time domain scheduling unit sequence, where a label of each time domain scheduling unit in the time domain scheduling unit sequence corresponds to one or more services in a preset mapping relationship Quality flow identity QoS flow ID.

In one possible design, the time domain scheduling unit is any one of the following: a radio frame, a subframe, a time slot, and a symbol.

In a possible design, the preset mapping relationship is a correspondence between a label of a time domain scheduling unit and a QoS flow ID, and the data in the data packet transmitted on the time domain scheduling unit is from a corresponding one or The QoS flow identified by the multiple QoS flow IDs, and the QoS flow identified by the QoS flow ID in the preset mapping relationship is a QoS flow mapped to the data radio bearer DRB of the terminal.

In a possible design, the label of the at least one time domain scheduling unit in the sequence of the time domain scheduling unit corresponds to a plurality of quality of service stream identity QoS flow IDs in the preset mapping relationship, the at least one time domain scheduling The data packet transmitted on the unit includes an indication message, and the indication message is used to indicate one of the multiple QoS flow IDs corresponding to the data packet.

In a possible design, the preset mapping relationship is determined by:

Determined by the reflective mapping of the QoS reflection mapping; or,

The flow mapping is determined according to the flow mapping indicated by the radio resource control RRC signal.

In a possible design, the processing unit is further configured to send, by using the communication unit, the preset mapping relationship by using a radio resource control RRC signal.

In one possible design, the terminal includes a processor configured to support the terminal in performing the corresponding functions of the above methods. Further, the terminal may further include a transceiver, where the transceiver is used to support communication between the terminal and the network side device. Further, the terminal may further include a memory for coupling with the processor, which stores program instructions and materials necessary for the terminal.

In a fourth aspect, an embodiment of the present invention provides a network side device, where the network side device has a function of implementing behavior of a network side device in the foregoing method design. The functions can be implemented by hardware or by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a possible design, the network side device, including the processing unit and the communication unit,

The processing unit is configured to receive uplink data by using the communication unit in a time domain scheduling unit sequence, where a label of each time domain scheduling unit in the time domain scheduling unit sequence corresponds to one or more services in a preset mapping relationship Quality flow identity QoS flow ID.

In one possible design, the time domain scheduling unit is any one of the following: a radio frame, a subframe, a time slot, and a symbol.

In a possible design, the preset mapping relationship is a correspondence between a label of a time domain scheduling unit and a QoS flow ID, and the data in the data packet transmitted on the time domain scheduling unit is from a corresponding one or The QoS flow identified by the multiple QoS flow IDs, and the QoS flow identified by the QoS flow ID in the preset mapping relationship is a QoS flow mapped to the data radio bearer DRB of the terminal.

In a possible design, the label of the at least one time domain scheduling unit in the sequence of the time domain scheduling unit corresponds to a plurality of quality of service stream identity QoS flow IDs in the preset mapping relationship, the at least one time domain scheduling The data packet transmitted on the unit includes an indication message, and the indication message is used to indicate one of the multiple QoS flow IDs corresponding to the data packet.

In a possible design, the preset mapping relationship is determined by:

Determined by the reflective mapping of the QoS reflection mapping; or,

According to the flow mapping flow mapping indicated by the RRC signal.

In a possible design, the processing unit is further configured to receive, by using the radio resource control RRC signal, the preset mapping relationship by using the communication unit.

In one possible design, the network side device includes a processor configured to support the network side device to perform the corresponding function in the above method. Further, the network side device may further include a transceiver, and the transceiver is configured to support communication between the network side device and the terminal. Further, the network side device may further include a memory for coupling with the processor, which saves necessary program instructions and materials of the network side device.

In a fifth aspect, an embodiment of the present invention provides a communication system, where the system includes the terminal and the network side device described in the foregoing aspect.

According to a sixth aspect, an embodiment of the present invention provides a computer readable storage medium, where the computer readable storage medium stores instructions, when executed on a computer, causing the computer to perform the foregoing first aspect or the second aspect. method.

In a seventh aspect, an embodiment of the present invention provides a computer program product including instructions, which, when run on a computer, causes the computer to perform the method of the first aspect or the second aspect.

It can be seen that, in the embodiment of the present invention, the preset mapping relationship includes the correspondence between the label of the time domain scheduling unit of the uplink data and the QoS flow ID, and the terminal and the network side device only need to use the label of the scheduling unit as the query. Identifying and querying the preset mapping relationship can be used to know which QoS flow the data in the data packet on the time domain scheduling unit comes from. Therefore, the transmitted data packet does not need to carry the QoS flow ID, which is beneficial to reducing the QoS flow of the uplink data. The overhead of ID improves the efficiency of uplink data transmission.

The technical solutions in the embodiments of the present invention will be described below with reference to the drawings. As shown in Figure 2, the access layer (Acess Stratum, AS) of the 5G NR is used to complete the mapping from the QoS flow to the data radio bearer DRB according to the corresponding QoS flow ID. The AS mainly includes the following functions: (1) QoS flow to the data radio bearer DRB route (2) QoS flow ID encapsulation in the downlink data (3) QoS flow ID encapsulation in the uplink data.

Please refer to FIG. 3. FIG. 3 is a schematic diagram of a possible network architecture of a mobile communication system according to an embodiment of the present invention. The network architecture includes a network side device and a terminal. When the terminal accesses the mobile communication network provided by the network side device, the terminal and the network side device can communicate through the wireless link. The mobile communication system can be, for example, a 5G NR mobile communication system or the like. The network side device may be, for example, a base station in a 5G network. In the embodiments of the present invention, the terms "network" and "system" are often used interchangeably, and those skilled in the art can understand the meaning thereof. The terminal involved in the embodiments of the present invention may include various handheld devices, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless data device, and various forms of user equipment (User Equipment). , UE), mobile station (MS), terminal device, and the like. For convenience of description, the devices mentioned above are collectively referred to as terminals.

Referring to FIG. 4A, FIG. 4A illustrates an uplink data transmission method according to an embodiment of the present invention. The method includes: part 401, which is specifically as follows:

In the 401 part, the terminal transmits the uplink data in the time domain scheduling unit sequence, where the label of each time domain scheduling unit in the time domain scheduling unit sequence corresponds to one or more service quality stream identity QoS flow IDs in the preset mapping relationship. .

The number of the time domain scheduling unit refers to the sequence number of the time domain scheduling unit. For example, the ten time domain scheduling units are divided into a time domain scheduling unit Num1, a time domain scheduling unit Num2, and a time domain scheduling unit Num3 according to the scheduled timing. a time domain scheduling unit Num4, a time domain scheduling unit Num5, a time domain scheduling unit Num6, a time domain scheduling unit Num7, a time domain scheduling unit Num8, a time domain scheduling unit Num9, a time domain scheduling unit Num10, then the time domain scheduling unit The labels are Num1, Num2, Num3, Num4, Num5, Num6, Num7, Num8, Num9, and Num10.

For example, the time domain scheduling unit is a subframe, and one subframe sequence includes 20 subframes with sequence numbers 1 to 20, where the sequence number of the subframe is the label of each subframe, if mapped to be used for transmission. The QoS flow on the radio bearer DRB of the uplink data includes QoS flow1 and QoS flow2, and the preset mapping relationship may include a subframe in order to make the data of the data packet transmitted on the time domain scheduling unit correspond to the QoS flow. Correspondence between 1/3/5/7/9/11/13/15/17/19 and QoS flow1, and the label including sub-frame 2/4/6/8/10/12/14/16 Correspondence between /18/20 and QoS flow2.

It can be seen that, in the embodiment of the present invention, the preset mapping relationship includes the correspondence between the label of the time domain scheduling unit of the uplink data and the QoS flow ID, and the terminal and the network side device only need to use the label of the scheduling unit as the query. Identifying and querying the preset mapping relationship can be used to know which QoS flow the data in the data packet on the time domain scheduling unit comes from. Therefore, the transmitted data packet does not need to carry the QoS flow ID, which is beneficial to reducing the QoS flow of the uplink data. The overhead of ID improves the efficiency of uplink data transmission.

In one possible example, the time domain scheduling unit is any one of the following: a radio frame, a subframe, a time slot, and a symbol.

For example, as shown in FIG. 4B, the terminal transmits the uplink data of QoS flow 1 in the subframe labeled 3i, and transmits the uplink data of QoS flow 2 in the subframe labeled 3i+1, which is labeled 3i+2. The subframe transmits the uplink data of QoS flow3, i is 0 or a positive integer, and so on, the terminal sends the corresponding uplink data at the time (subframe) to which the flow belongs. Correspondingly, when receiving the uplink data, the network side device can query the correspondence between the label of the subframe and the QoS flow ID (specifically: label 3i corresponds to QoS flow 1, label 3i+1 corresponds to QoS flow 2, label 3i +2 corresponds to QoS flow 3) to determine which QoS flow the received data should be mapped to. In an optional example, if no data is transmitted/received in a subframe with the label 3i+2, the terminal/base station will continue to transmit/receive other data according to the correspondence.

In a possible example, the preset mapping relationship is a correspondence between a label of a time domain scheduling unit and a QoS flow ID, and the data in the data packet transmitted on the time domain scheduling unit is from a corresponding one or The QoS flow identified by the multiple QoS flow IDs, and the QoS flow identified by the QoS flow ID in the preset mapping relationship is a QoS flow mapped to the data radio bearer DRB of the terminal.

The DRB is used to carry the user plane data. According to the QoS, the terminal and the network side device can simultaneously establish up to eight DRBs. The data radio bearer DRB of the terminal corresponds to the PDCP layer entity of the terminal, and one terminal can be multi-terminal. The number of PDCP entities, such as eight, can support eight DRBs. When the QoS flow of different service data on the network side is delivered, the network side device maps the QoS flow of different service data to the DRB, such as the QoS of the terminal's WeChat service. The flow is mapped to the first DRB of the terminal, and the QoS flow of the image service of the terminal is mapped to the first DRB or the second DRB.

In addition, it should be noted that not every time domain scheduling unit must transmit data packets, such as when the previous scheduling unit does not transmit data packets, and when the next time domain scheduling unit transmits data packets, the time domain scheduling unit labels and The QoS flow ID corresponding to the data in the data package still satisfies the preset mapping relationship.

In a possible example, the label of the at least one time domain scheduling unit in the sequence of the time domain scheduling unit corresponds to a plurality of quality of service stream identity QoS flow IDs in the preset mapping relationship, the at least one time domain scheduling The data packet transmitted on the unit includes an indication message, and the indication message is used to indicate one of the multiple QoS flow IDs corresponding to the data packet.

For example, as shown in FIG. 4C, the terminal transmits the uplink data of QoS flow 1 in the subframe labeled 3j, and transmits the uplink data of QoS flow 2 and QoS flow 3 in the subframe labeled 3j+1. The subframe of 3j+2 sends the uplink data of QoS flow 4, and j is 0 or a positive integer. In an optional example, if the base station receives the data packet in the 3i+1 subframe, it needs to determine that the data packet belongs to the QoS flow, for example, by using the following method: adding a 1-bit 0/1 to the data packet. Bit indication message to distinguish the data of two flows.

It can be seen that, in this example, for the label of the time domain scheduling unit corresponding to multiple QoS flow IDs, an indication message may be added to the data packet transmitted on the time domain scheduling unit to indicate the QoS flow ID corresponding to the current data packet. Avoid carrying the QoS flow ID, and the amount of information indicating the message is small. For example, for the data packet transmitted on the time domain scheduling unit corresponding to the two QoS flow IDs, two QoS can be indicated by one bit 1/0. Flow ID, which can effectively reduce the amount of data in the data package and improve the efficiency of data transmission.

In one possible example, the preset mapping relationship is determined by:

Determined by the reflective mapping of the QoS reflection mapping; or,

According to the flow mapping flow mapping indicated by the RRC signal.

Wherein, for the two data packets transmitted on the same DRB, the preset mapping relationship used by the latter data packet may be determined according to the mapping relationship used by the previous data packet, such as the previous data packet corresponding to the use according to the reflective The mapping relationship determined by the mapping, the latter data packet also uses the mapping relationship determined according to the reflective mapping. If the previous data packet corresponds to the mapping relationship determined by the flow mapping indicated by the RRC signal, the latter data packet is also used according to the mapping relationship. The mapping relationship determined by the flow mapping indicated by the RRC signal.

In one possible example, the method further includes:

Obtaining, by the access layer AS entity, the QoS flow ID of the QoS flow mapped to the data radio bearer DRB of the terminal;

The terminal establishes a correspondence between the label of the time domain scheduling unit and the QoS flow ID to form the preset mapping relationship.

It can be seen that, in this example, the AS entity of the terminal can directly obtain the QoS flow ID of the QoS flow mapped to the data radio bearer DRB of the terminal, and establish a correspondence between the label of the time domain scheduling unit and the QoS flow ID to form a relationship. The mapping relationship is preset, so that the data packet of the terminal does not need to wait for a preset mapping relationship at the PDCP layer, and the data from the QoS flow that the current data packet should carry is determined, which is beneficial to improving the immediacy of the data packet encapsulation of the terminal. , thereby improving the efficiency of data transmission.

In one possible example, the method further includes:

The terminal sends the preset mapping relationship by using a radio resource control RRC signal.

Please refer to FIG. 5. FIG. 5 is a schematic diagram of an uplink data transmission method according to an embodiment of the present invention. The method includes: part 501, which is as follows:

In 501, the network side device receives the uplink data in the time domain scheduling unit sequence, where the label of each time domain scheduling unit in the time domain scheduling unit sequence corresponds to one or more quality of service flow identity QoS in the preset mapping relationship. Flow ID.

It can be seen that, in the embodiment of the present invention, the preset mapping relationship includes the correspondence between the label of the time domain scheduling unit of the uplink data and the QoS flow ID, and the terminal and the network side device only need to use the label of the scheduling unit as the query identifier. By querying the preset mapping relationship, it can be known which QoS flow the data in the data packet on the time domain scheduling unit comes from, so the transmitted data packet does not need to carry the QoS flow ID, which is beneficial to reduce the QoS flow ID of the uplink data. Overhead, improve the efficiency of uplink data transmission.

In one possible design, the time domain scheduling unit is any one of the following: a radio frame, a subframe, a time slot, and a symbol.

In a possible design, the preset mapping relationship is a correspondence between a label of a time domain scheduling unit and a QoS flow ID, and the data in the data packet transmitted on the time domain scheduling unit is from a corresponding one or The QoS flow identified by the multiple QoS flow IDs, and the QoS flow identified by the QoS flow ID in the preset mapping relationship is a QoS flow mapped to the data radio bearer DRB of the terminal.

In a possible design, the label of the at least one time domain scheduling unit in the sequence of the time domain scheduling unit corresponds to a plurality of quality of service stream identity QoS flow IDs in the preset mapping relationship, the at least one time domain scheduling The data packet transmitted on the unit includes an indication message, and the indication message is used to indicate one of the multiple QoS flow IDs corresponding to the data packet.

In a possible design, the preset mapping relationship is determined by:

Determined by the reflective mapping of the QoS reflection mapping; or,

According to the flow mapping flow mapping indicated by the RRC signal.

In one possible design, the method further includes:

Determining, by the access layer AS entity, a label of the time domain scheduling unit;

The network side device uses the label of the time domain scheduling unit as a query identifier, queries the preset mapping relationship, and determines a QoS flow ID corresponding to the label of the time domain scheduling unit.

In one possible design, the method further includes:

The network side device receives the preset mapping relationship by using a radio resource control RRC signal.

The foregoing describes the solution of the embodiment of the present invention mainly from the perspective of interaction between the network elements. It can be understood that, in order to implement the above functions, the terminal and the network side device include a hardware structure and/or a software module corresponding to each function. It will be readily apparent to those skilled in the art that the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements of the examples and algorithm steps described in connection with the embodiments disclosed herein. . Whether a function is implemented in hardware or in a computer software-driven manner depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

The embodiment of the present invention may divide the functional unit into the terminal and the network side device according to the foregoing method. For example, each functional unit may be divided according to each function, or two or more functions may be integrated into one processing unit. The above integrated unit can be implemented in the form of a hardware or a software functional unit. It should be noted that the division of the unit in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.

In the case of employing an integrated unit, FIG. 6A shows a possible structural diagram of the first core network device involved in the above embodiment. The terminal 600 includes a processing unit 602 and a communication unit 603. The processing unit 602 is configured to control and manage the actions of the terminal. For example, the processing unit 602 is configured to support the terminal to perform step 401 in FIG. 4A and/or other processes for the techniques described herein. The communication unit 603 is used to support communication between the terminal and other devices, such as communication with the network side device shown in FIG. The terminal may further include a storage unit 601 for storing program codes and materials of the terminal.

The processing unit 602 can be a processor or a controller, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and a dedicated integrated circuit (Application- Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure. The processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like. The communication unit 603 can be a transceiver, a transceiver circuit, etc., and the storage unit 601 can be a memory.

The processing unit 602 is configured to transmit, by using the communication unit 603, uplink data in a time domain scheduling unit sequence, where a label of each time domain scheduling unit in the time domain scheduling unit sequence corresponds to one in a preset mapping relationship or Multiple Quality of Service flows identify the QoS flow ID.

In one possible example, the time domain scheduling unit is any one of the following: a radio frame, a subframe, a time slot, and a symbol.

In a possible example, the preset mapping relationship is a correspondence between a label of a time domain scheduling unit and a QoS flow ID, and the data in the data packet transmitted on the time domain scheduling unit is from a corresponding one or The QoS flow identified by the multiple QoS flow IDs, and the QoS flow identified by the QoS flow ID in the preset mapping relationship is a QoS flow mapped to the data radio bearer DRB of the terminal.

In a possible example, the label of the at least one time domain scheduling unit in the sequence of the time domain scheduling unit corresponds to a plurality of quality of service stream identity QoS flow IDs in the preset mapping relationship, the at least one time domain scheduling The data packet transmitted on the unit includes an indication message, and the indication message is used to indicate one of the multiple QoS flow IDs corresponding to the data packet.

In one possible example, the preset mapping relationship is determined by:

Determined by the reflective mapping of the QoS reflection mapping; or,

The flow mapping is determined according to the flow mapping indicated by the radio resource control RRC signal.

In a possible example, the processing unit 602 is further configured to send, by using the communication unit 603, the preset mapping relationship by using a radio resource control RRC signal.

When the processing unit 602 is a processor, the communication unit 603 is a communication interface, and the storage unit 601 is a memory, the terminal involved in the embodiment of the present invention may be the terminal shown in FIG. 4AB.

Referring to FIG. 6B, the terminal 610 includes a processor 612, a communication interface 613, and a memory 611. Optionally, the terminal 610 may further include a bus bar 614. The communication interface 613, the processor 612, and the memory 611 may be connected to each other through a bus bar 614. The bus bar 614 may be a Peripheral Component Interconnect (PCI) bus or an extended industry standard architecture (Extended Industry). Standard Architecture (EISA) busbars, etc. The bus bar 614 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 6B, but it does not mean that there is only one bus bar or one type of bus bar.

The terminal shown in FIG. 6A or FIG. 6B can also be understood as a device for a terminal, which is not limited in the embodiment of the present invention.

In the case of employing an integrated unit, FIG. 7A shows a possible structural diagram of the first core network device involved in the above embodiment. The network side device 700 includes a processing unit 702 and a communication unit 703. The processing unit 702 is configured to perform control management on the action of the network side device. For example, the processing unit 702 is configured to support the network side device to perform step 402 in FIG. 4A, step 501 in FIG. 4B, 602 in the step of FIG. 4C, and/or Other processes for the techniques described herein. The communication unit 703 is for supporting communication between the network side device and other devices, for example, communication with the terminal shown in FIG. The network side device may further include a storage unit 701 for storing program code and data of the network side device.

The processing unit 702 may be a processor or a controller, and may be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and a dedicated integrated circuit (Application- Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure. The processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like. The communication unit 703 may be a transceiver, a transceiver circuit, or the like, and the storage unit 701 may be a memory.

The processing unit 702 is configured to receive uplink data by using the communication unit 703 in a time domain scheduling unit sequence, where a label of each time domain scheduling unit in the time domain scheduling unit sequence corresponds to one in a preset mapping relationship or Multiple Quality of Service flows identify the QoS flow ID.

In one possible example, the time domain scheduling unit is any one of the following: a radio frame, a subframe, a time slot, and a symbol.

In a possible example, the preset mapping relationship is a correspondence between a label of a time domain scheduling unit and a QoS flow ID, and the data in the data packet transmitted on the time domain scheduling unit is from a corresponding one or The QoS flow identified by the multiple QoS flow IDs, and the QoS flow identified by the QoS flow ID in the preset mapping relationship is a QoS flow mapped to the data radio bearer DRB of the terminal.

In a possible example, the label of the at least one time domain scheduling unit in the sequence of the time domain scheduling unit corresponds to a plurality of quality of service stream identity QoS flow IDs in the preset mapping relationship, the at least one time domain scheduling The data packet transmitted on the unit includes an indication message, and the indication message is used to indicate one of the multiple QoS flow IDs corresponding to the data packet.

In one possible example, the preset mapping relationship is determined by:

Determined by the reflective mapping of the QoS reflection mapping; or,

According to the flow mapping flow mapping indicated by the RRC signal.

In one possible example, the processing unit 702 is further configured to receive, by using the radio resource control RRC signal, the preset mapping relationship by using the communication unit 703.

When the processing unit 702 is a processor, the communication unit 703 is a communication interface, and the storage unit 701 is a memory, the network side device according to the embodiment of the present invention may be the network side device shown in FIG. 7B.

Referring to FIG. 7B, the network side device 710 includes a processor 712, a communication interface 713, and a memory 711. Optionally, the network side device 710 may further include a bus bar 714. The communication interface 713, the processor 712, and the memory 711 may be connected to each other through a bus bar 714; the bus bar 714 may be a Peripheral Component Interconnect (PCI) bus or an extended industry standard architecture (Extended Industry) Standard Architecture (EISA) busbars, etc. The bus bar 714 can be divided into a address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 7B, but it does not mean that there is only one bus bar or one type of bus bar.

The network side device shown in FIG. 7A or FIG. 7B can also be understood as a device for the network side device, which is not limited in the embodiment of the present invention.

The embodiment of the invention further provides a communication system, which comprises the above terminal and a network side device.

The embodiment of the present invention further provides a terminal. As shown in FIG. 8 , for the convenience of description, only parts related to the embodiment of the present invention are shown. If the specific technical details are not disclosed, please refer to the method part of the embodiment of the present invention. The terminal can be any terminal device including a mobile phone, a tablet computer, a PDA (Personal Digital Assistant), a POS (Point of Sales), an in-vehicle computer, and the terminal is a mobile phone as an example:

FIG. 8 is a block diagram showing a partial structure of a mobile phone related to a terminal provided by an embodiment of the present invention. Referring to FIG. 8, the mobile phone includes: a radio frequency (RF) circuit 910, a memory 920, an input unit 930, a display unit 940, a sensor 950, an audio circuit 960, and a wireless fidelity (WiFi) module 970. , processor 980, and power supply 990 and other components. It will be understood by those of ordinary skill in the art that the structure of the handset shown in Figure 8 does not constitute a limitation to the handset, may include more or fewer components than illustrated, or may combine certain components, or different components. Arrangement.

The following describes the components of the mobile phone in detail with reference to FIG. 8:

The RF circuit 910 can be used for receiving and transmitting messages. Generally, RF circuit 910 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, the RF circuit 910 can also communicate with the network and other devices via wireless communication. The above wireless communication may use any communication standard or protocol, including but not limited to Global System of Mobile communication (GSM), General Packet Radio Service (GPRS), and code division multiple access (Code). Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), E-mail, Short Messaging Service (SMS), etc.

The memory 920 can be used to store software programs and modules. The processor 980 executes various functional applications and data processing of the mobile phone by running software programs and modules stored in the memory 920. The memory 920 can mainly include a storage program area and a storage data area, wherein the storage program area can store an operating system, an application required for at least one function, and the like; and the storage data area can store data created according to the use of the mobile phone. In addition, memory 920 can include high speed random access memory, and can also include non-volatile memory, such as at least one disk memory device, flash memory device, or other volatile solid state memory device.

The input unit 930 can be configured to receive an input digit or character message and generate a key signal input related to user settings and function control of the handset. Specifically, the input unit 930 can include a fingerprint recognition module 931 and other input devices 932. The fingerprint identification module 931 can collect fingerprint data of the user. In addition to the fingerprint recognition module 931, the input unit 930 may also include other input devices 932. Specifically, the other input device 932 may include, but is not limited to, one or more of a touch screen, a physical keyboard, function keys (such as a volume control button, a switch button, etc.), a trackball, a mouse, a joystick, and the like.

The display unit 940 can be used to display a message input by the user or a message provided to the user and various function tables of the mobile phone. The display unit 940 can include a display screen 941. Alternatively, the display screen 941 can be configured in the form of a liquid crystal display (LCD), an Organic Light-Emitting Diode (OLED), or the like. Although in FIG. 8, the fingerprint recognition module 931 and the display screen 941 are used as two separate components to implement the input and input functions of the mobile phone, in some embodiments, the fingerprint recognition module 931 and the display screen 941 may be Integrated to achieve the input and playback functions of the phone.

The handset can also include at least one sensor 950, such as a light sensor, motion sensor, and other sensors. Specifically, the photo sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display screen 941 according to the brightness of the ambient light, and the proximity sensor can be moved to the mobile phone to When the ear is closed, the display screen 941 and/or the backlight are turned off. As a kind of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (usually three axes). When it is still, it can detect the magnitude and direction of gravity. It can be used to identify the gesture of the mobile phone (such as horizontal and vertical screen). Switching, related games, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tapping), etc.; other functions such as gyroscope, barometer, hygrometer, thermometer, infrared sensor, etc. The detector will not be described here.

The audio circuit 960, the speaker 961, and the microphone 962 can provide an audio interface between the user and the mobile phone. The audio circuit 960 can transmit the received electrical signal converted to the audio data to the speaker 961, and the speaker 961 converts the audio signal into an audio signal. On the other hand, the microphone 962 converts the collected audio signal into an electrical signal, and the audio circuit 960 is used. After receiving, the data is converted into audio data, and then processed by the audio data playing processor 980, sent to the mobile phone 910 via the RF circuit 910, or the audio data is played to the memory 920 for further processing.

WiFi is a short-range wireless transmission technology. The mobile phone can be used to send and receive e-mails, browse web pages and access streaming media through the WiFi module 970, which provides users with wireless broadband Internet access. Although FIG. 8 shows the WiFi module 970, it can be understood that it does not belong to the essential configuration of the mobile phone, and can be omitted as needed within the scope of not changing the essence of the invention.

The processor 980 is a control center of the mobile phone, and connects various parts of the entire mobile phone by using various interfaces and lines, by running or executing software programs and/or modules stored in the memory 920, and calling data stored in the memory 920. The mobile phone's various functions and processing data are implemented to monitor the mobile phone as a whole. Optionally, the processor 980 may include one or more processing units; preferably, the processor 980 may integrate an application processor and a modem processor, where the application processor mainly processes the operating system, the user interface, and the application. Etc. The modem processor primarily handles wireless communications. It will be appreciated that the above described modem processor may also not be integrated into the processor 980.

The handset also includes a power source 990 (such as a battery) that supplies power to the various components. Preferably, the power source can be logically coupled to the processor 980 through a power management system to manage functions such as charging, discharging, and power management through the power management system.

Although not shown, the mobile phone may further include a camera, a Bluetooth module, and the like, and details are not described herein again.

In the foregoing embodiment shown in FIG. 4A and FIG. 5, the process on the terminal side in each step method may be implemented based on the structure of the mobile phone.

In the foregoing embodiment shown in FIG. 6A and FIG. 6B, each unit function can be implemented based on the structure of the mobile phone.

The steps of the method or algorithm described in the embodiments of the present invention may be implemented in a hardware manner, or may be implemented by a processor executing a software instruction. The software command can be composed of corresponding software modules. The software module can be stored in random access memory (RAM), flash memory, read only memory (ROM), erasable. In addition to Erasable Programmable ROM (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard drives, removable hard drives, CD-ROMs Or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from the storage medium and can write a message to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium can be bit in the ASIC. Additionally, the ASIC can be located in an access network device, a target network device, or a core network device. Of course, the processor and the storage medium may also exist as discrete components in the access network device, the target network device, or the core network device.

It should be appreciated by those of ordinary skill in the art that, in one or more examples described above, the functions described in the embodiments of the present invention may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from a computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website, computer, server or data. The center transmits to another website, computer, server or data center by wire (for example, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (for example, infrared, wireless, microwave, etc.). The computer readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that includes one or more available media. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a Digital Video Disc (DVD)), or a semiconductor medium (eg, a solid state disk (Solid State) Disk, SSD)) and so on.

The specific embodiments of the present invention have been described in detail with reference to the embodiments of the embodiments of the present invention. The scope of the present invention is defined by the scope of the present invention. Any modifications, equivalents, improvements, etc., which are included in the embodiments of the present invention, are included in the scope of the present invention.

401‧‧‧ steps

501‧‧‧Steps

600‧‧‧ Terminal

601‧‧‧ storage unit

602‧‧‧Processing unit

603‧‧‧Communication unit

610‧‧‧ Terminal

611‧‧‧ memory

612‧‧‧ processor

613‧‧‧Communication interface

614‧‧ ‧ busbar

700‧‧‧Network side equipment

701‧‧‧ storage unit

702‧‧‧Processing unit

703‧‧‧Communication unit

710‧‧‧Network side equipment

711‧‧‧ memory

712‧‧‧ processor

713‧‧‧Communication interface

714‧‧‧ busbar

910‧‧‧ Radio Frequency (RF) Circuit

920‧‧‧ memory

930‧‧‧Input unit

931‧‧‧Fingerprint Identification Module

932‧‧‧Other input devices

940‧‧‧Display unit

941‧‧‧ display screen

950‧‧‧ sensor

960‧‧‧Optical circuit

961‧‧‧Speaker

962‧‧‧Microphone

970‧‧‧Wireless Fidelity (WiFi) Module

980‧‧‧ processor

990‧‧‧Power supply

The following is a brief description of the drawings used in the embodiments or the description of the prior art. FIG. 1 is a schematic diagram of a PDU Session established by QoS of a 5G NR; FIG. 2 is a schematic structural diagram of a protocol stack of a 5G NR; FIG. 4A is a schematic diagram of communication of an uplink data transmission method according to an embodiment of the present invention; FIG. 4B is a schematic diagram of a preset mapping relationship provided by an embodiment of the present invention; FIG. 4 is a schematic diagram of another preset mapping relationship according to an embodiment of the present invention; FIG. 5 is a schematic diagram of communication of another uplink data transmission method according to an embodiment of the present invention; FIG. FIG. 6B is a schematic structural diagram of another terminal according to an embodiment of the present invention; FIG. 7B is a schematic structural diagram of a network side device according to an embodiment of the present invention; FIG. 7B is another network side device according to an embodiment of the present invention. FIG. 8 is a schematic structural diagram of another terminal according to an embodiment of the present invention.

Claims (10)

An uplink data transmission method, comprising: a terminal transmitting uplink data in a time domain scheduling unit sequence, wherein a label of each time domain scheduling unit in the time domain scheduling unit sequence corresponds to one or more service qualities in a preset mapping relationship Flow identity QoS flow ID. The method of claim 1, wherein the time domain scheduling unit is any one of the following: a radio frame, a subframe, a time slot, and a symbol. The method of claim 1, wherein the preset mapping relationship is a correspondence between a label of a time domain scheduling unit and a QoS flow ID, where the data packet transmitted on the time domain scheduling unit is The QoS flow identified by the QoS flow ID in the preset mapping relationship is the QoS flow mapped to the data radio bearer DRB of the terminal. The method of claim 1, wherein the label of the at least one time domain scheduling unit in the time domain scheduling unit sequence corresponds to a plurality of quality of service stream identity QoS flow IDs in the preset mapping relationship, The data packet transmitted on the at least one time domain scheduling unit includes an indication message, where the indication message is used to indicate one of the multiple QoS flow IDs corresponding to the data packet. The method of claim 1, wherein the preset mapping relationship is determined by: determining according to a reflection mapping of the QoS; or determining according to a flow mapping indicated by the radio resource control RRC signal. The method of any one of claims 1-5, wherein the method further comprises: the terminal transmitting the preset mapping relationship by using a radio resource control RRC signal. An uplink data transmission method, comprising: the network side device receiving uplink data in a time domain scheduling unit sequence, where the label of each time domain scheduling unit in the time domain scheduling unit sequence corresponds to one or more in a preset mapping relationship Quality of Service Flow Identifier QoS flow ID. The method of claim 7, wherein the time domain scheduling unit is any one of the following: a radio frame, a subframe, a time slot, and a symbol. The method of claim 7 or 8, wherein the preset mapping relationship is a correspondence between a label of a time domain scheduling unit and a QoS flow ID, and the data packet transmitted on the time domain scheduling unit. The QoS flow identified by the QoS flow ID in the preset mapping relationship is the QoS flow of the data radio bearer DRB mapped to the terminal. A terminal, comprising: a processor, a memory and a transceiver, wherein the processor is communicatively coupled to the memory and the transceiver; and the memory stores program code and data, the processor is configured to call The program code and the data in the memory perform the method of any one of claims 1-6.