Method and apparatus for preventing collision between uplink control messages for LC-MTC devices

Adjusting the PUCCH and PUSCH transmission in the LC-MTC device through processor configuration solves the problem of frequent channel conflicts in the device in the coverage enhancement mode, and improving the spectrum efficiency of the communication system and the reliability of channel transmission.

CN113132953BActive Publication Date: 2024-12-06ALCATEL LUCENT SA
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202110409840.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2015-04-19
Filing Date
2016-04-15
Publication Date
2024-12-06
Estimated Expiration
2036-04-15

AI Technical Summary

Technical Problem

In low-complexity machine-type communication (LC-MTC) devices operating in coverage enhancement mode, conflicts between the physical uplink control channel (PUCCH) and the physical uplink shared control channel (PUSCH) occur frequently, affecting communication The spectrum efficiency of the system.

Method used

Through the processor configuration, determine whether there will be conflict between PUCCH and PUSCH, and adjust the transmission mode of the second uplink control channel when the conflict occurs, including delay, merge, cover, punch, rate matching and interruption, etc., to Avoid conflicts and ensure effective channel transmission.

Benefits of technology

It effectively solves the problem of conflict between PUCCH and PUSCH, improves the spectrum efficiency of the communication system, and ensures reliable transmission of the channel.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113132953B_ABST
    Figure CN113132953B_ABST
Patent Text Reader

Abstract

In an example embodiment, a machine type communication device includes a processor configured to determine whether a first uplink control channel and a second uplink control channel will collide during a transmission from the machine type communication device to a communication network, and if the processor determines that the first control channel and the second control channel will collide, adjust transmission of the second uplink control channel relative to the first uplink control channel.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Related Applications Citations

[0002] This application is a divisional application of the invention patent application with international application number PCT / IB2016 / 000613, international application date April 15, 2016, priority date April 19, 2015, date of entry into the Chinese national phase on October 18, 2017, and Chinese national application number 201680022558.7. Background Art

[0003] A Machine Type Communication (MTC) device is a User Equipment (UE) used by a machine for a specific application (e.g., smart utility meters, parking meters, cars, and home appliances are a few examples of MTC UEs). Work is already underway to enable MTC UEs to operate within communication networks such as the Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) network. In 3GPP Technical Specification Release 12, a work item on Low Complexity MTC (LC-MTC) UEs was completed, according to which the complexity (cost) of MTC UEs was reduced by about 50%. In 3GPP Release 13, another work item has been agreed, according to which the complexity of MTC UEs is further reduced to enhance the coverage of MTC UEs and improve the power consumption of MTC UEs.

[0004] One technique for implementing LC-MTC UEs is to reduce the radio frequency (RF) bandwidth of the LC-MTC UEs to 1.4 MHz [operating with 6 PRBs (where a physical resource block (PRB) is a unit of resource allocation in the frequency domain)]. The LC-MTC UEs can operate in any given system bandwidth and coexist with legacy UEs (e.g., cellular phones, personal digital assistants (PDAs), laptop computers, etc.) within a communication network. In addition, the LC-MTC UEs are able to re-tune the frequency at which the LC-MTC UEs operate so as to operate in a different (1.4 MHz) sub-band within the system bandwidth (e.g., a long term evolution (LTE) communication system) to allow frequency reuse between the LC-MTC UEs and the legacy UEs.

[0005] For LC-MTC UEs operating in coverage enhancement mode, coverage is enhanced by repetition of physical channels. The number of repetitions may be relatively high (hundreds of repetitions), which in turn affects the spectral efficiency of the communication system.

[0006] The physical channels include the physical uplink control channel (PUCCH) and the physical uplink shared control channel (PUSCH). The PUCCH channel carries uplink control information (UCI). The resources [i.e., the physical resource blocks (PRBs) of the PUCCH carrying the UCI] are implicitly determined. The PUSCH channel carries uplink data information. The transmission of the PUSCH is scheduled by the downlink control information (DCI) provided by the serving base station (e.g., serving eNode B) to the LC-MTC UE.

[0007] In conventional systems, the resources used to transmit PUCCH are at the edge of the system bandwidth, which can be used for PUCCH transmission of LC-MTC UEs. Since LC-MTC can only operate within a subband (e.g., 1.4MHz), it is not possible to send both PUCCH and PUSCH at the same time if PUSCH is in another subband. In addition, in conventional systems, if PUCCH and PUSCH transmissions conflict (i.e., are scheduled to be transmitted at the same subframe), the UCI carried by PUCCH can be transmitted by piggybacking PUCCH to PUSCH transmission. For LC-MTC UEs operating in normal coverage mode (non-repetitive), the same mechanism as piggybacking UCI to PUSCH transmission can be used when a PUCCH and PUSCH conflict occurs.

[0008] However, for LC-MTC UEs operating in coverage enhancement mode, PUCCH and PUSCH are repeated and therefore more likely to have PUCCH and PUSCH collisions. In addition, PUSCH carrying a larger payload will experience longer repetitions than in PUCCH. Therefore, unlike the collisions in the above-mentioned conventional systems, the repeatedly sampled portion of the PUSCH or PUCCH transmission encounters a collision due to the difference in the number of repetitions and the start of the repetitions in PUCCH and PUSCH. Summary of the invention

[0009] At least one example embodiment relates to a machine type communication device configured to transmit an uplink control channel to a base station in a communication network.

[0010] In an example embodiment, a machine type communication device includes a processor configured to determine whether a first uplink control channel and a second uplink control channel will collide during transmission from the machine type communication device to a communication network, and if the processor determines that the first control channel and the second control channel will collide, adjust transmission of the second uplink control channel relative to the first uplink control channel.

[0011] In yet another example embodiment, the processor is configured to adjust transmission of the second uplink control channel if a number of collisions between the first control channel and the second control channel is greater than a threshold.

[0012] In yet another example embodiment, the processor is configured to adjust the transmission of the second uplink control channel by delaying the transmission of the second uplink control channel until after the transmission of the first uplink control channel is completed.

[0013] In yet another example embodiment, the processor is configured to adjust transmission of the second uplink channel by attaching the second uplink control channel to the first uplink control channel for transmission to the communication network. Attaching the second uplink control channel to the first uplink control channel may be referred to as merging the second uplink control channel onto the first uplink control channel.

[0014] In yet another example embodiment, the processor is configured to piggyback the second uplink control channel onto the first uplink control channel by mapping samples of the second uplink control channel that will collide with the first uplink control channel to one or more resource elements in a physical resource block associated with the first uplink control channel.

[0015] In yet another example embodiment, the processor is configured to attach a second uplink control channel to the first uplink control channel by puncturing one or more resource elements in a physical resource block associated with the first uplink control channel using uplink control information included in the second uplink control channel.

[0016] In yet another example embodiment, the processor is configured to attach the second uplink control channel to the first uplink control channel by rate matching resource units associated with the first uplink control channel around one or more resource units of the first uplink control channel designated for uplink control information including the second uplink control channel.

[0017] In yet another example embodiment, the processor is configured to attach a second uplink control channel to the first uplink control channel by interrupting transmission of the first uplink control channel, transmitting uplink control information of the second uplink control channel using resource elements in one or more physical resource blocks associated with the first uplink control channel, and resuming transmission of the first uplink control channel after transmission of the uplink control information of the second uplink control channel is completed.

[0018] In yet another example embodiment, the processor is configured to schedule transmission of a second uplink control channel prior to transmission of the first uplink control channel, and attach the second uplink control channel to the first uplink control channel by jointly encoding uplink control information of the second uplink control channel with device-specific information of the machine type communication device for transmission to the communication network.

[0019] In yet another example embodiment, the processor is configured to adjust transmission of the second uplink control channel by suspending transmission of the second uplink control channel if the processor determines that the first uplink control channel and the second uplink control channel will collide during transmission from the machine type communication device to the communication network.

[0020] In yet another example embodiment, the processor is configured to adjust transmission of the second uplink control channel by interrupting transmission of the second uplink control channel if a number of collisions between the first uplink control channel and the second uplink control channel is more than a threshold.

[0021] In yet another example embodiment, the communication network is a Long Term Evolution (LTE) communication network, the machine type communication device is in an enhanced coverage operation mode, the first uplink control channel is a physical uplink shared channel (PUSCH), and the second uplink control channel is a physical uplink control channel (PUCCH).

[0022] In yet another example embodiment, the processor is configured to adjust transmission of the second uplink control channel relative to the first uplink control channel based on a message received from the base station indicating a type of adjustment to be made to transmission of the second uplink control channel relative to the first uplink control channel.

[0023] At least one example embodiment is directed to a method of transmitting, in a communication network, an uplink control channel by a machine type communication network to a base station in the communication network.

[0024] In an example embodiment, the method includes determining, by a machine type communication device, whether a first uplink control channel and a second uplink control channel will collide during transmission by the machine type communication device to a communication network, and adjusting transmission of the second uplink control channel relative to the first uplink control channel if it is determined that the first control channel and the second control channel will collide.

[0025] In yet another example embodiment, if the number of collisions between the first control channel and the second control channel is greater than a threshold, transmission of the second uplink control channel is adjusted.

[0026] In yet another example embodiment, adjusting includes delaying transmission of the second uplink control channel until after transmission of the first uplink control channel is complete.

[0027] In yet another example embodiment, the adjusting includes piggybacking the second uplink control channel onto the first uplink control channel for transmission to the base station.

[0028] In another example embodiment, at least one of the following is additionally included: mapping samples of a second uplink control channel that will conflict with the first uplink control channel to one or more resource elements in a physical resource block associated with the first uplink control channel; puncturing one or more resource elements in a physical resource block associated with the first uplink control channel using uplink control information included in the second uplink control channel; and rate matching the resource elements associated with the first uplink control channel to around one or more resource elements of the first uplink control channel designated for including the uplink control information of the second uplink control channel.

[0029] In yet another example embodiment, the transmission includes interrupting transmission of a first uplink control channel; transmitting uplink control information of a second uplink control channel using resource elements in one or more physical resource blocks associated with the first uplink control channel; and resuming transmission of the first uplink control channel after transmission of the uplink control information of the second uplink control channel is completed.

[0030] In yet another example embodiment, the adjusting comprises one of: suspending transmission of the second uplink control channel if the processor determines that the first uplink control channel and the second uplink control channel will collide during transmission from the machine type communication device to the communication network; or suspending transmission of the second uplink control channel if the number of collisions between the first uplink control channel and the second uplink control channel is greater than a threshold. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The example embodiments will become more understandable through the description of the accompanying drawings, which are not limiting of the example embodiments, in which:

[0032] Figure 1 A communication system including a machine type communication user equipment operating therein is shown according to an example embodiment;

[0033] Figure 2-4 shows time-frequency representations of various downlink and uplink channels transmitted between a base station and a user equipment and different examples of collisions that may occur between uplink channels;

[0034] Figure 5is a flow chart describing the handling of collisions between PUSCH and PUCCH transmissions by an MTC UE according to an example embodiment;

[0035] Figure 6 Shown is pausing transmission of PUSCH to transmit PUCCH and then resuming transmission of PUSCH according to an example embodiment;

[0036] Figure 7 is a flow chart describing the handling of collisions between PUSCH and PUCCH transmissions by an MTC UE according to an example embodiment;

