EP3711428A1 - Ordre de canal de commande de liaison descendante physique pour communication de type machine - Google Patents

Ordre de canal de commande de liaison descendante physique pour communication de type machine

Info

Publication number
EP3711428A1
EP3711428A1 EP17932215.1A EP17932215A EP3711428A1 EP 3711428 A1 EP3711428 A1 EP 3711428A1 EP 17932215 A EP17932215 A EP 17932215A EP 3711428 A1 EP3711428 A1 EP 3711428A1
Authority
EP
European Patent Office
Prior art keywords
random access
user equipment
repetition value
network entity
downlink control
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP17932215.1A
Other languages
German (de)
English (en)
Other versions
EP3711428A4 (fr
Inventor
Chunhai Yao
Rapeepat Ratasuk
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Technologies Oy
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Publication of EP3711428A1 publication Critical patent/EP3711428A1/fr
Publication of EP3711428A4 publication Critical patent/EP3711428A4/fr
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system

Definitions

  • Various communication systems may benefit from improved random access related communications.
  • certain embodiments may benefit from improved physical downlink control channel order in enhanced machine type communications.
  • random access procedures are generally used to connect a user equipment to a network via a physical random access channel (PRACH) or a narrowband physical random access channel (NPRACH) . While the random access procedures are generally triggered or initiated by auser equipment, in some cases the random access procedures may be triggered or initiated by the network. The initiation of random access procedures at the network occurs when the user equipment is not synchronized with the network, and when there is a downlink data transmission that the network needs to transmit to the user equipment.
  • 3GPP Third Generation Partnership Project
  • PRACH physical random access channel
  • NPRACH narrowband physical random access channel
  • the PDCCH order is a procedure used to by the network initiate random access procedures at the user equipment, thereby synchronizing the uplink and/or downlink transmissions of the user equipment with a network entity located within the network.
  • the initiated random access procedures may be contention-less random access procedures.
  • the user equipment receiving the PDCCH order may send a random access preamble to the network entity using the preamble index included in the PDCCH order.
  • the network entity then responds to the random access preamble with a random access response message that include a new timing advance value, which is used by the user equipment to synchronize uplink and/or downlink transmissions.
  • Machine type communication devices are capable of receiving the PDCCH order from the network entity by MTC Physical Downlink Control Channel (MPDCCH) or the narrowband Physical Downlink Control Channel (NPDCCH) . Specifically, the machine type communication devices may use the PDCCH order to synchronize their uplink transmissions with the network.
  • MPDCCH Physical Downlink Control Channel
  • NPDCCH narrowband Physical Downlink Control Channel
  • an apparatus may include at least one memory including computer program code, and at least one processor.
  • the at least one memory and the computer program code may be configured, with the at least one processor, to cause the apparatus at least to receive a command to start random access from a network entity.
  • the at least one memory and the computer program code may also be configured, with the at least one processor, to cause the apparatus at least to determining, after receiving the command, timing for transmitting a random access preamble based on a repetition value of a physical downlink control channel. The repetition value may be used by the user equipment while another repetition value is used for the command to start the random access.
  • the at least one memory and the computer program code may be configured, with the at least one processor, to cause the apparatus at least to transmit the random access preamble from the user equipment to the network entity on a physical random access channel using the determined timing.
  • a method may include receiving at a user equipment a command to start random access from a network entity.
  • the method may also include determining at the user equipment, after receiving the command, timing for transmitting a random access preamble based on a repetition value of a physical downlink control channel.
  • the repetition value may be used by the user equipment while another repetition value is used for the command to start the random access.
  • the method may include transmitting the random access preamble from the user equipment to the network entity on a physical random access channel using the determined timing.
  • An apparatus may include means for receiving at a user equipment a command to start random access from a network entity.
  • the apparatus may also include means for determining at the user equipment, after receiving the command, timing for transmitting a random access preamble based on a repetition value of a physical downlink control channel. The repetition value may be used by the user equipment while another repetition value is used for the command to start the random access.
  • the apparatus may include means for transmitting the random access preamble from the user equipment to the network entity on a physical random access channel using the determined timing.
  • a non-transitory computer-readable medium encoding instructions that, when executed in hardware, perform a process.
  • the process may include receiving at a user equipment a command to start random access from a network entity.
  • the process may also include determining at the user equipment, after receiving the command, timing for transmitting a random access preamble based on a repetition value of a physical downlink control channel.
  • the repetition value may be used by the user equipment while another repetition value is used for the cormnand to start the random access.
  • the process may include transmitting the random access preamble from the user equipment to the network entity on a physical random access channel using the determined timing.
  • a computer program product may encode instructions for performing a process.
  • the process may include receiving at a user equipment a command to start random access from a network entity.
  • the process may also include determining at the user equipment, after receiving the command, timing for transmitting a random access preamble based on a repetition value of a physical downlink control channel.
  • the repetition value may be used by the user equipment while another repetition value is used for the command to start the random access.
  • the process may include transmitting the random access preamble from the user equipment to the network entity on a physical random access channel using the determined timing.
  • an apparatus may include at least one memory including computer program code, and at least one processor.
  • the at least one memory and the computer program code may be configured, with the at least one processor, to cause the apparatus at least to transmit a command to start random access to a user equipment using another repetition number other than a repetition value.
  • the at least one memory and the computer program code may also be configured, with the at least one processor, to cause the apparatus at least to receive a random access preamble from the user equipment via a physical random access channel according to a timing for transmitting the random access preamble that is based on the repetition value.
  • a method may include transmitting from a network entity a command to start random access to a user equipment using another repetition number other than a repetition value.
  • the method may also include receiving a random access preamble at the network entity from the user equipment via a physical random access channel according to a timing for transmitting the random access preamble that is based on the repetition value.
  • An apparatus may include means for transmitting from a network entity a command to start random access to a user equipment using another repetition number other than a repetition value.
  • the apparatus may also include means for receiving a random access preamble at the network entity from the user equipment via a physical random access channel according to a timing for transmitting the random access preamble that is based on the repetition value.
  • a non-transitory computer-readable medium encoding instructions that, when executed in hardware, perform a process.
  • the process may include transmitting from a network entity a command to start random access to a user equipment using another repetition number other than a repetition value.
  • the process may also include receiving a random access preamble at the network entity from the user equipment via a physical random access channel according to a timing for transmitting the random access preamble that is based on the repetition value.
  • a computer program product may encode instructions for performing a process.
  • the process may include transmitting from a network entity a command to start random access to a user equipment using another repetition number other than a repetition value.
  • the process may also include receiving a random access preamble at the network entity from the user equipment via a physical random access channel according to a timing for transmitting the random access preamble that is based on the repetition value.
  • Figure 1 illustrates an example of a timing relationship between PDCCH order and PRACH according to certain embodiments.
  • Figure 2 illustrates an example of a flow diagram according to certain embodiments.
  • Figure 3 illustrates an example of a flow diagram according to certain embodiments.
  • Figure 4 illustrates an example of a system according to certain embodiments.
  • Certain embodiments may relate to a relationship between a command to start random access, such as the MPDCCH/NPDCCH/PDCCH order, and a timing for transmitting a random access preamble, such as the PRACH/NPRACH transmission.
  • MPDCCH, NPDCCH, and/or PDCCH may generally be referred to a PDCCH below
  • NPRACH and/or PRACH may generally be referred to as PRACH below.
  • certain embodiments refer to MPDCCH, NPDCCH, PDCCH, NPRACH, and PRACH
  • certain other embodiments may use any other type of channel provided for by 3GPP or any other standard setting body.
  • 3GPP LTE and LTE-A other embodiments may apply to 3GPP 5 th generation (5G) or New Radio (NR) technology.
  • 5G 3GPP 5 th generation
  • NR New Radio
  • Section 6.1.1 of 3GPP TS 36.213 describes that when a random access procedure is initiated by a PDCCH order in subframe n and/or the reception of the PDCCH order ends in subframe n, the UE transmits a random access preamble in the first subframe n+k 2 , k 2 ⁇ 6, where a PRACH resource is available.
  • 3GPP TS 36.213 describes that the PRACH resource is available 6 or more subframes after subframe n.
  • the UE described in 3GPP TS 36.213 is a non-bandwidth limited (BL) or non-coverage enhanced (CE) user equipment (UE) .
  • a BL/CE UE may be a machine type communication device.
  • Section 16.3.2 of 3GPP TS 36.213 describes a similar procedure for a Narrowband Internet of Things (NB-IoT) .
  • 3GPP TS 36.213 is hereby incorporated by reference in its entirety.
  • the PDCCH may be an enhanced machine type communication (eMTC) PDCCH (MPDCCH) or NPDCCH.
  • MPDCCH may simply be referred to as PDCCH hereinafter.
  • the timing of the MPDCCH/NPDCCH reception determines when the PRACH/NPRACH transmission may occur.
  • the PDCCH order ends in subframe n, which means that the timing of the PRACH transmission may be determined based on when the PDCCH order ends.
  • a repetition number of MPDCCH is not known to the UE, but only known by the network, the UE does not know when the PDCCH order ends, and when PRACH transmissions begin.
  • the PDCCH order may be transmitted to the UE in a variety of different formats.
  • one such format may be a downlink control information (DCI) format 6-lA.
  • Another example may be a DCI format 6-1B or N1, where N1 may be the NB-IoT DCI format.
  • the DCI corresponding to a PDCCH order may be carried by MPDCCH.
  • format 6-1A may be used for a random access procedure initiated by a PDCCH order only when format 6-1A cyclic redundancy check (CRC) is scrambled with a cell radio network temporary identity (C-RNTI) .
  • CRC cyclic redundancy check
  • C-RNTI cell radio network temporary identity
  • the remaining fields in the 6-1A format may include a resource block assignment determined by the following equation: bits, with representing the downlink bandwidth configuration, expressed in a number of resource blocks.
  • the 6-1A format may include 6 bits of a preamble index, 4 bits of a PRACH mask index, 2 bits for a starting coverage enhancement level. All of the remaining bits in the DCI format 6-1A used for compact scheduling assignment of a physical downlink shared channel may be set to zero.
  • Section 5.7.1 of 3GPP TS 36.211 further describes that for BL/CE UEs, such as MTC devices, only a subset of the subframes are allowed for preamble transmissions, while also being allowed to serve as starting subframes for repetitions. may be a subframe in which the UE may start to transmit data via the PRACH.
  • 3GPP TS 36.211 is hereby incorporated by reference in its entirety.
  • the starting subframe for a PRACH transmission may be determined by the end of the repetitions of the PDCCH order and the starting subframe periodicity of the PRACH.
  • neither DCI format 6-1A nor 6-1B include a DCI subframe repetition number field. This means that the UE may not be informed of the ending subframe of the PDCCH order, and therefore may not know the starting subframe of the PRACH transmissions. This lack of awareness by the UE may lead to erroneous and conflicting operations being conducted by both the UE and the network entity transmitting the PDCCH order.
  • inventions described below may be used in any communication system in which the DCI subframe repetition number or the PDCCH order repetition number is unknown.
  • the embodiments help to ensure proper operation for eMTC PDCCH order, since it is not clear when the UE should send the PRACH in response to the reception of the order. This may help to achieve a common understanding between the UE and the network entity of the timing of the PRACH transmissions.
  • Figure 1 illustrates an example of a timing relationship between PDCCH order and PRACH transmission according to certain embodiments.
  • Figure 1 illustrates an example of a PDCCH order reception and corresponding PRACH transmissions.
  • a network entity such as an enhanced NodeB (eNB)
  • eNB enhanced NodeB
  • the UE may assume that the PDCCH order is capable of 256 repetitions. If the decoding of the PRACH order by the UE does not reveal that the PDCCH order is capable of 256 repetitions, the UE may not transmit on the PRACH.
  • the eNB may expect the UE to transmit the PRACH between subframes number 128 to 255 of the second search space.
  • the UE may be capable of decoding the MPDCCH correctly in the first MPDCCH candidate with 64 repetitions.
  • the UE may transmit the PRACH between subframes number 128 to 255 of the first MPDCCH search space.
  • the UE may transmit PRACH from subframes number 0 to 127 of the second MPDCCH search space, and/or from subframes number 128 to 255 of the second MPDCCH search space.
  • the user equipment may have two different options for transmitting on the PRACH that the eNB may not expect.
  • the eNB and UE could have a different understanding on the starting subframe of the PRACH transmission. This may cause the network entity, for example, to try to decode the PRACH while the PDCCH order is still transmitting. This is because subframe n , which is the subframe that marks the ending of the PDCCH order reception, may not be known by the UE. The implementation of the network entity, such as the eNB, may therefore become complicated, and possible errors may occur depending on UE implementation.
  • certain embodiments may improve the PDCCH order.
  • certain embodiments may configure a repetition value to the UE in order determine the PRACH timing.
  • the repetition value for example, may be a configured maximum repetition value (Rmax) .
  • Rmax may be the maximum number of repetitions configured for a UE specific search space for the MPDCCH.
  • the UE may be informed of the Rmax via an RRC parameter mPDCCH-NumRepetition or nPDCCH-NumRepetitions, which may be configured by a network entity, such as an eNB.
  • nPDCCH-NumRepetitions may be the parameter used in NB-IoT.
  • Rmax certain embodiments may solve or help to prevent the ambiguity between the PRACH timing perceived by the eNB and the UE, such as an eMTC UE.
  • Certain embodiments allow the UE to use a repetition value, such as Rmax, regardless of the repetition used by the network entity.
  • the network entity may use a fraction of the repetition value for the PDCCH order, but then PRACH timing may be determined according to the repetition value, such as a Rmax. Therefore, the another repetition number used for the PDCCH order, which may be different than the Rmax assumed for PRACH timing.
  • PRACH timing may be determined according to the repetition value, such as a Rmax. Therefore, the another repetition number used for the PDCCH order, which may be different than the Rmax assumed for PRACH timing.
  • Certain other embodiments may improve the PDCCH order format. Specifically, certain embodiments may introduce a field to indicate the number of repetitions in the downlink control information.
  • the field may be a DCI subframe repetition number field, and may be included in DCI formats 6-1A, 6-1B, or N1. With the addition of this DCI subframe repetition number field, the ambiguity between the PRACH or NPRACH timing perceived by the eNB and the UE may be resolved.
  • Figure 2 illustrates an example of a flow diagram according to certain embodiments.
  • Figure 2 illustrates a method or process performed by a UE, such as an eMTC or NB-IoT UE or an enhanced coverage user equipment.
  • the UE may receive a command to start random access from a network entity.
  • the command to start random access may take the form of a PDCCH order.
  • the UE may decode the PDCCH in order to determine the command to start random access, as shown in step 220.
  • the UE may use the repetition value as the reference timing for random access.
  • the repetition value may define a UE specific search space for the PDCCH.
  • the repetition value may be a configured maximum repetition value.
  • the PDCCH order may be formatted according to a DCI format 6-1A, 6-1B, or N1.
  • the actual repetition value may be indicated in a downlink control information (DCI) subframe repetition number field included in a format 6-1A, 6-1B, or N1 downlink control information.
  • DCI downlink control information
  • the repetition value assumed or used by the UE may be different than the another repetition number used by the network entity to determine the repetition for the commend to start random access, such as a PDCCH order.
  • the number used by the network may be a fraction of the repetition value assumed or used by the UE.
  • the UE and the network entity may use a different or another repetition number for the command to start random access, such as a PDCCH order, than the repetition value used by the UE to determine timing for transmitting a random access preamble, such as the PRACH timing.
  • the UE may determine the repetition value.
  • the repetition value may be determined based on a received message at the UE from a network entity, such as a eNB.
  • the repetition value may be determined based on a standard set by a network operator or a standard setting body. Both the UE and the network entity may be configured with or have access to the repetition value.
  • a fraction of the repetition value may be used by the network entity.
  • the repetition value is Rmax
  • the another repetition value used by the network entity may be Rmax/8, Rmax/4, Rmax/2, or Rmax, while the UE may use Rmax.
  • the repetition value used by the network entity may be 128, 64, or 32.
  • the UE may determine a timing for transmitting a random access preamble, for example a PRACH timing, based on a repetition value of a PDCCH.
  • the repetition value is used by the user equipment while another repetition value is used for the command to start the random access.
  • the UE may use the assumed repetition value to determine the timing of the random access preamble, while a separate or different another repetition value may be used by the network for the command to start the random access.
  • the another repetition value for the command to start the random access may be a fraction of the repetition value used for the timing for transmitting the random access preamble.
  • the UE may transmit the random access preamble from the UE to the network entity on the PRACH using the determined timing, such as a PRACH timing.
  • the transmitting of the preamble from the UE to the network entity using the PRACH timing may act to synchronize uplink transmissions between the UE to the network entity.
  • the transmitting of the preamble may be part of a random access operation.
  • the transmitting of the preamble may occur on a starting subframe of the PRACH.
  • the starting subframe may be determined based on at least one of the repetition value of the PDCCH and/or a periodicity of the starting subframe.
  • the starting subframe of the physical random access channel is later than a pre-defined number of subframes after an end subframe of a user equipment specific search space of the physical downlink control channel.
  • the pre-defined number of subframes may be 6 for eMTC, while the pre-defined number of subframes may be 8 for NB-IoT.
  • the starting subframe of the PRACH for example, may be later than the subframe Rmax+6 or Rmax+8.
  • the periodicity of the starting subframe may be configured by the network entity. In other embodiments, however, the periodicity may not be configured by the network.
  • Figure 3 illustrates an example of a flow diagram according to certain embodiments.
  • Figure 3 illustrates a method or process performed by a network entity, such as an eNB or a 5 th generation or New Radio NodeB (gNB) .
  • the network entity may transmit a command to start random access to a UE using another repetition number other than a repetition value.
  • the another repetition value for the command to start the random access may be a fraction of the repetition value used for the determined timing for the random access preamble.
  • the UE may use the repetition value for transmitting the random access preamble regardless of the fact that the network entity may use a different repetition value, such as a fraction of the repetition value, for transmitting the command to start the random access.
  • the repetition number may be indicated in a downlink control information subframe repetition number field included in a downlink control information format 6-1A, 6-1B, or N1.
  • the network entity may receive a random access preamble from the UE via a physical random access channel according to a timing for transmitting the random access preamble that is based on the repetition value. In other words, the UE may assume the repetition value, regardless of the another repetition value used by the network entity to transmit the command for random access.
  • the receiving of the preamble may occur on a starting subframe of the PRACH and/or the starting subframe may be determined based on the maximum repetition value of the PDCCH or a periodicity of the starting subframe.
  • the network entity may decode the random access preamble transmitted from the UE via the PRACH with a specific number of repetitions according to a coverage enhancement level of the UE. The network entity may then transmit a random access response from the network entity to the UE based on the decoded preamble, as shown in step 340. The transmitting of the random access response from the network entity to the user equipment acts to synchronize uplink transmissions between the user equipment and the network entity.
  • Figure 4 illustrates a system according to certain embodiments. It should be understood that each block in Figures 1, 2, and 3 may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and/or circuitry.
  • a system may include several devices, such as, for example, a network entity 420 or a UE 410.
  • the system may include more than one UE 410 and more one network entity 420, although only one network entity is shown for the purposes of illustration.
  • the network entity may be a network node, an access node, a base station, a eNB, a gNB, a server, a host, or any of the other access or network node discussed herein.
  • Each of these devices may include at least one processor or control unit or module, respectively indicated as 411 and 421.
  • At least one memory may be provided in each device, and indicated as 412 and 422, respectively.
  • the memory may include computer program instructions or computer code contained therein.
  • One or more transceiver 413 and 423 may be provided, and each device may also include an antenna, respectively illustrated as 414 and 424. Although only one antenna each is shown, many antennas and multiple antenna elements may be provided to each of the devices.
  • Higher category UEs generally include multiple antenna panels. Other configurations of these devices, for example, may be provided.
  • network entity 420 and UE 410 may be additionally configured for wired communication, in addition to wireless communication, and in such a case antennas 414 and 424 may illustrate any form of communication hardware, without being limited to merely an antenna.
  • Transceivers 413 and 423 may each, independently, be a transmitter, a receiver, or both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception.
  • the network entity may have at least one separate receiver or transmitter.
  • the transmitter and/or receiver (as far as radio parts are concerned) may also be implemented as a remote radio head which is not located in the device itself, but in a mast, for example.
  • the operations and functionalities may be performed in different entities, such as nodes, hosts or servers, in a flexible manner. In other words, division of labor may vary case by case.
  • One possible use is to make a network node deliver local content.
  • One or more functionalities may also be implemented as virtual application (s) in software that can run on a server.
  • a user device or user equipment may be a mobile station (MS) such as a mobile phone or smart phone or multimedia device, a computer, such as a tablet, provided with wireless communication capabilities, personal data or digital assistant (PDA) provided with wireless communication capabilities, portable media player, digital camera, pocket video camera, navigation unit provided with wireless communication capabilities or any combinations thereof.
  • the UE may be a machine type communication (MTC) device, an eMTC UE, or an Internet of Things device, which may not require human interaction, such as a sensor, a meter, or an actuator.
  • MTC machine type communication
  • eMTC UE eMTC UE
  • an Internet of Things device which may not require human interaction, such as a sensor, a meter, or an actuator.
  • an apparatus such as user equipment 410 or network entity 420, may include means for performing or carrying out embodiments described above in relation to Figures 1-3.
  • the apparatus may include at least one memory including computer program code and at least one processor.
  • the at least one memory including computer program code can be configured to, with the at least one processor, cause the apparatus at least to perform any of the processes described herein.
  • the apparatus for example, may be user equipment 410 or network entity 420.
  • Processors 411 and 421 may be embodied by any computational or data processing device, such as a central processing unit (CPU) , digital signal processor (DSP) , application specific integrated circuit (ASIC) , programmable logic devices (PLDs) , field programmable gate arrays (FPGAs) , digitally enhanced circuits, or comparable device or a combination thereof.
  • the processors may be implemented as a single controller, or a plurality of controllers or processors.
  • the implementation may include modules or unit of at least one chip set (for example, procedures, functions, and so on) .
  • Memories 412 and 422 may independently be any suitable storage device, such as a non-transitory computer-readable medium.
  • a hard disk drive (HDD) random access memory (RAM) , flash memory, or other suitable memory may be used.
  • the memories may be combined on a single integrated circuit as the processor, or may be separate therefrom.
  • the computer program instructions may be stored in the memory and which may be processed by the processors can be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.
  • the memory or data storage entity is typically internal but may also be external or a combination thereof, such as in the case when additional memory capacity is obtained from a service provider.
  • the memory may be fixed or removable.
  • a non-transitory computer-readable medium may be encoded with computer instructions or one or more computer program (such as added or updated software routine, applet or macro) that, when executed in hardware, may perform a process such as one of the processes described herein.
  • a computer program product may encode instructions for performing any of the processes described above, or a computer program product embodied in a non-transitory computer-readable medium and encoding instructions that, when executed in hardware, perform any of the processes describes above.
  • Computer programs may be coded by a programming language, which may be a high-level programming language, such as objective-C, C, C++, C#, Java, etc., or a low-level programming language, such as a machine language, or assembler. Alternatively, certain embodiments may be performed entirely in hardware.
  • a programming language which may be a high-level programming language, such as objective-C, C, C++, C#, Java, etc.
  • a low-level programming language such as a machine language, or assembler.
  • certain embodiments may be performed entirely in hardware.
  • Figure 4 illustrates a system including a network entity 420 and UE 410
  • certain embodiments may be applicable to other configurations, and configurations involving additional elements, as illustrated and discussed herein.
  • multiple user equipment devices and multiple network entities may be present, or other nodes providing similar functionality, such as nodes that combine the functionality of a user equipment and an network entity, such as a relay node.
  • the UE 410 may likewise be provided with a variety of configurations for communication other than communication network entity 420.
  • the UE 410 may be configured for device-to-device, machine-to-machine, and/or vehicle-to-vehicle transmission.
  • the above embodiments may provide for significant improvements to the functioning of a network and/or to the functioning of the user equipment and the network entities included within the network.
  • certain embodiments may help to prevent ambiguity between the network and the UE regarding the starting subframe of the PRACH. This may help to reduce the number of erroneous PRACH transmissions, while at the same time simplifying the PDCCH order.
  • This network simplification and error reduction will help to reduce the number of resources used by the network, thereby significantly improving the functioning of the network as a whole, as well as the functioning of network entities included within the network and eMTC UEs communicating with the network.
  • certain embodiments can help to improve the uplink synchronization process between the network and the UE, which may also help to reduce the amount of downtime experienced by the UE.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon la présente invention, divers systèmes de communication peuvent bénéficier de communications associées à un accès aléatoire amélioré. Par exemple, certains modes de réalisation peuvent bénéficier d'un ordre de canal de commande de liaison descendante physique amélioré dans des communications de type machine augmentées. Un procédé, selon certains modes de réalisation, peut consister à recevoir, au niveau d'un équipement utilisateur, une instruction de démarrage d'un accès aléatoire en provenance d'une entité de réseau. Le procédé peut également consister à déterminer, au niveau de l'équipement utilisateur, après réception de l'instruction, un temps pour transmettre un préambule d'accès aléatoire sur la base d'une valeur de répétition d'un canal de commande de liaison descendante physique (PDCCH). La valeur de répétition peut être utilisée par l'équipement utilisateur pendant qu'une autre valeur de répétition est utilisée pour l'instruction de démarrage de l'accès aléatoire. De plus, le procédé peut consister à transmettre le préambule d'accès aléatoire, de l'équipement utilisateur à l'entité de réseau, sur un canal d'accès aléatoire physique (PRACH) à l'aide du temps déterminé.
EP17932215.1A 2017-11-17 2017-11-17 Ordre de canal de commande de liaison descendante physique pour communication de type machine Pending EP3711428A4 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/111735 WO2019095320A1 (fr) 2017-11-17 2017-11-17 Ordre de canal de commande de liaison descendante physique pour communication de type machine

Publications (2)

Publication Number Publication Date
EP3711428A1 true EP3711428A1 (fr) 2020-09-23
EP3711428A4 EP3711428A4 (fr) 2021-07-14

Family

ID=66538451

Family Applications (1)

Application Number Title Priority Date Filing Date
EP17932215.1A Pending EP3711428A4 (fr) 2017-11-17 2017-11-17 Ordre de canal de commande de liaison descendante physique pour communication de type machine

Country Status (3)

Country Link
EP (1) EP3711428A4 (fr)
CN (1) CN111357376B (fr)
WO (1) WO2019095320A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022236705A1 (fr) * 2021-05-11 2022-11-17 Nokia Shanghai Bell Co., Ltd. Dispositif d'interrogation pour indication d'intérêt de service de diffusion/multidiffusion

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010093111A1 (fr) * 2009-02-11 2010-08-19 Lg Electronics Inc. Procédure d'accès aléatoire
CN101925107B (zh) * 2009-06-15 2014-12-10 华为技术有限公司 实现资源调度的方法、设备和系统
US9572171B2 (en) * 2013-10-31 2017-02-14 Intel IP Corporation Systems, methods, and devices for efficient device-to-device channel contention
WO2015102281A1 (fr) * 2013-12-30 2015-07-09 엘지전자 주식회사 Procédé et dispositif mtc d'exécution d'une procédure d'accès aléatoire conformément à une pluralité d'ensembles de paramètres
WO2016045715A1 (fr) * 2014-09-24 2016-03-31 Nokia Solutions And Networks Oy Transmission répétée d'une affectation d'ordonnancement à une réponse d'accès aléatoire
JP2018032886A (ja) * 2015-01-08 2018-03-01 シャープ株式会社 端末装置、基地局装置、無線通信方法及び集積回路
EP3852479A1 (fr) * 2015-01-30 2021-07-21 Nokia Solutions and Networks Oy Canal d'accès aléatoire physique et détection de réponse d'accès aléatoire pour équipement utilisateur
WO2016164011A1 (fr) * 2015-04-08 2016-10-13 Nokia Solutions And Networks Oy Transmission de message de réponse à accès aléatoire
CN106686691B (zh) * 2015-11-06 2019-11-08 电信科学技术研究院 一种随机接入响应rar传输方法及相关设备

Also Published As

Publication number Publication date
EP3711428A4 (fr) 2021-07-14
CN111357376B (zh) 2023-11-28
CN111357376A (zh) 2020-06-30
WO2019095320A1 (fr) 2019-05-23

Similar Documents

Publication Publication Date Title
US11818080B2 (en) Random access with bandwidth part switch
US10499368B2 (en) Control channel transmission for paging message coverage enhancement
US11178647B2 (en) Signaling support for uplink reference signal transmission
TWI586133B (zh) 用於鏈路預算受限制的器件之改良上行鏈路控制資訊的傳輸
EP3735799B1 (fr) Nouvelle conception de canal physique de commande de liaison descendante
EP3545720B1 (fr) Procédé et dispositif de transmission d'informations de commande de liaison descendante
CN110855401A (zh) 一种harq反馈方法和装置
US11716635B2 (en) Creating protocol data unit for early data transmission
JP2023529053A (ja) 通信のための方法、装置及びコンピュータ記憶媒体
WO2019095320A1 (fr) Ordre de canal de commande de liaison descendante physique pour communication de type machine
CN114424643A (zh) 一种上行传输方法及装置
EP3648383A1 (fr) Manipulation de harq-ack avec transmission multi-trp pucch en multiples dans nr
US20230353298A1 (en) Method and apparatus for mapping pusch repetitions
US20240080817A1 (en) Wireless communication method, terminal device, and network device
WO2022000431A1 (fr) Procédé et appareil de sauts de fréquence multi-faisceaux
WO2020164074A1 (fr) Transmission msg3 dans une bande sans licence
CN117837240A (zh) 用于从vrb到prb的映射的方法及设备
CN117501636A (zh) 用于物理上行链路控制信道(pucch)传输的方法及设备
KR20160141086A (ko) 사물 통신 단말의 랜덤 액세스 응답 수신 장치
KR20160141160A (ko) 사물 통신 단말의 랜덤 액세스 응답 수신 장치

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20200617

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20210610

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 74/08 20090101AFI20210604BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20230905