Random access method and apparatus, device, chip, and storage medium

Abstract

Embodiments of the present application provide a random access method, applied to a terminal device. The method comprises: sending a preamble to a network device on a random access channel (RACH) resource, wherein a resource pool to which the RACH resource belongs and / or a preamble set to which the preamble belongs is used for indicating whether an orthogonal cover code (OCC) is used when the terminal device sends the preamble. In this way, on the basis of the resource pool to which the RACH resource belongs, and / or the preamble set to which the preamble belongs used when the terminal device sends the preamble, the network device can determine whether an OCC is used when the terminal device sends the preamble, thereby facilitating receiving the preamble by the network device in a corresponding reception manner, thus facilitating reducing the implementation complexity of receiving the preamble by the network device.

Description

A random access method, device, equipment, chip and storage medium Technical Field

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

[0002] To enhance uplink capacity, the Orthogonal Cover Codes (OCC) scheme has been introduced. For example, when transmitting on the Physical Uplink Shared Channel (PUSCH) and / or Physical Random Access Channel (PRACH), OCC technology can be used to enable multiple terminal devices to reuse the same PUSCH and / or PRACH time-frequency resources for transmission. The PUSCH and / or PRACH transmitted by different terminal devices are distinguished by OCC.

[0003] During random access, message 1 (Msg1, also known as the preamble) and message 3 (Msg3) may use OCC for transmission. For Msg1, because the system may contain both OCC-capable and non-OCC-capable terminal devices, network devices (such as base stations) cannot accurately determine whether OCC was used during the reception of Msg1. Therefore, the network device must attempt to receive Msg1 both without and with OCC. This increases the complexity of receiving Msg1 compared to a solution without OCC.

[0004] Summary of the Invention

[0005] Embodiments of the present application provide a random access method, apparatus, device, chip, and storage medium.

[0006] In a first aspect, an embodiment of the present application provides a random access method applied to a terminal device, the method comprising: sending a preamble code to a network device on a random access channel RACH resource; a resource pool to which the RACH resource belongs and / or a preamble code set to which the preamble code belongs, used to indicate whether an orthogonal cover code OCC is used when the terminal device sends the preamble code.

[0007] In a second aspect, an embodiment of the present application provides a random access method applied to a network device, the method comprising: receiving a preamble from a terminal device on a random access channel RACH resource; a resource pool to which the RACH resource belongs and / or a preamble set to which the preamble belongs, used to indicate whether an orthogonal cover code OCC is used when the terminal device sends the preamble.

[0008] In a third aspect, an embodiment of the present application provides a random access method, applied to a terminal device, the method comprising: sending a preamble code to a network device on a random access channel RACH resource; the resource pool to which the RACH resource belongs and / or the preamble code set to which the preamble code belongs, are used to indicate: whether the terminal device requests to use the OCC to send message 3; or, whether the terminal device has a second capability; the second capability includes: the ability to use the OCC to send a physical uplink shared channel PUSCH for carrying message 3, or the ability to use the OCC to send PUSCH.

[0009] In a fourth aspect, an embodiment of the present application provides a random access method, which is applied to a network device, the method including: receiving a preamble code from a terminal device on a random access channel RACH resource; the resource pool to which the RACH resource belongs and / or the preamble code set to which the preamble code belongs, are used to indicate: whether the terminal device requests to use the OCC to send message 3; or, whether the terminal device has a second capability; the second capability includes: the ability to use the OCC to send a physical uplink shared channel PUSCH for carrying message 3, or the ability to use the OCC to send PUSCH.

[0010] In a fifth aspect, an embodiment of the present application provides a random access device, comprising: a first communication unit configured to send a preamble code to a network device on a random access channel RACH resource; a resource pool to which the RACH resource belongs and / or a preamble code set to which the preamble code belongs, used to indicate whether the device uses an orthogonal cover code OCC when sending the preamble code.

[0011] In a sixth aspect, an embodiment of the present application provides a random access device, comprising: a second communication unit configured to receive a preamble code from a terminal device on a random access channel RACH resource; a resource pool to which the RACH resource belongs and / or a preamble code set to which the preamble code belongs, used to indicate whether an orthogonal cover code OCC is used when the terminal device sends the preamble code.

[0012] In the seventh aspect, an embodiment of the present application provides a random access device, which includes: a third communication unit, configured to send a preamble code to a network device on a random access channel RACH resource; a resource pool to which the RACH resource belongs and / or a preamble code set to which the preamble code belongs, used to indicate: whether the device requests to use OCC to send message 3; or whether the device has a second capability; the second capability includes: the ability to use OCC to send a physical uplink shared channel PUSCH for carrying message 3, or the ability to use OCC to send PUSCH.

[0013] In the eighth aspect, an embodiment of the present application provides a random access device, which includes: a fourth communication unit, configured to receive a preamble code from a terminal device on a random access channel RACH resource; a resource pool to which the RACH resource belongs and / or a preamble code set to which the preamble code belongs, used to indicate: whether the terminal device requests to use the OCC to send message 3; or whether the terminal device has a second capability; the second capability includes: the ability to use the OCC to send a physical uplink shared channel PUSCH for carrying message 3, or the ability to use the OCC to send PUSCH.

[0014] In the ninth aspect, an embodiment of the present application provides a communication device, comprising: a memory for storing a computer program; a processor connected to the memory, for calling and running the computer program from the memory, to implement the method described in any one of the first to fourth aspects; and a transceiver for receiving and sending information during the process of sending and receiving information between other devices.

[0015] In a tenth aspect, embodiments of the present application provide a chip. The chip includes: a processor configured to load and execute a computer program from a memory, causing a device equipped with the chip to execute the method described in any one of aspects 1 to 4; and a transceiver configured to transmit and receive information during the process of transmitting and receiving information to and from the device or chip.

[0016] In an eleventh aspect, an embodiment of the present application provides a computer-readable storage medium for storing a computer program, which enables a computer to execute the method described in any one of the first to fourth aspects.

[0017] In a twelfth aspect, an embodiment of the present application provides a computer program product, comprising computer program instructions, which enable a computer to execute the method described in any one of the first to fourth aspects.

[0018] In a thirteenth aspect, an embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the method described in any one of the first to fourth aspects.

[0019] According to the method of an embodiment of the present application, a terminal device can send a preamble to a network device on a RACH resource. The resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs can be used to indicate whether the terminal device used an OCC when sending the preamble. In this way, the network device can determine whether the terminal device used an OCC when sending the preamble based on the resource pool to which the RACH resource used when the terminal device sent the preamble belongs and / or the preamble set to which the preamble belongs. This facilitates the network device to adopt the corresponding reception method to receive the preamble. For example, if the network device determines that the terminal device used an OCC when sending the preamble, the network device can use the OCC to receive the preamble. For another example, if the network device determines that the terminal device did not use an OCC when sending the preamble, the network device can receive the preamble without using the OCC. This eliminates the need for the network device to attempt to receive the preamble both without and with the OCC, thereby reducing the implementation complexity of the network device's preamble reception. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0021] FIG1 is a schematic diagram of an application scenario of an embodiment of the present application;

[0022] FIG2 is a schematic diagram of a contention-based random access process provided in an embodiment of the present application;

[0023] FIG3 is a schematic diagram of a non-contention-based random access process provided in an embodiment of the present application;

[0024] FIG4 is a flowchart of a random access method according to an embodiment of the present application;

[0025] FIG5 is a second flow diagram of a random access method provided in an embodiment of the present application;

[0026] FIG6 is a schematic diagram of the first structure of a random access device provided in an embodiment of the present application;

[0027] FIG7 is a second schematic diagram of the structure of a random access device provided in an embodiment of the present application;

[0028] FIG8 is a third schematic diagram of the structure of the random access device provided in an embodiment of the present application;

[0029] FIG9 is a fourth schematic diagram of the structure of a random access device provided in an embodiment of the present application;

[0030] FIG10 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0031] FIG11 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0032] FIG12 is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0033] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0034] FIG1 is a schematic diagram of an application scenario of an embodiment of the present application.

[0035] As shown in Figure 1, a communication system 100 may include a terminal device 110 and a network device 120. The network device 120 may communicate with the terminal device 110 via an air interface. The terminal device 110 and the network device 120 support multi-service transmission.

[0036] It should be understood that the embodiments of the present application are only illustrative of the communication system 100, but the embodiments of the present application are not limited thereto. That is, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine-Type Communications (eMTC) system, 5G communication system (also known as New Radio (NR) communication system), 6G communication system, or future communication systems.

[0037] In the communication system 100 shown in Figure 1, the network device 120 may be an access network device that communicates with the terminal device 110. The access network device may provide communication coverage for a specific geographical area and may communicate with the terminal device 110 (eg, UE) located within the coverage area.

[0038] The network device 120 can be an evolved base station (eNB or eNodeB) in a Long Term Evolution (LTE) system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB) in an NR system, or a base station in a 6G system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device 120 can be a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved Public Land Mobile Network (PLMN), etc.

[0039] The terminal device 110 may be any terminal device, including but not limited to a terminal device connected to the network device 120 or other terminal devices by wire or wireless connection.

[0040] For example, the terminal device 110 may refer to an access terminal, user equipment (UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, an IoT device, a satellite handheld terminal, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), 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 5G network, a terminal device in a 6G network, or a terminal device in a future evolution network, etc.

[0041] The terminal device 110 can be used for device-to-device (D2D) communication.

[0042] The communication system 100 may also include a core network device 130 that communicates with the network device 120. The core network device 130 may be a 5G core network (5G Core, 5GC) device, such as an Access and Mobility Management Function (AMF), an Authentication Server Function (AUSF), a User Plane Function (UPF), or a Session Management Function (SMF). In some embodiments, the core network device 130 may also be an Evolved Packet Core (EPC) device of an LTE network, such as a Session Management Function + Core Packet Gateway (SMF+PGW-C) device. It should be understood that SMF+PGW-C can simultaneously implement the functions that can be implemented by SMF and PGW-C. During the network evolution process, the above-mentioned core network device may also be called other names, or a new network entity may be formed by dividing the functions of the core network, which is not limited in the embodiments of the present application.

[0043] The functional units in the communication system 100 may also establish connections and implement communication via next generation (NG) network interfaces.

[0044] For example, the terminal device establishes an air interface connection with the access network device through the NR interface for transmitting user plane data and control plane signaling; the terminal device can establish a control plane signaling connection with the AMF through the NG interface 1 (referred to as N1); the access network device, such as the next generation wireless access base station (gNB), can establish a user plane data connection with the UPF through the NG interface 3 (referred to as N3); the access network device can establish a control plane signaling connection with the AMF through the NG interface 2 (referred to as N2); the UPF can establish a control plane signaling connection with the SMF through the NG interface 4 (referred to as N4); the UPF can exchange user plane data with the data network through the NG interface 6 (referred to as N6); the AMF can establish a control plane signaling connection with the SMF through the NG interface 11 (referred to as N11); the SMF can establish a control plane signaling connection with the PCF through the NG interface 7 (referred to as N7).

[0045] Figure 1 exemplarily shows a network device, a core network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and the coverage area of ​​each network device may include other numbers of terminal devices, which is not limited in this embodiment of the present application.

[0046] It should be noted that Figure 1 is merely an example of a system applicable to this application. Of course, the methods described in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" herein simply describes an association relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the associated objects are in an "or" relationship. It should also 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 relationship. For example, "A indicates B" can mean that A directly indicates B, for example, B can obtain information through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can obtain information through C; or it can mean that A and B have an association relationship. It should also be understood that the "correspondence" mentioned in the embodiments of this application can mean that there is a direct or indirect correspondence between two objects, or that there is an association relationship between the two objects, or a relationship between an indicator and the indicated, a configuration and the configured, and so on. It should also be understood that the “predefined” or “predefined rules” mentioned in the embodiments of the present application can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminal devices and network devices), and the present application does not limit its specific implementation method. For example, predefined can refer to what is defined in the protocol. It should also be understood that in the embodiments of the present application, the “protocol” may refer to a standard protocol in the field of communications, such as LTE protocols, NR protocols, and related protocols used in future communication systems, and the present application does not limit this.

[0047] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0048] 1. Triggering of random access process

[0049] In LTE and NR, the random access process can be triggered by the following events:

[0050] 1) Establishing a wireless connection when the UE initially accesses: The UE changes from the RRC_IDLE state to the RRC_CONNECTED state;

[0051] 2) RRC connection reestablishment process: used by the UE to reestablish the wireless connection after a radio link failure;

[0052] 3) Handover: The UE needs to establish uplink synchronization with the new cell;

[0053] 4) In the RRC_CONNECTED state, downlink (DL) data arrives, and the UL is in an out-of-sync state;

[0054] 5) In the RRC_CONNECTED state, uplink (UL) data arrives, and the UL is out of synchronization or there are no Physical Uplink Control Channel (PUCCH) resources for sending a Scheduling Request (SR);

[0055] 6) SR failure;

[0056] 7) The UE receives a synchronization reconfiguration request from the Radio Resource Control (RRC).

[0057] 2. Random access method

[0058] Currently, two random access modes are mainly supported, namely contention-based random access mode and non-contention-based random access mode.

[0059] FIG2 is a schematic diagram of a contention-based random access process provided by an embodiment of the present application. As shown in FIG2 , the contention-based random access process may include the following steps:

[0060] S201, the terminal device sends Msg1 to the network device.

[0061] Msg1 includes a random access preamble (RAP), or a preamble.

[0062] The terminal device can select a Physical Random Access Channel (PRACH) resource and send the selected preamble on the selected PRACH. Based on the preamble, the network device can estimate the uplink timing and the grant size required for the terminal device to transmit Msg3.

[0063] S202: The network device sends Msg2 to the terminal device.

[0064] Msg2 includes a Random Access Response (Random Access Response, RAR).

