CN108322287A - The method and apparatus of PUSCH data transmissions when a kind of readjustment - Google Patents

Abstract

The purpose of the present invention is to provide a method and equipment for PUSCH data transmission during retune. Compared with the prior art, in the present invention, the user equipment sends the capability parameter of the user equipment to the corresponding eNB, wherein the capability parameter includes a rate matching method used to indicate whether the user equipment supports retune to perform PUSCH For parameter information of data transmission, the present invention enables user equipment, especially Cat‑M UE, to balance UE implementation complexity and PUSCH decoding performance during retune. Further, if both the user equipment and the corresponding eNB support the rate-matching mapping mode, the eNB sends a configuration message to the corresponding user equipment, wherein the configuration message includes instructions for instructing the user equipment to use the rate matching mode for PUSCH data transmission configuration parameters, so that the user equipment adopts a rate matching method to transmit PUSCH data, and obtain additional PUSCH decoding gain.

Description

A method and device for PUSCH data transmission during retune

technical field

The present invention relates to the field of communication technology, in particular to a technology for PUSCH (Physical Uplink Shared Channel) data transmission during retune.

Background technique

In order to ease the data transmission of Internet of Things (Internet of Things, IoT) devices through LTE (Long Term Evolution, Long Term Evolution) network, Cat-M (Category-M) was introduced in 3GPP LTE Release 13. Cat-M UE (User Equipment) targets low complexity and low power consumption. Cat-M UE is only used for narrowband, that is, a maximum of 6 resource blocks (Resource Blocks, RB) can be occupied by Cat-M DL (downlink) and UL (uplink) physical channels. For UL, frequency retuning (Tx-to-Tx) between transmitters in two consecutive subframes results in a guard period. It is regarded as one or more OFDM (Orthogonal Frequency Division Multiplexing) symbols. These OFDM symbols cannot be used for PUSCH data transmission, that is, OFDM symbols without power.

When retuning, PUSCH has two data mapping methods: Puncturing and RateMatching. Existing 3GPP adopts a puncturing approach, which means that part of the PUSCH data will be mapped to unpowered (muted) OFDM symbols, so that they can be punctured when transmitting. However, 3GPP's initial research shows that the rate matching method has better performance, which means that muted symbols are not counted when data mapping.

In order to reduce the implementation complexity of the UE, the existing 3GPP specification adopts a hole-punching method for PUSCH data mapping during retune. However, there is a performance loss in this way. The diversity of IoT devices means that there are many types of Cat-M UEs. Some of these have low-complexity designs, and the hole punching approach seems reasonable for these UEs. However, for some high specification Cat-M UEs, it must adapt to those simple UEs and accept lower PUSCH performance, which is obviously unreasonable.

Therefore, how to provide an efficient and high-performance PUSCH data transmission mode during retune has become one of the problems that those skilled in the art need to solve urgently.

Contents of the invention

The purpose of the present invention is to provide a method and equipment for PUSCH data transmission during retune.

According to one aspect of the present invention, a method for transmitting PUSCH data during retune implemented at the user equipment side is provided, wherein the method includes:

a. Send the capability parameter of the user equipment to the corresponding eNB, where the capability parameter includes parameter information for indicating whether the user equipment supports PUSCH data transmission in a rate matching manner during retune.

Preferably, said step a includes:

receiving a capability query request sent from the eNB;

According to the capability query request, return the capability parameter to the eNB, where the capability parameter includes parameter information for indicating whether the user equipment supports rate matching mode for PUSCH data transmission during retune.

Preferably, the method also includes:

During the RRC session, receiving an RRC connection reconfiguration message sent by the eNB, wherein the RRC connection reconfiguration message includes configuration parameters for instructing the user equipment to perform PUSCH data transmission in a rate matching manner;

According to the RRC connection reconfiguration message, return an RRC connection reconfiguration complete message to the eNB;

Perform PUSCH data transmission to the eNB in a rate matching manner.

According to another aspect of the present invention, there is also provided a PUSCH data transmission method implemented at the eNB side during retune, wherein the method includes:

A receives the capability parameter sent by the corresponding user equipment, wherein the capability parameter includes parameter information used to indicate whether the user equipment supports PUSCH data transmission in a rate matching manner during retune;

B searches for at least one PUSCH data transmission mode supported by the eNB and selects a PUSCH data transmission mode;

C sends a configuration message to the user equipment according to the selected PUSCH data transmission mode, wherein the configuration message includes configuration parameters for instructing the user equipment to use a corresponding mode for PUSCH data transmission.

Preferably, during the RRC session, when the parameter information indicates that the user equipment supports retune, the PUSCH data transmission is performed in a rate matching manner, wherein the step B includes:

If the eNB supports PUSCH data transmission in a rate matching manner, use it as the PUSCH data transmission manner;

Wherein, the step C includes:

Sending an RRC connection reconfiguration message to the user equipment, wherein the RRC connection reconfiguration message includes configuration parameters for instructing the user equipment to perform PUSCH data transmission in a rate matching manner.

Preferably, the method also includes:

storing the capability parameter sent by the user equipment as a device attribute of the user equipment.