[0037] Figure 8 is a flow chart describing the handling of collisions between PUSCH and PUCCH repetitions by an MTC UE according to an example embodiment;

[0038] Fig. 9 is a flow chart describing the handling of collisions between PUSCH and PUCCH transmissions by an MTC UE according to an example embodiment;

[0039] Fig.10 An exemplary embodiment is shown Figure 1 The base station shown; and

[0040] Fig.11 An exemplary embodiment is shown Figure 1 The machine type communication system shown. DETAILED DESCRIPTION

[0041] Various example embodiments will now be described more fully with reference to the accompanying drawings, in which some example embodiments are shown.

[0042] Detailed illustrative embodiments are disclosed herein. However, for the purpose of describing the exemplary embodiments, the specific structural and functional details disclosed herein are merely representative. However, the present invention can be implemented in many alternative forms and should not be construed as being limited to the embodiments set forth herein.

[0043] Although the example embodiments are capable of various modifications and alternative forms, the embodiments are shown by way of example in the accompanying drawings and will be described in detail herein. However, it should be understood that the example embodiments are not intended to be limited to the specific forms disclosed. On the contrary, the example embodiments will cover all modifications, equivalents, and alternatives that fall within the scope of the present disclosure. Throughout the description of the drawings, similar reference numerals refer to similar components.

[0044] Although the terms first, second, etc. may be used herein to describe various components, these components should not be limited by these terms. These terms are only used to distinguish one component from another component. For example, without departing from the scope of the present disclosure, a first component may be referred to as a second component, and similarly, a second component may be referred to as a first component. As used herein, the term "and / or" includes any and all combinations of one or more of the related listed items.

[0045] When a component is referred to as being "connected" or "coupled" to another component, it may be directly connected or coupled to the other component, or intervening components may be present. In contrast, when a component is referred to as being "directly connected" or "directly coupled" to another component, there are no intervening components. Other words used to describe the relationship between components should be interpreted in a similar manner (e.g., "between" versus "directly between," "adjacent" versus "directly adjacent," etc.).

[0046] The terms used herein are only used for the purpose of describing specific embodiments and are not intended to be limiting. As used herein, the singular forms "a", "an", and "the" are also intended to include the plural forms unless the context clearly indicates otherwise. It will also be understood that the terms "comprise", "include", "includes", and / or "comprising" when used herein specify the presence of stated features, integers, steps, operations, parts, and / or components but do not exclude the presence or addition of one or more other features, integers, steps, operations, parts, components, and / or groups thereof.

[0047] It should also be noted that in some alternative implementations, the functions / actions noted may not be performed in the order shown in the figures. For example, depending on the functions / actions involved, two figures shown in succession may actually be performed substantially simultaneously or may sometimes be performed in reverse order.

[0048] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which the present embodiment belongs. It will also be further understood that terms defined in commonly used dictionaries, for example, should be interpreted as having a meaning consistent with their meaning in the context of the relevant art, and will not be interpreted in an idealized or overly formal manner unless explicitly defined as such.

[0049] Specific details are provided in the following description to provide a thorough understanding of the example embodiments. However, one of ordinary skill in the art will appreciate that the example embodiments may be practiced without these specific details. For example, the system may be shown in block diagram form so as not to obscure the example embodiments with unnecessary details. In other cases, well-known processes, structures, and techniques may be shown without unnecessary details so as not to obscure the example embodiments.

[0050] In the following description, the illustrative embodiments will be described with reference to actions and symbolic representations of operations (e.g., in the form of flowcharts, flow charts, data flow diagrams, structure diagrams, block diagrams, etc.), which may be implemented as program modules or functional processes, which include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types, and may be implemented using existing hardware at existing network elements. Such existing hardware may include one or more central processing units (CPUs), digital signal processors (DSPs), application specific integrated circuits, field programmable gate arrays (FPGAs), computers, etc.

[0051] Although a flow chart may describe operations as a sequential process, many operations may be performed in parallel, concurrently, or simultaneously. In addition, the order of the operations may be rearranged. A process may be terminated when its operations are completed, but may also have additional steps not included in the accompanying drawings. A process may correspond to a method, function, procedure, subroutine, subprogram, etc. When a process corresponds to a function, its termination may correspond to the function returning to the calling function or the main function.

[0052] As disclosed herein, the term "storage medium" or "computer-readable storage medium" may refer to one or more devices for storing data, including read-only memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage media, optical storage media, flash memory devices, and / or other tangible machine-readable media for storing information. The term "computer-readable medium" may include, but is not limited to, portable or fixed storage devices, optical storage devices, and various other media capable of storing, containing, or carrying instructions and / or data.

[0053] In addition, the example embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description language, or any combination thereof. When implemented in software, firmware, middleware, or microcode, the program code or code segments for performing the necessary tasks may be stored in a machine or computer readable medium, such as a computer readable storage medium. When implemented in software, a processor or multiple processors will perform the necessary tasks.

[0054] A code segment may represent any combination of a process, function, subprogram, program, routine, subroutine, module, software package, class, or instruction, data structure, or program statement. A code segment may be coupled to another code segment or a hardware circuit by passing and / or receiving information, data, parameters, coefficients, or memory contents. Information, parameters, coefficients, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.

[0055] Example embodiments may be used in conjunction with RANs such as: Universal Mobile Telecommunications System (UMTS); Global System for Mobile Communications (GSM); Advanced Mobile Phone Service (AMPS) system; Narrowband AMPS system (NAMPS); Total Access Communications System (TACS); Personal Digital Cellular (PDC) system; United States Digital Cellular (USDC) system; Code Division Multiple Access (CDMA) system described in EIA / TIA IS-95; High Rate Packet Data (HRPD) system, Worldwide Interoperability for Microwave Access (WiMAX); Ultra Mobile Broadband (UMB); and Third Generation Partnership Project LTE (3GPP LTE).

