CN111406394A - Method and device for transmitting data - Google Patents

Method and device for transmitting data Download PDF

Info

Publication number
CN111406394A
CN111406394A CN201880076835.1A CN201880076835A CN111406394A CN 111406394 A CN111406394 A CN 111406394A CN 201880076835 A CN201880076835 A CN 201880076835A CN 111406394 A CN111406394 A CN 111406394A
Authority
CN
China
Prior art keywords
bwp
channel
data
control channel
transmission
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.)
Pending
Application number
CN201880076835.1A
Other languages
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.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp 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 Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Publication of CN111406394A publication Critical patent/CN111406394A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation

Abstract

The embodiment of the application discloses a method and equipment for transmitting data, which can avoid a data transmission terminal caused by BWP switching, and the method comprises the following steps: the terminal device determines that a first BWP deactivation timer configured on a currently activated first bandwidth part BWP times out between transmission of a control channel received on the first BWP and a data channel indicated by the control channel or times out during transmission of the data channel; the terminal device starts or restarts the first BWP deactivation timer.

Description

Method and device for transmitting data Technical Field
The embodiments of the present application relate to the field of communications, and more particularly, to a method and apparatus for transmitting data.
Background
In a New wireless (NR) system of 5G, a concept of BandWidth Part (BWP) is introduced, and a terminal device may configure multiple BWPs, and activate only one BWP at a time, and the BWP may correspond to one BWP deactivation timer (inactivity timer), and when the BWP deactivation timer expires (or is disabled), the terminal device may switch the currently activated BWP to a default BWP or an initial BWP.
However, if the BWP deactivation timer times out when data transmission is not completed, the BWP switch will interrupt data transmission, and thus a solution to the above problem is needed.
Disclosure of Invention
Embodiments of the present application provide a method and an apparatus for transmitting data, which can avoid interruption of data transmission caused by BWP handover.
In a first aspect, a method for transmitting data is provided, including:
the terminal device determines that a first BWP deactivation timer configured on a currently activated first bandwidth part BWP times out between transmission of a control channel received on the first BWP and a data channel indicated by the control channel or times out during transmission of the data channel;
the terminal device starts or restarts the first BWP deactivation timer.
Therefore, according to the method for transmitting data of the embodiment of the present application, if the BWP deactivation timer expires when the data channel does not start transmission or does not finish transmission, the terminal device starts or restarts the BWP deactivation timer, so that the terminal device can remain on the currently activated BWP to continue data transmission, and data transmission interruption due to BWP switching can be avoided.
In one possible implementation, before the end device restarts the first BWP deactivation timer, the method further includes: the terminal device suspends BWP handover.
In one possible implementation, the data channel is a data transmission scheduled by the control channel.
In a possible implementation manner, the data channel is a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH, and the control channel is a physical downlink control channel PDCCH.
In one possible implementation, the data channel is a repeated data transmission over multiple time units.
In one possible implementation, the method further includes:
the terminal device continues to receive the data channel on the first BWP.
In a second aspect, a method for transmitting data is provided, including:
a terminal device suspends a first BWP deactivation timer configured on a first currently activated bandwidth portion BWP between transmissions of a control channel received on the first BWP and a data channel indicated by the control channel;
the terminal device continues or restarts the first BWP deactivation timer upon completion of the data channel transmission.
Therefore, according to the method for transmitting data of the embodiment of the present application, the terminal device may pause the BWP deactivation timer when the data channel does not start transmission or starts transmission, so that the terminal device may remain on the currently activated BWP to continue data transmission, and thus, interruption of data transmission due to BWP switching can be avoided.
In one possible implementation, the data channel is a data transmission scheduled for the control channel.
In a possible implementation manner, the data channel is a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH, and the control channel is a physical downlink control channel PDCCH.
In one possible implementation, the data channel is a repeated data transmission over multiple time units.
In a third aspect, a method for transmitting data is provided, including:
a terminal device stops performing BWP switching when a first BWP deactivation timer configured on a currently activated first bandwidth part BWP times out between a control channel received on the first BWP and transmission of the data channel indicated by the control channel, or when the time out in the transmission process of the data channel;
and the terminal equipment performs BWP switching under the condition that the data channel transmission is finished.
Therefore, according to the method for transmitting data of the embodiment of the present application, if the BWP deactivation timer expires when the data channel does not start transmission or finish transmission, the terminal device may suspend BWP switching without processing the first BWP deactivation timer, and then continue to transmit the data channel on the first BWP, and perform BWP switching when the data channel finishes transmission, thereby avoiding interruption of data transmission due to BWP switching.
In one possible implementation, the data channel is a data transmission scheduled for the control channel.
In a possible implementation manner, the data channel is a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH, and the control channel is a physical downlink control channel PDCCH.
In one possible implementation, the data channel is a repeated data transmission over multiple time units.
In a fourth aspect, a device for transmitting data is provided, configured to perform the method in the first aspect or any possible implementation manner of the first aspect, or configured to perform the method in the second aspect or any possible implementation manner of the second aspect, or configured to perform the method in any possible implementation manner of the third aspect or any possible implementation manner of the third aspect.
In particular, the apparatus comprises means for performing the method in the first aspect or any possible implementation manner of the first aspect, or means for performing the method in the second aspect or any possible implementation manner of the second aspect, or means for performing the method in any possible implementation manner of the third aspect or any possible implementation manner of the third aspect.
In a fifth aspect, there is provided an apparatus for transmitting data, the apparatus comprising: memory, processor, input interface and output interface. The memory, the processor, the input interface and the output interface are connected through a bus system. The memory is configured to store instructions, and the processor is configured to execute the instructions stored by the memory, to perform the method in the first aspect or any possible implementation manner of the first aspect, or to perform the method in the second aspect or any possible implementation manner of the second aspect, or to perform the method in any possible implementation manner of the third aspect or any possible implementation manner of the third aspect.
A sixth aspect provides a computer storage medium for storing computer software instructions for executing the method of the first aspect or any possible implementation manner of the first aspect, or the method of the second aspect or any possible implementation manner of the second aspect, or the method of the third aspect or any possible implementation manner of the third aspect, and the computer storage medium contains a program designed for executing the above aspects.
In a seventh aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the first aspect or any of the optional implementations of the first aspect, or the method of the second aspect or any of the possible implementations of the second aspect, or the method of the third aspect or any of the possible implementations of the third aspect.
Drawings
Fig. 1 is a schematic diagram of an example of a communication system to which an embodiment of the present application is applied.
Fig. 2 is a schematic flow chart of a method of transmitting data according to an embodiment of the present application.
Fig. 3 is a schematic diagram illustrating an example of a method for transmitting data according to an embodiment of the present application.
Fig. 4 is a schematic diagram of another example of a method for transmitting data according to an embodiment of the present application.
Fig. 5 is a schematic flow chart of a method of transmitting data according to another embodiment of the present application.
Fig. 6 is a schematic diagram illustrating an example of a method for transmitting data according to an embodiment of the present application.
Fig. 7 is a schematic flow chart of a method of transmitting data according to yet another embodiment of the present application.
Fig. 8 is a schematic diagram illustrating an example of a method for transmitting data according to an embodiment of the present application.
Fig. 9 is a schematic diagram of an apparatus for transmitting data according to an embodiment of the present application.
Fig. 10 is a schematic diagram of an apparatus for transmitting data according to another embodiment of the present application.
Fig. 11 is a schematic diagram of an apparatus for transmitting data according to still another embodiment of the present application.
Fig. 12 is a schematic diagram of an apparatus for transmitting data according to an embodiment of the present application.
Detailed Description
The technical solution of the embodiment of the present application can be applied to various communication systems, such as a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a long Term Evolution (L on Term Evolution (L TE) System, a L TE Frequency Division Duplex (FDD) System, a L TE Time Division Duplex (WiMAX), a Universal Mobile Telecommunications System (UMTS) System, a Worldwide Interoperability for Microwave Access (WiMAX) System, or a future communication System, such as a UMTS System.
Fig. 1 illustrates a wireless communication system 100 to which an embodiment of the present invention is applied, the wireless communication system 100 may include a Network device 110, the Network device 100 may be a device that communicates with a terminal device, the Network device 100 may provide communication coverage for a specific geographic area, and may communicate with a terminal device (e.g., UE) located within the coverage area, alternatively, the Network device 100 may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a Base Station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB, or eNodeB) in a L TE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the Network device may be a relay Station, an Access point, a vehicle-mounted device, a wearable device, a Network-side device in a future 5G Network, or a Network device in a future evolved Public land Mobile Network (MN L, L, etc.).
The Wireless communication system 100 also includes at least one terminal device 120 located within the coverage of the network device 110. the terminal device 120 may be mobile or fixed. alternatively, the terminal device 120 may refer to an access terminal, a User Equipment (UE), a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a Wireless communication device, a User agent, or a User Equipment.
In the communication system, a Physical Downlink Control CHannel (Physical Downlink Control CHannel PDCCH) may schedule a Physical Downlink Shared CHannel (PDSCH) for Downlink data transmission, or may schedule a Physical Uplink Shared CHannel (PUSCH) for Uplink data transmission, where a time interval between the PDCCH and the PDSCH is K0, a time interval between the PDCCH and the PUSCH is K2, that is, an interval from the end of PDCCH to the end of PDSCH transmission is K0, and an interval from the end of PDCCH to the end of PUSCH transmission is K2, where a value of K0/K2 may be 32ms at the maximum.
However, the duration of the BWP deactivation timer is usually short, for example, 1ms, 2ms, etc., and if the BWP deactivation timer expires during the transmission of the PDSCH or PUSCH or if the BWP deactivation timer expires when the transmission of the PDSCH or PUSCH is not started (i.e., the BWP deactivation timer is within K0/K2), the terminal device needs to perform BWP handover, which may result in interruption of data transmission.
In view of this, embodiments of the present disclosure provide a method for transmitting data, which can avoid data transmission interruption caused by BWP handover.
Fig. 2 is a schematic flow chart of a method 200 for transmitting data according to an embodiment of the present application, where the method 200 may be performed by a terminal device in the communication system 100 shown in fig. 1, and as shown in fig. 2, the method 200 may include the following steps:
s210, the terminal device determines that a first BWP deactivation timer configured on a currently activated first bandwidth part BWP times out between transmission of a control channel received on the first BWP and a data channel indicated by the control channel, or times out in the transmission process of the data channel;
s220, the terminal device starts or restarts the first BWP deactivation timer.
Generally, when the BWP deactivation timer configured on the currently activated BWP expires (or fails), the terminal device needs to perform BWP switching, that is, switching from the currently activated BWP to a default BWP or an initial BWP, in this case, if the data channel on the currently activated BWP has not been completely transmitted or has not started to be transmitted, or the data transmission on the currently activated BWP has not been completed, performing BWP switching may cause data transmission interruption.
Based on the above technical problem, in the embodiment of the present application, if a BWP deactivation timer configured on a currently activated BWP expires when a data channel has not started transmission (denoted as case 1), or expires between a received control channel and a transmission of the data channel indicated by the control channel (i.e. the data channel has not started transmission) (denoted as case 2), the terminal device starts (start) or restarts (restart) the BWP deactivation timer configured on the BWP, so that the terminal device can remain on the currently activated BWP to continue data transmission, and data transmission interruption due to BWP switching can be avoided.
It should be understood that the duration of the first BWP deactivation timer of the start or restart of the terminal device may be the same as the last time, or may also be different, for example, an initial timer duration, a default timer duration, or the like may be used, which is not limited in this embodiment of the application.
Optionally, in some embodiments, before the end device restarts the first BWP deactivation timer, the method further comprises:
the terminal device suspends BWP handover.
That is, the terminal device may suspend BWP handover in case 1 or case 2, that is, make the currently activated BWP of the terminal device still be the first BWP, and further, the terminal device may perform data channel transmission on the first BWP, so as to avoid data transmission interruption caused by BWP handover.
Optionally, in some embodiments, the data channel is a data transmission scheduled for the control channel.
For example, the data Channel is a Physical Downlink Shared Channel (PDSCH) or a Physical Uplink Shared Channel (PUSCH), and the Control Channel is a Physical Downlink Control Channel (PDCCH), that is, the PDSCH or the PUSCH may be Downlink data transmission or Uplink data transmission scheduled by the PDCCH.
Optionally, in this embodiment of the present application, the data channel is a repeated data transmission over a plurality of time units.
That is, the terminal device may repeatedly transmit the same data over multiple time units, and optionally, the time unit may be one or more time slots, one or more symbols, or the like, which is not limited in this embodiment of the present application.
Hereinafter, embodiments according to the present application will be described in detail with reference to specific examples shown in fig. 3 and 4.
For the embodiment shown in fig. 3, the terminal device may receive a PDCCH including Downlink Control Information (DCI) at a currently activated first BWP, where the DCI is used to indicate a downlink assignment (downlink assignment) or an Uplink grant (Uplink grant), that is, the DCI is used to schedule a PDSCH or a PUSCH, in which case the terminal device may start or restart a first BWP deactivation timer configured on the first BWP, and after receiving the PDCCH, the terminal device may wait to transmit the PDSCH or the PUSCH.
For case 1, if the first BWP deactivation timer expires within a time K0/K2 after the PDCCH, that is, the transmission of the PDSCH or PUSCH has not been started, or the duration of the first BWP deactivation timer is less than K0/K2, the terminal device may start or restart the first BWP deactivation timer, and continue to transmit the PDSCH or PUSCH on the first BWP, which is beneficial to avoid interruption of data transmission due to BWP handover.
For case 2, if the first BWP deactivation timer expires during the transmission of the PDSCH or PUSCH, or the duration of the first BWP deactivation timer is greater than K0/K2 and less than K0/K2+ T, where T is the transmission duration of the PDSCH or PUSCH, the terminal device may start or restart the first BWP deactivation timer, and continue to transmit the PDSCH or PUSCH on the first BWP, which is beneficial to avoiding interruption of data transmission due to BWP handover.
In the embodiment shown in fig. 4, for case 1, if the first BWP deactivation timer expires within a time K0/K2 after the PDCCH, that is, the transmission of the PDSCH or PUSCH has not started, or the duration of the first BWP deactivation timer is less than K0/K2, in this case, the terminal device may suspend BWP handover, and perform transmission of the PDSCH or PUSCH on the first BWP.
Optionally, in this embodiment, the terminal device may start or restart the first BWP deactivation timer when the PDSCH or PUSCH transmission is finished, so as to avoid interruption of data transmission due to BWP handover.
Fig. 5 is a schematic flow chart of a method 300 for transmitting data according to an embodiment of the present application, where the method 300 may be performed by a terminal device in the communication system 100 shown in fig. 1, and as shown in fig. 5, the method 300 may include the following steps:
s310, a terminal device pauses a first bandwidth part (BWP) deactivation timer configured on a first BWP between transmission of a control channel received on the first BWP which is currently activated and a data channel indicated by the control channel;
s320, when the data channel is completely transmitted, the terminal device continues or restarts the first BWP deactivation timer.
Alternatively, the time between the transmission of the control channel received on the currently activated first bandwidth portion BWP and the transmission of the data channel indicated by the control channel may be any time between the control channel and the data channel, for example, the time may be the time when the data channel starts to transmit, or may also be a certain time after the control channel and before the data channel starts to transmit, which is not limited in this embodiment of the application.
That is, the terminal device may pause the first BWP deactivation timer configured on the first BWP when the data channel starts to transmit or before the data channel starts to transmit, and then restart (restart) or continue (resume) the first BWP deactivation timer when the data channel finishes transmitting, so that it is possible to avoid interruption of data transmission due to case 1 or case 2.
It should be understood that, in the embodiment of the present application, the continuing of the first BWP deactivation timer may refer to continuing counting from the count value at which the first BWP deactivation timer is suspended, and the restarting of the first BWP deactivation timer may refer to the count value of the first BWP deactivation timer being counted again from an initial value or a default value.
It is understood that, in this embodiment, the duration of the first BWP deactivation timer may be greater than K0/K2 and less than K0/K2+ T, or the duration of the first BWP deactivation timer may also be less than K0/K2.
Optionally, in some embodiments, the data channel is a data transmission scheduled for the control channel.
Optionally, in some embodiments, the data channel is a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH, and the control channel is a physical downlink control channel PDCCH.
Optionally, in some embodiments, the data channel is a repeated data transmission over multiple time units.
Hereinafter, the embodiments of the present application will be described in detail with reference to a specific example shown in fig. 6.
In fig. 6, a terminal device may receive a PDCCH including DCI at a currently activated first BWP, wherein the DCI is used to schedule a PDSCH or a PUSCH, in which case the terminal device may start or restart a first BWP deactivation timer configured on the first BWP, and the terminal device may wait to transmit the PDSCH or PUSCH after receiving the PDCCH.
In this embodiment, the terminal device may suspend the first BWP deactivation timer at time t, where the time t may be the time when the PDSCH or PUSCH starts transmission, or may also be a time after the PDCCH until the PDSCH or PUSCH starts transmission, that is, the time interval between the time t and the PDCCH may be less than or equal to K0/K2.
Fig. 7 is a schematic flow chart of a method 400 for transmitting data according to an embodiment of the present application, where the method 400 may be performed by a terminal device in the communication system 100 shown in fig. 1, and as shown in fig. 5, the method 400 may include the following steps:
s410, the terminal device stops BWP switching when a first BWP deactivation timer configured on a currently activated first bandwidth part BWP times out between the control channel received on the first BWP and the transmission of the data channel indicated by the control channel, or when the time out in the transmission process of the data channel;
s420, the terminal device performs BWP handover when the data channel transmission is completed.
In this embodiment of the application, in case 1 or case 2, the terminal device may not process the first BWP deactivation timer, but may suspend BWP switching, and then continue data channel transmission on the first BWP, and in case of data channel transmission completion, perform BWP switching, thereby avoiding data transmission interruption caused by BWP switching.
Optionally, in some embodiments, the data channel is a data transmission scheduled for the control channel.
Optionally, in some embodiments, the data channel is a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH, and the control channel is a physical downlink control channel PDCCH.
Optionally, in some embodiments, the data channel is a repeated data transmission over multiple time units.
Hereinafter, the embodiments of the present application will be described in detail with reference to a specific example shown in fig. 8.
In fig. 8, a terminal device may receive a PDCCH including DCI for scheduling a PDSCH or a PUSCH at a currently activated first BWP, in which case the terminal device may start or restart a first BWP deactivation timer configured on the first BWP, and the terminal device may wait for transmission of the PDSCH or PUSCH after receiving the PDCCH.
In this embodiment, if the first BWP deactivation timer expires before PDSCH or PUSCH transmission is started, the terminal device may suspend BWP handover, continue to transmit PDSCH or PUSCH on the first BWP, and perform BWP handover when PDSCH or PUSCH transmission is completed, thereby avoiding interruption of data transmission due to BWP handover.
While method embodiments of the present application are described in detail above with reference to fig. 2-8, apparatus embodiments of the present application are described in detail below with reference to fig. 9-12, it being understood that apparatus embodiments correspond to method embodiments and that similar descriptions may be had with reference to method embodiments.
Fig. 9 shows a schematic block diagram of an apparatus 500 for transmitting data according to an embodiment of the application. As shown in fig. 9, the apparatus 500 includes:
a determining module 510, configured to determine that a first BWP deactivation timer configured on a currently activated first bandwidth part BWP times out between transmission of a control channel received on the first BWP and a data channel indicated by the control channel, or times out during transmission of the data channel;
a control module 520 to start or restart the first BWP deactivation timer.
Optionally, in some embodiments, the control module 520 is further configured to:
suspending BWP switching prior to restarting the first BWP deactivation timer.
Optionally, in some embodiments, the data channel is a data transmission scheduled for the control channel.
Optionally, in some embodiments, the data channel is a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH, and the control channel is a physical downlink control channel PDCCH.
Optionally, in some embodiments, the data channel is a repeated data transmission over multiple time units.
Optionally, in some embodiments, the apparatus 500 further comprises:
a communication module to continue receiving the data channel on the first BWP.
It should be understood that the device 500 for transmitting data according to the embodiment of the present application may correspond to a terminal device in the embodiment of the method of the present application, and the above and other operations and/or functions of each unit in the device 500 are respectively for implementing corresponding flows of the terminal device in the method 200 shown in fig. 2, and are not described herein again for brevity.
Fig. 10 is a schematic block diagram of an apparatus for transmitting data according to an embodiment of the present application. The apparatus 600 of fig. 10 includes:
a control module 610 for suspending a first BWP deactivation timer configured on a first bandwidth portion BWP between a control channel received on the first BWP currently active and a transmission of a data channel indicated by the control channel; and
the terminal device continues or restarts the first BWP deactivation timer upon completion of the data channel transmission.
Optionally, in some embodiments, the data channel is a data transmission scheduled for the control channel.
Optionally, in some embodiments, the data channel is a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH, and the control channel is a physical downlink control channel PDCCH.
Optionally, in some embodiments, the data channel is a repeated data transmission over multiple time units.
Specifically, the device 600 may correspond to (for example, may be configured with or be itself the network device described in the method 300), and each module or unit in the device 600 is respectively configured to execute each action or processing procedure executed by the terminal device in the method 300, and here, detailed descriptions thereof are omitted to avoid redundant description.
Fig. 11 is a schematic block diagram of an apparatus for transmitting data according to an embodiment of the present application. The apparatus 700 of fig. 10 comprises:
a control module 710, configured to time out a first BWP deactivation timer configured on a currently activated first bandwidth part BWP between a control channel received on the first BWP and a transmission of the data channel indicated by the control channel, or in case of time out during the transmission of the data channel, suspend BWP handover; and
and performing BWP switching under the condition that the data channel is transmitted completely.
Optionally, in some embodiments, the data channel is a data transmission scheduled for the control channel.
Optionally, in some embodiments, the data channel is a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH, and the control channel is a physical downlink control channel PDCCH.
Optionally, in some embodiments, the data channel is a repeated data transmission over multiple time units.
Specifically, the device 700 may correspond to (e.g., may be configured to or be the terminal device itself) the terminal device described in the method 400, and each module or unit in the device 700 is respectively configured to execute each action or processing procedure executed by the terminal device in the method 400, and here, a detailed description thereof is omitted to avoid redundancy.
As shown in fig. 12, an embodiment of the present application further provides an apparatus 800 for transmitting data, where the apparatus 800 may be the apparatus 500 in fig. 9, which can be used to execute the content of the terminal apparatus corresponding to the method 200 in fig. 2, or the apparatus 600 in fig. 10, which can be used to execute the content of the terminal apparatus corresponding to the method 300 in fig. 5, and the apparatus 700 in fig. 11, which can be used to execute the content of the terminal apparatus corresponding to the method 400 in fig. 7. The apparatus 800 comprises: an input interface 810, an output interface 820, a processor 830 and a memory 840, the input interface 810, the output interface 820, the processor 830 and the memory 840 being connectable by a bus system. The memory 840 is used to store programs, instructions or code. The processor 830 is configured to execute the program, instructions or codes in the memory 840 to control the input interface 810 to receive signals, control the output interface 820 to transmit signals, and perform the operations of the foregoing method embodiments.
It should be understood that, in the embodiment of the present application, the processor 830 may be a Central Processing Unit (CPU), and the processor 830 may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 840 may include both read-only memory and random access memory and provides instructions and data to the processor 830. A portion of memory 840 may also include non-volatile random access memory. For example, memory 840 may also store device type information.
In implementation, the various aspects of the methods described above may be performed by instructions in the form of hardware, integrated logic circuits, or software in the processor 830. The contents of the method disclosed in connection with the embodiments of the present application may be directly embodied as a hardware processor, or may be implemented by a combination of hardware and software modules in a processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 840, and the processor 830 reads the information in the memory 840 and combines the hardware to implement the above-mentioned method. To avoid repetition, it is not described in detail here.
In a specific embodiment, the communication module included in the apparatus 500 in fig. 9 may be implemented by the output interface 820 and the input interface 810 in fig. 12, and the determination module 510 and the control module 520 included in the apparatus 500 in fig. 9 may be implemented by the processor 830 in fig. 12.
In a specific embodiment, the control module 610 included in the apparatus 600 in fig. 10 can be implemented by the processor 830 in fig. 12.
In a specific embodiment, the control module 710 included in the apparatus 700 in fig. 11 can be implemented by the processor 830 in fig. 12.
Embodiments of the present application also provide a computer-readable storage medium storing one or more programs, the one or more programs including instructions, which when executed by a portable electronic device including a plurality of application programs, enable the portable electronic device to perform the method of the embodiments shown in fig. 2 to 9.
The embodiment of the present application also provides a computer program, which includes instructions, when the computer program is executed by a computer, the computer may execute the corresponding flow of the method of the embodiment shown in fig. 2 to 9.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, 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 functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (28)

  1. A method of transmitting data, comprising:
    the terminal device determines that a first BWP deactivation timer configured on a currently activated first bandwidth part BWP times out between transmission of a control channel received on the first BWP and a data channel indicated by the control channel or times out during transmission of the data channel;
    the terminal device starts or restarts the first BWP deactivation timer.
  2. The method according to claim 1, wherein before the end-device restarts the first BWP deactivation timer, the method further comprises:
    the terminal device suspends BWP handover.
  3. The method according to claim 1 or 2, characterized in that the data channel is a scheduled data transmission for the control channel.
  4. The method according to any one of claims 1 to 3, wherein the data channel is a Physical Downlink Shared Channel (PDSCH) or a Physical Uplink Shared Channel (PUSCH), and the control channel is a Physical Downlink Control Channel (PDCCH).
  5. The method of any of claims 1 to 4, wherein the data channel is a repeated data transmission over a plurality of time units.
  6. The method according to any one of claims 1 to 5, further comprising:
    the terminal device continues to receive the data channel on the first BWP.
  7. A method of transmitting data, comprising:
    a terminal device suspends a first BWP deactivation timer configured on a first currently activated bandwidth portion BWP between transmissions of a control channel received on the first BWP and a data channel indicated by the control channel;
    the terminal device continues or restarts the first BWP deactivation timer upon completion of the data channel transmission.
  8. The method of claim 7, wherein the data channel is a data transmission scheduled for the control channel.
  9. The method according to claim 7 or 8, wherein the data channel is a Physical Downlink Shared Channel (PDSCH) or a Physical Uplink Shared Channel (PUSCH), and the control channel is a Physical Downlink Control Channel (PDCCH).
  10. The method of any of claims 7 to 9, wherein the data channel is a repeated data transmission over a plurality of time units.
  11. A method of transmitting data, comprising:
    a terminal device stops performing BWP switching when a first BWP deactivation timer configured on a currently activated first bandwidth part BWP times out between a control channel received on the first BWP and transmission of the data channel indicated by the control channel, or when the time out in the transmission process of the data channel;
    and the terminal equipment performs BWP switching under the condition that the data channel transmission is finished.
  12. The method of claim 11, wherein the data channel is a data transmission scheduled for the control channel.
  13. The method according to claim 11 or 12, wherein the data channel is a Physical Downlink Shared Channel (PDSCH) or a Physical Uplink Shared Channel (PUSCH), and the control channel is a Physical Downlink Control Channel (PDCCH).
  14. The method of any of claims 11 to 13, wherein the data channel is a repeated data transmission over a plurality of time units.
  15. An apparatus for transmitting data, comprising:
    a determining module for determining that a first BWP deactivation timer configured on a currently activated first bandwidth part BWP times out between transmission of a control channel received on the first BWP and a data channel indicated by the control channel or times out during transmission of the data channel;
    a control module to start or restart the first BWP deactivation timer.
  16. The apparatus of claim 15, wherein the control module is further configured to:
    suspending BWP switching prior to restarting the first BWP deactivation timer.
  17. The apparatus of claim 15 or 16, wherein the data channel is a data transmission scheduled for the control channel.
  18. The apparatus according to any of claims 15-17, wherein the data channel is a physical downlink shared channel, PDSCH, or a physical uplink shared channel, PUSCH, and the control channel is a physical downlink control channel, PDCCH.
  19. The apparatus of any of claims 15-18, wherein the data channel is a repeated data transmission over a plurality of time units.
  20. The apparatus according to any one of claims 15 to 19, further comprising:
    a communication module to continue receiving the data channel on the first BWP.
  21. An apparatus for transmitting data, comprising:
    a control module for suspending a first BWP deactivation timer configured on a first BWP between a transmission of a control channel received on a currently active first bandwidth portion BWP and a data channel indicated by the control channel; and
    the terminal device continues or restarts the first BWP deactivation timer upon completion of the data channel transmission.
  22. The apparatus of claim 21, wherein the data channel is a data transmission scheduled for the control channel.
  23. The apparatus according to claim 21 or 22, wherein the data channel is a Physical Downlink Shared Channel (PDSCH) or a Physical Uplink Shared Channel (PUSCH), and the control channel is a Physical Downlink Control Channel (PDCCH).
  24. The apparatus of any of claims 21 to 23, wherein the data channel is a repeated data transmission over a plurality of time units.
  25. An apparatus for transmitting data, comprising:
    a control module, configured to time out a first BWP deactivation timer configured on a currently activated first bandwidth part BWP between a control channel received on the first BWP and a transmission of the data channel indicated by the control channel, or in case of time out during the transmission of the data channel, suspend BWP handover; and
    and performing BWP switching under the condition that the data channel is transmitted completely.
  26. The apparatus of claim 25, wherein the data channel is a data transmission scheduled for the control channel.
  27. The apparatus according to claim 25 or 26, wherein the data channel is a Physical Downlink Shared Channel (PDSCH) or a Physical Uplink Shared Channel (PUSCH), and the control channel is a Physical Downlink Control Channel (PDCCH).
  28. The apparatus of any of claims 25 to 27, wherein the data channel is a repeated data transmission over a plurality of time units.
