Methods for communication, terminal devices, and network devices

Abstract

To provide a method, a terminal device, and a network device relating to repetition of transmission during the access procedure.SOLUTION: In a communication system in which a network device and a plurality of terminal devices communicate data and control information in the open air, the network device sets up a resource dedicated to transmission repetition during an access procedure. If the terminal device determines to perform transmission repetition, it uses the dedicated resource, for transmission. The number of repetitions is determined based on target power for transmission and the maximum power at the terminal device. This improves the coverage of the terminal device and increases the success rate of accessing a channel.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly, to methods, terminal devices, and network devices for communication.

Background Art

[0002] Generally, the power level in a terminal device may not be high. While low power consumption can reduce equipment costs, it means lower uplink coverage. In some embodiments, the terminal device can perform retransmission via radio resource control (RRC) signaling to solve coverage problems. However, retransmission during the access procedure still needs to be discussed.

Summary of the Invention

Problems to be Solved by the Invention

[0003] Overall, exemplary embodiments of the present disclosure provide solutions for retransmission of transmissions during an access procedure.

Means for Solving the Problems

[0004] In a first aspect, a communication method is provided. The method includes receiving, at a terminal device, information indicating at least one resource allocated for retransmission of a transmission during an access procedure from a network device. The method further includes determining a target resource based at least in part on the information in accordance with a determination that retransmission of the transmission can be applied during the access procedure. The method further includes transmitting an access request for the access procedure on the target resource.

[0005] In a second embodiment, a communication method is provided. This method includes a network device transmitting information to a terminal device indicating at least one resource allocated for repeated transmissions during an access procedure. The method further includes receiving an access request from the terminal device on a target resource determined at least in part based on such information.

[0006] In a third embodiment, a terminal device is provided. The terminal device comprises a processing unit and a memory coupled to the processing unit in which commands are stored, and when a command is executed by the processing unit, the terminal device is instructed to receive from a network device information indicating at least one resource allocated for repeated transmissions in an access procedure, to determine a target resource at least in part based on the information, in accordance with the determination that repeated transmissions can be applied in the access procedure, and to send an access request for the access procedure on the target resource.

[0007] In a fourth embodiment, a network device is provided. The network device comprises a processing unit and a memory coupled to the processing unit in which commands are stored, and when a command is executed by the processing unit, the network device is caused to transmit to a terminal device information indicating at least one resource allocated for repeated transmissions in an access procedure, and to receive an access request from the terminal device on a target resource determined at least in part based on said information.

[0008] In a fifth embodiment, a computer-readable medium is provided on which instructions are stored. When the instructions are executed on at least one processor, the instructions cause the at least one processor to perform a method according to either the first or second embodiment.

[0009] Other features of this disclosure will be readily apparent from the following description. [Brief explanation of the drawing]

[0010] The drawings further illustrate some embodiments of this disclosure in more detail, thereby further clarifying the aforementioned and other objectives, features, and advantages of this disclosure.

[0011] [Figure 1] This is a schematic diagram of a communication environment in which the embodiments of this disclosure can be implemented.

[0012] [Figure 2] This is a signaling diagram illustrating the process according to the embodiments of this disclosure.

[0013] [Figure 3] This is a flowchart of an exemplary method according to an embodiment of the present disclosure.

[0014] [Figure 4] This is a flowchart of an exemplary method according to an embodiment of the present disclosure.

[0015] [Figure 5] This is a schematic block diagram of a device suitable for implementing an embodiment of the present disclosure.

[0016] In the diagram, identical or similar reference numbers represent identical or similar elements. [Modes for carrying out the invention]

[0017] The principles of this disclosure are described here with reference to several exemplary embodiments. These embodiments are provided for illustrative purposes only and are intended to help those skilled in the art understand and implement this disclosure, and should be understood as not implying any limitation on the scope of this disclosure. The disclosures described herein can be implemented in a variety of ways different from those described below.

[0018] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meanings as those generally understood by those skilled in the art.

[0019] As used in this text, the term “network device” means a device capable of providing or hosting a cell or coverage on which terminal devices can communicate. Examples of network devices include, but are not limited to, Node B (NodeB or NB), Evolutionary Node B (eNodeB or eNB), Node B for New Radio Access (gNB), Remote Radio Unit (RRU), Radio Head (RH), Remote Radio Head (RRH), low-power nodes such as femtonodes and piconodes, star network devices, and aircraft network devices. For illustrative purposes, several exemplary embodiments of a network device will be described below with reference to an eNB.

