CN108322287B - Method and device for PUSCH data transmission during retuning - Google Patents

Method and device for PUSCH data transmission during retuning Download PDF

Info

Publication number
CN108322287B
CN108322287B CN201710038138.4A CN201710038138A CN108322287B CN 108322287 B CN108322287 B CN 108322287B CN 201710038138 A CN201710038138 A CN 201710038138A CN 108322287 B CN108322287 B CN 108322287B
Authority
CN
China
Prior art keywords
user equipment
data transmission
enb
pusch data
rate matching
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
CN201710038138.4A
Other languages
Chinese (zh)
Other versions
CN108322287A (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.)
Nokia Shanghai Bell Co Ltd
Original Assignee
Nokia Shanghai Bell 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 Nokia Shanghai Bell Co Ltd filed Critical Nokia Shanghai Bell Co Ltd
Priority to CN201710038138.4A priority Critical patent/CN108322287B/en
Publication of CN108322287A publication Critical patent/CN108322287A/en
Application granted granted Critical
Publication of CN108322287B publication Critical patent/CN108322287B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1221—Wireless traffic scheduling based on age of data to be sent
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0002—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058—Allocation criteria
    • H04L5/0064—Rate requirement of the data, e.g. scalable bandwidth, data priority

Abstract

The invention aims to provide a method and equipment for re-timing PUSCH data transmission. Compared with the prior art, the method and the device have the advantages that the user equipment sends the capability parameters of the user equipment to the corresponding eNB, wherein the capability parameters comprise parameter information used for indicating whether the user equipment supports the re-tuning and carrying out PUSCH data transmission in a rate matching mode. Further, if the user equipment and the corresponding eNB both support the rate matching mapping mode, the eNB sends a configuration message to the corresponding user equipment, where the configuration message includes a configuration parameter for instructing the user equipment to perform PUSCH data transmission in the rate matching mode, so that the user equipment performs PUSCH data transmission in the rate matching mode to obtain an extra PUSCH decoding gain.

Description

