CN108023685B - Hybrid automatic repeat request HARQ (hybrid automatic repeat request) switching method and terminal - Google Patents

Hybrid automatic repeat request HARQ (hybrid automatic repeat request) switching method and terminal Download PDF

Info

Publication number
CN108023685B
CN108023685B CN201610974563.XA CN201610974563A CN108023685B CN 108023685 B CN108023685 B CN 108023685B CN 201610974563 A CN201610974563 A CN 201610974563A CN 108023685 B CN108023685 B CN 108023685B
Authority
CN
China
Prior art keywords
harq
harq process
asynchronous
synchronous
terminal
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.)
Active
Application number
CN201610974563.XA
Other languages
Chinese (zh)
Other versions
CN108023685A (en
Inventor
杨育波
刘蕾
周国华
赵毅男
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201610974563.XA priority Critical patent/CN108023685B/en
Publication of CN108023685A publication Critical patent/CN108023685A/en
Application granted granted Critical
Publication of CN108023685B publication Critical patent/CN108023685B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607Details of the supervisory signal
    • H04L1/1671Details of the supervisory signal the supervisory signal being transmitted together with control information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829Arrangements specially adapted for the receiver end

Landscapes

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

Abstract

The embodiment of the invention provides a hybrid automatic repeat request HARQ switching method and a terminal, wherein the method comprises the following steps: a terminal acquires a switching instruction, wherein the switching instruction is used for indicating switching from a synchronous HARQ to an asynchronous HARQ; the terminal switches from the synchronous HARQ to the asynchronous HARQ according to the switching indication; and the terminal maps the HARQ process identifier corresponding to the synchronous HARQ into the HARQ process identifier corresponding to the asynchronous HARQ. The method further comprises the following steps: a terminal acquires a switching instruction, wherein the switching instruction is used for indicating switching from asynchronous HARQ to synchronous HARQ; the terminal switches from asynchronous HARQ to synchronous HARQ according to the switching indication; and the terminal maps the HARQ process identifier corresponding to the asynchronous HARQ into the HARQ process identifier corresponding to the synchronous HARQ. The method can ensure the correctness of the HARQ switching result.

Description

Hybrid automatic repeat request HARQ (hybrid automatic repeat request) switching method and terminal
Technical Field
The present invention relates to communications technologies, and in particular, to a method and a terminal for HARQ switching.
Background
Enhanced Voice LTE (Enhanced Voice LTE, abbreviated to ewlte) supports uplink Hybrid Automatic Retransmission (HARQ) transmission. The HARQ transmission may use a synchronous HARQ transmission or may use an asynchronous HARQ transmission. When a terminal carries out voice communication and moves from an area with better coverage to an area with relatively weaker coverage, the terminal needs to switch from asynchronous HARQ to synchronous HARQ; on the contrary, when the terminal moves from the area with weaker coverage to the area with stronger coverage, the handover from the synchronous HARQ to the asynchronous HARQ needs to be performed.
Therefore, it is necessary to provide a reasonable HARQ handover method to ensure the accuracy of the HARQ handover result.
Disclosure of Invention
The embodiment of the invention provides a hybrid automatic repeat request (HARQ) switching method and a terminal, which are used for providing the HARQ switching method capable of ensuring the accuracy.
A first aspect of an embodiment of the present invention provides a HARQ switching method, where the method includes:
a terminal acquires a switching instruction, wherein the switching instruction is used for indicating switching from a synchronous HARQ to an asynchronous HARQ;
the terminal switches from the synchronous HARQ to the asynchronous HARQ according to the switching indication;
and the terminal maps the HARQ process identifier corresponding to the synchronous HARQ into the HARQ process identifier corresponding to the asynchronous HARQ.
In one possible design, the obtaining, by the terminal, a handover indication includes:
the terminal blindly detects downlink control information DCI in a user specific search space USS;
and if the DCI carrying the HARQ process identifier is detected in a blind mode, the terminal determines to acquire the switching indication.
In one possible design, the mapping, by the terminal, the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ includes:
if the transmission mode is a frequency division duplex FDD mode, the terminal maps the HARQ process identification corresponding to the synchronous HARQ into the HARQ process identification corresponding to the asynchronous HARQ according to a frame number, a subframe number and the number of the maximum parallel HARQ processes which can be supported;
and if the transmission mode is a Time Division Duplex (TDD) mode, the terminal maps the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ according to the frame number, the number of the supportable maximum parallel HARQ processes, the total number of Physical Uplink Shared Channels (PUSCHs) in each frame and the identifier of the PUSCHs.
In a possible design, if the transmission mode is the FDD mode, the mapping, by the terminal, the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ according to a frame number, a subframe number, and a number of HARQ processes that can support the maximum parallel HARQ includes:
if the transmission mode is the conventional HARQ, the terminal uses a formula (10 x FN + i)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is FDD shortest transmission interval TTI binding, the terminal uses a formula floor ((10 × FN + i% 16)/4)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in an FDD TTI binding transmission mode;
if the transmission mode is the enhanced FDD TTI binding, the terminal uses a formula floor ((10 × FN + i% 12)/4)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is the frame number, i is the subframe number of the first subframe in the TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the enhanced FDD TTI binding transmission mode.
In a possible design, if the transmission mode is the TDD mode, the terminal maps, according to a frame number, a number of maximum parallel HARQ processes that can be supported, a total number of physical uplink shared channels, PUSCHs, in each frame, and an identifier of the PUSCH, an HARQ process identifier corresponding to the synchronous HARQ to an HARQ process identifier corresponding to the asynchronous HARQ, including:
if the transmission mode is the conventional HARQ, the terminal uses a formula (N × FN + i)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the index of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is TDD TTI binding and the TDD ratio is 0, the terminal uses a formula floor ((N × FN + i% 14)/4)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the index of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the TDD TTI binding transmission mode;
if the transmission mode is TDD TTI bundling and the TDD ratio is 0 or 6, the terminal performs mapping of HARQ process identification corresponding to the synchronous HARQ to HARQ process identification corresponding to the asynchronous HARQ using a formula floor ((N × FN + i)/4)% HARQ process number, where FN is a frame number, N is a total number of PUSCHs in each frame, i is an identification of N PUSCHs, and HARQ process number is a maximum number of parallel HARQ processes that can be supported in the TDD TTI bundling transmission mode.
In one possible design, the mapping, by the terminal, the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ includes:
the terminal acquires a synchronous HARQ process identifier corresponding to a subframe where the DCI carrying the HARQ process identifier is located and is subjected to blind detection;
and the terminal maps the synchronous HARQ process identifier to the HARQ process identifier contained in the DCI carrying the HARQ process identifier.
In one possible design, the mapping, by the terminal, the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ includes:
and the terminal judges whether all the synchronous HARQ processes are finished, if so, the terminal uses the scheduling resources of the base station to carry out asynchronous HARQ transmission, wherein the identification of the asynchronous HARQ process is the HARQ process identification corresponding to the DCI carrying the HARQ process identification.
In one possible design, after the terminal obtains the handover indication, the method includes:
terminating all HARQ processes;
and carrying out asynchronous HARQ transmission by using the scheduling resource of the base station.
In one possible design, the mapping, by the terminal, the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ includes:
the terminal receives a connection reconfiguration RRC indication, wherein the RRC indication carries a frame number, a subframe number and an HARQ process identifier;
and the terminal uses the scheduling resource of the base station to carry out asynchronous HARQ transmission according to the RRC indication.
A second aspect of the present invention provides a HARQ switching method, where the method includes:
the base station determines whether to switch from synchronous HARQ to asynchronous HARQ;
and if so, the base station sends a switching instruction to the terminal, wherein the switching instruction is used for indicating the synchronous HARQ to be switched to the asynchronous HARQ.
In one possible design, the base station sending a handover indication to the terminal includes:
and the base station sends DCI to the terminal, wherein the DCI carries the switched asynchronous HARQ process identifier so that the terminal acquires a switching indication according to the asynchronous HARQ process identifier.
A third aspect of the embodiments of the present invention provides a HARQ switching method, where the method includes:
a terminal acquires a switching instruction, wherein the switching instruction is used for indicating switching from asynchronous HARQ to synchronous HARQ;
the terminal switches from asynchronous HARQ to synchronous HARQ according to the switching indication;
and the terminal maps the HARQ process identifier corresponding to the asynchronous HARQ into the HARQ process identifier corresponding to the synchronous HARQ.
In one possible design, the obtaining, by the terminal, a handover indication includes:
the terminal blindly detects downlink control information DCI in the USS;
and if the DCI with the format of 0 or 4 is detected in a blind mode, the terminal determines to acquire the switching indication.
In one possible design, the mapping, by the terminal, the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ includes:
if the transmission mode is the FDD mode, the terminal maps the HARQ process identifier corresponding to the asynchronous HARQ into the HARQ process identifier corresponding to the synchronous HARQ according to a frame number, a subframe number and the number of the maximum parallel HARQ processes which can be supported;
and if the transmission mode is a TDD mode, the terminal maps the HARQ process identifier corresponding to the asynchronous HARQ into the HARQ process identifier corresponding to the synchronous HARQ according to the frame number, the number of the supportable maximum parallel HARQ processes, the total number of Physical Uplink Shared Channels (PUSCHs) in each frame and the identifier of the PUSCHs.
In a possible design, if the transmission mode is the FDD mode, the mapping, by the terminal, the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ according to a frame number, a subframe number, and a number of HARQ processes that can support the maximum parallel HARQ includes:
if the transmission mode is the conventional HARQ, the terminal uses a formula (10 x FN + i)% HARQ process number to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the conventional HARQ transmission mode;
if the transmission mode is FDD TTI binding, the terminal uses a formula floor ((10 × FN + i% 16)/4)% HARQ process number) to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the FDD TTI binding transmission mode;
if the transmission mode is the enhanced FDD TTI binding, the terminal uses a formula floor ((10 × FN + i% 12)/4)% HARQ process number) to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is the frame number, i is the subframe number of the first subframe in the TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the enhanced FDD TTI binding transmission mode.
In a possible design, if the transmission mode is the TDD mode, the terminal maps, according to a frame number, a number of maximum parallel HARQ processes that can be supported, a total number of physical uplink shared channels, PUSCHs, in each frame, and an identifier of the PUSCH, an HARQ process identifier corresponding to the asynchronous HARQ to an HARQ process identifier corresponding to the synchronous HARQ, including:
if the transmission mode is the conventional HARQ, the terminal uses a formula (N × FN + i)% HARQ process number to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the identifier of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is TDD TTI binding and the TDD ratio is 0, the terminal uses a formula floor ((N × FN + i% 14)/4)% HARQ process number to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the identifier of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes that can be supported in the TDD TTI binding transmission mode;
if the transmission mode is TDD TTI bundling and the TDD ratio is 0 or 6, the terminal performs mapping of HARQ process identifiers corresponding to the asynchronous HARQ to HARQ process identifiers corresponding to the synchronous HARQ using a formula floor ((N × FN + i)/4)% HARQ process number, where FN is a frame number, N is a total number of PUSCHs in each frame, i is an identifier of N PUSCHs, and HARQ process number is a maximum number of parallel HARQ processes that can be supported in the TDD TTI bundling transmission mode.
In one possible design, after the terminal obtains the handover indication, the method includes:
terminating all HARQ processes;
and performing synchronous HARQ transmission by using the scheduling resource of the base station.
A fourth aspect of the present invention provides a HARQ switching method, including:
the base station determines whether to switch from asynchronous HARQ to synchronous HARQ;
and if so, the base station sends a switching instruction to the terminal, wherein the switching instruction is used for indicating the switching from the asynchronous HARQ to the synchronous HARQ.
In one possible design, the base station sending a handover indication to the terminal includes:
and the base station sends DCI to the terminal, wherein the format of the DCI is 0 or 4, so that the terminal acquires a switching indication according to the format of the DCI.
A fifth aspect of the present invention provides an HARQ switching apparatus, including:
a receiving module, configured to obtain a handover indication, where the handover indication is used to indicate a handover from a synchronous HARQ to an asynchronous HARQ;
a processing module, configured to switch from a synchronous HARQ to an asynchronous HARQ according to the switching indication;
the processing module is further configured to map the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ.
In one possible design, the receiving module is specifically configured to:
blind detecting downlink control information DCI in the USS; and if the DCI carrying the HARQ process identifier is detected in a blind mode, the terminal determines to acquire the switching indication.
In one possible design, the processing module is specifically configured to:
if the transmission mode is the FDD mode, mapping the HARQ process identifier corresponding to the synchronous HARQ into the HARQ process identifier corresponding to the asynchronous HARQ according to a frame number, a subframe number and the number of the maximum parallel HARQ processes which can be supported;
and if the transmission mode is a TDD mode, mapping the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ according to a frame number, the number of the supportable maximum parallel HARQ processes, the total number of the PUSCHs in each frame and the identifier of the PUSCHs.
In one possible design, the processing module is further specifically configured to:
if the transmission mode is the conventional HARQ, using a formula (10 x FN + i)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is FDD shortest transmission interval TTI binding, using a formula (10 x FN + i% 16)/4)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in an FDD TTI binding transmission mode;
if the transmission mode is the enhanced FDD TTI binding, a formula floor ((10 × FN + i% 12)/4)% HARQ process number) is used for mapping the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in the TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the enhanced FDD TTI binding transmission mode.
In one possible design, the processing module is further specifically configured to:
if the transmission mode is the conventional HARQ, using a formula (N × FN + i)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the index of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is TDD TTI binding and the TDD ratio is 0, using a formula floor ((N × FN + i% 14)/4)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the index of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the TDD TTI binding transmission mode;
if the transmission mode is TDD TTI binding and the TDD ratio is 0 or 6, using a formula floor ((N × FN + i)/4)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is the frame number, N is the total number of PUSCHs in each frame, i is the identification of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes that can be supported in the TDD TTI binding transmission mode.
In one possible design, the processing module is further specifically configured to:
acquiring a synchronous HARQ process identifier corresponding to a subframe where the DCI carrying the HARQ process identifier is located and subjected to blind detection;
and mapping the synchronous HARQ process identifier to the HARQ process identifier contained in the DCI carrying the HARQ process identifier.
In one possible design, the processing module is further specifically configured to:
and judging whether all synchronous HARQ processes are finished, if so, using scheduling resources of a base station to carry out asynchronous HARQ transmission, wherein the identifier of the asynchronous HARQ process is the HARQ process identifier corresponding to the DCI carrying the HARQ process identifier.
In one possible design, the processing module is further specifically configured to:
terminating all HARQ processes;
and carrying out asynchronous HARQ transmission by using the scheduling resource of the base station.
In one possible design, the processing module is further specifically configured to:
receiving a connection reconfiguration RRC indication, wherein the RRC indication carries a frame number, a subframe number and an HARQ process identifier;
and according to the RRC indication, using the scheduling resource of the base station to carry out asynchronous HARQ transmission.
In a sixth aspect of the embodiments of the present invention, there is provided an HARQ switching apparatus, including:
a processing module for determining whether to switch from synchronous HARQ to asynchronous HARQ;
and the sending module is used for sending a switching instruction to the terminal if the terminal is in the idle state, wherein the switching instruction is used for indicating the synchronous HARQ to be switched to the asynchronous HARQ.
In one possible design, the sending module is specifically configured to:
and sending DCI to a terminal, wherein the DCI carries the switched asynchronous HARQ process identifier so that the terminal acquires a switching indication according to the asynchronous HARQ process identifier.
A seventh aspect of the present invention provides an HARQ switching apparatus, including:
a receiving module, configured to obtain a handover indication, where the handover indication is used to indicate a handover from an asynchronous HARQ to a synchronous HARQ;
a processing module, configured to switch from asynchronous HARQ to synchronous HARQ according to the switching indication;
the processing module is further configured to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ.
In one possible design, the receiving module is specifically configured to:
blind detecting downlink control information DCI in the USS;
and if the DCI with the format of 0 or 4 is detected in a blind mode, the terminal determines to acquire the switching indication.
In one possible design, the processing module is specifically configured to:
if the transmission mode is the FDD mode, mapping the HARQ process identifier corresponding to the asynchronous HARQ into the HARQ process identifier corresponding to the synchronous HARQ according to a frame number, a subframe number and the number of the maximum parallel HARQ processes which can be supported;
and if the transmission mode is a TDD mode, mapping the HARQ process identifier corresponding to the asynchronous HARQ into the HARQ process identifier corresponding to the synchronous HARQ according to a frame number, the number of the supportable maximum parallel HARQ processes, the total number of the PUSCHs in each frame and the identifier of the PUSCHs.
In one possible design, the processing module is further specifically configured to:
if the transmission mode is the conventional HARQ, using a formula (10 x FN + i)% HARQ process number to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is FDD TTI binding, using a formula floor ((10 × FN + i% 16)/4)% HARQ process number) to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the FDD TTI binding transmission mode;
if the transmission mode is the enhanced FDD TTI binding, a formula floor ((10 × FN + i% 12)/4)% HARQ process number) is used for mapping the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in the TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the enhanced FDD TTI binding transmission mode.
In one possible design, the processing module is further specifically configured to:
if the transmission mode is the conventional HARQ, mapping HARQ process identifications corresponding to the asynchronous HARQ to HARQ process identifications corresponding to the synchronous HARQ by using a formula (N × FN + i)% HARQ process number, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the identifications of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is TDD TTI binding and the TDD ratio is 0, using a formula floor ((N × FN + i% 14)/4)% HARQ process number to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the identifier of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the TDD TTI binding transmission mode;
if the transmission mode is TDD TTI binding and the TDD ratio is 0 or 6, using a formula floor ((N × FN + i)/4)% HARQ process number to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is the frame number, N is the total number of PUSCHs in each frame, i is the identifier of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes that can be supported in the TDD TTI binding transmission mode.
In one possible design, the processing module is further specifically configured to:
terminating all HARQ processes;
and performing synchronous HARQ transmission by using the scheduling resource of the base station.
An eighth aspect of the present invention provides an HARQ switching apparatus, including:
a processing module for determining whether to switch from asynchronous HARQ to synchronous HARQ;
and the sending module is used for sending a switching instruction to the terminal if the terminal is in the idle state, wherein the switching instruction is used for indicating the asynchronous HARQ to be switched to the synchronous HARQ.
In one possible design, the sending module is specifically configured to:
and sending DCI to a terminal, wherein the format of the DCI is 0 or 4, so that the terminal acquires a switching indication according to the format of the DCI.
In a ninth aspect of the embodiments of the present invention, a terminal is provided, including:
a memory and a processor.
The memorizer is used for storing program instructions, and the processor is used for calling the program instructions in the memorizer and executing the following method:
acquiring a switching indication, wherein the switching indication is used for indicating switching from a synchronous HARQ to an asynchronous HARQ;
switching from synchronous HARQ to asynchronous HARQ according to the switching indication;
and mapping the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ.
In one possible design, the processor is specifically configured to:
blind detecting downlink control information DCI in the USS;
and if the DCI carrying the HARQ process identifier is detected in a blind mode, determining to acquire the switching indication.
In one possible design, the processor is further specifically configured to:
if the transmission mode is the FDD mode, mapping the HARQ process identifier corresponding to the synchronous HARQ into the HARQ process identifier corresponding to the asynchronous HARQ according to a frame number, a subframe number and the number of the maximum parallel HARQ processes which can be supported;
and if the transmission mode is a TDD mode, mapping the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ according to a frame number, the number of the supportable maximum parallel HARQ processes, the total number of the PUSCHs in each frame and the identifier of the PUSCHs.
In one possible design, if the transmission mode is an FDD mode, the processor is further specifically configured to:
if the transmission mode is the conventional HARQ, using a formula (10 x FN + i)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is FDD shortest transmission interval TTI binding, using a formula (10 x FN + i% 16)/4)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in an FDD TTI binding transmission mode;
if the transmission mode is the enhanced FDD TTI binding, a formula floor ((10 × FN + i% 12)/4)% HARQ process number) is used for mapping the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in the TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the enhanced FDD TTI binding transmission mode.
In one possible design, if the transmission mode is the TDD mode, the processor is further specifically configured to:
if the transmission mode is the conventional HARQ, using a formula (N × FN + i)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the index of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is TDD TTI binding and the TDD ratio is 0, using a formula floor ((N × FN + i% 14)/4)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the index of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the TDD TTI binding transmission mode;
if the transmission mode is TDD TTI binding and the TDD ratio is 0 or 6, using a formula floor ((N × FN + i)/4)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is the frame number, N is the total number of PUSCHs in each frame, i is the identification of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes that can be supported in the TDD TTI binding transmission mode.
In one possible design, the processor is further specifically configured to:
acquiring a synchronous HARQ process identifier corresponding to a subframe where the DCI carrying the HARQ process identifier is located and subjected to blind detection;
and mapping the synchronous HARQ process identifier to the HARQ process identifier contained in the DCI carrying the HARQ process identifier.
In one possible design, the processor is further specifically configured to:
and judging whether all synchronous HARQ processes are finished, if so, using scheduling resources of a base station to carry out asynchronous HARQ transmission, wherein the identifier of the asynchronous HARQ process is the HARQ process identifier corresponding to the DCI carrying the HARQ process identifier.
In one possible design, the processor is further to:
terminating all HARQ processes;
and carrying out asynchronous HARQ transmission by using the scheduling resource of the base station.
In one possible design, the processor is further to:
receiving a connection reconfiguration RRC indication, wherein the RRC indication carries a frame number, a subframe number and an HARQ process identifier;
and according to the RRC indication, using the scheduling resource of the base station to carry out asynchronous HARQ transmission.
In a tenth aspect of the embodiments of the present invention, there is provided a base station, including:
a memory and a processor.
The memorizer is used for storing program instructions, and the processor is used for calling the program instructions in the memorizer and executing the following method:
determining whether to switch from synchronous HARQ to asynchronous HARQ;
and if so, sending a switching instruction to the terminal, wherein the switching instruction is used for indicating the synchronous HARQ to be switched to the asynchronous HARQ.
In one possible design, the processor is specifically configured to:
and sending DCI to a terminal, wherein the DCI carries the switched asynchronous HARQ process identifier so that the terminal acquires a switching indication according to the asynchronous HARQ process identifier.
In an eleventh aspect of the embodiments of the present invention, there is provided a terminal, including:
a memory and a processor.
The memorizer is used for storing program instructions, and the processor is used for calling the program instructions in the memorizer and executing the following method:
acquiring a switching indication, wherein the switching indication is used for indicating switching from asynchronous HARQ to synchronous HARQ;
switching from asynchronous HARQ to synchronous HARQ according to the switching indication;
and mapping the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ.
In one possible design, the processor is specifically configured to:
blind detecting downlink control information DCI in the USS;
and if the DCI with the format of 0 or 4 is detected in a blind mode, determining to acquire the switching indication.
In one possible design, the processor is further specifically configured to:
if the transmission mode is the FDD mode, mapping the HARQ process identifier corresponding to the asynchronous HARQ into the HARQ process identifier corresponding to the synchronous HARQ according to a frame number, a subframe number and the number of the maximum parallel HARQ processes which can be supported;
and if the transmission mode is a TDD mode, mapping the HARQ process identifier corresponding to the asynchronous HARQ into the HARQ process identifier corresponding to the synchronous HARQ according to a frame number, the number of the supportable maximum parallel HARQ processes, the total number of the PUSCHs in each frame and the identifier of the PUSCHs.
In one possible design, if the transmission mode is the FDD mode, the processor is further specifically configured to:
if the transmission mode is the conventional HARQ, using a formula (10 x FN + i)% HARQ process number to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is FDD TTI binding, using a formula floor ((10 × FN + i% 16)/4)% HARQ process number) to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the FDD TTI binding transmission mode;
if the transmission mode is the enhanced FDD TTI binding, a formula floor ((10 × FN + i% 12)/4)% HARQ process number) is used for mapping the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in the TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the enhanced FDD TTI binding transmission mode.
In one possible design, if the transmission mode is the TDD mode, the processor is further specifically configured to:
if the transmission mode is the conventional HARQ, mapping HARQ process identifications corresponding to the asynchronous HARQ to HARQ process identifications corresponding to the synchronous HARQ by using a formula (N × FN + i)% HARQ process number, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the identifications of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is TDD TTI binding and the TDD ratio is 0, using a formula floor ((N × FN + i% 14)/4)% HARQ process number to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the identifier of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the TDD TTI binding transmission mode;
if the transmission mode is TDD TTI binding and the TDD ratio is 0 or 6, using a formula floor ((N × FN + i)/4)% HARQ process number to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is the frame number, N is the total number of PUSCHs in each frame, i is the identifier of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes that can be supported in the TDD TTI binding transmission mode.
In one possible design, the processor is further to:
terminating all HARQ processes;
and performing synchronous HARQ transmission by using the scheduling resource of the base station.
In a twelfth aspect of the embodiments of the present invention, there is provided a base station, including:
a memory and a processor.
The memorizer is used for storing program instructions, and the processor is used for calling the program instructions in the memorizer and executing the following method:
determining whether to switch from asynchronous HARQ to synchronous HARQ;
and if so, sending a switching instruction to the terminal, wherein the switching instruction is used for indicating the switching from the asynchronous HARQ to the synchronous HARQ.
In one possible design, the processor is specifically configured to:
and sending DCI to a terminal, wherein the format of the DCI is 0 or 4, so that the terminal acquires a switching indication according to the format of the DCI.
The scheme provided by the embodiment can ensure the accuracy of the switching result.
Drawings
In order to more clearly illustrate the technical solutions of the present invention or the prior art, the following briefly introduces the drawings needed to be used in the description of the embodiments or the prior art, and obviously, the drawings in the following description are some embodiments of the present invention, and those skilled in the art can obtain other drawings according to the drawings without inventive labor.
Fig. 1 is an interactive flowchart of switching from synchronous HARQ to asynchronous HARQ according to a first embodiment of the present invention;
fig. 2 is a flowchart illustrating a second embodiment of switching from synchronous HARQ to asynchronous HARQ according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating a third embodiment of switching from synchronous HARQ to asynchronous HARQ according to the present invention;
fig. 4 is a flowchart illustrating a fourth embodiment of switching from synchronous HARQ to asynchronous HARQ according to the present invention;
fig. 5 is an interaction flowchart of switching from the asynchronous HARQ to the synchronous HARQ according to a first embodiment of the present invention;
fig. 6 is a flowchart illustrating a second embodiment of switching from asynchronous HARQ to synchronous HARQ according to an embodiment of the present invention;
fig. 7 is a block diagram of a HARQ switching apparatus according to a first embodiment of the present invention;
fig. 8 is a block diagram of a HARQ switching apparatus according to a first embodiment of the present invention;
fig. 9 is a block diagram of a HARQ switching apparatus according to a first embodiment of the present invention;
fig. 10 is a block diagram of a HARQ switching apparatus according to a first embodiment of the present invention;
fig. 11 is a block diagram of a first terminal according to a first embodiment of the present invention;
fig. 12 is a block diagram of a base station according to a first embodiment of the present invention;
fig. 13 is a block diagram of a first terminal according to a first embodiment of the present invention;
fig. 14 is a block diagram of a base station according to a first embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
For synchronous HARQ, the terminal can directly derive the identification of the synchronous HARQ process from the subframe number and the timing relation specified in the protocol without explicitly sending the identification of the HARQ process. For asynchronous HARQ, the base station needs to explicitly send the HARQ process id when sending the scheduling information.
Therefore, for synchronous HARQ, the base station and the terminal need to maintain one HARQ process group, and each HARQ process is determined by the set timing relationship. For asynchronous HARQ, the HARQ process identities of the base station and the terminal for the current uplink transmission need to be kept consistent, i.e. for a particular HARQ process, the base station and the terminal need to understand consistent.
When the synchronous HARQ is switched to the asynchronous HARQ, the base station needs to indicate the current HARQ process identifier in order to keep the terminal and the base station understanding the same for the HARQ process identifier. When the asynchronous HARQ is switched to the synchronous HARQ, although the base station and the terminal maintain the HARQ process group, the terminal still needs to determine the corresponding relationship between the HARQ process that is not completed by transmission and the original asynchronous HARQ process.
Based on the above processes, the embodiments of the present invention provide a HARQ switching method, which can accurately map HARQ process identifiers in the process of switching from a synchronous HARQ to an asynchronous HARQ and from an asynchronous HARQ to a synchronous HARQ, thereby ensuring normal execution of the HARQ and asynchronous switching processes.
Fig. 1 is an interactive flowchart of switching from a synchronous HARQ to an asynchronous HARQ according to a first embodiment of the present invention, and as shown in fig. 1, the method includes:
s101, the base station determines whether to switch from the synchronous HARQ to the asynchronous HARQ, if so, S102 is executed, otherwise, the following steps are not executed.
For example, when the base station recognizes that the terminal moves from an area with weak coverage to an area with strong coverage, it is determined that the terminal can be switched from synchronous HARQ to asynchronous HARQ.
S102, the base station sends a switching instruction to the terminal, and the switching instruction is used for indicating the switching from the synchronous HARQ to the asynchronous HARQ.
Alternatively, the base station may transmit the handover indication using Downlink Control Information (DCI) or through Connection Reconfiguration (RRC), which will be described in detail below.
S103, the terminal obtains the switching instruction and switches from the synchronous HARQ to the asynchronous HARQ according to the switching instruction.
And after the terminal acquires the switching instruction, switching from the synchronous HARQ to the asynchronous HARQ according to the switching instruction.
S104, the terminal maps the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ.
Alternatively, the terminal may perform mapping from the synchronous HARQ process identifier to the asynchronous HARQ process identifier by using a formula mapping, a timing mapping, and the like, which will be described in detail below.
In this embodiment, after acquiring the handover instruction sent by the base station, the terminal first completes the handover from the synchronous HARQ to the asynchronous HARQ, and then the terminal maps the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ, thereby ensuring normal execution of the HARQ synchronous to asynchronous handover process.
In an optional embodiment, a specific method for the terminal to obtain the handover indication in S103 is as follows:
the terminal blindly detects DCI in a user Specific Search Space (USS for short), and if the terminal blindly detects DCI carrying HARQ process identification, the terminal determines to acquire the switching indication.
That is, if the terminal blindly detects DCI carrying the HARQ process identifier, it indicates that the base station has instructed to switch from the synchronous HARQ to the asynchronous HARQ, and the HARQ process identifier carried in the blindly detected DCI is the asynchronous HARQ process identifier to which the base station switches.
Correspondingly, when the base station sends the switching instruction to the terminal in step S102, the DCI may be sent to the terminal, where the DCI carries the switched asynchronous HARQ process identifier, so that the terminal obtains the switching instruction according to the asynchronous HARQ process identifier.
Several alternative embodiments of step S104 are described below:
the first mode is as follows: formula calculation implementing mapping
If the transmission mode is a Frequency Division Duplex (FDD) mode, the terminal maps the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ according to the frame number, the subframe number, and the number of HARQ processes that can support the maximum parallel HARQ.
If the transmission mode is a Time Division Duplex (TDD) mode, the terminal maps the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ according to a frame number, the number of maximum parallel HARQ processes that can be supported, a total number of Physical Uplink Shared Channels (PUSCHs) in each frame, and an identifier of the PUSCH.
The frame may be a system frame or a radio frame.
The specific calculation formula is as follows:
FDD transmission mode:
1. conventional harq (normal harq) transmission:
(10*FN+i)%HARQ process number
wherein, FN is frame number, i is subframe number, and HARQ process number is the maximum number of parallel HARQ processes that can be supported under Normal HARQ transmission mode.
It should be noted that the FN is the frame number of the system frame, the range of the conventional system frame number is 0 to 1023, and the system frame is counted from 0 again when the system frame is 1025 th frame. Thus, the FN is defined by the formula:
Figure BDA0001143010300000191
hereinafter, the meaning and definition of FN are the same as those of FN, and are not described in detail.
And the i is the subframe number and has a value range of 0-9.
The HARQ process number is a maximum number of parallel HARQ processes that can be supported in the Normal HARQ transmission scheme, and specifically, the maximum number of parallel HARQ processes that can be supported in the Normal HARQ transmission scheme is 8.
2. FDD TTI bundling transmission scheme:
floor((10*FN+i%16)/4)%HARQ process number
the TTI is an abbreviation of a shortest Transmission Time Interval (Transmission Time Interval).
The FN is a frame number, i is a subframe number of a first subframe in TTI bundling, and the HARQ process number is the number of the maximum parallel HARQ processes which can be supported in an FDD TTI bundling transmission mode.
"16" in the formula indicates that loop Time delay (RTT) of FDD TTI bundling is 16 ms.
The HARQ process number is a maximum number of parallel HARQ processes that can be supported in an FDD TTI bundling transmission mode, and specifically, the maximum number of parallel HARQ processes that can be supported in the FDD TTI bundling transmission mode is 4.
In addition, the floor () in the formula is a floor function, and the floor () in the following formula represents the same meaning and is not described again.
3. Enhanced FDD TTI bundling transmission scheme:
floor((10*FN+i%12)/4)%HARQ process number
the method comprises the steps that FN is a frame number, i is a subframe number of a first subframe in TTI bundling, and HARQ process number is the number of the maximum parallel HARQ processes which can be supported in an Enhanced FDD TTI bundling transmission mode.
"12" in this equation indicates that the RTT of the Enhanced FDD TTI bundling is 12 ms.
The HARQ process number is a maximum number of parallel HARQ processes that can be supported in an Enhanced FDD TTI bundling transmission mode, and specifically, the maximum number of parallel HARQ processes that can be supported in the Enhanced FDD TTI bundling transmission mode is 3.
TDD transmission mode:
1. normal HARQ transmission scheme:
(N*FN+i)%HARQ process number
the FN is a frame number, N is the total number of PUSCHs in each frame, i is the index of the N PUSCHs, and the HARQ process number is the number of the maximum parallel HARQ processes which can be supported under a Normal HARQ transmission mode.
The value range of the i is 0-N-1.
The HARQ process number has different values in different TDD configurations, which may be specifically shown in table 1:
TABLE 1
Figure BDA0001143010300000201
2. TDD TTI bundling transmission scheme:
(1) the TDD ratio is 0:
floor((N*FN+i%14)/4)%HARQ process number
the FN is a frame number, N is the total number of PUSCHs in each frame, i is the index of the N PUSCHs, and the HARQ process number is the number of the maximum parallel HARQ processes which can be supported in a TDD TTI bundling transmission mode.
The value range of the i is 0-N-1.
Referring to table 1, the HARQ process number in this formula has a value of 3.
(2) The TDD ratio is 1 or 6:
floor((N*FN+i)/4)%HARQ process number
the FN is a frame number, N is the total number of PUSCHs in each frame, i is the identification of the N PUSCHs, and the HARQ process number is the maximum number of parallel HARQ processes which can be supported under the TDD TTI bundling transmission mode.
The value range of the i is 0-N-1.
Referring to table 1, when the TDD ratio is 1, the HARQ process number in the formula has a value of 2; when the TDD ratio is 6, the HARQ process number in this formula has a value of 3.
The second mode is as follows: timing mapping
Fig. 2 is a schematic flow chart of an embodiment two of switching from synchronous HARQ to asynchronous HARQ provided in the embodiment of the present invention, and as shown in fig. 2, a specific process of implementing the step S104 by timing mapping includes:
s201, the terminal acquires the synchronous HARQ process identification corresponding to the subframe where the DCI carrying the HARQ process identification is located and is subjected to blind detection.
S202, the terminal maps the synchronous HARQ process identification to the HARQ process identification contained in the DCI carrying the HARQ process identification.
For example, suppose that the terminal receives DCI containing HARQ process identifier (assuming that the process identifier is n) on subframe k, if in the original synchronous HARQ, the control signaling received by subframe k corresponds to HARQ process m maintained by the terminal, and after switching to asynchronous HARQ, HARQ process m is mapped to HARQ process n in the DCI for the terminal.
The third mode is as follows: asynchronous HARQ transmission after synchronous HARQ process is finished
And the terminal judges whether all the synchronous HARQ processes are finished, and if so, the terminal uses the scheduling resources of the base station to carry out asynchronous HARQ transmission.
The identifier of the asynchronous HARQ process for carrying out asynchronous HARQ transmission is the HARQ process identifier corresponding to the DCI carrying the HARQ process identifier, and the base station side and the terminal side keep consistent understanding of the HARQ process identifier in the asynchronous HARQ transmission.
That is, in the present embodiment, after all the synchronous HARQ processes are finished, the new process uses asynchronous HARQ transmission.
Specifically, in the process of performing synchronous HARQ transmission, once an HARQ process receives an ACK in a subframe corresponding to the HARQ process, the terminal determines that the HARQ process has ended, and if all HARQ processes in the terminal are finished, the subsequent HARQ transmission all uses asynchronous transmission, and the process identifier of the asynchronous HARQ uses the process identifier carried in the DCI, so as to ensure that the base station side and the terminal side keep consistent understanding of the HARQ process identifier in the asynchronous HARQ transmission.
The fourth mode is that: terminating HARQ processes
Fig. 3 is a schematic flow chart of a third embodiment of switching from synchronous HARQ to asynchronous HARQ according to an embodiment of the present invention, and as shown in fig. 3, a specific process of implementing the step S104 by terminating the HARQ process includes:
s301, all HARQ processes are terminated.
S302, asynchronous HARQ transmission is carried out by using scheduling resources of the base station.
Specifically, after the terminal acquires the DCI containing the HARQ process identifier, it is determined that the base station has switched to the asynchronous HARQ transmission, the terminal terminates all HARQ processes running on the terminal, and performs the asynchronous HARQ transmission using the scheduling resource of the base station, that is, the HARQ process identifier carried in the DCI is used as the HARQ process identifier on the terminal side, and the newly scheduled HARQ process is the asynchronous HARQ process.
The fifth mode is as follows: RRC indicating mode
Fig. 4 is a schematic flow chart of a fourth embodiment of switching from synchronous HARQ to asynchronous HARQ according to the embodiment of the present invention, and as shown in fig. 4, the specific process of implementing the step S104 by RRC indication includes:
s401, the terminal receives an RRC indication, wherein the RRC indication carries a frame number, a subframe number and an HARQ process identifier.
S402, the terminal uses the scheduling resource of the base station to carry out asynchronous HARQ transmission according to the RRC indication.
Fig. 5 is an interaction flowchart of switching from asynchronous HARQ to synchronous HARQ according to a first embodiment of the present invention, and as shown in fig. 5, the method includes:
s501, the base station determines whether to switch from asynchronous HARQ to synchronous HARQ, if so, S502 is executed, otherwise, the following steps are not executed.
For example, when the base station recognizes that the terminal moves from an area with better coverage to an area with relatively weaker coverage, it is determined that the handover from asynchronous HARQ to synchronous HARQ is possible for the terminal.
S502, the base station sends a switching instruction to the terminal, and the switching instruction is used for indicating the switching from the synchronous HARQ to the asynchronous HARQ.
Alternatively, the base station may transmit the handover indication using DCI, which will be described in detail below.
S503, the terminal acquires the switching indication and switches from the asynchronous HARQ to the synchronous HARQ according to the switching indication.
And after the terminal acquires the switching instruction, switching from the asynchronous HARQ to the synchronous HARQ according to the switching instruction.
S504, the terminal maps the HARQ process identification corresponding to the asynchronous HARQ into the HARQ process identification corresponding to the synchronous HARQ.
Alternatively, the terminal may perform mapping from the asynchronous HARQ process identifier to the synchronous HARQ process identifier by using a formula mapping or the like, which will be described in detail below.
In this embodiment, after acquiring the handover instruction sent by the base station, the terminal first completes the handover from the asynchronous HARQ to the synchronous HARQ, and then the terminal maps the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, thereby ensuring normal execution of the HARQ asynchronous to synchronous handover process.
In an optional embodiment, a specific method for the terminal to obtain the handover indication in S503 is as follows:
and the terminal blindly detects the DCI in the USS, and if the terminal blindly detects the DCI with the format of 0 or 4, the terminal determines to acquire the switching indication.
That is, if the terminal blindly detects DCI of format 0 or 4, it indicates that the base station has instructed switching from asynchronous HARQ to synchronous HARQ.
Accordingly, when the base station sends the handover instruction to the terminal in step S502, the base station may send DCI to the terminal, where the DCI format is 0 or 4, so that the terminal acquires the handover instruction according to the DCI format.
Two alternative embodiments of step S504 are described below:
the first mode is as follows: formula calculation implementing mapping
If the transmission mode is the FDD mode, the terminal maps the HARQ process identifier corresponding to the asynchronous HARQ into the HARQ process identifier corresponding to the synchronous HARQ according to the frame number, the subframe number and the number of the maximum parallel HARQ processes which can be supported.
If the transmission mode is TDD mode, the terminal maps the HARQ process identification corresponding to asynchronous HARQ to the HARQ process identification corresponding to synchronous HARQ according to the frame number, the number of the maximum parallel HARQ processes which can be supported, the total number of PUSCHs in each frame and the identification of the PUSCH.
The specific calculation formula in the different transmission modes is the same as the formula for switching from the synchronous HARQ to the asynchronous HARQ, and the formula for switching from the synchronous HARQ to the asynchronous HARQ may be referred to, which is not described herein again. However, it is to be noted that the foregoing formula is used in the present embodiment to implement the handover from the synchronous HARQ to the asynchronous HARQ, that is, compared to the foregoing embodiment, although the calculation formula is the same, the role thereof is not the same.
It should be noted that, when the formula mapping is used to implement mapping from the asynchronous HARQ process identifier to the synchronous HARQ process identifier, it is necessary to terminate part of the HARQ processes when the number of the parallel HARQ processes is too large.
The concrete description is as follows:
referring to the above formula mapping method, the maximum number of parallel HARQ processes that can be supported in various synchronous HARQ transmissions is 8, i.e. the Normal HARQ transmission method of FDD. While the number of parallel HARQ processes in an asynchronous HARQ transmission may be greater than 8. Therefore, if the number of parallel HARQ processes in the asynchronous HARQ transmission is greater than 8, a partial HARQ process needs to be terminated during the handover from the asynchronous HARQ to the synchronous HARQ.
Alternatively, the following two ways may be used for discarding:
1. terminating the asynchronous HARQ process identifies asynchronous HARQ processes greater than 7.
2. The mapping of the asynchronous HARQ process identification to the synchronous HARQ process identification is performed only for asynchronous HARQ processes that need to be retransmitted.
The above process can be summarized as follows:
if the number of the parallel asynchronous HARQ is more than 8, the asynchronous HARQ process with the asynchronous HARQ process identification more than 7 is stopped, or the mapping from the asynchronous HARQ process identification to the synchronous HARQ process identification is only executed for the asynchronous HARQ process needing to be retransmitted.
The second mode is as follows: terminating HARQ processes
Fig. 6 is a flowchart illustrating an embodiment two of switching asynchronous HARQ to synchronous HARQ provided in the embodiment of the present invention, and as shown in fig. 6, a specific process of implementing the step S504 by terminating the HARQ process includes:
s601, terminating all HARQ processes.
S602, synchronous HARQ transmission is carried out by using the scheduling resource of the base station.
Specifically, after the terminal acquires the DCI with the format 0 or 4, it determines that the base station has switched to synchronous HARQ transmission, and terminates all HARQ processes running thereon, and performs synchronous HARQ transmission using the scheduling resource of the base station.
It should be noted that, if the terminal blindly detects DCI carrying the HARQ process identifier in the USS and blindly detects DCI with format 0 or 4 in Common Search Space (CSS), the UE determines that synchronous HARQ and asynchronous HARQ currently exist simultaneously, and distinguishes synchronous HARQ and asynchronous HARQ through the USS and CSS.
The above process can be summarized as follows:
and if the DCI carrying the HARQ process identifier is detected in the USS in a blind mode and the DCI with the format of 0 or 4 is detected in the CSS in a blind mode, the terminal determines that the synchronous HARQ and the asynchronous HARQ exist at the same time.
Fig. 7 is a block diagram of a first embodiment of an HARQ switching apparatus according to an embodiment of the present invention, and as shown in fig. 7, the apparatus includes:
a receiving module 701, configured to obtain a handover indication, where the handover indication is used to indicate a handover from a synchronous HARQ to an asynchronous HARQ.
A processing module 702, configured to switch from the synchronous HARQ to the asynchronous HARQ according to the switching indication.
The processing module 702 is further configured to map the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ.
The device is used for realizing the method embodiments, the realization principle and the technical effect are similar, and the details are not repeated here.
In another embodiment, the receiving module 701 is specifically configured to:
blind detecting DCI in the USS; and if the DCI carrying the HARQ process identifier is detected in a blind mode, determining to acquire the switching indication.
In another embodiment, the processing module 702 is specifically configured to:
if the transmission mode is the FDD mode, mapping the HARQ process identifier corresponding to the synchronous HARQ into the HARQ process identifier corresponding to the asynchronous HARQ according to a frame number, a subframe number and the number of the maximum parallel HARQ processes which can be supported; and if the transmission mode is a TDD mode, mapping the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ according to a frame number, the number of the supportable maximum parallel HARQ processes, the total number of the PUSCHs in each frame and the identifier of the PUSCHs.
In another embodiment, the processing module 702 is further specifically configured to:
if the transmission mode is the conventional HARQ, using a formula (10 x FN + i)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is FDD TTI binding, using a formula floor ((10 × FN + i% 16)/4)% HARQ process number) to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the FDD TTI binding transmission mode;
if the transmission mode is the enhanced FDD TTI binding, a formula floor ((10 × FN + i% 12)/4)% HARQ process number) is used for mapping the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in the TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the enhanced FDD TTI binding transmission mode.
In another embodiment, the processing module 702 is further specifically configured to:
if the transmission mode is the conventional HARQ, using a formula (N × FN + i)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the index of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is TDD TTI binding and the TDD ratio is 0, using a formula floor ((N × FN + i% 14)/4)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the index of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the TDD TTI binding transmission mode;
if the transmission mode is TDD TTI binding and the TDD ratio is 0 or 6, using a formula floor ((N × FN + i)/4)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is the frame number, N is the total number of PUSCHs in each frame, i is the identification of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes that can be supported in the TDD TTI binding transmission mode.
In another embodiment, the processing module 702 is further specifically configured to:
acquiring a synchronous HARQ process identifier corresponding to a subframe where the DCI carrying the HARQ process identifier is located and subjected to blind detection; and mapping the synchronous HARQ process identifier to the HARQ process identifier contained in the DCI carrying the HARQ process identifier.
In another embodiment, the processing module 702 is further specifically configured to:
and judging whether all synchronous HARQ processes are finished, if so, using scheduling resources of a base station to carry out asynchronous HARQ transmission, wherein the identifier of the asynchronous HARQ process is the HARQ process identifier corresponding to the DCI carrying the HARQ process identifier.
In another embodiment, the processing module 702 is further specifically configured to:
terminating all HARQ processes; and carrying out asynchronous HARQ transmission by using the scheduling resource of the base station.
In another embodiment, the processing module 702 is further specifically configured to:
receiving a connection reconfiguration RRC indication, wherein the RRC indication carries a frame number, a subframe number and an HARQ process identifier; and according to the RRC indication, using the scheduling resource of the base station to carry out asynchronous HARQ transmission.
Fig. 8 is a block diagram of a first embodiment of an HARQ switching apparatus according to an embodiment of the present invention, and as shown in fig. 8, the apparatus includes:
a processing module 801 is configured to determine whether to switch from synchronous HARQ to asynchronous HARQ.
A sending module 802, configured to send a handover instruction to the terminal if the terminal is a ue, where the handover instruction is used to instruct to handover from the synchronous HARQ to the asynchronous HARQ.
The device is used for realizing the method embodiments, the realization principle and the technical effect are similar, and the details are not repeated here.
In another embodiment, the sending module 802 is specifically configured to:
and sending DCI to a terminal, wherein the DCI carries the switched asynchronous HARQ process identifier so that the terminal acquires a switching indication according to the asynchronous HARQ process identifier.
Fig. 9 is a block diagram of a first embodiment of an HARQ switching apparatus according to an embodiment of the present invention, and as shown in fig. 9, the apparatus includes:
a receiving module 901, configured to obtain a handover indication, where the handover indication is used to indicate handover from asynchronous HARQ to synchronous HARQ.
A processing module 902, configured to switch from asynchronous HARQ to synchronous HARQ according to the switching indication.
The processing module 902 is further configured to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ.
In another embodiment, the receiving module 901 is specifically configured to:
blind detecting DCI in the USS; and if the DCI with the format of 0 or 4 is detected in a blind mode, the terminal determines to acquire the switching indication.
In another embodiment, the processing module 902 is specifically configured to:
and if the transmission mode is the FDD mode, mapping the HARQ process identifier corresponding to the asynchronous HARQ into the HARQ process identifier corresponding to the synchronous HARQ according to a frame number, a subframe number and the number of the maximum parallel HARQ processes which can be supported.
And if the transmission mode is a TDD mode, mapping the HARQ process identifier corresponding to the asynchronous HARQ into the HARQ process identifier corresponding to the synchronous HARQ according to a frame number, the number of the supportable maximum parallel HARQ processes, the total number of the PUSCHs in each frame and the identifier of the PUSCHs.
In another embodiment, the processing module 902 is further specifically configured to:
if the transmission mode is the conventional HARQ, using a formula (10 x FN + i)% HARQ process number to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is FDD TTI binding, using a formula floor ((10 × FN + i% 16)/4)% HARQ process number) to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the FDD TTI binding transmission mode;
if the transmission mode is the enhanced FDD TTI binding, a formula floor ((10 × FN + i% 12)/4)% HARQ process number) is used for mapping the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in the TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the enhanced FDD TTI binding transmission mode.
In another embodiment, the processing module 902 is further specifically configured to:
if the transmission mode is the conventional HARQ, mapping HARQ process identifications corresponding to the asynchronous HARQ to HARQ process identifications corresponding to the synchronous HARQ by using a formula (N × FN + i)% HARQ process number, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the identifications of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is TDD TTI binding and the TDD ratio is 0, using a formula floor ((N × FN + i% 14)/4)% HARQ process number to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the identifier of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the TDD TTI binding transmission mode;
if the transmission mode is TDD TTI binding and the TDD ratio is 0 or 6, using a formula floor ((N × FN + i)/4)% HARQ process number to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is the frame number, N is the total number of PUSCHs in each frame, i is the identifier of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes that can be supported in the TDD TTI binding transmission mode.
In another embodiment, the processing module 902 is further specifically configured to:
terminating all HARQ processes; and performing synchronous HARQ transmission by using the scheduling resource of the base station.
Fig. 10 is a block diagram of a first embodiment of an HARQ switching apparatus according to an embodiment of the present invention, and as shown in fig. 10, the apparatus includes:
a processing module 1001 for determining whether to switch from asynchronous HARQ to synchronous HARQ.
A sending module 1002, configured to send a handover instruction to a terminal if the terminal is a synchronous HARQ, where the handover instruction is used to instruct to switch from an asynchronous HARQ to a synchronous HARQ.
In another embodiment, the sending module 1002 is specifically configured to:
and sending DCI to a terminal, wherein the format of the DCI is 0 or 4, so that the terminal acquires a switching indication according to the format of the DCI.
Fig. 11 is a block diagram of a first embodiment of a terminal according to the present invention, and as shown in fig. 11, the terminal includes:
a memory 1101 and a processor 1102.
The memory 1101 is used for storing program instructions, and the processor 1102 is used for calling the program instructions in the memory 1101 to execute the following method:
acquiring a switching indication, wherein the switching indication is used for indicating switching from a synchronous HARQ to an asynchronous HARQ;
switching from synchronous HARQ to asynchronous HARQ according to the switching indication;
and mapping the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ.
In another embodiment, the processor 1102 is specifically configured to:
blind detecting DCI in the USS;
and if the DCI carrying the HARQ process identifier is detected in a blind mode, determining to acquire the switching indication.
In another embodiment, the processor 1102 is further specifically configured to:
if the transmission mode is the FDD mode, mapping the HARQ process identifier corresponding to the synchronous HARQ into the HARQ process identifier corresponding to the asynchronous HARQ according to a frame number, a subframe number and the number of the maximum parallel HARQ processes which can be supported;
and if the transmission mode is a TDD mode, mapping the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ according to a frame number, the number of the supportable maximum parallel HARQ processes, the total number of the PUSCHs in each frame and the identifier of the PUSCHs.
In another embodiment, if the transmission mode is FDD mode, the processor 1102 is further specifically configured to:
if the transmission mode is the conventional HARQ, using a formula (10 x FN + i)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is FDD TTI binding, using a formula floor ((10 × FN + i% 16)/4)% HARQ process number) to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the FDD TTI binding transmission mode;
if the transmission mode is the enhanced FDD TTI binding, a formula floor ((10 × FN + i% 12)/4)% HARQ process number) is used for mapping the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in the TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the enhanced FDD TTI binding transmission mode.
In another embodiment, if the transmission mode is the TDD mode, the processor 1102 is further specifically configured to:
if the transmission mode is the conventional HARQ, using a formula (N × FN + i)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the index of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is TDD TTI binding and the TDD ratio is 0, using a formula floor ((N × FN + i% 14)/4)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the index of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the TDD TTI binding transmission mode;
if the transmission mode is TDD TTI binding and the TDD ratio is 0 or 6, using a formula floor ((N × FN + i)/4)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is the frame number, N is the total number of PUSCHs in each frame, i is the identification of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes that can be supported in the TDD TTI binding transmission mode.
In another embodiment, the processor 1102 is further specifically configured to:
acquiring a synchronous HARQ process identifier corresponding to a subframe where the DCI carrying the HARQ process identifier is located and subjected to blind detection;
and mapping the synchronous HARQ process identifier to the HARQ process identifier contained in the DCI carrying the HARQ process identifier.
In another embodiment, the processor 1102 is further specifically configured to:
and judging whether all synchronous HARQ processes are finished, if so, using scheduling resources of a base station to carry out asynchronous HARQ transmission, wherein the identifier of the asynchronous HARQ process is the HARQ process identifier corresponding to the DCI carrying the HARQ process identifier.
In another embodiment, the processor 1102 is further configured to:
terminating all HARQ processes;
and carrying out asynchronous HARQ transmission by using the scheduling resource of the base station.
In another embodiment, the processor 1102 is further configured to:
receiving a connection reconfiguration RRC indication, wherein the RRC indication carries a frame number, a subframe number and an HARQ process identifier;
and according to the RRC indication, using the scheduling resource of the base station to carry out asynchronous HARQ transmission.
Fig. 12 is a block diagram of a base station according to a first embodiment of the present invention, and as shown in fig. 12, the terminal includes:
a memory 1201 and a processor 1202.
The memory 1201 is used for storing program instructions, and the processor 1202 is used for calling the program instructions in the memory 1201 and executing the following method:
determining whether to switch from synchronous HARQ to asynchronous HARQ;
and if so, sending a switching instruction to the terminal, wherein the switching instruction is used for indicating the synchronous HARQ to be switched to the asynchronous HARQ.
In another embodiment, the processor 1202 is specifically configured to:
and sending DCI to a terminal, wherein the DCI carries the switched asynchronous HARQ process identifier so that the terminal acquires a switching indication according to the asynchronous HARQ process identifier.
Fig. 13 is a block diagram of a first embodiment of a terminal according to the present invention, and as shown in fig. 13, the terminal includes:
memory 1301 and processor 1302.
The memory 1301 is used for storing program instructions, and the processor 1302 is used for calling the program instructions in the memory 1301 and executing the following method:
acquiring a switching indication, wherein the switching indication is used for indicating switching from asynchronous HARQ to synchronous HARQ;
switching from asynchronous HARQ to synchronous HARQ according to the switching indication;
and mapping the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ.
In another embodiment, the processor 1302 is specifically configured to:
blind detecting DCI in the USS;
and if the DCI with the format of 0 or 4 is detected in a blind mode, determining to acquire the switching indication.
In another embodiment, the processor 1302 is further specifically configured to:
if the transmission mode is the FDD mode, mapping the HARQ process identifier corresponding to the asynchronous HARQ into the HARQ process identifier corresponding to the synchronous HARQ according to a frame number, a subframe number and the number of the maximum parallel HARQ processes which can be supported;
and if the transmission mode is a TDD mode, mapping the HARQ process identifier corresponding to the asynchronous HARQ into the HARQ process identifier corresponding to the synchronous HARQ according to a frame number, the number of the supportable maximum parallel HARQ processes, the total number of the PUSCHs in each frame and the identifier of the PUSCHs.
In another embodiment, if the transmission mode is the FDD mode, the processor 1302 is further configured to:
if the transmission mode is the conventional HARQ, using a formula (10 x FN + i)% HARQ process number to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is FDD TTI binding, using a formula floor ((10 × FN + i% 16)/4)% HARQ process number) to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the FDD TTI binding transmission mode;
if the transmission mode is the enhanced FDD TTI binding, a formula floor ((10 × FN + i% 12)/4)% HARQ process number) is used for mapping the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in the TTI binding, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the enhanced FDD TTI binding transmission mode.
In another embodiment, if the transmission mode is the TDD mode, the processor 1302 is further configured to:
if the transmission mode is the conventional HARQ, mapping HARQ process identifications corresponding to the asynchronous HARQ to HARQ process identifications corresponding to the synchronous HARQ by using a formula (N × FN + i)% HARQ process number, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the identifications of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is TDD TTI binding and the TDD ratio is 0, using a formula floor ((N × FN + i% 14)/4)% HARQ process number to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the identifier of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported in the TDD TTI binding transmission mode;
if the transmission mode is TDD TTI binding and the TDD ratio is 0 or 6, using a formula floor ((N × FN + i)/4)% HARQ process number to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is the frame number, N is the total number of PUSCHs in each frame, i is the identifier of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes that can be supported in the TDD TTI binding transmission mode.
In another embodiment, processor 1302 is further configured to:
terminating all HARQ processes;
and performing synchronous HARQ transmission by using the scheduling resource of the base station.
Fig. 14 is a block diagram of a base station according to a first embodiment of the present invention, and as shown in fig. 14, the base station includes:
a memory 1401, and a processor 1402.
The memory 1401 is used for storing program instructions, and the processor 1402 is used for calling the program instructions in the memory 1401 and executing the following method:
determining whether to switch from asynchronous HARQ to synchronous HARQ;
and if so, sending a switching instruction to the terminal, wherein the switching instruction is used for indicating the switching from the asynchronous HARQ to the synchronous HARQ.
In another embodiment, the processor 1402 is specifically configured to:
and sending DCI to a terminal, wherein the format of the DCI is 0 or 4, so that the terminal acquires a switching indication according to the format of the DCI.
The embodiments of the present invention may be referred to each other, and the apparatus provided in the embodiments of the present invention may be used to execute various functions of the corresponding method provided in the embodiments of the present invention, which are not described herein again.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.