CN201880076835.1A 2018-02-12 2018-02-12 Method and device for transmitting data Pending CN111406394A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/076538 WO2019153353A1 (en) 2018-02-12 2018-02-12 Method and device for transmitting data

Publications (1)

Publication Number Publication Date
CN111406394A true CN111406394A (en) 2020-07-10

Family

ID=67547782

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201880076835.1A Pending CN111406394A (en) 2018-02-12 2018-02-12 Method and device for transmitting data

Country Status (2)

Country Link
CN (1) CN111406394A (en)
WO (1) WO2019153353A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023050319A1 (en) * 2021-09-30 2023-04-06 Oppo广东移动通信有限公司 Wireless communication method, terminal device and network device

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113810993A (en) * 2020-06-16 2021-12-17 展讯通信(上海)有限公司 Multicast service data receiving method and communication device

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102104465A (en) * 2010-04-02 2011-06-22 电信科学技术研究院 Carrier deactivation method and equipment
US20110243048A1 (en) * 2010-04-02 2011-10-06 Chun-Yen Wang Method of Handling Component Carrier Activation and Deactivation and Communication Device Thereof
CN102655668A (en) * 2011-03-02 2012-09-05 中兴通讯股份有限公司 Discontinuous receiving method and device
CN103313375A (en) * 2012-03-13 2013-09-18 中兴通讯股份有限公司 Random access method for auxiliary service cell and user equipment (UE)

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101360028B (en) * 2008-07-24 2011-05-25 华中科技大学 Real-time scheduling method suitable for industrial sensor network
CN105099634B (en) * 2014-05-09 2019-05-07 中兴通讯股份有限公司 Distribution method and device, base station, the terminal of dynamic resource
CN105992318B (en) * 2015-02-11 2021-04-06 中兴通讯股份有限公司 Management method of deactivation timer and terminal
KR102450976B1 (en) * 2015-07-31 2022-10-05 삼성전자 주식회사 Apparatus and method for controlling the scell in wireless communication system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102104465A (en) * 2010-04-02 2011-06-22 电信科学技术研究院 Carrier deactivation method and equipment
US20110243048A1 (en) * 2010-04-02 2011-10-06 Chun-Yen Wang Method of Handling Component Carrier Activation and Deactivation and Communication Device Thereof
CN102655668A (en) * 2011-03-02 2012-09-05 中兴通讯股份有限公司 Discontinuous receiving method and device
CN103313375A (en) * 2012-03-13 2013-09-18 中兴通讯股份有限公司 Random access method for auxiliary service cell and user equipment (UE)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023050319A1 (en) * 2021-09-30 2023-04-06 Oppo广东移动通信有限公司 Wireless communication method, terminal device and network device

