[go: up one dir, main page]

WO2025208253A1 - Dispositif, procédé et support lisible par ordinateur pour des communications - Google Patents

Dispositif, procédé et support lisible par ordinateur pour des communications

Info

Publication number
WO2025208253A1
WO2025208253A1 PCT/CN2024/085114 CN2024085114W WO2025208253A1 WO 2025208253 A1 WO2025208253 A1 WO 2025208253A1 CN 2024085114 W CN2024085114 W CN 2024085114W WO 2025208253 A1 WO2025208253 A1 WO 2025208253A1
Authority
WO
WIPO (PCT)
Prior art keywords
random access
terminal device
multiplexing
access preamble
rar
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/085114
Other languages
English (en)
Inventor
Yue Zhou
Zonghui XIE
Li Zhang
Bohang ZHANG
Gang Wang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Corp
Original Assignee
NEC Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by NEC Corp filed Critical NEC Corp
Priority to PCT/CN2024/085114 priority Critical patent/WO2025208253A1/fr
Publication of WO2025208253A1 publication Critical patent/WO2025208253A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access

Definitions

  • Embodiments of the present disclosure generally relate to the field of communication, and in particular, to devices, methods and computer readable medium for the random access.
  • NB-IoT narrow band internet of things
  • eMTC extended Machine Type Communications
  • a network device comprising a processor.
  • the processor is configured to cause the network device to receive, from a terminal device, a random access preamble that is spread by an orthogonal code sequence based on a multiplexing configuration.
  • the multiplexing configuration comprises information on code domain multiplexing.
  • the network device is further caused to transmit, to the terminal device, a random access response (RAR) for the random access preamble, such that the terminal device to receive the RAR during an RAR window. At least one of a starting time or a size of the RAR window is associated with the multiplexing configuration.
  • RAR random access response
  • a terminal device comprising a processor.
  • the processor is configured to cause the terminal device to receive, from a network device, association information that indicates an association between one or more carriers and one or more multiplexing configurations.
  • a multiplexing configuration of the one or more multiplexing configurations comprises information on code domain multiplexing.
  • the terminal device is further caused to transmit, to the network device, a random access preamble that is spread by an orthogonal code sequence based on a first multiplexing configuration of the one or more multiplexing configurations.
  • the terminal device is further caused to receive, from the network device and on a first carrier of the one or more carriers, a random access response (RAR) for the random access preamble, wherein the first carrier is associated with the first multiplexing configuration.
  • RAR random access response
  • a network device comprising a processor.
  • the processor is configured to cause the network device to transmit, to a terminal device, association information that indicates an association between one or more carriers and one or more multiplexing configurations.
  • a multiplexing configuration of the one or more multiplexing configurations comprises information on code domain multiplexing.
  • the network device is further caused to receive, from the terminal device, a random access preamble that is spread by an orthogonal code sequence based on a first multiplexing configuration of the one or more multiplexing configurations.
  • the network device is further caused to transmit, to the terminal device and on a first carrier of the one or more carriers, a random access response (RAR) for the random access preamble, wherein the first carrier is associated with the first multiplexing configuration.
  • RAR random access response
  • a terminal device comprising a processor.
  • the processor is configured to cause the terminal device to transmit, to a network device, a random access preamble that is spread by an orthogonal code sequence based on a first multiplexing configuration of a plurality of multiplexing configurations.
  • a multiplexing configuration of the plurality of multiplexing configurations comprises information on code domain multiplexing.
  • the terminal device is further caused to determine a random access (RA) -radio network temporary identifier (RNTI) based on the first multiplexing configuration and information related to a transmission of the random access preamble.
  • the terminal device is further caused to receive, from the network device, a random access response (RAR) for the random access preamble using the RA-RNTI.
  • RA random access
  • RAR random access response
  • a network device comprising a processor.
  • the processor is configured to cause the network device to receive, from a terminal device, a random access preamble that is spread by an orthogonal code sequence based on a first multiplexing configuration of a plurality of multiplexing configurations.
  • a multiplexing configuration of the plurality of multiplexing configurations comprises information on code domain multiplexing.
  • the network device is further caused to determine the first multiplexing configuration among the plurality of multiplexing configurations by detecting the random access preamble.
  • the network device is further caused to determine a random access (RA) -radio network temporary identifier (RNTI) based on the first multiplexing configuration and information related to a transmission of the random access preamble.
  • the network device is further caused to transmit, to the terminal device, a random access response (RAR) for the random access preamble using the RA-RNTI.
  • RA random access
  • RAR random access response
  • a terminal device comprising a processor.
  • the processor is configured to cause the terminal device to transmit, to a network device, a random access preamble that is spread by an orthogonal code sequence based on a first multiplexing configuration of a plurality of multiplexing configurations.
  • a multiplexing configuration of the plurality of multiplexing configurations comprises information on code domain multiplexing.
  • the terminal device is further caused to detect, on random access response (RAR) resources associated with the random access preamble, at least one of i) one or more downlink control channels of one or more RARs, or ii) one or more downlink shared channels of the one or more RARs.
  • RAR random access response
  • the terminal device is further caused to determine, among the one or more RARs, a target RAR for the random access preamble based on detecting at least one of: a target downlink control channel among the one or more downlink control channels, the target downlink control channel comprising a code sequence index corresponding to the first multiplexing configuration, or a target downlink shared channel among the one or more downlink shared channels, the target downlink shared channel comprising the code sequence index.
  • a network device comprising a processor.
  • the processor is configured to cause the network device to receive, from a terminal device, a random access preamble that is spread by an orthogonal code sequence based on a first multiplexing configuration of a plurality of multiplexing configurations.
  • a multiplexing configuration of the plurality of multiplexing configurations comprises information on code domain multiplexing.
  • the network device is further caused to include a code sequence index corresponding to the first multiplexing configuration into at least one of a downlink control channel or a downlink shared channel of a random access response (RAR) for the random access preamble.
  • the network device is further caused to transmit, to the terminal device, the RAR on random access response (RAR) resources associated with the random access preamble.
  • a method implemented at a terminal device transmits, to a network device, a random access preamble that is spread by an orthogonal code sequence based on a multiplexing configuration.
  • the multiplexing configuration comprises information on code domain multiplexing.
  • the terminal device receives, from the network device, a random access response (RAR) for the random access preamble during an RAR window. At least one of a starting time or a size of the RAR window is associated with the multiplexing configuration.
  • RAR random access response
  • the network device receives, from a terminal device, a random access preamble that is spread by an orthogonal code sequence based on a multiplexing configuration.
  • the multiplexing configuration comprises information on code domain multiplexing.
  • the network device transmits, to the terminal device, a random access response (RAR) for the random access preamble, such that the terminal device to receive the RAR during an RAR window, wherein at least one of a starting time or a size of the RAR window is associated with the multiplexing configuration.
  • RAR random access response
  • the terminal device receives, from a network device, association information that indicates an association between one or more carriers and one or more multiplexing configurations.
  • a multiplexing configuration of the one or more multiplexing configurations comprises information on code domain multiplexing.
  • the terminal device transmits, to the network device, a random access preamble that is spread by an orthogonal code sequence based on a first multiplexing configuration of the one or more multiplexing configurations.
  • the terminal device receives, from the network device and on a first carrier of the one or more carriers, a random access response (RAR) for the random access preamble.
  • the first carrier is associated with the first multiplexing configuration
  • the network device receives, from a terminal device, a random access preamble that is spread by an orthogonal code sequence based on a first multiplexing configuration of a plurality of multiplexing configurations.
  • a multiplexing configuration of the plurality of multiplexing configurations comprises information on code domain multiplexing.
  • the network device determines the first multiplexing configuration among the plurality of multiplexing configurations by detecting the random access preamble.
  • the network device determines a radio network temporary identifier (RNTI) based on the first multiplexing configuration and information related to a transmission of the random access preamble.
  • the network device transmits, to the terminal device, a random access response (RAR) for the random access preamble using the RNTI.
  • RAR random access response
  • a method implemented at a terminal device transmits, to a network device, a random access preamble that is spread by an orthogonal code sequence based on a first multiplexing configuration of a plurality of multiplexing configurations.
  • a multiplexing configuration of the plurality of multiplexing configurations comprises information on code domain multiplexing.
  • the terminal device detects, on random access response (RAR) resources associated with the random access preamble, at least one of i) one or more downlink control channels of one or more RARs, or ii) one or more downlink shared channels of the one or more RARs.
  • RAR random access response
  • FIG. 10 illustrates a flowchart of an example method implemented at a network device according to some embodiments of the present disclosure
  • FIG. 12 illustrates a flowchart of an example method implemented at a network device according to some embodiments of the present disclosure
  • FIG. 14 illustrates a flowchart of an example method implemented at a network device according to some embodiments of the present disclosure
  • FIG. 15 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure.
  • terminal device refers to any device having wireless or wired communication capabilities.
  • the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, devices for Integrated Access and Backhaul (IAB) , Small Data Transmission (SDT) , mobility, Multicast and Broadcast Services (MBS) , positioning, dynamic/flexible duplex in commercial networks, reduced capability (RedCap) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eX
  • UE user equipment
  • the ‘terminal device’ can further has ‘multicast/broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4/IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may be also incorporated one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM.
  • SIM Subscriber Identity Module
  • the term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal, a wireless device or a reduced capability terminal device.
  • the term “network device” refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate.
  • a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , Network-controlled Repeaters, and the like.
  • NodeB Node B
  • eNodeB or eNB evolved NodeB
  • gNB next generation NodeB
  • TRP transmission reception point
  • RRU remote radio unit
  • RH radio head
  • RRH remote radio head
  • IAB node a
  • the terminal device or the network device may have Artificial intelligence (AI) or Machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
  • the terminal or the network device may work on several frequency ranges, e.g. FR1 (410 MHz –7125 MHz) , FR2 (24.25 GHz to 71 GHz) , 71 GHz to 114 GHz, and frequency band larger than 100 GHz as well as Tera Hertz (THz) . It can further work on licensed/unlicensed/shared spectrum.
  • the terminal device may have more than one connection with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario.
  • MR-DC Multi-Radio Dual Connectivity
  • the terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.
  • the network device may have the function of network energy saving, Self-Organizing Networks (SON) /Minimization of Drive Tests (MDT) .
  • the terminal may have the function of power saving.
  • test equipment e.g. signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator.
  • the embodiments of the present disclosure may be performed according to any generation communication protocols either currently known or to be developed in the future.
  • Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.
  • the terminal device may be connected with a first network device and a second network device.
  • One of the first network device and the second network device may be a master node and the other one may be a secondary node.
  • the first network device and the second network device may use different radio access technologies (RATs) .
  • the first network device may be a first RAT device and the second network device may be a second RAT device.
  • the first RAT device is eNB and the second RAT device is gNB.
  • Information related with different RATs may be transmitted to the terminal device from at least one of the first network device and the second network device.
  • first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device.
  • information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device.
  • Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.
  • the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’
  • the term ‘based on’ is to be read as ‘at least in part based on. ’
  • the term ‘one embodiment’ and ‘an embodiment’ are to be read as ‘at least one embodiment. ’
  • the term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’
  • the terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.
  • values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
  • circuitry used herein may refer to hardware circuits and/or combinations of hardware circuits and software.
  • the circuitry may be a combination of analog and/or digital hardware circuits with software/firmware.
  • the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions.
  • the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software/firmware for operation, but the software may not be present when it is not needed for operation.
  • circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and/or firmware.
  • the subband and the frequency subband may be used interchangeable without any limitation.
  • the group size of a RBG may be also referred to as the RBG size without any limitation.
  • the control channel may be interchangeably used with the physical downlink control channel (PDCCH) without any limitation.
  • PDCCH physical downlink control channel
  • downlink (DL) control channel and “physical downlink control channel (PDCCH) ” can be used interchangeably.
  • the terms “downlink shared channel” and “physical downlink shared channel (PDSCH) ” can be used interchangeably.
  • the term RAR response window refers to a time duration for the terminal device to detect a Msg 2 for the Msg 1 transmitted by the terminal device in a four-step random access, and/or a time duration for the terminal device detect a Msg B for the Msg A transmitted by the terminal device in a two-step random access.
  • the starting time of the RAR response window is related to the transmission of the random access preamble of the Msg 1/Msg A.
  • the size of the RAR window is related to the interval between consecutive PDCCH occasions. Specifically, the size of the RAR window may be a multiple of a PDCCH period (pp) .
  • the terms “RAR window” , “Msg 2 RAR window” and “Msg B RAR window” can be used interchangeably.
  • the term “PDCCH period (pp) ” refers to the interval between the start of two consecutive PDCCH occasions and depends on the currently used PDCCH search space.
  • a PDCCH occasion is the start of a search space and is defined by subframe k0.
  • the calculation of number of PDCCH-subframes for the timer configured in units of a PDCCH period is done by multiplying the number of PDCCH periods with npdcch-NumRepetitions-RA when the UE uses the common search space or by npdcch-NumRepetitions when the UE uses the UE specific search space.
  • the UE When counting a timer whose length is calculated in PDCCH-subframes, the UE shall include PDCCH-subframes that will be dropped or not required to be monitored.
  • the calculation of the number of subframes for the timer configured in units of a PDCCH period is done by multiplying the number of PDCCH periods with a duration between two consecutive PDCCH occasions.
  • the term “radio network temporary identifier (RNTI) ” refers to the identifier which may be used to distinguish the terminal devices in the random access.
  • the RNTI may include random access (RA) -RNTI, cell -RNTI (C-RNTI) , and so on.
  • the RNTI may be also referred to as “X-RNTI” .
  • RA-RNTI in response to a Msg 1 from a terminal device, the network device may use a RA-RNTI to scramble a PDCCH for the Msg 2 towards this terminal device.
  • the RA-RNTI is calculated based on the resource position of the random access preamble in Msg 1.
  • the terminal device may also determine the respective RA-RNTI accordingly (since it is aware of the resource position) and use this RA-RNTI to de-scramble the PDCCH of Msg 2. Furthermore, the PDCCH of the Msg 2 indicates the resource position for the PDSCH of the Msg 2, thus the terminal device may further receive the PDSCH of the Msg 2.
  • the network device may use a MsgB-RNTI to scramble a PDCCH for the Msg B towards this terminal device.
  • the MsgB-RNTI is calculated based on the resource position of the random access preamble in Msg A.
  • the terminal device may also determine the respective MsgB-RNTI accordingly (since it is aware of the resource position) and use this MsgB-RNTI to de-scramble the PDCCH of Msg B.
  • the PDCCH of the Msg B indicates the resource position for the PDSCH of the Msg B, thus the terminal device may further receive the PDSCH of the Msg B.
  • the terms “orthogonal code sequence” and “orthogonal codebook set” may be used interchangeably without any limitation.
  • the terms “orthogonal code sequence index” refers to the index of an orthogonal code sequence.
  • An example of the orthogonal code sequence index may be “OCC-index” .
  • the terms “orthogonal code sequence index” and “code book set index” may be used interchangeably.
  • the first orthogonal code sequence index may be also referred to a “first codebook set index” , “1 st codebook set index” , “codebook set index 1 st ” , “codebook set index 1” or other similar expressions.
  • IoT network is resource limited, especially in the UL (e.g., UL in the initial access phase) , when a limited amount of spectrum is expected to be available for deployment of IoT NTN services.
  • a terminal device transmits a random access preamble to a network device.
  • the random access preamble is spread by an orthogonal code sequence based on a multiplexing configuration.
  • the multiplexing configuration includes information on code domain complexing.
  • the terminal device receives an RAR for the random access preamble during a RAR window, and at least one of a starting time or a size of the RAR window is associated with the multiplexing configuration. In this way, even if more time will be consumed due to the blind detection of the random access preamble spread by the orthogonal code sequence, the terminal device may receive the respective RAR in an adapted RAR window.
  • a terminal device receives association information from a network device.
  • the association information indicates an association between one or more carriers and one or more multiplexing configurations.
  • a multiplexing configuration of the one or more multiplexing configurations includes information on code domain multiplexing.
  • the terminal device further transmits random access preamble that is spread by an orthogonal code sequence based on a first multiplexing configuration of the one or more multiplexing configurations to the network device.
  • the terminal device receives or detects, on a first carrier of the one or more carriers, a random access response (RAR) for the random access preamble from the network device.
  • This first carrier is associated with the first multiplexing configuration.
  • the terminal device e.g., NB-IoT devices using the same PRACH resources are able to identify the respective RAR.
  • the terminal device detects a target downlink control channel including a code sequence index corresponding to the first multiplexing configuration, and/or if the terminal device detects a target downlink shared channel including the code sequence index, the terminal device is able to determine, among the one or more RARs, a target RAR for the random access preamble. In this way, the terminal device can identify the expected RAR based on code sequence index carried by the RAR.
  • FIG. 1A illustrates an example environment 100 in which example embodiments of the present disclosure can be implemented.
  • the environment 100 which may be a part of a communication network, comprises a terminal device 110-1, a terminal device 110-2, a terminal device 110-3 and a terminal device 110-4 which are collectively referred to as the terminal device 110.
  • these terminal devices may be NB-IoT devices. Without any limitation, these terminal devices may also have different device types, for example, legacy terminal device and NB-IoT device.
  • the environment 100 further comprises a network device 120-1 (for example, a base station) and a network device 120-2 (for example, a network access device for non-terrestrial network, NTN) which are collectively referred to as the network device 120.
  • a network device 120-1 for example, a base station
  • a network device 120-2 for example, a network access device for non-terrestrial network, NTN
  • FIG. 1B illustrates an example signaling process 100B of four-step random access.
  • the 4-step random access includes four signaling steps.
  • the terminal device transmits a message 1 (Msg 1) 130 including random access preambles (which may be also referred to physical random access channel, PRACH) to a network device to initiate the random access.
  • Msg 1 message 1
  • PRACH physical random access channel
  • the network device transmits a random access response (RAR) , i.e., message 2 (Msg 2) 140, for the random access preambles to the terminal device.
  • RAR random access response
  • the terminal device transmits a message 3 (Msg 3) 150 using the resources allocated in the RAR to the network device.
  • the network device transmits a message 4 (Msg) 4 160 to the terminal device.
  • Msg message 4
  • the Msg 3 and Msg 4 may be used for the contention-based solution.
  • the random access procedure may be also contention-free.
  • the terminal devices may transmit, on the same time-frequency PRACH resources, random access preambles that are spread by orthogonal code sequences.
  • the network device may transmit the respective RARs.
  • Msg 1 and Msg A can be used interchangeably, and the terms “Msg 2” and “Msg B” can be used interchangeably.
  • FIG. 1D illustrates some example code domain multiplexing levels.
  • n represents an index of an orthogonal code sequence “w n (i) ” .
  • the terminal device may spread a random access preamble by applying an orthogonal code sequence to the random access preamble. Specifically, multiplying a code unit/element (e.g., “+1” or “-1” in a sequence) and one or more symbols for the random access preamble. Generally, the more symbols to which one code unit is applied or multiplied by a code unit, the more resources required for decoding the random access preamble. As shown in FIG.
  • one code unit is applied to a symbol in a random access symbol group, and this may be also referred to as “intra-symbol group multiplexing level” .
  • intra-symbol group multiplexing level if the random access preamble is spread in the intra-symbol group multiplexing level, the spread symbol length of each code unit is smaller than one random access symbol group.
  • one code unit is applied to a plurality of symbols in different random access symbol groups, and this may be also referred to as “inter-symbol group multiplexing level” .
  • the random access preamble is spread in the inter-symbol group multiplexing level
  • the spread symbols are distributed in different random access symbol groups and the spread symbol length of each code unit is smaller than an NPRACH repetition.
  • one code unit is applied to a plurality of symbols crossing NPRACH repetitions, and this may be also referred to as “repetition multiplexing level” .
  • the random access preamble is spread in the repetition multiplexing level
  • the spread symbols are distributed in different NPRACH repetitions, e.g., the NPRACH repetitions 1 and 2.
  • the complexity of decoding random access preamble which is spread in the repetition multiplexing level is higher than that of the inter-symbol group multiplexing level.
  • the complexity of decoding random access preamble which is spread in the inter-symbol group multiplexing level is higher than that of the intra-symbol group multiplexing level
  • FIG. 2 illustrates an example signaling process 200 for the random access by applying the orthogonal code sequence to Msg 1 according to some embodiments of the present disclosure.
  • the process 200 will be described with reference to FIG. 1A. It would be appreciated that although the process 200 has been described with respect to communication environment of FIG. 1A, this process 200 may be likewise applied to other communication environments.
  • the terminal device 110 may initiate a random access in an NB-IoT physical uplink shared channel (NPUSCH) .
  • NPUSCH physical uplink shared channel
  • some NB-IoT devices may be allocated with the same PUSCH resource pool.
  • the terminal device 110 may also use the same PUSCH resources to initial a random access with symbols spread by the orthogonal code sequence using the respective multiplexing configuration. That is, the NPRACH may be transmitted in Msg 1, Msg A or NPUSCH.
  • the information on the code domain multiplexing may indicate a code sequence type, a multiplexing level, a code sequence length, a codebook index, an OCC sequence length and/or an OCC sequence index.
  • the code sequence type may include OCC type, m sequence type, Gold sequence type, Walsh-Hadamard sequence type and any other sequence types.
  • the multiplexing level may include intra-symbol group multiplexing level, inter-symbol group multiplexing level and repetition multiplexing level as mentioned above.
  • the code sequence length may specify the number of code units in the orthogonal code sequence. As shown in Table 4, the length of the orthogonal code sequence is four.
  • the length of an orthogonal code sequence may be equal to the number of terminal device groups using the orthogonal code sequences.
  • a first terminal device group may use the orthogonal code sequence identified by index “0” (i.e., [+1 +1 +1 +1] )
  • a second terminal device group may use the orthogonal code sequence identified by index “1” (i.e., [+1 -1 +1 -1] )
  • the UL transmissions from the terminal devices of different can be orthogonal due to the characteristics of the orthogonal code sequence.
  • the same orthogonal code sequence may be multiplexed using the same orthogonal code sequence in different time-frequency resources by the terminal devices in the same terminal device group.
  • the same PRACH time-frequency resources may be configured by the network or is the result that the terminal device randomly selects the PRACH resources.
  • the OCC sequence length (which may be also referred to as “OCC-length” ) may specify the number of code units in an OCC sequence.
  • the codebook index may be the index of an orthogonal code sequence.
  • the codebook index may be also referred to as an orthogonal code sequence index.
  • the OCC sequence index i.e., OCC-index
  • the terminal device may spread the random access preamble following the multiplexing configuration, for example, using the orthogonal code sequence identified by the codebook mark, using the indicated code sequence type, using the indicated multiplexing level and so on.
  • the multiplexing configuration may be one of a plurality of multiplexing configurations configured by the network device 120, and the terminal device 110 may randomly select a multiplexing configuration from the plurality of multiplexing configurations.
  • the multiplexing configuration may be indicated by a PDCCH order.
  • the network device 120 may transmit the RAR 235 in Msg 2 or Msg B.
  • the network device 120 may transmit another response message to the terminal device 110. That is, the terminal device 110 may, during the RAR window, detect the RAR in response to the random access preamble 215 or detect the other response message in response to the initiation of the random access in NPUSCH.
  • the starting time of the RAR window may be calculated based on an ending time of a last repetition for the random access preamble, a first number of subframes and a second number of subframes.
  • first number of subframes and X subframes may be used interchangeably
  • second number of subframes and Y subframes may be used interchangeably.
  • the RAR window may start at the subframe that contains the end of the last preamble repetition plus X and Y subframes.
  • the format of random access preamble 215 is of preamble format 0, and the number of NPRACH repetition is 64, then the X subframes is determined as 41 subframes.
  • the Y subframes may be determined based on the multiplexing configuration.
  • the second number of the subframes may be related to the multiplexing level indicated in the multiplexing configuration. For example, the second number in the repetition multiplexing level is greater than another second number in the inter-symbol group multiplexing level. As mentioned above, the complexity of the repetition multiplexing level is above that of the inter-symbol group multiplexing level, and thus the RAR may be delayed for a longer time. Similarly, the second number in the inter-symbol group multiplexing level is greater than the respective second number in the intra-symbol group multiplexing level. In addition, the longer orthogonal code sequence, the greater second number of subframes.
  • the above multiplexing configuration may be also referred to as the first multiplexing configuration
  • the random access preamble 215 may be also referred to as a first random access preamble
  • the above the RAR window may be also referred to as a first RAR window.
  • the terminal device 110 transmits to the network device 120 a second random access preamble that is spread based on a second multiplexing configuration
  • the terminal device 120 receives from the network device 110 a second RAR for the second random access preamble during a second RAR window.
  • the second multiplexing configuration specifies a second code sequence length shorter than the first code sequence length
  • the second number of subframes is greater than the respective second number of subframes for determining the starting time of the second RAR.
  • the second multiplexing configuration indicates that a code unit of the orthogonal code sequence is applied to a third number of symbols in the first random access preamble
  • the second multiplexing configuration indicates that a code unit of a respective orthogonal code sequence is applied to a fourth number of symbols in the second random access preamble, and the fourth number is smaller than the third number of symbols
  • the second number of subframes is greater than the respective second number of subframes for determining the starting time of the second RAR.
  • the second number of subframes is greater than the respective second number of subframes for determining the starting time of the second RAR.
  • the second number of subframes is greater than the respective second number of subframes for determining the starting time of the second RAR.
  • the fifth number of subframes may be determined from Table 5, based on a format of the random access preamble 215, the number of repetitions of narrow band (NB) -internet of things (IoT) physical random access channel (NPRACH) and the multiplexing configuration.
  • NB narrow band
  • IoT internet of things
  • NPRACH physical random access channel
  • the RAR window starts at the subframe that contains the end of the last preamble repetition plus Z subframes (i.e., the fifth number of subframes) and has length ra-ResponseWindowSize for the corresponding enhanced coverage level, where value Z is determined from Table 4 based on the used preamble format and the number of NPRACH repetitions. It is to be understood that the “X, Y and Z” used herein are only for discussion purposes, and they can be replaced by any other terms.
  • FIG. 3A illustrates an example of a starting time and size of the RAR window in the case that Msg 1 is applied with the orthogonal code sequence according to some embodiments of the present disclosure. Specifically, FIG. 3A shows an example starting time of the RAR window in a terrestrial network (TN) .
  • TN terrestrial network
  • the block 302 represents the last repetition of the random access preamble 215.
  • the time occasion 304 represents the end of the last repetition 215.
  • the time length 308 represents the first number subframes (i.e., X subframes) and the time length 310 represents the second number of subframes (i.e., Y subframes) .
  • the time occasion 306 represents the starting time of the RAR window 307.
  • the time length 307 represents the size of the RAR window which is further discussed below.
  • the time length 312 represents the fifth number of subframes (i.e. Z subframes) .
  • FIG. 3A shows an example starting time of the RAR window in a terrestrial network (TN) .
  • TN terrestrial network
  • the starting time of the RAR window is calculated based on an ending time 304 of a last repetition for the random access preamble, a first number of subframes 308, a second number of subframes 310 and the RTT 314.
  • the RAR window may start at the subframe that contains the end of the last preamble repetition plus X and Y subframes plus “UE-eNB RTT” .
  • the size of the RAR window may be selected from a set of candidate sizes.
  • the size of the RAR window is selected based on a coverage level.
  • the set of candidate sizes may include ⁇ pp2, pp3, pp4, pp5, pp6, pp7, pp8, pp10 ⁇ (the definition of “pp” is discussed above) .
  • These candidate sizes may be referred to the original sizes in some embodiments of the disclosure. Since the introduction of the code domain spreading, the blind detection may consume more time. Thus, in some embodiments, the RAR window may be extended.
  • the set of candidate sizes may further include one or more candidate sizes associated with the multiplexing configuration.
  • the terminal device may be difficult to identify the expected RAR on the RAR resources. Some of following embodiments may enable the terminal device identify the expected RAR correctly.
  • FIG. 4 illustrates another example signaling process 400 for the random access by applying the orthogonal code sequence to Msg 1 according to some embodiments of the present disclosure.
  • the process 400 will be described with reference to FIG. 1A. It would be appreciated that although the process 400 has been described with respect to communication environment of FIG. 1A, this process 400 may be likewise applied to other communication environments.
  • the network device 120 transmits (410) association information 415 to the terminal device 110, and the association information 415 indicates an association between one or more carriers and one or more multiplexing configurations.
  • the terminal device 110 receives (420) the association information 415 accordingly.
  • a multiplexing configuration of the one or more multiplexing configurations may include information on code domain multiplexing.
  • the multiplexing configuration of the one or more multiplexing configurations may specify the similar information as discussed above, for example, code type, code length, OCC length and so on.
  • the association information may be carried by PDCCH order for a terminal device.
  • the PDCCH order may include a multiplexing configuration and a carrier for detecting the RAR, and the PDCCH order triggers the terminal device to perform a random access.
  • the association information may be carried by a broadcast message (e.g., system information block, SIB1) .
  • SIB1 system information block
  • the association information carried in the broadcast message may include an association list that indicates a carrier of the one or more carriers is associated with a respective multiplexing configuration of the one or more multiplexing configurations.
  • the association list may include only one pair of the carrier for detecting RAR and the multiplexing configuration.
  • the one or more carriers may be divided into carrier groups.
  • a plurality of the carriers configured for the transmission of the RAR may be divided into a number of carrier groups.
  • the number of carrier groups may be determined based on an orthogonal code sequence length (e.g., OCC-length) .
  • the number (of carrier groups) may be based on the number of the terminal device groups which use or select the same NPRACH resources.
  • the terminal device 110 transmits (440) a random access preamble 435 that is spread by an orthogonal code sequence based on a first multiplexing configuration of the one or more multiplexing configurations.
  • the network device 120 detects and receives (440) the random access preamble 435 accordingly.
  • the one or more multiplexing configurations may be configured by the network device 120, predefined or preconfigured.
  • the network device 120 may determine the first multiplexing configuration by blind detecting the random access preamble 435.
  • the network device 120 transmits (450) RAR 455 a first carrier which is associated with the first multiplexing configuration.
  • the terminal device 110 detects and receives (460) RAR 455 on the first carrier.
  • FIG. 5 illustrates a further example signaling process 500 for the random access by applying the orthogonal code sequence to Msg 1 according to some embodiments of the present disclosure.
  • the process 500 will be described with reference to FIG. 1A. It would be appreciated that although the process 500 has been described with respect to communication environment of FIG. 1A, this process 500 may be likewise applied to other communication environments.
  • the terminal device 110 transmits (530) a random access preamble 535 to the network device 120.
  • the random access preamble 535 is spread by an orthogonal code sequence based on a first multiplexing configuration of a plurality multiplexing configurations.
  • the plurality of multiplexing configurations may be predefined or preconfigured for the terminal device 110 and the network device 120.
  • the plurality of multiplexing configurations may be configured by the network device 120 to the terminal device 110.
  • the network device 120 may transmit (510) the plurality of multiplexing configurations 515 to the terminal device 110.
  • the terminal device 110 may receive (520) the plurality of multiplexing configurations 515 accordingly.
  • a multiplexing configuration of the plurality of multiplexing configurations includes information on code domain multiplexing.
  • the multiplexing configuration of the plurality of multiplexing configurations may specify the similar information as discussed above, for example, code type, code length, OCC length and so on.
  • the network device 120 may determine the RA-RNTI further based on information related to a transmission of the random access preamble 515.
  • the RA-RNTI may be calculated based on the orthogonal code sequence index in the first multiplexing configuration and the information related to a transmission of the random access preamble 515.
  • SFN_id represents the first radio frame identifier (ID) in which the random access preamble 535 is transmitted
  • the carrier_id represents the ID of the carrier for transmitting the random access preamble 535
  • the orthogonal codeword set index represents the orthogonal code sequence index.
  • the function “f (orthogonal codeword set index) ” may be designed to be used for calculating a unique RA-RNTI corresponding to a certain SFN_id, a certain carrier_id and a certain orthogonal codeword set index. In other words, if any of the SFN_id, carrier_id and orthogonal codeword set index (orthogonal code sequence index) is different, then the RA-RNTI should be different.
  • the function “f (orthogonal codeword set index) ” should be aligned between the terminal device 110 and the network device 120. In this way, the terminal device 110 may determine the same RA-RNTI to de-scramble the RAR. In some embodiments, if the terminal device 110 transmits the random access preamble without code domain multiplexing, the orthogonal codeword set index may be set to “zero (0) ” .
  • the calculation of the RA-RNTI is further based on the total number of available non-anchor carriers for a transmission of the random access preamble.
  • the calculation of the RA-RNTI may be based on the number of non-anchor carriers of the network.
  • the maximum number of non-anchor carriers represents the total number of non- anchor carriers for the NPRACH in NB-IoT or the total number of non-anchor carriers of the network.
  • RA-RNTI 1 + floor (SFN_id/4) + 256*carrier_id + f (OCC_index, Maximum number of non-anchor carriers for NB-IoT ) (3)
  • OCC-index represents an index of an OCC sequence.
  • RA-RNTI 1 + floor (SFN_id/4) + 256*carrier_id + (occ-index+1) *256* (maxNonAnchorCarriers+1) (4)
  • the range of RA-RNTI is from 1 ⁇ 20480.
  • the value range 1-4096 of RA-RNTI are the terminal devices without OCC multiplexing.
  • the value range 4097 ⁇ 8192 of RA-RNTI are the terminals with the OCC-index 0 (or the 1 st orthogonal code sequence) .
  • the value range 8193 ⁇ 12288 of RA-RNTI are the terminals with the OCC-index 1 (or the 2 nd orthogonal code sequence) .
  • the value range 12289 ⁇ 16384 of RA-RNTI are the terminals with the OCC-index 2 (or 3 rd orthogonal code sequence) .
  • the value range 16385 ⁇ 20480 of RA-RNTI are the terminals with the OCC-index 3 (or 4 th orthogonal code sequence) .
  • Equation (5) is adapted to the situation in which orthogonal code sequence indexes starting from “0” .
  • the portion “f (orthogonal codeword set index) ” of equation (1) or f (OCC_index, Maximum number of non-anchor carriers for NB-IoT ) of equations (2) - (4) may be alternatively constructed to comply with any other orthogonal code sequence indexes.
  • equations (1) - (4) may be further adjusted on demand which is not limited in this disclosure.
  • the network device transmits (570) RAR 575 using the RNTI calculated based on the first multiplexing configuration.
  • the terminal device 110 may determine the same RNTI using the same RNTI generation function. Thus, the terminal device 110 may be aware of the RNTI applied to the RAR 575. Then, the terminal device 110 receives (580) the RAR 575 for the random access preamble 535 using the RNTI. In an example, the terminal device 110 may use the RA-RNTI to de-scramble the PDCCH of RAR 575 to determine the expected PDCCH, and then receive the respective PDSCH of the RAR 575 based on the expected PDCCH.
  • the terminal device 110 may also initiates a random access in an NB-IoT physical uplink shared channel (NPUSCH) as mentioned above. Then, the terminal device 110 may detect the other response message in response to the initiation of the random access in NPUSCH. In some embodiments, at least a portion of the other response message is scrambled with the RNTI.
  • NPUSCH NB-IoT physical uplink shared channel
  • the RNTI for NB-IoT UEs can be enhanced to indicate the expected RARs for the random access a preamble using orthogonal code sequence. For example, calculating the RNTI based on the first radio frame ID with the PRACH in which the Random Access Preamble is transmitted (SFN_id) , carrier ID (anchor carrier is 0, non-anchor carrier: 1 ⁇ maxNonAnchorCarriers) and a function of the orthogonal codeword set index (occ-index) .
  • the terminal devices that transmit the same preamble in MSG1 /MSGA or NPUSCH in the same physical resources with different orthogonal codewords is able to identify the RAR by the RNTI.
  • the contention in Msg3 can be alleviated, the PRACH/Msg1/MsgA capacity can be enhanced, and the uplink transmission can be finished in a shorter time and less power consumption.
  • FIG. 6A illustrates a further example signaling process 600 for the random access by applying the orthogonal code sequence to Msg 1 according to some embodiments of the present disclosure.
  • the process 600 will be described with reference to FIG. 1A. It would be appreciated that although the process 600 has been described with respect to communication environment of FIG. 1A, this process 600 may be likewise applied to other communication environments.
  • the terminal device 110 transmits (630) a random access preamble 635 to the network device 120.
  • the random access preamble 635 is spread by an orthogonal code sequence based on a first multiplexing configuration of a plurality of multiplexing configurations.
  • the plurality of multiplexing configurations may be predefined or preconfigured for the terminal device 110 and the network device 120.
  • the plurality of multiplexing configurations may be configured by the network device 120 to the terminal device 110.
  • the network device 120 may transmit (610) the plurality of multiplexing configurations 615 to the terminal device 110.
  • the terminal device 110 may receive (620) the plurality of multiplexing configurations 515 accordingly.
  • a multiplexing configuration of the plurality of multiplexing configurations includes information on code domain multiplexing.
  • the multiplexing configuration of the plurality of multiplexing configurations may specify the similar information as discussed above, for example, code type, code length, OCC length and so on.
  • the network device 120 may determine the first multiplexing configuration from the plurality of multiplexing configurations, since the plurality of multiplexing configurations is preconfigured or configured by the network device 120. Then, the network device 120 includes, into at least one of a PDCCH or a PDSCH of the RAR for the random access preamble 635, an orthogonal code sequence index corresponding to the first multiplexing configuration, for example, the OCC-index indicated by the first multiplexing configuration. The network device 120 further transmits (650) the RAR 655 on the associated RAR resources to the terminal device 110.
  • the network device 120 includes the orthogonal code sequence index into PDCCH of RAR 655.
  • the terminal device 110 detects and receives (660) the PDCCHs of RARs on the associated RAR resources.
  • the associated RAR resources may be determined based on the random access preamble 635.
  • the terminal device 110 may determine the expected RAR correctly. Further, the terminal device 110 may determine the PDSCH for the expected RAR based on the target PDCCH.
  • the network device 120 includes the orthogonal code sequence index into PDSCH of RAR 655.
  • the terminal device 110 detects and receives (660) all the PDCCHs of RARs on the associated RAR resources.
  • the associated RAR resources may be determined based on the random access preamble 635.
  • the terminal device 110 may detect and receive one or more PDSCHs associated with all the PDCCHs.
  • the terminal device 110 determines (670) , among the one or more PDSCHs, a target PDSCHs comprising the code sequence index. In this way, the terminal device 120 may determine the expected RAR accordingly.
  • the transmitted RAR (for example, RARs 235, 455, 575, 655) may indicate a multiplexing configuration to be used for Msg 3.
  • the indication of the multiplexing configuration may be included in the PDSCH for RAR, since PDCCH for RAR is of DCI format N1 which cannot configure Msg 3.
  • the PDSCH may use 2 bits in the reserved bits in MAC RAR for NB-IoT UEs to indicate the multiplexing configuration.
  • the PDSCH may use MSB 2biys in Temporary C-RNTI in MAC RAR for NB-IoT UEs to indicate the multiplexing configuration.
  • the PDSCH may use LSB 2bits in Temporary C-RNTI in MAC RAR for NB-IoT UEs to indicate the multiplexing configuration.
  • the terminal device 110 may transmit Msg 3 with a chosen code domain multiplexing configuration, based on the indication from Msg 2 (MAC PDU) .
  • the network device 120 may detect Msg 3 accordingly.
  • the information on the code domain multiplexing indicates at least one of the following: a code sequence type; a multiplexing level; a code sequence length; a codebook index; an orthogonal cover code (OCC) sequence length; or an OCC sequence index.
  • the starting time of the RAR window is calculated based on an ending time of a last repetition for the random access preamble, a first number of subframes and a second number of subframes, the first number of subframes is determined based on a format of the random access preamble and the number of repetitions of narrow band (NB) -internet of things (IoT) physical random access channel (NPRACH) for the random access preamble, and the second number of subframes is determined based on the multiplexing configuration.
  • NB narrow band
  • IoT internet of things
  • NPRACH physical random access channel
  • the random access preamble is a first random access preamble
  • the RAR window is a first RAR window
  • the multiplexing configuration is a first multiplexing configuration
  • the terminal device further: transmits, to the network device, a second random access preamble that is spread based on a second multiplexing configuration; and receives, from the network device, a second RAR for the second random access preamble during a second RAR window.
  • the second number of subframes is greater than a further second number of subframes for determining a further starting time of the second RAR window, in the case that at least one of the following: the first multiplexing configuration comprises a first code sequence length and the second multiplexing configuration comprises a second code sequence length shorter than the first code sequence length; the first multiplexing configuration indicates that a code unit of the orthogonal code sequence is applied to a third number of symbols in the first random access preamble, and the second multiplexing configuration indicates that a code unit of a respective orthogonal code sequence is applied to a fourth number of symbols in the second random access preamble, and the fourth number is smaller than the third number of symbols; the first multiplexing configuration comprises a repetition multiplexing level and the second multiplexing configuration comprises an inter-symbol group multiplexing level; or the first multiplexing configuration comprises an inter-symbol multiplexing level and the second multiplexing configuration comprises an intra-symbol group multiplexing level.
  • the starting time of the RAR window is calculated based on an ending time of a last repetition for the random access preamble and a fifth number of subframes, and the fifth number of subframes is determined based on the multiplexing configuration, a format of the random access preamble and a number of repetitions of NPRACH for the random access preamble.
  • a portion corresponding to the multiplexing configuration of the fifth number of subframes is related to at least one of a code sequence length or a multiplexing level in the multiplexing configuration.
  • the size of the RAR window is selected from a set of candidate sizes comprising one or more candidate sizes associated with the multiplexing configuration and a plurality of original candidate sizes, and a candidate size of the one or more candidate sizes is greater than an original candidate size of the plurality of initial candidate sizes.
  • the orthogonal code sequence comprises an OCC sequence
  • the terminal device is one of a plurality of narrow band (NB) -internet of things (IoT) devices that is allocated with the same time-frequency radio resource for an NB-IoT physical random access channel (NPRACH)
  • the network device is a network access device of a non-terrestrial network (NTN)
  • RTT round-trip time
  • the network device 120 receives, from a terminal device, a random access preamble that is spread by an orthogonal code sequence based on a multiplexing configuration.
  • the multiplexing configuration comprises information on code domain multiplexing.
  • the network device 120 transmits, to the terminal device, a random access response (RAR) for the random access preamble, such that the terminal device to receive the RAR during an RAR window, wherein at least one of a starting time or a size of the RAR window is associated with the multiplexing configuration.
  • RAR random access response
  • the information on the code domain multiplexing indicates at least one of the following: a code sequence type; a multiplexing level; a code sequence length; a codebook index; an orthogonal cover code (OCC) sequence length; or an OCC sequence index.
  • the starting time of the RAR window is calculated based on an ending time of a last repetition for the random access preamble, a first number of subframes and a second number of subframes, the first number of subframes is determined based on a format of the random access preamble and the number of repetitions of narrow band (NB) -internet of things (IoT) physical random access channel (NPRACH) for the random access preamble, and the second number of subframes is determined based on the multiplexing configuration.
  • NB narrow band
  • IoT internet of things
  • NPRACH physical random access channel
  • the random access preamble is a first random access preamble
  • the RAR window is a first RAR window
  • the multiplexing configuration is a first multiplexing configuration
  • the network device further receives, from the terminal device, a second random access preamble that is spread based on a second multiplexing configuration; and transmits, to the terminal device, a second RAR for the second random access preamble, such that the terminal device to receive the second RAR during a second RAR window.
  • the starting time of the RAR window is calculated based on an ending time of a last repetition for the random access preamble and a fifth number of subframes, and the fifth number of subframes is determined based on the multiplexing configuration, a format of the random access preamble and a number of repetitions of NPRACH for the random access preamble.
  • the network device 120 transmits, to a terminal device, association information that indicates an association between one or more carriers and one or more multiplexing configurations.
  • a multiplexing configuration of the one or more multiplexing configurations comprises information on code domain multiplexing.
  • the network device 120 receives, from the terminal device, a random access preamble that is spread by an orthogonal code sequence based on a first multiplexing configuration of the one or more multiplexing configurations.
  • the network device 120 transmits, to the terminal device and on a first carrier of the one or more carriers, a random access response (RAR) for the random access preamble.
  • the first carrier is associated with the first multiplexing configuration.
  • FIG. 11 illustrates a flowchart of an example method 1100 implemented at a terminal device according to some embodiments of the present disclosure.
  • the method 1100 can be implemented at the terminal device 110 shown in FIG. 1A.
  • the method 1100 will be described with reference to FIG. 1A. It is to be understood that the method 1100 may include additional acts not shown and/or may omit some shown acts, and the scope of the present disclosure is not limited in this regard.
  • the first multiplexing configuration comprises a codebook index
  • the terminal device determines the RNTI by: determining the RNTI based on the codebook index.
  • the codebook index comprises an OCC sequence index.
  • the plurality of multiplexing configurations is preconfigured for the terminal device and the network device.
  • the information on the code domain multiplexing indicates at least one of the following: a code sequence type; a multiplexing level; a code sequence length; a codebook index; an orthogonal cover code (OCC) sequence length; or an OCC sequence index.
  • the orthogonal code sequence comprises an OCC sequence; and/or the terminal device is one of a plurality of narrow band (NB) -internet of things (IoT) devices that is allocated with the same time-frequency radio resource for an NB-IoT physical random access channel (NPRACH) .
  • NB narrow band
  • IoT internet of things
  • FIG. 14 illustrates a flowchart of an example method 1400 implemented at a network device according to some embodiments of the present disclosure.
  • the method 1400 can be implemented at the network device 120 shown in FIG. 1A.
  • the method 1400 will be described with reference to FIG. 1A. It is to be understood that the method 1400 may include additional acts not shown and/or may omit some shown acts, and the scope of the present disclosure is not limited in this regard.
  • the present 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, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to any of Figs. 2 to 17.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • the terminal device is further caused to: transmit, to the network device, a second random access preamble that is spread based on a second multiplexing configuration; and receive, from the network device, a second RAR for the second random access preamble during a second RAR window.
  • the second number of subframes is greater than a further second number of subframes for determining a further starting time of the second RAR window, in the case that at least one of the following: the first multiplexing configuration comprises a first code sequence length and the second multiplexing configuration comprises a second code sequence length shorter than the first code sequence length; the first multiplexing configuration indicates that a code unit of the orthogonal code sequence is applied to a third number of symbols in the first random access preamble, and the second multiplexing configuration indicates that a code unit of a respective orthogonal code sequence is applied to a fourth number of symbols in the second random access preamble, and the fourth number is smaller than the third number of symbols; the first multiplexing configuration comprises a repetition multiplexing level and the second multiplexing configuration comprises an inter-symbol group multiplexing level; or the first multiplexing configuration comprises an inter-symbol multiplexing level and the second multiplexing configuration comprises an intra-symbol group multiplexing level.
  • the starting time of the RAR window is calculated based on an ending time of a last repetition for the random access preamble and a fifth number of subframes
  • the fifth number of subframes is determined based on the multiplexing configuration, a format of the random access preamble and a number of repetitions of NPRACH for the random access preamble.
  • a portion corresponding to the multiplexing configuration of the fifth number of subframes is related to at least one of a code sequence length or a multiplexing level in the multiplexing configuration.
  • the orthogonal code sequence comprises an OCC sequence
  • the terminal device is one of a plurality of narrow band (NB) -internet of things (IoT) devices that is allocated with the same time-frequency radio resource for an NB-IoT physical random access channel (NPRACH)
  • the network device is a network access device of a non-terrestrial network (NTN)
  • RTT round-trip time
  • a network device comprising: a processor, and the processor is configured to cause the terminal device to: receive, from a terminal device, a random access preamble that is spread by an orthogonal code sequence based on a multiplexing configuration, wherein the multiplexing configuration comprises information on code domain multiplexing; and transmit, to the terminal device, a random access response (RAR) for the random access preamble, such that the terminal device to receive the RAR during an RAR window, wherein at least one of a starting time or a size of the RAR window is associated with the multiplexing configuration.
  • RAR random access response
  • the starting time of the RAR window is calculated based on an ending time of a last repetition for the random access preamble, a first number of subframes and a second number of subframes
  • the first number of subframes is determined based on a format of the random access preamble and the number of repetitions of narrow band (NB) -internet of things (IoT) physical random access channel (NPRACH) for the random access preamble
  • the second number of subframes is determined based on the multiplexing configuration.
  • the network device is further caused to: receive, from the terminal device, a second random access preamble that is spread based on a second multiplexing configuration; and transmit, to the terminal device, a second RAR for the second random access preamble, such that the terminal device to receive the second RAR during a second RAR window.
  • the starting time of the RAR window is calculated based on an ending time of a last repetition for the random access preamble and a fifth number of subframes
  • the fifth number of subframes is determined based on the multiplexing configuration, a format of the random access preamble and a number of repetitions of NPRACH for the random access preamble.
  • the orthogonal code sequence comprises an OCC sequence
  • the terminal device is one of a plurality of narrow band (NB) -internet of things (IoT) devices that is allocated with the same time-frequency radio resource for an NB-IoT physical random access channel (NPRACH) .
  • NB narrow band
  • IoT internet of things
  • a network device comprising: a processor, and the processor is configured to cause the network device to: transmit, to a terminal device, association information that indicates an association between one or more carriers and one or more multiplexing configurations, wherein a multiplexing configuration of the one or more multiplexing configurations comprises information on code domain multiplexing; receive, from the terminal device, a random access preamble that is spread by an orthogonal code sequence based on a first multiplexing configuration of the one or more multiplexing configurations; and transmit, to the terminal device and on a first carrier of the one or more carriers, a random access response (RAR) for the random access preamble, wherein the first carrier is associated with the first multiplexing configuration.
  • RAR random access response
  • the network device is caused to transmit the association information by at least one of the following: transmitting, to the terminal device, a physical downlink control channel (PDCCH) order that comprises a multiplexing configuration and a carrier for detecting the RAR, wherein the PDCCH order triggers the terminal device to perform a random access; or transmitting, to the terminal device, a broadcast message that comprises a multiplexing configuration and a carrier for detecting the RAR.
  • a physical downlink control channel (PDCCH) order that comprises a multiplexing configuration and a carrier for detecting the RAR, wherein the PDCCH order triggers the terminal device to perform a random access
  • a broadcast message that comprises a multiplexing configuration and a carrier for detecting the RAR.
  • the information on the code domain multiplexing indicates at least one of the following: a code sequence type; a multiplexing level; a code sequence length; a codebook index; an orthogonal cover code (OCC) sequence length; or a OCC sequence index.
  • a plurality of carriers configured for a transmission of the RAR is divided into a first number of carrier groups, and the plurality of carriers comprises the one or more carriers, and the first number is determined based on a code sequence length for a multiplexing configuration.
  • a terminal device comprising: a processor, and the processor is configured to cause the terminal device to: transmit, to a network device, a random access preamble that is spread by an orthogonal code sequence based on a first multiplexing configuration of a plurality of multiplexing configurations, wherein a multiplexing configuration of the plurality of multiplexing configurations comprises information on code domain multiplexing; determine a radio network temporary identifier (RNTI) based on the first multiplexing configuration and information related to a transmission of the random access preamble; and receive, from the network device, a random access response (RAR) for the random access preamble using the RNTI.
  • RNTI radio network temporary identifier
  • the information on the code domain multiplexing indicates at least one of the following: a code sequence type; a multiplexing level; a code sequence length; a codebook index; an orthogonal cover code (OCC) sequence length; or an OCC sequence index.
  • the terminal device is caused to determine the RNTI by:determining the RNTI further based on the total number of available non-anchor carriers for a transmission of the random access preamble.
  • the codebook index comprises an OCC sequence index.
  • the orthogonal code sequence comprises an OCC sequence
  • the terminal device is one of a plurality of narrow band (NB) -internet of things (IoT) devices that is allocated with the same time-frequency radio resource for an NB-IoT physical random access channel (NPRACH) .
  • NB narrow band
  • IoT internet of things
  • the information on the code domain multiplexing indicates at least one of the following: a code sequence type; a multiplexing level; a code sequence length; a codebook index; an orthogonal cover code (OCC) sequence length; or an OCC sequence index.
  • the codebook index comprises an OCC sequence index.
  • a terminal device comprising: a processor, and the processor is configured to cause the terminal device to: transmit, to a network device, a random access preamble that is spread by an orthogonal code sequence based on a first multiplexing configuration of a plurality of multiplexing configurations, wherein a multiplexing configuration of the plurality of multiplexing configurations comprises information on code domain multiplexing; detect, on random access response (RAR) resources associated with the random access preamble, at least one of i) one or more downlink control channels of one or more RARs, or ii) one or more downlink shared channels of the one or more RARs; and determine, among the one or more RARs, a target RAR for the random access preamble based on detecting at least one of: a target downlink control channel among the one or more downlink control channels, the target downlink control channel comprising an orthogonal code sequence index corresponding to the first multiplexing configuration, or a target downlink shared channel among the one or more downlink shared channels, the
  • the information on the code domain multiplexing indicates at least one of the following: a code sequence type; a multiplexing level; a code sequence length; a codebook index; an orthogonal cover code (OCC) sequence length; or an OCC sequence index.
  • a network device comprising: a processor, and the processor is configured to cause the terminal device to: receive, from a terminal device, a random access preamble that is spread by an orthogonal code sequence based on a first multiplexing configuration of a plurality of multiplexing configurations, wherein a multiplexing configuration of the plurality of multiplexing configurations comprises information on code domain multiplexing; include an orthogonal code sequence index corresponding to the first multiplexing configuration into at least one of a downlink control channel or a downlink shared channel of a random access response (RAR) for the random access preamble; and transmit, to the terminal device, the RAR on random access response (RAR) resources associated with the random access preamble.
  • RAR random access response
  • the orthogonal code sequence index is included in one or more reserved bits in downlink control information (DCI) transmitted in the target downlink control channel, and the DCI is of downlink control information (DCI) format N1; or the orthogonal code sequence index is included in one or more reserved bits in a media access control protocol data unit (MAC PDU) transmitted in the target downlink shared channel.
  • DCI downlink control information
  • DCI downlink control information
  • MAC PDU media access control protocol data unit
  • the information on the code domain multiplexing indicates at least one of the following: a code sequence type; a multiplexing level; a code sequence length; a codebook index; an orthogonal cover code (OCC) sequence length; or an OCC sequence index.
  • the orthogonal code sequence comprises an OCC sequence
  • the terminal device is one of a plurality of narrow band (NB) -internet of things (IoT) devices that is allocated with the same time-frequency radio resource for an NB-IoT physical random access channel (NPRACH) .
  • NB narrow band
  • IoT internet of things
  • a method of communication comprising: transmitting, by a terminal device to a network device, a random access preamble that is spread by an orthogonal code sequence based on a multiplexing configuration, wherein the multiplexing configuration comprises information on code domain multiplexing; and receiving, from the network device, a random access response (RAR) for the random access preamble during an RAR window, wherein at least one of a starting time or a size of the RAR window is associated with the multiplexing configuration.
  • RAR random access response
  • a method of communication comprising: receiving, by a network device from a terminal device, a random access preamble that is spread by an orthogonal code sequence based on a multiplexing configuration, wherein the multiplexing configuration comprises information on code domain multiplexing; and transmitting, to the terminal device, a random access response (RAR) for the random access preamble, such that the terminal device to receive the RAR during an RAR window, wherein at least one of a starting time or a size of the RAR window is associated with the multiplexing configuration.
  • RAR random access response
  • a method of communication comprising: receiving, by a terminal device from a network device, association information that indicates an association between one or more carriers and one or more multiplexing configurations, wherein a multiplexing configuration of the one or more multiplexing configurations comprises information on code domain multiplexing; transmit, to the network device, a random access preamble that is spread by an orthogonal code sequence based on a first multiplexing configuration of the one or more multiplexing configurations; and receive, from the network device and on a first carrier of the one or more carriers, a random access response (RAR) for the random access preamble, wherein the first carrier is associated with the first multiplexing configuration
  • RAR random access response
  • a method of communication comprising: transmitting, by a network device to a terminal device, association information that indicates an association between one or more carriers and one or more multiplexing configurations, wherein a multiplexing configuration of the one or more multiplexing configurations comprises information on code domain multiplexing; receiving, from the terminal device, a random access preamble that is spread by an orthogonal code sequence based on a first multiplexing configuration of the one or more multiplexing configurations; and transmitting, to the terminal device and on a first carrier of the one or more carriers, a random access response (RAR) for the random access preamble, wherein the first carrier is associated with the first multiplexing configuration.
  • RAR random access response
  • a method of communication comprising: transmitting, by a terminal device to a network device, a random access preamble that is spread by an orthogonal code sequence based on a first multiplexing configuration of a plurality of multiplexing configurations, wherein a multiplexing configuration of the plurality of multiplexing configurations comprises information on code domain multiplexing; detecting, on random access response (RAR) resources associated with the random access preamble, at least one of i) one or more downlink control channels of one or more RARs, or ii) one or more downlink shared channels of the one or more RARs; and determining, among the one or more RARs, a target RAR for the random access preamble based on detecting at least one of: a target downlink control channel among the one or more downlink control channels, the target downlink control channel comprising an orthogonal code sequence index corresponding to the first multiplexing configuration, or a target downlink shared channel among the one or more downlink shared channels, the target downlink control channel comprising
  • a method of communication comprising: receiving, by a network device from a terminal device, a random access preamble that is spread by an orthogonal code sequence based on a first multiplexing configuration of a plurality of multiplexing configurations, wherein a multiplexing configuration of the plurality of multiplexing configurations comprises information on code domain multiplexing; including an orthogonal code sequence index corresponding to the first multiplexing configuration into at least one of a downlink control channel or a downlink shared channel of a random access response (RAR) for the random access preamble; and transmitting, to the terminal device, the RAR on random access response (RAR) resources associated with the random access preamble.
  • RAR random access response

