RU2783599C1 - Random access procedure - Google Patents

Abstract

FIELD: random access procedure means.

SUBSTANCE: invention relates to means for a random access procedure. At the terminal device, a random access request is transmitted to the network device in a random access procedure. It is determined, in response to receiving from the network device, during the random access procedure, the uplink resource grant to the terminal device, whether the size indicated by the uplink resource grant matches the size of the media access control PDU stored in the buffer terminal device. The media access control PDU subunit is included in the subsequent uplink transmission after determining that the size indicated by the uplink resource grant does not match the size of the media access control’s PDU stored in the buffer.

EFFECT: reducing the load between preambles.

18 cl, 5 dwg

Description

FIELD OF TECHNOLOGY

Embodiments of the present disclosure generally relate to the field of telecommunications and, in particular, to methods, devices and a computer-readable medium for storing information for a random access procedure.

BACKGROUND OF THE INVENTION

New radio communication (New Radio - NR) 5G is provided with a multipath mode of operation. Support for multipath operation in NR includes beam quality measurement, beam quality reporting, beam assignment, and a recovery mechanism in case the assigned beam quality is not good enough. NR provides support for multipath operation in all phases of radio operation: initial/random access, paging, transmit/receive data/control, and mobility management.

In the case of multipath operation in NR, user equipment (UE) can switch between beams allocated random access resources without contention (Contention Free Random Access - CFRA), and beams allocated random access resources based on contention (Contention Based Random Access). - CBRA). However, in LTE, the communication network allocates CFRA resources in the entire cell to the UE. In other words, there is no switching between CFRA and CBRA. Thus, when a beam switching procedure occurs in NR, the Medium Access Control (MAC) Protocol Data Unit (PDU) size allowed in the uplink resource grant allocated during the procedure Random Access (RA) that is transmitted from a network device (eg, gNB) may be different from the MAC PDU size received from the UE's Msg3 buffer.

SUMMARY OF THE INVENTION

In general, exemplary embodiments of the present disclosure provide methods, apparatuses, and a computer-readable medium for storing information for a random access procedure.

In a first aspect, a method implemented on a terminal device is provided. Said method includes transmitting, at the terminal device, a random access request in a random access procedure to a network device; determining, in response to receiving, in the random access procedure, from the network device an uplink resource grant to the terminal device, whether the first size of the first data block indicated by the uplink resource grant corresponds to the second size of the second data block stored in the buffer of the terminal device; determining, in response to determining that the first size does not match the second size, the first part of the second data block for subsequent transmissions.

In a second aspect, a method implemented on a network device is provided. This method includes receiving from the terminal device a random access request in a random access procedure; transmitting, in response to receiving the random access request, to the uplink resource grant terminal device of the terminal device, wherein the uplink resource grant indicates a first size of the first data block such that the terminal device determines whether the first size of the first data block matches the second size the second block of data stored in the buffer of the terminal device.

In a third aspect, a terminal device is provided. The specified device contains at least one processor; and at least one storage device containing computer program codes. Said at least one storage device and said computer program codes are configured, by means of at least one processor, to cause said device to at least perform said method in accordance with said first aspect.

In a fourth aspect, a network device is provided. The specified device contains at least one processor; and at least one storage device containing computer program codes. Said at least one storage device and said computer program codes are configured, by means of at least one processor, to cause said device to at least perform said method in accordance with said second aspect.

In a fifth aspect, an apparatus is provided, comprising means for carrying out the steps of the method according to the first aspect.

In a sixth aspect, an apparatus is provided, comprising means for performing the steps of the method according to the second aspect.

In a seventh aspect, a computer-readable medium is provided that contains a computer program stored thereon, which, when executed by at least one device processor, causes said device to execute the method according to the first aspect.

In an eighth aspect, a computer-readable medium is provided that contains a computer program stored thereon, which, when executed by at least one device processor, causes said device to execute the method according to the second aspect.

It should be understood that this section of the summary is not intended to define key or essential characteristics of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily apparent from the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

By describing in more detail some exemplary embodiments of the present disclosure in the accompanying drawings, the aforementioned and other objects, features, and advantages of the present disclosure will become more apparent, while:

in fig. 1 shows an example of a communication system 100 in which exemplary embodiments of the present invention may be implemented;

in fig. 2 is a diagram of an exemplary process 200 for a random access procedure according to some exemplary embodiments of the present disclosure;

in fig. 3 is a flow diagram of an example method 300 for a random access procedure according to some example embodiments of the present disclosure;

in fig. 4 is a flow diagram of an exemplary method 400 for a random access procedure according to some exemplary embodiments of the present disclosure;

in fig. 5 is a simplified block diagram of an apparatus suitable for implementing an exemplary embodiment of the present disclosure.

Throughout the drawings, the same or like reference numerals designate the same or like element.

DETAILED DESCRIPTION

The principle of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for purposes of illustration only and to assist those skilled in the art in understanding and practicing the present disclosure without suggesting any limitation as to the scope of the disclosure. The disclosure described herein may be implemented in a variety of ways other than those described below.

In the following description and claims, unless otherwise indicated, all technical and scientific terms used herein have the same meaning as generally understood by a person skilled in the art to which this disclosure pertains.

As used herein, the term “communication network” refers to a network that follows any suitable communication standards or protocols, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A) ) and 5G NR, and uses any suitable communication technology, including, for example, multiple input and multiple output (Multiple-Input Multiple-Output - MIMO), OFDM, time division multiplexing (TDM), frequency division multiplexing (frequency division multiplexing - FDM), code division multiplexing (CDM), Bluetooth, ZigBee, machine type communication (MTS), eMBB, mMTC and uRLLC technologies. For discussion purposes, in some embodiments, an LTE network, an LTE-A network, a 5G NR network, or any combination thereof is taken as an example of a communication network.