According to yet another aspect of the present invention, there is also provided a user equipment for implementing PUSCH data transmission during retune, wherein the user equipment includes:

The first means is 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 rate matching for PUSCH data transmission during retune.

Preferably, the first device is used for:

receiving a capability query request sent from the eNB;

According to the capability query request, return the capability parameter to the eNB, where the capability parameter includes parameter information for indicating whether the user equipment supports rate matching mode for PUSCH data transmission during retune.

Preferably, the user equipment further includes:

The second device is configured to receive the RRC connection reconfiguration message sent by the eNB during the RRC session, wherein the RRC connection reconfiguration message includes instructions for instructing the user equipment to perform PUSCH in a rate matching manner Configuration parameters for data transmission;

The third device is configured to return an RRC connection reconfiguration complete message to the eNB according to the RRC connection reconfiguration message;

The fourth device is configured to perform PUSCH data transmission to the eNB in a rate matching manner.

According to another aspect of the present invention, an eNB for implementing PUSCH data transmission during retune is also provided, wherein the eNB includes:

The fifth device is configured to receive a capability parameter sent from a corresponding user equipment, wherein the capability parameter includes parameter information used to indicate whether the user equipment supports PUSCH data transmission in a rate matching manner during retune;

A sixth device, configured to search for at least one PUSCH data transmission mode supported by the eNB and select a PUSCH data transmission mode therefrom;

The seventh means is configured to send a configuration message to the user equipment according to the selected PUSCH data transmission mode, wherein the configuration message includes configuration parameters for instructing the user equipment to use a corresponding mode for PUSCH data transmission.

Preferably, during the RRC session, when the parameter information indicates that the user equipment supports retune, the PUSCH data transmission is performed in a rate matching manner, wherein the sixth device is used for:

If the eNB supports PUSCH data transmission in a rate matching manner, use it as the PUSCH data transmission manner;

Wherein, the seventh device is used for:

Sending an RRC connection reconfiguration message to the user equipment, wherein the RRC connection reconfiguration message includes configuration parameters for instructing the user equipment to perform PUSCH data transmission in a rate matching manner.

Preferably, the eNB also includes:

The eighth means is configured to store the capability parameter sent by the user equipment as an equipment attribute of the user equipment.

According to still another aspect of the present invention, there is also provided a system for realizing PUSCH data transmission during retune, which includes the user equipment described in any one of the above items and the eNB described in any one of the above items.

Compared with the prior art, in the present invention, the user equipment sends the capability parameter of the user equipment to the corresponding eNB, wherein the capability parameter includes a rate matching method used to indicate whether the user equipment supports retune to perform PUSCH For parameter information of data transmission, the present invention enables user equipment, especially Cat-M UE, to balance UE implementation and PUSCH decoding performance during readjustment.

Further, if both the user equipment and the corresponding eNB support the rate-matching mapping mode, the eNB sends a configuration message to the corresponding user equipment, wherein the configuration message includes instructions for instructing the user equipment to use the rate matching mode for PUSCH data transmission configuration parameters, so that the user equipment adopts a rate matching method to transmit PUSCH data and obtain additional PUSCH decoding gain.

Description of drawings

Other characteristics, objects and advantages of the present invention will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings:

FIG. 1 shows a schematic diagram of a PUSCH data transmission method during retune implemented at a user equipment end according to an aspect of the present invention;

FIG. 2 shows a schematic diagram of a PUSCH data transmission method implemented at the eNB side during retune according to another aspect of the present invention;

Fig. 3 shows a schematic diagram of PUSCH data transmission during retune according to a preferred embodiment of the present invention.

The same or similar reference numerals in the drawings represent the same or similar components.

Detailed ways

The term "base station" as used herein may be considered synonymous with and may sometimes be referred to hereinafter: Node B, eNode B, eNodeB, eNB, base transceiver station (BTS), RNC, etc., and may describe transceivers that communicate with and provide radio resources to mobile terminals in a wireless communication network that may span multiple technology generations. The base stations discussed herein may have all the functionality associated with conventional, well-known base stations, except for the ability to implement the methods discussed herein.

The methods discussed later 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) can perform the necessary tasks.

Specific structural and functional details disclosed herein are representative only and for purposes of describing example embodiments of the present invention. This invention may, however, be embodied in many alternative 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 could be termed a second element, and, similarly, a second element could 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 should be interpreted in a similar fashion (e.g., "between" as opposed to "directly between", "adjacent to" as opposed to than "directly adjacent to" etc.).

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 "an" are intended to include the plural unless the context clearly dictates otherwise. It should also be understood that the terms "comprising" and/or "comprising" as used herein specify the presence of stated features, integers, steps, operations, units and/or components, but do not exclude the presence or addition of one or more Other features, integers, steps, operations, units, components and/or combinations 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 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 exemplary embodiments belong. It should also be understood that, unless expressly defined herein, terms such as those defined in commonly used dictionaries should be interpreted to have a meaning consistent with their meaning in the context of the relevant field, and not in an idealized or in an overly formal sense.

The present invention will be described in further detail below in conjunction with the accompanying drawings.

Fig. 1 shows a schematic diagram of a method for transmitting PUSCH data during retune implemented on a user equipment side according to an aspect of the present invention, the method includes step S101.

