WO2020248930A1 - 随机接入方法、响应方法、终端及网络设备 - Google Patents

随机接入方法、响应方法、终端及网络设备 Download PDF

Info

Publication number
WO2020248930A1
WO2020248930A1 PCT/CN2020/094878 CN2020094878W WO2020248930A1 WO 2020248930 A1 WO2020248930 A1 WO 2020248930A1 CN 2020094878 W CN2020094878 W CN 2020094878W WO 2020248930 A1 WO2020248930 A1 WO 2020248930A1
Authority
WO
WIPO (PCT)
Prior art keywords
rar
rar message
format
terminal
random access
Prior art date
Application number
PCT/CN2020/094878
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 维沃移动通信有限公司
Publication of WO2020248930A1 publication Critical patent/WO2020248930A1/zh
Priority to US17/548,390 priority Critical patent/US20220104275A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W74/00Wireless channel access
    • H04W74/08Non-scheduled access, e.g. ALOHA
    • H04W74/0833Random access procedures, e.g. with 4-step access
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0091Signaling for the administration of the divided path
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/23Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a random access method, a response method, a terminal, and a network device.
  • the 2-step random access process first the terminal can trigger the 2-step random access process and send a random access message to the network device, and then the network device can send a random access response (Random access response) after receiving the random access message. Access Response (RAR) message to the terminal.
  • RAR Access Response
  • the embodiments of the present disclosure provide a random access method, a response method, a terminal, and a network device to solve the problem that it is not yet clear what content the RAR message in the 2-step random access process includes, so that the terminal cannot distinguish different response situations.
  • embodiments of the present disclosure provide a random access method applied to a terminal, including:
  • the embodiments of the present disclosure provide a random access response method, which is applied to a network device, and includes:
  • the RAR message includes indication information, and the indication information indicates a format type of the RAR message.
  • the embodiments of the present disclosure provide a random access method applied to a terminal, including:
  • control information it is determined that the random access procedure is successful.
  • a terminal including:
  • the first sending module is used to send a random access message to a network device
  • the first receiving module is configured to receive a RAR message from the network device, the RAR message includes indication information, and the indication information indicates the format type of the RAR message;
  • the execution module is used to execute the corresponding random access operation according to the instruction information.
  • embodiments of the present disclosure provide a network device, including:
  • the second receiving module is configured to receive a random access message from the terminal
  • the second sending module is configured to send a RAR message to the terminal
  • the RAR message includes indication information, and the indication information indicates a format type of the RAR message.
  • a terminal including:
  • the third sending module is used to send a random access message to the network device
  • a third receiving module configured to receive a RAR message from the network device, the RAR message including control information corresponding to terminal requirements
  • the determining module is used to determine the success of the random access process according to the control information.
  • an embodiment of the present disclosure provides a terminal, including a memory, a processor, and a computer program stored on the memory and capable of running on the processor, wherein the computer program is executed by the processor During execution, the steps of the random access method in the first aspect mentioned above are realized, or the steps of the random access response method in the second aspect mentioned above are realized, or the steps of the random access method mentioned in the third aspect mentioned above are realized.
  • embodiments of the present disclosure provide a computer-readable storage medium on which a computer program is stored, wherein the computer program is executed by a processor to implement the steps of the random access method in the first aspect, Either implement the steps of the random access response method in the second aspect described above, or implement the steps of the random access method in the third aspect described above.
  • the instruction information indicates the format type of the RAR message, and at least the random access process (such as the 2-step random access process) What content is included in the RAR message in ), so that the terminal can distinguish different response conditions of the network equipment, thereby reducing the delay and processing complexity in the random access process.
  • Fig. 1 is a flowchart of a 2-step random access process according to an embodiment of the disclosure
  • FIG. 2 is one of the flowcharts of the random access method according to an embodiment of the disclosure
  • 3A is one of the schematic diagrams of the MAC RAR subheader format including BI information according to an embodiment of the disclosure
  • FIG. 3B is a schematic diagram of the MAC RAR subheader format including RAPID according to an embodiment of the disclosure
  • FIG. 4A is one of the schematic diagrams of the fallback RAR format according to an embodiment of the disclosure.
  • FIG. 4B is one of the schematic diagrams of the successful RAR format according to an embodiment of the disclosure.
  • 4C is one of the schematic diagrams of multiplexing and sending multiple RAR messages according to an embodiment of the disclosure.
  • 5A is the second schematic diagram of the MAC RAR subheader format including BI information according to an embodiment of the disclosure
  • FIG. 5B is a schematic diagram of other MAC RAR subheader formats except for including BI information according to an embodiment of the disclosure
  • 6A is the second schematic diagram of the fallback RAR format according to an embodiment of the disclosure.
  • 6B is the third schematic diagram of the fallback RAR format according to an embodiment of the disclosure.
  • 6C is the second schematic diagram of a successful RAR format according to an embodiment of the disclosure.
  • 6D is the second schematic diagram of multiplexing and sending multiple RAR messages according to an embodiment of the disclosure.
  • FIG. 7 is a schematic diagram of the format after combining MAC RAR subheader and MAC RAR according to an embodiment of the disclosure
  • FIG. 8 is a flowchart of a random access response method according to an embodiment of the disclosure.
  • FIG. 9 is the second flowchart of the random access method according to an embodiment of the disclosure.
  • FIG. 10A is one of the schematic diagrams of the MAC subheader format according to an embodiment of the disclosure.
  • FIG. 10B is one of the schematic diagrams of the MAC CE format of an embodiment of the disclosure.
  • FIG. 10C is the second schematic diagram of the MAC CE format of an embodiment of the disclosure.
  • FIG. 11A is the second schematic diagram of the MAC subheader format according to an embodiment of the disclosure.
  • FIG. 11B is one of the schematic diagrams of the MAC subPDU format according to an embodiment of the disclosure.
  • FIG. 11C is the second schematic diagram of the MAC subPDU format of an embodiment of the disclosure.
  • FIG. 12 is one of schematic structural diagrams of a terminal according to an embodiment of the disclosure.
  • FIG. 13 is one of the schematic structural diagrams of the network device of the embodiment of the disclosure.
  • FIG. 14 is the second structural diagram of a terminal according to an embodiment of the disclosure.
  • FIG. 15 is the third structural diagram of a terminal according to an embodiment of the disclosure.
  • FIG. 16 is the second structural diagram of a network device according to an embodiment of the disclosure.
  • the wireless communication system in the embodiment of the present disclosure includes a terminal and a network device.
  • the terminal can also be called a terminal device or a user terminal (User Equipment, UE), and the terminal can be a mobile phone, a tablet (Personal Computer), a laptop (Laptop Computer), a personal digital assistant (Personal Digital Assistant, PDA), Terminal-side devices such as Mobile Internet Device (MID), Wearable Device (Wearable Device), or in-vehicle device, it should be noted that the specific types of terminals are not limited in the embodiments of the present disclosure.
  • the network equipment may be a base station or a core network.
  • the base station may be a base station of 5G and later versions (for example: gNB, 5G NR NB, etc.), or a base station in other communication systems (for example: eNB, WLAN access point, or other access point). Access point, etc.), the base station can be called Node B, Evolved Node B, Access Point, Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS) , Extended Service Set (ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, WLAN Access Point, WiFi Node, or some other suitable one in the field Terminology, as long as it achieves the same technical effect, is not limited to specific technical vocabulary.
  • the applicable scenario of the embodiment of the present disclosure may be a 2-step random access (2-step RACH) process.
  • the 2-step RACH process may include the following steps:
  • Step 11 The network device configures the terminal with 2-step random access configuration information; the configuration information includes, for example, the transmission resource information corresponding to the random access message and the random access response message; the random access message may be called a random access request Message or MsgA; this random access response message can be called MsgB;
  • Step 12 The terminal triggers a 2-step random access procedure and sends MsgA to the network device; the Msg1 can be sent through the Physical Uplink Shared Channel (PUSCH), and the Msg1 includes at least the request data data and the terminal identification ID;
  • PUSCH Physical Uplink Shared Channel
  • Step 13 The network device returns MsgB to the terminal. If the terminal fails to receive MsgB, the terminal can resend MsgA.
  • MsgA can be equivalent to the content included in Msg1 and Msg3 in the combined 4-step RACH process
  • MsgB can be equivalent to the content included in Msg2 and Msg4 in the combined 4-step RACH process.
  • the response of MsgB feedback may include any of the following: 1) For the case where MsgA includes common control channel (CCCH) information, MsgB may indicate at least one of the following: Backoff Indicator (BI) information , Fallback RAR messages, successful RAR messages; and successful RAR messages may include terminal-specific downlink data; 2) For the case where MsgA includes Cell-Radio Network Tempory Identity (C-RNTI), the network The device needs to respond to the terminal, so that the C-RNTI is used to parse the physical downlink control channel (Physical Downlink Control Channel, PDCCH) scheduling signaling including the timing advance command (Timing Advanced Command, TAC) or uplink authorization to inform the terminal that the contention resolution is successful .
  • CCCH common control channel
  • PDCCH Physical Downlink Control Channel
  • TAC Timing Advanced Command
  • the terminal can monitor in the MsgB window the RA-RNTI is used to resolve the scheduling signaling of the PDCCH (PDCCH addressed to RA-RNTI):
  • the terminal can perform a fallback operation (fallback operation) and fall back to the 4-step RACH process;
  • the terminal If it receives its own successful RAR message (success RAR), and the contention resolution identification verification is successful, the terminal can confirm that the random access process is successful;
  • the terminal can receive the relevant data according to the situation of the terminal-specific SRB or data indicated by the network device, and confirm the success of the random access process ;
  • the terminal can retry the 2-step after performing the fallback operation based on the BI information RACH process.
  • the terminal can monitor in the MsgB window to use RA-RNTI to resolve PDCCH (PDCCH addressed to RA-RNTI) and use C-RNTI to resolve PDCCH (PDCCH addressed to C- RNTI) scheduling signaling:
  • the terminal can perform a rollback operation and fall back to the 4-step RACH process;
  • the terminal can confirm that the random access process is successful;
  • the terminal can retry the 2-step after performing the fallback operation based on the BI information RACH process.
  • FIG. 2 is a flowchart of a random access method provided by an embodiment of the present disclosure. The method is applied to a terminal. As shown in FIG. 2, the method includes the following steps:
  • Step 201 Send a random access message to the network device.
  • the random access message may be referred to as a random access request message or MsgA.
  • the random access message may include CCCH information.
  • the terminal when the terminal is in the Idle state or in the Inactive state, the terminal can initiate a radio resource control (Radio Resource Control, RRC) connection establishment process or an RRC connection recovery process, which can trigger 2 -step RACH process to establish uplink synchronization with network equipment and complete the signaling interaction process.
  • RRC Radio Resource Control
  • the terminal can send a random access preamble (Preamble code) in the MsgA, and send an MsgA similar to Msg3 in the 4-step RACH process on the corresponding uplink PUSCH, and carry CCCH information;
  • the CCCH information can be used for RRC connection establishment or RRC connection recovery, etc.
  • Step 202 Receive a RAR message from a network device.
  • the RAR message may include indication information, and the indication information indicates a format type of the RAR message.
  • Step 203 Perform a corresponding random access operation according to the instruction information.
  • the random access method of the embodiment of the present disclosure performs a corresponding random access operation according to the indication information included in the RAR message.
  • the indication information indicates the format type of the RAR message.
  • At least the random access process (such as 2-step random access) What content is included in the RAR message in the access process, so that the terminal can distinguish different response conditions of the network equipment, thereby reducing the delay and processing complexity in the random access process.
  • the receiving situation of the terminal MsgA may include any of the following possible situations:
  • the network device can respond with different content to instruct the terminal to behave next.
  • the RA-RNTI is calculated according to the time-frequency resource location of the terminal sending the Preamble or MsgA
  • the same RA-RNTI can correspond to multiple terminals, that is, in order to improve the efficiency of response, the network device can give multiple terminals
  • the response messages are multiplexed together for transmission.
  • the response content of the network device to the terminal MsgA may include at least the following types:
  • the indication information included in the above-mentioned RAR message can take at least the following two forms, as described below.
  • the foregoing indication information may include a first indication field, and the first indication field indicates that the RAR message includes BI information or RAR information.
  • the RAR information may optionally be a random access preamble identifier (Random Access Preamble Identifier, RAPID).
  • RAPID Random Access Preamble Identifier
  • the first indication field may be a T field included in a media access control (Media Access Control, MAC) RAR subheader (subheader), and the T field may also be referred to as a T1 field.
  • Media Access Control Media Access Control, MAC
  • RAR subheader subheader
  • FIG. 3A is a schematic diagram of the MAC RAR subheader format including BI information, and the MAC RAR subheader may include at least the following fields:
  • -E field (such as 1bit): used to indicate whether the current MAC subPDU is the last one; for example, the value of the E field can be 0 or 1, 0 means there are other MAC subPDUs in the future, 1 means the current MAC subPDU is the last one , The remaining content is padding bits;
  • -T field (such as 1bit): type indication information, used to indicate that the corresponding RAR message includes BI information or MAC RAR information; for example, if the value of the T field is 0 or 1, 0 means BI information is included, 1 means MAC RAR is included Information, the value of the T field shown in Figure 3A is 0;
  • -R domain (such as 1bit): reserved bits; for example, the value of R domain can be 0;
  • -BI domain (such as 4bits): used to indicate the fallback behavior in the case of network overload.
  • FIG. 3B is a schematic diagram of the MAC RAR subheader format including RAPID, and the MAC RAR subheader may include at least the following fields:
  • -E field (such as 1bit): used to indicate whether the current MAC subPDU is the last one; for example, the value of the E field can be 0 or 1, 0 means there are other MAC subPDUs in the future, 1 means the current MAC subPDU is the last one , The remaining content is padding bits;
  • -T field (such as 1bit): type indication information, used to indicate that the corresponding RAR message includes BI information or MAC RAR information; for example, if the value of the T field is 0 or 1, 0 means BI information is included, 1 means MAC RAR is included Information, the value of the T field shown in Figure 3B is 1;
  • RAPID field (such as 6 bits), used to correspond to the preamble code used in random access messages (such as MsgA). It should be pointed out that if the preamble code corresponding to RAPID is a dedicated preamble code configured for system information (System Information, SI) requests, there is no need to carry MAC RAR information subsequently.
  • SI System Information
  • the indication information may further include a second indication field, and the second indication field indicates that the format of the RAR message is Exit RAR format, or succeed in RAR format.
  • the second indication field may optionally be the T2 field included in the format of the MAC RAR message (for example, the fallback RAR format or the successful RAR format).
  • the indication information may further include a third indication field, and the third indication field indicates that the RAR message includes The case of terminal dedicated data.
  • the third indication field may optionally be the P field included in the successful RAR format.
  • the third indication field may optionally be at least 1 bit.
  • the third indicator field indicates whether the RAR message includes terminal-specific data; or, when the third indicator field is at least 1 bit, the third indicator field indicates the RAR Whether the message includes terminal-specific data, and if the RAR message includes terminal-specific data, the number of terminal-specific data included in the RAR message.
  • the terminal-specific data may be at least one of a MAC service data unit (Service Data Unit, SDU) and a MAC control unit (CE).
  • SDU Service Data Unit
  • CE MAC control unit
  • the terminal-specific data can be selected as MAC SDU or MAC CE; and if the number of terminal-specific data is multiple, the multiple terminal-specific data can all be MAC SDUs, or It can be all MAC CE, or part of it can be MAC SDU, and the other part can be MAC CE.
  • the above-mentioned fallback RAR format may include at least the following fields:
  • -T2 field (such as 1bit): used to indicate that the format of the current MAC RAR message is the fallback RAR format or the successful RAR format; for example, if the value of the T2 field is 0 or 1, 0 means fallback RAR format, 1 means If the RAR format is successful, the value of the T2 field shown in Figure 4A is 0;
  • -TAC field (such as 12bits): used to send the terminal's uplink advance
  • -UL Grant field (such as 27bits): used to allocate uplink grants for the terminal to transmit random access messages
  • Temporary C-RNTI ie Temporary C-RNTI field (for example, 16 bits): used to allocate a temporary C-RNTI for the fallback UE.
  • the above successful RAR format may include at least the following fields:
  • -T2 field (such as 1bit): used to indicate that the format of the current MAC RAR message is the fallback RAR format or the successful RAR format; for example, if the value of the T2 field is 0 or 1, 0 means fallback RAR format, 1 means If the RAR format is successful, the value of the T2 field shown in Figure 4B is 1;
  • -R domain (such as 1bit): reserved bits; for example, the value of R domain can be 0;
  • -TAC field (such as 12bits): used to send the terminal's uplink advance
  • -C-RNTI field (such as 16 bits): used to allocate C-RNTI for successful UEs;
  • UE Contention Resolution ID (UE Contention Resolution ID) field (for example, 48 bits): used to send the content of the CCCH information in the terminal MsgA; if the size of the CCCH information exceeds 48 bits, the first 48 bits of the CCCH information can be filled in;
  • -P field (for example, 1, 2 or 3 bits can be selected): used to indicate that the corresponding RAR message includes terminal-specific data.
  • the size of the P field can be selected based on actual conditions and can indicate different conditions. As for how many bits are selected for the P field, it can be specified in the agreement or configured in the system message.
  • the value of the P field can be 0 or 1.
  • 0 means that the corresponding successful RAR message does not include any terminal-specific data.
  • the terminal-specific data may be, for example, a terminal-specific signaling radio bearer (Signaling Radio Bearer). Radio Bearer (SRB) subPDU and Data Radio Bearer (DRB) subPDU; 1 indicates that the corresponding successful RAR message includes a terminal-specific SRB subPDU or DRB subPDU.
  • SRB Signaling radio bearer
  • DRB Data Radio Bearer
  • the value of the P field can be 00, 01, 10, or 11.
  • 00 indicates that the corresponding successful RAR message does not include terminal-specific SRB subPDU and DRB subPDU
  • 01 indicates the corresponding successful RAR message Including a terminal-specific SRB subPDU or DRB subPDU
  • 10 indicates that the corresponding successful RAR message includes two terminal-specific data (such as SRB subPDU or DRB subPDU)
  • 11 indicates that the corresponding successful RAR message includes three terminal-specific data Data (such as SRB subPDU or DRB subPDU).
  • the value of the P field can be 000, 001, 010, 011, 100, 101, 110, or 111,000, indicating that the corresponding successful RAR message does not include terminal-specific data, and 001 indicates the corresponding
  • the successful RAR message includes one terminal-specific data
  • 010 indicates that the corresponding successful RAR message includes two terminal-specific data
  • 011 indicates that the corresponding successful RAR message includes three terminal-specific data
  • 100 indicates that the corresponding successful RAR message includes four
  • 101 indicates that the corresponding successful RAR message includes five terminal-specific data
  • 110 indicates that the corresponding successful RAR message includes six terminal-specific data
  • 111 indicates that the corresponding successful RAR message includes seven terminal-specific data ;
  • the terminal-specific data here can be SRB subPDU or DRB subPDU.
  • the network device can multiplex response messages to multiple terminals for transmission, as shown in Figure 4C.
  • the MAC RAR subheader (including BI information) of UE1 and the MAC RAR subheader of UE2 can be combined. (Including RAPID), the fallback RAR message of UE3, the success RAR message of UE4, etc. are multiplexed together for transmission.
  • the format of MAC data subPDU may be adopted.
  • the terminal can know which logical channel the corresponding subPDU belongs to and the length of the data according to the logical channel identification (Logical Channel Identify, LCID) field and the L field, and when the value of the LCID field is special, it can also represent that the corresponding subPDU is a MAC CE subPDU.
  • the terminal can determine the size of the corresponding subPDU. If it is its own data, it can be parsed, if it is not its own data, it can skip and continue to decode the remaining subPDUs to obtain itself data.
  • the above indication information may include a fourth indication field, and the fourth indication field indicates any one of the following:
  • the RAR message includes BI information
  • the format of the RAR message is a fallback RAR format
  • the format of the RAR message is a successful RAR format
  • the number of terminal-specific data included in the RAR message is the number of terminal-specific data included in the RAR message.
  • the fourth indication field may be the T field included in the MAC RAR subheader, and the T field may be 2 or 3 bits.
  • FIG. 5A is a schematic diagram of the MAC RAR subheader format including BI information, and the MAC RAR subheader may include at least the following fields:
  • -E field (such as 1bit): used to indicate whether the current MAC subPDU is the last one; for example, the value of the E field can be 0 or 1, 0 means there are other MAC subPDUs in the future, 1 means the current MAC subPDU is the last one , The remaining content is padding bits;
  • type indication information used to indicate whether the corresponding RAR message includes BI information, and the format of the corresponding RAR message
  • -R domain (such as 1bit): reserved bits; for example, the value of R domain can be 0;
  • -BI domain (such as 4bits): used to indicate the fallback behavior in the case of network overload.
  • FIG. 5B is a schematic diagram of other MAC RAR subheader formats other than BI information.
  • the MAC RAR subheader may include at least the following fields:
  • -E field (such as 1bit): used to indicate whether the current MAC subPDU is the last one; for example, the value of the E field can be 0 or 1, 0 means there are other MAC subPDUs in the future, 1 means the current MAC subPDU is the last one , The remaining content is padding bits;
  • type indication information used to indicate whether the corresponding RAR message includes BI information, and the format of the corresponding RAR message
  • -R field (such as 1bit): reserved bits; for example, the value of the R field can be 0.
  • T field As 2bits as an example, see Table 1 below.
  • the value of the T field can be 00, 01, 10, or 11.
  • 00 indicates that the corresponding RAR message includes BI information
  • 01 indicates that the format of the corresponding RAR message is Fallback RAR format
  • 10 indicates that the format of the corresponding RAR message is a successful RAR format
  • 11 indicates that the corresponding RAR message includes a terminal-specific data, such as MAC SDU or MAC CE.
  • T domain Description 00 Including BI information 01 Is the fallback RAR format 10 Is a successful RAR format 11 Includes a terminal specific data
  • the value of the T field can be 000, 001, 010, 011, 100, 101, 110, or 111,000, indicating that the corresponding RAR message includes BI information.
  • 001 indicates that the format of the corresponding RAR message is a fallback RAR format
  • 010 indicates that the format of the corresponding RAR message is a successful RAR format
  • 011 indicates that the corresponding RAR message includes one terminal-specific data
  • 100 indicates that the corresponding RAR message includes two terminal-specific data
  • 101 indicates The corresponding RAR message includes three terminal-specific data or reservations
  • 110 indicates that the corresponding RAR message includes four terminal-specific data or reservations
  • 111 indicates that the corresponding RAR message includes five terminal-specific data or reservations.
  • T domain Description 000 Including BI information 001 Is the fallback RAR format 010 Is a successful RAR format 011 Includes a terminal specific data 100 Including two terminal dedicated data 101 Including three terminal dedicated data or reserved
  • the format of the corresponding RAR message can be a fallback RAR (fallback RAR) format, or a success RAR (success RAR) format .
  • the fields included in the fallback RAR format may be similar to those in the foregoing FIG. 4A
  • the fields included in the successful RAR format may be similar to those in the foregoing FIG. 4B, but have at least the following differences:
  • the fourth indication field indicates that the format of the RAR message is the fallback RAR format
  • the RAR message includes RAPID for identity verification
  • the RAR message may not include RAPID; the reason for not including RAPID is: the terminal can pass the contention resolution ID (UE Contention Resolution ID) field Perform identity verification without RAPID for identity verification, so RAPID may not be included.
  • contention resolution ID UE Contention Resolution ID
  • the subsequent RAR The format can no longer be distinguished and indicated.
  • the corresponding fallback RAR format may include at least the following fields:
  • -T2 field (such as 1bit): used to indicate that the format of the current MAC RAR message is the fallback RAR format or the successful RAR format; for example, if the value of the T2 field is 0 or 1, 0 means fallback RAR format, 1 means If the RAR format is successful, the value of the T2 field shown in Figure 6A and Figure 6B is 0; the value of note is that the T2 field can be optionally replaced by the R field, and the format of the RAR message is no longer indicated;
  • -R domain (such as 1bit): reserved bits; for example, the value of R domain can be 0;
  • -RAPID field (such as 6 bits), used to correspond to the preamble code used in random access messages (such as MsgA).
  • -TAC field (such as 12bits): used to send the terminal's uplink advance
  • -UL Grant field (such as 27bits): used to allocate uplink grants for the terminal to transmit random access messages
  • -T-C-RNTI field (for example, 16 bits): used to allocate a temporary C-RNTI to the fallback UE.
  • the corresponding successful RAR format may include at least the following fields:
  • -R domain (such as 1bit): reserved bits; for example, the value of R domain can be 0;
  • -TAC field (such as 12bits): used to send the terminal's uplink advance
  • -C-RNTI field (such as 16 bits): used to allocate C-RNTI for successful UEs;
  • UE Contention Resolution ID (UE Contention Resolution ID) field (for example, 48 bits): used to send the content of the CCCH information in the terminal MsgA; if the size of the CCCH information exceeds 48 bits, the first 48 bits of the CCCH information can be filled in.
  • the network device may multiplex response messages to multiple terminals for transmission, as shown in Figure 6D.
  • the MAC RAR subheader (including BI information) of UE1 and the fallback RAR message of UE2 may be used as shown in Figure 6D.
  • UE3's successful RAR message and so on are multiplexed together for transmission.
  • the successful RAR format does not include the RAPID field separately for the following reasons:
  • the CCCH information can include The SI request message does not need to use a special Preamble code to represent the SI request message, so the RAPID field may not be included, and the contention resolution identifier in the successful RAR format can be directly used to correspond to the CCCH information sent by the terminal to respond to the terminal's request for SI If successful, the same effect can be achieved; on the other hand, if a separate RAPID format is required, you can give the RAPID format a special value in the T field; or, first divide the separate RAPID format into a fallback RAR format one Class, share the same T field indication with the fallback RAR format, and then replace the first R field with the T2 field in the fallback RAR format, indicating that it is a separate RAPID format or a normal
  • the MAC RAR subheader and the MAC RAR are arranged in full bytes respectively, resulting in multiple R bits in each. If MAC RAR subheader and MAC RAR are combined together, although the independent design of MAC RAR subheader and MAC RAR may be broken, the overall length and Rbit size can be reduced, and the overhead can be reduced.
  • the format of the combined MAC RAR subheader and MAC RAR can be shown in FIG. 7.
  • the corresponding merged format can be understood as the MAC RAR subheader shown in Fig. 5B and the successful RAR format shown in Fig. 6C are merged together.
  • the terminal behavior will not change, only the RAR format is changed, and the response content included is similar.
  • the biggest difference is that RAPID is no longer included in the successful RAR message.
  • RAPID can only be used to initially determine the preamble used by the uplink terminal corresponding to the response, but the actual two terminals may use the same preamble, so the terminal identity is finally determined It is still necessary to compare the contention resolution identification, so not carrying RAPID in the successful RAR message does not affect the final confirmation terminal.
  • the foregoing step 203 may include at least one of the following:
  • the indication information indicates that the RAR message includes BI information
  • the indication information indicates that the format of the RAR message is a fallback RAR format, perform a fallback operation
  • the indication information indicates that the format of the RAR message is a successful RAR format
  • the RAR message includes a contention resolution identifier and the contention resolution identifier is successfully verified, it is determined that the random access process is successful
  • the indication information indicates that the format of the RAR message is a successful RAR format
  • the RAR message includes RAPID and a contention resolution identifier, and the verification of the RAPID and contention resolution identifier is successful, a random access process is determined success
  • the indication information indicates that the format of the RAR message is a successful RAR format
  • the RAR message includes a contention resolution identifier and the contention resolution identifier is successfully verified
  • the RAR message includes terminal-specific Data, according to the terminal-specific data indicated by the instruction information, receive processing of related data
  • the indication information indicates that the format of the RAR message is a successful RAR format
  • the RAR message includes RAPID and a contention resolution identifier
  • the verification of the RAPID and contention resolution identifier is successful
  • the RAR message It includes terminal-specific data, and the relevant data is received according to the situation of the terminal-specific data indicated by the indication information.
  • the terminal can distinguish different response situations of the network device and perform corresponding processing, thereby reducing the delay and processing complexity in the random access process.
  • the following takes the 2-step random access process as an example to describe the terminal behavior in detail.
  • the terminal can use the Preamble code and/or related RNTI to parse the PDCCH in the Msg B window; if it detects that the RAPID corresponding to its own Preamble code is included in the response In the message, it is determined that the network device has correctly received the SI request, and then waits to receive the SI, and the random access process of the SI request is successful.
  • the terminal can use the Preamble code and/or in the MsgB window. Or the relevant RNTI parses the PDCCH; if it is detected that the RAPID corresponding to its own Preamble code is included in the response message, then:
  • the terminal can fall back to the 4-step RACH process to initiate Msg3 transmission according to the UL grant indicated in the fallback RAR format;
  • the terminal can parse the RAR message according to the successful RAR format, and compare the bit stream carried in the contention resolution identification field with the CCCH information previously sent by itself; If it succeeds, it is determined that the contention resolution is successful, and the random access process is successful. If the comparison fails, it is determined that this is not a response message for itself, and the monitoring continues. It should be pointed out that if the contention is resolved successfully, and it is found that the successful RAR message also includes additional Downlink Shared Channel (DL-SCH) data, the terminal can proceed according to the number of terminal-specific data indicated in the RAR Analyze the DL-SCH data one by one and submit it to the higher level for processing.
  • DL-SCH Downlink Shared Channel
  • the terminal can follow the instructions and header instructions of each RAR format, skip the RAR format and possible DL-SCH format that do not belong to itself in turn, and try to perform subsequent RAPID Compare and RAR analysis until you find your own response.
  • the terminal can determine that the random access process has failed, and according to the received in the Msg B window After a certain random delay, the next random access failure is initiated until the preset maximum number of random access attempts is reached, and the random access failure is reported to the higher layer.
  • FIG. 8 is a flowchart of a random access response method provided by an embodiment of the present disclosure. The method is applied to a network device. As shown in FIG. 8, the method includes the following steps:
  • Step 801 Receive a random access message from the terminal.
  • Step 802 Send a RAR message to the terminal.
  • the RAR message includes indication information, and the indication information indicates a format type of the RAR message.
  • the random access response method of the embodiment of the present disclosure with the help of the indication information included in the RAR message, it is possible to at least clarify what content the RAR message includes in the random access process (such as the 2-step random access process), so that the terminal can distinguish Different response conditions of network equipment, thereby reducing the delay and processing complexity in the random access process.
  • the random access process such as the 2-step random access process
  • the indication information includes a first indication field, and the first indication field indicates that the RAR message includes BI information or RAR information.
  • the RAR information includes: RAPID.
  • the indication information further includes a second indication field, and the second indication field indicates that the format of the RAR message is fallback RAR format, or successful RAR format.
  • the indication information indicates that the format of the RAR message is a successful RAR format
  • the indication information further includes a third indication field
  • the third indication field indicates that the RAR message includes terminal-specific data Case.
  • the third indication field indicates whether the RAR message includes terminal-specific data
  • the third indication field indicates whether the RAR message includes terminal-specific data, and when the RAR message includes terminal-specific data, the RAR message The number of terminal-specific data included.
  • the indication information includes a fourth indication field, and the fourth indication field indicates any one of the following:
  • the RAR message includes BI information
  • the format of the RAR message is a fallback RAR format
  • the format of the RAR message is a successful RAR format
  • the number of terminal-specific data included in the RAR message is the number of terminal-specific data included in the RAR message.
  • the RAR message includes RAPID
  • RAPID is not included in the RAR message.
  • the terminal-specific data is: at least one of MAC SDU and MAC CE.
  • FIG. 9 is a flowchart of a random access method provided by an embodiment of the present disclosure. The method is applied to a terminal. As shown in FIG. 9, the method includes the following steps:
  • Step 901 Send a random access message to the network device.
  • the random access message may be referred to as a random access request message, Msg1 or MsgA.
  • the random access message may include C-RNTI.
  • Step 902 Receive a RAR message from the network device.
  • the RAR message includes control information corresponding to terminal requirements.
  • Step 903 According to the control information, it is determined that the random access process is successful.
  • the random access method in the embodiments of the present disclosure based on the control information included in the RAR message, it is possible to at least clarify what content the RAR message includes in the random access process (such as the 2-step random access process), so that the terminal can distinguish between networks Different response conditions of the equipment, thereby reducing the delay and processing complexity in the random access process.
  • the random access process such as the 2-step random access process
  • control information may include but is not limited to any of the following:
  • TAC of preset length and uplink scheduling authorization are preset length and uplink scheduling authorization.
  • the terminal when the terminal is in the RRC connected state, the terminal may also initiate a random access process due to the arrival of uplink data or a beam failure recovery (Beam Failure Recovery) trigger.
  • the Msg A of the connected terminal usually includes its own C-RNTI to inform the network equipment of the identity of the terminal; in addition, the Msg A may also include some information about the buffer status report (Buffer Status Report, BSR) or beam failure. After receiving this information, the network device responds according to the terminal demand.
  • BSR Buffer Status Report
  • a possible response is that the network device issues to the terminal the uplink scheduling signaling that uses the C-RNTI to parse the PDCCH (PDCCH addressed by C-RNTI). If the terminal receives its own dedicated uplink scheduling signaling, the terminal can determine that the network device correctly receives the MsgA, and can further determine that the 2-step random access process is successful, and then perform corresponding transmission according to the network scheduling.
  • the network device can send to the terminal a scheduling signaling that uses C-RNTI to resolve PDCCH on the corresponding new beam resource after beam failure recovery.
  • This scheduling signaling can be Upstream can also be downstream. Since the response message is sent on the new beam resource, after receiving the message, the terminal can determine that the MsgA is successfully received, and further determine that the random access process is successful.
  • the network device may update the terminal's uplink synchronization TA, or may send a traditional TAC MAC CE to the terminal for the terminal to adjust the TA. Therefore, after the terminal sends the MsgA including the C-RNTI, if it receives the dedicated TAC MAC CE sent by the network device in the MsgB window, it can determine that the corresponding random access process is successful.
  • the network device needs to send TA information to the terminal, which is different from the TAC included in the traditional MAC CE.
  • the traditional TAC is used to adjust the currently existing TA, which is an offset, and the initial value of the TA is needed before the uplink synchronization is established.
  • the TAC in the traditional MAC CE format is 6 bits, and the TAC for establishing initial synchronization is a preset length such as 12 bits.
  • the TAC included in the MAC RAR message is 12 bits.
  • the network device may send a TAC signaling of a preset length, such as a special TAC signaling with a length of 12 bits, to the terminal for the UE to establish initial uplink synchronization.
  • the terminal can confirm the success of the random access process according to the special TAC signaling with a length of 12 bits.
  • the aforementioned TAC of the preset length may be indicated by an LCID.
  • a special LCID indication field can be allocated in the MAC subheader to indicate the 12-bit TAC.
  • the corresponding MAC CE format may be as shown in FIG. 10B.
  • the MAC CE format includes 12 bits of TAC.
  • the MAC CE format including the 12-bit TAC may also include a T field (such as 1 bit) and a UL Grant field (such as 27 bits).
  • the T field indication includes a separate TAC field, or includes TAC domain and UL Grant domain.
  • the format of the UL Grant mentioned above can also adopt other forms, such as the form of Downlink Control Information (DCI) authorized MAC CE, which includes at least time-frequency resource location and HARQ process identifier. , Redundancy Version (RV), Supplement Uplink (Supplement Uplink, SUL) indication and other information.
  • DCI Downlink Control Information
  • RV Redundancy Version
  • SUL Supplement Uplink
  • two special LCIDs can also be used to indicate whether it is 12bit TAC, 12bit TAC and UL Grant, or the MAC subheader includes the L field. Based on the length of the L field, it indicates whether it is a separate 12bit TAC or 12bit TAC and UL Grant.
  • the aforementioned TAC of the preset length may be indicated by the first indication field in the MAC header.
  • the first indication field may be the first R field in the MAC subheader, and is indicated by other values different from the first R field.
  • the data transmitted on DL-SCH usually starts with MAC subheader, and the first bit of all MAC subheaders is the R field, and the value is 0. Therefore, in order to distinguish the 12-bit TAC as quickly as possible, as shown in Figure 11, the first R field in the MAC subheader can be set to 1.
  • the corresponding MAC subPDU format may be shown in FIG. 11B, and the MAC subPDU format includes a 12-bit TAC.
  • the MAC subPDU format including the 12-bit TAC may also include a T field (such as 1 bit) and a UL Grant field (such as 27 bits).
  • the T field indication includes a separate TAC field, or includes TAC domain and UL Grant domain.
  • the terminal can learn that this is a special 12-bit TAC (or UL Grant). For the terminal that has sent the MsgA, if it receives the 12-bit TAC included in the scheduling signaling of the PDCCH using the C-RNTI to analyze the PDCCH, it can be determined that the random access process is successful.
  • the terminal in addition to monitoring its own C-RNTI, the terminal can also simultaneously monitor the RA-RNTI used to parse the PDCCH; if it receives its own fallback RAR message, the terminal can perform a fallback operation. If the terminal does not receive either the fallback RAR message or the successful RAR message in the MsgB window, it can be determined that the random access process has failed, and the random access process is performed again after the fallback delay according to the BI indication.
  • FIG. 12 is a schematic structural diagram of a terminal provided by an embodiment of the present disclosure.
  • the terminal 120 includes:
  • the first sending module 121 is configured to send a random access message to a network device
  • the first receiving module 122 is configured to receive a RAR message from the network device, where the RAR message includes indication information, and the indication information indicates a format type of the RAR message;
  • the execution module 123 is configured to execute a corresponding random access operation according to the instruction information.
  • the terminal of the embodiment of the present disclosure performs a corresponding random access operation according to the indication information included in the RAR message.
  • the indication information indicates the format type of the RAR message, and at least the random access process (such as the 2-step random access process) What content is included in the RAR message in ), so that different response situations of network devices can be distinguished, and the delay and processing complexity in the random access process can be reduced.
  • the indication information includes a first indication field, and the first indication field indicates that the RAR message includes backoff indication BI information or RAR information.
  • the RAR information includes RAPID.
  • the indication information further includes a second indication field, and the second indication field indicates that the format of the RAR message is fallback RAR format, or successful RAR format.
  • the indication information indicates that the format of the RAR message is a successful RAR format
  • the indication information further includes a third indication field
  • the third indication field indicates that the RAR message includes terminal-specific data Case.
  • the third indication field indicates whether the RAR message includes terminal-specific data; or, when the third indication field is at least 1 bit, the The third indication field indicates whether the RAR message includes terminal-specific data, and if the RAR message includes terminal-specific data, the number of terminal-specific data included in the RAR message.
  • the indication information may include a fourth indication field, and the fourth indication field indicates any one of the following:
  • the RAR message includes BI information
  • the format of the RAR message is a fallback RAR format
  • the format of the RAR message is a successful RAR format
  • the number of terminal-specific data included in the RAR message is the number of terminal-specific data included in the RAR message.
  • the RAR message includes RAPID
  • RAPID is not included in the RAR message.
  • the terminal-specific data is: at least one of MAC SDU and MAC CE.
  • the execution module 123 is configured to execute any one of the following:
  • the indication information indicates that the RAR message includes BI information
  • the indication information indicates that the format of the RAR message is a fallback RAR format, perform a fallback operation
  • the indication information indicates that the format of the RAR message is a successful RAR format
  • the RAR message includes a contention resolution identifier and the contention resolution identifier is successfully verified, it is determined that the random access process is successful
  • the indication information indicates that the format of the RAR message is a successful RAR format
  • the RAR message includes RAPID and a contention resolution identifier, and the verification of the RAPID and contention resolution identifier is successful, a random access process is determined success
  • the indication information indicates that the format of the RAR message is a successful RAR format
  • the RAR message includes a contention resolution identifier and the contention resolution identifier is successfully verified
  • the RAR message includes terminal-specific Data, according to the terminal-specific data indicated by the instruction information, receive processing of related data
  • the indication information indicates that the format of the RAR message is a successful RAR format
  • the RAR message includes RAPID and a contention resolution identifier
  • the verification of the RAPID and contention resolution identifier is successful
  • the RAR message It includes terminal-specific data, and the relevant data is received according to the situation of the terminal-specific data indicated by the indication information.
  • FIG. 13 is a schematic structural diagram of a network device provided by an embodiment of the present disclosure. As shown in FIG. 13, the network device 130 includes:
  • the second receiving module 131 is configured to receive a random access message from the terminal
  • the second sending module 132 is configured to send RAR messages to the terminal
  • the RAR message includes indication information, and the indication information indicates a format type of the RAR message.
  • the network device of the embodiment of the present disclosure with the help of the indication information included in the RAR message, can at least clarify what content the RAR message includes in the random access process (such as the 2-step random access process), so that the terminal can distinguish between different network devices. Respond to the situation, thereby reducing the delay and processing complexity in the random access process.
  • the random access process such as the 2-step random access process
  • the indication information includes a first indication field, and the first indication field indicates that the RAR message includes BI information or RAR information.
  • the RAR information includes: RAPID.
  • the indication information further includes a second indication field, and the second indication field indicates that the format of the RAR message is fallback RAR format, or successful RAR format.
  • the indication information indicates that the format of the RAR message is a successful RAR format
  • the indication information further includes a third indication field
  • the third indication field indicates that the RAR message includes terminal-specific data Case.
  • the third indication field indicates whether the RAR message includes terminal-specific data; or, when the third indication field is at least 1 bit, the The third indication field indicates whether the RAR message includes terminal-specific data, and if the RAR message includes terminal-specific data, the number of terminal-specific data included in the RAR message.
  • the indication information may include a fourth indication field, and the fourth indication field indicates any one of the following:
  • the RAR message includes BI information
  • the format of the RAR message is a fallback RAR format
  • the format of the RAR message is a successful RAR format
  • the number of terminal-specific data included in the RAR message is the number of terminal-specific data included in the RAR message.
  • the RAR message includes RAPID
  • RAPID is not included in the RAR message.
  • the terminal-specific data is: at least one of MAC SDU and MAC CE.
  • FIG. 14 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.
  • the terminal 140 includes:
  • the third sending module 141 is configured to send a random access message to a network device
  • the third receiving module 142 is configured to receive a RAR message from the network device, where the RAR message includes control information corresponding to terminal requirements;
  • the determining module 143 is configured to determine that the random access process is successful according to the control information.
  • the terminal of the embodiment of the present disclosure can at least clarify what content the RAR message includes in a random access process (such as a 2-step random access process), thereby distinguishing different response situations of network devices , Thereby reducing the delay and processing complexity in the random access process.
  • a random access process such as a 2-step random access process
  • control information may include any one of the following:
  • TAC of preset length and uplink scheduling authorization are preset length and uplink scheduling authorization.
  • the control information includes a TAC of a preset length
  • the TAC of a preset length is indicated by a logical channel identifier LCID
  • the TAC of the preset length is indicated by the first indication field in the MAC header.
  • the embodiment of the present disclosure also provides a communication device including a processor, a memory, and a computer program stored on the memory and capable of running on the processor.
  • a communication device including a processor, a memory, and a computer program stored on the memory and capable of running on the processor.
  • the computer program is executed by the processor, Implement each process of the random access method embodiment shown in FIG. 2, or implement each process of the random access response method embodiment shown in FIG. 8, or implement the random access method implementation shown in FIG. 9
  • Each process of the example can achieve the same technical effect. To avoid repetition, I won’t repeat it here.
  • the communication device can be a terminal or a network device.
  • FIG. 15 is a schematic diagram of the hardware structure of a terminal implementing various embodiments of the present disclosure.
  • the terminal 1500 includes but is not limited to: a radio frequency unit 1501, a network module 1502, an audio output unit 1503, an input unit 1504, a sensor 1505, and a display unit. 1506, user input unit 1507, interface unit 1508, memory 1509, processor 1510, power supply 1511 and other components.
  • the terminal structure shown in FIG. 15 does not constitute a limitation on the terminal, and the terminal may include more or fewer components than shown in the figure, or combine some components, or arrange different components.
  • terminals include, but are not limited to, mobile phones, tablet computers, notebook computers, palmtop computers, vehicle-mounted terminals, wearable devices, and pedometers.
  • the radio frequency unit 1501 is configured to send a random access message to a network device and receive a RAR message from the network device, where the RAR message includes indication information, and the indication information indicates the format type of the RAR message;
  • the processor 1510 is configured to perform a corresponding random access operation according to the instruction information.
  • the radio frequency unit 1501 is configured to send a random access message to a network device; to receive a RAR message from the network device, the RAR message includes control information corresponding to terminal requirements; the processor 1510 is configured to control Information to determine the success of the random access process.
  • the terminal 1500 can distinguish different response conditions of network devices, thereby reducing the random access process Delay and processing complexity.
  • terminal 1500 of the embodiment of the present disclosure can implement each process implemented in the method embodiment shown in FIG. 2, or implement each process implemented in the method embodiment shown in FIG. 8, and achieve the same benefits.
  • the effect, in order to avoid repetition, will not be repeated here.
  • the radio frequency unit 1501 can be used for receiving and sending signals in the process of sending and receiving information or talking. Specifically, after receiving the downlink data from the base station, it is processed by the processor 1510; Uplink data is sent to the base station.
  • the radio frequency unit 1501 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • the radio frequency unit 1501 can also communicate with the network and other devices through a wireless communication system.
  • the terminal provides users with wireless broadband Internet access through the network module 1502, such as helping users to send and receive emails, browse web pages, and access streaming media.
  • the audio output unit 1503 may convert the audio data received by the radio frequency unit 1501 or the network module 1502 or stored in the memory 1509 into audio signals and output them as sounds. Moreover, the audio output unit 1503 may also provide audio output related to a specific function performed by the terminal 1500 (for example, call signal reception sound, message reception sound, etc.).
  • the audio output unit 1503 includes a speaker, a buzzer, and a receiver.
  • the input unit 1504 is used to receive audio or video signals.
  • the input unit 1504 may include a graphics processing unit (GPU) 15041 and a microphone 15042, and the graphics processor 15041 is configured to respond to still pictures or video images obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. Data is processed.
  • the processed image frame may be displayed on the display unit 1506.
  • the image frame processed by the graphics processor 15041 may be stored in the memory 1509 (or other storage medium) or sent via the radio frequency unit 1501 or the network module 1502.
  • the microphone 15042 can receive sound, and can process such sound into audio data.
  • the processed audio data can be converted into a format that can be sent to a mobile communication base station via the radio frequency unit 1501 in the case of a telephone call mode for output.
  • the terminal 1500 also includes at least one sensor 1505, such as a light sensor, a motion sensor, and other sensors.
  • the light sensor includes an ambient light sensor and a proximity sensor.
  • the ambient light sensor can adjust the brightness of the display panel 15061 according to the brightness of the ambient light.
  • the proximity sensor can close the display panel 15061 and/or when the terminal 1500 is moved to the ear. Or backlight.
  • the accelerometer sensor can detect the magnitude of acceleration in various directions (usually three-axis), and can detect the magnitude and direction of gravity when stationary, and can be used to identify terminal posture (such as horizontal and vertical screen switching, related games, Magnetometer attitude calibration), vibration recognition related functions (such as pedometer, percussion), etc.; the sensor 1505 can also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared Sensors, etc., will not be repeated here.
  • the display unit 1506 is used to display information input by the user or information provided to the user.
  • the display unit 1506 may include a display panel 15061, and the display panel 15061 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc.
  • LCD liquid crystal display
  • OLED organic light-emitting diode
  • the user input unit 1507 may be used to receive inputted numeric or character information, and generate key signal input related to user settings and function control of the terminal.
  • the user input unit 1507 includes a touch panel 15071 and other input devices 15072.
  • the touch panel 15071 also called a touch screen, can collect the user's touch operations on or near it (for example, the user uses any suitable objects or accessories such as fingers, stylus, etc.) on the touch panel 15071 or near the touch panel 15071. operating).
  • the touch panel 15071 may include two parts, a touch detection device and a touch controller.
  • the touch detection device detects the user's touch position, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it
  • the processor 1510 receives and executes the command sent by the processor 1510.
  • the touch panel 15071 can be implemented in multiple types such as resistive, capacitive, infrared, and surface acoustic wave.
  • the user input unit 1507 may also include other input devices 15072.
  • other input devices 15072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackball, mouse, and joystick, which will not be repeated here.
  • the touch panel 15071 can be overlaid on the display panel 15061.
  • the touch panel 15071 detects a touch operation on or near it, it transmits it to the processor 1510 to determine the type of the touch event, and then the processor 1510 determines the type of the touch event.
  • the type of event provides corresponding visual output on the display panel 15061.
  • the touch panel 15071 and the display panel 15061 are used as two independent components to realize the input and output functions of the terminal, but in some embodiments, the touch panel 15071 and the display panel 15061 can be integrated. Realize the input and output functions of the terminal, which is not limited here.
  • the interface unit 1508 is an interface for connecting an external device and the terminal 1500.
  • the external device may include a wired or wireless headset port, an external power source (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, audio input/output (I/O) port, video I/O port, headphone port, etc.
  • the interface unit 1508 can be used to receive input (for example, data information, power, etc.) from an external device and transmit the received input to one or more elements in the terminal 1500 or can be used to communicate between the terminal 1500 and the external device. transfer data.
  • the memory 1509 can be used to store software programs and various data.
  • the memory 1509 may mainly include a program storage area and a data storage area.
  • the program storage area may store an operating system, an application program required by at least one function (such as a sound playback function, an image playback function, etc.), etc.; Data (such as audio data, phone book, etc.) created by the use of mobile phones.
  • the memory 1509 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices.
  • the processor 1510 is the control center of the terminal. It uses various interfaces and lines to connect various parts of the entire terminal. It executes by running or executing software programs and/or modules stored in the memory 1509, and calling data stored in the memory 1509. Various functions of the terminal and processing data, so as to monitor the terminal as a whole.
  • the processor 1510 may include one or more processing units; optionally, the processor 1510 may integrate an application processor and a modem processor, where the application processor mainly processes the operating system, user interface, and application programs, etc.
  • the adjustment processor mainly deals with wireless communication. It can be understood that the foregoing modem processor may not be integrated into the processor 1510.
  • the terminal 1500 may also include a power supply 1511 (such as a battery) for supplying power to various components.
  • a power supply 1511 such as a battery
  • the power supply 1511 may be logically connected to the processor 1510 through a power management system, so as to manage charging, discharging, and power consumption management through the power management system. And other functions.
  • terminal 1500 may also include some functional modules that are not shown, which will not be repeated here.
  • FIG. 16 is a schematic diagram of the hardware structure of a network device that implements various embodiments of the present disclosure.
  • the network device 160 includes, but is not limited to: a bus 161, a transceiver 162, an antenna 163, a bus interface 164, a processor 165, and Storage 166.
  • the network device 160 further includes: a computer program stored on the memory 166 and capable of running on the processor 165.
  • a computer program stored on the memory 166 and capable of running on the processor 165.
  • the following steps are implemented:
  • the RAR message is sent to the terminal; the RAR message includes indication information, and the indication information indicates the format type of the RAR message.
  • the network device 160 of the embodiment of the present disclosure can implement the various processes implemented in the method embodiment shown in FIG. 9 and achieve the same beneficial effects. To avoid repetition, details are not described herein again.
  • the transceiver 162 is used to receive and send data under the control of the processor 165.
  • bus 161 may include any number of interconnected buses and bridges, bus 161 will include one or more processors represented by processor 165 and memory represented by memory 166
  • the various circuits are linked together.
  • the bus 161 may also link various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, no further descriptions thereof are provided herein.
  • the bus interface 164 provides an interface between the bus 161 and the transceiver 162.
  • the transceiver 162 may be one element or multiple elements, such as multiple receivers and transmitters, and provide a unit for communicating with various other devices on the transmission medium.
  • the data processed by the processor 165 is transmitted on the wireless medium through the antenna 163, and further, the antenna 163 also receives the data and transmits the data to the processor 165.
  • the processor 165 is responsible for managing the bus 161 and general processing, and can also provide various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the memory 166 may be used to store data used by the processor 165 when performing operations.
  • the processor 165 may be a CPU, ASIC, FPGA, or CPLD.
  • the embodiment of the present disclosure also provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, each process of the random access method embodiment shown in FIG. 2 is realized. Either implement each process of the random access response method embodiment shown in FIG. 8, or implement each process of the random access method embodiment shown in FIG. 9, and achieve the same technical effect. To avoid repetition, I won't repeat it here.
  • the computer-readable storage medium is, for example, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk, or an optical disk.
  • the method of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. ⁇
  • the technical solution of the present disclosure essentially or the part that contributes to the related technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk). ) Includes several instructions to make a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the method described in each embodiment of the present disclosure.

