Terminal device, base station, and circuit and method for terminal device and base station

Abstract

The present application relates to a terminal device and a base station, as well as circuits and methods for the terminal device and the base station. A terminal device for receiving an acknowledgment message in a random access procedure in a mobile telecommunication system includes a transmitter, a receiver, and a controller, wherein the controller is configured to: send an uplink random access request via the transmitter; receive a downlink allocation message via the receiver, the downlink allocation message being in response to the uplink random access request and indicating downlink resources for sending the downlink message; receive a downlink message using the resources indicated in the downlink allocation message via the receiver; send an uplink message via the transmitter in response to receiving the downlink message; and receive an acknowledgment message regarding the uplink message and using one or more acknowledgment resources via the receiver, wherein the one or more acknowledgment resources are identified based on at least one of the downlink allocation message and the downlink message.

Description

[0001] This application is a divisional application of the Chinese national phase application with an international filing date of September 22, 2016, an international filing number of PCT / EP2016 / 072506, and an invention title of “Method for indicating resources allocated to HARQ messages in a random access process for a low-complexity narrowband terminal”, which had a national phase entry date of March 23, 2018, an application number of 201680055515.9, and an invention title of “Method for indicating resources allocated to HARQ messages in a random access process for a low-complexity narrowband terminal”. Technical Field

[0002] The present disclosure relates to telecommunication devices and methods. Background Art

[0003] The "background" description provided herein is for the purpose of generally presenting the context of the present disclosure. To the extent described in this background section, the work of the inventors presently mentioned and aspects of the description that may not be prior art at the time of filing are neither explicitly nor implicitly admitted to be prior art against the present invention.

[0004] Mobile telecommunication systems, such as those based on the UMTS and Long Term Evolution (LTE) and Long Term Evolution Advanced (LTE-A) architectures defined by 3GPP, are capable of supporting more complex services than the simple voice and messaging services provided by previous generations of mobile telecommunication systems. For example, with the improved radio interface and enhanced data rates provided by LTE systems, users are able to enjoy high data rate applications such as video streaming and video conferencing on mobile communication devices, which were previously only available through fixed-line data connections.

[0005] The expected widespread deployment of third and fourth generation networks has led to the parallel development of a class of devices and applications that exploit not the available high data rates but the increasing ubiquity of the robust radio interface and coverage. Examples include so-called machine type communication (MTC) applications, some of which are represented in some respects by semi-autonomous or autonomous wireless communication devices (MTC devices) that transmit small amounts of data on a relatively infrequent basis. Examples include so-called smart meters, which are located, for example, in a customer's home and periodically send data back to a central MTC server relating to the customer's consumption of utilities such as gas, water, electricity, etc. Smart metering is only one example of potential MTC device applications. More information on the characteristics of MTC type devices can be found, for example, in the corresponding standards, such as 3GPP TS 22.368 Version 13.1.0 Release 13 (2014-12) [1].

[0006] While terminals such as MTC-type terminals can conveniently take advantage of the wide coverage provided by third- or fourth-generation mobile telecommunications networks, there are currently drawbacks. Unlike traditional third- or fourth-generation mobile terminals such as smartphones, a primary driver for MTC-type terminals is the desire for such terminals to be relatively simple and inexpensive. For example, compared to smartphones supporting video streaming, the types of functions typically performed by MTC-type terminals (such as simple collection and reporting / receiving of relatively small amounts of data) do not require particularly complex processing. However, third- and fourth-generation mobile telecommunications networks often employ advanced data modulation techniques and support bandwidth utilization on the radio interface, which may require more complex and expensive radio transceivers and decoders to implement. The inclusion of such complex components in smartphones is generally justified, as smartphones typically require powerful processors to perform typical smartphone-type functions. However, as mentioned above, there is now a desire for relatively inexpensive and less complex devices that are still capable of communicating using LTE-type networks.

[0007] Among the techniques proposed to reduce the complexity, cost and power consumption of these devices, the first is to limit the frequency band in which the devices operate. Currently, it has been proposed that low complexity ("LC") terminals will operate in a bandwidth of no more than 6 physical resource blocks "PRBs". In LTE, 6PRBs correspond to a bandwidth of 1.4MHz. When a terminal is provided with limited bandwidth to provide limited operating capabilities, it is usually referred to as "narrowband". Therefore, the bandwidth of the telecommunications system can be divided into multiple 6PRB narrowbands, and the LC-MTC terminal can be tuned to any one of these narrowbands.

[0008] Another technique for increasing the coverage of MTC and LC-MTC devices is repetition. In this coverage enhancement (CE) function, the coverage of LC-MTC can be extended by up to 15dB (relative to the coverage of Cat-1 terminals) by repeating the symbols or messages sent to the LC-MTC. Using multiple repetitions of the same information, the coverage provided by the base station can be extended.

[0009] While narrowband technology can simplify terminals by reducing the operating bandwidth, thereby reducing cost, complexity, and power consumption, integrating narrowband terminals into legacy systems that have been designed with full-bandwidth terminals in mind can be challenging, and proper operation of the LC terminal can prove difficult when the LC terminal cannot receive signals across the entire system bandwidth of the system. In particular, the terminal is limited in the bandwidth it can receive at a certain point in time, making some existing arrangements and technologies unusable for such terminals. Summary of the Invention

[0010] According to a first exemplary aspect, a method for sending an acknowledgment message in a random access procedure in a mobile telecommunications system is provided. The method comprises: sending an uplink random access request; in response to the random access request, sending a downlink assignment message indicating downlink resources for transmitting the downlink message; sending the downlink message using the resources indicated in the downlink assignment message; in response to receiving the downlink message, sending an uplink message; and sending an acknowledgment message regarding the uplink message and using one or more acknowledgment resources, wherein the one or more acknowledgment resources are identified based on at least one of the downlink assignment message, the downlink message, and the uplink random access request.

[0011] According to a second exemplary aspect, a mobile telecommunication system for sending an acknowledgment message in a random access procedure is provided. The mobile telecommunication system includes a mobile node and a terminal, and is configured to: send an uplink random access request from the terminal to the mobile node; in response to the random access request, send a downlink allocation message from the mobile node to the terminal indicating downlink resources for transmitting a downlink message; send a downlink message from the mobile node to the terminal using the resources indicated in the downlink allocation message; in response to receiving the downlink message, send an uplink message from the terminal to the mobile node; and send an acknowledgment message regarding the uplink message and using one or more acknowledgment resources from the mobile node to the terminal, wherein the one or more acknowledgment resources are identified based on at least one of the downlink allocation message, the downlink message, and the uplink random access request.

[0012] According to a third exemplary aspect, a method for operating a terminal to receive an acknowledgment message in a random access procedure in a mobile telecommunications system is provided. The method comprises: transmitting an uplink random access request; receiving a downlink allocation message in response to the uplink random access request, the downlink allocation message indicating downlink resources for transmitting the downlink message; receiving a downlink message using the resources indicated in the downlink allocation message; transmitting an uplink message via a transmitter in response to receiving the downlink message; and receiving an acknowledgment message regarding the uplink message and using one or more acknowledgment resources via a receiver, wherein the one or more acknowledgment resources are identified based on at least one of the downlink allocation message and the downlink message.

