TWI678903B - Method for uplink data transmission, and terminal - Google Patents

Abstract

Method, terminal, network side equipment and system for uplink data transmission, including: terminal in time domain adjustment Degree unit sequence transmits uplink data, 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 ID) in a preset mapping relationship. . The embodiments of the present invention are beneficial to reduce the overhead of QoS flow ID of uplink data and improve the transmission efficiency of uplink data.

Description

Method and terminal for uplink data transmission

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

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

The fifth-generation (5th-Generation, 5G) new radio (NR) QoS mainly includes two parts: non-access stratum mapping (NAS Mapping) and access stratum mapping (Access Stratum Mapping (AS Mapping), which includes the process of data packet mapping from Internet Protocol flow (IP flow) to quality of service flow QoS flow, and QoS Flow mapping to Data Radio Bear (DRB). As shown in Figure 1, according to the latest progress of the 3rd Generation Partnership Project (3GPP) conference, 5G NR QoS needs to establish a Protocol Data Unit Session (PDU Session). The PDU The Session contains the service flow QoS flow mapped from multiple Internet Protocol flows IP flows. Each packet in the QoS flow will carry the QoS flow identification ID. For uplink data, the mapping of its QoS Flow to the data radio bearer DRB is determined according to the downlink data mapping rules. Each data packet needs to carry a QoS flow ID to complete the mapping. For uplink data, the receiver's slave The mapping of DRB to QoS flow needs to be judged according to the QoS flow ID. This requires carrying a QoS flow ID on each packet, but carrying a QoS flow ID on each packet obviously adds additional waste of resources.

Embodiments of the present invention provide an uplink data transmission method, terminal, network-side equipment, and system, so as to reduce the overhead of QoS flow ID of uplink data and improve the transmission efficiency of uplink data.

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

The terminal transmits uplink data in a time-domain scheduling unit sequence, and each time-domain scheduling unit in the time-domain scheduling unit sequence corresponds to one or more QoS flow IDs in a 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 time domain scheduling unit label and the QoS flow ID of the uplink data, the terminal only needs to query the preset mapping by using the label of the scheduling unit as the query identifier. Relationship, you can know which QoS flow the data in the data packet on the time-domain scheduling unit comes from. Therefore, the transmitted data packet no longer needs to carry the QoS flow ID, which is helpful to reduce the overhead of the QoS flow ID of the upstream data and increase the uplink. Data transmission efficiency.

In a 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 data in a data packet transmitted on the time domain scheduling unit comes from a corresponding one or The QoS flow identified by 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 a data radio bearer DRB of the terminal.

In a possible design, a label of at least one time domain scheduling unit in the time domain scheduling unit sequence corresponds to multiple QoS flow IDs in the preset mapping relationship, and the at least one time domain scheduling The data packet transmitted on the unit includes an instruction message, where the instruction 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 in the following manner:

Determined based on reflective mapping of QoS; or

Determined according to the flow mapping indicated by the radio resource control RRC signal.

In a possible design, the method further includes:

The terminal sends the preset mapping relationship through 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 uplink data in a time-domain scheduling unit sequence, and a label of each time-domain scheduling unit in the time-domain scheduling unit sequence corresponds to one or more QoS flow IDs in a 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 time domain scheduling unit label and the QoS flow ID of the uplink data, the network-side device only needs to query the prediction by using the label of the scheduling unit as the query identifier. By setting the mapping relationship, you can know which QoS flow the data in the data packet on the time domain scheduling unit comes from. Therefore, the transmitted data packet no longer needs to carry the QoS flow ID, which is beneficial to reducing the overhead of the QoS flow ID of the uplink data. Improve upstream data transmission efficiency.

In a 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 data in a data packet transmitted on the time domain scheduling unit comes from a corresponding one or The QoS flow identified by 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 a data radio bearer DRB of the terminal.

In a possible design, a label of at least one time domain scheduling unit in the time domain scheduling unit sequence corresponds to multiple QoS flow IDs in the preset mapping relationship, and the at least one time domain scheduling The data packet transmitted on the unit includes an instruction message, where the instruction 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 in the following manner:

Determined based on reflective mapping of QoS; or

Determined according to the flow mapping indicated by the RRC signal.

In a possible design, the method further includes:

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

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

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

The processing unit is configured to transmit uplink data in a time domain scheduling unit sequence through the communication unit, and 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. QoS flow ID.

In a 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 data in a data packet transmitted on the time domain scheduling unit comes from a corresponding one or The QoS flow identified by 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 a data radio bearer DRB of the terminal.

In a possible design, a label of at least one time domain scheduling unit in the time domain scheduling unit sequence corresponds to multiple QoS flow IDs in the preset mapping relationship, and the at least one time domain scheduling The data packet transmitted on the unit includes an instruction message, where the instruction 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 in the following manner:

Determined based on reflective mapping of QoS; or

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 the preset mapping relationship through a radio resource control RRC signal through the communication unit.

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

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

In a possible design, the network-side equipment includes a processing unit and a communication unit,

The processing unit is configured to receive uplink data through the communication unit in a time domain scheduling unit sequence, and 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. QoS flow ID.

In a 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 data in a data packet transmitted on the time domain scheduling unit comes from a corresponding one or The QoS flow identified by 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 a data radio bearer DRB of the terminal.

In a possible design, a label of at least one time domain scheduling unit in the time domain scheduling unit sequence corresponds to multiple QoS flow IDs in the preset mapping relationship, and the at least one time domain scheduling The data packet transmitted on the unit includes an instruction message, where the instruction 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 in the following manner:

Determined based on reflective mapping of QoS; or

Determined according to the flow mapping indicated by the RRC signal.

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

In a possible design, the network-side device includes a processor, and the processor is configured to support the network-side device to perform a corresponding function in the foregoing 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, which is used for coupling with the processor, and stores program instructions and data necessary for the network-side device.

In a fifth aspect, an embodiment of the present invention provides a communication system. The system includes a terminal and a network-side device according to the foregoing aspect.

According to a sixth aspect, an embodiment of the present invention provides a computer-readable storage medium. The computer-readable storage medium stores instructions, and when the computer-readable storage medium runs on the computer, causes the computer to execute the foregoing 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 execute the method described in the first aspect or the second aspect.

As can be seen from the above, in the embodiment of the present invention, since the preset mapping relationship includes the correspondence between the time domain scheduling unit label and the QoS flow ID of the uplink data, the terminal and the network-side device only need to query by using the label of the scheduling unit. Identification, query the preset mapping relationship, you can know which QoS flow the data in the data packet on the time-domain scheduling unit comes from, so the transmitted data packet no longer needs to carry the QoS flow ID, which is helpful to reduce the QoS flow of 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 a new protocol layer used to complete the mapping from QoS flow to data radio bearer DRB according to the corresponding QoS flow ID. The AS mainly includes the following functions: (1) Routing of QoS flow to data radio bearer DRB (2) Encapsulation of QoS flow ID in downlink data (3) Encapsulation of QoS flow ID in uplink data.

Please refer to FIG. 3. FIG. 3 is a possible network architecture of a mobile communication system according to an embodiment of the present invention. The network architecture includes network-side equipment and terminals. When the terminal accesses the mobile communication network provided by the network-side equipment, the terminal and the network-side equipment can be connected through a wireless link communication. The mobile communication system may be, for example, a 5G NR mobile communication system. 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. The terminals involved in the embodiments of the present invention may include various handheld devices with unlimited communication functions, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to wireless data machines, and various forms of user equipment (User Equipment , UE), mobile station (Mobile Station, MS), terminal device (terminal device), and so on. For ease of description, the devices mentioned above are collectively referred to as terminals.

Please refer to FIG. 4A. FIG. 4A is an uplink data transmission method provided by an embodiment of the present invention. The method includes a 401 part, which is specifically as follows:

In part 401, the terminal transmits uplink data in a time-domain scheduling unit sequence, and a label of each time-domain scheduling unit in the time-domain scheduling unit sequence corresponds to one or more QoS flow IDs in a preset mapping relationship. .

The number of the time-domain scheduling unit refers to the serial number of the time-domain scheduling unit. For example, the ten time-domain scheduling units are divided into time-domain scheduling unit Num1, time-domain scheduling unit Num2, time-domain scheduling unit Num3, Time domain scheduling unit Num4, time domain scheduling unit Num5, time domain scheduling unit Num6, time domain scheduling unit Num7, time domain scheduling unit Num8, time domain scheduling unit Num9, time domain scheduling unit Num10, then the time domain scheduling unit's The labels are Num1, Num2, Num3, Num4, Num5, Num6, Num7, Num8, Num9, Num10.

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

It can be seen that, in the embodiment of the present invention, since the preset mapping relationship includes the correspondence between the time domain scheduling unit label and the QoS flow ID of the uplink data, the terminal and the network-side device only need to query by using the label of the scheduling unit. Identification, query the preset mapping relationship, you can know which QoS flow the data in the data packet on the time-domain scheduling unit comes from, so the transmitted data packet no longer needs to carry the QoS flow ID, which is helpful to reduce the QoS flow of uplink data The overhead of ID improves the efficiency of uplink data transmission.

In a 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 sends uplink data of QoS flow 1 in the subframe labeled 3i, and sends uplink data of QoS flow 2 in the subframe labeled 3i + 1, and 3i + 2. The uplink data of QoS flow3 is sent in the subframes, 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: the label 3i corresponds to QoS flow 1, the label 3i + 1 corresponds to QoS flow 2, and the 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 sent / received in a subframe labeled 3i + 2, the terminal / base station will continue to send / receive other data according to the corresponding relationship.

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 data in a data packet transmitted on the time domain scheduling unit comes from a corresponding one or The QoS flow identified by 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 a data radio bearer DRB of the terminal.

Among them, the DRB is used to carry user plane data. According to different QoS, a maximum of 8 DRBs can be established between the terminal and the network-side device. The data radio bearer of the terminal corresponds to the PDCP layer entity of the terminal. One terminal can be composed of multiple PDCP entities, such as eight, can support eight DRBs. When the QoS flows of different service data on the network side are issued, the network-side device maps the QoS flows of different service data to the DRB, such as the terminal's WeChat service QoS. The flow is mapped to the first DRB of the terminal, and the QoS flow of the video 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 necessarily transmits a data packet. For example, when the previous scheduling unit does not transmit a data packet and the latter time-domain scheduling unit transmits a data packet, the label and The QoS flow ID corresponding to the data in the data packet still satisfies the preset mapping relationship.

In a possible example, a label of at least one time domain scheduling unit in the time domain scheduling unit sequence corresponds to multiple QoS flow IDs in the preset mapping relationship, and the at least one time domain scheduling The data packet transmitted on the unit includes an instruction message, where the instruction 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 sends uplink data of QoS flow 1 in the subframe labeled 3j, and sends uplink data of QoS flow2 and QoS flow3 in the subframe labeled 3j + 1. The 3j + 2 subframe sends uplink data of QoS flow 4, where j is 0 or a positive integer. In an optional example, if the base station receives a data packet in a sub-frame labeled 3i + 1, it needs to determine which QoS flow the data packet belongs to. For example, it can be implemented by the following method: adding 1 bit of 0/1 to the data packet The bit indicates the message to distinguish the data of the two flows.

It can be seen that, in this example, for a time domain scheduling unit corresponding to multiple QoS flow IDs at the same time, an indication message can be added to a data packet transmitted on the time domain scheduling unit to indicate the QoS flow ID corresponding to the current data packet. , Avoid carrying QoS flow ID, and the amount of information of the indication message is small. For example, for data packets transmitted on the time domain scheduling unit corresponding to two QoS flow IDs, two QoS can be indicated by 1 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 a possible example, the preset mapping relationship is determined in the following manner:

Determined based on reflective mapping of QoS; or

Determined according to the flow mapping indicated by the RRC signal.

Among them, for the two data packets transmitted before and after on the same DRB, the preset mapping relationship used by the latter data packet can be determined according to the mapping relationship used by the previous data packet. The mapping relationship determined by mapping, the latter data packet also corresponds to 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 also corresponds to the The mapping relationship determined by the flow mapping indicated by the RRC signal.

In a possible example, the method further includes:

Acquiring, by the terminal through an access layer AS entity, a QoS flow ID of a QoS flow of a data radio bearer DRB mapped to the terminal;

The terminal establishes a correspondence relationship between a 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 the correspondence between the label of the time domain scheduling unit and the QoS flow ID to form Preset mapping relationship, which makes it unnecessary for the terminal's data packet to spend extra delay at the PDCP layer waiting for the preset mapping relationship. It has been determined that the current data packet should carry data from the QoS flow, which is helpful to improve the immediacy of data packet encapsulation by the terminal. To improve data transmission efficiency.

In a possible example, the method further includes:

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

Please refer to FIG. 5. FIG. 5 is an uplink data transmission method according to an embodiment of the present invention. The method includes: 501, and the details are as follows:

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

It can be seen that, in the embodiment of the present invention, since the preset mapping relationship includes the correspondence between the time domain scheduling unit label and the QoS flow ID of the uplink data, the terminal and the network-side device only need to use the scheduling unit label as the query identifier. By querying the preset mapping relationship, you can know which QoS flow the data in the data packet on the time domain scheduling unit comes from. Therefore, the transmitted data packet no longer needs to carry the QoS flow ID, which is beneficial to reducing the QoS flow ID of the uplink data. Overhead to improve uplink data transmission efficiency.

In a 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 data in a data packet transmitted on the time domain scheduling unit comes from a corresponding one or The QoS flow identified by 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 a data radio bearer DRB of the terminal.

In a possible design, a label of at least one time domain scheduling unit in the time domain scheduling unit sequence corresponds to multiple QoS flow IDs in the preset mapping relationship, and the at least one time domain scheduling The data packet transmitted on the unit includes an instruction message, where the instruction 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 in the following manner:

Determined based on reflective mapping of QoS; or

Determined according to the flow mapping indicated by the RRC signal.

In a possible design, the method further includes:

Determining, by the network-side device, the label of the time-domain scheduling unit through an access layer AS entity;

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 a possible design, the method further includes:

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

The above mainly introduces the solution of the embodiment of the present invention from the perspective of interaction between various network elements. It can be understood that, in order to realize the above functions, the terminal and the network-side device include a hardware structure and / or a software module corresponding to each function. Those with ordinary knowledge in the technical field should easily realize that the present invention can be implemented in the form of hardware or a combination of hardware and computer software in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein. . Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application of the technical solution and design constraints. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation should not be considered outside the scope of the present invention.

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

In the case of using an integrated unit, FIG. 6A shows a possible structural schematic diagram of the first core network device involved in the foregoing 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 used in the technology described herein. The communication unit 603 is configured to support communication between the terminal and other devices, for example, communication with a network-side device shown in FIG. 3. The terminal may further include a storage unit 601 for storing program codes and materials of the terminal.

The processing unit 602 may be a processor or a controller. For example, the processing unit 602 may be 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 devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the present disclosure. The processor may also be a combination that implements computing functions, such as a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on. The communication unit 603 may be a transceiver, a transceiver circuit, and the like, and the storage unit 601 may be a memory.

The processing unit 602 is configured to transmit uplink data in the time domain scheduling unit sequence through the communication unit 603. Each time domain scheduling unit number in the time domain scheduling unit sequence corresponds to one or more in a preset mapping relationship. Multiple QoS flow IDs.

In a 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 data in a data packet transmitted on the time domain scheduling unit comes from a corresponding one or The QoS flow identified by 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 a data radio bearer DRB of the terminal.

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

In a possible example, the preset mapping relationship is determined in the following manner:

Determined based on reflective mapping of QoS; or

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 the preset mapping relationship through a radio resource control RRC signal through the communication unit 603.

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 this embodiment of the present invention may be a terminal shown in FIG. 4AB.

As shown in 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 614. The communication interface 613, the processor 612, and the memory 611 may be connected to each other through a bus 614. The bus 614 may be a Peripheral Component Interconnect (PCI) bus or an extended industry standard architecture. Standard Architecture (EISA) bus. The bus 614 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only a thick line is used in FIG. 6B, but it does not mean that there is only one bus or one type of bus.

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

In the case of using an integrated unit, FIG. 7A shows a possible structural schematic diagram of the first core network device involved in the foregoing embodiment. The network-side device 700 includes a processing unit 702 and a communication unit 703. The processing unit 702 is configured to control and manage the actions 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 step 4C, and / or Other procedures for the techniques described herein. The communication unit 703 is configured to support communication between the network-side device and other devices, for example, communication with a terminal shown in FIG. 3. The network-side device may further include a storage unit 701 for storing program codes and data of the network-side device.

The processing unit 702 may be a processor or a controller. For example, the processing unit 702 may be 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 devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the present disclosure. The processor may also be a combination that implements computing functions, such as a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on. The communication unit 703 may be a transceiver, a transceiver circuit, and the like, and the storage unit 701 may be a memory.

The processing unit 702 is configured to receive uplink data through the communication unit 703 in a time-domain scheduling unit sequence, and each time-domain scheduling unit number in the time-domain scheduling unit sequence corresponds to a preset mapping relationship or Multiple QoS flow IDs.

In a 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 data in a data packet transmitted on the time domain scheduling unit comes from a corresponding one or The QoS flow identified by 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 a data radio bearer DRB of the terminal.

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

In a possible example, the preset mapping relationship is determined in the following manner:

Determined based on reflective mapping of QoS; or

Determined according to the flow mapping indicated by the RRC signal.

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

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 involved in the embodiment of the present invention may be the network-side device shown in FIG. 7B.

As shown in 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 714. The communication interface 713, the processor 712, and the memory 711 may be connected to each other through a bus 714. The bus 714 may be a Peripheral Component Interconnect (PCI) bus or an extended industry standard architecture. Standard Architecture (EISA) bus. The bus 714 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only a thick line is used in FIG. 7B, but it does not mean that there is only one bus or one type of bus.

The above-mentioned network-side device shown in FIG. 7A or FIG. 7B may also be understood as a device for a network-side device, and the embodiment of the present invention is not limited.

An embodiment of the present invention further provides a communication system. The communication system includes the foregoing terminal and a network-side device.

This embodiment of the present invention also provides another terminal. As shown in FIG. 8, for convenience of explanation, only a part related to the embodiment of the present invention is shown. For specific technical details 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, sales terminal), an in-vehicle computer, etc. Taking the terminal as 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. Those with ordinary knowledge in the technical field may understand that the structure of the mobile phone shown in FIG. 8 does not constitute a limitation on the mobile phone, and may include more or fewer parts than shown in the figure, or combine some parts, or different parts. Layout.

The following describes the various 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, the RF circuit 910 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (Low Noise Amplifier, LNA), a duplexer, and the like. In addition, the RF circuit 910 can also communicate with a network and other devices through wireless communication. The above wireless communication can use any communication standard or protocol, including but not limited to the 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), email, Short Messaging Service (SMS), etc.

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

The input unit 930 can be used to receive inputted digital or character messages, and generate key signal inputs related to user settings and function control of the mobile phone. Specifically, the input unit 930 may include a fingerprint recognition module 931 and other input devices 932. The fingerprint identification module 931 can collect fingerprint data on the user. In addition to the fingerprint recognition module 931, the input unit 930 may 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 volume control keys, switch keys, etc.), a trackball, a mouse, an operation lever, and the like.

The display unit 940 may be used to display messages input by the user or messages provided to the user and various function tables of the mobile phone. The display unit 940 may include a display screen 941. Optionally, the display screen 941 may 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 identification module 931 and the display screen 941 are implemented as two independent components to implement the input and input functions of the mobile phone, in some embodiments, the fingerprint identification module 931 and the display screen 941 can be used Integration to realize the input and playback functions of the mobile phone.

The mobile phone may further include at least one sensor 950, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display screen 941 according to the brightness of the ambient light, and the proximity sensor may be moved to At your ears, turn off the display 941 and / or the backlight. As a kind of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in various directions (usually three axes). It can detect the magnitude and direction of gravity when it is stationary. It can be used to identify the attitude of mobile phones (such as horizontal and vertical screens) Switching, related games, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tap), etc .; as for the mobile phone can also be equipped with gyroscope, barometer, hygrometer, thermometer, infrared sensor and other sensors Tester, will not repeat them 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 may transmit the received electrical data converted electrical signals to a speaker 961, which is converted into a sound signal for playback; on the other hand, the microphone 962 converts the collected sound signal into an electrical signal, and the audio circuit 960 After receiving it, it is converted into audio data, which is then processed by the audio data playback processor 980 and then sent to, for example, another mobile phone 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. Through the WiFi module 970, a mobile phone can explain users to send and receive emails, browse web pages, and access streaming media. It 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 necessary configuration of the mobile phone, and can be omitted as needed without changing the essence of the invention.