Landscapes

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

Abstract

本公开提供一种随机接入方法、响应方法、终端及网络设备,该随机接入方法包括:向网络设备发送随机接入消息;从所述网络设备接收RAR消息,所述RAR消息中包括指示信息,所述指示信息指示所述RAR消息的格式类型;根据所述指示信息,执行相应的随机接入操作。

Description

随机接入方法、响应方法、终端及网络设备
相关申请的交叉引用
本申请主张在2019年6月14日在中国提交的中国专利申请No.201910517640.2的优先权,其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域,尤其涉及一种随机接入方法、响应方法、终端及网络设备。
背景技术
与相关技术中的4步随机接入过程相比,目前引入了一种新的随机接入过程,即2步随机接入过程。在2步随机接入过程中,首先终端可触发2步随机接入过程,将随机接入消息发送至网络设备,然后网络设备在接收到随机接入消息之后,可发送随机接入响应(Random Access Response,RAR)消息至终端。
然而,目前虽引入了2步随机接入过程,但是对于RAR消息包括哪些内容却没有定论,使得终端无法区分不同的响应情况。
发明内容
本公开实施例提供一种随机接入方法、响应方法、终端及网络设备,以解决目前尚未明确2步随机接入过程中的RAR消息包括哪些内容,使得终端无法区分不同的响应情况的问题。
为了解决上述技术问题,本公开实施例是这样实现的:
第一方面,本公开实施例提供了一种随机接入方法,应用于终端,包括:
向网络设备发送随机接入消息;
从所述网络设备接收RAR消息,所述RAR消息中包括指示信息,所述指示信息指示所述RAR消息的格式类型;
根据所述指示信息,执行相应的随机接入操作。
第二方面,本公开实施例提供了一种随机接入的响应方法,应用于网络设备,包括:
从终端接收随机接入消息;
向所述终端发送RAR消息;
其中,所述RAR消息中包括指示信息,所述指示信息指示所述RAR消息的格式类型。
第三方面,本公开实施例提供了一种随机接入方法,应用于终端,包括:
向网络设备发送随机接入消息;
从所述网络设备接收RAR消息,所述RAR消息中包括与终端需求对应的控制信息;
根据所述控制信息,确定随机接入过程成功。
第四方面,本公开实施例提供了一种终端,包括:
第一发送模块,用于向网络设备发送随机接入消息;
第一接收模块,用于从所述网络设备接收RAR消息,所述RAR消息中包括指示信息,所述指示信息指示所述RAR消息的格式类型;
执行模块,用于根据所述指示信息,执行相应的随机接入操作。
第五方面,本公开实施例提供了一种网络设备,包括:
第二接收模块,用于从终端接收随机接入消息;
第二发送模块,用于向所述终端发送RAR消息;
其中,所述RAR消息中包括指示信息,所述指示信息指示所述RAR消息的格式类型。
第六方面,本公开实施例提供了一种终端,包括:
第三发送模块,用于向网络设备发送随机接入消息;
第三接收模块,用于从所述网络设备接收RAR消息,所述RAR消息中包括与终端需求对应的控制信息;
确定模块,用于根据所述控制信息,确定随机接入过程成功。
第七方面,本公开实施例提供了一种终端,包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序,其中,所述计算机程序被所述处理器执行时实现上述的第一方面中随机接入方法的步骤,或者 实现上述的第二方面中随机接入的响应方法的步骤,或者实现上述的第三方面中随机接入方法的步骤。
第八方面,本公开实施例提供了一种计算机可读存储介质,其上存储有计算机程序,其中,所述计算机程序被处理器执行时实现上述的第一方面中随机接入方法的步骤,或者实现上述的第二方面中随机接入的响应方法的步骤,或者实现上述的第三方面中随机接入方法的步骤。
在本公开实施例中,通过根据RAR消息中包括的指示信息,执行相应的随机接入操作,该指示信息指示RAR消息的格式类型,至少可以明确随机接入过程(比如2步随机接入过程)中的RAR消息包括哪些内容,从而使得终端可以区分网络设备不同的响应情况,从而降低随机接入过程中的时延和处理复杂度。
附图说明
为了更清楚地说明本公开实施例的技术方案,下面将对本公开实施例中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本公开的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动性的前提下,还可以根据这些附图获得其他的附图。
图1为本公开实施例的2步随机接入过程的流程图;
图2为本公开实施例的随机接入方法的流程图之一;
图3A为本公开实施例的包括BI信息的MAC RAR subheader格式的示意图之一;
图3B为本公开实施例的包括RAPID的MAC RAR subheader格式的示意图;
图4A为本公开实施例的回退RAR格式的示意图之一;
图4B为本公开实施例的成功RAR格式的示意图之一;
图4C为本公开实施例的将多个RAR消息复用发送的示意图之一;
图5A为本公开实施例的包括BI信息的MAC RAR subheader格式的示意图之二;
图5B为本公开实施例的除包括BI信息之外的其他MAC RAR subheader 格式的示意图;
图6A为本公开实施例的回退RAR格式的示意图之二;
图6B为本公开实施例的回退RAR格式的示意图之三;
图6C为本公开实施例的成功RAR格式的示意图之二;
图6D为本公开实施例的将多个RAR消息复用发送的示意图之二;
图7为本公开实施例的将MAC RAR subheader和MAC RAR合并后的格式示意图;
图8为本公开实施例的随机接入的响应方法的流程图;
图9为本公开实施例的随机接入方法的流程图之二;
图10A为本公开实施例的MAC subheader的格式示意图之一;
图10B为本公开实施例的MAC CE格式的示意图之一;
图10C为本公开实施例的MAC CE格式的示意图之二;
图11A为本公开实施例的MAC subheader的格式示意图之二;
图11B为本公开实施例的MAC subPDU格式的示意图之一;
图11C为本公开实施例的MAC subPDU格式的示意图之二;
图12为本公开实施例的终端的结构示意图之一;
图13为本公开实施例的网络设备的结构示意图之一;
图14为本公开实施例的终端的结构示意图之二;
图15为本公开实施例的终端的结构示意图之三;
图16为本公开实施例的网络设备的结构示意图之二。
具体实施方式
为了更清楚地说明本公开实施例的技术方案,下面将对本公开实施例中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本公开的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动性的前提下,还可以根据这些附图获得其他的附图。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象,而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换,以便这里描述的本申请的实施例例如能够以除 了在这里图示或描述的那些以外的顺序实施。此外,术语“包括”和“具有”以及他们的任何变形,意图在于覆盖不排他的包含,例如,包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元,而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本公开实施例中无线通信系统包括终端和网络设备。终端也可以称作终端设备或者用户终端(User Equipment,UE),终端可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、个人数字助理(Personal Digital Assistant,PDA)、移动上网装置(Mobile Internet Device,MID)、可穿戴式设备(Wearable Device)或车载设备等终端侧设备,需要说明的是,在本公开实施例中并不限定终端的具体类型。网络设备可以是基站或核心网,该基站可以是5G及以后版本的基站(例如:gNB、5G NR NB等),或者其他通信系统中的基站(例如:eNB、WLAN接入点、或其他接入点等),基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station,BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set,BSS)、扩展服务集(Extended Service Set,ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点或所述领域中其他某个合适的术语,只要达到相同的技术效果,不限于特定技术词汇。
可选地,本公开实施例适用的场景可为2步随机接入(2-step RACH)过程。如图1所示,该2-step RACH过程可包括以下步骤:
步骤11:网络设备为终端配置2步随机接入的配置信息;该配置信息比如包括随机接入消息和随机接入响应消息对应的发送资源信息;该随机接入消息可称为随机接入请求消息或者MsgA;该随机接入响应消息可称为MsgB;
步骤12:终端触发2步随机接入过程,将MsgA发送至网络设备;该Msg1可通过物理上行共享信道(Physical Uplink Shared Channel,PUSCH)发送,该Msg1中至少包括请求数据data和终端标识ID;
步骤13:网络设备返回MsgB至终端。若终端接收MsgB失败,则终端可以重新发送MsgA。
对于2-step RACH过程而言,MsgA可相当于合并4-step RACH过程中 Msg1和Msg3包括的内容,MsgB可相当于合并4-step RACH过程中Msg2和Msg4包括的内容。而MsgB反馈的响应情况可包括以下任意一种:1)针对MsgA包括公共控制信道(common control channel,CCCH)信息的情况,MsgB可指示以下至少一项:回退指示(Backoff Indicator,BI)信息、回退的RAR消息、成功的RAR消息;而成功的RAR消息可包括终端专用下行数据;2)针对MsgA包含小区无线网络临时标识(Cell-Radio Network Tempory Identity,C-RNTI)的情况,网络设备需要响应终端,以使得利用C-RNTI解析物理下行控制信道(Physical Downlink Control Channel,PDCCH)的调度信令包括定时提前命令(Timing Advanced Command,TAC)或者上行授权的方式,告知终端竞争解决成功。
可选地,当终端发送了包含CCCH信息的MsgA之后,终端可在MsgB窗口中监听利用RA-RNTI解析PDCCH(PDCCH addressed to RA-RNTI)的调度信令:
1)若接收到自身的回退的RAR消息(fallback RAR),则终端可执行回退操作(fallback操作),并回退到4-step RACH过程;
2)若接收到自身的成功的RAR消息(success RAR),且竞争解决标识验证成功,则终端可确认随机接入过程成功;
3)若接收到自身的成功的RAR消息,且竞争解决标识验证成功,则终端可根据网络设备指示的包含终端专用SRB或者数据的情况,进行相关数据的接收处理,并确认随机接入过程成功;
4)若在MsgB窗口中既没有接收到给自身的回退的RAR消息,也没有接收到给自身的成功的RAR消息,则终端可在根据BI信息进行回退操作之后,重新尝试2-step RACH过程。
可选地,当终端发送了包含C-RNTI的MsgA之后,终端可在MsgB窗口中监听利用RA-RNTI解析PDCCH(PDCCH addressed to RA-RNTI)和利用C-RNTI解析PDCCH(PDCCH addressed to C-RNTI)的调度信令:
1)若接收到自身的回退的RAR消息,则终端可执行回退操作,并回退到4-step RACH过程;
2)若接收到的利用C-RNTI解析PDCCH的调度信令中包含TAC信令和 /或上行调度资源,则终端可确认随机接入过程成功;
3)若在MsgB窗口中既没有接收到给自身的回退的RAR消息,也没有接收到给自身的成功的RAR消息,则终端可在根据BI信息进行回退操作之后,重新尝试2-step RACH过程。
下面将结合实施例和附图对本公开进行详细说明。
请参见图2,图2是本公开实施例提供的一种随机接入方法的流程图,该方法应用于终端,如图2所示,该方法包括如下步骤:
步骤201:向网络设备发送随机接入消息。
可选地,该随机接入消息可称为随机接入请求消息或者MsgA。该随机接入消息中可包括CCCH信息。
一种实施方式中,当终端处于空闲(Idle)状态或者去激活(Inactive)状态时,终端可以发起无线资源控制(Radio Resource Control,RRC)连接建立过程或者RRC连接恢复过程,此时可触发2-step RACH过程,以建立与网络设备的上行同步并完成信令交互过程。在触发2-step RACH过程时,终端在MsgA中,可以发送随机接入前导码(Preamble码),并在对应的上行PUSCH上发送类似4-step RACH过程中Msg3的MsgA,并携带CCCH信息;该CCCH信息可用于RRC连接建立或者RRC连接恢复等。
步骤202:从网络设备接收RAR消息。
可选地,所述RAR消息中可包括指示信息,所述指示信息指示所述RAR消息的格式类型。
步骤203:根据所述指示信息,执行相应的随机接入操作。
本公开实施例的随机接入方法,通过根据RAR消息中包括的指示信息,执行相应的随机接入操作,该指示信息指示RAR消息的格式类型,至少可以明确随机接入过程(比如2步随机接入过程)中的RAR消息包括哪些内容,从而使得终端可以区分网络设备不同的响应情况,从而降低随机接入过程中的时延和处理复杂度。
可理解地,对于网络设备而言,对终端MsgA的接收情况可包括以下任意一种可能情况:
-Preamble码和对应的PUSCH内容都接收成功;
-Preamble码接收成功,但对应的PUSCH内容接收失败;
-Preamble码接收失败,但对应的PUSCH内容接收成功;
-Preamble码和对应的PUSCH内容都接收失败;
进一步地,根据不同的接收情况和网络自身状态,网络设备可以响应不同内容,以指示终端下一步的行为。同时,由于RA-RNTI是按照终端发送Preamble或者MsgA的时频资源位置进行计算的,因此同一个RA-RNTI可以对应于多个终端,即为了提高响应的效率,网络设备可以将给多个终端的响应消息复用到一起进行发送。
可选地,网络设备对终端MsgA的响应内容至少可包括以下几种:
-BI信息;
-失败的RAR消息(Fallback RAR);
-成功的RAR消息(Success RAR);
-成功的RAR消息和终端专用数据(UE dedicated data)。
本公开至少一个实施例中,基于网络设备对终端随机接入消息(比如MsgA)的响应内容,上述RAR消息中包括的指示信息至少可以采用如下两种形式,说明如下。
形式一
形式一下,上述指示信息可包括第一指示域,所述第一指示域指示所述RAR消息包括BI信息,或者RAR信息。
一种实施方式中,该RAR信息可选为随机接入前导码标识(Random Access Preamble Identifier,RAPID)。
一种实施方式中,该第一指示域可为媒体接入控制(Media Access Control,MAC)RAR子头(subheader)中包括的T域,该T域也可称为T1域等。
比如,参见图3A所示,图3A为包括BI信息的MAC RAR subheader格式的示意图,该MAC RAR subheader中可至少包括以下域:
-E域(比如1bit):用于指示当前MAC subPDU是否是最后一个;比如,E域的取值可为0或1,0表示后续还有其它的MAC subPDU,1表示当前MAC subPDU是最后一个,剩余内容为填充比特;
-T域(比如1bit):类型指示信息,用于指示对应RAR消息包括BI信息 或者MAC RAR信息;比如,若T域的取值为0或1,0表示包括BI信息,1表示包括MAC RAR信息,则图3A所示的T域取值为0;
-R域(比如1bit):预留比特位;例如,R域的取值可为0;
-BI域(比如4bits):用于指示网络过载情况下的后退行为。
又比如,参见图3B所示,图3B为包括RAPID的MAC RAR subheader格式的示意图,该MAC RAR subheader中可至少包括以下域:
-E域(比如1bit):用于指示当前MAC subPDU是否是最后一个;比如,E域的取值可为0或1,0表示后续还有其它的MAC subPDU,1表示当前MAC subPDU是最后一个,剩余内容为填充比特;
-T域(比如1bit):类型指示信息,用于指示对应RAR消息包括BI信息或者MAC RAR信息;比如,若T域的取值为0或1,0表示包括BI信息,1表示包括MAC RAR信息,则图3B所示的T域取值为1;
-RAPID域(比如6bits),用于与随机接入消息(比如MsgA)所使用的preamble码对应。需指出的是,若RAPID对应的preamble码为配置给系统消息(System Information,SI)请求专用的Preamble码,后续不需要携带MAC RAR信息。
可选地,在所述第一指示域指示所述RAR消息包括RAR信息的情况下,所述指示信息还可包括第二指示域,所述第二指示域指示所述RAR消息的格式是回退RAR格式,或者成功RAR格式。
一种实施方式中,该第二指示域可选为MAC RAR消息的格式(比如回退RAR格式,或者成功RAR格式)中包括的T2域。
可选地,在所述第二指示域指示所述RAR消息的格式是成功RAR格式的情况下,所述指示信息还可包括第三指示域,所述第三指示域指示所述RAR消息包括终端专用数据的情况。
一种实施方式中,该第三指示域可选为成功RAR格式中包括的P域。
进一步地,该第三指示域可选为至少1比特。当该第三指示域为1比特时,该第三指示域指示所述RAR消息是否包括终端专用数据;或者,当该第三指示域为至少1比特时,该第三指示域指示所述RAR消息是否包括终端专用数据,以及在所述RAR消息包括终端专用数据的情况下,所述RAR消息 包括的终端专用数据的个数。
可选地,上述终端专用数据可以为:MAC服务数据单元(Service Data Unit,SDU)和MAC控制单元(Control Element,CE)中的至少一者。
比如,若终端专用数据的个数为一个,该终端专用数据可选为MAC SDU或者MAC CE;而若终端专用数据的个数为多个,该多个终端专用数据可以全部为MAC SDU,也可以全部为MAC CE,也可以一部分为MAC SDU,另一部分为MAC CE。
一种实施方式中,如图4A所示,上述回退RAR格式至少可包括以下域:
-T2域(比如1bit):用于指示当前MAC RAR消息的格式是回退RAR格式,或者成功RAR格式;比如,若T2域的取值为0或1,0表示回退RAR格式,1表示成功RAR格式,则图4A所示的T2域取值为0;
-TAC域(比如12bits):用于发送终端的上行提前量;
-上行授权UL Grant域(比如27bits):用于为终端分配传输随机接入消息所使用的上行授权;
-T-C-RNTI(即Temporary C-RNTI)域(比如16bits):用于为回退终端(fallback UE)分配临时的C-RNTI。
另一种实施方式中,如图4B所示,上述成功RAR格式至少可以包括以下域:
-T2域(比如1bit):用于指示当前MAC RAR消息的格式是回退RAR格式,或者成功RAR格式;比如,若T2域的取值为0或1,0表示回退RAR格式,1表示成功RAR格式,则图4B所示的T2域取值为1;
-R域(比如1bit):预留比特位;例如,R域的取值可为0;
-TAC域(比如12bits):用于发送终端的上行提前量;
-C-RNTI域(比如16bits):用于为成功终端(success UE)分配C-RNTI;
-竞争解决标识(UE Contention Resolution ID)域(比如48bits):用于发送终端MsgA中CCCH信息的内容;若CCCH信息的大小超过48bits,则可以取CCCH信息的前48bits信息填入;
-P域(比如可选为1、2或3bits):用于指示对应RAR消息包括终端专用数据的情况。
需说明的是,P域的大小可以基于实际情况选择,可以指示不同的情况。至于P域选为多少比特,可以协议规定也可以系统消息中配置。
比如,当P域为1bit时,P域的取值可为0或1,0表示对应成功RAR消息中不包括任何终端专用数据,该终端专用数据比如可为终端专用的信令无线承载(Signaling Radio Bearer,SRB)subPDU和数据无线承载(Data Radio Bearer,DRB)subPDU;1表示对应成功RAR消息中包括一个终端专用的SRB subPDU或DRB subPDU。
又比如,当P域为2bits时,P域的取值可为00、01、10或11,00表示对应成功RAR消息中不包括终端专用的SRB subPDU和DRB subPDU,01表示对应成功RAR消息中包括一个终端专用的SRB subPDU或DRB subPDU,10表示对应成功RAR消息中包括两个终端专用的数据(该数据比如为SRB subPDU或DRB subPDU),11表示对应成功RAR消息中包括三个终端专用的数据(该数据比如为SRB subPDU或DRB subPDU)。
又比如,当P域为3bits时,P域的取值可为000、001、010、011、100、101、110或111,000表示对应成功RAR消息中不包括终端专用的数据,001表示对应成功RAR消息中包括一个终端专用的数据,010表示对应成功RAR消息中包括两个终端专用的数据,011表示对应成功RAR消息中包括三个终端专用的数据,100表示对应成功RAR消息中包括四个终端专用的数据,101表示对应成功RAR消息中包括五个终端专用的数据,110表示对应成功RAR消息中包括六个终端专用的数据,111表示对应成功RAR消息中包括七个终端专用的数据;此处终端专用的数据可为SRB subPDU或DRB subPDU。
又一种实施方式中,网络设备可以将给多个终端的响应消息复用到一起进行发送,如图4C所示,比如可以将UE1的MAC RAR subheader(包括BI信息)、UE2的MAC RAR subheader(包括RAPID)、UE3的回退RAR消息、UE4的成功RAR消息等等复用到一起进行发送。
需说明的是,对于上述的SRB subPDU或DRB subPDU,可以采用MAC数据subPDU的格式。终端可以根据逻辑信道标识(Logical Channel Identify,LCID)域和L域,获知对应subPDU是属于哪个逻辑信道的数据以及数据的长度,并且当LCID域取值特殊时,还可以代表对应subPDU是一个MAC CE  subPDU。也就是说,终端在读取LCID域和L域之后,可以确定对应subPDU的大小,若为自身数据即可进行解析,若不是自身数据则可以跳过,并继续解码剩余的subPDU,以获取自身数据。
形式二
形式二下,上述指示信息可包括第四指示域,所述第四指示域指示以下任意一项:
所述RAR消息包括BI信息;
所述RAR消息的格式是回退RAR格式;
所述RAR消息的格式是成功RAR格式;
所述RAR消息包括终端专用数据的情况;
所述RAR消息包括的终端专用数据的个数。
一种实施方式中,该第四指示域可选为MAC RAR subheader中包括的T域,该T域可选为2或3bits。
比如,参见图5A所示,图5A为包括BI信息的MAC RAR subheader格式的示意图,该MAC RAR subheader中可至少包括以下域:
-E域(比如1bit):用于指示当前MAC subPDU是否是最后一个;比如,E域的取值可为0或1,0表示后续还有其它的MAC subPDU,1表示当前MAC subPDU是最后一个,剩余内容为填充比特;
-T域(可选为2或3bits):类型指示信息,用于指示对应RAR消息是否包括BI信息,以及对应RAR消息的格式等;
-R域(比如1bit):预留比特位;例如,R域的取值可为0;
-BI域(比如4bits):用于指示网络过载情况下的后退行为。
又比如,参见图5B所示,图5B为除包括BI信息之外的其他MAC RAR subheader格式的示意图,该MAC RAR subheader中可至少包括以下域:
-E域(比如1bit):用于指示当前MAC subPDU是否是最后一个;比如,E域的取值可为0或1,0表示后续还有其它的MAC subPDU,1表示当前MAC subPDU是最后一个,剩余内容为填充比特;
-T域(可选为2或3bits):类型指示信息,用于指示对应RAR消息是否包括BI信息,以及对应RAR消息的格式等;
-R域(比如1bit):预留比特位;例如,R域的取值可为0。
下面,分别以T域为2bits或3bits为例,结合表1和表2对本实施例中的T域进行举例说明。
1)以T域为2bits为例,参见如下的表1所示,T域的取值可为00、01、10或11,00表示对应RAR消息包括BI信息,01表示对应RAR消息的格式是回退RAR格式,10表示对应RAR消息的格式是成功RAR格式,11表示对应RAR消息包括一个终端专用数据,该终端专用数据比如为MAC SDU或MAC CE。
表1
T域 说明
00 包括BI信息
01 是回退RAR格式
10 是成功RAR格式
11 包括一个终端专用数据
2)以T域为3bits为例,参见如下的表2所示,T域的取值可为000、001、010、011、100、101、110或111,000表示对应RAR消息包括BI信息,001表示对应RAR消息的格式是回退RAR格式,010表示对应RAR消息的格式是成功RAR格式,011表示对应RAR消息包括一个终端专用数据,100表示对应RAR消息包括两个终端专用数据,101表示对应RAR消息包括三个终端专用数据或者预留,110表示对应RAR消息包括四个终端专用数据或者预留,111表示对应RAR消息包括五个终端专用数据或者预留。
表2
T域 说明
000 包括BI信息
001 是回退RAR格式
010 是成功RAR格式
011 包括一个终端专用数据
100 包括两个终端专用数据
101 包括三个终端专用数据或者预留
110 包括四个终端专用数据或者预留
111 包括五个终端专用数据或者预留
需说明的是,在上述的第四指示域(比如MAC RAR subheader中的T域)的基础上,对应RAR消息的格式可为回退RAR(fallback RAR)格式,或者成功RAR(success RAR)格式。可选地,该回退RAR格式所包括的域可与上述图4A中的类似,该成功RAR格式所包括的域可与上述图4B中的类似,但至少具有以下不同:
1)在第四指示域指示RAR消息的格式是回退RAR格式的情况下,所述RAR消息中包括RAPID,以进行身份验证;
2)在第四指示域指示RAR消息的格式是成功RAR格式的情况下,所述RAR消息中可不包括RAPID;此不包括RAPID的原因为:终端可以通过竞争解决标识(UE Contention Resolution ID)域进行身份验证,而无需RAPID进行身份验证,因此可以不包括RAPID。
对于回退RAR消息和成功RAR消息的不同格式类型,因为已经通过MAC RAR subheader中的T域进行了区分,并且包括的终端专用数据的个数也可在该T域进行指示,因此后续的RAR格式可不再进行区分和指示。
比如,参见图6A和图6B所示,对应回退RAR格式至少可包括以下域:
-T2域(比如1bit):用于指示当前MAC RAR消息的格式是回退RAR格式,或者成功RAR格式;比如,若T2域的取值为0或1,0表示回退RAR格式,1表示成功RAR格式,则图6A和图6B所示的T2域取值为0;值的注意的是,该T2域可选为被R域替换,不再对RAR消息的格式进行指示;
-R域(比如1bit):预留比特位;例如,R域的取值可为0;
-RAPID域(比如6bits),用于与随机接入消息(比如MsgA)所使用的preamble码对应。
-TAC域(比如12bits):用于发送终端的上行提前量;
-UL Grant域(比如27bits):用于为终端分配传输随机接入消息所使用的上行授权;
-T-C-RNTI域(比如16bits):用于为回退终端(fallback UE)分配临时的C-RNTI。
又比如,参见图6C所示,对应成功RAR格式至少可包括以下域:
-R域(比如1bit):预留比特位;例如,R域的取值可为0;
-TAC域(比如12bits):用于发送终端的上行提前量;
-C-RNTI域(比如16bits):用于为成功终端(success UE)分配C-RNTI;
竞争解决标识(UE Contention Resolution ID)域(比如48bits):用于发送终端MsgA中CCCH信息的内容;若CCCH信息的大小超过48bits,则可以取CCCH信息的前48bits信息填入。
一种实施方式中,网络设备可以将给多个终端的响应消息复用到一起进行发送,如图6D所示,比如可以将UE1的MAC RAR subheader(包括BI信息)、UE2的回退RAR消息、UE3的成功RAR消息等等复用到一起进行发送。
从上述图6C所示的成功RAR格式可知,所述成功RAR格式没有单独包括RAPID域,理由如下:一方面,在2-step RACH过程中,由于PUSCH可以携带CCCH信息,同时CCCH信息中可以包括SI请求消息,不需要以专门的Preamble码来表示SI请求消息,因此可以不包括RAPID域,而直接可以用成功RAR格式中的竞争解决标识对应于终端发送的CCCH信息来响应终端对于SI的请求成功,可达到一样的效果;另一方面,若需要单独的RAPID格式,则可以在T域中给该RAPID格式一个专门的取值;或者,首先将单独的RAPID格式划分为回退RAR格式一类,与回退RAR格式共用同一个T域指示,然后在回退RAR格式中将第一个R域替代为T2域,指示是单独的RAPID格式或者正常的fallback RAR格式,如图6A和图6B所示,单独的RAPID格式仅需一个字节,后六bit为RAPID域,第一个bit为类型指示信息,第二个bit为R预留比特。
需说明的是,上述实施例中是区分MAC RAR subheader和MAC RAR分别各自整字节排列的,从而导致各自都出现了多个R bit。而若将MAC RAR subheader和MAC RAR合并一起,虽可能会打破MAC RAR subheader和MAC RAR各自独立的设计,但可以降低整体的长度和Rbit的大小,降低开销。
一种实施方式中,以成功RAR消息为例,将MAC RAR subheader和MAC RAR合并后的格式可以参见图7所示。如图7所示,对应合并后的格式可以 理解为上述图5B所示的MAC RAR subheader和上述图6C所示的成功RAR格式合并在一起。此情况下,终端行为不会发生变化,仅是改变了RAR格式,包括的响应内容也是类似的。最大不同是在成功RAR消息中不再包括RAPID,主要由于RAPID仅能用于初步确定响应对应的上行终端所使用的preamble,但实际两个终端可能会使用相同的preamble,因此最终的确定终端身份仍旧需要比对竞争解决标识,因此在成功RAR消息中不携带RAPID并不影响最终确认终端。
本公开至少一个实施例中,上述步骤203可包括以下至少一项:
在所述指示信息指示所述RAR消息包括BI信息的情况下,根据所述BI信息,执行回退操作;
在所述指示信息指示所述RAR消息的格式是回退RAR格式的情况下,执行回退操作;
在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,当所述RAR消息中包括竞争解决标识,且所述竞争解决标识验证成功时,确定随机接入过程成功;
在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,当所述RAR消息中包括RAPID和竞争解决标识,且所述RAPID和竞争解决标识验证成功时,确定随机接入过程成功;
在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,当所述RAR消息中包括竞争解决标识,且所述竞争解决标识验证成功时,若所述RAR消息中包括终端专用数据,根据所述指示信息指示的终端专用数据的情况,进行相关数据的接收处理;
在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,当所述RAR消息中包括RAPID和竞争解决标识,且所述RAPID和竞争解决标识验证成功时,若所述RAR消息中包括终端专用数据,根据所述指示信息指示的终端专用数据的情况,进行相关数据的接收处理。
这样,借助RAR消息中包括的指示信息,可使得终端区分网络设备不同的响应情况并进行相应处理,从而降低随机接入过程中的时延和处理复杂度。
下面以2步随机接入过程为例,对终端行为进行详细说明。
1)如果终端发送了特殊的Preamble码用于SI请求,则终端可在Msg B窗口中,利用该Preamble码和/或相关的RNTI解析PDCCH;若检测到自身的Preamble码对应的RAPID包含在响应消息中,则确定网络设备已经正确接收到SI请求,后续等待接收SI即可,SI请求的随机接入过程成功。
2)如果终端发送的Msg A中包括CCCH信息,该CCCH信息用于RRC连接建立请求、RRC连接恢复请求或者类似传统Msg3的SI请求消息等,则终端可在MsgB窗口中,利用Preamble码和/或相关的RNTI解析PDCCH;若检测到自身的Preamble码对应的RAPID包含在响应消息中,则:
-如果该RAPID对应的RAR格式为回退RAR格式,则终端可按照回退RAR格式中指示的UL grant,回退到4-step RACH过程发起Msg3传输;
-如果该RAPID对应的RAR格式为成功RAR格式,则终端可按照成功RAR格式来解析RAR消息,并将竞争解决标识域所带的bit流与自身先前发送的CCCH信息进行比对;若比对成功,则确定竞争解决成功,随机接入过程成功,而若比对失败,则确定此不是给自己的响应消息,继续监听。需指出的是,如果竞争解决成功,并发现成功RAR消息中还包括额外的下行共享信道(Downlink Share Channel,DL-SCH)的数据,则终端可按照RAR中指示的终端专用数据的个数进行DL-SCH数据的逐个解析,并将其递交至高层进行处理。
-如果该RAPID与自身Preamble不对应或者竞争解决失败,则终端可按照每个RAR格式的指示和头指示,依次跳过不属于自己的RAR格式和可能的DL-SCH的格式,尝试进行后续RAPID比对和RAR的解析,直到找到自己的响应为止。
3)如果终端在Msg B窗口中没有接收到任何跟自己的RAPID对应的RAR消息,或者竞争解决都失败了,则终端可以确定此次随机接入过程失败,并根据在Msg B窗口中接收到的BI信息,进行一定的随机延迟,之后发起下一次随机接入失败,直至达到预设最大随机接入尝试次数仍旧不成功,向高层上报随机接入失败。
请参见图8,图8是本公开实施例提供的一种随机接入的响应方法的流程图,该方法应用于网络设备,如图8所示,该方法包括如下步骤:
步骤801:从终端接收随机接入消息。
步骤802:向所述终端发送RAR消息。
可选地,所述RAR消息中包括指示信息,所述指示信息指示所述RAR消息的格式类型。
本公开实施例的随机接入的响应方法,借助RAR消息中包括的指示信息,至少可以明确随机接入过程(比如2步随机接入过程)中的RAR消息包括哪些内容,从而使得终端可以区分网络设备不同的响应情况,从而降低随机接入过程中的时延和处理复杂度。
本公开实施例中,可选地,所述指示信息包括第一指示域,所述第一指示域指示所述RAR消息包括BI信息,或者RAR信息。
可选地,所述RAR信息包括:RAPID。
可选地,在所述第一指示域指示所述RAR消息包括RAR信息的情况下,所述指示信息还包括第二指示域,所述第二指示域指示所述RAR消息的格式是回退RAR格式,或者是成功RAR格式。
可选地,在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,所述指示信息还包括第三指示域,所述第三指示域指示所述RAR消息包括终端专用数据的情况。
可选地,当所述第三指示域为1比特时,所述第三指示域指示所述RAR消息是否包括终端专用数据;
或者,当所述第三指示域为至少1比特时,所述第三指示域指示所述RAR消息是否包括终端专用数据,以及在所述RAR消息包括终端专用数据的情况下,所述RAR消息包括的终端专用数据的个数。
本公开实施例中,可选地,所述指示信息包括第四指示域,所述第四指示域指示以下任意一项:
所述RAR消息包括BI信息;
所述RAR消息的格式是回退RAR格式;
所述RAR消息的格式是成功RAR格式;
所述RAR消息包括终端专用数据的情况;
所述RAR消息包括的终端专用数据的个数。
可选地,在所述指示信息指示所述RAR消息的格式是回退RAR格式的情况下,所述RAR消息中包括RAPID;
或者,在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,所述RAR消息中不包括RAPID。
可选地,所述终端专用数据为:MAC SDU和MAC CE中的至少一者。
请参见图9,图9是本公开实施例提供的一种随机接入方法的流程图,该方法应用于终端,如图9所示,该方法包括如下步骤:
步骤901:向网络设备发送随机接入消息。
可选地,该随机接入消息可称为随机接入请求消息、Msg1或者MsgA。该随机接入消息中可包括C-RNTI。
步骤902:从网络设备接收RAR消息。
可选地,所述RAR消息中包括与终端需求对应的控制信息。
步骤903:根据所述控制信息,确定随机接入过程成功。
本公开实施例的随机接入方法,通过根据RAR消息中包括的控制信息,至少可以明确随机接入过程(比如2步随机接入过程)中的RAR消息包括哪些内容,从而使得终端可以区分网络设备不同的响应情况,从而降低随机接入过程中的时延和处理复杂度。
本公开实施例中,可选地,上述控制信息可包括但不限于以下任意一项:
利用C-RNTI解析PDCCH的调度信令;
TAC MAC CE;
波束失败恢复情况下的在新波束资源上的调度信令;
预设长度的TAC;
预设长度的TAC和上行调度授权。
一种实施方式中,当终端处于RRC连接状态时,由于上行数据到达或者波束失败恢复(Beam failure recovery)等触发,终端也可发起随机接入过程。连接态终端的Msg A中通常会包括自身C-RNTI,以告知网络设备该终端的身份;此外该Msg A中可能还包括缓存状态报告(Buffer Status Report,BSR)或者波束失败的一些信息,以使得网络设备在接收到这些信息之后,根据终端需求进行响应。
以2步随机接入为例,对于包括C-RNTI的MsgA,一种可能的响应是,网络设备向终端下发利用C-RNTI解析PDCCH(PDCCH addressed by C-RNTI)的上行调度信令。若终端接收到自身专用的上行调度信令,则终端可确定网络设备正确接收到MsgA,进一步可确定2步随机接入过程成功,后续根据网络调度进行相应传输即可。
对于波束失败恢复的情况,网络设备在接收到终端的MsgA之后,可以在波束失败恢复后对应的新波束资源上,向终端发送利用C-RNTI解析PDCCH的调度信令,此调度信令可以是上行的也可以是下行的。由于是在新波束资源上发送的响应消息,因此终端接收到后,可以确定MsgA接收成功,进一步确定随机接入过程成功。
另外,由于MsgA中包括Preamble码,网络设备在接收到Preamble码后,可能会对终端的上行同步TA进行更新计算,也可能给终端发送一个传统的TAC MAC CE,用于终端对TA进行调整。因此,终端在发送了包括C-RNTI的MsgA之后,若在MsgB窗口中接收到网络设备发送给自己的专用TAC MAC CE,可以确定对应的随机接入过程成功。
另一种实施方式中,对于连接态终端,当终端当前处于上行失步状态时,网络设备需向终端发送TA信息,该TA信息与传统MAC CE中包括的TAC是有差别的。传统TAC用于对当前已有的TA进行调整,是个偏移量,而在未建立上行同步之前,需要的是TA的初始值。传统MAC CE形式的TAC为6bits,而建立初始同步的TAC为预设长度比如12bits,例如MAC RAR消息中包括的TAC为12bits。
此时网络设备为了响应终端的MsgA,可向终端发送一个预设长度的TAC信令比如12bits长度专门的TAC信令,用于UE建立初始的上行同步。对应地,终端根据该12bits长度专门的TAC信令,可确认随机接入过程成功。
可选地,上述预设长度的TAC可以是通过LCID指示的。
一种实施方式中,以12bits的TAC为例,如图10A所示,可在MAC subheader中分配一个专门的LCID指示域,以指示12bits的TAC。而对应的MAC CE格式可如图10B所示,该MAC CE格式中包括12bits的TAC。
进一步地,该包括12bits的TAC的MAC CE格式中,还可包括T域(比 如1bit)和UL Grant域(比如27bits),如图10C所示,该T域指示包括单独的TAC域,或者包括TAC域和UL Grant域。
需说明的是,上述UL Grant的格式除可采用上述形式外,还可采用其他形式,比如下行控制信息(Downlink Control Information,DCI)授权MAC CE的形式,至少包含时频资源位置、HARQ进程标识、冗余版本(Redundancy Version,RV)、增补上行链路(Supplement Uplink,SUL)指示等信息。
此外,本实施例中还可利用两个特殊的LCID指示是12bit TAC,还是12bit TAC和UL Grant,或者以MAC subheader中包括L域,基于L域的长度不同,指示是单独的12bit TAC,还是12bit TAC和UL Grant。
可选地,上述预设长度的TAC可以是通过MAC头中的第一个指示域指示的。
一种实施方式中,该第一个指示域可为MAC subheader中的第一个R域,并以区分于第一个R域的其它取值来指示。
在DL-SCH上传输的数据,常以MAC subheader起头,而所有MAC subheader的第一个比特为R域,取值为0。因此,为了尽快区分12bits的TAC,如图11所示,可以将MAC subheader中的第一个R域设为1。而对应的MAC subPDU格式可如图11B所示,该MAC subPDU格式中包括12bits的TAC。
进一步地,该包括12bits的TAC的MAC subPDU格式中,还可包括T域(比如1bit)和UL Grant域(比如27bits),如图11C所示,该T域指示包括单独的TAC域,或者包括TAC域和UL Grant域。
可理解地,无论采用上述的哪种MAC CE格式或者MAC subPDU格式,终端都可获知此是一个特殊的12bits的TAC(或包括UL Grant)。对于发送了MsgA的终端,若接收到利用C-RNTI解析PDCCH的调度信令中包括的12bits的TAC,则可以确定随机接入过程成功。
本实施例中,终端除了监听自身C-RNTI之外,还可以同时监听用于解析PDCCH的RA-RNTI;若接收到自身的回退RAR消息,则终端可以执行回退操作。若终端在MsgB窗口中,对回退RAR消息和成功RAR消息都没有接收到,则可以确定随机接入过程失败,并根据BI指示后退延时后再次进行 随机接入过程。
上述实施例对本公开的随机接入方法及其响应方法进行了说明,下面将结合实施例和附图对本公开的终端和网络设备进行说明。
请参见图12,图12是本公开实施例提供的一种终端的结构示意图,如图12所示,该终端120包括:
第一发送模块121,用于向网络设备发送随机接入消息;
第一接收模块122,用于从所述网络设备接收RAR消息,所述RAR消息中包括指示信息,所述指示信息指示所述RAR消息的格式类型;
执行模块123,用于根据所述指示信息,执行相应的随机接入操作。
本公开实施例的终端,通过根据RAR消息中包括的指示信息,执行相应的随机接入操作,该指示信息指示RAR消息的格式类型,至少可以明确随机接入过程(比如2步随机接入过程)中的RAR消息包括哪些内容,从而可以区分网络设备不同的响应情况,降低随机接入过程中的时延和处理复杂度。
本公开实施例,可选地,所述指示信息包括第一指示域,所述第一指示域指示所述RAR消息包括回退指示BI信息,或者RAR信息。
可选地,所述RAR信息包括RAPID。
可选地,在所述第一指示域指示所述RAR消息包括RAR信息的情况下,所述指示信息还包括第二指示域,所述第二指示域指示所述RAR消息的格式是回退RAR格式,或者成功RAR格式。
可选地,在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,所述指示信息还包括第三指示域,所述第三指示域指示所述RAR消息包括终端专用数据的情况。
可选地,当所述第三指示域为1比特时,所述第三指示域指示所述RAR消息是否包括终端专用数据;或者,当所述第三指示域为至少1比特时,所述第三指示域指示所述RAR消息是否包括终端专用数据,以及在所述RAR消息包括终端专用数据的情况下,所述RAR消息包括的终端专用数据的个数。
可选地,所述指示信息可以包括第四指示域,所述第四指示域指示以下任意一项:
所述RAR消息包括BI信息;
所述RAR消息的格式是回退RAR格式;
所述RAR消息的格式是成功RAR格式;
所述RAR消息包括终端专用数据的情况;
所述RAR消息包括的终端专用数据的个数。
可选地,在所述指示信息指示所述RAR消息的格式是回退RAR格式的情况下,所述RAR消息中包括RAPID;
或者,在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,所述RAR消息中不包括RAPID。
可选地,所述终端专用数据为:MAC SDU和MAC CE中的至少一者。
可选地,所述执行模块123用于执行以下任意一项:
在所述指示信息指示所述RAR消息包括BI信息的情况下,根据所述BI信息,执行回退操作;
在所述指示信息指示所述RAR消息的格式是回退RAR格式的情况下,执行回退操作;
在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,当所述RAR消息中包括竞争解决标识,且所述竞争解决标识验证成功时,确定随机接入过程成功;
在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,当所述RAR消息中包括RAPID和竞争解决标识,且所述RAPID和竞争解决标识验证成功时,确定随机接入过程成功;
在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,当所述RAR消息中包括竞争解决标识,且所述竞争解决标识验证成功时,若所述RAR消息中包括终端专用数据,根据所述指示信息指示的终端专用数据的情况,进行相关数据的接收处理;
在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,当所述RAR消息中包括RAPID和竞争解决标识,且所述RAPID和竞争解决标识验证成功时,若所述RAR消息中包括终端专用数据,根据所述指示信息指示的终端专用数据的情况,进行相关数据的接收处理。
请参见图13,图13是本公开实施例提供的一种网络设备的结构示意图,如图13所示,该网络设备130包括:
第二接收模块131,用于从终端接收随机接入消息;
第二发送模块132,用于向所述终端发送RAR消息;
其中,所述RAR消息中包括指示信息,所述指示信息指示所述RAR消息的格式类型。
本公开实施例的网络设备,借助RAR消息中包括的指示信息,至少可以明确随机接入过程(比如2步随机接入过程)中的RAR消息包括哪些内容,从而使得终端可以区分网络设备不同的响应情况,从而降低随机接入过程中的时延和处理复杂度。
可选地,所述指示信息包括第一指示域,所述第一指示域指示所述RAR消息包括BI信息,或者RAR信息。
可选地,所述RAR信息包括:RAPID。
可选地,在所述第一指示域指示所述RAR消息包括RAR信息的情况下,所述指示信息还包括第二指示域,所述第二指示域指示所述RAR消息的格式是回退RAR格式,或者是成功RAR格式。
可选地,在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,所述指示信息还包括第三指示域,所述第三指示域指示所述RAR消息包括终端专用数据的情况。
可选地,当所述第三指示域为1比特时,所述第三指示域指示所述RAR消息是否包括终端专用数据;或者,当所述第三指示域为至少1比特时,所述第三指示域指示所述RAR消息是否包括终端专用数据,以及在所述RAR消息包括终端专用数据的情况下,所述RAR消息包括的终端专用数据的个数。
可选地,所述指示信息可以包括第四指示域,所述第四指示域指示以下任意一项:
所述RAR消息包括BI信息;
所述RAR消息的格式是回退RAR格式;
所述RAR消息的格式是成功RAR格式;
所述RAR消息包括终端专用数据的情况;
所述RAR消息包括的终端专用数据的个数。
可选地,在所述指示信息指示所述RAR消息的格式是回退RAR格式的情况下,所述RAR消息中包括RAPID;
或者,在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,所述RAR消息中不包括RAPID。
可选地,所述终端专用数据为:MAC SDU和MAC CE中的至少一者。
请参见图14,图14是本公开实施例提供的一种终端的结构示意图,如图14所示,该终端140包括:
第三发送模块141,用于向网络设备发送随机接入消息;
第三接收模块142,用于从所述网络设备接收RAR消息,所述RAR消息中包括与终端需求对应的控制信息;
确定模块143,用于根据所述控制信息,确定随机接入过程成功。
本公开实施例的终端,通过根据RAR消息中包括的控制信息,至少可以明确随机接入过程(比如2步随机接入过程)中的RAR消息包括哪些内容,从而可以区分网络设备不同的响应情况,从而降低随机接入过程中的时延和处理复杂度。
可选地,所述控制信息可包括以下任意一项:
利用C-RNTI解析PDCCH的调度信令;
TAC MAC CE;
波束失败恢复情况下的在新波束资源上的调度信令;
预设长度的TAC;
预设长度的TAC和上行调度授权。
可选地,在所述控制信息包括预设长度的TAC情况下,所述预设长度的TAC是通过逻辑信道标识LCID指示的;
或者,所述预设长度的TAC是通过MAC头中的第一个指示域指示的。
本公开实施例还提供了一种通信设备,包括处理器,存储器,存储在所述存储器上并可在所述处理器上运行的计算机程序,其中,所述计算机程序被所述处理器执行时实现上述图2所示的随机接入方法实施例的各个过程, 或者实现上述图8所示的随机接入的响应方法实施例的各个过程,或者实现上述图9所示的随机接入方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。该通信设备可选为终端或者网络设备。
具体地,图15为实现本公开各个实施例的一种终端的硬件结构示意图,终端1500包括但不限于:射频单元1501、网络模块1502、音频输出单元1503、输入单元1504、传感器1505、显示单元1506、用户输入单元1507、接口单元1508、存储器1509、处理器1510、以及电源1511等部件。本领域技术人员可以理解,图15中示出的终端结构并不构成对终端的限定,终端可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置。在本公开实施例中,终端包括但不限于手机、平板电脑、笔记本电脑、掌上电脑、车载终端、可穿戴设备、以及计步器等。
可选地,射频单元1501,用于向网络设备发送随机接入消息,从所述网络设备接收RAR消息,所述RAR消息中包括指示信息,所述指示信息指示所述RAR消息的格式类型;处理器1510,用于根据所述指示信息,执行相应的随机接入操作。
或者,射频单元1501,用于向网络设备发送随机接入消息;从所述网络设备接收RAR消息,所述RAR消息中包括与终端需求对应的控制信息;处理器1510,用于根据所述控制信息,确定随机接入过程成功。
本公开实施例中,至少可以明确随机接入过程(比如2步随机接入过程)中的RAR消息包括哪些内容,从而使得终端1500可以区分网络设备不同的响应情况,从而降低随机接入过程中的时延和处理复杂度。
需说明的是,本公开实施例的终端1500,可以实现上述图2所示方法实施例中实现的各个过程,或者实现上述图8所示方法实施例中实现的各个过程,以及达到相同的有益效果,为避免重复,这里不再赘述。
应理解的是,本公开实施例中,射频单元1501可用于收发信息或通话过程中,信号的接收和发送,具体地,将来自基站的下行数据接收后,给处理器1510处理;另外,将上行的数据发送给基站。通常,射频单元1501包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。此外,射频单元1501还可以通过无线通信系统与网络和其他设备通信。
终端通过网络模块1502为用户提供了无线的宽带互联网访问,如帮助用户收发电子邮件、浏览网页和访问流式媒体等。
音频输出单元1503可以将射频单元1501或网络模块1502接收的或者在存储器1509中存储的音频数据转换成音频信号并且输出为声音。而且,音频输出单元1503还可以提供与终端1500执行的特定功能相关的音频输出(例如,呼叫信号接收声音、消息接收声音等等)。音频输出单元1503包括扬声器、蜂鸣器以及受话器等。
输入单元1504用于接收音频或视频信号。输入单元1504可以包括图形处理器(Graphics Processing Unit,GPU)15041和麦克风15042,图形处理器15041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。处理后的图像帧可以显示在显示单元1506上。经图形处理器15041处理后的图像帧可以存储在存储器1509(或其它存储介质)中或者经由射频单元1501或网络模块1502进行发送。麦克风15042可以接收声音,并且能够将这样的声音处理为音频数据。处理后的音频数据可以在电话通话模式的情况下转换为可经由射频单元1501发送到移动通信基站的格式输出。
终端1500还包括至少一种传感器1505,比如光传感器、运动传感器以及其他传感器。具体地,光传感器包括环境光传感器及接近传感器,其中,环境光传感器可根据环境光线的明暗来调节显示面板15061的亮度,接近传感器可在终端1500移动到耳边时,关闭显示面板15061和/或背光。作为运动传感器的一种,加速计传感器可检测各个方向上(一般为三轴)加速度的大小,静止时可检测出重力的大小及方向,可用于识别终端姿态(比如横竖屏切换、相关游戏、磁力计姿态校准)、振动识别相关功能(比如计步器、敲击)等;传感器1505还可以包括指纹传感器、压力传感器、虹膜传感器、分子传感器、陀螺仪、气压计、湿度计、温度计、红外线传感器等,在此不再赘述。
显示单元1506用于显示由用户输入的信息或提供给用户的信息。显示单元1506可包括显示面板15061,可以采用液晶显示器(Liquid Crystal Display,LCD)、有机发光二极管(Organic Light-Emitting Diode,OLED)等形式来配置显示面板15061。
用户输入单元1507可用于接收输入的数字或字符信息,以及产生与终端的用户设置以及功能控制有关的键信号输入。具体地,用户输入单元1507包括触控面板15071以及其他输入设备15072。触控面板15071,也称为触摸屏,可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触控面板15071上或在触控面板15071附近的操作)。触控面板15071可包括触摸检测装置和触摸控制器两个部分。其中,触摸检测装置检测用户的触摸方位,并检测触摸操作带来的信号,将信号传送给触摸控制器;触摸控制器从触摸检测装置上接收触摸信息,并将它转换成触点坐标,再送给处理器1510,接收处理器1510发来的命令并加以执行。此外,可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触控面板15071。除了触控面板15071,用户输入单元1507还可以包括其他输入设备15072。具体地,其他输入设备15072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆,在此不再赘述。
进一步地,触控面板15071可覆盖在显示面板15061上,当触控面板15071检测到在其上或附近的触摸操作后,传送给处理器1510以确定触摸事件的类型,随后处理器1510根据触摸事件的类型在显示面板15061上提供相应的视觉输出。虽然在图15中,触控面板15071与显示面板15061是作为两个独立的部件来实现终端的输入和输出功能,但在某些实施例中,可将触控面板15071与显示面板15061集成而实现终端的输入和输出功能,此处不做限定。
接口单元1508为外部装置与终端1500连接的接口。例如,外部装置可以包括有线或无线头戴式耳机端口、外部电源(或电池充电器)端口、有线或无线数据端口、存储卡端口、用于连接具有识别模块的装置的端口、音频输入/输出(I/O)端口、视频I/O端口、耳机端口等等。接口单元1508可用于接收来自外部装置的输入(例如,数据信息、电力等等)并且将接收到的输入传输到终端1500内的一个或多个元件或者可以用于在终端1500和外部装置之间传输数据。
存储器1509可用于存储软件程序以及各种数据。存储器1509可主要包括存储程序区和存储数据区,其中,存储程序区可存储操作系统、至少一个 功能所需的应用程序(比如声音播放功能、图像播放功能等)等;存储数据区可存储根据手机的使用所创建的数据(比如音频数据、电话本等)等。此外,存储器1509可以包括高速随机存取存储器,还可以包括非易失性存储器,例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。
处理器1510是终端的控制中心,利用各种接口和线路连接整个终端的各个部分,通过运行或执行存储在存储器1509内的软件程序和/或模块,以及调用存储在存储器1509内的数据,执行终端的各种功能和处理数据,从而对终端进行整体监控。处理器1510可包括一个或多个处理单元;可选地,处理器1510可集成应用处理器和调制解调处理器,其中,应用处理器主要处理操作系统、用户界面和应用程序等,调制解调处理器主要处理无线通信。可以理解的是,上述调制解调处理器也可以不集成到处理器1510中。
终端1500还可以包括给各个部件供电的电源1511(比如电池),可选地,电源1511可以通过电源管理系统与处理器1510逻辑相连,从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。
另外,终端1500还可包括一些未示出的功能模块,在此不再赘述。
具体地,图16为实现本公开各个实施例的一种网络设备的硬件结构示意图,所述网络设备160包括但不限于:总线161、收发机162、天线163、总线接口164、处理器165和存储器166。
在本公开实施例中,所述网络设备160还包括:存储在存储器166上并可在处理器165上运行的计算机程序。可选地,该计算机程序被处理器165执行时实现以下步骤:
从终端接收随机接入消息;
向所述终端发送RAR消息;所述RAR消息中包括指示信息,所述指示信息指示所述RAR消息的格式类型。
本公开实施例的网络设备160,可以实现上述图9所示方法实施例中实现的各个过程,以及达到相同的有益效果,为避免重复,这里不再赘述。
收发机162,用于在处理器165的控制下接收和发送数据。
在图16中,总线架构(用总线161来代表),总线161可以包括任意数量的互联的总线和桥,总线161将包括由处理器165代表的一个或多个处理 器和存储器166代表的存储器的各种电路链接在一起。总线161还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起,这些都是本领域所公知的,因此,本文不再对其进行进一步描述。总线接口164在总线161和收发机162之间提供接口。收发机162可以是一个元件,也可以是多个元件,比如多个接收器和发送器,提供用于在传输介质上与各种其他装置通信的单元。经处理器165处理的数据通过天线163在无线介质上进行传输,进一步,天线163还接收数据并将数据传送给处理器165。
处理器165负责管理总线161和通常的处理,还可以提供各种功能,包括定时,外围接口,电压调节、电源管理以及其他控制功能。而存储器166可以被用于存储处理器165在执行操作时所使用的数据。
可选地,处理器165可以是CPU、ASIC、FPGA或CPLD。
本公开实施例还提供一种计算机可读存储介质,计算机可读存储介质上存储有计算机程序,该计算机程序被处理器执行时实现上述图2所示的随机接入方法实施例的各个过程,或者实现上述图8所示的随机接入的响应方法实施例的各个过程,或者实现上述图9所示的随机接入方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。其中,该计算机可读存储介质,例如为只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等。
需要说明的是,在本文中,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本公开的技术方案本质上或者说对相关技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光 盘)中,包括若干指令用以使得一台终端(可以是手机,计算机,服务器,空调器,或者网络设备等)执行本公开各个实施例所述的方法。
上面结合附图对本公开的实施例进行了描述,但是本公开并不局限于上述的具体实施方式,上述的具体实施方式仅仅是示意性的,而不是限制性的,本领域的普通技术人员在本公开的启示下,在不脱离本公开宗旨和权利要求所保护的范围情况下,还可做出很多形式,均属于本公开的保护之内。