[0065] After the terminal device sends Msg1, it can open a random access response time window (ra-ResponseWindow) and monitor the physical downlink control channel (PDCCH) scrambled by the random access radio network temporary identifier (RA-RNTI) within the random access response time window. In LTE, the calculation formula of RA-RNTI is shown in formula (1): RA-RNTI = 1 + t_id + 10 * f_id (1);

[0066] Among them, t_id (0≤t_id<10) is the index of the first subframe transmitted by PRACH, f_id (0≤f_id<6) is the frequency domain index corresponding to PRACH in the subframe, and PRACH resources are numbered in ascending order in the frequency domain.

[0067] For an enhanced machine type communication (eMTC) terminal device, the calculation formula of RA-RNTI is shown in formula (2): RA-RNTI=1+t_id+10*f_id+60*(SFN_id mod(Wmax / 10)) (2);

[0068] Where t_id (0≤t_id<10) is the index of the first subframe transmitted by PRACH, and f_id (0≤f_id<6) is the frequency domain index corresponding to the PRACH in that subframe. PRACH resources are numbered sequentially in the frequency domain from low to high. SFN_id is the index of the first system frame number (SFN) transmitted by PRACH, and Wmax is the maximum RAR window length supported by eMTC, which is 400 subframes.

[0069] For Narrow Band Internet of Things (NB-IoT) terminal devices, the calculation formula of RA-RNTI is shown in formula (3): RA-RNTI = 1 + floor (SFN_id / 4) + 256 * carrier_id (3);

[0070] Where SFN_id is the index of the first SFN transmitted by PRACH, and carrier_id is the index of the UL carrier corresponding to the PRACH transmission. The carrier_id corresponding to the anchor carrier is 0.

[0071] For NB-IoT terminal devices in time division duplexing (TDD) mode, the calculation formula of RA-RNTI is shown in formula (4): RA-RNTI = 1 + floor (SFN_id / 4) + 256 * (H-SFN mod 2) (4);

[0072] SFN_id is the index of the first SFN transmitted by the PRACH, and H-SFN is the first hyper system frame number (Hyper System Frame Number, H-SFN) transmitted by the PRACH.

[0073] It can be seen from the above RA-RNTI calculation formula that RA-RNTI is related to the PRACH time-frequency resources used by the terminal device to send Msg1.

[0074] After the terminal device successfully receives the RA-RNTI-scrambled PDCCH, it can obtain the Physical Downlink Shared Channel (PDSCH) scheduled by the PDCCH, which includes the RAR. The RAR specifically contains the following information:

[0075] The RAR subheader contains a backoff indicator (BI), which is used to indicate the backoff time for retransmitting Msg1.

[0076] Random access preamble identifier (RAP Identify, RAPID) in RAR: the preamble index received in the network response;

[0077] The RAR payload contains a tag, which is used to adjust the uplink timing.

[0078] Uplink grant (UL grant): used to schedule uplink resource indication of Msg3;

[0079] Temporary cell radio network temporary identifier (Temporary C-RNTI, TC-RNTI): used to scramble the PDCCH of Msg4 (initial access).

[0080] If the terminal device receives a PDCCH scrambled by RAR-RNTI, and the RAR contains the preamble index sent by itself, the terminal device considers that the random access response has been successfully received.

[0081] For non-contention-based random access, the random access process ends after the terminal device successfully receives Msg2. For contention-based random access, after the terminal device successfully receives Msg2, it needs to continue to transmit Msg3 and receive Msg4.

[0082] S203, the terminal device sends Msg3 (Scheduled Transmission) to the network device.

[0083] The terminal device can transmit Msg3 on resources scheduled by the network device. Msg3 is primarily used to inform the network device of the event that triggered the random access process. For example, if it is an initial random access process, the Msg3 will carry the terminal device's ID and establishment cause; if it is an RRC reestablishment, it will carry the connected terminal device ID and establishment cause.

[0084] S204: The network device sends Msg4 (Contention Resolution) to the terminal device.

[0085] Msg4 has two functions, one is to resolve contention conflicts, and the second is for the network device to transmit RRC configuration messages to the terminal device. There are two ways to resolve contention conflicts: one is that if the terminal device carries the Cell Radio Network Temporary Identifier (C-RNTI) in Msg3, Msg4 is scheduled with the PDCCH scrambled by the C-RNTI. The other is that if the terminal device does not carry the C-RNTI in Msg3, such as the initial access, Msg4 is scheduled with the PDCCH scrambled by the TC-RNTI. The conflict is resolved by the terminal device receiving the PDSCH of Msg4, which is achieved by matching the Common Control Channel Service Data Unit (CCCH SDU) in the PDSCH.

[0086] FIG3 is a schematic diagram of a non-contention-based random access process provided by an embodiment of the present application. As shown in FIG3 , the non-contention-based random access process may include the following steps:

[0087] S301: The network device sends a random access preamble assignment (RA Preamble assignment) message to the terminal device.

[0088] S302: The terminal device sends Msg1 to the network device.

[0089] Msg1 includes a random access preamble, or preamble. The terminal device can send the preamble on a PRACH resource specified by the network device. Based on the preamble, the network device can estimate the uplink timing and grant size required for the terminal device to transmit Msg3.

[0090] S303: The network device sends Msg2 to the terminal device.

[0091] This step can refer to the aforementioned step S202 and will not be repeated here.

[0092] As can be seen from the above random access process, the main purpose of random access is to achieve uplink synchronization between the terminal device and the cell. During the random access process, the network device can determine the time when the terminal device transmits the preamble based on the time-frequency resources of the Random Access Channel (RACH) used by the preamble from the terminal device. Based on the transmission and reception times of the preamble, the network device determines the initial timing advance (TA) of the terminal device and notifies the terminal device through the RAR.

[0093] The above briefly explains the relevant technologies / terms involved in this application, which will not be repeated in the following embodiments.

[0094] To enhance uplink capacity, the OCC solution was introduced. For example, when transmitting PUSCH and / or PRACH, OCC technology can be used to enable multiple terminal devices to reuse the same PUSCH and / or PRACH time-frequency resources for transmission. The PUSCH and / or PRACH transmitted by different terminal devices can be distinguished by OCC.

[0095] After the introduction of OCC, the transmission of Message 1 (i.e., the preamble) and Message 3 during the random access process may use OCC. For Message 1, because the system may contain both OCC-capable and non-OCC-capable terminal devices, the network device cannot accurately determine whether OCC was used during the reception of Message 1. Therefore, the network device needs to attempt to receive Message 1 both without and with OCC. This increases the implementation complexity of Message 1 reception for the network device compared to a solution without OCC.

[0096] In view of this, the present application provides a random access method, apparatus, device, chip, and storage medium. In this method, a terminal device can send a preamble to a network device on a RACH resource. The resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs can be used to indicate whether the terminal device used an OCC when sending the preamble.

[0097] In this way, the network device can learn whether the terminal device used OCC when sending the preamble based on the resource pool to which the RACH resource used when the terminal device sent the preamble belongs, and / or the preamble set to which the preamble belongs, thereby facilitating the network device to adopt the corresponding receiving method to receive the preamble. For example, if the network device learns that the terminal device used OCC when sending the preamble, then the network device can use OCC to receive the preamble; for another example, if the network device learns that the terminal device did not use OCC when sending the preamble, then the network device can receive the preamble without using OCC. In this way, the network device does not need to try to receive the preamble with and without using OCC, thereby reducing the implementation complexity of the network device receiving the preamble.

[0098] It should be noted that the "resources" in the embodiments of the present application may refer to "time-frequency resources" for example, that is, the "resources" in the embodiments of the present application may also be replaced by "time-frequency resources"; accordingly, the "resource pool" in the embodiments of the present application may also be replaced by "time-frequency resource pool".

[0099] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0100] FIG4 is a flow chart of a random access method according to an embodiment of the present application. As shown in FIG4 , the method may include the following steps:

[0101] S401, the terminal device sends a preamble to the network device on the RACH resource; the resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs are used to indicate whether the terminal device uses OCC when sending the preamble.

[0102] In this embodiment, the terminal device may send a preamble to the network device on a RACH resource, and the network device may receive the preamble from the terminal device on the RACH resource. The resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs may be used to indicate whether the terminal device used an OCC when sending the preamble.

[0103] The resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs are used to indicate whether the terminal device used the OCC when sending the preamble. This can also be understood as indicating whether the terminal device used the OCC when sending the preamble. That is, the network device can determine whether the terminal device used the OCC when sending the preamble based on the RACH resource and / or the preamble used by the terminal device when sending the preamble.

[0104] In some embodiments, when the RACH resource belongs to the first RACH resource pool and / or the preamble belongs to the first preamble set, the terminal device uses OCC when sending the preamble.

[0105] In one example, when the RACH resource belongs to the first RACH resource pool, the terminal device uses an OCC when sending the preamble. That is, if the RACH resource belongs to the first RACH resource pool, it indicates that the terminal device used an OCC when sending the preamble. Alternatively, the information that "the RACH resource belongs to the first RACH resource pool" can be used to indicate that the terminal device used an OCC when sending the preamble. In this case, if the network device identifies that the RACH resource used by the terminal device to send the preamble belongs to the first RACH resource pool, it can be determined that the terminal device used an OCC when sending the preamble.

[0106] In another example, when the preamble belongs to the first preamble set, the terminal device uses an OCC when sending the preamble. In other words, if the preamble belongs to the first preamble set, it means that the terminal device used an OCC when sending the preamble. In other words, the information that "the preamble belongs to the first preamble set" can be used to indicate that the terminal device used an OCC when sending the preamble. In this case, if the network device recognizes that the preamble sent by the terminal device belongs to the first preamble set, it can be determined that the terminal device used an OCC when sending the preamble.

[0107] As another example, when the RACH resource belongs to the first RACH resource pool and the preamble belongs to the first preamble set, the terminal device uses the OCC when sending the preamble. That is, if the RACH resource belongs to the first RACH resource pool and the preamble belongs to the first preamble set, it means that the terminal device used the OCC when sending the preamble, or in other words, the information "the RACH resource belongs to the first RACH resource pool and the preamble belongs to the first preamble set" can be used to indicate that the terminal device used the OCC when sending the preamble. In this case, if the network device recognizes that the RACH resource used by the terminal device to send the preamble belongs to the first RACH resource pool and the preamble belongs to the first preamble set, it can be determined that the terminal device used the OCC when sending the preamble.

[0108] In some embodiments, when the RACH resource belongs to the second RACH resource pool and / or the preamble belongs to the second preamble set, the terminal device does not use OCC when sending the preamble.

[0109] In one example, when the RACH resource belongs to the second RACH resource pool, the terminal device does not use an OCC when sending the preamble. That is, if the RACH resource belongs to the second RACH resource pool, this indicates that the terminal device did not use an OCC when sending the preamble. Alternatively, the information that "the RACH resource belongs to the second RACH resource pool" can be used to indicate that the terminal device did not use an OCC when sending the preamble. In this case, if the network device identifies that the RACH resource used by the terminal device to send the preamble belongs to the second RACH resource pool, it can determine that the terminal device did not use an OCC when sending the preamble.

[0110] In another example, if the preamble belongs to the second preamble set, the terminal device does not use an OCC when sending the preamble. In other words, if the preamble belongs to the second preamble set, it means that the terminal device does not use an OCC when sending the preamble. In other words, the information that "the preamble belongs to the second preamble set" can be used to indicate that the terminal device used an OCC when sending the preamble. In this case, if the network device recognizes that the preamble sent by the terminal device belongs to the second preamble set, it can be determined that the terminal device did not use an OCC when sending the preamble.

[0111] As another example, when the RACH resource belongs to the second RACH resource pool and the preamble belongs to the second preamble set, the terminal device does not use the OCC when sending the preamble. That is, if the RACH resource belongs to the second RACH resource pool and the preamble belongs to the second preamble set, it means that the terminal device does not use the OCC when sending the preamble, or in other words, the information that "the RACH resource belongs to the second RACH resource pool and the preamble belongs to the second preamble set" can be used to indicate that the terminal device does not use the OCC when sending the preamble. In this case, if the network device recognizes that the RACH resource used by the terminal device when sending the preamble belongs to the second RACH resource pool and the preamble belongs to the second preamble set, it can be determined that the terminal device does not use the OCC when sending the preamble.

[0112] According to the method of this embodiment, the network device can obtain whether the terminal device uses OCC when sending the preamble code based on the resource pool to which the RACH resource used when the terminal device sends the preamble code belongs, and / or the preamble code set to which the preamble code belongs. This is conducive to the network device adopting the corresponding receiving method to receive the preamble code, thereby helping to reduce the implementation complexity of the network device receiving the preamble code.

[0113] In some embodiments, the selection of the RACH resource and / or the preamble is related to whether the terminal device uses OCC to send the preamble. In other words, the terminal device may select the corresponding RACH resource and / or preamble based on whether it uses (e.g., whether it can use, or whether it decides to use) OCC to send the preamble.

[0114] In some embodiments, when the terminal device uses OCC to send a preamble, the RACH resource is selected from a first RACH resource pool, and / or the preamble is selected from a first preamble set, and the terminal device has a first capability.

[0115] The first capability is the ability to use OCC to send PRACH, which can be used to carry preamble codes. The terminal device has the first capability, which can also be understood as the terminal device having the ability to use OCC to send PRACH, or the terminal device having the ability to use OCC to send preamble codes (carried by PRACH).

[0116] In this embodiment, when the terminal device has the first capability, if the terminal device uses (such as decides to use / plans to use) OCC to send a preamble code, then the terminal device can select a RACH resource for sending the preamble code from the first RACH resource pool, and / or can select the preamble code to be sent from the first preamble code set.

[0117] In one example, if a terminal device has the first capability and uses (e.g., decides to use / plans to use) an OCC to send a preamble, the terminal device may select a RACH resource from the first RACH resource pool for sending the preamble. Consequently, the terminal device may send the preamble on the RACH resource selected from the first RACH resource pool. In this way, if the network device identifies that the RACH resource used by the terminal device to send the preamble belongs to the first RACH resource pool, the network device may determine that the terminal device used the OCC when sending the preamble.

