WO2020143383A1 - Procédé et dispositif de transmission de données - Google Patents

Procédé et dispositif de transmission de données Download PDF

Info

Publication number
WO2020143383A1
WO2020143383A1 PCT/CN2019/124536 CN2019124536W WO2020143383A1 WO 2020143383 A1 WO2020143383 A1 WO 2020143383A1 CN 2019124536 W CN2019124536 W CN 2019124536W WO 2020143383 A1 WO2020143383 A1 WO 2020143383A1
Authority
WO
WIPO (PCT)
Prior art keywords
random access
logical channel
uplink
pending
resource
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.)
Ceased
Application number
PCT/CN2019/124536
Other languages
English (en)
Chinese (zh)
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
Publication of WO2020143383A1 publication Critical patent/WO2020143383A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

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

Definitions

  • This application relates to the field of communication technology, and in particular, to a data transmission method and device.
  • 5G wireless communication technology is an extension of the fourth generation (4th Generation, 4G) wireless communication technology. Therefore, the 5G communication system is called “super 4G network", or “Long Term Evolution (LTE) system”, or New Radio (NR).
  • LTE Long Term Evolution
  • NR New Radio
  • the network device can configure multiple logical channels (Logical Channels) for the terminal device.
  • logical channels Logical Channels
  • PUSCH Physical Uplink Shared Channel
  • PUCCH Physical Uplink Control Channel
  • SR scheduling Request
  • the terminal device needs to trigger random access to a special cell (Spcell) to request resources.
  • Spcell Special Cell
  • the terminal device will switch to the initial Initial Uplink BWP for random access , And will switch the Active Downlink (Downlink) DL BWP to Initial Downlink BWP, causing the DL BWP of the terminal device to change;
  • the terminal device will switch the Active DL BWP to On the DL BWP with the same ID as Active UL BWP ID, in the Frequency Division Duplex (FDD) system, since the Active DL BWP ID and Active UL BWP ID are not necessarily the same, it may lead to Active terminal equipment DL BWP changes.
  • FDD Frequency Division Duplex
  • the network device will continue to send on the Active DL BWP before the terminal device switches Downstream data, because the Active DL of the terminal device has changed at this time, the terminal device cannot receive the downlink data, which results in the service on the logical channel being stuck or interrupted.
  • the present application provides a data transmission method and device, which improves the continuity of services on a logical channel during data transmission.
  • an embodiment of the present application provides a data transmission method.
  • the method may include:
  • the first logical channel When the first logical channel triggers pending scheduling request pending SR, obtain uplink resources, where the first logical channel is a logical channel that is not matched with any scheduling request configuration;
  • the terminal device can obtain the uplink resource, and after obtaining the uplink resource, send the first Cache status information of a logical channel, and after confirming that the network device has received the cache status information of the first logical channel, cancel the pending SR triggered on the first logical channel, so that the uplink authorization that can be obtained through non-random access
  • the indicated physical uplink shared channel PUSCH resource sends the buffer status information of the first logical channel, which avoids random access by the terminal device, thereby improving the continuity of services on the logical channel.
  • canceling the pending SR triggered on the first logical channel may include:
  • acquiring uplink resources may include:
  • the uplink grant sent by the network device is received, and the physical uplink shared channel PUSCH resource indicated by the uplink grant is an uplink resource, thereby obtaining the uplink resource.
  • the method before sending the scheduling request to the network device on the physical uplink control channel PUCCH resource corresponding to the scheduling request configuration matching the second logical channel, the method may further include:
  • acquiring uplink resources may include:
  • the configuration authorization Type 1 and/or the configuration authorization type 2 configured authorization sent by the network device Receive the configuration authorization Type 1 and/or the configuration authorization type 2 configured authorization sent by the network device.
  • the physical uplink shared channel PUSCH resource indicated by the configuration authorization is an uplink resource, thereby obtaining the uplink resource.
  • an embodiment of the present application further provides a data transmission method.
  • the method may include:
  • the time-frequency resource and random access preamble for random access are acquired, where the first logical channel is a logical channel that is not matched to any scheduling request configuration ;
  • the buffer state information of the first logical channel is sent according to the reception result, and the random access RA process of the terminal device is optimized to reduce the negative influence of the terminal device on RA and improve the service continuity on the logical channel.
  • the method may further include:
  • sending the buffer status information of the first logical channel according to the reception result may include:
  • the random access third message is sent in the uplink resource indicated by the uplink authorization carried in the random access response message; wherein, the random access third message Carries the buffer status information of the first logical channel.
  • the method may further include:
  • sending the buffer status information of the first logical channel according to the reception result may include:
  • acquiring uplink resources may include:
  • the uplink grant sent by the network device is received, and the physical uplink shared channel PUSCH resource indicated by the uplink grant is an uplink resource.
  • the method before sending the scheduling request to the network device on the physical uplink control channel PUCCH resource corresponding to the scheduling request configuration matching the second logical channel, the method may further include:
  • acquiring uplink resources may include:
  • the configuration authorization Type 1 and/or the configuration authorization type 2 configured authorization sent by the network device is received; where the physical uplink shared channel PUSCH resource indicated by the configuration authorization is an uplink resource.
  • acquiring the time-frequency resource and random access preamble for random access may include:
  • the random access parameter information may include: random access parameter information of the initial uplink bandwidth part, random access parameter information of the activated uplink bandwidth part, or free competition At least one of the random access parameter information;
  • the random access time-frequency resource and the random access preamble are determined according to the random access parameter information.
  • an embodiment of the present application further provides a communication device.
  • the communication device may include:
  • the processing unit is configured to acquire uplink resources when the pending scheduling request pending SR is triggered by the first logical channel, where the first logical channel is a logical channel that 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 also used to cancel the pending SR triggered on the first logical channel.
  • the processing unit is specifically configured to confirm that the network device has received the buffer status information of the first logical channel; and cancel the pending SR triggered on the first logical channel.
  • the device may further include a receiving unit;
  • the sending unit is further configured to send a scheduling request to the network device on the physical uplink control channel PUCCH resource corresponding to the scheduling request configuration matched by the second logical channel;
  • the receiving unit is configured to receive an uplink authorization sent by a network device, and the physical uplink shared channel PUSCH resource indicated by the uplink authorization is an uplink resource.
  • the processing unit is further configured to determine that the second logical channel has triggered pending SR.
  • the receiving unit is further configured to receive the configuration authorization Type 1 and/or the configuration authorization type 2 configured authorization sent by the network device; where the physical uplink shared channel PUSCH indicated by the configuration authorization is configured
  • the resources are uplink resources.
  • an embodiment of the present application further provides a communication device, which may include:
  • the processing unit is configured to obtain a time-frequency resource and a random access preamble for random access when the first logical channel triggers a pending scheduling request pending SR, where the first logical channel is not matched to any scheduling Request the configured logical channel;
  • a sending unit used to send a random access preamble on time-frequency resources
  • the processing unit is also used to determine whether to switch to the downlink bandwidth part DL BWP where the random access response message is located; if it is determined to switch, then switch to the downlink bandwidth where the random access response message is located within the random access response window Part of DL BWP;
  • the receiving unit is used to receive the random access response message corresponding to the random access preamble on the downlink bandwidth part DL BWP;
  • the sending unit is further configured to send the buffer status information of the first logical channel according to the reception result.
  • the processing unit is further configured to determine not to switch to the downlink bandwidth part DL where the random access response message is located if at least one of the following conditions is satisfied;
  • the sending unit is specifically configured to send the uplink resource indication uplink resource indication carried in the random access response message if a random access response message is received on the downlink bandwidth part DL BWP The third random access message; wherein, the third random access message carries buffer status information of the first logical channel.
  • the processing unit is also used to cancel the pending SR triggered on the first logical channel.
  • the processing unit is also used to end the time window indicated by the random access response window ra-ResponseWindow if a random access response message is not received on the downlink bandwidth part DL BWP After that, switch back to the original downlink bandwidth part DL BWP and obtain uplink resources;
  • the sending unit is specifically configured to send the buffer status information of the first logical channel on the uplink resource.
  • the sending unit is specifically configured to send the scheduling request to the network device on the physical uplink control channel PUCCH resource corresponding to the scheduling request configuration matched by the second logical channel;
  • the receiving unit is also used to receive the uplink grant sent by the network device, and the physical uplink shared channel PUSCH resource indicated by the uplink grant is an uplink resource.
  • the processing unit is further configured to determine that the second logical channel has triggered pending SR.
  • the receiving unit is further configured to receive the configuration authorization Type 1 and/or the configuration authorization type 2 configured authorization sent by the network device; where the physical uplink shared channel PUSCH indicated by the configuration authorization is configured
  • the resources are uplink resources.
  • 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: random access parameter information of the initial uplink bandwidth part, activation At least one of random access parameter information in the uplink bandwidth part or free access random access parameter information;
  • the processing unit is specifically used to determine the random access time-frequency resource and the random access preamble according to the random access parameter information.
  • an embodiment of the present application further provides a communication device.
  • the communication device may include a processor and a memory, where,
  • the memory is used 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 the first aspect described above according to the program instructions in the memory, or execute the data transmission method according to any one of the second aspect above.
  • an embodiment of the present application further provides a computer storage medium, which may include instructions, which, when executed by one or more processors, cause the communication device to perform the data transmission method described in any one of the above aspects, Or the data transmission method according to any one of the first aspect above.
  • an embodiment of the present application further provides a chip that stores a computer program on the chip, and when the computer program is executed by a processor, executes the data transmission method described in any one of the first aspects above; or, executes the above The data transmission method shown in any one of the two aspects.
  • the terminal device when the pending scheduling request pending SR is triggered by the first logical channel, the terminal device can acquire the uplink resource, and after acquiring the uplink resource, send the first on the uplink resource Cache status information of the logical channel, and after confirming that the network device has received the cache status information of the first logical channel, cancel the pending SR triggered on the first logical channel, so that the uplink authorization indication that can be obtained through non-random access
  • the physical uplink shared channel PUSCH resource sends the buffer status information of the first logical channel, which avoids random access by the terminal device, thereby improving service continuity on the logical channel.
  • FIG. 1 is a schematic diagram of a system architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a data transmission method provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of another data transmission method provided by an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a communication device according to an embodiment of this application.
  • FIG. 5 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of yet another communication device provided by an embodiment of this application.
  • FIG. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • NR New Radio
  • LTE Long Term Evolution
  • GSM Universal Mobile Telecommunications System
  • UTRAN Universal Mobile Telecommunications System
  • GSM Global System for Mobile Communication
  • EDGE Enhanced Data Rate for GSM Evolution
  • GSM EDGE Radio Access Network GSM EDGE Radio Access Network
  • MME Mobility Management Entity
  • GPRS General Packet Radio Service
  • SGSN Serving GPRS Support Node
  • GGW ⁇ PGW Gateway GPRS Support Node
  • Node, GGSN Gateway GPRS Support
  • Embodiments of the present application relate to terminal equipment.
  • the terminal device is also called a terminal, and can be a device that includes wireless transceiver functions and can cooperate with network devices to provide communication services for users.
  • the terminal may refer to user equipment (User Equipment, UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user Agent or user device.
  • User Equipment User Equipment
  • the terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminals in future 5G networks or networks after 5G, etc., which are not limited in the embodiments of the present application.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the embodiments of the present application also relate to network equipment.
  • the network device may be a device for communicating with the terminal device, for example, it may be a base station (Base Transceiver Station, BTS) in the GSM system or CDMA, or a base station (NodeB, NB) in the WCDMA system, or it may be Evolutionary base station (Evolutional Node B, eNB or eNodeB) in the LTE system, or the network device may be a relay station, an access point, an in-vehicle device, a wearable device, and a network side device in a future 5G network or a network after 5G Network equipment in the public land mobile network (PLMN) that will evolve in the future.
  • BTS Base Transceiver Station
  • NodeB, NB base station
  • Evolutional Node B, eNB or eNodeB Evolutionary base station
  • the network device may be a relay station, an access point, an in-vehicle device, a wearable
  • the network device involved in the embodiments of the present application may also be referred to as a radio access network (Radio Access Network, RAN) device.
  • the RAN device is connected to the terminal, and is used to receive terminal data and send it to the core network device.
  • RAN equipment corresponds to different equipment in different communication systems, for example, corresponds to base stations and base station controllers in 2G systems, corresponds to base stations and radio network controllers (RNC) in 3G systems, and evolves in 4G systems.
  • a type of base station (Evolutional Node B, eNB) corresponds to a 5G system in a 5G system, such as an access network device (eg, gNB, CU, DU) in a new radio access system (New Radio Access Technology, NR).
  • an access network device eg, gNB, CU, DU
  • New Radio Access Technology New Radio Access Technology
  • FIG. 1 is a schematic diagram of a system architecture provided by an embodiment of the present application.
  • the wireless communication system shown in the system architecture may include a core network and an access network.
  • the core network may be NGC/5GC or For EPC
  • the access network may be 5G NR or E-UTRAN.
  • the embodiments of the present application are collectively referred to as a core network and an access network.
  • the access network may include a network device and at least one terminal device.
  • the terminal device may be directly connected to the network device, such as the terminal device 1 shown in FIG. 1.
  • the access network may also include a relay device and a relay connection
  • the terminal device such as terminal device 2 shown in FIG.
  • the relay device may be a relay device or a customer premises equipment (Customer Equipment, Customer Equipment, CPE).
  • the relay device establishes a connection with the network device through link 2.
  • the relay device can also be regarded as a terminal device; the relay device establishes a connection with the user device 2 through link 3, as opposed to the terminal device.
  • the relay device can also be regarded as a network device.
  • the network device can perform data interaction with the terminal device.
  • the terminal device sends the random access preamble Preamble
  • the network device will continue to send downlink data on the Active DL BWP before the terminal device is switched.
  • the terminal device cannot receive the downlink data, which results in the interruption of the service on the logical channel.
  • embodiments of the present application provide a data transmission method, which can improve the continuity of services on the logical channel through at least two possible implementation methods.
  • a first logical channel that is not matched to any scheduling request configuration triggers pending SR.
  • the first logical channel may not need to initiate random access (Random Access, RA), but is physically uplinked through other uplink authorization instructions.
  • the link shared channel PUSCH resource sends the buffer status information of the first logical channel, and cancels the pending (Scheduling Request, SR) of the first logical channel to avoid random access by the terminal device, thereby improving the service of the logical channel Continuity.
  • the terminal device may Determine whether to switch to the downlink bandwidth part DL BWP where the random access response message is located; if it is determined to switch, switch to the downlink bandwidth part DL BWP where the random access response message is located within the random access response window, and then Receive the random access response message corresponding to the random access preamble on the downlink bandwidth part DL BWP, and then send the buffer status information of the first logical channel according to the reception result, thereby optimizing the RA process of the terminal device to make the RA process The negative impact is minimized, thereby improving the continuity of business on the logical channel.
  • FIG. 2 is a schematic diagram of a data transmission method provided by an embodiment of the present application.
  • the data transmission method may include:
  • the terminal device obtains uplink resources.
  • the first logical channel is a logical channel that is not matched to any scheduling request configuration.
  • the first logical channel triggers pending SR when the first logical channel triggers pending SR, it cannot be limited to the moment when the first logical channel triggers pending SR, but can be broadly understood as the first logical channel triggering pending
  • the time of SR and the time period of pending SR after the first logical channel is triggered can be set. As for how long this time period is, it can be set according to actual needs. Here, for the length of this time period, this application is implemented Examples do not make specific restrictions.
  • the uplink resources may be acquired through the following manner 1 and manner 2.
  • a scheduling request can be sent to the network device on the physical uplink control channel PUCCH resource corresponding to the scheduling request configuration matched by the second logical channel; and an uplink authorization sent by the network device and the physical uplink sharing indicated by the uplink authorization can be received
  • the channel PUSCH resource is an uplink resource, so that the uplink resource is obtained.
  • the terminal device can obtain the UL Grant through the SR sent by the second logical channel; of course, the terminal device can also send the first logic through the SR configuration corresponding to other logical channels The SR corresponding to the channel.
  • Method 2 Can receive the configuration authorization type 1 (configured grant Type 1) and/or the configuration authorization type 2 (configured grant Type 2) configuration authorization sent from the network device; the physical uplink shared channel where the authorization indication is configured PUSCH resources are uplink resources.
  • this method 2 when acquiring the uplink resource, it may receive only the configuration authorization of the configuration authorization type 1 sent by the network device, and the physical uplink shared channel PUSCH resource indicated by the configuration authorization type 1 configuration authorization is Uplink resources; can also only receive the uplink authorization of the configuration authorization type 2 sent by the network device, and the physical uplink shared channel PUSCH resource indicated by the configuration authorization type 2 configuration authorization is the uplink resource; of course, it can also receive the The configuration authorization of the configuration authorization type 1 and the configuration authorization type 2; the physical uplink shared channel PUSCH resource indicated by the configuration authorization is an uplink resource, so that the uplink resource is obtained.
  • the configuration authorization may be a semi-static scheduling authorization SPS Grant or an authorization-free uplink authorization Grant-free UL Grant.
  • the buffer status information of the first logical channel can be sent on the uplink resource, that is, the following S202 is executed:
  • the buffer status information on the first logical channel may include uplink data amount information on the first logical channel, and the uplink data amount information is determined according to the uplink data amount on the first logical channel.
  • the determination method can refer to the relevant description in 3GPP TS 38.321.
  • the terminal device can refer to the relevant descriptions in 3GPP TS 38.322 and 3GPP TS 38.323, and details will not be repeated in the embodiments of the present application.
  • the buffer status information on the first logical channel may also be the uplink data volume information of the logical channel group (LCG) where the first logical channel is located, and the uplink data volume information is based on the LCG where the first logical channel is located
  • the determination method can refer to the relevant description in 3GPP TS 38.321.
  • the calculation method of the terminal device can refer to the relevant descriptions in 3GPP TS 38.322 and 3GPP TS 38.323.
  • the embodiments of the present application will not repeat them.
  • the terminal device when the terminal device sends the buffer status information of the first logical channel on the uplink resource, it may send a buffer status report (Buffer Status Report, BSR) on the uplink resource.
  • BSR Buffer Status Report
  • the foregoing buffer status information of the first logical channel may be carried.
  • the BSR sent by the terminal device may be any one of short BSR, Long BSR, Short Truncated BSR, and Long Truncated MAC in BSR format.
  • the format of the BSR is not further limited by the embodiments of the present application.
  • the terminal device confirms that the network device has received the buffer status information of the first logical channel.
  • the terminal device determines that the network device has received the buffer status information of the first logical channel, it may determine in at least two ways. Method 1, if the terminal device does not receive the retransmission indication information of the network device, It means that the network device has received the buffer status information of the first logical channel. Manner 2: If the terminal device receives the confirmation message sent by the network device, it means that the network device has received the buffer status information of the first logical channel.
  • the confirmation message may be a hybrid automatic repeat request confirmation (Hybrid Automatic Repeat Request Acknowledgement, HARQ ACK) message.
  • the terminal device may execute the following S204:
  • the terminal device cancels the pending SR triggered on the first logical channel.
  • the Pending SR triggered by the first logical channel can be cancelled to avoid that the Pending SR triggers the terminal device to initiate random access, thereby avoiding the downlink affecting other logical channels data transmission.
  • the terminal device can obtain the uplink resource, and after obtaining the uplink resource, send the first Cache status information of a logical channel, and after confirming that the network device has received the cache status information of the first logical channel, cancel the pending SR triggered on the first logical channel, so that the uplink authorization that can be obtained through non-random access
  • the indicated physical uplink shared channel PUSCH resource sends the buffer status information of the first logical channel, which avoids random access by the terminal device, thereby improving the continuity of services on the logical channel.
  • FIG. 2 describes in detail a possible implementation manner, if a first logical channel that is not matched with any scheduling request configuration triggers pending SR, and indicates the physical
  • the uplink shared channel PUSCH resource sends the buffer status information of the first logical channel, and then cancels the pending SR of the first logical channel to avoid random access by the terminal device, thereby improving the continuity of services on the logical channel.
  • FIG. 3 which is another example provided by an embodiment of the present application.
  • a schematic diagram of a data transmission method which may include:
  • the terminal device obtains a time-frequency resource and a random access preamble for random access.
  • the first logical channel is a logical channel that is not matched to any scheduling request configuration.
  • the first logical channel triggers pending SR when the first logical channel triggers pending SR, it cannot be limited to the moment when the first logical channel triggers pending SR, but can be broadly understood as the first logical channel trigger Both the moment of pending SR and the time period of pending SR after the first logical channel is triggered, as to how long the time period is, it can be set according to actual needs.
  • this application The embodiment is not specifically limited.
  • the terminal device may receive the random access parameter information sent by the network device, and determine the random access parameter according to the random access parameter information Time-frequency resources and random access preamble.
  • the random access parameter information includes time-frequency resource information for indicating random access and indication information for indicating a random access preamble, where the time-frequency resource information for random access may be a physical random access channel (Physical Random Access Channel, PRACH) time-frequency resource information, the PRACH time-frequency resource information may include PRACH format, period, frame number within the period, subframe number, start symbol, PRACH slot, PRACH transmission opportunity within the slot, Select one or more types of information such as normal uplink (NUL) or supplementary uplink (SUL) transmission; the indication information used to indicate the random access preamble may include generating a random access preamble sequence Root sequence traction, selection set and other information.
  • PRACH Physical Random Access Channel
  • the random access parameter information includes: at least one of initial uplink bandwidth part random access parameter information, activated uplink bandwidth part random access parameter information, or free contention random access parameter information That is, the random access parameter information may include only random access parameter information of the initial uplink bandwidth portion, random access parameter information of the activated uplink bandwidth portion, or free competition random access parameter information.
  • a kind of random access parameter information which may also include any two of random access parameter information of the initial uplink bandwidth portion, random access parameter information of the activated uplink bandwidth portion, or free competition random access parameter information Random access parameter information, of course, may also include the random access parameter information of the initial uplink bandwidth part, the random access parameter information of the activated uplink bandwidth part, and the random access parameter information by competition Random access parameter information.
  • the embodiment of the present application only includes 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 with the random access parameter information At least one of the information is used as an example for description, but it does not mean that the embodiments of the present application are limited to this.
  • the terminal device when the random access parameter information includes random access parameter information of the initial uplink bandwidth part, the terminal device will subsequently send the random access on the PRACH time-frequency resource on the initial uplink bandwidth part Initial Uplink BWP
  • the preamble specifically, when the terminal device is not configured with random access resources on the currently activated uplink bandwidth part Active UL BWP, the terminal device can perform random access on the Initial Uplink BWP.
  • the random access parameter information includes the random access parameter information that activates the uplink bandwidth part
  • the terminal device will subsequently send the random access preamble on the PRACH time-frequency resource on Actvie UL BWP.
  • the terminal device when the terminal device When the frequency division duplex (Frequency Division Division Duplex, FDD) system is used, when the terminal device is configured with random access resources on the current Active UL BWP, the terminal device can perform random access on the current Active UL BWP.
  • the random access parameter information includes free competition random access parameter information, and the terminal device needs to perform random access on the Initial Uplink BWP or Active UL BWP, only the Contention-free random access resource configured on the BWP is used Information for random access.
  • the random access parameter information when the terminal device receives the random access parameter information sent by the network device, the random access parameter information may be carried in the system information, Radio Resource Control (RRC) In the configuration message, or in the system information change instruction message.
  • RRC Radio Resource Control
  • the embodiments of the present application are only described by taking the random access parameter information in the system information, the radio resource control RRC configuration message, or the system information change indication message as examples, but this does not mean that the embodiments of the present application are only Limited to this.
  • the following describes how to obtain the time-frequency resources for 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 instruction message. And random access preamble.
  • the terminal device obtains the random access parameter information by receiving the system information of the network device, and further determines the PRACH resource and the PRACH resource for random access according to the random access parameter information Random access preamble.
  • the network device is an eNB
  • the network device carries the prach-ConfigIndex and prach_FreqOffset fields in the SIB2 message.
  • the terminal device can Each parameter determines the PRACH resource and random access preamble used for random access.
  • the network device For the determination process, refer to relevant technical specifications such as 3GPP TS36.211, 3GPP TS36.213, 3GPP TS 36.321, and so on.
  • the network device When the network device is gNB, the network device carries the BWP-UplinkCommon IE in the SIB1 message, which includes the rach-ConfigCommon IE, which further contains the RACH-ConfigDedicated IE used by the terminal device for random access and other random access.
  • the IE and parameters used at the time of entry such as the parameter prach-RootSequenceIndex used to generate the random access preamble, and the parameters that determine the PRACH time-frequency resource that finally sends the random access preamble, such as prach-ConfigurationIndex, msg1-FrequencyStart Etc., for determining the power of the random access preamble, such as preambleTransMax, powerRampingStep, etc.
  • those skilled in the art can understand that the specific parameters carried in it
  • the terminal device can determine the PRACH resources and random access preamble for random access according to the parameters therein, specifically, the determination process can refer to 3GPP TS38.211, 3GPP TS38. 213, 3GPP TS 38.321 and other related technical specifications. It should be noted that when the network device is configured with SUL, the terminal device may determine to perform random access on NUL or SUL according to the threshold rsrp-ThresholdSSB-SUL sent by the network device, or on the basis of the instruction information of the network device Random access is performed on the SUL.
  • the indication information can be delivered directly by the network device or by another transit network device.
  • the network device when the network device is a secondary cell group (Secondary Cell Group, SCG)
  • the network device of the master cell group (MCG) can send signaling carrying the indication information to the terminal device, or the terminal device determines to perform random access on the NUL or SUL according to its own implementation. Therefore, the available PRACH resources for random access by the terminal device are PRACH time-frequency resources on the NUL or SUL determined by the terminal device.
  • the terminal device When the random access parameter information is carried in the radio resource control RRC configuration message, that is, the terminal device obtains the random access parameter information by receiving the RRC message configuration message of the network device, and further determines the random access parameter according to the parameter information PRACH resources and random access preamble.
  • the network device when the network device is an eNB, the network device carries parameters such as prach-ConfigIndex and prach_FreqOffset in the RRC message.
  • parameters such as prach-ConfigIndex and prach_FreqOffset in the RRC message.
  • the terminal device can The PRACH resources and the random access preamble used for random access are determined according to the parameters therein.
  • the network device can carry the information required by the terminal device for random access in the RRC message used for BWP configuration, for example, by carrying RACH-ConfigCommon IE in BWP-UplinkCommon IE, and in BWP-UPlinkDedicated IE carries beamFailureRecoveryConfigIE, which includes rach-ConfigGenericIE and other parameters; or, the network device carries ReconfigurationWithSyncIE in the RRC message used for ServingCell configuration, which carries rach-ConfigDedicatedIE.
  • RACH-ConfigCommon IE, beamFailureRecoveryConfig IE, rach-ConfigDedicated IE all contain RACH-ConfigDedicated IE and other IEs and parameters used for random access, such as the parameter prach-RootSequenceIndex used to generate the Preamble, determine The parameters of the PRACH time-frequency resources that finally send the random access preamble, such as prach-ConfigurationIndex, msg1-FrequencyStart, etc., parameters used to determine the power to send the Preamble, such as preambleTransMax, powerRampingStep, etc., those skilled in the art can understand , For the specific parameters carried in it, please refer to the relevant description in 3GPP TS38.331.
  • the terminal device can determine the PRACH resource and random access preamble for random access according to the parameters therein, and the determination process can refer to 3GPP TS38.211, 3GPP TS38.213, 3GPP TS 38.321 and other related technical specifications. It should be noted that when the network device is configured with SUL, the terminal device may determine to perform random access on the NUL or SUL according to the threshold rsrp-Threshold SSB-SUL sent by the network device, or on the basis of the instruction information of the network device Or random access on SUL, the indication information can be delivered directly by the network device or by another transit network device.
  • the network device when the network device is an SCG device, it can be sent by the MCG
  • the network device delivers signaling carrying instruction information to the terminal device, or the terminal device determines to perform random access on the NUL or SUL according to its own implementation. Therefore, the available PRACH resources for random access by the terminal device are PRACH time-frequency resources on the NUL or SUL determined by the terminal device.
  • the PRACH resource for transmitting the random access preamble and the random access preamble for random access determined by the terminal device can be used for contention-based random access, or can be a dedicated resource for the terminal device Perform non-contention based random access.
  • the terminal device When the random access parameter information is carried in the system information change instruction message, that is, the terminal device obtains the random access parameter information by receiving the system information change instruction message SI Change Change Indication message sent by the network device, and further determines the random access according to the parameter information
  • SI Change Change Indication message sent by the network device
  • the random access parameter information is carried in the system information or in the radio resource control RRC configuration message.
  • this application The embodiment will not be repeated here.
  • the terminal device sends a random access preamble on the time-frequency resource.
  • the specific sending method can refer to the description in the standard specifications of 3GPP TS38.211, 3GPP TS 38.213 and 3GPP TS 38.321.
  • the embodiments of the present application are not Repeat them again.
  • the method for the terminal device to send the random access preamble may not be limited to the method specified in the above standard specifications.
  • the terminal device may increase the transmission power and power.
  • Backoff and other mechanisms are modified.
  • the embodiments of the present application do not make specific limitations.
  • the terminal device determines whether to switch to the downlink bandwidth part DL BWP where the random access response message is located.
  • the corresponding downlink bandwidth part DL BWP refers to the initial downlink bandwidth part Initial Downlink BWP; when the terminal device is in the current Active BUL
  • the corresponding DL BWP refers to the DL BWP corresponding to the same ID as Active UL BWP ID.
  • the terminal device when determining whether to switch to the downlink bandwidth portion DL BWP where the random access response message is located, there are at least three possible ways to determine:
  • the terminal device can determine whether uplink transmission is required within the time window indicated by the random access response window ra-Response Window.
  • the terminal device can determine whether uplink transmission is required within the time window indicated by the random access response window ra-Response Window.
  • the terminal device can determine whether uplink transmission is required within the time window indicated by the random access response window ra-Response Window.
  • Method 2 The terminal device can determine whether downlink reception is required within the time window indicated by the random access response window ra-Response Window. When there is downlink reception within the time window indicated by the random access response window ra-Response Window, for example, in In this time window, the time window indicated by Configured DL Grant on the original Active DL BWP comes, or, if the terminal device needs to receive downlink HARQ information within the time window, it means that the terminal device needs to be on the current Active DL BWP To prepare for downlink reception, at this time, the terminal device can determine not to switch to the corresponding DL BWP.
  • Method 3 The terminal device can determine whether there is downlink received data in the original downlink bandwidth part before the time window indicated by the random access response window ra-Response Window arrives, and when there is a data in the original downlink bandwidth part before the random access response window
  • the terminal device may determine not to switch to the corresponding DL BWP.
  • the terminal device when determining whether to switch to the downlink bandwidth part DL BWP where the random access response message is located, the terminal device only uses the above three methods as examples for description, but it does not represent The embodiments of the present application are limited to this.
  • the terminal device When determining whether to switch to the downlink bandwidth part DL BWP where the random access response message is located, the terminal device can perform the corresponding operation according to the judgment result, and if determined, determine not to switch to the downlink where the random access response message is located For the bandwidth part DL BWP, the corresponding upstream transmission or downstream reception is completed on the original Actvie UL BWP. Conversely, if it is determined to switch to the downlink bandwidth part DL where the random access response message is located, the following S304 is executed:
  • the terminal device After the judgment in S303, if the terminal device determines that it is necessary to switch to the downlink bandwidth part DL where the random access response message is located, it switches to the corresponding time when the time window indicated by the random access response window ra-Response Window arrives DL BWP, and receive the random access response message corresponding to the random access preamble on the corresponding DL BWP, that is, execute the following S305:
  • the terminal device monitors the random access response message sent by the network device on the downlink bandwidth portion DL BWP where the random access response message is located, and sends the first logic according to whether the random access response message corresponding to the random access preamble is received For channel buffer status information, if a random access response message is received on the downlink bandwidth part DL BWP where the random access response message is located, the following S306 is executed; on the contrary, if the random access response message is located on the downlink If no random access response message is received on the link bandwidth part DL BWP, the following S307-S308 is executed.
  • the terminal device receives the random access response message on the downlink bandwidth part DL BWP where the random access response message is located, the uplink resource indicated by the uplink authorization carried in the random access response message sends the random access Three news.
  • the third random access message carries buffer status information of the first logical channel.
  • the buffer status information on the first logical channel may include uplink data amount information on the first logical channel, the uplink data amount information is determined according to the uplink data amount on the first logical channel, and the uplink data amount information on the first logical channel
  • the determination method can refer to the relevant description in 3GPP TS 38.321.
  • the terminal device when calculating the uplink data amount on the first logical channel, can refer to the relevant descriptions in 3GPP TS 38.322 and 3GPP TS 38.323, and details will not be repeated in the embodiments of the present application.
  • the buffer status information on the first logical channel may also be the uplink data volume information of the LCG where the first logical channel is located.
  • the uplink data volume information is determined according to the uplink data volume of the LCG where the first logical channel is located.
  • the determination method can refer to the relevant description in 3GPP TS 38.321.
  • the calculation method of the terminal device can refer to the relevant descriptions in 3GPP TS 38.322 and 3GPP TS 38.323.
  • the embodiments of the present application will not repeat them.
  • the terminal device receives the random access response message on the downlink bandwidth part DL BWP where the random access response message is located, the uplink resource indicated by the uplink authorization carried in the random access response message is sent with the first logical channel.
  • the terminal device carries the C-RNTI on the time-frequency resource indicated by UL Grant carried in the random access response message RAR to indicate to the network device that it has established an RRC connection.
  • the terminal device when the network device is in TDD mode, when the terminal device performs random access on the current Active UL BWP, there is no need to switch the Active DL BWP. At this time, the terminal device receives the RAR and the UL grant of the SR request. It is on the same DL BWP; when the network device is FDD, when the terminal device performs random access on the current Active BWP, it is necessary to ensure that when receiving the RAR, the downlink Active DL BWP ID and the uplink Active UL The ID of the BWP remains the same. Therefore, it is possible that the DL when the terminal device receives the RAR and the DL BWP of the UL Grant receiving the SR request are not the same DL BWP. In this case, the terminal device can apply this solution.
  • the uplink resources can also be acquired through the following manner 1 and manner 2.
  • a scheduling request can be sent to the network device on the physical uplink control channel PUCCH resource corresponding to the scheduling request configuration matched by the second logical channel; and an uplink authorization sent by the network device and the physical uplink sharing indicated by the uplink authorization can be received
  • the channel PUSCH resource is an uplink resource, so that the uplink resource is obtained.
  • the terminal device can obtain the UL Grant through the SR sent by the second logical channel; of course, the terminal device can also send the first logical channel through the SR configuration corresponding to other logical channels Corresponding SR.
  • Method 2 It can receive the configuration authorization type 1 (configured grant Type 1) and/or configuration authorization type 2 (configured grant Type 2) configuration authorization sent by the network device; where, the physical uplink shared channel PUSCH resource indicated by the configuration authorization It is an uplink resource.
  • this method 2 when acquiring the uplink resource, it may receive only the configuration authorization of the configuration authorization type 1 sent by the network device, and the physical uplink shared channel PUSCH resource indicated by the configuration authorization type 1 configuration authorization is Uplink resources; it can also receive only the configuration authorization type 2 configuration authorization sent by the network device, and the physical uplink shared channel PUSCH resource indicated by the configuration authorization type 2 configuration authorization is an uplink resource; of course, it can also receive the configuration resource sent by the network device
  • the configuration authorization of the configuration authorization type 1 and the configuration authorization type 2; the physical uplink shared channel PUSCH resource indicated by the configuration authorization is an uplink resource, so that the uplink resource is obtained.
  • the configuration authorization may be a semi-static scheduling authorization SPS Grant or an authorization-free uplink authorization Grant-free UL Grant.
  • the buffer status information of the first logical channel can be sent on the uplink resource, that is, the following S308 is executed:
  • the terminal device when the terminal device sends the buffer status information of the first logical channel on the uplink resource, it may send a buffer status report (Buffer Status Report, BSR) on the uplink resource. It may carry the buffer status information of the first logical channel.
  • BSR Buffer Status Report
  • the BSR sent by the terminal device may be any one of short BSR, Long BSR, Short Truncated BSR, and Long Truncated MAC in BSR format.
  • the format of the BSR is not further limited by the embodiments of the present application.
  • the terminal device After the terminal device sends the buffer status information of the first logical channel on the uplink resource, it does not immediately cancel the pending SR triggered on the first logical channel, but after confirming that the network device has received the buffer status information of the first logical channel, Then execute S308 below to cancel the pending SR triggered on the first logical channel. It should be noted that when the terminal device determines that the network device has received the buffer status information of the first logical channel, it may determine in at least two ways. Method 1, if the terminal device does not receive the retransmission indication information of the network device, It means that the network device has received the buffer status information of the first logical channel. Manner 2: If the terminal device receives the confirmation message (for example, HARQ) sent by the network device, it means that the network device has received the buffer status information of the first logical channel.
  • the confirmation message for example, HARQ
  • the terminal device cancels the pending SR triggered on the first logical channel.
  • the Pending SR triggered by the first logical channel can be cancelled to avoid that the Pending SR triggers the terminal device to initiate random access, thereby avoiding the downlink affecting other logical channels data transmission.
  • the terminal device continues to send the Preamble on the available PRACH resource and executes the foregoing steps 303 to 306 Process, until the terminal device obtains the uplink resource in any one of step 307 or step 305 and sends the buffer status information of the first logical channel, the terminal device cancels the Pending triggered SR on the first logical channel.
  • the terminal device when the pending scheduling request pending SR is triggered by the first logical channel, the terminal device first obtains the time-frequency resources and random access preamble for random access, and After obtaining the time-frequency resource and random access preamble, send the random access preamble on the time-frequency resource; then determine whether to switch to the downlink bandwidth part DL BWP where the random access response message is located, if it is determined to switch to random
  • the downlink bandwidth part DL BWP where the access response message is located is switched to the downlink bandwidth part DL BWP where the random access response message is located within the random access response window and received on the downlink bandwidth part DL BWP
  • the random access response message corresponding to the random access preamble; if a random access response message is received on the downlink bandwidth portion DL BWP where the random access response message is located, the uplink authorization carried in the random access response message
  • the indicated uplink resource sends a random access third message, and the random access third message includes the buffer status information of the
  • FIG. 4 is a schematic structural diagram of a communication device 40 according to an embodiment of the present application.
  • the communication device 40 may include:
  • the processing unit 401 is configured to acquire uplink resources when the pending scheduling request pending SR is triggered by the first logical channel, where the first logical channel is a logical channel that is not matched with any scheduling request configuration.
  • the sending unit 402 is configured to send the buffer status information of the first logical channel on the uplink resource.
  • the processing unit 401 is also used to cancel the pending SR triggered on the first logical channel.
  • the processing unit 401 is specifically configured to confirm that the network device has received the buffer status information of the first logical channel; and cancel the pending SR triggered on the first logical channel.
  • the communication device 40 further includes a receiving unit 403.
  • a receiving unit 403. for an example, please refer to FIG. 5, which is a schematic structural diagram of another communication device 40 according to an 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 by the second logical channel.
  • the receiving unit 403 is configured to receive an uplink grant sent by a network device, and the physical uplink shared channel PUSCH resource indicated by the uplink grant is an uplink resource.
  • the processing unit 401 is also used to determine that the second logical channel has triggered pending SR.
  • the receiving unit 403 is further configured to receive the configuration authorization Type 1 and/or the configuration authorization type 2 configured authorization sent by the network device; where the physical uplink shared channel PUSCH resource indicated by the configuration authorization is an uplink resource .
  • the communication device 40 shown in the embodiment of the present application can execute the data transmission method on the terminal device side in the embodiment shown in FIG. 2 above, and the realization principle and beneficial effects of the data transmission method on the terminal device side and the data transmission method on the terminal device side Similarly, no more details will be given here.
  • FIG. 6 is a schematic structural diagram of yet another communication device 60 provided by an embodiment of the present application.
  • the communication device 60 may include:
  • the processing unit 601 is configured to obtain a time-frequency resource and a random access preamble for random access when the first logical channel triggers a pending scheduling request pending SR, wherein the first logical channel is not matched to any The logical channel configured by the scheduling request.
  • the sending unit 602 is configured to send a random access preamble on time-frequency resources.
  • the processing unit 601 is also used to determine whether to switch to the downlink bandwidth part DL BWP where the random access response message is located; if it is determined to switch, then switch to the downlink where the random access response message is located within the random access response window The bandwidth part DL BWP.
  • the receiving unit 603 is configured to receive a random access response message corresponding to a random access preamble on the downlink bandwidth part DL BWP.
  • the sending unit 602 is further configured to send the buffer status information of the first logical channel according to the reception result.
  • the processing unit 601 is further configured to determine not to switch to the downlink bandwidth part DL where the random access response message is located if at least one of the following conditions is satisfied;
  • the sending unit 602 is specifically configured to: if a random access response message is received on the downlink bandwidth part DL BWP, then the uplink resource indicated by the uplink authorization carried in the random access response message sends a random access Three messages; wherein, the random access third message carries the buffer status information of the first logical channel.
  • the processing unit 601 is also used to cancel pending SR triggered on the first logical channel.
  • the processing unit 601 is further configured to switch back to the random access response window ra-Response Window when the random access response message is not received on the downlink bandwidth part DL BWP.
  • the original downlink bandwidth part DL BWP and obtain uplink resources.
  • the sending unit 602 is specifically configured to send the buffer status information of the first logical channel on the uplink resource.
  • 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 by the second logical channel.
  • the receiving unit 603 is further configured to receive an uplink authorization sent by a network device, and the physical uplink shared channel PUSCH resource indicated by the uplink authorization is an uplink resource.
  • processing unit 601 is further configured to determine that the second logical channel has triggered pending SR.
  • the receiving unit 603 is further configured to receive a configuration authorization Type 1 and/or a configuration authorization type 2 configured authorization sent by the network device; where the physical uplink shared channel PUSCH resource indicated by the configuration authorization is an uplink resource .
  • 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: random access parameter information of the initial uplink bandwidth part and activated uplink bandwidth part At least one of random access parameter information or free competition random access parameter information;
  • the processing unit 601 is specifically configured to determine a random access time-frequency resource and a random access preamble according to random access parameter information.
  • the communication device 60 shown in the embodiment of the present application can execute the data transmission method on the terminal device side in the embodiment shown in FIG. 3 above, and the realization principle and beneficial effects of the data transmission method on the terminal device side and the data transmission method on the terminal device side Similarly, no more details will be given here.
  • the communication device 70 may include a processor 701 and a memory 702, where,
  • the memory 702 is used to store program instructions
  • the processor 701 is used to read the program instructions 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 instructions in the memory 702, or execute the embodiment shown in FIG. 3
  • the implementation principle and beneficial effects of the data transmission method on the terminal device side are similar to the implementation principles and beneficial effects of the data transmission method on the terminal device side, and will not be repeated here.
  • An embodiment of the present application further provides a computer storage medium, including instructions, which when executed by one or more processors, cause the communication apparatus to execute the data transmission method on the terminal device side in the embodiment shown in FIG. 2 or execute
  • a computer storage medium including instructions, which when executed by one or more processors, cause the communication apparatus to execute the data transmission method on the terminal device side in the embodiment shown in FIG. 2 or execute
  • the implementation principle and beneficial effects of the data transmission method on the terminal device side are similar to the implementation principles and beneficial effects of the data transmission method on the terminal device side, and will not be repeated here.
  • An embodiment of the present application further provides a chip that stores a computer program, and when the computer program is executed by a processor, executes the data transmission method on the terminal device side in the embodiment shown in FIG. 2 above, or executes the method shown in FIG. 3 above
  • the data transmission method on the terminal device side has implementation principles and beneficial effects similar to those of the data transmission method on the terminal device side, and will not be repeated here.
  • the processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an existing programmable gate array (FPGA) Or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA existing programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application may be implemented or executed.
  • the 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 conjunction with the embodiments of the present application may be directly embodied and executed by a hardware decoding processor, or may be executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory or electrically erasable programmable memory, registers, etc.
  • Storage media The storage medium is located in the memory.
  • the processor reads the instructions in the memory and combines the hardware to complete the steps of the above method.
  • the disclosed device and method may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical, or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware, or in the form of hardware plus software functional units.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente invention portent sur un procédé et un dispositif de transmission de données. Le procédé comprend les étapes suivantes : lorsqu'une demande de programmation (SR) en attente est déclenchée sur un premier canal logique, acquérir une ressource de liaison montante, le premier canal logique étant un canal logique sans aucune configuration de demande de programmation correspondante ; envoyer des informations d'état de mémoire tampon du premier canal logique sur la ressource de liaison montante ; et annuler la SR en attente déclenchée sur le premier canal logique. Dans l'invention, les informations d'état de tampon du premier canal logique peuvent être envoyées sur un canal Partagé de liaison montante physique (PUSCH) ressource indiquée dans une autorisation de liaison montante obtenue au moyen d'un accès non aléatoire, ce qui permet d'empêcher un dispositif terminal d'effectuer un accès aléatoire, ce qui améliore la continuité de service sur le canal logique.
PCT/CN2019/124536 2019-01-10 2019-12-11 Procédé et dispositif de transmission de données Ceased WO2020143383A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910022428.9 2019-01-10
CN201910022428.9A CN111432432B (zh) 2019-01-10 2019-01-10 数据传输方法和设备

Publications (1)

Publication Number Publication Date
WO2020143383A1 true WO2020143383A1 (fr) 2020-07-16

Family

ID=71520843

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/124536 Ceased WO2020143383A1 (fr) 2019-01-10 2019-12-11 Procédé et dispositif de transmission de données

Country Status (2)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114245473A (zh) * 2020-09-09 2022-03-25 成都鼎桥通信技术有限公司 随机接入的方法、装置、电子设备及存储介质

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114339617B (zh) * 2020-10-09 2023-07-04 成都鼎桥通信技术有限公司 Nr小区中mbs资源的配置使用方法及装置
WO2022126577A1 (fr) * 2020-12-18 2022-06-23 Qualcomm Incorporated Obtention de ressources de liaison montante pour un canal logique sans configuration de demande de planification associée

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180324635A1 (en) * 2017-05-04 2018-11-08 Ofinno Technologies, Llc Scheduling request in a wireless device and wireless network
CN108811099A (zh) * 2017-05-03 2018-11-13 华为技术有限公司 上行传输资源的调度方法和设备
CN109392175A (zh) * 2017-08-11 2019-02-26 华为技术有限公司 调度请求的发送方法、调度请求的处理方法及相关设备

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20060105304A (ko) * 2005-04-04 2006-10-11 삼성전자주식회사 이동통신 시스템에서 스케줄링을 효율적으로 하는 방법 및장치
US10200991B2 (en) * 2016-04-25 2019-02-05 Ofinno Technologies, Llc Scheduling request process in a wireless device and wireless network
US10491363B2 (en) * 2016-05-24 2019-11-26 Lg Electronics Inc. Method for transmitting a data in a communication system and device therefor
CN109156025B (zh) * 2017-04-27 2022-02-15 北京小米移动软件有限公司 上行资源获取方法、装置及计算机可读存储介质
CN108811146B (zh) * 2017-05-04 2020-08-28 维沃移动通信有限公司 上行调度请求处理方法及装置
US10524294B2 (en) * 2017-05-04 2019-12-31 Ofinno, Llc Scheduling request transmission
US10785802B2 (en) * 2017-05-05 2020-09-22 Motorola Mobility Llc Transmitting SR prior to completing RACH
CN108811152B (zh) * 2017-05-05 2024-01-02 华为技术有限公司 资源申请方法及设备
KR102055061B1 (ko) * 2017-06-08 2019-12-11 아서스테크 컴퓨터 인코포레이션 무선 통신 시스템에서의 다중 sr (scheduling request) 구성의 방법 및 장치
JP2020524439A (ja) * 2017-06-15 2020-08-13 コンヴィーダ ワイヤレス， エルエルシー スケジューリングリクエスト、状態報告、および論理チャネル優先順位付け
CN109152025B (zh) * 2017-06-16 2024-04-26 华为技术有限公司 通信方法、终端及基站

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108811099A (zh) * 2017-05-03 2018-11-13 华为技术有限公司 上行传输资源的调度方法和设备
US20180324635A1 (en) * 2017-05-04 2018-11-08 Ofinno Technologies, Llc Scheduling request in a wireless device and wireless network
CN109392175A (zh) * 2017-08-11 2019-02-26 华为技术有限公司 调度请求的发送方法、调度请求的处理方法及相关设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "Further Considerations on RACH Related BWP Issues", R2-1801815, 3GPP TSG-RAN2 #101, 2 March 2018 (2018-03-02), XP051400051 *
LENOVO ET AL.: "Scheduling Request Procedure", R2-1800681, 3GPP TSG-RAN WG2 NR AH#1, 26 January 2018 (2018-01-26), XP051385804 *
SAMSUNG ELECTRONICS R&D INSTITUE UK: "Outstanding Issues with SR Design for NR and TP for TS 38.321", R2-1712284, 3GPP TSG-RAN WG2 #100, 1 December 2017 (2017-12-01), XP051370890 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114245473A (zh) * 2020-09-09 2022-03-25 成都鼎桥通信技术有限公司 随机接入的方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN111432432B (zh) 2022-04-22
CN111432432A (zh) 2020-07-17

Similar Documents

Publication Publication Date Title
KR100980919B1 (ko) 랜덤 액세스 절차의 실패를 검출하는 방법
CN111869306B (zh) 随机接入的方法、终端设备和网络设备
EP3432674B1 (fr) Procédés de transmission de données
US20210212112A1 (en) Method and apparatus for processing lbt monitoring failures and system
CN109076600B (zh) 一种随机接入的通信方法、终端和基站
JP7703828B2 (ja) 上りリンク信号の送受信方法及び装置
WO2020191637A1 (fr) Procédé d'accès aléatoire, dispositif terminal et dispositif de réseau
WO2020186546A1 (fr) Procédé et dispositif d'accès aléatoire
WO2016183705A1 (fr) Procédé et appareil pour transmettre des données de liaison montante dans un système d'accès assisté par licence
CN114342465B (zh) 无线通信的方法和终端设备
CN109155951B (zh) 传输方法、基站和终端
CN112352462B (zh) 竞争窗口调整方法、装置以及通信系统
EP3001751B1 (fr) Procédé de transmission de données dans un réseau local sans fil, équipement d'utilisateur et point d'accès
JP2024545327A (ja) 伝送決定方法、装置、端末、ネットワーク側機器及び記憶媒体
CN114731632A (zh) 一种随机接入的方法和装置
US9426826B1 (en) Contention resolution for an orthogonal frequency-division multiplexing wireless access node
CN116647932A (zh) 物理上行控制信道传输的方法、终端设备和网络设备
WO2020215330A1 (fr) Procédé de transmission de données dans un processus d'accès aléatoire, dispositif terminal, et dispositif de réseau
CN109792785B (zh) 用于竞争随机接入的方法、网络设备和终端设备
WO2020143383A1 (fr) Procédé et dispositif de transmission de données
US12108458B2 (en) Method of random access, terminal device, and non-transitory computer-readable storage medium
CN112997574B (zh) 随机接入的方法、终端设备和网络设备
WO2020024616A1 (fr) Procédé d'accès aléatoire et dispositif associé
US12457159B2 (en) Delay performance evaluation method and apparatus, and storage medium
US12389260B2 (en) Delay performance evaluation method and apparatus, and storage medium

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19909438

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19909438

Country of ref document: EP

Kind code of ref document: A1