Claims (23)

  1. 一种随机接入方法,应用于终端,包括:
    向网络设备发送随机接入消息;
    从所述网络设备接收随机接入响应RAR消息,所述RAR消息中包括指示信息,所述指示信息指示所述RAR消息的格式类型;
    根据所述指示信息,执行相应的随机接入操作。
  2. 根据权利要求1所述的方法,其中,
    所述指示信息包括第二指示域,所述第二指示域指示所述RAR消息的格式是回退RAR格式,或者成功RAR格式。
  3. 根据权利要求1所述的方法,其中,
    在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,所述指示信息还包括第三指示域,所述第三指示域指示所述RAR消息包括终端专用数据的情况。
  4. 根据权利要求3所述的方法,其中,
    当所述第三指示域为1比特时,所述第三指示域指示所述RAR消息是否包括终端专用数据;
    或者,
    当所述第三指示域为至少1比特时,所述第三指示域指示所述RAR消息是否包括终端专用数据,以及在所述RAR消息包括终端专用数据的情况下,所述RAR消息包括的终端专用数据的个数。
  5. 根据权利要求1所述的方法,其中,所述指示信息包括第四指示域,所述第四指示域指示以下任意一项:
    所述RAR消息包括BI信息;
    所述RAR消息的格式是成功RAR格式。
  6. 根据权利要求1所述的方法,其中,在所述指示信息指示所述RAR消息的格式是回退RAR格式的情况下,所述RAR消息中包括随机接入前导码标识RAPID;
    或者,
    在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,所述RAR消息中不包括RAPID。
  7. 根据权利要求3至6中任一项所述的方法,其中,
    所述终端专用数据为:媒体接入控制MAC服务数据单元SDU和MAC控制单元CE中的至少一者。
  8. 根据权利要求1所述的方法,其中,所述根据所述指示信息,执行相应的随机接入操作,包括以下至少一项:
    在所述指示信息指示所述RAR消息包括BI信息的情况下,根据所述BI信息,执行回退操作;
    在所述指示信息指示所述RAR消息的格式是回退RAR格式的情况下,执行回退操作;
    在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,当所述RAR消息中包括竞争解决标识,且所述竞争解决标识验证成功时,确定随机接入过程成功;
    在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,当所述RAR消息中包括RAPID和竞争解决标识,且所述RAPID和竞争解决标识验证成功时,确定随机接入过程成功;
    在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,当所述RAR消息中包括竞争解决标识,且所述竞争解决标识验证成功时,若所述RAR消息中包括终端专用数据,根据所述指示信息指示的终端专用数据的情况,进行相关数据的接收处理;
    在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,当所述RAR消息中包括RAPID和竞争解决标识,且所述RAPID和竞争解决标识验证成功时,若所述RAR消息中包括终端专用数据,根据所述指示信息指示的终端专用数据的情况,进行相关数据的接收处理。
  9. 一种随机接入的响应方法,应用于网络设备,包括:
    从终端接收随机接入消息;
    向所述终端发送RAR消息;
    其中,所述RAR消息中包括指示信息,所述指示信息指示所述RAR消 息的格式类型。
  10. 根据权利要求9所述的方法,其中,
    所述指示信息包括第二指示域,所述第二指示域指示所述RAR消息的格式是回退RAR格式,或者是成功RAR格式。
  11. 根据权利要求9所述的方法,其中,
    在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,所述指示信息还包括第三指示域,所述第三指示域指示所述RAR消息包括终端专用数据的情况。
  12. 根据权利要求11所述的方法,其中,
    当所述第三指示域为1比特时,所述第三指示域指示所述RAR消息是否包括终端专用数据;
    或者,
    当所述第三指示域为至少1比特时,所述第三指示域指示所述RAR消息是否包括终端专用数据,以及在所述RAR消息包括终端专用数据的情况下,所述RAR消息包括的终端专用数据的个数。
  13. 根据权利要求9所述的方法,其中,所述指示信息包括第四指示域,所述第四指示域指示以下任意一项:
    所述RAR消息包括BI信息;
    所述RAR消息的格式是成功RAR格式。
  14. 根据权利要求9所述的方法,其中,
    在所述指示信息指示所述RAR消息的格式是回退RAR格式的情况下,所述RAR消息中包括RAPID;
    或者,
    在所述指示信息指示所述RAR消息的格式是成功RAR格式的情况下,所述RAR消息中不包括RAPID。
  15. 根据权利要求11至14中任一项所述的方法,其中,
    所述终端专用数据为:MAC SDU和MAC CE中的至少一者。
  16. 一种随机接入的方法,应用于终端,包括:
    向网络设备发送随机接入消息;
    从所述网络设备接收RAR消息,所述RAR消息中包括与终端需求对应的控制信息;
    根据所述控制信息,确定随机接入过程成功。
  17. 根据权利要求16所述的方法,其中,所述控制信息包括以下任意一项:
    利用小区无线网络临时标识C-RNTI解析物理下行控制信道PDCCH的调度信令;
    定时提前信令TAC媒体介入控制控制单元MAC CE;
    波束失败恢复情况下的在新波束资源上的调度信令;
    预设长度的TAC;
    预设长度的TAC和上行调度授权。
  18. 根据权利要求17所述的方法,其中,在所述控制信息包括预设长度的TAC情况下,
    所述预设长度的TAC是通过逻辑信道标识LCID指示的;
    或者,
    所述预设长度的TAC是通过MAC头中的第一个指示域指示的。
  19. 一种终端,包括:
    第一发送模块,用于向网络设备发送随机接入消息;
    第一接收模块,用于从所述网络设备接收RAR消息,所述RAR消息中包括指示信息,所述指示信息指示所述RAR消息的格式类型;
    执行模块,用于根据所述指示信息,执行相应的随机接入操作。
  20. 一种网络设备,包括:
    第二接收模块,用于从终端接收随机接入消息;
    第二发送模块,用于向所述终端发送RAR消息;
    其中,所述RAR消息中包括指示信息,所述指示信息指示所述RAR消息的格式类型。
  21. 一种终端,包括:
    第三发送模块,用于向网络设备发送随机接入消息;
    第三接收模块,用于从所述网络设备接收RAR消息,所述RAR消息中 包括与终端需求对应的控制信息;
    确定模块,用于根据所述控制信息,确定随机接入过程成功。
  22. 一种通信设备,包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序,其中,所述计算机程序被所述处理器执行时实现如权利要求1至8中任一项所述的随机接入方法的步骤,或者实现如权利要求9至15中任一项所述的随机接入的响应方法的步骤,或者实现如权利要求16至18中任一项所述的随机接入方法的步骤。
  23. 一种计算机可读存储介质,其上存储有计算机程序,其中,所述计算机程序被处理器执行时实现如权利要求1至8中任一项所述的随机接入方法的步骤,或者实现如权利要求9至15中任一项所述的随机接入的响应方法的步骤,或者实现如权利要求16至18中任一项所述的随机接入方法的步骤。