[0056] Figure 1 A communication system including a machine type communication user equipment operating therein according to an example embodiment is shown. Figure 1 As shown, the communication network 100 may include a base station 101, a legacy device 102, and one or more MTC UEs 103. The communication network 100 may be a fourth generation (4G)-LTE communication system. However, the communication system 100 is not limited to the 4G-LTE system.

[0057] The base station 101 may be an e-Node B or any other base station (e.g., a small cell base station such as a femtocell base station, a picocell base station), which serves devices such as a traditional device 102 and an MTC UE 103 present in a geographical area covered by the base station 101. Hereinafter, the base station 101 may also be referred to as a serving base station 101.

[0058] The legacy device 102 may be any known or to-be-developed communication device capable of establishing voice and / or data communications with other components within the communication system 100. For example, assuming that the communication system 100 is a 4G-LTE communication system, the legacy device 102 may be any known or to-be-developed device with 4G-LTE capabilities (e.g., a mobile device, PDA, laptop computer, tablet computer, etc. with 4G-LTE capabilities).

[0059] The MTC UE 103, which may also be referred to as an LC MTC UE, may include, but is not limited to, a parking meter, a traffic light, a subway vehicle, a street lamp, a home appliance, or any other type of device that may be configured to establish a connection with other devices and / or users via a network such as the Internet and exchange data with other devices and / or users. The MTC UE may establish a connection to the network through the base station 101.

[0060] Although in Figure 1 A specific number of base stations, legacy devices, and MTC UEs are shown in FIG. 1 , but example embodiments are not limited to Figure 1In addition, the communication system 100 may include other components necessary to establish connections between devices operating within the communication system 100 or to enable connections between the legacy device 102, the MTC UE 103, and the Internet.

[0061] In addition, each of the base station 101, the traditional device 102, and the MTC UE 103 may have a memory and an associated processor. The memory may be configured to store computer-readable instructions in addition to other types of information, so that when the computer-readable instructions are executed by the associated processor, the associated processor becomes a special-purpose machine that configures the base station 101, the traditional device 102, and the MTC UE 103 to perform the functions to be described below. Figure 10-11 To describe the structural configuration of the base station 101 and the MTC UE 103.

[0062] As described above, in the context of MTC UEs 103 operating within the communication system 100, uplink control channels such as a physical uplink shared channel (PUSCH) and a physical uplink control channel (PUCCH) may be repeatedly transmitted from one or more MTC UEs 103 to the base station 101. However, due to the relatively large number of repetitions, collisions may occur between some and / or all of the PUSCH and PUCCH repetitions.

[0063] Figure 2-4 Different examples of time-frequency representations of various downlink and uplink channels transmitted between a base station and a user equipment and possible collisions between uplink channels are shown. Figure 2 In the present invention, on the downlink (DL) side, the base station 101 may repeatedly transmit an enhanced physical downlink control channel (EPDCCH) 210, which may include downlink control information (DCI) for authorizing physical downlink shared control channel (PDSCH) transmission and scheduling of MTC UE 103 to transmit PUSCH to the base station 101, in addition to other types of information known in the art. Also on the DL side, repeated transmissions of EPDCCH 210 may be followed by repeated transmissions of PDSCH 211. PDSCH 211 may carry specific information known in the art.

[0064] On the uplink (UL) side, repetition transmission of PUSCH 212 may start at time point 213. At time point 214 and after repetition transmission of PUSCH 212 starts, repetition transmission of PUCCH 215 may start. Therefore, at time point 214, repetition of PUSCH 212 and repetition of PUCCH 215 collide. The collision may continue until time point 216 when repetition transmission of PUSCH 212 is completed. Thereafter, any remaining repetition transmission of PUCCH 215 may be performed.

[0065] As noted above, the PUSCH 215 carries uplink data information including ACK / NACK messages for the PDSCH 211 sent by the base station 101 to the MTC UE 103. In an example embodiment, the PUCCH 215 carries uplink control information (UCI) on designated resource elements (REs) within one or more physical resource blocks (PRBs) of the PUCCH 215.

[0066] and Figure 2 In comparison, Figure 3 In the embodiment of the present invention, the base station 101 may repeatedly transmit separate EPDCCHs 310-1 and 310-2. The first EPDCCH 310-1 repetition may include DCI grants and transmission scheduling for PUSCH transmissions and other types of information. The second EPDCCH 310-2 repetition may include DCI grants for PDSCH transmissions and other types of information. Still on the DL side, the repeated transmission of the second EPDCCH 310-1 may be followed by repeated transmission of PDSCH 311. PDSCH 311 may carry specific information known in the art.

[0067] Similar to reference Figure 2 As described, on the uplink (UL) side, repetition transmission of PUSCH 312 may start at time point 313. At time point 314 and after repetition transmission of PUSCH 312 starts, repetition transmission of PUCCH 315 may start. Therefore, at time point 315, PUSCH 312 repetition and PUCCH 315 repetition collide. The collision may continue until time point 316 when repetition transmission of PUSCH 312 is completed. Thereafter, any remaining repetition transmission of PUCCH 315 may be performed.

[0068] As described above, the PUSCH 315 carries uplink data information including the ACK / NACK message of the PDSCH 311 sent by the base station 101 to the MTC UE 103. In an example embodiment, the PUCCH 315 carries uplink control information (UCI) on designated resource elements (REs) within one or more physical resource blocks (PRBs) of the PUCCH 315.

[0069] In addition, if Figure 3 As shown, Figure 2 The repetitions of the PUSCH 312 may be longer than shown. The repetitions of the PUSCH 312 may be longer due to, for example, a larger payload that the PUSCH 312 may carry.