In step S101, the user equipment sends the capability parameter of the user equipment to the corresponding eNB, wherein the capability parameter includes parameter information used to indicate whether the user equipment supports PUSCH data transmission in a rate matching manner during retune .

Specifically, the user equipment, such as the aforementioned Cat-M UE, sends the capability parameter of the user equipment to the corresponding base station, such as eNB, one or more times actively or upon request through an agreed communication method, and then Therefore, a new UE capability parameter is introduced to indicate whether the UE supports rate matching for PUSCH data transmission during retune. Therefore, the capability parameter sent by the user equipment to the eNB includes an The parameter information of PUSCH data transmission using the rate matching method for timing adjustment. For example, the following parameter information is introduced in PhyLayerParameters-v13X0: pusch-RateMatchingWhenRetuning-r13 ENUMERATED{supported}OPTIONAL

Here, the parameter information indicates whether the user equipment supports parameter information for transmitting PUSCH data in a rate matching manner during retune, which may be supported or not.

Preferably, in step S101, the user equipment receives the capability query request sent from the eNB; according to the capability query request, returns the capability parameter to the eNB, wherein the capability parameter includes Parameter information describing whether the user equipment supports PUSCH data transmission in a rate matching manner during retune.

Specifically, in step S101, the user equipment may also first receive a capability query request sent from the corresponding eNB; according to the capability query request, find its own capability parameters, for example, find out which data of the PUSCH it supports when retuning The mapping method, such as only supporting the puncturing method, only supporting the rate matching method, or supporting both data mapping methods, returns the capability parameter to the eNB; or further, finds the information used to indicate the user equipment Whether to support the parameter information of PUSCH data transmission in the rate matching mode during retune, and put the parameter information in a specific field of the capability parameter, and return it to the eNB. For example, as mentioned above, for example, the following parameter information is introduced in the capability parameter PhyLayerParameters-v13X0 returned by the user equipment to the eNB: pusch-RateMatchingWhenRetuning-r13ENUMERATED{supported}OPTIONAL

For example, during the RRC session, when the eNB receives the RRC Connection Complete message (RRCConnectionComplete) returned by the user equipment, it means that the user equipment has completed the initial access; subsequently, the eNB triggers ueCapabilityEnquiry, that is, sends a capability query request to the user equipment; the user The device receives the capability query request sent from the eNB, and returns a capability parameter to the eNB according to the capability query request, wherein the capability parameter includes the PUSCH data used to indicate whether the user equipment supports retune by using a rate matching method For the transmitted parameter information, for example, the user equipment replies with pusch-RateMatchingWhenRetuning-r13=supported, that is, it is considered that the user equipment supports the rate matching mode for PUSCH data transmission when retuning is supported.

Preferably, the method further includes steps S102 (not shown), S103 (not shown) and S104 (not shown).

During the RRC session, in step S102, the user equipment receives the RRC connection reconfiguration message sent by the eNB, wherein the RRC connection reconfiguration message includes instructions for instructing the user equipment to adopt rate matching Configuration parameters for PUSCH data transmission; then, in step S103, the user equipment returns an RRC connection reconfiguration complete message to the eNB according to the RRC connection reconfiguration message; in step S104, the user equipment sends a rate matching method to the eNB The eNB performs PUSCH data transmission.

Specifically, the eNB can introduce new UE configuration parameters to indicate the UE PUSCH transmission mode, that is, the following configuration parameters can be introduced into PUSCH-ConfigDedicated-r13, and the PUSCH-ConfigDedicated-r13 can be sent in the RRC connection reconfiguration message To the corresponding UE: rEMappingMethodWhenRetuning-r13 ENUMERATED{rateMatching,puncturing}OPTIONAL

During the RRC session, in step S102, the user equipment receives an RRC connection reconfiguration message sent from the corresponding eNB, wherein the RRC connection reconfiguration message includes instructions for instructing the user equipment to adopt a rate matching method to perform The configuration parameter of PUSCH data transmission, for example, includes the configuration parameter rEMappingMethodWhenRetuning-r13=rateMatching in the RRC connection reconfiguration message, which means that the eNB instructs the user equipment to adopt the rate matching method for PUSCH data transmission.

Subsequently, in step S103, the user equipment completes its own reconfiguration according to the RRC connection reconfiguration message, for example, according to the configuration parameter rEMappingMethodWhenRetuning-r13=rateMatching included in the RRC connection reconfiguration message, reconfigures itself as the following In the rate matching mode, PUSCH data transmission is performed to the eNB, and after the reconfiguration is completed, an RRC connection reconfiguration complete message is returned to the eNB.

Next, in step S104, the user equipment starts to transmit PUSCH data to the eNB in a rate matching manner.

Here, the user equipment can always use puncturing as the default method for PUSCH data transmission until the configuration parameter rEMappingMethodWhenRetuning-r13=rateMatching is obtained from the RRC connection reconfiguration message of the eNB.

Here, the user equipment sends the capability parameter of the user equipment to the corresponding eNB, where the capability parameter includes parameter information for indicating whether the user equipment supports PUSCH data transmission in a rate matching manner during retune, This enables the user equipment, especially the Cat-M UE, to balance UE implementation and PUSCH decoding performance during retune.