[0013] According to a fourth exemplary aspect, a terminal for receiving an acknowledgment message in a random access procedure in a mobile telecommunications system is provided. The terminal includes a transmitter, a receiver, and a controller, the controller being configured to: transmit an uplink random access request via the transmitter; receive a downlink allocation message in response to the uplink random access request and indicating downlink resources for transmitting a downlink message via the receiver; receive a downlink message using the resources indicated in the downlink allocation message via the receiver; transmit an uplink message via the transmitter in response to receiving the downlink message; and receive an acknowledgment message regarding the uplink message and using one or more acknowledgment resources via the receiver, wherein the one or more acknowledgment resources are identified based on at least one of the downlink allocation message and the downlink message.

[0014] According to a fifth exemplary aspect, an integrated circuit for a terminal is provided for receiving an acknowledgment message in a random access procedure in a mobile telecommunications system. The integrated circuit includes a controller element and a transceiver element, the controller element and the transceiver element being configured to operate together to: send an uplink random access request via the transceiver element; receive a downlink allocation message, responsive to the uplink random access request and indicating downlink resources for transmitting a downlink message, via the transceiver element; receive a downlink message, using the resources indicated in the downlink allocation message, via the transceiver element; in response to receiving the downlink message, send an uplink message via the transceiver element; and receive an acknowledgment message, via the transceiver element, regarding the uplink message and using one or more acknowledgment resources, wherein the one or more acknowledgment resources are identified based on at least one of the downlink allocation message and the downlink message.

[0015] According to a sixth example aspect, a method for operating a mobile node for sending a confirmation message in a random access procedure in a mobile telecommunications system is provided, the method comprising: receiving an uplink random access request via a receiver; sending, in response to the random access request and via a transmitter, a downlink allocation message indicating downlink resources for transmitting a downlink message; sending a downlink message via the transmitter using the resources indicated in the downlink allocation message; receiving an uplink signal of the uplink message via the receiver; and sending a confirmation message regarding the uplink message and using one or more confirmation resources via the transmitter, wherein the one or more confirmation resources are identified based on at least one of the downlink allocation message and the downlink message.

[0016] According to a seventh example aspect, a mobile node is provided for sending a confirmation message in a random access process in a mobile telecommunication system, the mobile node comprising a transmitter, a receiver and a controller, the controller being configured to: receive an uplink random access request via the receiver; send a downlink allocation message indicating downlink resources for transmitting a downlink message in response to the random access request and via the transmitter; send a downlink message via the transmitter using the resources indicated in the downlink allocation message; receive an uplink signal of the uplink message via the receiver; and send a confirmation message regarding the uplink message and using one or more confirmation resources via the transmitter, wherein the one or more confirmation resources are identified based on at least one of the downlink allocation message and the downlink message.

[0017] According to an eighth example aspect, an integrated circuit for a mobile node is provided for sending a confirmation message in a random access procedure in a mobile telecommunications system, wherein the integrated circuit includes a controller element and a transceiver element, and the controller element and the transceiver element are configured to operate together to: receive an uplink random access request via the transceiver element; send a downlink allocation message indicating downlink resources for transmitting a downlink message in response to the random access request and via the transceiver element; send the downlink message via the transceiver element using the resources indicated in the downlink allocation message; receive an uplink signal of the uplink message via the transceiver element; and send a confirmation message regarding the uplink message via the transceiver element; and use one or more confirmation resources, wherein the one or more confirmation resources are identified based on the downlink allocation message and at least one box in the downlink message.

[0018] According to a ninth and a tenth example aspect, there is provided computer software which, when executed by a computer, causes the computer to perform any of the methods discussed above, and a storage medium storing the computer software, respectively.

[0019] Further individual aspects and features are defined by the appended claims.

[0020] The preceding paragraphs are provided by way of general introduction and are not intended to limit the scope of the claims that follow.The described embodiments, together with their advantages, will be best understood by reference to the following detailed description taken in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] A more complete understanding of the present disclosure and many of its attendant advantages may be readily obtained by referring to the following detailed description in conjunction with the accompanying drawings, wherein like reference numerals designate like or corresponding parts throughout the several views, and wherein:

[0022] Figure 1 A schematic diagram illustrating an example of a mobile telecommunications system is provided;

[0023] Figure 2 An example of conventional PUSCH / HARQ timing is shown;

[0024] Figure 3 An example call flow for a conventional RACH procedure is shown;

[0025] Figure 4 is a schematic diagram of narrowband distribution;

[0026] Figure 5 An example of HARQ resource indication using RAR messages is shown;

[0027] Figure 6 An example of HARQ resource indication using a DCI message is shown;

[0028] Figure 7 An example of using RAR messages to indicate the timing and frequency of HARQ resources is shown;

[0029] Figure 8 An example of using a DCI message to indicate HARQ resources is shown;

[0030] Figure 9 An example of using RAR messages and coverage levels to indicate the timing and frequency of HARQ resources is shown;

[0031] Figure 10 An example method for sending an acknowledgement message in a random access procedure is shown; and

[0032] Figure 11 Shown are an example terminal and an example base station in a telecommunications system. DETAILED DESCRIPTION

[0033] Figure 1 A schematic diagram is provided illustrating some basic functionality of a mobile (cellular) telecommunication network / system 100 which, in this example, generally operates according to LTE principles and which may be suitable for implementing embodiments of the present disclosure as further described below. Figure 1The various elements of and their respective modes of operation are well known and defined in the relevant standards managed by the 3GPP (RTM) body and are also described in a number of books on the subject, such as Holma, H. and Toskala, A. [2]. It will be understood that aspects of the operation of the telecommunications network that are not specifically described below may be implemented in accordance with any known technology, such as in accordance with the relevant standards and known variations thereof. Furthermore, it will be appreciated that although some of the specific examples described herein may refer to implementations based on specific 3GPP implementations, the same principles may be applied regardless of the underlying operating principles of the network. That is, the same principles may be applied to wireless telecommunications networks operating in accordance with other standards, whether past, present or yet to be specified.

[0034] The network comprises a plurality of base stations 101 connected to a core network 102. Each base station provides a coverage area 103 (i.e., a cell) in which data can be transmitted to or from a terminal device 104. Data is transmitted from the base station 101 to the terminal device 104 within each coverage area 103 via a radio downlink. Data is transmitted from the terminal device 104 to the base station 101 via a radio uplink. Uplink and downlink communications are carried out using radio resources that can be used by the network operator. The core network 102 routes data to and from the terminal device 104 via each base station 101 and provides functions such as authentication, mobility management, and billing. In addition to the base stations 101 and the terminal devices 104, the system may also include one or more relay nodes / devices. These can be used to enhance coverage for terminal devices operating in one or more associated cells. The deployment of relay nodes (e.g., in terms of their location) can follow commonly established techniques for using relay nodes to support coverage in wireless telecommunications systems. With respect to terminology, it will be understood that a terminal device may also be referred to as a mobile station, user equipment (UE), user terminal, mobile radio, mobile terminal, mobile device, etc. Similarly, a base station may also be referred to as a transceiver station / Node B / e-Node B, etc.

[0035] Mobile telecommunication systems, such as those arranged according to the Long Term Evolution (LTE) architecture defined by 3GPP, use Orthogonal Frequency Division Multiplexing (OFDM) based interfaces for the radio downlink (so-called OFDMA) and the radio uplink (so-called SC-FDMA).