Method and device for PUSCH data transmission during retuning
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a technology for data transmission of a Physical Uplink Shared Channel (PUSCH) during retuning.
Background
In order to reduce data transmission of Internet of Things (IoT) devices through an LTE (Long Term Evolution) network, Cat-M (Category-M) is introduced into 3GPP LTE Release 13. The goal of Cat-M UEs (user equipment) is low complexity and low power consumption. The Cat-M UE is only used for narrowband, i.e. maximum 6 Resource Blocks (RBs) can be occupied by Cat-M DL (downlink) and UL (uplink) physical channels. For the UL, a guard period is created by frequency re-tuning (tuning) between the transmitting ends (Tx-to-Tx) in two consecutive subframes. Which is considered to be one or more OFDM (Orthogonal Frequency Division Multiplexing) symbols. These OFDM symbols cannot be used for PUSCH data transmission, i.e. powerless OFDM symbols.
When retuning, the PUSCH has two data mapping modes: puncturing (punting) and Rate Matching (Rate Matching). Existing 3GPP employs puncturing, which means that part of the PUSCH data will be mapped to a power-free (muted) OFDM symbol, so that it can be punctured when transmitted. However, initial studies of 3GPP have shown that the rate matching approach has better performance, which means that muted symbols are not counted at the time of data mapping.
In order to reduce the implementation complexity of the UE, the existing 3GPP specification adopts a puncturing manner for PUSCH data mapping during retuning. However, there is a performance penalty in this approach. There are diverse differences in IoT devices, which means that there are many types of Cat-M UEs. Some of them have low complexity designs, and the way of puncturing seems reasonable for these UEs. However, for some high-specification Cat-M UEs, it is clearly unreasonable that they must accommodate those simple UEs and accept lower PUSCH performance.
Therefore, how to provide an efficient and high-performance way for re-timing PUSCH data transmission becomes one of the problems that needs to be solved by those skilled in the art.
Disclosure of Invention
The invention aims to provide a method and equipment for re-timing PUSCH data transmission.
According to an aspect of the present invention, a reschedule PUSCH data transmission method implemented at a user equipment end is provided, wherein the method includes:
a, sending a capability parameter of the user equipment to a corresponding eNB, wherein the capability parameter comprises parameter information used for indicating whether the user equipment supports the re-tuning and adopting a rate matching mode to carry out PUSCH data transmission.
Preferably, the step a includes:
receiving a capability query request transmitted from the eNB;
and returning the capability parameters to the eNB according to the capability query request, wherein the capability parameters comprise parameter information used for indicating whether the user equipment supports the re-tuning and adopting a rate matching mode to carry out PUSCH data transmission.
Preferably, the method further comprises:
receiving an RRC connection reconfiguration message sent by the eNB in an RRC session process, wherein the RRC connection reconfiguration message comprises configuration parameters for instructing the user equipment to adopt a rate matching mode for PUSCH data transmission;
returning an RRC connection reconfiguration completion message to the eNB according to the RRC connection reconfiguration message;
and carrying out PUSCH data transmission to the eNB in a rate matching mode.
According to another aspect of the present invention, there is also provided a reschedule PUSCH data transmission method implemented at an eNB, wherein the method includes:
a, receiving capability parameters sent by corresponding user equipment, wherein the capability parameters comprise parameter information used for indicating whether the user equipment supports the re-tuning and adopting a rate matching mode to carry out PUSCH data transmission;
b, searching at least one PUSCH data transmission mode supported by the eNB and selecting one PUSCH data transmission mode from the PUSCH data transmission modes;
and C, sending a configuration message to the user equipment according to the selected PUSCH data transmission mode, wherein the configuration message comprises configuration parameters for indicating the user equipment to adopt a corresponding mode to carry out PUSCH data transmission.
Preferably, in an RRC session, when the parameter information indicates that the user equipment supports the retuning, a PUSCH data transmission is performed in a rate matching manner, where step B includes:
if the eNB supports the PUSCH data transmission in a rate matching mode, the eNB is used as the PUSCH data transmission mode;
wherein the step C comprises:
and sending an RRC connection reconfiguration message to the user equipment, wherein the RRC connection reconfiguration message comprises configuration parameters for indicating the user equipment to adopt a rate matching mode to carry out PUSCH data transmission.
Preferably, the method further comprises:
storing the capability parameter sent by the user equipment as a device attribute of the user equipment.
According to another aspect of the present invention, there is also provided a user equipment for implementing the retimed PUSCH data transmission, wherein the user equipment includes:
a first apparatus, configured to send a capability parameter of the user equipment to a corresponding eNB, where the capability parameter includes parameter information used to indicate whether the user equipment supports a retuning and perform PUSCH data transmission in a rate matching manner.
Preferably, the first means is for:
receiving a capability query request transmitted from the eNB;
and returning the capability parameters to the eNB according to the capability query request, wherein the capability parameters comprise parameter information used for indicating whether the user equipment supports the re-tuning and adopting a rate matching mode to carry out PUSCH data transmission.
Preferably, the user equipment further comprises:
a second apparatus, configured to receive, in an RRC session, an RRC connection reconfiguration message sent by the eNB, where the RRC connection reconfiguration message includes a configuration parameter for instructing the user equipment to perform PUSCH data transmission in a rate matching manner;
a third device, configured to return an RRC connection reconfiguration complete message to the eNB according to the RRC connection reconfiguration message;
fourth means for performing PUSCH data transmission to the eNB in a rate-matching manner.
According to another aspect of the present invention, there is also provided an eNB for implementing the re-tuning PUSCH data transmission, wherein the eNB includes:
a fifth apparatus, configured to receive a capability parameter sent from a corresponding user equipment, where the capability parameter includes parameter information used to indicate whether the user equipment supports a retuning and perform PUSCH data transmission in a rate matching manner;
a sixth apparatus, configured to search for at least one PUSCH data transmission scheme supported by the eNB and select one PUSCH data transmission scheme from the at least one PUSCH data transmission scheme;
a seventh means, configured to send a configuration message to the user equipment according to the selected PUSCH data transmission mode, where the configuration message includes a configuration parameter for instructing the user equipment to perform PUSCH data transmission in a corresponding mode.
Preferably, in an RRC session, when the parameter information indicates that the user equipment supports the retuning, the sixth apparatus is configured to perform PUSCH data transmission in a rate matching manner, wherein:
if the eNB supports the PUSCH data transmission in a rate matching mode, the eNB is used as the PUSCH data transmission mode;
wherein the seventh means is for:
and sending an RRC connection reconfiguration message to the user equipment, wherein the RRC connection reconfiguration message comprises configuration parameters for indicating the user equipment to adopt a rate matching mode to carry out PUSCH data transmission.
Preferably, the eNB further includes:
an eighth means, configured to store the capability parameter sent by the ue as a device attribute of the ue.
According to still another aspect of the present invention, there is also provided a system for implementing re-scheduled PUSCH data transmission, including the user equipment as described in any of the above and the eNB as described in any of the above.
Compared with the prior art, the method and the device have the advantages that the user equipment sends the capability parameters of the user equipment to the corresponding eNB, wherein the capability parameters comprise parameter information used for indicating whether the user equipment supports the re-tuning and carrying out PUSCH data transmission in a rate matching mode.
Further, if the user equipment and the corresponding eNB both support the rate matching mapping mode, the eNB sends a configuration message to the corresponding user equipment, where the configuration message includes a configuration parameter for instructing the user equipment to perform PUSCH data transmission in the rate matching mode, so that the user equipment performs PUSCH data transmission in the rate matching mode to obtain an extra PUSCH decoding gain.
Drawings
Other features, objects and advantages of the invention will become more apparent upon reading of the detailed description of non-limiting embodiments made with reference to the following drawings:
fig. 1 shows a schematic diagram of a re-scheduling PUSCH data transmission method implemented at a user equipment end according to an aspect of the present invention;
fig. 2 shows a schematic diagram of a re-tuning PUSCH data transmission method implemented at the eNB end according to another aspect of the present invention;
fig. 3 shows a schematic diagram of a re-tuned PUSCH data transmission according to a preferred embodiment of the present invention.
The same or similar reference numbers in the drawings identify the same or similar elements.
Detailed Description
The term "base station" as used herein may be considered synonymous with, and sometimes referred to hereinafter as: a node B, an evolved node B, an eNodeB, an eNB, a Base Transceiver Station (BTS), an RNC, etc., and may describe a transceiver that communicates with a mobile terminal and provides radio resources for it in a wireless communication network that may span multiple technology generations. The base stations discussed herein may have all of the functionality associated with conventional well-known base stations, except for the ability to implement the methods discussed herein.
The methods discussed below may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the necessary tasks may be stored in a machine or computer readable medium such as a storage medium. The processor(s) may perform the necessary tasks.
Specific structural and functional details disclosed herein are merely representative and are provided for purposes of describing example embodiments of the present invention. The present invention may, however, be embodied in many alternate forms and should not be construed as limited to only the embodiments set forth herein. It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element may be termed a second element, and, similarly, a second element may be termed a first element, without departing from the scope of example embodiments. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.
It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may be present. In contrast, when an element is referred to as being "directly connected" or "directly coupled" to another element, there are no intervening elements present. Other words used to describe the relationship between elements (e.g., "between" versus "directly between", "adjacent" versus "directly adjacent to", etc.) should be interpreted in a similar manner.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It should also be noted that, in some alternative implementations, the functions/acts noted may occur out of the order noted in the figures. For example, two figures shown in succession may, in fact, be executed substantially concurrently, or the figures may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which example embodiments belong. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
The present invention is described in further detail below with reference to the attached drawing figures.
Fig. 1 shows a schematic diagram of a re-scheduling PUSCH data transmission method implemented on the user equipment side according to an aspect of the present invention, and the method includes step S101.
In step S101, a user equipment transmits a capability parameter of the user equipment to a corresponding eNB, where the capability parameter includes parameter information used for indicating whether the user equipment supports a retuning and performing PUSCH data transmission in a rate matching manner.
Specifically, a user equipment, for example, a Cat-M UE as described above, actively or on request one or more times transmits a capability parameter of the user equipment to a corresponding base station, for example, an eNB, through an agreed communication manner, where a new UE capability parameter is introduced to indicate whether the UE supports a retuning, and a rate matching manner is adopted for PUSCH data transmission, so that parameter information used for indicating whether the user equipment supports a retuning and adopting a rate matching manner for PUSCH data transmission is included in the capability parameter transmitted by the user equipment to the eNB, for example, the following parameter information is introduced in PhyLayerParameters-v13X 0: Pusch-RateMatchingWhen Returning-r 13 Enumerized supported Optional
Here, the parameter information indicates whether the user equipment supports the parameter information for PUSCH data transmission by using the rate matching method when the user equipment supports the retuning, and the parameter information may be supported or unsupported.
Preferably, in step S101, the ue receives a capability query request sent from the eNB; and returning the capability parameters to the eNB according to the capability query request, wherein the capability parameters comprise parameter information used for indicating whether the user equipment supports the re-tuning and adopting a rate matching mode to carry out PUSCH data transmission.
Specifically, in step S101, the ue may further receive a capability query request sent by a corresponding eNB; according to the capability query request, searching a capability parameter of itself, for example, searching a manner of which data mapping of the PUSCH is supported when the capability query request is retuned, such as a manner of supporting only puncturing, a manner of supporting only rate matching, or both manners of data mapping, and returning the capability parameter to the eNB; or further, searching parameter information for indicating whether the user equipment supports the retuning and performing PUSCH data transmission in a rate matching mode, placing the parameter information in a specific field of a capability parameter, and returning the parameter information to the eNB. For example, as described above, the following parameter information is introduced in the capability parameter PhyLayerParameters-v13X0 of the user equipment returning to the eNB, for example: Pusch-RateMatchingWhen Returning-r 13 Enumerized supported Optional
For example, in the RRC session, when the eNB receives an RRC connection complete message (RRCConnectionComplete) returned by the user equipment, that is, it indicates that the user equipment completes the initial access; subsequently, the eNB triggers the ueCapabilityEnquiry, that is, sends a capability query request to the user equipment; the ue receives the capability query request sent from the eNB, and returns a capability parameter to the eNB according to the capability query request, where the capability parameter includes parameter information indicating whether the ue supports PUSCH data transmission in a rate matching manner when the ue supports retuning, for example, the ue replies that PUSCH-ratematchingWheats-r 13 is supported, that is, the ue assumes that PUSCH data transmission is performed in a rate matching manner when the ue supports retuning.
Preferably, the method further comprises steps S102 (not shown), S103 (not shown) and S104 (not shown).
In the RRC session process, in step S102, a user equipment receives an RRC connection reconfiguration message sent by the eNB, where the RRC connection reconfiguration message includes a configuration parameter for instructing the user equipment to perform PUSCH data transmission in a rate matching manner; subsequently, in step S103, the ue returns an RRC connection reconfiguration complete message to the eNB according to the RRC connection reconfiguration message; in step S104, the user equipment performs PUSCH data transmission to the eNB in a rate matching manner.
Specifically, the eNB may introduce a new UE configuration parameter to indicate the UE PUSCH transmission mode, that is, may introduce the following configuration parameters in the PUSCH-configdivided-r 13, and send the PUSCH-configdivided-r 13 to the corresponding UE in the RRC connection reconfiguration message: rEMapping method WhenReturning-r 13 ENGERETED { rateactivating, activating } Optional
In the RRC session procedure, in step S102, the user equipment receives an RRC connection reconfiguration message sent by a corresponding eNB, where the RRC connection reconfiguration message includes a configuration parameter for instructing the user equipment to perform PUSCH data transmission in a rate matching manner, for example, the RRC connection reconfiguration message includes a configuration parameter rmemappingmethod and when receiving a configuration parameter r13, that is, the eNB instructs the user equipment to perform PUSCH data transmission in a rate matching manner.
Subsequently, in step S103, the ue completes its reconfiguration according to the RRC connection reconfiguration message, for example, reconfigures itself for PUSCH data transmission to the eNB in a rate matching manner according to a configuration parameter rmemappingmethod when receiving a reconfiguration-r 13, and returns an RRC connection reconfiguration complete message to the eNB after the reconfiguration is completed.
Next, in step S104, the user equipment starts PUSCH data transmission to the eNB in a rate matching manner.
Here, the user equipment may always perform PUSCH data transmission with puncturing as a default until obtaining a configuration parameter rmemappingmethod when transmitting-r 13 from the RRC connection reconfiguration message of the eNB.
Here, the capability parameter of the user equipment is sent to the corresponding eNB by the user equipment, where the capability parameter includes parameter information for indicating whether the user equipment supports the retuning, and performs PUSCH data transmission in a rate matching manner, so that the user equipment, particularly Cat-M UE, balances UE implementation and PUSCH decoding performance during the retuning.
Fig. 2 shows a schematic diagram of a re-tuning PUSCH data transmission method implemented at the eNB end according to another aspect of the present invention, and the method includes steps S201, S202 and S203.
In step S201, the eNB receives a capability parameter sent from a corresponding user equipment, where the capability parameter includes parameter information used for indicating whether the user equipment supports a retuning and performing PUSCH data transmission in a rate matching manner.
Specifically, in step S201, the eNB receives, for example, through an agreed communication method, a capability parameter sent from a corresponding user equipment, where the capability parameter includes parameter information used to indicate whether the user equipment supports the retuning, and the eNB may know whether the user equipment supports the retuning, and may or may not support, to perform PUSCH data transmission in the rate matching manner according to the parameter information. For example, as exemplified previously, the user equipment introduces the following parameter information in PhyLayerParameters-v13X 0: the PUSCH-ratematchingwheatretuning-r 13 ended { supported } option al is sent to the eNB, and when the eNB obtains parameter information of PUSCH-ratematchingwheatretuning-r 13 ═ supported, the PUSCH data transmission is performed in a rate matching manner when the ue is considered to support the retuning.
In step S202, the eNB searches for at least one PUSCH data transmission scheme supported by the eNB and selects one PUSCH data transmission scheme from the at least one PUSCH data transmission scheme.
Specifically, in step S202, the eNB searches for at least one PUSCH data transmission scheme supported by itself, for example, finds whether the eNB itself supports only puncturing, only rate matching, or both data mapping, and then selects one PUSCH data transmission scheme from the at least one PUSCH data transmission scheme supported by itself according to the PUSCH data transmission scheme supported by the user equipment. For example, if the ue only supports the puncturing scheme and does not support the rate matching scheme, and both schemes are supported by the eNB, the eNB selects the puncturing scheme; if the user equipment supports both the two modes and the eNB also supports both the two modes, the eNB selects a rate matching mode. That is, in the case of rate matching priority, both eNB and user equipment can support the selected mode.
In step S203, the eNB sends a configuration message to the user equipment according to the selected PUSCH data transmission mode, where the configuration message includes a configuration parameter for instructing the user equipment to perform PUSCH data transmission in a corresponding mode.
Specifically, in step S203, the eNB transmits a configuration message to the corresponding user equipment according to the PUSCH data transmission scheme selected in step S202, for example, if the eNB selects a puncturing scheme for PUSCH data transmission, the configuration message transmitted to the user equipment includes configuration parameters for instructing the user equipment to perform PUSCH data transmission in the puncturing scheme; if the eNB selects the rate matching method to perform PUSCH data transmission, the configuration message sent to the user equipment includes configuration parameters for instructing the user equipment to perform PUSCH data transmission in the rate matching method.
Preferably, if the user equipment uses the puncturing mode as a default mode for performing PUSCH data transmission, when the eNB selects the puncturing mode for performing PUSCH data transmission, the user equipment may not send a configuration message to the user equipment, that is, the user equipment performs PUSCH data transmission in the puncturing mode by default until the eNB acquires configuration parameters indicating that the user equipment performs PUSCH data transmission in a rate matching mode.
Preferably, in an RRC session, when the parameter information indicates that the user equipment supports the retuning, the PUSCH data transmission is performed in a rate matching manner, wherein in step S202, if the eNB supports the PUSCH data transmission in the rate matching manner, the eNB uses the PUSCH data transmission as the PUSCH data transmission manner; in step S203, the eNB sends an RRC connection reconfiguration message to the user equipment, where the RRC connection reconfiguration message includes configuration parameters for instructing the user equipment to perform PUSCH data transmission in a rate matching manner.
Specifically, in the RRC session, if the parameter information included in the capability parameter sent by the ue to the eNB indicates that the ue supports the retuning, the PUSCH data transmission is performed in a rate matching manner, for example, if the capability parameter sent by the ue to the eNB actively or in response to a request of the eNB includes parameter information PUSCH-ratematchingWhenReturning-r 13, the capability parameter indicates that the ue supports the retuning, the PUSCH data transmission is performed in the rate matching manner; in step S202, if the eNB finds that the eNB also supports PUSCH data transmission in the rate matching manner by checking the manners supported by the eNB, the eNB uses the rate matching manner as the PUSCH data transmission manner; subsequently, in step S203, the eNB sends an RRC connection reconfiguration message to the user equipment, where the RRC connection reconfiguration message includes a configuration parameter, rmemappingmethod and when receiving a configuration parameter r13, that is, the eNB indicates that the user equipment instructs the user equipment to perform PUSCH data transmission in a rate matching manner.
Here, if both the user equipment and the corresponding eNB support the rate matching mapping method, the eNB sends a configuration message to the corresponding user equipment, where the configuration message includes a configuration parameter for instructing the user equipment to perform PUSCH data transmission in the rate matching method, so that the user equipment performs PUSCH data transmission in the rate matching method to obtain an extra PUSCH decoding gain.
Preferably, the method further comprises step S204 (not shown). In step S204, the eNB stores the capability parameter sent by the user equipment as a device attribute of the user equipment.
The following describes, in a preferred embodiment, the interaction between the ue and the eNB in the RRC procedure to complete the PUSCH data transmission when the re-tuning is completed.
As shown in fig. 3, in step S301, when the eNB receives an RRC connection complete message (RRCConnectionComplete), indicating that the user equipment, such as a Cat-M UE, completes the initial access; the eNB triggers the ueCapabilityEnquiry, that is, the eNB sends a capability query request to the corresponding user equipment;
in step S302, the ue checks its capability parameter, such as checking its PUSCH RE mapping capability, or further checks whether it supports RE-tuning, and performs PUSCH data transmission in a rate matching manner;
in step S303, the UE returns a capability parameter to the eNB, where the capability parameter includes parameter information for indicating whether the UE supports the retuning and performs PUSCH data transmission in a rate matching manner, for example, the capability parameter includes parameter information PUSCH-ratematchingWhenReturning-r 13-supported, that is, the capability parameter indicates that the UE supports the retuning and performs PUSCH data transmission in the rate matching manner;
in step S304, the eNB stores the capability parameter of the ue, for example, the capability parameter that the ue supports both the puncturing and rate matching; then, the eNB searches for at least one PUSCH data transmission mode supported by itself and selects one PUSCH data transmission mode from the at least one PUSCH data transmission mode, for example, if the eNB also supports a rate matching mode, the rate matching mode is selected as the PUSCH data transmission mode;
in step S305, the eNB sends an RRC connection reconfiguration message (RRCConnectionReconfiguration) to the user equipment, where the RRC connection reconfiguration message includes configuration parameters for instructing the user equipment to perform PUSCH data transmission in a rate matching manner, such as rrmapppingmethodwhinreturning-r 13 ═ rateimplementation;
in step S306, the ue reconfigures according to the RRC connection reconfiguration message;
in step S307, the user equipment returns an RRC connection reconfiguration complete message (rrcconnectionreconfiguration complete) to the eNB;
in step S308, the user equipment performs PUSCH data transmission by using a rate matching method.
According to another aspect of the present invention, there is also provided a user equipment for implementing the retimed PUSCH data transmission, the user equipment comprising the first means.
A first device in user equipment sends a capability parameter of the user equipment to a corresponding eNB, wherein the capability parameter comprises parameter information used for indicating whether the user equipment supports the re-tuning and carrying out PUSCH data transmission in a rate matching mode.
Specifically, a user equipment, for example, a Cat-M UE as described above, where a first device actively or on request transmits capability parameters of the user equipment to a corresponding base station, such as an eNB, one or more times in an agreed communication manner, where a new UE capability parameter is introduced to indicate whether the UE supports a retuning, and the capability parameter transmitted by the first device of the user equipment to the eNB includes parameter information for indicating whether the user equipment supports a retuning, and the parameter information is introduced in PhyLayerParameters-v13X0, for example, the following parameter information is introduced: pusch-RateMatchingWhen Returning-r 13 Enumerized supported Optional
Here, the parameter information indicates whether the user equipment supports the parameter information for PUSCH data transmission by using the rate matching method when the user equipment supports the retuning, and the parameter information may be supported or unsupported.
Preferably, the first device in the user equipment receives a capability query request transmitted from the eNB; and returning the capability parameters to the eNB according to the capability query request, wherein the capability parameters comprise parameter information used for indicating whether the user equipment supports the re-tuning and adopting a rate matching mode to carry out PUSCH data transmission.
Specifically, the first device in the user equipment may further receive a capability query request sent by a corresponding eNB; according to the capability query request, searching a capability parameter of itself, for example, searching a manner of which data mapping of the PUSCH is supported when the capability query request is retuned, such as a manner of supporting only puncturing, a manner of supporting only rate matching, or both manners of data mapping, and returning the capability parameter to the eNB; or further, searching parameter information for indicating whether the user equipment supports the retuning and performing PUSCH data transmission in a rate matching mode, placing the parameter information in a specific field of a capability parameter, and returning the parameter information to the eNB. For example, as described before, the following parameter information is introduced in the capability parameter PhyLayerParameters-v13X0 of the first device in the user equipment returning to the eNB, for example: Pusch-RateMatchingWhen Returning-r 13 Enumerized supported Optional
For example, in the RRC session, when the eNB receives an RRC connection complete message (RRCConnectionComplete) returned by the user equipment, that is, it indicates that the user equipment completes the initial access; subsequently, the eNB triggers the ueCapabilityEnquiry, that is, sends a capability query request to the user equipment; the first apparatus in the user equipment receives the capability query request sent from the eNB, and returns a capability parameter to the eNB according to the capability query request, where the capability parameter includes parameter information indicating whether the user equipment supports PUSCH data transmission in a rate matching manner when the user equipment supports retuning, for example, the first apparatus in the user equipment replies that PUSCH-ratematchingWheats-r 13 is supported, that is, the user equipment is considered to support PUSCH data transmission in a rate matching manner when the user equipment supports retuning.
Preferably, the user equipment further comprises a second means, a third means and a fourth means.
In the process of an RRC session, a second device in the ue receives an RRC connection reconfiguration message sent by the eNB, where the RRC connection reconfiguration message includes configuration parameters for instructing the ue to perform PUSCH data transmission in a rate matching manner; then, the third device in the user equipment returns an RRC connection reconfiguration complete message to the eNB according to the RRC connection reconfiguration message; and the fourth device in the user equipment transmits PUSCH data to the eNB in a rate matching mode.
Specifically, the eNB may introduce a new UE configuration parameter to indicate the UE PUSCH transmission mode, that is, may introduce the following configuration parameters in the PUSCH-configdivided-r 13, and send the PUSCH-configdivided-r 13 to the corresponding UE in the RRC connection reconfiguration message: rEMapping method WhenReturning-r 13ENUMERATED { rat activating, pumping } OptiONAL
In an RRC session, a second device in the user equipment receives an RRC connection reconfiguration message sent by a corresponding eNB, where the RRC connection reconfiguration message includes a configuration parameter used to instruct the user equipment to perform PUSCH data transmission in a rate matching manner, for example, the RRC connection reconfiguration message includes a configuration parameter rmemappingmethod wheatreceiving-r 13, that is, the RRC connection reconfiguration message indicates that the eNB instructs the user equipment to perform PUSCH data transmission in a rate matching manner.
Then, the third device in the ue completes its reconfiguration according to the RRC connection reconfiguration message, for example, reconfigures itself for PUSCH data transmission to the eNB in a rate matching manner according to a configuration parameter rmemappingmethod when receiving a reconfiguration-r 13, and returns an RRC connection reconfiguration complete message to the eNB after the reconfiguration is completed.
Next, the fourth device in the user equipment starts PUSCH data transmission to the eNB in a rate matching manner.
Here, the user equipment may always perform PUSCH data transmission with puncturing as a default until obtaining a configuration parameter rmemappingmethod when transmitting-r 13 from the RRC connection reconfiguration message of the eNB.
Here, the capability parameter of the user equipment is sent to the corresponding eNB by the user equipment, where the capability parameter includes parameter information for indicating whether the user equipment supports the retuning, and performs PUSCH data transmission in a rate matching manner, so that the user equipment, particularly Cat-M UE, balances UE implementation and PUSCH decoding performance during the retuning.
According to still another aspect of the present invention, there is also provided an eNB implementing retimed PUSCH data transmission, wherein the eNB includes fifth, sixth and seventh apparatuses.
A fifth device in the eNB receives a capability parameter sent from a corresponding user equipment, where the capability parameter includes parameter information used for indicating whether the user equipment supports a re-tuning and performing PUSCH data transmission in a rate matching manner.
Specifically, the fifth apparatus in the eNB receives, for example, through an agreed communication method, a capability parameter sent from a corresponding user equipment, where the capability parameter includes parameter information used to indicate whether the user equipment supports a retuning, and the eNB may know whether the user equipment supports the retuning, and uses a rate matching method to perform PUSCH data transmission, which may be supported or unsupported, according to the parameter information. For example, as exemplified previously, the user equipment introduces the following parameter information in PhyLayerParameters-v13X 0: the fifth device in the eNB obtains parameter information PUSCH-ratematchchinerenuncing-r 13-supported from the capability parameter, that is, performs PUSCH data transmission in a rate matching manner when the ue is considered to support the retuning.
The sixth device in the eNB searches for at least one PUSCH data transmission mode supported by the eNB and selects one PUSCH data transmission mode from the at least one PUSCH data transmission mode.
Specifically, the sixth apparatus in the eNB searches for at least one PUSCH data transmission scheme supported by itself, for example, searches whether the eNB itself supports only puncturing, only rate matching, or both data mapping, and then selects one PUSCH data transmission scheme from the at least one PUSCH data transmission scheme supported by the eNB according to the PUSCH data transmission scheme supported by the user equipment. For example, if the ue only supports the puncturing scheme and does not support the rate matching scheme, and both schemes are supported by the eNB, the sixth apparatus in the eNB selects the puncturing scheme; if the ue supports both of the two modes and the eNB also supports both of the two modes, the sixth apparatus in the eNB selects a rate matching mode. That is, in the case of rate matching priority, both eNB and user equipment can support the selected mode.
And a seventh device in the eNB sends a configuration message to the user equipment according to the selected PUSCH data transmission mode, where the configuration message includes configuration parameters for instructing the user equipment to perform PUSCH data transmission in a corresponding mode.
Specifically, the seventh device in the eNB sends a configuration message to the corresponding user equipment according to the PUSCH data transmission scheme selected by the sixth device, for example, if the sixth device in the eNB selects a puncturing scheme for PUSCH data transmission, the configuration message sent by the seventh device to the user equipment includes a configuration parameter for instructing the user equipment to perform PUSCH data transmission in the puncturing scheme; if the sixth apparatus in the eNB selects the rate matching method to perform PUSCH data transmission, the configuration message sent by the seventh apparatus to the user equipment includes configuration parameters for instructing the user equipment to perform PUSCH data transmission in the rate matching method.
Preferably, if the user equipment uses the puncturing mode as a default mode for performing PUSCH data transmission, when the eNB selects the puncturing mode for performing PUSCH data transmission, the user equipment may not send a configuration message to the user equipment, that is, the user equipment performs PUSCH data transmission in the puncturing mode by default until the eNB acquires configuration parameters indicating that the user equipment performs PUSCH data transmission in a rate matching mode.
Preferably, in an RRC session, when the parameter information indicates that the user equipment supports the retuning, a rate matching method is used for PUSCH data transmission, and if the eNB supports PUSCH data transmission in the rate matching method, a sixth device in the eNB uses the parameter information as the PUSCH data transmission method; a seventh device in the eNB sends an RRC connection reconfiguration message to the user equipment, where the RRC connection reconfiguration message includes configuration parameters for instructing the user equipment to perform PUSCH data transmission in a rate matching manner.
Specifically, in the RRC session, if the parameter information included in the capability parameter sent by the ue to the eNB indicates that the ue supports the retuning, the PUSCH data transmission is performed in a rate matching manner, for example, if the capability parameter sent by the ue to the eNB actively or in response to a request of the eNB includes parameter information PUSCH-ratematchingWhenReturning-r 13, the capability parameter indicates that the ue supports the retuning, the PUSCH data transmission is performed in the rate matching manner; if the eNB finds that the eNB also supports PUSCH data transmission in a rate matching manner through checking the manners supported by the eNB, the sixth apparatus in the eNB uses the rate matching manner as the PUSCH data transmission manner; subsequently, the seventh apparatus in the eNB sends an RRC connection reconfiguration message to the user equipment, where the RRC connection reconfiguration message includes a configuration parameter, rmemappingmethod and when receiving a configuration parameter r13, that is, the seventh apparatus indicates that the eNB instructs the user equipment to perform PUSCH data transmission in a rate matching manner.
Here, if both the user equipment and the corresponding eNB support the rate matching mapping method, the eNB sends a configuration message to the corresponding user equipment, where the configuration message includes a configuration parameter for instructing the user equipment to perform PUSCH data transmission in the rate matching method, so that the user equipment performs PUSCH data transmission in the rate matching method to obtain an extra PUSCH decoding gain.
Preferably, the eNB further comprises an eighth apparatus. An eighth means in the eNB stores the capability parameter transmitted by the user equipment as a device attribute of the user equipment.
The following describes, in a preferred embodiment, the interaction between the ue and the eNB in the RRC procedure to complete the PUSCH data transmission when the re-tuning is completed.
When the eNB receives an RRC connection complete message (RRCConnectionComplete), indicating that the user equipment, such as Cat-M UE, completes the initial access; the eNB triggers the ueCapabilityEnquiry, that is, the eNB sends a capability query request to the corresponding user equipment;
the user equipment checks the capability parameter of the user equipment according to the capability inquiry request, such as checking the mapping capability of the PUSCH RE of the user equipment, or further checking whether the user equipment supports the RE-tuning and adopts a rate matching mode to carry out PUSCH data transmission;
the UE returns, to the eNB, a capability parameter, where the capability parameter includes parameter information used to indicate whether the UE supports retuning and performs PUSCH data transmission in a rate matching manner, and for example, the capability parameter includes parameter information PUSCH-ratematchingWhenReturning-r 13-supported, that is, indicates that the UE supports retuning and performs PUSCH data transmission in a rate matching manner;
the eNB stores the capability parameter of the ue, for example, stores the capability parameter that the ue supports both the puncturing mode and the rate matching mode; then, the eNB searches for at least one PUSCH data transmission mode supported by itself and selects one PUSCH data transmission mode from the at least one PUSCH data transmission mode, for example, if the eNB also supports a rate matching mode, the rate matching mode is selected as the PUSCH data transmission mode;
the eNB sends an RRC connection reconfiguration message (RRCConnectionReconfiguration) to the ue, where the RRC connection reconfiguration message includes configuration parameters for instructing the ue to perform PUSCH data transmission in a rate matching manner, such as rrmapping method and when there is no radio resource assignment, r 13;
the user equipment reconfigures according to the RRC connection reconfiguration message;
the user equipment returns an RRC connection reconfiguration complete message (rrcconnectionreconfiguration complete) to the eNB;
and the user equipment adopts a rate matching mode to carry out PUSCH data transmission.
According to still another aspect of the present invention, there is also provided a system for implementing re-scheduled PUSCH data transmission, including the user equipment as described in any of the above and the eNB as described in any of the above.
It should be noted that the present invention may be implemented in software and/or in a combination of software and hardware, for example, as an Application Specific Integrated Circuit (ASIC), a general purpose computer or any other similar hardware device. In one embodiment, the software program of the present invention may be executed by a processor to implement the steps or functions described above. Also, the software programs (including associated data structures) of the present invention can be stored in a computer readable recording medium, such as RAM memory, magnetic or optical drive or diskette and the like. Further, some of the steps or functions of the present invention may be implemented in hardware, for example, as circuitry that cooperates with the processor to perform various steps or functions.
In addition, some of the present invention can be applied as a computer program product, such as computer program instructions, which when executed by a computer, can invoke or provide the method and/or technical solution according to the present invention through the operation of the computer. Program instructions which invoke the methods of the present invention may be stored on a fixed or removable recording medium and/or transmitted via a data stream on a broadcast or other signal-bearing medium and/or stored within a working memory of a computer device operating in accordance with the program instructions. An embodiment according to the invention herein comprises an apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein the computer program instructions, when executed by the processor, trigger the apparatus to perform a method and/or solution according to embodiments of the invention as described above.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it is obvious that the word "comprising" does not exclude other elements or steps, and the singular does not exclude the plural. A plurality of units or means recited in the apparatus claims may also be implemented by one unit or means in software or hardware. The terms first, second, etc. are used to denote names, but not any particular order.