Claims (22)

1. A hybrid automatic repeat HARQ switching method is characterized by comprising the following steps:
a terminal acquires a switching instruction, wherein the switching instruction is used for indicating switching from a synchronous HARQ to an asynchronous HARQ;
the terminal switches from the synchronous HARQ to the asynchronous HARQ according to the switching indication;
the terminal maps the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ;
the terminal acquires a switching instruction, comprising:
the terminal blindly detects downlink control information DCI in a user specific search space USS;
if DCI carrying HARQ process identification is detected in a blind mode, the terminal determines to obtain the switching indication;
the terminal maps the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ, including:
if the transmission mode is a frequency division duplex FDD mode, the terminal maps the HARQ process identification corresponding to the synchronous HARQ into the HARQ process identification corresponding to the asynchronous HARQ according to a frame number, a subframe number and the number of the maximum parallel HARQ processes which can be supported;
if the transmission mode is the FDD mode, the terminal maps the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ according to a frame number, a subframe number, and a number of HARQ processes that can support the maximum parallel HARQ, including:
if the transmission scheme is normal HARQ, the terminal uses the formula (10 x FN + i)%
Figure FDA0002755909770000011
The process number maps the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number, and the HARQ process number is the maximum number of parallel HARQ processes which can be supported in a conventional HARQ transmission mode;
if the transmission scheme is FDD shortest Transmission Interval TTI bundling, the terminal uses the formula floor ((10 × FN + i% 16)/4)%
Figure FDA0002755909770000012
The process number maps the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in TTI binding, and the HARQ process number is the maximum number of parallel HARQ processes which can be supported in an FDD TTI binding transmission mode;
if the transmission mode is enhanced FDD TTI bundling, the terminal uses the formula floor ((10 × FN + i% 12)/4)%
Figure FDA0002755909770000021
And the process number carries out mapping from the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in TTI binding, and the HARQ process number is the maximum number of parallel HARQ processes which can be supported in an enhanced FDD TTI binding transmission mode.
2. The method as claimed in claim 1, wherein the terminal maps the HARQ process id corresponding to the synchronous HARQ to the HARQ process id corresponding to the asynchronous HARQ, further comprising:
and if the transmission mode is a Time Division Duplex (TDD) mode, the terminal maps the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ according to the frame number, the number of the supportable maximum parallel HARQ processes, the total number of Physical Uplink Shared Channels (PUSCHs) in each frame and the identifier of the PUSCHs.
3. The method according to claim 2, wherein if the transmission mode is TDD mode, the terminal maps the HARQ process id corresponding to the synchronous HARQ to the HARQ process id corresponding to the asynchronous HARQ according to a frame number, a number of maximum parallel HARQ processes that can be supported, a total number of PUSCH (physical uplink shared channel) in each frame, and an id of PUSCH, and includes:
if the transmission mode is the conventional HARQ, the terminal uses a formula (N × FN + i)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the index of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is TDD TTI bundling and the TDD ratio is 0, the terminal uses the formula floor ((N × FN + i% 14)/4)%
Figure FDA0002755909770000022
proceThe ss number carries out mapping from the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the index of N PUSCHs, and the HARQ process number is the maximum number of parallel HARQ processes which can be supported under the TDD TTI binding transmission mode;
if the transmission mode is TDD TTI bundling and the TDD ratio is 0 or 6, the terminal performs mapping of HARQ process identification corresponding to the synchronous HARQ to HARQ process identification corresponding to the asynchronous HARQ using a formula floor ((N × FN + i)/4)% HARQ process number, where FN is a frame number, N is a total number of PUSCHs in each frame, i is an identification of N PUSCHs, and HARQ process number is a maximum number of parallel HARQ processes that can be supported in the TDD TTI bundling transmission mode.
4. The method as claimed in claim 1, wherein the mapping, by the terminal, the HARQ process id corresponding to the synchronous HARQ to the HARQ process id corresponding to the asynchronous HARQ comprises:
the terminal acquires a synchronous HARQ process identifier corresponding to a subframe where the DCI carrying the HARQ process identifier is located and is subjected to blind detection;
and the terminal maps the synchronous HARQ process identifier to the HARQ process identifier contained in the DCI carrying the HARQ process identifier.
5. The method as claimed in claim 1, wherein the mapping, by the terminal, the HARQ process id corresponding to the synchronous HARQ to the HARQ process id corresponding to the asynchronous HARQ comprises:
and the terminal judges whether all the synchronous HARQ processes are finished, if so, the terminal uses the scheduling resources of the base station to carry out asynchronous HARQ transmission, wherein the identification of the asynchronous HARQ process is the HARQ process identification corresponding to the DCI carrying the HARQ process identification.
6. The method of claim 1, wherein after the terminal obtains the handover indication, the method comprises:
terminating all HARQ processes;
and carrying out asynchronous HARQ transmission by using the scheduling resource of the base station.
7. The method as claimed in claim 1, wherein the mapping, by the terminal, the HARQ process id corresponding to the synchronous HARQ to the HARQ process id corresponding to the asynchronous HARQ comprises:
the terminal receives a connection reconfiguration RRC indication, wherein the RRC indication carries a frame number, a subframe number and an HARQ process identifier;
and the terminal uses the scheduling resource of the base station to carry out asynchronous HARQ transmission according to the RRC indication.
8. A hybrid automatic repeat HARQ switching method is characterized by comprising the following steps:
a terminal acquires a switching instruction, wherein the switching instruction is used for indicating switching from asynchronous HARQ to synchronous HARQ;
the terminal switches from asynchronous HARQ to synchronous HARQ according to the switching indication;
the terminal maps the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ;
the terminal acquires a switching instruction, comprising:
the terminal blindly detects downlink control information DCI in a user specific search space USS;
if the DCI with the format of 0 or 4 is detected in a blind mode, the terminal determines to acquire the switching indication;
the terminal maps the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, including:
if the transmission mode is a frequency division duplex FDD mode, the terminal maps the HARQ process identification corresponding to the asynchronous HARQ into the HARQ process identification corresponding to the synchronous HARQ according to a frame number, a subframe number and the number of the maximum parallel HARQ processes which can be supported;
if the transmission mode is the FDD mode, the terminal maps the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ according to a frame number, a subframe number, and a number of HARQ processes that can support the maximum parallel HARQ, including:
if the transmission scheme is normal HARQ, the terminal uses the formula (10 x FN + i)%
Figure FDA0002755909770000041
The process number maps the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number, and the HARQ process number is the maximum number of parallel HARQ processes which can be supported in a conventional HARQ transmission mode;
if the transmission scheme is FDD shortest Transmission Interval TTI bundling, the terminal uses the formula floor ((10 × FN + i% 16)/4)%
Figure FDA0002755909770000042
The process number maps the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in TTI binding, and the HARQ process number is the maximum number of parallel HARQ processes which can be supported in an FDD TTI binding transmission mode;
if the transmission mode is enhanced FDD TTI bundling, the terminal uses the formula floor ((10 × FN + i% 12)/4)%
Figure FDA0002755909770000043
And the process number is used for mapping the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in TTI binding, and the HARQ process number is the maximum number of parallel HARQ processes which can be supported in an enhanced FDD TTI binding transmission mode.
9. The method as claimed in claim 8, wherein the terminal maps the HARQ process id corresponding to the asynchronous HARQ to the HARQ process id corresponding to the synchronous HARQ, further comprising:
and if the transmission mode is a Time Division Duplex (TDD) mode, the terminal maps the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ according to the frame number, the number of the supportable maximum parallel HARQ processes, the total number of Physical Uplink Shared Channels (PUSCHs) in each frame and the identifier of the PUSCHs.
10. The method according to claim 9, wherein if the transmission mode is TDD mode, the terminal maps the HARQ process id corresponding to the asynchronous HARQ to the HARQ process id corresponding to the synchronous HARQ according to a frame number, a number of maximum parallel HARQ processes that can be supported, a total number of PUSCH (physical uplink shared channel) in each frame, and an id of PUSCH, and includes:
if the transmission mode is the conventional HARQ, the terminal uses a formula (N × FN + i)% HARQ process number to map the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the identifier of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission mode is TDD TTI bundling and the TDD ratio is 0, the terminal uses the formula floor ((N × FN + i% 14)/4)%
Figure FDA0002755909770000051
The process number maps the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is the frame number, N is the total number of PUSCHs in each frame, i is the identifier of N PUSCHs, and the HARQ process number is the number of the maximum parallel HARQ processes which can be supported in a TDD TTI binding transmission mode;
if the transmission mode is TDD TTI bundling and the TDD ratio is 0 or 6, the terminal performs mapping of HARQ process identifiers corresponding to the asynchronous HARQ to HARQ process identifiers corresponding to the synchronous HARQ using a formula floor ((N × FN + i)/4)% HARQ process number, where FN is a frame number, N is a total number of PUSCHs in each frame, i is an identifier of N PUSCHs, and HARQ process number is a maximum number of parallel HARQ processes that can be supported in the TDD TTI bundling transmission mode.
11. The method of claim 8, wherein after the terminal obtains the handover indication, the method comprises:
terminating all HARQ processes;
and performing synchronous HARQ transmission by using the scheduling resource of the base station.
12. A terminal, comprising:
a memory and a processor;
the memorizer is used for storing program instructions, and the processor is used for calling the program instructions in the memorizer and executing the following method:
acquiring a switching indication, wherein the switching indication is used for indicating switching from a synchronous HARQ to an asynchronous HARQ;
switching from synchronous HARQ to asynchronous HARQ according to the switching indication;
mapping the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ;
the processor is specifically configured to:
blind detecting Downlink Control Information (DCI) in a user specific search space (USS);
if DCI carrying HARQ process identification is detected in a blind mode, determining to obtain the switching indication;
the processor is further specifically configured to:
if the transmission mode is a frequency division duplex FDD mode, mapping the HARQ process identification corresponding to the synchronous HARQ into the HARQ process identification corresponding to the asynchronous HARQ according to a frame number, a subframe number and the number of the maximum parallel HARQ processes which can be supported;
if the transmission mode is the FDD mode, the processor is further specifically configured to:
if the transmission scheme is conventional HARQ, using the equation (10 × FN + i)%
Figure FDA0002755909770000061
The process number maps the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number, and the HARQ process number is the maximum number of parallel HARQ processes which can be supported in a conventional HARQ transmission mode;
if the transmission scheme is FDD shortest Transmission Interval TTI bundling, then use the formula floor ((10 × FN + i% 16)/4)%
Figure FDA0002755909770000062
The process number maps the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in TTI binding, and the HARQ process number is the maximum number of parallel HARQ processes which can be supported in an FDD TTI binding transmission mode;
if the transmission mode is FDD TTI bundling enhancement, then use the formula floor ((10 × FN + i% 12)/4)%
Figure FDA0002755909770000063
And the process number carries out mapping from the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in TTI binding, and the HARQ process number is the maximum number of parallel HARQ processes which can be supported in an enhanced FDD TTI binding transmission mode.
13. The terminal of claim 12, wherein the processor is further specifically configured to:
and if the transmission mode is a Time Division Duplex (TDD) mode, mapping the HARQ process identifier corresponding to the synchronous HARQ to the HARQ process identifier corresponding to the asynchronous HARQ according to a frame number, the number of the supportable maximum parallel HARQ processes, the total number of Physical Uplink Shared Channels (PUSCHs) in each frame and the identifier of the PUSCHs.
14. The terminal of claim 13, wherein if the transmission mode is TDD mode, the processor is further configured to:
if the transmission mode is the conventional HARQ, using a formula (N × FN + i)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the index of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission scheme is TDD TTI bundling and the TDD ratio is 0, then use the formula floor ((N × FN + i% 14)/4)%
Figure FDA0002755909770000071
The process number maps the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the index of N PUSCHs, and the HARQ process number is the number of the HARQ processes which can support the maximum parallel in a TDD TTI binding transmission mode;
if the transmission mode is TDD TTI binding and the TDD ratio is 0 or 6, using a formula floor ((N × FN + i)/4)% HARQ process number to map the HARQ process identification corresponding to the synchronous HARQ to the HARQ process identification corresponding to the asynchronous HARQ, wherein FN is the frame number, N is the total number of PUSCHs in each frame, i is the identification of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes that can be supported in the TDD TTI binding transmission mode.
15. The terminal of claim 12, wherein the processor is further specifically configured to:
acquiring a synchronous HARQ process identifier corresponding to a subframe where the DCI carrying the HARQ process identifier is located and subjected to blind detection;
and mapping the synchronous HARQ process identifier to the HARQ process identifier contained in the DCI carrying the HARQ process identifier.
16. The terminal of claim 12, wherein the processor is further specifically configured to:
and judging whether all synchronous HARQ processes are finished, if so, using scheduling resources of a base station to carry out asynchronous HARQ transmission, wherein the identifier of the asynchronous HARQ process is the HARQ process identifier corresponding to the DCI carrying the HARQ process identifier.
17. The terminal of claim 12, wherein the processor is further configured to:
terminating all HARQ processes;
and carrying out asynchronous HARQ transmission by using the scheduling resource of the base station.
18. The terminal of claim 12, wherein the processor is further configured to:
receiving a connection reconfiguration RRC indication, wherein the RRC indication carries a frame number, a subframe number and an HARQ process identifier;
and according to the RRC indication, using the scheduling resource of the base station to carry out asynchronous HARQ transmission.
19. A terminal, comprising:
a memory and a processor;
the memorizer is used for storing program instructions, and the processor is used for calling the program instructions in the memorizer and executing the following method:
acquiring a switching indication, wherein the switching indication is used for indicating switching from asynchronous HARQ to synchronous HARQ;
switching from asynchronous HARQ to synchronous HARQ according to the switching indication;
mapping the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ;
the processor is specifically configured to:
blind detecting Downlink Control Information (DCI) in a user specific search space (USS);
if DCI with the format of 0 or 4 is detected in a blind mode, determining to acquire the switching indication;
the processor is further specifically configured to:
if the transmission mode is a frequency division duplex FDD mode, mapping the HARQ process identification corresponding to the asynchronous HARQ into the HARQ process identification corresponding to the synchronous HARQ according to a frame number, a subframe number and the number of the maximum parallel HARQ processes which can be supported;
if the transmission mode is the FDD mode, the processor is further specifically configured to:
if the transmission scheme is conventional HARQ, using the equation (10 × FN + i)%
Figure FDA0002755909770000081
The process number maps the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number, and the HARQ process number is the maximum number of parallel HARQ processes which can be supported in a conventional HARQ transmission mode;
if the transmission scheme is FDD shortest Transmission Interval TTI bundling, then use the formula floor ((10 × FN + i% 16)/4)%
Figure FDA0002755909770000082
The process number maps the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in TTI binding, and the HARQ process number is the maximum number of parallel HARQ processes which can be supported in an FDD TTI binding transmission mode;
if the transmission mode is FDD TTI bundling enhancement, then use the formula floor ((10 × FN + i% 12)/4)%
Figure FDA0002755909770000091
And the process number is used for mapping the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is a frame number, i is a subframe number of a first subframe in TTI binding, and the HARQ process number is the maximum number of parallel HARQ processes which can be supported in an enhanced FDD TTI binding transmission mode.
20. The terminal of claim 19, wherein the processor is further specifically configured to:
and if the transmission mode is a Time Division Duplex (TDD) mode, mapping the HARQ process identifier corresponding to the asynchronous HARQ into the HARQ process identifier corresponding to the synchronous HARQ according to a frame number, the number of the supportable maximum parallel HARQ processes, the total number of Physical Uplink Shared Channels (PUSCHs) in each frame and the identifier of the PUSCHs.
21. The terminal of claim 20, wherein if the transmission mode is TDD mode, the processor is further specifically configured to:
if the transmission mode is the conventional HARQ, mapping HARQ process identifications corresponding to the asynchronous HARQ to HARQ process identifications corresponding to the synchronous HARQ by using a formula (N × FN + i)% HARQ process number, wherein FN is a frame number, N is the total number of PUSCHs in each frame, i is the identifications of N PUSCHs, and HARQ process number is the maximum number of parallel HARQ processes which can be supported under the conventional HARQ transmission mode;
if the transmission scheme is TDD TTI bundling and the TDD ratio is 0, then use the formula floor ((N × FN + i% 14)/4)%
Figure FDA0002755909770000092
The process number maps the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ, wherein FN is the frame number, N is the total number of PUSCHs in each frame, i is the identifier of N PUSCHs, and the HARQ process number is the number of the maximum parallel HARQ processes which can be supported in a TDD TTI binding transmission mode;
if the transmission mode is TDD TTI bundling and the TDD ratio is 0 or 6, performing mapping from the HARQ process identifier corresponding to the asynchronous HARQ to the HARQ process identifier corresponding to the synchronous HARQ using a formula floor ((N × FN + i)/4)% HARQ process number, where FN is a frame number, N is a total number of PUSCHs in each frame, i is an identifier of N PUSCHs, and HARQ processes.
22. The terminal of claim 19, wherein the processor is further configured to:
terminating all HARQ processes;
and performing synchronous HARQ transmission by using the scheduling resource of the base station.
CN201610974563.XA 2016-11-03 2016-11-03 Hybrid automatic repeat request HARQ (hybrid automatic repeat request) switching method and terminal Active CN108023685B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610974563.XA CN108023685B (en) 2016-11-03 2016-11-03 Hybrid automatic repeat request HARQ (hybrid automatic repeat request) switching method and terminal

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610974563.XA CN108023685B (en) 2016-11-03 2016-11-03 Hybrid automatic repeat request HARQ (hybrid automatic repeat request) switching method and terminal