PCT/CN2020/094878 2019-06-14 2020-06-08 随机接入方法、响应方法、终端及网络设备 WO2020248930A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/548,390 US20220104275A1 (en) 2019-06-14 2021-12-10 Random access method, random access response method, terminal, and network device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910517640.2 2019-06-14
CN201910517640.2A CN111417214B (zh) 2019-06-14 2019-06-14 随机接入方法、响应方法、终端及网络设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/548,390 Continuation US20220104275A1 (en) 2019-06-14 2021-12-10 Random access method, random access response method, terminal, and network device

Publications (1)

Publication Number Publication Date
WO2020248930A1 true WO2020248930A1 (zh) 2020-12-17

Family

ID=71494315

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/094878 WO2020248930A1 (zh) 2019-06-14 2020-06-08 随机接入方法、响应方法、终端及网络设备

Country Status (3)

Country Link
US (1) US20220104275A1 (zh)
CN (3) CN111417214B (zh)
WO (1) WO2020248930A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11864235B2 (en) * 2019-10-08 2024-01-02 Qualcomm Incorporated Random access response mapping for two-step random access channel procedure
CN113747427B (zh) * 2020-05-29 2023-12-12 维沃移动通信有限公司 下行数据的处理方法、装置、终端及存储介质
WO2022015108A1 (en) * 2020-07-17 2022-01-20 Samsung Electronics Co., Ltd. Method and apparatus for random access procedure for small data transmission in wireless communication
CN114040516A (zh) * 2021-11-30 2022-02-11 上海星思半导体有限责任公司 信息解析方法、发送方法、装置、电子设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108282901A (zh) * 2017-01-06 2018-07-13 电信科学技术研究院 一种随机接入响应方法和装置
CN108632987A (zh) * 2017-03-17 2018-10-09 华硕电脑股份有限公司 无线通信中应用于随机接入程序的后退机制的方法和设备
US20180324863A1 (en) * 2017-05-04 2018-11-08 At&T Intellectual Property I, L.P. Facilitating signaling and transmission protocols for enhanced beam management for initial access

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20130097586A (ko) * 2012-02-24 2013-09-03 주식회사 팬택 다중 요소 반송파 시스템에서 랜덤 액세스 절차의 수행 장치 및 방법
US11057935B2 (en) * 2017-03-22 2021-07-06 Comcast Cable Communications, Llc Random access process in new radio
CN109392178B (zh) * 2017-08-10 2021-07-13 维沃移动通信有限公司 Mpdu传输的方法、用户侧设备和网络侧设备
CN109392188B (zh) * 2017-08-11 2020-12-25 华为技术有限公司 随机接入方法、设备及系统
WO2019029251A1 (en) * 2017-08-11 2019-02-14 Telefonaktiebolaget Lm Ericsson (Publ) NETWORK DEVICE, TERMINAL DEVICE, AND ASSOCIATED METHODS

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108282901A (zh) * 2017-01-06 2018-07-13 电信科学技术研究院 一种随机接入响应方法和装置
CN108632987A (zh) * 2017-03-17 2018-10-09 华硕电脑股份有限公司 无线通信中应用于随机接入程序的后退机制的方法和设备
US20180324863A1 (en) * 2017-05-04 2018-11-08 At&T Intellectual Property I, L.P. Facilitating signaling and transmission protocols for enhanced beam management for initial access

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3GPP TS 36.321 V15.5.0", 3RD GENERATION PARTNERSHIP PROJECT; TECHNICAL SPECIFICATION GROUP RADIO ACCESS NETWORK; EVOLVED UNIVERSAL TERRESTRIAL RADIO ACCESS (E-UTRA); MEDIUM ACCESS CONTROL (MAC) PROTOCOL SPECIFICATION(RELEASE 15), 31 March 2019 (2019-03-31), DOI: 20200805165527X *

