CN111432432A - Data transmission method and device - Google Patents

Data transmission method and device Download PDF

Info

Publication number
CN111432432A
CN111432432A CN201910022428.9A CN201910022428A CN111432432A CN 111432432 A CN111432432 A CN 111432432A CN 201910022428 A CN201910022428 A CN 201910022428A CN 111432432 A CN111432432 A CN 111432432A
Authority
CN
China
Prior art keywords
random access
uplink
logical channel
resource
channel
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN201910022428.9A
Other languages
Chinese (zh)
Other versions
CN111432432B (en
Inventor
李小仙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201910022428.9A priority Critical patent/CN111432432B/en
Priority to PCT/CN2019/124536 priority patent/WO2020143383A1/en
Publication of CN111432432A publication Critical patent/CN111432432A/en
Application granted granted Critical
Publication of CN111432432B publication Critical patent/CN111432432B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/0278Traffic management, e.g. flow control or congestion control using buffer status reports
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/12Wireless traffic scheduling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/12Wireless traffic scheduling
    • H04W72/1263Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows

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 is a hot spot in the industry, and 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 an "ultra 4G network", or a "long Term Evolution (L ong Term Evolution, L TE) system", or a New Radio (NR).
In the data transmission process, the network device may configure multiple logical channels (L 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 Uplink Shared Channel (PUSCH) resources, the terminal device may be triggered to send an SR message on a Physical Uplink Control Channel (PUCCH) resource indicated by Scheduling Request (SR) configuration matched by the logical Channel, according to the specification of 3GPP TS38.321, one logical Channel may be matched to 0 or 1 SR configuration, that is, one logical Channel may not have corresponding SR configuration, therefore, when there is data to be transmitted on the logical Channel and the terminal device does not have available PUSCH resources, the terminal device needs to trigger a special cell (dedicated cell, space) to Request resources to switch to a dedicated Access Channel (BWP) to a random Access Channel (BWP) for requesting resources if there is data to be transmitted on the logical Channel and the terminal device does not have available PUSCH resources, the terminal device needs to switch to a dedicated cell (dedicated cell, space) to a random Access Channel (BWP) for requesting resources if there is a currently Active Channel L, which is configured with a same Bandwidth Part (BWP 27, which may cause a random Access change of the Uplink Shared Channel (BWP) and the Uplink Shared Channel (BWP) may not change.
Therefore, if the terminal device switches the current Active D L 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 D L BWP before the terminal device switches, and at this time, since the Active D L BWP of the terminal device has been changed, the terminal device cannot receive the downlink data, thereby causing the traffic on the logical channel to be stuck or interrupted.
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 pendingSR, 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 configuration authorization ConfigardGrant of configuration authorization type 1 and/or configuration authorization type 2 sent by network equipment; 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 portion D L BWP in which the random access response message is located;
if the handover is determined, the handover is performed to the downlink bandwidth part D L BWP in which the random access response message is located within the random access response window;
receiving a random access response message corresponding to the random access preamble on the downlink bandwidth portion D L 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:
determining not to switch to the downlink bandwidth portion D L BWP in which the random access response message is 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;
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:
and if the random access response message is received on the downlink bandwidth part D L BWP, sending a random access third message from the uplink resource indicated by the uplink authorization carried in the random access response message, wherein the random access third message carries the buffer state information of the first logical channel.
In one possible implementation, the method may further include:
the pending SR triggered on the first logical channel is cancelled.
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 not received on the downlink bandwidth part D L BWP, switching back to the original downlink bandwidth part D L BWP after the time Window indicated by the random access Response Window 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:
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.
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 configuration authorization ConfigardGrant of configuration authorization type 1 and/or configuration authorization type 2 sent by network equipment; 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 pendingSR.
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 also used for determining whether to switch to the downlink bandwidth part D L BWP where the random access response message is located, and if the switching is determined, switching to the downlink bandwidth part D L BWP where the random access response message is located 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 portion D L 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 D L 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;
there is downlink received data in the original downlink bandwidth portion before 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 portion D L BWP, where the random access third message carries buffer status information of the first logical 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 portion D L BWP, switch back to the original downlink bandwidth portion D L 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 processing unit is further configured to determine that the second logical channel has triggered pendingSR.
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 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 (L ong Term Evolution, L TE) architecture, and may also be applied to a Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) architecture, or a Global System for Mobile communications (GSM)/Enhanced Data Rate GSM Evolution (Enhanced Data Rate for GSM Radio Network, GERAN) architecture of an EDGE) System, where the MME function is implemented by a General Packet Radio Service (GPRS) Support Node (SGSN ), the SGW function is implemented by a GPRS Support Node (GGSN, GGSN 635) System, and may even be applied to a GPRS System, such as a GPRS System, a GPRS Network, a future GPRS Network, or a GPRS Network, and other embodiments of the present application are not limited to the GPRS System, such as the GPRS Network and the GPRS System, the GPRS Gateway (GGSN) technology, the present application may also be implemented by a GPRS Radio Network (GPRS) Support Node (GPRS Radio Network) Support Node (Serving, a GPRS) Network, a GPRS Support Node, a GPRS System, or a future Mobile communication System (GPRS) technology, such as the present application.
The terminal may refer to, for example, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless local loop (Wireless L o c L op, W LL) station, a Personal Digital Assistant (PDA), a computing device with Wireless communication function, or another 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, and the present invention is not limited thereto.
The Network device may be a device for communicating with a terminal device, and for example, may be a Base 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 L TE system, or a Network device in 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 Public land mobile Network (Public L and mobile Network, P L MN) in the future.
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 an embodiment of the present application, where a wireless communication system shown in the system architecture may include a core network, an access network, and the like, taking a 5G communication system as an example, the core network may be an NGC/5GC or an EPC, and the access network may be a 5G NR or an E-UTRAN, and for convenience of description, in this embodiment, the core network and the access network are collectively referred to as the core network and the access network in the present application, where the access network may include a network device and at least one terminal device, and the terminal device may be directly connected to the network device, as a 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, as a terminal device 2 shown in fig. 1, the Relay device may be a Relay device or a Customer Premises Equipment (CPE) connected to the network device through a link 2, and the Relay device may also be considered as a terminal device as a Relay device, the Relay device may establish a connection with the user device through a link 3, and the Relay device may also be considered as a network device may perform a network device and perform a downlink data transmission on a downlink data channel switching between the terminal device and a downlink data channel before bwd, so that the downlink data transmission of the terminal device may not be able to generate a downlink data transmission channel before a downlink data transmission channel switching, and send a bwd, so that the downlink data transmission of the terminal device may be interrupted after the bwd, and the downlink data transmission device may be.
In order to improve the continuity of services on logical channels, embodiments of the present application provide a data transmission method, which may improve the continuity of services on logical channels through at least two possible implementation manners, in one possible implementation manner, if a first logical channel that is not matched to any Scheduling Request configuration triggers a pending SR, at this time, the first logical channel may not need to initiate Random Access (RA), but send the buffer status information of the first logical channel through a physical uplink shared channel PUSCH resource indicated by other uplink grants, and cancel the pending Request (SR) of the first logical channel to avoid the 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, the terminal device may determine whether to switch to a downlink bandwidth portion D24 where a Random Access response message is located, and then perform a detailed handover procedure to a Random Access window p 638652, thereby optimizing the reception of a Random Access message on a downlink bandwidth portion through a Random Access window, and thus optimizing the Random Access response of the Random Access window.
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 determining 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. 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 this embodiment 1, before sending the scheduling request to the network device on the physical uplink control channel PUCCH resource corresponding to the scheduling request configuration matched to 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 U L Grant through the SR sent by the second logical channel, and of course, the terminal device may also send the SR corresponding to the first logical channel through the SRconfiguration corresponding to the 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 this mode 2, when acquiring an uplink resource, only the configuration Grant of the configuration Grant type 1 sent by the network device may be received, where the PUSCH resource of the physical uplink shared channel indicated by the configuration Grant of the configuration Grant type 1 is an uplink resource, or only the uplink Grant of the configuration Grant type 2 sent by the network device may be received, where the PUSCH resource of the physical uplink shared channel indicated by the configuration Grant of the configuration Grant type 2 is an uplink resource, and of course, the configuration grants of the configuration Grant type 1 and the configuration Grant type 2 sent by the network device may also be received, where the PUSCH resource of the physical uplink shared channel indicated by the configuration Grant is an uplink resource, so as to acquire the uplink resource.
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 the uplink data amount information on the first logical Channel is determined according to the uplink data amount on the first logical Channel, the determining method may refer to the related description in 3GPP TS38.321, where the computing method of the terminal device may refer to the related descriptions in 3GPP TS38.322 and 3GPP TS 38.323 when computing the uplink data amount on the first logical Channel, where the description is not repeated herein in this application embodiment, or the buffer status information on the first logical Channel may also refer to the uplink data amount information of a logical Channel Group (L logical Channel Group, L CG) where the first logical Channel is located, the uplink data amount information is determined according to the uplink data amount of a CG 2 where the first logical Channel is located, and when determining the uplink data amount information of a logical Channel Group where the first logical Channel is located according to the uplink data amount of a CG 23 where the first logical Channel is located, the related description of the uplink data amount information in 3GPP L may refer to the description in this application, where the computing method of the relevant description is performed by the third embodiment, and the third embodiment, the third embodiment.
It should be noted that, in this embodiment of the present application, when the terminal device sends the Buffer state information of the first logical channel on the uplink resource, a Buffer State Report (BSR) may be sent on the uplink resource, where the BSR may carry the Buffer state information of the first logical channel, where the BSR sent by the terminal device may be any one of the MAC CEs in Short BSR, L ong BSR, Short routed BSR, and L ong routed BSR formats, and here, as for the format of the BSR, this embodiment of the present application is not further limited.
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.
Therefore, in this possible implementation manner, when the first logical channel triggers the pending scheduling request pendingSR, 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.
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.
Wherein the first logical channel is a logical channel that is not matched to any scheduling request configuration.
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 acquiring a time-frequency resource and a Random Access preamble for performing Random Access, a terminal device may receive Random Access parameter information sent by a network device, and determine a time-frequency resource and a Random Access preamble for Random Access according to the Random Access parameter information, where the Random Access parameter information includes time-frequency resource information for indicating Random Access and indication information for indicating the Random Access preamble, where the time-frequency resource information for Random Access may be Physical Random Access Channel (PRACH) time-frequency resource information, the PRACH time-frequency resource information may include one or more of PRACH format, period, frame number in the period, subframe number, start symbol, PRACH slot, PRACH transmission opportunity in the slot, and information for selecting Normal Uplink (NU L) or supplemental Uplink (SU L) for transmission, and the indication information for indicating the Random Access preamble may include information such as root sequence traction, selection set, and the like for generating the Random Access preamble.
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 Initial Uplink BWP, specifically, when the terminal device is not configured with the random access resource on the currently activated Uplink bandwidth part Active U L BWP, the terminal device may perform random access on the Initial Uplink BWP.
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, according to the random access parameter information, the PRACH resource and the random access preamble for performing random access, for example, when the network device is an eNB, the network device carries, in a SIB2 message, a PRACH resource and a random access preamble for performing random access, the specific information may refer to a relevant description in 3GPP TS36.331, a skilled person in the art may understand that the terminal device may determine, according to various parameters therein, the PRACH resource and the random access preamble for performing random access, the determination process may refer to related technical specifications such as 3GPP TS36.211, 3GPP TS36.213, 3 TS 36.321, and the like, when the network device is a gNB, the network device itself carries, in a message of a random access-contention common, which includes a RACH-common, when the network device further includes a PRACH-gprs-preamble for performing random access, a random access parameter specification, a contention-contention parameter which is indicated by a contention-null-contention parameter specification, a contention parameter which is used by a contention-contention parameter specification when the network device is used for performing random access, a contention-contention parameter, or a contention parameter which is used by a contention parameter specification, is used by a contention-contention parameter specification, determined by a contention parameter which is used by a contention-contention parameter, a contention-contention parameter, such as a contention parameter specification, a contention-contention parameter specification, a contention parameter which is used by a contention-contention parameter specification, a contention-element, a contention-element, a contention-element, a contention-element, a contention-element, a random access-element.
The network device may determine that the network device carries the parameters such as PRACH-configuration index and PRACH-freq offset in the RRC message, and the specific parameter information may refer to the relevant description in 3GPP TS36.331, the technical personnel in the art may understand that the terminal device may determine the PRACH resource and the random access Preamble for random access according to the parameters such as PRACH-configuration index and PRACH-freq offset in the RRC message, which may refer to the relevant technical specifications such as 3GPP TS36.211, 3GPP TS36.213, 3GPP TS 36.321, when the network device is a gmb, the network device may carry the information required for random access in the RRC message for BWP configuration, for example, when the network device carries the information such as the RRC parameter specification in the RRC-uplink-downlink, the parameter information is used for determining that the network device carries the information, the information required for random access by the terminal device in the RRC-configuration index information, the parameter information may be used for random access-contention information or the parameter information used for random access of the random access network device to send the PRACH-configuration information, the RRC-configuration information, the parameter information may be used for the random access parameter specification when the network device determines that the network device carries the parameter information such as the PRACH-contention information, the parameter information, such as the parameter information, which is used for random access parameter information, the PRACH-contention of the PRACH-contention, the PRACH-precoding-negotiation, the network device may refer to the parameter, the parameter information, the parameter which is used by the PRACH-precoding-discovery information, the parameter which is used for random access network device, the PRACH-precoding-discovery network device, the PRACH-discovery information, the network, the parameter which is used for random access network, the random access network, the random access of the random access network, the random access network device may refer to carry the random access network device may refer to the random access network, the random access network device may refer to the random access network, the random access network device may refer to the random access network, the random.
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 TS38.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 portion D L 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 D L BWP refers to the Initial Downlink BWP, and when the terminal device sends the random access preamble on the current Active U L BWP, the corresponding D L BWP refers to the D L BWP corresponding to the same ID as the Active U L BWPID.
For the terminal device, when determining whether to switch to the downlink bandwidth portion D L 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 a ra-Response Window, and when there is uplink transmission in the time Window indicated by the ra-Response Window, for example, whether a time Window corresponding to an SPS U L Grant or a U L Grant configured by a Grant-free U L Grant arrives in the time Window, if a time Window corresponding to an SPS U L Grant or a U L configured by a Grant-free U L Grant arrives in the time Window, it is determined 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 D L 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 D L Grant arrives on the original Active D L 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 D L BWP, and at this time, the terminal device may determine not to switch to the corresponding D L BWP.
In mode 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 U L 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 D L 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 D L BWP where the random access response message is located, but does not represent that the embodiment of the present application is limited thereto.
The terminal device may perform corresponding operations according to the determination result when determining whether to switch to the downlink bandwidth part D L BWP in which the ra response message is located, and if it is determined not to switch to the downlink bandwidth part D L BWP in which the ra response message is located after the determination, corresponding uplink transmission or downlink reception is completed on the original Actvie U L BWP, otherwise, if it is determined to switch to the downlink bandwidth part D L BWP in which the ra response message is located, the following S304 is performed:
and S304, if the switching is determined, switching to the downlink bandwidth part D L BWP in which the random access response message is located in the random access response window.
After the determination of S303, if the terminal device determines that it needs to switch to the downlink bandwidth portion D L BWP where the random access Response message is located, then it switches to the corresponding D L 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 D L BWP, that is, the following S305 is executed:
s305, receiving the random access response message on the downlink bandwidth portion D L BWP where the random access response message is located.
The terminal device listens to the random access response message sent by the network device on the downlink bandwidth part D L BWP where the random access response message is located, and sends the buffer status information of the first logical channel according to whether the random access response message corresponding to the random access preamble is received, and if the random access response message is received on the downlink bandwidth part D L BWP where the random access response message is located, performs the following S306, and conversely, if the random access response message is not received on the downlink bandwidth part D L BWP where the random access response message is located, performs the following S307-S308.
S306, if the terminal device receives the random access response message on the downlink bandwidth portion D L BWP where the random access response message is located, sending a third random access message on the uplink resource indicated by the uplink grant carried in the random access response message.
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 an 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 determining method may refer to a related description in 3GPP TS38.321, where the calculating method of the terminal device may refer to related descriptions in 3GPP TS38.322 and 3GPP TS 38.323 when calculating the uplink data amount on the first logical channel, and herein, the description is not repeated in this application embodiment, or the buffer status information on the first logical channel may also be uplink data amount information of L CG where the first logical channel is located, the uplink data amount information is determined according to an uplink data amount of L CG where the first logical channel is located, and when determining an uplink data amount information of L where the first logical channel is located according to an uplink data amount of L where the first logical channel is located, the description of a related data amount information in 3GPP 7328 may refer to a related description in this application, where the description of a related description of a terminal device 3GPP TS 4933 GPP 3 is not repeated.
If the terminal device receives the random access response message on the downlink bandwidth portion D L 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 U L 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 TDD mode, the terminal device performs random access on the current Active U L BWP without switching Active D L BWP, and at this time, the terminal device receives RAR and the U L0 Grant receiving the SR request are on the same D L BWP, and when the network device is in FDD mode, the terminal device performs random access on the current Active U L BWP, it is necessary to ensure that the ID of the downlink Active D L BWP and the ID of the uplink Active U L BWP are consistent when receiving RAR, so that the D L BWP when the terminal device receives RAR and the D L BWP of the U L Grant receiving the SR request are not the same D L BWP, in which case, the terminal device may apply the present scheme.
S307, if the terminal equipment does not receive the random access Response message on the downlink bandwidth part D L BWP where the random access Response message is, after the time Window indicated by the random access Response Window ra-Response Window is ended, switching back to the original D L BWP, 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.
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 this embodiment 1, before sending the scheduling request to the network device on the physical uplink control channel PUCCH resource corresponding to the scheduling request configuration matched to the second logical channel, it needs to determine whether the second logical channel has triggered the pending SR, if the second logical channel has triggered the pending SR, the terminal device may obtain the U L Grant through the SR sent by the second logical channel, and of course, the terminal device may also send the SR corresponding to the first logical channel through the SRconfiguration corresponding to the other logical channels.
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 this mode 2, when acquiring an uplink resource, only the configuration Grant of the configuration Grant type 1 sent by the network device may be received, where the PUSCH resource of the physical uplink shared channel indicated by the configuration Grant of the configuration Grant type 1 is an uplink resource, or only the configuration Grant of the configuration Grant type 2 sent by the network device may be received, where the PUSCH resource of the physical uplink shared channel indicated by the configuration Grant of the configuration Grant type 2 is an uplink resource, and of course, the configuration grants of the configuration Grant type 1 and the configuration Grant type 2 sent by the network device may also be received, where the PUSCH resource of the physical uplink shared channel indicated by the configuration Grant is an uplink resource, so as to acquire the uplink resource.
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 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.
It should be noted that, in this embodiment of the present application, when the terminal device sends the Buffer state information of the first logical channel on the uplink resource, a Buffer State Report (BSR) may be sent on the uplink resource, where the BSR may carry the Buffer state information of the first logical channel, where the BSR sent by the terminal device may be any one of the Short BSR, L ong BSR, Short routed BSR, and MAC CE in L ong routed BSR format, and here, regarding the format of the BSR, this embodiment of the present application is not limited further.
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.
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.
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.
It can be seen that, in this possible implementation manner, when a pending scheduling request pendingSR is triggered by a first logical channel, a terminal device first acquires a time-frequency resource and a 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, then determines whether to switch to a downlink bandwidth portion D L BWP where a random access Response message is located, and if it is determined to switch to a downlink bandwidth portion D L BWP where the random access Response message is located, switches to a downlink bandwidth portion D L BWP where the random access Response message is located in a random access Response Window, and receives a random access Response message corresponding to the random access Response message on a downlink bandwidth portion D L BWP, and if the random access Response message is received on the downlink bandwidth portion D L BWP where the random access Response message is located, transmits a random access third message to an uplink resource indicated by an uplink grant carried in the random access Response message, where the random access Response message includes a buffer status of the first logical channel, and if the random access Response message is not received on a logical channel state indicating that the random access Response message on a logical channel when the random access Response message is not sent on a logical channel, the first logical channel, the random access Response message is not sent on a logical channel, and the random access Response message is not sent on a logical channel when the random access Response Window D SR..
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.
The processing unit 601 is further configured to determine whether to switch to the downlink bandwidth portion D L BWP where the random access response message is located, and if the switch is determined, switch to the downlink bandwidth portion D L BWP where the random access response message is located within 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 D L 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 D L 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;
there is downlink received data in the original downlink bandwidth portion before the random access response window.
Optionally, the sending unit 602 is specifically configured to send a random access third message on the uplink resource indicated by the uplink grant carried in the random access response message if the random access response message is received on the downlink bandwidth portion D L BWP, where the random access third message carries the buffer status information of the first logical 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 portion D L BWP, switch back to the original downlink bandwidth portion D L 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 each of 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 component. 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 (30)

1. A method of data transmission, comprising:
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 buffer state information of the first logic channel on the uplink resource;
canceling the pending SR triggered on the first logical channel.
2. The method of claim 1, wherein canceling the pending SR triggered on the first logical channel comprises:
confirming that the network equipment has received the cache state information of the first logic channel;
canceling the pending SR triggered on the first logical channel.
3. The method according to claim 1 or 2, wherein the acquiring the uplink resource comprises:
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 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, 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.
5. The method according to claim 1 or 2, wherein the acquiring the uplink resource comprises:
receiving configuration authorization ConfigardGrant of configuration authorization type 1 and/or configuration authorization type 2 sent by network equipment; and the Physical Uplink Shared Channel (PUSCH) resource indicated by the configuration authorization is the uplink resource.
6. A method of data transmission, comprising:
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;
transmitting the random access preamble on the time-frequency resource;
determining whether to switch to a downlink bandwidth portion D L BWP in which the random access response message is located;
if the handover is determined, the handover is performed to the downlink bandwidth part D L BWP in which the random access response message is located within the random access response window;
receiving a random access response message corresponding to the random access preamble on the downlink bandwidth portion D L BWP;
and sending the cache state information of the first logic channel according to the receiving result.
7. The method of claim 6, further comprising:
determining not to switch to the downlink bandwidth portion D L BWP in which the random access response message is 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;
and downlink receiving data exists in the original downlink bandwidth part before the random access response window.
8. The method according to claim 6 or 7, wherein the sending the buffer status information of the first logical channel according to the receiving result comprises:
and if the random access response message is received on the downlink bandwidth part D L BWP, sending a third random access message from the uplink resource indicated by the uplink grant carried in the random access response message, wherein the third random access message carries the buffer status information of the first logical channel.
9. The method of claim 8, further comprising:
canceling the pending SR triggered on the first logical channel.
10. The method according to claim 6 or 7, 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 not received on the downlink bandwidth part D L BWP, switching back to the original downlink bandwidth part D L BWP after the time Window indicated by the random access Response Window ra-Response Window is finished, and acquiring uplink resources;
and sending the buffer state information of the first logic channel on the uplink resource.
11. The method of claim 10, wherein the obtaining the uplink resource comprises:
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 grant sent by the network equipment, wherein the Physical Uplink Shared Channel (PUSCH) resource indicated by the uplink grant is the uplink resource.
12. The method of claim 11, 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.
13. The method of claim 10, wherein the obtaining the uplink resource comprises:
receiving configuration authorization ConfigardGrant of configuration authorization type 1 and/or configuration authorization type 2 sent by network equipment; and the Physical Uplink Shared Channel (PUSCH) resource indicated by the configuration authorization is the uplink resource.
14. The method of claim 6, 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.
15. 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;
a sending unit, configured to send the buffer status information of the first logical channel on the uplink resource;
the processing unit is further configured to cancel a pending SR triggered on the first logical channel.
16. The apparatus of claim 15,
the processing unit is specifically configured to confirm that the network device has received the cache state information of the first logical channel; and canceling the pending SR triggered on the first logical channel.
17. The apparatus according to claim 15 or 16, characterized in that the apparatus 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.
18. The apparatus of claim 17,
the processing unit is further configured to determine that the second logical channel has triggered a pending SR.
19. The apparatus according to claim 15 or 16,
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.
20. A communication device, comprising:
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 the random access preamble on the time-frequency resource;
the processing unit is further configured to determine whether to switch to the downlink bandwidth part D L BWP where the random access response message is located, and if the switching is determined, switch to the downlink bandwidth part D L BWP where the random access response message is located 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 portion D L BWP;
the sending unit is further configured to send the buffer status information of the first logical channel according to the receiving result.
21. The apparatus of claim 20,
the processing unit is further configured to determine not to switch to the downlink bandwidth portion D L 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;
and downlink receiving data exists in the original downlink bandwidth part before the random access response window.
22. The apparatus according to claim 20 or 21,
the sending unit is specifically configured to send a random access third message in the uplink resource indicated by the uplink grant carried in the random access response message if the random access response message is received on the downlink bandwidth portion D L BWP, where the random access third message carries the buffer status information of the first logical channel.
23. The apparatus of claim 22,
the processing unit is further configured to cancel a pending SR triggered on the first logical channel.
24. The apparatus according to claim 20 or 21,
the processing unit is further configured to, if the random access Response message is not received on the downlink bandwidth part D L BWP, switch back to the original downlink bandwidth part D L BWP after the time Window indicated by the 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.
25. The apparatus of claim 24,
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.
26. The apparatus of claim 25,
the processing unit is further configured to determine that the second logical channel has triggered a pending SR.
27. The apparatus of claim 24,
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.
28. The apparatus of claim 20,
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.
29. 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 any one of claims 1 to 5 or execute the data transmission method according to any one of claims 6 to 14 according to the program instructions in the memory.
30. A computer storage medium comprising instructions that, when executed by one or more processors, cause a communications apparatus to perform the data transmission method of any of claims 1-5 or to perform the data transmission method of any of claims 6-14.
CN201910022428.9A 2019-01-10 2019-01-10 Data transmission method and device Active CN111432432B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201910022428.9A CN111432432B (en) 2019-01-10 2019-01-10 Data transmission method and device
PCT/CN2019/124536 WO2020143383A1 (en) 2019-01-10 2019-12-11 Data transmission method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910022428.9A CN111432432B (en) 2019-01-10 2019-01-10 Data transmission method and device

Publications (2)

Publication Number Publication Date
CN111432432A true CN111432432A (en) 2020-07-17
CN111432432B CN111432432B (en) 2022-04-22

Family

ID=71520843

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910022428.9A Active CN111432432B (en) 2019-01-10 2019-01-10 Data transmission method and device

Country Status (2)

Country Link
CN (1) CN111432432B (en)
WO (1) WO2020143383A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114245473A (en) * 2020-09-09 2022-03-25 成都鼎桥通信技术有限公司 Random access method, device, electronic equipment and storage medium
CN114339617A (en) * 2020-10-09 2022-04-12 成都鼎桥通信技术有限公司 Method and device for configuring and using MBS (multicast broadcast multicast service) resources in NR (neighbor radio network) cell
WO2022126577A1 (en) * 2020-12-18 2022-06-23 Qualcomm Incorporated Obtaining uplink resources for logical channel without associated scheduling request configuration

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1710962A1 (en) * 2005-04-04 2006-10-11 Samsung Electronics Co.,Ltd. Method and apparatus for scheduling uplink packet transmission in a mobile communication system
US20170347369A1 (en) * 2016-05-24 2017-11-30 Lg Electronics Inc. Method for transmitting a data in a communication system and device therefor
US20180324867A1 (en) * 2017-05-05 2018-11-08 Motorola Mobility Llc Transmitting sr prior to completing rach
US20180324872A1 (en) * 2017-05-04 2018-11-08 Ofinno Technologies, Llc Scheduling Request Transmission
CN108811146A (en) * 2017-05-04 2018-11-13 维沃移动通信有限公司 Uplink scheduling request processing method and processing device
CN108811152A (en) * 2017-05-05 2018-11-13 华为技术有限公司 Resource application method and equipment
US20180332580A1 (en) * 2016-04-25 2018-11-15 Ofinno Technologies, Llc Transport Block Transmission by a Wireless Device in a Wireless Network
CN109041245A (en) * 2017-06-08 2018-12-18 华硕电脑股份有限公司 The method and apparatus of multiple scheduling request configurations in wireless communication system
WO2018232259A1 (en) * 2017-06-15 2018-12-20 Convida Wireless, Llc Scheduling requests, status reports, and logical channel prioritization
CN109152025A (en) * 2017-06-16 2019-01-04 华为技术有限公司 Communication means, terminal and base station
CN109156025A (en) * 2017-04-27 2019-01-04 北京小米移动软件有限公司 Ascending resource acquisition methods, device and computer readable storage medium

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108811099A (en) * 2017-05-03 2018-11-13 华为技术有限公司 The dispatching method and equipment of uplink transmission resource
ES2913902T3 (en) * 2017-05-04 2022-06-06 Ofinno Llc Programming request on a wireless device and wireless network
CN109392175B (en) * 2017-08-11 2023-08-08 华为技术有限公司 Scheduling request sending method, scheduling request processing method and related equipment

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1710962A1 (en) * 2005-04-04 2006-10-11 Samsung Electronics Co.,Ltd. Method and apparatus for scheduling uplink packet transmission in a mobile communication system
US20180332580A1 (en) * 2016-04-25 2018-11-15 Ofinno Technologies, Llc Transport Block Transmission by a Wireless Device in a Wireless Network
US20170347369A1 (en) * 2016-05-24 2017-11-30 Lg Electronics Inc. Method for transmitting a data in a communication system and device therefor
CN109156025A (en) * 2017-04-27 2019-01-04 北京小米移动软件有限公司 Ascending resource acquisition methods, device and computer readable storage medium
US20180324872A1 (en) * 2017-05-04 2018-11-08 Ofinno Technologies, Llc Scheduling Request Transmission
CN108811146A (en) * 2017-05-04 2018-11-13 维沃移动通信有限公司 Uplink scheduling request processing method and processing device
US20180324867A1 (en) * 2017-05-05 2018-11-08 Motorola Mobility Llc Transmitting sr prior to completing rach
CN108811152A (en) * 2017-05-05 2018-11-13 华为技术有限公司 Resource application method and equipment
CN109041245A (en) * 2017-06-08 2018-12-18 华硕电脑股份有限公司 The method and apparatus of multiple scheduling request configurations in wireless communication system
WO2018232259A1 (en) * 2017-06-15 2018-12-20 Convida Wireless, Llc Scheduling requests, status reports, and logical channel prioritization
CN109152025A (en) * 2017-06-16 2019-01-04 华为技术有限公司 Communication means, terminal and base station

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: ""Further considerations on RACH related BWP issues"", 《3GPP TSG-RAN2 #101 R2-1801815》 *
LENOVO, MOTOROLA MOBILITY: ""Scheduling Request procedure"", 《3GPP TSG-RAN WG2 NR AH#1 R2-1800681》 *
SAMSUNG ELECTRONICS R&D INSTITUTE UK: ""Outstanding issues with SR design for NR and TP for TS 38.321"", 《3GPP TSG-RAN WG2 #100 R2-1712284》 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114245473A (en) * 2020-09-09 2022-03-25 成都鼎桥通信技术有限公司 Random access method, device, electronic equipment and storage medium
CN114339617A (en) * 2020-10-09 2022-04-12 成都鼎桥通信技术有限公司 Method and device for configuring and using MBS (multicast broadcast multicast service) resources in NR (neighbor radio network) cell
WO2022126577A1 (en) * 2020-12-18 2022-06-23 Qualcomm Incorporated Obtaining uplink resources for logical channel without associated scheduling request configuration

Also Published As

Publication number Publication date
WO2020143383A1 (en) 2020-07-16
CN111432432B (en) 2022-04-22

Similar Documents

Publication Publication Date Title
JP4677490B2 (en) Wireless connection information transmission / reception method in wireless mobile communication system
CN101999219B (en) Method and apparatus of processing random access
WO2016183705A1 (en) Method and apparatus for transmitting uplink data in licensed-assisted access system
CN113490286B (en) Random access method, terminal equipment and network equipment
US20200374920A1 (en) Method and apparatus for transmitting data in random access process
CN113905453B (en) Random access method and equipment
CN110972322B (en) Random access method and communication device
US9942910B2 (en) Method for transmitting data on wireless local area network, user equipment, and access point
CN108365912B (en) Transmission mode switching method and device
US20210297188A1 (en) Data transmission method and communication apparatus
CN111432432B (en) Data transmission method and device
CN112153750B (en) Random access method and communication device
US10849146B2 (en) Method for transmitting data, terminal device and network-side device
CN114731632A (en) Random access method and device
US20210378013A1 (en) Data transmission method and apparatus and communication system
CN114616904A (en) Random access method, device and communication system
CN107484258B (en) Apparatus and method for processing communication with base station
EP3742780A1 (en) Communication method and communication device
WO2020248944A1 (en) Random access method and apparatus
US20220394781A1 (en) Random access method and apparatus and communication system
US20210136834A1 (en) Random Access Method, Terminal Device, and Network Device
WO2018058537A1 (en) Signal transmission method and apparatus
JP7412460B2 (en) Wireless communication method, terminal device and network device
CN113228807B (en) Data transmission method, device and communication system
CN110199565B (en) Random access method, device and storage medium on unlicensed frequency band

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant