TWI692961B - Data transmission method and sending end equipment - Google Patents

Abstract

A method for transmitting data and a device at a transmitting end capable of supporting a multi-basic parameter set mechanism. The method includes: the device at a transmitting end determines a MAC entity to be used for transmitting data to be transmitted among a plurality of MAC entities, and the data to be transmitted is from a media interface. Enter the first protocol entity above the control MAC layer; send the data to be sent through the determined MAC entity used to send the data to be sent.

Description

Data transmission method and sending end equipment

The present application relates to the field of communications, and more specifically, to a method of transmitting data and a device at a transmitting end.

In the existing Long Term Evolution (LTE) system, the Media Access Control (MAC) layer is responsible for Hybrid Automatic Repeat reQuest (HARQ) and uplink and downlink scheduling. The MAC layer provides services for the Radio Link Control (RLC) layer in the form of logical channels. Its main purpose is to provide an effective connection between the RLC layer and the physical layer.

In the 5G system, due to the diversity of business needs, the design of the MAC layer can meet the diversity of business needs. Therefore, a new design method of the MAC layer needs to be studied to support the diversity of business needs.

The embodiments of the present application provide a data transmission method and a sending end device, which can support the diversity of service requirements.

In the first aspect, a method for transmitting data is provided, including:

The sending-end device determines the MAC entity used to send the data to be sent among multiple media access control MAC entities, where the data to be sent comes from the first protocol entity above the MAC layer;

Sending the data to be sent through the determined MAC entity used for sending the data to be sent.

Optionally, the sending end device determining the MAC entity to be used for sending the data to be sent among multiple MAC entities includes:

According to the logical channel or radio bearer or data flow used by each MAC entity in the plurality of MAC entities, the available resources of each MAC entity, the channel conditions that each MAC entity can handle, and each MAC At least one of the maximum amount of data that can be processed by the entity or the range of data amount determines the MAC entity used to send the data to be sent.

Optionally, according to the logical channel or radio bearer or data stream used by each MAC entity in the plurality of MAC entities, the available uplink resources of each MAC entity, and the channels that each MAC entity can handle Conditions, at least one of the maximum amount of data or the range of data amounts that each MAC entity can process, and determining the MAC entity to use for sending the data to be sent includes:

According to the first correspondence, and the logical channel or radio bearer or data stream used by the data to be sent, determine the MAC entity used to send the data to be sent among the plurality of MAC entities, the first correspondence indicates the sending Correspondence between logical channels or radio bearers or data streams used by data and MAC entities.

Optionally, in the first correspondence, each MAC entity corresponds to at least one logical channel or at least one radio bearer, and the logical channel or radio bearer or data stream used according to the first correspondence and the data to be sent , Determining the MAC entity used to send the data to be sent among the multiple MAC entities, including:

Determine, according to the correspondence between each MAC entity and the at least one logical channel or the at least one radio bearer, and the logical channel or radio bearer used to send the data to be sent, determine to send among the multiple MAC entities The MAC entity used by the data to be sent.

Optionally, according to the logical channel or radio bearer or data stream used by each MAC entity in the plurality of MAC entities, the available uplink resources of each MAC entity, and the channels that each MAC entity can handle Conditions, at least one of the maximum amount of data or the range of data amounts that each MAC entity can process, and determining the MAC entity to use for sending the data to be sent includes:

A MAC entity used to send the data to be sent is determined among the MAC entities of the multiple MAC entities that have available uplink resources.

Optionally, the determining, among the MAC entities of the plurality of MAC entities with available uplink resources, the MAC entity used for sending the data to be sent includes:

It is determined that the MAC entity with the most available uplink resources is the MAC entity used for sending the data to be sent.

Optionally, according to the logical channel or radio bearer or data stream used by each MAC entity in the plurality of MAC entities, the available resources of each MAC entity, and the channel conditions that each MAC entity can handle , At least one of the maximum amount of data or the range of data amounts that each MAC entity can process, and determining the MAC entity to use for sending the data to be sent includes:

According to the data volume of the data to be sent and the correspondence between each MAC entity and the maximum data volume or the range of data volume that each MAC entity can handle, determine the sending location among multiple MAC entities Describe the MAC entity used for the data to be sent.

Optionally, according to the logical channel or radio bearer or data stream used by each MAC entity in the plurality of MAC entities, the available resources of each MAC entity, and the channel conditions that each MAC entity can handle , At least one of the maximum amount of data or the range of data amounts that each MAC entity can process, and determining the MAC entity to use for sending the data to be sent includes:

According to the channel conditions of the logical channel used to send the data to be sent and the correspondence between each MAC entity and the channel conditions that each MAC entity can handle, determine the use of the data to be sent from multiple MAC entities MAC entity.

Optionally, the sending end device is a terminal device or a network device.

Optionally, if the sending end device is a terminal device, the method further includes:

The sending end device receives the first correspondence sent by the network device.

Optionally, if the sending end device is a terminal device, the method further includes:

The sending end device receives the correspondence between each MAC entity sent by the network device and the maximum data volume that can be processed or the range of data volume that can be processed.

Optionally, if the sending end device is a terminal device, the method further includes:

The sending end device receives the correspondence between each MAC entity and channel condition sent by the network device.

Optionally, if the sending end device is a terminal device, the method further includes:

The sending-end device initiates a random access process through the primary MAC entity or any MAC entity among the multiple MAC entities.

Optionally, the method further includes:

The sending end device receives configuration information of a network device, and the configuration information instructs the sending end device to use a primary MAC entity or any MAC entity among the plurality of MAC entities to initiate a random access process.

Optionally, the first protocol entity is a radio link control RLC entity or a packet data aggregation protocol PDCP entity.

Optionally, the method is performed by a data distribution module in the sending-end device, and the data distribution module is located in an upper layer entity of the plurality of MAC entities.

Optionally, the data distribution module is located in an RLC entity or a PDCP entity.

Optionally, the method is performed by a data distribution module in the sending-end device, and the data distribution module is located in a high-level protocol at the MAC layer.

Optionally, the method is performed by a data distribution module in the sending-end device, and the data distribution module is located in any MAC entity of the plurality of MAC entities.

In the second aspect, a method for transmitting data is provided, including:

The sending-end device determines the MAC entity corresponding to the basic parameter set among multiple MAC entities according to the basic parameter set used by the data to be transmitted from the physical layer and the correspondence between the medium access control MAC entity and the basic parameter set;

Sending the data to be sent through the MAC entity corresponding to the basic parameter set.

Optionally, the sending end device is a network device or a terminal device.

Optionally, if the sending end device is a terminal device, the method further includes:

The sending end device receives the correspondence between the MAC entity and the basic parameter set sent by the network device.

Optionally, if the sending end device is a terminal device, the method further includes:

The sending end device receives a physical downlink control channel PDCCH sent by a network device, the PDCCH includes a basic parameter set of a first channel, and the data to be sent is sent through the first channel;

It is determined that the basic parameter set of the first channel is the basic parameter set used by the data to be sent.

In a third aspect, a sending-end device is provided, and the sending-end device may include a unit that executes the method in the first aspect or any optional implementation manner thereof.

According to a fourth aspect, a sending end device is provided, and the sending end device may include a unit that executes the method in the second aspect or any optional implementation manner thereof.

According to a fifth aspect, a sending-end device is provided. The sending-end device includes a processor and a memory. Wherein, the program code is stored in the memory, and the processor is used to call the program code stored in the memory to execute the method in the first aspect or its various implementations.

According to a sixth aspect, a sending-end device is provided, and the sending-end device includes a processor and a memory. Wherein, the program code is stored in the memory, and the processor is used to call the program code stored in the memory to execute the method in the second aspect or various implementations thereof. .

According to a seventh aspect, a computer-readable medium is provided. The computer-readable medium stores program code for execution by a terminal device, where the program code includes instructions for executing the method in the first aspect or various implementations thereof.

In an eighth aspect, a computer-readable medium is provided, the computer-readable medium storing program code for execution by a terminal device, the program code including instructions for performing a method in the second aspect or various implementations thereof.

Based on the above technical solution, the MAC layer includes multiple MAC entities, which correspond to multiple basic parameter sets of the physical layer. When the sending device has data to be sent from a higher layer that needs to be sent, multiple MAC entities in the MAC layer Choose a MAC entity as the MAC entity to send the data to be sent, and then send the data to be sent through the MAC entity. Therefore, the data transmission method according to the embodiment of the present application can support the diversity of business requirements.

The technical solutions in the embodiments of the present application will be described below in conjunction with the illustrations in the embodiments of the present application.

It should be understood that the technical solution of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, and wideband code division multiple Address (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, advanced long term evolution (LTE-A) System, Universal Mobile Telecommunication System (UMTS), 5G New Radio (NR) system, etc.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this article is just an association relationship that describes an associated object, indicating that there can be three relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone. three situations. In addition, the character "/" in this article generally indicates that the related objects are a "or" relationship.

FIG. 1 is a schematic diagram of a wireless communication system 100 applied in an embodiment of the present application. The wireless communication system 100 includes at least one network device 110. The network device 100 may be a device that communicates with a terminal device. Each network device 100 can provide communication coverage for a specific geographic area, and can communicate with terminal devices located in the coverage area. The network device 100 may be a base station (Base Transceiver Station, BTS) in a GSM system or a code division multiple access (CDMA) system, or a base station (NodeB, NB) in a WCDMA system, or may be Evolutionary Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device can be a relay station, an access point, Vehicle-mounted devices, wearable devices, network-side devices in the future 5G network or network devices in the public land mobile network (PLMN) that will evolve in the future, etc.

The wireless communication system 100 further includes at least one terminal device 120 located within the coverage of the network device 110. The terminal device 120 may be mobile or fixed. Alternatively, the terminal device 120 may refer to an access terminal, user equipment (User Equipment, UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication Device, user agent, or user device. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), or wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in future 5G networks or terminal devices in future evolved PLMNs, etc.

Figure 2 shows a functional structure diagram of the Media Access Control (MAC) layer. The main functions supported by the MAC layer include: mapping between logical channels and transmission channels; selection of transmission formats, for example, by selecting transmission blocks Size, modulation scheme, etc. are provided as input parameters to the physical layer; priority management of logical channels between one UE or multiple UEs; error correction through HARQ mechanism; padding; Radio Link Control (Radio Link Control, RLC) ) Protocol Data Unit (Protocol Data Unit, PDU) multiplexing and de-multiplexing, business volume measurement and reporting, etc.

The services provided by the MAC layer to the upper layer mainly include: data transmission and wireless resource allocation. The services provided by the physical layer to the MAC layer include: data transmission, Hybrid Automatic Repeat ReQuest (HARQ) feedback signaling, scheduling request signaling, and measurement.

In the uplink, the MAC layer of the terminal device multiplexes its own multiple uplink data streams and decides whether to send an uplink scheduling request or uplink data. On the downlink shared channel, the eNodeB must consider the data flow (or logical channel) sent to all user equipment in the cell. This involves priority processing, which is a major function of the MAC layer. Priority processing refers to the process of selecting a packet from different waiting queues, passing it to the physical layer, and sending it through the wireless interface. Because the transmission of different information flows must be considered, including pure user data, E-UTRAN signaling and Evolved Packet Core (EPC) signaling, this process is very complicated. When the transmitted data is not received correctly, whether to retransmit is also related to priority processing, so the priority processing process is still closely related to HARQ, HARQ is another main function of MAC. In addition, the MAC layer of the network device is responsible for uplink priority processing because it must select from all uplink scheduling request messages of multiple terminals sharing the UL-SCH transmission channel.

It should be understood that the functional structure of the MAC entity shown in FIG. 2 is only an example, and should not constitute any limitation to the embodiments of the present application.

FIG. 3 schematically shows a data transmission method 300 provided by an embodiment of the present application. The method 300 can be applied to the wireless communication system 100 described above, but the embodiments of the present application are not limited thereto.

As shown in FIG. 3, the method 300 includes the following.

In 301, a sending-end device determines a MAC entity used for sending data to be sent from a plurality of MAC entities, where the data to be sent comes from a first protocol entity above a MAC layer.

In 302, the data to be sent is sent through the determined MAC entity used to send the data to be sent.

Optionally, the functional structure of the multiple MAC entities may be the functional structure of the MAC entity shown in FIG. 2, or may also adopt other forms of functional structures, which are not limited in the embodiments of the present application.