Also Published As

Publication number Publication date
US20220104275A1 (en) 2022-03-31
CN114375068B (zh) 2024-05-03
CN114375068A (zh) 2022-04-19
CN111417214B (zh) 2022-02-22
CN114375067A (zh) 2022-04-19
CN111417214A (zh) 2020-07-14

Similar Documents

Publication Publication Date Title
WO2020248930A1 (zh) 随机接入方法、响应方法、终端及网络设备
US11343855B2 (en) Method and device for random access and terminal
WO2020020212A1 (zh) 随机接入方法、终端及网络设备
US20220132589A1 (en) Method for random access procedure fallback, device, and system
US20210250802A1 (en) Sidelink connection control method, terminal, and network side device
WO2021088907A1 (zh) 失败报告的上报方法及相关设备
WO2021037148A1 (zh) 数据传输方法及终端
WO2019137305A1 (zh) 收发信息的方法、终端设备及网络设备
US20220052748A1 (en) Uplink transmission method, terminal, and network side device
CN110944406A (zh) 一种旁链路的链路建立方法及终端
WO2020063240A1 (zh) 信道接入方法、配置方法、终端及网络侧设备
WO2020169028A1 (zh) 副链路组播通信的配置方法和终端
WO2020156451A1 (zh) 随机接入方法及设备
US20220167306A1 (en) Data receiving method, data sending method, terminal, and network device
US20220159735A1 (en) Random access method, configuration method, terminal, and network side device
CN110719647B (zh) 一种随机接入方法、终端及网络设备
WO2019137368A1 (zh) 系统信息的传输方法和用户终端
WO2021027716A1 (zh) 能力协商方法、终端及网络设备
WO2020156072A1 (zh) 随机接入方法、装置、设备及介质
WO2019242466A1 (zh) 一种随机接入方法、终端及网络设备
WO2019137425A1 (zh) 重配置方法、终端及基站
WO2021204152A1 (zh) 资源确定方法及终端
JP7170119B2 (ja) ランダムアクセス方法、端末装置及びネットワーク装置
WO2021023219A1 (zh) 随机接入请求资源的选择方法、终端及网络设备
AU2020342206B2 (en) Message transmission method and terminal

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: 20823168

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: 20823168

Country of ref document: EP

Kind code of ref document: A1