As used herein, the term "network device" refers to any suitable device on the network side of a communications network. The network device may include any suitable device in the access network of the communication network, for example, including a base station (base station - BS), a repeater, an access point (AP), a node B (node B - NodeB, or NB), an advanced NodeB (evolved NodeB - eNodeB, or eNB), gigabit NodeB (gigabit NodeB - gNB), remote radio module (Remote Radio Module - RRU), radio module (radio header - RH), remote radio module (remote radio head - RRH), node with low power consumption such as femto, pico and the like. For purposes of discussion, in some embodiments, an eNB is taken as an example of a network device.

The network device may also include any suitable device in the core network, for example, including multi-standard radio (MSR) radio equipment such as the MSR BS, network controllers such as radio network controllers (RNCs) or base station controllers. stations (base station controller - BSC), multi-cell / multicast coordination objects (Multi-cell / multicast Coordination Entitie - MCE), mobile switching centers (Mobile Switching Center - MSC) and MME, nodes of operation and management (Operation and Management - O & M ), Operation Support System (OSS) nodes, Self-Organization Network (SON) nodes, positioning nodes such as Enhanced Serving Mobile Location Center (E-SMLC), and /or mobile data terminals (Mobile Data Terminal - MDT).

As used herein, the term "terminal device" refers to a device capable of, configured for, configured and/or operable to communicate with a network device or additional terminal device in a communications network. Communication may include the transmission and/or reception of wireless signals using electromagnetic signals, radio waves, infrared signals, and/or other types of signals suitable for transmitting information over the air. In some embodiments, a terminal device may be configured to transmit and/or receive information without direct human interaction. For example, a terminal device may transmit information to a network device on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.

Examples of a terminal device include, but are not limited to, User Equipment (UE) such as smartphones, wirelessly enabled tablet computers, laptop-embedded equipment (LEE), laptop-mounted equipment - LME) and / or wireless equipment installed in the subscriber's premises (customer-premises equipment - CPE). For purposes of discussion below, some embodiments will be described with reference to UEs as examples of terminal devices, and the terms "terminal device" and "user equipment" (UE) may be used interchangeably in the context of this disclosure.

As used herein, the term "cell" refers to an area covered by radio signals transmitted by a network device. A terminal device in a cell may be served by a network device and access a communication network through the network device.

As used herein, the term "scheme" may refer to one or more or all of the following:

(a) implementations of circuits in hardware only (for example, implementations in analog and/or digital circuits only), and

(b) combinations of hardware circuits and software, such as (if applicable): (i) a combination of analog and/or digital hardware circuits with software/firmware and (ii) any parts of the hardware processor(s) with software ( including digital signal processor(s), software and storage device(s) that work together to cause a machine such as a mobile phone or server to perform various functions) and

(c) hardware(s) circuit(s) and/or processor(s), such as a microprocessor(s) or part of a microprocessor(s), that require software (such as firmware) to operate, but said software may be absent when it is not needed for work.

This definition of "scheme" applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term "circuit" also encompasses the implementation of simply a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) associated software and/or firmware. The term "circuitry" also encompasses, for example, and when applicable to a particular claim element, a baseband 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.

In the context of this document, the singular forms are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "includes" and its variants should be understood as open terms meaning "includes, but is not limited to". The term "based on" should be read as "based at least in part on". The terms "one embodiment" and "an embodiment" should be read as "at least one embodiment". The term "another embodiment" should be read as "at least one other embodiment". Other definitions, explicit and implicit, may be included below.

In FIG. 1 illustrates a communications network 100 in which embodiments of the present disclosure may be implemented. Communication network 100 may conform to any suitable protocol or standard that already exists or will be developed in the future. In some embodiments, communication network 100 may be an LTE (or LTE-A) network, an NR network, or a combination thereof.

Communication network 100 includes network device 110. Network device 110 services terminal device 120 in cell 111. It should be understood that the number of network devices and terminal devices shown is for illustration purposes only, without any limitation. Communication network 100 may include any suitable number of network devices and terminal devices. Communication between network device 110 and terminal device 120 may use any suitable technology that already exists or will be developed in the future.

The issue of different resource grant sizes provided by the communication network for the transmission of MESSAGE 3 (MESSAGE 3 - Msg3) has been discussed in LTE. Msg3 can transmit layer 2 and layer 3 messages, such as a request to establish radio resource control for initial access or a C-RNTI Control Element (CE) for random access in connected mode, from the terminal device 120 to the network device 110. If an uplink resource grant provided in a Random Access Response (RAR) for the same RAP group has a different size than the previous uplink resource grant connection (eg, the first grant of an uplink resource) allocated during this random access procedure, then the behavior of the terminal device 120 has not been specified within the random access procedure, since this is considered to be a very rare case. In LTE, the communication network allocates CFRA resources in the entire cell to terminal device 120. In other words, there is no switching between CFRA and CBRA within the random access procedure.

New radio communication (New Radio - NR) 5G is provided with a multipath mode of operation. Thus, unlike in LTE, where CFRA resources can be allocated to a single cell (eg, cell 111 as shown in FIG. 1), in NR, the communication network may not allocate CFRA resources to all beams, but only to a subset of beams in cell 111 , because it may be too expensive to allocate CFRA resources for all beams for all UEs, and this may defeat the purpose of beamforming.