The processor 980 is the control center of the mobile phone. It uses various interfaces and lines to connect various parts of the entire mobile phone. By running or executing software programs and / or modules stored in the memory 920, and calling data stored in the memory 920, To perform various functions and process data of the mobile phone, so as 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, wherein the application processor mainly processes an operating system, a user interface, and an application program. Etc., the modem processor mainly deals with wireless communication. It can be understood that the foregoing modem processor may not be integrated into the processor 980.

The mobile phone also includes a power supply 990 (such as a battery) for supplying power to various components. Preferably, the power supply can be logically connected to the processor 980 through a power management system, so as to implement functions such as management of charging, discharging, and power consumption 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 embodiments 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 embodiments shown in FIG. 6A and FIG. 6B, the functions of each unit may be implemented based on the structure of the mobile phone.

The method or algorithm steps described in the embodiments of the present invention may be implemented in a hardware manner, or may be implemented in a manner that a processor executes software instructions. Software instructions can be composed of corresponding software modules. The software modules can be stored in Random Access Memory (RAM), flash memory, read only memory (ROM), and erasable. Except for programmable ROM (Erasable Programmable ROM, EPROM), electrically erasable programmable ROM (Electrically EPROM, EEPROM), registers, hard disk, removable hard disk, CD-ROM 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, and write information to, the storage medium. Of course, the storage medium may also be part of the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may 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.

