WO2018127240A1 - 一种随机接入响应方法和装置 - Google Patents

一种随机接入响应方法和装置 Download PDF

Info

Publication number
WO2018127240A1
WO2018127240A1 PCT/CN2018/076489 CN2018076489W WO2018127240A1 WO 2018127240 A1 WO2018127240 A1 WO 2018127240A1 CN 2018076489 W CN2018076489 W CN 2018076489W WO 2018127240 A1 WO2018127240 A1 WO 2018127240A1
Authority
WO
WIPO (PCT)
Prior art keywords
random access
mac rar
mac
access request
identifier
Prior art date
Application number
PCT/CN2018/076489
Other languages
English (en)
French (fr)
Inventor
谌丽
赵亚利
许芳丽
Original Assignee
电信科学技术研究院
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 电信科学技术研究院 filed Critical 电信科学技术研究院
Priority to US16/476,050 priority Critical patent/US11102825B2/en
Publication of WO2018127240A1 publication Critical patent/WO2018127240A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/542—Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H04W74/0841—Random access procedures, e.g. with 4-step access with collision treatment
    • H04W74/0858—Random access procedures, e.g. with 4-step access with collision treatment collision detection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a random access response method and apparatus.
  • the random access of the LTE system is divided into two types: contention random access and non-contention random access.
  • the process is as follows.
  • the competitive random access process is shown in Figure 1. It is mainly divided into four-step random access, which can also be called 4-step RA:
  • the UE selects a random access preamble (random access preamble) and a PRACH (Physical Random Access Channel) resource and uses the PRACH resource to send the selected random access preamble code to the base station (random access) Preamble).
  • a random access preamble random access preamble
  • PRACH Physical Random Access Channel
  • Msg2 The base station receives the preamble code and sends a random access response.
  • the random access response consists of two parts: the MAC header and the MAC RAR.
  • the MAC header contains multiple subheaders. Each subheader format is as shown in FIG. 2, and its main content is RAPID (Random Access Preamble ID).
  • the MAC RAR includes a timing advance TAC (Time Advance Command), an uplink resource grant (UL Grant, uplink scheduling grant) for Msg3, and a temporary C-RNTI (Temporary C-RNTI) allocated by the network side.
  • TAC Time Advance Command
  • UL Grant uplink scheduling grant
  • C-RNTI Temporary C-RNTI
  • the PDCCH (Physical Downlink Control Channel) carrying the Msg2 scheduling information is scrambled by the RA-RNTI, and the RA-RNTI uniquely corresponds to the time-frequency resource for transmitting the Msg1 within the window length of the UE receiving Msg2.
  • the UE receives the Msg2, it determines that the Msg2 corresponds to the Msg1 sent by the RA-RNTI and the preamble ID.
  • the UE sends an uplink transmission on the UL grant specified by the Msg2.
  • the content of the Msg3 uplink transmission is different for different random access reasons. For example, for the initial access, the Msg3 transmits an RRC connection establishment request.
  • Msg4 The contention resolution message, the UE can judge whether the random access is successful according to Msg4. For the initial access UE, after the contention resolution is successful, the temporary C-RNTI is automatically converted into the UE's unique UE identity C-RNTI in the cell.
  • Non-competitive random access is shown in Figure 4. It is mainly divided into three steps:
  • the base station allocates a dedicated preamble code for non-contention random access and a PRACH resource used by the random access to the UE.
  • Msg1 The UE sends the designated dedicated preamble to the base station on the designated PRACH resource according to the indication of Msg0. After receiving the Msg1, the base station calculates the uplink timing advance TA according to Msg1.
  • the base station sends a random access response to the UE.
  • the random access response includes timing advance information and a subsequent uplink transmission resource allocation UL grant, and the timing advance is used for the timing relationship of the UE subsequent uplink transmission.
  • a two-step random access procedure (or 2-step RA) is performed on the basis of 4-step RA, and the process is as shown in FIG. 5 .
  • 2-step RA random access procedure
  • Step 1 Msg1+Msg3, which is equivalent to 4-step RA, contains the random access code part and the data part, and the two parts can be decoded independently.
  • the random access code part is used to send the preamble code, which is the random access code preamble of Msg1 in the 4-step RA;
  • the data part is similar to the Msg3 in the 4-step RA, and may include the UE identifier (according to different random access events) And the UE status, the specific UE identification content may be different), the buffer status report (BSR, Buffer Status Report or DV, Data Volume), PHR (Power Headroom Report, power headroom report), uplink data.
  • BSR Buffer Status Report or DV, Data Volume
  • PHR Power Headroom Report, power headroom report
  • Step 2 Msg2+Msg4 equivalent to 4-step RA. It is used to complete random access competition resolution and uplink data reception feedback.
  • a two-step random access 2-step RA is introduced in the 5G system, and the random access response message in the random access procedure in the related art is no longer applicable to the 2-step RA.
  • the embodiments of the present disclosure provide a random access response method and apparatus, and how to design a random access response in a new generation wireless communication system (NR system or 5G system) to meet the requirements of a new generation wireless communication system.
  • NR system or 5G system new generation wireless communication system
  • a random access response method including:
  • the UE sends a random access request, where the random access request carries information including the identifier of the UE;
  • the UE receives the random access response, and if the UE identifier carried in the random access response is consistent with the UE identifier in the random access request, the contention negotiation is completed; if the UE identifier and the random access request carried in the random access response are If the UE identifiers are inconsistent, the UE determines that the random access fails, and re-initiates the random access attempt; if the random access response does not carry the UE identifier, the UE falls back to the random access request without carrying the UE. a random access procedure for identifying information;
  • the random access response is adaptively generated by the network side according to the random access request.
  • the random access that carries the UE identifier in the random access request is also called a two-step random access, and the random access that does not carry the UE identifier in the random access request is also called a four-step random access.
  • the random access response is sent by using a MAC PDU, where the MAC PDU includes a MAC header and a MAC RAR, and the MAC header includes multiple MAC subheaders, and each MAC subheader includes a RAPID, corresponding to the random access request.
  • each MAC subheader corresponds to one MAC RAR, and the random access response MAC RAR carrying the UE identity and the random access response MAC RAR not carrying the UE identity may be multiplexed into one MAC PDU.
  • a MAC RAR of the same length is used, and the MAC RAR length is fixed to include a maximum UE identifier length.
  • the Temporary C-RNTI, or both is used.
  • the MAC RAR includes any one or more of the following:
  • T1 indicating a MAC RAR followed by four-step random access or a MAC RAR of two-step random access
  • T2 appears only in the two-step random access MAC RAR, and is used to indicate that it is a long UE ID or a short UE ID;
  • Timing Advance Command Upstream timing advance
  • Temporary C-RNTI converted to a C-RNTI allocated to the UE after the contention resolution is completed;
  • Contention Resolution Identity information corresponding to the UE identifier included in the random access request of the two-step random access
  • the MAC RAR includes all possible domains, each of which is a maximum length of the possible length, and the length of each domain is fixed. If the domain is not required in the random access response, The field is actually reserved, filling the value specified by the protocol or determining the value of the padding by the network side.
  • the sending, by the UE, a random access request includes:
  • the UE sends a random access request preamble code, and does not send information carrying the UE identifier
  • a random access response including:
  • the UE acquires the MAC RAR corresponding to the MAC sub-header. If the indication field in the MAC RAR is determined to determine that the MAC RAR does not carry the UE identifier, the subsequent domain in the MAC RAR is read, and the related operations are performed according to the indications of the domains, and the subsequent operations are completed. a random access procedure; if the indication field in the parsing MAC RAR determines that the MAC RAR carries the UE identity, determines that the random access fails, and subsequently initiates a new random access attempt.
  • the sending, by the UE, a random access request includes:
  • a random access request including a preamble code and information including a UE identifier
  • a random access response including:
  • the UE acquires the MAC RAR corresponding to the MAC sub-header. If the indication field T1 in the MAC RAR is determined to determine that the MAC RAR does not carry the UE identifier, it is determined that the network side only receives the preamble code and does not correctly receive the data part, and reads the MAC RAR. The subsequent domain in the process, falls back to the four-step random access, parses each domain in the MAC RAR according to the four-step random access procedure, and then completes the subsequent random access procedure according to the indication of each domain in the MAC RAR; or
  • the indication field T1 in the parsing MAC RAR determines that the MAC RAR carries the UE identity, and the indication field T2 determines that the UE identity is a long UE ID, if the UE sends a long UE ID, the UE determines whether the UE identity in the MAC RAR is Consistent with the long UE ID sent by the UE, if it is consistent, determining to complete the contention resolution, the UE receives the PDCCH scheduling command with the Temporary C-RNTI sent by the network side, and sends the uplink transmission according to the scheduling command; if not, the UE Determining that the random access fails, and subsequently re-initiating a random access attempt; or
  • the indication field T1 in the parsing MAC RAR determines that the MAC RAR carries the UE identity, and the indication field T2 determines that the UE identity is a long UE ID, if the UE sends a short UE ID, it is determined that the MAC RAR is not for itself, this time Random access fails, and subsequent random access attempts are re-initiated; or
  • the indication field T1 in the parsing MAC RAR determines that the MAC RAR carries the UE identity, and the indication field T2 determines that the UE identity is a short UE ID, if the UE sends a long UE ID, it is determined that the MAC RAR is not for itself, this time Random access fails, and subsequent random access attempts are re-initiated; or
  • the indication field T1 in the parsing MAC RAR determines that the MAC RAR carries the UE identity, and the indication field T2 determines that the UE identity is a short UE ID, if the UE sends the short UE ID, the UE determines whether the UE identity in the MAC RAR is Consistent with the short UE ID sent by the UE, if consistent, determining to complete the contention resolution, the UE parses the UL Grant in the MAC RAR, and sends a subsequent uplink transmission according to the resource indicated by the UL Grant in the MAC RAR; if not, the UE determines The random access fails, and the random access attempt is re-initiated.
  • the sending, by the UE, a random access request includes:
  • a random access request including a preamble code and information including a UE ID identifier
  • a random access response including:
  • the UE acquires the MAC RAR corresponding to the MAC sub-header. If the indication field T1 in the parsing MAC RAR determines that the MAC RAR does not carry the UE identifier, the UE determines that the network side only receives the preamble code and does not correctly receive the data part. The UE only parses the Timing Advance Command, the UL Grant, and the Temporary C-RNTI field in the MAC RAR, and rolls back to the four-step random access, and then the UE adjusts the uplink timing advance according to the indication of each domain in the MAC RAR, and obtains Temporary C-RNTI, which sends Msg3 according to the UL Grant and completes the subsequent random access procedure; or
  • Determining the indication field T1 in the MAC RAR determines that the MAC RAR carries the UE identity, and the indication field T2 determines that the UE identity is a long UE ID, parses all domains, and if the UE sends a long UE ID, the UE determines the MAC RAR. Whether the UE identifier is consistent with the long UE ID sent by the UE. If the UE is consistent, the UE determines to complete the contention resolution, and then the UE sends a subsequent uplink transmission according to the resource indicated by the UL Grant in the MAC RAR; if not, the UE determines the present The secondary random access fails, and the subsequent random access attempt is re-initiated; or
  • Determining the indication field T1 in the MAC RAR determines that the MAC RAR carries the UE identity, and the indication field T2 determines that the UE identity is a long UE ID, parses all domains, and if the UE sends a short UE ID, determines that the MAC RAR is not for its own The random access fails, and the random access attempt is re-initiated; or
  • the indication field T1 in the parsing MAC RAR determines that the MAC RAR carries the UE identity, and the indication domain T2 determines that the UE identity is a short UE ID, parses all domains, and if the UE sends a long UE ID, it is determined that the MAC RAR is not for itself.
  • the random access fails, and the random access attempt is re-initiated; or
  • the indication field T1 in the parsing MAC RAR determines that the MAC RAR carries the UE identity, and the indication field T2 determines that the UE identity is a short UE ID, parses all domains, and if the UE sends a short UE ID, the UE determines the UE in the MAC RAR. Whether the identifier is consistent with the short UE ID sent by the UE. If the UE is consistent, the UE determines to complete the contention resolution. Then, the UE sends the subsequent uplink transmission according to the resource indicated by the UL Grant in the MAC RAR. If the information is inconsistent, the random access fails. Initiate a random access attempt.
  • the MAC subheader includes a preamble ID and a length indication field L, where the length indication field L is used to indicate a length of the corresponding MAC RAR or a MAC RAR type.
  • the MAC RAR type includes any one or more of the following:
  • MAC RAR format 1 Applicable to the scenario where the UE initiates four-step competitive random access;
  • Four-step random access MAC RAR format 2 Applicable to the scenario where the UE initiates four-step non-contention random access;
  • Four-step random access MAC RAR format 3 Applicable to the scenario where the UE initiates four-step non-contention random access, and the network side determines that the UE only needs to perform synchronization and does not need to send uplink data.
  • Two-step random access MAC RAR format 1 The random access request carries the RRC connection establishment or the RRC connection reestablishment or the inactive UE ID on the CCCH channel.
  • the network side needs to allocate the C-RNTI to the UE, and the network side needs the UE to perform the uplink. Synchronous calibration
  • Two-step random access MAC RAR format 2 The random access request carries the RRC connection establishment or the RRC connection reestablishment or the inactive UE ID on the CCCH channel, and the network side needs to allocate the C-RNTI to the UE, and the network side does not need the UE to perform Uplink synchronization calibration;
  • Two-step random access MAC RAR format 3 The random access request carries the RRC connection establishment or the RRC connection reestablishment or the inactive UE ID on the CCCH channel, and the network side needs to allocate the C-RNTI to the UE, and the network side does not need the UE to perform Uplink synchronization calibration;
  • Two-step random access MAC RAR format 4 The random access request carries the inactive UE ID, and the network side only confirms the data in the random access request, and does not need the UE to enter the connected state;
  • Two-step random access MAC RAR format 5 The random access request carries the C-RNTI of the connected state UE, and the network side needs the UE to perform uplink synchronization calibration;
  • Two-step random access MAC RAR format 6 The random access request carries the C-RNTI of the connected state UE, and the network side does not need the UE to perform uplink synchronization calibration;
  • Two-step random access MAC RAR format 7 The random access request carries the C-RNTI of the connected state UE, and the network side confirms that the data content in the random access request is correctly received, and determines that the UE does not need subsequent uplink transmission, and the network side No UL Grant is assigned.
  • the sending, by the UE, a random access request includes:
  • the UE sends a random access request preamble code, and does not send information carrying the UE identifier
  • a random access response including:
  • the UE receives a random access response, determines a MAC sub-header corresponding to the transmitted preamble code according to the RAPID field in the MAC sub-header, and parses the L-domain in the MAC sub-header to determine a subsequent MAC RAR length or a MAC RAR type;
  • the UE determines that the random access response is not for itself, the random access fails, and the UE subsequently initiates a new random access attempt;
  • the UE acquires the MAC RAR, and the UE completes the required subsequent random access procedure according to the MAC RAR domain indication.
  • the sending, by the UE, a random access request includes:
  • a random access request including a preamble code and a UE identifier
  • a random access response including:
  • the UE receives a random access response, determines a MAC sub-head corresponding to the transmitted preamble code according to the RAPID field in the MAC sub-header, and parses the L-domain in the MAC sub-head to determine a subsequent MAC RAR type;
  • the UE determines that the network side does not correctly receive the data part in the random access request, falls back to the four-step random access procedure, and sends the Msg3 according to the MAC RAR indication, and Receiving the downlink transmission Msg4 to complete the contention resolution;
  • the following processing is performed according to different MAC RAR types indicated by the L domain:
  • the UE If the format type is two-step random access MAC RAR format 1, the UE carries a long UE ID in the random access request, and the UE identifier in the MAC RAR is consistent with the long UE ID in the random access request, If the contention is successful, the UE performs uplink synchronization timing calibration, sends uplink data, and applies C-RNTI according to the indication in the MAC RAR; if the UE sends the short UE ID or the UE in the MAC RAR in the random access request The identifier is inconsistent with the UE identifier in the random access request, and the random access is considered to be failed, and the random access attempt is subsequently re-initiated; or
  • the format type is two-step random access MAC RAR format 2
  • the UE carries a long UE ID in the random access request, and the UE identifier in the MAC RAR is consistent with the long UE ID in the random access request
  • the contention is successful, the UE sends the uplink data according to the indication in the MAC RAR, and applies the C-RNTI; if the UE sends the short UE ID in the random access request or the UE identifier and the random access request in the MAC RAR
  • the UE identifiers are inconsistent, and the random access fails, and the UE subsequently re-initiates a random access attempt; or
  • the format type is two-step random access MAC RAR format 3
  • the UE carries a long UE ID in the random access request, and the UE identifier in the MAC RAR is consistent with the long UE ID in the random access request
  • the contention resolution is successful, the UE applies the C-RNTI according to the indication in the MAC RAR; if the UE sends the short UE ID in the random access request or the UE in the MAC RAR and the UE in the random access request If the identifier is inconsistent, the random access fails, and the UE subsequently re-initiates a random access attempt; or
  • the competition is considered If the solution succeeds, according to the application C-RNTI in the MAC RAR, the PDCCH scheduling command carrying the C-RNTI is subsequently received, and the uplink transmission is sent according to the scheduling command; if the UE sends the short UE ID in the random access request or the The UE identifier in the MAC RAR is inconsistent with the UE identifier in the random access request, and the random access fails, and the UE subsequently re-initiates a random access attempt; or
  • the competition is considered If the solution is successful, perform uplink synchronization timing calibration and send uplink data according to the indication in the MAC RAR; if the UE sends a long UE ID in the random access request or the UE identifier in the MAC RAR is inconsistent with the UE identifier in the random access request If the random access fails, the UE subsequently re-initiates a random access attempt; or
  • the format type is a two-step random access MAC RAR format 6-, if the UE carries a short UE ID in the random access request, and the UE identifier in the MAC RAR is the same as the short UE ID in the random access request, it is considered that If the contention is successful, the uplink data is sent according to the indication in the MAC RAR; if the UE sends the long UE ID in the random access request or the UE identifier in the MAC RAR is inconsistent with the UE identifier in the random access request, the random access is considered Failure, the UE subsequently re-initiates a random access attempt; or
  • the format type is two-step random access MAC RAR format 7
  • the contention is successful, the PDCCH scheduling command carrying the C-RNTI of the UE is subsequently monitored, and if the PDCCH scheduling command for scheduling the uplink transmission is received, the uplink transmission is sent according to the scheduling command; if the UE sends the long UE ID in the random access request Or the UE identifier in the MAC RAR is inconsistent with the UE identifier in the random access request, and the random access fails, and the UE subsequently re-initiates the random access attempt.
  • a random access response method including:
  • the network side receives the random access request sent by the terminal UE, and the random access request carries the information including the UE identifier;
  • the network side adaptively generates a random access response according to the random access request, and sends the random access response to the UE. If the random access request carries the information including the UE identifier, according to the two-step random access procedure, The UE identifier is included in the random access response. If the random access request does not carry the information including the UE identifier, the random access response is generated according to the four-step random access.
  • the random access response is sent by using a MAC PDU, where the MAC PDU includes a MAC header and a medium access control layer random access response MAC RAR, and the MAC header includes multiple MAC sub-headers, and each MAC sub-header Include a RAPID corresponding to the preamble code in the random access request, each MAC sub-header corresponding to one MAC RAR, and the random access response MAC RAR carrying the UE identifier and the random access response MAC RAR not carrying the UE identifier may be reused. Go to a MAC PDU.
  • a MAC RAR of the same length is used, and the MAC RAR length is fixed to include a maximum UE ID length.
  • the Temporary C-RNTI, or both is used.
  • the MAC RAR includes any one or more of the following:
  • T1 indicating a MAC RAR followed by four-step random access or a MAC RAR of two-step random access
  • T2 appears only in the two-step random access MAC RAR, and is used to indicate that it is a long UE ID or a short UE ID;
  • Timing Advance Command Upstream timing advance
  • Temporary C-RNTI converted to a C-RNTI allocated to the UE after the contention resolution is completed;
  • Contention Resolution Identity information corresponding to the UE identifier included in the two-step random access request
  • the MAC RAR includes all possible domains, each of which is a maximum length of the possible length, and the length of each domain is fixed. If the domain is not required in the random access response, The field is actually reserved, filling the value specified by the protocol or determining the value of the padding by the network side.
  • the network side receives the random access request sent by the UE, including:
  • the network side adaptively generates a random access response according to the random access request, including:
  • the network side sends a random access response, where the random access response includes an uplink timing advance, an uplink transmission resource, and a Temporary C-RNTI configured according to the preamble code.
  • the network side receives the random access request sent by the UE, including:
  • the network side adaptively generates a random access response according to the random access request, including:
  • the network side generates a corresponding MAC RAR according to the received random access request and sends the corresponding MAC RAR to the UE.
  • the network side sends a PDCCH scheduling command that carries the Temporary C-RNTI, The UE allocates subsequent uplink transmission resources.
  • the MAC subheader includes a preamble ID and a length indication field L, where the length indication field is used to indicate the length or type of the corresponding MAC RAR.
  • the MAC RAR type includes any one or more of the following:
  • MAC RAR format 1 Applicable to the scenario where the UE initiates four-step competitive random access;
  • Four-step random access MAC RAR format 2 Applicable to the scenario where the UE initiates four-step non-contention random access;
  • Four-step random access MAC RAR format 3 Applicable to the scenario where the UE initiates four-step non-contention random access, and the network side determines that the UE only needs to perform synchronization and does not need to send uplink data.
  • Two-step random access MAC RAR format 1 The random access request carries the RRC connection establishment or the RRC connection reestablishment or the inactive UE ID on the CCCH channel.
  • the network side needs to allocate the C-RNTI to the UE, and the network side needs the UE to perform the uplink. Synchronous calibration
  • Two-step random access MAC RAR format 2 The random access request carries the RRC connection establishment or the RRC connection reestablishment or the inactive UE ID on the CCCH channel, and the network side needs to allocate the C-RNTI to the UE, and the network side does not need the UE to perform Uplink synchronization calibration;
  • Two-step random access MAC RAR format 3 The random access request carries the RRC connection establishment or the RRC connection reestablishment or the inactive UE ID on the CCCH channel, and the network side needs to allocate the C-RNTI to the UE, and the network side does not need the UE to perform Uplink synchronization calibration;
  • Two-step random access MAC RAR format 4 The random access request carries the inactive UE ID, and the network side only confirms the data in the random access request, and does not need the UE to enter the connected state;
  • Two-step random access MAC RAR format 5 The random access request carries the C-RNTI of the connected state UE, and the network side needs the UE to perform uplink synchronization calibration;
  • Two-step random access MAC RAR format 6 The random access request carries the C-RNTI of the connected state UE, and the network side does not need the UE to perform uplink synchronization calibration;
  • Two-step random access MAC RAR format 7 The random access request carries the C-RNTI of the connected state UE, and the network side confirms that the data content in the random access request is correctly received, and determines that the UE does not need subsequent uplink transmission, and the network side No UL Grant is assigned.
  • a terminal including:
  • a sending module configured to send a random access request, where the random access request carries information including a UE identifier
  • a first processing module configured to receive a random access response, if the UE identifier carried in the random access response is consistent with the UE identifier in the random access request, complete the contention resolution; if the UE identifier and the random identifier carried in the random access response If the UE identifiers in the access request are inconsistent, the UE determines that the random access fails, and re-initiates the random access attempt; if the random access response does not carry the UE identifier, the UE falls back to the random access request. a random access procedure that does not carry UE identification information;
  • the random access response is adaptively generated by the network side according to the random access request.
  • the random access that carries the UE identifier in the random access request is also called a two-step random access, and the random access that does not carry the UE identifier in the random access request is also called a four-step random access.
  • the random access response is sent by using a MAC PDU, where the MAC PDU includes a MAC header and a MAC RAR, and the MAC header includes multiple MAC subheaders, and each MAC subheader includes a RAPID, corresponding to the random access request.
  • each MAC subheader corresponds to one MAC RAR, and the random access response MAC RAR carrying the UE identity and the random access response MAC RAR not carrying the UE identity may be multiplexed into one MAC PDU.
  • a MAC RAR of the same length is used, and the MAC RAR length is fixed to include a maximum UE identifier length.
  • the Temporary C-RNTI, or both is used.
  • the MAC RAR includes any one or more of the following:
  • T1 indicating a MAC RAR followed by four-step random access or a MAC RAR of two-step random access
  • T2 appears only in the two-step random access MAC RAR, and is used to indicate that it is a long UE ID or a short UE ID;
  • Timing Advance Command Upstream timing advance
  • Temporary C-RNTI converted to a C-RNTI allocated to the UE after the contention resolution is completed;
  • Contention Resolution Identity information corresponding to the UE identifier included in the random access request of the two-step random access
  • the MAC RAR includes all possible domains, each of which is a maximum length of the possible length, and the length of each domain is fixed. If the domain is not required in the random access response, The field is actually reserved, filling the value specified by the protocol or determining the value of the padding by the network side.
  • the sending module is further configured to: send a random access request preamble code, and not send information that carries the UE identifier;
  • the first processing module is further configured to: receive a random access response, determine a MAC sub-head corresponding to the transmitted preamble code according to the RAPID field in the MAC sub-header; and obtain, by the UE, a MAC RAR corresponding to the MAC sub-header, if parsing
  • the indication field in the MAC RAR determines that the MAC RAR does not carry the UE identifier, reads the subsequent domain in the MAC RAR, performs related operations according to the indication of each domain, and completes the subsequent random access procedure; if the indication domain in the MAC RAR is parsed, the The MAC RAR carries the UE identifier, determines that the random access fails, and subsequently initiates a new random access attempt.
  • the sending module is further configured to: send a random access request, including a preamble code and information including a UE identifier;
  • the first processing module is further configured to: receive a random access response, and determine, according to the RAPID field in the MAC sub-head, a MAC sub-head corresponding to the transmitted preamble code;
  • the MAC RAR corresponding to the MAC sub-header if the indication field T1 in the parsing MAC RAR determines that the MACRAR does not carry the UE identifier, determining that the network side only receives the preamble code and does not correctly receive the data part, and reads the subsequent domain in the MAC RAR. Retiring to the four-step random access, parsing the domains in the MAC RAR according to the four-step random access procedure, and then completing the subsequent random access procedure according to the indications of the domains in the MAC RAR; or
  • the indication field T1 in the parsing MAC RAR determines that the MAC RAR carries the UE identity, and the indication field T2 determines that the UE identity is a long UE ID, if the UE sends a long UE ID, it is determined whether the UE identity in the MAC RAR is sent with the UE.
  • the long UE IDs are consistent. If they are consistent, the QoS scheduling command with the Temporary C-RNTI sent by the network side is received, and the uplink transmission is sent according to the scheduling command. If not, the UE determines the random access. Failure, subsequent re-initiation of random access attempts; or
  • the indication field T1 in the parsing MAC RAR determines that the MAC RAR carries the UE identity, and the indication field T2 determines that the UE identity is a long UE ID, if the UE sends a short UE ID, it is determined that the MAC RAR is not for itself, this time Random access fails, and subsequent random access attempts are re-initiated; or
  • the indication field T1 in the parsing MAC RAR determines that the MAC RAR carries the UE identity, and the indication field T2 determines that the UE identity is a short UE ID, if the UE sends a long UE ID, it is determined that the MAC RAR is not for itself, this time Random access fails, and subsequent random access attempts are re-initiated; or
  • the indication field T1 in the parsing MAC RAR determines that the MAC RAR carries the UE identity, and the indication field T2 determines that the UE identity is a short UE ID, if the UE sends the short UE ID, the UE determines whether the UE identity in the MAC RAR is Consistent with the short UE ID sent by the UE, if consistent, determining to complete the contention resolution, parsing the UL Grant in the MAC RAR, and transmitting the subsequent uplink transmission according to the resource indicated by the UL Grant in the MAC RAR; if not, the UE determines the current random The access fails, and the random access attempt is re-initiated.
  • the sending module is further configured to: send a random access request, including a preamble code and information including a UE ID identifier;
  • the first processing module is further configured to: receive a random access response, and determine, according to the RAPID field in the MAC sub-head, a MAC sub-head corresponding to the preamble code sent by the RAPID field;
  • the MAC RAR corresponding to the MAC sub-header, if the indication field T1 in the parsing MAC RAR determines that the MAC RAR does not carry the UE identifier, determining that the network side only receives the preamble code and does not correctly receive the data part, and only parses the Timing in the MAC RAR.
  • the Advance Command, the UL Grant, and the Temporary C-RNTI domain are rolled back to the four-step random access, and then the UE adjusts the uplink timing advance according to the indication of each domain in the MAC RAR, acquires the Temporary C-RNTI, and sends according to the UL Grant. Msg3, and complete the subsequent random access process; or
  • Determining the indication field T1 in the MAC RAR determines that the MAC RAR carries the UE identity, and the indication field T2 determines that the UE identity is a long UE ID, parses all domains, and if the UE sends a long UE ID, the UE determines the MAC RAR. Whether the UE identifier is consistent with the long UE ID sent by the UE. If the UE is consistent, it is determined that the contention resolution is complete, and then the subsequent uplink transmission is sent according to the resource indicated by the UL Grant in the MAC RAR; if not, the UE determines that the random access fails. Subsequent re-initiation of random access attempts; or
  • Determining the indication field T1 in the MAC RAR determines that the MAC RAR carries the UE identity, and the indication field T2 determines that the UE identity is a long UE ID, parses all domains, and if the UE sends a short UE ID, determines that the MAC RAR is not for its own The random access fails, and the random access attempt is re-initiated; or
  • the indication field T1 in the parsing MAC RAR determines that the MAC RAR carries the UE identity, and the indication domain T2 determines that the UE identity is a short UE ID, parses all domains, and if the UE sends a long UE ID, it is determined that the MAC RAR is not for itself.
  • the random access fails, and the random access attempt is re-initiated; or
  • the indication field T1 in the parsing MAC RAR determines that the MAC RAR carries the UE identifier
  • the indication field T2 determines that the UE identifier is a short UE ID
  • parses all domains and if the UE sends a short UE ID, determines the UE identifier in the MAC RAR. Whether it is consistent with the short UE ID sent by the UE, if it is consistent, it is determined that the contention resolution is completed, and then the subsequent uplink transmission is sent according to the resource indicated by the UL Grant in the MAC RAR; if not, the random access failure is determined, and the random reconnection is subsequently initiated. Try it.
  • the MAC subheader includes a preamble ID and a length indication field L, where the length indication field L is used to indicate a length of the corresponding MAC RAR or a MAC RAR type.
  • the MAC RAR type includes any one or more of the following:
  • MAC RAR format 1 Applicable to the scenario where the UE initiates four-step competitive random access;
  • Four-step random access MAC RAR format 2 Applicable to the scenario where the UE initiates four-step non-contention random access;
  • Four-step random access MAC RAR format 3 Applicable to the scenario where the UE initiates four-step non-contention random access, and the network side determines that the UE only needs to perform synchronization and does not need to send uplink data.
  • Two-step random access MAC RAR format 1 The random access request carries the RRC connection establishment or the RRC connection reestablishment or the inactive UE ID on the CCCH channel.
  • the network side needs to allocate the C-RNTI to the UE, and the network side needs the UE to perform the uplink. Synchronous calibration
  • Two-step random access MAC RAR format 2 The random access request carries the RRC connection establishment or the RRC connection reestablishment or the inactive UE ID on the CCCH channel, and the network side needs to allocate the C-RNTI to the UE, and the network side does not need the UE to perform Uplink synchronization calibration;
  • Two-step random access MAC RAR format 3 The random access request carries the RRC connection establishment or the RRC connection reestablishment or the inactive UE ID on the CCCH channel, and the network side needs to allocate the C-RNTI to the UE, and the network side does not need the UE to perform Uplink synchronization calibration;
  • Two-step random access MAC RAR format 4 The random access request carries the inactive UE ID, and the network side only confirms the data in the random access request, and does not need the UE to enter the connected state;
  • Two-step random access MAC RAR format 5 The random access request carries the C-RNTI of the connected state UE, and the network side needs the UE to perform uplink synchronization calibration;
  • Two-step random access MAC RAR format 6 The random access request carries the C-RNTI of the connected state UE, and the network side does not need the UE to perform uplink synchronization calibration;
  • Two-step random access MAC RAR format 7 The random access request carries the C-RNTI of the connected state UE, and the network side confirms that the data content in the random access request is correctly received, and determines that the UE does not need subsequent uplink transmission, and the network side No UL Grant is assigned.
  • the sending module is further configured to: send a random access request preamble code, and not send information that carries the UE identifier;
  • the first processing module is further configured to: receive a random access response, determine a MAC sub-head corresponding to the transmitted preamble code according to the RAPID field in the MAC sub-header, and parse the L-domain in the MAC sub-head to determine a subsequent MAC RAR length or MAC RAR type;
  • the L domain indicates the MAC RAR type of the two-step random access, it is determined that the random access response is not for itself, the random access fails, and a new random access attempt is subsequently initiated;
  • the MAC RAR is obtained, and the required subsequent random access procedure is completed according to the MAC RAR domain indication.
  • the sending module is further configured to: send a random access request, including a preamble code and a UE identifier;
  • the first processing module is further configured to: receive a random access response, determine a MAC sub-head corresponding to the transmitted preamble code according to the RAPID field in the MAC sub-header, and parse the L-domain in the MAC sub-head to determine a subsequent MAC RAR type;
  • the MAC RAR type is a four-step random access RAR, it is determined that the network side does not correctly receive the data part in the random access request, falls back to the four-step random access procedure, sends the Msg3 according to the MAC RAR indication, and receives the downlink transmission.
  • Msg4 complete the competition resolution
  • the following processing is performed according to different MAC RAR types indicated by the L domain:
  • the format type is two-step random access MAC RAR format 1
  • the long-end UE ID is carried in the random access request, and the UE identifier in the MAC RAR is consistent with the long UE ID in the random access request, and the contention is considered to be resolved.
  • Successfully perform uplink synchronization timing calibration, transmit uplink data, and apply C-RNTI according to the indication in the MAC RAR; if the UE sends the short UE ID or the UE identifier and the random access request in the MAC RAR in the random access request The UE IDs in the packets are inconsistent, and the random access fails, and the random access attempt is re-initiated; or
  • the format type is two-step random access MAC RAR format 2
  • the random access request carries a long UE ID, and the UE identifier in the MAC RAR is consistent with the long UE ID in the random access request, the contention is considered to be resolved.
  • the UE sends the uplink data according to the indication in the MAC RAR, and applies the C-RNTI; if the UE sends the short UE ID in the random access request or the UE identifier in the MAC RAR is inconsistent with the UE identifier in the random access request, it is considered that Random access fails, and subsequent random access attempts are re-initiated; or
  • the format type is two-step random access MAC RAR format 3
  • the random access request carries a long UE ID, and the UE identifier in the MAC RAR is consistent with the long UE ID in the random access request, the contention is considered to be resolved.
  • the C-RNTI is applied according to the indication in the MAC RAR; if the UE sends the short UE ID in the random access request or the UE identifier in the MAC RAR is inconsistent with the UE identifier in the random access request, it is considered to be randomly connected. Incoming failure, subsequent re-initiation of random access attempts; or
  • the format type is two-step random access MAC RAR format 4
  • the random access request carries a long UE ID, and the UE identifier in the MAC RAR is consistent with the long UE ID in the random access request, the contention is considered to be resolved.
  • Successfully according to the application C-RNTI in the MAC RAR, subsequently receiving the PDCCH scheduling command carrying the C-RNTI, and transmitting the uplink transmission according to the scheduling command; if the UE sends the short UE ID or the MAC in the random access request
  • the UE identifier in the RAR is inconsistent with the UE identifier in the random access request, and the random access is considered to be failed, and the random access attempt is subsequently re-initiated; or
  • the format type is two-step random access MAC RAR format 5
  • the random access request carries a short UE ID
  • the UE identifier in the MAC RAR is the same as the short UE ID in the random access request
  • the contention is considered to be resolved.
  • Successfully performing uplink synchronization timing calibration and transmitting uplink data according to the indication in the MAC RAR; if the UE sends a long UE ID in the random access request or the UE identifier in the MAC RAR is inconsistent with the UE identifier in the random access request, Considering that the random access fails, and subsequently re-initiating a random access attempt; or
  • the format type is two-step random access MAC RAR format 6
  • the random access request carries a short UE ID, and the UE identifier in the MAC RAR is the same as the short UE ID in the random access request, the contention is considered to be resolved.
  • the UE sends the uplink data according to the indication in the MAC RAR if the UE sends the long UE ID in the random access request or the UE identifier in the MAC RAR is inconsistent with the UE identifier in the random access request, the random access fails. Subsequent re-initiation of random access attempts; or
  • the format type is two-step random access MAC RAR format 7
  • the random access request carries a short UE ID, and the UE identifier in the MAC RAR is consistent with the short UE ID in the random access request
  • the competition is considered If the solution succeeds, the PDCCH scheduling command carrying the C-RNTI of the UE is subsequently monitored, and if the PDCCH scheduling command for scheduling the uplink transmission is received, the uplink transmission is sent according to the scheduling command; if the UE sends the long UE ID in the random access request or The UE identifier in the MAC RAR is inconsistent with the UE identifier in the random access request, and the random access is considered to be failed, and the random access attempt is subsequently re-initiated.
  • a network side device including:
  • a receiving module configured to receive a random access request sent by the terminal UE, where the random access request carries information including the UE identifier;
  • a second processing module configured to: adaptively generate a random access response according to the random access request, and send the random access response to the UE, and if the random access request carries the information including the UE identifier, the random access is performed according to two steps. In the process, the UE ID information is included in the random access response. If the random access request does not carry the information including the UE identifier, the random access response is generated according to the four-step random access.
  • the random access response is sent by using a MAC PDU, where the MAC PDU includes a MAC header and a medium access control layer random access response MAC RAR, and the MAC header includes multiple MAC sub-headers, and each MAC sub-header Include a RAPID corresponding to the preamble code in the random access request, each MAC sub-header corresponding to one MAC RAR, and the random access response carrying the UE identifier and the random access response MAC RAR not carrying the UE identifier may be multiplexed into one In the MAC PDU.
  • the same length of the MAC RAR is used for the four-step random access and the two-step random access, and the two random access scenarios, and the MAC RAR length is fixed to include the maximum UE ID length and Temporary C-RNTI, or both.
  • the MAC RAR includes any one or more of the following:
  • T1 indicating a MAC RAR followed by four-step random access or a MAC RAR of two-step random access
  • T2 appears only in the two-step random access MAC RAR, and is used to indicate that it is a long UE ID or a short UE ID;
  • Timing Advance Command Upstream timing advance
  • Temporary C-RNTI converted to a C-RNTI allocated to the UE after the contention resolution is completed;
  • Contention Resolution Identity information corresponding to the UE identifier included in the two-step random access request
  • the MAC RAR includes all possible domains, each of which is a maximum length of the possible length, and the length of each domain is fixed. If the domain is not required in the random access response, The field is actually reserved, filling the value specified by the protocol or determining the value of the padding by the network side.
  • the receiving module is further configured to: receive a random access request, where the random access request includes a preamble code, and does not send information that carries the UE identifier;
  • the second processing module is further configured to: send a random access response, where the random access response includes an uplink timing advance, an uplink transmission resource, and a Temporary C-RNTI configured according to the preamble code.
  • the receiving module is further configured to: receive a random access request, where the random access request includes a preamble code or includes a preamble code and a data part;
  • the processing module is further configured to: generate a corresponding MAC RAR according to the received random access request, and send the corresponding MAC RAR to the UE.
  • the network side sends a PDCCH scheduling command that carries the Temporary C-RNTI, The UE allocates subsequent uplink transmission resources.
  • the MAC subheader includes a preamble ID and a length indication field L, where the length indication field is used to indicate the length or type of the corresponding MAC RAR.
  • the MAC RAR type includes any one or more of the following:
  • MAC RAR format 1 Applicable to the scenario where the UE initiates four-step competitive random access;
  • Four-step random access MAC RAR format 2 Applicable to the scenario where the UE initiates four-step non-contention random access;
  • Four-step random access MAC RAR format 3 Applicable to the scenario where the UE initiates four-step non-contention random access, and the network side determines that the UE only needs to perform synchronization and does not need to send uplink data.
  • Two-step random access MAC RAR format 1 The random access request carries the RRC connection establishment or the RRC connection reestablishment or the inactive UE ID on the CCCH channel.
  • the network side needs to allocate the C-RNTI to the UE, and the network side needs the UE to perform the uplink. Synchronous calibration
  • Two-step random access MAC RAR format 2 The random access request carries the RRC connection establishment or the RRC connection reestablishment or the inactive UE ID on the CCCH channel, and the network side needs to allocate the C-RNTI to the UE, and the network side does not need the UE to perform Uplink synchronization calibration;
  • Two-step random access MAC RAR format 3 The random access request carries the RRC connection establishment or the RRC connection reestablishment or the inactive UE ID on the CCCH channel, and the network side needs to allocate the C-RNTI to the UE, and the network side does not need the UE to perform Uplink synchronization calibration;
  • Two-step random access MAC RAR format 4 The random access request carries the inactive UE ID, and the network side only confirms the data in the random access request, and does not need the UE to enter the connected state;
  • Two-step random access MAC RAR format 5 The random access request carries the C-RNTI of the connected state UE, and the network side needs the UE to perform uplink synchronization calibration;
  • Two-step random access MAC RAR format 6 The random access request carries the C-RNTI of the connected state UE, and the network side does not need the UE to perform uplink synchronization calibration;
  • Two-step random access MAC RAR format 7 The random access request carries the C-RNTI of the connected state UE, and the network side confirms that the data content in the random access request is correctly received, and determines that the UE does not need subsequent uplink transmission, and the network side No UL Grant is assigned.
  • a terminal including a processor, a transceiver, and a memory;
  • the processor is configured to read a program in the memory and perform the following process:
  • the random access response is generated by the network side according to the random access request
  • the transceiver is configured to receive and transmit data
  • the memory is used to store data used by the processor to perform operations.
  • a network side device including a processor, a transceiver, and a memory;
  • the processor is configured to read a program in the memory and perform the following process:
  • the transceiver is configured to receive and transmit data
  • the memory is used to store data used by the processor to perform operations.
  • One technical solution in the foregoing technical solution has the following advantages or benefits: if the terminal (UE) identifier carried in the random access response is consistent with the UE identifier in the random access request, the UE completes the contention resolution; if the random access response is If the carried UE identifier is inconsistent with the UE identifier in the random access request, the UE determines that the random access fails and re-initiates the random access attempt; if the random access response does not carry the UE identifier, the UE falls back to the random access.
  • the random access procedure (four-step random access, also called 4-step RA) that does not carry the UE identification information in the incoming request can ensure the unified process and enable the UE to use different random access purposes and types.
  • the correct feedback is obtained.
  • the UE initiates two-step random access no expected feedback is received in the random access response, and it is possible to fall back to the four-step random access.
  • FIG. 1 is a schematic diagram of a MAC subheader including a random access code number
  • FIG. 2 is a schematic diagram of a MAC RAR
  • FIG. 3 is a schematic diagram of a competitive random access procedure
  • FIG. 4 is a schematic diagram of a non-contention random access procedure
  • Figure 5 is a schematic diagram of 2-step RA
  • FIG. 6 is a schematic flowchart of a method for random access response on a terminal side according to some embodiments of the present disclosure
  • FIG. 7 is a schematic flowchart of a method for random access response on a network side according to some embodiments of the present disclosure
  • FIG. 8 is a schematic diagram of a random access response MAC PDU format according to some embodiments of the present disclosure.
  • FIG. 9 is a schematic diagram of a MAC subheader corresponding to a fixed length MAC RAR in some embodiments of the present disclosure.
  • FIG. 10 is a schematic diagram of a MAC subheader corresponding to a variable length MAC RAR in some embodiments of the present disclosure
  • 11a is a schematic diagram of a 4-step MAC RAR in some embodiments of the present disclosure.
  • 11b is a schematic diagram of a 2-step MAC RAR of a long UE ID in some embodiments of the present disclosure
  • 11c is a schematic diagram of a 2-step MAC RAR of a short UE ID in some embodiments of the present disclosure
  • FIG. 12 is a schematic diagram of a fixed length MAC RAR in some embodiments of the present disclosure.
  • 13a-13c are schematic diagrams of a 4-step RA MAC RAR format in some embodiments of the present disclosure.
  • 13d to 13j are schematic diagrams of a 2-step RA MAC RAR format in some embodiments of the present disclosure
  • 14a is a schematic diagram of a MAC subheader in some embodiments of the present disclosure.
  • 14b to 14d are schematic diagrams of MAC RAR in some embodiments of the present disclosure.
  • 15a is a schematic diagram of a MAC subheader in some embodiments of the present disclosure.
  • Figure 15b is a schematic diagram of a MAC RAR in some embodiments of the present disclosure.
  • 16 is a MAC subheader corresponding to a variable length MAC RAR in some embodiments of the present disclosure
  • 17 is a structural block diagram of a terminal in some embodiments of the present disclosure.
  • FIG. 18 is a structural block diagram of a network side device in some embodiments of the present disclosure.
  • Step 601 The UE sends a random access request, where the random access request carries information including a UE identifier.
  • Step 602 The UE receives the random access response, and if the UE identifier carried in the random access response is consistent with the UE identifier in the random access request, completes the contention resolution; if the UE identifier and the random access request carried in the random access response If the UE identifiers are inconsistent, the UE determines that the random access fails, and re-initiates the random access attempt; if the random access response does not carry the UE identifier, the UE falls back to the random access request without carrying the UE identification information. a random access procedure; wherein the random access response is adaptively generated by the network side according to the random access request.
  • the random access carrying the UE identifier in the random access request is also referred to as a 2-step random access (2-step RA), and the random access request not carrying the UE identifier in the random access request is also called It is a four-step random access (4-step RA).
  • Step 701 The network side receives a random access request sent by the terminal UE, where the random access request carries information including the UE identifier.
  • Step 702 The network side adaptively generates a random access response according to the random access request, and sends the random access response to the UE. If the random access request carries the information including the UE identifier, the two-step random access procedure is followed. The UE is identified in the random access response. If the random access request does not carry the information including the UE identifier, the random access response is generated according to the four-step random access.
  • Some embodiments of the present disclosure employ a unified process for different random access purposes and random access types (four-step random access and two-step random access). That is, the UE sends a random access request (step 1), and receives a random access response according to a unified rule (step 2).
  • the random access response adopts a unified MAC PDU format.
  • the MAC PDU includes a MAC header and a MAC RAR.
  • the MAC header may include multiple MAC subheaders, and each MAC subheader includes a RAPID (Random Access Preamble ID). ), corresponding to the preamble code in the random access request (step 1).
  • RAPID Random Access Preamble ID
  • Each MAC sub-header corresponds to one MAC RAR, and the random access response MAC RAR carrying the UE identifier and the random access response MAC RAR not carrying the UE identifier may be multiplexed into one MAC PDU, and one UE may be randomly accessed. response.
  • an adaptive MAC RAR design is adopted, that is, a unified process can be ensured, and the UE can obtain correct feedback under different random access purposes and types, and at the same time, due to the unified process and the adaptive MAC RAR. If the UE initiates two-step random access, it does not receive the expected feedback in the random access response, and may also fall back to the four-step random access.
  • MAC RAR has two design modes, variable length and fixed length, which correspond to different MAC subheaders. The details are as follows.
  • the MAC subheader corresponds to the MAC RAR one by one. According to whether the MAC RAR is fixed length or variable length, there are two different MAC subheader design methods.
  • the format is the same as the MAC sub-header in the LTE random access response MAC PDU, and mainly includes a preamble ID (ie, RAPID) field, and other bits are necessary indication fields that cooperate with other parts of the MAC PDU.
  • RAPID preamble ID
  • FIG. 9 is only a schematic diagram. If the length of the preamble in the 5G system changes, the bit occupied by the RAPID field may increase, that is, the MAC sub-header of FIG. 9 may occupy 2 bytes, and the MAC sub-header designs the RAPID field in the following method 2. The same.
  • the MAC subheader mainly contains two parts: a preamble ID (RAPID) and a length indication field L.
  • the length of the length indication field L is limited to 8 bits (i.e., 1 byte). If the L length is less than 8 bits, other indications in 1 byte are set as reserved bits R, and Fig. 10 is an example in which the L length is 7 bits.
  • the L field has two expressions. The first is to directly indicate the length of the corresponding RAR. For example, the RAR length is 6 bytes and the L field is 0000110. The other expression is to indicate the RAR type. If the RAR type can have N types, L only It is necessary to indicate which of the N types RAR is. For the variable length MAC RAR design, FIG.
  • FIG. 13a to FIG. 13j there are 10 kinds of MAC RAR lengths, and the L field can correspond to the format indicating FIG. 13a to FIG. 13j.
  • the MAC RAR formats of Figures 13a-13j may not always be present at the same time, and the L-domains that the L-domain needs to indicate may be less.
  • Method 1-1 The RAR length is fixed to include the maximum UE ID length and the Temporary C-RNTI.
  • the specific domain content may be different for different random access response scenarios, but all the bits indicate different RAR specific formats.
  • the MAC RAR is fixed to 8 bytes, the maximum UE ID length is 46 bits, the Temporary C-RNTI is 16 bits, and the UL Grant length is 20 bits. In actual applications, the length of each domain may change. For example, if the UL Grant length is 12 bits, the total length of the MAC RAR is 7 bytes.
  • the description of each domain is as follows:
  • the specific values of T1 are not specifically limited in some embodiments;
  • Timing Advance Command Upstream timing advance
  • UL Grant Uplink Scheduling Authorization: The resource allocation of subsequent uplink transmissions. If there is no such domain, the uplink transmission is scheduled by the PDCCH with the Temporary C-RNTI (the Temporary C-RNTI has been converted into C-RNTI).
  • the length is 20bit or 12bit. The figure shows 20bit as an example.
  • Temporary C-RNTI temporary cell radio network temporary identifier: after the contention resolution is completed, the C-RNTI is allocated to the UE, and the length is 16 bits.
  • Contention Resolution Identity Information corresponding to the UE identifier contained in the random access request for two-step random access.
  • the UE ID corresponds to the initial access, the connection reestablishment, and the inactive UE initiates the random access.
  • the UE ID is the RRC connection setup request message, the RRC connection reestablishment request message, and the inactive UE ID.
  • the short UE ID is associated with the connected UE. Random access, which is C-RNTI.
  • R reserved bit, which can be set to the protocol specified value or filled by the network side.
  • Method 1-2 The RAR contains all possible domains, each of which is the maximum length of the possible length.
  • Contention Resolution Identity is unique to 2-step RA.
  • 2-step RA it is redundant domain.
  • 2-step RA may be redundant domain.
  • the RAR schematic is shown in Figure 12.
  • the Contention Resolution Identity takes a maximum of 6 bytes. The length of each domain is fixed. If the domain is not required in the random access response, the domain is actually reserved, and the value specified by the padding protocol or the value determined by the network side is determined by the network side.
  • variable length RAR indicates that the network side can adaptively generate the most suitable length of the MAC RAR according to the random access request, and the MAC RAR only needs to include the necessary domain.
  • Variable length MAC RARs are available in the following types. Note that these MAC RAR types do not necessarily exist in the protocol. In the figure, the T1 field can be used to distinguish the same length MAC RAR format if the MAC sub-header L field indicates the MAC RAR length, such as distinguishing between FIG. 13a and FIG. 13g and distinguishing between FIG. 13g and FIG. 13h. However, the MAC RARs of FIG. 13c and FIG. 13i are the same length. Since the MAC RAR of FIG.
  • FIG. 13c has no remaining bits for distinguishing indications, if the format of FIG. 13c and FIG. 13i coexist, the L-domain in the MAC sub-header can only be used to indicate the MAC RAR.
  • the format type cannot be used to indicate the MAC RAR length. The following describes the applicable scenarios for each format:
  • MAC RAR format 1 Applicable to the scenario where the UE initiates 4-step (four-step) contention random access.
  • 4-step RA MAC RAR format 2 Applicable to the scenario where the UE initiates 4-step non-contention random access.
  • 4-step RA MAC RAR format 3 Applicable to the scenario where the UE initiates 4-step non-contention random access, and the network side determines that the UE only needs to perform synchronization and does not need to send uplink data.
  • 2-step RA two-step random access
  • MAC RAR format 1 The random access request (step 1) carries the RRC connection establishment or RRC connection reestablishment or inactive UE ID (or resume ID) on the CCCH channel.
  • the UE needs to allocate the C-RNTI to the UE, and the network side needs the UE to perform uplink synchronization calibration (although the UE is in the uplink synchronization state).
  • the random access request (step 1) carries the RRC connection establishment or RRC connection reestablishment or the inactive UE ID (or resume ID) on the CCCH channel, and the network side allocates C- to the UE.
  • the RNTI does not require the UE to perform uplink synchronization calibration on the network side.
  • the random access request (step 1) carries the RRC connection establishment or RRC connection reestablishment or the inactive UE ID (or resume ID) on the CCCH channel, and the network side allocates C- to the UE.
  • the RNTI does not require the UE to perform uplink synchronization calibration on the network side.
  • the random access request (step 1) carries the inactive UE ID (or resume ID), and the network side only confirms the data in the random access request, and does not need the UE to enter the connected state. .
  • the random access request (step 1) carries the C-RNTI of the connected state UE, and the network side needs the UE to perform uplink synchronization calibration.
  • the 2-step RA MAC RAR format 6 The random access request (step 1) carries the C-RNTI of the connected state UE, and the network side does not need the UE to perform uplink synchronization calibration.
  • 2-step RA MAC RAR format 7 The random access request (step 1) carries the C-RNTI of the connected state UE, and the network side confirms that the data content in the random access request is correctly received, and determines that the UE does not need subsequent uplink transmission. Therefore no UL Grant is assigned.
  • the locations of different domains in the foregoing MAC PDU format may not be limited to those shown in the figure, and different domain locations may be interchanged.
  • the UE ID may be placed before other domains or after that.
  • the opposite value indication may be used as long as the indication can be clearly distinguished.
  • the fixed length MAC RAR method 1-1 the UE only transmits the preamble code (four-step random access)
  • the MAC PDU format includes the following MAC subheaders (Fig. 14a) and MAC RARs (Fig. 14b to Fig. 14d).
  • Step 1 Send a random access request preamble code
  • Step 2 Receive a random access response, determine the same preamble code number that is sent by itself according to the RAPID field in the MAC sub-header, and interpret the corresponding MAC RAR;
  • Step 1 Receive a random access request preamble code
  • Step 2 Send a random access response, and configure an uplink timing advance, an uplink transmission resource, and a Temporary C-RNTI for the UE.
  • Step 3 Interpret the subsequent uplink transmission of the UE, etc., to complete the random access procedure.
  • the fixed length MAC RAR method 1-1 the UE sends a preamble code and a UE ID (two-step random access)
  • the MAC PDU format is the same as that of the above embodiment, and is still shown in Figs. 14a to 14b.
  • Step 1 Send a random access request, including a preamble code and a UE ID, and other uplink transmissions (such as BSR, PHR, and uplink data).
  • the random access request needs to distinguish whether the UE sends a long UE ID or a short UE ID. Differentiating a long UE ID or a short UE ID by using different LCID fields in the MAC subheader;
  • Step 2 Receive a random access response, determine the same preamble code number that is sent by itself according to the RAPID field in the MAC sub-header, and interpret the corresponding MAC RAR;
  • Step 3 Parse T1 with the following branches:
  • step 1 If the UE sends a long UE ID in step 1, it is determined that the MAC RAR is not for itself, the current random access fails, and the random access attempt may be re-initiated; if the UE sends the short UE ID in step 1. Go to step 4-3.
  • Step 4 According to the result of step 3, there are the following branches:
  • the UE receives the subsequent domain in the MAC RAR (1) and falls back to the four-step random access, that is, according to the four-step random access procedure, parses each domain in the MAC RAR (1), and proceeds to step 5- 1;
  • the UE receives the MAC RAR (2), determines whether the value in the Contention Resolution Identity is consistent with the UE ID sent in step 1, if the UE agrees to complete the contention resolution, go to step 5-2; if the UE ID If the random access fails, the random access attempt may be re-initiated;
  • Step 5-3 The UE receives the MAC RAR (3), determines whether the value in the Contention Resolution Identity is consistent with the UE ID sent in step 1. If they are consistent, the UE determines to complete the contention resolution, parses the UL Grant in the MAC RAR, and proceeds to Step 5-3: If the UE IDs are inconsistent, it is determined that the random access fails, and the random access attempt may be re-initiated;
  • Step 5 According to the result of step 4, there are the following branches:
  • the UE adjusts the uplink timing advance according to the indication of each domain in the MAC RAR, acquires the Temporary C-RNTI, sends the Msg3 according to the UL Grant, and completes the subsequent random access procedure;
  • the UE receives a PDCCH scheduling command with a Temporary C-RNTI sent by the network side, and sends an uplink transmission according to the scheduling command;
  • the UE sends a subsequent uplink transmission according to the resource indicated by the UL Grant in the MAC RAR.
  • Step 1 Receive a random access request, which may be a preamble code or a preamble code plus data part;
  • Step 2 Generate a corresponding MAC RAR according to the received random access request and send it to the UE. If the MAC RAR (2) is generated, a PDCCH scheduling command with the Temporary C-RNTI is sent to allocate subsequent uplink transmission resources to the UE;
  • Step 3 Receive uplink transmission on the scheduled resource. If it is a four-step random access, complete the subsequent Msg3 and Msg4.
  • the fixed length MAC RAR method 1-2 the UE only transmits the preamble code (four-step random access)
  • the MAC PDU format includes the following MAC subheader (Fig. 15a) and MAC RAR (Fig. 15b).
  • Step 1 Send a random access request preamble code
  • Step 2 Receive a random access response, determine the same preamble code number that is sent by itself according to the RAPID field in the MAC sub-header, and interpret the corresponding MAC RAR;
  • Step 1 Receive a random access request preamble code
  • Step 2 Send a random access response, and configure an uplink timing advance, an uplink transmission resource, and a Temporary C-RNTI for the UE.
  • Step 3 Interpret the subsequent uplink transmission of the UE, etc., to complete the random access procedure.
  • the fixed length MAC RAR method 1-2 the UE sends the preamble code and the UE ID (two-step random access)
  • the MAC PDU format is the same as the above embodiment, and is still Figures 15a and 15b.
  • Step 1 Send a random access request, including a preamble code and a UE ID, and other uplink transmissions (such as BSR, PHR, and uplink data).
  • the random access request needs to distinguish whether the UE sends a long UE ID or a short UE ID. Differentiating a long UE ID or a short UE ID by using different LCID fields in the MAC subheader;
  • Step 2 Receive a random access response, determine the same preamble code number that is sent by itself according to the RAPID field in the MAC sub-header, and interpret the corresponding MAC RAR;
  • Step 3 Parse T1 with the following branches:
  • step 1 If the UE sends a long UE ID in step 1, it is determined that the MAC RAR is not for itself, the current random access fails, and the random access attempt may be re-initiated; if the UE sends the short UE ID in step 1. Go to step 4-2.
  • Step 4 According to the result of step 3, there are the following branches:
  • step 5-1 The UE only parses the Timing Advance Command, the UL Grant, and the Temporary C-RNTI domain in the MAC RAR, and rolls back to the four-step random access, that is, according to the four-step random access procedure, proceeds to step 5-1;
  • the UE determines whether the value in the Contention Resolution Identity is consistent with the UE ID sent in step 1. If the UE is consistent, the UE determines to complete the contention resolution, and proceeds to step 5-2; if the UE ID is inconsistent, the current random connection is determined. If the entry fails, the subsequent random access attempt can be re-initiated;
  • Step 5 According to the result of step 4, there are the following branches:
  • the UE adjusts the uplink timing advance according to the indication of each domain in the MAC RAR, obtains the Temporary C-RNTI, sends the Msg3 according to the UL Grant, and completes the subsequent random access procedure (Msg3, Msg4);
  • the UE sends a subsequent uplink transmission according to the resource indicated by the UL Grant in the MAC RAR.
  • Step 1 Receive a random access request, which may be a preamble code or a preamble code plus data part;
  • Step 2 Generate a corresponding MAC RAR according to the received random access request and send it to the UE.
  • Step 3 Receive uplink transmission on the scheduled resource. If the network side considers it to be four-step random access, it needs to complete subsequent Msg3 and Msg4.
  • variable length MAC RAR the UE only transmits the preamble code (four-step random access)
  • the MAC sub-header format of the random access response MAC PDU is as shown in FIG. 16, and the possible MAC RAR format is shown in FIGS. 13a to 13j.
  • Step 1 Send a random access request preamble code
  • Step 2 Receive a random access response, and determine that the preamble code number sent by itself is the same according to the RAPID field in the MAC sub-header. If the same, the L-domain is determined to determine the subsequent MAC RAR type, and if the L-domain indicates the two-step random access. The MAC RAR type determines that the random access response is not for itself, the random access fails, and may subsequently initiate a new random access attempt; if the MAC RAR type is a four-step random access RAR, go to step 3.
  • Step 3 Acquire MAC RAR.
  • the three MAC RARs of Figure 13a to Figure 13c may not exist at the same time. It is likely that there is only one MAC RAR of Figure 13a.
  • the UE completes the required subsequent random access procedure (Msg3, Msg4) according to the MAC RAR domain indication.
  • Step 1 Receive a random access request preamble code
  • Step 2 Generate a random access response according to the random access response, including the correct MAC subheader and MAC RAR;
  • Step 3 Interpret the subsequent uplink transmission of the UE and complete the random access procedure.
  • variable length MAC RAR the UE sends the preamble code and the UE ID (two-step random access)
  • the format of the MAC subheader is shown in Figure 15.
  • the format of the MAC PDU is shown in Figures 13a to 13j.
  • Step 1 Send a random access request, including a preamble code and a UE ID, and other uplink transmissions (such as BSR, PHR, and uplink data).
  • the random access request needs to distinguish whether the UE sends a long UE ID or a short UE ID. Differentiating a long UE ID or a short UE ID by using different LCID fields in the MAC subheader;
  • Step 2 Receive a random access response, and receive a random access response.
  • the RAPID field in the MAC sub-header is determined to be the same as the preamble code number sent by itself. If the same, the L-domain is determined to determine the subsequent MAC RAR type.
  • Step 3 According to different MAC RAR types indicated by the L domain, there are the following branches:
  • the L field indicates the MAC RAR type of the four-step random access (Fig. 13a)
  • the network side does not correctly receive the data part of the random access request, and falls back to the four-step random access procedure, that is, according to the MAC
  • the RAR indicates that the uplink transmission (Msg3) is sent, and the subsequent downlink transmission Msg4 is received to complete the contention resolution.
  • step 4 If the MAC RAR type is a two-step random access RAR, proceed to step 4.
  • Step 4 For the two-step random access MAC RAR, according to the different MAC RAR types indicated by the L domain, there are the following branches:
  • a two-step MAC RAR format 4 (Fig. 13g) if the UE carries a long UE ID in the random access request of step 1, and the UE ID is consistent with the random access request, the contention resolution is considered successful.
  • the PDCCH scheduling command carrying the C-RNTI is subsequently received, and the uplink transmission is sent according to the scheduling command; if the UE sends the short transmission request in the random access request.
  • the UE ID or the UE ID is inconsistent with the UE ID in the random access request, and the random access is considered to be failed, and the random access attempt may be re-initiated.
  • This format is only applicable when the UE sends an uplink transmission in the inactive state, and does not need to obtain the C-RNTI to enter the connected state.
  • the contention resolution is considered successful. Then, the PDCCH scheduling command carrying the C-RNTI of the UE is monitored, and if the PDCCH scheduling command for scheduling the uplink transmission is received, the uplink transmission is sent according to the scheduling command; if the UE sends the long UE ID or the UE ID in the random access request If the random access fails, the random access attempt may be re-initiated.
  • the format is mainly applicable to the case where the UE sends only one uplink transmission in the connected state, and no subsequent transmission is required. The network side does not necessarily send the PDCCH scheduling command to schedule the uplink transmission.
  • a terminal is further provided in some embodiments of the present disclosure.
  • the principle of solving the problem is similar to the random access response method in FIG. 6 of some embodiments of the present disclosure. Therefore, the implementation of the terminal may refer to the method. Implementation, repetitions are not repeated.
  • terminal 1700 comprising:
  • the sending module 1701 is configured to send a random access request, where the random access request carries information including a UE identifier;
  • the first processing module 1702 is configured to receive a random access response, if the UE identifier carried in the random access response is consistent with the UE identifier in the random access request, complete the contention resolution; if the UE identifier in the random access response is If the UE identifier in the random access request is inconsistent, the UE determines that the random access fails, and re-initiates the random access attempt; if the random access response does not carry the UE identifier, the UE falls back to the random access.
  • a random access procedure that does not carry UE identification information in the request;
  • the random access response is adaptively generated by the network side according to the random access request.
  • the random access that carries the UE identifier in the random access request is also called a two-step random access, and the random access that does not carry the UE identifier in the random access request is also called a four-step random access.
  • the random access response is sent by using a MAC PDU, where the MAC PDU includes a MAC header and a MAC RAR, and the MAC header includes multiple MAC subheaders, and each MAC subheader includes A RAPID corresponding to the preamble code in the random access request, each MAC subheader corresponding to one MAC RAR, and the random access response MAC RAR carrying the UE identifier and the random access response MAC RAR not carrying the UE identifier may be multiplexed to In a MAC PDU.
  • a MAC RAR of the same length is used, and the MAC RAR length is used.
  • the MAC RAR includes any one or more of the following:
  • T1 indicating a MAC RAR followed by four-step random access or a MAC RAR of two-step random access
  • T2 appears only in the two-step random access MAC RAR, and is used to indicate that it is a long UE ID or a short UE ID;
  • Timing Advance Command Upstream timing advance
  • Temporary C-RNTI converted to a C-RNTI allocated to the UE after the contention resolution is completed;
  • Contention Resolution Identity information corresponding to the UE identifier included in the random access request of the two-step random access
  • the MAC RAR includes all possible domains, each of which has a maximum length of possible length, and each domain has a fixed length if random access If the domain is not required in the response, the domain is actually reserved, filling the value specified by the protocol or determining the value of the padding by the network side.
  • the sending module is further configured to: send a random access request preamble code, and not send information that carries the UE identifier;
  • the first processing module is further configured to: receive a random access response, determine a MAC sub-head corresponding to the transmitted preamble code according to the RAPID field in the MAC sub-header; and obtain, by the UE, a MAC RAR corresponding to the MAC sub-header, if parsing
  • the indication field in the MAC RAR determines that the MAC RAR does not carry the UE identifier, reads the subsequent domain in the MAC RAR, performs related operations according to the indication of each domain, and completes the subsequent random access procedure; if the indication domain in the MAC RAR is parsed, the The MAC RAR carries the UE identifier, determines that the random access fails, and subsequently initiates a new random access attempt.
  • the sending module is further configured to send a random access request, including a preamble code and information including a UE identifier;
  • the first processing module is further configured to: receive a random access response, and determine, according to the RAPID field in the MAC sub-head, a MAC sub-head corresponding to the transmitted preamble code;
  • the MAC RAR corresponding to the MAC sub-header if the indication field T1 in the parsing MAC RAR determines that the MAC RAR does not carry the UE identifier, determining that the network side only receives the preamble code and does not correctly receive the data part, and reads the subsequent in the MAC RAR.
  • the domain is backed up to the four-step random access, and the domains in the MAC RAR are parsed according to the four-step random access procedure, and then the subsequent random access procedure is completed according to the indications of the domains in the MAC RAR; or
  • the indication field T1 in the parsing MAC RAR determines that the MAC RAR carries the UE identity, and the indication field T2 determines that the UE identity is a long UE ID, if the UE sends a long UE ID, it is determined whether the UE identity in the MAC RAR is sent with the UE.
  • the long UE IDs are consistent. If they are consistent, the QoS scheduling command with the Temporary C-RNTI sent by the network side is received, and the uplink transmission is sent according to the scheduling command. If not, the UE determines the random access. Failure, subsequent re-initiation of random access attempts; or
  • the indication field T1 in the parsing MAC RAR determines that the MAC RAR carries the UE identity, and the indication domain T2 determines that the UE identity is a long UE ID, if the UE sends the short UE ID, it is determined that the MAC RAR is not for itself, this time Random access fails, and subsequent random access attempts are re-initiated; or
  • the indication field T1 in the parsing MAC RAR determines that the MAC RAR carries the UE identity, and the indication field T2 determines that the UE identity is a short UE ID, if the UE sends a long UE ID, it is determined that the MAC RAR is not for itself, this time Random access fails, and subsequent random access attempts are re-initiated; or
  • the indication field T1 in the parsing MAC RAR determines that the MAC RAR carries the UE identity, and the indication field T2 determines that the UE identity is a short UE ID, if the UE sends the short UE ID, the UE determines whether the UE identity in the MAC RAR is Consistent with the short UE ID sent by the UE, if consistent, determining to complete the contention resolution, parsing the UL Grant in the MAC RAR, and transmitting the subsequent uplink transmission according to the resource indicated by the UL Grant in the MAC RAR; if not, the UE determines the current random The access fails, and the random access attempt is re-initiated.
  • the sending module is further configured to: send a random access request, including a preamble code and information including a UE ID identifier;
  • the first processing module is further configured to: receive a random access response, and determine, according to the RAPID field in the MAC sub-head, a MAC sub-head corresponding to the preamble code sent by the RAPID field;
  • the MAC RAR corresponding to the MAC sub-header, if the indication field T1 in the parsing MAC RAR determines that the MAC RAR does not carry the UE identifier, determining that the network side only receives the preamble code and does not correctly receive the data part, and only parses the Timing in the MAC RAR.
  • the Advance Command, the UL Grant, and the Temporary C-RNTI domain are rolled back to the four-step random access, and then the UE adjusts the uplink timing advance according to the indication of each domain in the MAC RAR, acquires the Temporary C-RNTI, and sends according to the UL Grant. Msg3, and complete the subsequent random access process; or
  • Determining the indication field T1 in the MAC RAR determines that the MAC RAR carries the UE identity, and the indication field T2 determines that the UE identity is a long UE ID, parses all domains, and if the UE sends a long UE ID, the UE determines the MAC RAR. Whether the UE identifier is consistent with the long UE ID sent by the UE. If the UE is consistent, it is determined that the contention resolution is complete, and then the subsequent uplink transmission is sent according to the resource indicated by the UL Grant in the MAC RAR; if not, the UE determines that the random access fails. Subsequent re-initiation of random access attempts; or
  • Determining the indication field T1 in the MAC RAR determines that the MAC RAR carries the UE identity, and the indication field T2 determines that the UE identity is a long UE ID, parses all domains, and if the UE sends a short UE ID, determines that the MAC RAR is not for its own The random access fails, and the random access attempt is re-initiated; or
  • the indication field T1 in the parsing MAC RAR determines that the MAC RAR carries the UE identity, and the indication domain T2 determines that the UE identity is a short UE ID, parses all domains, and if the UE sends a long UE ID, it is determined that the MAC RAR is not for itself.
  • the random access fails, and the random access attempt is re-initiated; or
  • the indication field T1 in the parsing MAC RAR determines that the MAC RAR carries the UE identifier
  • the indication field T2 determines that the UE identifier is a short UE ID
  • parses all domains and if the UE sends a short UE ID, determines the UE identifier in the MAC RAR. Whether it is consistent with the short UE ID sent by the UE, if it is consistent, it is determined that the contention resolution is completed, and then the subsequent uplink transmission is sent according to the resource indicated by the UL Grant in the MAC RAR; if not, the random access failure is determined, and the random reconnection is subsequently initiated. Try it.
  • the MAC subheader includes a preamble ID and a length indication field L, and the length indication field L is used to indicate a length of the corresponding MAC RAR or a MAC RAR type.
  • the MAC RAR type includes any one or more of the following:
  • Four-step random access MAC RAR format 2 Applicable to the scenario where the UE initiates four-step non-contention random access;
  • Four-step random access MAC RAR format 3 Applicable to the scenario where the UE initiates four-step non-contention random access, and the network side determines that the UE only needs to perform synchronization and does not need to send uplink data.
  • Two-step random access MAC RAR format 1 The random access request carries the RRC connection establishment or the RRC connection reestablishment or the inactive UE ID on the CCCH channel.
  • the network side needs to allocate the C-RNTI to the UE, and the network side needs the UE to perform the uplink. Synchronous calibration
  • Two-step random access (2-step RA) MAC RAR format 2 The random access request carries the RRC connection establishment or the RRC connection reestablishment or the inactive UE ID on the CCCH channel, and the network side allocates the C-RNTI to the UE. The network side does not need the UE to perform uplink synchronization calibration;
  • Two-step random access MAC RAR format 3 The random access request carries the RRC connection establishment or the RRC connection reestablishment or the inactive UE ID on the CCCH channel, and the network side needs to allocate the C-RNTI to the UE, and the network side does not need the UE to perform Uplink synchronization calibration;
  • Two-step random access MAC RAR format 4 The random access request carries the inactive UE ID, and the network side only confirms the data in the random access request, and does not need the UE to enter the connected state;
  • Two-step random access MAC RAR format 5 The random access request carries the C-RNTI of the connected state UE, and the network side needs the UE to perform uplink synchronization calibration;
  • Two-step random access MAC RAR format 6 The random access request carries the C-RNTI of the connected state UE, and the network side does not need the UE to perform uplink synchronization calibration;
  • Two-step random access MAC RAR format 7 The random access request carries the C-RNTI of the connected state UE, and the network side confirms that the data content in the random access request is correctly received, and determines that the UE does not need subsequent uplink transmission, and the network side No UL Grant is assigned.
  • the sending module is further configured to: send a random access request preamble code, and not send information that carries the UE identifier;
  • the first processing module is further configured to: receive a random access response, determine a MAC sub-head corresponding to the transmitted preamble code according to the RAPID field in the MAC sub-header, and parse the L-domain in the MAC sub-head to determine a subsequent MAC RAR length or MAC RAR type;
  • the L domain indicates the MAC RAR type of the two-step random access, it is determined that the random access response is not for itself, the random access fails, and a new random access attempt is subsequently initiated;
  • the MAC RAR is obtained, and the required subsequent random access procedure is completed according to the MAC RAR domain indication.
  • the sending module is further configured to: send a random access request, including a preamble code and a UE identifier;
  • the first processing module is further configured to: receive a random access response, determine a MAC sub-head corresponding to the transmitted preamble code according to the RAPID field in the MAC sub-header, and parse the L-domain in the MAC sub-head to determine a subsequent MAC RAR type;
  • the MAC RAR type is a four-step random access RAR, it is determined that the network side does not correctly receive the data part in the random access request, falls back to the four-step random access procedure, sends the Msg3 according to the MAC RAR indication, and receives the downlink transmission.
  • Msg4 complete the competition resolution
  • the following processing is performed according to different MAC RAR types indicated by the L domain:
  • the format type is two-step random access MAC RAR format 1
  • the long-end UE ID is carried in the random access request, and the UE identifier in the MAC RAR is consistent with the long UE ID in the random access request, and the contention is considered to be resolved.
  • Successfully perform uplink synchronization timing calibration, transmit uplink data, and apply C-RNTI according to the indication in the MAC RAR; if the UE sends the short UE ID or the UE identifier and the random access request in the MAC RAR in the random access request The UE IDs in the packets are inconsistent, and the random access fails, and the random access attempt is re-initiated; or
  • the format type is two-step random access MAC RAR format 2
  • the random access request carries a long UE ID, and the UE identifier in the MAC RAR is consistent with the long UE ID in the random access request, the contention is considered to be resolved.
  • the UE sends the uplink data according to the indication in the MAC RAR, and applies the C-RNTI; if the UE sends the short UE ID in the random access request or the UE identifier in the MAC RAR is inconsistent with the UE identifier in the random access request, Random access fails, and subsequent random access attempts are re-initiated; or
  • the format type is two-step random access MAC RAR format 3
  • the random access request carries a long UE ID, and the UE identifier in the MAC RAR is consistent with the long UE ID in the random access request, the contention is considered to be resolved.
  • the C-RNTI is applied according to the indication in the MAC RAR; if the UE sends the short UE ID in the random access request or the UE identifier in the MAC RAR is inconsistent with the UE identifier in the random access request, it is considered to be randomly connected. Incoming failure, subsequent re-initiation of random access attempts; or
  • the format type is two-step random access MAC RAR format 4
  • the random access request carries a long UE ID, and the UE identifier in the MAC RAR is consistent with the long UE ID in the random access request, the contention is considered to be resolved.
  • Successfully according to the application C-RNTI in the MAC RAR, subsequently receiving the PDCCH scheduling command carrying the C-RNTI, and transmitting the uplink transmission according to the scheduling command; if the UE sends the short UE ID or the MAC in the random access request
  • the UE identifier in the RAR is inconsistent with the UE identifier in the random access request, and the random access is considered to be failed, and the random access attempt is subsequently re-initiated; or
  • the format type is two-step random access MAC RAR format 5
  • the random access request carries a short UE ID
  • the UE identifier in the MAC RAR is the same as the short UE ID in the random access request
  • the contention is considered to be resolved.
  • Successfully performing uplink synchronization timing calibration and transmitting uplink data according to the indication in the MAC RAR; if the UE sends a long UE ID in the random access request or the UE identifier in the MAC RAR is inconsistent with the UE identifier in the random access request, Considering that the random access fails, and subsequently re-initiating a random access attempt; or
  • the format type is two-step random access MAC RAR format 6
  • the random access request carries a short UE ID, and the UE identifier in the MAC RAR is the same as the short UE ID in the random access request, the contention is considered to be resolved.
  • the UE sends the uplink data according to the indication in the MAC RAR if the UE sends the long UE ID in the random access request or the UE identifier in the MAC RAR is inconsistent with the UE identifier in the random access request, the random access fails. Subsequent re-initiation of random access attempts; or
  • the format type is two-step random access MAC RAR format 7
  • the random access request carries a short UE ID, and the UE identifier in the MAC RAR is consistent with the short UE ID in the random access request
  • the competition is considered If the solution succeeds, the PDCCH scheduling command carrying the C-RNTI of the UE is subsequently monitored, and if the PDCCH scheduling command for scheduling the uplink transmission is received, the uplink transmission is sent according to the scheduling command; if the UE sends the long UE ID in the random access request or The UE identifier in the MAC RAR is inconsistent with the UE identifier in the random access request, and the random access is considered to be failed, and the random access attempt is subsequently re-initiated.
  • a network side device is further provided in some embodiments of the present disclosure.
  • the principle of solving the problem in the network side device is similar to the method for competing random access in FIG. 7 in some embodiments of the present disclosure, so the network side is
  • the implementation of the device can be referred to the implementation of the method, and the repetition is not described.
  • the network side device 1800 includes:
  • the receiving module 1801 is configured to receive a random access request sent by the terminal UE, where the random access request carries information including the UE identifier.
  • the second processing module 1802 is configured to: adaptively generate a random access response according to the random access request, and send the random access response to the UE, if the random access request carries the information including the UE identifier, according to the two-step random
  • the access procedure includes the UE ID information in the random access response. If the random access request does not carry the information including the UE identifier, the random access response is generated according to the four-step random access.
  • the random access response is sent by using a MAC PDU, where the MAC PDU includes a MAC header and a medium access control layer random access response MAC RAR, and the MAC header includes multiple MAC sub- In the header, each MAC sub-head contains a RAPID corresponding to the preamble code in the random access request, and each MAC sub-head corresponds to one MAC RAR, and carries a random access response of the UE identifier and a random access that does not carry the UE identifier.
  • the response MAC RAR can be multiplexed into one MAC PDU.
  • a MAC RAR of the same length is used for four-step random access and two-step random access, and different random access scenarios of two-step random access, where the MAC RAR length is fixed.
  • the maximum UE ID length and Temporary C-RNTI, or both are examples of the maximum UE ID length and Temporary C-RNTI, or both.
  • the MAC RAR includes any one or more of the following:
  • T1 indicating a MAC RAR followed by four-step random access or a MAC RAR of two-step random access
  • T2 appears only in the two-step random access MAC RAR, and is used to indicate that it is a long UE ID or a short UE ID;
  • Timing Advance Command Upstream timing advance
  • Temporary C-RNTI converted to a C-RNTI allocated to the UE after the contention resolution is completed;
  • Contention Resolution Identity information corresponding to the UE identifier included in the two-step random access request
  • the MAC RAR includes all possible domains, each of which has a maximum length of possible length, and each domain has a fixed length if random access If the domain is not required in the response, the domain is actually reserved, filling the value specified by the protocol or determining the value of the padding by the network side.
  • the receiving module is further configured to: receive a random access request, where the random access request includes a preamble code, and does not send information that carries the UE identifier;
  • the second processing module is further configured to: send a random access response, where the random access response includes an uplink timing advance, an uplink transmission resource, and a Temporary C-RNTI configured according to the preamble code.
  • the receiving module is further configured to:
  • the random access request including a preamble code or including a preamble code and a data portion
  • the processing module is further configured to: generate a corresponding MAC RAR according to the received random access request, and send the corresponding MAC RAR to the UE.
  • the network side sends the carrying Temporary C
  • the PDCCH scheduling command of the RNTI allocates subsequent uplink transmission resources to the UE.
  • the MAC subheader includes a preamble ID and a length indication field L, where the length indication field is used to indicate the length or type of the corresponding MAC RAR.
  • the MAC RAR type includes any one or more of the following:
  • MAC RAR format 1 Applicable to the scenario where the UE initiates four-step competitive random access;
  • Four-step random access MAC RAR format 2 Applicable to the scenario where the UE initiates four-step non-contention random access;
  • Four-step random access MAC RAR format 3 Applicable to the scenario where the UE initiates four-step non-contention random access, and the network side determines that the UE only needs to perform synchronization and does not need to send uplink data.
  • Two-step random access MAC RAR format 1 The random access request carries the RRC connection establishment or the RRC connection reestablishment or the inactive UE ID on the CCCH channel.
  • the network side needs to allocate the C-RNTI to the UE, and the network side needs the UE to perform the uplink. Synchronous calibration
  • Two-step random access MAC RAR format 2 The random access request carries the RRC connection establishment or the RRC connection reestablishment or the inactive UE ID on the CCCH channel, and the network side needs to allocate the C-RNTI to the UE, and the network side does not need the UE to perform Uplink synchronization calibration;
  • Two-step random access MAC RAR format 3 The random access request carries the RRC connection establishment or the RRC connection reestablishment or the inactive UE ID on the CCCH channel, and the network side needs to allocate the C-RNTI to the UE, and the network side does not need the UE to perform Uplink synchronization calibration;
  • Two-step random access MAC RAR format 4 The random access request carries the inactive UE ID, and the network side only confirms the data in the random access request, and does not need the UE to enter the connected state;
  • Two-step random access MAC RAR format 5 The random access request carries the C-RNTI of the connected state UE, and the network side needs the UE to perform uplink synchronization calibration;
  • Two-step random access MAC RAR format 6 The random access request carries the C-RNTI of the connected state UE, and the network side does not need the UE to perform uplink synchronization calibration;
  • Two-step random access MAC RAR format 7 The random access request carries the C-RNTI of the connected state UE, and the network side confirms that the data content in the random access request is correctly received, and determines that the UE does not need subsequent uplink transmission, and the network side No UL Grant is assigned.
  • the UE determines that the random access fails, and re-initiates the random access attempt; if the random access response does not carry the UE identifier, the UE falls back to the random access procedure that does not carry the UE identification information in the random access request (four Step random access, also known as 4-step RA), not only guarantees a uniform process, but also enables the UE to get correct feedback under different random access purposes and types, and at the same time, due to the unified process and adaptive MAC RAR If the UE initiates two-step random access, it does not receive the expected feedback in the random access response, and may also fall back to the four-step random access.
  • 4-step random access also known as 4-step RA
  • system and “network” are used interchangeably herein.
  • B corresponding to A means that B is associated with A, and B can be determined from A.
  • determining B from A does not mean that B is only determined based on A, and that B can also be determined based on A and/or other information.
  • the disclosed method and apparatus may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • each functional unit in various embodiments of the present disclosure may be integrated into one processing unit, or each unit may be physically included separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium.
  • the above software functional unit is stored in a storage medium and includes a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network side device, etc.) to perform part of the steps of the transceiving method of the various embodiments of the present disclosure.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, and the program code can be stored. Medium.