Thus, in the case of multipath operation in NR, a user equipment (UE), such as a terminal device 120, as shown in FIG. 1 can move inside the cell and change the beam. The terminal device 120 may switch between beams with one RA resource type to some other beams with a different RA resource type, for example, the terminal device can switch in cell 111 between the beams allocated with contention-free random access (CFRA) resources and the beams allocated with random access resources (CFRA). contention-based access (CBRA).

If terminal device 120 switches from CFRA to CBRA, there are no problems caused by Msg3, which can only be generated during the first CBRA attempt. In the case of CFRA, the RA procedure is already successful in receiving Msg2 from the gNB (eg, network device 110 as shown in FIG. 1).

However, if the terminal device 120 switches from CBRA to CFRA, according to TS 38.321, Msg3 has been generated and must also be transmitted using CFRA because the Hybrid automatic repeat request (hybrid ARQ or HARQ) buffer must be cleared. after the completion of the RA procedure, but the Msg3 buffer must not be flushed. In addition, in the HARQ entity, in case an uplink resource grant is received in RAR and there is a Media Access Control (MAC) Protocol Data Unit (MAC) in the Msg3 buffer, the MAC PDU can be obtained from the Msg3 buffer.

In the above case, if the resource grant provided in the RAR for the CFRA preamble transmission has a size equal to the size indicated in the resource grant provided earlier in response to the CBRA preamble transmission, the MAC PDU in the Msg3 buffer may be transmitted in the secured resource grant. However, two different preamble groups are defined for CBRA, ie. preambles Group-A and Group-B. In general, terminal device 120 selects a sequence from these two groups based on the uplink burst size and radio conditions. This helps network device 110 calculate the Physical Uplink Shared Channel (PUSCH) resources required for uplink transmission from terminal device 120. Group-A preambles are used for smaller packets or larger packets in poor radio conditions. Group-B preambles are used for larger packets in good radio conditions. In this case, the network device 110 will not know whether the terminal device 120 attempted CBRA before the CFRA or which preamble group was applied when transmitting the CBRA preamble. Therefore, the problem caused by different Msg3 resource grant sizes is expected to occur frequently in NR.

In addition, given the fact that the MAC PDU in the Msg3 buffer can be multiplexed, for example, at least the segment of the handover transmission complete command (RRCReconfigurationComplete), it is undesirable to lose such data and delay the completion of the HO procedure (because a layer retransmission would be required). RLC). In the case where CFRA is selected for the preamble attempt, terminal device 120 will use the Msg3 buffer to transmit the first uplink data in the RA procedure. In case CFRA is selected for the preamble attempt, the RA procedure is successfully completed by receiving the RAR.

Thus, with respect to the fact that the size of the MAC PDU indicated in the uplink resource grant allocated during the RA procedure that is transmitted from the network device 110 may be different from the size of the MAC PDU obtained from the Msg3 buffer of the terminal device 120, there were some approaches to solving this problem are considered.

One approach suggested that during selection of a random access resource for handover, terminal device 120 should not select a random access preamble from among the CFRA preamble if Msg3 was transmitted in the current random access procedure. However, this approach can waste allocated resources for CFRA and unnecessarily increase the load between contention-based preambles.

In a further approach, it has been proposed that the multiplexing and translation entity could include a plurality of MAC sub-PDUs from the received MAC PDU in subsequent uplink transmissions. In case the size of the uplink resource grant does not match the earlier uplink resource grant provided in response to the CBRA preamble, the Msg3 buffer may be cleared and a new MAC PDU may be obtained from the mux and broadcast entity. However, this approach can lead to data loss.

As an option to clear Msg3, the MAC may indicate data that has been multiplexed in the MAC PDU, in which case the RLC PDU may be regenerated and multiplexed again. This approach may be good for data processing, but may not work for MAC Control Elements (CEs).

The principle and implementations of the present disclosure will be described in detail below with reference to FIG. 2, which shows a process 200 according to exemplary embodiments of the present disclosure. For purposes of discussion, process 200 will be described with reference to FIG. 1. Process 200 may include a random access procedure.

In FIG. 2 is a diagram of an exemplary process 200 for a random access procedure in accordance with some exemplary embodiments of the present disclosure.

As shown in FIG. 2, when terminal device 120 performs random access, terminal device 120 sends 210 a random access request, i.e., a random access preamble (RAP), to network device 110. RAP is also referred to as "MESSAGE 1" or "Msg1" in the context of this disclosure. The RAP is a signature code sequence that acts as an identifier for the terminal device 120. Depending on whether the RAP is UE-specific, the random access procedure is divided into a contention-free random access (CFRA) procedure and a contention-based random access (CBRA) procedure. ). Therefore, the terminal device 120 may send to the network device 110 a different random access preamble, namely a CFRA preamble or a CBRA preamble. As described above, for the CBRA procedure, terminal device 120 may select a CBRA preamble from Group-A and Group-B. Terminal device 120 may select a sequence from these two groups based on the uplink burst size and radio conditions.

Upon detection of the RAP preamble from terminal device 120, network device 110 may respond 220 to the random access request by transmitting a random access response (RAR) (also referred to as "MESSAGE 2" or "Msg2" in the context of this disclosure) to terminal device 120 based on the received preamble. RAP. The RAR may be scheduled over a physical downlink control channel (PDCCH) and the actual message over a physical downlink shared channel (PDSCH). The RAR may include, for example, a Timing Advance Command (TAC) for UL timing alignment, an uplink resource grant, and a temporary cellular radio network ID for terminal device 120.

In a contention-free random access procedure, that is, a contention-free random access procedure, the terminal device 120 sends a dedicated RAP to the network device 110; and, if the terminal device 120 receives the RAR sent by the network device 110, the terminal device 120 determines the success of the random access procedure.