Fig. 2 shows a schematic diagram of a method for transmitting PUSCH data during retune at the eNB side according to another aspect of the present invention, the method includes steps S201, S202 and S203.

In step S201, the eNB receives a capability parameter sent from a corresponding user equipment, wherein the capability parameter includes parameter information for indicating whether the user equipment supports rate matching for PUSCH data transmission during retune.

Specifically, in step S201, the eNB receives, for example, through an agreed communication method, the capability parameter sent from the corresponding user equipment, wherein the capability parameter includes a parameter used to indicate whether the user equipment supports retune using rate matching According to the parameter information of PUSCH data transmission, the eNB can know whether the user equipment supports the rate matching method for PUSCH data transmission during retune, which may or may not be supported. For example, as mentioned above, the user equipment introduces the following parameter information in PhyLayerParameters-v13X0: pusch-RateMatchingWhenRetuning-r13 ENUMERATED{supported}OPTIONAL and sends the capability parameter to the eNB, when the eNB learns the parameter information pusch-RateMatchingWhenRetuning-r13 from it =supported, that is, it is considered that the user equipment supports PUSCH data transmission in a rate matching manner during retune.

In step S202, the eNB searches for at least one PUSCH data transmission mode supported by the eNB and selects a PUSCH data transmission mode therefrom.

Specifically, in step S202, the eNB searches for at least one PUSCH data transmission method supported by itself, for example, finds out whether the eNB itself only supports the method of puncturing, the method of only supporting rate matching, or the method of two kinds of data mapping. Then, according to the PUSCH data transmission mode supported by the user equipment, the eNB selects a PUSCH data transmission mode from at least one PUSCH data transmission mode supported by itself. For example, if the user equipment only supports the puncturing method but not the rate matching method, and the eNB supports both methods, the eNB selects the puncturing method; if the user equipment supports both methods, the eNB If both methods are supported, the eNB selects the rate matching method. That is to say, in the case of giving priority to rate matching, both the eNB and the user equipment must support the selected mode at the same time.

In step S203, the eNB sends a configuration message to the user equipment according to the selected PUSCH data transmission mode, wherein the configuration message includes configuration parameters for instructing the user equipment to use a corresponding mode for PUSCH data transmission.

Specifically, in step S203, the eNB sends a configuration message to the corresponding user equipment according to the PUSCH data transmission method selected in step S202. The configuration message sent by the device includes configuration parameters for instructing the user equipment to transmit PUSCH data in the manner of puncturing; if the eNB selects the mode of rate matching for PUSCH data transmission, the configuration message sent to the user equipment includes A configuration parameter for instructing the user equipment to perform PUSCH data transmission in a rate matching manner.

Preferably, if the user equipment uses the puncturing method as the default method for PUSCH data transmission, when the eNB selects the puncturing method for PUSCH data transmission, it may not send a configuration message to the user equipment, that is, the The user equipment performs PUSCH data transmission in a puncturing manner by default, until it obtains configuration parameters indicating that it performs PUSCH data transmission in a rate-matching manner from the eNB.

Preferably, during the RRC session, when the parameter information indicates that the user equipment supports retune, PUSCH data transmission is performed in a rate matching manner, wherein, in step S202, if the eNB supports PUSCH data transmission in a rate matching manner data transmission, the eNB uses it as the PUSCH data transmission mode; wherein, in step S203, the eNB sends an RRC connection reconfiguration message to the user equipment, wherein the RRC connection reconfiguration message includes a Describes the configuration parameters for the user equipment to perform PUSCH data transmission in a rate matching manner.

Specifically, during the RRC session, if the parameter information included in the capability parameter sent by the user equipment to the eNB indicates that the user equipment supports retune, the rate matching method is used for PUSCH data transmission, for example, the user equipment actively or should the eNB request, the capability parameter sent to the eNB includes the parameter information pusch-RateMatchingWhenRetuning-r13=supported, which means that the user equipment supports the rate matching method for PUSCH data transmission during retune; then in step S202, if the eNB passes Check the mode supported by itself, and find that it also supports PUSCH data transmission in a rate matching mode, then the eNB uses the rate matching mode as the PUSCH data transmission mode; then, in step S203, the eNB sends to the user equipment The RRC connection reconfiguration message includes the configuration parameter rEMappingMethodWhenRetuning-r13=rateMatching in the RRC connection reconfiguration message, which means that the eNB instructs the user equipment to transmit PUSCH data 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, wherein the configuration message includes instructions for instructing the user equipment to use the rate matching method for PUSCH data transmission. configuration parameters, so that the user equipment adopts a rate matching method to transmit PUSCH data and obtain additional PUSCH decoding gain.

Preferably, the method further includes 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 uses a preferred embodiment to describe the interaction between the user equipment and the eNB during the RRC process to complete the PUSCH data transmission during retune.

As shown in Figure 3, in step S301, when the eNB receives the RRC Connection Complete message (RRCConnectionComplete), indicating that the user equipment, such as Cat-M UE, completes the initial access; then the eNB triggers ueCapabilityEnquiry, that is, the eNB sends The corresponding user equipment sends a capability query request;

