Random access method and apparatus, device and storage medium

Abstract

A random access method and apparatus, a device, and a storage medium, relating to the technical field of communications. The method comprises: in a random access process, a terminal device transmitting a first message to a network device, a first OCC being used during transmission of the first message (510); and the network device transmitting a second message, the second message being related to a second OCC, and a first matching result of the first OCC and the second OCC being used for determining a step execution result of the random access process (520). By means of the method, even if the same information is indicated or carried by first messages transmitted by different terminal devices, as long as the OCCs are different, the network device can still identify a plurality of terminal devices (for example, two terminal devices) by means of the different OCCs. By means of indicating or using OCCs in second messages, the network device can provide feedback to two terminal devices using different OCCs, respectively, thereby facilitating increasing the capacity of the random access process.

Description

Random access method, device, equipment and storage medium Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular to a random access method, apparatus, device, and storage medium. Background Art

[0002] The random access process refers to the process from when the terminal device sends a random access preamble to try to access the network to when a basic signaling connection is established with the network.

[0003] To further enhance uplink capacity, an OCC (Orthogonal Cover Code) solution can be introduced into the communication system. After the introduction of OCC, the random access process needs further study.

[0004] Summary of the Invention

[0005] The embodiments of the present application provide a random access method, apparatus, device, and storage medium. The technical solutions provided by the embodiments of the present application are as follows:

[0006] According to one aspect of an embodiment of the present application, a random access method is provided, the method being performed by a terminal device, the method including:

[0007] During a random access process, a first message is sent to a network device, where the first message uses a first OCC in transmission;

[0008] receiving a second message sent by the network device, where the second message is related to a second OCC;

[0009] The first matching result between the first OCC and the second OCC is used to determine the execution result of the steps of the random access process.

[0010] According to one aspect of an embodiment of the present application, a random access method is provided, the method being performed by a network device, the method including:

[0011] During a random access process, receiving a first message sent by a terminal device, where the first message uses a first OCC in transmission;

[0012] sending a second message, the second message being related to a second OCC;

[0013] The first matching result between the first OCC and the second OCC is used to determine the execution result of the step of the random access process by the terminal device.

[0014] According to one aspect of an embodiment of the present application, a random access device is provided, the device including:

[0015] A sending module, configured to send a first message to a network device during a random access process, where the first message uses a first OCC during transmission;

[0016] a receiving module, configured to receive a second message sent by the network device, where the second message is related to a second OCC;

[0017] The first matching result between the first OCC and the second OCC is used to determine the execution result of the steps of the random access process.

[0018] According to one aspect of an embodiment of the present application, a random access device is provided, the device including:

[0019] A receiving module, configured to receive a first message sent by a terminal device during a random access process, where the first message uses a first OCC in transmission;

[0020] a sending module, configured to send a second message, where the second message is related to a second OCC;

[0021] The first matching result between the first OCC and the second OCC is used to determine the execution result of the step of the random access process by the terminal device.

[0022] According to one aspect of an embodiment of the present application, a terminal device is provided, comprising a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program to implement the random access method on the terminal device side.

[0023] According to one aspect of an embodiment of the present application, a network device is provided, comprising a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program to implement the random access method on the network device side.

[0024] According to one aspect of an embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is used to be executed by a processor to implement the above-mentioned random access method on the terminal device side, or to implement the above-mentioned random access method on the network device side.

[0025] According to one aspect of an embodiment of the present application, a chip is provided, which includes a programmable logic circuit and / or program instructions. When the chip is running, it is used to implement the above-mentioned random access method on the terminal device side, or to implement the above-mentioned random access method on the network device side.

[0026] According to one aspect of an embodiment of the present application, a computer program product is provided, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. A processor reads and executes the computer instructions from the computer-readable storage medium to implement the above-mentioned random access method on the terminal device side, or to implement the above-mentioned random access method on the network device side.

[0027] The technical solutions provided by the embodiments of the present application may have the following beneficial effects:

[0028] For the random access process, if the terminal device uses OCC when sending the first message, the network device also needs to indicate or use OCC in the second message fed back, and the matching results of the above two OCCs are used to determine the execution results of the steps of the random access process. Even if different terminal devices indicate or carry the same information when sending the first message, as long as the OCCs are different, the network device can still identify multiple terminal devices (for example, two terminal devices) through different OCCs. The network device indicates or uses OCC in the second message to provide feedback to two terminal devices with different OCCs, which helps to improve the capacity of the random access process. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] FIG1 is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0030] FIG2 is a schematic diagram of a contention-based random access method provided by an embodiment of the present application;

[0031] FIG3 is a schematic diagram of a non-contention-based random access method provided by an embodiment of the present application;

[0032] FIG4 is a schematic diagram of the format of a RAR MAC PDU provided in one embodiment of the present application;

[0033] FIG5 is a flowchart of a random access method provided by an embodiment of the present application;

[0034] FIG6 is a schematic diagram of using a separate MAC subheader to indicate an OCC according to an embodiment of the present application;

[0035] FIG7 is a schematic diagram of using a separate MAC subheader to indicate an OCC according to another embodiment of the present application;

[0036] FIG8 is a schematic diagram of using a MAC subheader to indicate a random access preamble sequence and an OCC according to an embodiment of the present application;

[0037] FIG9 is a schematic diagram of using RAR to indicate OCC according to an embodiment of the present application;

[0038] FIG10 is a schematic diagram of using RAR to indicate OCC according to another embodiment of the present application;

[0039] FIG11 is a schematic diagram of using a separate MAC CE to indicate an OCC according to an embodiment of the present application;

[0040] FIG12 is a schematic diagram of using a MAC CE to indicate a contention resolution identifier and an OCC according to an embodiment of the present application;

[0041] FIG13 is a block diagram of a random access apparatus provided by one embodiment of the present application;

[0042] FIG14 is a block diagram of a random access apparatus provided by another embodiment of the present application;

[0043] FIG15 is a schematic structural diagram of a communication device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0044] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0045] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. A person skilled in the art will appreciate that, with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0046] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system, B5G (Beyound 5G) system, sixth-generation communication (6G) system or other communication systems, etc.

[0047] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0048] The communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0049] The communication system in the embodiment of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as an unshared spectrum.

[0050] The embodiments of the present application can be applied to both non-terrestrial networks (NTN) and terrestrial networks (TN). NTNs generally use satellite communications to provide communication services to terrestrial users. Currently, NTN systems include NR-NTN and IoT-NTN systems, and may include other NTN systems in the future.

[0051] Please refer to FIG1 , which shows a schematic diagram of a network architecture 100 provided by an embodiment of the present application. The network architecture 100 may include: a terminal device 10 , an access network device 20 , and a core network element 30 .