Landscapes

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

Abstract

本公开提供了一种随机接入响应方法和装置，该方法包括：UE发送随机接入请求，所述随机接入请求中携带包含UE标识的信息；所述UE接收随机接入响应，如果随机接入响应中携带的UE标识与随机接入请求中的UE标识一致，完成竞争解决；如果随机接入响应中携带的UE标识与随机接入请求中的UE标识不一致，则所述UE确定本次随机接入失败，重新发起随机接入尝试；如果随机接入响应中未携带UE标识，则所述UE回退到随机接入请求中不携带UE标识信息的随机接入过程。

Description

一种随机接入响应方法和装置
相关申请的交叉引用
本申请主张在2017年1月6日在中国提交的中国专利申请号No.201710009612.0的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其涉及一种随机接入响应方法和装置。
背景技术
LTE系统的随机接入分为竞争随机接入和非竞争随机接入两种。其过程分别如下。
竞争随机接入过程如图1所示，主要分为四步随机接入，也可称为4-step RA：
Msg1：UE选择随机接入preamble(随机接入前导码)和PRACH(Physical Random Access Channel，物理随机接入信道)资源并利用该PRACH资源向基站发送所选的随机接入preamble码(随机接入前导码)。
Msg2：基站接收到preamble码，发送随机接入响应。随机接入响应包含两部分：MAC头和MAC RAR。MAC头包含多个子头，每个子头格式如图2所示，其主要内容为RAPID(Random Access Preamble ID)。MAC RAR如图3所示，包括定时提前量TAC(Time Advance Command)、针对Msg3的上行资源授权(UL Grant，上行调度授权)和网络侧分配的临时C-RNTI(Temporary C-RNTI)。承载Msg2调度信息的PDCCH(Physical Downlink Control Channel，物理下行控制信道)用RA-RNTI加扰，RA-RNTI在UE接收Msg2的窗长内与发送Msg1的时频资源唯一对应。UE接收Msg2时，通过RA-RNTI和preamble ID确定该Msg2是与其发送的Msg1对应的。
Msg3：UE在Msg2指定的UL grant上发送上行传输，不同随机接入原因Msg3上行传输的内容不同，比如对于初始接入，Msg3传输的是RRC连接建立请求。
Msg4：竞争解决消息，UE根据Msg4可以判断随机接入是否成功。对于初始接入UE，竞争解决成功后临时C-RNTI自动转化为UE在该小区的唯一UE标识C-RNTI。
非竞争随机接入如图4所示，主要分为三步：
Msg0：基站向UE分配用于非竞争随机接入的专用preamble码以及随机接入使用的PRACH资源。
Msg1：UE根据Msg0的指示，在指定的PRACH资源上向基站发送指定的专用preamble。基站接收到Msg1后根据Msg1计算上行定时提前量TA。
Msg2：基站向UE发送随机接入响应，随机接入响应中包含定时提前量信息、后续上行传输资源分配UL grant，定时提前量用于UE后续上行传输的定时关系。
在新一代无线网络系统中，针对UE侧和gNB不需要进行同步的场景，在4-step RA基础上进行出两步随机接入过程(或者称为2-step RA)，其过程如下图5。为便于表达，以下不再成Msg1、Msg2，而称为step1、step2。
Step 1：相当于4-step RA的Msg1+Msg3，包含随机接入码部分和数据部分，两部分可以各自独立解码。随机接入码部分用于发送preamble码，即为4-step RA中Msg1的随机接入码preamble；数据部分类似于4-step RA中的Msg3，可以包含UE标识(根据不同的随机接入事件和UE状态，具体UE标识内容可能不同)、缓存状态报告(BSR，Buffer Status Report或DV，Data Volume)、PHR(Power Headroom Report，功率余量报告)、上行数据。
Step 2：相当于4-step RA的Msg2+Msg4。用于完成随机接入竞争解决和上行数据接收反馈。
在5G系统中引入两步随机接入2-step RA，相关技术中的随机接入过程中的随机接入响应消息已不再适用于2-step RA。
发明内容
鉴于上述技术问题，本公开实施例提供一种随机接入响应方法和装置，解决在新一代无线通信系统(NR系统或5G系统)中如何设计随机接入响应，以满足新一代无线通信系统的随机接入过程的特性和需求。
依据本公开实施例的一个方面，提供了一种随机接入响应方法，包括：
UE发送随机接入请求，所述随机接入请求中携带包含UE标识的信息；
所述UE接收随机接入响应，如果随机接入响应中携带的UE标识与随机接入请求中的UE标识一致，完成竞争解决；如果随机接入响应中携带的UE标识与随机接入请求中的UE标识不一致，则所述UE确定本次随机接入失败，重新发起随机接入尝试；如果随机接入响应中未携带UE标识，则所述UE回退到随机接入请求中不携带UE标识信息的随机接入过程；
其中，所述随机接入响应是网络侧根据随机接入请求自适应生成的；
随机接入请求中携带UE标识的随机接入又称为两步随机接入，随机接入请求中不携带UE标识的随机接入又称为四步随机接入。
可选地，所述随机接入响应采用MAC PDU发送，该MAC PDU中包含MAC头和MAC RAR，MAC头包含多个MAC子头，每个MAC子头中包含一个RAPID，对应随机接入请求中的preamble码，每个MAC子头与一个MAC RAR对应，携带UE标识的随机接入响应MAC RAR和不携带UE标识的随机接入响应MAC RAR可以复用到一个MAC PDU中。
可选地，对于四步随机接入和两步随机接入，以及两步随机接入的不同随机接入场景，采用相同长度的MAC RAR，所述MAC RAR长度固定为能包含最大UE标识长度和Temporary C-RNTI，或同时能包含UL Grant。
可选地，所述MAC RAR包含以下任一项或多项：
T1：指示后续为四步随机接入的MAC RAR或者两步随机接入的MAC RAR；
T2：只在两步随机接入的MAC RAR中出现，用于指示是长UE ID或者为短UE ID；
Timing Advance Command：上行定时提前量；
UL Grant：后续上行传输的资源分配；
Temporary C-RNTI：竞争解决完成后转换为给UE分配的C-RNTI；
Contention Resolution Identity：对应两步随机接入的随机接入请求中包含的UE标识的信息；
R：预留比特。
可选地，所述MAC RAR中包含所有可能的域，每个域的长度都为可能长 度的最大值，每个域的长度都是固定的，如果随机接入响应中不需要该域，则该域实际为预留bit，填充协议规定的值或由网络侧确定填充的值。
可选地，所述UE发送随机接入请求，包括：
所述UE发送随机接入请求preamble码，不发送携带UE标识的信息；
所述UE接收随机接入响应，包括：
所述UE接收随机接入响应，根据MAC子头中RAPID域确定与发送的preamble码对应的MAC子头；
所述UE获取该MAC子头对应的MAC RAR，如果解析MAC RAR中的指示域确定该MAC RAR不携带UE标识，读取MAC RAR中的后续域，根据各域的指示进行相关操作，完成后续随机接入过程；如果解析MAC RAR中的指示域确定该MAC RAR携带UE标识，确定随机接入失败，后续发起新的随机接入尝试。
可选地，所述UE发送随机接入请求，包括：
所述UE发送随机接入请求，包括preamble码和包含UE标识的信息；
所述UE接收随机接入响应，包括：
所述UE接收随机接入响应，根据MAC子头中RAPID域确定与发送的preamble码对应的MAC子头；
所述UE获取该MAC子头对应的MAC RAR，如果解析MAC RAR中的指示域T1确定该MAC RAR不携带UE标识，确定网络侧只收到了preamble码而没有正确接收数据部分，读取MAC RAR中的后续域，回退到四步随机接入，按照四步随机接入过程解析MAC RAR中各域，然后根据MAC RAR中各域的指示，完成后续的随机接入过程；或者
如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，如果UE发送的是长UE ID，所述UE判断MAC RAR中的UE标识是否与UE发送的长UE ID一致，如果一致，确定完成竞争解决，所述UE接收随后网络侧发送的带Temporary C-RNTI的PDCCH调度命令，根据该调度命令发送上行传输；如果不一致，所述UE确定本次随机接入失败，后续重新发起随机接入尝试；或者
如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，如果UE发送的是短UE ID，确定该MAC RAR不是针对 自己的，本次随机接入失败，后续重新发起随机接入尝试；或者
如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，如果UE发送的是长UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续重新发起随机接入尝试；或者
如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，如果UE发送的是短UE ID，所述UE判断MAC RAR中的UE标识是否与UE发送的短UE ID一致，如果一致，确定完成竞争解决，所述UE解析MAC RAR中的UL Grant，根据MAC RAR中UL Grant指示的资源，发送后续上行传输；如果不一致，所述UE确定本次随机接入失败，后续重新发起随机接入尝试。
可选地，所述UE发送随机接入请求，包括：
所述UE发送随机接入请求，包括preamble码和包含UE ID标识的信息；
所述UE接收随机接入响应，包括：
所述UE接收随机接入响应，根据MAC子头中RAPID域确定与其发送的preamble码对应的MAC子头；
所述UE获取该MAC子头对应的MAC RAR，如果解析MAC RAR中的指示域T1确定该MAC RAR不携带UE标识，所述UE确定网络侧只收到了preamble码而没有正确接收数据部分，所述UE只解析MAC RAR中的Timing Advance Command、UL Grant、Temporary C-RNTI域，回退到四步随机接入，然后所述UE根据MAC RAR中各域的指示，调整上行定时提前量，获取Temporary C-RNTI，根据UL Grant发送Msg3，并完成后续的随机接入过程；或者
解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，解析全部域，如果UE发送的是长UE ID，所述UE判断MAC RAR中的UE标识是否与UE发送的长UE ID一致，如果一致，所述UE确定完成竞争解决，然后所述UE根据MAC RAR中UL Grant指示的资源，发送后续上行传输；如果不一致，所述UE确定本次随机接入失败，后续重新发起随机接入尝试；或者
解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，解析全部域，如果UE发送的是短UE ID，确定该 MAC RAR不是针对自己的，本次随机接入失败，后续重新发起随机接入尝试；或者
如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，解析全部域，如果UE发送的是长UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续重新发起随机接入尝试；或者
如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，解析全部域，如果UE发送的是短UE ID，UE判断MAC RAR中的UE标识是否与UE发送的短UE ID一致，如果一致，UE确定完成竞争解决，然后UE根据MAC RAR中UL Grant指示的资源，发送后续上行传输；如果不一致，确定本次随机接入失败，后续重新发起随机接入尝试。
可选地，所述MAC子头包含preamble ID和长度指示域L，该长度指示域L用于指示对应MAC RAR的长度或MAC RAR类型。
可选地，MAC RAR类型包含以下任一项或多项：
四步随机接入MAC RAR格式1：适用于UE发起四步竞争随机接入的场景；
四步随机接入MAC RAR格式2：适用于UE发起四步非竞争随机接入的场景；
四步随机接入MAC RAR格式3：适用于UE发起四步非竞争随机接入，且网络侧确定UE只需进行同步，不需发送上行数据的场景；
两步随机接入MAC RAR格式1：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧需要UE进行上行同步校准；
两步随机接入MAC RAR格式2：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准；
两步随机接入MAC RAR格式3：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准；
两步随机接入MAC RAR格式4：随机接入请求中携带的是inactive UE ID， 网络侧只是确认收到随机接入请求中的数据，不需要UE进入连接态；
两步随机接入MAC RAR格式5：随机接入请求中携带的是连接态UE的C-RNTI，网络侧需要UE进行上行同步校准；
两步随机接入MAC RAR格式6：随机接入请求中携带的是连接态UE的C-RNTI，网络侧不需要UE进行上行同步校准；
两步随机接入MAC RAR格式7：随机接入请求中携带的是连接态UE的C-RNTI，网络侧确认随机接入请求中的数据内容接收正确，确定UE不需要后续上行传输，网络侧不分配UL Grant。
可选地，所述UE发送随机接入请求，包括：
所述UE发送随机接入请求preamble码，不发送携带UE标识的信息；
所述UE接收随机接入响应，包括：
所述UE接收随机接入响应，根据MAC子头中RAPID域确定与发送的preamble码对应的MAC子头，解析该MAC子头中的L域确定后续MAC RAR长度或MAC RAR类型；
如果L域指示的是两步随机接入的MAC RAR类型，所述UE确定该随机接入响应不是针对自己的，随机接入失败，所述UE后续发起新的随机接入尝试；
如果L域指示的是四步随机接入的MAC RAR类型，所述UE获取MAC RAR，所述UE根据MAC RAR各域指示完成所需的后续随机接入过程。
可选地，所述UE发送随机接入请求，包括：
所述UE发送随机接入请求，包括preamble码和UE标识；
所述UE接收随机接入响应，包括：
所述UE接收随机接入响应，根据MAC子头中RAPID域确定与发送的preamble码对应的MAC子头，解析该MAC子头中的L域确定后续MAC RAR类型；
如果的MAC RAR类型是四步随机接入RAR，所述UE确定网络侧没有正确接收到随机接入请求中的数据部分，回退到四步随机接入过程，根据MAC RAR指示发送Msg3，并接收下行传输Msg4，完成竞争解决；
如果MAC RAR类型是两步随机接入RAR，则根据L域指示的不同MAC RAR类型进行如下处理：
如果格式类型为两步随机接入MAC RAR格式1，所述UE在随机接入请求中携带的是长UE ID，且该MAC RAR中的UE标识与随机接入请求中的长UE ID一致，认为竞争解决成功，所述UE根据MAC RAR中的指示进行上行同步定时校准、发送上行数据、应用C-RNTI；如果UE在随机接入请求中发送的是短UE ID或该MAC RAR中的UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者
如果格式类型为两步随机接入MAC RAR格式2，所述UE如果在随机接入请求中携带的是长UE ID，且该MAC RAR中UE标识与随机接入请求中的长UE ID一致，认为竞争解决成功，所述UE根据MAC RAR中的指示发送上行数据、应用C-RNTI；如果UE在随机接入请求中发送的是短UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，所述UE后续重新发起随机接入尝试；或者
如果格式类型为两步随机接入MAC RAR格式3，所述UE如果在随机接入请求中携带的是长UE ID，且该MAC RAR中UE标识与随机接入请求中的长UE ID一致，认为竞争解决成功，所述UE根据MAC RAR中的指示应用C-RNTI；如果所述UE在随机接入请求中发送的是短UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，所述UE后续重新发起随机接入尝试；或者
如果格式类型为两步随机接入MAC RAR格式4，UE如果在随机接入请求中携带的是长UE ID，且该MAC RAR中UE标识与随机接入请求中的长UE ID一致，认为竞争解决成功，根据MAC RAR中的应用C-RNTI，随后接收携带该C-RNTI的PDCCH调度命令，并根据该调度命令发送上行传输；如果UE在随机接入请求中发送的是短UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，所述UE后续重新发起随机接入尝试；或者
如果格式类型为两步随机接入MAC RAR格式5，UE如果在随机接入请求中携带的是短UE ID，且该MAC RAR中UE标识与随机接入请求中短UE ID的一致，认为竞争解决成功，根据MAC RAR中的指示进行上行同步定时校准、发送上行数据；如果UE在随机接入请求中发送的是长UE ID或该MAC RAR中 UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，所述UE后续重新发起随机接入尝试；或者
如果格式类型为两步随机接入MAC RAR格式6-，UE如果在随机接入请求中携带的是短UE ID，且该MAC RAR中UE标识与随机接入请求中的短UE ID一致，认为竞争解决成功，根据MAC RAR中的指示发送上行数据；如果UE在随机接入请求中发送的是长UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，所述UE后续重新发起随机接入尝试；或者
如果格式类型为两步随机接入MAC RAR格式7，UE如果在随机接入请求中携带的是短UE ID，且该MAC RAR中的UE标识与随机接入请求中的短UE ID一致，认为竞争解决成功，随后监听携带该UE C-RNTI的PDCCH调度命令，如果接收到调度上行传输的PDCCH调度命令，根据该调度命令发送上行传输；如果UE在随机接入请求中发送的是长UE ID或该MAC RAR中的UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，所述UE后续重新发起随机接入尝试。
依据本公开实施例的第二个方面，还提供了一种随机接入响应方法，包括：
网络侧接收终端UE发送的随机接入请求，随机接入请求中携带包含UE标识的信息；
所述网络侧根据随机接入请求自适应生成随机接入响应，并将所述随机接入响应发送给UE，如果随机接入请求中携带包含UE标识的信息，按照两步随机接入过程，在随机接入响应中包含该UE标识，如果随机接入请求中未携带包含UE标识的信息，按照四步随机接入生成随机接入响应。
可选地，所述随机接入响应采用MAC PDU发送，该MAC PDU中包含MAC头和媒体接入控制层随机接入响应MAC RAR，MAC头包含多个MAC子头，每个MAC子头中包含一个RAPID，对应随机接入请求中的preamble码，每个MAC子头与一个MAC RAR对应，携带UE标识的随机接入响应MAC RAR和不携带UE标识的随机接入响应MAC RAR可以复用到一个MAC PDU中。
可选地，对于四步随机接入和两步随机接入，以及两步随机接入的不同 随机接入场景，采用相同长度的MAC RAR，所述MAC RAR长度固定为能包含最大UE ID长度和Temporary C-RNTI，或同时能包含UL Grant。
可选地，所述MAC RAR包含以下任一项或多项：
T1：指示后续为四步随机接入的MAC RAR或者两步随机接入的MAC RAR；
T2：只在两步随机接入的MAC RAR中出现，用于指示是长UE ID或者为短UE ID；
Timing Advance Command：上行定时提前量；
UL Grant：后续上行传输的资源分配；
Temporary C-RNTI：竞争解决完成后转换为给UE分配的C-RNTI；
Contention Resolution Identity：对应两步随机接入请求中包含的UE标识的信息；
R：预留比特。
可选地，所述MAC RAR中包含所有可能的域，每个域的长度都为可能长度的最大值，每个域的长度都是固定的，如果随机接入响应中不需要该域，则该域实际为预留bit，填充协议规定的值或由网络侧确定填充的值。
可选地，所述网络侧接收UE发送的随机接入请求，包括：
所述网络侧接收随机接入请求，所述随机接入请求包含preamble码，不发送携带UE标识的信息；
所述网络侧根据随机接入请求自适应生成随机接入响应，包括：
所述网络侧发送随机接入响应，所述随机接入响应中包括根据所述preamble码为UE配置的上行定时提前量、上行传输资源和Temporary C-RNTI。
可选地，所述网络侧接收UE发送的随机接入请求，包括：
所述网络侧接收随机接入请求，所述随机接入请求包含preamble码或者包含preamble码和数据部分；
所述网络侧根据随机接入请求自适应生成随机接入响应，包括：
所述网络侧根据接收到的随机接入请求，生成对应的MAC RAR并发送给UE。
可选地，如果生成MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，所述网络侧发送携带Temporary  C-RNTI的PDCCH调度命令，为UE分配后续上行传输资源。
可选地，所述MAC子头包含preamble ID和长度指示域L，该长度指示域用于指示对应MAC RAR的长度或类型。
可选地，MAC RAR类型包含以下任一项或多项：
四步随机接入MAC RAR格式1：适用于UE发起四步竞争随机接入的场景；
四步随机接入MAC RAR格式2：适用于UE发起四步非竞争随机接入的场景；
四步随机接入MAC RAR格式3：适用于UE发起四步非竞争随机接入，且网络侧确定UE只需进行同步，不需发送上行数据的场景；
两步随机接入MAC RAR格式1：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧需要UE进行上行同步校准；
两步随机接入MAC RAR格式2：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准；
两步随机接入MAC RAR格式3：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准；
两步随机接入MAC RAR格式4：随机接入请求中携带的是inactive UE ID，网络侧只是确认收到随机接入请求中的数据，不需要UE进入连接态；
两步随机接入MAC RAR格式5：随机接入请求中携带的是连接态UE的C-RNTI，网络侧需要UE进行上行同步校准；
两步随机接入MAC RAR格式6：随机接入请求中携带的是连接态UE的C-RNTI，网络侧不需要UE进行上行同步校准；
两步随机接入MAC RAR格式7：随机接入请求中携带的是连接态UE的C-RNTI，网络侧确认随机接入请求中的数据内容接收正确，确定UE不需要后续上行传输，网络侧不分配UL Grant。
依据本公开实施例的第三个方面，还提供了一种终端，包括：
发送模块，用于发送随机接入请求，所述随机接入请求中携带包含UE标识的信息；
第一处理模块，用于接收随机接入响应，如果随机接入响应中携带的UE标识与随机接入请求中的UE标识一致，完成竞争解决；如果随机接入响应中携带的UE标识与随机接入请求中的UE标识不一致，则所述UE确定本次随机接入失败，重新发起随机接入尝试；如果随机接入响应中未携带UE标识，则所述UE回退到随机接入请求中不携带UE标识信息的随机接入过程；
其中，所述随机接入响应是网络侧根据随机接入请求自适应生成的；
随机接入请求中携带UE标识的随机接入又称为两步随机接入，随机接入请求中不携带UE标识的随机接入又称为四步随机接入。
可选地，所述随机接入响应采用MAC PDU发送，该MAC PDU中包含MAC头和MAC RAR，MAC头包含多个MAC子头，每个MAC子头中包含一个RAPID，对应随机接入请求中的preamble码，每个MAC子头与一个MAC RAR对应，携带UE标识的随机接入响应MAC RAR和不携带UE标识的随机接入响应MAC RAR可以复用到一个MAC PDU中。
可选地，对于四步随机接入和两步随机接入，以及两步随机接入的不同随机接入场景，采用相同长度的MAC RAR，所述MAC RAR长度固定为能包含最大UE标识长度和Temporary C-RNTI，或同时能包含UL Grant。
可选地，所述MAC RAR包含以下任一项或多项：
T1：指示后续为四步随机接入的MAC RAR或者两步随机接入的MAC RAR；
T2：只在两步随机接入的MAC RAR中出现，用于指示是长UE ID或者为短UE ID；
Timing Advance Command：上行定时提前量；
UL Grant：后续上行传输的资源分配；
Temporary C-RNTI：竞争解决完成后转换为给UE分配的C-RNTI；
Contention Resolution Identity：对应两步随机接入的随机接入请求中包含的UE标识的信息；
R：预留比特。
可选地，所述MAC RAR中包含所有可能的域，每个域的长度都为可能长度的最大值，每个域的长度都是固定的，如果随机接入响应中不需要该域，则该域实际为预留bit，填充协议规定的值或由网络侧确定填充的值。
可选地，所述发送模块进一步用于：发送随机接入请求preamble码，不发送携带UE标识的信息；
所述第一处理模块进一步用于：接收随机接入响应，根据MAC子头中RAPID域确定与发送的preamble码对应的MAC子头；所述UE获取该MAC子头对应的MAC RAR，如果解析MAC RAR中的指示域确定该MAC RAR不携带UE标识，读取MAC RAR中的后续域，根据各域的指示进行相关操作，完成后续随机接入过程；如果解析MAC RAR中的指示域确定该MAC RAR携带UE标识，确定随机接入失败，后续发起新的随机接入尝试。
可选地，所述发送模块进一步用于：发送随机接入请求，包括preamble码和包含UE标识的信息；
所述第一处理模块进一步用于：接收随机接入响应，根据MAC子头中RAPID域确定与发送的preamble码对应的MAC子头；
获取该MAC子头对应的MAC RAR，如果解析MAC RAR中的指示域T1确定该MACRAR不携带UE标识，确定网络侧只收到了preamble码而没有正确接收数据部分，读取MAC RAR中的后续域，回退到四步随机接入，按照四步随机接入过程解析MAC RAR中各域，然后根据MAC RAR中各域的指示，完成后续的随机接入过程；或者
如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，如果UE发送的是长UE ID，判断MAC RAR中的UE标识是否与UE发送的长UE ID一致，如果一致，确定完成竞争解决，接收随后网络侧发送的带Temporary C-RNTI的PDCCH调度命令，根据该调度命令发送上行传输；如果不一致，所述UE确定本次随机接入失败，后续重新发起随机接入尝试；或者
如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，如果UE发送的是短UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续重新发起随机接入尝试；或者
如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，如果UE发送的是长UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续重新发起随机接入尝试；或者
如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，如果UE发送的是短UE ID，所述UE判断MAC RAR中的UE标识是否与UE发送的短UE ID一致，如果一致，确定完成竞争解决，解析MAC RAR中的UL Grant，根据MAC RAR中UL Grant指示的资源，发送后续上行传输；如果不一致，所述UE确定本次随机接入失败，后续重新发起随机接入尝试。
可选地，所述发送模块进一步用于：发送随机接入请求，包括preamble码和包含UE ID标识的信息；
所述第一处理模块进一步用于：接收随机接入响应，根据MAC子头中RAPID域确定与其发送的preamble码对应的MAC子头；
获取该MAC子头对应的MAC RAR，如果解析MAC RAR中的指示域T1确定该MAC RAR不携带UE标识，确定网络侧只收到了preamble码而没有正确接收数据部分，只解析MAC RAR中的Timing Advance Command、UL Grant、Temporary C-RNTI域，回退到四步随机接入，然后所述UE根据MAC RAR中各域的指示，调整上行定时提前量，获取Temporary C-RNTI，根据UL Grant发送Msg3，并完成后续的随机接入过程；或者
解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，解析全部域，如果UE发送的是长UE ID，所述UE判断MAC RAR中的UE标识是否与UE发送的长UE ID一致，如果一致，确定完成竞争解决，然后根据MAC RAR中UL Grant指示的资源，发送后续上行传输；如果不一致，所述UE确定本次随机接入失败，后续重新发起随机接入尝试；或者
解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，解析全部域，如果UE发送的是短UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续重新发起随机接入尝试；或者
如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，解析全部域，如果UE发送的是长UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续重新发起随机接入尝试；或者
如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，解析全部域，如果UE发送的是短UE ID，判断MAC RAR中的UE标识是否与UE发送的短UE ID一致，如果一致，确定完成竞争解决，然后根据MAC RAR中UL Grant指示的资源，发送后续上行传输；如果不一致，确定本次随机接入失败，后续重新发起随机接入尝试。
可选地，所述MAC子头包含preamble ID和长度指示域L，该长度指示域L用于指示对应MAC RAR的长度或MAC RAR类型。
可选地，MAC RAR类型包含以下任一项或多项：
四步随机接入MAC RAR格式1：适用于UE发起四步竞争随机接入的场景；
四步随机接入MAC RAR格式2：适用于UE发起四步非竞争随机接入的场景；
四步随机接入MAC RAR格式3：适用于UE发起四步非竞争随机接入，且网络侧确定UE只需进行同步，不需发送上行数据的场景；
两步随机接入MAC RAR格式1：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧需要UE进行上行同步校准；
两步随机接入MAC RAR格式2：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准；
两步随机接入MAC RAR格式3：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准；
两步随机接入MAC RAR格式4：随机接入请求中携带的是inactive UE ID，网络侧只是确认收到随机接入请求中的数据，不需要UE进入连接态；
两步随机接入MAC RAR格式5：随机接入请求中携带的是连接态UE的C-RNTI，网络侧需要UE进行上行同步校准；
两步随机接入MAC RAR格式6：随机接入请求中携带的是连接态UE的C-RNTI，网络侧不需要UE进行上行同步校准；
两步随机接入MAC RAR格式7：随机接入请求中携带的是连接态UE的C-RNTI，网络侧确认随机接入请求中的数据内容接收正确，确定UE不需要后 续上行传输，网络侧不分配UL Grant。
可选地，所述发送模块进一步用于：发送随机接入请求preamble码，不发送携带UE标识的信息；
所述第一处理模块进一步用于：接收随机接入响应，根据MAC子头中RAPID域确定与发送的preamble码对应的MAC子头，解析该MAC子头中的L域确定后续MAC RAR长度或MAC RAR类型；
如果L域指示的是两步随机接入的MAC RAR类型，确定该随机接入响应不是针对自己的，随机接入失败，后续发起新的随机接入尝试；
如果L域指示的是四步随机接入的MAC RAR类型，获取MAC RAR，根据MAC RAR各域指示完成所需的后续随机接入过程。
可选地，所述发送模块进一步用于：发送随机接入请求，包括preamble码和UE标识；
所述第一处理模块进一步用于：接收随机接入响应，根据MAC子头中RAPID域确定与发送的preamble码对应的MAC子头，解析该MAC子头中的L域确定后续MAC RAR类型；
如果的MAC RAR类型是四步随机接入RAR，确定网络侧没有正确接收到随机接入请求中的数据部分，回退到四步随机接入过程，根据MAC RAR指示发送Msg3，并接收下行传输Msg4，完成竞争解决；
如果MAC RAR类型是两步随机接入RAR，则根据L域指示的不同MAC RAR类型进行如下处理：
如果格式类型为两步随机接入MAC RAR格式1，在随机接入请求中携带的是长UE ID，且该MAC RAR中的UE标识与随机接入请求中的长UE ID一致，认为竞争解决成功，根据MAC RAR中的指示进行上行同步定时校准、发送上行数据、应用C-RNTI；如果UE在随机接入请求中发送的是短UE ID或该MAC RAR中的UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者
如果格式类型为两步随机接入MAC RAR格式2，如果在随机接入请求中携带的是长UE ID，且该MAC RAR中UE标识与随机接入请求中的长UE ID一致，认为竞争解决成功，根据MAC RAR中的指示发送上行数据、应用C-RNTI； 如果UE在随机接入请求中发送的是短UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者
如果格式类型为两步随机接入MAC RAR格式3，如果在随机接入请求中携带的是长UE ID，且该MAC RAR中UE标识与随机接入请求中的长UE ID一致，认为竞争解决成功，根据MAC RAR中的指示应用C-RNTI；如果所述UE在随机接入请求中发送的是短UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者
如果格式类型为两步随机接入MAC RAR格式4，如果在随机接入请求中携带的是长UE ID，且该MAC RAR中UE标识与随机接入请求中的长UE ID一致，认为竞争解决成功，根据MAC RAR中的应用C-RNTI，随后接收携带该C-RNTI的PDCCH调度命令，并根据该调度命令发送上行传输；如果UE在随机接入请求中发送的是短UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者
如果格式类型为两步随机接入MAC RAR格式5，如果在随机接入请求中携带的是短UE ID，且该MAC RAR中UE标识与随机接入请求中短UE ID的一致，认为竞争解决成功，根据MAC RAR中的指示进行上行同步定时校准、发送上行数据；如果UE在随机接入请求中发送的是长UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者
如果格式类型为两步随机接入MAC RAR格式6，如果在随机接入请求中携带的是短UE ID，且该MAC RAR中UE标识与随机接入请求中的短UE ID一致，认为竞争解决成功，根据MAC RAR中的指示发送上行数据；如果UE在随机接入请求中发送的是长UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者
如果格式类型为两步随机接入MAC RAR格式7，如果在随机接入请求中携带的是短UE ID，且该MAC RAR中的UE标识与随机接入请求中的短UE ID一致，认为竞争解决成功，随后监听携带该UE C-RNTI的PDCCH调度命令，如果接收到调度上行传输的PDCCH调度命令，根据该调度命令发送上行传输； 如果UE在随机接入请求中发送的是长UE ID或该MAC RAR中的UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试。
依据本公开实施例的第四个方面，还提供了一种网络侧设备，包括：
接收模块，用于接收终端UE发送的随机接入请求，随机接入请求中携带包含UE标识的信息；
第二处理模块，用于根据随机接入请求自适应生成随机接入响应，并将所述随机接入响应发送给UE，如果随机接入请求中携带包含UE标识的信息，按照两步随机接入过程，在随机接入响应中包含该UE ID信息，如果随机接入请求中未携带包含UE标识的信息，按照四步随机接入生成随机接入响应。
可选地，所述随机接入响应采用MAC PDU发送，该MAC PDU中包含MAC头和媒体接入控制层随机接入响应MAC RAR，MAC头包含多个MAC子头，每个MAC子头中包含一个RAPID，对应随机接入请求中的preamble码，每个MAC子头与一个MAC RAR对应，携带UE标识的随机接入响应和不携带UE标识的随机接入响应MAC RAR可以复用到一个MAC PDU中。
可选地，对于四步随机接入和两步随机接入，以及两步随机接入的不同随机接入场景采用相同长度的MAC RAR，所述MAC RAR长度固定为能包含最大UE ID长度和Temporary C-RNTI，或同时能包含UL Grant。
可选地，所述MAC RAR包含以下任一项或多项：
T1：指示后续为四步随机接入的MAC RAR或者两步随机接入的MAC RAR；
T2：只在两步随机接入的MAC RAR中出现，用于指示是长UE ID或者为短UE ID；
Timing Advance Command：上行定时提前量；
UL Grant：后续上行传输的资源分配；
Temporary C-RNTI：竞争解决完成后转换为给UE分配的C-RNTI；
Contention Resolution Identity：对应两步随机接入请求中包含的UE标识的信息；
R：预留比特。
可选地，所述MAC RAR中包含所有可能的域，每个域的长度都为可能长 度的最大值，每个域的长度都是固定的，如果随机接入响应中不需要该域，则该域实际为预留bit，填充协议规定的值或由网络侧确定填充的值。
可选地，所述接收模块进一步用于：接收随机接入请求，所述随机接入请求包含preamble码，不发送携带UE标识的信息；
所述第二处理模块进一步用于：发送随机接入响应，所述随机接入响应中包括根据所述preamble码为UE配置的上行定时提前量、上行传输资源和Temporary C-RNTI。
可选地，所述接收模块进一步用于：接收随机接入请求，所述随机接入请求包含preamble码或者包含preamble码和数据部分；
所述处理模块进一步用于：根据接收到的随机接入请求，生成对应的MAC RAR并发送给UE。
可选地，如果生成MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，所述网络侧发送携带Temporary C-RNTI的PDCCH调度命令，为UE分配后续上行传输资源。
可选地，所述MAC子头包含preamble ID和长度指示域L，该长度指示域用于指示对应MAC RAR的长度或类型。
可选地，MAC RAR类型包含以下任一项或多项：
四步随机接入MAC RAR格式1：适用于UE发起四步竞争随机接入的场景；
四步随机接入MAC RAR格式2：适用于UE发起四步非竞争随机接入的场景；
四步随机接入MAC RAR格式3：适用于UE发起四步非竞争随机接入，且网络侧确定UE只需进行同步，不需发送上行数据的场景；
两步随机接入MAC RAR格式1：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧需要UE进行上行同步校准；
两步随机接入MAC RAR格式2：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准；
两步随机接入MAC RAR格式3：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络 侧不需要UE进行上行同步校准；
两步随机接入MAC RAR格式4：随机接入请求中携带的是inactive UE ID，网络侧只是确认收到随机接入请求中的数据，不需要UE进入连接态；
两步随机接入MAC RAR格式5：随机接入请求中携带的是连接态UE的C-RNTI，网络侧需要UE进行上行同步校准；
两步随机接入MAC RAR格式6：随机接入请求中携带的是连接态UE的C-RNTI，网络侧不需要UE进行上行同步校准；
两步随机接入MAC RAR格式7：随机接入请求中携带的是连接态UE的C-RNTI，网络侧确认随机接入请求中的数据内容接收正确，确定UE不需要后续上行传输，网络侧不分配UL Grant。
依据本公开实施例的第五个方面，还提供了一种终端，包括处理器、收发机和存储器；
其中，所述处理器用于读取所述存储器中的程序，执行下列过程：
发送随机接入请求，所述随机接入请求中携带包含UE标识的信息；
接收随机接入响应，如果随机接入响应中携带的UE标识与随机接入请求中的UE标识一致，完成竞争解决；如果随机接入响应中携带的UE标识与随机接入请求中的UE标识不一致，则所述UE确定本次随机接入失败，重新发起随机接入尝试；如果随机接入响应中未携带UE标识，则所述UE回退到随机接入请求中不携带UE标识信息的随机接入过程；
其中，所述随机接入响应是网络侧根据随机接入请求生成的；
所述收发机用于接收和发送数据；
所述存储器用于保存所述处理器执行操作时所使用的数据。
依据本公开实施例的第六个方面，还提供了一种网络侧设备，包括处理器、收发机和存储器；
其中，所述处理器用于读取所述存储器中的程序，执行下列过程：
接收终端UE发送的随机接入请求，随机接入请求中携带包含UE标识的信息；
根据随机接入请求生成随机接入响应，并将所述随机接入响应发送给UE；
所述收发机用于接收和发送数据；
所述存储器用于保存所述处理器执行操作时所使用的数据。
上述技术方案中的一个技术方案具有如下优点或有益效果：如果随机接入响应中携带的终端(UE)标识与随机接入请求中的UE标识一致，UE完成竞争解决；如果随机接入响应中携带的UE标识与随机接入请求中的UE标识不一致，则UE确定本次随机接入失败，重新发起随机接入尝试；如果随机接入响应中未携带UE标识，则UE回退到随机接入请求中不携带UE标识信息的随机接入过程(四步随机接入，也可称为4-step RA)，既可以保证统一流程，又可使UE在不同随机接入目的和类型情况下得到正确反馈，同时，由于统一流程和自适应MAC RAR的使用，如果UE发起两步随机接入，在随机接入响应中没有收到期待反馈，还可能回退到四步随机接入。
附图说明
图1为包含随机接入码编号的MAC子头的示意图；
图2为MAC RAR的示意图；
图3为竞争随机接入过程的示意图；
图4为非竞争随机接入过程的示意图；
图5为2-step RA的示意图；
图6为本公开一些实施例中终端侧的随机接入响应方法的流程示意图；
图7为本公开一些实施例中网络侧的随机接入响应方法的流程示意图；
图8为本公开一些实施例中随机接入响应MAC PDU格式的示意图；
图9为本公开一些实施例中与固定长度MAC RAR对应的MAC子头的示意图；
图10为本公开一些实施例中与可变长度MAC RAR对应的MAC子头的示意图；
图11a为本公开一些实施例中4-step MAC RAR的示意图；
图11b为本公开一些实施例中长UE ID的2-step MAC RAR的示意图；
图11c为本公开一些实施例中短UE ID的2-step MAC RAR的示意图；
图12为本公开一些实施例中固定长度MAC RAR的示意图；
图13a～图13c为本公开一些实施例中4-step RA MAC RAR格式的示意图；
图13d～图13j为本公开一些实施例中2-step RA MAC RAR格式的示意图；
图14a为本公开一些实施例中MAC子头的示意图；
图14b～图14d为本公开一些实施例中MAC RAR的示意图；
图15a为本公开一些实施例中MAC子头的示意图；
图15b为本公开一些实施例中MAC RAR的示意图；
图16为本公开一些实施例中与可变长度MAC RAR对应的MAC子头；
图17为本公开一些实施例中终端的结构框图；
图18为本公开一些实施例中网络侧设备的结构框图。
具体实施方式
下面将参照附图更详细地描述本公开的示例性实施例。虽然附图中显示了本公开的示例性实施例，然而应当理解，可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本公开，并且能够将本公开的范围完整的传达给本领域的技术人员。
参见图6，图中示出了终端侧的随机接入响应方法的流程，具体步骤如下：
步骤601、UE发送随机接入请求，所述随机接入请求中携带包含UE标识的信息；
步骤602、UE接收随机接入响应，如果随机接入响应中携带的UE标识与随机接入请求中的UE标识一致，完成竞争解决；如果随机接入响应中携带的UE标识与随机接入请求中的UE标识不一致，则UE确定本次随机接入失败，重新发起随机接入尝试；如果随机接入响应中未携带UE标识，则UE回退到随机接入请求中不携带UE标识信息的随机接入过程；其中，随机接入响应是网络侧根据随机接入请求自适应生成的。
在本公开一些实施例中，随机接入请求中携带UE标识的随机接入又称为两步随机接入(2-step RA)，随机接入请求中不携带UE标识的随机接入又称为四步随机接入(4-step RA)。
参见图7，图中示出了网络侧的随机接入响应方法的流程，具体步骤如下：
步骤701、网络侧接收终端UE发送的随机接入请求，随机接入请求中携带包含UE标识的信息；
步骤702、网络侧根据随机接入请求自适应生成随机接入响应，并将所述随机接入响应发送给UE，如果随机接入请求中携带包含UE标识的信息，按照两步随机接入过程，在随机接入响应中包含该UE标识，如果随机接入请求中未携带包含UE标识的信息，按照四步随机接入生成随机接入响应。
本公开一些实施例针对不同的随机接入目的和随机接入类型(四步随机接入与两步随机接入)采用统一过程。即：UE发送随机接入请求(step1)，按统一规则接收随机接入响应(step2)。
随机接入响应采用统一的MAC PDU格式，参见图8，该MAC PDU中包含MAC头和MAC RAR，MAC头可以包含多个MAC子头，每个MAC子头中包含一个RAPID(Random Access Preamble ID)，对应随机接入请求(step1)中的preamble码。每个MAC子头与一个MAC RAR对应，携带UE标识的随机接入响应MAC RAR和不携带UE标识的随机接入响应MAC RAR可以复用到一个MAC PDU中，可完成一个UE的随机接入响应。
本公开一些实施例中，采用自适应的MAC RAR设计，即可以保证统一流程，又可使UE在不同随机接入目的和类型情况下得到正确反馈，同时，由于统一流程和自适应MAC RAR的使用，如果UE发起两步随机接入，在随机接入响应中没有收到期待反馈，还可能回退到四步随机接入。MAC RAR有变长度和固定长度两种设计方式，对应不同的MAC子头设计。下面分别具体说明。
MAC子头设计：MAC子头与MAC RAR一一对应，根据MAC RAR是固定长还是可变长度，有两种不同的MAC子头设计方法。
a)方法1：针对固定长度MAC RAR的MAC子头
如图9所示。其格式与LTE随机接入响应MAC PDU中MAC子头一致，主要包含preamble ID(即RAPID)域，其他bit为必要的与MAC PDU中其他部分配合的指示域。需要说明的是，图9只是示意图，如果5G系统中preamble长度变化，RAPID域所占比特为可能增加，即图9的MAC子头可能占用2byte，MAC子头设计下述方法2中的RAPID域与之相同。
b)方法2：针对可变长度MAC RAR的MAC子头
如图10所示。MAC子头中主要包含两部分：preamble ID(RAPID)和长度指示域L。长度指示域L的长度限制在8bit(即1byte)之内足够，如果L长度 不足8bit，1byte中的其他指示为可设置为预留比特R，图10是L长度为7bit的示例。L域有两种表达方式，一是直接指示对应RAR的长度，例如，针对RAR长度为6byte，L域为0000110；另一种表达方式为指示RAR类型，如果RAR类型可以有N种，L只需要指示RAR为这N种中的哪一个即可。针对变长MAC RAR设计图13a到图13j，有10种MAC RAR长度，L域可对应指示图13a～图13j的格式。图13a～图13j的MAC RAR格式不一定总是可能同时存在，L域需要指示的MAC RAR类型可能更少。
MAC RAR设计
a)方法1：固定长度RAR
固定长度RAR对于4-step RA和2-step RA，以及2-step RA的不同随机接入场景采用相同长度的RAR设计，参见图11a、图11b和图11c。
方法1-1：RAR长度固定为能包含最大UE ID长度和Temporary C-RNTI，针对不同随机接入响应场景，具体的域内容可以不同，但都有比特位指示不同的RAR具体格式。
具体如下几种格式，MAC RAR固定为8byte，最大UE ID长度为46bit，Temporary C-RNTI长度为16bit，UL Grant长度为20bit。实际应用中，各个域的长度可能有变化，如UL Grant长度可能为12bit，则MAC RAR总长度为7byte。各域的说明如下：
T1：指示后续为4-step RA MAC RAR还是2-step RA MAC RAR，例如T＝0表示该MAC RAR不携带UE标识，T＝1表示该MAC RAR携带UE标识，当然可以理解的是在本公开一些实施例中并不具体限定T1的具体值；
T2：只在2-step RA MAC RAR中出现，用于指示后续是长UE ID还是短UE ID，例如T2＝0表示MAC RAR携带的UE标识为长UE ID，T2＝1表示MAC RAR携带的UE标识为短UE ID，当然可以理解的是在本公开一些实施例中并不具体限定T2的具体值；
Timing Advance Command(定时提前量指令)：上行定时提前量；
UL Grant(上行调度授权)：后续上行传输的资源分配，如果没有这个域，后续用带Temporary C-RNTI(该Temporary C-RNTI已转化成C-RNTI)的PDCCH调度上行传输。长度为20bit或12bit，图中以20bit为例说明；
Temporary C-RNTI(临时小区无线网络临时标识)：竞争解决完成后转化为给UE分配的C-RNTI，长度为16bit；
Contention Resolution Identity(竞争解决身份)：对应两步随机接入的随机接入请求中包含的UE标识的信息。长UE ID对应初始接入、连接重建、inactive UE发起随机接入的场景，此时UE ID分别RRC连接建立请求消息、RRC连接重建请求消息、inactive UE ID；短UE ID对应连接态UE发起的随机接入，为C-RNTI。
R：预留比特，可设置为协议规定值或由网络侧自行决定填充。
方法1-2：RAR中包含所有可能的域，每个域的长度都为可能长度的最大值。
可能包含的域有：TAC(跟踪区编码)、UL grant、Temporary C-RNTI、UE ID。其中，Contention Resolution Identity是2-step RA特有的，对于4-step RA为冗余域，其他域如TAC则对2-step RA可能为冗余域。RAR示意图如图12。其中Contention Resolution Identity取最大值6byte。每个域长度都是固定的，如果随机接入响应中本来不需要该域，则该域实际为预留bit，填充协议规定的值或由网络侧自行所需确定填充的值。MAC RAR的第一个比特T1为指示bit，用于指示该MAC RAR是否包含Contention Resolution Identity，例如T1＝0，表示后续是对四步随机接入的响应，Contention Resolution Identity的值可忽略；T1＝1，表示后续是对两步随机接入的响应，Contention Resolution Identity与随机接入请求(step1)的数据域中携带的UE ID相同。指示比特T2进一步指示后续UE ID是短UE ID还是长UE ID，例如T2＝0不是长UE ID，T2＝1表示短UE ID。
b)方法2：可变长度RAR
可变长度RAR表示网络侧可以根据随机接入请求自适应生成最合适长度的MAC RAR，MAC RAR中只需包含必须的域。可变长度MAC RAR可能有以下几种类型。注意这些MAC RAR类型不一定在协议中都存在。图中，T1域可以用于如果MAC子头L域指示的是MAC RAR长度时，区分相同长度MAC RAR格式，如区分图13a和图13g和区分图13g和图13h。但图13c和图13i的MAC RAR长度相同，由于图13c的MAC RAR没有剩余bit用于区分指示，所以如果出现图13c和图13i 格式共存，MAC子头中L域只能用于指示MAC RAR格式类型，不能用于指示MAC RAR长度。下面对每种格式的适用场景进行说明：
4-step RA(四步随机接入)MAC RAR格式1：适用于UE发起4-step(四步)竞争随机接入的场景。
4-step RA MAC RAR格式2：适用于UE发起4-step非竞争随机接入的场景。
4-step RA MAC RAR格式3：适用于UE发起4-step非竞争随机接入，且网络侧确定UE只需进行同步，不需发送上行数据的场景。
2-step RA(两步随机接入)MAC RAR格式1：随机接入请求(step1)中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID(或称resume ID)，网络侧要为UE分配C-RNTI，网络侧需要UE进行上行同步校准(虽然UE本来就处于上行同步状态)。
2-step RA MAC RAR格式2：随机接入请求(step1)中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID(或称resume ID)，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准。
2-step RA MAC RAR格式3：随机接入请求(step1)中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID(或称resume ID)，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准。
2-step RA MAC RAR格式4：随机接入请求(step1)中携带的是inactive UE ID(或称resume ID)，网络侧只是确认收到随机接入请求中的数据，不需要UE进入连接态。
2-step RA MAC RAR格式5：随机接入请求(step1)中携带的是连接态UE的C-RNTI，网络侧需要UE进行上行同步校准。
2-step RA MAC RAR格式6：随机接入请求(step1)中携带的是连接态UE的C-RNTI，网络侧不需要UE进行上行同步校准。
2-step RA MAC RAR格式7：随机接入请求(step1)中携带的是连接态UE的C-RNTI，网络侧确认随机接入请求中的数据内容接收正确，确定UE不需要后续上行传输，因此不分配UL Grant。
需要说明的是：上述MAC PDU格式中的不同域的位置可以不限于图中的所示，不同域位置可以互换，例如包含UE ID的MAC RAR格式中，UE ID可以放在 其他域之前或之后。用于指示的比特位T1、T2等，可以采用相反的取值指示，只要能明确区分指示即可。
本公开一些实施例中，固定长度MAC RAR方法1-1，UE只发送preamble码(四步随机接入)
固定长度MAC RAR方法1-1中，MAC PDU格式包括如下MAC子头(图14a)和MAC RAR(图14b～图14d)。
UE侧：
步骤1：发送随机接入请求preamble码；
步骤2：接收随机接入响应，根据MAC子头中RAPID域确定与自己发送的preamble码编号相同，解读对应的MAC RAR；
步骤3：获取MAC RAR(1)，格式如图14b，如果T1＝0，读取后续域，根据各域的指示进行相关操作，包括上行定时调整、根据UL Grant发送上行数据传输，获取分配的Temporary C-RNTI等，完成后续随机接入过程；如果T1＝1，确定该随机接入响应不是针对自己的，随机接入失败，后续可以发起新的随机接入尝试。
网络侧：
步骤1：接收随机接入请求preamble码；
步骤2：发送随机接入响应，为UE配置上行定时提前量、上行传输资源、Temporary C-RNTI；
步骤3：解读UE后续上行传输等，完成随机接入过程。
本公开一些实施例中，固定长度MAC RAR方法1-1，UE发送preamble码和UE ID(两步随机接入)
MAC PDU格式与上述实施例相同，仍为图14a～图14b。
UE侧：
步骤1：发送随机接入请求，包括preamble码和UE ID以及其他上行传输(如BSR、PHR、上行数据)，该随机接入请求中需要区分UE发送的是长UE ID还是短UE ID，可以用MAC子头中的不同LCID域区分长UE ID还是短UE ID；
步骤2：接收随机接入响应，根据MAC子头中RAPID域确定与自己发送的preamble码编号相同，解读对应的MAC RAR；
步骤3：解析T1，有如下分支：
-3-1：如果T1＝0，获取MAC RAR(1)，格式如图14b，UE确定网络侧只收到了preamble码而没有正确接收数据部分，转到步骤4-1；
-3-2：如果T1＝1，T2＝0，获取MAC RAR(2)，格式如图14c。如果UE在步骤1中发送的是长UE ID，转到步骤4-2；如果UE在步骤1中发送的是短UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续可以重新发起随机接入尝试；
-3-3，如果T1＝1，T2＝1，获取MAC RAR(3)，格式如图14d。如果UE在步骤1中发送的是长UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续可以重新发起随机接入尝试；如果UE在步骤1中发送的是短UE ID，转到步骤4-3。
步骤4：根据步骤3的结果，有如下分支：
-4-1：UE接收MAC RAR(1)中的后续域，回退到四步随机接入，即按照四步随机接入过程，解析MAC RAR(1)中各域，转到步骤5-1；
-4-2：UE接收MAC RAR(2)，确定Contention Resolution Identity中的数值是否与步骤1中发送的UE ID一致，如果一致，UE确定完成竞争解决，转到步骤5-2；如果UE ID不一致，确定本次随机接入失败，后续可以重新发起随机接入尝试；
-4-3：UE接收MAC RAR(3)，确定Contention Resolution Identity中的数值是否与步骤1中发送的UE ID一致，如果一致，UE确定完成竞争解决，解析MAC RAR中的UL Grant，转到步骤5-3；如果UE ID不一致，确定本次随机接入失败，后续可以重新发起随机接入尝试；
步骤5：根据步骤4的结果，有如下分支：
-5-1：UE根据MAC RAR中各域的指示，调整上行定时提前量，获取Temporary C-RNTI，根据UL Grant发送Msg3，并完成后续的随机接入过程；
-5-2：UE接收随后网络侧发送的带Temporary C-RNTI的PDCCH调度命令，根据该调度命令发送上行传输；
-5-3：UE根据MAC RAR中UL Grant指示的资源，发送后续上行传输。
网络侧：
步骤1：接收随机接入请求，该随机接入请求可能是preamble码或preamble码加数据部分；
步骤2：根据接收到的随机接入请求，生成对应的MAC RAR并发送给UE。如果生成MAC RAR(2)，随之发送一条带Temporary C-RNTI的PDCCH调度命令，为UE分配后续上行传输资源；
步骤3：在调度的资源上接收上行传输，如果是四步随机接入，需完成后续的Msg3、Msg4。
本公开一些实施例中，固定长度MAC RAR方法1-2，UE只发送preamble码(四步随机接入)
固定长度MAC RAR方法1-2中，MAC PDU格式包括如下MAC子头(图15a)和MAC RAR(图15b)。
UE侧：
步骤1：发送随机接入请求preamble码；
步骤2：接收随机接入响应，根据MAC子头中RAPID域确定与自己发送的preamble码编号相同，解读对应的MAC RAR；
步骤3：获取MAC RAR，格式如图15b，解析T1＝0，读取后续域，根据各域的指示进行相关操作，包括上行定时调整、根据UL Grant发送上行数据传输，获取分配的Temporary C-RNTI等，完成后续随机接入过程；如果T1＝1，确定该随机接入响应不是针对自己的，随机接入失败，后续可以重新发起随机接入尝试。
网络侧：
步骤1：接收随机接入请求preamble码；
步骤2：发送随机接入响应，为UE配置上行定时提前量、上行传输资源、Temporary C-RNTI；
步骤3：解读UE后续上行传输等，完成随机接入过程。
本公开一些实施例中，固定长度MAC RAR方法1-2，UE发送preamble码和UE ID(两步随机接入)
MAC PDU格式与上述实施例相同，仍为图15a和图15b。
UE侧：
步骤1：发送随机接入请求，包括preamble码和UE ID以及其他上行传输(如BSR、PHR、上行数据)，该随机接入请求中需要区分UE发送的是长UE ID还是短UE ID，可以用MAC子头中的不同LCID域区分长UE ID还是短UE ID；
步骤2：接收随机接入响应，根据MAC子头中RAPID域确定与自己发送的preamble码编号相同，解读对应的MAC RAR；
步骤3：解析T1，有如下分支：
-3-1：如果T1＝0，UE确定网络侧只收到了preamble码而没有正确接收数据部分，转到步骤4-1；
-3-2：如果T1＝1，T2＝0，解析全部域。如果UE在步骤1中发送的是长UE ID，转到步骤4-2；如果UE在步骤1中发送的是短UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续可以重新发起随机接入尝试；
-3-3，如果T1＝1，T2＝1，解析全部域。如果UE在步骤1中发送的是长UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续可以重新发起随机接入尝试；如果UE在步骤1中发送的是短UE ID，转到步骤4-2。
步骤4：根据步骤3的结果，有如下分支：
-4-1：UE只解析MAC RAR中的Timing Advance Command、UL Grant、Temporary C-RNTI域，回退到四步随机接入，即按照四步随机接入过程，转到步骤5-1；
-4-2：UE判断Contention Resolution Identity中的数值是否与步骤1中发送的UE ID一致，如果一致，UE确定完成竞争解决，转到步骤5-2；如果UE ID不一致，确定本次随机接入失败，后续可以重新发起随机接入尝试；
步骤5：根据步骤4的结果，有如下分支：
-5-1：UE根据MAC RAR中各域的指示，调整上行定时提前量，获取Temporary C-RNTI，根据UL Grant发送Msg3，并完成后续的随机接入过程(Msg3、Msg4)；
-5-3：UE根据MAC RAR中UL Grant指示的资源，发送后续上行传输。
网络侧：
步骤1：接收随机接入请求，该随机接入请求可能是preamble码或preamble码加数据部分；
步骤2：根据接收到的随机接入请求，生成对应的MAC RAR并发送给UE；
步骤3：在调度的资源上接收上行传输，如果网络侧认为是四步随机接入，需完成后续的Msg3、Msg4。
本公开一些实施例中，可变长度MAC RAR，UE只发送preamble码(四步随机接入)
随机接入响应MAC PDU中MAC子头格式如图16，可能的MAC RAR格式为图13a～13j。本公开一些实施例中，L与用于指示采用哪种MAC RAR格式，如L＝1表示格式1，L＝10表示格式10实际应用中，10种MAC RAR格式可能不是全都可以共存。
UE侧：
步骤1：发送随机接入请求preamble码；
步骤2：接收随机接入响应，根据MAC子头中RAPID域确定与自己发送的preamble码编号相同，如果相同，解析L域确定后续MAC RAR类型，如果L域指示的是两步随机接入的MAC RAR类型，确定该随机接入响应不是针对自己的，随机接入失败，后续可以发起新的随机接入尝试；如果MAC RAR类型是四步随机接入RAR，进入步骤3。
步骤3：获取MAC RAR，图13a～图13c三种MAC RAR可能不能同时存在，很可能只有图13a这一种MAC RAR。UE根据MAC RAR各域指示完成所需的后续随机接入过程(Msg3、Msg4)。
网络侧：
步骤1：接收随机接入请求preamble码；
步骤2：根据随机接入响应生成随机接入响应，包括正确的MAC子头和MAC RAR；
步骤3：解读UE后续上行传输，完成随机接入过程。
本公开一些实施例中，可变长度MAC RAR，UE发送preamble码和UE ID(两步随机接入)
MAC子头格式如图15，MAC PDU格式如图13a～13j
UE侧：
步骤1：发送随机接入请求，包括preamble码和UE ID以及其他上行传输 (如BSR、PHR、上行数据)，该随机接入请求中需要区分UE发送的是长UE ID还是短UE ID，可以用MAC子头中的不同LCID域区分长UE ID还是短UE ID；
步骤2：接收随机接入响应，接收随机接入响应，根据MAC子头中RAPID域确定与自己发送的preamble码编号相同，如果相同，解析L域确定后续MAC RAR类型。
步骤3：根据L域指示的不同MAC RAR类型，有如下分支：
-如果L域指示的是四步随机接入的MAC RAR类型(图13a)，确定网络侧没有正确接收到随机接入请求中的数据部分，回退到四步随机接入过程，即根据MAC RAR指示发送上行传输(Msg3)，并接收随之而来的下行传输Msg4，完成竞争解决
-如果MAC RAR类型是两步随机接入RAR，进入步骤4。
步骤4：对于两步随机接入MAC RAR，根据L域指示的不同MAC RAR类型，有如下分支：
-接收到两步MAC RAR格式1(图13d)，UE如果在步骤1的随机接入请求中携带的是长UE ID，且该UE ID与随机接入请求中的一致，认为竞争解决成功，根据MAC RAR中的指示进行上行同步定时校准(根据TAC)、根据UL Grant发送上行数据、应用C-RNTI(根据Temporary C-RNTI)；如果UE在随机接入请求中发送的是短UE ID或该UE ID与随机接入请求中的UE ID不一致，认为随机接入失败，后续可以重新发起随机接入尝试。
-接收到两步MAC RAR格式2(图13e)，UE如果在步骤1的随机接入请求中携带的是长UE ID，且该UE ID与随机接入请求中的一致，认为竞争解决成功，根据MAC RAR中的指示发送上行数据(根据UL Grant)、应用C-RNTI(根据Temporary C-RNTI)；如果UE在随机接入请求中发送的是短UE ID或该UE ID与随机接入请求中的UE ID不一致，认为随机接入失败，后续可以重新发起随机接入尝试。
-接收到两步MAC RAR格式3(图13f)，UE如果在步骤1的随机接入请求中携带的是长UE ID，且该UE ID与随机接入请求中的一致，认为竞争解决成功，根据MAC RAR中的指示应用C-RNTI(根据Temporary C-RNTI)，进入步骤5-1；如果UE在随机接入请求中发送的是短UE ID或该UE ID与随机接入请求中的UE  ID不一致，认为随机接入失败，后续可以重新发起随机接入尝试。
-接收到两步MAC RAR格式4(图13g)，UE如果在步骤1的随机接入请求中携带的是长UE ID，且该UE ID与随机接入请求中的一致，认为竞争解决成功，根据MAC RAR中的应用C-RNTI(根据Temporary C-RNTI)，随后接收携带该C-RNTI的PDCCH调度命令，并根据该调度命令发送上行传输；如果UE在随机接入请求中发送的是短UE ID或该UE ID与随机接入请求中的UE ID不一致，认为随机接入失败，后续可以重新发起随机接入尝试。该格式只适用于UE在inactive状态下发送上行传输，不需获取C-RNTI进入连接态的情况。
-接收到两步MAC RAR格式5(图13h)，UE如果在步骤1的随机接入请求中携带的是短UE ID，且该UE ID与随机接入请求中的一致，认为竞争解决成功，根据MAC RAR中的指示进行上行同步定时校准(根据TAC)、根据UL Grant发送上行数据；如果UE在随机接入请求中发送的是长UE ID或该UE ID与随机接入请求中的UE ID不一致，认为随机接入失败，后续可以重新发起随机接入尝试。
-接收到两步MAC RAR格式6(图13i)，UE如果在步骤1的随机接入请求中携带的是短UE ID，且该UE ID与随机接入请求中的一致，认为竞争解决成功，根据MAC RAR中的指示发送上行数据(根据UL Grant)；如果UE在随机接入请求中发送的是长UE ID或该UE ID与随机接入请求中的UE ID不一致，认为随机接入失败，后续可以重新发起随机接入尝试。
-接收到两步MAC RAR格式7(图13j)，UE如果在步骤1的随机接入请求中携带的是短UE ID，且该UE ID与随机接入请求中的一致，认为竞争解决成功，随后监听携带该UE C-RNTI的PDCCH调度命令，如果接收到调度上行传输的PDCCH调度命令，根据该调度命令发送上行传输；如果UE在随机接入请求中发送的是长UE ID或该UE ID与随机接入请求中的UE ID不一致，认为随机接入失败，后续可以重新发起随机接入尝试。该格式主要适用于UE在连接态只发一次上行传输，不需后续传输的情况，网络侧不一定会后续接着发送PDCCH调度命令调度上行传输。
基于同一发明构思，本公开一些实施例中还提供了一种终端，由于该终端解决问题的原理与本公开一些实施例图6中随机接入响应方法相似，因此该终端的实施可以参见方法的实施，重复之处不再敷述。
参见图17，图中示出了一种终端，该终端1700包括：
发送模块1701，用于发送随机接入请求，所述随机接入请求中携带包含UE标识的信息；
第一处理模块1702，用于接收随机接入响应，如果随机接入响应中携带的UE标识与随机接入请求中的UE标识一致，完成竞争解决；如果随机接入响应中携带的UE标识与随机接入请求中的UE标识不一致，则所述UE确定本次随机接入失败，重新发起随机接入尝试；如果随机接入响应中未携带UE标识，则所述UE回退到随机接入请求中不携带UE标识信息的随机接入过程；
其中，所述随机接入响应是网络侧根据随机接入请求自适应生成的；
随机接入请求中携带UE标识的随机接入又称为两步随机接入，随机接入请求中不携带UE标识的随机接入又称为四步随机接入。
在本公开一些实施例中，可选地，所述随机接入响应采用MAC PDU发送，该MAC PDU中包含MAC头和MAC RAR，MAC头包含多个MAC子头，每个MAC子头中包含一个RAPID，对应随机接入请求中的preamble码，每个MAC子头与一个MAC RAR对应，携带UE标识的随机接入响应MAC RAR和不携带UE标识的随机接入响应MAC RAR可以复用到一个MAC PDU中。
在本公开一些实施例中，可选地，对于四步随机接入和两步随机接入，以及两步随机接入的不同随机接入场景，采用相同长度的MAC RAR，所述MAC RAR长度固定为能包含最大UE标识长度和Temporary C-RNTI，或同时能包含UL Grant。
在本公开一些实施例中，可选地，所述MAC RAR包含以下任一项或多项：
T1：指示后续为四步随机接入的MAC RAR或者两步随机接入的MAC RAR；
T2：只在两步随机接入的MAC RAR中出现，用于指示是长UE ID或者为短UE ID；
Timing Advance Command：上行定时提前量；
UL Grant：后续上行传输的资源分配；
Temporary C-RNTI：竞争解决完成后转换为给UE分配的C-RNTI；
Contention Resolution Identity：对应两步随机接入的随机接入请求中包含的UE标识的信息；
R：预留比特。
在本公开一些实施例中，可选地，所述MAC RAR中包含所有可能的域，每个域的长度都为可能长度的最大值，每个域的长度都是固定的，如果随机接入响应中不需要该域，则该域实际为预留bit，填充协议规定的值或由网络侧确定填充的值。
在本公开一些实施例中，可选地，所述发送模块进一步用于：发送随机接入请求preamble码，不发送携带UE标识的信息；
所述第一处理模块进一步用于：接收随机接入响应，根据MAC子头中RAPID域确定与发送的preamble码对应的MAC子头；所述UE获取该MAC子头对应的MAC RAR，如果解析MAC RAR中的指示域确定该MAC RAR不携带UE标识，读取MAC RAR中的后续域，根据各域的指示进行相关操作，完成后续随机接入过程；如果解析MAC RAR中的指示域确定该MAC RAR携带UE标识，确定随机接入失败，后续发起新的随机接入尝试。
在本公开一些实施例中，可选地所述发送模块进一步用于，发送随机接入请求，包括preamble码和包含UE标识的信息；
所述第一处理模块进一步用于：接收随机接入响应，根据MAC子头中RAPID域确定与发送的preamble码对应的MAC子头；
获取该MAC子头对应的MAC RAR，如果解析MAC RAR中的指示域T1确定该MAC RAR不携带UE标识，确定网络侧只收到了preamble码而没有正确接收数据部分，读取MAC RAR中的后续域，回退到四步随机接入，按照四步随机接入过程解析MAC RAR中各域，然后根据MAC RAR中各域的指示，完成后续的随机接入过程；或者
如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，如果UE发送的是长UE ID，判断MAC RAR中的UE标识是否与UE发送的长UE ID一致，如果一致，确定完成竞争解决，接收随后网络侧发送的带Temporary C-RNTI的PDCCH调度命令，根据该调度命令发送上行传输；如果不一致，所述UE确定本次随机接入失败，后续重新发起随机接入尝试；或者
如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2 确定该UE标识为长UE ID，如果UE发送的是短UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续重新发起随机接入尝试；或者
如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，如果UE发送的是长UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续重新发起随机接入尝试；或者
如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，如果UE发送的是短UE ID，所述UE判断MAC RAR中的UE标识是否与UE发送的短UE ID一致，如果一致，确定完成竞争解决，解析MAC RAR中的UL Grant，根据MAC RAR中UL Grant指示的资源，发送后续上行传输；如果不一致，所述UE确定本次随机接入失败，后续重新发起随机接入尝试。
在本公开一些实施例中，可选地，所述发送模块进一步用于：发送随机接入请求，包括preamble码和包含UE ID标识的信息；
所述第一处理模块进一步用于：接收随机接入响应，根据MAC子头中RAPID域确定与其发送的preamble码对应的MAC子头；
获取该MAC子头对应的MAC RAR，如果解析MAC RAR中的指示域T1确定该MAC RAR不携带UE标识，确定网络侧只收到了preamble码而没有正确接收数据部分，只解析MAC RAR中的Timing Advance Command、UL Grant、Temporary C-RNTI域，回退到四步随机接入，然后所述UE根据MAC RAR中各域的指示，调整上行定时提前量，获取Temporary C-RNTI，根据UL Grant发送Msg3，并完成后续的随机接入过程；或者
解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，解析全部域，如果UE发送的是长UE ID，所述UE判断MAC RAR中的UE标识是否与UE发送的长UE ID一致，如果一致，确定完成竞争解决，然后根据MAC RAR中UL Grant指示的资源，发送后续上行传输；如果不一致，所述UE确定本次随机接入失败，后续重新发起随机接入尝试；或者
解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，解析全部域，如果UE发送的是短UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续重新发起随机接入尝试； 或者
如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，解析全部域，如果UE发送的是长UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续重新发起随机接入尝试；或者
如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，解析全部域，如果UE发送的是短UE ID，判断MAC RAR中的UE标识是否与UE发送的短UE ID一致，如果一致，确定完成竞争解决，然后根据MAC RAR中UL Grant指示的资源，发送后续上行传输；如果不一致，确定本次随机接入失败，后续重新发起随机接入尝试。
在本公开一些实施例中，可选地所述MAC子头包含preamble ID和长度指示域L，该长度指示域L用于指示对应MAC RAR的长度或MAC RAR类型。
在本公开一些实施例中，可选地MAC RAR类型包含以下任一项或多项：
四步随机接入(4-step RA)MAC RAR格式1：适用于UE发起四步竞争随机接入的场景；
四步随机接入MAC RAR格式2：适用于UE发起四步非竞争随机接入的场景；
四步随机接入MAC RAR格式3：适用于UE发起四步非竞争随机接入，且网络侧确定UE只需进行同步，不需发送上行数据的场景；
两步随机接入MAC RAR格式1：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧需要UE进行上行同步校准；
两步随机接入(2-step RA)MAC RAR格式2：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准；
两步随机接入MAC RAR格式3：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准；
两步随机接入MAC RAR格式4：随机接入请求中携带的是inactive UE ID，网络侧只是确认收到随机接入请求中的数据，不需要UE进入连接态；
两步随机接入MAC RAR格式5：随机接入请求中携带的是连接态UE的C-RNTI，网络侧需要UE进行上行同步校准；
两步随机接入MAC RAR格式6：随机接入请求中携带的是连接态UE的C-RNTI，网络侧不需要UE进行上行同步校准；
两步随机接入MAC RAR格式7：随机接入请求中携带的是连接态UE的C-RNTI，网络侧确认随机接入请求中的数据内容接收正确，确定UE不需要后续上行传输，网络侧不分配UL Grant。
在本公开一些实施例中，可选地，所述发送模块进一步用于：发送随机接入请求preamble码，不发送携带UE标识的信息；
所述第一处理模块进一步用于：接收随机接入响应，根据MAC子头中RAPID域确定与发送的preamble码对应的MAC子头，解析该MAC子头中的L域确定后续MAC RAR长度或MAC RAR类型；
如果L域指示的是两步随机接入的MAC RAR类型，确定该随机接入响应不是针对自己的，随机接入失败，后续发起新的随机接入尝试；
如果L域指示的是四步随机接入的MAC RAR类型，获取MAC RAR，根据MAC RAR各域指示完成所需的后续随机接入过程。
在本本公开一些实施例中，可选地，所述发送模块进一步用于：发送随机接入请求，包括preamble码和UE标识；
所述第一处理模块进一步用于：接收随机接入响应，根据MAC子头中RAPID域确定与发送的preamble码对应的MAC子头，解析该MAC子头中的L域确定后续MAC RAR类型；
如果的MAC RAR类型是四步随机接入RAR，确定网络侧没有正确接收到随机接入请求中的数据部分，回退到四步随机接入过程，根据MAC RAR指示发送Msg3，并接收下行传输Msg4，完成竞争解决；
如果MAC RAR类型是两步随机接入RAR，则根据L域指示的不同MAC RAR类型进行如下处理：
如果格式类型为两步随机接入MAC RAR格式1，在随机接入请求中携带的是长UE ID，且该MAC RAR中的UE标识与随机接入请求中的长UE ID一致，认为竞争解决成功，根据MAC RAR中的指示进行上行同步定时校准、发送上 行数据、应用C-RNTI；如果UE在随机接入请求中发送的是短UE ID或该MAC RAR中的UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者
如果格式类型为两步随机接入MAC RAR格式2，如果在随机接入请求中携带的是长UE ID，且该MAC RAR中UE标识与随机接入请求中的长UE ID一致，认为竞争解决成功，根据MAC RAR中的指示发送上行数据、应用C-RNTI；如果UE在随机接入请求中发送的是短UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者
如果格式类型为两步随机接入MAC RAR格式3，如果在随机接入请求中携带的是长UE ID，且该MAC RAR中UE标识与随机接入请求中的长UE ID一致，认为竞争解决成功，根据MAC RAR中的指示应用C-RNTI；如果所述UE在随机接入请求中发送的是短UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者
如果格式类型为两步随机接入MAC RAR格式4，如果在随机接入请求中携带的是长UE ID，且该MAC RAR中UE标识与随机接入请求中的长UE ID一致，认为竞争解决成功，根据MAC RAR中的应用C-RNTI，随后接收携带该C-RNTI的PDCCH调度命令，并根据该调度命令发送上行传输；如果UE在随机接入请求中发送的是短UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者
如果格式类型为两步随机接入MAC RAR格式5，如果在随机接入请求中携带的是短UE ID，且该MAC RAR中UE标识与随机接入请求中短UE ID的一致，认为竞争解决成功，根据MAC RAR中的指示进行上行同步定时校准、发送上行数据；如果UE在随机接入请求中发送的是长UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者
如果格式类型为两步随机接入MAC RAR格式6，如果在随机接入请求中携带的是短UE ID，且该MAC RAR中UE标识与随机接入请求中的短UE ID一致，认为竞争解决成功，根据MAC RAR中的指示发送上行数据；如果UE在随 机接入请求中发送的是长UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者
如果格式类型为两步随机接入MAC RAR格式7，如果在随机接入请求中携带的是短UE ID，且该MAC RAR中的UE标识与随机接入请求中的短UE ID一致，认为竞争解决成功，随后监听携带该UE C-RNTI的PDCCH调度命令，如果接收到调度上行传输的PDCCH调度命令，根据该调度命令发送上行传输；如果UE在随机接入请求中发送的是长UE ID或该MAC RAR中的UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试。
基于同一发明构思，本公开一些实施例中还提供了一种网络侧设备，由于该网络侧设备解决问题的原理与本公开一些实施例图7中竞争随机接入的方法相似，因此该网络侧设备的实施可以参见方法的实施，重复之处不再敷述。
参见图18，图中示出了一种网络侧设备，该网络侧设备1800包括：
接收模块1801，用于接收终端UE发送的随机接入请求，随机接入请求中携带包含UE标识的信息；
第二处理模块1802，用于根据随机接入请求自适应生成随机接入响应，并将所述随机接入响应发送给UE，如果随机接入请求中携带包含UE标识的信息，按照两步随机接入过程，在随机接入响应中包含该UE ID信息，如果随机接入请求中未携带包含UE标识的信息，按照四步随机接入生成随机接入响应。
在本公开一些实施例中，可选地，所述随机接入响应采用MAC PDU发送，该MAC PDU中包含MAC头和媒体接入控制层随机接入响应MAC RAR，MAC头包含多个MAC子头，每个MAC子头中包含一个RAPID，对应随机接入请求中的preamble码，每个MAC子头与一个MAC RAR对应，携带UE标识的随机接入响应和不携带UE标识的随机接入响应MAC RAR可以复用到一个MAC PDU中。
在本公开一些实施例中，可选地，对于四步随机接入和两步随机接入，以及两步随机接入的不同随机接入场景采用相同长度的MAC RAR，所述MAC RAR长度固定为能包含最大UE ID长度和Temporary C-RNTI，或同时能包含 UL Grant。
在本公开一些实施例中，可选地，所述MAC RAR包含以下任一项或多项：
T1：指示后续为四步随机接入的MAC RAR或者两步随机接入的MAC RAR；
T2：只在两步随机接入的MAC RAR中出现，用于指示是长UE ID或者为短UE ID；
Timing Advance Command：上行定时提前量；
UL Grant：后续上行传输的资源分配；
Temporary C-RNTI：竞争解决完成后转换为给UE分配的C-RNTI；
Contention Resolution Identity：对应两步随机接入请求中包含的UE标识的信息；
R：预留比特。
在本公开一些实施例中，可选地，所述MAC RAR中包含所有可能的域，每个域的长度都为可能长度的最大值，每个域的长度都是固定的，如果随机接入响应中不需要该域，则该域实际为预留bit，填充协议规定的值或由网络侧确定填充的值。
在本公开一些实施例中，可选地，所述接收模块进一步用于：接收随机接入请求，所述随机接入请求包含preamble码，不发送携带UE标识的信息；
所述第二处理模块进一步用于：发送随机接入响应，所述随机接入响应中包括根据所述preamble码为UE配置的上行定时提前量、上行传输资源和Temporary C-RNTI。
在本公开一些实施例中，可选地，所述接收模块进一步用于：
接收随机接入请求，所述随机接入请求包含preamble码或者包含preamble码和数据部分；
所述处理模块进一步用于：根据接收到的随机接入请求，生成对应的MAC RAR并发送给UE。
在本公开一些实施例中，可选地，如果生成MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，所述网络侧发送携带Temporary C-RNTI的PDCCH调度命令，为UE分配后续上行传输资源。
在本公开一些实施例中，可选地，所述MAC子头包含preamble ID和长度指示域L，该长度指示域用于指示对应MAC RAR的长度或类型。
在本公开一些实施例中，可选地，MAC RAR类型包含以下任一项或多项：
四步随机接入MAC RAR格式1：适用于UE发起四步竞争随机接入的场景；
四步随机接入MAC RAR格式2：适用于UE发起四步非竞争随机接入的场景；
四步随机接入MAC RAR格式3：适用于UE发起四步非竞争随机接入，且网络侧确定UE只需进行同步，不需发送上行数据的场景；
两步随机接入MAC RAR格式1：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧需要UE进行上行同步校准；
两步随机接入MAC RAR格式2：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准；
两步随机接入MAC RAR格式3：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准；
两步随机接入MAC RAR格式4：随机接入请求中携带的是inactive UE ID，网络侧只是确认收到随机接入请求中的数据，不需要UE进入连接态；
两步随机接入MAC RAR格式5：随机接入请求中携带的是连接态UE的C-RNTI，网络侧需要UE进行上行同步校准；
两步随机接入MAC RAR格式6：随机接入请求中携带的是连接态UE的C-RNTI，网络侧不需要UE进行上行同步校准；
两步随机接入MAC RAR格式7：随机接入请求中携带的是连接态UE的C-RNTI，网络侧确认随机接入请求中的数据内容接收正确，确定UE不需要后续上行传输，网络侧不分配UL Grant。
如果随机接入响应中携带的终端(UE)标识与随机接入请求中的UE标识一致，UE完成竞争解决；如果随机接入响应中携带的UE标识与随机接入请求中的UE标识不一致，则UE确定本次随机接入失败，重新发起随机接入尝试；如果随机接入响应中未携带UE标识，则UE回退到随机接入请求中不携 带UE标识信息的随机接入过程(四步随机接入，也可称为4-step RA)，既可以保证统一流程，又可使UE在不同随机接入目的和类型情况下得到正确反馈，同时，由于统一流程和自适应MAC RAR的使用，如果UE发起两步随机接入，在随机接入响应中没有收到期待反馈，还可能回退到四步随机接入。
应理解，说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本公开的至少一个实施例中。因此，在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。
在本公开的各种实施例中，应理解，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本公开实施例的实施过程构成任何限定。
另外，本文中术语“系统”和“网络”在本文中常可互换使用。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
在本申请所提供的实施例中，应理解，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
在本申请所提供的几个实施例中，应该理解到，所揭露方法和装置，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理包括，也可以两个或两个以上单元集成在一个单 元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元，可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络侧设备等)执行本公开各个实施例所述收发方法的部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述的是本公开的优选实施方式，应当指出对于本技术领域的普通人员来说，在不脱离本公开所述的原理前提下还可以做出若干改进和润饰，这些改进和润饰也在本公开的保护范围内。