In step S302, the user equipment checks its own capability parameters according to the capability query request, such as checking its own PUSCH RE mapping capability, or further, checks whether it supports retune and adopts a rate matching method for PUSCH data transmission;

In step S303, the user equipment returns the capability parameter to the eNB, including parameter information indicating whether the user equipment supports rate matching mode for PUSCH data transmission during retune, for example, the user equipment includes the parameter in the capability parameter The information pusch-RateMatchingWhenRetuning-r13=supported means that the UE supports the rate matching method for PUSCH data transmission during retuning;

In step S304, the eNB stores the capability parameters of the user equipment, for example, stores the capability parameters of the user equipment supporting both the puncturing mode and the rate matching mode; then, the eNB searches for at least one PUSCH data supported by itself Transmission mode and select a PUSCH data transmission mode, for example, if the eNB also supports the rate matching mode, select the rate matching mode as the PUSCH data transmission mode;

In step S305, the eNB sends an RRC connection reconfiguration message (RRCConnectionReconfiguration) to the user equipment, and the RRC connection reconfiguration message includes configuration parameters for instructing the user equipment to use a rate matching method for PUSCH data transmission, such as rEMappingMethodWhenRetuning-r13= rateMatching;

In step S306, the user equipment performs reconfiguration according to the RRC connection reconfiguration message;

In step S307, the user equipment returns an RRC connection reconfiguration complete message (RRCConnectionReconfigurationComplete) to the eNB;

In step S308, the user equipment transmits PUSCH data in a rate matching manner.

According to another aspect of the present invention, a user equipment for implementing PUSCH data transmission during retune is also provided, and the user equipment includes a first apparatus.

The first device in the user equipment sends the capability parameter of the user equipment to the corresponding eNB, where the capability parameter includes parameter information for indicating whether the user equipment supports PUSCH data transmission in a rate matching manner during retune .

Specifically, the user equipment, such as the above-mentioned Cat-M UE, wherein the first device actively or upon request, sends the user equipment to the corresponding base station, such as eNB, one or more times through the agreed communication method Here, a new UE capability parameter is introduced to indicate whether the UE supports rate matching for PUSCH data transmission during retune. Therefore, the capability parameter sent by the first device of the user equipment to the eNB includes Parameter information for indicating whether the user equipment supports retuning by adopting a rate matching method for PUSCH data transmission, for example, the following parameter information is introduced in PhyLayerParameters-v13X0: pusch-RateMatchingWhenRetuning-r13ENUMERATED{supported}OPTIONAL

Here, the parameter information indicates whether the user equipment supports parameter information for transmitting PUSCH data in a rate matching manner during retune, which may be supported or not.

Preferably, the first device in the user equipment receives a capability query request sent from the eNB; returns the capability parameter to the eNB according to the capability query request, wherein the capability parameter includes Parameter information describing whether the user equipment supports PUSCH data transmission in a rate matching manner during retune.

Specifically, the first device in the user equipment may also first receive a capability query request sent from the corresponding eNB; according to the capability query request, find its own capability parameters, for example, find out which data of the PUSCH it supports when retuning The mapping method, such as only supporting the puncturing method, only supporting the rate matching method, or supporting both data mapping methods, returns the capability parameter to the eNB; or further, finds the information used to indicate the user equipment Whether to support the parameter information of PUSCH data transmission in the rate matching mode during retune, and put the parameter information in a specific field of the capability parameter, and return it to the eNB. For example, as mentioned above, for example, the following parameter information is introduced in the capability parameter PhyLayerParameters-v13X0 returned by the first device in the user equipment to the eNB: pusch-RateMatchingWhenRetuning-r13 ENUMERATED{supported}OPTIONAL

For example, during the RRC session, when the eNB receives the RRC Connection Complete message (RRCConnectionComplete) returned by the user equipment, it means that the user equipment has completed the initial access; subsequently, the eNB triggers ueCapabilityEnquiry, that is, sends a capability query request to the user equipment; the user The first device in the device receives a 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 a rate used to indicate whether the user equipment supports retune Parameter information for PUSCH data transmission in matching mode, for example, the first device in the user equipment replies pusch-RateMatchingWhenRetuning-r13=supported, that is, it considers that the user equipment supports retuning and adopts rate matching mode for PUSCH data transmission.

Preferably, the user equipment further includes a second device, a third device and a fourth device.

During the RRC session, the second device connected to the user equipment receives the RRC connection reconfiguration message sent by the eNB, wherein the RRC connection reconfiguration message includes a Configure parameters for PUSCH data transmission; 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; the fourth device in the user equipment sends a rate matching method to the eNB The eNB performs PUSCH data transmission.

Specifically, the eNB can introduce new UE configuration parameters to indicate the UE PUSCH transmission mode, that is, the following configuration parameters can be introduced into PUSCH-ConfigDedicated-r13, and the PUSCH-ConfigDedicated-r13 can be sent in the RRC connection reconfiguration message To the corresponding UE: rEMappingMethodWhenRetuning-r13ENUMERATED{rateMatching,puncturing}OPTIONAL