[0118] As another example, if the terminal device has the first capability and uses (e.g., decides to use / plans to use) an OCC to send a preamble, the preamble to be sent may be selected from the first preamble set. Consequently, the terminal device may send the preamble selected from the first preamble set on a RACH resource. Thus, if the network device identifies that the preamble sent by the terminal device belongs to the first preamble set, it may determine that the terminal device used the OCC when sending the preamble.

[0119] As another example, when a terminal device has the first capability, if the terminal device uses (e.g., decides to use / plans to use) an OCC to send a preamble, the terminal device may select a RACH resource for sending the preamble from the first RACH resource pool, and may select the preamble to be sent from the first preamble set. Thus, the terminal device may send the preamble selected from the first preamble set on the RACH resource selected from the first RACH resource pool. Thus, if the network device identifies that the RACH resource used by the terminal device to send the preamble belongs to the first RACH resource pool, and that the preamble belongs to the first preamble set, it may be determined that the terminal device used the OCC when sending the preamble.

[0120] In some embodiments, when the terminal device does not use OCC to send a preamble, the RACH resource is determined from a second RACH resource pool, and / or the preamble is selected from a second preamble set, and the terminal device has or does not have the first capability.

[0121] In some embodiments, the case where the terminal device does not use OCC to send the preamble may include, for example, the following case A, case B, and case C. That is, if the following case A, case B, or case C is met, it can be considered that the terminal device does not use OCC to send the preamble.

[0122] Case A: The terminal device does not have the first capability, that is, the terminal device does not have the capability to use OCC to send PRACH, or in other words, the terminal device does not have the capability to use OCC to send a preamble (carried by PRACH).

[0123] Case B: The terminal device has the first capability, but the terminal device decides / plans to send the preamble without using OCC.

[0124] Case C: The network device is not configured with a RACH resource pool that can be used to transmit PRACH when using OCC. For example, the network device is configured with the second RACH resource pool but not the first RACH resource pool. RACH resources in the first RACH resource pool are used to transmit PRACH when using OCC, while RACH resources in the second RACH resource pool are used to transmit PRACH when not using OCC.

[0125] In this embodiment, if the terminal device does not use OCC to send the preamble, then the terminal device may select a RACH resource for sending the preamble from the second RACH resource pool and / or may select the preamble to be sent from the second preamble set.

[0126] For example, if the terminal device does not use OCC to send a preamble, it can select a RACH resource from the second RACH resource pool for sending the preamble. The terminal device can then send the preamble on the RACH resource selected from the second RACH resource pool. In this way, if the network device identifies that the RACH resource used by the terminal device to send the preamble belongs to the second RACH resource pool, it can determine that the terminal device did not use OCC when sending the preamble.

[0127] As another example, if the terminal device does not use OCC to send a preamble, the preamble to be sent may be selected from the second preamble set. Consequently, the terminal device may send the preamble selected from the second preamble set on the RACH resource. In this way, if the network device identifies that the preamble sent by the terminal device belongs to the second preamble set, it can determine that the terminal device did not use OCC when sending the preamble.

[0128] As another example, if the terminal device does not use OCC to send a preamble, it may select a RACH resource for sending the preamble from the second RACH resource pool and select the preamble to be sent from the second preamble set. Consequently, the terminal device may send a preamble selected from the second preamble set on the RACH resource selected from the second RACH resource pool. In this way, if the network device recognizes that the RACH resource used by the terminal device to send a preamble belongs to the second RACH resource pool and that the preamble belongs to the second preamble set, it may determine that the terminal device did not use OCC when sending the preamble.

[0129] In some embodiments, if the network device determines that the terminal device uses OCC when sending a preamble, the network device may use OCC to receive the preamble, or in other words, the network device may use an OCC-based method to receive the preamble; if the network device determines that the terminal device does not use OCC when sending a preamble, the network device may use OCC to receive the preamble, or in other words, the network device may use an OCC-free method to receive the preamble. In this way, the network device does not need to try to receive the preamble using both methods without and with OCC, thereby reducing the implementation complexity of the network device receiving the preamble.

[0130] In some embodiments, the resource pool to which the RACH resource (the RACH resource used when the terminal device sends a preamble code) belongs and / or the preamble code set to which the preamble code (the preamble code sent by the terminal device) belongs are also used to indicate: whether the terminal device requests to use OCC to send message 3; or whether the terminal device has the second capability.

[0131] The resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs are further used to indicate whether the terminal device requests to use OCC to send message 3, or whether the terminal device has the second capability. This can also be understood as indicating whether the RACH resource and / or the preamble are further used to indicate whether the terminal device requests to use OCC to send message 3, or whether the terminal device has the second capability. That is, the network device can determine whether the terminal device requests to use OCC to send message 3, or whether the terminal device has the second capability, based on the RACH resource and / or the preamble used by the terminal device when sending the preamble.

[0132] The second capability includes: the capability of using the OCC to send a PUSCH for carrying message 3, or the capability of using the OCC to send a PUSCH.

[0133] In one example, the second capability includes the ability to use OCC to send a PUSCH for carrying message 3. In this case, if the terminal device has the second capability, it means that the terminal device can use OCC to send a PUSCH for carrying message 3, that is, the terminal device has the ability to use OCC to send a PUSCH for carrying message 3.

[0134] In another example, the second capability includes the ability to use OCC to send PUSCH. In this case, if the terminal device has the second capability, it means that the terminal device can use OCC to send PUSCH, that is, the terminal device has the ability to use OCC to send PUSCH. In this case, the terminal device not only has the ability to use OCC to send PUSCH carrying Message 3, but also has the ability to use OCC to send PUSCH carrying other data / messages.

[0135] In some embodiments, when the RACH resource belongs to the first RACH resource pool and / or the preamble belongs to the first preamble set, the terminal device requests to use OCC to send message 3, or the terminal device has the second capability.

[0136] As an example, when the RACH resource belongs to the first RACH resource pool, the terminal device requests to use OCC to send message 3, or the terminal device has the second capability. That is to say, if the RACH resource belongs to the first RACH resource pool, it means that the terminal device requests to use OCC to send message 3, or it means that the terminal device has the second capability. In other words, the information that "the RACH resource belongs to the first RACH resource pool" can be used to indicate that the terminal device requests to use OCC to send message 3, or it can be used to indicate that the terminal device has the second capability. In this case, if the network device recognizes that the RACH resource used by the terminal device to send the preamble belongs to the first RACH resource pool, it can be determined that the terminal device requests to use OCC to send message 3, or it can be determined that the terminal device has the second capability.

[0137] As another example, when the preamble belongs to the first preamble set, the terminal device requests to use OCC to send message 3, or the terminal device has the second capability. That is, if the preamble belongs to the first preamble set, it indicates that the terminal device requests to use OCC to send message 3, or that the terminal device has the second capability. In other words, the information that "the preamble belongs to the first preamble set" can be used to indicate that the terminal device requests to use OCC to send message 3, or that the terminal device has the second capability. In this case, if the network device recognizes that the preamble sent by the terminal device belongs to the first preamble set, it can be determined that the terminal device requests to use OCC to send message 3, or that the terminal device has the second capability.

[0138] As another example, when the RACH resource belongs to the first RACH resource pool and the preamble belongs to the first preamble set, the terminal device requests to use OCC to send message 3, or the terminal device has the second capability. That is to say, if the RACH resource belongs to the first RACH resource pool and the preamble belongs to the first preamble set, it means that the terminal device requests to use OCC to send message 3, or it means that the terminal device has the second capability. In other words, the information that "the RACH resource belongs to the first RACH resource pool and the preamble belongs to the first preamble set" can be used to indicate that the terminal device requests to use OCC to send message 3, or it can be used to indicate that the terminal device has the second capability. In this case, if the network device recognizes that the RACH resource used by the terminal device to send the preamble belongs to the first RACH resource pool, and the preamble belongs to the first preamble set, it can be determined that the terminal device requests to use OCC to send message 3, or it can be determined that the terminal device has the second capability.

[0139] In some embodiments, when the RACH resource belongs to the second RACH resource pool and / or the preamble belongs to the second preamble set, the terminal device does not request to use OCC to send message 3, or the terminal device does not have the second capability. In some scenarios, the terminal device does not request to use OCC to send message 3, which can also be understood as the terminal device requesting not to use OCC to send message 3. When the terminal device does not request to use OCC to send message 3, the terminal device may or may not have the second capability.

[0140] As an example, when the RACH resource belongs to the second RACH resource pool, the terminal device does not request to use OCC to send message 3, or the terminal device does not have the second capability. That is to say, if the RACH resource belongs to the second RACH resource pool, it means that the terminal device does not request to use OCC to send message 3, or it means that the terminal device does not have the second capability, or in other words, the information that "the RACH resource belongs to the second RACH resource pool" can be used to indicate that the terminal device does not request to use OCC to send message 3, or it can be used to indicate that the terminal device does not have the second capability. In this case, if the network device recognizes that the RACH resource used by the terminal device to send the preamble belongs to the second RACH resource pool, it can be determined that the terminal device does not request to use OCC to send message 3, or it can be determined that the terminal device does not have the second capability.

[0141] As another example, when the preamble belongs to the second preamble set, the terminal device does not request to use OCC to send message 3, or the terminal device does not have the second capability. That is to say, if the preamble belongs to the second preamble set, it means that the terminal device does not request to use OCC to send message 3, or it means that the terminal device does not have the second capability. In other words, the information that "the preamble belongs to the second preamble set" can be used to indicate that the terminal device does not request to use OCC to send message 3, or it can be used to indicate that the terminal device does not have the second capability. In this case, if the network device recognizes that the preamble sent by the terminal device belongs to the second preamble set, it can be determined that the terminal device does not request to use OCC to send message 3, or it can be determined that the terminal device does not have the second capability.

[0142] As another example, when the RACH resource belongs to the second RACH resource pool and the preamble belongs to the second preamble set, the terminal device does not request to use OCC to send message 3, or the terminal device does not have the second capability. That is to say, if the RACH resource belongs to the second RACH resource pool and the preamble belongs to the second preamble set, it means that the terminal device does not request to use OCC to send message 3, or it means that the terminal device does not have the second capability. In other words, the information that "the RACH resource belongs to the second RACH resource pool and the preamble belongs to the second preamble set" can be used to indicate that the terminal device does not request to use OCC to send message 3, or it can be used to indicate that the terminal device does not have the second capability. In this case, if the network device recognizes that the RACH resource used by the terminal device to send the preamble belongs to the second RACH resource pool, and the preamble belongs to the second preamble set, it can be determined that the terminal device does not request to use OCC to send message 3, or it can be determined that the terminal device does not have the second capability.

[0143] In some embodiments, the method may further include: the network device sending a random access response to the terminal device, and accordingly, the terminal device may receive the random access response from the network device.

[0144] In some embodiments, when the terminal device requests to use OCC to send message 3, or when the terminal device has the second capability, the random access response can be used to indicate: a first PUSCH resource and a first OCC; the first OCC is used by the terminal device to send message 3 to the network device on the first PUSCH resource.

[0145] That is to say, if the network device determines that the terminal device requests to use OCC to send message 3, or determines that the terminal device has the second capability, then the network device can carry the first PUSCH resource and the first OCC in the random access response sent to the terminal device, so that the terminal device can use the first OCC on the first PUSCH resource to send message 3 to the network device.

[0146] In some embodiments, when the terminal device does not request to use OCC to send message 3, or the terminal device does not have the second capability, the random access response can be used to indicate: a second PUSCH resource; the second PUSCH resource is used by the terminal device to send message 3 to the network device without using OCC.

[0147] That is to say, if the network device determines that the terminal device has not requested to use OCC to send message 3, or determines that the terminal device does not have the second capability, then the network device may carry a second PUSCH resource in the random access response sent to the terminal device, so that the terminal device can send message 3 to the network device on the second PUSCH, and does not use OCC when sending message 3.

[0148] According to the method of this embodiment, the network device may determine whether the terminal device requests to use OCC to send message 3 or whether the terminal device has the second capability based on the resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs. In this way, the network device may determine a scheduling policy for message 3 for the terminal device based on whether the terminal device requests to use OCC to send message 3 or whether it has the second capability. For example, if the network device determines that the terminal device requests to use OCC to send message 3 or has the second capability, it can determine that the scheduling strategy for message 3 of the terminal device is: use OCC to transmit the PUSCH carrying message 3. At this time, the network device can carry the PUSCH resources (first PUSCH resources) and OCC (first OCC) used for the terminal device to send message 3 in the random access response; if the network device determines that the terminal device does not request to use OCC to send message 3 or does not have the second capability, it can determine that the scheduling strategy for message 3 of the terminal device is: transmit the PUSCH carrying message 3 without using OCC. At this time, the network device can carry the PUSCH resources (second PUSCH resources) used for the terminal device to send message 3 in the random access response without carrying OCC.

[0149] In some embodiments, the selection of the RACH resource and / or the preamble is related to whether the terminal device requests to use OCC to send message 3, or whether the terminal device has the second capability. That is, the terminal device may select the corresponding RACH resource and / or preamble based on whether it requests to use OCC to send message 3; alternatively, the terminal device may select the corresponding RACH resource and / or preamble based on whether it has the second capability.

[0150] In some embodiments, when the terminal device requests to use OCC to send message 3, or the terminal device has the second capability, the RACH resource is selected from the first RACH resource pool, and / or the preamble code is selected from the first preamble code set.

[0151] That is, if the terminal device requests to use OCC to send message 3, or the terminal device has the second capability, then the terminal device can select RACH resources for sending preamble codes from the first RACH resource pool, and / or can select the preamble codes to be sent from the first preamble code set.

[0152] In one example, if the terminal device requests to use OCC to send message 3, or if the terminal device has the second capability, a RACH resource for sending a preamble may be selected from the first RACH resource pool and the preamble may be sent on the RACH resource. Thus, if the network device identifies that the RACH resource used by the terminal device to send the preamble belongs to the first RACH resource pool, it may determine that the terminal device requests to use OCC to send message 3, or that the terminal device has the second capability.