Claims (11)

1. A re-scheduling PUSCH data transmission method realized at a user equipment end, wherein the method comprises the following steps:
a, sending capability parameters of the user equipment to a corresponding eNB, wherein the capability parameters comprise parameter information used for indicating whether the user equipment supports the re-tuning and adopting a rate matching mode to carry out PUSCH data transmission;
wherein the step a comprises:
receiving a capability query request transmitted from the eNB;
and searching the capability parameter of the user equipment according to the capability query request, and returning the capability parameter to the eNB, wherein the user equipment searches a data mapping mode supporting the PUSCH when the user equipment is reset, and returns the searched capability parameter to the eNB, or searches parameter information used for indicating whether the user equipment supports the reset and performing PUSCH data transmission by adopting a rate matching mode, places the parameter information in a specific field of the capability parameter, and returns the parameter information to the eNB.
2. The method of claim 1, wherein the method further comprises:
receiving an RRC connection reconfiguration message sent by the eNB in an RRC session process, wherein the RRC connection reconfiguration message comprises configuration parameters for instructing the user equipment to adopt a rate matching mode for PUSCH data transmission;
returning an RRC connection reconfiguration completion message to the eNB according to the RRC connection reconfiguration message;
and carrying out PUSCH data transmission to the eNB in a rate matching mode.
3. A re-scheduling PUSCH data transmission method realized at an eNB side, wherein the method comprises the following steps:
a, sending a capability query request to self-corresponding user equipment, and receiving a capability parameter sent by the user equipment according to the capability query request, wherein the capability parameter comprises parameter information used for indicating whether the user equipment supports retuning and adopting a rate matching mode to carry out PUSCH data transmission, the user equipment searches a mode of supporting PUSCH data mapping when the user equipment resets and returns the searched capability parameter to the eNB, or searches parameter information used for indicating whether the user equipment supports retuning and adopting the rate matching mode to carry out PUSCH data transmission and places the parameter information in a specific field of the capability parameter and returns the parameter information to the eNB;
b, searching at least one PUSCH data transmission mode supported by the eNB and selecting one PUSCH data transmission mode from the PUSCH data transmission modes;
and C, sending a configuration message to the user equipment according to the selected PUSCH data transmission mode, wherein the configuration message comprises configuration parameters for indicating the user equipment to adopt a corresponding mode to carry out PUSCH data transmission.
4. The method according to claim 3, wherein, in the RRC session, when the parameter information indicates that the user equipment supports the retuning, the PUSCH data transmission is performed in a rate matching manner, wherein the step B comprises:
if the eNB supports the PUSCH data transmission in a rate matching mode, the eNB is used as the PUSCH data transmission mode;
wherein the step C comprises:
and sending an RRC connection reconfiguration message to the user equipment, wherein the RRC connection reconfiguration message comprises configuration parameters for indicating the user equipment to adopt a rate matching mode to carry out PUSCH data transmission.
5. The method of claim 3 or 4, wherein the method further comprises:
storing the capability parameter sent by the user equipment as a device attribute of the user equipment.
6. A user equipment for implementing retimed PUSCH data transmission, wherein the user equipment comprises:
a first apparatus, configured to send a capability parameter of the user equipment to a corresponding eNB, where the capability parameter includes parameter information used to indicate whether the user equipment supports a retuning and perform PUSCH data transmission in a rate matching manner;
wherein the first means is for:
receiving a capability query request transmitted from the eNB;
and searching the capability parameter of the user equipment according to the capability query request, and returning the capability parameter to the eNB, wherein the user equipment searches a data mapping mode supporting the PUSCH when the user equipment is reset, and returns the searched capability parameter to the eNB, or searches parameter information used for indicating whether the user equipment supports the reset and performing PUSCH data transmission by adopting a rate matching mode, places the parameter information in a specific field of the capability parameter, and returns the parameter information to the eNB.
7. The user equipment of claim 6, wherein the user equipment further comprises:
a second apparatus, configured to receive, in an RRC session, an RRC connection reconfiguration message sent by the eNB, where the RRC connection reconfiguration message includes a configuration parameter for instructing the user equipment to perform PUSCH data transmission in a rate matching manner;
a third device, configured to return an RRC connection reconfiguration complete message to the eNB according to the RRC connection reconfiguration message;
fourth means for performing PUSCH data transmission to the eNB in a rate-matching manner.
8. An eNB that enables retimed PUSCH data transmission, wherein the eNB comprises:
a fifth device, configured to send a capability query request to a self-corresponding user equipment, and receive a capability parameter sent by the user equipment according to the capability query request, where the capability parameter includes parameter information used to indicate whether the user equipment supports retuning, where the user equipment uses a rate matching method to perform PUSCH data transmission, and searches for a method that supports PUSCH data mapping when the user equipment retunes itself, and returns the searched capability parameter to the eNB, or searches for parameter information used to indicate whether the user equipment supports retuning, and places the parameter information in a specific field of the capability parameter, and returns the parameter information to the eNB;
a sixth apparatus, configured to search for at least one PUSCH data transmission scheme supported by the eNB and select one PUSCH data transmission scheme from the at least one PUSCH data transmission scheme;
a seventh means, configured to send a configuration message to the user equipment according to the selected PUSCH data transmission mode, where the configuration message includes a configuration parameter for instructing the user equipment to perform PUSCH data transmission in a corresponding mode.
9. The eNB of claim 8, wherein, during an RRC session, when the parameter information indicates that the user equipment supports a retune, the apparatus is configured to perform PUSCH data transmission in a rate matching manner, and wherein the sixth apparatus is configured to:
if the eNB supports the PUSCH data transmission in a rate matching mode, the eNB is used as the PUSCH data transmission mode;
wherein the seventh means is for:
and sending an RRC connection reconfiguration message to the user equipment, wherein the RRC connection reconfiguration message comprises configuration parameters for indicating the user equipment to adopt a rate matching mode to carry out PUSCH data transmission.
10. The eNB of claim 8 or 9, wherein the eNB further comprises:
an eighth means, configured to store the capability parameter sent by the ue as a device attribute of the ue.
11. A system implementing retimed PUSCH data transmission, comprising a user equipment according to claim 6 or 7 and an eNB according to any of claims 8 to 10.
CN201710038138.4A 2017-01-18 2017-01-18 Method and device for PUSCH data transmission during retuning Active CN108322287B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710038138.4A CN108322287B (en) 2017-01-18 2017-01-18 Method and device for PUSCH data transmission during retuning

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710038138.4A CN108322287B (en) 2017-01-18 2017-01-18 Method and device for PUSCH data transmission during retuning

