CN111432432B

CN111432432B - Data transmission method and device

Info

Publication number: CN111432432B
Application number: CN201910022428.9A
Authority: CN
Inventors: 李小仙
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-01-10
Filing date: 2019-01-10
Publication date: 2022-04-22
Anticipated expiration: 2039-01-10
Also published as: WO2020143383A1; CN111432432A

Abstract

An embodiment of the application provides a data transmission method and device, and the method comprises the following steps: acquiring uplink resources when a first logic channel triggers a pending scheduling request pending SR, wherein the first logic channel is a logic channel which is not matched with any scheduling request configuration; sending the cache state information of the first logic channel on the uplink resource; and then canceling the pending SR triggered on the first logic channel, so that the buffer state information of the first logic channel can be sent through the Physical Uplink Shared Channel (PUSCH) resource indicated by the uplink authorization acquired in a non-random access mode, the random access of the terminal equipment is avoided, and the service continuity on the logic channel is improved.

Description

Data transmission method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a data transmission method and device.

Background

With the rapid development of wireless communication technology, the fifth Generation (5th Generation, 5G) wireless communication technology has been a hot spot in the industry. The 5G wireless communication technology is an extension of the fourth Generation (4th Generation, 4G) wireless communication technology. Therefore, the 5G communication system is called a "super 4G network", or a "Long Term Evolution (LTE) system", or a New Radio (NR).

In the data transmission process, the network device may configure a plurality of Logical channels (Logical channels) for the terminal device, and when there is data to be transmitted on a certain Logical Channel and the terminal device does not have available Physical Uplink Shared Channel (PUSCH) resources, the network device may be triggered to send an SR message on a Physical Uplink Control Channel (PUCCH) resource indicated by Scheduling Request (SR) configuration matched with the Logical Channel. According to the specification of 3GPP TS 38.321, one logical channel may be matched to 0 or 1 SR configuration, i.e. one logical channel may not have a corresponding SR configuration. Therefore, when there is data to be transmitted on the logical channel and the terminal device has no available PUSCH resource, the terminal device needs to trigger random access to a special cell (scell) to request the resource. If no Physical Random Access Channel (PRACH) PRACH resource is configured on the currently activated Active UL Bandwidth Part (BWP), the terminal device will switch to the Initial Uplink BWP for Random Access, and will switch the Active Downlink (Downlink DL) BWP to the Initial Downlink BWP, causing the DL BWP on the terminal device side to change; if the PRACH resource is configured on the current Active UL BWP, the terminal device will switch the Active DL BWP to a DL BWP with the same ID as the Active UL BWP ID, and in a Frequency Division Duplex (FDD) system, the Active DL BWP ID is not necessarily the same as the Active UL BWP ID, which may cause the Active DL BWP of the terminal device to change.

Therefore, if the terminal device switches the current Active DL BWP after sending the random access Preamble, when a service corresponding to a certain logical channel generates downlink data, the network device will continue to send the downlink data on the Active DL BWP before the terminal device switches, and at this time, because the Active DL BWP of the terminal device has been changed, the terminal device cannot receive the downlink data, thereby causing the traffic jam or interruption on the logical channel.

Disclosure of Invention

The application provides a data transmission method and equipment, which improve the continuity of services on a logic channel in the data transmission process.

In a first aspect, an embodiment of the present application provides a data transmission method, where the method may include:

acquiring uplink resources when a first logic channel triggers a pending scheduling request pending SR, wherein the first logic channel is a logic channel which is not matched with any scheduling request configuration;

sending the cache state information of the first logic channel on the uplink resource;

the pending SR triggered on the first logical channel is cancelled.

Therefore, in this possible implementation manner, when the first logical channel triggers the pending scheduling request pending SR, the terminal device may obtain the uplink resource, and after obtaining the uplink resource, send the buffer status information of the first logical channel on the uplink resource, and after confirming that the network device has received the buffer status information of the first logical channel, cancel the pending SR triggered on the first logical channel, so that the buffer status information of the first logical channel is sent by the physical uplink shared channel PUSCH resource indicated by the uplink grant obtained in the non-random access manner, thereby avoiding the random access of the terminal device, and improving the continuity of the service on the logical channel.

In one possible implementation, canceling the pending SR triggered on the first logical channel may include:

confirming that the network equipment has received the cache state information of the first logic channel;

the pending SR triggered on the first logical channel is cancelled.

In a possible implementation manner, acquiring the uplink resource may include:

sending a scheduling request to the network equipment on a Physical Uplink Control Channel (PUCCH) resource corresponding to the scheduling request configuration matched with the second logical channel;

and receiving an uplink authorization sent by the network equipment, wherein the Physical Uplink Shared Channel (PUSCH) resource indicated by the uplink authorization is an uplink resource, so that the uplink resource is obtained.

In a possible implementation manner, before sending the scheduling request to the network device on the physical uplink control channel PUCCH resource corresponding to the scheduling request configuration matched with the second logical channel, the method may further include:

determining that the second logical channel has triggered the pending SR.

In a possible implementation manner, acquiring the uplink resource may include:

receiving a configuration authorization Configured Grant of a configuration authorization type 1 and/or a configuration authorization type 2 sent by a network device; and configuring the Physical Uplink Shared Channel (PUSCH) resource indicated by the authorization as an uplink resource so as to acquire the uplink resource.

In a second aspect, an embodiment of the present application further provides a data transmission method, where the method may include:

when a first logic channel triggers a pending scheduling request pending SR, acquiring a time-frequency resource and a random access lead code for random access, wherein the first logic channel is a logic channel which is not matched with any scheduling request configuration;

sending a random access lead code on time-frequency resources;

determining whether to switch to a downlink bandwidth part DL BWP where the random access response message is located;

if the switching is determined, switching to the DL BWP of the downlink bandwidth part where the random access response message is in the random access response window;

receiving a random access response message corresponding to the random access preamble on the downlink bandwidth part DL BWP;

and sending the cache state information of the first logic channel according to the receiving result, and optimizing the Random Access (RA) process of the terminal equipment, so that the negative influence of RA on the terminal equipment is reduced, and the service continuity on the logic channel is improved.

In one possible implementation, the method may further include:

if at least one of the following conditions is satisfied, determining not to switch to the downlink bandwidth part DL BWP where the random access response message is located;

uplink transmission data exist in the random access response window;

downlink receiving data exists in the random access response window;

there is downlink received data in the original downlink bandwidth portion before the random access response window.

In a possible implementation manner, sending the buffer status information of the first logical channel according to the receiving result may include:

if the random access response message is received on the downlink bandwidth part DL BWP, sending a random access third message on the uplink resource indicated by the uplink authorization carried in the random access response message; and the random access third message carries the cache state information of the first logic channel.

In one possible implementation, the method may further include:

the pending SR triggered on the first logical channel is cancelled.

if the random access Response message is not received on the DL BWP, switching back to the original DL BWP after the time Window indicated by the ra-Response Window is ended, and acquiring uplink resources;

and sending the buffer state information of the first logical channel on the uplink resource.

In a possible implementation manner, acquiring the uplink resource may include:

and receiving an uplink authorization sent by the network equipment, wherein the Physical Uplink Shared Channel (PUSCH) resource indicated by the uplink authorization is an uplink resource.

determining that the second logical channel has triggered the pending SR.

In a possible implementation manner, acquiring the uplink resource may include:

receiving a configuration authorization Configured Grant of a configuration authorization type 1 and/or a configuration authorization type 2 sent by a network device; and configuring the Physical Uplink Shared Channel (PUSCH) resource indicated by the authorization as an uplink resource.

In one possible implementation manner, acquiring the time-frequency resource and the random access preamble for performing the random access may include:

receiving random access parameter information sent by network equipment; wherein, the random access parameter information may include: at least one of random access parameter information of the initial uplink bandwidth part, random access parameter information of the activated uplink bandwidth part, or random access parameter information of free contention;

and determining the time-frequency resource and the random access lead code of the random access according to the random access parameter information.

In a third aspect, an embodiment of the present application further provides a communication device, where the communication device may include:

the system comprises a processing unit and a scheduling request scheduling unit, wherein the processing unit is used for acquiring uplink resources when a first logic channel triggers a pending scheduling request (pending SR), and the first logic channel is a logic channel which is not matched with any scheduling request configuration;

a sending unit, configured to send the buffer status information of the first logical channel on the uplink resource;

and the processing unit is further used for canceling the pending SR triggered on the first logical channel.

In a possible implementation manner, the processing unit is specifically configured to confirm that the network device has received the cache state information of the first logical channel; and cancels the pending SR triggered on the first logical channel.

In one possible implementation, the apparatus may further include a receiving unit;

the sending unit is further configured to send a scheduling request to the network device on a Physical Uplink Control Channel (PUCCH) resource corresponding to the scheduling request configuration matched with the second logical channel;

and the receiving unit is used for receiving the uplink authorization sent by the network equipment, and the Physical Uplink Shared Channel (PUSCH) resource indicated by the uplink authorization is the uplink resource.

In a possible implementation manner, the processing unit is further configured to determine that the second logical channel has triggered the pending SR.

In a possible implementation manner, the receiving unit is further Configured to receive a configuration authorization Configured Grant of a configuration authorization type 1 and/or a configuration authorization type 2 sent by the network device; and configuring the Physical Uplink Shared Channel (PUSCH) resource indicated by the authorization as an uplink resource.

In a fourth aspect, an embodiment of the present application further provides a communication device, where the device may include:

the system comprises a processing unit and a processing unit, wherein the processing unit is used for acquiring time-frequency resources and a random access lead code for random access when a first logic channel triggers a pending scheduling request pending SR, and the first logic channel is a logic channel which is not matched with any scheduling request configuration;

a sending unit, configured to send a random access preamble on a time-frequency resource;

the processing unit is further configured to determine whether to switch to a downlink bandwidth part DL BWP where the random access response message is located; if the switching is determined, switching to the DL BWP of the downlink bandwidth part where the random access response message is in the random access response window;

a receiving unit, configured to receive a random access response message corresponding to the random access preamble on the downlink bandwidth part DL BWP;

and the sending unit is further used for sending the buffer state information of the first logic channel according to the receiving result.

In a possible implementation manner, the processing unit is further configured to determine not to switch to the downlink bandwidth portion DL BWP in which the random access response message is located if it is determined that at least one of the following conditions is met;

uplink transmission data exist in the random access response window;

downlink receiving data exists in the random access response window;

In a possible implementation manner, the sending unit is specifically configured to send a random access third message in an uplink resource indicated by an uplink grant carried in the random access response message if the random access response message is received on the downlink bandwidth part DL BWP; and the random access third message carries the cache state information of the first logic channel.

In a possible implementation manner, the processing unit is further configured to cancel a pending SR triggered on the first logical channel.

In a possible implementation manner, the processing unit is further configured to, if the random access Response message is not received on the downlink bandwidth part DL BWP, switch back to the original downlink bandwidth part DL BWP after the time Window indicated by the random access Response Window ra-Response Window ends, and acquire the uplink resource;

a sending unit, configured to send the buffer status information of the first logical channel on the uplink resource.

In a possible implementation manner, the sending unit is specifically configured to send the scheduling request to the network device on a physical uplink control channel PUCCH resource corresponding to the scheduling request configuration matched with the second logical channel;

and the receiving unit is further configured to receive an uplink grant sent by the network device, where the physical uplink shared channel PUSCH resource indicated by the uplink grant is an uplink resource.

In a possible implementation manner, the receiving unit is further configured to receive random access parameter information sent by the network device; wherein, the random access parameter information may include: at least one of random access parameter information of the initial uplink bandwidth part, random access parameter information of the activated uplink bandwidth part, or random access parameter information of free contention;

and the processing unit is specifically used for determining the time-frequency resource and the random access lead code of the random access according to the random access parameter information.

In a fifth aspect, embodiments of the present application further provide a communication device, which may include a processor and a memory, wherein,

the memory is used for storing program instructions;

the processor is configured to read the program instructions in the memory, and execute the data transmission method according to any one of the first aspect or execute the data transmission method according to any one of the second aspect according to the program instructions in the memory.

In a sixth aspect, embodiments of the present application further provide a computer storage medium, which may include instructions that, when executed by one or more processors, cause a communication apparatus to perform the data transmission method of any one of the above first aspects, or the data transmission method of any one of the above first aspects.

In a seventh aspect, an embodiment of the present application further provides a chip, where a computer program is stored on the chip, and when the computer program is executed by a processor, the data transmission method shown in any of the first aspect is executed; alternatively, the data transmission method according to any of the second aspects is performed.

According to the data transmission method and device provided by the embodiment of the application, when the first logical channel triggers the pending scheduling request pending SR, the terminal device can acquire the uplink resource, and after acquiring the uplink resource, send the buffer status information of the first logical channel on the uplink resource, and after confirming that the network device has received the buffer status information of the first logical channel, cancel the pending SR triggered on the first logical channel, so that the buffer status information of the first logical channel is sent through the physical uplink shared channel PUSCH resource indicated by the uplink authorization acquired in a non-random access manner, thereby avoiding the random access of the terminal device, and improving the continuity of services on the logical channel.

Drawings

Fig. 1 is a schematic diagram of a system architecture according to an embodiment of the present application;

fig. 2 is a schematic diagram of a data transmission method according to an embodiment of the present application;

fig. 3 is a schematic diagram of another data transmission method according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of another communication device provided in an embodiment of the present application;

fig. 6 is a schematic structural diagram of another communication device provided in an embodiment of the present application;

fig. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

It should be understood that the technical solution of the embodiment of the present application may be applied to a New Radio (NR) System or a Long Term Evolution (LTE) architecture, and may also be applied to a Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UMTS) architecture or a Global System for Mobile communications (GSM)/Enhanced Data Rate GSM Evolution (Enhanced Data Rate for GSM Evolution, EDGE) Radio Access Network (GERAN) architecture of an EDGE System. In the UTRAN architecture or/GERAN architecture, the function of MME is completed by Serving GPRS Support Node (SGSN), and the function of SGW/PGW is completed by Gateway GPRS Support Node (GGSN). The technical solution of the embodiment of the present application may also be applied to other communication systems, for example, a Public Land Mobile Network (PLMN) system, and even a future 5G communication system or a communication system after 5G, and the like, which is not limited in the embodiment of the present application.

The embodiment of the application relates to terminal equipment. The terminal device, also called a terminal, may be a device that includes a wireless transceiving function and can cooperate with a network device to provide a communication service for a user. In particular, a terminal may refer to a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, or a User Equipment. For example, the 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), a handheld device with a Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, a terminal in a future 5G network or a network after 5G, and the like, which is not limited in this embodiment of the present application.