Due to the diversified directions of business requirements, a variety of basic parameter set transmission technologies are introduced in the physical layer. Therefore, in the embodiment of the present application, there may be multiple MAC entities corresponding to the MAC layer to support multiple basic parameter set mechanisms. Therefore, accordingly, when transmitting data from a higher layer above the MAC layer to the MAC layer, since there are multiple MAC entities, it is necessary to select the MAC entity used for data transmission.

Specifically, when receiving the data to be sent from the first protocol entity above the MAC layer, the sending end device may determine the MAC entity used to send the data to be sent among the multiple MAC entities of the MAC layer, and then determine The MAC entity sends the data to be sent.

It should be understood that, in the embodiments of the present application, the sending end device may be a terminal device or a network device.

Optionally, in some embodiments, the first protocol entity may be an RLC entity or a Packet Data Convergence Protocol (PDCP) entity.

Optionally, in some embodiments, the sending-end device determining the MAC entity used to send the data to be sent among multiple MAC entities includes:

According to the logical channel or radio bearer or data flow used by each MAC entity in the plurality of MAC entities, the available resources of each MAC entity, the channel conditions that each MAC entity can handle, and each MAC At least one of the maximum amount of data that can be processed by the entity or the range of data amount determines the MAC entity used to send the data to be sent.

That is to say, the sending-end device can determine the MAC entity used to send the data to be sent according to the logical channel or radio bearer or data stream used by each MAC entity, or can also be determined according to the available resources of each MAC entity The MAC entity used to send the data to be sent, or the MAC entity used to send the data to be sent can be determined according to the available resources of each MAC entity combined with the channel conditions that each MAC entity can handle, or can also be determined according to The maximum amount of data that each MAC entity can handle, combined with the channel conditions that each MAC entity can handle, determines the MAC entity used to send the data to be sent, etc., which is not limited in the embodiments of the present application.

Optionally, in some embodiments, according to the logical channel or radio bearer or data flow used by each MAC entity of the plurality of MAC entities, the available uplink resources of each MAC entity, the each The channel condition that the MAC entity can handle, at least one of the maximum amount of data or the range of data amount that each MAC entity can handle, and determining the MAC entity used to send the data to be sent includes:

According to the first correspondence, and the logical channel or radio bearer or data stream used by the data to be sent, determine the MAC entity used to send the data to be sent among the plurality of MAC entities, the first correspondence indicates the sending Correspondence between logical channels or radio bearers or data streams used by data and MAC entities.

Specifically, the first correspondence may be a correspondence between a logical channel used to send data and a MAC entity, or may be a correspondence between a wireless bearer used to send data and a MAC entity, or may be data used to send data Correspondence between flows and MAC entities. For example, in the first correspondence, signaling radio bearer (Signaling Radio Bearer, SRB) 0 corresponds to the MAC0 entity, SRB1 corresponds to the MAC1 entity, and SRB2 corresponds to the MAC2 entity, then when sending the data to be sent through SRB0, the sending end The device may determine that the SRB0 corresponds to the MAC0 entity according to the first correspondence, and then may send the data to be sent through the MAC0 entity. For another example, in the first correspondence, a common control channel (Common Control Channel, CCCH) corresponds to the MAC0 entity, a dedicated control channel (Dedicated Control Channel, DCCH) corresponds to the MAC1 entity, and a dedicated traffic channel (Dedicated Traffic Channel, DTCH) corresponds to MAC2. Entity, then if the sending end device needs to send the data to be sent through the DTCH channel, it can determine that the DTCH channel corresponds to the MAC2 entity according to the first correspondence, and then can send the data to be sent through the MAC2 entity.

Optionally, in some embodiments, in the first correspondence, each MAC entity corresponds to at least one logical channel or at least one radio bearer, the logical channel used according to the first correspondence, and the data to be sent Or a wireless bearer or a data stream, and determining, among the multiple MAC entities, the MAC entity used to send the data to be sent includes:

Determine, according to the correspondence between each MAC entity and the at least one logical channel or the at least one radio bearer, and the logical channel or radio bearer used to send the data to be sent, determine to send among the multiple MAC entities The MAC entity used by the data to be sent.

Specifically, each MAC entity may correspond to at least one logical channel or at least one radio bearer, and the sending end device may combine each MAC entity with the at least one according to the logical channel or radio bearer used to send the data to be sent Correspondence between logical channels, or combining the correspondence between each MAC entity and the at least one radio bearer, determines the MAC entity corresponding to the data to be sent, and then sends the data to be sent through the determined MAC entity.

Optionally, one MAC entity among the multiple MAC entities is set as the main MAC entity, and all the data to be sent can be set to be sent through the main MAC entity, or the main MAC entity can also be set to handle the use of a specific SRB or For the data to be sent of a specific channel, for example, data to be sent using SRB0, SRB1 and SRB2 may be set to be sent through the primary MAC entity, or data to be sent using CCCH, DCCH and DTCH may also be set to be sent through the primary MAC entity. Alternatively, the primary MAC entity may also be configured to process messages of the control plane of the sending end device, etc. This embodiment of the present application does not limit this.

Optionally, in some embodiments, if the sending device is a terminal device, the method further includes:

The sending end device receives the first correspondence sent by the network device.

That is, when the sending end device is a terminal device, the first correspondence may be sent by the network device to the terminal device. Optionally, the sending end device may notify the terminal device of the first correspondence by sending a Physical Downlink Control Channel (PDCCH), or the network device may also notify the terminal device of the first correspondence by other signals There is a corresponding relationship, which is not limited in the embodiments of the present application.

Optionally, in some embodiments, according to the logical channel or radio bearer or data flow used by each MAC entity of the plurality of MAC entities, the available uplink resources of each MAC entity, the each The channel condition that the MAC entity can handle, at least one of the maximum amount of data or the range of data amount that each MAC entity can handle, and determining the MAC entity used to send the data to be sent includes:

A MAC entity used to send the data to be sent is determined among the MAC entities of the multiple MAC entities that have available uplink resources.

Specifically, the sending-end device may determine a MAC entity with available uplink resources among the multiple MAC entities, and then determine a MAC entity for sending the data to be sent among the MAC entities with available uplink resources, optionally, The sending device may select the MAC entity with the most available uplink resources among the MAC entities with available uplink resources as the MAC entity for sending the data to be sent, or may select any MAC entity for sending the data to be sent MAC entity.