During the RRC session, the second device in the user equipment receives an RRC connection reconfiguration message sent from the corresponding eNB, wherein the RRC connection reconfiguration message includes instructions for instructing the user equipment to use a rate matching method to perform The configuration parameter of PUSCH data transmission, for example, includes the configuration parameter rEMappingMethodWhenRetuning-r13=rateMatching in the RRC connection reconfiguration message, which means that the eNB instructs the user equipment to adopt the rate matching method for PUSCH data transmission.

Subsequently, the third device in the user equipment completes its own reconfiguration according to the RRC connection reconfiguration message, for example, according to the configuration parameter rEMappingMethodWhenRetuning-r13=rateMatching included in the RRC connection reconfiguration message, reconfigures itself as the following In the rate matching mode, PUSCH data transmission is performed to the eNB, and after the reconfiguration is completed, an RRC connection reconfiguration complete message is returned to the eNB.

Then, the fourth device in the user equipment starts to transmit PUSCH data to the eNB in a rate matching manner.

Here, the user equipment can always use puncturing as the default method for PUSCH data transmission until the configuration parameter rEMappingMethodWhenRetuning-r13=rateMatching is obtained from the RRC connection reconfiguration message of the eNB.

Here, the user equipment sends the capability parameter of the user equipment to the corresponding eNB, where the capability parameter includes parameter information for indicating whether the user equipment supports PUSCH data transmission in a rate matching manner during retune, This enables the user equipment, especially the Cat-M UE, to balance UE implementation and PUSCH decoding performance during retune.

According to yet another aspect of the present invention, an eNB for implementing PUSCH data transmission during retune is also provided, wherein the eNB includes fifth means, sixth means and seventh means.

The fifth apparatus in the eNB receives the capability parameter sent by the corresponding user equipment, where the capability parameter includes parameter information for indicating whether the user equipment supports rate matching mode for PUSCH data transmission during retune.

Specifically, the fifth device in the eNB receives, for example, through an agreed communication method, the capability parameter sent from the corresponding user equipment, where the capability parameter includes a parameter used to indicate whether the user equipment supports retune using rate matching According to the parameter information, eNB can know whether the user equipment supports PUSCH data transmission in rate matching mode during retune, which may be supported or not. For example, as mentioned above, the user equipment introduces the following parameter information in PhyLayerParameters-v13X0: pusch-RateMatchingWhenRetuning-r13 ENUMERATED{supported}OPTIONAL and sends the capability parameter to the eNB, when the fifth device in the eNB learns the parameter information from it pusch-RateMatchingWhenRetuning-r13=supported, that is, it is considered that the user equipment supports the rate matching mode for PUSCH data transmission when retuning is supported.

The sixth device in the eNB searches for at least one PUSCH data transmission mode supported by the eNB and selects a PUSCH data transmission mode therefrom.

Specifically, the sixth device in the eNB searches for at least one PUSCH data transmission method supported by itself, for example, finds out whether the eNB itself only supports the method of puncturing, the method of only supporting rate matching, or the method of two kinds of data mapping. Then, the sixth device in the eNB selects a PUSCH data transmission mode from at least one PUSCH data transmission mode supported by the eNB itself according to the PUSCH data transmission mode supported by the user equipment. For example, if the user equipment only supports the puncturing method but does not support the rate matching method, and the eNB supports both methods, the sixth device in the eNB selects the puncturing method; Both methods are supported, and the eNB also supports both methods, then the sixth device in the eNB selects a rate matching method. That is to say, in the case of giving priority to rate matching, both the eNB and the user equipment must support the selected mode at the same time.

The seventh device in the eNB sends a configuration message to the user equipment according to the selected PUSCH data transmission mode, wherein the configuration message includes configuration parameters for instructing the user equipment to use a corresponding mode for PUSCH data transmission.

Specifically, the seventh device in the eNB sends a configuration message to the corresponding user equipment according to the PUSCH data transmission method selected by the sixth device, for example, if the sixth device in the eNB selects the puncturing method for PUSCH data transmission , the configuration message sent by the seventh device to the user equipment includes configuration parameters for instructing the user equipment to perform PUSCH data transmission in a puncturing manner; if the sixth device in the eNB selects a 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 a rate matching manner.

Preferably, if the user equipment uses the puncturing method as the default method for PUSCH data transmission, when the eNB selects the puncturing method for PUSCH data transmission, it may not send a configuration message to the user equipment, that is, the The user equipment performs PUSCH data transmission in a puncturing manner by default, until it obtains configuration parameters indicating that it performs PUSCH data transmission in a rate-matching manner from the eNB.

Preferably, during the RRC session, when the parameter information indicates that the user equipment supports retune, PUSCH data transmission is performed in a rate matching manner, wherein, if the eNB supports PUSCH data transmission in a rate matching manner, the eNB The sixth means in the eNB uses it as the PUSCH data transmission mode; wherein, the seventh means in the eNB sends an RRC connection reconfiguration message to the user equipment, wherein the RRC connection reconfiguration message includes information for indicating the Describes the configuration parameters for the user equipment to perform PUSCH data transmission in a rate matching manner.