The embodiment of the application also relates to network equipment. The Network device may be a device for communicating with the terminal device, and for example, the Network device may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a Base Station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB, or eNodeB) in an LTE system, or a relay Station, an access point, a vehicle-mounted device, a wearable device, and a Network-side device in a future 5G Network or a Network after 5G or a Network device in a future evolved Public Land Mobile Network (PLMN), and the like.

The Network device related in the embodiment of the present application may also be referred to as a Radio Access Network (RAN) device. The RAN equipment is connected with the terminal and used for receiving data of the terminal and sending the data to the core network equipment. RAN devices correspond to different devices in different communication systems, for example, a base station and a base station Controller in a 2G system, a base station and a Radio Network Controller (RNC) in a 3G system, an evolved Node B (eNB) in a 4G system, and an Access Network device (e.g., gbb, CU, DU) in a 5G system, such as a New Radio Access Technology (NR).

Fig. 1 is a schematic diagram of a system architecture provided in this embodiment, a wireless communication system shown in the system architecture may include a core network and an access network, and taking a 5G communication system as an example, the core network may be NGC/5GC or EPC, and the access network may be 5G NR or E-UTRAN, and for convenience of description, in this embodiment, the core network and the access network are collectively referred to as a core network and an access network. In the access network, the access network may include a network device and at least one terminal device, where the terminal device may be directly connected to the network device, such as terminal device 1 shown in fig. 1, the access network may further include a Relay device and a terminal device connected to the Relay device, such as terminal device 2 shown in fig. 1, and the Relay device may be a Relay device or a Customer Premises Equipment (CPE). The relay device establishes connection with the network device through the link 2, and relative to the network device, the relay device can also be regarded as a terminal device; the relay device establishes a connection with the user equipment 2 via the link 3, and the relay device may also be regarded as a network device with respect to the terminal device. The network device can perform data interaction with the terminal device. In the downlink data transmission process, after the terminal device sends the random access Preamble, when a service corresponding to a certain logical channel generates downlink data, the network device will continue to send the downlink data on the Active DL BWP before the terminal device switches, and at this time, since the Active DL BWP of the terminal device has been changed, the terminal device cannot receive the downlink data, thereby causing service interruption on the logical channel.

In order to improve the continuity of services on logical channels, an embodiment of the present application provides a data transmission method, which may improve the continuity of services on logical channels through at least two possible implementation manners, and in one possible implementation manner, if a first logical channel that is not matched to any Scheduling Request configuration triggers a pending SR, the first logical channel may send the buffer status information of the first logical channel through a physical uplink shared channel PUSCH resource indicated by other uplink grants without initiating Random Access (RA), and cancel the pending Request (SR) of the first logical channel, so as to avoid a terminal device performing Random Access, thereby improving the continuity of services on logical channels. In another possible implementation manner, if a first logical channel that is not matched to any scheduling request configuration triggers a pending SR and the first logical channel has initiated a random access RA, at this time, the terminal device may determine whether to switch to a downlink bandwidth portion DL BWP where the random access response message is located; if the switching is determined, switching to the downlink bandwidth part DL BWP where the random access response message is located in the random access response window, receiving the random access response message corresponding to the random access preamble on the downlink bandwidth part DL BWP, and sending the cache state information of the first logical channel according to the receiving result, thereby optimizing the RA process of the terminal device, so as to minimize the negative influence of the RA process, and thereby improving the service continuity on the logical channel. In the following, these two possible implementations will be described in detail by specific embodiments.

In a possible implementation manner, for example, please refer to fig. 2, where fig. 2 is a schematic diagram of a data transmission method provided in an embodiment of the present application, and the data transmission method may include:

s201, when the first logic channel triggers a pending scheduling request pending SR, the terminal equipment acquires uplink resources.

Wherein the first logical channel is a logical channel that is not matched to any scheduling request configuration.

It can be understood that, in the embodiment of the present application, when the first logical channel triggers the pending SR, the time when the first logical channel triggers the pending SR cannot be understood restrictively, but the time when the first logical channel triggers the pending SR and a time period after the first logical channel triggers the pending SR can be understood widely, as to how long the time period is, the time period may be set according to actual needs, and here, as to the duration of the time period, the embodiment of the present application is not limited specifically.

When it is determined that the first logical CHannel triggers the pending SR, in order to avoid performing random access on the first logical CHannel, the buffer status information of the first logical CHannel needs to be sent through a Physical Uplink Shared CHannel (PUSCH) resource indicated by another Uplink grant, so that the Uplink resource needs to be acquired first to send the buffer status information of the first logical CHannel. Optionally, when acquiring the uplink resource, the uplink resource may be acquired by the following manner 1 and manner 2.

In the method 1, a scheduling request may be sent to a network device on a physical uplink control channel PUCCH resource corresponding to the scheduling request configuration matched with the second logical channel; and receiving an uplink authorization sent by the network equipment, wherein the Physical Uplink Shared Channel (PUSCH) resource indicated by the uplink authorization is an uplink resource, so that the uplink resource is obtained.

It should be noted that, in the method 1, before the scheduling request is sent to the network device on the physical uplink control channel PUCCH resource corresponding to the scheduling request configuration matched with the second logical channel, it needs to determine whether the second logical channel has triggered the pending SR, and if the second logical channel has triggered the pending SR, the terminal device may obtain the UL Grant through the SR sent by the second logical channel; of course, the terminal device may also send the SR corresponding to the first logical channel through SR configuration corresponding to other logical channels.

Mode 2, a configuration authorized configurable grant of configuration authorized Type 1(configured grant Type 1) and/or configuration authorized Type 2(configured grant Type 2) sent by the network device may be received; and configuring the Physical Uplink Shared Channel (PUSCH) resource indicated by the authorization as an uplink resource.

In detail, in the method 2, when acquiring the uplink resource, only the configuration grant of the configuration grant type 1 sent by the network device may be received, where the physical uplink shared channel PUSCH resource indicated by the configuration grant of the configuration grant type 1 is the uplink resource; or only receiving an uplink grant of configuration grant type 2 sent by the network device, where the PUSCH resource of the configuration grant indication of configuration grant type 2 is an uplink resource; of course, the configuration authorization of the configuration authorization type 1 and the configuration authorization type 2 sent by the network device may also be received; and the Physical Uplink Shared Channel (PUSCH) resource indicated by the configuration authorization is an uplink resource, so that the uplink resource is acquired. For example, the configuration Grant may be a semi-persistent scheduling Grant SPS Grant or a Grant-free UL Grant.

In the embodiment of the present application, when acquiring uplink resources, the above-described embodiments 1 and 2 are merely used as examples to acquire uplink resources, but the embodiment of the present application is not limited thereto.

After acquiring the uplink resource through S201, the buffer status information of the first logical channel may be sent on the uplink resource, that is, the following S202 is executed:

s202, sending the buffer state information of the first logic channel on the uplink resource.