[0153] In another example, if the terminal device requests to use OCC to send message 3, or if the terminal device has the second capability, the preamble to be sent may be selected from the first preamble set and may be sent on the RACH resource. In this way, if the network device recognizes that the preamble sent by the terminal device belongs to the first preamble set, it may be determined that the terminal device requests to use OCC to send message 3, or that the terminal device has the second capability.

[0154] As another example, if the terminal device requests to use OCC to send message 3, or if the terminal device has the second capability, a RACH resource for sending a preamble may be selected from the first RACH resource pool, and the preamble to be sent may be selected from the first preamble set. The terminal device may send the preamble selected from the first preamble set on the RACH resource selected from the first RACH resource pool. In this way, if the network device recognizes that the RACH resource used by the terminal device to send the preamble belongs to the first RACH resource pool, and that the preamble belongs to the first preamble set, it may be determined that the terminal device requests to use OCC to send message 3, or that the terminal device has the second capability.

[0155] In some embodiments, if the terminal device does not request to use OCC to send message 3, or if the terminal device does not have the second capability, the RACH resource is determined from the second RACH resource pool, and / or the preamble is selected from the second preamble set. In some scenarios, if the terminal device does not request to use OCC to send message 3, it can also be understood that the terminal device requests not to use OCC to send message 3. If the terminal device does not request to use OCC to send message 3, the terminal device may or may not have the second capability.

[0156] In one example, if the terminal device does not request to use OCC to send Message 3, or if the terminal device does not possess the second capability, a RACH resource for sending a preamble may be selected from the second RACH resource pool, and the preamble may be sent on the RACH resource. Thus, if the network device identifies that the RACH resource used by the terminal device to send the preamble belongs to the second RACH resource pool, it may be determined that the terminal device did not request to use OCC to send Message 3, or that the terminal device does not possess the second capability.

[0157] In another example, if the terminal device does not request to use OCC to send Message 3, or the terminal device does not have the second capability, a preamble to be sent may be selected from the second preamble set and sent on the RACH resource. In this way, if the network device recognizes that the preamble sent by the terminal device belongs to the second preamble set, it can be determined that the terminal device did not request to use OCC to send Message 3, or that the terminal device does not have the second capability.

[0158] As another example, if the terminal device does not request to use OCC to send Message 3, or if the terminal device does not possess the second capability, a RACH resource for sending a preamble may be selected from the second RACH resource pool, and the preamble to be sent may be selected from the second preamble set. The terminal device may send a preamble selected from the second preamble set on the RACH resource selected from the second RACH resource pool. In this way, if the network device recognizes that the RACH resource used by the terminal device to send the preamble belongs to the second RACH resource pool, and that the preamble belongs to the second preamble set, it may be determined that the terminal device did not request to use OCC to send Message 3, or that the terminal device does not possess the second capability.

[0159] In some embodiments, one or more of the first RACH resource pool, the second RACH resource pool, the first preamble set, and the second preamble set may be included in configuration information sent by the network device. In other words, one or more of the first RACH resource pool, the second RACH resource pool, the first preamble set, and the second preamble set may be configured by the network device.

[0160] Exemplarily, the network device may send configuration information to the terminal device, and correspondingly, the terminal device may receive the configuration information from the network device. The configuration information may include one or more of the following, or in other words, the configuration information may be used to configure one or more of the following: a first RACH resource pool, a second RACH resource pool, a first preamble set, and a second preamble set.

[0161] In some embodiments, the RACH resources in the first RACH resource pool are used to transmit PRACH when using OCC; the RACH resources in the second RACH resource pool are used to transmit PRACH when not using OCC, and PRACH is used to carry the preamble. That is, if the RACH resource selected by the terminal device belongs to the first RACH resource pool, the terminal device can use OCC to transmit PRACH on the RACH resource; if the RACH resource selected by the terminal device belongs to the second RACH resource pool, the terminal device can transmit PRACH on the RACH resource without using OCC. In some embodiments, the RACH resources in the first RACH resource pool and the RACH resources in the second RACH resource pool do not overlap.

[0162] In some embodiments, preambles in the first preamble set are transmitted using an OCC, while preambles in the second preamble set are transmitted without an OCC. That is, if a preamble selected by a terminal device belongs to the first preamble set, the terminal device may transmit the preamble using an OCC; if a preamble selected by the terminal device belongs to the second preamble set, the terminal device may transmit the preamble without an OCC. In some embodiments, the preambles in the first preamble set and the preambles in the second preamble set do not overlap.

[0163] In some embodiments, when the configuration information does not include the second RACH resource pool and / or the second preamble set, the cell corresponding to the network device does not allow access by terminal devices that do not have the first capability, where the first capability is the ability to use the OCC to send a PRACH, where the PRACH is used to carry the preamble.

[0164] That is, if the network device is not configured with the second RACH resource pool and / or the second preamble code set, the terminal device that does not have the first capability may consider that the current cell (the cell corresponding to the network device) does not allow the terminal device to access.

[0165] In some embodiments, the configuration information also includes an OCC set (or, the configuration information is further used to configure the OCC set), and the OCC set can be used by the terminal device to select the OCC to use when the OCC is used to send a preamble. For example, if the terminal device uses the OCC to send a preamble, the terminal device can select an OCC from the OCC set, and then the terminal device can use the OCC selected from the OCC set to send the preamble on the RACH resource.

[0166] According to the method of this embodiment, the network device may be configured with different RACH resource pools and / or preamble sets. The terminal device may select a RACH resource for sending a preamble from the corresponding RACH resource pool and / or select the preamble to be sent from the corresponding preamble set, depending on whether the terminal device uses OCC to send a preamble. For example, if the terminal device uses OCC to send a preamble, the RACH resource for sending the preamble may be selected from the first RACH resource pool and / or the preamble to be sent may be selected from the first preamble set. If the terminal device does not use OCC to send a preamble, the RACH resource for sending the preamble may be selected from the second RACH resource pool and / or the preamble to be sent may be selected from the second preamble set. In this way, the network device can know whether the terminal device uses OCC when sending the preamble code based on the resource pool to which the RACH resource used when the terminal device sends the preamble code belongs, and / or the preamble code set to which the preamble code belongs, so that the network device can use the corresponding receiving method to receive the preamble code, thereby reducing the implementation complexity of the network device receiving the preamble code.

[0167] In addition, in some embodiments, when the terminal device selects the RACH resources and / or preamble codes for sending the preamble code, it may also be combined with whether it requests to use the OCC to send message 3 or whether it has the second capability. In this way, the network device can also know whether the terminal device requests to use the OCC to send message 3 or whether it has the second capability based on the resource pool to which the RACH resources used by the terminal device to send the preamble code belong and / or the preamble code set to which the preamble code belongs, thereby facilitating the network device to determine an appropriate scheduling strategy for message 3 for the terminal device.

[0168] As mentioned above, after the introduction of OCC, the transmission of Messages 1 and 3 during the random access process may use OCC. For Message 3, if the network device does not know in advance whether the terminal device has the ability to use OCC to transmit the PUSCH carrying Message 3 (or the ability to transmit PUSCH), then the network device cannot determine the appropriate scheduling strategy for Message 3. In other words, it cannot determine whether OCC is used to transmit the PUSCH carrying Message 3 between the terminal device and the network device.

[0169] In view of this, the present application also provides a random access method. In this method, a terminal device may send a preamble to a network device on a RACH resource. The resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs may be used to indicate: whether the terminal device requests to use the OCC to send message 3; or whether the terminal device has a second capability. The second capability includes: the ability to use the OCC to send a PUSCH for carrying message 3, or the ability to use the OCC to send a PUSCH.

[0170] In this way, the network device can learn whether the terminal device requests to use OCC to send message 3 or whether it has the second capability based on the resource pool to which the RACH resource used when the terminal device sends the preamble belongs, and / or the preamble set to which the preamble belongs, thereby facilitating the network device to determine an appropriate scheduling strategy for message 3. For example, if the network device learns that the terminal device requests to use OCC to send message 3 or has the second capability, the scheduling strategy for message 3 for the terminal device can be determined as: using OCC to transmit the PUSCH carrying message 3; if the network device learns that the terminal device does not request to use OCC to send message 3 or does not have the second capability, the scheduling strategy for message 3 for the terminal device can be determined as: transmitting the PUSCH carrying message 3 without using OCC.

[0171] FIG5 is a second flow chart of a random access method provided in an embodiment of the present application. As shown in FIG5 , the method may include the following steps:

[0172] S501, the terminal device sends a preamble code to the network device on the RACH resource; the resource pool to which the RACH resource belongs and / or the preamble code set to which the preamble code belongs are used to indicate: whether the terminal device requests to use the OCC to send message 3; or whether the terminal device has a second capability; the second capability includes: the ability to use the OCC to send a PUSCH for carrying message 3, or the ability to use the OCC to send a PUSCH.

[0173] In this embodiment, the terminal device may send a preamble to the network device on a RACH resource, and correspondingly, the network device may receive a preamble from the terminal device on the RACH resource. The resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs may be used to indicate: whether the terminal device requests to use the OCC to send Message 3; or whether the terminal device has the second capability.

[0174] The resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs are used to indicate whether the terminal device requests to use the OCC to send message 3, or whether the terminal device has the second capability. This can also be understood as indicating whether the terminal device requests to use the OCC to send message 3, or whether the terminal device has the second capability. That is, the network device can determine whether the terminal device requests to use the OCC to send message 3, or whether the terminal device has the second capability, based on the RACH resource and / or the preamble used by the terminal device when sending the preamble.

[0175] The second capability includes: the capability of using the OCC to send a PUSCH for carrying message 3, or the capability of using the OCC to send a PUSCH.

[0176] In one example, the second capability includes the ability to use OCC to send a PUSCH for carrying message 3. In this case, if the terminal device has the second capability, it means that the terminal device can use OCC to send a PUSCH for carrying message 3, that is, the terminal device has the ability to use OCC to send a PUSCH for carrying message 3.

[0177] In another example, the second capability includes the ability to use OCC to send PUSCH. In this case, if the terminal device has the second capability, it means that the terminal device can use OCC to send PUSCH, that is, the terminal device has the ability to use OCC to send PUSCH. In this case, the terminal device not only has the ability to use OCC to send PUSCH carrying Message 3, but also has the ability to use OCC to send PUSCH carrying other data / messages.

[0178] In some embodiments, when the RACH resource belongs to the first RACH resource pool and / or the preamble belongs to the first preamble set, the terminal device requests to use OCC to send message 3, or the terminal device has the second capability.

[0179] As an example, when the RACH resource belongs to the first RACH resource pool, the terminal device requests to use OCC to send message 3, or the terminal device has the second capability. That is to say, if the RACH resource belongs to the first RACH resource pool, it means that the terminal device requests to use OCC to send message 3, or it means that the terminal device has the second capability. In other words, the information that "the RACH resource belongs to the first RACH resource pool" can be used to indicate that the terminal device requests to use OCC to send message 3, or it can be used to indicate that the terminal device has the second capability. In this case, if the network device recognizes that the RACH resource used by the terminal device to send the preamble belongs to the first RACH resource pool, it can be determined that the terminal device requests to use OCC to send message 3, or it can be determined that the terminal device has the second capability.

[0180] As another example, when the preamble belongs to the first preamble set, the terminal device requests to use OCC to send message 3, or the terminal device has the second capability. That is, if the preamble belongs to the first preamble set, it indicates that the terminal device requests to use OCC to send message 3, or that the terminal device has the second capability. In other words, the information that "the preamble belongs to the first preamble set" can be used to indicate that the terminal device requests to use OCC to send message 3, or that the terminal device has the second capability. In this case, if the network device recognizes that the preamble sent by the terminal device belongs to the first preamble set, it can be determined that the terminal device requests to use OCC to send message 3, or that the terminal device has the second capability.

[0181] As another example, when the RACH resource belongs to the first RACH resource pool and the preamble belongs to the first preamble set, the terminal device requests to use OCC to send message 3, or the terminal device has the second capability. That is to say, if the RACH resource belongs to the first RACH resource pool and the preamble belongs to the first preamble set, it means that the terminal device requests to use OCC to send message 3, or it means that the terminal device has the second capability. In other words, the information that "the RACH resource belongs to the first RACH resource pool and the preamble belongs to the first preamble set" can be used to indicate that the terminal device requests to use OCC to send message 3, or it can be used to indicate that the terminal device has the second capability. In this case, if the network device recognizes that the RACH resource used by the terminal device to send the preamble belongs to the first RACH resource pool, and the preamble belongs to the first preamble set, it can be determined that the terminal device requests to use OCC to send message 3, or it can be determined that the terminal device has the second capability.

[0182] In some embodiments, when the RACH resource belongs to the second RACH resource pool and / or the preamble belongs to the second preamble set, the terminal device does not request to use OCC to send message 3, or the terminal device does not have the second capability. In some scenarios, the terminal device does not request to use OCC to send message 3, which can also be understood as the terminal device requesting not to use OCC to send message 3. When the terminal device does not request to use OCC to send message 3, the terminal device may or may not have the second capability.

[0183] As an example, when the RACH resource belongs to the second RACH resource pool, the terminal device does not request to use OCC to send message 3, or the terminal device does not have the second capability. That is to say, if the RACH resource belongs to the second RACH resource pool, it means that the terminal device does not request to use OCC to send message 3, or it means that the terminal device does not have the second capability, or in other words, the information that "the RACH resource belongs to the second RACH resource pool" can be used to indicate that the terminal device does not request to use OCC to send message 3, or it can be used to indicate that the terminal device does not have the second capability. In this case, if the network device recognizes that the RACH resource used by the terminal device to send the preamble belongs to the second RACH resource pool, it can be determined that the terminal device does not request to use OCC to send message 3, or it can be determined that the terminal device does not have the second capability.