Specifically, during the RRC session, if the parameter information included in the capability parameter sent by the user equipment to the eNB indicates that the user equipment supports retune, the rate matching method is used for PUSCH data transmission, for example, the user equipment actively or should the eNB request, the capability parameter sent to the eNB includes the parameter information pusch-RateMatchingWhenRetuning-r13=supported, which means that the user equipment supports the rate matching method for PUSCH data transmission during retune; Checking the mode, it is found that it also supports PUSCH data transmission in the rate matching mode, then the sixth device in the eNB uses the rate matching mode as the PUSCH data transmission mode; then, the seventh device in the eNB sends to the user equipment The RRC connection reconfiguration message includes the configuration parameter rEMappingMethodWhenRetuning-r13=rateMatching in the RRC connection reconfiguration message, which means that the eNB instructs the user equipment to transmit PUSCH data 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, wherein the configuration message includes instructions for instructing the user equipment to use the rate matching method for PUSCH data transmission. configuration parameters, so that the user equipment adopts a rate matching method to transmit PUSCH data and obtain additional PUSCH decoding gain.

Preferably, the eNB further includes an eighth device. The eighth device in the eNB stores the capability parameter sent by the user equipment as an equipment attribute of the user equipment.

The following uses a preferred embodiment to describe the interaction between the user equipment and the eNB during the RRC process to complete the PUSCH data transmission during retune.

When the eNB receives the RRC Connection Complete message (RRCConnectionComplete), indicating that the user equipment, such as Cat-M UE, completes the initial access; then the eNB triggers ueCapabilityEnquiry, that is, the eNB sends a capability query request to the corresponding user equipment;

According to the capability query request, the user equipment checks its own capability parameters, such as checking its own PUSCH RE mapping capability, or further, checks whether it supports the rate matching mode for PUSCH data transmission during retune;

The user equipment returns capability parameters to the eNB, including parameter information used to indicate whether the user equipment supports rate matching for PUSCH data transmission during retune, for example, the user equipment includes parameter information pusch-RateMatchingWhenRetuning- r13=supported, which means that the UE supports PUSCH data transmission in the rate matching mode during retune;

The eNB stores the capability parameters of the user equipment, for example, stores the capability parameters that the user equipment 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 from it A PUSCH data transmission method, for example, if the eNB also supports the rate matching method, select the rate matching method as the PUSCH data transmission method;

The eNB sends an RRC connection reconfiguration message (RRCConnectionReconfiguration) to the user equipment, and the RRC connection reconfiguration message includes configuration parameters for instructing the user equipment to use the rate matching method for PUSCH data transmission, such as rEMappingMethodWhenRetuning-r13=rateMatching;

The user equipment performs reconfiguration according to the RRC connection reconfiguration message;

The user equipment returns an RRC connection reconfiguration complete message (RRCConnectionReconfigurationComplete) to the eNB;

The user equipment performs PUSCH data transmission in a rate matching manner.

According to still another aspect of the present invention, there is also provided a system for realizing PUSCH data transmission during retune, which includes the user equipment described in any one of the above items and the eNB described in any one of the above items.