[0020] As used in this text, the term “terminal device” means any device having wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to, user devices (UEs), personal computers, desktop computers, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, any Internet of Things (IoE) devices, machine-type communication (MTC) devices, and in-vehicle devices for V2X communication, where the “X” in V2X represents pedestrians, vehicles or infrastructure / networks, or image acquisition devices such as digital cameras, game consoles, music storage and playback devices, or internet-connected home appliances that enable wireless or wired internet access and browsing. In the following description, the terms “terminal device,” “communication device,” “terminal,” “user device,” and “UE” can be used interchangeably.

[0021] The communications described in this specification can comply with any suitable standard, including but not limited to New Radio (NR), Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), cdma2000, and Global System for Mobile Communications (GSM). Further, the communications can be performed according to any generation of communication protocol, currently known or to be developed in the future. Examples of communication protocols include, but are not limited to, the first generation (1G), second generation (2G), 2.5G, 2.85G, third generation (3G), fourth generation (4G), 4.5G, and fifth generation (5G) communication protocols. The techniques described in the present text can be used in the above-mentioned wireless networks and wireless technologies, as well as other wireless networks and wireless technologies.

[0022] As used herein, the singular forms "a", "an", and "the" include the plural forms as well, unless the context clearly dictates otherwise. The terms "comprises" and variations thereof should be understood as open-ended terms meaning "including, but not limited to". The term "based on" should be understood as "at least partially based on". The terms "one embodiment" and "an embodiment" should be understood as "at least one embodiment". The term "another embodiment" should be understood as "at least one other embodiment". The terms "first", "second", etc. can refer to different or the same object. Other explicit and implicit definitions may be included hereinafter.

[0023] In some instances, values, procedures, or devices are referred to as "best", "lowest", "highest", "minimum", "maximum", etc. Such descriptions are intended to indicate that a selection can be made from among many available functional alternatives, and it should be understood that such a selection need not be better, smaller, higher, or otherwise more preferred than other selections.

[0024] In a conventional communication system, the power level in a terminal device may not be high. While low power consumption can reduce equipment costs, it means lower uplink coverage. In some embodiments, the terminal device can perform retransmission via radio resource control (RRC) signaling to solve the coverage problem.

[0025] When transmitting a physical uplink shared channel (PUSCH) scheduled by downlink control information within a physical downlink control channel (PDCCH), if the terminal device is configured with pusch-AggregationFactor, apply the same symbol allocation over pusch-AggregationFactor consecutive slots and limit the PUSCH to a single transmission layer. The terminal device should repeat the transport block over pusch-AggregationFactor consecutive slots where the same symbol allocation is applied within each slot.

[0026] For PUCCH format 1, 3, or 4, the terminal device can be configured to use multiple time slots for PUCCH transmission repetition according to respective nrofSlots. Before dedicated RRC configuration, there is no repetition on PUSCH and PUCCH.

[0027] According to the prior art, the terminal device can determine the coverage enhancement level required by the terminal device and repeatedly transmit a physical random access channel (PRACH) signal. However, there has been no discussion on how to determine the coverage extension level.

[0028] In other prior art, repetitions may be determined based on the selected transport block size. However, the low-power problem in terminal devices remains unresolved. Therefore, further research is needed on methods for signaling more PUSCH / PUCCH repetitions in the RRC signal, and for signaling and executing repeated PUSCH messages and repeated HARQ-ACK feedback of msg4 on PUCCH.

[0029] To solve at least some of the above problems, a new technique for repeated transmissions during an access procedure is needed. According to embodiments of this disclosure, a network device can configure a resource dedicated to repeated transmissions during an access procedure. When a terminal device decides to perform repeated transmissions, the terminal device uses this dedicated resource for transmission. The number of repetitions is determined based on the target power for transmission and the maximum power on the terminal device. This improves the coverage of the terminal device and increases the success rate of accessing the channel.