In the contention-based random access procedure, after the terminal device 120 receives the RAR, the terminal device 120 may send a message (also referred to as "MESSAGE 3" or "Msg3") on a Physical Uplink Shared Channel (PUSCH) to the network device 110 As indicated above, Msg3 may transmit layer 2 and layer 3 messages, such as a request to establish radio resource control for initial access or a MAC C-RNTI CE for connected mode random access, from terminal device 120 to network device 110. If the terminal device 120 receives the RAR from the network device 110, the terminal device can obtain an uplink resource grant contained in the RAR indicating an available uplink resource grant for the terminal device 120 to transmit its Msg3.

As mentioned above, terminal device 120 may send a preamble from different groups based on uplink packet size and radio conditions, and network device 110 may allocate an appropriate uplink resource grant to terminal device 120 to transmit Msg3. In this case, for transmitting Msg3, the uplink resource grant contained in the RAR may correspond to the uplink resource grant in the Msg3 buffer of the terminal device 120.

As shown in FIG. 2, terminal device 120 determines 230 whether the first size of the first data block indicated by the uplink resource grant matches the second size of the second data block stored in the buffer of terminal device 120. The first and second data blocks may be referred to as a MAC PDU. The buffer may be referred to as the Msg3 buffer of terminal device 120.

In some exemplary embodiments, to determine if the first size matches the second size, terminal device 120 may determine the second size based on the Msg3 that was transmitted from the Msg3 buffer of terminal device 120. The terminal device may further determine the first size from the uplink resource grant. transmitted from the network device 110. The terminal device 120 may compare the first size with the second size and determine if there is a mismatch between the first size and the second size.

In some exemplary embodiments, Msg3 may indicate at least one control element for media access control (MAC CE). In some exemplary embodiments, the MAC CE may comprise at least one of the C-RNTI MAC CE, Buffer Status Report (BSR), and Power Headroom Report (PHR).

In general, a BSR is a type of MAC CE from a UE (eg, terminal device 120) to a gNB (eg, network device 110) carrying information about how much data is in the UE's buffer to send.

BSR can refer to different types of BSR. For example, a BSR may contain a regular BSR, a periodic BSR, and a fill BSR. A regular BSR is sent when new data enters the buffer and the new data has a higher priority than the data already waiting in the buffer. The periodic BSR is sent at a predetermined frequency. The specified gNB may preconfigure the periodicity for the UE with an RRC message (eg, RRCConnectionReconfiguration). In addition, the padding BSR is sent when the number of padding bits in the data message is greater than the size of the padding BSR, so that the padding bit space can be used to send the BSR. The padding BSR may contain a truncated BSR in case the full BSR does not match the available padding bits. In this case, the BSR is truncated and the terminal device 120 only reports the highest priority data to the network device 110.

In general, the PHR may indicate how much transmit power is left in the UE.

As shown in FIG. 2, if terminal device 120 determines that the first size does not match the second size, terminal device 120 determines 240 the first part of the second data block for subsequent transmissions.

In some exemplary embodiments, subsequent transmissions may comprise at least one of the following: a transmission associated with an uplink resource grant provided in a Random Access Response (RAR) and a transmission associated with an additional uplink resource grant that is different from providing an uplink resource.

In some exemplary embodiments, terminal device 120 may determine if the second dimension matches the first dimension. If the terminal device determines that the second size does not match the first size, the terminal device 120 may discard some portions from the second data block or may not consider them for subsequent transmissions.

In some exemplary embodiments, terminal device 120 may discard the truncated BSR from the second data block.

Alternatively or additionally, terminal device 120 may discard the padding BSR from the second data block.

Alternatively or additionally, terminal device 120 may discard the PHR from the second data block.

Alternatively or additionally, terminal device 120 may adjust the size of the truncated BSR. For example, the truncated BSR is adjusted to match the available size, i.e. the number of reported Logical Channel Groups (LCGs) varies. Naturally, the bitmap may reflect the addition/deletion of the reported LCG. Adjusting the size of the truncated BSR may be limited to cases where the size is reduced. It should be understood that removing information may be easier for a UE to implement than creating additional information. In this way, the latest information about the BSR can be provided.

Alternatively or additionally, terminal device 120 may discard the regular/periodic BSR and/or PHR. In addition, regular/periodic BSRs and/or PHRs cannot be canceled until the regular/periodic BSRs and PHRs are included in a resource grant scheduled by the C-RNTI or CS-RNTI. This approach is intended to provide the latest available information about the buffer status and power headroom of terminal device 120 as the BSR/PHR will be re-generated for subsequent transmissions.

In some exemplary embodiments, if the terminal device determines that the second size does not match the first size, the terminal device 120 may determine whether the random access procedure has been successfully completed by receiving an uplink resource grant. If the terminal device 120 determines that the random access procedure is considered to be successfully completed, the terminal device may discard the C-RNTI MAC medium access control (CE MAC) control element from the second data block.

In some exemplary embodiments, if terminal device 120 determines that the second size does not match the first size, terminal device 120 may determine if a contention-free random access preamble was transmitted. If the terminal device 120 determines that the contention-free random access preamble has been transmitted, the terminal device may discard the C-RNTI MAC media access control (MAC CE) control element from the second data block.

In some exemplary embodiments, determining by terminal device 120 whether the random access procedure has been successfully completed may include determining that the uplink resource grant and/or RAR are addressed to at least one of the following: a temporary C-RNTI and a temporary random access radio network identifier RA-RNTI.

The case described now may relate to the random access procedure during the switchover of the terminal device 120 from the CBRA procedure to the CFRA procedure, because in the CFRA procedure, the terminal device 120 sends a dedicated RAP to the network device 110; and, if the terminal device 120 receives the RAR sent by the network device 110, the terminal device 120 determines the success of the random access. That is, it is not necessary to transmit the CE MAC C-RNTI to the network device 110.