[0184] As another example, when the preamble belongs to the second preamble set, the terminal device does not request to use OCC to send message 3, or the terminal device does not have the second capability. That is to say, if the preamble belongs to the second preamble set, it means that the terminal device does not request to use OCC to send message 3, or it means that the terminal device does not have the second capability. In other words, the information that "the preamble belongs to the second preamble set" can be used to indicate that the terminal device does not request to use OCC to send message 3, or it can be used to indicate that the terminal device does not have the second capability. In this case, if the network device recognizes that the preamble sent by the terminal device belongs to the second preamble set, it can be determined that the terminal device does not request to use OCC to send message 3, or it can be determined that the terminal device does not have the second capability.

[0185] As another example, when the RACH resource belongs to the second RACH resource pool and the preamble belongs to the second preamble set, the terminal device does not request to use OCC to send message 3, or the terminal device does not have the second capability. That is to say, if the RACH resource belongs to the second RACH resource pool and the preamble belongs to the second preamble set, it means that the terminal device does not request to use OCC to send message 3, or it means that the terminal device does not have the second capability. In other words, the information that "the RACH resource belongs to the second RACH resource pool and the preamble belongs to the second preamble set" can be used to indicate that the terminal device does not request to use OCC to send message 3, or it can be used to indicate that the terminal device does not have the second capability. In this case, if the network device recognizes that the RACH resource used by the terminal device to send the preamble belongs to the second RACH resource pool, and the preamble belongs to the second preamble set, it can be determined that the terminal device does not request to use OCC to send message 3, or it can be determined that the terminal device does not have the second capability.

[0186] In some embodiments, the method may further include: the network device sending a random access response to the terminal device, and accordingly, the terminal device may receive the random access response from the network device.

[0187] In some embodiments, when the terminal device requests to use OCC to send message 3, or when the terminal device has the second capability, the random access response can be used to indicate: a first PUSCH resource and a first OCC; the first OCC is used by the terminal device to send message 3 to the network device on the first PUSCH resource.

[0188] That is to say, if the network device determines that the terminal device requests to use OCC to send message 3, or determines that the terminal device has the second capability, then the network device can carry the first PUSCH resource and the first OCC in the random access response sent to the terminal device, so that the terminal device can use the first OCC on the first PUSCH resource to send message 3 to the network device.

[0189] In some embodiments, when the terminal device does not request to use OCC to send message 3, or the terminal device does not have the second capability, the random access response can be used to indicate: a second PUSCH resource; the second PUSCH resource is used by the terminal device to send message 3 to the network device without using OCC.

[0190] That is to say, if the network device determines that the terminal device has not requested to use OCC to send message 3, or determines that the terminal device does not have the second capability, then the network device may carry a second PUSCH resource in the random access response sent to the terminal device, so that the terminal device can send message 3 to the network device on the second PUSCH, and does not use OCC when sending message 3.

[0191] According to the method of this embodiment, the network device may determine whether the terminal device requests to use OCC to send message 3 or whether the terminal device has the second capability based on the resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs. In this way, the network device may determine a scheduling policy for message 3 for the terminal device based on whether the terminal device requests to use OCC to send message 3 or whether it has the second capability. For example, if the network device determines that the terminal device requests to use OCC to send message 3 or has the second capability, it can determine that the scheduling strategy for message 3 of the terminal device is: use OCC to transmit the PUSCH carrying message 3. At this time, the network device can carry the PUSCH resources (first PUSCH resources) and OCC (first OCC) used for the terminal device to send message 3 in the random access response; if the network device determines that the terminal device does not request to use OCC to send message 3 or does not have the second capability, it can determine that the scheduling strategy for message 3 of the terminal device is: transmit the PUSCH carrying message 3 without using OCC. At this time, the network device can carry the PUSCH resources (second PUSCH resources) used for the terminal device to send message 3 in the random access response without carrying OCC.

[0192] In some embodiments, the selection of the RACH resource and / or the preamble is related to whether the terminal device requests to use OCC to send message 3, or whether the terminal device has the second capability. In other words, the terminal device may select the corresponding RACH resource and / or preamble based on whether it requests to use OCC to send message 3; alternatively, the terminal device may select the corresponding RACH resource and / or preamble based on whether it has the second capability.

[0193] In some embodiments, when the terminal device requests to use OCC to send message 3, or the terminal device has the second capability, the RACH resource is selected from the first RACH resource pool, and / or the preamble code is selected from the first preamble code set.

[0194] That is, if the terminal device requests to use OCC to send message 3, or the terminal device has the second capability, then the terminal device can select RACH resources for sending preamble codes from the first RACH resource pool, and / or can select the preamble codes to be sent from the first preamble code set.

[0195] In one example, if the terminal device requests to use OCC to send message 3, or if the terminal device has the second capability, a RACH resource for sending a preamble may be selected from the first RACH resource pool and the preamble may be sent on the RACH resource. Thus, if the network device identifies that the RACH resource used by the terminal device to send the preamble belongs to the first RACH resource pool, it may determine that the terminal device requests to use OCC to send message 3, or that the terminal device has the second capability.

[0196] In another example, if the terminal device requests to use OCC to send message 3, or if the terminal device has the second capability, the preamble to be sent may be selected from the first preamble set and may be sent on the RACH resource. In this way, if the network device recognizes that the preamble sent by the terminal device belongs to the first preamble set, it may be determined that the terminal device requests to use OCC to send message 3, or that the terminal device has the second capability.

[0197] As another example, if the terminal device requests to use OCC to send message 3, or if the terminal device has the second capability, a RACH resource for sending a preamble may be selected from the first RACH resource pool, and the preamble to be sent may be selected from the first preamble set. The terminal device may send the preamble selected from the first preamble set on the RACH resource selected from the first RACH resource pool. In this way, if the network device recognizes that the RACH resource used by the terminal device to send the preamble belongs to the first RACH resource pool, and that the preamble belongs to the first preamble set, it may be determined that the terminal device requests to use OCC to send message 3, or that the terminal device has the second capability.

[0198] In some embodiments, if the terminal device does not request to use OCC to send message 3, or if the terminal device does not have the second capability, the RACH resource is determined from the second RACH resource pool, and / or the preamble is selected from the second preamble set. In some scenarios, if the terminal device does not request to use OCC to send message 3, it can also be understood that the terminal device requests not to use OCC to send message 3. If the terminal device does not request to use OCC to send message 3, the terminal device may or may not have the second capability.

[0199] In one example, if the terminal device does not request to use OCC to send Message 3, or if the terminal device does not possess the second capability, a RACH resource for sending a preamble may be selected from the second RACH resource pool, and the preamble may be sent on the RACH resource. Thus, if the network device identifies that the RACH resource used by the terminal device to send the preamble belongs to the second RACH resource pool, it may be determined that the terminal device did not request to use OCC to send Message 3, or that the terminal device does not possess the second capability.

[0200] In another example, if the terminal device does not request to use OCC to send Message 3, or the terminal device does not have the second capability, a preamble to be sent may be selected from the second preamble set and sent on the RACH resource. In this way, if the network device recognizes that the preamble sent by the terminal device belongs to the second preamble set, it can be determined that the terminal device did not request to use OCC to send Message 3, or that the terminal device does not have the second capability.

[0201] As another example, if the terminal device does not request to use OCC to send Message 3, or if the terminal device does not possess the second capability, a RACH resource for sending a preamble may be selected from the second RACH resource pool, and the preamble to be sent may be selected from the second preamble set. The terminal device may send a preamble selected from the second preamble set on the RACH resource selected from the second RACH resource pool. In this way, if the network device recognizes that the RACH resource used by the terminal device to send the preamble belongs to the second RACH resource pool, and that the preamble belongs to the second preamble set, it may be determined that the terminal device did not request to use OCC to send Message 3, or that the terminal device does not possess the second capability.

[0202] In some embodiments, one or more of the first RACH resource pool, the second RACH resource pool, the first preamble set, and the second preamble set may be included in configuration information sent by the network device. In other words, one or more of the first RACH resource pool, the second RACH resource pool, the first preamble set, and the second preamble set may be configured by the network device.

[0203] Exemplarily, the network device may send configuration information to the terminal device, and correspondingly, the terminal device may receive the configuration information from the network device. The configuration information may include one or more of the following, or in other words, the configuration information may be used to configure one or more of the following: a first RACH resource pool, a second RACH resource pool, a first preamble set, and a second preamble set.

[0204] In some embodiments, the RACH resources in the first RACH resource pool and the RACH resources in the second RACH resource pool do not overlap. In some embodiments, the preambles in the first preamble set and the preambles in the second preamble set do not overlap.

[0205] According to the method of this embodiment, the network device may be configured with different RACH resource pools and / or preamble sets. The terminal device may select a RACH resource for sending a preamble from the corresponding RACH resource pool and / or select a preamble to be sent from the corresponding preamble set based on whether the terminal device requests to use OCC to send message 3 or has the second capability. For example, if the terminal device requests to use OCC to send message 3 or has the second capability, the RACH resource for sending a preamble may be selected from the first RACH resource pool and / or the preamble to be sent may be selected from the first preamble set. If the terminal device does not request to use OCC to send message 3 or does not have the second capability, the RACH resource for sending a preamble may be selected from the second RACH resource pool and / or the preamble to be sent may be selected from the second preamble set. In this way, the network device can know whether the terminal device requests to use OCC to send message 3 or whether it has the second capability based on the resource pool to which the RACH resource used when the terminal device sends the preamble code belongs, and / or the preamble code set to which the preamble code belongs, thereby facilitating the network device to determine a suitable scheduling strategy for message 3.

[0206] The above introduces the random access method provided in the embodiment of the present application. To facilitate understanding of the embodiment of the present application, the following takes the network device as a base station and the terminal device as a UE as an example to introduce possible implementation schemes of the random access method applicable to the embodiment of the present application.

[0207] Option 1

[0208] In solution one, the base station may configure a RACH resource pool and / or preamble code set for UEs that support PRACH transmission using OCC and UEs that do not support PRACH transmission using OCC, respectively. In random access, the UE may select RACH resources and / or preamble codes from the corresponding RACH resource pool and / or preamble code set based on whether it has the ability to use OCC for PRACH transmission (first capability). If the base station does not configure a corresponding RACH resource pool and / or preamble code set for a UE that does not support PRACH transmission using OCC, the UE that does not support PRACH transmission using OCC may consider that the cell corresponding to the base station prohibits the UE from accessing (that is, the cell is cellbarred).

[0209] The implementation process of Solution 1 may include the following steps 11 and 12.

[0210] Step 11: The UE receives RACH resource configuration information (corresponding to the configuration information in the above embodiment) from the base station. The RACH resource configuration information may include one or more of the following:

[0211] a) RACH resource pool 1 (corresponding to the first RACH resource pool in the aforementioned embodiment).

[0212] PRACH transmission on the RACH resources in RACH resource pool 1 uses OCC-based transmission, or in other words, the RACH resources in RACH resource pool 1 are used to transmit PRACH while using OCC.

[0213] b) RACH resource pool 2 (corresponding to the second RACH resource pool in the aforementioned embodiment).

[0214] PRACH transmission on the RACH resources in RACH resource pool 2 does not use OCC-based transmission, or in other words, the RACH resources in RACH resource pool 2 are used to transmit PRACH without using OCC.

[0215] In this embodiment, the RACH resources in RACH resource pool 1 and RACH resource pool 2 do not overlap.

[0216] c) Preamble set 1 (corresponding to the first preamble set in the aforementioned embodiment).

[0217] The preambles in preamble set 1 are transmitted using OCC-based transmission, or in other words, the preambles in preamble set 1 are transmitted using OCC.

[0218] d) Preamble set 2 (corresponding to the second preamble set in the aforementioned embodiment).

[0219] The preambles in preamble set 2 are not transmitted using OCC-based transmission, or in other words, the preambles in preamble set 2 are not transmitted using OCC.

[0220] In this embodiment, the preambles in preamble set 1 and preamble set 2 do not overlap.

[0221] e) The OCC set used for PRACH transmission (corresponding to the OCC set in the above embodiment).

[0222] Step 12: During the random access process, the UE selects RACH resources and / or preambles from the corresponding RACH resource pool and / or preamble set based on whether the UE has the first capability (capability of using the OCC for PRACH transmission).