Those with ordinary knowledge in the technical field should be aware that in one or more of the above examples, 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 using software, it may be implemented in the form of a computer program product, in whole or in part. 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 according to the embodiments of the present invention are wholly or partially generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be from a website, a computer, a server, or data. The center transmits to another website, computer, server, or data center through wired (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, and the like that includes one or more available medium integration. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a Digital Video Disc (DVD)), or a semiconductor medium (for example, a solid state disk (Solid State) Disk, SSD)) and so on.

The specific implementation manners described above further describe the objectives, technical solutions, and beneficial effects of the embodiments of the present invention in detail. It should be understood that the foregoing are only specific implementation manners of the embodiments of the present invention, and are not used for The protection scope of the embodiments of the present invention is limited. Any modification, equivalent replacement, or improvement based on the technical solution of the embodiments of the present invention shall be included in the protection scope of the embodiments of the present invention.

401‧‧‧step

501‧‧‧step

600‧‧‧Terminal

601‧‧‧storage unit

602‧‧‧Processing unit

603‧‧‧communication unit

610‧‧‧Terminal

611‧‧‧Memory

612‧‧‧Processor

613‧‧‧ communication interface

614‧‧‧Bus

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‧‧‧Bus

910‧‧‧Radio frequency (RF) circuit

920‧‧‧Memory