Also Published As

Publication number Publication date
WO2019153353A1 (en) 2019-08-15

Similar Documents

Publication Publication Date Title
CN110831027B (en) Method and communication device for monitoring physical downlink control channel
CN109644352B (en) Method and terminal equipment for activating and deactivating secondary cell
CN111357311B (en) Data transmission method, terminal equipment and network equipment
US11229036B2 (en) Communication method, terminal device, and network device
CN114143863B (en) Discontinuous reception method, terminal equipment and network equipment
CN109792680B (en) Method and terminal device for transmitting data
CN110495229A (en) Transmit method, terminal device and the network equipment of data
CN110602790A (en) Data sending method and device
CN110199553B (en) Method for transmitting information, terminal equipment and network equipment
CN111418223A (en) Method for managing timer and terminal equipment
CN111406394A (en) Method and device for transmitting data
CN111869288B (en) Method and device for starting timer and terminal
CN113366898A (en) Method and equipment for adjusting PDCCH monitoring period
CN109644329B (en) Method and device for transmitting data
CN115002853B (en) Discontinuous reception processing method and terminal equipment
CN111699751A (en) Wireless communication method of dual-registration terminal equipment, terminal equipment and network equipment
CN110933752B (en) Communication method and device
CN111386724A (en) Wireless communication method for dual-registration terminal equipment, network equipment and terminal equipment
CN113767674B (en) Timer control method and device
CN111314978B (en) Wireless communication method, terminal device, network device, system, chip and storage medium
CN113812181A (en) Method and apparatus for wireless communication
CN114760679B (en) Discontinuous Reception (DRX) configuration switching method, device and terminal
CN112911655B (en) Method for deactivating secondary cell, method and apparatus for indicating deactivation of secondary cell
WO2022236581A1 (en) Method and apparatus for inactivity timer handling
CN110547023A (en) Channel transmission method, terminal equipment and network equipment

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
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20200710