Orthogonal overlay code configuration for message 3

By transmitting DCI and RAR between network devices and terminal devices, the OCC configuration of MSG 3 is clarified, which solves the problem of insufficient OCC of MSG 3 and improves the uplink capacity and user equipment multiplexing capability of satellite communication system.

CN123126008APending Publication Date: 2026-11-17ALCATEL LUCENT SHANGHAI BELL CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480090387.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-04-03
Publication Date
2026-11-17

Smart Images

  • Figure CN123126008A_ABST
    Figure CN123126008A_ABST
Patent Text Reader

Abstract

Embodiments of this disclosure relate to the configuration of an orthogonal coverage code (OCC) for random access message (MSG) 3. In one aspect, a terminal device receives downlink control information (DCI) from a network device for scheduling a random access response (RAR). The terminal device receives the RAR from the network device based on the DCI. At least one of the DCI or the RAR includes first configuration information associated with the orthogonal coverage code (OCC) for transmitting message 3 (MSG 3). The terminal device transmits MSG 3 to the network device based on the first configuration information. Therefore, a solution regarding how a network device signals the OCC code for transmitting message (MSG) 3 is proposed for uplink capacity enhancement, thereby improving communication performance.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Various example embodiments relate to the field of communications, and particularly to devices, methods, apparatuses, and computer-readable storage media for configuring orthogonal cover codes (OCC) for random access messages (MSG) 3. Background Technology

[0002] A communication network can be viewed as a facility that enables communication between two or more communication devices, or provides communication devices with access to a data network. Mobile or wireless communication networks are an example of communication networks.

[0003] Such communication networks operate according to standards, such as those issued by 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of such standards include the so-called 5G (fifth generation) standard and other standards issued by 3GPP. Summary of the Invention

[0004] In general, the example embodiments of this disclosure provide a solution for OCC configuration for Random Access Message (MSG) 3.

[0005] In a first aspect, a terminal device is provided. The terminal device includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the terminal device to: receive downlink control information (DCI) for scheduling a random access response (RAR) from a network device; receive the RAR from the network device based on the DCI, wherein at least one of the DCI or the RAR includes first configuration information associated with an orthogonal overlay code (OCC) for transmitting message 3 (MSG 3); and transmit MSG 3 to the network device based on the first configuration information.

[0006] In a second aspect, a network device is provided. The network device includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the network device to: transmit downlink control information (DCI) for scheduling a random access response (RAR) to an end device; transmit the RAR to the end device based on the DCI, wherein at least one of the DCI or the RAR includes first configuration information associated with an orthogonal overlay code (OCC) for transmitting message 3 (MSG 3); and receive MSG 3 from the end device based on the first configuration information.

[0007] In a third aspect, a method is provided. The method includes: receiving downlink control information (DCI) for scheduling a random access response (RAR) from a network device at an end device; receiving the RAR from the network device based on the DCI, wherein at least one of the DCI or the RAR includes first configuration information associated with an orthogonal overlay code (OCC) for transmitting message 3 (MSG 3); and transmitting MSG 3 to the network device based on the first configuration information.

[0008] In a fourth aspect, a method is provided. The method includes: transmitting downlink control information (DCI) for scheduling a random access response (RAR) to an end device at a network device; transmitting the RAR to the end device based on the DCI, wherein at least one of the DCI or the RAR includes first configuration information associated with an orthogonal overlay code (OCC) for transmitting message 3 (MSG 3); and receiving MSG 3 from the end device based on the first configuration information.

[0009] In a fifth aspect, an apparatus is provided, comprising: components for receiving downlink control information (DCI) for scheduling a random access response (RAR) from a network device at an end device; components for receiving the RAR from the network device based on the DCI, wherein at least one of the DCI or the RAR includes first configuration information associated with an orthogonal overlay code (OCC) for transmitting message 3 (MSG 3); and components for transmitting MSG 3 to the network device based on the first configuration information.

[0010] In a sixth aspect, an apparatus is provided, comprising: components for transmitting downlink control information (DCI) for scheduling a random access response (RAR) to an end device at a network device; components for transmitting the RAR to the end device based on the DCI, wherein at least one of the DCI or the RAR includes first configuration information associated with an orthogonal overlay code (OCC) for transmitting message 3 (MSG 3); and components for receiving MSG 3 from the end device based on the first configuration information.

[0011] In a seventh aspect, a non-transitory computer-readable medium is provided, comprising program instructions for causing a device to perform at least the method according to any one of the third to fourth aspects described above.

[0012] In an eighth aspect, a computer program including instructions is provided, which, when executed by an apparatus, cause the apparatus to at least: receive downlink control information (DCI) for scheduling a random access response (RAR) from a network device; receive the RAR from the network device based on the DCI, wherein at least one of the DCI or the RAR includes first configuration information associated with an orthogonal overlay code (OCC) for transmitting message 3 (MSG 3); and transmit MSG 3 to the network device based on the first configuration information.

[0013] In a ninth aspect, a computer program including instructions is provided, which, when executed by an apparatus, cause the apparatus to at least: transmit downlink control information (DCI) for scheduling a random access response (RAR) to a terminal device; transmit the RAR to the terminal device based on the DCI, wherein at least one of the DCI or the RAR includes first configuration information associated with an orthogonal overlay code (OCC) for transmitting message 3 (MSG 3); and receive MSG 3 from the terminal device based on the first configuration information.

[0014] In a tenth aspect, a terminal device is provided. The terminal device includes a first receiving circuit system configured to receive downlink control information (DCI) for scheduling a random access response (RAR) from a network device at the terminal device; a second receiving circuit system configured to receive the RAR from the network device based on the DCI, wherein at least one of the DCI or the RAR includes first configuration information associated with an orthogonal overlay code (OCC) for transmitting message 3 (MSG 3); and a transmission circuit system configured to transmit MSG 3 to the network device based on the first configuration information.

[0015] In an eleventh aspect, a network device is provided. The network device includes a first transmission circuit system configured to transmit downlink control information (DCI) for scheduling a random access response (RAR) to an end device at the network device; a second transmission circuit system configured to transmit the RAR to the end device based on the DCI, wherein at least one of the DCI or the RAR includes first configuration information associated with an orthogonal coverage code (OCC) for transmitting message 3 (MSG 3); and a receiving circuit system configured to receive MSG 3 from the end device based on the first configuration information.

[0016] It should be understood that the summary portion of this disclosure is not intended to identify key or essential features of the embodiments thereof, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0017] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which:

[0018] Figure 1A The illustration shows an example communication network in which embodiments of the present disclosure may be implemented;

[0019] Figure 1B The illustration shows an example of a MAC payload consisting of a MAC header and a MAC RAR.

[0020] Figure 1C and Figure 1D The diagram illustrates the MAC RAR payload structure for eMTC.

[0021] Figure 1E and Figure 1F The diagram illustrates the MAC RAR payload structure for NB-IoT.

[0022] Figure 1G The diagram illustrates the random access symbol group;

[0023] Figure 2 A flowchart is shown that illustrates an example process for OCC configuration for random access MSG 3 according to some embodiments of the present disclosure;

[0024] Figure 3 The illustration shows an example process for OCC configuration for random access MSG 3 according to some embodiments of the present disclosure;

[0025] Figure 4 The illustration shows another example process for OCC configuration for random access MSG 3 according to some embodiments of the present disclosure;

[0026] Figure 5 The illustration shows a flowchart of a method implemented at a terminal device according to some embodiments of the present disclosure;

[0027] Figure 6 The illustration shows a flowchart of a method implemented at a network device according to some embodiments of the present disclosure;

[0028] Figure 7 A simplified block diagram of an apparatus suitable for implementing embodiments of the present disclosure is illustrated; and

[0029] Figure 8 A block diagram of an example computer-readable medium according to some embodiments of the present disclosure is illustrated.

[0030] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0031] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. This disclosure described herein can also be implemented in various other ways besides those described below.

[0032] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0033] References to "an embodiment," "an embodiment," "an example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed that in conjunction with other embodiments (whether explicitly described or not) affecting such a feature, structure, or characteristic is within the knowledge of those skilled in the art.

[0034] It should be understood that although the terms “first” and “second”, etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0035] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including,” when used herein, specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. As used herein, “at least one of the following: ” and “at least one of ” and similar wording (where the list of two or more elements is connected by “and” or “or”) means at least any one of these elements, or at least any two or more of these elements, or at least all of these elements.

[0036] As used in this application, the term "circuit system" may refer to one or more or all of the following: (a) Hardware circuit implementation only (such as implementation in analog and / or digital circuit systems only), and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits with software / firmware; and (ii) Any portion of the hardware processor(s) having software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions, and (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to function, but may be absent when operation does not require software.

[0037] This definition of circuit system applies to all uses of the term in this application, including in any claim. As another example, as used in this application, the term circuit system also covers only hardware circuitry or a processor (or processors), or a portion of hardware circuitry or a processor and its accompanying software and / or firmware implementation. The term circuit system also covers (e.g., and if applicable to a particular claim element) baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0038] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as 5G New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocols, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, future fifth-generation (5G) communication protocols, and / or any other protocols currently known or to be developed in the future. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communication, future types of communication technologies and systems will naturally exist, and this disclosure can be embodied using these future types of communication technologies and systems. This should not be construed as limiting the scope of this disclosure to the systems described above.

[0039] As used herein, the term "network device" refers to a node in a communication network through which terminal devices access the network and receive services. Network devices can refer to base stations (BS) or access points (APs), such as Node B (NodeB or NB), evolved Node B (eNodeB or eNB), NR NB (also known as gNB, a base station in 5G systems), Remote Radio Unit (RRU), Radio Header (RH), Remote Radio Header (RRH), relay, low-power nodes (such as femtoseconds, picoseconds), etc., depending on the terminology and technology used.

[0040] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not a limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices can include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal equipment", "communication equipment", "terminal", "user equipment" and "UE" are used interchangeably.

[0041] In some solutions, satellite access has been introduced for new radio (NR) users, as well as for enhanced machine-type communications (eMTC) and narrowband Internet of Things (NB-IoT) devices. The technical specifications in these solutions are functional and enable the deployment of real-time satellite networks for these types of devices. However, due to the limited spectrum available for deployment and the very large satellite footprint (very large cells), these systems may quickly reach their capacity limits. Therefore, non-terrestrial network (NTN) systems require new solutions that can scale system capacity. Regarding the need for uplink capacity enhancement, NB-IoT NTN is currently being deployed in the field. In these early and upcoming deployments, it is clear that IoT-NTN, especially NB-IoT, will have to support huge capacity in terms of the number and types of UEs, some of which have inferior characteristics compared to other UEs (e.g., low-cost devices, wearables, etc.). Therefore, the multiplexing of UEs using orthogonal coverage codes (OCC) for narrowband physical uplink shared channel (NPUSCH) format 1 and narrowband physical random access channel (NPRACH) should be investigated, and whether this is beneficial should be specified. Therefore, to unlock the additional UL capacity potential, methods for decoupling UL from DL as much as possible need to be identified. The goal of the above aspects is to support capacity enhancements for the uplink. Where beneficial, enhancements should be made to enable multiple UE multiplexing in a single 3.75kHz or 15kHz subcarrier via orthogonal coverage codes (OCC) for NPUSCH format 1 and NPRACH (e.g., up to a minimum of 4 and the maximum allowed by UL and DL signaling). Multi-tone support for 15kHz SCS should also be considered.

[0042] In some solutions, the MSG 2 RAR lacks spare bits to notify the UE which OCCs will be applied to MSG 3 PUSCH transmissions. To address this issue, new solutions are proposed in some embodiments of this disclosure. For example, in some embodiments, a solution regarding how the eNB signals the OCC code used for (N)PUSCH transmissions of message (MSG) 3 is proposed for uplink capacity enhancement, thereby improving communication performance. The principles and embodiments of this disclosure will be described in detail below with reference to the accompanying drawings.

[0043] First refer to Figure 1AThe illustration depicts an example communication system 100 (or communication network) in which embodiments of the present disclosure may be implemented. System 100 (e.g., communication network) includes multiple network devices and terminal devices, such as terminal device 101 and network device 103. During a random access process, terminal device 101 and other terminal devices (e.g., terminal device 102) may initiate random access to network device 103. Network device 103 may allocate resources for successfully accessed terminal devices. By using orthogonal overlay codes (OCC), more than one terminal device may use the same allocated resources to transmit message 3 (MSG 3) to network device 103. Network device 103 may communicate with (multiple) terminal devices (e.g., terminal device 101) to transmit some configuration associated with the OCC.

[0044] It should be understood that the number of network devices and terminal devices is for illustrative purposes only and does not imply any limitation. System 100 may include any suitable number of network devices and terminal devices appropriate for implementing embodiments of this disclosure.

[0045] Communication in communication system 100 can be implemented according to any suitable communication protocol(s), including but not limited to cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), and fifth-generation (5G), wireless local area network communication protocols such as IEEE 802.11, and / or any other protocols currently known or to be developed in the future. Furthermore, communication can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Discrete Fourier Transform Spread Spectrum OFDM (DFT-s-OFDM), and / or any other technologies currently known or to be developed in the future.

[0046] To clearly describe the embodiments of this disclosure, some solutions regarding the random access procedure will be introduced below. In some solutions to the random access procedure, the network will configure multiple random access opportunities and random access preambles in the system information. A UE attempting to access the system (or issuing a request) will initiate a random access procedure including steps 1 to 4.

[0047] Step 1: Transmission of Message (MSG) 1 (from UE to base station). During this process, the UE randomly selects one available random access preamble from a subset of available random access preambles (when a contention-based RA is used), and transmits the preamble in one of the UL resources reserved as the RA timing. The UE begins monitoring the PDCCH resource scrambled with RA-RNTI, which is allocated a PDSCH with RAR. Since RA-RNTI depends only on its corresponding RACH timing (i.e., the SFN of the timing in which the preamble is transmitted), multiple UEs can monitor and decode the same RA-RNTI.

[0048] Step 2: Transmission of MSG 2 (from base station to UE). During this period, the NW will send a Random Access Response (RAR) to the received random access attempt. This RAR includes: power control information, timing advance command, UL scheduling of MSG 3, and a temporary C-RNTI (temporary UE ID). As mentioned above, multiple UEs can monitor the same RA-RNTI. Several UEs may attempt RA at the same RA timing and wait for the RAR. To distinguish its RAR from those transmitted to other UEs attempting different preambles at the same RA timing, the UE needs to indicate in the MAC sub-header carrying the RAR whether the RAPID (Random Access Preamble ID) is the same as the RAPID selected by the UE when MSG 1 was transmitted.

[0049] See Figure 1B Here is an example of how step (2) of the process is completed. After reading the MAC sub-header with the corresponding RAPID, the UE will locate the corresponding MAC payload (i.e., MAC RAR) and read the corresponding fields. Figure 1BThe diagram illustrates the header and RAR payload. The MAC header is of variable size and consists of the following fields: E, T, R, BI, and RAPID. The E field (i.e., the extension field) is a flag indicating whether there are additional fields in the MAC header. The E field is set to "1" to indicate that at least another set of E / T / RAPID fields follows. The E field is set to "0" to indicate that MAC RAR or padding begins with the next byte. The T field (i.e., the type field) is a flag indicating whether the MAC subheader contains a random access ID or a backoff indicator. The T field is set to "0" to indicate the presence of a backoff indicator field (BI) in the subheader. The T field is set to "1" to indicate the presence of a random access preamble ID field (RAPID) in the subheader. The R field (i.e., the reserved bit) is set to "0". The BI field (i.e., the backoff indicator field) identifies overload conditions in the cell. The BI field is 4 bits in size. The RAPID field (i.e., the Random Access Preamble Identifier field) identifies the transmitted random access preamble (see Section 5.1.3 of 3GPP TS 36.321). The RAPID field is 6 bits in size. If the UE is already in connected mode, i.e., if the UE already has an assigned C-RNTI, the UE ignores the provisional C-RNTI field and continues to the next step (or continues the connection in the absence of contention for the RA). It should be noted that the RAR content depends on the device type and PRACH format.

[0050] Step 3: Transmission of MSG 3 (from UE to base station). When message 3 is required (based on contention RA), it is transmitted by the UE using the scheduling information provided in MSG 2. The message is scrambled by the UE's T-CRNTI. If the contention is successfully resolved in MSG 4 for this UE, the UE will use the T-CRNTI as the C-RNTI, which is used to identify the UL / DL resources addressed / from the UE, and scramble this information.

[0051] Step 4: Transmission of MSG 4 (from BS to UE). Typically, MSG 4 is used to resolve contention-based processes when necessary.

[0052] Figure 1C and Figure 1D The diagram illustrates the MAC RAR payload structure used in eMTC. Specifically, Figure 1C An example of the MACRAR structure is shown. Figure 1D An example of MAC RAR for PRACH enhanced coverage level 2 or 3 is shown. Figure 1E and Figure 1F The diagram illustrates the MAC RAR payload structure for NB-IoT. Specifically, Figure 1E An example of a MAC RAR for NB-IoT UE is shown. Figure 1F An example of a MAC RAR for an NB-IoT UE using PRACH preamble format 2 is shown. Figures 1C to 1F As shown, the MAC RAR has a fixed size and consists of the following fields. R (i.e., reserved bit) is set to “0”. For BL UE or CE UE, this bit is set to “1” to indicate that the UL grant in the random access response is for EDT. The timing advance command field indicates the index value TA (0, 1, 2…1282) of the amount of timing adjustment that is used to control the MAC entity to apply (see TS 36.213[2] Section 4.2.3), except for NB-IoT UE using preamble format 2, where the timing advance command field indicates the index value TA (0, 1, 2…1536). The size of the timing advance command field is 11 bits. The uplink grant field indicates the resources that will be used on the uplink (see TS 36.213[2] Section 6.2, or for NB-IoT UE, see TS 36.213[2] Section 16.3.3). The UL grant field is 20 bits in size, except for NB-IoT UEs, where the UL grant field is 15 bits in size, and except for BL UEs and UEs in Enhanced Coverage Level 2 or 3, where the UL grant field is 12 bits in size. The ER (i.e., Extended RAPID bits) indicates the two least significant bits of the Extended RAPID used when PRACH preamble format 2 is transmitted. The Temporary C-RNTI indicates a temporary identifier used by the MAC entity during random access. The Temporary C-RNTI field is 16 bits in size. The MAC RAR is octet aligned.

[0053] For eMTC CE Mode A and CE Mode B, DCI formats 6-1A and 6-1B will be used to schedule RAR. For NB-IoT, DCI format N1 will be used to schedule RAR. In DCI formats 6-1A / 1B and N1, some DCI fields are retained when scrambled using RA-RNTI. This means that it is possible to redefine these fields when OCC is supported in PRACH. When format 6-1A CRC is scrambled using RA-RNTI, the following fields are retained: HARQ procedure number, new data indicator, downlink allocation index, and HARQ-ACK resource offset. When format 6-1B CRC is scrambled using RA-RNTI, the following fields are retained: HARQ procedure number, new data indicator, and HARQ-ACK resource offset. When format N1 CRC is scrambled using RA-RNTI or G-RNTI, the following fields are reserved for RA-RNTI but not for G-RNTI: New Data Indicator and HARQ-ACK Resource.

[0054] In the NPRACH time-domain structure, the preamble consists of a sequence of 3-5 identical symbols, which, combined with the cyclic prefix, form a symbol group. For the time and frequency structure of a narrowband physical random access channel, the physical layer random access preamble is based on a single subcarrier frequency-hopping symbol group. The symbol group... Figure 1G The diagram shows a structure with a length of... The cyclic prefix and total length are It consists of a sequence of N identical symbols. The total number of symbol groups in the preamble repetition unit is determined by... P The number of consecutive time symbol groups is represented by... G The parameters for the random access preamble used in frame structure 1 are given in Table 1. Table 1

[0055] For NPUSCH, a resource element consists of 2-16 time slots, with each time slot containing 7 symbols. Resource elements are used to describe the mapping from NPUSCH to resource elements. A resource element is defined in the time domain... SC-FDMA symbols and frequency domain One consecutive subcarrier. Used for frame structure type 1. , ,as well as The supported combinations can be found in Table 2. Table 2

[0056] Based on the above, the NPRACH preamble is based on grouping 3-5 symbols and 1 CP, while the NPUSH preamble is based on grouping at least 2 time slots, each consisting of 7 symbols. This means that the OCC length used for NPRACH can not match the OCC length of NPUSH. For example, if 5 symbols are used for NPRACH, it does not match the number of symbols in any type of NPUSCH transmission. This means that the UE will not be expected to apply the same OCC configuration on NPRACH and NPUSCH, because the length applied on NPRACH cannot be reused on NPUSCH. Similarly, in eMTC / LTE-M, the resource block used for PUSCH consists of 7 symbols (with normal CP) and 6 symbols (with extended CP), while PRACH is spaced [1-2]. 24576 On the Ts (preamble format 0-3) sequence. 7 symbols (one time slot) correspond to 15360. Ts, and therefore the mapping between PUSCH and PRACH is also difficult. Furthermore, multiple preambles can exist using the same OCC number (e.g., preambles #A and #B both use OCC#1 and OCC#2). In a RAR used to allocate PUSCH resources for MSG 3 corresponding to preambles #A and #B, allocating them in the same PUSCH resources (i.e., the same subframe and the same PRB) but using different OCCs is a flexibility that NW can achieve (e.g., the PUSCH OCC numbers for preamble #A can be OCC#1 and OCC#2, while the PUSCH OCC numbers for preamble #B can be OCC#3 and OCC#4). In other words, the OCC number used in the preamble can be different from the OCC number used in the MSG 3 PUSCH. This means that the OCC number used for the MSG 3 PUSCH may need to be indicated in the RAR, whether explicitly or implicitly.

[0057] In some solutions, the PUSCH resource for MSG 3 is scheduled by RAR in the UL authorization field, which cannot indicate OCC. For example... Figures 1C to 1F As explicitly defined in the MAC payload definition, there are no available bits to signal the UE that the OCC should be applied to message 3 transmission on (N)PUSCH. Similarly, there are no spare bits in the MAC subheader.

[0058] In light of these analyses and considerations, a novel solution is proposed in some embodiments of this disclosure. In some examples, the base station (e.g., eNB) can notify the UE how to apply OCC on the (N)PUSCH used for message 3 transmission. In principle, this can be independent of whether OCC is used on the (N)PRACH. In some other examples, the base station can notify the UE whether to use OCC on the (N)PUSCH used for message 3 transmission. Details of some solutions in this disclosure can also be found in [reference]. Figures 2 to 4 The example shown.

[0059] Now for reference Figure 2 This illustrates the process for OCC configuration for Random Access MSG 3 according to some embodiments of this disclosure. For example... Figure 2 As shown, in process 200, terminal device 101 and network device 103 are involved. In some examples, terminal device 101 may be a UE or another terminal device. Network device 103 may be a base station, such as an eNB or gNB. In some embodiments, MSG 3 may be a third message transmitted during the four-step random access process. For example, MSG 3 may be a message transmitted on the uplink shared channel (UL-SCH) that contains a Cell Radio Network Temporary Identifier (C-RNTI), a Media Access Control Unit (MAC CE), or a Common Control Channel Service Data Unit (CCCH SDU), which is submitted from a higher layer as part of the random access process and associated with a UE contention resolution identifier.

[0060] In process 200, network device 103 may transmit (202) downlink control information (DCI) 205 for scheduling a random access response (RAR) 215 to terminal device 101. Terminal device 101 may receive (204) the downlink control information (DCI) 205 from network device 103. Network device 103 may transmit (206) the RAR 215 to terminal device 101 based on the DCI 205. On the terminal device 101 side, terminal device 101 may receive (208) the RAR 215 from network device 103 based on the DCI 205. In some examples, the DCI 205 includes first configuration information associated with an orthogonal overlay code (OCC) for transmitting message 3 (MSG 3) 225. In other examples, the RAR 215 includes first configuration information associated with an OCC for transmitting MSG 3 225.

[0061] In some examples, the first configuration information may include an index of the first OCC among multiple OCCs, or an indication that no OCC will be applied to the transmission of MSG 3 225. The first OCC among multiple OCCs will be applied to the transmission of MSG 3 225. The index of the first OCC may be the identifier (ID) of the first OCC.

[0062] In some examples, the first configuration information may be carried in the first temporary connection radio network temporary identifier (TC-RNTI) in RAR 215. For example, when the UE has received the MAC RAR 215, the UE will know which OCCs will be applied to the (N)PUSCH of MSG 3 225. Alternatively or alternatively, the first configuration information may be carried in a set of bits in DCI 205, such as at least one first bit in DCI 205, or at least one second bit in DCI 205, or both. For example, when the UE has received DCI 205, the UE will know which OCCs will be applied to the (N)PUSCH of MSG 3 225. Details will be described below.

[0063] In some examples, the initial configuration information may be determined based on the first TC-RNTI in RAR 215, the OCC length or the number of multiple OCCs, and a mapping rule from the TC-RNTI to the OCC index. For example, the mapping rule could be: OCCID based on "TC-RNTI mod OCC length". In some examples, the first TC-RNTI mapped to the index of the first OCC among the multiple OCCs indicates that the first OCC will be applied to the transmission of MSG 3 225. In some examples, the first TC-RNTI mapped to a value different from the index of the OCCs among the multiple OCCs indicates that no OCC will be applied to the transmission of MSG 3 225. For example, a value determined based on the mapping rule that differs from any OCC ID among the multiple OCC IDs (OCC IDs of multiple OCCs) indicates that no OCC will be applied to the transmission of MSG 3 225.

[0064] In some examples, the mapping rule indicates that the OCC index can be based on TC-RNTI and parameters. For example, such parameters could be the OCC length, the number of OCCs, the OCC length plus 1, the number of OCCs plus 1, or any combination thereof. For instance, the mapping rule could be: OCC ID based on "TC-RNTI mod (OCC length + 1)". The OCC length or the number of OCCs can be indicated in DCI 205; that is, network device 103 can indicate the OCC length or the number of OCCs to terminal device 101 in DCI 205. Alternatively, the OCC length or the number of OCCs can be predetermined, for example, specified in a protocol.

[0065] In some examples, the mapping rule applies to multiple TC-RNTIs. Multiple TC-RNTIs can correspond to multiple value ranges. In other examples, the mapping rule applies to a subset of multiple TC-RNTIs. In other words, the mapping rule applies to (multiple) TC-RNTIs within one value range of multiple TC-RNTIs. (Multiple) TC-RNTIs within one value range of multiple TC-RNTIs can be considered a subset of multiple TC-RNTIs. For example, the functions "TC-RNTI mod OCC length" or "TC-RNTI mod (OCC length + 1)" only apply to a subset of TC-RNTIs. In such examples, i.e., the mapping rule applies to a subset of multiple TC-RNTIs, the first TC-RNTI of a TC-RNTI that is not a subset of multiple TC-RNTIs can indicate that no OCC will be applied to the transmission of MSG 3 225.

[0066] In some examples, the initial configuration information can be determined based on the first TC-RNTI in RAR 215 and the mapping rules from the value range of the TC-RNTI to the OCC index. For example, RAR 215 can instruct the TC-RNTI range [X:Y] to apply OCC code 1, the range [Y+1:Z] to apply OCC code 2, and so on. Based on the first TC-RNTI and the mapping rules, the terminal device 101 can know which OCCs will be applied to the (N)PUSCH of MSG 3 225.

[0067] In some examples, the mapping rules in the above examples can be configured by network device 103, meaning that network device 103 can configure mapping rules to terminal device 101. Alternatively, the mapping rules in the above examples can be predefined. For example, the eNB (or specification) can define mapping rules from TC-RNTI to the OCC of MSG 3 225. TC-RNTI can be included in the MAC RAR payload and controlled by the network, i.e., it can also control the OCC.

[0068] In some examples, first configuration information may be carried in at least one first bit in DCI 205, which indicates the index of the first OCC to be applied to the transmission of MSG 3 225. For example, the eNB may use one or more reserved bits in DCI 205, which schedule RAR(MSG 2) 215, to define the OCC of MSG 3 225. As described above, the relevant DCI is format 6-1A, 6-1B, and N1. DCI 205 is received in time resources and frequency resources. In some examples, at least one of time resources or frequency resources and at least one first bit in DCI 205 indicate the index of the first OCC to be applied to the transmission of MSG 3 225. For example, if the number of OCCs exceeds the number of bits available in DCI 205, in this scenario, network device 103 may define that DCI 205 transmitted in one time / frequency resource corresponds to a range of OCCs, while DCI 205 in another resource corresponds to another range of OCCs. In some examples, the first configuration information is carried in at least one second bit in DCI 205, which indicates whether OCC will be applied to the transmission of MSG 3 225. For example, at least one second bit as a flag is used to indicate whether OCC is applied to the transmission of MSG 3 225.

[0069] In some examples, the first configuration information may be determined based on the difference between the OCC used to transmit MSG 3 225 and the OCC used to transmit message 1 (MSG 1). This difference may be indicated in DCI 205 or RAR 215 or both.

[0070] In some examples, network device 103 may transmit third configuration information associated with the OCC used to transmit MSG 1 to terminal device 101. Terminal device 101 may receive the third configuration information from network device 103. The OCC used to transmit MSG 1 may be different from the OCC used to transmit MSG 3 225.

[0071] In some examples, network device 103 may transmit second configuration information to terminal device 101 indicating whether OCC will be applied to the transmission of MSG 1. Terminal device 101 may receive the second configuration information from network device 103. The second configuration information may also be used to indicate whether OCC will be applied to the transmission of MSG 3 225.

[0072] In some examples, after receiving MSG 1 from terminal device 101, network device 103 may check whether the OCC used for transmitting MSG 3 225 is different from the OCC used for transmitting MSG 1, and based on the difference between the OCC used for transmitting MSG 3 225 and the OCC used for transmitting MSG 1, indicate first configuration information in at least one of DCI 205 or RAR 215.

[0073] In some examples, after receiving MSG 1 from terminal device 101, network device 103 may check whether the OCC used for transmitting MSG 3 225 and the OCC used for transmitting MSG 1 are adjusted to be the same, and based on the fact that the OCC used for transmitting MSG 3 225 and the OCC used for transmitting MSG 1 are not adjusted to be the same, indicate first configuration information in at least one of DCI 205 or RAR 215.

[0074] In some examples, based on the fact that the OCC used to transmit MSG 3 225 is different from the OCC used to transmit MSG 1, or based on the fact that the OCC used to transmit MSG 3 225 and the OCC used to transmit MSG 1 were not adjusted to be the same, or based on both of the above, at least one of DCI 205 or RAR 215 includes first configuration information.

[0075] In the example above, since the resources used for (N)PRACH and (N)PUSCH are different, different OCC lengths are required for MSG 1 and MSG 3 225. The network can change or reconfigure the OCC for MSG 3 225 by indicating the difference between the OCC used to transmit MSG 3 225 and the OCC used to transmit MSG 1, or a new absolute value of the OCC used to transmit MSG 3 225, or a mapping rule, etc. Alternatively, for example, when MSG 1 is received, network device 103 can check whether the OCCs used for (N)PRACH and (N)PUSCH can be adjusted so that the same OCC can be used. If not, network device 103 can indicate the first configuration information described above.

[0076] Continue to refer to Figure 2Terminal device 101 can transmit (212) MSG3 225 to network device 103 based on the first configuration information. Network device 103 can receive (214) MSG 3 225 from terminal device 101. Using example procedure 200, a solution for how network devices signal the OCC code for the transmission of MSG 3 is proposed for uplink capacity enhancement, thereby improving communication performance. In some aspects, for example, referring to the example above, the solution is about the OCC for MSG 3. The indication (i.e., the first configuration information) is used in the explicit indication / configuration in the DCI for RAR or RAR content so that the network device (e.g., Node B) can select the OCC for the MSG 3 of the terminal device (e.g., UE) to avoid additional conflicts from the UE and speed up the random access procedure. In addition, the mapping between OCC and indication can be one-to-many TC-RNTI so as to have more distinction between UEs with different motivations. Some details of the solution will be described further below.

[0077] Figure 3 The illustration depicts an example procedure for OCC configuration for Random Access MSG 3 according to some embodiments of the present disclosure. In procedure 300, as an example, terminal device 101 may be a UE. Network device 103 (which may be referred to as the network) may be an eNB.

[0078] As shown in process 300, network device 103 can transmit (302) a configuration 305 for the TC-RNTI mapping to the OCC, and terminal device 101 can receive (304) the configuration 305. The OCC is associated with the transmission of MSG 3 345. The configuration 305 for the TC-RNTI mapping to the OCC can be regarded as an indication of the OCC and can be implemented in various ways. For example, network device 103 can define the OCC ID based on "TC-RNTI mod OCC length". In some examples, the OCC length can be extended by 1, such as network device 103 indicating that no OCC will be applied to the transmission of MSG 3 345. For example, the OCC ID is based on "TC-RNTI mod (OCC length + 1)", where an additional value different from the OCC ID in the modulo result means "no OCC applied".

[0079] In some examples, network device 103 can be configured to apply the "mod OCC length" or "TC-RNTI mod (OCC length + 1)" function to multiple TC-RNTIs. For example, the TC-RNTI configured for terminal device 101 can be one of multiple TC-RNTIs, and the mapping rule for the TC-RNTI mapping to OCC in configuration 305 can apply to multiple TC-RNTIs. In some other examples, network device 103 can be configured to apply the "TC-RNTI mod OCC length" or "TC-RNTI mod (OCC length + 1)" function only to a subset of TC-RNTIs. That is, the mapping rule only applies to (multiple) TC-RNTIs within one value range of multiple value ranges of multiple TC-RNTIs. For example, the mapping rule for the TC-RNTI mapping to OCC in configuration 305 can apply to a subset of multiple TC-RNTIs. In some examples, network device 103 may (e.g., in system information) signal that the TC-RNTI range [X:Y] applies OCC code 1, the range [Y+1:Z] applies OCC code 2, and so on. In other words, the mapping rule for the TC-RNTI to OCC mapping can be from the range of TC-RNTI values ​​to the OCC index. In such examples, the OCC index can be the OCC ID.

[0080] Terminal device 101 may transmit (306) a random access preamble 315, and network device 103 may receive (308) the random access preamble 315. Network device 103 may transmit (310) a scheduling random access response (RAR) 335, which is a DCI 325. On the terminal device 101 side, terminal device 101 may receive (312) the DCI 325. Then, network device 103 may transmit (314) the RAR 335, which includes the MSG 3 scheduling grant and the TC-RNTI. In some examples, the TC-RNTI may be configured by network device 103. Terminal device 101 may receive (316) the random access response 335. Terminal device 101 may determine (318) the OCC applied on MSG 3 345 based on the TC-RNTI of the RAR 335 and the received configuration 305. Terminal device 101 can use the indicated OCC to transmit (320) MSG 3 345. On the network device 103 side, network device 103 can receive (322) MSG 3 345.

[0081] In some examples, DCI 325 can define the total number of OCC codes used for MSG 3 345 (e.g., 4 or 8). The UE will then know (based on the configured rules) how to interpret the TC-RNTI. In this way, the network can be enabled to adjust the number of OCC codes according to the current PUSCH load.

[0082] Figure 4 The illustration shows another example procedure for OCC configuration for Random Access MSG 3 according to some embodiments of the present disclosure. In procedure 400, as an example, terminal device 101 may be a UE. Network device 103 (which may be referred to as the network) may be an eNB.

[0083] As shown in process 400, terminal device 101 may transmit (402) a random access preamble 405, and network device 103 may receive (404) the random access preamble 405. Network device 103 may transmit (406) a Distributed Access Control (DCI) 415 of a Scheduled Random Access Response (RAR) 425. DCI 415 includes an indication of the OCC for MSG 3 435. On the terminal device 101 side, terminal device 101 may receive (408) DCI 415. In some examples, one or more reserved bits in DCI 415 may be used to indicate the OCC. In some examples, this corresponds to 2 bits if the target defines multiplexing for at least 4 UEs, i.e., at least 4 OCCs are required. Furthermore, 3 bits are required for the above example if a flag is needed to indicate whether the OCC will be used.

[0084] In some other examples, such indications may also be given elsewhere, for example, in a PRACH configuration, or in connection with whether an OCC is used for MSG 1. In other words, an indication of whether an OCC is applied to a transmission of MSG 1 may also be used to indicate whether an OCC is applied to a transmission of MSG 3 435. In some examples, if the number of OCCs exceeds the number of bits available in DCI 415, network device 103 may define that DCI 415 transmitted in one time / frequency resource corresponds to OCCs in range [A:B], while DCI 415 in another resource corresponds to OCCs in range [C:D]. For example, if four OCCs are required, but only one bit is available in DCI 415, then range A:B corresponds to 0:1, and range C:D corresponds to 2:3. Then, depending on when DCI 415 is transmitted, a single bit in DCI 415 may be defined as 0 and 2 or 1 and 3.

[0085] Network device 103 can transmit (410) a RAR 425 including a scheduling authorization for MSG 3. Terminal device 101 can receive (412) the RAR 425. Based on a DCI 415 indicating an OCC including MSG 3 435, terminal device 101 can determine (414) the OCC to be applied to MSG 3 435. Terminal device 101 can use the indicated OCC to transmit (416) MSG 3 435. On the network device 103 side, network device 103 can receive (418) MSG 3 435.

[0086] Figure 5 The illustration shows a flowchart of a method implemented at a terminal device according to some embodiments of the present disclosure. The terminal device performing method 500 may be an example of the terminal device 101 described above. The network device mentioned in method 500 may be an example of network device 103.

[0087] At box 510, the terminal device may receive downlink control information (DCI) for scheduling a random access response (RAR) from the network device. At box 520, the terminal device may receive the RAR from the network device based on the DCI. At least one of the DCI or RAR includes first configuration information associated with an orthogonal overlay code (OCC) for transmitting message 3 (MSG 3). At box 530, the terminal device may transmit MSG 3 to the network device based on the first configuration information.

[0088] In some embodiments, the first configuration information includes: an index of a first OCC among a plurality of OCCs, wherein the first OCC will be applied to the transmission of MSG 3; or an indication that no OCC will be applied to the transmission of MSG 3.

[0089] In some embodiments, the first configuration information is carried in the following: a first temporary connection radio network temporary identifier (TC-RNTI) in the RAR; or a bit set in the DCI; or both.

[0090] In some embodiments, the first configuration information is determined based on the following: the first TC-RNTI in the RAR; the OCC length or the number of multiple OCCs; and the mapping rules for the index from the TC-RNTI to the OCCs.

[0091] In some embodiments, a first TC-RNTI mapped to the index of a first OCC among a plurality of OCCs indicates that the first OCC will be applied to the transmission of MSG 3. Alternatively, a first TC-RNTI mapped to a value different from the index of an OCC among a plurality of OCCs indicates that no OCC will be applied to the transmission of MSG 3.

[0092] In some embodiments, the mapping rule applies to multiple TC-RNTIs. Alternatively, the mapping rule applies to at least one TC-RNTI within one of a range of values ​​for multiple TC-RNTIs.

[0093] In some embodiments, a first TC-RNTI that is not in one of the multiple value ranges of multiple TC-RNTIs indicates that no OCC will be applied to the transmission of MSG 3, wherein the mapping rule applies to (multiple) TC-RNTIs in one of the multiple value ranges of multiple TC-RNTIs.

[0094] In some embodiments, the mapping rule indicates that the OCC index is based on TC-RNTI and at least one of the following: OCC length; number of multiple OCCs; OCC length plus 1; or number of multiple OCCs plus 1.

[0095] In some embodiments, the length of the OCC or the number of multiple OCCs is indicated or predetermined in the DCI.

[0096] In some embodiments, the first configuration information is determined based on the following: the first TC-RNTI in the RAR; and the mapping rules from the value range of the TC-RNTI to the OCC index.

[0097] In some embodiments, the mapping rules are configured by the network device or are predetermined.

[0098] In some embodiments, the first configuration information is carried in at least one first bit in the DCI, indicating the index of the first OCC to be applied to the transmission of MSG 3.

[0099] In some embodiments, the first configuration information is carried in at least one second bit in the DCI that indicates whether OCC will be applied to the transmission of MSG 3.

[0100] In some embodiments, the terminal device may receive second configuration information from the network device indicating whether OCC will be applied to the transmission of message 1 (MSG 1), wherein the second configuration information is also used to indicate whether OCC will be applied to the transmission of MSG 3.

[0101] In some embodiments, the terminal device may receive third configuration information from the network device associated with the OCC used to transmit MSG 1, wherein the OCC used to transmit MSG 1 is different from the OCC used to transmit MSG 3.

[0102] In some embodiments, the first configuration information is determined based on the difference between the OCC used for transmitting MSG 3 and the OCC used for transmitting MSG 1, wherein the difference is indicated in at least one of DCI or RAR.

[0103] In some embodiments, at least one of the DCI or RAR includes first configuration information based on at least one of the following: the OCC used for transmitting MSG 3 is different from the OCC used for transmitting MSG 1; or the OCC used for transmitting MSG 3 and the OCC used for transmitting MSG 1 are not adjusted to be the same.

[0104] In some embodiments, the DCI is received in time resources and frequency resources. At least one of the time resources or frequency resources and at least one first bit in the DCI 205 indicates the index of the first OCC to be applied to the transmission of MSG 3.

[0105] Figure 6 The illustration shows a flowchart of a method implemented at a network device according to some embodiments of the present disclosure. The network device performing method 600 may be an example of network device 103 described above. The terminal device mentioned in method 600 may be an example of terminal device 101.

[0106] At box 610, the network device may transmit downlink control information (DCI) for scheduling a random access response (RAR) to the terminal device. At box 620, the network device may transmit the RAR to the terminal device based on the DCI, wherein at least one of the DCI or RAR includes first configuration information associated with an orthogonal coverage code (OCC) for transmitting message 3 (MSG 3). At box 630, the network device may receive MSG 3 from the terminal device based on the first configuration information.

[0107] In some embodiments, the first configuration information includes: an index of a first OCC among a plurality of OCCs, wherein the first OCC will be applied to the transmission of MSG 3; or an indication that no OCC will be applied to the transmission of MSG 3; or both.

[0108] In some embodiments, the first configuration information is carried in the following: a first temporary connection radio network temporary identifier (TC-RNTI) in the RAR; or a set of bits in the DCI; or a combination thereof.

[0109] In some embodiments, the first configuration information is determined based on the first TC-RNTI in the RAR, the length of the OCC or the number of multiple OCCs, and the mapping rules of the index from the TC-RNTI to the OCC.

[0110] In some embodiments, a first TC-RNTI mapped to the index of a first OCC among a plurality of OCCs indicates that the first OCC will be applied to the transmission of MSG 3, or a first TC-RNTI mapped to a value different from the index of an OCC among a plurality of OCCs indicates that no OCC will be applied to the transmission of MSG 3.

[0111] In some embodiments, the mapping rule applies to multiple TC-RNTIs; or the mapping rule applies to at least one TC-RNTI in one of a range of values ​​for multiple TC-RNTIs.

[0112] In some embodiments, a first TC-RNTI that is not in one of the multiple value ranges of a plurality of TC-RNTIs indicates that no OCC will be applied to the transmission of MSG 3, wherein the mapping rule applies to at least one TC-RNTI in one of the multiple value ranges of a plurality of TC-RNTIs.

[0113] In some embodiments, the mapping rule indicates that the OCC index is based on TC-RNTI and at least one of the following: OCC length, number of multiple OCCs, OCC length plus 1, or number of multiple OCCs plus 1.

[0114] In some embodiments, the network device may indicate the OCC length or the number of multiple OCCs to the terminal device in the DCI.

[0115] In some embodiments, the first configuration information is determined based on the first TC-RNTI in the RAR and the mapping rules from the value range of the TC-RNTI to the OCC index.

[0116] In some embodiments, a network device may configure mapping rules for a terminal device.

[0117] In some embodiments, the first configuration information is carried in at least one first bit of the DCI, which is an index of the first OCC that indicates the transmission to be applied to MSG 3.

[0118] In some embodiments, the first configuration information is carried in at least one second bit in the DCI that indicates whether OCC will be applied to the transmission of MSG 3.

[0119] In some embodiments, the network device may transmit second configuration information to the terminal device indicating whether OCC will be applied to the transmission of message 1 (MSG 1). The second configuration information may also be used to indicate whether OCC will be applied to the transmission of MSG 3.

[0120] In some embodiments, the network device may transmit third configuration information associated with the OCC used to transmit MSG 1 to the terminal device. The OCC used to transmit MSG 1 may be different from the OCC used to transmit MSG 3.

[0121] In some embodiments, after receiving MSG 1 from the terminal device, the network device may check whether the OCC used for transmitting MSG 3 is different from the OCC used for transmitting MSG 1. Based on the difference between the OCC used for transmitting MSG 3 and the OCC used for transmitting MSG 1, the network device may indicate first configuration information in at least one of DCI or RAR.

[0122] In some embodiments, after receiving MSG 1 from the terminal device, the network device may check whether the OCC used for transmitting MSG 3 and the OCC used for transmitting MSG 1 are adjusted to be the same. If the OCC used for transmitting MSG 3 and the OCC used for transmitting MSG 1 are not adjusted to be the same, the network device may indicate first configuration information in at least one of DCI or RAR.

[0123] In some embodiments, the first configuration information is determined based on the difference between the OCC used for transmitting MSG 3 and the OCC used for transmitting MSG 1. This difference may be indicated in at least one of DCI or RAR.

[0124] In some embodiments, the DCI is transmitted in time resources and frequency resources. At least one of the time resources or frequency resources and at least one first bit in the DCI 205 indicates the index of the first OCC to be applied to the transmission of MSG 3.

[0125] In some embodiments, an apparatus capable of performing any of the methods 500 (e.g., terminal device 101) may include components for performing the corresponding steps of method 500. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0126] In some embodiments, the apparatus includes: components for receiving downlink control information (DCI) for scheduling a random access response (RAR) from a network device; components for receiving the RAR from the network device based on the DCI, wherein at least one of the DCI or the RAR includes first configuration information associated with an orthogonal overlay code (OCC) for transmitting message 3 (MSG 3); and components for transmitting MSG 3 to the network device based on the first configuration information.

[0127] In some embodiments, the first configuration information may include: an index of a first OCC among a plurality of OCCs, wherein the first OCC will be applied to the transmission of MSG 3; or an indication that no OCC will be applied to the transmission of MSG 3.

[0128] In some embodiments, the first configuration information may be carried in the following: a first temporary connection radio network temporary identifier (TC-RNTI) in the RAR; or a bit set in the DCI; or a combination thereof.

[0129] In some embodiments, the first configuration information is determined based on the following: the first TC-RNTI in the RAR; the OCC length or the number of multiple OCCs; and the mapping rules for the index from the TC-RNTI to the OCCs.

[0130] In some embodiments, a first TC-RNTI mapped to the index of a first OCC among a plurality of OCCs indicates that the first OCC will be applied to the transmission of MSG 3. Alternatively, a first TC-RNTI mapped to a value different from the index of an OCC among a plurality of OCCs indicates that no OCC will be applied to the transmission of MSG 3.

[0131] In some embodiments, the mapping rule applies to multiple TC-RNTIs, or the mapping rule applies to at least one TC-RNTI in one of multiple value ranges of multiple TC-RNTIs.

[0132] In some embodiments, a first TC-RNTI that is not in one of the multiple value ranges of a plurality of TC-RNTIs indicates that no OCC will be applied to the transmission of MSG 3, wherein the mapping rule applies to at least one TC-RNTI in one of the multiple value ranges of a plurality of TC-RNTIs.

[0133] In some embodiments, the mapping rule indicates that the OCC index is based on TC-RNTI and at least one of the following: OCC length, number of multiple OCCs, OCC length plus 1, or number of multiple OCCs plus 1.

[0134] In some embodiments, the length of the OCC or the number of multiple OCCs is indicated or predetermined in the DCI.

[0135] In some embodiments, the first configuration information is determined based on the following: the first TC-RNTI in the RAR; and the mapping rules from the value range of the TC-RNTI to the OCC index.

[0136] In some embodiments, the mapping rules are configured by the network device or are predetermined.

[0137] In some embodiments, the first configuration information is carried in at least one first bit in the DCI, indicating the index of the first OCC to be applied to the transmission of MSG 3.

[0138] In some embodiments, the first configuration information is carried in at least one second bit in the DCI that indicates whether OCC will be applied to the transmission of MSG 3.

[0139] In some embodiments, the apparatus further includes a component for receiving second configuration information from a network device indicating whether OCC will be applied to the transmission of message 1 (MSG 1), wherein the second configuration information is also used to indicate whether OCC will be applied to the transmission of MSG 3.

[0140] In some embodiments, the apparatus further includes a component for receiving third configuration information associated with an OCC used for transmitting MSG 1 from a network device, wherein the OCC used for transmitting MSG 1 is different from the OCC used for transmitting MSG 3.

[0141] In some embodiments, the first configuration information is determined based on the difference between the OCC used for transmitting MSG 3 and the OCC used for transmitting MSG 1. This difference is indicated in at least one of DCI or RAR.

[0142] In some embodiments, the DCI and / or RAR include first configuration information based on one or more of the following: the OCC used for transmitting MSG 3 is different from the OCC used for transmitting MSG 1; or the OCC used for transmitting MSG 3 and the OCC used for transmitting MSG 1 are not adjusted to be the same.

[0143] In some embodiments, the DCI is received in time resources and frequency resources. At least one of the time resources or frequency resources and at least one first bit in the DCI 205 indicates the index of the first OCC to be applied to the transmission of MSG 3.

[0144] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 500. In some embodiments, the components include at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to cause execution of the apparatus.

[0145] In some embodiments, an apparatus capable of performing any of the methods 600 (e.g., network device 103) may include components for performing the corresponding steps of method 600. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0146] In some embodiments, the apparatus includes: components for transmitting downlink control information (DCI) for scheduling a random access response (RAR) to a terminal device; components for transmitting the RAR to the terminal device based on the DCI, wherein at least one of the DCI or the RAR includes first configuration information associated with an orthogonal overlay code (OCC) for transmitting message 3 (MSG 3); and components for receiving MSG 3 from the terminal device based on the first configuration information.

[0147] In some embodiments, the first configuration information includes: an index of a first OCC among a plurality of OCCs, wherein the first OCC will be applied to the transmission of MSG 3; or an indication that no OCC will be applied to the transmission of MSG 3.

[0148] In some embodiments, the first configuration information is carried in the following: a first temporary connection radio network temporary identifier (TC-RNTI) in the RAR; or a set of bits in the DCI; or a combination thereof.

[0149] In some embodiments, the first configuration information is determined based on the first TC-RNTI in the RAR, the length of the OCC or the number of multiple OCCs, and the mapping rules of the index from the TC-RNTI to the OCC.

[0150] In some embodiments, a first TC-RNTI mapped to the index of a first OCC among a plurality of OCCs indicates that the first OCC will be applied to the transmission of MSG 3. Alternatively, a first TC-RNTI mapped to a value different from the index of an OCC among a plurality of OCCs indicates that no OCC will be applied to the transmission of MSG 3.

[0151] In some embodiments, the mapping rule applies to multiple TC-RNTIs; or the mapping rule applies to at least one TC-RNTI in one of a range of values ​​for multiple TC-RNTIs.

[0152] In some embodiments, a first TC-RNTI that is not in one of the multiple value ranges of a plurality of TC-RNTIs indicates that no OCC will be applied to the transmission of MSG 3, wherein the mapping rule applies to at least one TC-RNTI in one of the multiple value ranges of a plurality of TC-RNTIs.

[0153] In some embodiments, the mapping rule indicates that the OCC index is based on TC-RNTI and at least one of the following: OCC length, number of multiple OCCs, OCC length plus 1, or number of multiple OCCs plus 1.

[0154] In some embodiments, the apparatus further includes a component for indicating the length of an OCC or the number of multiple OCCs to a terminal device in a DCI.

[0155] In some embodiments, the first configuration information is determined based on the first TC-RNTI in the RAR and the mapping rules from the value range of the TC-RNTI to the OCC index.

[0156] In some embodiments, the apparatus further includes a component for configuring mapping rules for a terminal device.

[0157] In some embodiments, the first configuration information is carried in at least one first bit of the DCI, which is an index of the first OCC that indicates the transmission to be applied to MSG 3.

[0158] In some embodiments, the first configuration information is carried in at least one second bit in the DCI that indicates whether OCC will be applied to the transmission of MSG 3.

[0159] In some embodiments, the apparatus further includes a component for transmitting second configuration information to a terminal device, indicating whether OCC will be applied to the transmission of message 1 (MSG 1), wherein the second configuration information may also be used to indicate whether OCC will be applied to the transmission of MSG 3.

[0160] In some embodiments, the apparatus further includes a component for transmitting to a terminal device third configuration information associated with an OCC used for transmitting MSG 1, wherein the OCC used for transmitting MSG 1 may be different from the OCC used for transmitting MSG 3.

[0161] In some embodiments, the apparatus further includes: a component for checking whether the OCC used for transmitting MSG 3 and the OCC used for transmitting MSG 1 are different after receiving MSG 1 from the terminal device; and a component for indicating first configuration information in at least one of the DCI or RAR based on the difference between the OCC used for transmitting MSG 3 and the OCC used for transmitting MSG 1.

[0162] In some embodiments, the apparatus further includes: a component for checking whether the OCC for transmitting MSG 3 and the OCC for transmitting MSG 1 are adjusted to be the same after receiving MSG 1 from the terminal device; and a component for indicating first configuration information in at least one of the DCI or RAR based on the failure of the OCC for transmitting MSG 3 and the OCC for transmitting MSG 1 to be adjusted to be the same.

[0163] In some embodiments, the first configuration information is determined based on the difference between the OCC used for transmitting MSG 3 and the OCC used for transmitting MSG 1, wherein the difference is indicated in at least one of DCI or RAR.

[0164] In some embodiments, the DCI is transmitted in time resources and frequency resources. At least one of the time resources or frequency resources and at least one first bit in the DCI 205 indicates the index of the first OCC to be applied to the transmission of MSG 3.

[0165] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 600. In some embodiments, the components include at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to cause execution of the apparatus.

[0166] Figure 7 This is a simplified block diagram of a device 700 suitable for implementing embodiments of the present disclosure. Device 700 may be provided to implement a communication device, such as a terminal device or a network device. As shown, device 700 includes one or more processors 710, one or more memories 720 coupled to processor 710, and one or more communication modules 740 coupled to processor 710.

[0167] Communication module 740 is used for bidirectional communication. Communication module 740 has at least one antenna to facilitate communication. The communication interface can represent any interface required for communication with other network elements.

[0168] Processor 710 can be of any type suitable for a local technology network, and by way of non-limiting example, can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 700 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock synchronized with the main processor.

[0169] Memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disc (CD), digital video disc (DVD), and other magnetic storage devices and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that will not persist during power outages.

[0170] Computer program 730 includes computer-executable instructions that are executed by the associated processor 710. Program 730 may be stored in ROM 724. Processor 710 may perform any suitable actions and processes by loading program 730 into RAM 722.

[0171] The embodiments of this disclosure can be implemented via program 730, enabling device 700 to execute reference... Figures 2 to 6 Any process discussed in this disclosure. Embodiments of this disclosure may also be implemented by hardware or by a combination of software and hardware.

[0172] In some embodiments, program 730 may be tangibly contained in a computer-readable medium, which may be included in device 700 (such as memory 720) or in other storage devices accessible by device 700. Device 700 may load program 730 from the computer-readable medium into RAM 722 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 8 An example of a computer-readable medium 800 in the form of a CD or DVD is shown. The computer-readable medium has a program 730 stored thereon.

[0173] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the exemplary embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0174] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions that are executed in a device on a target real or virtual processor, such as instructions included in a program module to perform the functions described above. Figures 2-6 Methods 500 or 600 are described. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions for a program module can be executed on a local or distributed device. In a distributed device, a program module can reside on both local and remote storage media.

[0175] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0176] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier wave to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carrier waves include signals, computer-readable media, etc.

[0177] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer floppy disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. As used herein, the term "non-transient" is a limitation on the medium itself (i.e., tangible, not signaling), not a limitation on the persistence of data storage (e.g., RAM and ROM).

[0178] Furthermore, although the operations are described in a specific order, this should not be construed as requiring such operations to be performed in the specific order shown or in sequence, or that all illustrated operations be performed to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0179] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features or actions described above are disclosed as exemplary forms of implementing the claims.

Claims

1. A terminal device, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the terminal device to at least: Receive downlink control information (DCI) from network devices for scheduling random access response (RAR); Based on the DCI, the RAR is received from the network device, wherein at least one of the DCI or the RAR includes: first configuration information associated with the orthogonal overlay code (OCC) for transmitting message 3 (MSG 3); as well as Based on the first configuration information, the MSG 3 is transmitted to the network device.

2. The terminal device according to claim 1, wherein the first configuration information includes: An index of the first OCC among a plurality of OCCs, wherein the first OCC will be applied to the transmission of the MSG 3; or No OCC will be applied to the instruction of the transmission in the MSG 3.

3. The terminal device according to claim 1 or 2, wherein the first configuration information is carried in at least one of the following: The first temporary connection radio network temporary identifier (TC-RNTI) in the RAR; or The set of bits in the DCI.

4. The terminal device according to any one of claims 1 to 3, wherein the first configuration information is determined based on the following: The first TC-RNTI in the RAR; OCC length or the number of multiple OCCs; and Mapping rules from TC-RNTI to OCC indexes.

5. The terminal device according to claim 4, wherein: The first TC-RNTI, whose index is mapped to the first OCC among multiple OCCs, indicates that the first OCC will be applied to the transmission of the MSG 3; or The first TC-RNTI, which is mapped to a value different from the index of the OCC in the plurality of OCCs, indicates that no OCC will be applied to the transmission of the MSG 3.

6. The terminal device according to claim 4 or 5, wherein: The mapping rules apply to multiple TC-RNTIs; or The mapping rule applies to at least one TC-RNTI in one of the multiple value ranges of the multiple TC-RNTIs.

7. The terminal device according to claim 4, wherein: The first TC-RNTI that is not in one of the multiple value ranges of the multiple TC-RNTIs indicates that no OCC will be applied to the transmission of the MSG 3, wherein the mapping rule applies to at least one TC-RNTI in one of the multiple value ranges of the multiple TC-RNTIs.

8. The terminal device according to any one of claims 4 to 7, wherein the mapping rule indicates that the OCC index is based on TC-RNTI and at least one of the following: The length of the OCC; The number of the plurality of OCCs; The OCC length is increased by 1; or The number of the plurality of OCCs is increased by 1.

9. The terminal device according to claim 4 or 8, wherein the length of the OCC or the number of the plurality of OCCs is indicated or predetermined in the DCI.