[0030] Figure 1 is a schematic diagram of a communication system that can implement an embodiment of the present disclosure. The communication system 100, which is part of a communication network, comprises terminal device 110-1, terminal device 110-2, ..., terminal device 110-N, which can be collectively referred to as "terminal device 110".

[0031] The communication system 100 further includes a network device 120. In the communication system 100, the network device 120 and the terminal device 110 can communicate data and control information with each other. The number of terminal devices and network devices shown in Figure 1 is for illustrative purposes only and does not imply any limitation.

[0032] Communication in communication system 100 can be implemented according to any suitable communication protocol, including but not limited to, cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), and fifth-generation (5G), wireless local area network communication protocols such as IEEE 802.11, and / or any other protocols currently known or to be developed in the future. Furthermore, communication can utilize any suitable wireless communication technology, including but not limited to code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplexer (FDD), time division duplexer (TDD), multi-input multiple-output (MIMO), orthogonal frequency division multiple access (OFDMA), and / or any other technologies currently known or to be developed in the future.

[0033] Embodiments of the present disclosure are described in detail below. First, we refer to Figure 2, which shows a signaling diagram illustrating an interaction 200 between network devices according to some exemplary embodiments of the present disclosure. For illustrative purposes only, we will describe process 200 with reference to Figure 1. Process 200 may involve terminal device 110-1 and network device 120 in Figure 1.

[0034] The network device 120 transmits information to the terminal device 110-1 (2005). This information indicates one or more resources allocated for repeated transmissions during the access procedure. The resources may be dedicated PRACH resources. Alternatively, the resources may be different preamble indices. This information can be transmitted via an RRC system information block. It should be noted that this information can be transmitted by any appropriate signaling.

[0035] In some embodiments, the terminal device 110-1 can determine the number of transmission repetitions based on the target power of the transmission and the power available in the terminal device 110-1 (2010). For example, the available power may be the maximum power of the terminal device 110-1. For example, the margin power of the terminal device 110-1 can be determined based on the following formula. (Math 1) S = P_target + PL - P_available (1) Here, P_target is the target power provided by the upper layer (e.g., PREAMBLE_RECEIVED_TARGET_POWER), PL is the path loss, and P_available is the maximum power at terminal device 110-1. In this case, the transmit power during the access procedure is minimum(P_available, P_target + PL).

[0036] For example, repeating factors represented by "N" can be obtained from Table 1. It should be noted that the values ​​in Table 1 are merely examples and not restrictions. [Table 1]

[0037] In some embodiments, the terminal device 110-1 can determine that the number of repetitions "Nm" is equal to the selected repetition factor N. Alternatively, the number of repetitions may be greater than the selected repetition factor N. S can be calculated only for the first PRACH transmission, and the selected N can be used for the remaining PRACH processes.

[0038] In some embodiments, the terminal device 110-1 can determine Nm, which is a repeating value, such that the minimum value set by the RRC is greater than or equal to a selected N. If the authorized radio network temporary identifier (RNTI) is equal to the temporary cell radio network temporary identifier (TC-RNTI) in the Random Access Response (RAR), the terminal device 110-1 can use Nm in the RAR for subsequent transmissions.

[0039] Terminal device 110-1 determines the target resource based at least partially on this information (2015). This enables repeated transmissions during the access procedure. The success rate of the access procedure is improved because the repetitions can be adjusted based on the terminal device's power.

[0040] In some embodiments, resources may be set for each repetition. For example, the network device 120 may set different preambles for different numbers of repetitions. In other embodiments, the network device 120 may set different PRACH resources for different numbers of repetitions. As an example, this information may include "Msg3-repetition4-preamble-list SEQUENCE of (1..maxPreamblePerRepetation) integer (1..64)" used to set the PRACH preamble for repeating the PUSCH transmission four times.

[0041] In another exemplary embodiment, this information may indicate that preamble indices 11-20 are used for 4 repetitions and preamble indices 21-30 are used for 8 repetitions. In this case, if terminal device 110-1 determines that the number of repetitions is 4 according to Table 1, terminal device 110-1 can select a preamble from preambles 11-20.

[0042] Alternatively, resources can be allocated for each repetition. In this case, if terminal device 110-1 decides to perform a repetition of transmission, the target resource can be determined based on that information. This allows network device 120 to understand that terminal device 110-1 supports repetition.