[0052] The terminal device 10 may refer to a UE (User Equipment), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a wireless communication device, a user agent, or a user apparatus. In some embodiments, the terminal device 10 may also be a cellular phone, a cordless phone, a SIP (Session Initiation Protocol) phone, a WLL (Wireless Local Loop) station, a PDA (Personal Digital Assistant), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5GS (5th Generation System) or a terminal device in a future evolved PLMN (Public Land Mobile Network), etc., and the embodiments of the present application are not limited thereto. For ease of description, the above-mentioned devices are collectively referred to as terminal devices. The number of terminal devices 10 is generally multiple, and one or more terminal devices 10 may be distributed in a cell managed by each access network device 20. The terminal device may also be referred to as a terminal or UE for short, and those skilled in the art will understand its meaning.

[0053] Access network equipment 20 is a device deployed in an access network to provide wireless communication capabilities for terminal devices 10. Access network equipment 20 may include various forms of macro base stations, micro base stations, relay stations, access points, and the like. In systems employing different wireless access technologies, the names of devices that provide access network equipment functions may vary. For example, in 5G NR systems, they are referred to as gNodeBs or gNBs. As communication technologies evolve, the term "access network equipment" may change. For ease of description, in the embodiments of this application, the aforementioned devices that provide wireless communication capabilities for terminal devices 10 are collectively referred to as access network equipment. In some embodiments, access network equipment 20 enables communication between terminal devices 10 and core network elements 30. For example, in an LTE (Long Term Evolution) system, access network equipment 20 may be an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or one or more eNodeBs within the EUTRAN. In a 5G NR system, access network equipment 20 may be a Radio Access Network (RAN) or one or more gNBs within the RAN. In the embodiment of the present application, unless otherwise specified, the "network device" refers to the access network device 20, such as a base station.

[0054] The core network element 30 is a network element deployed in the core network. The functions of the core network element 30 are mainly to provide user connection, user management, and service bearer, and to provide an interface to the external network as a bearer network. For example, the core network elements in the 5G NR system may include network elements such as the AMF (Access and Mobility Management Function) entity, the UPF (User Plane Function) entity, and the SMF (Session Management Function) entity.

[0055] In some embodiments, the access network device 20 and the core network element 30 communicate with each other via an air interface technology, such as the NG interface in the 5G NR system. The access network device 20 and the terminal device 10 communicate with each other via an air interface technology, such as the Uu interface.

[0056] The "5G NR system" in the embodiments of the present application may also be referred to as a 5G system or an NR system, but those skilled in the art will understand its meaning. The technical solutions described in the embodiments of the present application may be applicable to LTE systems, 5G NR systems, and subsequent evolution systems of 5G NR systems (e.g., B5G (Beyond 5G) systems, 6G systems (6th Generation System, sixth generation mobile communication systems)), and other communication systems such as NB-IoT (Narrow Band Internet of Things) systems, which are not limited in this application.

[0057] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources (for example, frequency domain resources, or spectrum resources) on the carrier used by the cell. The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0058] Before introducing the technical solutions of this application, we first introduce and explain the related technologies involved in this application. The following related technologies can be combined with the technical solutions of the embodiments of this application as optional solutions, and they all fall within the scope of protection of the embodiments of this application. The embodiments of this application include at least part of the following contents.

[0059] 1. Contention-based random access and non-contention-based random access

[0060] Both LTE and NR systems support two random access methods: contention-based random access and non-contention-based random access. These two methods are applicable in different scenarios. In contention-based random access, the RACH (Random Access Channel) is a pool of resources available to terminal devices. Different terminal devices can use the same resources, resulting in resource contention. In non-contention-based random access, specific resources are reserved and allocated exclusively to a terminal device at a specific time.

[0061] Figure 2 illustrates contention-based random access, featuring code resource sharing and a four-step access process: access request, access response, connection request, and contention resolution. This process includes steps 1 through 4. It's important to note that the messages exchanged in each step of contention-based random access are referred to as Msg1 through Msg4.

[0062] Step 1: Access Request (Msg1)

[0063] The terminal device selects a PRACH (Physical Random Access Channel) resource (including time-frequency and code domain resources) and sends the selected preamble on the selected PRACH time-frequency resource. Based on the preamble, the network device can estimate the uplink timing and the grant size required by the terminal device to transmit Msg3.

[0064] Step 2: Access Response (Msg2)

[0065] After the network device receives the preamble sent by the terminal device, it sends a RAR (Random Access Response) to the terminal device. After the terminal device sends Msg1, it opens a RAR window and monitors the PDCCH (Physical Downlink Control Channel) within the window. The PDCCH is scrambled with RA-RNTI (Random Access-Radio Network Temporary Indentifier). After successfully monitoring the PDCCH scrambled with RA-RNTI, the terminal device can obtain the PDSCH (Physical Downlink Shared Channel) scheduled by the PDCCH, which contains the RAR.

[0066] A RAR MAC (Medium Access Control) PDU (Protocol Data Unit) consists of one or more MAC subPDUs and padding (optional).

[0067] In some embodiments, the RAR format is shown in FIG4 .

[0068] In Figure 4, MAC subPDU 1 is a BI-only MAC subPDU. BI (Backoff Indicator) indicates the backoff time for a terminal device to wait before re-initiating random access after a random access failure. This also indicates the backoff time for retransmitting Msg1. The BI field indicates that the cell is overloaded. The BI field is 4 bits long.

[0069] In Figure 4, MAC subPDU 2 is a RAPID-only MAC subPDU. RAPID stands for Random Access Preamble ID, which refers to the index number of the preamble used by the terminal device to initiate random access. The RAPID field indicates the transmitted random access preamble and is 6 bits long. The terminal device compares this RAPID with its own transmitted preamble. If they match, the received RAR is intended for it. Otherwise, the received RAR is discarded.

[0070] In Figure 4, MAC subPDU 3 is a MAC subPDU that includes RAPID and MAC RAR. The MAC RAR carries the following main information:

[0071] Timing Advance, that is, the uplink timing advance, is used to indicate how much time in advance the terminal device sends the uplink transmission to ensure that the uplink data reaches the network device and is consistent with the uplink air interface time of the network device. The timing advance is obtained by the physical layer of the network device by measuring the preamble sent by the terminal device. The TA command field indicates the index value used for the terminal device time adjustment. The TA index value can be one of 0, 1, 2, ..., 1282. The length of the TA command field is 11 bits. After the terminal device receives the RAR, it needs to configure the TA value to the physical layer, and the physical layer controls the delay of the subsequent Msg3 on the air interface to ensure that the time when the signals of different terminal devices arrive at the network device is roughly consistent.

[0072] Temporary C-RNTI, also known as TC-RNTI (Temporary Cell-RNTI). When a terminal device successfully competes for a cellular radio network, it directly upgrades the TC-RNTI to C-RNTI (Cell-RNTI). The TC-RNTI field is 16 bits long and is used for scrambling and descrambling in Msg3.

[0073] UL-Grant, uplink authorization. Because the terminal device has not yet established an RRC (Radio Resource Control) connection with the network device and has not performed uplink synchronization, it is impossible to request uplink authorization from the network device for uplink transmission through Scheduling Request. The terminal device can only send the first uplink message Msg3, which is RRCSetupRequest (RRC connection establishment request), by carrying uplink authorization information in the RAR message. The UL-Grant field indicates the resources used for uplink transmission. The length of the UL-Grant field is 20 bits, and Msg3 is actually sent using this resource.