Landscapes

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

Abstract

Des modes de réalisation de la présente divulgation concernent des dispositifs, des procédés et un support lisible par ordinateur pour l'amélioration de l'accès aléatoire. Selon des modes de réalisation de la présente divulgation, un équipement terminal émet, vers un dispositif de réseau, un préambule d'accès aléatoire qui est étalé par une séquence de code orthogonal sur la base d'une configuration de multiplexage. La configuration de multiplexage comprend des informations sur le multiplexage de domaine de code. L'équipement terminal reçoit, en provenance du dispositif de réseau, une réponse d'accès aléatoire (RAR) pour le préambule d'accès aléatoire pendant une fenêtre RAR. Au moins l'un d'un temps de démarrage ou d'une taille de la fenêtre RAR est associé à la configuration de multiplexage. De cette manière, l'accès aléatoire peut être amélioré.
PCT/CN2024/085114 2024-03-30 2024-03-30 Dispositif, procédé et support lisible par ordinateur pour des communications Pending WO2025208253A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/085114 WO2025208253A1 (fr) 2024-03-30 2024-03-30 Dispositif, procédé et support lisible par ordinateur pour des communications

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/085114 WO2025208253A1 (fr) 2024-03-30 2024-03-30 Dispositif, procédé et support lisible par ordinateur pour des communications

Publications (1)

Publication Number Publication Date
WO2025208253A1 true WO2025208253A1 (fr) 2025-10-09

Family

ID=97265764

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/085114 Pending WO2025208253A1 (fr) 2024-03-30 2024-03-30 Dispositif, procédé et support lisible par ordinateur pour des communications

Country Status (1)

Country Link
WO (1) WO2025208253A1 (fr)

Similar Documents

Publication Publication Date Title
US20250142425A1 (en) Method, device and computer storage medium of communication
WO2023178624A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2024192688A1 (fr) Dispositif, procédé et support lisible par ordinateur pour communication
WO2023201490A1 (fr) Procédé, dispositif et support de stockage informatique destinés à la communication
EP4374638A1 (fr) Procédé, dispositif et support lisible par ordinateur destinés aux communications
WO2025208253A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications
WO2024000601A1 (fr) Procédés, dispositifs, ainsi que support de communication
WO2025059945A1 (fr) Dispositifs et procédés de communication
WO2025213424A1 (fr) Dispositif, procédé et support lisible par ordinateur pour les communications
WO2025231772A1 (fr) Dispositifs et procédés de communication
WO2025199980A1 (fr) Dispositifs et procédés de communication
WO2023193262A1 (fr) Procédés, dispositifs et support lisible par ordinateur destinés à la communication
WO2024044907A1 (fr) Procédés, dispositifs et support lisible par ordinateur destiné aux communications
WO2025217821A1 (fr) Dispositifs et procédés de transmission en sub-band full duplex
WO2023141999A1 (fr) Procédé, dispositif et support de stockage informatique destinés à des communications
WO2025160991A1 (fr) Dispositifs et procédés de transmission de nprach
WO2024168570A1 (fr) Dispositifs et procédés de communication
WO2024197899A1 (fr) Procédés, dispositifs et support de communication
WO2025199686A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications
WO2023168603A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2023133829A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2025160990A1 (fr) Dispositifs et procédés de transmission de nprach
WO2025231860A1 (fr) Dispositifs, procédés et support de communication
WO2024159494A1 (fr) Procédés, dispositifs et support lisible par ordinateur destiné aux communications
WO2023065332A1 (fr) Procédés, dispositifs et support de communication

Legal Events

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

Ref document number: 24933217

Country of ref document: EP

Kind code of ref document: A1