Claims (46)

  1. 一种随机接入响应方法，包括：
    UE发送随机接入请求，所述随机接入请求中携带包含UE标识的信息；
    所述UE接收随机接入响应，如果随机接入响应中携带的UE标识与随机接入请求中的UE标识一致，完成竞争解决；如果随机接入响应中携带的UE标识与随机接入请求中的UE标识不一致，则所述UE确定本次随机接入失败，重新发起随机接入尝试；如果随机接入响应中未携带UE标识，则所述UE回退到随机接入请求中不携带UE标识信息的随机接入过程；
    其中，所述随机接入响应是网络侧根据随机接入请求生成的。
  2. 根据权利要求1所述的方法，其中，所述随机接入响应采用媒体接入控制协议数据单元MAC PDU发送，该MAC PDU中包含MAC头和MAC RAR，MAC头包含多个MAC子头，每个MAC子头中包含一个随机接入前导码标识RAPID，对应随机接入请求中的随机接入前导码preamble码，每个MAC子头与一个MAC RAR对应，携带UE标识的随机接入响应MAC RAR和不携带UE标识的随机接入响应MAC RAR可以复用到一个MAC PDU中。
  3. 根据权利要求2所述的方法，其中，对于四步随机接入和两步随机接入，以及两步随机接入的不同随机接入场景，采用相同长度的MAC RAR，所述MAC RAR长度固定为能包含最大UE标识长度和临时小区无线网络临时标识Temporary C-RNTI，或同时能包含上行调度授权UL Grant。
  4. 根据权利要求2所述的方法，其中，所述MAC RAR包含以下任一项或多项：
    T1：指示后续为四步随机接入的MAC RAR或者两步随机接入的MAC RAR；
    T2：只在两步随机接入的MAC RAR中出现，用于指示是长UE ID或者为短UE ID；
    定时提前量指令Timing Advance Command：上行定时提前量；
    UL Grant：后续上行传输的资源分配；
    Temporary C-RNTI：竞争解决完成后转换为给UE分配的C-RNTI；
    竞争解决身份Contention Resolution Identity：对应两步随机接入的 随机接入请求中包含的UE标识的信息；
    R：预留比特。
  5. 根据权利要求2所述的方法，其中，所述MAC RAR中包含所有可能的域，每个域的长度都为可能长度的最大值，每个域的长度都是固定的，如果随机接入响应中不需要该域，则该域实际为预留bit，填充协议规定的值或由网络侧确定填充的值。
  6. 根据权利要求3或5所述的方法，其中，
    所述UE发送随机接入请求，包括：
    所述UE发送随机接入请求preamble码，不发送携带UE标识的信息；
    所述UE接收随机接入响应，包括：
    所述UE接收随机接入响应，根据MAC子头中RAPID域确定与发送的preamble码对应的MAC子头；
    所述UE获取该MAC子头对应的MAC RAR，如果解析MAC RAR中的指示域确定该MAC RAR不携带UE标识，读取MAC RAR中的后续域，根据各域的指示进行相关操作，完成后续随机接入过程；如果解析MAC RAR中的指示域确定该MAC RAR携带UE标识，确定随机接入失败，后续发起新的随机接入尝试。
  7. 根据权利要求3所述的方法，其中，
    所述UE发送随机接入请求，包括：
    所述UE发送随机接入请求，包括preamble码和包含UE标识的信息；
    所述UE接收随机接入响应，包括：
    所述UE接收随机接入响应，根据MAC子头中RAPID域确定与发送的preamble码对应的MAC子头；
    所述UE获取该MAC子头对应的MAC RAR，如果解析MAC RAR中的指示域T1确定该MAC RAR不携带UE标识，确定网络侧只收到了preamble码而没有正确接收数据部分，读取MAC RAR中的后续域，回退到四步随机接入，按照四步随机接入过程解析MAC RAR中各域，然后根据MAC RAR中各域的指示，完成后续的随机接入过程；或者
    如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，如果UE发送的是长UE ID，所述UE判断MAC RAR中的 UE标识是否与UE发送的长UE ID一致，如果一致，确定完成竞争解决，所述UE接收随后网络侧发送的带Temporary C-RNTI的物理下行控制信道PDCCH调度命令，根据该调度命令发送上行传输；如果不一致，所述UE确定本次随机接入失败，后续重新发起随机接入尝试；或者
    如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，如果UE发送的是短UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续重新发起随机接入尝试；或者
    如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，如果UE发送的是长UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续重新发起随机接入尝试；或者
    如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，如果UE发送的是短UE ID，所述UE判断MAC RAR中的UE标识是否与UE发送的短UE ID一致，如果一致，确定完成竞争解决，所述UE解析MAC RAR中的UL Grant，根据MAC RAR中UL Grant指示的资源，发送后续上行传输；如果不一致，所述UE确定本次随机接入失败，后续重新发起随机接入尝试。
  8. 根据权利要求5所述的方法，其中，
    所述UE发送随机接入请求，包括：
    所述UE发送随机接入请求，包括preamble码和包含UE ID标识的信息；
    所述UE接收随机接入响应，包括：
    所述UE接收随机接入响应，根据MAC子头中RAPID域确定与其发送的preamble码对应的MAC子头；
    所述UE获取该MAC子头对应的MAC RAR，如果解析MAC RAR中的指示域T1确定该MAC RAR不携带UE标识，所述UE确定网络侧只收到了preamble码而没有正确接收数据部分，所述UE只解析MAC RAR中的Timing Advance Command、UL Grant、Temporary C-RNTI域，回退到四步随机接入，然后所述UE根据MAC RAR中各域的指示，调整上行定时提前量，获取Temporary C-RNTI，根据UL Grant发送Msg3，并完成后续的随机接入过程；或者
    解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2 确定该UE标识为长UE ID，解析全部域，如果UE发送的是长UE ID，所述UE判断MAC RAR中的UE标识是否与UE发送的长UE ID一致，如果一致，所述UE确定完成竞争解决，然后所述UE根据MAC RAR中UL Grant指示的资源，发送后续上行传输；如果不一致，所述UE确定本次随机接入失败，后续重新发起随机接入尝试；或者
    解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，解析全部域，如果UE发送的是短UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续重新发起随机接入尝试；或者
    如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，解析全部域，如果UE发送的是长UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续重新发起随机接入尝试；或者
    如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，解析全部域，如果UE发送的是短UE ID，UE判断MAC RAR中的UE标识是否与UE发送的短UE ID一致，如果一致，UE确定完成竞争解决，然后UE根据MAC RAR中UL Grant指示的资源，发送后续上行传输；如果不一致，确定本次随机接入失败，后续重新发起随机接入尝试。
  9. 根据权利要求2所述的方法，其中，所述MAC子头包含preamble ID和长度指示域L，该长度指示域L用于指示对应MAC RAR的长度或MAC RAR类型。
  10. 根据权利要求9所述的方法，其中，MAC RAR类型包含以下任一项或多项：
    四步随机接入MAC RAR格式1：适用于UE发起四步竞争随机接入的场景；
    四步随机接入MAC RAR格式2：适用于UE发起四步非竞争随机接入的场景；
    四步随机接入MAC RAR格式3：适用于UE发起四步非竞争随机接入，且网络侧确定UE只需进行同步，不需发送上行数据的场景；
    两步随机接入MAC RAR格式1：随机接入请求中携带的是公共控制信道 CCCH上的无线资源控制RRC连接建立或RRC连接重建或闲置终端标识inactive UE ID，网络侧要为UE分配C-RNTI，网络侧需要UE进行上行同步校准；
    两步随机接入MAC RAR格式2：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准；
    两步随机接入MAC RAR格式3：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准；
    两步随机接入MAC RAR格式4：随机接入请求中携带的是inactive UE ID，网络侧只是确认收到随机接入请求中的数据，不需要UE进入连接态；
    两步随机接入MAC RAR格式5：随机接入请求中携带的是连接态UE的C-RNTI，网络侧需要UE进行上行同步校准；
    两步随机接入MAC RAR格式6：随机接入请求中携带的是连接态UE的C-RNTI，网络侧不需要UE进行上行同步校准；
    两步随机接入MAC RAR格式7：随机接入请求中携带的是连接态UE的C-RNTI，网络侧确认随机接入请求中的数据内容接收正确，确定UE不需要后续上行传输，网络侧不分配UL Grant。
  11. 根据权利要求9所述的方法，其中，
    所述UE发送随机接入请求，包括：
    所述UE发送随机接入请求preamble码，不发送携带UE标识的信息；
    所述UE接收随机接入响应，包括：
    所述UE接收随机接入响应，根据MAC子头中RAPID域确定与发送的preamble码对应的MAC子头，解析该MAC子头中的L域确定后续MAC RAR长度或MAC RAR类型；
    如果L域指示的是两步随机接入的MAC RAR类型，所述UE确定该随机接入响应不是针对自己的，随机接入失败，所述UE后续发起新的随机接入尝试；
    如果L域指示的是四步随机接入的MAC RAR类型，所述UE获取MAC RAR，所述UE根据MAC RAR各域指示完成所需的后续随机接入过程。
  12. 根据权利要求9所述的方法，其中，
    所述UE发送随机接入请求，包括：
    所述UE发送随机接入请求，包括preamble码和UE标识；
    所述UE接收随机接入响应，包括：
    所述UE接收随机接入响应，根据MAC子头中RAPID域确定与发送的preamble码对应的MAC子头，解析该MAC子头中的L域确定后续MAC RAR类型；
    如果的MAC RAR类型是四步随机接入RAR，所述UE确定网络侧没有正确接收到随机接入请求中的数据部分，回退到四步随机接入过程，根据MAC RAR指示发送Msg3，并接收下行传输Msg4，完成竞争解决；
    如果MAC RAR类型是两步随机接入RAR，则根据L域指示的不同MAC RAR类型进行如下处理：
    如果格式类型为两步随机接入MAC RAR格式1，所述UE在随机接入请求中携带的是长UE ID，且该MAC RAR中的UE标识与随机接入请求中的长UE ID一致，认为竞争解决成功，所述UE根据MAC RAR中的指示进行上行同步定时校准、发送上行数据、应用C-RNTI；如果UE在随机接入请求中发送的是短UE ID或该MAC RAR中的UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者
    如果格式类型为两步随机接入MAC RAR格式2，所述UE如果在随机接入请求中携带的是长UE ID，且该MAC RAR中UE标识与随机接入请求中的长UEID一致，认为竞争解决成功，所述UE根据MAC RAR中的指示发送上行数据、应用C-RNTI；如果UE在随机接入请求中发送的是短UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，所述UE后续重新发起随机接入尝试；或者
    如果格式类型为两步随机接入MAC RAR格式3，所述UE如果在随机接入请求中携带的是长UE ID，且该MAC RAR中UE标识与随机接入请求中的长UEID一致，认为竞争解决成功，所述UE根据MAC RAR中的指示应用C-RNTI；如果所述UE在随机接入请求中发送的是短UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，所述UE后续重新发起随机接入尝试；或者
    如果格式类型为两步随机接入MAC RAR格式4，UE如果在随机接入请求中携带的是长UE ID，且该MAC RAR中UE标识与随机接入请求中的长UE ID一致，认为竞争解决成功，根据MAC RAR中的应用C-RNTI，随后接收携带该C-RNTI的PDCCH调度命令，并根据该调度命令发送上行传输；如果UE在随机接入请求中发送的是短UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，所述UE后续重新发起随机接入尝试；或者
    如果格式类型为两步随机接入MAC RAR格式5，UE如果在随机接入请求中携带的是短UE ID，且该MAC RAR中UE标识与随机接入请求中短UE ID的一致，认为竞争解决成功，根据MAC RAR中的指示进行上行同步定时校准、发送上行数据；如果UE在随机接入请求中发送的是长UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，所述UE后续重新发起随机接入尝试；或者
    如果格式类型为两步随机接入MAC RAR格式6-，UE如果在随机接入请求中携带的是短UE ID，且该MAC RAR中UE标识与随机接入请求中的短UE ID一致，认为竞争解决成功，根据MAC RAR中的指示发送上行数据；如果UE在随机接入请求中发送的是长UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，所述UE后续重新发起随机接入尝试；或者
    如果格式类型为两步随机接入MAC RAR格式7，UE如果在随机接入请求中携带的是短UE ID，且该MAC RAR中的UE标识与随机接入请求中的短UE ID一致，认为竞争解决成功，随后监听携带该UE C-RNTI的PDCCH调度命令，如果接收到调度上行传输的PDCCH调度命令，根据该调度命令发送上行传输；如果UE在随机接入请求中发送的是长UE ID或该MAC RAR中的UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，所述UE后续重新发起随机接入尝试。
  13. 一种随机接入响应方法，其中，
    网络侧接收终端UE发送的随机接入请求，随机接入请求中携带包含UE标识的信息；
    所述网络侧根据随机接入请求生成随机接入响应，并将所述随机接入响应发送给UE。
  14. 根据权利要求13所述的方法，其中，所述随机接入响应采用MAC PDU发送，该MAC PDU中包含MAC头和媒体接入控制层随机接入响应MAC RAR，MAC头包含多个MAC子头，每个MAC子头中包含一个RAPID，对应随机接入请求中的preamble码，每个MAC子头与一个MAC RAR对应，携带UE标识的随机接入响应MAC RAR和不携带UE标识的随机接入响应MAC RAR可以复用到一个MAC PDU中。
  15. 根据权利要求14所述的方法，其中，对于四步随机接入和两步随机接入，以及两步随机接入的不同随机接入场景，采用相同长度的MAC RAR，所述MAC RAR长度固定为能包含最大UE ID长度和Temporary C-RNTI，或同时能包含UL Grant。
  16. 根据权利要求14所述的方法，其中，所述MAC RAR包含以下任一项或多项：
    T1：指示后续为四步随机接入的MAC RAR或者两步随机接入的MAC RAR；
    T2：只在两步随机接入的MAC RAR中出现，用于指示是长UE ID或者为短UE ID；
    Timing Advance Command：上行定时提前量；
    UL Grant：后续上行传输的资源分配；
    Temporary C-RNTI：竞争解决完成后转换为给UE分配的C-RNTI；
    Contention Resolution Identity：对应两步随机接入请求中包含的UE标识的信息；
    R：预留比特。
  17. 根据权利要求14所述的方法，其中，所述MAC RAR中包含所有可能的域，每个域的长度都为可能长度的最大值，每个域的长度都是固定的，如果随机接入响应中不需要该域，则该域实际为预留bit，填充协议规定的值或由网络侧确定填充的值。
  18. 根据权利要求16或17所述的方法，其中，
    所述网络侧接收UE发送的随机接入请求，包括：
    所述网络侧接收随机接入请求，所述随机接入请求包含preamble码，不 发送携带UE标识的信息；
    所述网络侧根据随机接入请求生成随机接入响应，包括：
    所述网络侧发送随机接入响应，所述随机接入响应中包括根据所述preamble码为UE配置的上行定时提前量、上行传输资源和Temporary C-RNTI。
  19. 根据权利要求16所述的方法，其中，
    所述网络侧接收UE发送的随机接入请求，包括：
    所述网络侧接收随机接入请求，所述随机接入请求包含preamble码或者包含preamble码和数据部分；
    所述网络侧根据随机接入请求生成随机接入响应，包括：
    所述网络侧根据接收到的随机接入请求，生成对应的MAC RAR并发送给UE。
  20. 根据权利要求19所述的方法，其中，如果生成MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，所述网络侧发送携带Temporary C-RNTI的PDCCH调度命令，为UE分配后续上行传输资源。
  21. 根据权利要求14所述的方法，其中，所述MAC子头包含preamble ID和长度指示域L，该长度指示域用于指示对应MAC RAR的长度或类型。
  22. 根据权利要求21所述的方法，其中，MAC RAR类型包含以下任一项或多项：
    四步随机接入MAC RAR格式1：适用于UE发起四步竞争随机接入的场景；
    四步随机接入MAC RAR格式2：适用于UE发起四步非竞争随机接入的场景；
    四步随机接入MAC RAR格式3：适用于UE发起四步非竞争随机接入，且网络侧确定UE只需进行同步，不需发送上行数据的场景；
    两步随机接入MAC RAR格式1：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧需要UE进行上行同步校准；
    两步随机接入MAC RAR格式2：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准；
    两步随机接入MAC RAR格式3：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准；
    两步随机接入MAC RAR格式4：随机接入请求中携带的是inactive UE ID，网络侧只是确认收到随机接入请求中的数据，不需要UE进入连接态；
    两步随机接入MAC RAR格式5：随机接入请求中携带的是连接态UE的C-RNTI，网络侧需要UE进行上行同步校准；
    两步随机接入MAC RAR格式6：随机接入请求中携带的是连接态UE的C-RNTI，网络侧不需要UE进行上行同步校准；
    两步随机接入MAC RAR格式7：随机接入请求中携带的是连接态UE的C-RNTI，网络侧确认随机接入请求中的数据内容接收正确，确定UE不需要后续上行传输，网络侧不分配UL Grant。
  23. 一种终端，包括：
    发送模块，用于发送随机接入请求，所述随机接入请求中携带包含UE标识的信息；
    第一处理模块，用于接收随机接入响应，如果随机接入响应中携带的UE标识与随机接入请求中的UE标识一致，完成竞争解决；如果随机接入响应中携带的UE标识与随机接入请求中的UE标识不一致，则所述UE确定本次随机接入失败，重新发起随机接入尝试；如果随机接入响应中未携带UE标识，则所述UE回退到随机接入请求中不携带UE标识信息的随机接入过程；
    其中，所述随机接入响应是网络侧根据随机接入请求生成的。
  24. 根据权利要求23所述的终端，其中，所述随机接入响应采用MAC PDU发送，该MAC PDU中包含MAC头和MAC RAR，MAC头包含多个MAC子头，每个MAC子头中包含一个RAPID，对应随机接入请求中的preamble码，每个MAC子头与一个MAC RAR对应，携带UE标识的随机接入响应MAC RAR和不携带UE标识的随机接入响应MAC RAR可以复用到一个MAC PDU中。
  25. 根据权利要求24所述的终端，其中，对于四步随机接入和两步随机接入，以及两步随机接入的不同随机接入场景，采用相同长度的MAC RAR，所述MAC RAR长度固定为能包含最大UE标识长度和Temporary C-RNTI，或 同时能包含UL Grant。
  26. 根据权利要求24所述的终端，其中，所述MAC RAR包含以下任一项或多项：
    T1：指示后续为四步随机接入的MAC RAR或者两步随机接入的MAC RAR；
    T2：只在两步随机接入的MAC RAR中出现，用于指示是长UE ID或者为短UE ID；
    Timing Advance Command：上行定时提前量；
    UL Grant：后续上行传输的资源分配；
    Temporary C-RNTI：竞争解决完成后转换为给UE分配的C-RNTI；
    Contention Resolution Identity：对应两步随机接入的随机接入请求中包含的UE标识的信息；
    R：预留比特。
  27. 根据权利要求25所述的终端，其中，所述MAC RAR中包含所有可能的域，每个域的长度都为可能长度的最大值，每个域的长度都是固定的，如果随机接入响应中不需要该域，则该域实际为预留bit，填充协议规定的值或由网络侧确定填充的值。
  28. 根据权利要求25或27所述的终端，其中，
    所述发送模块进一步用于：发送随机接入请求preamble码，不发送携带UE标识的信息；
    所述第一处理模块进一步用于：接收随机接入响应，根据MAC子头中RAPID域确定与发送的preamble码对应的MAC子头；所述UE获取该MAC子头对应的MAC RAR，如果解析MAC RAR中的指示域确定该MAC RAR不携带UE标识，读取MAC RAR中的后续域，根据各域的指示进行相关操作，完成后续随机接入过程；如果解析MAC RAR中的指示域确定该MAC RAR携带UE标识，确定随机接入失败，后续发起新的随机接入尝试。
  29. 根据权利要求25所述的终端，其中，
    所述发送模块进一步用于：发送随机接入请求，包括preamble码和包含UE标识的信息；
    所述第一处理模块进一步用于：接收随机接入响应，根据MAC子头中 RAPID域确定与发送的preamble码对应的MAC子头；
    获取该MAC子头对应的MAC RAR，如果解析MAC RAR中的指示域T1确定该MACRAR不携带UE标识，确定网络侧只收到了preamble码而没有正确接收数据部分，读取MAC RAR中的后续域，回退到四步随机接入，按照四步随机接入过程解析MAC RAR中各域，然后根据MAC RAR中各域的指示，完成后续的随机接入过程；或者
    如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，如果UE发送的是长UE ID，判断MAC RAR中的UE标识是否与UE发送的长UE ID一致，如果一致，确定完成竞争解决，接收随后网络侧发送的带Temporary C-RNTI的PDCCH调度命令，根据该调度命令发送上行传输；如果不一致，所述UE确定本次随机接入失败，后续重新发起随机接入尝试；或者
    如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，如果UE发送的是短UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续重新发起随机接入尝试；或者
    如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，如果UE发送的是长UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续重新发起随机接入尝试；或者
    如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，如果UE发送的是短UE ID，所述UE判断MAC RAR中的UE标识是否与UE发送的短UE ID一致，如果一致，确定完成竞争解决，解析MAC RAR中的UL Grant，根据MAC RAR中UL Grant指示的资源，发送后续上行传输；如果不一致，所述UE确定本次随机接入失败，后续重新发起随机接入尝试。
  30. 根据权利要求27所述的终端，其中，
    所述发送模块进一步用于：发送随机接入请求，包括preamble码和包含UE ID标识的信息；
    所述第一处理模块进一步用于：接收随机接入响应，根据MAC子头中RAPID域确定与其发送的preamble码对应的MAC子头；
    获取该MAC子头对应的MAC RAR，如果解析MAC RAR中的指示域T1确定 该MAC RAR不携带UE标识，确定网络侧只收到了preamble码而没有正确接收数据部分，只解析MAC RAR中的Timing Advance Command、UL Grant、Temporary C-RNTI域，回退到四步随机接入，然后所述UE根据MAC RAR中各域的指示，调整上行定时提前量，获取Temporary C-RNTI，根据UL Grant发送Msg3，并完成后续的随机接入过程；或者
    解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，解析全部域，如果UE发送的是长UE ID，所述UE判断MAC RAR中的UE标识是否与UE发送的长UE ID一致，如果一致，确定完成竞争解决，然后根据MAC RAR中UL Grant指示的资源，发送后续上行传输；如果不一致，所述UE确定本次随机接入失败，后续重新发起随机接入尝试；或者
    解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，解析全部域，如果UE发送的是短UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续重新发起随机接入尝试；或者
    如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，解析全部域，如果UE发送的是长UE ID，确定该MAC RAR不是针对自己的，本次随机接入失败，后续重新发起随机接入尝试；或者
    如果解析MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为短UE ID，解析全部域，如果UE发送的是短UE ID，判断MAC RAR中的UE标识是否与UE发送的短UE ID一致，如果一致，确定完成竞争解决，然后根据MAC RAR中UL Grant指示的资源，发送后续上行传输；如果不一致，确定本次随机接入失败，后续重新发起随机接入尝试。
  31. 根据权利要求24所述的终端，其中，所述MAC子头包含preamble ID和长度指示域L，该长度指示域L用于指示对应MAC RAR的长度或MAC RAR类型。
  32. 根据权利要求31所述的终端，其中，MAC RAR类型包含以下任一项或多项：
    四步随机接入MAC RAR格式1：适用于UE发起四步竞争随机接入的场景；
    四步随机接入MAC RAR格式2：适用于UE发起四步非竞争随机接入的场景；
    四步随机接入MAC RAR格式3：适用于UE发起四步非竞争随机接入，且网络侧确定UE只需进行同步，不需发送上行数据的场景；
    两步随机接入MAC RAR格式1：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧需要UE进行上行同步校准；
    两步随机接入MAC RAR格式2：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准；
    两步随机接入MAC RAR格式3：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准；
    两步随机接入MAC RAR格式4：随机接入请求中携带的是inactive UE ID，网络侧只是确认收到随机接入请求中的数据，不需要UE进入连接态；
    两步随机接入MAC RAR格式5：随机接入请求中携带的是连接态UE的C-RNTI，网络侧需要UE进行上行同步校准；
    两步随机接入MAC RAR格式6：随机接入请求中携带的是连接态UE的C-RNTI，网络侧不需要UE进行上行同步校准；
    两步随机接入MAC RAR格式7：随机接入请求中携带的是连接态UE的C-RNTI，网络侧确认随机接入请求中的数据内容接收正确，确定UE不需要后续上行传输，网络侧不分配UL Grant。
  33. 根据权利要求31所述的终端，其中，
    所述发送模块进一步用于：发送随机接入请求preamble码，不发送携带UE标识的信息；
    所述第一处理模块进一步用于：接收随机接入响应，根据MAC子头中RAPID域确定与发送的preamble码对应的MAC子头，解析该MAC子头中的L域确定后续MAC RAR长度或MAC RAR类型；
    如果L域指示的是两步随机接入的MAC RAR类型，确定该随机接入响应不 是针对自己的，随机接入失败，后续发起新的随机接入尝试；
    如果L域指示的是四步随机接入的MAC RAR类型，获取MAC RAR，根据MAC RAR各域指示完成所需的后续随机接入过程。
  34. 根据权利要求31所述的终端，其中，
    所述发送模块进一步用于：发送随机接入请求，包括preamble码和UE标识；
    所述第一处理模块进一步用于：接收随机接入响应，根据MAC子头中RAPID域确定与发送的preamble码对应的MAC子头，解析该MAC子头中的L域确定后续MAC RAR类型；
    如果的MAC RAR类型是四步随机接入RAR，确定网络侧没有正确接收到随机接入请求中的数据部分，回退到四步随机接入过程，根据MAC RAR指示发送Msg3，并接收下行传输Msg4，完成竞争解决；
    如果MAC RAR类型是两步随机接入RAR，则根据L域指示的不同MAC RAR类型进行如下处理：
    如果格式类型为两步随机接入MAC RAR格式1，在随机接入请求中携带的是长UE ID，且该MAC RAR中的UE标识与随机接入请求中的长UE ID一致，认为竞争解决成功，根据MAC RAR中的指示进行上行同步定时校准、发送上行数据、应用C-RNTI；如果UE在随机接入请求中发送的是短UE ID或该MACRAR中的UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者
    如果格式类型为两步随机接入MAC RAR格式2，如果在随机接入请求中携带的是长UE ID，且该MAC RAR中UE标识与随机接入请求中的长UE ID一致，认为竞争解决成功，根据MAC RAR中的指示发送上行数据、应用C-RNTI；如果UE在随机接入请求中发送的是短UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者
    如果格式类型为两步随机接入MAC RAR格式3，如果在随机接入请求中携带的是长UE ID，且该MAC RAR中UE标识与随机接入请求中的长UE ID一致，认为竞争解决成功，根据MAC RAR中的指示应用C-RNTI；如果所述UE 在随机接入请求中发送的是短UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者如果格式类型为两步随机接入MAC RAR格式4，如果在随机接入请求中携带的是长UE ID，且该MAC RAR中UE标识与随机接入请求中的长UE ID一致，认为竞争解决成功，根据MAC RAR中的应用C-RNTI，随后接收携带该C-RNTI的PDCCH调度命令，并根据该调度命令发送上行传输；如果UE在随机接入请求中发送的是短UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者
    如果格式类型为两步随机接入MAC RAR格式5，如果在随机接入请求中携带的是短UE ID，且该MAC RAR中UE标识与随机接入请求中短UE ID的一致，认为竞争解决成功，根据MAC RAR中的指示进行上行同步定时校准、发送上行数据；如果UE在随机接入请求中发送的是长UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者
    如果格式类型为两步随机接入MAC RAR格式6，如果在随机接入请求中携带的是短UE ID，且该MAC RAR中UE标识与随机接入请求中的短UE ID一致，认为竞争解决成功，根据MAC RAR中的指示发送上行数据；如果UE在随机接入请求中发送的是长UE ID或该MAC RAR中UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试；或者
    如果格式类型为两步随机接入MAC RAR格式7，如果在随机接入请求中携带的是短UE ID，且该MAC RAR中的UE标识与随机接入请求中的短UE ID一致，认为竞争解决成功，随后监听携带该UE C-RNTI的PDCCH调度命令，如果接收到调度上行传输的PDCCH调度命令，根据该调度命令发送上行传输；如果UE在随机接入请求中发送的是长UE ID或该MAC RAR中的UE标识与随机接入请求中的UE标识不一致，认为随机接入失败，后续重新发起随机接入尝试。
  35. 一种网络侧设备，包括：
    接收模块，用于接收终端UE发送的随机接入请求，随机接入请求中携带包含UE标识的信息；
    第二处理模块，用于根据随机接入请求生成随机接入响应，并将所述随机接入响应发送给UE。
  36. 根据权利要求35所述的网络侧设备，其中，所述随机接入响应采用MAC PDU发送，该MAC PDU中包含MAC头和媒体接入控制层随机接入响应MAC RAR，MAC头包含多个MAC子头，每个MAC子头中包含一个RAPID，对应随机接入请求中的preamble码，每个MAC子头与一个MAC RAR对应，携带UE标识的随机接入响应和不携带UE标识的随机接入响应MAC RAR可以复用到一个MAC PDU中。
  37. 根据权利要求36所述的网络侧设备，其中，对于四步随机接入和两步随机接入，以及两步随机接入的不同随机接入场景采用相同长度的MAC RAR，所述MAC RAR长度固定为能包含最大UE ID长度和Temporary C-RNTI，或同时能包含UL Grant。
  38. 根据权利要求36所述的网络侧设备，其中，所述MAC RAR包含以下任一项或多项：
    T1：指示后续为四步随机接入的MAC RAR或者两步随机接入的MAC RAR；
    T2：只在两步随机接入的MAC RAR中出现，用于指示是长UE ID或者为短UE ID；
    Timing Advance Command：上行定时提前量；
    UL Grant：后续上行传输的资源分配；
    Temporary C-RNTI：竞争解决完成后转换为给UE分配的C-RNTI；
    Contention Resolution Identity：对应两步随机接入请求中包含的UE标识的信息；
    R：预留比特。
  39. 根据权利要求36所述的网络侧设备，其中，所述MAC RAR中包含所有可能的域，每个域的长度都为可能长度的最大值，每个域的长度都是固定的，如果随机接入响应中不需要该域，则该域实际为预留bit，填充协议规定的值或由网络侧确定填充的值。
  40. 根据权利要求38或39所述的网络侧设备，其中，
    所述接收模块进一步用于：接收随机接入请求，所述随机接入请求包含preamble码，不发送携带UE标识的信息；
    所述第二处理模块进一步用于：发送随机接入响应，所述随机接入响应中包括根据所述preamble码为UE配置的上行定时提前量、上行传输资源和Temporary C-RNTI。
  41. 根据权利要求38所述的网络侧设备，其中，
    所述接收模块进一步用于：接收随机接入请求，所述随机接入请求包含preamble码或者包含preamble码和数据部分；
    所述处理模块进一步用于：根据接收到的随机接入请求，生成对应的MAC RAR并发送给UE。
  42. 根据权利要求41所述的网络侧设备，其中，如果生成MAC RAR中的指示域T1确定该MAC RAR携带UE标识，且指示域T2确定该UE标识为长UE ID，所述网络侧发送携带Temporary C-RNTI的PDCCH调度命令，为UE分配后续上行传输资源。
  43. 根据权利要求36所述的网络侧设备，其中，所述MAC子头包含preamble ID和长度指示域L，该长度指示域用于指示对应MAC RAR的长度或类型。
  44. 根据权利要求43所述的网络侧设备，其中，MAC RAR类型包含以下任一项或多项：
    四步随机接入MAC RAR格式1：适用于UE发起四步竞争随机接入的场景；
    四步随机接入MAC RAR格式2：适用于UE发起四步非竞争随机接入的场景；
    四步随机接入MAC RAR格式3：适用于UE发起四步非竞争随机接入，且网络侧确定UE只需进行同步，不需发送上行数据的场景；
    两步随机接入MAC RAR格式1：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧需要UE进行上行同步校准；
    两步随机接入MAC RAR格式2：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络侧不需要UE进行上行同步校准；
    两步随机接入MAC RAR格式3：随机接入请求中携带的是CCCH信道上的RRC连接建立或RRC连接重建或inactive UE ID，网络侧要为UE分配C-RNTI，网络 侧不需要UE进行上行同步校准；
    两步随机接入MAC RAR格式4：随机接入请求中携带的是inactive UE ID，网络侧只是确认收到随机接入请求中的数据，不需要UE进入连接态；
    两步随机接入MAC RAR格式5：随机接入请求中携带的是连接态UE的C-RNTI，网络侧需要UE进行上行同步校准；
    两步随机接入MAC RAR格式6：随机接入请求中携带的是连接态UE的C-RNTI，网络侧不需要UE进行上行同步校准；
    两步随机接入MAC RAR格式7：随机接入请求中携带的是连接态UE的C-RNTI，网络侧确认随机接入请求中的数据内容接收正确，确定UE不需要后续上行传输，网络侧不分配UL Grant。
  45. 一种终端，包括处理器、收发机和存储器；
    其中，所述处理器用于读取所述存储器中的程序，执行下列过程：
    发送随机接入请求，所述随机接入请求中携带包含UE标识的信息；
    接收随机接入响应，如果随机接入响应中携带的UE标识与随机接入请求中的UE标识一致，完成竞争解决；如果随机接入响应中携带的UE标识与随机接入请求中的UE标识不一致，则所述UE确定本次随机接入失败，重新发起随机接入尝试；如果随机接入响应中未携带UE标识，则所述UE回退到随机接入请求中不携带UE标识信息的随机接入过程；
    其中，所述随机接入响应是网络侧根据随机接入请求生成的；
    所述收发机用于接收和发送数据；
    所述存储器用于保存所述处理器执行操作时所使用的数据。
  46. 一种网络侧设备，包括处理器、收发机和存储器；
    其中，所述处理器用于读取所述存储器中的程序，执行下列过程：
    接收终端UE发送的随机接入请求，随机接入请求中携带包含UE标识的信息；
    根据随机接入请求生成随机接入响应，并将所述随机接入响应发送给UE；
    所述收发机用于接收和发送数据；
    所述存储器用于保存所述处理器执行操作时所使用的数据。