The buffer status information on the first logical channel may include uplink data amount information on the first logical channel, where the uplink data amount information is determined according to the uplink data amount on the first logical channel, and when determining the uplink data amount information on the first logical channel according to the uplink data amount on the first logical channel, the determining method may refer to the related description in 3GPP TS 38.321. When the terminal device calculates the uplink data amount on the first logical channel, the calculation method may refer to the relevant descriptions in 3GPP TS 38.322 and 3GPP TS 38.323, and herein, the embodiments of the present application are not described again. Or, the buffer status information on the first Logical Channel may also be uplink data amount information of a Logical Channel Group (LCG) where the first Logical Channel is located, where the uplink data amount information is determined according to an uplink data amount of the LCG where the first Logical Channel is located, and when determining the uplink data amount information of the LCG where the first Logical Channel is located according to the uplink data amount of the LCG where the first Logical Channel is located, the determination method may refer to relevant description in 3GPP TS 38.321. When the terminal device calculates the uplink data amount of the LCG, the calculation method may refer to the relevant description in 3GPP TS 38.322 and 3GPP TS 38.323, and herein, the embodiments of the present application are not described again.

It should be noted that, in this embodiment of the present application, when the terminal device sends the Buffer Status information of the first logical channel on the uplink resource, a Buffer Status Report (BSR) may be sent on the uplink resource, and the BSR may carry the Buffer Status information of the first logical channel. The BSR sent by the terminal device may be any one of MAC CEs in Short BSR, Long BSR, Short routed BSR, and Long routed BSR formats, and the BSR format is not further limited in the embodiments of the present application.

S203, the terminal device confirms that the network device has received the buffer status information of the first logical channel.

It should be noted that, when determining that the network device has received the cache state information of the first logical channel, the terminal device may determine in at least two ways, where the way 1 indicates that the network device has received the cache state information of the first logical channel if the terminal device does not receive the retransmission indication information of the network device. In the method 2, if the terminal device receives the acknowledgement message sent by the network device, it indicates that the network device has received the buffer status information of the first logical channel. For example, the Acknowledgement message may be a hybrid automatic repeat request Acknowledgement (HARQ ACK) message.

After confirming that the network device has received the buffer status information of the first logical channel, the terminal device may perform the following S204:

s204, the terminal equipment cancels the pending SR triggered on the first logic channel.

After the network device is confirmed to have received the cache state information of the first logical channel, the Pending SR triggered by the first logical channel can be cancelled, so that the Pending SR is prevented from triggering the terminal device to initiate random access, and downlink data transmission of other logical channels is prevented from being affected.

The embodiment shown in fig. 2 describes in detail that, in a possible implementation manner, if a first logical channel that is not matched to any scheduling request configuration triggers a pending SR, the buffering state information of the first logical channel is sent through a physical uplink shared channel PUSCH resource indicated by other uplink grants, and then the pending SR of the first logical channel is cancelled, so that the terminal device is prevented from performing random access, and thus the continuity of a service on the logical channel is improved. In the following, a technical solution of how to improve the continuity of the service on the logical channel in another possible implementation manner will be described in detail, for example, please refer to fig. 3, where fig. 3 is a schematic diagram of another data transmission method provided in this embodiment, and the data transmission method may include:

s301, when a first logic channel triggers a pending scheduling request pending SR, a terminal device acquires a time-frequency resource and a random access preamble for random access.

It can also be understood that, in the embodiment of the present application, when the first logical channel triggers the pending SR, the time when the first logical channel triggers the pending SR cannot be understood in a limited manner, but may be widely understood as both the time when the first logical channel triggers the pending SR and a time period of the pending SR after the first logical channel triggers, as to how long the time period is specifically set according to actual needs, where, as to the duration of the time period, the embodiment of the present application is not limited in particular.

Optionally, when obtaining the time-frequency resource and the random access preamble for performing the random access, the terminal device may receive the random access parameter information sent by the network device, and determine the time-frequency resource and the random access preamble for the random access according to the random access parameter information. The Random Access parameter information includes time-frequency resource information used for indicating Random Access and indication information used for indicating a Random Access preamble, where the time-frequency resource information of Random Access may be time-frequency resource information of a Physical Random Access Channel (PRACH), and the time-frequency resource information of the PRACH may include one or more of information of a PRACH format, a cycle, a frame number in the cycle, a subframe number, a starting symbol, a PRACH time slot, a PRACH transmission opportunity in the time slot, and a selection of Normal Uplink (NUL) or Supplementary Uplink (SUL) for transmission; the indication information for indicating the random access preamble code may include information of a root sequence pull, a selection set, etc. for generating the random access preamble sequence.

Optionally, the random access parameter information includes: at least one of the random access parameter information of the initial uplink bandwidth part, the random access parameter information of the activated uplink bandwidth part, or the free-contention random access parameter information, i.e., the random access parameter information may only include any one of the random access parameter information of the initial uplink bandwidth part, the random access parameter information of the activated uplink bandwidth part, or the free-contention random access parameter information, or may include any two of the random access parameter information of the initial uplink bandwidth part, the random access parameter information of the activated uplink bandwidth part, or the free-contention random access parameter information, or of course, the random access parameter information of the initial uplink bandwidth part, the random access parameter information of the activated uplink bandwidth part, or the free-contention random access parameter information of the activated uplink bandwidth part, And three random access parameter information of the competitive random access parameter information. Here, the embodiment of the present application only includes the following random access parameter information: at least one of the random access parameter information of the initial uplink bandwidth part, the random access parameter information of the activated uplink bandwidth part, or the random access parameter information of the free contention is described as an example, but the embodiment of the present application is not limited thereto.

Further, when the random access parameter information includes random access parameter information of the Initial Uplink bandwidth part, the terminal device will subsequently transmit the random access preamble on the PRACH time-frequency resource on the Initial Uplink bandwidth part Active Uplink BWP, and specifically, when the terminal device is not configured with a random access resource on the currently activated Uplink bandwidth part Active UL BWP, the terminal device may perform random access on the Initial Uplink BWP. When the random access parameter information includes random access parameter information that activates an uplink bandwidth part, the terminal device subsequently sends the random access preamble on a PRACH time-Frequency resource on the Actvie UL BWP, and specifically, when the terminal device is in a Frequency Division Duplex (FDD) system, the terminal device may perform random access on the current Active UL BWP when the terminal device configures a random access resource on the current Active UL BWP. When the random access parameter information includes the random access parameter information of free Contention and the terminal device needs to perform random access on the Initial Uplink BWP or Active UL BWP, only the random access resource information of the context-free configured on the BWP is used for performing random access.

It should be noted that, in this embodiment of the present application, when the terminal device receives the random access parameter information sent by the network device, the random access parameter information may be carried in system information, a Radio Resource Control (RRC) configuration message, or a system information change indication message. Of course, the embodiment of the present application is described only by taking as an example that the random access parameter information may be carried in system information, a radio resource control RRC configuration message, or a system information change indication message, but the embodiment of the present application is not limited thereto. Next, how to acquire the time-frequency resource and the random access preamble for performing random access according to the random access information when the random access parameter information is carried in the system information, the radio resource control RRC configuration message, or the system information change indication message will be described.