[0074] Step 3: Connection Request (Msg3)

[0075] After receiving the RAR and using the Timing Advance in the RAR message to achieve uplink synchronization with the network device, the terminal device will use the uplink time-frequency domain resources indicated by the UL grant carried in the RAR to send Msg3. For the random access process of the terminal device accessing the cell, it is the RRC message: RRCSetupRequest.

[0076] The terminal device sends an RRC connection establishment request (RRCSetupRequest) to the network device, which carries the contention resolution ID. Msg3 is primarily used to inform the network device of the event that triggered the RACH process. For example, if it is an initial access randomization process, Msg3 will carry the UE ID and establishment cause; if it is an RRC reestablishment, it will carry the connected UE identifier and establishment cause. The ID carried in Msg3 also allows contention to be resolved in Step 4.

[0077] Step 4: Conflict Resolution (Msg4)

[0078] After sending Msg3, the terminal device will start the ra-ContentionResolutionTimer. Before the timer expires, the terminal device will continue to monitor the PDCCH of Msg4. If the timer expires, the terminal device will consider the contention failed and re-initiate the random access process.

[0079] After receiving the Msg3 sent by the terminal device, the network device will send a Msg4 (i.e., an RRCSetup message, the PDCCH corresponding to the message is scrambled using the TC-RNTI indicated in the RAR) to a certain terminal device, and carry the contention resolution ID sent by the terminal device in Msg3 in the MAC CE of the PDSCH carrying the Msg4 message. After receiving the Msg4 message, multiple terminal devices in contention will take out the contention resolution ID in the message and compare it with the contention resolution ID in their own Msg3. If the two are the same, the terminal device considers that the contention resolution is successful and sends RRCSetupComplete (RRC connection establishment completion message); otherwise, the terminal device considers that the contention has failed and re-initiates the random access process.

[0080] Msg4 has two functions: the first is to resolve contention conflicts, and the second is to transmit RRC configuration messages to terminal devices.

[0081] There are two ways to resolve contention conflicts: Method 1: If the terminal device carries C-RNTI in Msg3, Msg4 is scheduled with PDCCH scrambled with C-RNTI. Method 2: If the terminal device does not carry C-RNTI in Msg3, such as initial access, Msg4 is scheduled with PDCCH scrambled with TC-RNTI. The conflict is resolved by the terminal device receiving the PDSCH carrying Msg4 and matching the CCCH (Common Control Channel) SDU (Service Data Unit) in the PDSCH with the contention resolution ID in its own Msg3 to see if they are the same.

[0082] Figure 3 illustrates a non-contention-based random access scheme, whose key features are exclusive code resource allocation and a three-step access method, including preamble allocation, access request, and access response. This process includes the following steps: Step 0 through Step 2. It is important to note that the messages exchanged in each step of the non-contention-based random access scheme are referred to as Msg0 through Msg2.

[0083] Step 0: Preamble allocation (Msg0)

[0084] The network device allocates a random access preamble to the terminal device and sends it using an RRC message or DCI (Downlink Control Information).

[0085] Step 1: Access Request (Msg1)

[0086] Step 2: Access Response (Msg2)

[0087] For the description of Msg1 and Msg2, please refer to the above text and will not be repeated here.

[0088] To further enhance uplink capacity, both NTN and IoT-NTN are exploring OCC solutions. With the introduction of OCC, both Msg1 and Msg3 during the random access process may support OCC transmission. This has a significant impact on the random access process, as the current random access process does not support OCC and therefore cannot identify the OCC used by different terminal devices.

[0089] Please refer to Figure 5, which shows a flow chart of a random access method provided by an embodiment of the present application. The method can be applied to the network architecture shown in Figure 1. The method can include at least one of the following steps 510 to 520.

[0090] Step 510: During a random access process, the terminal device sends a first message to the network device, where the first message uses a first OCC during transmission.

[0091] Correspondingly, the network device receives the first message sent by the terminal device.

[0092] In some embodiments, the first message is Msg1 in the random access process, such as the Msg1 described in the contention-based / non-contention-based random access method described above. If the first message is Msg1, the second message in step 520 is Msg2.

[0093] In some embodiments, the first message is Msg3 in the random access process, such as Msg3 described above in the contention-based random access method. If the first message is Msg3, the second message in step 520 is Msg4.

[0094] In addition, the first OCC refers to the OCC used in the transmission of the first message. In some embodiments, the use of the first OCC in the transmission of the first message means that the terminal device uses OCC technology when sending the first message, such as superimposing the first OCC into the time domain, frequency domain, or code domain before transmitting the first message.

[0095] In step 520, the network device sends a second message, where the second message is related to the second OCC, wherein the first matching result between the first OCC and the second OCC is used to determine the execution result of the steps of the random access process.

[0096] Correspondingly, the terminal device receives the second message sent by the network device.

[0097] The second message is a message sent by the network device to the terminal device after receiving the first message sent by the terminal device.

[0098] If the first message is Msg1, after sending Msg1, the terminal device monitors Msg2 (i.e., random access response). For example, the terminal device calculates the RA-RNTI as described above and monitors the PDCCH scrambled by the RA-RNTI. After successfully monitoring the PDCCH scrambled by the RA-RNTI, the terminal device can obtain the PDSCH scheduled by the PDCCH, which includes the RAR.

[0099] If the first message is Msg3, the terminal device monitors Msg4 (i.e., contention resolution message) after sending Msg3. For example, the terminal device introduced above receives the contention resolution message by monitoring the PDCCH encrypted with TC-RNTI (if the terminal device does not carry C-RNTI in Msg3, such as initial access).

[0100] In some embodiments, the second message is related to the second OCC, which means that the second OCC is indicated in the second message. For example, the second message includes the second OCC, or the second message includes identification information of the second OCC. The identification information of the OCC is used to distinguish different OCCs, and different OCCs have different identification information. The above identification information can be in the form of an ID (Indentifier), an index, etc., which is not limited in this application. The second OCC can be determined by the identification information of the second OCC.

[0101] In some embodiments, the second message is associated with the second OCC, which means that the second message uses the second OCC during transmission. For example, the network device uses OCC technology when sending the second message, such as superimposing the second OCC into the time domain, frequency domain, or code domain before transmitting the second message.

[0102] In some embodiments, the first matching result indicates whether the first OCC and the second OCC match. In some embodiments, if they are identical, they are considered a match, and if they are different, they are considered a mismatch. For example, the first matching result may indicate that the first OCC and the second OCC are identical, meaning they match; or the first matching result may indicate that the first OCC and the second OCC are different, meaning they do not match.

[0103] If the first message is Msg1 and the second message is Msg2, the first matching result is used to determine the execution result of the random access response step of the random access procedure, and the execution result may be successful or failed reception of the random access response.

[0104] If the first message is Msg3 and the second message is Msg4, the first matching result is used to determine the execution result of the contention resolution step of the random access procedure, and the execution result may be contention resolution success or contention resolution failure.