According to this solution, since the terminal device 120 is already identified from the transmitted CFRA preamble, unnecessary transmission overhead can be avoided. In addition, this solution avoids the transmission of any other types of MAC PDUs by the terminal device 120 because the network device 110 does not expect to receive the C-RNTI MAC CE in response to the transmission of the CFRA preamble.

In some exemplary embodiments, another MAC CE multiplexed in a received MAC PDU may be indicated to a multiplexing and translation entity for inclusion in subsequent uplink transmissions. Thus, loss of control information during Msg3 recovery can be avoided because other multiplexed MAC CEs can be included in subsequent transmissions.

As shown in FIG. 2, terminal device 120 transmits 250 at least a portion of the first portion of the second data block in the first data block to the network device. The remainder of the first part may be transmitted in subsequent transmissions.

Through the above embodiments, for each uplink resource grant, the HARQ entity of the terminal device 120 must identify the HARQ process associated with that resource grant. For each identified HARQ process:

if the received resource grant was not addressed to the temporary C-RNTI on the PDCCH and the New Data Indicator (NDI) provided in the associated HARQ information was switched from the value in the previous transmission of this transmission block (Transfer Block - TB) this HARQ process; or

if an uplink resource grant was received on the PDCCH for the C-RNTI and the identified process's HARQ buffer is empty; or

if the uplink resource grant was received in a random access response; or

if the uplink resource grant is part of a configured resource grant packet and can be used for initial transmission in accordance with subclause 6.1.2.3 of TS 38.214 [7], and if no MAC PDU has been received for that packet:

if there is a MAC PDU in buffer Msg3 and an uplink resource grant was received in a random access response:

if the size of the uplink resource grant does not match the size of the MAC PDU in the Msg3 buffer:

direct the multiplexing and translation entity to include a MAC sub-PDU except for the MAC sub-PDU containing the truncated BSR MAC CE from the MAC PDU in the Msg3 buffer in subsequent uplink transmissions, if any;

receive the MAC PDU for transmission from the multiplexing and translation entity and store it in the Msg3 buffer;

if the size of the uplink resource grant is equal to the size of the MAC PDU in the Msg3 buffer:

receive MAC PDU for transmission from Msg3 buffer.

if there is no MAC PDU in buffer Msg3 and an uplink resource grant was received in a random access response:

receive the MAC PDU for transmission from the multiplexing and translation entity, if any;

Alternatively or additionally, through the above embodiments, for each uplink resource grant, the HARQ entity of the terminal device 120 must identify the HARQ process associated with that resource grant. For each identified HARQ process:

if the received resource grant was not addressed to the temporary C-RNTI on the PDCCH and the New Data Indicator (NDI) provided in the associated HARQ information was switched from the value in the previous transmission of this transmission block (Transfer Block - TB) this HARQ process; or

if an uplink resource grant was received on the PDCCH for the C-RNTI and the identified process's HARQ buffer is empty; or

if the uplink resource grant was received in a random access response; or

if the uplink resource grant is part of a configured resource grant packet and can be used for initial transmission in accordance with subclause 6.1.2.3 of TS 38.214 [7], and if no MAC PDU has been received for that packet:

if there is a MAC PDU in buffer Msg3 and an uplink resource grant was received in a random access response scheduled PDCCH addressed to RA-RNTI or C-RNTI:

if the size of the uplink resource grant does not match the size of the MAC PDU in the Msg3 buffer, and

if with this random access response the random access procedure is successfully completed:

direct the multiplexing and translation entity to include a MAC sub-PDU excluding the MAC sub-PDU containing the truncated BSR MAC CE or C-RNTI MAC CE from the MAC PDU in the Msg3 buffer in subsequent uplink transmissions, if any;

receive the MAC PDU for transmission from the multiplexing and translation entity and store it in the Msg3 buffer;

if the size of the uplink resource grant is equal to the size of the MAC PDU in the Msg3 buffer:

receive MAC PDU for transmission from Msg3 buffer.

if there is no MAC PDU in buffer Msg3 and an uplink resource grant was received in a random access response:

receive the MAC PDU for transmission from the multiplexing and translation entity, if any;

Thus, the problem caused by the mismatch of the uplink resource grant indicated in the RAR by the MAC PDU in the Msg3 buffer can be solved by recovering the MAC CE for the MAC PDU according to the embodiments of the present invention.

In more detail, exemplary embodiments in accordance with the present disclosure will be described with reference to FIGS. 3-4.

In FIG. 3 is a flow diagram of an example method 300 for a random access procedure according to some exemplary embodiments of the present disclosure. Method 300 may be implemented in terminal device 120 as shown in FIG. 2. For purposes of discussion, method 300 will be described with reference to FIG. 2.

In step 310, the terminal device 120 transmits a random access request in a random access procedure to the network device.

In some exemplary embodiments, terminal device 120 may transmit one of the following: a contention-free random access preamble and a contention-based random access preamble.

In step 320, if the terminal device 120 receives an uplink resource grant for the terminal device 120 in a random access procedure from the network device 110, then the terminal device 120 determines whether the first size of the first data block indicated by the uplink resource grant matches the second the size of the second block of data stored in the buffer of the terminal device.

In some exemplary embodiments, the second data block may comprise at least one of the following MAC CEs: C-RNTI, BSR, and PHR.

In some exemplary embodiments, the BSR may comprise at least one of the following: truncated BSR, padding BSR, regular BSR; and periodic BSR.

At step 330, if the terminal device 120 determines that the first size does not match the second size, if the terminal device 120 determines the first part of the second data block for subsequent transmissions at least based on the first size.