10. The terminal device according to any one of claims 1 to 3, wherein the first configuration information is determined based on the following: The first TC-RNTI in the RAR; and Mapping rules from the TC-RNTI value range to the OCC index.

11. The terminal device according to any one of claims 4 to 10, wherein the mapping rule is configured or predetermined by the network device.

12. The terminal device according to any one of claims 1 to 3, wherein the first configuration information is carried in the following: The DCI indicates at least one first bit of the index of the first OCC to be applied to the transmission of the MSG 3.

13. The terminal device according to any one of claims 1 to 3, wherein the first configuration information is carried in the following: Indicates whether OCC will be applied to at least one second bit of the DCI in the transmission of the MSG 3.

14. The terminal device according to any one of claims 1 to 12, wherein the terminal device is further configured to: The network device receives second configuration information indicating whether OCC will be applied to the transmission of message 1 (MSG 1), wherein the second configuration information is also used to indicate whether OCC will be applied to the transmission of MSG 3.

15. The terminal device according to any one of claims 1 to 14, wherein the terminal device is further configured to: Receive third configuration information from the network device associated with the OCC used to transmit MSG 1, wherein the OCC used to transmit MSG 1 is different from the OCC used to transmit MSG 3.

16. The terminal device according to any one of claims 1 to 3, wherein the first configuration information is determined based on the following: The difference between the OCC used to transmit the MSG 3 and the OCC used to transmit the MSG 1, wherein the difference is indicated in at least one of the DCI or the RAR.

17. The terminal device according to any one of claims 1 to 16, wherein the at least one of the DCI or the RAR includes the first configuration information based on at least one of the following: The OCC used to transmit MSG 3 is different from the OCC used to transmit MSG 1; or The OCC used to transmit MSG 3 and the OCC used to transmit MSG 1 were not adjusted to be the same.

18. The terminal device according to claim 1 or 2, wherein the DCI is received in time resources and frequency resources, and wherein: The time resource or the frequency resource, and at least one first bit in the DCI, indicate the index of the first OCC to be applied to the transmission of the MSG 3.

19. A network device, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the network device to at least: Transmit downlink control information (DCI) to the terminal device for scheduling random access response (RAR); Based on the DCI, the RAR is transmitted to the terminal device, wherein at least one of the DCI or the RAR includes: first configuration information associated with the orthogonal overlay code (OCC) for transmitting message 3 (MSG 3); as well as Based on the first configuration information, the MSG 3 is received from the terminal device.

20. The network device of claim 19, wherein the first configuration information includes: An index of the first OCC among a plurality of OCCs, wherein the first OCC will be applied to the transmission of the MSG 3; or No OCC will be applied to the instruction of the transmission in the MSG 3.

21. The network device according to claim 19 or 20, wherein the first configuration information is carried in at least one of the following: The first temporary connection radio network temporary identifier (TC-RNTI) in the RAR; or The set of bits in the DCI.

22. The network device according to any one of claims 19 to 21, wherein the first configuration information is determined based on: The first TC-RNTI in the RAR; OCC length or the number of multiple OCCs; and Mapping rules from TC-RNTI to OCC indexes.

23. The network device according to claim 22, wherein: The first TC-RNTI, whose index is mapped to the first OCC among multiple OCCs, indicates that the first OCC will be applied to the transmission of the MSG 3; or The first TC-RNTI, which is mapped to a value different from the index of the OCC in the plurality of OCCs, indicates that no OCC will be applied to the transmission of the MSG 3.

24. The network device according to claim 22 or 23, wherein: The mapping rules apply to multiple TC-RNTIs; or The mapping rule applies to at least one TC-RNTI in one of the multiple value ranges of the multiple TC-RNTIs.

25. The network device according to claim 22, wherein: The first TC-RNTI that is not in one of the multiple value ranges of the multiple TC-RNTIs indicates that no OCC will be applied to the transmission of the MSG 3, wherein the mapping rule applies to at least one TC-RNTI in one of the multiple value ranges of the multiple TC-RNTIs.

26. The network device according to any one of claims 22 to 25, wherein the mapping rule indicates that the OCC index is based on TC-RNTI and at least one of the following: The length of the OCC; The number of the plurality of OCCs; The OCC length is increased by 1; or The number of the plurality of OCCs is increased by 1.

27. The network device according to claim 22 or 26, wherein the network device is further configured to: The DCI indicates the length of the OCC or the number of the plurality of OCCs to the terminal device.

28. The network device according to any one of claims 19 to 21, wherein the first configuration information is determined based on: The first TC-RNTI in the RAR; and Mapping rules from the TC-RNTI value range to the OCC index.

29. The network device according to any one of claims 22 to 28, wherein the network device is further configured to: Configure the mapping rules for the terminal device.

30. The network device according to any one of claims 19 to 21, wherein the first configuration information is carried in the following: The DCI indicates at least one first bit of the index of the first OCC to be applied to the transmission of the MSG 3.

31. The network device according to any one of claims 19 to 21, wherein the first configuration information is carried in the following: Indicates whether OCC will be applied to at least one second bit of the DCI in the transmission of the MSG 3.

32. The network device according to any one of claims 19 to 31, wherein the network device is further configured to: The terminal device is transmitted second configuration information indicating whether OCC will be applied to the transmission of message 1 (MSG 1), wherein the second configuration information is also used to indicate whether OCC will be applied to the transmission of MSG 3.

33. The network device according to any one of claims 19 to 32, wherein the network device is further configured to: The terminal device is transmitted third configuration information associated with the OCC used to transmit MSG 1, wherein the OCC used to transmit MSG 1 is different from the OCC used to transmit MSG 3.

34. The network device according to any one of claims 19 to 21, wherein the network device is further configured to: After receiving MSG 1 from the terminal device, check whether the OCC used to transmit MSG 3 and the OCC used to transmit MSG 1 are different; and The first configuration information is indicated in at least one of the DCI or the RAR, based on the fact that the OCC used to transmit the MSG 3 is different from the OCC used to transmit the MSG 1.

35. The network device according to any one of claims 19 to 21, wherein the network device is further configured to: After receiving MSG 1 from the terminal device, it is checked whether the OCC used to transmit MSG 3 and the OCC used to transmit MSG 1 have been adjusted to be the same; and The first configuration information is indicated in at least one of the DCI or the RAR if the OCC used for transmitting the MSG 3 and the OCC used for transmitting the MSG 1 are not adjusted to be the same.

36. The network device according to any one of claims 19 to 21, wherein the first configuration information is determined based on: The difference between the OCC used to transmit the MSG 3 and the OCC used to transmit the MSG 1, wherein the difference is indicated in at least one of the DCI or the RAR.

37. The network device according to claim 19 or 20, wherein the DCI is transmitted in time resources and frequency resources, and wherein: At least one of the time resources or the frequency resources and at least one first bit of the DCI indicate that the index of the first OCC of the transmission of the MSG 3 will be applied.

38. A method comprising: At the terminal device, downlink control information (DCI) for scheduling random access response (RAR) is received from the network device. The RAR is received from the network device based on the DCI, wherein at least one of the DCI or the RAR includes: first configuration information associated with the orthogonal overlay code (OCC) for transmitting message 3 (MSG 3); as well as Based on the first configuration information, the MSG 3 is transmitted to the network device.

39. A method comprising: At the network device, downlink control information (DCI) for scheduling random access response (RAR) is transmitted to the terminal device. Based on the DCI, the RAR is transmitted to the terminal device, wherein at least one of the DCI or the RAR includes: first configuration information associated with the orthogonal overlay code (OCC) for transmitting message 3 (MSG 3); as well as Based on the first configuration information, the MSG 3 is received from the terminal device.

40. An apparatus comprising: A component used at the terminal device to receive downlink control information (DCI) from the network device for scheduling random access response (RAR); A component for receiving the RAR from the network device based on the DCI, wherein at least one of the DCI or the RAR includes: first configuration information associated with an orthogonal overlay code (OCC) for transmitting message 3 (MSG 3); as well as A component for transmitting the MSG 3 to the network device based on the first configuration information.

41. An apparatus comprising: A component used to transmit downlink control information (DCI) for scheduling random access responses (RAR) from network devices to terminal devices; A component for transmitting the RAR to the terminal device based on the DCI, wherein at least one of the DCI or the RAR includes: first configuration information associated with an orthogonal overlay code (OCC) for transmitting message 3 (MSG 3); as well as A component for receiving the MSG 3 from the terminal device based on the first configuration information.

42. A non-transitory computer-readable medium comprising program instructions that, when executed by a device, cause the device to perform at least the method according to any one of claims 38 to 39.