When the random access parameter information is carried in the system information, that is, the terminal device obtains the random access parameter information by receiving the system information of the network device, and further determines the PRACH resource and the random access preamble for performing random access according to the random access parameter information. For example, when the network device is an eNB, the network device carries fields of PRACH-ConfigIndex and PRACH _ FreqOffset in an SIB2 message, and specific information of the fields may refer to relevant descriptions in 3GPP TS36.331, and those skilled in the art can understand that the terminal device may determine PRACH resources and a random access preamble for performing random access according to various parameters therein, and a determination process of the PRACH resources and the random access preamble may refer to relevant technical specifications such as 3GPP TS36.211, 3GPP TS36.213, and 3GPP TS 36.321. When the network device is a gNB, the network device carries a BWP-UplinkCommon IE in a SIB1 message, where the IE includes a RACH-ConfigCommon IE, and the IE further includes a RACH-ConfigDedicated IE used by the terminal device for performing random access, and other IEs and parameters used in random access, such as a parameter pramh-rootsequence index used for generating a random access preamble, a parameter for determining a PRACH time-frequency resource for finally transmitting the random access preamble, such as a parameter pram-ConfigurationIndex, msg1-FrequencyStart, and the like, and a parameter for determining power for transmitting the random access preamble, such as pramblefransmax, powerRampingStep, and the like, and those skilled in the art can understand that the specific parameters carried therein may refer to the relevant description in 3GPP TS 38.331. As will be understood by those skilled in the art, the terminal device may determine the PRACH resource and the random access preamble for performing the random access according to various parameters therein, and specifically, the determination process may refer to relevant technical specifications of 3GPP TS38.211, 3GPP TS38.213, 3GPP TS 38.321, and the like. It should be noted that, when the network device is configured with the SUL, the terminal device may determine to perform random access on the NUL or the SUL according to a threshold rsrp-threshold ssb-SUL sent by the network device, or determine to perform random access on the NUL or the SUL according to indication information of the network device, where the indication information may be directly issued by the network device or issued by another relay network device, for example, in an EN-DC scenario, when the network device is a Secondary Cell Group (SCG) device, a network device of a Master Cell Group (MCG) may issue a signaling carrying the indication information to the terminal device, or the terminal device determines to perform random access on the NUL or the SUL according to its implementation. Therefore, the PRACH resource available for the terminal device to perform random access is a PRACH time-frequency resource on the NUL or SUL determined by the terminal device.

When the random access parameter information is carried in the radio resource control RRC configuration message, that is, the terminal device obtains the random access parameter information by receiving the RRC message configuration message of the network device, and further determines the PRACH resource and the random access preamble for performing random access according to the parameter information. For example, when the network device is an eNB, the network device carries parameters such as PRACH-ConfigIndex and PRACH _ FreqOffset in an RRC message, and specific parameter information of the network device may refer to relevant descriptions in 3GPP TS36.331, and those skilled in the art can understand that the terminal device may determine PRACH resources and a random access preamble for performing random access according to various parameters therein, and a determination process of the terminal device may refer to relevant technical specifications such as 3GPP TS36.211, 3GPP TS36.213, and 3GPP TS 36.321. When the network device is a gbb, the network device may carry information required for the terminal device to perform random access in an RRC message for BWP configuration, for example, by carrying an RACH-ConfigCommon IE in a BWP-UplinkCommon IE and carrying a beamFailureRecoveryConfig IE in a BWP-uplinkddedicated IE, where the RACH-ConfigGeneric IE and other parameters are included; or, the network device carries a reconfiguration withsync IE in the RRC message for Serving Cell configuration, where the rach-ConfigDedicated IE is carried. The RACH-ConfigCommon IE, the beamf ailurerecoveryconfig IE, and the RACH-ConfigDedicated IE all include RACH-ConfigDedicated IE and other IEs and parameters used in random access, such as parameter PRACH-rootsequence index for generating Preamble, parameters for determining PRACH time-frequency resources for finally transmitting the random access Preamble, such as PRACH-configurability index, msg1-FrequencyStart, and parameters for determining power for transmitting Preamble, such as preambleTransMax, powerstep, etc., and those skilled in the art will understand that specific parameters carried therein may refer to the relevant description in 3GPP TS 38.331. Those skilled in the art will understand that the terminal device may determine the PRACH resource and the random access preamble for performing random access according to various parameters therein, and the determination process may refer to relevant technical specifications of 3GPP TS38.211, 3GPP TS38.213, 3GPP TS 38.321, and so on. It should be noted that, when the network device is configured with the SUL, the terminal device may determine to perform random access on the NUL or the SUL according to a Threshold rsrp-Threshold SSB-SUL sent by the network device, or determine to perform random access on the NUL or the SUL according to indication information of the network device, where the indication information may be directly issued by the network device or issued by another relay network device, for example, in an EN-DC scenario, when the network device is an SCG device, a signaling carrying the indication information may be issued to the terminal device by the network device of the MCG, or the terminal device determines to perform random access on the NUL or the SUL according to its own implementation. Therefore, the PRACH resource available for the terminal device to perform random access is a PRACH time-frequency resource on the NUL or SUL determined by the terminal device. It should be noted that the PRACH resource for transmitting the random access preamble and the random access preamble for performing the random access determined by the terminal device may perform contention-based random access, or may be dedicated resources for the terminal device to perform non-contention-based random access.

When the random access parameter information is carried in the system information Change Indication message, that is, the terminal device obtains the random access parameter information by receiving the system information Change Indication message SI Change Indication message sent by the network device, and further determines the PRACH resource and the random access preamble of the random access according to the parameter information, the specific parameter information and the determining method thereof may refer to the above-mentioned description about when the random access parameter information is carried in the system information or in the radio resource control RRC configuration message, and herein, the embodiments of the present application are not described in detail again.

After acquiring the time-frequency resource and the random access preamble for random access through S301, the following S302 may be performed:

s302, the terminal equipment sends the random access lead code on the time frequency resource.

When the terminal device sends the random access preamble on the time-frequency resource, the specific sending manner may refer to descriptions in standard specifications of 3GPP TS38.211, 3GPP TS38.213, 3GPP TS 38.321, and the like, and herein, the embodiments of the present application are not described in detail again.

It should be noted that the manner in which the terminal device sends the random access preamble may also not be limited to the manner specified in the above standard specification, for example, during the process of sending the random access preamble, the terminal device may change the mechanisms of transmission power, power boosting, back-off, and the like, and herein, the embodiment of the present application is not limited specifically.

S303, the terminal device determines whether to switch to the downlink bandwidth part DL BWP where the random access response message is located.

When the terminal device sends the random access preamble on the Initial Uplink BWP, the corresponding Downlink bandwidth part DL BWP refers to the Initial Downlink BWP; when the terminal device transmits the random access preamble on the current Active UL BWP, the corresponding DL BWP refers to the DL BWP corresponding to the same ID as the Active UL BWP ID.

For the terminal device, when determining whether to switch to the downlink bandwidth part DL BWP where the random access response message is located, it can be determined in at least three possible ways:

in the method 1, the terminal device may determine whether uplink transmission needs to be performed in a time Window indicated by the ra-Response Window, and when uplink transmission exists in the time Window indicated by the ra-Response Window, for example, whether a time Window corresponding to an SPS UL Grant or a UL Grant configured by a Grant-free UL Grant arrives in the time Window, and if a time Window corresponding to an SPS UL Grant or a UL Grant configured by a Grant-free UL Grant arrives in the time Window, it is indicated that the terminal device needs to perform uplink data transmission, and at this time, the terminal device may determine not to switch to a corresponding DL BWP.

In the method 2, the terminal device may determine whether downlink reception is required within the time Window indicated by the ra-Response Window, and when there is downlink reception within the time Window indicated by the ra-Response Window, for example, within the time Window, a time Window indicated by a Configured DL Grant arrives on the original Active DL BWP, or, if the terminal device needs to receive downlink HARQ information within the time Window, it indicates that the terminal device needs to prepare for downlink reception on the current Active DL BWP, and at this time, the terminal device may determine not to switch to the corresponding DL BWP.