[0105] In an embodiment of the present application, for the random access process, if the terminal device uses OCC when sending the first message, the network device also needs to indicate or use OCC in the second message fed back, and the matching results of the above two OCCs are used to determine the execution results of the steps of the random access process. Even if different terminal devices indicate or carry the same information when sending the first message, as long as the OCCs are different, the network device can still identify multiple terminal devices (for example, two terminal devices) through different OCCs. The network device indicates or uses OCC in the second message to provide feedback to two terminal devices with different OCCs, which helps to improve the capacity of the random access process.

[0106] Below, the technical solution of the present application is introduced and explained for the two cases where the first message is Msg1 and Msg3.

[0107] 1. The first message is Msg1

[0108] In some embodiments, the first message includes a first random access preamble sequence, and the second message indicates a second random access preamble sequence; wherein the first matching result and the second matching result of the first random access preamble sequence and the second random access preamble sequence are used to determine the execution result of the random access response step in the random access process.

[0109] The first message may be Msg1 during a random access process, which includes a first random access preamble sequence. The first random access preamble sequence refers to the random access preamble sequence included in the first message. For a contention-based random access scheme, the first random access preamble sequence may be a random access preamble sequence selected by the terminal device. For a non-contention-based random access scheme, the first random access preamble sequence may be a random access preamble sequence assigned by the network device to the terminal device.

[0110] The second message may be Msg2 in the random access process, which may include identification information of the second random access preamble sequence, such as an ID or index. After receiving the second message, the terminal device can determine the second random access preamble sequence according to the identification information of the second random access preamble sequence.

[0111] In the embodiment of the present application, the random access preamble sequence is also referred to as a random access preamble code, that is, the preamble mentioned above.

[0112] The second matching result indicates whether the first random access preamble sequence and the second random access preamble sequence match. In some embodiments, if they are identical, they are considered a match; if they are different, they are considered a mismatch. For example, the second matching result may be that the first random access preamble sequence and the second random access preamble sequence are identical, i.e., they match; or the second matching result may be that the first random access preamble sequence and the second random access preamble sequence are different, i.e., they do not match.

[0113] In the embodiment of the present application, after the OCC technology is introduced, if the first matching result is that the first OCC and the second OCC are the same, and the second matching result is that the first random access preamble sequence and the second random access preamble sequence are the same, then the execution result of the random access response step is a reception success. Conversely, if the first matching result is that the first OCC and the second OCC are different, and / or the second matching result is that the first random access preamble sequence and the second random access preamble sequence are different, then the execution result of the random access response step is a reception failure.

[0114] In the case where the first message is Msg1 and the second message is Msg2, the present application provides several possible implementations of indicating the second OCC in Msg2.

[0115] Mode 1: The second message includes at least one sub-packet, and a header of a first sub-packet in the at least one sub-packet indicates the second OCC.

[0116] The sub-packet is a component of the packet of the second message, and the packet of the second message may include at least one sub-packet. The first sub-packet may be a sub-packet in the at least one sub-packet.

[0117] In some embodiments, the second message is a MAC PDU, which may include at least one MAC subPDU, where the MAC subPDU is a subpacket. The first subpacket may be a MAC subPDU in the at least one MAC subPDU, such as a first MAC subPDU.

[0118] In some embodiments, the first subpacket may include a header. For example, the header of the first MAC subPDU may be called a MAC subheader. The second OCC may be indicated in the MAC subheader of the first MAC subPDU.

[0119] In some embodiments, the header of the first sub-packet includes a first information field and a second information field. The first information field is used to indicate that an OCC is indicated in the header of the first sub-packet, and the second information field is used to indicate a second OCC. For example, the second information field may include identification information of the second OCC, such as an ID or index, to indicate the second OCC.

[0120] For example, as shown in FIG6 , taking the OCC identification information occupying 4 bits as an example, the MAC subheader can be an E / T1 / T2 / R / OCCID MAC subheader. E is an extended bit. The combination of T1 and T2 serves as a first information field, used to indicate that an OCC is indicated in the MAC subheader, or to indicate that the MAC subheader is an E / T1 / T2 / R / OCCID MAC subheader. For example, T1=1 and T2 equals 1, indicating that an OCC is indicated in the MAC subheader. R is a reserved bit. OCCID, as a second information field, includes OCC identification information and is used to indicate the OCC.

[0121] For example, as shown in Figure 7, taking the OCC identification information occupying 5 bits as an example, the MAC subheader can be an E / T1 / T2 / OCCID MAC subheader. E represents an extension bit. The combination of T1 and T2, as the first information field, is used to indicate that the MAC subheader contains an OCC, or to indicate that the MAC subheader is an E / T1 / T2 / OCCID MAC subheader. For example, T1 = 1 and T2 equals 1, indicating that the MAC subheader contains an OCC. OCCID, as the second information field, includes OCC identification information and is used to indicate the OCC.

[0122] In the examples shown in Figures 6 and 7 above, the OCC identification information occupies 4 or 5 bits, and the MAC subheader including the OCC identification information is 8 bits in total, equivalent to one byte. If the OCC identification information requires more bits, a MAC subheader of 2 bytes or more can be defined, and the excess bits can be padded with R bits (reserved bits).

[0123] Through this approach 1, it is achieved that a separate sub-packet header is used in the second message to indicate the OCC, such as using a separate MAC subheader to indicate the OCC in Msg2.

[0124] Mode 2: The second message includes at least one subpacket, and a header of a first subpacket in the at least one subpacket indicates the second random access preamble sequence and the second OCC.

[0125] For an introduction to subpackets and headers, refer to the description of Method 1 above and are not repeated here. The difference between Method 2 and Method 1 is that Method 1 uses a separate subpacket header in the second message to indicate the OCC, while Method 2 uses a subpacket header in the second message to indicate the random access preamble sequence and OCC.

[0126] In some embodiments, the header of the first subpacket includes a first information field, a second information field, and a third information field. The first information field is used to indicate that an OCC is indicated in the header of the first subpacket, the second information field is used to indicate a second OCC, and the third information field is used to indicate a second random access preamble sequence. For example, the third information field may include identification information of the second random access preamble sequence, such as an ID or an index, to indicate the second random access preamble sequence.

[0127] Exemplarily, as shown in Figure 8, taking the OCC identification information occupying 5 bits as an example, the MAC subheader can be an E / T1 / T2 / R / R / RAPID / OCCID MAC subheader. Among them, E is an extension bit. The combination of T1 and T2 is used as the first information field to indicate that the MAC subheader indicates an OCC, or to indicate that the MAC subheader is an E / T1 / T2 / R / R / RAPID / OCCID MAC subheader. For example, T1=1 and T2 equals 1, which means that the MAC subheader indicates an OCC. OCCID is used as the second information field, including the identification information of the OCC, and is used for OCC. RAPID is used as the third information field, including the identification information of the random access preamble sequence, and is used to indicate the random access preamble sequence (preamble).

[0128] In addition, the front-to-back position relationship of OCCID and RAPID in the MAC subheader can be OCCID in front and RAPID in the back (as shown in FIG8 ), or RAPID in front and OCCID in the back, which is not limited in this application.