[0043] Terminal device 110-1 sends an access request (2020) to network device 120. In some embodiments, terminal device 110-1 can send message 1 to network device 120. For example, if terminal device 110-1 determines that the number of repetitions is 4, terminal device 110-1 can send the preamble index in Msg3-repetition4-preamble-list. Alternatively, terminal device 110-1 can send message A to network device 120. Similarly, if terminal device 110-1 determines that the number of repetitions is 4, terminal device 110-1 may send the preamble index in the preamble list assigned to message A.

[0044] In some embodiments, the network device 120 can determine the number of iterations (2025). For example, the network device 120 can estimate the available power at terminal device 110-1 based on the received access request. The network device 120 can compare the estimated power with the target power and determine the number of iterations based on the comparison. As an example, the network device 120 can determine the number of iterations according to Table 1 above. For example, if the difference between the target power and the estimated power is less than 1 and greater than 0, the network device 120 can determine that the number of iterations is 2.

[0045] The network device 120 sends an access response to the terminal device 110-1 (2030). For example, the network device 120 may send message 2 to the terminal device 110-1. Alternatively, the network device 120 may send message B to the terminal device 110-1. In some embodiments, the access response (e.g., message 2) may indicate the number of repetitions determined by the network device 120. It should be noted that the access response may also indicate other resource allocations. For example, the access response may include one or more wireless network temporary identifiers.

[0046] Alternatively or additionally, terminal device 110-1 may send connection requests to network device 120 (2035) based on the number of repetitions. For example, terminal device 110-1 may resend message 3 to network device 120 based on the number of repetitions. In some embodiments, terminal device 110-1 may use the number of repetitions "Nm" as the push-AggregationFactor for sending message 3 PUSCH. Alternatively, terminal device 110-1 may use the number of repetitions "Nm" as the nrofSlots for PUCCH transmission.

[0047] In an exemplary embodiment, terminal device 110-1 may determine time resources for a connection request based on Table 2 below. For example, there may be a 4-bit PUSCH time resource allocation field. Table 2 can combine encoding the number of repetitions and other PUSCH resource application parameters. It should be noted that the parameters in Table 2 are examples only and not limitations. [Table 2]

[0048] In some embodiments, the network device 120 can send a connection response (2040). For example, the network device 120 can send message 4 to the terminal device 110-1. The terminal device 110-1 can send feedback to the network device 120 (2045). In some embodiments, the terminal device 110-1 can resend the feedback based on the number of repetitions.

[0049] The network device 120 can send an instruction (2050) to the terminal device 110-1. This instruction may include the number of supported iteration extensions after the access procedure. For example, it may send a new RRC parameter, push-AggregationFactor-extend.

[0050] In some embodiments, the number of iterations can be extended to, for example, 16, 32, or any appropriate number. For example, if push-AggregationFactor-extend exists and push-AggregationFactor does not exist, it means that the number of iterations has been extended to 16 and 32.

[0051] Alternatively, if `pusch-AggregationFactor` does not exist but `pusch-AggregationFactor-extend` does, the number of iterations can be up to 16. If both `pusch-AggregationFactor` and `pusch-AggregationFactor-extend` exist, the number of iterations is the value of `pusch-AggregationFactor-extend` multiplied by the value of `pusch-AggregationFactor`, for example, 32, 64, or 128. It should be noted that the number of iterations can be any appropriate number.

[0052] According to embodiments of this disclosure, terminal device coverage can be improved. Even when the terminal device has insufficient power, it can still access the channel. Furthermore, for scenarios with limited coverage or lower power devices, uplink coverage performance can be further improved.

[0053] Figure 3 is a flowchart of an exemplary method 300 according to an embodiment of the present disclosure. For illustrative purposes only, method 300 can be implemented in a terminal device 110-1 as shown in Figure 1.

[0054] In block 310, terminal device 110-1 receives information from network device 120. This information indicates one or more resources allocated for repeated transmissions during an access procedure. The resources may be dedicated physical random access channel (PRACH) resources. Alternatively, the resources may be different preamble indices. This information can be transmitted via a radio resource control (RRC) system information block. It should be noted that this information can be transmitted by any appropriate signaling.