PCT/CN2018/076489 2017-01-06 2018-02-12 一种随机接入响应方法和装置 WO2018127240A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/476,050 US11102825B2 (en) 2017-01-06 2018-02-12 Method and device for responding to random access

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710009612.0 2017-01-06
CN201710009612.0A CN108282901B (zh) 2017-01-06 2017-01-06 一种随机接入响应方法和装置

Publications (1)

Publication Number Publication Date
WO2018127240A1 true WO2018127240A1 (zh) 2018-07-12

Family

ID=62790901

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/076489 WO2018127240A1 (zh) 2017-01-06 2018-02-12 一种随机接入响应方法和装置

Country Status (3)

Country Link
US (1) US11102825B2 (zh)
CN (1) CN108282901B (zh)
WO (1) WO2018127240A1 (zh)

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020156072A1 (zh) * 2019-02-02 2020-08-06 维沃移动通信有限公司 随机接入方法、装置、设备及介质
WO2020191773A1 (en) 2019-03-28 2020-10-01 Nokia Shanghai Bell Co., Ltd. Mechanism for first random access mode falling back to second random access mode
WO2020260002A1 (fr) * 2019-06-28 2020-12-30 Orange Procede d'acces a un reseau de communication, procede d'attachement, terminal, station de base et programmes d'ordinateur correspondants
WO2021062825A1 (zh) * 2019-09-30 2021-04-08 Oppo广东移动通信有限公司 发送或接收反馈信息的方法和装置
CN113348723A (zh) * 2019-02-01 2021-09-03 株式会社Ntt都科摩 用户装置以及基站装置
EP3820233A4 (en) * 2018-07-27 2021-09-08 Guangdong Oppo Mobile Telecommunications Corp., Ltd. DIRECT ACCESS METHOD, TERMINAL DEVICE AND NETWORK DEVICE
EP3855789A4 (en) * 2018-09-21 2021-09-29 Guangdong Oppo Mobile Telecommunications Corp., Ltd. DIRECT ACCESS METHOD AND DEVICE, NETWORK DEVICE AND TERMINAL DEVICE
CN113875311A (zh) * 2019-09-30 2021-12-31 Oppo广东移动通信有限公司 基于非竞争的两步随机接入方法、装置、终端及存储介质
EP3902366A4 (en) * 2019-01-25 2022-02-23 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND APPARATUS
EP3927095A4 (en) * 2019-03-22 2022-03-09 Guangdong Oppo Mobile Telecommunications Corp., Ltd. RANDOM ACCESS METHOD AND DEVICE, USER DEVICE AND NETWORK DEVICE
EP3941150A4 (en) * 2019-06-14 2022-04-06 Guangdong Oppo Mobile Telecommunications Corp., Ltd. DIRECT ACCESS METHOD, TERMINAL DEVICE AND NETWORK DEVICE
JP2022544938A (ja) * 2019-08-14 2022-10-24 北京小米移動軟件有限公司 ランダムアクセスメッセージ伝送方法、装置及び読み取り可能な記憶媒体
RU2789818C1 (ru) * 2019-04-30 2023-02-10 Зтэ Корпорейшн Системы и способы расширенной процедуры случайного доступа
EP3817500B1 (en) * 2018-08-01 2023-08-16 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Random access method and device, and computer storage medium