[0223] In one possible case (case #1), the RACH resource configuration information includes both RACH resource pool 1 and / or preamble set 1 and RACH resource pool 2 and / or preamble set 2.

[0224] As an example of case #1, the RACH resource configuration information may include: RACH resource pool 1, RACH resource pool 2, preamble set 1, and preamble set 2.

[0225] In this case, for a UE with the first capability, if the UE uses (plans to use / decides to use) an OCC to transmit a preamble, the UE may select a RACH resource and a preamble from RACH resource pool 1 and preamble set 1, and may select an OCC from the OCC set used for PRACH transmission. The UE may then transmit the selected preamble on the selected RACH resource based on the selected OCC. In this case, the RACH resource configuration information also includes the OCC set used for PRACH transmission.

[0226] For a UE with the first capability, if the UE does not use (plans not to use / decides not to use) OCC to send a preamble, it can select RACH resources and preambles from RACH resource pool 2 and preamble set 2. Then, the UE can transmit the selected preamble on the selected RACH resource. In this case, PRACH transmission does not use OCC.

[0227] For a UE that does not have the first capability, since it cannot use OCC for PRACH transmission, the UE can select RACH resources and preambles from RACH resource pool 2 and preamble set 2, and then the UE can transmit the selected preamble on the selected RACH resources.

[0228] As another example of case #1, the RACH resource configuration information may include: RACH resource pool 1 and resource pool 2.

[0229] In this case, for a UE with the first capability, if the UE uses (plans to use / decides to use) an OCC to transmit a preamble, it can select a RACH resource from RACH resource pool 1 and select an OCC from the OCC set used for PRACH transmission. The UE can then transmit the preamble based on the selected OCC on the selected RACH resource. In this case, the RACH resource configuration information also includes the OCC set used for PRACH transmission.

[0230] For a UE with the first capability, if the UE does not use (plans not to use / decides not to use) the OCC to send a preamble, a RACH resource can be selected from RACH resource pool 2. Then, the UE can transmit the preamble on the selected RACH resource. In this case, the PRACH (carrying the preamble) transmission does not use the OCC.

[0231] For a UE that does not have the first capability, since it cannot use the OCC for PRACH transmission, the UE may select a RACH resource from the RACH resource pool 2, and then the UE may transmit a preamble on the selected RACH resource.

[0232] As another example of case #1, the RACH resource configuration information may include: preamble set 1 and preamble set 2.

[0233] In this case, for a UE with the first capability, if the UE uses (plans to use / decides to use) an OCC to transmit a preamble, it may select a preamble from preamble set 1 and may select an OCC from the OCC set used for PRACH transmission. The UE may then transmit the selected preamble on the RACH resource based on the selected OCC. In this case, the RACH resource configuration information also includes the OCC set used for PRACH transmission.

[0234] For a UE with the first capability, if the UE does not use (plans not to use / decides not to use) OCC to send a preamble, it can select a preamble from preamble set 2. Then, the UE can transmit the selected preamble on the RACH resource. At this time, PRACH transmission does not use OCC.

[0235] For a UE that does not have the first capability, since it cannot use the OCC for PRACH transmission, the UE may select a preamble from the preamble set 2, and then the UE may transmit the selected preamble on the RACH resource.

[0236] In another possible case (case #2), the RACH resource configuration information includes RACH resource pool 1 and / or preamble set 1, but does not include RACH resource pool 2 and / or preamble set 2.

[0237] As an example of case #2, the RACH resource configuration information may include: RACH resource pool 1.

[0238] In this case, for a UE with the first capability, if the UE uses (plans to use / decides to use) an OCC to transmit a preamble, it can select a RACH resource from RACH resource pool 1 and select an OCC from the OCC set used for PRACH transmission. The UE can then transmit the preamble based on the selected OCC on the selected RACH resource. In this case, the RACH resource configuration information also includes the OCC set used for PRACH transmission.

[0239] A UE that does not have the first capability may consider that the current cell is barred from access. That is, the UE may consider that the current cell does not allow a UE that does not have the first capability to access.

[0240] As another example of case #2, the RACH resource configuration information includes: preamble set 1.

[0241] In this case, for a UE with the first capability, if the UE uses (plans to use / decides to use) an OCC to transmit a preamble, it may select a preamble from preamble set 1 and may select an OCC from the OCC set used for PRACH transmission. The UE may then transmit the selected preamble on the RACH resource based on the selected OCC. In this case, the RACH resource configuration information also includes the OCC set used for PRACH transmission.

[0242] A UE that does not have the first capability may consider that the current cell is barred from access. That is, the UE may consider that the current cell does not allow a UE that does not have the first capability to access.

[0243] As another example of case #2, the RACH resource configuration information may include: RACH resource pool 1 and preamble code set 1.

[0244] In this case, for a UE with the first capability (capability to use OCC for PRACH transmission), if the UE uses (plans to use / decides to use) an OCC to send a preamble, it can select a RACH resource and a preamble from RACH resource pool 1 and preamble set 1, and can select an OCC from the OCC set used for PRACH transmission. The UE can then transmit the selected preamble on the selected RACH resource based on the selected OCC. In this case, the RACH resource configuration information also includes the OCC set used for PRACH transmission.

[0245] A UE that does not have the first capability may consider that the current cell is barred from access. That is, the UE may consider that the current cell does not allow a UE that does not have the first capability to access.

[0246] In another possible case (case #3), the RACH resource configuration information includes RACH resource pool 2 and / or preamble set 2, but does not include RACH resource pool 1 and / or preamble set 1.

[0247] As an example of case #3, the RACH resource configuration information may include: RACH resource pool 2.

[0248] In this case, for a UE that does not have the first capability, a RACH resource may be selected from the RACH resource pool 2, and then the UE may transmit a preamble on the selected RACH resource.

[0249] For a UE with the first capability, a RACH resource may also be selected from the RACH resource pool 2. Then, the UE may transmit a preamble on the selected RACH resource. In this case, PRACH (carrying the preamble) transmission does not use OCC.

[0250] As another example of case #3, the RACH resource configuration information may include: preamble set 2.

[0251] In this case, for a UE that does not have the first capability, a preamble may be selected from preamble set 2, and then the UE may transmit the selected preamble on the RACH resource.

[0252] For a UE with the first capability, a preamble may also be selected from the preamble set 2. Then, the UE may transmit the selected preamble on the RACH resource. In this case, the PRACH (carrying the preamble) transmission does not use the OCC.

[0253] As another example of case #3, the RACH resource configuration information may include: RACH resource pool 2 and preamble code set 2.

[0254] In this case, for a UE that does not have the first capability, a RACH resource and a preamble may be selected from RACH resource pool 2 and preamble set 2, and then the UE may transmit the selected preamble on the selected RACH resource.

[0255] For a UE with the first capability, RACH resources and preambles may also be selected from RACH resource pool 2 and preamble set 2. Then, the UE may transmit the selected preamble on the selected RACH resources. In this case, PRACH (carrying preamble) transmission does not use OCC.

[0256] In solution 1, when receiving a preamble (Msg1) from a UE, the base station can determine whether the UE used an OCC when transmitting the preamble based on the preamble set to which the preamble belongs and / or the RACH resource pool to which the RACH resource used to transmit the preamble belongs. In other words, the preamble set to which the preamble belongs and / or the RACH resource pool to which the RACH resource used to transmit the preamble belongs can be used to indicate to the base station whether the UE used an OCC when transmitting the preamble.

[0257] In one example, if the preamble set to which the preamble belongs is preamble set 1, the base station can determine that the UE used OCC when transmitting the preamble; if the preamble set to which the preamble belongs is preamble set 2, the base station can determine that the UE did not use OCC when transmitting the preamble.

[0258] In another example, if the resource pool to which the RACH resource for transmitting the preamble belongs is RACH resource pool 1, the base station can determine that the UE used OCC when transmitting the preamble; if the resource pool to which the RACH resource for transmitting the preamble belongs is RACH resource pool 2, the base station can determine that the UE did not use OCC when transmitting the preamble.

[0259] As another example, if the preamble set to which the preamble belongs is preamble set 1, and the resource pool to which the RACH resource for transmitting the preamble belongs is RACH resource pool 1, the base station can determine that the UE used OCC when transmitting the preamble; if the preamble set to which the preamble belongs is preamble set 2, and the resource pool to which the RACH resource for transmitting the preamble belongs is RACH resource pool 2, the base station can determine that the UE did not use OCC when transmitting the preamble.

[0260] According to the method in Solution 1, during the process of receiving the preamble code (Msg1), the base station can learn whether the UE used OCC when transmitting the preamble code. In this way, the base station can use the corresponding reception method to receive the preamble code without having to try to receive it using both the method without using OCC and the method with OCC respectively, thereby reducing the implementation complexity of the base station receiving the preamble code.

[0261] Option 2

[0262] In solution 2, the UE may indicate to the base station via Msg1 (preamble) whether the UE has the second capability, or whether the UE requests to use OCC to send Msg3.

[0263] Among them, the second capability includes: the ability to use OCC to transmit PUSCH carrying Msg3 (or, the ability to superimpose OCC on the time domain / frequency domain and then transmit PUSCH carrying Msg3), or the ability to use OCC to transmit PUSCH (or, the ability to superimpose OCC on the time domain / frequency domain and then transmit PUSCH).

[0264] The implementation process of Option 2 may include the following steps 21 to 23.

[0265] Step 21: The UE receives RACH resource configuration information (corresponding to the configuration information in the above embodiment) from the base station. The RACH resource configuration information may include one or more of the following: RACH resource pool 1; RACH resource pool 2; preamble set 1; preamble set 2.

[0266] The RACH resources in the RACH resource pool 1 and the RACH resource pool 2 do not overlap; and the preambles in the preamble set 1 and the preamble set 2 do not overlap.

[0267] It should be noted that RACH resource pool 1, RACH resource pool 2, preamble set 1, and preamble set 2 in solution 2 may be the same as or different from RACH resource pool 1, RACH resource pool 2, preamble set 1, and preamble set 2 in solution 1.

[0268] Step 22: During the random access process, the UE may select RACH resources and / or preamble codes from the corresponding RACH resource pool and / or preamble code set based on whether the UE has the second capability or whether it requests to use the OCC to send Msg3.

[0269] In one example, if the UE has the second capability, or the UE requests to use OCC to send Msg3, it can select RACH resources and / or preambles from RACH resource pool 1 and / or preamble set 1, and transmit the preamble on the selected RACH resources.

[0270] In another example, if the UE does not have the second capability, or the UE does not request to use OCC to send Msg3, it can select RACH resources and / or preambles from RACH resource pool 2 and / or preamble set 2, and transmit the preamble on the selected RACH resources.

[0271] It should be noted that, when the UE does not request to use the OCC to send Msg3, the UE may or may not have the second capability.

[0272] Step 23: After receiving the preamble (Msg1), the base station can determine (identify) whether the UE has the second capability or whether the UE requests to use the OCC to send Msg3 based on the preamble set to which the preamble belongs and / or the RACH resource pool to which the RACH resource transmitting the preamble belongs. Thus, the base station can determine the scheduling strategy for the PUSCH (carrying Msg3) for the UE.

[0273] In one example, if the preamble belongs to preamble set 1 and / or the resource pool to which the RACH resource transmitting the preamble belongs is RACH resource pool 1, the base station may determine that the UE has the second capability, or that the UE requests to use an OCC to send Msg3. In this case, in addition to indicating the resources for transmitting the PUSCH (for carrying Msg3) in the random access response sent to the UE, the base station may also indicate an OCC, so that the UE can use the OCC to transmit the PUSCH carrying Msg3 on the resources.

[0274] As another example, if the preamble belongs to preamble set 2, and / or the resource pool to which the RACH resource transmitting the preamble belongs is RACH resource pool 2, the base station may determine that the UE does not have the second capability or that the UE did not request to use the OCC to send Msg3. In this case, the base station may indicate the resources used to transmit the PUSCH (for carrying Msg3) in the random access response sent to the UE without indicating the OCC. In this case, the UE does not use the OCC when transmitting the PUSCH carrying Msg3.

[0275] According to the method in Solution 2, the base station can learn through Msg1 (preamble code) whether the UE has the second capability, or whether it requests to use OCC to send Msg3. Thus, the base station can determine the appropriate Msg3 scheduling strategy, that is, whether OCC is used to transmit the PUSCH carrying Msg3 between the UE and the base station.

[0276] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all fall within the scope of protection of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will no longer describe the various possible combinations separately. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the idea of ​​the present application, they should also be regarded as the contents disclosed in the present application. For another example, under the premise of no conflict, the various embodiments and / or the technical features in each embodiment described in the present application can be arbitrarily combined with the prior art, and the technical solution obtained after the combination should also fall within the scope of protection of the present application.

[0277] It should also be understood that in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply a precedence in their execution order. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. In addition, in the embodiments of the present application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data, where "downlink" is used to indicate the first direction of signal or data transmission from a site to a user equipment in a cell, "uplink" is used to indicate the second direction of signal or data transmission from a user equipment in a cell to a site, and "sidelink" is used to indicate the third direction of signal or data transmission from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the signal is transmitted in the first direction. In addition, in the embodiments of the present application, the term "and / or" is merely a description of the association relationship between associated objects, indicating that three relationships can exist. Specifically, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0278] Based on the aforementioned embodiments, the embodiments of the present application provide corresponding random access devices.

[0279] FIG6 is a schematic diagram of the first structure of a random access apparatus provided in an embodiment of the present application, which is applied to a terminal device. As shown in FIG6 , a random access apparatus 600 (hereinafter referred to as apparatus 600 ) includes:

[0280] The first communication unit 601 is configured to send a preamble to the network device on a random access channel RACH resource; the resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs are used to indicate whether the apparatus 600 uses an orthogonal cover code OCC when sending the preamble.

[0281] In some embodiments, when the RACH resource belongs to the first RACH resource pool and / or the preamble belongs to the first preamble set, the apparatus 600 uses the OCC when sending the preamble; when the RACH resource belongs to the second RACH resource pool and / or the preamble belongs to the second preamble set, the apparatus 600 does not use the OCC when sending the preamble.

[0282] In some embodiments, the selection of RACH resources and / or preambles is related to whether the apparatus 600 uses OCC to send preambles.

[0283] In some embodiments, when the device 600 uses OCC to send a preamble, RACH resources are selected from a first RACH resource pool and / or the preamble is selected from a first preamble set, and the device 600 has a first capability; when the device 600 does not use OCC to send a preamble, RACH resources are determined from a second RACH resource pool and / or the preamble is selected from a second preamble set, and the device 600 has or does not have the first capability; the first capability is the ability to use OCC to send a physical random access channel PRACH, and PRACH is used to carry the preamble.

[0284] In some embodiments, the resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs are also used to indicate: whether the device 600 requests to use the OCC to send message 3; or whether the device 600 has a second capability; the second capability includes: the ability to use the OCC to send a physical uplink shared channel PUSCH for carrying message 3, or the ability to use the OCC to send PUSCH.

[0285] In some embodiments, when the RACH resources belong to the first RACH resource pool and / or the preamble belongs to the first preamble set, the apparatus 600 requests to use the OCC to send message 3, or the apparatus 600 has the second capability; when the RACH resources belong to the second RACH resource pool and / or the preamble belongs to the second preamble set, the apparatus 600 does not request to use the OCC to send message 3, or the apparatus 600 does not have the second capability.

[0286] In some embodiments, the first communication unit 601 is further configured to: receive a random access response from the network device; when the device 600 requests to use OCC to send message 3, or when the device 600 has the second capability, the random access response is used to indicate: a first PUSCH resource and a first OCC; the first OCC is used by the device 600 to send message 3 to the network device on the first PUSCH resource; when the device 600 does not request to use OCC to send message 3, or when the device 600 does not have the second capability, the random access response is used to indicate: a second PUSCH resource; the second PUSCH resource is used by the device 600 to send message 3 to the network device without using OCC.

[0287] In some embodiments, the selection of RACH resources and / or preamble codes is related to whether the apparatus 600 requests to use OCC to send message 3, or whether the apparatus 600 has the second capability.

[0288] In some embodiments, when the device 600 requests to use OCC to send message 3, or when the device 600 has the second capability, the RACH resource is selected from the first RACH resource pool, and / or the preamble is selected from the first preamble set; when the device 600 does not request to use OCC to send message 3, or when the device 600 does not have the second capability, the RACH resource is determined from the second RACH resource pool, and / or the preamble is selected from the second preamble set.

[0289] In some embodiments, one or more of the first RACH resource pool, the second RACH resource pool, the first preamble set, and the second preamble set are included in configuration information sent by the network device.

[0290] In some embodiments, the configuration information further includes an OCC set, and the OCC set is used by the apparatus 600 to select the OCC to be used when the OCC is used to send a preamble.

[0291] In some embodiments, when the configuration information does not include a second RACH resource pool and / or a second preamble code set, the cell corresponding to the network device does not allow terminal devices that do not have a first capability to access; the first capability is the ability to use OCC to send PRACH, and PRACH is used to carry the preamble code.

[0292] In some embodiments, RACH resources in the first RACH resource pool are used to transmit PRACH when using OCC; RACH resources in the second RACH resource pool are used to transmit PRACH when not using OCC, and PRACH is used to carry preamble codes; preamble codes in the first preamble code set are transmitted using OCC; preamble codes in the second preamble code set are not transmitted using OCC.

[0293] FIG7 is a second schematic diagram of the structure of a random access device provided in an embodiment of the present application, which is applied to a network device. As shown in FIG7 , a random access device 700 (hereinafter referred to as device 700 ) includes:

[0294] The second communication unit 701 is configured to receive a preamble from a terminal device on a random access channel RACH resource; the resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs are used to indicate whether the terminal device uses an orthogonal cover code OCC when sending the preamble.

[0295] In some embodiments, when the RACH resource belongs to a first RACH resource pool and / or the preamble belongs to a first preamble set, the terminal device uses OCC when sending the preamble; when the RACH resource belongs to a second RACH resource pool and / or the preamble belongs to a second preamble set, the terminal device does not use OCC when sending the preamble.

[0296] In some embodiments, the selection of RACH resources and / or preambles is related to whether the terminal device uses OCC to send preambles.

[0297] In some embodiments, when the terminal device uses OCC to send a preamble, the RACH resource is selected from a first RACH resource pool, and / or the preamble is selected from a first preamble set, and the terminal device has a first capability; when the terminal device does not use OCC to send a preamble, the RACH resource is determined from a second RACH resource pool, and / or the preamble is selected from a second preamble set, and the terminal device has or does not have the first capability; the first capability is the ability to use OCC to send a physical random access channel PRACH, and PRACH is used to carry the preamble.

[0298] In some embodiments, the resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs are also used to indicate: whether the terminal device requests to use OCC to send message 3; or whether the terminal device has a second capability, the second capability including: the ability to use OCC to send a physical uplink shared channel PUSCH for carrying message 3, or the ability to use OCC to send PUSCH.

[0299] In some embodiments, when the RACH resources belong to the first RACH resource pool and / or the preamble code belongs to the first preamble code set, the terminal device requests to use OCC to send message 3, or the terminal device has the second capability; when the RACH resources belong to the second RACH resource pool and / or the preamble code belongs to the second preamble code set, the terminal device does not request to use OCC to send message 3, or the terminal device does not have the second capability.

[0300] In some embodiments, the second communication unit 701 is further configured to: send a random access response to the terminal device; when the terminal device requests to use the OCC to send message 3, or the terminal device has the second capability, the random access response is used to indicate: a first PUSCH resource and a first OCC; the first OCC is used by the terminal device to send message 3 to the apparatus 700 on the first PUSCH resource; when the terminal device does not request to use the OCC to send message 3, or the terminal device does not have the second capability, the random access response is used to indicate: a second PUSCH resource; the second PUSCH resource is used by the terminal device to send message 3 to the apparatus 700 without using the OCC.

[0301] In some embodiments, the selection of RACH resources and / or preamble codes is related to whether the terminal device requests to use OCC to send message 3, or whether the terminal device has the second capability.

[0302] In some embodiments, when the terminal device requests to use OCC to send message 3, or the terminal device has the second capability, the RACH resource is selected from the first RACH resource pool, and / or the preamble code is selected from the first preamble code set; when the terminal device does not request to use OCC to send message 3, or the terminal device does not have the second capability, the RACH resource is determined from the second RACH resource pool, and / or the preamble code is selected from the second preamble code set.

[0303] In some embodiments, one or more of the first RACH resource pool, the second RACH resource pool, the first preamble set, and the second preamble set are included in the configuration information sent by the apparatus 700 .

[0304] In some embodiments, the configuration information is also used to configure an OCC set, and the OCC set is used by the terminal device to select the OCC to be used when the OCC is used to send a preamble code.

[0305] In some embodiments, when the configuration information does not include a second RACH resource pool and / or a second preamble code set, the cell corresponding to the apparatus 700 does not allow access by terminal devices that do not have a first capability; the first capability is the ability to use OCC to send PRACH, and PRACH is used to carry preamble codes.

[0306] In some embodiments, RACH resources in the first RACH resource pool are used to transmit PRACH when using OCC; RACH resources in the second RACH resource pool are used to transmit PRACH when not using OCC, and PRACH is used to carry preamble codes; preamble codes in the first preamble code set are transmitted using OCC; preamble codes in the second preamble code set are not transmitted using OCC.

[0307] FIG8 is a third schematic diagram of the structure of a random access apparatus provided in an embodiment of the present application, which is applied to a terminal device. As shown in FIG8 , a random access apparatus 800 (hereinafter referred to as apparatus 800 ) includes:

[0308] The third communication unit 801 is configured to send a preamble code to the network device on the random access channel RACH resource; the resource pool to which the RACH resource belongs and / or the preamble code set to which the preamble code belongs are used to indicate: whether the device requests to use the OCC to send message 3; or whether the device has a second capability; the second capability includes: the ability to use the OCC to send a physical uplink shared channel PUSCH for carrying message 3, or the ability to use the OCC to send PUSCH.

[0309] In some embodiments, when the RACH resources belong to the first RACH resource pool and / or the preamble belongs to the first preamble set, the apparatus 800 requests to use the OCC to send message 3, or the apparatus 800 has the second capability; when the RACH resources belong to the second RACH resource pool and / or the preamble belongs to the second preamble set, the apparatus 800 does not request to use the OCC to send message 3, or the apparatus 800 does not have the second capability.

[0310] In some embodiments, the third communication unit 801 is further configured to: receive a random access response from the network device; when the device 800 requests to use OCC to send message 3, or when the device 800 has the second capability, the random access response is used to indicate: a first PUSCH resource and a first OCC; the first OCC is used by the device 800 to send message 3 to the network device on the first PUSCH resource; when the device 800 does not request to use OCC to send message 3, or when the device 800 does not have the second capability, the random access response is used to indicate: a second PUSCH resource; the second PUSCH resource is used by the device 800 to send message 3 to the network device without using OCC.

[0311] In some embodiments, the selection of RACH resources and / or preamble codes is related to whether the apparatus 800 requests to use OCC to send message 3, or whether the apparatus 800 has the second capability.

[0312] In some embodiments, when the device 800 requests to use OCC to send message 3, or when the device 800 has the second capability, the RACH resource is selected from the first RACH resource pool, and / or the preamble is selected from the first preamble set; when the device 800 does not request to use OCC to send message 3, or when the device 800 does not have the second capability, the RACH resource is determined from the second RACH resource pool, and / or the preamble is selected from the second preamble set.

[0313] In some embodiments, one or more of the first RACH resource pool, the second RACH resource pool, the first preamble set, and the second preamble set are included in configuration information sent by the network device.

[0314] FIG9 is a fourth structural diagram of a random access apparatus provided in an embodiment of the present application, which is applied to a network device. As shown in FIG9 , a random access apparatus 900 (hereinafter referred to as apparatus 900 ) includes:

[0315] The fourth communication unit 901 is configured to receive a preamble code from the terminal device on the random access channel RACH resource; the resource pool to which the RACH resource belongs and / or the preamble code set to which the preamble code belongs are used to indicate: whether the terminal device requests to use the OCC to send message 3; or whether the terminal device has the second capability; the second capability includes: the ability to use the OCC to send a physical uplink shared channel PUSCH for carrying message 3, or the ability to use the OCC to send PUSCH.

[0316] In some embodiments, when the RACH resources belong to the first RACH resource pool and / or the preamble code belongs to the first preamble code set, the terminal device requests to use OCC to send message 3, or the terminal device has the second capability; when the RACH resources belong to the second RACH resource pool and / or the preamble code belongs to the second preamble code set, the terminal device does not request to use OCC to send message 3, or the terminal device does not have the second capability.

[0317] In some embodiments, the fourth communication unit 901 is further configured to: send a random access response to the terminal device; when the terminal device requests to use the OCC to send message 3, or the terminal device has the second capability, the random access response is used to indicate: a first PUSCH resource and a first OCC; the first OCC is used by the terminal device to send message 3 to the apparatus 900 on the first PUSCH resource; when the terminal device does not request to use the OCC to send message 3, or the terminal device does not have the second capability, the random access response is used to indicate: a second PUSCH resource; the second PUSCH resource is used by the terminal device to send message 3 to the apparatus 900 without using the OCC.

[0318] In some embodiments, the selection of RACH resources and / or preamble codes is related to whether the terminal device requests to use OCC to send message 3, or whether the terminal device has the second capability.

[0319] In some embodiments, when the terminal device requests to use OCC to send message 3, or the terminal device has the second capability, the RACH resource is selected from the first RACH resource pool, and / or the preamble code is selected from the first preamble code set; when the terminal device does not request to use OCC to send message 3, or the terminal device does not have the second capability, the RACH resource is determined from the second RACH resource pool, and / or the preamble code is selected from the second preamble code set.

[0320] In some embodiments, one or more of the first RACH resource pool, the second RACH resource pool, the first preamble set, and the second preamble set are included in the configuration information sent by the apparatus 900 .

[0321] Those skilled in the art should understand that the relevant description of the above-mentioned random access device in the embodiment of the present application can be understood with reference to the relevant description of the random access method in the embodiment of the present application.

[0322] Figure 10 is a schematic diagram of a communication device 1000 provided in an embodiment of the present application. The communication device can be a terminal device or a network device. The communication device 1000 shown in Figure 10 includes a processor 1010, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0323] Optionally, as shown in FIG10 , the communication device 1000 may further include a memory 1020. The processor 1010 may call and execute a computer program from the memory 1020 to implement the method in the embodiment of the present application.

[0324] The memory 1020 may be a separate device independent of the processor 1010 , or may be integrated into the processor 1010 .

[0325] Optionally, as shown in FIG10 , the communication device 1000 may further include a transceiver 1030 , and the processor 1010 may control the transceiver 1030 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0326] The transceiver 1030 may include a transmitter and a receiver. The transceiver 1030 may further include an antenna, and the number of antennas may be one or more.