Publications (2)

Publication Number Publication Date
CN108322287A CN108322287A (en) 2018-07-24
CN108322287B true CN108322287B (en) 2021-04-30

Family

ID=62892075

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710038138.4A Active CN108322287B (en) 2017-01-18 2017-01-18 Method and device for PUSCH data transmission during retuning

Country Status (1)

Country Link
CN (1) CN108322287B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10986516B2 (en) 2017-03-10 2021-04-20 Huawei Technologies Co., Ltd. System and method of network policy optimization
US11678252B2 (en) 2018-10-05 2023-06-13 Huawei Technologies Co., Ltd. Quality of service information notification to user equipment, users, and application server

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006020156A (en) * 2004-07-02 2006-01-19 Fujitsu Ltd Communication equipment, radio communication system
CN103248598A (en) * 2012-02-01 2013-08-14 华为技术有限公司 Communication method, base station and user equipment
CN104995862A (en) * 2013-01-03 2015-10-21 高通股份有限公司 ENB PDCCH implementation to avoid ambiguous DCI information
CN105580466A (en) * 2014-08-30 2016-05-11 华为技术有限公司 Antenna information transmission and reception method and device
WO2016209833A1 (en) * 2015-06-25 2016-12-29 Qualcomm Incorporated Retuning for enhanced machine type communication
CN106301737A (en) * 2010-06-24 2017-01-04 诺基亚通信公司 Rate matching pattern is changed in the case of there is channel state information reference signals transmission

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160219587A1 (en) * 2015-01-28 2016-07-28 Mediatek Inc. Control Channel and Data Channel Design for User Equipment

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006020156A (en) * 2004-07-02 2006-01-19 Fujitsu Ltd Communication equipment, radio communication system
CN106301737A (en) * 2010-06-24 2017-01-04 诺基亚通信公司 Rate matching pattern is changed in the case of there is channel state information reference signals transmission
CN103248598A (en) * 2012-02-01 2013-08-14 华为技术有限公司 Communication method, base station and user equipment
CN104995862A (en) * 2013-01-03 2015-10-21 高通股份有限公司 ENB PDCCH implementation to avoid ambiguous DCI information
CN105580466A (en) * 2014-08-30 2016-05-11 华为技术有限公司 Antenna information transmission and reception method and device
WO2016209833A1 (en) * 2015-06-25 2016-12-29 Qualcomm Incorporated Retuning for enhanced machine type communication

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Discussion of issues with rate matching for UL narrow band change";Qualcomm Incorporated;《3GPP TSG RAN WG1 Meeting R1-163003》;20160415;第一段 *
"Summary on remaining issues on narrowband retuning for eMTC";Intel Corporation;《3GPP TSG RAN WG1 Meeting R1- 161255》;20160219;全文 *

