Contention resolution during random access
By using the downlink control channel scrambled by identifiers in the communication network for competition resolution, the transmission conflict problem of random access channels is solved, and the access success rate and communication efficiency are improved.
Patent Information
- Application Number
- CN201980091877.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-02-22
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2039-02-22
AI Technical Summary
In a communication network, sharing of random access channels results in transmission conflicts between terminal devices, which may lead to random access failure and transmission delay.
By sending a random access request and response containing preamble and identification information between the terminal device and the network device, a downlink control channel scrambled by identifiers is used for competition resolution, reducing the number of RNTIs and reducing overhead.
It effectively solves the competition problem in the random access process, improves the access success rate and reduces the response overhead, reduces the number of RNTIs, and improves communication efficiency.
Smart Images

Figure CN113455089B_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present disclosure generally relate to communication technology, and more particularly, to a method, apparatus, and computer-readable medium for contention resolution in a random access procedure. Background Art
[0002] In recent communication networks, terminal devices share the Random Access Channel (RACH) to request access to the network for call establishment and burst data transmission. Since the RACH is shared, two or more terminal devices may transmit at the same time and their transmissions collide. This is called contention. If the terminal device does not get a response, it performs a random access request again. This transmission conflict may cause undesirable random access failures and unexpected transmission delays. Summary of the invention
[0003] Generally speaking, embodiments of the present disclosure relate to a contention resolution method in a random access procedure and a corresponding communication device.
[0004] In a first aspect, an embodiment of the present disclosure provides a terminal device. The terminal device includes: at least one processor; and a memory coupled to the at least one processor, the memory having instructions stored therein, which, when executed by the at least one processor, causes the terminal device to: send a random access request to a network device at the terminal device. The random access request includes at least one preamble for a random access procedure and identification information of the terminal device. The terminal device is also caused to: receive a random access response scheduled by a downlink control channel scrambled with an identifier for the random access request from the network device. One or more terminal devices send a preamble for a random access procedure to the network device on a random access channel. The identifier is used to scramble a downlink control channel associated with the terminal device. The terminal device is also caused to: determine that the random access procedure of the terminal device is successful in response to determining that the random access response includes the identification information of the terminal device.
[0005] In a second aspect, an embodiment of the present disclosure provides a network device. The network device includes: at least one processor; and a memory coupled to the at least one processor, the memory having instructions stored therein, which, when executed by the at least one processor, causes the network device to: receive a random access request from one or more terminal devices at the network device. The random access request includes at least a preamble for a random access procedure of the terminal device and identification information of the terminal device. The preamble is sent on a random access channel. The network device is also caused to: send a random access response to the terminal device on a downlink control channel scrambled with an identifier. The random access response includes identification information of at least one terminal device to indicate that the random access procedure of at least one terminal device among the one or more terminal devices is successful. The identifier is used to scramble a downlink control channel associated with the terminal device.
[0006] In a third aspect, an embodiment of the present disclosure provides a method. The method includes: at a terminal device, sending a random access request to a network device. The random access request includes at least one preamble code for a random access process and identification information of the terminal device. The method also includes receiving a random access response to the random access request scheduled by a downlink control channel from the network device, and the downlink control channel is scrambled with an identifier. The random access response includes identification information of at least one terminal device. The terminal device sends a preamble code for a random access process to the network device on a random access channel. The identifier is used to scramble a downlink control channel associated with the terminal device. The method also includes determining that the random access process of the terminal device is successful in response to determining that the random access response includes the identification information of the terminal device.
[0007] In a fourth aspect, an embodiment of the present disclosure provides a method. The method includes: receiving a random access request from one or more terminal devices at a network device. The random access request includes at least a preamble for a random access procedure of the terminal device and identification information of the terminal device. The preamble is sent on a random access channel. The method also includes sending a random access response to the terminal device on a downlink control channel scrambled with an identifier. The random access response includes identification information of at least one terminal device to indicate that the random access procedure of at least one terminal device is successful. The identifier is used to scramble a downlink control channel associated with the terminal device.
[0008] In a fifth aspect, an embodiment of the present disclosure provides a device. The device includes a component for sending a random access request from a terminal device to a network device. The random access request includes at least one preamble code for a random access process and identification information of the terminal device. The device also includes a component for receiving a random access response scheduled by a downlink control channel from the network device for the random access request, and the downlink control channel is scrambled with an identifier. The random access response includes identification information of one or more terminal devices. The terminal device sends a preamble code for a random access process to the network device on a random access channel. The identifier is used to scramble a downlink control channel associated with the terminal device. The device also includes a component for determining that the random access process of the terminal device is successful in response to determining that the random access response includes the identification information of the terminal device.
[0009] In a sixth aspect, an embodiment of the present disclosure provides an apparatus. The apparatus includes a component for receiving a random access request from one or more terminal devices at a network device. The random access request includes at least a preamble for a random access procedure of the terminal device and identification information of the terminal device. The preamble is sent on a random access channel. The apparatus also includes a component for sending a random access response to one or more terminal devices on a downlink control channel scrambled with an identifier. The random access response includes identification information of at least one terminal device to indicate that the random access procedure of at least one terminal device is successful. The identifier is used to scramble a downlink control channel associated with the terminal device.
[0010] In a seventh aspect, an embodiment of the present disclosure provides a computer-readable medium, wherein the computer-readable medium stores instructions, and when the instructions are executed by at least one processing unit of a machine, the machine implements the method according to the third and fourth aspects.
[0011] Other features and advantages of embodiments of the present disclosure will also be apparent from the following description of specific embodiments when read in conjunction with the accompanying drawings, which illustrate by way of example the principles of embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] Embodiments of the present disclosure are presented by way of example and their advantages are explained in more detail below with reference to the accompanying drawings, in which
[0013] Figure 1 A schematic diagram of the conventional four-step RACH process is shown;
[0014] Figure 2 A schematic diagram of the process of the conventional two-step RACH method is shown;
[0015] Figure 3 A schematic diagram of a communication system according to an embodiment of the present disclosure is shown;
[0016] Figure 4 A schematic diagram showing the interaction between devices according to an embodiment of the present disclosure;
[0017] Figure 5 A flowchart of a method implemented at a communication device according to an embodiment of the present disclosure is shown;
[0018] Figure 6 A flowchart of a method implemented at a communication device according to an embodiment of the present disclosure is shown;
[0019] Figure 7 A schematic diagram showing a device according to an embodiment of the present disclosure; and
[0020] Figure 8 A block diagram of an example computer-readable medium is shown according to some embodiments of the present disclosure.
[0021] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION
[0022] The subject matter described herein will now be discussed with reference to several example embodiments. It should be understood that these embodiments are discussed only for the purpose of enabling those skilled in the art to better understand and thus implement the subject matter described herein, without providing any limitation on the scope of the subject matter.
[0023] The terms used herein are only for the purpose of describing specific embodiments and are not intended to limit the exemplary embodiments. As used herein, unless the context clearly indicates otherwise, the singular forms of "a", "an" and "the" are also intended to include plural forms. It should be further understood that when used herein, the terms "include", "comprise", "include", "include" and / or "include" specify the presence of the features, wholes, steps, operations, elements and / or components, but do not exclude the presence or increase of one or more other features, wholes, steps, operations, elements, components and / or groups thereof.
[0024] It should also be noted that in some alternative implementations, the functions / actions mentioned may not occur in the order indicated in the figures. For example, depending on the functions / actions involved, two functions or actions shown in succession may actually be performed simultaneously, or may sometimes be performed in the reverse order.
[0025] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed Packet Access (HSPA), etc. In addition, the communication between the terminal device and the network equipment in the communication network can be performed according to any suitable generation of communication protocols, including but not limited to first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocols and / or any other protocols currently known or to be developed in the future.
[0026] The embodiments of the present disclosure can be applied to various communication systems. Considering the rapid development of communication, of course, there will be future types of communication technologies and systems that can embody the present disclosure. The scope of the present disclosure should not be limited to only the above-mentioned systems. For the purpose of illustration, the embodiments of the present disclosure will be described with reference to the 5G communication system.
[0027] The term "network device" as used herein includes, but is not limited to, a base station (BS), a gateway, a registration management entity, and other suitable equipment in a communication system. The term "base station" or "BS" means a Node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR NB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low power node (e.g., a femto, a pico, etc.).
[0028] The term "terminal device" as used herein includes, but is not limited to, "user equipment (UE)" and other suitable terminal devices capable of communicating with network devices. For example, "terminal device" may refer to a terminal, a mobile terminal (MT), a subscriber station (SS), a portable subscriber station, a mobile station (MS), or an access terminal (AT).
[0029] As used herein, the term "circuitry" may refer to one or more or all of the following:
[0030] (a) pure hardware circuit implementation (such as implementation in analog and / or digital circuitry only), and
[0031] (b) a combination of hardware circuitry and software such as (where applicable):
[0032] (i) a combination of analog and / or digital hardware circuitry and software / firmware, and
[0033] (ii) any portion of a hardware processor (including a digital signal processor) with software, software and memory that work together to cause a device such as a mobile phone or server to perform various functions, and
[0034] (c) Hardware circuits and / or processors, such as a microprocessor or portion of a microprocessor, that require software (e.g., firmware) to operate but that may be absent when the software is not required for operation.
[0035] This definition of "circuitry" applies to all uses of this term in this application, including in any claims. As another example, as used in this application, the term "circuitry" also covers only an implementation of a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term "circuitry" also covers (for example and where applicable to a particular claim element) a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.
[0036] As mentioned above, several mechanisms have been proposed for RACH. For example, a four-step RACH procedure has been proposed. Figure 1 As shown, for a four-step RACH process, a RACH transmission opportunity is defined as a time-frequency resource for transmitting a PRACH message 1 using a configured PRACH preamble format. A user equipment (UE) 110 may transmit 1010 a RACH preamble on a PRACH resource mapped to a RA-RNTI, and a network device may decode the preamble and obtain the RA-RNTI based on the PRACH resource on which the preamble was received. The gNB 120 may send 1020 a message 2, which may indicate a transmission resource for a message 3. Specifically, the gNB 120 may send a RA response scheduled by a PDCCH addressed by a RA-RNTI calculated from a PRACH resource (e.g., time and / or frequency allocation). The UE 110 may decode the RA response and obtain a transmission resource for message 3. The UE 110 may send 1030 a radio resource control (RRC) connection request as message 3 (message 2) with the T-CRNTI obtained from the RA response. gNB 120 may respond 1040 with message 3 scrambled by the T-CRNTI obtained from the RA response (message 2). gNB 120 responds with the contention resolution ID (containing the UL CCCH SDU in message 3) in message 4 scrambled by the T-CRNTI obtained from the RA response (message 2), and the T-CRNTI is considered as C-RNTI by the UE after receiving message 4.
[0037] In recent studies, a two-step RACH method has also been proposed, such as Figure 2As shown. UE 210 sends 2010 message A to gNB 220, and gNB 220 sends 2020 message B to UE 210. Compared to the traditional four-step RACH with preamble, RAR, message 3, and contention resolution message, two-step RACH combines the transmission of the preamble and message 3 payload into message A, and combines the RAR and contention resolution message into message B. For two-step RACH, message A is a signal to detect user equipment, while the second message is used to resolve contention for CBRA that may have payload. Message A will contain at least the same information as in message 3 for the four-step RACH transmission.
[0038] As a baseline, all triggering factors for four-step RACH also apply to two-step RACH; however, further analysis is needed on the system scheduling request (SI) request and BFR, as well as how to obtain time advance and grant for message A.
[0039] Contention resolution in two-step RACH is performed by including the user equipment identifier in the first message (i.e., Message A) and echoing it in the second message (i.e., Message B). Fallback from two-step RACH to four-step RACH is supported. Fallback after transmission of Message A is only possible if the user equipment can be detected without decoding the payload and is therefore dependent on physical layer support. If two-step RACH is used for initial access, the parameters of the two-step RACH procedure will be broadcast, including the resources for Message A. The network can configure different PRACH resources or different preambles for four-step RACH and two-step RACH.
[0040] For the design of contention resolution and RNTI for two-step RACH, studies have been conducted to reuse the definition of two-step four-level RACH.
[0041] The RA-RNTI associated with the PRACH transmitting the random access preamble is uniquely calculated as:
[0042] RA-RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_operator_id (1)
[0043] Among them, s_id is the index of the first orthogonal frequency division multiplexing symbol (OFDM) of the specified PRACH (0≤s_id<14), t_id is the index of the first time slot of the specified PRACH in the system frame (0≤t_id<80), f_id is the index of the specified PRACH in the frequency domain (0≤f_id<8), and ul_carrier_id is the ul carrier used for message 1 transmission (0 represents NUL carrier and 1 represents SUL carrier). In other words, there is a one-to-one relationship between RA-RNTI and the PRACH opportunity used to send the random access preamble.
[0044] It has been discussed that the RAR window (currently up to 10ms) needs to be extended to cope with potential LBT failures, which means that the RA-RNTI range also needs to be extended. Similarly, the window for receiving message B is also likely to be longer than the current RAR window. The current RA-RNTI space has exceeded the 19k value, and further extending the RA-RNTI to control overhead is not desirable.
[0045] Contention resolution for four-step RACH will be addressed to either the temporary C-RNTI or the C-RNTI, depending on whether the UE has been assigned a C-RNTI and includes the C-RNTI MAC CE in message 3. Neither can be used for two-step RACH. When the UE has not been assigned a C-RNTI, the C-RNTI is not applicable for two-step RACH initiated from idle mode. The temporary C-RNTI is allocated in message 2 of the four-step RACH and is therefore not applicable for two-step RACH.
[0046] According to an embodiment of the present disclosure, a terminal device sends a random access request, and a network device sends a response to the random access request, the response including identification information of the terminal device that succeeded in RACH. According to an embodiment of the present disclosure, a terminal device sends a random access request in a random access channel, and a network device sends a response to the random access request on a downlink control channel addressed to a common identifier. According to an embodiment of the present disclosure, there is a one-to-many mapping between a contention resolution radio network temporary identifier (CR-RNTI) and a physical RACH (PRACH). In this way, the number of RNTIs is reduced and the overhead is reduced.
[0047] Figure 3 Schematic diagram of a communication system 300 in which embodiments of the present disclosure may be implemented is shown. The communication system 300 as part of a communication network includes terminal devices 310-1, 310-2, ..., 310-N (collectively referred to as "terminal devices 310", where N is an integer). The communication system 300 includes one or more network devices, such as network device 320. It should be understood that the communication system 300 may also include other elements omitted for clarity. It should be understood that Figure 3 The number of terminal devices and network devices shown is given for illustrative purposes and does not imply any limitation. Network device 320 can communicate with terminal device 310.
[0048] The communication in the communication system 300 can be implemented according to any appropriate communication protocol, including but not limited to cellular communication protocols such as the first generation (1G), the second generation (2G), the third generation (3G), the fourth generation (4G) and the fifth generation (5G), wireless local network communication protocols such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocol currently known or to be developed in the future. In addition, the communication can utilize any appropriate 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 duplex (FDD), time division duplex (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiple access (OFDMA) and / or any other technology currently known or to be developed in the future.
[0049] Figure 4 A schematic diagram of an interaction 400 according to an embodiment of the present disclosure is shown. The interaction 400 may be implemented on any suitable device. For illustrative purposes only, the interaction 400 is described as being implemented at the terminal device 310 - 1 and the network device 320 .
[0050] The terminal device 310-1 sends 405 one or more random access requests (also referred to as "message A") to the network device 320. The random access request includes a preamble for a random access procedure. The preamble is sent on a random access channel, such as a physical random access channel (PRACH). In some embodiments, the terminal device 310-1 may determine the PRACH and the preamble based on a predetermined configuration. For example, the terminal device 310-1 may be configured with information indicating the PRACH and / or preamble for a two-step RACH.
[0051] In addition, the random access request includes identification information of the terminal device 310-1. The identification information may be sent on a physical uplink shared channel (PUSCH). In some embodiments, if the terminal device 310-1 is in idle mode and / or inactive mode, the identification information may be a common control channel (CCCH) message containing a UE ID, for example, an RRC establishment request message for an idle mode UE or an RRC recovery request for an inactive mode UE. In other embodiments, if the terminal device 310-1 has a cell radio network temporary identifier (C-RNTI), for example, the terminal device 310-1 may be in connected mode, the identification information may be a C-RNTI. The request may include a C-RNTI medium access control (MAC) control element (CE).
[0052] Alternatively or in addition, the random access request may also include a buffer report (BSR) and / or a power headroom report (PHR). Depending on the size of the request, the random access request may also include other appropriate data.
[0053] The network device 320 receives a random access request from one or more terminal devices 310 (e.g., terminal devices 310-1 and / or 310-2). The network device 320 determines 410 at least one terminal device (referred to as a "target terminal device") from the one or more terminal devices 310. The target terminal device successfully accesses the random access. The random access request may come from one terminal device. Alternatively, the random access request may come from different terminal devices.
[0054] In some embodiments, the network device 320 may determine 415 the random access channel on which the random access request is received. In some embodiments, the preamble may be sent on different random access channels. In other embodiments, the preamble may be sent on the same random access channel.
[0055] In some embodiments, the network device 320 may be configured with information indicating a set of predetermined PRACHs for two-step RACH. If the PRACHs belong to the set of predetermined PRACHs, the network device 320 may determine that the random access request is for two-step RACH.
[0056] Alternatively or additionally, the network device 320 may be configured with information indicating a set of predetermined preambles for two-step RACH. If the preamble belongs to the set of predetermined preambles, the network device 320 may determine that the random access request is for two-step RACH.
[0057] The network device 320 may generate 420 a random access response (message B). The random access response includes identification information of the target terminal device. If the identification information carried in the random access request is the CCCH UE ID of the target terminal device, the network device 320 generates a random access response indicating the CCCH UE ID. For example, the random access response may include a CCCH MAC CE as a contention resolution. Alternatively or in addition, the random access response may include a C-RNTI field to allocate a C-RNTI to the target terminal device.
[0058] In other embodiments, if the identification information carried in the random access request is the C-RNTI of the target terminal device, the network device 320 generates a random access response indicating the C-RNTI MAC CE in the message if the response is not scheduled by the PDCCH addressed to the C-RNTI. For example, the random access response may include the C-RNTI MAC CE as a contention solution. Alternatively, the random access response may be scheduled by the PDCCH addressed to the C-RNTI without indicating the C-RNTI MAC CE in the message.
[0059] The identifier may be common to requests received on different random access channels. Alternatively, the identifier may be common to all requests received on a random access channel. In an exemplary embodiment, a common specific RNTI contention resolution RNTI (CR-RNTI) may be configured for sending a random access response, rather than linking the response to the PRACH opportunity that sent the preamble for the random access request.
[0060] In another embodiment, a finer granularity than just one public specific RNTI may be defined for the CR-RNTI. In this way, the decoding work of the terminal device to which the network device 320 does not respond is reduced. For example, each subframe / time slot within a radio frame corresponds to one RNTI. The CR-RNTI may be preconfigured to the network device 320 and the terminal device 310, or may be fixed in the specification.
[0061] The network device 320 may determine 425 a physical downlink control channel for sending the random access response. The downlink control channel is scrambled with an identifier.
[0062] In some embodiments, the downlink control channel is scrambled using the CR-RNTI. In other embodiments, if the network device 320 knows the C-RNTI of the terminal device 310-1, the downlink control channel is scrambled using the C-RNTI. In this way, the number of RNTIs can be reduced, thereby saving RNTI space for the RA procedure.
[0063] The network device 320 sends 430 a random access response (also referred to as "message B") to the terminal device 310-1. In some embodiments, the terminal device 310-1 may determine the CR-RNTI and receive the random access response on a PDCCH addressed to the CR-RNTI. For example, the terminal device 310-1 may monitor the PDCCH addressed to the CR-RNTI during a configured window time (e.g., a contention resolution window). Alternatively, the terminal device 310-1 may determine the C-RNTI and receive a random access response on a PDCCH addressed to the C-RNTI. For example, the terminal device 310-1 may monitor the PDCCH addressed to the C-RNTI during a configured window time.
[0064] The terminal device 310-1 determines 435 whether the random access procedure is successful. For example, if the terminal device 310-1 determines that the random access response includes identification information of the terminal device 310-1, the terminal device 310-1 may determine that the random access procedure of the terminal device 310-1 is successful.
[0065] In some embodiments, if the terminal device 310 - 1 determines that the random access response does not include identification information of the terminal device 310 - 1 , the terminal device 310 - 1 may determine that the attempt of the random access procedure of the terminal device 310 - 1 is unsuccessful.
[0066] In this way, a limited number of RNTIs are required for random access scheduling, rather than tens of thousands of RNTIs. In addition, the overhead of random access responses is reduced.
[0067] In some embodiments, the terminal device 310-1 may monitor the downlink control channel until the timer of the random access response expires. In some embodiments, if the random access response includes another indication that there is no other random access response to the random access request, the terminal device 310-1 may stop monitoring the random access response before the timer expires.
[0068] In addition, in some embodiments, the random access response may include an indication of another random access response for the random access request, and the terminal device 310-1 may monitor the other random access response within the window. The other random response may be for a specific PRACH resource, such as a PRACH opportunity, a preamble, a time slot / subframe number. In this way, the terminal device 310-1 does not have to wait and can immediately send another random access request.
[0069] Figure 5 1 is a flow chart of a method 500 according to an embodiment of the present disclosure. The method 500 may be implemented on any suitable device. For illustration purposes only, the method 500 is described as being implemented at the terminal device 310 - 1 .
[0070] At block 510, the terminal device 310-1 sends a random access request to the network device 320. The random access request includes at least one preamble for a random access procedure. The preamble may be sent on a random access channel (e.g., PRACH). In some embodiments, the terminal device 310-1 may determine the random access channel based on a predetermined configuration. For example, the terminal device 310-1 may be configured with information indicating a PRACH for a two-step RACH.
[0071] In addition, the random access request includes identification information of the terminal device 310-1. The identification information may be sent on a physical uplink shared channel (PUSCH). In some embodiments, if the terminal device 310-1 is in idle mode and / or inactive mode, the identification information may be a common control channel (CCCH) UE ID. In other embodiments, if the terminal device 310-1 has a cell radio network temporary identifier (C-RNTI), for example, the terminal device 310-1 may be in connected mode, the identification information may be a C-RNTI. The request may include a C-RNTI medium access control (MAC) control element (CE).
[0072] Alternatively or in addition, the random access request may also include a buffer report (BSR) and / or a power headroom report (PHR). Depending on the size of the request, the random access request may also include other appropriate data.
[0073] At block 520, terminal device 310-1 receives a random access response scheduled by a downlink control channel scrambled with an identifier from network device 320. The random access response includes identification information of at least one terminal device among the one or more terminal devices that succeeded in the random access procedure. The one or more terminal devices send a preamble to network device 320. The identifier is used to scramble a downlink control channel associated with the one or more terminal devices.
[0074] In some embodiments, the terminal device 310-1 may determine the CR-RNTI and receive a random access response on a PDCCH addressed to the CR-RNTI. For example, the terminal device 310-1 may monitor a PDCCH addressed to the CR-RNTI during a configured window time (e.g., a contention resolution window). Alternatively, the terminal device 310-1 may determine the C-RNTI and receive a random access response on a PDCCH addressed to the C-RNTI. For example, the terminal device 310-1 may monitor a PDCCH addressed to the C-RNTI during a configured window time.
[0075] If the identification information carried in the random access request is the CCCH UE ID of the target terminal device, the random access response may indicate the CCCH UE ID. For example, the random access response may include a CCCH MAC CE as a contention resolution. Alternatively or in addition, the random access response may include a C-RNTI MAC CE to allocate a C-RNTI to the terminal device.
[0076] In other embodiments, if the identification information carried in the random access request is the C-RNTI of the target terminal device, the random access response may indicate the C-RNTI. For example, the random access response may include a C-RNTI MAC CE as a contention resolution.
[0077] At block 530, the terminal device 310-1 determines whether the identification information of the terminal device 310-1 is in the random access response to determine that the random access procedure of the terminal device 310-1 is successful. If the terminal device 310-1 determines that the random access response includes the identification information of the terminal device 310-1, then at block 540, the terminal device 310-1 may determine that the random access procedure of the terminal device 310-1 is successful.
[0078] In some embodiments, the terminal device 310-1 may monitor the downlink control channel until a timer for the random access response expires. In some embodiments, if the random access response includes another indication that there is no further random access response to the random access request, the terminal device 310-1 may stop monitoring the random access response before the timer expires.
[0079] In some embodiments, if the terminal device 310 - 1 determines that the random access response does not include identification information of the terminal device 310 - 1 , the terminal device 310 - 1 may determine that the random access procedure of the terminal device 310 - 1 is unsuccessful.
[0080] In some embodiments, the apparatus for executing method 500 (eg, terminal device 310-1) may include corresponding components for executing corresponding steps in method 500. These components may be implemented in any suitable manner. For example, it may be implemented by a circuit or a software module.
[0081] In some embodiments, the apparatus includes: a component for sending a random access request at a terminal device to a network device, the random access request including at least one preamble code for a random access process and identification information of the terminal device; a component for receiving a random access response for the random access request scheduled by a downlink control channel from the network device, the random access response being encrypted with an identifier, the random access response including identification information of at least one terminal device among one or more terminal devices, the one or more terminal devices sending a preamble code for a random access process to the network device on a random access channel, the identifier being used to scramble a downlink control channel associated with the one or more terminal devices; and a component for determining that the random access process of the terminal device is successful in response to determining that the random access response includes the identification information of the terminal device.
[0082] In some embodiments, the identifier is common to a plurality of the random access channels.
[0083] In some embodiments, the identifier is common to all random access channels.
[0084] In some embodiments, means for receiving a random access response comprises means for determining the identifier as a contention resolution radio network temporary identifier (CR-RNTI); and means for receiving the random access response on a downlink control channel addressed to the CR-RNTI.
[0085] In some embodiments, means for receiving a random access response comprises means for determining the identifier as a cell radio network temporary identifier (C-RNTI); and means for receiving the random access response on a downlink control channel addressed to the C-RNTI.
[0086] In some embodiments, the component for sending identification information includes: a component for sending identification information including a common control channel (CCCH) user equipment (UE) ID in response to the terminal device being in an idle mode or an inactive mode; or a component for sending identification information including a cell radio network temporary identifier (C-RNTI) medium access control (MAC) control unit (ce) in response to the terminal device being in a connected mode.
[0087] In some embodiments, the random access request further includes at least one of: a buffer status report (BSR) or a power headroom report.
[0088] In some embodiments, the apparatus further comprises at least one of: a component for determining that a random access request of a terminal device has failed in response to determining that the random access response does not include identification information of the terminal device; and a component for monitoring another random access response in response to the random access response including an indication of another random access response to the random access request.
[0089] In some embodiments, the random access response includes at least one of the following: a CCH MAC CE or a C-RNTI MAC CE.
[0090] In some embodiments, the apparatus further comprises means for stopping monitoring the downlink control channel before expiration of a time for the random access response in response to the random access response comprising another indication indicating that there is no another random access response to the random access request.
[0091] In some embodiments, the apparatus further comprises: means for monitoring the downlink control channel until the random access response time expires.
[0092] Figure 61 shows a flow chart of a method 600 according to an embodiment of the present disclosure. The method 600 may be implemented on any suitable device. For illustration purposes only, the method 600 is described as being implemented at the network device 120.
[0093] At block 610, the network device 320 receives a random access request from one or more terminal devices 310-1. The random access request includes a preamble for a random access procedure of one or more terminal devices. The preamble may be received on a random access channel. In some embodiments, the preamble may be received on different random access channels. In other embodiments, the preamble may be received on the same random access channel.
[0094] In addition, the random access request includes identification information of the terminal device 310. The identification information may be received on a physical uplink shared channel (PUSCH). In some embodiments, if the terminal device is in an idle mode and / or an inactive mode, the identification information may be a common control channel (CCCH) UE ID. In other embodiments, if the terminal device 310 has a cell radio network temporary identifier (C-RNTI), for example, the terminal device 310-1 may be in a connected mode, the identification information may be a C-RNTI. The request may include a C-RNTI medium access control (MAC) control element (CE).
[0095] Alternatively or in addition, the random access request may also include a buffer report (BSR) and / or a power headroom report (PHR). Depending on the size of the request, the random access request may also include other appropriate data.
[0096] In some embodiments, the network device 320 may determine a random access channel for receiving the random access request. In some embodiments, the network device 320 may be configured with information indicating a set of predetermined random access channels for two-step RACH. If the random access channel belongs to the set of predetermined random access channels, the network device 320 may determine that the random access request is for two-step RACH.
[0097] In some embodiments, the network device 320 may be configured with information indicating a set of predetermined preambles for two-step RACH. If the preamble belongs to the set of predetermined preambles, the network device 320 may determine that the random access request is for two-step RACH.
[0098] In some embodiments, the network device 320 may generate a random access response. The random access response includes identification information of the target terminal device. If the identification information carried in the random access request is the CCCH UE ID of the target terminal device, the network device 320 generates a random access response indicating the CCCH UE ID. For example, the random access response may include a CCCH MAC CE as a contention resolution. Alternatively or in addition, the random access response may include a C-RNTI field for allocating a C-RNTI to the terminal device.
[0099] In other embodiments, if the identification information carried in the random access request is the C-RNTI of the target terminal device, the network device 320 generates a random access response indicating the C-RNTI. For example, if the random access is not scheduled by the PDCCH addressed to the C-RNTI, but is arranged by the contention resolution RNTI, the random access response may include the C-RNTI MAC CE as contention resolution.
[0100] In an exemplary embodiment, a common specific RNTI contention resolution RNTI (CR-RNTI) may be configured for sending a random access response, rather than linking the response to the PRACH opportunity where the preamble of the random access request was sent.
[0101] In another embodiment, a finer granularity than just one public specific RNTI can be defined for the CR-RNTI. In this way, the access effort of the terminal device to which the network device 320 does not respond is reduced. For example, each subframe / time slot in a radio frame corresponds to one RNTI. The CR-RNTI can be preconfigured to the network device 320 and the terminal device 310.
[0102] The network device 320 may determine a physical downlink control channel (PDCCH) for sending a random access response. In some embodiments, the PDCCH is addressed to the CR-RNTI. In other embodiments, the PDCCH is addressed to the C-RNTI. In this way, the number of RNTIs may be reduced, thereby saving space.
[0103] At block 620, the network device 320 sends a random access response to the terminal device 310-1. The random access response is scheduled by a downlink control channel, and the downlink control channel is scrambled with an identifier. In some embodiments, the PDCCH may be scrambled with a CR-RNTI. Alternatively, the PDCCH may also be scrambled with a C-RNTI. In some embodiments, the identifier is common to multiple random access channels in the random access channel. Alternatively, the identifier is common to all random access channels.
[0104] In some embodiments, an apparatus for executing method 600 (e.g., network device 120) may include corresponding components for executing corresponding steps in method 600. These components may be implemented in any suitable manner. For example, it may be implemented by a circuit or a software module.
[0105] In some embodiments, the apparatus includes: a component for receiving a random access request from one or more terminal devices at a network device, the random access request including a preamble code for a random access process for the one or more terminal devices and identification information of the one or more terminal devices, the preamble code being sent on a random access channel; and a component for sending a random access response to the one or more terminal devices on a downlink control channel scrambled with an identifier, the random access response including identification information of at least one of the one or more terminal devices to indicate that the random access process of at least one of the one or more terminal devices is successful, the identifier being used to scramble a downlink control channel associated with the one or more terminal devices.
[0106] In some embodiments, the identification information of multiple terminal devices includes: a common control channel (CCCH) user equipment (UE) ID of multiple terminal devices, or at least one of the cell radio network temporary identifier (C-RNTI) medium access control (MAC) control elements (CES) of one or more terminal devices.
[0107] In some embodiments, the random access request further comprises at least one of: a buffer status report (BSR) or a power headroom report (PHR).
[0108] In some embodiments, the apparatus further comprises: means for determining whether another random access response is required; and means for adding an indication in the random access response indicating another random access response in response to determining that another random access response is required.
[0109] In some embodiments, the means for sending a random access response includes: means for determining a physical random access channel on which a preamble is received; means for comparing the PRACH with a set of predetermined PRACHs; means for determining a downlink control channel addressed to the identifier in response to the PRACH belonging to the set of PRACHs; and means for sending the random access response on the downlink control channel.
[0110] In some embodiments, the means for sending a random access response includes: means for comparing a preamble to a set of predetermined preambles; means for determining a downlink control channel addressed to the identifier in response to the preamble belonging to the set of predetermined preambles; and means for sending the random access response on the downlink control channel.
[0111] In some embodiments, the component for sending a random access response includes: a component for generating a random access response indicating a common control channel (CCCH) user equipment (UE) ID of the at least one terminal device in response to the identification information of the at least one terminal device being a CCH ID of the at least one terminal device; or a component for generating a random access response indicating a cell radio network temporary identifier (C-RNTI) of the at least one terminal device in response to the identification information of the at least one terminal device being a C-RNTI.
[0112] Figure 7 700 is a simplified block diagram of a device 700 suitable for implementing an embodiment of the present disclosure. The device 700 may be implemented at a registration management entity 730. The device 700 may also be implemented at a terminal device 110-1. The device 700 may also be implemented at a network device 120-1. As shown, the device 700 includes one or more processors 710, one or more memories 720 coupled to the processor 710, and one or more transmitters and / or receivers (TX / RX) 740 coupled to the processor 710.
[0113] Processor 710 may be of any type suitable for the local technology network, and may include, as non-limiting examples, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 700 may have multiple processors, such as application specific integrated circuit chips, that are time slaved to a clock synchronized with a main processor.
[0114] Memory 720 may be of any type suitable for the local technology network and may be implemented using any suitable data storage technology, such as, by way of non-limiting example, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory.
[0115] The memory 720 stores at least a portion of the program 730. The TX / RX 740 is used for bidirectional communication. The TX / RX 740 has at least one antenna to facilitate communication, although in practice the access nodes mentioned in this application may have multiple antennas. The communication interface may represent any interface necessary to communicate with other network elements.
[0116] Assume that program 730 includes program instructions that, when executed by associated processor 710, enable device 700 to operate in accordance with embodiments of the present disclosure, as referred to herein. Figure 2 and 6That is, the embodiments of the present disclosure may be implemented by computer software that may be executed by the processor 710 of the device 700, or by hardware, or by a combination of software and hardware.
[0117] Although this specification contains many specific implementation details, these should not be interpreted as limiting the scope of any disclosure or content that may be claimed, but should be interpreted as a description of features specific to the specific disclosure of a specific implementation. Certain features described in this specification in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments or in any suitable sub-combination, respectively. In addition, although the features may be described above as working in certain combinations and even initially claimed as such, in some cases, one or more features in the claimed combination may be excluded from the combination, and the claimed combination may involve a variant of a sub-combination or a sub-combination.
[0118] Similarly, although operations are depicted in a particular order in the accompanying drawings, this should not be understood as requiring that such operations be performed in the particular order shown or in a sequential order, or that all of the illustrated operations be performed to achieve the desired results. In some cases, multitasking and parallel processing may be advantageous. In addition, the separation of various system components in the above-described embodiments should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated into a single software product, or packaged into multiple software products.
[0119] When read in conjunction with the accompanying drawings, in view of the foregoing description, various modifications and adaptations to the foregoing exemplary embodiments of the present disclosure will become clear to those skilled in the art. Any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of the present disclosure. In addition, those skilled in the art to which these embodiments of the present disclosure relate who benefit from the teachings presented in the foregoing description and the associated drawings will be able to conceive of other embodiments of the present disclosure set forth herein.
[0120] Therefore, it should be understood that the embodiments of the present disclosure are not limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are used herein, they are used in a generic and descriptive sense only and not for the purpose of limitation.
Claims
1. A terminal device, comprising: at least one processor; as well as A memory is coupled to the at least one processor, wherein the memory stores instructions, and when the instructions are executed by the at least one processor, the terminal device: At the terminal device, sending a random access request to a network device, the random access request comprising at least one preamble for a random access procedure and a cell radio network temporary identifier of the terminal device; receiving, from the network device and during a configured time window, a random access response to the random access request on a downlink control channel addressed to the cell radio network temporary identifier; In response to the receiving, determining that the random access procedure of the terminal device is successful; as well as In response to the random access response including another indication indicating that there is no another random access response scheduled by the downlink control channel for the random access request, stopping monitoring for another random access response scheduled by the downlink control channel before the time window for the random access response expires.
2. A terminal device according to claim 1, wherein the cell radio network temporary identifier is common to multiple random access channels in the random access channel, and one or more terminal devices send a preamble code for a random access procedure to the network device on the random access channel.
3. The terminal device according to claim 2, wherein the cell radio network temporary identifier is common to all of the random access channels.
4. The terminal device according to claim 1, wherein the terminal device is further caused to send the cell radio network temporary identifier by: In response to the terminal device being in connected mode, the cell radio network temporary identifier is sent.
5. The terminal device according to claim 1, wherein the random access request further comprises at least one of the following: Buffer status report, or Power Headroom Report.
6. The terminal device according to claim 1, wherein the terminal device is further configured to perform at least one of the following: In response to determining that the random access response is not addressed to the cell radio network temporary identifier, determining that the random access request of the terminal device has failed; and In response to the random access response including an indication indicating another random access response to the random access request, monitoring the another random access response.
7. The terminal device according to claim 1, wherein the terminal device is further configured to: The downlink control channel is monitored until a time for the random access response expires.
8. The terminal device of claim 1, wherein the random access response comprises a Cell Radio Network Temporary Identifier (NRTI) Medium Access Control (MAC) control element.
9. A method of communication, comprising: At a terminal device, sending a random access request to a network device, the random access request comprising at least one preamble for a random access procedure and a cell radio network temporary identifier of the terminal device; receiving, from the network device and during a configured time window, a random access response to the random access request on a downlink control channel addressed to the cell radio network temporary identifier; In response to the receiving, determining that the random access procedure of the terminal device is successful; as well as In response to the random access response including another indication indicating that there is no another random access response scheduled by the downlink control channel for the random access request, stopping monitoring for another random access response scheduled by the downlink control channel before the time window for the random access response expires.
10. The method of claim 9, wherein the cell radio network temporary identifier is common to a plurality of random access channels in a random access channel on which one or more terminal devices transmit a preamble for a random access procedure to the network device.
11. The method of claim 10, wherein the cell radio network temporary identifier is common to all of the random access channels.
12. The method of claim 9, wherein sending the cell radio network temporary identifier comprises: In response to the terminal device being in connected mode, the cell radio network temporary identifier is sent.
13. The method according to claim 9, wherein the random access request further comprises at least one of the following: Buffer status report, or Power Headroom Report.
14. The method according to claim 9, further comprising at least one of the following: In response to determining that the random access response is not addressed to the cell radio network temporary identifier, determining that the random access request of the terminal device has failed; and In response to the random access response including an indication indicating another random access response to the random access request, monitoring the another random access response.
15. The method according to claim 9, further comprising: The downlink control channel is monitored until a time for the random access response expires.
16. The method of claim 9, wherein the random access response comprises a Cell Radio Network Temporary Identifier (NRTI) Medium Access Control (MAC) control element.
17. A computer-readable medium having instructions stored thereon, which, when executed by at least one processing unit of a machine, causes the machine to execute the method according to any one of claims 9 to 16.
18. An apparatus for communication, comprising: means for sending, at a terminal device, a random access request to a network device, the random access request comprising at least one preamble for a random access procedure and a cell radio network temporary identifier of the terminal device; means for receiving, from the network device and during a configured time window, a random access response to the random access request on a downlink control channel addressed to the cell radio network temporary identifier; means for determining, in response to said receiving, that said random access procedure of said terminal device is successful; as well as means for stopping monitoring for another random access response scheduled by the downlink control channel before expiration of the time window for the random access response in response to the random access response including another indication indicating that there is no another random access response scheduled by the downlink control channel for the random access request.
Citation Information
Patent Citations
Random access response RAR transmission method and related device
CN106686691A
Random-access response with analog beamforming
CN107409416A
Random access method, device and equipment
CN107872899A
Random access method and apparatus
WO2018107499A1
Method and apparatus for random access
WO2018119612A1