930‧‧‧input unit

931‧‧‧Fingerprint recognition module

932‧‧‧Other input devices

940‧‧‧display unit

941‧‧‧display

950‧‧‧Sensor

960‧‧‧Audio Circuit

961‧‧‧Speaker

962‧‧‧microphone

970‧‧‧Wireless Fidelity (WiFi) Module

980‧‧‧ processor

990‧‧‧ Power

The following will briefly introduce the diagrams used in the embodiments or the description of the prior art. Figure 1 is a schematic diagram of a PDU Session established by the QoS of 5G NR; Figure 2 is a schematic diagram of the structure of a protocol stack of 5G NR; Figure 3 FIG. 4A is a schematic communication diagram of an uplink data transmission method according to an embodiment of the present invention; FIG. 4B is a preset mapping relationship provided by an embodiment of the present invention 4C is a schematic diagram of another preset mapping relationship provided by an embodiment of the present invention; FIG. 5 is a communication diagram of another uplink data transmission method provided by an embodiment of the present invention; FIG. 6A is a terminal provided by an embodiment of the present invention Schematic diagram of the structure; FIG. 6B is a diagram of the structure of another terminal provided by an embodiment of the present invention; FIG. 7A is a diagram of the structure of a network-side device provided by 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 ID QoS flow ID. The method according to item 1 of the scope of patent application, 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 according to item 1 of the scope of patent application, wherein the preset mapping relationship is a correspondence between a label of a time-domain scheduling unit and a QoS flow ID. The data comes from the QoS flow identified by the corresponding one or more QoS flow IDs, and 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. The method according to item 1 of the scope of patent application, wherein the label of at least one time domain scheduling unit in the sequence of time domain scheduling units corresponds to multiple QoS flow IDs in the preset mapping relationship, The data packet transmitted on the at least one time domain scheduling unit includes an instruction message, and the instruction message is used to indicate one of the multiple QoS flow IDs corresponding to the data packet. The method according to item 1 of the scope of patent application, wherein the preset mapping relationship is determined by: determining a reflection mapping based on QoS; or determining a flow mapping indicated by a radio resource control RRC signal. The method according to any one of claims 1 to 5, wherein the method further comprises: the terminal sending the preset mapping relationship through a radio resource control RRC signal. An uplink data transmission method, comprising: receiving, by a network-side device, uplink data in a time-domain scheduling unit sequence, and a label of each time-domain scheduling unit in the time-domain scheduling unit sequence corresponds to one or more of the preset mapping relationships. QoS flow ID. The method according to item 7 of the scope of patent application, 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 according to item 7 or 8 of the scope of patent application, wherein the preset mapping relationship is a correspondence between a time domain scheduling unit label and a QoS flow ID, and a data packet transmitted on the time domain scheduling unit. The data in the data comes from the QoS flow identified by the corresponding one or more QoS flow IDs. 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 includes a processor, a memory, and a transceiver, and the processor is communicatively connected to the memory and the transceiver; and the memory stores program code and data, and the processor is configured to call The program code and the data in the memory execute the method according to any one of claims 1-6 of the scope of patent application.