Publications (2)

Publication Number Publication Date
CN108023685A CN108023685A (en) 2018-05-11
CN108023685B true CN108023685B (en) 2021-02-12

Family

ID=62083679

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610974563.XA Active CN108023685B (en) 2016-11-03 2016-11-03 Hybrid automatic repeat request HARQ (hybrid automatic repeat request) switching method and terminal

Country Status (1)

Country Link
CN (1) CN108023685B (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110635868B (en) * 2018-06-21 2021-02-09 维沃移动通信有限公司 HARQ-ACK processing method and device for hybrid automatic repeat request feedback information
CN110086567B (en) * 2019-03-22 2021-11-23 西安电子科技大学 Method for enhancing DCI (Downlink control information) carrying mode information of HARQ (hybrid automatic repeat request) stop process
CN109936426B (en) * 2019-03-22 2021-09-28 西安电子科技大学 Method and computer for adding HARQ stop-wait process attribute configuration in RRC signaling
CN110121192B (en) * 2019-03-22 2021-09-14 西安电子科技大学 MAC CE, HARQ process mode switching method, and transmitting and receiving method for switching MAC CE

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101882985A (en) * 2009-05-06 2010-11-10 中兴通讯股份有限公司 Indicating method for sending hybrid automatic repeat request (HARQ) and base station thereof
CN104348597A (en) * 2013-08-08 2015-02-11 北京三星通信技术研究有限公司 PUSCH (physical uplink shared channel) scheduling and HARQ-ACK (hybrid automatic repeat request-acknowledgement) information transmission method
CN104798329A (en) * 2012-11-13 2015-07-22 Lg电子株式会社 Method and apparatus for transmitting data, and method and apparatus for transmitting data
WO2016040290A1 (en) * 2014-09-08 2016-03-17 Interdigital Patent Holdings, Inc. Systems and methods of operating with different transmission time interval (tti) durations
WO2016074635A1 (en) * 2014-11-13 2016-05-19 Qualcomm Incorporated Retransmission signaling for discontinuous transmission (dtx) in shared spectrum

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007110740A2 (en) * 2006-03-24 2007-10-04 Nokia Corporation Reducing allocation signalling at retransmissions
WO2009022310A2 (en) * 2007-08-14 2009-02-19 Nokia Corporation Resource scheduling enabling partially-constrained retransmission
KR20100094924A (en) * 2009-02-19 2010-08-27 삼성전자주식회사 Method for performing hybrid automatic repeat request operation in wireless mobile communication system
US8472391B2 (en) * 2009-04-13 2013-06-25 Research In Motion Limited System and method for semi-synchronous hybrid automatic repeat request
CN102377546B (en) * 2010-08-10 2016-09-07 中兴通讯股份有限公司 The ascending HARQ course recognition methods of a kind of repeated link and device
CN105634691B (en) * 2011-04-01 2019-10-22 华为技术有限公司 Data transmission method, apparatus and system
PL2725753T3 (en) * 2012-10-29 2019-01-31 Alcatel Lucent Apparatus, method and computer program for configuring a delay for a synchronous transmission cycle
US20150173102A1 (en) * 2013-12-12 2015-06-18 Sharp Kabushiki Kaisha Terminal apparatus, base station apparatus, communication system, communication method, and integrated circuit

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101882985A (en) * 2009-05-06 2010-11-10 中兴通讯股份有限公司 Indicating method for sending hybrid automatic repeat request (HARQ) and base station thereof
CN104798329A (en) * 2012-11-13 2015-07-22 Lg电子株式会社 Method and apparatus for transmitting data, and method and apparatus for transmitting data
CN104348597A (en) * 2013-08-08 2015-02-11 北京三星通信技术研究有限公司 PUSCH (physical uplink shared channel) scheduling and HARQ-ACK (hybrid automatic repeat request-acknowledgement) information transmission method
WO2016040290A1 (en) * 2014-09-08 2016-03-17 Interdigital Patent Holdings, Inc. Systems and methods of operating with different transmission time interval (tti) durations
WO2016074635A1 (en) * 2014-11-13 2016-05-19 Qualcomm Incorporated Retransmission signaling for discontinuous transmission (dtx) in shared spectrum

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
《Support for Short TTIs and Processing Times in LTE》;InterDigital Communications;《3GPP TSG-RAN WG1 #83》;20151120;全文 *

Also Published As

Publication number Publication date
CN108023685A (en) 2018-05-11

Similar Documents

Publication Publication Date Title
CN107005509B (en) Method, apparatus and system for data transmission in an unlicensed shared medium
US10057885B2 (en) Device and method of handling transmission in unlicensed band
TWI577151B (en) Device and Method of Handling Service in Unlicensed Cell
KR102246591B1 (en) Method and device for transmitting and receiving transmission timing information
US20170311337A1 (en) Data Processing Implementation Method, Base Station and User Equipment
JP7037566B2 (en) Information transmission method and equipment
US10432349B2 (en) Data block transmission with variable retransmission feedback time
CN108023685B (en) Hybrid automatic repeat request HARQ (hybrid automatic repeat request) switching method and terminal
US11259276B2 (en) Method and device for selecting resources
CN112970214B (en) Feedback signaling for side links
EP3742641A1 (en) Timer-based bandwidth part switching method, terminal device, and network device
EP3211813A2 (en) Device and method of handling hybrid automatic repeat request transmission
KR101479886B1 (en) Method and base station, user equipment and system for activating coexistence work mode
EP3175569B1 (en) Cellular feedback transmission for user equipments enabling device-to-device communications
CN107528676B (en) Method and equipment for transmitting feedback information of uplink transmission
CN114071776A (en) Communication method, user equipment, network equipment and electronic equipment
WO2017195171A1 (en) Signaling of tdd subframe use to short tti ues
WO2016122932A1 (en) Wireless data transmission
CN112602281B (en) Communication method and device
CN109218002B (en) Apparatus and method for performing data transmission in a bandwidth portion
EP3089392B1 (en) Device and method of handling harq operation for unlicensed band
WO2017206585A1 (en) Data transmission method, apparatus and system
EP3076739A1 (en) Device and method of handling data transmission in unlicensed band
US10938522B2 (en) Low latency service feedback
CN112019308A (en) HARQ transmission method and device

Legal Events

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