In the manner 3, the terminal device may determine whether there is downlink received data in the original downlink bandwidth portion before the time Window indicated by the ra-Response Window arrives, and when there is downlink transmission content in the original downlink bandwidth portion before the random access Response Window, and the downlink transmission content includes the UL Grant or the transmission time Window of the downlink transmission content overlaps with the time Window indicated by the ra-Response Window, the terminal device may determine not to switch to the corresponding DL BWP.

It should be noted that, in the embodiment of the present application, the terminal device only takes the above three manners as examples when determining whether to switch to the downlink bandwidth portion DL BWP where the random access response message is located, but the embodiment of the present application is not limited thereto.

The terminal device may perform a corresponding operation according to a determination result when determining whether to switch to the downlink bandwidth portion DL BWP where the random access response message is located, and if it is determined that the terminal device does not switch to the downlink bandwidth portion DL BWP where the random access response message is located after the determination, complete corresponding uplink transmission or downlink reception on the original Actvie UL BWP. On the contrary, if it is determined that the handover is to be performed to the downlink bandwidth part DL BWP where the random access response message is located, the following S304 is performed:

s304, if the switching is determined, switching to the DL BWP in the downlink bandwidth part where the random access response message is located in the random access response window.

After the determination in S303, if the terminal device determines that it needs to switch to the DL BWP of the downlink bandwidth portion where the random access Response message is located, the terminal device switches to the corresponding DL BWP when the time Window indicated by the random access Response Window ra-Response Window arrives, and receives the random access Response message corresponding to the random access preamble on the corresponding DL BWP, that is, the following S305 is executed:

s305, receiving the random access response message on the downlink bandwidth part DL BWP where the random access response message is located.

The terminal device monitors the random access response message sent by the network device on the downlink bandwidth part DL BWP where the random access response message is located, and sends the cache state information of the first logical channel according to whether the random access response message corresponding to the random access preamble is received, if the random access response message is received on the downlink bandwidth part DL BWP where the random access response message is located, the following S306 is executed; in contrast, if the random access response message is not received on the downlink bandwidth part DL BWP where the random access response message is located, the following S307-S308 are performed.

S306, if the terminal device receives the random access response message on the DL BWP of the downlink bandwidth part where the random access response message is, sending a third random access message on the uplink resource of the uplink authorization indication carried in the random access response message.

And the random access third message carries the cache state information of the first logic channel. The buffer status information on the first logical channel may include uplink data amount information on the first logical channel, where the uplink data amount information is determined according to the uplink data amount on the first logical channel, and when the uplink data amount information on the first logical channel is determined according to the uplink data amount on the first logical channel, the determination method may refer to the relevant description in 3GPP TS 38.321. When the terminal device calculates the uplink data amount on the first logical channel, the calculation method may refer to the relevant descriptions in 3GPP TS 38.322 and 3GPP TS 38.323, and herein, the embodiments of the present application are not described again. Or, the buffer status information on the first logical channel may also be uplink data amount information of the LCG where the first logical channel is located, where the uplink data amount information is determined according to the uplink data amount of the LCG where the first logical channel is located, and when determining the uplink data amount information of the LCG where the first logical channel is located according to the uplink data amount of the LCG where the first logical channel is located, the determining method may refer to relevant description in 3GPP TS 38.321. When the terminal device calculates the uplink data amount of the LCG, the calculation method may refer to the relevant description in 3GPP TS 38.322 and 3GPP TS 38.323, and herein, the embodiments of the present application are not described again.

If the terminal device receives the random access response message on the downlink bandwidth part DL BWP where the random access response message is located, the uplink resource indicated by the uplink grant carried in the random access response message sends a random access third message carrying the buffer status information of the first logical channel, so as to send the buffer status information of the first logical channel on the uplink resource.

It should be noted that the terminal device carries the C-RNTI on the time-frequency resource indicated by the UL Grant carried in the random access response message RAR, so as to indicate to the network device that the terminal device is a device that has already established an RRC connection.

In addition, it should be noted that, when the network device is in the TDD mode, the terminal device randomly accesses the current Active UL BWP without switching Active DL BWP, and at this time, the terminal device receives the RAR and the UL Grant receiving the SR request are on the same DL BWP; when the network device is of FDD system, and the terminal device performs random access on the current Active UL BWP, it needs to ensure that when receiving RAR, the ID of the downlink Active DL BWP is consistent with the ID of the uplink Active UL BWP, so the DL BWP when the terminal device receives RAR and the DL BWP of the UL Grant receiving SR request may not be the same DL BWP, and in this case, the terminal device may apply the present scheme.

S307, if the terminal equipment does not receive the random access Response message on the DL BWP of the downlink bandwidth part where the random access Response message is, switching back to the original DL BWP after the time Window indicated by the ra-Response Window is ended, and acquiring the uplink resource.

Optionally, when acquiring the uplink resource, the uplink resource may also be acquired by the following manner 1 and manner 2.

Mode 2, may receive configuration authorization of configuration authorization Type 1(configured grant Type 1) and/or configuration authorization Type 2(configured grant Type 2) sent by the network device; and configuring the Physical Uplink Shared Channel (PUSCH) resource indicated by the authorization as an uplink resource.

In detail, in the method 2, when acquiring the uplink resource, only the configuration grant of the configuration grant type 1 sent by the network device may be received, where the physical uplink shared channel PUSCH resource indicated by the configuration grant of the configuration grant type 1 is the uplink resource; or only receiving a configuration authorization of configuration authorization type 2 sent by the network device, where the PUSCH resource of the configuration authorization indication of the configuration authorization type 2 is an uplink resource; of course, the configuration authorization of the configuration authorization type 1 and the configuration authorization type 2 sent by the network device may also be received; and the Physical Uplink Shared Channel (PUSCH) resource indicated by the configuration authorization is an uplink resource, so that the uplink resource is acquired. For example, the configuration Grant may be a semi-persistent scheduling Grant SPS Grant or a Grant-free UL Grant.

After acquiring the uplink resource through S307, the buffer status information of the first logical channel may be sent on the uplink resource, that is, the following S308 is executed:

and S308, sending the buffer state information of the first logic channel on the uplink resource.

After the terminal device sends the buffer status information of the first logical channel on the uplink resource, instead of immediately canceling the pending SR triggered on the first logical channel, after it is determined that the network device has received the buffer status information of the first logical channel, the following S308 is performed to cancel the pending SR triggered on the first logical channel. It should be noted that, when determining that the network device has received the cache state information of the first logical channel, the terminal device may determine in at least two ways, where the way 1 indicates that the network device has received the cache state information of the first logical channel if the terminal device does not receive the retransmission indication information of the network device. In the method 2, if the terminal device receives an acknowledgement message (e.g., HARQ ACK) sent by the network device, it indicates that the network device has received the buffer status information of the first logical channel.

After the terminal device sends the buffer status information of the first logical channel on the uplink resource and confirms that the network device has received the buffer status information of the first logical channel, the following S309 is executed:

s309, the terminal equipment cancels the pending SR triggered on the first logic channel.

Further, if the terminal device does not acquire the uplink resource in the manner of step 307 before the next available PRACH resource arrives, the terminal device continues to transmit a Preamble on the available PRACH resource, and executes the processes described in steps 303 to 306 until the terminal device acquires the uplink resource in any one of step 307 or step 305 and transmits the buffer status information of the first logical channel, and the terminal device cancels the Pending SR triggered on the first logical channel.