In some exemplary embodiments, terminal device 120 may determine if the second dimension matches the first dimension. If the second size does not match the first size, the terminal device may perform at least one of the following: discarding a truncated buffer status report (BSR) from the second data block; discarding a padding buffer status report (BSR) from the second data block; discarding the regular BSRH3 of the second data block; discarding the periodic BSR from the second data block; and discarding the PHR power headroom report from the second data block; and adjusting the size of the truncated BSR.

In some exemplary embodiments, terminal device 120 may determine if the second dimension matches the first dimension. If the second size does not match the first size, the terminal device 120 can determine whether the random access procedure is successfully completed by receiving an uplink resource grant. If the terminal device 120 determines that the random access procedure is considered to be successfully completed, the terminal device 120 may discard the C-RNTI MAC medium access control (MAC CE) control element from the second data block.

In some exemplary embodiments, terminal device 120 may determine if the second dimension matches the first dimension. If the second size does not match the first size, then terminal device 120 may determine whether a contention-free random access preamble was transmitted. If the terminal device 120 determines that the contention-free random access preamble has been transmitted, the terminal device may discard the C-RNTI MAC media access control (MAC CE) control element from the second data block.

In some exemplary embodiments, determining by terminal device 120 whether the random access procedure has been successfully completed may include determining that the uplink resource grant is addressed to at least one of the following: C-RNTI and Temporary Random Access Radio Network Identifier RA-RNTI.

In some exemplary embodiments, subsequent transmissions may comprise at least one of a transmission associated with an uplink resource grant and a transmission associated with an additional uplink resource grant that is different from the uplink resource grant.

In some exemplary embodiments, terminal device 120 may further transmit at least a portion of the first portion of the second data block in the first data block to the network device.

In FIG. 4 is a flow diagram of an example method 400 for a random access procedure according to some exemplary embodiments of the present disclosure. Method 300 may be implemented in network device 110 as shown in FIG. 2. For purposes of discussion, method 400 will be described with reference to FIG. 2.

In step 410, the network device 110 receives a random access request from the terminal device 120 in a random access procedure.

In some exemplary embodiments, network device 110 may receive one of the following: a contention-free random access preamble; and a contention based random access preamble.

In step 420, network device 110 transmits to terminal device 120 an uplink resource grant of the terminal device, wherein the uplink resource grant indicates the first size of the first data block such that the terminal device determines whether the first size of the first data block matches the second size of the second block. data stored in the buffer of the terminal device.

In some exemplary embodiments, the second data block may comprise at least one of the following MAC CEs: C-RNTI, BSR, and PHR.

In some exemplary embodiments, the BSR may comprise at least one of the following: a truncated BSR and a padding BHR, a regular BSR; and periodic BSR.

In some exemplary embodiments, the network device 110 may further receive from the terminal device at least a portion of the first portion of the second data block in the first data block.

In some exemplary embodiments, an apparatus capable of performing method 300 (eg, terminal device 120) may include means for performing the corresponding steps of method 300. Such means may be implemented in any suitable form. For example, the tool may be implemented as a circuit or a software module.

In some exemplary embodiments, the apparatus comprises: means for transmitting, at the terminal device, a random access request in a random access procedure to a network device; means for determining, in response to receiving, in the random access procedure, from the network device an uplink resource grant to the terminal device, whether the first size of the first data block indicated by the uplink resource grant corresponds to the second size of the second data block , stored in the buffer of the terminal device; means for determining, in response to determining that the first size does not match the second size, the first part of the second data block for subsequent transmissions.

In some exemplary embodiments, means for transmitting a random access request may comprise means for transmitting one of the following: a contention-free random access preamble; and contention-based random access preambles.

In some exemplary embodiments, the second data block may comprise at least one of the following MAC CEs: C-RNTI, BSR, and PHR.

In some exemplary embodiments, the BSR may comprise at least one of the following: a truncated BSR and a padding BHR, a regular BSR; and periodic BSR.

In some exemplary embodiments, the means for determining the first part may comprise means for performing, in response to determining that the second size does not match the first size, at least one of the following: discarding a truncated buffer status report (BSR) from the second data block ; discarding a padding buffer status report (BSR) from the second data block; discarding the regular BSR from the second data block; discarding the periodic BSR from the second data block; and discarding the PHR power headroom report from the second data block; and adjusting the size of the truncated BSR.

In some exemplary embodiments, means for determining the first part may comprise means for determining, in response to determining that the second size does not match the first size, whether the random access procedure is successfully completed by receiving an uplink resource grant, and means for discarding , in response to determining that the random access procedure is considered to be successfully completed, the control element for control access to the medium MAC (CE MAC) C-RNTI from the second data block.

In some exemplary embodiments, the means for determining whether the random access procedure has been successfully completed may comprise means for determining that the uplink resource grant is addressed to at least one of the following: a C-RNTI and a random access radio network temporary identifier. RA-RNTI access.

In some exemplary embodiments, subsequent transmissions may comprise at least one of a transmission associated with an uplink resource grant and a transmission associated with an additional uplink resource grant that is different from the uplink resource grant.

In some exemplary embodiments, the apparatus may further comprise means for transmitting to the network device at least a portion of the first portion of the second data block in the first data block.

In some exemplary embodiments, an apparatus capable of performing method 400 (eg, network device 110) may include means for performing the corresponding steps of method 400. Such means may be implemented in any suitable form. For example, the tool may be implemented as a circuit or a software module.