[0070] and Figure 2 and Figure 3 On the contrary, Figure 4 In the DL side, the base station 101 repeatedly transmits PDSCH 410 and then repeatedly transmits EPDCCH 411. Figure 2 and Figure 3 In contrast to the example shown, EPDCCH 411 may include only a DCI grant and a transmission schedule for the PUSCH.

[0071] like Figure 4 As shown, on the uplink (UL) side, the MTC UE 103 starts transmission of PUCCH 412 at time point 413. Then at time point 414 and while repeated transmission of PUCCH 214 is ongoing, the MTC UE 103 starts repeated transmission of PUSCH 416. Then, repeated transmission of PUCCH 412 may end at time point 415. Therefore, between time points 414 and 415, repeated transmissions of PUCCH 412 and PUSCH 416 may collide. Thereafter, repeated transmission of PUSCH 416 may continue until, for example, time point 417.

[0072] In the following, example embodiments for handling collisions between PUSCH and PUCCH repetitions on the UL side will be described.

[0073] Figure 5 1 is a flowchart describing the handling of a conflict between a PUSCH transmission and a PUCCH transmission of an MTC UE according to an example embodiment. Figure 5However, the same situation is applicable to any number of MTC UEs 103. Hereinafter, repeated transmissions of PUSCH and PUCCH may be referred to as PUSCH repetition and PUCCH repetition, respectively.

[0074] At S500, the MTC UE 103 determines via an associated processor (not shown) whether PUSCH (first uplink control channel) repetitions and PUCCH (second uplink control channel) repetitions will conflict during transmission from the MTC UE 103 to the base station 101. In an example embodiment, the MTC UE 103 determines whether PUSCH and PUCCH repetitions will conflict by, for example, determining the start time of PUSCH and PUCCH and the repetitions of the two channels to see whether a conflict occurs during repeated transmission of one of the channels. In an example embodiment, the MTC UE 103 determines the start time of PUSCH PUCCH and the number of repetitions of each within several subframes (e.g., one, two, three, four subframes) before transmission of PUSCH and PUCCH starts.

[0075] If at S500 the MTC UE 103 determines that there is no collision between PUSCH and PUCCH repetitions, the MTC UE 103 may repeat S500 for the next scheduled PUSCH and / or PUCCH transmission until the MTC UE 103 detects a collision between PUSCH and PUCCH repetitions.

[0076] However, if the MTC UE 103 determines at S500 that the PUSCH and PUCCH repetitions will collide, then at S510 the MTC UE 103 determines whether the collision period (e.g., the number of collision subframes) between the PUSCH and PUCCH transmissions within a given time window is equal to or greater than a threshold. In an example embodiment, the time window is equal to the longer duration of the PUSCH repetition or the PUCCH repetition.

[0077] In an exemplary embodiment, the threshold value may be set based on empirical research, and may take values ​​such as 30%, 50%, etc. However, the value of the threshold value is not limited to the above-mentioned specific value, and may take any other value.

[0078] In an example embodiment, in order to be able to compare the number of conflicting subframes with the threshold, the MTC UE 103 calculates the number of conflicting subframes and stores the number of conflicting subframes in a memory of the MTC UE 103. Therefore, at S510, the MTC UE 103 may compare the stored number of conflicting subframes with the threshold to determine whether the number of conflicting subframes is greater than the threshold.

[0079] If at S510, the MTC UE 103 determines that the number of collisions is less than a threshold, then at S520, the MTC UE 103 adjusts transmission of one of the PUSCH repetitions and the PUCCH repetitions relative to the other of the PUSCH repetitions and the PUCCH repetitions to avoid further collisions between the PUSCH and the PUCCH repetitions during transmission from the MTC UE 103 to the base station 101. In an example embodiment, the adjustment at S520 includes sequential transmission of the PUCCH repetitions, wherein the PUCCH repetitions are transmitted after the PUSCH repetitions are completed.

[0080] If at S510, the MTC UE 103 determines that the number of collisions is equal to or greater than the threshold, then at S530, the MTC UE 103 adjusts the transmission of one of the PUSCH repetitions and the PUCCH repetitions relative to the other of the PUSCH repetitions and the PUCCH repetitions so as to avoid further collisions between the PUSCH and the PUCCH repetitions during transmission from the MTC UE 103 to the base station 101. In an example embodiment, the adjustment at S530 includes attaching the PUCCH repetitions to the PUSCH repetitions for transmission. The attaching of the PUCCH repetitions to the PUSCH repetitions may also be referred to as merging the PUCCH repetitions with the PUSCH repetitions. The above reference to the above may be performed whenever a scheduled PUSCH and / or PUCCH transmission session starts. Figure 5 S500-S530 describe the process.

[0081] Hereinafter, various exemplary embodiments for performing the accompanying will be described.

[0082] In an example embodiment, the MTC UE 103 performs the attachment by mapping the UCI of the repeated samples of the PUCCH to collide with the PUSCH samples to one or more resource elements (REs) within one or more physical resource blocks (PRBs) of the PUSCH. For example, one or more of the REs within one or more PUSCH PRBs are replaced by symbols of the PUCCH. The PUSCH PRBs to be replaced and the associated REs may be known according to the 3GPP specifications.

[0083] In an example embodiment, the MTC UE 103 performs attachment such that the UCI of repeated symbols of the PUCCH that collide with the PUSCH symbols are punctured to one or more REs within one or more PRBs as specified in the 3GPP specification. In an example embodiment, the PUSCH symbols punctured to one or more REs are implemented by rewriting the corresponding symbols of the PUSCH. An example of puncturing is provided below.