Optionally, in some embodiments, the determining, among the MAC entities of the plurality of MAC entities with available uplink resources, the MAC entity used to send the data to be sent includes:

It is determined that the MAC entity with the most available uplink resources is the MAC entity used for sending the data to be sent.

Optionally, in some embodiments, according to the logical channel or radio bearer or data flow used by each MAC entity of the plurality of MAC entities, the available resources of each MAC entity, the each MAC The channel condition that the entity can handle, at least one of the maximum amount of data or the range of data amount that each MAC entity can handle, and determining the MAC entity used to send the data to be sent includes:

According to the data volume of the data to be sent and the correspondence between each MAC entity and the maximum data volume or the range of data volume that each MAC entity can handle, determine the sending location among multiple MAC entities Describe the MAC entity used for the data to be sent.

Specifically, each MAC entity may correspond to the corresponding maximum data volume or data volume range that can be processed, and the sending end device may combine the maximum data that each MAC entity can process with the corresponding maximum data volume that can be processed according to the data volume of the data to be transmitted The corresponding relationship between the amount or the range of the data amount determines the MAC entity used to send the data to be sent. For example, MAC0 corresponds to the amount of data that can be processed from 2MB to 4MB, MAC1 corresponds to the amount of data that can be processed from 4MB to 6MB, and MAC2 corresponds to the amount of data that can be processed from 6MB to 8MB. When the data to be sent is 5MB, this The sending device may determine that the data to be sent can be sent through MAC1. For another example, MAC0 corresponds to a maximum data volume of 2MB, MAC1 corresponds to a maximum data volume of 4MB, and MAC2 corresponds to a maximum data volume of 8MB. When the data to be transmitted is 5MB, the sender The device may determine that the data to be sent can be sent through MAC2.

Optionally, in some embodiments, if the sending device is a terminal device, the method further includes:

The sending-end device receives the correspondence between each MAC entity and the maximum amount of data that each MAC entity can process or the range of data amounts that can be processed sent by the network device.

That is to say, when the sending end device is a terminal device, the correspondence between each MAC entity and the maximum data volume that can be processed or the range of data volume that can be processed may be sent by the network device to the terminal device. Optionally, the sending end device may notify the terminal device of the correspondence between each MAC entity and the maximum data volume that can be processed or the range of data volume that can be processed by sending the PDCCH, or the network device may also be notified by other signals The correspondence between each MAC entity of the terminal device and the maximum data volume that can be processed or the range of data volume that can be processed is not limited in this embodiment of the present application.

Optionally, in some embodiments, according to the logical channel or radio bearer or data flow used by each MAC entity of the plurality of MAC entities, the available resources of each MAC entity, the each MAC The channel condition that the entity can handle, at least one of the maximum amount of data or the range of data amount that each MAC entity can handle, and determining the MAC entity used to send the data to be sent includes:

According to the channel conditions of the logical channel used to send the data to be sent and the correspondence between each MAC entity and the channel conditions that each MAC entity can handle, determine the use of the data to be sent from multiple MAC entities MAC entity.

Specifically, each MAC entity can correspond to a corresponding channel condition that can be processed. The sending end device can determine the MAC entity corresponding to the channel condition according to the current channel condition of the logical channel used to send the data to be sent, and then pass the The MAC entity sends the data to be sent.

Optionally, the channel condition may be a channel quality threshold or a channel quality range, and each MAC entity corresponds to a corresponding channel quality threshold or channel quality range that can be processed, for example, MAC0 for channel quality threshold 0~channel quality threshold 1. MAC1 corresponds to channel quality threshold 1 ~ channel quality threshold 2, MAC2 corresponds to channel quality threshold 2 ~ channel quality threshold 3, the sending end device determines that the current channel quality of the logical channel used to send the data to be sent falls within the channel quality threshold 2 ~ Within the channel quality threshold 3, it can be determined that the MAC2 entity is used to send the data to be sent.

Optionally, in some embodiments, if the sending device is a terminal device, the method further includes:

The sending-end device receives the correspondence between each MAC entity and the channel conditions that each MAC entity can handle sent by the network device.

That is to say, when the sending end device is a terminal device, the correspondence between each MAC entity and the channel conditions that each MAC entity can handle may be sent by the network device to the terminal device. Optionally, the sending end device may notify the terminal device of the correspondence between each MAC entity and the channel conditions that each MAC entity can handle by sending the PDCCH, or the network device may also notify the terminal device of each signal through other signals. The correspondence relationship between each MAC entity and the channel conditions that each MAC entity can handle is not limited in this embodiment of the present application.

Optionally, in some embodiments, if the sending device is a terminal device, the method further includes:

The sending-end device initiates a random access process through the primary MAC entity or any MAC entity among the multiple MAC entities.

That is to say, the random access process may correspond to the main MAC entity or may correspond to any MAC entity among multiple MAC entities. When the random access process corresponds to the main MAC entity, the sending end device may pass the main MAC entity Initiate a random access process. When the random access process corresponds to any MAC entity, the sending end device may initiate the random access process through any MAC entity.

In this case, the method may further include:

The sending end device receives configuration information of a network device, and the configuration information instructs the sending end device to use a primary MAC entity or any MAC entity among the plurality of MAC entities to initiate a random access process.

That is, the sending end device can receive configuration information of the network device, and the configuration information indicates that the random access process corresponds to the main MAC entity or any MAC entity among the multiple MAC entities.

Optionally, in some embodiments, the method is performed by a data distribution module in the sending-end device, where the data distribution module is located in an upper layer entity of the multiple MAC entities.

Optionally, in some embodiments, the method is performed by a data distribution module in the sending-end device, where the data distribution module is located in a high-level protocol at the MAC layer.

Optionally, in some embodiments, the method is performed by a data distribution module in the sending-end device, and the data distribution module is located in any MAC entity of the plurality of MAC entities.

That is to say, the data distribution module may be located in any MAC entity, may also be located in an upper layer entity of the MAC entity, or may be located in a higher layer protocol of the MAC layer, the higher layer protocol of the MAC layer is in the MAC of the MAC layer Below the RLC layer above the entity. The data distribution module can select an appropriate MAC entity for processing the data from the upper layer, and can also aggregate the data from each MAC entity and submit it to the upper layer. The upper layer can be the RLC layer or the PDCP layer.