Families Citing this family (74)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10820352B2 (en) * 2017-03-29 2020-10-27 Sharp Kabushiki Kaisha Random access procedure(s) for radio system
CN109756991B (zh) 2017-11-06 2021-11-19 华为技术有限公司 通信方法及装置
CN110769516B (zh) * 2018-07-26 2022-01-28 维沃移动通信有限公司 一种随机接入方法及相关设备
CN110769517B (zh) * 2018-07-26 2022-02-01 维沃移动通信有限公司 一种随机接入方法及相关设备
WO2020020348A1 (zh) * 2018-07-27 2020-01-30 Oppo广东移动通信有限公司 一种信息传输方法及装置、终端设备、网络设备
JP2021533606A (ja) 2018-07-27 2021-12-02 オッポ広東移動通信有限公司Guangdong Oppo Mobile Telecommunications Corp., Ltd. ランダムアクセス方法及び装置
CA3108098C (en) * 2018-07-30 2023-05-23 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Random access method and related device
CN110831230B (zh) 2018-08-10 2021-10-01 华为技术有限公司 随机接入方法、装置、设备及存储介质
CN110913499B (zh) * 2018-09-18 2022-07-15 维沃移动通信有限公司 一种随机接入方法、终端及计算机可读存储介质
CN110913498B (zh) * 2018-09-18 2021-07-06 维沃移动通信有限公司 一种随机接入方法及终端
CN110933766B (zh) * 2018-09-19 2022-02-08 维沃移动通信有限公司 随机接入信息的获取、发送方法及网络节点
US11497060B2 (en) * 2018-10-01 2022-11-08 Mediatek Singapore Pte. Ltd. Multiplexing, addressing and HARQ for MsgB in two-step RACH in mobile communications
CN111050412B (zh) * 2018-10-12 2022-11-25 华为技术有限公司 一种随机接入方法及其装置
CN111083798B (zh) * 2018-10-22 2022-02-08 普天信息技术有限公司 一种基于竞争的随机接入方法和装置
EP3876590A4 (en) * 2018-10-31 2022-06-15 Beijing Xiaomi Mobile Software Co., Ltd. METHOD AND DEVICE FOR TRANSMITTING RANDOM ACCESS INDICATION INFORMATION
US20200137760A1 (en) * 2018-10-31 2020-04-30 Asustek Computer Inc. Method and apparatus for transmission using preconfigured uplink resources in a wireless communication system
EP3869837A4 (en) * 2018-10-31 2022-06-15 Beijing Xiaomi Mobile Software Co., Ltd. METHOD AND APPARATUS FOR TRANSMITTING RANDOM ACCESS INDICATION INFORMATION
US11711851B2 (en) * 2018-11-02 2023-07-25 FG Innovation Company Limited Two-step random access procedure in next generation wireless networks
WO2020124598A1 (zh) * 2018-12-21 2020-06-25 Oppo广东移动通信有限公司 随机接入的方法和设备
CN111405503B (zh) * 2019-01-02 2021-04-27 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
CN115226242A (zh) * 2019-01-11 2022-10-21 上海朗帛通信技术有限公司 一种用于无线通信的通信节点中的方法和装置
US11438930B2 (en) 2019-01-11 2022-09-06 Qualcomm Incorporated Timing indication for a two-step random access channel procedure
CN116390240A (zh) * 2019-01-22 2023-07-04 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
CN111278149B (zh) * 2019-01-30 2022-02-08 维沃移动通信有限公司 信息发送方法、信息检测方法、终端设备及网络设备
EP3918870A4 (en) * 2019-01-30 2022-09-28 Telefonaktiebolaget LM Ericsson (publ) RANDOM ACCESS METHOD AND APPARATUS
CN111526597B (zh) * 2019-02-01 2023-04-18 大唐移动通信设备有限公司 一种两步随机接入方法、设备及装置
US20210410191A1 (en) * 2019-02-05 2021-12-30 Google Llc Efficient messaging in a procedure for accessing a communication channel
WO2020166047A1 (ja) * 2019-02-14 2020-08-20 株式会社Ｎｔｔドコモ ユーザ装置、及び制御方法
WO2020168469A1 (en) * 2019-02-19 2020-08-27 Nokia Shanghai Bell Co., Ltd. Communicating between a terminal and a wireless network node
CN111601391A (zh) * 2019-02-21 2020-08-28 中国移动通信有限公司研究院 随机接入方法、装置、终端及网络侧设备
WO2020170412A1 (ja) * 2019-02-22 2020-08-27 富士通株式会社 通信装置、第２通信装置、通信システム、及び通信方法
WO2020177135A1 (zh) 2019-03-07 2020-09-10 Oppo广东移动通信有限公司 功率控制方法及随机接入方法、装置、终端
CN111885690A (zh) * 2019-03-07 2020-11-03 Oppo广东移动通信有限公司 功率控制方法及随机接入方法、装置、终端
WO2020181431A1 (zh) * 2019-03-08 2020-09-17 富士通株式会社 随机接入响应的发送和接收方法、装置和系统
KR20200110201A (ko) * 2019-03-14 2020-09-23 한국전자통신연구원 통신 시스템에서 단말의 접속 제어 방법
EP3923668A4 (en) * 2019-03-19 2022-02-23 Guangdong Oppo Mobile Telecommunications Corp., Ltd. WIRELESS COMMUNICATION METHOD, TERMINAL DEVICE AND NETWORK DEVICE
EP3930414A4 (en) * 2019-03-19 2022-05-11 Guangdong Oppo Mobile Telecommunications Corp., Ltd. RANDOM ACCESS METHOD AND DEVICE
CN114025433B (zh) * 2019-03-19 2023-03-10 Oppo广东移动通信有限公司 用于两步随机接入的方法、终端设备和网络设备
CN111726870A (zh) 2019-03-22 2020-09-29 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
WO2020191599A1 (zh) * 2019-03-25 2020-10-01 北京欧珀通信有限公司 通信方法、终端设备和网络设备
CN111757525B (zh) * 2019-03-27 2022-10-04 华为技术有限公司 随机接入方法和装置
EP3716723A1 (en) * 2019-03-28 2020-09-30 Comcast Cable Communications LLC Access procedures for wireless communications
CN111757537B (zh) * 2019-03-28 2022-09-16 华为技术有限公司 随机接入方法和装置
US11903039B2 (en) 2019-04-02 2024-02-13 Beijing Xiaomi Mobile Software Co., Ltd. Random access method and random access apparatus
CN111769922B (zh) * 2019-04-02 2023-08-15 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
WO2020199581A1 (en) * 2019-04-04 2020-10-08 Guangdong Oppo Mobile Telecommunications Corp., Ltd. User equipment and method for random access channel procedure of same
CN111787634B (zh) * 2019-04-04 2022-05-24 中国信息通信研究院 一种随机接入的方法、基站及用户设备
WO2020206651A1 (en) * 2019-04-11 2020-10-15 Qualcomm Incorporated Indication for two-step rach fallback to four-step rach
WO2020207392A1 (en) * 2019-04-11 2020-10-15 Qualcomm Incorporated Random access procedure
US10925096B2 (en) * 2019-04-22 2021-02-16 Industrial Technology Research Institute Extended random access method used by UE and base station and related apparatuses using the same
CN114222350B (zh) * 2019-04-24 2023-03-24 Oppo广东移动通信有限公司 一种随机接入方法及装置、用户设备、网络设备
US20220210837A1 (en) * 2019-04-26 2022-06-30 Ntt Docomo, Inc. User equipment and base station apparatus
EP3964005A4 (en) * 2019-04-30 2022-05-11 ZTE Corporation RESOURCE INDICATION IN RANDOM ACCESS
CN113748713A (zh) * 2019-04-30 2021-12-03 中兴通讯股份有限公司 增强型随机接入过程的系统和方法
CN117676904A (zh) * 2019-04-30 2024-03-08 华为技术有限公司 一种随机接入方法、装置及存储介质
EP3965518A4 (en) * 2019-04-30 2022-05-04 Fujitsu Limited RANDOM ACCESS METHOD AND APPARATUS, AND COMMUNICATION SYSTEM
CN111867126A (zh) * 2019-04-30 2020-10-30 华为技术有限公司 随机接入方法和装置
CN114375068B (zh) * 2019-06-14 2024-05-03 维沃移动通信有限公司 随机接入方法、响应方法、终端及网络设备
CN112118609A (zh) * 2019-06-19 2020-12-22 普天信息技术有限公司 随机接入消息区分方法、网络侧设备及移动终端
CN112153750B (zh) * 2019-06-28 2022-08-26 华为技术有限公司 一种随机接入的方法及通信装置
CN111800886B (zh) * 2019-07-12 2022-04-08 维沃移动通信有限公司 一种随机接入过程回退方法、设备及系统
CN112312578B (zh) * 2019-07-29 2023-09-15 大唐移动通信设备有限公司 一种信息处理方法、装置、设备及计算机可读存储介质
BR112022000728A2 (pt) 2019-07-30 2022-03-22 Zte Corp Arquitetura para mensagem de acesso aleatório
EP4007428B1 (en) * 2019-07-31 2023-11-01 Beijing Xiaomi Mobile Software Co., Ltd. Random access method, device, and medium
EP3780870A1 (en) 2019-08-13 2021-02-17 Apple Inc. Downlink radio resource control message transmission in 2-step random access
CN112399626A (zh) * 2019-08-13 2021-02-23 苹果公司 2步随机接入中的下行链路无线电资源控制消息传输
WO2021026919A1 (zh) * 2019-08-15 2021-02-18 Oppo广东移动通信有限公司 两步随机接入方法、装置、终端及存储介质
CN113260079A (zh) * 2020-02-07 2021-08-13 中国移动通信有限公司研究院 随机接入的处理方法、装置、终端及网络侧设备
US11672007B2 (en) * 2020-03-06 2023-06-06 Qualcomm Incorporated Feedback reporting in a two-step random-access procedure
WO2021179178A1 (zh) * 2020-03-10 2021-09-16 北京小米移动软件有限公司 数据传输方法、装置及存储介质
CN113891348A (zh) * 2020-07-02 2022-01-04 大唐移动通信设备有限公司 一种随机接入信息的传输方法、终端及网络侧设备
CN114258149B (zh) * 2020-09-24 2024-02-02 上海华为技术有限公司 一种接入方法以及相关设备
CN116368929A (zh) * 2020-09-30 2023-06-30 深圳市万普拉斯科技有限公司 随机接入方法及通信系统、通信装置、可读存储介质
CN117528526A (zh) * 2022-07-29 2024-02-06 华为技术有限公司 一种通信方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100278131A1 (en) * 2009-04-29 2010-11-04 Samsung Electronics Co., Ltd. Apparatus and method for managing a random access channel in a mobile communication system
CN104205670A (zh) * 2012-03-22 2014-12-10 中兴通讯(美国)公司 机器类型通信数据从移动装置向无线网络的优化传输
WO2016208962A1 (ko) * 2015-06-22 2016-12-29 삼성전자 주식회사 무선 통신 시스템에서 반영구 스케줄링 기반의 통신 기법

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4545768B2 (ja) * 2007-02-28 2010-09-15 株式会社エヌ・ティ・ティ・ドコモ 無線制御信号生成方法、無線基地局装置、および移動局
KR100968020B1 (ko) 2008-06-18 2010-07-08 엘지전자 주식회사 랜덤 액세스 절차를 수행하는 방법 및 그 단말
JP5525034B2 (ja) * 2010-03-12 2014-06-18 富士通株式会社 移動通信システム、中継制御方法及び中継局
CN102469617A (zh) * 2010-11-19 2012-05-23 普天信息技术研究院有限公司 一种竞争随机接入的方法
KR20130001096A (ko) * 2011-06-23 2013-01-03 주식회사 팬택 무선 통신 시스템에서 랜덤 액세스의 수행장치 및 방법
WO2014175788A1 (en) * 2013-04-22 2014-10-30 Telefonaktiebolaget L M Ericsson (Publ) Transmission of a random access response message
WO2015094057A1 (en) * 2013-12-19 2015-06-25 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for providing random access information when paging a wireless device
CN105430750A (zh) * 2014-09-22 2016-03-23 夏普株式会社 用于配置随机接入响应的方法以及基站和用户设备
US10039132B2 (en) * 2015-09-24 2018-07-31 Kt Corporation Method and apparatus for receiving random access response for MTC UE
CN107041012B (zh) * 2016-02-03 2022-11-22 北京三星通信技术研究有限公司 基于差分波束的随机接入方法、基站设备及用户设备
CN107872899B (zh) * 2016-09-23 2022-12-06 中兴通讯股份有限公司 一种随机接入方法、装置和设备
EP4054271A1 (en) * 2016-10-07 2022-09-07 Samsung Electronics Co., Ltd. Method and apparatus for enhanced contention based random access procedure
US10785801B2 (en) * 2017-01-05 2020-09-22 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for random access in a wireless communication system
WO2018127549A1 (en) * 2017-01-06 2018-07-12 Sony Corporation Wireless telecommunications apparatuses and methods
US11057935B2 (en) * 2017-03-22 2021-07-06 Comcast Cable Communications, Llc Random access process in new radio
US11647543B2 (en) * 2017-03-23 2023-05-09 Comcast Cable Communications, Llc Power control for random access

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100278131A1 (en) * 2009-04-29 2010-11-04 Samsung Electronics Co., Ltd. Apparatus and method for managing a random access channel in a mobile communication system
CN104205670A (zh) * 2012-03-22 2014-12-10 中兴通讯(美国)公司 机器类型通信数据从移动装置向无线网络的优化传输
WO2016208962A1 (ko) * 2015-06-22 2016-12-29 삼성전자 주식회사 무선 통신 시스템에서 반영구 스케줄링 기반의 통신 기법

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA; ALCATEL-LUCENT SHANGHAI BELL: "Considerations on NR RACH procedures", 3GPP TSG-RAN WG2 MEETING #96, R2-168013, 4 November 2016 (2016-11-04), pages 3, XP051192332, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_96/Docs/> *