In some exemplary embodiments, the apparatus comprises: means for receiving from a terminal device a random access request in a random access procedure; means for transmitting to the terminal device, in response to receiving the random access request, an uplink resource grant of the terminal device, wherein the uplink resource grant indicates the first size of the first data block such that the terminal device determines whether the first size matches the first data block the second size of the second block of data stored in the buffer of the terminal device.

In some exemplary embodiments, means for receiving a random access request may comprise means for receiving one of the following: a contention-free random access preamble; and contention-based random access preambles.

In some exemplary embodiments, the second data block may comprise at least one of the following MAC CEs: C-RNTI, BSR, and PHR.

In some exemplary embodiments, the BSR may comprise at least one of the following: a truncated BSR and a padding BHR, a regular BSR; and periodic BSR.

In some exemplary embodiments, the apparatus further comprises: means for receiving from the terminal device at least a portion of the first portion of the second data block in the first data block.

In FIG. 5 is a simplified diagram of an apparatus 500 suitable for implementing an exemplary embodiment of the present invention. Device 500 can be viewed as a further example of an implementation of terminal device 120 as shown in FIG. 1. Accordingly, device 500 may be implemented on or as at least a portion of terminal device 110.

As shown, device 500 includes processor 510, memory 520 coupled to processor 510, suitable transmitter (TX) and receiver (RX) 540 coupled to processor 510, and a communications interface coupled to TX/RX 540. Memory 510 stores at least a portion of program 530. TX/RX 540 is designed for bi-directional communication. The TX/RX 540 has at least one antenna for communication, although in practice the access point referred to in this application may have multiple antennas. The communication interface may represent any interface that is necessary for communication with other network elements, such as an X2 interface for bidirectional communication between eNBs, an S1 interface for communication between a Mobility Management Entity (MME)/Serving Gateway (S-GW). ) and eNB, Un interface for communication between eNB and relay node (relay node - RN) or Uu interface for communication between eNB and terminal device.

Program 530 is contemplated to contain program instructions that, when executed by an appropriate processor 510, enable device 500 to operate in accordance with exemplary embodiments of the present invention as described herein with reference to FIG. 2-4. The exemplary embodiments herein may be implemented by computer software executed by the processor 510 of the device 500 using hardware or a combination of software and hardware. Processor 510 may be configured to implement various exemplary embodiments of the present disclosure. In addition, the combination of processor 510 and memory 510 may form processing means 550 configured to implement various exemplary embodiments of the present disclosure.

The storage device 510 may be of any type suitable for a local area network and may be implemented using any suitable data storage technology, for example, computer-readable medium for long-term storage of information, semiconductor memories, magnetic storage devices and systems, optical storage devices. and systems, non-removable and removable storage devices, which are listed as non-limiting examples. Although only one storage device 510 is shown in device 500, there may be several physically distinct storage modules in device 500. Processor 510 may be of any type suitable for a local area network and may include one or more general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), and processors based on a multi-core processor architecture, in as non-limiting examples. The device 500 may have multiple processors, such as ASICs, operating in accordance with a clock signal that provides synchronization with the main processor.

In general, various embodiments of the present disclosure may be implemented in hardware or custom circuitry, software, logic, or any combination thereof. Some aspects of the invention may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present invention are illustrated and described as block diagrams, flow charts, or using any other graphical representations, it should be understood that the units, apparatus, systems, techniques, or methods described herein may be implemented, in as non-limiting examples, in hardware, software, firmware, dedicated circuitry or logic, general purpose hardware or controller, or other computing devices, or combinations thereof.

The present disclosure also provides at least one computer program product tangibly stored on a computer-readable medium for long-term storage of information. The computer program product contains computer-executable instructions, such as those included in program modules executing on a device on a target real or virtual processor, for performing a process or method as described above with reference to any of FIGS. 2-5. Typically, program modules contain subroutines, programs, libraries, objects, classes, components, data structures, and the like that perform specific tasks or implement specific abstract data types. The functionality of the software modules may be combined or shared between software modules, as desired in various embodiments. The machine-executable instructions for the program modules may be executed on a local or distributed device. In a distributed device, program modules can be located on both local and remote storage media.

Program code for performing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program codes executed by the processor or controller dictate the functions/operations indicated in the flow charts and/or flowcharts, which are to be implemented. The program code may be executed entirely on the machine, partially on the machine as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

In the context of the present disclosure, computer program codes or associated data may be carried on any suitable medium to enable a device, apparatus, or processor to perform various processes and operations as described above. Examples of media include signal, computer readable media.

The computer-readable medium may be a computer-readable signal medium or a computer-readable medium for storing information. The computer-readable medium may comprise, among other things, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a computer-readable medium for storing information may include an electrical connection having one or more wires, a portable computer floppy disk, a hard drive, random access memory (RAM), read-only memory - ROM), erasable programmable readonly memory (EPROM, or flash memory), optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device , a magnetic storage device, or any suitable combination of the above.

In addition, although the operations are illustrated in a particular order, this should not be understood as a requirement that such operations be performed in the particular order or sequence indicated, or that all of the illustrated operations be performed to achieve the desired results. Under certain circumstances, multitasking and parallel processing may be preferable. Likewise, although some specific implementation details are contained in the above discussions, they should not be considered as limitations on the scope of the present disclosure, but as descriptions of features for particular embodiments. Certain features described in the context of individual embodiments may also be implemented in combination in one embodiment. Conversely, various features described in the context of one embodiment may also be implemented in multiple embodiments individually or in any suitable combination.

While the present disclosure has been described in specific language of structural features and/or operation of methods, it is understood that the invention is defined in the claims and is not limited to the features or operation described above. The specific features and actions described above are disclosed as examples of the implementation of the claims.

Claims (66)