Also Published As

Publication number Publication date
CN108322287A (en) 2018-07-24

Similar Documents

Publication Publication Date Title
EP4221355A1 (en) Method and apparatus for transmitting a rach preamble on a wireless network
RU2669784C1 (en) Pdcch initiating, suitable for mtc devices
US10798699B2 (en) Physical downlink control channel transmission method, base station device, and user equipment
US11330543B2 (en) Signal sending method, signal receiving method, and apparatus
EP3592065B1 (en) Method for transmitting data, and terminal device
CN110463274B (en) Wireless communication device and method for managing system information provided by a wireless communication network
EP3216161B1 (en) Enhanced physical downlink control channel user equipment specific search space subband hopping for machine type communication device
US10270576B2 (en) Information transmission method, user equipment, and base station
EP3496351A1 (en) Pilot signal transmission method and device
TW201740765A (en) Method for transmitting system information, base station and terminal
JP2021503206A (en) System information transmission technology
CN108322287B (en) Method and device for PUSCH data transmission during retuning
KR20220002578A (en) Method and apparatus and communication system for transmission of reference signal
JP2019521539A (en) Signal transmission method, network equipment and terminal equipment
EP3493560B1 (en) Method, terminal device, and network device for transmitting information
US10756787B2 (en) Signal transmission method, network device, and terminal 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