Cited By (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3820233A4 (en) * 2018-07-27 2021-09-08 Guangdong Oppo Mobile Telecommunications Corp., Ltd. DIRECT ACCESS METHOD, TERMINAL DEVICE AND NETWORK DEVICE
EP3817500B1 (en) * 2018-08-01 2023-08-16 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Random access method and device, and computer storage medium
US11997717B2 (en) 2018-09-21 2024-05-28 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Random access method and apparatus, network device, and terminal
EP3855789A4 (en) * 2018-09-21 2021-09-29 Guangdong Oppo Mobile Telecommunications Corp., Ltd. DIRECT ACCESS METHOD AND DEVICE, NETWORK DEVICE AND TERMINAL DEVICE
EP3902366A4 (en) * 2019-01-25 2022-02-23 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND APPARATUS
CN113348723A (zh) * 2019-02-01 2021-09-03 株式会社Ntt都科摩 用户装置以及基站装置
WO2020156072A1 (zh) * 2019-02-02 2020-08-06 维沃移动通信有限公司 随机接入方法、装置、设备及介质
EP3927095A4 (en) * 2019-03-22 2022-03-09 Guangdong Oppo Mobile Telecommunications Corp., Ltd. RANDOM ACCESS METHOD AND DEVICE, USER DEVICE AND NETWORK DEVICE
CN113647186A (zh) * 2019-03-28 2021-11-12 上海诺基亚贝尔股份有限公司 用于第一随机接入模式回退到第二随机接入模式的机制
EP3949646A4 (en) * 2019-03-28 2022-10-26 Nokia Technologies OY MECHANISM FOR FALLING BACK FROM A FIRST RANDOM ACCESS MODE TO A SECOND RANDOM ACCESS MODE
WO2020191773A1 (en) 2019-03-28 2020-10-01 Nokia Shanghai Bell Co., Ltd. Mechanism for first random access mode falling back to second random access mode
RU2789818C1 (ru) * 2019-04-30 2023-02-10 Зтэ Корпорейшн Системы и способы расширенной процедуры случайного доступа
EP3941150A4 (en) * 2019-06-14 2022-04-06 Guangdong Oppo Mobile Telecommunications Corp., Ltd. DIRECT ACCESS METHOD, TERMINAL DEVICE AND NETWORK DEVICE
WO2020260002A1 (fr) * 2019-06-28 2020-12-30 Orange Procede d'acces a un reseau de communication, procede d'attachement, terminal, station de base et programmes d'ordinateur correspondants
JP2022544938A (ja) * 2019-08-14 2022-10-24 北京小米移動軟件有限公司 ランダムアクセスメッセージ伝送方法、装置及び読み取り可能な記憶媒体
RU2791289C1 (ru) * 2019-08-14 2023-03-07 Бейдзин Сяоми Мобайл Софтвэр Ко., Лтд. Способ и устройство передачи сообщений произвольного доступа и читаемый носитель данных
JP7429768B2 (ja) 2019-08-14 2024-02-08 北京小米移動軟件有限公司 ランダムアクセスメッセージ伝送方法、装置及び読み取り可能な記憶媒体
CN113875311A (zh) * 2019-09-30 2021-12-31 Oppo广东移动通信有限公司 基于非竞争的两步随机接入方法、装置、终端及存储介质
WO2021062825A1 (zh) * 2019-09-30 2021-04-08 Oppo广东移动通信有限公司 发送或接收反馈信息的方法和装置
CN113875311B (zh) * 2019-09-30 2023-12-05 Oppo广东移动通信有限公司 基于非竞争的两步随机接入方法、装置、终端及存储介质

Also Published As

Publication number Publication date
CN108282901B (zh) 2019-08-09
US20190335515A1 (en) 2019-10-31
US11102825B2 (en) 2021-08-24
CN108282901A (zh) 2018-07-13

Similar Documents

Publication Publication Date Title
WO2018127240A1 (zh) 一种随机接入响应方法和装置
US11770856B2 (en) Random access response method and device, base station and user equipment
WO2018127226A1 (zh) 一种竞争随机接入的方法和装置
US8243667B2 (en) Method for transmitting scheduling request effectively in wireless communication system
US20190380154A1 (en) Communications device, infrastructure equipment and methods
JP2021522715A (ja) Ｍｅｓｓａｇｅ３プロトコルデータユニットを送受信する装置及び方法
WO2019029300A1 (zh) 传输随机接入响应的方法、接入网设备和终端设备
WO2018024011A1 (zh) 一种随机接入方法和设备
WO2019154272A1 (zh) 波束失败恢复方法及用户终端
KR20190128233A (ko) 랜덤 액세스 백오프 후의 랜덤 액세스를 위한 방법 및 장치, 및 랜덤 액세스 백오프를 지시하기 위한 방법 및 장치
US20200374920A1 (en) Method and apparatus for transmitting data in random access process
JP6938777B2 (ja) Ｒｒｃ接続モードでのランダムアクセスのための帯域幅部分操作
JP2013027045A (ja) ランダムアクセス応答を処理する方法
US11382142B2 (en) Random access method and device, storage medium, and electronic device
WO2013107171A1 (zh) 一种多载波系统的随机接入方法及系统及终端及基站设备
WO2014196908A1 (en) Telecommunications apparatus and method relating to a random access procedure
CN108617004B (zh) 一种rrc连接态传输数据的方法及装置
JP5033918B2 (ja) 移動通信システムにおける無線リソース割り当て要求の効果的な伝送方法
WO2019062562A1 (zh) 信息指示方法、用户设备及基站
WO2019178728A1 (zh) 一种随机接入方法及装置
WO2019095115A1 (zh) 用于竞争随机接入的方法、网络设备和终端设备
CN113906816B (zh) 通信方法及装置
WO2018227510A1 (zh) 接入控制方法及相关产品
JP7184086B2 (ja) 基地局、端末、無線通信システム
WO2020221279A1 (zh) 随机接入方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18736578

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18736578

Country of ref document: EP

Kind code of ref document: A1