[0327] Optionally, the communication device 1000 may specifically be a network device in an embodiment of the present application, and the communication device 1000 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0328] Optionally, the communication device 1000 may specifically be a terminal device of an embodiment of the present application, and the communication device 1000 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0329] Figure 11 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 1100 shown in Figure 11 includes a processor 1110, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0330] Optionally, as shown in FIG11 , the chip 1100 may further include a memory 1120. The processor 1110 may call and execute a computer program from the memory 1120 to implement the method in the embodiment of the present application.

[0331] The memory 1120 may be a separate device independent of the processor 1110 , or may be integrated into the processor 1110 .

[0332] Optionally, the chip 1100 may further include an input interface 1130. The processor 1110 may control the input interface 1130 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0333] Optionally, the chip 1100 may further include an output interface 1140. The processor 1110 may control the output interface 1140 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0334] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0335] Optionally, the chip can be applied to the terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0336] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0337] An embodiment of the present application further provides a computer storage medium, which stores one or more programs. The one or more programs can be executed by one or more processors to implement the method in the embodiment of the present application.

[0338] FIG12 is a schematic block diagram of a communication system 1200 provided in an embodiment of the present application. As shown in FIG12 , the communication system 1200 includes a terminal device 1210 and a network device 1220 .

[0339] Among them, the terminal device 1210 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1220 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they will not be repeated here.

[0340] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0341] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0342] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0343] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0344] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0345] Optionally, the computer-readable storage medium can be applied to the terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0346] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0347] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0348] Optionally, the computer program product can be applied to the terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0349] The embodiment of the present application also provides a computer program.

[0350] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here.

[0351] Optionally, the computer program can be applied to the terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0352] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0353] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0354] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0355] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0356] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0357] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0358] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A random access method, applied to a terminal device, comprising: Sending a preamble to a network device on a random access channel (RACH) resource; The resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs are used to indicate whether the terminal device uses an orthogonal cover code OCC when sending the preamble.

2. The method according to claim 1, wherein When the RACH resource belongs to a first RACH resource pool and / or the preamble belongs to a first preamble set, the terminal device uses an OCC when sending the preamble; In a case where the RACH resource belongs to a second RACH resource pool and / or the preamble belongs to a second preamble set, the terminal device does not use an OCC when sending the preamble.

3. The method according to claim 1 or 2, wherein: The selection of the RACH resource and / or the preamble is related to whether the terminal device uses OCC to send the preamble.