FIG. 4 shows a schematic flowchart of a data transmission method 400 according to an embodiment of the present application, as shown in FIG. 4,

At 401, the sending-end device determines the basis for using the data to be sent among multiple MAC entities according to the basic parameter set used by the data to be sent from the physical layer and the correspondence between the medium access control MAC entity and the basic parameter set MAC entity corresponding to the parameter set.

At 402, the data to be sent is sent through the determined MAC entity corresponding to the basic parameter set.

Specifically, between the physical layer and the MAC layer, multiple basic parameter sets of the physical layer and MAC entities of the MAC layer may have a corresponding relationship, and each basic parameter set may be processed by a corresponding MAC entity, so that the transmitting end device may According to the basic parameter set used by the data to be sent from the physical layer and the corresponding relationship between the MAC entity and the basic parameter set, determine the MAC entity corresponding to the basic parameter set used by the data to be sent, and then pass the MAC entity corresponding to the basic parameter set Sending the data to be sent.

Optionally, in some embodiments, the sending end device is a network device or a terminal device.

Optionally, in some embodiments, if the sending device is a terminal device, the method further includes:

The sending end device receives the correspondence between the MAC entity and the basic parameter set sent by the network device.

That is to say, when the sending end device is a terminal device, the correspondence between the MAC entity and the basic parameter set may be sent by the network device to the terminal device. Optionally, the sending device may notify the terminal device of the correspondence between the MAC entity and the basic parameter set by sending a PDCCH, or the network device may also notify the terminal device of the MAC entity and the basic by other signals The corresponding relationship of the parameter set is not limited in this embodiment of the present application.

Optionally, if the sending end device is a terminal device, the method further includes:

The sending end device receives a physical downlink control channel PDCCH sent by a network device, the PDCCH includes a basic parameter set of a first channel, and the data to be sent is sent through the first channel;

It is determined that the basic parameter set of the first channel is the basic parameter set used by the data to be sent.

That is, the network device may notify the terminal device of the basic parameter set used by the data to be sent. Optionally, the network device may notify the terminal device of the basic parameter set used by the first channel through the PDCCH, so that the terminal device may receive the data to be transmitted transmitted through the first channel according to the basic parameter set. Therefore, the first The basic parameter set used by one channel is the basic parameter set used by the data transmitted on the first channel.

In general, when the sending end device receives the data to be sent from the physical layer, it can determine the basic parameter set used by the data to be sent, and then according to the correspondence between the MAC entity configured by the network device and the basic parameter set To determine to which MAC entity to submit the data to be sent. After receiving the data to be sent, the corresponding MAC entity may further submit the data to be sent to a higher layer, such as the RLC layer or the PDCP layer. Optionally, the MAC entity may also submit the data to be sent to the data distribution module, and then the data distribution module may submit the data to be sent to the upper layer. Optionally, if the data distribution module needs to reorder the data to be sent, the data to be sent can be reordered. The data distribution module can then continue to submit the data to be sent to a higher layer for processing, such as the RLC layer or the PDCP layer.

FIG. 5 is a schematic block diagram of a sending end device 500 according to an embodiment of the present application. As shown in FIG. 5, the sending-end device 500 includes a determining unit 510 and a transceiver unit 520.

The determining unit 510 is configured to determine a MAC entity used for sending data to be sent among multiple media access control MAC entities, where the data to be sent comes from a first protocol entity above the MAC layer;

The transceiver unit 520 is configured to send the data to be sent through the determined MAC entity used to send the data to be sent.

Optionally, in some embodiments, the determining unit 510 is further used to:

According to the logical channel or radio bearer or data flow used by each MAC entity in the plurality of MAC entities, the available resources of each MAC entity, the channel conditions that each MAC entity can handle, and each MAC At least one of the maximum amount of data that can be processed by the entity or the range of data amount determines the MAC entity used to send the data to be sent.

Optionally, in some embodiments, the determining unit 510 is specifically configured to:

According to the first correspondence, and the logical channel or radio bearer or data stream used by the data to be sent, determine the MAC entity used to send the data to be sent among the plurality of MAC entities, the first correspondence indicates the sending Correspondence between logical channels or radio bearers or data streams used by data and MAC entities.

Optionally, in some embodiments, in the first correspondence, each MAC entity corresponds to at least one logical channel or at least one radio bearer, and the determining unit 510 is specifically configured to:

Determine, according to the correspondence between each MAC entity and the at least one logical channel or the at least one radio bearer, and the logical channel or radio bearer used to send the data to be sent, determine to send among the multiple MAC entities The MAC entity used by the data to be sent.

Optionally, in some embodiments, the determining unit 510 is specifically configured to:

A MAC entity used to send the data to be sent is determined among the MAC entities of the multiple MAC entities that have available uplink resources.

Optionally, in some embodiments, the determining unit 510 is specifically configured to:

It is determined that the MAC entity with the most available uplink resources is the MAC entity used for sending the data to be sent.

Optionally, in some embodiments, the determining unit 510 is specifically configured to:

According to the data volume of the data to be sent and the correspondence between each MAC entity and the maximum data volume or the range of data volume that each MAC entity can handle, determine the sending location among multiple MAC entities Describe the MAC entity used for the data to be sent.

Optionally, in some embodiments, the determining unit 510 is specifically configured to:

According to the channel conditions of the logical channel used to send the data to be sent and the correspondence between each MAC entity and the channel conditions that each MAC entity can handle, determine the use of the data to be sent from multiple MAC entities MAC entity.

Optionally, in some embodiments, the sending end device is a terminal device or a network device.

Optionally, in some embodiments, if the sending device is a terminal device, the transceiver unit 520 is further configured to:

Receiving the first correspondence sent by the network device.

Optionally, in some embodiments, if the sending device is a terminal device, the transceiver unit 520 is further configured to:

Correspondence between each MAC entity sent by the network device and the maximum data volume that can be processed or the range of data volume that can be processed.

Optionally, in some embodiments, if the sending device is a terminal device, the transceiver unit 520 is further configured to:

Receive the correspondence between each MAC entity and channel condition sent by the network device.

Optionally, in some embodiments, if the sending device is a terminal device, the transceiver unit 520 is further configured to:

A random access process is initiated through the main MAC entity or any MAC entity among the multiple MAC entities.

Optionally, in some embodiments, the transceiver unit 520 is further used to:

Receiving configuration information of a network device, the configuration information instructing the sending end device to use a primary MAC entity or any MAC entity among the plurality of MAC entities to initiate a random access process.

Optionally, in some embodiments, the first protocol entity is a radio link control RLC entity or a packet data aggregation protocol PDCP entity.

Optionally, in some embodiments, the determining unit 510 is a data distribution module in the sending-end device, and the data distribution module is located in an upper layer entity of the multiple MAC entities.

Optionally, in some embodiments, the data distribution module is located in an RLC entity or a PDCP entity.

Optionally, in some embodiments, the determining unit 510 is a data distribution module in the sending-end device, and the data distribution module is located in a high-level protocol at the MAC layer.

Optionally, in some embodiments, the determining unit 510 is a data distribution module in the sending-end device, and the data distribution module is located in any MAC entity among the plurality of MAC entities.

Optionally, the sending end device 500 may be used to perform the corresponding operation performed by the sending end device in the method 300, and for the sake of brevity, details are not described herein again.

6 is a schematic block diagram of a sending end device 600 according to an embodiment of the present application. As shown in FIG. 6, the sending-end device 600 includes a determining unit 610 and a transceiver unit 620.

The determining unit 610 is configured to determine the MAC corresponding to the basic parameter set among multiple MAC entities according to the basic parameter set used by the data to be sent from the physical layer and the correspondence between the medium access control MAC entity and the basic parameter set entity;

The transceiver unit 620 is configured to send the data to be sent through the MAC entity corresponding to the basic parameter set.

Optionally, in some embodiments, the sending end device is a network device or a terminal device.

Optionally, in some embodiments, if the sending device is a terminal device, the transceiver unit 620 is further configured to:

Receiving the correspondence between the MAC entity and the basic parameter set sent by the network device.

Optionally, in some embodiments, if the sending device is a terminal device, the transceiver unit 620 is further configured to:

Receiving a physical downlink control channel PDCCH sent by a network device, where the PDCCH includes a basic parameter set of a first channel, and the data to be sent is sent through the first channel;

The determining unit 610 is also used to:

It is determined that the basic parameter set of the first channel is the basic parameter set used by the data to be sent.

Optionally, the sending end device 600 may be used to perform the corresponding operation performed by the sending end device in the method 400, and for the sake of brevity, details are not described herein again.

7 is a schematic block diagram of a sending end device 700 according to an embodiment of the present application. As shown in FIG. 7, the sending-end device 700 includes a processor 710 and a memory 720. The memory 720 may store program codes, and the processor 710 may execute the program codes stored in the memory 720.

Optionally, as shown in FIG. 7, the device 700 may include a transceiver 730, and the processor 710 may control the transceiver 730 to communicate externally.

Optionally, the processor 710 may call the program code stored in the memory 720 to perform the corresponding operation in the method 300 shown in FIG. 3, and for the sake of brevity, no further description is provided here.

Optionally, the processor 710 may call the program code stored in the memory 720 to perform the corresponding operation in the method 300 shown in FIG. 4, and for the sake of brevity, no further description is provided here.

Optionally, the sending end device 700 may be a terminal device or a system chip that can be placed in the terminal device; or, the sending end device 700 may be a network device or may be placed in the network device System chip.

It should be understood that in the embodiment of the present application, the processor 710 may be a central processing unit (Central Processing Unit, CPU), and the processor 710 may also be other general-purpose processors, digital signal processors (DSPs), and application-specific integrated circuits (ASIC), ready-made programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 720 may include a read-only memory and a random access memory, and provide instructions and data to the processor 710. A portion of the memory 720 may also include non-volatile random access memory. For example, the memory 720 may also store device type information.

In the implementation process, the steps of the above method may be completed by instructions in the form of hardware integrated logic circuits or software in the processor 710. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied and executed by a hardware processor, or may be executed and completed by a combination of hardware and software modules in the processor. The software module may be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, and registers. The storage medium is located in the memory, and the processor 710 reads the information in the memory and completes the steps of the above method in combination with its hardware. In order to avoid repetition, they are not described in detail here.

Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application of the technical solution and design constraints. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

Those of ordinary skill in the art can clearly understand that for the convenience and conciseness of the description, the specific working processes of the above-described systems, devices, and units can refer to the corresponding processes in the foregoing method embodiments, which are not repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or may Integration into another system, or some features can be ignored, or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application essentially or part of the contribution to the existing technology or part of the technical solution can be embodied in the form of a software product, the computer software product is stored in a storage medium, including several The instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. The foregoing storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes.

The above is only the specific implementation of this application, but the scope of protection of this application is not limited to this, any person with ordinary knowledge in the technical field can easily think of changes or replacements within the technical scope disclosed in this application. It should be covered by the scope of protection of this application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

It should be understood that the term “and/or” in this article is merely an association relationship describing the associated objects, and indicates that there may be three relationships, for example, A and/or B, which may indicate: A exists alone, and A and B exist simultaneously. There are three cases of B. In addition, the character "/" in this article generally indicates that the related objects are a "or" relationship.

It should be understood that in various embodiments of the present application, the size of the sequence numbers of the above processes does not mean that the execution order is sequential, and the execution order of each process should be determined by its function and inherent logic, and should not correspond to the embodiments of the present application. The implementation process constitutes no limitation.

Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application of the technical solution and design constraints. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

Those of ordinary skill in the art can clearly understand that for the convenience and conciseness of the description, the specific working processes of the above-described systems, devices, and units can refer to the corresponding processes in the foregoing method embodiments, which are not repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or may Integration into another system, or some features can be ignored, or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application essentially or part of the contribution to the existing technology or part of the technical solution can be embodied in the form of a software product, the computer software product is stored in a storage medium, including several The instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage media include: USB hard disks, mobile hard disks, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disks or optical discs, etc., which can store program codes. medium.

The above is only the specific implementation of this application, but the scope of protection of this application is not limited to this, any person with ordinary knowledge in the technical field can easily think of changes or replacements within the technical scope disclosed in this application. It should be covered by the scope of protection of this application. Therefore, the protection scope of the present application shall be subject to the protection scope of the patent application scope.