[0084] Assume that PUSCH is normally transmitted with 60 symbols (1 symbol is placed on 1 PUSCH RE). In addition, assume that the UCI of PUCCH requires 10 symbols. According to the puncturing, all PUSCH symbols except the 10 PUSCH symbols are placed on their respective REs. The REs corresponding to the 10 lost PUSCH symbols are overwritten with the 10 symbols of UCI. When decoding PUSCH, the base station 101 will still receive 60 symbols as input, but some symbols are missing, or alternatively, contain irrelevant information.

[0085] In an example embodiment, the MTC UE 103 performs piggybacking such that the PUSCH REs are rate matched around REs of the PUSCH determined to carry UCI information for the PUCCH. In an example embodiment, rate matching refers to a scenario where one or more PUSCH REs are reserved for PUCCH symbols such that the PUSCH symbols are mapped around the PUCCH symbols without PUSCH symbols (even those corresponding to PUSCH REs reserved for PUCCH symbols) being lost. An example of rate matching is provided below.

[0086] Assume that PUSCH is usually transmitted using 60 symbols (1 symbol is placed on 1 PUSCH RE). In addition, assume that the UCI of PUCCH requires 10 symbols. According to rate matching, MTC UE 103 knows that there are only 50 REs left to adapt 50 symbols. Therefore, instead of sending the message using 60 symbols, MTC UE 103 sends PUSCH using 50 symbols and places the PUSCH symbols in their corresponding REs. On the base station side, when decoding PUSCH, base station 101 takes 50 symbols as input instead of receiving 60 symbols and some of them are lost or contain irrelevant information.

[0087] In an example embodiment, the MTC UE 103 performs a sidecar so that all REs in one or more PRBs of the PUSCH carry the UCI of the PUCCH. Dedicating all REs in one or more PRBs of the PUSCH to the UCI of the PUCCH effectively results in suspending the transmission of the PUSCH repetitions so that only the PUCCH repetitions are transmitted. After the transmission of the MTC repetitions is completed, the MTC UE 103 resumes the transmission of the PUSCH repetitions. This will be referred to below Figure 6 Give a description.

[0088] Figure 6 The transmission of PUSCH is suspended to send PUCCH and then resumed according to an example embodiment. Figure 6610-1, 610-2, 611 and 612 are respectively the same as those in the above reference Figure 3 The described 310-1, 310-2, 311, 312 are the same. Therefore, for the sake of brevity, 610-1, 610-2, 611 and 612 will not be described in further detail.

[0089] and Figure 3 Similarly, and in an example embodiment, repeated transmission of PUSCH 612 begins at time point 613. Repeated transmission of PUSCH 612 may then be paused (stopped) at time point 614. At time point 614, repeated transmission of PUCCH 615 may begin until time point 616. Time point 614 may correspond to a time point at which one or more PRBs of PUSCH 612 (all REs of which are dedicated to transmission of PUCCH 615) have been scheduled for transmission. Time point 616 may correspond to a time point at which transmission of one or more PRBs of PUSCH 612 (all REs of which are dedicated to transmission of PUCCH) is completed. At time point 616, MTC UE 103 may resume repeated transmission of PUSCH 612 until a time point such as time point 617.

[0090] Between time points 614 and 616, transmission of PUSCH 612 is interrupted and PUCCH 615 is transmitted instead.

[0091] Referring back to the various example embodiments according to which the MTC UE 103 performs the attachment, in yet another example embodiment, the MTC UE 103 performs the attachment by jointly encoding the UCI (from the PUCCH) and the unicast message and as a single message on the PUSCH. In an example embodiment, the encoding of the UCI includes sending the UCI to the base station 101 at the MAC layer, wherein the UCI is multiplexed with the unicast message prior to encoding. The unicast message may be associated with the PUSCH and include MTC UE 103 specific data.

[0092] In one example embodiment, to encode the UCI, the MTC UE 103 knows the content of the UCI (e.g., whether it is an ACK or a NACK) at the beginning of the transmission of the PUSCH. Therefore, to encode the UCI, the MTC UE 103 may first encode the UCI before initiating the transmission of the PUSCH repetition (e.g., similar to Figure 4 As shown), initiate repeated transmission of PUCCH.

[0093] In addition to handling the conflicts between PUSCH and PUCCH repetitions, Figure 5 , the MTC UE 103 may utilize other methods of handling conflicts as described below.

[0094] Figure 7 is a flow chart describing the handling of collisions between PUSCH and PUCCH transmissions by an MTC UE according to an example embodiment. Figure 7 In the embodiment, S700 is the same as S500. Therefore, for the sake of brevity, S700 will not be described in detail. If at S700, the MTC UE 103 determines that there is a conflict between the PUCCH and PUSCH transmissions, then at S710, the MTC UE 103 stops (e.g., interrupts) the transmission of the PUCCH repetitions. Therefore, the base station 101 may assume a forced NACK message (due to not receiving the PUCCH repetitions) and therefore resend the PDSCH repetitions on the DL channel.

[0095] However, if at S700, the MTC UE 103 determines that there is no conflict between the PUCCH and the PUSCH repetitions, then at S720, the MTC UE 103 transmits the PUCCH and the PUSCH repetitions to the base station 101. Thereafter, the process returns to S700, and steps S700 to S720 may then be repeated by the MTC UE 103 for each scheduled PUSCH and / or PUCCH transmission session.

[0096] Figure 8 is a flow chart describing the handling of conflicts between PUSCH and PUCCH repetitions by an MTC UE according to an example embodiment. Figure 8 In the embodiment, S800 is the same as S500. Therefore, for the sake of brevity, S800 will not be described in detail. If at S800, the MTC UE 103 does not detect any conflict between the PUSCH and PUCCH repetitions, the MTC UE 103 may repeat S800 for the next scheduled PUSCH and / or PUCCH transmission until the MTC UE 103 detects a conflict between the PUSCH and PUCCH repetitions.