1. A device for performing a random access procedure, comprising: means for transmitting, at the terminal device, to the network device a random access request in a random access procedure; means for determining, in response to receiving from the network device, during a random access procedure, an uplink resource grant to the terminal device, whether the size indicated by the uplink resource grant matches the size of the media access control PDU stored in the buffer of the terminal device; means for including the media access control PDU subblock of the media access control PDU in subsequent uplink transmission after determining that the size indicated by the uplink resource grant does not match the size of the access control PDU to the transmission medium stored in the buffer. 2. The device according to claim. 1, characterized in that the device is instructed to transmit a random access request by transmitting one of the following: contention-free random access preambles; and contention-based random access preambles. 3. The device according to claim 1 or 2, characterized in that the media access control protocol data block contains at least one of the following control elements (CE) for media access control (MAC): Cellular Radio Network Temporary Identifier (C-RNTI); buffer status report (BSR); and power headroom report (PHR). 4. The device according to claim 3, characterized in that the BSR contains at least one of the following: truncated BSR; filling BSR; regular BSR; and periodic BSR. 5. The device according to any one of paragraphs. 1-4, characterized in that the inclusion of the PDU subunit of the media access control PDU of the PDU of the media access control PDU in the subsequent uplink transmission comprises at least one of the following: discarding the truncated BSR from the media access control PDU; discarding the padding BSR from the media access control PDU; discard regular BSR from media access control PDU discarding the periodic BSR from the media access control PDU; discarding the PHR from the media access control PDU; and adjusting the size of the truncated BSR. 6. The device according to any one of paragraphs. 1-5, characterized in that the inclusion of a sub-block of protocol data access control to the medium transmission of the protocol data block of control access to the medium in the subsequent transmission on the uplink contains: determining whether the random access procedure is successfully completed by receiving an uplink resource grant; and discarding or disregarding, in response to determining that the random access procedure is successfully completed, the control element (CE) for the C-RNTI medium access control (MAC) from the media access control PDU in the specified subsequent uplink transmission. 7. The device according to claim 6, characterized in that the device is instructed to determine whether the random access procedure has been successfully completed by: determining that the uplink resource grant is addressed to at least one of the following: Cellular Radio Network Temporary Identifier (C-RNTI); and random access radio network temporary identifier (RA-RNTI). 8. The device according to any one of paragraphs. 1-7, characterized in that said subsequent uplink transmission comprises at least one of the following: a transmission associated with granting an uplink resource; and a transmission associated with an additional uplink resource grant, wherein the additional uplink resource grant is different from the uplink resource grant. 9. The device according to any one of paragraphs. 1-8, characterized in that the device further comprises: means for transmitting to the network device at least a portion of the media access control protocol data subunit of the media access control protocol data unit. 10. A device for performing a random access procedure, comprising: means for receiving, from the terminal device, a random access request in a random access procedure; means for transmitting to the terminal device, in response to receiving the random access request, an uplink resource grant of the terminal device, the uplink resource grant indicating a size such that the terminal device determines whether the size indicated in the uplink resource grant matches , the size of the media access control protocol data block stored in the buffer of the terminal device. 11. The device of claim. 10, characterized in that the device is instructed to receive a random access request by receiving one of the following: contention-free random access preambles; and contention-based random access preambles. 12. The device according to claim 10 or 11, characterized in that the media access control protocol data unit contains at least one of the following control elements (CE) for media access control (MAC): Cellular Radio Network Temporary Identifier (C-RNTI); buffer status report (BSR); and power headroom report (PHR). 13. The device according to any one of paragraphs. 10-12, characterized in that the BSR contains at least one of the following: truncated BSR; filling BSR; regular BSR; and periodic BSR. 14. The device according to any one of paragraphs. 10-13, characterized in that the device further comprises: means for receiving from the terminal device at least a portion of the media access control protocol data subunit of the media access control protocol data unit. 15. A method for performing a random access procedure, including: transmitting, at the terminal device, to the network device a random access request in a random access procedure; determining, in response to receiving from the network device, during the random access procedure, the uplink resource grant to the terminal device, whether the size indicated by the uplink resource grant matches the size of the media access control PDU stored in the buffer terminal device; inclusion of the Media Access Control PDU sub-block of the Media Access Control PDU in subsequent uplink transmission, after determining that the size indicated by the uplink resource grant does not match the size of the Media Access Control PDU transfer stored in the buffer. 16. A method for performing a random access procedure implemented on a network device, including: receiving from the terminal device a random access request in a random access procedure; transmitting to the terminal device, in response to receiving the random access request, an uplink resource grant of the terminal device, wherein the uplink resource grant indicates a size such that the terminal device determines whether the size indicated by the uplink resource grant matches the size a media access control protocol data block stored in a buffer of the terminal device. 17. A computer-readable medium containing program instructions for instructing the specified device to perform at least: transmitting, at the terminal device, to the network device a random access request in a random access procedure; determining, in response to receiving from the network device, during the random access procedure, the uplink resource grant to the terminal device, whether the size indicated by the uplink resource grant matches the size of the media access control PDU stored in the buffer terminal device; inclusion of the Media Access Control PDU sub-block of the Media Access Control PDU in subsequent uplink transmission, after determining that the size indicated by the uplink resource grant does not match the size of the Media Access Control PDU transfer stored in the buffer. 18. A computer-readable medium containing program instructions for instructing the specified device to perform at least: receiving from the terminal device a random access request in a random access procedure; and transmitting to the terminal device, in response to receiving the random access request, an uplink resource grant of the terminal device, wherein the uplink resource grant indicates a size such that the terminal device determines whether the size indicated by the uplink resource grant matches the size a media access control protocol data block stored in a buffer of the terminal device.

Images