[0036] For MTC terminals, the terminals are less likely to be mobile (e.g., smart meters), but this is not necessary, and are less likely to require high throughput communications with low latency, thus limiting the capabilities of the terminals. For example, using narrowband may not be as problematic for them as it is for traditional terminals. However, one of the challenges faced by narrowband terminals is that the terminal can only use one narrowband at a time. In the case where an LC terminal is communicating with another mobile node, some existing configurations and technologies are no longer available to the terminal. For example, this can become a problem in the random access process, as shown below Figure 2 and Figure 3 The discussion will be obvious, among which Figure 2 shows an example of conventional PUSCH / HARQ timing, and Figure 3 An example call flow is shown for a conventional RACH procedure in an example LTE environment.

[0037] In LTE, uplink traffic is transmitted using the Physical Uplink Shared Channel (PUSCH), in which synchronous HARQ retransmissions are used. In synchronous HARQ transmission, the time position of the PUSCH, HARQ ACK / NACK, and subsequent PUSCH retransmissions are predefined within the HARQ process. For example, Figure 2 In the protocol, the terminal receives an uplink grant (containing scheduling information such as MCS and PRB) from, for example, Downlink Control Information (DCI) carried by the Evolved Physical Downlink Control Channel (EPDCCH) between times t0 and t1. However, the uplink grant does not contain any time information about when the terminal should transmit the PUSCH. As predefined in the communication protocols and conventions, the terminal is expected to send the PUSCH signal in four subframes after receiving the uplink grant, i.e., in the subframes between times t2 and t3. The terminal will then send the PUSCH signal in four subframes after sending the PUSCH, i.e., in the subframes between times t2 and t3. Figure 2 A HARQ ACK / NACK confirmation message is expected from the base station between time t3 and t4 in the UE. If there is a retransmission, for example, the base station fails to correctly receive the PUSCH, the retransmission occurs in the four subframes after the HARQ ACK / NACK is received, that is, in the subframe starting from time t5. While this HARQ process is being executed, up to seven other HARQ processes may occur after time t1 (a total of eight attempts). If the base station does not receive the PUSCH after reaching the maximum number of retransmissions, the transmission fails, and the terminal and the base station will effectively throw the data to the upper layer to recover or retry the transmission. Accordingly, the timing of the HARQ resources is predefined by the resources allocated for PUSCH transmission.

[0038] The frequency resources used to send HARQ messages are also predefined and may depend on whether the HARQ transmission is in adaptive or non-adaptive mode. In current systems, HARQ ACK / NACK messages (acknowledgement messages) can be sent using non-adaptive HARQ or adaptive HARQ, where in non-adaptive HARQ, the base station sends a Physical Hybrid ARQ Indicator Channel (PHICH) message containing the ACK or NACK. If the terminal receives a NACK, it will then retransmit the PUSCH 4 subframes later using the same modulation and coding scheme (MCS) and frequency resources (physical resource blocks "PRBs") as those in the initial uplink grant used for the PUSCH transmission. The PHICH spans the entire system bandwidth. If in adaptive HARQ, the base station then sends an uplink grant using DCI carried by the EPDCCH, which contains the NACK and scheduling information indicating, for example, which PRB (frequency resource) is used for the PUSCH retransmission. In other words, adaptive HARQ gives the base station more scheduling flexibility to use other resources for PUSCH retransmissions than for the original PUSCH transmission. EPDCCH also spans the entire system bandwidth.

[0039] Now turn Figure 3 , illustrating a conventional random access procedure (sometimes referred to as a RACH or PRACH procedure). A terminal performs a RACH procedure in order to connect (or request resources) from the network and may decide to initiate the procedure itself or may be prompted to do so, for example after a paging message. The terminal first sends a message on the Random Access Channel (RACH) using a preamble, and the base station responds on the downlink with a Random Access Response (RAR) message indicating the preamble to which the base station is responding, along with an uplink grant (scheduling information) for the corresponding message 3. In practice, the RAR is scheduled using the PDCCH (in the common search space), for example with a DCI message on the PDCCH (or EPDCCH, if appropriate).

[0040] If the base station acknowledges the terminal's preamble, the terminal will use the PUSCH resources indicated in the uplink grant (in the RAR) to send message 3, which is typically an RRC connection request for initiating an RRC connection. This is usually followed by message 4 in the downlink (e.g., RRC connection establishment) and message 5 in the uplink (e.g., RRC connection establishment complete). Since message 3 is sent via PUSCH, HARQ acknowledgment and (re)transmission apply to this message if appropriate. However, conventional HARQ methods rely on (E)PDCCH and / or send acknowledgments to the terminal on PHICH. Since conventional PHICH & PDCCH occupy the entire system bandwidth, terminals with limited bandwidth capabilities cannot use them, for example, Rel-13+LC-MTC terminals can only receive signals in the 6PRB narrowband and cannot receive signals from wider frequency bands.

[0041] It has been proposed to use MPDCCH, which is based on EPDCCH and can be sent within 6PRBs, to schedule RAR to carry DCI containing scheduling information for RAR. Although the details of the transmission of resource allocation for RAR messages are relevant to this disclosure, they are beyond its scope. Instead, this disclosure is concerned with the transmission of confirmation messages for random access procedures, in particular, the transmission of the third message for random access procedures on the uplink, and the resource allocation for the confirmation messages. It should also be understood that Figure 3 Message 3 in is the first PUSCH transmission from the terminal since idle mode, and the terminal-specific configuration is not yet available at this time. Therefore, if appropriate, HARQ resources need to be configured and selected to enable HARQ retransmission of message 3.

[0042] In one example, the resources used to transmit the confirmation message are based on and can be identified from at least one of an assignment message (e.g., DCI), a downlink message (e.g., RAR) as a response to an uplink random access message (e.g., PRACH preamble message), and an uplink random access request / message (e.g., PRACH preamble message). For example, the resources can be implicitly and / or explicitly indicated by any combination of one or more of the random access request, assignment message, and downlink message. The confirmation is for an uplink message sent in response to a downlink message, which itself was sent in response to an uplink random access request.

[0043] In the following example, it is expected that only some narrow frequency bands in the system bandwidth can be used to send HARQ messages, such as Figure 4As shown, a narrowband distribution is shown. However, it will be understood that the same principles apply if all narrower frequency bands (hereinafter referred to as narrowbands, using current LTE terminology, even though the present disclosure is not limited to the narrowbands currently defined in LTE) in the system bandwidth can be used to send HARQ acknowledgment messages, or if fewer / more / different narrowbands can be used to send acknowledgment messages. Moreover, if only some narrowbands, but not all narrowbands, are available for acknowledgment, the acknowledgment narrowbands may be known to the terminal (e.g., redefined in the standard) or may be transmitted to the terminal. In one example, the resources available for HARQ retransmissions may be sent to the terminal via a broadcast message, such as a system information block (SIB) message sent by a base station to its entire cell. In the examples below, it is generally assumed that different base stations may wish to use different resources for HARQ messages, such that each base station will use SIB transmissions to transmit to all terminals in the cell which resources will be used for HARQ messages, but the present disclosure is not limited to this example.

[0044] Figure 5 The figure shows an example of HARQ resource indication using a RAR message. In this example, the frequency resource used to send the HARQ message for message 3 on the PUSCH is indicated in the RAR message sent in response to the uplink random access message. For example, Figure 5 In