[0055] In block 320, if repeated transmissions can be applied during the access procedure, the terminal device 110-1 determines the target resource based at least partially on this information. This enables repeated transmissions during the access procedure. Since the repetitions can be adjusted based on the terminal device's power, the success rate of the access procedure is improved.

[0056] In some embodiments, the terminal device 110-1 can determine the number of transmission repetitions based on the target power of the transmission and the power available in the terminal device 110-1 (2010). For example, the available power may be the maximum power of the terminal device 110-1.

[0057] In some embodiments, resources may be set for each repetition. For example, the network device 120 may set different preambles for different numbers of repetitions. In other embodiments, the network device 120 may set different PRACH resources for different numbers of repetitions. As an example, this information may include "Msg3-repetition4-preamble-list SEQUENCE of (1..maxPreamblePerRepetation) integer (1..64)" used to set the PRACH preamble for repeating the PUSCH transmission four times.

[0058] In another exemplary embodiment, this information may indicate that preamble indices 11-20 are used for 4 repetitions and preamble indices 21-30 are used for 8 repetitions. In this case, if terminal device 110-1 determines that the number of repetitions is 4 according to Table 1, terminal device 110-1 can select a preamble from preambles 11-20.

[0059] Alternatively, resources can be allocated for each repetition. In this case, if terminal device 110-1 decides to perform a repetition of transmission, the target resource can be determined based on that information. This allows network device 120 to understand that terminal device 110-1 supports repetition.

[0060] In some embodiments, the terminal device 110-1 can determine Nm, which is repeated such that the minimum value set by the RRC is greater than or equal to a selected N. If the authorized radio network temporary identifier (RNTI) is equal to the temporary cell radio network temporary identifier (TC-RNTI) in the RAR, the terminal device 110-1 can use Nm in the RAR for subsequent transmissions.

[0061] In block 330, terminal device 110-1 sends an access request to network device 120. In some embodiments, terminal device 110-1 can send message 1 to network device 120. For example, if terminal device 110-1 determines that the number of repetitions is 4, terminal device 110-1 can send the preamble index in Msg3-repetition4-preamble-list. Alternatively, terminal device 110-1 can send message A to network device 120. Similarly, if terminal device 110-1 determines that the number of repetitions is 4, terminal device 110-1 may send the preamble index in the preamble list assigned to message A. In some embodiments, terminal device 110-1 can receive an access response from network device 120. The access response may indicate the number of repetitions in the access procedure determined by network device 120.

[0062] Alternatively or additionally, terminal device 110-1 may send a connection request to network device 120 based on the number of repetitions. For example, terminal device 110-1 may resend message 3 to network device 120 based on the number of repetitions. In some embodiments, terminal device 110-1 may use the number of repetitions "Nm" as the push-AggregationFactor for sending message 3 PUSCH. Alternatively, terminal device 110-1 may use the number of repetitions "Nm" as the nrofSlots for PUCCH transmission.

[0063] In an exemplary embodiment, terminal device 110-1 can determine the time resources for a connection request based on Table 2 above. For example, there may be a 4-bit PUSCH time resource allocation field.

[0064] In some embodiments, the terminal device 110-1 can send feedback to the network device 120. In some embodiments, the terminal device 110-1 can resend the feedback based on the number of repetitions.

[0065] Terminal device 110-1 can receive instructions from network device 120. These instructions may include the number of repetition extensions supported after the access procedure. For example, a new RRC parameter, push-AggregationFactor-extend, can be sent.

[0066] In some embodiments, the number of iterations can be extended to, for example, 16, 32, or any appropriate number. For example, if push-AggregationFactor-extend exists and push-AggregationFactor does not exist, it means that the number of iterations has been extended to 16 and 32.

[0067] Alternatively, if `pusch-AggregationFactor` does not exist but `pusch-AggregationFactor-extend` does, the number of iterations can be up to 16. If both `pusch-AggregationFactor` and `pusch-AggregationFactor-extend` exist, the number of iterations is the value of `pusch-AggregationFactor-extend` multiplied by the value of `pusch-AggregationFactor`, for example, 32, 64, or 128. It should be noted that the number of iterations can be any appropriate number.

[0068] Figure 4 is a flowchart of an exemplary method 400 according to an embodiment of the present disclosure. For illustrative purposes only, method 400 can be implemented in a network device 120-1 as shown in Figure 1.