[0129] In addition, the number of OCCID bits determines the number of R bits (reserved bits) in the MAC subheader. For example, when the OCCID has 5 bits, the number of R bits in the MAC subheader is 2 (as shown in Figure 8); when the OCCID has 6 bits, the number of R bits in the MAC subheader is 1; and when the OCCID has 7 bits, the number of R bits in the MAC subheader is 0.

[0130] Through this approach 2, it is achieved that a header of a subpacket is used in the second message to jointly indicate the random access preamble sequence and the OCC, for example, a MAC subheader is used in Msg2 to indicate the random access preamble sequence and the OCC.

[0131] Mode 3: The second message includes at least one sub-packet, and a packet body of a first sub-packet in the at least one sub-packet indicates the second OCC.

[0132] For the introduction of sub-packages, please refer to the introduction in method 1 above, which will not be repeated here.

[0133] In some embodiments, the first sub-packet may include a header and a body. For example, the body of the first MAC subPDU may be called a MAC RAR, and the second OCC may be indicated in the MAC RAR of the first MAC subPDU.

[0134] In some embodiments, the body of the first sub-packet includes a fourth information field and a fifth information field. The fourth information field is used to indicate that an OCC is indicated in the body of the first sub-packet, and the fifth information field is used to indicate a second OCC. For example, the fifth information field may include identification information of the second OCC, such as an ID or index, to indicate the second OCC.

[0135] In some embodiments, the MAC RAR originally includes 7 bytes, and one or more bytes are added to the MAC RAR to indicate the OCC.

[0136] For example, as shown in Figure 9, the MAC RAR is increased from 7 bytes to 8 bytes. Assuming that the OCC identification information occupies 8 bits, the originally reserved bits R can be used as the fourth information field to indicate that the MAC RAR indicates an OCC. The OCCID, as the fifth information field, includes OCC identification information and is used to indicate the OCC.

[0137] For example, as shown in FIG10 , the MAC RAR is increased from 7 bytes to 8 bytes. Assume that the OCC identification information occupies 7 bits, where T is used as the fourth information field to indicate that the MAC RAR contains an OCC. OCCID is used as the fifth information field to include OCC identification information and is used to indicate the OCC.

[0138] In addition, if the number of OCCID bits is less than 8 or 7 bits, R bits (reserved bits) can be added to pad the bits. If the number of OCCID bits needs to be greater than 8 bits, 2 or more bytes can be added to the MAC RAR. In addition, in Figures 9 and 10, the OCCID is located in the last byte of the MAC RAR as an example. The OCCID can also be located in other positions in the MAC RAR, and this application does not limit this.

[0139] Through this method 3, it is achieved that the OCC is indicated by using the body of a sub-packet in the second message, such as using MAC RAR to indicate the OCC in Msg2.

[0140] After the introduction of Msg1 OCC transmission, even if different terminal devices select the same preamble, as long as the OCC is different, the network device can still identify multiple terminal devices (for example, two terminal devices) through different OCCs. In the prior art, Msg2 only indicates RAPID, so it is impossible to determine which terminal device the subsequent RAR is for instead of for both terminal devices at the same time. Indicating both RAPID and OCC ID in Msg2 allows the network device to send two MAC subPDUs to two terminal devices (each terminal device is jointly identified by RAPID and OCC) in one Msg2, and then separately indicate MAC RAR to the two terminal devices that send the same preamble but different OCCs, which helps to improve the capacity of the random access process.

[0141] 2. The first message is Msg3

[0142] In some embodiments, the first message includes a CCCH SDU, and the second message includes a contention resolution identifier; wherein the first matching result and the third matching result of the CCCH SDU and the contention resolution identifier are used to determine the execution result of the contention resolution step in the random access process.

[0143] The first message may be Msg3 in the random access process, which includes the CCCH SDU. The second message may be Msg4 in the random access process, which includes the contention resolution flag.

[0144] The third matching result is used to indicate whether the CCCH SDU matches the contention resolution identifier. In some embodiments, if the CCCH SDU includes the contention resolution identifier, it indicates a match; if the CCCH SDU does not include the contention resolution identifier, it indicates a mismatch.

[0145] In the embodiment of the present application, after the OCC technology is introduced, if the first matching result is that the first OCC and the second OCC are the same, and the third matching result is that the CCCH SDU matches the contention resolution identifier, then the execution result of the contention resolution step is a successful contention resolution. Conversely, if the first matching result is that the first OCC and the second OCC are different, and / or the third matching result is that the CCCH SDU does not match the contention resolution identifier, then the execution result of the contention resolution step is a failed contention resolution.

[0146] In the case where the first message is Msg3, the second message is Msg4. This application provides several possible implementations of indicating the second OCC in Msg4.

[0147] Mode 1: The second message includes at least one control element, wherein a first control element in the at least one control element is used to indicate the second OCC. The second message also includes a second control element, wherein the second control element is used to indicate a contention resolution identifier, and the first control element and the second control element are two different control elements.

[0148] A control element (CE) is a component of a second message, and the second message may include at least one control element. The first control element may be one of the at least one control element.

[0149] In some embodiments, Msg4 includes a first MAC CE and a second MAC CE, and the first MAC CE and the second MAC CE are two different MAC CEs, wherein the first MAC CE is used to indicate the second OCC, and the second MAC CE is used to indicate the contention resolution identifier. Exemplarily, the first MAC CE can be called an OCC ID MAC CE, and the second MAC CE is a UE Contention Resolution Identity MAC CE (UE Contention Resolution Identity MAC CE). If Msg4 contains a UE Contention Resolution Identity MAC CE and an OCC ID MAC CE, wherein the indicated UE Contention Resolution Identity matches the CCCH SDU in Msg3 and the indicated OCC ID matches the identification information of the second OCC used to send Msg3, the terminal device considers that the contention resolution is successful.

[0150] For example, taking the OCC identification information occupying 8 bits as an example, the OCC Identity MAC CE is shown in Figure 11. If the number of bits of the OCC identification information is greater than 8 bits, a length of 2 bytes or more can be used; if the number of bits of the OCC identification information is less than 8 bits, R bits (reserved bits) are used for padding.

[0151] In some embodiments, the first control element has a corresponding logical channel identifier. One MAC CE corresponds to one logical channel. For the newly introduced OCC Identity MAC CE, an LCID / eLCID is determined from the reserved LCID (Logical Channel Identification) or eLCID (Extended Logical Channel Identification) to identify the ID of the logical channel of the OCC ID MAC CE.

[0152] Through this approach 1, it is achieved that a separate control element is used in the second message to indicate the OCC, such as using a separate MAC CE to indicate the OCC in Msg4.

[0153] Mode 2: The second message includes at least one control element, a first control element in the at least one control element is used to indicate the second OCC, and the first control element is also used to indicate a contention resolution identifier.

[0154] For an introduction to control elements, please refer to the introduction to Method 1 above and will not be repeated here. The difference between Method 2 and Method 1 is that Method 1 uses a separate control element in the second message to indicate the OCC, while Method 2 uses a single control element in the second message to indicate the contention resolution identifier and the OCC.