[0097] If at S800, the MTC UE 103 determines that there is a conflict between the PUCCH and PUSCH repetitions, then at S810, the MTC UE 103 reiterates the PUCCH in a time window (such as the one described above with reference to FIG. Figure 5 The MTC UE 103 may determine whether the number of conflicts is equal to or greater than a threshold value over a time window described in the embodiment of the present invention. The threshold value may be a configurable value determined based on empirical studies. A non-limiting example of the value of the threshold value is 80%. In an example embodiment, and in order to be able to compare the number of conflicts with the threshold value, the MTC UE 103 may store the number of conflicting subframes in a memory of the MTC UE 103. Therefore, at S810, the MTC UE 103 may compare the stored number of conflicting subframes with the threshold value to determine whether the number of conflicts is greater than the threshold value.

[0098] If at S810, the MTC UE 103 determines that the number of collisions is not equal to or greater than the threshold, the process returns to S800. However, if at S810, the MTC UE 103 determines that the number of collisions is greater than the threshold, then at S820, the MTC UE 103 stops (e.g., does not continue) the repeated transmission of the PUSCH, but keeps (continues) the repeated transmission of the PUCCH. Therefore, since the base station 101 cannot decode the PUSCH (because the PUSCH transmission of the MTC UE 103 has been stopped), the base station 101 can assign another UL to the MTC UE 103 for subsequent retransmission of the PUCCH by the MTC UE 103 to the base station 101.

[0099] The above reference Figure 8 The process described in S800-S820 may be performed whenever a scheduled PUSCH and / or PUCCH transmission session starts.

[0100] Fig. 9 is a flowchart describing the handling of a conflict between PUSCH and PUCCH transmissions by an MTC UE according to an example embodiment. At S900, the MTC UE 103 receives a message from the base station 101. The message may be sent in a DCI included in an EPDCCH sent by the base station 101 to the MTC UE 103. In the case where the MTC UE 103 detects a conflict between a PUSCH and a PUCCH repetition, and if one or more conditions are satisfied (e.g., the threshold number of conflicts described above with respect to one or more example embodiments) such that the MTC UE 103 determines that the transmission of the PUCCH and the PUSCH is to be adjusted, the message may indicate whether the transmission of the PUCCH repetition is to be delayed, or whether the PUCCH is to be attached to the PUSCH repetition.

[0101] exist Fig. 9 In the embodiment, S910 is the same as S500. Therefore, for the sake of brevity, S910 will not be described in detail. If at S910, the MTC UE 103 does not detect any conflict between the PUSCH and PUCCH repetitions, the MTC UE 103 may repeat S910 for the next scheduled PUSCH and / or PUCCH transmission until the MTC UE 103 detects a conflict between the PUSCH and PUCCH repetitions.

[0102] However, if at S910, the MTC UE 103 detects a collision between the PUSCH and the PUCCH repetitions, the process proceeds to S920. If the message received at S900 indicates that the transmission of the PUCCH repetitions will be delayed, at S920, the MTC UE 103 transmits the PUSCH repetitions in a manner similar to that of the PUCCH. Figure 5 The transmission of the PUCCH is adjusted relative to the PUSCH in the same manner as discussed in S520.

[0103] However, if the message received at S900 indicates that the PUCCH repeated transmission is to be attached to the PUSCH repeated transmission, then at S920, the MTC UE 103 transmits the PUCCH repeated transmission as described above. Figure 5 The transmission of PUCCH relative to PUSCH is adjusted in the same manner as discussed in S530.

[0104] In an example embodiment, if the message sent by the base station 101 to the MTC UE 103 indicates that the PUCCH repetition is to be attached to the PUSCH repetition, the MTC UE 103 may increase the PUSCH repetition. The MTC UE 103 may increase the PUSCH repetition because some REs of the PUSCH are used to carry the UCI of the PUCCH to the base station 101. In addition, in an example embodiment, sending the second message 101 by the base station to the MTC UE 103 enables the base station 101 to control the number of PUSCH repetitions.

[0105] The above referenced steps may be performed whenever a scheduled PUSCH and / or PUCCH transmission session starts. Fig. 9 The process of S900-S920 is described.

[0106] As described above, the base station 101 and the one or more MTC UEs 103 may each have a processor and a memory associated therewith for performing the above functions. Fig.10 and 11 A base station 101 and an MTC UE 103 are described.

[0107] Fig.10 An exemplary embodiment is shown Figure 1 The base station shown.

[0108] refer to Fig.10 In the illustrated example embodiment, base station 101 is an eNodeB (eNB) including memory 1050, processor 1060, scheduler 1070, wireless communication interface 1080, and backhaul data and signaling interface (referred to herein as backhaul interface) 1090. Processor or processing circuit 1060 controls the functions of eNB 101 and is operably coupled to memory 1050 and communication interface 1080. Although Fig.10 Only one processor 1060 is shown in FIG. 1 , but it should be understood that multiple processors may be included in a typical eNB such as eNB 101. The functions performed by processor 1060 (i.e., the functions described above with respect to Figure 2-9The functions described herein may be implemented using hardware. As discussed above, such hardware may include one or more central processing units (CPUs), digital signal processors (DSPs), application specific integrated circuits, field programmable gate arrays (FPGAs), computers, etc. The term processor or processing circuit used throughout this document may refer to any of these example implementations, although the term is not limited to these examples.

[0109] Still reference Fig.10 The wireless communication interface 1080 (also referred to as the communication interface 1080) includes various interfaces, including one or more transmitters / receivers (or transceivers) connected to one or more antennas, for wirelessly sending control and data signals to / from traditional devices such as the traditional device 102 and / or the MTC UE 103, or via a control plane.

[0110] The backhaul interface 1090 is connected to other components (not shown) of the communication network 100, including but not limited to: a serving gateway (SGW), a mobility management entity (MME), other eNBs, or other evolved packet core (EPC) network components and / or radio access network (RAN) components within an IP packet data network (IP-CAN).

[0111] The memory 1050 may buffer and store data being processed at the eNB 101 and transmitted to and received from the eNB 101 .

[0112] Still reference Fig.10 The scheduler 1070 schedules the eNB 101 to send data to the legacy device and the MTC UE (such as Figure 1 The conventional device 102 and the MTC UE 103 are shown to send and receive data from the conventional device and the MTC UE (such as Figure 1 The conventional device 102 and the MTC UE 103 are shown receiving control and data communications.

[0113] Fig.11 An exemplary embodiment is shown Figure 1 The machine type communication system shown.

[0114] refer to Fig.11, the MTC UE 103 includes a memory 1155, a processor (or processing circuit) 1165 connected to the memory 1155, various interfaces 1175 connected to the processor 1165, and an antenna 1185 connected to the various interfaces 1175. The various interfaces 1175 and the antenna 1185 may constitute a transceiver for receiving data from / sending data to the eNB 101. It should be understood that, according to an embodiment, the MTC UE 103 may include more than Fig.11 Those components shown are many more components. However, for purposes of disclosing the illustrative example embodiments, not all of these generally conventional components need be shown.

[0115] The memory 1155 may be a computer-readable storage medium that typically includes a random access memory (RAM), a read-only memory (ROM), and / or a permanent mass storage device such as a disk drive. The memory 1155 also stores an operating system and any other routines / modules / applications executed by the processor to provide the functions of the MTC UE 103 (e.g., the functions of the MTC UE, the methods according to the example embodiments, etc.). These software components may also be loaded into the memory 1155 from a separate computer-readable storage medium using a drive mechanism (not shown). Such a separate computer-readable storage medium may include a disk, a tape, a DVD / CD-ROM drive, a memory card, or other similar computer-readable storage medium (not shown). In some embodiments, the software components may be loaded into the memory 1155 via one of the various interfaces 1175 rather than via a computer-readable storage medium.

[0116] The processor 1165 may be configured to execute instructions of a computer program by performing arithmetic, logical, and input / output operations of the system. The instructions may be provided to the processor 1165 by the memory 1155 .

[0117] Various interfaces 1175 may include components that interface the processor 1165 with the antenna 1185 or other input / output components. As will be appreciated, the interface 1175 and the programs stored in the memory 1155 to address the specific functions of the MTC UE 103 will vary depending on the implementation of the MTC UE 103.

[0118] The example embodiments being thus described, it will be obvious that the same may be varied in many ways. Such variations are not to be regarded as a departure from the spirit and scope of the example embodiments, and all such modifications obvious to one skilled in the art are intended to be included within the scope of the claims.

Claims

1. A machine type communication device (103), configured to transmit an uplink control channel in a communication network, the device comprising: The processor (1165) is configured to: determining whether a physical uplink shared channel repetition and a physical uplink control channel repetition will conflict during transmission from the machine type communication device to the communication network, and adjusting the transmission of the physical uplink shared channel repetition relative to the physical uplink control channel repetition by ceasing the transmission of the physical uplink shared channel if the processor determines that the physical uplink shared channel repetition and the physical uplink control channel repetition will conflict, and At least one of the following: The processor is further configured to: wherein the processor is configured to compare the number of collisions to a threshold value, and if the processor determines that the number of collisions is greater than the threshold value, adjust the transmission of the physical uplink shared channel repetition by stopping the transmission of the physical uplink shared channel repetition; The processor is further configured to: compare the number of conflicting subframes between the physical uplink shared channel repetition and the physical uplink control channel repetition with a threshold, and if the processor determines that the number of conflicting subframes between the physical uplink shared channel repetition and the physical uplink control channel repetition is greater than the threshold, adjust the transmission of the physical uplink shared channel repetition by stopping the transmission of the physical uplink shared channel repetition; or The processor is further configured to determine that if the number of collisions is greater than a threshold, the device stops the transmission of the physical uplink shared channel repetitions but maintains the transmission of the physical uplink control channel repetitions.

2. The machine type communication device (103) of claim 1, wherein the device further comprises a computer readable storage medium comprising a program code executable by the processor.

3. A communication method, comprising: determining whether a physical uplink shared channel repetition and a physical uplink control channel repetition will conflict during a transmission from the machine type communication device to the communication network, and adjusting the transmission of the physical uplink shared channel repetition relative to the physical uplink control channel repetition by ceasing the transmission of the physical uplink shared channel if it is determined that the physical uplink shared channel repetition and the physical uplink control channel repetition will conflict, and At least one of the following: comparing the number of collisions to a threshold, and if it is determined that the number of collisions is greater than the threshold, adjusting the transmission of the physical uplink shared channel repetitions by stopping the transmission of the physical uplink shared channel repetitions; comparing the number of conflicting subframes between the physical uplink shared channel repetition and the physical uplink control channel repetition with a threshold, and if it is determined that the number of conflicting subframes between the physical uplink shared channel repetition and the physical uplink control channel repetition is greater than the threshold, adjusting the transmission of the physical uplink shared channel repetition by stopping the transmission of the physical uplink shared channel repetition; or It is determined that if the number of collisions is greater than a threshold, the device stops the transmission of the physical uplink shared channel repetitions but maintains the transmission of the physical uplink control channel repetitions. 4 . The method of claim 3 , wherein the device further comprises a computer-readable storage medium comprising program code executable by a processor.

5. A computer-readable storage medium storing program code, wherein when the program code is executed by a processor, the method according to any one of claims 3 and 4 is performed.

Citation Information

Patent Citations

  • Radio packet collision control system

    JP1989055937A