[0069] In block 410, the network device 120 transmits information to the terminal device 110-1. This information indicates one or more resources allocated for repeated transmissions during the access procedure. The resources may be dedicated PRACH resources. Alternatively, the resources may be different preamble indices. This information can be transmitted via the RRC system information block. It should be noted that this information can be transmitted by any appropriate signaling.

[0070] In some embodiments, resources may be configured for each iteration. For example, the network device 120 may configure different preambles for different numbers of iterations. In other embodiments, the network device 120 may configure different PRACH resources for different numbers of iterations. Alternatively, resources may be allocated for all iterations.

[0071] In some embodiments, the network device 120 can determine the number of iterations (2025). For example, the network device 120 can estimate the available power in the terminal device 110-1 based on the received access request. The network device 120 can compare the estimated power with the target power and determine the number of iterations based on the comparison.

[0072] In block 420, the network device 120 sends an access response to the terminal device 110-1. For example, the network device 120 may send message 2 to the terminal device 110-1. Alternatively, the network device 120 may send message B to the terminal device 110-1. In some embodiments, the access response may indicate the number of repetitions determined by the network device 120. It should be noted that the access response may also indicate other resource allocations. For example, the access response may include one or more wireless network temporary identifiers.

[0073] In some embodiments, the network device 120 can send a connection response. For example, the network device 120 can send message 4 to the terminal device 110-1. The network device 120 can send instructions to the terminal device 110-1. These instructions may include the number of repetitions after an extended, supported access procedure. For example, a new RRC parameter, push-AggregationFactor-extend, can be sent.

[0074] In some embodiments, the number of iterations can be extended to, for example, 16, 32, or any appropriate number. For example, if push-AggregationFactor-extend exists and push-AggregationFactor does not exist, it means that the number of iterations has been extended to 16 and 32.

[0075] Alternatively, if `pusch-AggregationFactor` does not exist but `pusch-AggregationFactor-extend` does, the number of iterations can be up to 16. If both `pusch-AggregationFactor` and `pusch-AggregationFactor-extend` exist, the number of iterations is the value of `pusch-AggregationFactor-extend` multiplied by the value of `pusch-AggregationFactor`, for example, 32, 64, or 128. It should be noted that the number of iterations can be any appropriate number.

[0076] Figure 5 is a schematic block diagram of a device 500 suitable for implementing an embodiment of the present disclosure. The device 500 can be considered as another exemplary embodiment of the terminal device 110 and network device 120 shown in Figure 1. Therefore, the device 500 can be implemented in the terminal device 110 or the network device 120, or as at least a part thereof.

[0077] As illustrated, the device 500 comprises a processor 510, a memory 520 coupled to the processor 510, appropriate transmitters (TX) and receivers (RX) 540 coupled to the processor 510, and a communication interface coupled to the TX / RX 540. The memory 520 stores at least a portion of the program 530. The TX / RX 540 is used for bidirectional communication. The TX / RX 540 has at least one antenna to facilitate communication, although the access node referred to herein may actually have multiple antennas. The communication interface can represent any interface necessary for communication with other network elements, such as an X2 interface for bidirectional communication between eNBs, an S1 interface for communication between a mobility management entity (MME) / serving gateway (S-GW) and an eNB, an Un interface for communication between an eNB and a relay node (RN), or a Uu interface for communication between an eNB and a terminal device.

[0078] It is assumed that program 530 includes program instructions that, when executed by the associated processor 510 as described herein with reference to Figures 2 to 4, enable the device 500 to operate according to embodiments of the present disclosure. Embodiments herein can be implemented by computer software executable by the processor 510 of the device 500, by hardware, or by a combination of software and hardware. The processor 510 can be configured to implement various embodiments of the present disclosure. Furthermore, a combination of the processor 510 and memory 520 can form a processing means 550 suitable for implementing various embodiments of the present disclosure.

[0079] Memory 520 may be of any type suitable for a local technology network and can be implemented using any suitable data storage technology, such as non-temporary computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. Although only one memory 520 is shown in device 500, several physically different memory modules may be present in device 500. Processor 510 may be of any type suitable for a local technology network and can include, as non-limiting examples, one or more of general-purpose computers, dedicated computers, microprocessors, digital signal processors (DSPs), and processors based on multicore processor architectures. Device 500 may have multiple processors, for example, application-specific integrated circuit chips that are time-dependent to a clock that synchronizes the main processor.