Therefore, in this possible implementation manner, when the first logical channel triggers the pending scheduling request pending SR, the terminal device first acquires the time-frequency resource and the random access preamble for performing random access, and after acquiring the time-frequency resource and the random access preamble, transmits the random access preamble on the time-frequency resource; judging whether to switch to the DL bandwidth part DL BWP where the random access response message is located, if the switching to the DL bandwidth part DL BWP where the random access response message is located is determined, switching to the DL bandwidth part DL BWP where the random access response message is located in a random access response window, and receiving the random access response message corresponding to the random access preamble on the DL bandwidth part DL BWP; if the random access response message is received on the downlink bandwidth part DL BWP where the random access response message is located, sending a random access third message from an uplink resource indicated by uplink authorization carried in the random access response message, wherein the random access third message comprises the cache state information of the first logic channel so as to complete the sending of the cache state information of the first logic channel; if the random access Response message is not received on the DL BWP of the downlink bandwidth part where the random access Response message is located, switching back to the original DL BWP after the time Window indicated by the ra-Response Window is ended, acquiring uplink resources, and sending the cache state information of the first logic channel on the uplink resources; after the terminal device sends the buffer status information of the first logical channel on the uplink resource, the pending SR triggered on the first logical channel is not cancelled immediately, but the pending SR triggered on the first logical channel is cancelled after the network device is confirmed to have received the buffer status information of the first logical channel. By optimizing the random access RA process of the terminal equipment, the negative influence of RA of the terminal equipment is reduced, and the service continuity on the logical channel is improved.

Fig. 4 is a schematic structural diagram of a communication device 40 according to an embodiment of the present application, and for example, please refer to fig. 4, the communication device 40 may include:

the processing unit 401 is configured to acquire an uplink resource when a first logical channel triggers a pending scheduling request pending SR, where the first logical channel is a logical channel that is not matched to any scheduling request configuration.

A sending unit 402, configured to send the buffer status information of the first logical channel on the uplink resource.

The processing unit 401 is further configured to cancel the pending SR triggered on the first logical channel.

Optionally, the processing unit 401 is specifically configured to confirm that the network device has received the cache state information of the first logical channel; and cancels the pending SR triggered on the first logical channel.

Optionally, the communication device 40 further includes a receiving unit 403, for example, please refer to fig. 5, and fig. 5 is a schematic structural diagram of another communication device 40 provided in this embodiment of the present application.

The sending unit 402 is further configured to send the scheduling request to the network device on the physical uplink control channel PUCCH resource corresponding to the scheduling request configuration matched with the second logical channel.

A receiving unit 403, configured to receive an uplink grant sent by a network device, where a physical uplink shared channel PUSCH resource indicated by the uplink grant is an uplink resource.

Optionally, the processing unit 401 is further configured to determine that the second logical channel has triggered the pending SR.

Optionally, the receiving unit 403 is further Configured to receive a configuration authorization Configured Grant of the configuration authorization type 1 and/or the configuration authorization type 2 sent by the network device; and configuring the Physical Uplink Shared Channel (PUSCH) resource indicated by the authorization as an uplink resource.

The communication device 40 shown in the embodiment of the present application may execute the data transmission method on the terminal device side in the embodiment shown in fig. 2, and the implementation principle and the beneficial effect of the method are similar to those of the data transmission method on the terminal device side, and details are not repeated here.

Fig. 6 is a schematic structural diagram of another communication device 60 provided in the embodiment of the present application, and for example, please refer to fig. 6, the communication device 60 may include:

the processing unit 601 is configured to acquire a time-frequency resource and a random access preamble for performing random access when a first logical channel triggers a pending scheduling request pending SR, where the first logical channel is a logical channel that is not matched to any scheduling request configuration.

A sending unit 602, configured to send the random access preamble on a time-frequency resource.

A processing unit 601, configured to determine whether to switch to a downlink bandwidth portion DL BWP where the random access response message is located; and if the handover is determined, switching to the downlink bandwidth part DL BWP in which the random access response message is positioned in the random access response window.

A receiving unit 603, configured to receive a random access response message corresponding to the random access preamble on the downlink bandwidth portion DL BWP.

The sending unit 602 is further configured to send the buffer status information of the first logical channel according to the receiving result.

Optionally, the processing unit 601 is further configured to determine not to switch to the downlink bandwidth portion DL BWP where the random access response message is located if it is determined that at least one of the following conditions is met;

uplink transmission data exist in the random access response window;

downlink receiving data exists in the random access response window;

Optionally, the sending unit 602 is specifically configured to send a random access third message on an uplink resource indicated by an uplink grant carried in the random access response message if the random access response message is received on the downlink bandwidth part DL BWP; and the random access third message carries the cache state information of the first logic channel.

Optionally, the processing unit 601 is further configured to cancel a pending SR triggered on the first logical channel.

Optionally, the processing unit 601 is further configured to, if the random access Response message is not received on the downlink bandwidth part DL BWP, switch back to the original downlink bandwidth part DL BWP after the time Window indicated by the random access Response Window ra-Response Window is ended, and acquire the uplink resource.

The sending unit 602 is specifically configured to send the buffer status information of the first logical channel on the uplink resource.

Optionally, the sending unit 602 is specifically configured to send the scheduling request to the network device on the physical uplink control channel PUCCH resource corresponding to the scheduling request configuration matched with the second logical channel.

The receiving unit 603 is further configured to receive an uplink grant sent by the network device, where a physical uplink shared channel PUSCH resource indicated by the uplink grant is an uplink resource.

Optionally, the processing unit 601 is further configured to determine that the second logical channel has triggered the pending SR.

Optionally, the receiving unit 603 is further Configured to receive a configuration authorization Configured Grant of the configuration authorization type 1 and/or the configuration authorization type 2 sent by the network device; and configuring the Physical Uplink Shared Channel (PUSCH) resource indicated by the authorization as an uplink resource.

Optionally, the receiving unit 603 is further configured to receive random access parameter information sent by the network device; wherein the random access parameter information includes: at least one of random access parameter information of the initial uplink bandwidth part, random access parameter information of the activated uplink bandwidth part, or random access parameter information of free contention;

the processing unit 601 is specifically configured to determine a time-frequency resource and a random access preamble for random access according to the random access parameter information.

The communication device 60 shown in the embodiment of the present application may execute the data transmission method on the terminal device side in the embodiment shown in fig. 3, and the implementation principle and the beneficial effect of the method are similar to those of the data transmission method on the terminal device side, and details are not repeated here.

Fig. 7 is a schematic structural diagram of a communication device 70 according to an embodiment of the present application, and for example, referring to fig. 7, the communication device 70 may include a processor 701 and a memory 702, wherein,

the memory 702 is used to store program instructions;

the processor 701 is configured to read the program instruction in the memory 702, and execute the data transmission method on the terminal device side in the embodiment shown in fig. 2 according to the program instruction in the memory 702, or execute the data transmission method on the terminal device side in the embodiment shown in fig. 3, which is similar to the implementation principle and the beneficial effect of the data transmission method on the terminal device side, and therefore details are not repeated here.

An embodiment of the present application further provides a computer storage medium, which includes instructions, and when the instructions are executed by one or more processors, the communication apparatus is enabled to execute the data transmission method on the terminal device side in the embodiment shown in fig. 2 or execute the data transmission method on the terminal device side in the embodiment shown in fig. 3, and an implementation principle and beneficial effects of the computer storage medium are similar to an implementation principle and beneficial effects of the data transmission method on the terminal device side, and are not described herein again.