[15] , the system bandwidth consists of 8 narrowbands (each narrowband is 6 PRBs), and the SIB configures these three narrowbands (narrowband 1, narrowband 4, and narrowband 7) as HARQ resources. If DCI-based HARQ ACK / NACK is used, these indicated narrowbands will be the MPDCCH search space, and the LC-MTC terminal will search in the relevant narrowbands (e.g., Figure 5 Therefore, the terminal can deduce from the RAR message which resources will be used to send the HARQ message for message 3 and can thus receive the ACK / NACK message by tuning to the appropriate narrowband to receive the confirmation message.

[0045] Figure 6 An example of HARQ resource indication using DCI message is shown. This example is similar to the example about Figure 5 The example discussed, however, is one in which the indication of the downlink resources used to send the acknowledgement message is provided by a downlink assignment message (e.g., DCI) for a downlink message (e.g., a RAR message). This DCI will then include information about the scheduling of the RAR message, but also about the scheduling of the HARQ message sent in response to the RAR message (Message 3).

[0046] Typically, the resource indication may indicate the frequency resources and / or timing of the resources from which the terminal should search for the acknowledgment message. In one example, the indication may be for one of the narrowbands, and the timing may be derived from the timing of the uplink (e.g., PUSCH) message as described above, while in other cases other timing arrangements may be used, as discussed further below. Also in some configurations, the indication may be an explicit indication, such as resource allocation / scheduling information included in the RAR and / or DCI message, or may be an implicit indication, as shown below.

[0047] While indicating HARQ resources in the RAR and / or DCI message can provide more flexibility in the resources that can be used to send HARQ messages (thereby potentially improving resource utilization), this will increase the size of the RAR and / or DCI messages. Although this impact may be limited or considered insignificant in normal coverage, it may result in longer repetitions in coverage enhancement operations where the DCI and RAR will repeat. To improve this, in some examples, the HARQ resources can be implicitly identified at least in part from any one or more of the random access request, the downlink assignment message, and the corresponding downlink message (in response to the random access request).

[0048] In one example, the acknowledgment (HARQ) resources can be implicitly identified using a link defined between the RACH resources used for the uplink random access request and the HARQ resources used. For example, the link can be defined in the SIB and / or the specification. Typically, the RACH resources include a frequency, time and coding (PRACH preamble) combination. Depending on the preamble selected by the terminal, the resources used for the HARQ message can be identified (if appropriate, also based on additional information). In the case of using three CE levels (i.e., a total of 4 coverage levels if normal coverage is included without repetition), RACH resources can be defined for each CE level, for example. That is, different frequency resources can be used for different CE levels, and / or different preamble codings can be used for different CE levels. For example, there are 64 preamble codes, and if three HARQ resources are defined (e.g., three narrowbands for sending HARQ messages), the terminal can be configured so that terminals in CE level 1 use preamble codes 0 to 21 and HARQ messages will use HARQ resource 1, preamble codes 22 to 42 are used for terminals in CE level 2, and preamble codes 43 to 64 are used for terminals in CE level 3. It will be appreciated that similar relationships can be defined for RACH frequency resources or a combination of frequency and preamble code. In some examples, the time at which a random access request has been sent can also be linked to the resources used for the HARQ message regarding message 3.

[0049] In another example, the HARQ resource is implicitly indicated by the (PDSCH) resource used to send the downlink message (e.g., RAR). RAR is scheduled by DCI and can occupy any configured narrowband, and in one example, the narrowband used can be used to indicate the HARQ resource. For example, if three HARQ resources (HARQ resource 1, HARQ resource 2 & HARQ resource 3) are considered again, and the narrowband used for RAR is narrowband 6, then the HARQ resource can be a function of the narrowband used to transmit the RAR, such as:

[0050] (1) HARQ resource = (narrowband RAR MOD 3)+1

[0051] That is, in this illustrative example, the HARQ resource would be HARQ resource 1. It will be appreciated that this is a MOD function provided for illustration, and that other functions or associations based on downlink (e.g., PDSCH) resources may be used. Furthermore, where repetition and / or frequency hopping is used to send downlink messages (e.g., RAR on PDSCH), then the HARQ resource may be implicitly indicated using a narrowband corresponding to the first or last repetition, e.g., based on convention. Notably, this example of implicit indication from a downlink message also corresponds to Figure 5 A description in which an indication of which resource or resources to use is at least implicitly, rather than explicitly, indicated.

[0052] Similarly, in Figure 6 In the present invention, the acknowledgment resource can be at least partially implicitly identified based on a downlink assignment message (e.g., DCI on an MPDCCH for scheduling RAR), for example, based on the resources used to transmit the downlink assignment message. In one example, the first enhanced control channel element (ECCE) index used in the MPDCCH is used to implicitly indicate the HARQ resource used. An additional or other linkage between the time and / or frequency resources used to transmit the downlink assignment message and the resources used to transmit the acknowledgment message can be used.

[0053] Figure 8 Another example of implicitly indicating the acknowledgement resource using a DCI message is shown. In this example, the HARQ message is carried by the DCI in the MPDCCH search space, and the HARQ resources (i.e., the MPDCCH search space containing the DCI) are the same as the HARQ resources used to schedule the RAR. Figure 8As shown, the terminal first monitors the MPDCCH search space of the DCI that schedules the RAR. The RAR includes scheduling information for Message 3 (PUSCH), and after sending Message 3 (using the PUSCH), the terminal can monitor the same MPDCCH search space (i.e., the same frequency resources and MPDCCH candidate set) used for HARQ ACK / NACK. This timing can be determined as appropriate, for example, after a predetermined time (e.g., 4 subframes) after the uplink transmission of Message 3, or using any other timing determination method. It should be noted that sharing the same MPDCCH search space between DCI and HARQ ACK / NACK messages can lead to congestion. However, this example can provide a relatively simple method for determining HARQ resources.

[0054] Moreover, although the resource indication that can be derived to identify the ACK / NACK resource as discussed above generally discusses identifying the frequency band or frequency resource where the acknowledgment message will be sent, an explicit or implicit indication may also provide the time when the acknowledgment message is to be sent. In some examples, the timing will be automatically selected based on the timing of the uplink message (message 3), for example, 4 subframes later, while in other examples, other timings may be used and they may be identified based on at least one of an uplink random access request (PRACH message), a downlink assignment message (DCI), or a downlink message (RAR). For example, Figure 7 An example of using RAR messages to indicate the timing and frequency of HARQ resources is shown. In this example, the RAR also instructs the terminal (e.g., LC-MTC terminal) to monitor the timing offset of its HARQ ACK / NACK messages. This scenario recognizes that for situations where there may not be enough HARQ resources in the frequency domain, it may be useful to adjust the timing of the acknowledgment message transmission. Therefore, this embodiment allows the HARQ resources to be spread in time. More specifically, in Figure 7 In the example shown, three HARQ resources are configured in the frequency domain. Multiple RARs can be multiplexed into a single MAC message, and if there are not enough resources in the frequency domain, the RAR can indicate one of the HARQ resources in time. If no offset is indicated or a default offset is indicated, the terminal will know the default timing of monitoring the indicated frequency resources (e.g., based on the timing of PUSCH transmission or other). Figure 7In the example shown, the RAR for a particular terminal points to HARQ resource 2 starting at time t2, for example, the default time is time t1. Effectively, this example uses time or timing to indicate the HARQ resource for sending the acknowledgment message. It should be noted that the introduction of a time offset will disrupt the timeline of the currently used PUSCH synchronized HARQ transmissions. However, in some cases, this may be considered acceptable, such as in coverage enhancement operations or repeated operations where the timeline may already be disrupted due to message duplication.

[0055] It should also be noted that the resources used to send the acknowledgment message may span multiple subframes if repetition is implemented and used. HARQ resources may be used for specific coverage levels, for example in the case of three different coverage levels, HARQ resource 1 may be used for (LC-MTC) terminals in coverage level 1, HARQ resource 2 may be used for terminals in coverage level 2 and HARQ resource 3 may be used for terminals in coverage level 3. Different coverage levels will require different numbers of repetitions, so the HARQ resources may span different numbers of subframes depending on the associated number of repetitions. It should also be appreciated that more than one HARQ resource may be configured for a single coverage level. In this example, the RAR may indicate the HARQ resource that has been used and an index (e.g., 2 bits) for the terminal to monitor for HARQ ACK / NACK.

[0056] While implicitly indicating acknowledgment resources, for example, using a defined linkage to another resource (e.g., a RACH message, a RAR message on the PDSCH, an MPDCCHECCE on the DCI, etc.), this can impose limitations on the base station scheduler. For example, once resources linked to HARQ resources have been used, the base station should generally attempt to ensure that the linked HARQ resources remain available in the event that HARQ transmission is required (e.g., if the random access process is not terminated before it completes). This increases complexity for the base station and reduces its flexibility in allocating and scheduling resources for transmission. On the other hand, explicit indication of resources can increase the size of the RAR or DCI, which also imposes limitations. Therefore, in another example, a hybrid implicit / explicit indication can be used. While any combination of implicit and explicit indications as discussed herein can be used, in one example, an implicit indication (e.g., a RACH resource selected by the terminal) can narrow the possible HARQ resources that can be used (e.g., HARQ resource 1 or HARQ resource 2 instead of HARQ resource 3), while reduced explicit signaling in the RAR or DCI message can indicate the precise HARQ resource (e.g., resource 2). For example, in Figure 9, an example of using RACH messages and RAR messages to indicate the timing and frequency of HARQ resources is shown, where three HARQ resources (frequency bands) are available in the frequency domain, where HARQ resource 1 is used for coverage enhancement level 1, HARQ resource 2 is used for coverage enhancement level 2, and HARQ resource 3 is used for coverage enhancement level 3. For example, for HARQ resource 1 and HARQ resource 2, they are also spread out in time in order to make more extensive use of time resources. In this example, the RACH resource used by the LC-MTC terminal will implicitly indicate the coverage enhancement level used, and this will narrow the range of possibilities for HARQ resources. For example, if the RACH resource used corresponds to coverage enhancement level 2, only 1 bit is needed in the RAR to indicate whether HARQ resource 2 starts at time t1 or t3.

[0057] In another illustrative example, the hybrid indication of resources may rely on a RAR or DCI message indicating an offset to a reference HARQ resource. For example, in the case where HARQ ACK / NACK is carried by DCI, the reference HARQ resource may be the MPDCCH search space used to schedule RAR (see, e.g., Figure 8 (discussed in [ 15]), which will provide an implicit indication of the resource (frequency resource) used to send the acknowledgment message. The RAR or DCI message can explicitly indicate the frequency or time offset associated with the resource. For example, if the MPDCCH search space scheduling the RAR is in narrowband 5, the RAR can indicate a frequency offset of +1, indicating that the HARQ resources can be found in narrowband 6.

[0058] Figure 10An example method 1000 for sending an acknowledgment message during a random access procedure is shown. Method 1000 begins, and in S101, an uplink random access request is sent, for example, by a terminal and / or on an uplink random access channel. For example, the uplink message may be a message indicating a preamble and sent on the RACH. Then, in response to the random access request, a downlink (DL) assignment message is sent, for example, by a base station, indicating DL resources for sending a DL message. For example, the DL assignment message may be DCI carried by an MPDCCH. Then, in S103, a DL message is sent, for example, by the base station, using the resources indicated in the DL assignment message. For example, the DL message may be a RAR message carried by a PDSCH. Then, in S104, and in response to receiving the DL message, an UL message is sent, for example, by the terminal. The UL message may correspond to Message 3 in the RACH procedure, for example, for initiating an RRC connection. Then, an acknowledgment message regarding the uplink message is sent using one or more acknowledgment resources (S105), the one or more acknowledgment resources being identified based on at least one of the uplink random access request, the downlink assignment message, and the downlink message. For example, they may be based on any one or more of implicit or explicit indications from an uplink random access request, a downlink assignment message, or a downlink message. Thus, the terminal may identify which resources will be used to send an acknowledgment message and may monitor these resources to determine whether they contain an acknowledgment message for its uplink message. As will be appreciated by those skilled in the art, in this disclosure, when reference is made to an uplink random access request, a downlink assignment message, a downlink message, or an uplink message without more specific information, this is intended to refer to, for example, reference to a random access request, a downlink assignment message, a downlink message, or an uplink message. Figure 10 Although the method 10 may generally be performed by a terminal and a base station, in other examples, they may be performed by different elements, such as by a terminal and a relay node or by a relay node and a base station, respectively.

[0059] Figure 11 Shown are an example terminal and an example base station in a telecommunications system. Figure 11An example terminal (1110) and an example base station (1120) are shown that are configured to communicate with each other and that can implement one or more techniques as described herein. Terminal 1110 includes a receiver 1111 and a transmitter 1112, connected to an antenna for communicating via a wireless interface. The terminal also includes a controller 1113 for controlling at least the receiver and transmitter of terminal 1110. For example, the controller, receiver, and transmitter can be configured to operate together to transmit an uplink random access request via the transmitter; receive a downlink allocation message via the receiver in response to the uplink random access request and indicating downlink resources for transmitting a downlink message; receive a downlink message via the receiver using the resources indicated in the downlink allocation message; transmit an uplink message via the transmitter in response to receiving the downlink message; and transmit an acknowledgment message regarding the uplink message and using one or more acknowledgment resources via the transmitter, wherein the one or more acknowledgment resources are identified based on at least one of the downlink allocation message and the downlink message. Similarly, base station 1120 includes a receiver 1121 and a transmitter 1122 connected to an antenna for communicating via a wireless interface. Base station 1120 also includes a controller 1123 for controlling at least the receiver and transmitter of base station 1120. For example, the controller, receiver, and transmitter can be configured to operate together to receive an uplink random access request via the receiver; transmit a downlink assignment message indicating downlink resources for transmitting the downlink message via the transmitter in response to the random access request; transmit the downlink message via the transmitter using the resources indicated in the downlink assignment message; receive an uplink signal for the uplink message via the receiver; and transmit an acknowledgment message regarding the uplink message via the transmitter using one or more acknowledgment resources, wherein the one or more acknowledgment resources are identified based on at least one of the downlink assignment message and the downlink message. The base station and the terminal can communicate over the air via the wireless interface by transmitting uplink signals from the terminal to the base station and downlink signals from the base station to the terminal.

[0060] although Figure 11 A schematic diagram of a terminal and a base station is shown, but it will be understood that although in the examples of the present disclosure, each terminal includes a transmitter, a receiver and a controller, and each base station includes a transmitter, a receiver and a controller to allow communication between the terminals and / or base stations, the terminals and base stations may be implemented using any suitable technology. For example, the controller may include one or more processor units that are appropriately configured / programmed to provide the desired functionality described herein using conventional programming / configuration techniques for devices in wireless telecommunications systems. For each terminal, in Figure 11The transmitter, receiver, and controller are schematically shown as separate elements for ease of presentation. However, it will be understood that for each terminal, the functionality of these elements may be provided in a variety of different ways, such as using a single appropriately programmed general-purpose computer or appropriately configured (one or more) application-specific integrated circuits / circuits, or using multiple discrete circuits / processing elements for providing different elements of the desired functionality. It will be understood that, depending on established wireless telecommunications technology, a terminal will typically include various other elements associated with its operating functionality (e.g., a power supply, possibly a user interface, etc.).

[0061] Thus, a configuration has been described in which an acknowledgment message can be sent using resources that can be identified by the recipient from any one or more previous messages in the random access procedure, from the random access request to the downlink message in response to the random access. Thus, rather than using a single acknowledgment channel, which may limit resource usage, the acknowledgment message can be sent using more flexible and potentially wider resources, while limiting the amount of resources specifically allocated for acknowledgment.

[0062] It will be appreciated that while the present disclosure has been generally presented in the context of LC-MTC devices, the teachings of the present invention are not limited to this example environment and may be used in other mobile telecommunication environments. For example, a HARQ ACK / NACK message may be understood as simply an example of an acknowledgment message, where the acknowledgment may be used to send only a positive acknowledgment, a negative acknowledgment, or both a positive and negative acknowledgment (e.g., as in HARQ). Similarly, RAR and DCI are examples of downlink messages (in response to a random access request) and downlink assignment requests (for scheduling downlink messages), respectively, using the terminology of the present disclosure.

[0063] Furthermore, while the examples herein generally discuss referring to "HARQ resources," this should be understood as an example of one or more resources. For example, in the context of the above examples, a HARQ resource generally refers to a narrowband that can be used to send acknowledgments. From one perspective, this can be viewed as one resource (a frequency band), and from another perspective, it can be viewed as several resources (e.g., one or more—typically six—PRBs with one or more subframes or frames, etc.).

[0064] Furthermore, the present disclosure is applicable to both non-adaptive HARQ and adaptive HARQ scenarios (or other acknowledgment procedures with both adaptive and non-adaptive modes). That is, in the case of a negative acknowledgment, the negative acknowledgment may indicate resources for retransmission of the uplink message, or may not include any such indication, and the retransmission resources may be determined based on the resources previously used for uplink message transmission.

[0065] In addition, in the event that retransmission is required, the downlink allocation message and / or downlink message for negative acknowledgment may further indicate one or more additional resources for additional acknowledgment messages sent in response to the uplink message retransmission. For example, the DCI carrying the HARQ ACK / NACK for message 3 may further indicate the HARQ resources for the next retransmission of message 3 in the event of NACK. That is, after the LC-MTC terminal sends the first PUSCH message carrying message 3, it will monitor the HARQ resources for HARQ ACK / NACK. If retransmission is required, in addition to notifying the LC-MTC terminal that the acknowledgment message is "NACK", the DCI will also notify the LC-MTC terminal where to monitor the HARQ ACK / NACK after the PUSCH carrying message 3 has been retransmitted. This can provide further flexibility for the base station scheduler.

[0066] In addition, the method steps discussed herein can be performed in any suitable order. For example, the steps can be performed in an order different from the order used in the examples discussed above, or, wherever possible or appropriate, according to the order indicated for enumerating steps elsewhere (e.g., in the claims). Thus, in some cases, some steps can be performed in a different order, or simultaneously or in the same order. As long as the order of execution of any steps of any method discussed herein is technically feasible, it is expressly included in this disclosure.

[0067] As used herein, transmitting information or a message to an element may involve sending one or more messages to the element and may involve sending portions of the information separately from the remaining information. The number of "messages" involved may also vary depending on the layer or granularity considered (e.g., a single MAC message may correspond to multiple REs). Furthermore, transmissions from a terminal to a base station may involve sending any one or more of user data, discovery information, control signaling, and any other type of information to be transmitted.

[0068] Moreover, whenever an aspect is disclosed with respect to a device or system, the teaching of the corresponding method is also disclosed. Similarly, whenever an aspect is disclosed with respect to a method, the teaching for any suitable corresponding device or system is also disclosed. In addition, it is also explicitly disclosed herein that, for any teaching related to a method or system in which it is not clearly specified which or which elements are configured to perform a function or step, any suitable one or more elements that can perform the function can be configured to perform this function or step. For example, as long as it is technically feasible, any one or more mobile terminals (e.g., D2D terminals), relay nodes (e.g., terminal-to-terminal relay nodes), base stations or any other mobile nodes can be configured accordingly.

[0069] Whenever the expressions "greater than" or "less than" or equivalents are used herein, they are intended to disclose both alternatives "and equal to" and "and not equal to," unless one alternative is explicitly excluded.

[0070] It is worth noting that although the present disclosure has been discussed in the context of LTE and / or LC-MTC, its teachings are applicable to, but not limited to, LTE or other 3GPP standards. In particular, although the terminology used herein is generally the same as or similar to that of the LTE standard, the present teachings are not limited to current versions of LTE and may be equally applied to any suitable arrangement that is not based on LTE and / or is compatible with any other future version of LTE or 3GPP or other standards (e.g., the 5G standard).

[0071] Further particular and preferred aspects of the invention are set out in the accompanying independent and dependent claims.It will be understood that features of the dependent claims may be combined with features of the independent claims other than those explicitly set out in a claim.

[0072] Therefore, the above discussion discloses and describes only exemplary embodiments of the present invention. As will be appreciated by those skilled in the art, the present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. Therefore, the disclosure of the present invention is intended to be illustrative, not limiting, of the scope of the present invention and the other claims. This disclosure, including any readily discernible variations taught herein, defines, in part, the scope of the preceding claim terms so that no subject matter of the invention is exclusively available to the public.

[0073] The various technical solutions of the present disclosure are defined by the following numbered items:

[0074] Item 1. A method for sending an acknowledgement message in a random access procedure in a mobile telecommunication system, the method comprising:

[0075] Sending an uplink random access request;

[0076] In response to the random access request, sending a downlink allocation message indicating downlink resources for sending a downlink message;

[0077] sending a downlink message using the resources indicated in the downlink assignment message;

[0078] In response to receiving the downlink message, sending an uplink message; and

[0079] An acknowledgement message is sent regarding the uplink message and using one or more acknowledgement resources, wherein the one or more acknowledgement resources are identified based on at least one of a downlink assignment message, a downlink message, and an uplink random access request.

[0080] Item 2. A method according to any of the preceding items, wherein the downlink message allocates one or more uplink resources for the transmission of an uplink message, and wherein the uplink message is transmitted using the one or more uplink resources.

[0081] Item 3. The method of any preceding item, wherein the one or more acknowledgment resources are identified based at least in part on an acknowledgment resource indicator in the downlink assignment message.

[0082] Item 4. The method of any preceding item, wherein the one or more acknowledgment resources are identified based at least in part on a set of one or more resources used to send a downlink assignment message.

[0083] Item 5. A method according to any of the preceding items, wherein the one or more acknowledgment resources are identified based at least in part on an acknowledgment resource indicator in a downlink message.

[0084] Item 6. The method of any preceding item, wherein the one or more acknowledgment resources are identified based at least in part on a set of one or more resources used to send downlink messages.

[0085] Item 7. The method of any preceding item, wherein the one or more acknowledgment resources are identified based at least in part on a set of one or more resources used to send an uplink random access request.

[0086] Item 8. A method according to any of the preceding items, wherein the one or more confirmation resources are further identified based at least in part on an indication of one or more sets of resources used to send the confirmation message, the indication being included in the broadcast message.

[0087] Clause 9. The method of any preceding clause, wherein the one or more acknowledgment resources are further identified based at least in part on a repetition level for transmission of acknowledgment messages.

[0088] Item 10. The method of any preceding item, wherein at least one of a frequency band and a timing of the one or more confirmation resources is identified based on at least one of a downlink assignment message and a downlink message.

[0089] Item 11. A method according to any one of the preceding items, wherein, if the confirmation message is a negative confirmation, the confirmation message includes

[0090] does not have a negative acknowledgement of the scheduling information for the uplink message retransmission, or

[0091] With negative acknowledgement of scheduling information for uplink message retransmission.

[0092] Item 12. The method according to any one of the preceding items, wherein:

[0093] The downlink assignment message is a Downlink Control Information "DCI" message; and / or

[0094] The downlink message is a Random Access Response "RAR" message; and / or

[0095] The uplink message is used to send a Radio Resource Control "RRC" message for initiating a connection.

[0096] Clause 13. The method of any preceding clause, wherein the confirmation message is used to indicate one of a positive confirmation and a negative confirmation and only one of a positive confirmation.

[0097] Item 14. A mobile telecommunication system for sending an acknowledgement message in a random access procedure, the mobile telecommunication system comprising a mobile node and a terminal, and configured to:

[0098] Sending an uplink random access request from the terminal to the mobile node;

[0099] In response to the random access request, sending a downlink allocation message from the mobile node to the terminal indicating downlink resources for sending a downlink message;

[0100] sending a downlink message from the mobile node to the terminal using the resources indicated in the downlink assignment message;

[0101] sending an uplink message from the terminal to the mobile node in response to receiving the downlink message; and

[0102] An acknowledgement message regarding an uplink message and using one or more acknowledgement resources is sent from the mobile node to the terminal, wherein the one or more acknowledgement resources are identified based on at least one of a downlink assignment message, a downlink message, and an uplink random access request.

[0103] Item 15. A method of operating a terminal for receiving an acknowledgement message in a random access procedure in a mobile telecommunications system, the method comprising:

[0104] Sending an uplink random access request;

[0105] receiving a downlink allocation message in response to the uplink random access request, the downlink allocation message indicating downlink resources for transmitting a downlink message;

[0106] receiving a downlink message using resources indicated in the downlink assignment message;

[0107] sending, via the transmitter, an uplink message in response to receiving the downlink message; and

[0108] An acknowledgement message is received via a receiver regarding the uplink message and using one or more acknowledgement resources, wherein the one or more acknowledgement resources are identified based on at least one of the downlink assignment message and the downlink message.

[0109] Item 16. A terminal for receiving an acknowledgement message in a random access procedure in a mobile telecommunication system, the terminal comprising a transmitter, a receiver, and a controller, the controller being configured to:

[0110] sending, via a transmitter, an uplink random access request;

[0111] receiving, via a receiver, a downlink allocation message in response to the uplink random access request and indicating downlink resources for transmitting a downlink message;

[0112] receiving, via a receiver, a downlink message using resources indicated in the downlink assignment message;

[0113] sending, via the transmitter, an uplink message in response to receiving the downlink message; and

[0114] An acknowledgment message is received via a receiver regarding the uplink message and using one or more acknowledgment resources, wherein the one or more acknowledgment resources are identified based on at least one of the downlink assignment message and the downlink message.

[0115] Item 17. The terminal of Item 16, wherein the controller is configured to identify the one or more acknowledgement resources based on at least one of the received downlink assignment message and the received downlink message.

[0116] Item 18. A terminal according to item 16 or 17, wherein the receiver is configured to receive a signal from a first frequency band and to receive a signal in a second frequency band having a bandwidth not exceeding a bandwidth threshold at any point in time, wherein the second frequency band is within the first frequency band and wherein the bandwidth of the first frequency band exceeds the bandwidth threshold.

[0117] Item 19. An integrated circuit for a terminal, for receiving an acknowledgement message in a random access procedure in a mobile telecommunications system, wherein the integrated circuit comprises a controller element and a transceiver element, the controller element and the transceiver element being configured to operate together to:

[0118] sending, via the transceiver element, an uplink random access request;

[0119] receiving, via the transceiver element, a downlink allocation message in response to the uplink random access request and indicating downlink resources for transmitting a downlink message;

[0120] receiving, via the transceiver element, a downlink message using resources indicated in the downlink assignment message;

[0121] In response to receiving the downlink message, transmitting, via the transceiver element, an uplink message; and

[0122] An acknowledgement message is received via the transceiver element regarding the uplink message and using one or more acknowledgement resources, wherein the one or more acknowledgement resources are identified based on at least one of the downlink assignment message and the downlink message.

[0123] Clause 20. A method of operating a mobile node for sending an acknowledgement message in a random access procedure in a mobile telecommunications system, the method comprising:

[0124] Receiving an uplink random access request via a receiver

[0125] transmitting, in response to the random access request and via a transmitter, a downlink allocation message indicating downlink resources for transmitting a downlink message;

[0126] transmitting, via a transmitter, a downlink message using resources indicated in the downlink assignment message;

[0127] receiving, via a receiver, an uplink signal of an uplink message; and

[0128] An acknowledgment message regarding the uplink message and using one or more acknowledgment resources is transmitted via a transmitter, wherein the one or more acknowledgment resources are identified based on at least one of the downlink assignment message and the downlink message.

[0129] Item 21. A mobile node for sending an acknowledgement message in a random access procedure in a mobile telecommunication system, the mobile node comprising a transmitter, a receiver, and a controller, the controller being configured to:

[0130] Receiving an uplink random access request via a receiver

[0131] transmitting, in response to the random access request and via a transmitter, a downlink allocation message indicating downlink resources for transmitting a downlink message;

[0132] transmitting, via a transmitter, a downlink message using resources indicated in the downlink assignment message;

[0133] receiving, via a receiver, an uplink signal of an uplink message; and

[0134] An acknowledgment message regarding the uplink message and using one or more acknowledgment resources is transmitted via a transmitter, wherein the one or more acknowledgment resources are identified based on at least one of the downlink assignment message and the downlink message.

[0135] Clause 22. An integrated circuit for a mobile node, for sending an acknowledgement message in a random access procedure in a mobile telecommunications system, wherein the integrated circuit comprises a controller element and a transceiver element, the controller element and the transceiver element being configured to operate together to:

[0136] Receiving an uplink random access request via a transceiver element

[0137] transmitting, in response to the random access request and via the transceiver element, a downlink allocation message indicating downlink resources for transmitting a downlink message;

[0138] transmitting, via the transceiver element, a downlink message using resources indicated in the downlink assignment message;

[0139] receiving an uplink signal of an uplink message via the transceiver element; and

[0140] An acknowledgement message is sent via the transceiver element regarding the uplink message and using one or more acknowledgement resources, wherein the one or more acknowledgement resources are identified based on at least one of the downlink assignment message and the downlink message.

[0141] Item 23. Computer software that, when executed by a computer, causes the computer to perform the method of any one of items 1 to 13, 15, and 20.

[0142] Item 24. A storage medium storing computer software according to Item 23.

[0143] Item 25. A method of sending a confirmation message, a mobile telecommunications system for sending a confirmation message, a method of operating a terminal to receive a confirmation message, a terminal for receiving a confirmation message, an integrated circuit of a terminal for receiving a confirmation message, a method of operating a mobile node to send a confirmation message, a mobile node for sending a confirmation message, an integrated circuit of a mobile node for sending a confirmation message, computer software and / or storage medium, substantially as described above with reference to the accompanying drawings.

[0144] Item 26. Any of the preceding items, wherein the base station and the mobile communication device are operable to communicate via a wireless interface using at least one of a 3GPP communication protocol, an LTE communication protocol, a 4G communication protocol, and a 5G communication protocol.

[0145] References

[0146] [1]3GPP TS 22.368version 13.1.0Release 13(2014-12)

[0147] [2]Holma H.and Toskala A.,“LTE for UMTS OFDMA and SC-FDMA based radioaccess”,John Wiley and Sons,2009.

Claims

1. A terminal device for receiving an acknowledgement message in a random access procedure in a mobile telecommunication system, the terminal device comprising a transmitter, a receiver, and a controller, the controller being configured to: sending an uplink random access request via the transmitter; receiving, via the receiver, a downlink control information (DCI) message in response to the uplink random access request and indicating downlink resources for sending a random access response (RAR) message; receiving, via the receiver, the RAR message using resources indicated in the DCI message; In response to receiving the RAR message, sending an uplink message via the transmitter; as well as receiving, via the receiver, an acknowledgment message regarding the uplink message and using one or more acknowledgment resources, The one or more confirmation resources are identified based on information included in the RAR message, and the information indicates the one or more confirmation resources by performing a modulo operation using resources of the RAR message.

2. The terminal device according to claim 1, wherein The controller is further configured to identify the one or more acknowledgement resources based on the received DCI message and the received RAR message.

3. The terminal device according to claim 1, wherein The receiver is configured to receive signals from a first frequency band and to receive signals in a second frequency band whose bandwidth does not exceed a bandwidth threshold at any point in time, wherein the second frequency band is within the first frequency band and wherein the bandwidth of the first frequency band exceeds the bandwidth threshold. The terminal device according to claim 1 , wherein: The information is further included in the DCI message, and The information includes a confirmation resource indicator. The terminal device according to claim 1 , wherein: The information includes a confirmation resource indicator.

6. A circuit for a terminal device, the terminal device being configured to receive an acknowledgement message in a random access procedure in a mobile telecommunications system, the circuit comprising a control circuit and a transceiver circuit, the control circuit and the transceiver circuit being configured to operate together to: sending an uplink random access request via the transceiver circuit; receiving, via the transceiver circuit, a downlink control information (DCI) message in response to the uplink random access request and indicating downlink resources for sending a random access response (RAR) message; receiving, via the transceiver circuit, the RAR message using the resources indicated in the DCI message; In response to receiving the RAR message, sending an uplink message via the transceiver circuit; as well as receiving, via the transceiver circuit, an acknowledgment message regarding the uplink message and using one or more acknowledgment resources, The one or more confirmation resources are identified based on information included in the RAR message, and the information indicates the one or more confirmation resources by performing a modulo operation using resources of the RAR message.

7. The circuit according to claim 6, wherein The control circuitry is further configured to identify the one or more acknowledgement resources based on the received DCI message and the received RAR message.

8. The circuit according to claim 6, wherein The transceiver circuit is configured to receive signals from a first frequency band and receive signals in a second frequency band whose bandwidth does not exceed a bandwidth threshold at any point in time, wherein the second frequency band is within the first frequency band and wherein the bandwidth of the first frequency band exceeds the bandwidth threshold.

9. The circuit according to claim 6, wherein The information is further included in the DCI message, and The information includes a confirmation resource indicator.

10. The circuit according to claim 6, wherein The information includes a confirmation resource indicator.

11. A method of operating a terminal device for receiving an acknowledgement message in a random access procedure in a mobile telecommunication system, the method comprising: Sending an uplink random access request; receiving a downlink control information DCI message, wherein the downlink control information DCI message is in response to the uplink random access request and indicates downlink resources for sending a random access response RAR message; receiving the RAR message using the resources indicated in the DCI message; In response to receiving the RAR message, sending an uplink message; as well as receiving an acknowledgment message regarding the uplink message and using one or more acknowledgment resources, The one or more confirmation resources are identified based on information included in the RAR message, and the information indicates the one or more confirmation resources by performing a modulo operation using resources of the RAR message.

12. A base station for sending a confirmation message in a random access procedure in a mobile telecommunication system, the base station comprising a transmitter, a receiver, and a controller, the controller being configured to: receiving, via the receiver, an uplink random access request; sending, via the transmitter, a downlink control information (DCI) message in response to the uplink random access request and indicating downlink resources for sending a random access response (RAR) message; sending, via the transmitter, the RAR message using the resources indicated in the DCI message; receiving, via the receiver, an uplink signal for an uplink message; sending, via the transmitter, an acknowledgment message regarding the uplink message and using one or more acknowledgment resources, The one or more confirmation resources are identified based on information included in the RAR message, and the information indicates the one or more confirmation resources by performing a modulo operation using resources of the RAR message.

13. The base station according to claim 12, wherein: The information is further included in the DCI message, and The information includes a confirmation resource indicator. The base station according to claim 12 , wherein: The information includes a confirmation resource indicator.

15. A circuit for a base station, the base station being configured to send an acknowledgement message in a random access procedure in a mobile telecommunications system, the circuit comprising a control circuit and a transceiver circuit, the control circuit and the transceiver circuit being configured to operate together to: receiving an uplink random access request via the transceiver circuit; Sending, via the transceiver circuit, a downlink control information DCI message, wherein the downlink control information DCI message responds to the uplink random access request and indicates downlink resources for sending a random access response RAR message; sending, via the transceiver circuit, the RAR message using the resources indicated in the DCI message; receiving, via the transceiver circuit, an uplink signal for an uplink message; sending, via the transceiver circuit, an acknowledgment message regarding the uplink message and using one or more acknowledgment resources, The one or more confirmation resources are identified based on information included in the RAR message, and the information indicates the one or more confirmation resources by performing a modulo operation using resources of the RAR message.

16. The circuit of claim 15, wherein: The information is further included in the DCI message, and The information includes a confirmation resource indicator.

17. The circuit of claim 15, wherein: The information includes a confirmation resource indicator.

18. A method of operating a base station for sending an acknowledgement message in a random access procedure in a mobile telecommunication system, the method comprising: receiving an uplink random access request; Sending a downlink control information DCI message, where the downlink control information DCI message responds to the uplink random access request and indicates downlink resources for sending a random access response RAR message; sending the RAR message using the resources indicated in the DCI message; receiving an uplink signal for an uplink message; sending an acknowledgment message regarding the uplink message and using one or more acknowledgment resources, The one or more confirmation resources are identified based on information included in the RAR message, and the information indicates the one or more confirmation resources by performing a modulo operation using resources of the RAR message.

19. The method according to claim 18, wherein The information is further included in the DCI message, and The information includes a confirmation resource indicator.

20. The method according to claim 18, wherein The information includes a confirmation resource indicator.

Images