[0155] In some embodiments, Msg4 includes a first MAC CE, which is used to indicate a contention resolution identifier and a second OCC. Exemplarily, the first MAC CE may be referred to as a UE Contention Resolution Identity & OCC Identity MAC CE. If Msg4 includes a UE Contention Resolution Identity & OCC Identity MAC CE, where the indicated UE Contention Resolution Identity matches the CCCH SDU in Msg3 and the indicated OCC ID matches the identification information of the second OCC used in sending Msg3, the terminal device deems that the contention resolution is successful.

[0156] For example, taking the OCC identification information occupying 8 bits as an example, the UE Contention Resolution Identity & OCC Identity MAC CE is shown in Figure 12. If the number of bits of the OCC identification information is greater than 8 bits, a length of 8 bytes or more can be used; if the number of bits of the OCC identification information is less than 8 bits, it is padded with R bits (reserved bits). The position of the OCC identification information can be before or after the UE Contention Resolution Identity, which is not limited in this application.

[0157] In some embodiments, the first control element has a corresponding logical channel identifier. One MAC CE corresponds to one logical channel. For the newly introduced UE Contention Resolution Identity & OCC Identity MAC CE, an LCID / eLCID is determined from the reserved LCIDs or eLCIDs to identify the ID of the logical channel of the UE Contention Resolution Identity & OCC Identity MAC CE. Alternatively, the LCID or eLCID originally assigned to the UE Contention Resolution Identity MAC CE is used as the LCID or eLCID of the newly introduced UE Contention Resolution Identity & OCC Identity MAC CE.

[0158] Through this approach 2, it is achieved that a control element is used in the second message to jointly indicate the contention resolution identifier and the OCC, such as using a MAC CE in Msg4 to indicate the contention resolution identifier and the OCC.

[0159] After the introduction of Msg3 OCC transmission, even if the terminal device sends the same CCCH SDU in Msg3, as long as the OCC is different, the network device can still identify multiple terminal devices (for example, two terminal devices) through different OCCs. In the prior art, Msg4 only indicates the UE Contention Resolution Identity (used to compare CCCH SDU), so it is impossible to determine which terminal device the contention resolution is for. Indicating both the UE Contention Resolution Identity and the OCC ID in Msg4 allows the network device to indicate in Msg4 which of the two terminal devices the contention resolution is for. Reduce contention conflicts and improve the capacity of the random access process.

[0160] The above embodiments only describe the technical solutions provided by this application from the perspective of the interaction between a terminal device and a network device. The above steps performed by the terminal device can be independently implemented as a random access method on the terminal device side. The above steps performed by the network device can be independently implemented as a random access method on the network device side.

[0161] The following are device embodiments of the present application, which can be used to implement the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

[0162] Please refer to Figure 13, which shows a block diagram of a random access device provided by one embodiment of the present application. This device has the functionality to implement the random access method described above. This functionality can be implemented in hardware or by hardware executing corresponding software. This device can be the terminal device described above, or it can be provided within a terminal device. As shown in Figure 13, this device 1300 may include a sending module 1310 and a receiving module 1320.

[0163] The sending module 1310 is configured to send a first message to a network device during a random access process, where the first message uses a first OCC during transmission.

[0164] The receiving module 1320 is configured to receive a second message sent by the network device, wherein the second message is related to a second OCC. The first matching result between the first OCC and the second OCC is used to determine the execution result of the steps of the random access process.

[0165] In some embodiments, the second message is related to the second OCC, including: the second OCC is indicated in the second message, or the second message uses the second OCC in transmission.

[0166] In some embodiments, the first message includes a first random access preamble sequence, and the second message indicates a second random access preamble sequence; wherein the first matching result and the second matching result between the first random access preamble sequence and the second random access preamble sequence are used to determine the execution result of the random access response step of the terminal device in the random access process.

[0167] In some embodiments, the second message includes at least one sub-packet, and a header of a first sub-packet in the at least one sub-packet indicates the second OCC.

[0168] In some embodiments, the header of the first subpacket includes a first information field and a second information field, the first information field is used to indicate that the header of the first subpacket indicates an OCC, and the second information field is used to indicate the second OCC.

[0169] In some embodiments, the second message includes at least one sub-packet, and a header of a first sub-packet in the at least one sub-packet indicates the second random access preamble sequence and the second OCC.

[0170] In some embodiments, the header of the first subpacket includes a first information field, a second information field, and a third information field, the first information field is used to indicate that an OCC is indicated in the header of the first subpacket, the second information field is used to indicate the second OCC, and the third information field is used to indicate the second random access preamble sequence.

[0171] In some embodiments, the second message includes at least one sub-packet, and a packet body of a first sub-packet in the at least one sub-packet indicates the second OCC.

[0172] In some embodiments, the body of the first subpacket includes a fourth information field and a fifth information field, the fourth information field is used to indicate that the body of the first subpacket indicates an OCC, and the fifth information field is used to indicate the second OCC.

[0173] In some embodiments, if the first matching result is that the first OCC is the same as the second OCC, and the second matching result is that the first random access preamble sequence is the same as the second random access preamble sequence, then the execution result of the random access response step is successful reception.

[0174] In some embodiments, the first message includes a CCCH SDU, and the second message includes a contention resolution identifier; wherein the first matching result and the third matching result of the CCCH SDU and the contention resolution identifier are used to determine the execution result of the contention resolution step of the terminal device in the random access process.

[0175] In some embodiments, the second message includes at least one control element, and a first control element of the at least one control element is used to indicate the second OCC.

[0176] In some embodiments, the second message further includes a second control element, where the second control element is used to indicate the contention resolution identifier, and the first control element and the second control element are two different control elements.

[0177] In some embodiments, the first control element is further used to indicate the contention resolution identifier.

[0178] In some embodiments, the first control element has a corresponding logical channel identifier.

[0179] In some embodiments, if the first matching result is that the first OCC is the same as the second OCC, and the third matching result is that the CCCH SDU matches the contention resolution identifier, then the execution result of the contention resolution step is that contention resolution is successful.

[0180] Please refer to Figure 14, which shows a block diagram of a random access device provided by another embodiment of the present application. This device has the functionality to implement the random access method described above. This functionality can be implemented in hardware or by hardware executing corresponding software. This device can be the network device described above, or it can be provided within a network device. As shown in Figure 14, this device 1400 may include a receiving module 1410 and a sending module 1420.

[0181] The receiving module 1410 is configured to receive a first message sent by a terminal device during a random access process, where the first message uses a first OCC during transmission.

[0182] The sending module 1420 is configured to send a second message, where the second message is related to a second OCC. The first matching result between the first OCC and the second OCC is used to determine the execution result of the step of the random access process by the terminal device.

[0183] In some embodiments, the second message is related to the second OCC, including: the second OCC is indicated in the second message, or the second message uses the second OCC in transmission.

[0184] In some embodiments, the first message includes a first random access preamble sequence, and the second message indicates a second random access preamble sequence; wherein the first matching result and the second matching result between the first random access preamble sequence and the second random access preamble sequence are used to determine the execution result of the random access response step of the terminal device in the random access process.