[0080] Overall, various embodiments of the Disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some embodiments may be implemented in hardware, while others may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Various embodiments of the Disclosure are illustrated and described using block diagrams, flowcharts, or any other pictorial representation, but it should be understood that the blocks, devices, systems, techniques, or methods described herein can be implemented, in non-limiting examples, in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or any combination thereof.

[0081] This disclosure also provides at least one computer program product tangibly stored on a non-temporary computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions contained in a program module, which are executed within a device on a target real or virtual processor to perform the processes or methods described above with reference to any one of Figures 2 to 4. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a specific task or implement a specific abstract data type. In various embodiments, the functions of program modules can be combined or separated among program modules as needed. The machine-executable instructions of a program module can be executed within a local or distributed device. In a distributed device, the program module may reside in both local and remote storage media.

[0082] Program code for performing the methods of this disclosure can be written in any combination of one or more programming languages. These program codes are provided to a processor or controller of a general-purpose computer, a dedicated computer, or other programmable data processing device, and when executed by the processor or controller, the program code implements the functions / operations specified in the flowcharts and / or block diagrams. The program code can be executed entirely on a machine, partially on a machine, as an independent software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0083] The program code described above may be implemented on a machine-readable medium, which may be any tangible medium that can contain or store programs used by or associated with an instruction execution system, device, or apparatus. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or any suitable combination of the aforementioned mediums. More specific examples of machine-readable storage media may include electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above.

[0084] While the operations have been described in a specific order, it should not be understood that, in order to obtain the desired results, these operations must be performed in the specific order shown, or in a sequential order, or that all of the described operations must be performed. In some cases, multitasking or parallel processing may be advantageous. Similarly, while some specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of this disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Some features described in the context of individual embodiments may be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may be implemented separately or in any suitable subcombination in multiple embodiments.

[0085] While this disclosure has been described in language specific to structural features and / or methodological behavior, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or behaviors described above. Rather, the specific features and behaviors described above are disclosed as exemplary forms of implementing the claims.

Claims

1. The terminal device, The process involves receiving configuration information via radio resource control (RRC) signaling, including instructions indicating a set of preambles for repeating message 3 transmissions. A process for performing random access using a preamble from a set of preambles for repeatedly sending the aforementioned message 3.

2. The process that performs the random access sends a preamble from the set of preambles for repeating the transmission of message 3. The method according to claim 1.

3. In the process that performs the aforementioned random access, a random access response (RAR) is received that indicates the first number of repetitions of sending the message 3. The method according to claim 2.

4. The network device The process involves transmitting configuration information via radio resource control (RRC) signaling, including instructions indicating a set of preambles for repeating message 3 transmissions. A process for performing random access using a preamble from a set of preambles for repeatedly sending the aforementioned message 3.

5. The process that performs the random access mentioned above receives a preamble from the set of preambles for repeating the transmission of message 3. The method according to claim 4.

6. In the process that performs the random access, a random access response (RAR) indicating the first number of repetitions of sending message 3 is sent. The method according to claim 5.

7. Means for receiving configuration information via radio resource control (RRC) signaling, including instructions indicating a set of preambles for repeating message 3 transmissions, A terminal device having means for performing random access using a preamble from a set of preambles for repeated transmission of the message 3.

8. The means for performing the random access transmits a preamble from a set of preambles for repeating the transmission of message 3. The terminal device according to claim 7.

9. The means for performing the random access receives a random access response (RAR) indicating a first number of repetitions of sending the message 3. The terminal device according to claim 8.

10. Means for transmitting configuration information including instructions indicating a set of preambles for repeating message 3 transmission via radio resource control (RRC) signaling, A network device having means for performing random access using a preamble from a set of preambles for repeated transmission of the message 3.

11. The means for performing the random access receives a preamble from a set of preambles for repeating the transmission of message 3. The network device according to claim 10.

12. The means for performing the random access transmits a random access response (RAR) indicating a first number of repetitions of the message 3 transmission. The network device according to claim 11.

Images