4. The method according to any one of claims 1 to 3, wherein In a case where the terminal device uses an OCC to send the preamble, the RACH resource is selected from a first RACH resource pool, and / or the preamble is selected from a first preamble set, and the terminal device has a first capability; In a case where the terminal device does not use the OCC to send the preamble, the RACH resource is determined from a second RACH resource pool, and / or the preamble is selected from a second preamble set, and the terminal device has or does not have the first capability; The first capability is the capability of using the OCC to send a physical random access channel PRACH, where the PRACH is used to carry a preamble code.

5. The method according to any one of claims 1 to 4, wherein The resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs are further used to indicate: Whether the terminal device requests to use OCC to send message 3; or Whether the terminal device has a second capability; the second capability includes: the ability to use OCC to send a physical uplink shared channel PUSCH for carrying message 3, or the ability to use OCC to send PUSCH.

6. The method according to claim 5, wherein: In a case where the RACH resource belongs to a first RACH resource pool and / or the preamble belongs to a first preamble set, the terminal device requests to use OCC to send the message 3, or the terminal device has the second capability; In a case where the RACH resource belongs to a second RACH resource pool and / or the preamble belongs to a second preamble set, the terminal device does not request to use OCC to send the message 3, or the terminal device does not have the second capability.

7. The method according to claim 5 or 6, wherein: The method further comprises: receiving a random access response from the network device; When the terminal device requests to use the OCC to send the message 3, or when the terminal device has the second capability, the random access response is used to indicate: a first PUSCH resource and a first OCC; the first OCC is used by the terminal device to send the message 3 to the network device on the first PUSCH resource; When the terminal device does not request to use OCC to send the message 3, or the terminal device does not have the second capability, the random access response is used to indicate: a second PUSCH resource; the second PUSCH resource is used by the terminal device to send the message 3 to the network device without using OCC.

8. The method according to any one of claims 5 to 7, wherein The selection of the RACH resource and / or the preamble is related to whether the terminal device requests to use the OCC to send the message 3, or whether the terminal device has the second capability.

9. The method according to any one of claims 5 to 8, wherein When the terminal device requests to use OCC to send the message 3, or when the terminal device has the second capability, the RACH resource is selected from a first RACH resource pool, and / or the preamble is selected from a first preamble set; When the terminal device does not request to use OCC to send the message 3, or the terminal device does not have the second capability, the RACH resource is determined from a second RACH resource pool, and / or the preamble code is selected from a second preamble code set.

10. The method according to claim 2, 4, 6 or 9, wherein One or more of the first RACH resource pool, the second RACH resource pool, the first preamble code set, and the second preamble code set are included in the configuration information sent by the network device.

11. The method according to claim 10, wherein: The configuration information further includes an OCC set, and the OCC set is used by the terminal device to select the OCC to be used when the OCC is used to send a preamble code.

12. The method according to claim 10 or 11, wherein: In a case where the configuration information does not include the second RACH resource pool and / or the second preamble code set, the cell corresponding to the network device does not allow a terminal device that does not have the first capability to access; The first capability is a capability of using the OCC to send a PRACH, where the PRACH is used to carry a preamble code.

13. The method according to any one of claims 2, 4, 6, 9 to 12, wherein The RACH resources in the first RACH resource pool are used to transmit the PRACH when the OCC is used; The RACH resources in the second RACH resource pool are used to transmit a PRACH without using an OCC, where the PRACH is used to carry a preamble; The preambles in the first preamble set are transmitted using OCC; The preambles in the second preamble set are not transmitted using OCC.

14. A random access method, applied to a network device, comprising: Receiving a preamble from a terminal device on a random access channel RACH resource; The resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs are used to indicate whether the terminal device uses an orthogonal cover code OCC when sending the preamble.

15. The method according to claim 14, wherein When the RACH resource belongs to a first RACH resource pool and / or the preamble belongs to a first preamble set, the terminal device uses an OCC when sending the preamble; In a case where the RACH resource belongs to a second RACH resource pool and / or the preamble belongs to a second preamble set, the terminal device does not use an OCC when sending the preamble.

16. The method according to claim 14 or 15, wherein: The selection of the RACH resource and / or the preamble is related to whether the terminal device uses OCC to send the preamble.

17. The method according to any one of claims 14 to 16, wherein In a case where the terminal device uses an OCC to send the preamble, the RACH resource is selected from a first RACH resource pool, and / or the preamble is selected from a first preamble set, and the terminal device has a first capability; In a case where the terminal device does not use the OCC to send the preamble, the RACH resource is determined from a second RACH resource pool, and / or the preamble is selected from a second preamble set, and the terminal device has or does not have the first capability; The first capability is the capability of using the OCC to send a physical random access channel PRACH, where the PRACH is used to carry a preamble code.

18. The method according to any one of claims 14 to 17, wherein The resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs are further used to indicate: Whether the terminal device requests to use OCC to send message 3; or Whether the terminal device has a second capability, the second capability including: the ability to use OCC to send a physical uplink shared channel PUSCH for carrying message 3, or the ability to use OCC to send PUSCH.

19. The method according to claim 18, wherein In a case where the RACH resource belongs to a first RACH resource pool and / or the preamble belongs to a first preamble set, the terminal device requests to use OCC to send the message 3, or the terminal device has the second capability; In a case where the RACH resource belongs to a second RACH resource pool and / or the preamble belongs to a second preamble set, the terminal device does not request to use OCC to send the message 3, or the terminal device does not have the second capability.

20. The method according to claim 18 or 19, wherein The method further comprises: Sending a random access response to the terminal device; When the terminal device requests to use the OCC to send the message 3, or when the terminal device has the second capability, the random access response is used to indicate: a first PUSCH resource and a first OCC; the first OCC is used by the terminal device to send the message 3 to the network device on the first PUSCH resource; When the terminal device does not request to use OCC to send the message 3, or the terminal device does not have the second capability, the random access response is used to indicate: a second PUSCH resource; the second PUSCH resource is used by the terminal device to send the message 3 to the network device without using OCC.

21. The method according to any one of claims 18 to 20, wherein The selection of the RACH resource and / or the preamble is related to whether the terminal device requests to use the OCC to send the message 3, or whether the terminal device has the second capability.

22. The method according to any one of claims 18 to 21, wherein When the terminal device requests to use OCC to send the message 3, or when the terminal device has the second capability, the RACH resource is selected from a first RACH resource pool, and / or the preamble is selected from a first preamble set; When the terminal device does not request to use OCC to send the message 3, or the terminal device does not have the second capability, the RACH resource is determined from a second RACH resource pool, and / or the preamble code is selected from a second preamble code set.

23. The method of claim 15, 17, 19 or 22, wherein: One or more of the first RACH resource pool, the second RACH resource pool, the first preamble code set, and the second preamble code set are included in the configuration information sent by the network device.

24. The method according to claim 23, wherein The configuration information further includes an OCC set, and the OCC set is used by the terminal device to select the OCC to be used when the OCC is used to send a preamble code.

25. The method according to claim 23 or 24, wherein In a case where the configuration information does not include the second RACH resource pool and / or the second preamble code set, the cell corresponding to the network device does not allow a terminal device that does not have the first capability to access; The first capability is a capability of using the OCC to send a PRACH, where the PRACH is used to carry a preamble code.

26. The method according to any one of claims 15, 17, 19, 22 to 25, wherein The RACH resources in the first RACH resource pool are used to transmit the PRACH when the OCC is used; The RACH resources in the second RACH resource pool are used to transmit a PRACH without using an OCC, where the PRACH is used to carry a preamble; The preambles in the first preamble set are transmitted using OCC; The preambles in the second preamble set are not transmitted using OCC.

27. A random access method, applied to a terminal device, comprising: Sending a preamble to a network device on a random access channel (RACH) resource; The resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs are used to indicate: Whether the terminal device requests to use OCC to send message 3; or, Whether the terminal device has a second capability; the second capability includes: the ability to use OCC to send a physical uplink shared channel PUSCH for carrying message 3, or the ability to use OCC to send PUSCH.

28. The method according to claim 27, wherein In a case where the RACH resource belongs to a first RACH resource pool and / or the preamble belongs to a first preamble set, the terminal device requests to use OCC to send the message 3, or the terminal device has the second capability; In a case where the RACH resource belongs to a second RACH resource pool and / or the preamble belongs to a second preamble set, the terminal device does not request to use OCC to send the message 3, or the terminal device does not have the second capability.

29. The method according to claim 27 or 28, wherein The method further comprises: receiving a random access response from a network device; When the terminal device requests to use the OCC to send the message 3, or when the terminal device has the second capability, the random access response is used to indicate: a first PUSCH resource and a first OCC; the first OCC is used by the terminal device to send the message 3 to the network device on the first PUSCH resource; When the terminal device does not request to use OCC to send the message 3, or the terminal device does not have the second capability, the random access response is used to indicate: a second PUSCH resource; the second PUSCH resource is used by the terminal device to send the message 3 to the network device without using OCC.

30. The method according to any one of claims 27 to 29, wherein The selection of the RACH resource and / or the preamble is related to whether the terminal device requests to use the OCC to send the message 3, or whether the terminal device has the second capability.

31. The method according to any one of claims 27 to 30, wherein When the terminal device requests to use OCC to send the message 3, or when the terminal device has the second capability, the RACH resource is selected from a first RACH resource pool, and / or the preamble is selected from a first preamble set; When the terminal device does not request to use OCC to send the message 3, or the terminal device does not have the second capability, the RACH resource is determined from a second RACH resource pool, and / or the preamble code is selected from a second preamble code set.

32. The method according to claim 28 or 31, wherein One or more of the first RACH resource pool, the second RACH resource pool, the first preamble code set, and the second preamble code set are included in the configuration information sent by the network device.

33. A random access method, applied to a network device, comprising: Receiving a preamble from a terminal device on a random access channel RACH resource; The resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs are used to indicate: Whether the terminal device requests to use OCC to send message 3; or, Whether the terminal device has a second capability; the second capability includes: the ability to use OCC to send a physical uplink shared channel PUSCH for carrying message 3, or the ability to use OCC to send PUSCH.

34. The method according to claim 33, wherein In a case where the RACH resource belongs to a first RACH resource pool and / or the preamble belongs to a first preamble set, the terminal device requests to use OCC to send the message 3, or the terminal device has the second capability; In a case where the RACH resource belongs to a second RACH resource pool and / or the preamble belongs to a second preamble set, the terminal device does not request to use OCC to send the message 3, or the terminal device does not have the second capability.

35. The method according to claim 33 or 34, wherein The method further comprises: Sending a random access response to the terminal device; When the terminal device requests to use the OCC to send the message 3, or when the terminal device has the second capability, the random access response is used to indicate: a first PUSCH resource and a first OCC; the first OCC is used by the terminal device to send the message 3 to the network device on the first PUSCH resource; When the terminal device does not request to use OCC to send the message 3, or the terminal device does not have the second capability, the random access response is used to indicate: a second PUSCH resource; the second PUSCH resource is used by the terminal device to send the message 3 to the network device without using OCC.

36. The method according to any one of claims 33 to 35, wherein The selection of the RACH resource and / or the preamble is related to whether the terminal device requests to use the OCC to send the message 3, or whether the terminal device has the second capability.

37. The method according to any one of claims 33 to 36, wherein When the terminal device requests to use OCC to send the message 3, or when the terminal device has the second capability, the RACH resource is selected from a first RACH resource pool, and / or the preamble is selected from a first preamble set; When the terminal device does not request to use OCC to send the message 3, or the terminal device does not have the second capability, the RACH resource is determined from a second RACH resource pool, and / or the preamble code is selected from a second preamble code set.

38. The method according to claim 34 or 37, wherein One or more of the first RACH resource pool, the second RACH resource pool, the first preamble code set, and the second preamble code set are included in the configuration information sent by the network device.

39. A random access device, comprising: A first communication unit is configured to send a preamble code to the network device on a random access channel RACH resource; The resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs are used to indicate whether the device uses an orthogonal cover code OCC when sending the preamble.

40. A random access device, comprising: The second communication unit is configured to receive a preamble from a terminal device on a random access channel RACH resource; The resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs are used to indicate whether the terminal device uses an orthogonal cover code OCC when sending the preamble.

41. A random access device, comprising: A third communication unit is configured to send a preamble code to the network device on a random access channel RACH resource; The resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs are used to indicate: Whether the device requests to use OCC to send message 3; or, Whether the device has a second capability; the second capability includes: the ability to use OCC to send a physical uplink shared channel PUSCH for carrying message 3, or the ability to use OCC to send PUSCH.

42. A random access device, comprising: The fourth communication unit is configured to receive a preamble from a terminal device on a random access channel RACH resource; The resource pool to which the RACH resource belongs and / or the preamble set to which the preamble belongs are used to indicate: Whether the terminal device requests to use OCC to send message 3; or, Whether the terminal device has a second capability; the second capability includes: the ability to use OCC to send a physical uplink shared channel PUSCH for carrying message 3, or the ability to use OCC to send PUSCH.

43. A communication device, comprising: memory for storing computer programs; a processor, connected to the memory, configured to call and execute the computer program from the memory to implement the method according to any one of claims 1 to 13, or the method according to any one of claims 14 to 26, or the method according to any one of claims 27 to 32, or the method according to any one of claims 33 to 38; A transceiver is used to send and receive information between devices.

44. A chip, comprising: A processor configured to call and run a computer program from a memory, so that a device equipped with the chip performs the method according to any one of claims 1 to 13, or the method according to any one of claims 14 to 26, or the method according to any one of claims 27 to 32. A method according to any one of claims 33 to 38; A transceiver is used to send and receive information between a device or chip.

45. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to perform the method according to any one of claims 1 to 13, or the method according to any one of claims 14 to 26, or the method according to any one of claims 27 to 32, or the method according to any one of claims 33 to 38.

46. A computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method of any one of claims 1 to 13, or the method of any one of claims 14 to 26, or the method of any one of claims 27 to 32, or the method of any one of claims 33 to 38.

47. A computer program causing a computer to perform the method of any one of claims 1 to 13, or the method of any one of claims 14 to 26, or the method of any one of claims 27 to 32, or the method of any one of claims 33 to 38.

Images