100‧‧‧Method 110‧‧‧Network equipment 120‧‧‧terminal equipment 301, 302, 401, 402‧‧‧ steps 500, 600, 700 ‧‧‧ equipment 510、610‧‧‧determination unit 520, 620‧‧‧ transceiver unit 710‧‧‧ processor 720‧‧‧Memory 730‧‧‧ transceiver

FIG. 1 is a schematic diagram of a wireless communication system according to an embodiment of the present application.

2 is a schematic diagram of an exemplary functional structure of a MAC entity.

FIG. 3 is a schematic flowchart of a data transmission method according to an embodiment of the present application.

4 is a schematic flowchart of a data transmission method according to an embodiment of the present application.

5 is a schematic block diagram of a transmitting end device according to an embodiment of the present application.

6 is a schematic block diagram of a sending end device according to another embodiment of the present application.

7 is a schematic block diagram of a transmitting end device according to yet another embodiment of the present application.

301, 302‧‧‧ steps

Claims (44)

A method for transmitting data, which includes: a sending-end device in multiple media access control MAC entities, according to a logical channel or radio bearer or data stream used by each of the multiple MAC entities, the The available resources of each MAC entity, the channel conditions that each MAC entity can handle, at least one of the maximum amount of data or the range of data amounts that each MAC entity can handle, determining the MAC entity to use for sending the data to be sent, The data to be sent comes from the first protocol entity above the MAC layer; and the data to be sent is sent by the MAC entity determined to send the data to be sent. The method according to item 1 of the patent application scope, wherein, according to the logical channel or radio bearer or data flow used by each MAC entity of the plurality of MAC entities, the available upstream resources of each MAC entity, The channel condition that each MAC entity can handle, at least one of the maximum amount of data or the amount of data range that each MAC entity can handle, determining the MAC entity to use for sending the data to be sent includes: according to the first Correspondence, and the logical channel or radio bearer or data stream used by the data to be sent, among the plurality of MAC entities, the MAC entity used to send the data to be sent is determined, and the first correspondence indicates the data used by the data to be sent. Correspondence between logical channels or radio bearers or data streams and MAC entities. The method according to item 2 of the patent application scope, wherein in the first correspondence, each MAC entity corresponds to at least one logical channel or at least one radio bearer, the first correspondence, and the data to be sent The logical channel or radio bearer or data stream used to determine the MAC entity to be used for sending the data to be sent among the multiple MAC entities includes: according to each MAC entity and the at least one logical channel or the The correspondence between at least one radio bearer and the logical channel or radio bearer used to send the data to be sent determine the MAC entity used to send the data to be sent among the plurality of MAC entities. The method according to item 1 of the patent application scope, wherein, according to the logical channel or radio bearer or data flow used by each MAC entity of the plurality of MAC entities, the available upstream resources of each MAC entity, The channel conditions that each MAC entity can handle, at least one of the maximum amount of data or the amount of data that each MAC entity can handle, and determining the MAC entity to use for sending the data to be sent includes: Among the MAC entities with available uplink resources of multiple MAC entities, the MAC entity used for sending the data to be sent is determined. The method according to item 4 of the patent application scope, wherein the determining, among the MAC entities with available uplink resources of the plurality of MAC entities, the MAC entity used for sending the data to be sent includes: determining available uplink resources The most MAC entities are the MAC entities used to send the data to be sent; or any MAC entity that determines that there is available uplink resource is the MAC entity used to send the data to be sent. The method according to item 1 of the patent application scope, wherein the available resources of each MAC entity are based on the logical channel or radio bearer or data flow used by each MAC entity of the plurality of MAC entities. The channel conditions that each MAC entity can handle, at least one of the maximum amount of data or the amount of data range that each MAC entity can handle, determining the MAC entity to use for sending the data to be sent includes: according to the The amount of data sent, and the correspondence between each MAC entity and the maximum amount of data that each MAC entity can handle or the range of data that can be processed, and determining to send the data to be sent among multiple MAC entities The MAC entity used. The method according to item 1 of the patent application scope, wherein the available resources of each MAC entity are based on the logical channel or radio bearer or data flow used by each MAC entity of the plurality of MAC entities. Describe the channel conditions that each MAC entity can handle, at least one of the maximum amount of data or the amount of data range that each MAC entity can handle, and determining the MAC entity to use for sending the data to be sent includes: The channel conditions of the logical channel used by the data to be sent, and the correspondence between each MAC entity and the channel conditions that each MAC entity can handle, determine the MAC entity used to send the data to be sent among multiple MAC entities. According to the method described in item 1 of the patent application scope, the sending-end device is a terminal device or a network device. The method according to item 2 of the patent application scope, wherein, if the sending-end device is a terminal device, the method further includes: the sending-end device receives the first correspondence sent by a network device. The method according to item 6 of the patent application scope, wherein, if the sending end device is a terminal device, the method further comprises: the sending end device receiving each MAC entity sent by the network device and capable of processing most Correspondence between large amounts of data or ranges of data that can be processed. The method according to item 7 of the patent application scope, wherein, if the sending-end device is a terminal device, the method further includes: the sending-end device receiving each MAC entity and channel condition sent by the network device Correspondence. The method according to item 1 of the patent application scope, wherein, if the sending-end device is a terminal device, the method further includes: the sending-end device passes the primary MAC entity or any of the multiple MAC entities The MAC entity initiates the random access process. The method according to item 12 of the patent application scope, wherein the method further comprises: the sending end device receives configuration information of a network device, and the configuration information instructs the sending end device to use the plurality of MAC entities The primary MAC entity or any MAC entity initiates the random access process. The method according to item 1 of the patent application scope, wherein the first protocol entity is a radio link control RLC entity or a packet data aggregation protocol PDCP entity. The method according to item 1 of the patent application scope, wherein the method is performed by a data distribution module in the sending-end device, and the data distribution module is located in an upper layer entity of the plurality of MAC entities. The method according to item 15 of the patent application scope, wherein the data distribution module is located in an RLC entity or a PDCP entity. The method according to item 1 of the patent application scope, wherein the method is performed by a data distribution module in the sending-end device, and the data distribution module is located in a high-level protocol at the MAC layer. The method according to item 1 of the patent application scope, wherein the method is performed by a data distribution module in the sending-end device, and the data distribution module is located in any MAC entity of the plurality of MAC entities. A method for transmitting data, which includes: the sending-end device uses the basic parameter set used by the data to be sent from the physical layer, and the correspondence between the medium access control MAC entity and the basic parameter set to determine the number of MAC entities The MAC entity corresponding to the basic parameter set used by the data to be sent; and sending the data to be transmitted through the determined MAC entity corresponding to the basic parameter set. The method according to item 19 of the patent application scope, wherein the sending device is a network device or a terminal device. The method according to item 19 of the patent application scope, wherein, if the sending end device is a terminal device, the method further comprises: the sending end device receiving the correspondence between the MAC entity and the basic parameter set sent by the network device relationship. The method according to item 19 of the patent application scope, wherein, if the sending end device is a terminal device, the method further includes: the sending end device receives a physical downlink control channel PDCCH sent by a network device, and the PDCCH includes A basic parameter set of the first channel, the data to be sent is sent through the first channel; it is determined that the basic parameter set of the first channel is the basic parameter set used by the data to be sent. A sending-end device, comprising: a determining unit for, among a plurality of MAC entities, according to a logical channel or radio bearer or data flow used by each of the plurality of MAC entities, each of the MAC entities Available resources, at least one of the channel conditions that each MAC entity can handle, the maximum amount of data or the range of data amounts that each MAC entity can handle, determine the MAC entity to use for sending the data to be sent, the The sending data comes from the first protocol entity above the MAC layer of the medium access control; and a transceiver unit, configured to send the data to be sent through the determined MAC entity used to send the data to be sent. The sending end device according to item 23 of the patent application scope, wherein the determining unit is specifically configured to: according to the first correspondence, and the logical channel or radio bearer or data stream used by the data to be sent, in the multiple Among the MAC entities, the MAC entity used to send the data to be sent is determined, and the first correspondence indicates the correspondence between the logical channel or radio bearer or data stream used to send the data and the MAC entity. The sender device according to item 24 of the patent application scope, wherein in the first correspondence, each MAC entity corresponds to at least one logical channel or at least one radio bearer, and the determining unit is specifically configured to: according to the The correspondence between each MAC entity and the at least one logical channel or the at least one radio bearer, and the logical channel or radio bearer used to send the data to be sent, in the Among multiple MAC entities, a MAC entity used for sending the data to be sent is determined. The sender device according to item 23 of the patent application scope, wherein the determining unit is specifically configured to: determine the MAC used for sending the data to be sent among the MAC entities of the multiple MAC entities that have available uplink resources entity. The sending device according to item 26 of the patent application scope, wherein the determining unit is specifically configured to: determine that the MAC entity with the most available uplink resources is the MAC entity used to send the data to be sent; or determine that there are available uplink resources Any of the MAC entities is the MAC entity used to send the data to be sent. The sender device according to item 23 of the patent application scope, wherein the determining unit is specifically configured to: according to the data volume of the data to be sent, and each MAC entity and each MAC entity can process The corresponding relationship between the maximum data volume or the range of data volume that can be processed determines the MAC entity used to send the data to be transmitted among multiple MAC entities. The sending end device according to item 23 of the patent application scope, wherein the determining unit is specifically configured to: according to the channel condition of the logical channel used for sending the data to be sent, and each MAC entity and each MAC Correspondence of the channel conditions that the entity can handle determines the MAC entity used to send the data to be sent among multiple MAC entities. According to the transmitter device described in item 23 of the patent application scope, the transmitter device is a terminal device or a network device. The sender device according to item 24 of the patent application scope, wherein, if the sender device is a terminal device, the transceiver unit is further configured to: receive the first correspondence sent by a network device. The transmitter device according to item 28 of the patent application scope, wherein, if the transmitter device is a terminal device, the transceiver unit is further configured to: receive each MAC entity sent by the network device and the maximum Correspondence between the amount of data or the range of data that can be processed. The sender device according to item 29 of the patent application scope, wherein, if the The sending-end device is a terminal device, and the transceiving unit is further configured to receive the correspondence between each MAC entity and channel condition sent by the network device. The transmitter device according to item 23 of the patent application scope, wherein, if the transmitter device is a terminal device, the transceiver unit is further used to: through the master MAC entity or any MAC among the plurality of MAC entities The entity initiates the random access process. The transmitter device according to item 34 of the patent application scope, wherein the transceiver unit is further configured to receive configuration information of a network device, and the configuration information instructs the transmitter device to use the multiple MAC entities. The main MAC entity or any MAC entity initiates the random access process. The sender device according to item 23 of the patent application scope, wherein the first protocol entity is a radio link control RLC entity or a packet data aggregation protocol PDCP entity. The sender device according to item 23 of the patent application scope, wherein the determination unit is a data distribution module in the sender device, and the data distribution module is located in an upper layer entity of the plurality of MAC entities. The sender device according to item 37 of the patent application scope, wherein the data distribution module is located in an RLC entity or a PDCP entity. The sender device according to item 23 of the patent application scope, wherein the determination unit is a data distribution module in the sender device, and the data distribution module is located in a high-level protocol at the MAC layer. The sender device according to item 23 of the patent application scope, wherein the determination unit is a data distribution module in the sender device, and the data distribution module is located in any MAC entity of the plurality of MAC entities in. A sending-end device, comprising: a determining unit for determining among multiple MAC entities based on the corresponding relationship between the basic parameter set used by the data to be transmitted from the physical layer and the medium access control MAC entity and the basic parameter set A MAC entity corresponding to the basic parameter set used by the data to be sent; and a transceiver unit configured to send the data to be transmitted through the determined MAC entity corresponding to the basic parameter set. The sender device according to item 41 of the patent application scope, wherein the sender device is a network device or a terminal device. The transmitter device according to item 41 of the patent application scope, wherein, if the transmitter device is a terminal device, the transceiver unit is further configured to: receive the correspondence between the MAC entity and the basic parameter set sent by the network device . The transmitter device according to item 41 of the patent application scope, wherein, if the transmitter device is a terminal device, the transceiver unit is further configured to: receive a physical downlink control channel PDCCH sent by a network device, and the PDCCH includes the A basic parameter set of a channel, the data to be sent is sent through the first channel; the determining unit is further configured to determine that the basic parameter set of the first channel is a basic parameter used by the data to be sent set.

Images