It should be noted that the present invention can be implemented in software and/or a combination of software and hardware, for example, it can be implemented by an application specific integrated circuit (ASIC), a general purpose computer or any other similar hardware devices. In one embodiment, the software program of the present invention can be executed by a processor to realize the steps or functions described above. Likewise, the software program (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 floppy disk and the like. In addition, some steps or functions of the present invention may be implemented by hardware, for example, as a circuit that cooperates with a processor to execute each step or function.

In addition, a part of the present invention can be applied as a computer program product, such as a computer program instruction. When it is executed by a computer, the method and/or technical solution according to the present invention can be invoked or provided through the operation of the computer. The program instructions for invoking the method of the present invention may be stored in a fixed or removable recording medium, and/or transmitted through broadcasting or data streams in other signal-carrying media, and/or stored in the in the working memory of the computer device on which the program instructions described above are executed. Here, an embodiment according to the present invention comprises an apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein when the computer program instructions are executed by the processor, a trigger The operation of the device is based on the foregoing methods and/or technical solutions according to multiple embodiments of the present invention.

It will be apparent to those skilled in the art that the invention is not limited to the details of the above-described exemplary embodiments, but that the invention can be embodied in other specific forms without departing from the spirit or essential characteristics of the invention. Accordingly, the embodiments should be regarded in all points of view as exemplary and not restrictive, the scope of the invention being defined by the appended claims rather than the foregoing description, and it is therefore intended that the scope of the invention be defined by the appended claims rather than by the foregoing description. All changes within the meaning and range of equivalents of the elements are embraced in the present invention. Any reference sign in a claim should not be construed as limiting the claim concerned. In addition, 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 stated in the device claims may also be realized by one unit or device through software or hardware. The words first, second, etc. are used to denote names and do not imply any particular order.

Claims (13)

1. PUSCH data transmission methods when a kind of readjustment realized at user equipment end, wherein this method includes：

A sends the ability parameter of the user equipment to corresponding eNB, wherein the ability parameter is described including being used to indicate Whether user equipment is supported to carry out the parameter information of PUSCH data transmissions when resetting using rate-matched mode.

2. according to the method described in claim 1, wherein, the step a includes：

Received from the capability query request transmitted by the eNB；

It is asked according to the capability query, the ability parameter is returned to the eNB, wherein the ability parameter includes being used for Indicate whether the user equipment is supported to carry out the parameter information of PUSCH data transmissions when resetting using rate-matched mode.

3. method according to claim 1 or 2, wherein this method further includes：

In RRC conversation procedures, message is set received from the RRC connection reconfigurations transmitted by the eNB, wherein the RRC connections weight Configuration message includes the configuration ginseng for being used to indicate the user equipment and carrying out PUSCH data transmissions using rate-matched mode Number；

Message is set according to the RRC connection reconfigurations, is set to eNB returns RRC connection reconfigurations and completes message；

In a manner of rate-matched PUSCH data transmissions are carried out to the eNB.

4. PUSCH data transmission methods when a kind of readjustment realized at the ends eNB, wherein this method includes：

A receives the ability parameter transmitted by self-corresponding user equipment, wherein the ability parameter includes being used to indicate the use Whether family equipment is supported to carry out the parameter information of PUSCH data transmissions when resetting using rate-matched mode；

B searches at least one PUSCH data transfer modes that the eNB is supported and therefrom selects a kind of PUSCH data transmissions Mode；

C sends configuration message according to selected PUSCH data transfer modes, to the user equipment, wherein the configuration disappears Breath includes the configuration parameter for being used to indicate the user equipment and carrying out PUSCH data transmissions using corresponded manner.

5. according to the method described in claim 4, wherein, in RRC conversation procedures, when the parameter information indicates the user Equipment is supported using rate-matched mode to carry out PUSCH data transmissions when resetting, wherein the step B includes：

If the eNB supports carry out PUSCH data transmissions in a manner of rate-matched, as the PUSCH data transmissions Mode；

Wherein, the step C includes：

RRC connection reconfigurations are sent to the user equipment and set message, wherein it includes being used for that the RRC connection reconfigurations, which set message, Indicate that the user equipment carries out the configuration parameter of PUSCH data transmissions using rate-matched mode.

6. method according to claim 4 or 5, wherein this method further includes：

Store the ability parameter transmitted by the user equipment, the device attribute as the user equipment.

7. a kind of user equipment for realizing PUSCH data transmissions when resetting, wherein the user equipment includes：

First device, the ability parameter for sending the user equipment to corresponding eNB, wherein the ability parameter includes The parameter letter for carrying out PUSCH data transmissions when whether the user equipment is supported to reset using rate-matched mode be used to indicate Breath.

8. user equipment according to claim 7, wherein the first device is used for：

Received from the capability query request transmitted by the eNB；

It is asked according to the capability query, the ability parameter is returned to the eNB, wherein the ability parameter includes being used for Indicate whether the user equipment is supported to carry out the parameter information of PUSCH data transmissions when resetting using rate-matched mode.

9. user equipment according to claim 7 or 8, wherein the user equipment further includes：

Second device, in RRC conversation procedures, message to be set received from the RRC connection reconfigurations transmitted by the eNB, wherein It includes being used to indicate the user equipment to carry out PUSCH data using rate-matched mode that the RRC connection reconfigurations, which set message, The configuration parameter of transmission；

3rd device sets completion to eNB returns RRC connection reconfigurations and disappears for setting message according to the RRC connection reconfigurations Breath；

4th device, for carrying out PUSCH data transmissions to the eNB in a manner of rate-matched.

10. a kind of eNB realizing PUSCH data transmissions when resetting, wherein the eNB includes：

5th device, for receiving the ability parameter transmitted by self-corresponding user equipment, wherein the ability parameter includes using The parameter information of PUSCH data transmissions is carried out using rate-matched mode when indicating whether the user equipment is supported to reset；

6th device, for search at least one PUSCH data transfer modes that the eNB is supported and therefrom selection it is a kind of PUSCH data transfer modes；

7th device, for according to selected PUSCH data transfer modes, configuration message to be sent to the user equipment, In, the configuration message includes the configuration for being used to indicate the user equipment and carrying out PUSCH data transmissions using corresponded manner Parameter.

11. eNB according to claim 10, wherein in RRC conversation procedures, when the parameter information indicates the use PUSCH data transmissions are carried out using rate-matched mode when family equipment is supported to reset, wherein the 6th device is used for：

If the eNB supports carry out PUSCH data transmissions in a manner of rate-matched, as the PUSCH data transmissions Mode；

Wherein, the 7th device is used for：

RRC connection reconfigurations are sent to the user equipment and set message, wherein it includes being used for that the RRC connection reconfigurations, which set message, Indicate that the user equipment carries out the configuration parameter of PUSCH data transmissions using rate-matched mode.

12. the eNB according to claim 10 or 11, wherein the eNB further includes：

8th device, for storing the ability parameter transmitted by the user equipment, the equipment as the user equipment Attribute.

13. it is a kind of realize reset when PUSCH data transmissions system comprising the use as described in any one of claim 7 to 9 Family equipment and the eNB as described in any one of claim 10 to 12.