An embodiment of the present application further provides a chip, where a computer program is stored on the chip, and when the computer program is executed by a processor, the method for transmitting data on the terminal device side in the embodiment shown in fig. 2 is executed, or the method for transmitting data on the terminal device side in the embodiment shown in fig. 3 is executed, and an implementation principle and beneficial effects of the method for transmitting data on the terminal device side are similar to those of the method for transmitting data on the terminal device side, and are not described herein again.

The processor in the above embodiments may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may be located in a Random Access Memory (RAM), a flash memory, a read-only memory (ROM), a programmable ROM, an electrically erasable programmable memory, a register, or other storage media that are well known in the art. The storage medium is located in a memory, and a processor reads instructions in the memory and combines hardware thereof to complete the steps of the method.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

Claims

1. A method of data transmission, comprising:

sending the buffer state information of the first logic channel on the uplink resource;

canceling a pending SR triggered on the first logical channel;

the acquiring the uplink resource includes:

receiving an uplink grant sent by the network equipment, wherein a Physical Uplink Shared Channel (PUSCH) resource indicated by the uplink grant is the uplink resource;

the cancelling the pending SR triggered on the first logical channel includes:

canceling a pending SR triggered on the first logical channel;

before the sending the scheduling request to the network device on the physical uplink control channel PUCCH resource corresponding to the scheduling request configuration matched with the second logical channel, the method further includes:

determining that the second logical channel has triggered a pending SR.

2. The method of claim 1, wherein the obtaining the uplink resource comprises:

receiving a configuration authorization Configured Grant of a configuration authorization type 1 and/or a configuration authorization type 2 sent by a network device; and the Physical Uplink Shared Channel (PUSCH) resource indicated by the configuration authorization is the uplink resource.

3. A method of data transmission, comprising:

transmitting the random access preamble on the time-frequency resource;

sending the cache state information of the first logic channel according to the receiving result;

the sending the buffer status information of the first logical channel according to the receiving result includes:

the acquiring the uplink resource includes:

and receiving an uplink grant sent by the network equipment, wherein the Physical Uplink Shared Channel (PUSCH) resource indicated by the uplink grant is the uplink resource.

4. The method of claim 3, further comprising:

uplink transmission data exist in the random access response window;

downlink receiving data exists in the random access response window;

and downlink receiving data exists in the original downlink bandwidth part before the random access response window.

5. The method according to claim 3 or 4, wherein the sending the buffer status information of the first logical channel according to the receiving result comprises:

if the random access response message is received on the downlink bandwidth part DL BWP, sending a random access third message on an uplink resource indicated by an uplink authorization carried in the random access response message; wherein the random access third message carries the buffer status information of the first logical channel.

6. The method of claim 5, further comprising:

canceling the pending SR triggered on the first logical channel.

7. The method of claim 3, wherein before sending the scheduling request to the network device on the Physical Uplink Control Channel (PUCCH) resource corresponding to the second logical channel matched scheduling request configuration, further comprising:

determining that the second logical channel has triggered a pending SR.

8. The method of claim 3, wherein the obtaining the uplink resource comprises:

9. The method of claim 3, wherein the obtaining the time-frequency resource and the random access preamble for random access comprises:

receiving random access parameter information sent by network equipment; wherein the random access parameter information includes: at least one of random access parameter information of the initial uplink bandwidth part, random access parameter information of the activated uplink bandwidth part, or random access parameter information of free contention;

and determining the time-frequency resource of the random access and the random access lead code according to the random access parameter information.

10. A communication device, comprising:

the system comprises a processing unit and a scheduling unit, wherein the processing unit is used for acquiring uplink resources when a first logic channel triggers a pending scheduling request pending SR, and the first logic channel is a logic channel which is not matched with any scheduling request configuration;

the processing unit is further configured to cancel a pending SR triggered on the first logical channel;

the device further comprises a receiving unit;

the sending unit is further configured to send a scheduling request to the network device on a physical uplink control channel PUCCH resource corresponding to the scheduling request configuration matched with the second logical channel;

the receiving unit is configured to receive an uplink grant sent by the network device, where a physical uplink shared channel PUSCH resource indicated by the uplink grant is the uplink resource;

the processing unit is specifically configured to confirm that the network device has received the cache state information of the first logical channel; canceling the pending SR triggered on the first logic channel;

the processing unit is further configured to determine that the second logical channel has triggered a pending SR.

11. The apparatus of claim 10,

the receiving unit is further Configured to receive a configuration authorization Configured Grant of the configuration authorization type 1 and/or the configuration authorization type 2 sent by the network device; and the Physical Uplink Shared Channel (PUSCH) resource indicated by the configuration authorization is the uplink resource.

12. A communication device, comprising:

a sending unit, configured to send the random access preamble on the time-frequency resource;

the sending unit is further configured to send the buffer status information of the first logical channel according to a receiving result;

the processing unit is further configured to, if the random access Response message is not received on the downlink bandwidth part DL BWP, switch back to the original downlink bandwidth part DL BWP after a time Window indicated by a random access Response Window ra-Response Window is ended, and acquire an uplink resource;

the sending unit is specifically configured to send the buffer status information of the first logical channel on the uplink resource;

the sending unit is specifically configured to send a scheduling request to the network device on a physical uplink control channel PUCCH resource corresponding to the scheduling request configuration matched with the second logical channel;

the receiving unit is further configured to receive an uplink grant sent by the network device, where a physical uplink shared channel PUSCH resource indicated by the uplink grant is the uplink resource.

13. The apparatus of claim 12,

the processing unit is further configured to determine not to switch to the downlink bandwidth part DL BWP where the random access response message is located if it is determined that at least one of the following conditions is satisfied;

uplink transmission data exist in the random access response window;

downlink receiving data exists in the random access response window;

14. The apparatus according to claim 12 or 13,

the sending unit is specifically configured to send a random access third message in the uplink resource of the uplink grant indication carried in the random access response message if the random access response message is received on the downlink bandwidth part DL BWP; wherein the random access third message carries the buffer status information of the first logical channel.

15. The apparatus of claim 14,

the processing unit is further configured to cancel a pending SR triggered on the first logical channel.

16. The apparatus of claim 12,

17. The apparatus of claim 12,

the receiving unit is further Configured to receive a configuration authorization Configured Grant of a configuration authorization type 1 and/or a configuration authorization type 2 sent by the network device; and the Physical Uplink Shared Channel (PUSCH) resource indicated by the configuration authorization is the uplink resource.

18. The apparatus of claim 12,

the receiving unit is further configured to receive random access parameter information sent by the network device; wherein the random access parameter information includes: at least one of random access parameter information of the initial uplink bandwidth part, random access parameter information of the activated uplink bandwidth part, or random access parameter information of free contention;

the processing unit is specifically configured to determine the time-frequency resource of the random access and the random access preamble according to the random access parameter information.

19. A communication device comprising a processor and a memory, wherein,

the memory is to store program instructions;

the processor is configured to read the program instructions in the memory and execute the data transmission method according to claim 1 or 2, or execute the data transmission method according to any one of claims 3 to 9 according to the program instructions in the memory.

20. A computer storage medium comprising instructions which, when executed by one or more processors, cause a communications device to perform the data transmission method of claim 1 or 2, or to perform the data transmission method of any of claims 3-9.