[0185] In some embodiments, the second message includes at least one sub-packet, and a header of a first sub-packet in the at least one sub-packet indicates the second OCC.

[0186] In some embodiments, the header of the first subpacket includes a first information field and a second information field, the first information field is used to indicate that the header of the first subpacket indicates an OCC, and the second information field is used to indicate the second OCC.

[0187] In some embodiments, the second message includes at least one sub-packet, and a header of a first sub-packet in the at least one sub-packet indicates the second random access preamble sequence and the second OCC.

[0188] In some embodiments, the header of the first subpacket includes a first information field, a second information field, and a third information field, the first information field is used to indicate that an OCC is indicated in the header of the first subpacket, the second information field is used to indicate the second OCC, and the third information field is used to indicate the second random access preamble sequence.

[0189] In some embodiments, the second message includes at least one sub-packet, and a packet body of a first sub-packet in the at least one sub-packet indicates the second OCC.

[0190] In some embodiments, the body of the first subpacket includes a fourth information field and a fifth information field, the fourth information field is used to indicate that the body of the first subpacket indicates an OCC, and the fifth information field is used to indicate the second OCC.

[0191] In some embodiments, if the first matching result is that the first OCC is the same as the second OCC, and the second matching result is that the first random access preamble sequence is the same as the second random access preamble sequence, then the execution result of the random access response step is successful reception.

[0192] In some embodiments, the first message includes a CCCH SDU, and the second message includes a contention resolution identifier; wherein the first matching result and the third matching result of the CCCH SDU and the contention resolution identifier are used to determine the execution result of the contention resolution step of the terminal device in the random access process.

[0193] In some embodiments, the second message includes at least one control element, and a first control element of the at least one control element is used to indicate the second OCC.

[0194] In some embodiments, the second message further includes a second control element, where the second control element is used to indicate the contention resolution identifier, and the first control element and the second control element are two different control elements.

[0195] In some embodiments, the first control element is further used to indicate the contention resolution identifier.

[0196] In some embodiments, the first control element has a corresponding logical channel identifier.

[0197] In some embodiments, if the first matching result is that the first OCC is the same as the second OCC, and the third matching result is that the CCCH SDU matches the contention resolution identifier, then the execution result of the contention resolution step is that contention resolution is successful.

[0198] It should be noted that, when the device provided in the above embodiment realizes its function, it only uses the division of the above-mentioned functional modules as an example. In actual application, the above-mentioned functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0199] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here. For details not described in detail in the embodiment of the device, reference can be made to the above method embodiment.

[0200] Please refer to Figure 15, which shows a schematic diagram of the structure of a communication device provided by one embodiment of the present application. The communication device can be the terminal device or network device described above. The communication device 1500 may include: a processor 1501, a transceiver 1502, and a memory 1503. The processor 1501 is used to implement various processing functions of the communication device 1500, such as generating information to be transmitted, processing received information, and controlling transmission and / or reception. The transceiver 1502 is used to implement transmission and / or reception functions, such as the functions of the transmission module and / or reception module described above.

[0201] The processor 1501 includes one or more processing cores. The processor 1501 executes various functional applications and information processing by running software programs and modules.

[0202] The transceiver 1502 may include a receiver and a transmitter. For example, the receiver and the transmitter may be implemented as the same wireless communication component, which may include a wireless communication chip and a radio frequency antenna.

[0203] The memory 1503 may be connected to the processor 1501 and the transceiver 1502 .

[0204] The memory 1503 may be used to store a computer program executed by the processor, and the processor 1501 is used to execute the computer program to implement each step in the above method embodiment.

[0205] In some embodiments, the communication device 1500 is a terminal device, and the transceiver 1502 is used to send a first message to a network device during a random access process, where the first message uses a first OCC during transmission; the transceiver 1502 is also used to receive a second message sent by the network device, where the second message is related to a second OCC; wherein the first matching result between the first OCC and the second OCC is used to determine the execution result of the steps of the random access process.

[0206] In some embodiments, the communication device 1500 is a network device, and the transceiver 1502 is used to receive a first message sent by a terminal device during a random access process, and the first message uses a first OCC in transmission; the transceiver 1502 is also used to send a second message, and the second message is related to a second OCC; wherein the first matching result between the first OCC and the second OCC is used to determine the execution result of the step of the random access process by the terminal device.

[0207] For details not described in detail in this embodiment, please refer to the above embodiments and will not be described in detail here.

[0208] In addition, the memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic or optical disks, electrically erasable programmable read-only memory, erasable programmable read-only memory, static access memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0209] The embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored, and the computer program is used to be executed by a processor to implement the random access method on the terminal device side or the random access method on the network device side. In some embodiments, the computer-readable storage medium may include: ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives) or optical disks, etc. Among them, the random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

[0210] An embodiment of the present application also provides a chip, which includes a programmable logic circuit and / or program instructions. When the chip is running, it is used to implement the above-mentioned random access method on the terminal device side, or to implement the above-mentioned random access method on the network device side.

[0211] An embodiment of the present application also provides a computer program product, which includes computer instructions, which are stored in a computer-readable storage medium. A processor reads and executes the computer instructions from the computer-readable storage medium to implement the above-mentioned random access method on the terminal device side, or to implement the above-mentioned random access method on the network device side.

[0212] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0213] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0214] In some embodiments of the present application, "predefined" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, predefined may refer to information defined in a protocol.

[0215] In some embodiments of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, it may include the BLE protocol, the Wi-Fi protocol and related protocols used in future communication systems, and the present application does not limit this.

[0216] In this document, "plurality" refers to two or more. "And / or" describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. The character " / " generally indicates an "or" relationship between the associated objects.

[0217] The term “greater than or equal to” mentioned herein may mean greater than or equal to, or greater than, and the term “less than or equal to” may mean less than or equal to, or less than.

[0218] In addition, the step numbers described in this document only illustrate a possible execution order between the steps. In some other embodiments, the above steps may not be executed in the order of the numbers, such as two steps with different numbers are executed at the same time, or two steps with different numbers are executed in the opposite order of the diagram. The embodiments of the present application are not limited to this.

[0219] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0220] The above description is merely an exemplary embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A random access method, characterized in that: The method is executed by a terminal device, and includes: During a random access process, a first message is sent to a network device, where the first message uses a first orthogonal cover code (OCC) during transmission; receiving a second message sent by the network device, where the second message is related to a second OCC; The first matching result between the first OCC and the second OCC is used to determine the execution result of the steps of the random access process.

2. The method according to claim 1, characterized in that The second message is related to the second OCC, including: the second OCC is indicated in the second message, or the second message uses the second OCC during transmission.

3. The method according to claim 1 or 2, characterized in that The first message includes a first random access preamble sequence, and the second message indicates a second random access preamble sequence; The first matching result and the second matching result between the first random access preamble sequence and the second random access preamble sequence are used to determine an execution result of a random access response step in the random access process.

4. The method according to claim 3, characterized in that The second message includes at least one sub-packet, and a header of a first sub-packet in the at least one sub-packet indicates the second OCC.

5. The method according to claim 4, characterized in that The header of the first subpacket includes a first information field and a second information field, the first information field is used to indicate that the header of the first subpacket indicates an OCC, and the second information field is used to indicate the second OCC.

6. The method according to claim 3, characterized in that The second message includes at least one sub-packet, and a header of a first sub-packet in the at least one sub-packet indicates the second random access preamble sequence and the second OCC.

7. The method according to claim 6, characterized in that The header of the first subpacket includes a first information field, a second information field, and a third information field. The first information field is used to indicate that an OCC is indicated in the header of the first subpacket, the second information field is used to indicate the second OCC, and the third information field is used to indicate the second random access preamble sequence.

8. The method according to claim 3, characterized in that The second message includes at least one sub-packet, and a packet body of a first sub-packet in the at least one sub-packet indicates the second OCC.

9. The method according to claim 8, characterized in that The body of the first subpacket includes a fourth information field and a fifth information field, the fourth information field is used to indicate that the body of the first subpacket indicates an OCC, and the fifth information field is used to indicate the second OCC.

10. The method according to any one of claims 3 to 9, characterized in that If the first matching result is that the first OCC is the same as the second OCC, and the second matching result is that the first random access preamble sequence is the same as the second random access preamble sequence, then the execution result of the random access response step is successful reception.

11. The method according to claim 1 or 2, characterized in that The first message includes a common control channel CCCH service data unit SDU, and the second message includes a contention resolution identifier; The first matching result and the third matching result between the CCCH SDU and the contention resolution identifier are used to determine the execution result of the contention resolution step in the random access process.

12. The method according to claim 11, characterized in that The second message includes at least one control element, and a first control element in the at least one control element is used to indicate the second OCC.

13. The method according to claim 12, characterized in that The second message also includes a second control element, where the second control element is used to indicate the contention resolution identifier. The first control element and the second control element are two different control elements.

14. The method according to claim 12, characterized in that The first control element is further used to indicate the contention resolution identifier.

15. The method according to any one of claims 12 to 14, characterized in that The first control element has a corresponding logical channel identifier.

16. The method according to any one of claims 11 to 15, characterized in that If the first matching result is that the first OCC is the same as the second OCC, and the third matching result is that the CCCH SDU matches the contention resolution identifier, then the execution result of the contention resolution step is that contention resolution is successful.

17. A random access method, characterized in that: The method is performed by a network device, and includes: During a random access process, receiving a first message sent by a terminal device, where the first message uses a first orthogonal cover code OCC during transmission; sending a second message, the second message being related to a second OCC; The first matching result between the first OCC and the second OCC is used to determine the execution result of the step of the random access process by the terminal device.

18. The method according to claim 17, characterized in that The second message is related to the second OCC, including: the second OCC is indicated in the second message, or the second message uses the second OCC during transmission.

19. The method according to claim 17 or 18, characterized in that The first message includes a first random access preamble sequence, and the second message indicates a second random access preamble sequence; The first matching result and the second matching result between the first random access preamble sequence and the second random access preamble sequence are used to determine the execution result of the random access response step of the terminal device in the random access process.

20. The method according to claim 19, characterized in that The second message includes at least one sub-packet, and a header of a first sub-packet in the at least one sub-packet indicates the second OCC.

21. The method according to claim 20, characterized in that The header of the first subpacket includes a first information field and a second information field, the first information field is used to indicate that the header of the first subpacket indicates an OCC, and the second information field is used to indicate the second OCC.

22. The method according to claim 19, wherein The second message includes at least one sub-packet, and a header of a first sub-packet in the at least one sub-packet indicates the second random access preamble sequence and the second OCC.

23. The method according to claim 22, characterized in that The header of the first subpacket includes a first information field, a second information field, and a third information field. The first information field is used to indicate that an OCC is indicated in the header of the first subpacket, the second information field is used to indicate the second OCC, and the third information field is used to indicate the second random access preamble sequence.

24. The method according to claim 19, wherein The second message includes at least one sub-packet, and a packet body of a first sub-packet in the at least one sub-packet indicates the second OCC.

25. The method according to claim 24, characterized in that The body of the first subpacket includes a fourth information field and a fifth information field, the fourth information field is used to indicate that the body of the first subpacket indicates an OCC, and the fifth information field is used to indicate the second OCC.

26. The method according to any one of claims 19 to 25, characterized in that If the first matching result is that the first OCC is the same as the second OCC, and the second matching result is that the first random access preamble sequence is the same as the second random access preamble sequence, then the execution result of the random access response step is successful reception.

27. The method according to claim 17 or 18, characterized in that The first message includes a common control channel CCCH service data unit SDU, and the second message includes a contention resolution identifier; Among them, the first matching result and the third matching result of the CCCH SDU and the contention resolution identifier are used to determine the execution result of the contention resolution step of the terminal device in the random access process.

28. The method according to claim 27, characterized in that The second message includes at least one control element, and a first control element in the at least one control element is used to indicate the second OCC.

29. The method according to claim 28, characterized in that The second message also includes a second control element, where the second control element is used to indicate the contention resolution identifier. The first control element and the second control element are two different control elements.

30. The method according to claim 28, wherein The first control element is further used to indicate the contention resolution identifier.

31. The method according to any one of claims 28 to 30, characterized in that The first control element has a corresponding logical channel identifier.

32. The method according to any one of claims 27 to 31, characterized in that If the first matching result is that the first OCC is the same as the second OCC, and the third matching result is that the CCCH SDU matches the contention resolution identifier, then the execution result of the contention resolution step is that contention resolution is successful.

33. A random access device, characterized in that: The device comprises: A sending module, configured to send a first message to a network device during a random access process, where the first message uses a first orthogonal cover code OCC during transmission; a receiving module, configured to receive a second message sent by the network device, where the second message is related to a second OCC; The first matching result between the first OCC and the second OCC is used to determine the execution result of the steps of the random access process.

34. A random access device, characterized in that: The device comprises: A receiving module, configured to receive a first message sent by a terminal device during a random access process, where the first message uses a first orthogonal cover code OCC during transmission; a sending module, configured to send a second message, where the second message is related to a second OCC; The first matching result between the first OCC and the second OCC is used to determine the execution result of the step of the random access process by the terminal device.

35. A terminal device, characterized in that: The terminal device includes a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program to implement the method according to any one of claims 1 to 16.

36. A network device, characterized in that: The network device includes a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program to implement the method according to any one of claims 17 to 32.

37. A computer-readable storage medium, characterized in that The storage medium stores a computer program, which is used to be executed by a processor to implement the method according to any one of claims 1 to 16, or to implement the method according to any one of claims 17 to 32.

38. A chip, characterized in that: The chip includes a programmable logic circuit and / or program instructions, and when the chip is running, it is used to implement the method according to any one of claims 1 to 16, or to implement the method according to any one of claims 17 to 32.

39. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium. A processor reads and executes the computer instructions from the computer-readable storage medium to implement the method according to any one of claims 1 to 16, or to implement the method according to any one of claims 17 to 32.

Images