WO2022213257A1 - Procédé et appareil de configuration d'une partie de bande passante - Google Patents

Procédé et appareil de configuration d'une partie de bande passante Download PDF

Info

Publication number
WO2022213257A1
WO2022213257A1 PCT/CN2021/085628 CN2021085628W WO2022213257A1 WO 2022213257 A1 WO2022213257 A1 WO 2022213257A1 CN 2021085628 W CN2021085628 W CN 2021085628W WO 2022213257 A1 WO2022213257 A1 WO 2022213257A1
Authority
WO
WIPO (PCT)
Prior art keywords
bwp
initial
redcap
dedicated
message
Prior art date
Application number
PCT/CN2021/085628
Other languages
English (en)
Inventor
Yuantao Zhang
Hongmei Liu
Zhi YAN
Yingying Li
Haiming Wang
Original Assignee
Lenovo (Beijing) Limited
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 Lenovo (Beijing) Limited filed Critical Lenovo (Beijing) Limited
Priority to PCT/CN2021/085628 priority Critical patent/WO2022213257A1/fr
Publication of WO2022213257A1 publication Critical patent/WO2022213257A1/fr

Links

Images

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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal

Definitions

  • the present disclosure relates to wireless communication technology, especially to a method and an apparatus for bandwidth part configuration.
  • the communication system not only support the legacy UEs with normal capability, for example, the Enhanced Mobile Broadband (eMBB) UEs, the Ultra-Reliable and Low Latency Communications (URLLC) UEs, but also support the UEs with reduced capability i.e. RedCap UEs, such as the industrial wireless sensors, video surveillances, or wearables devices. Compared with the legacy UEs, the RedCap UEs may have reduced number of antennas, reduced bandwidth, etc.
  • eMBB Enhanced Mobile Broadband
  • URLLC Ultra-Reliable and Low Latency Communications
  • RedCap UEs still use the resources configured for legacy UEs, there might be some issues due to their reduced capability, such as the supported bandwidth thereof.
  • One embodiment of the present disclosure provides a method performed by a first user equipment (UE) , comprising: determining whether a first initial uplink (UL) bandwidth part (BWP) for the first UE is configured in a system information block; determining whether random access channel (RACH) occasions (ROs) are configured in the first initial UL BWP; and starting a RACH procedure in the first initial UL BWP or in a second UL initial BWP based on a determined RO.
  • UE user equipment
  • the method further comprises determining whether a first initial downlink (DL) BWP is configured for the first UE in the system information block.
  • DL downlink
  • the initial UL BWP is the first initial UL BWP if configured, and the initial UL BWP is the second initial UL BWP if the first initial UL BWP is not configured, and wherein the initial DL BWP is the first initial DL BWP if configured, and the initial DL BWP is a second initial DL BWP if the first initial UL BWP is not configured.
  • the method further comprises: in the case that the ROs are configured in the second initial UL BWP and no RO is configured in the first initial UL BWP, transmitting a first message of the RACH procedure in one RO in the second initial UL BWP.
  • the method further comprises: radio frequency (RF) retuning to the first initial UL BWP after transmitting the first message.
  • RF radio frequency
  • the method further comprises: switching from an active UL BWP to the first initial UL BWP after transmitting the first message.
  • the method further comprises: switching from an active DL BWP to the first initial DL BWP when the first initial DL BWP is configured.
  • the method further comprises: in the case that the ROs are configured in the first initial UL BWP, transmitting a first message of a RACH procedure in one RO in the first initial UL BWP.
  • the method further comprises: receiving a downlink control information (DCI) for scheduling a second message of the RACH procedure, wherein the DCI is scrambled by a dedicated random access radio network temporary identifier (RA-RNTI) .
  • DCI downlink control information
  • RA-RNTI dedicated random access radio network temporary identifier
  • the DCI is received in the second DL BWP.
  • the dedicated RA-RNTI is determined by an index of the initial UL BWP.
  • the method further comprises: receiving a second message of the RACH procedure, wherein the index of the initial UL BWP of the first UE is different from an index of the initial UL of a second UE.
  • the method further comprises: receiving downlink control information (DCI) for scheduling a second message of the RACH procedure in a dedicated random access (RA) search space for the first UE.
  • DCI downlink control information
  • RA dedicated random access
  • the method further comprises: receiving a second message of the RACH procedure in a first initial DL BWP for the first UE.
  • the method further comprises: in the case that neither the first initial UL BWP nor the first initial DL BWP is configured, receiving a physical uplink control channel (PUCCH) resource configuration indicating a starting PRB and a bandwidth size associated with PUCCH hopping, wherein the starting PRB is within the bandwidth of the first UE and the bandwidth size is equal to or smaller than a bandwidth size of the first UE.
  • PUCCH physical uplink control channel
  • Another embodiment of the present disclosure provides method performed by a base station (BS) , comprising: transmitting a configuration indicating a first initial uplink (UL) bandwidth part (BWP) and/or a second initial UL BWP for a first user equipment (UE) , wherein random access channel (RACH) occasions (ROs) are configured in in the first initial UL BWP and/or in the second initial UL BWP; and performing a RACH procedure initiated by a UE based on a received first message in a RO.
  • BS base station
  • the method further comprises transmitting a configuration indicating a first initial downlink (DL) initial BWP and/or a second initial DL BWP for the first UE.
  • DL downlink
  • the method further comprises: in the case that the ROs are configured in the second initial UL BWP and no RO is configured in the first initial UL BWP for the first UE, receiving a first message of the RACH procedure from the first UE in a RO.
  • the method further comprises: in the case that the ROs are configured in the first initial UL BWP, receiving a first message of the RACH procedure from the first UE in a RO.
  • the method further comprises: transmitting a second message of the RACH procedure of the first UE, wherein the index of the initial UL BWP of the first UE is different from an index of the initial UL BWP of a second UE.
  • the method further comprises: transmitting a downlink control information (DCI) for scheduling a second message of the RACH procedure, wherein the DCI is scrambled by a dedicated random access radio network temporary identifier (RA-RNTI) .
  • DCI downlink control information
  • RA-RNTI dedicated random access radio network temporary identifier
  • the method wherein the dedicated RA-RNTI is determined by an index of the initial UL BWP.
  • the method further comprises: transmitting downlink control information (DCI) for scheduling a second message of the RACH procedure in a dedicated random access (RA) search space for the first UE.
  • DCI downlink control information
  • the method further comprises: transmitting a second message of the RACH procedure in a first initial DL BWP for the first UE.
  • the method further comprises: in the case that neither the first initial UL BWP nor the first initial DL BWP is configured, transmitting a dedicated physical uplink control channel (PUCCH) resource configuration to UE indicating a starting PRB and a bandwidth size associated with PUCCH hopping, wherein the starting PRB is within the bandwidth of the first UE and the bandwidth size is equal to or smaller than a bandwidth size of the first UE.
  • PUCCH physical uplink control channel
  • Yet another embodiment of the present disclosure provides an apparatus, comprising: a non-transitory computer-readable medium having stored thereon computer-executable instructions; a receiving circuitry; a transmitting circuitry; and a processor coupled to the non-transitory computer-readable medium, the receiving circuitry and the transmitting circuitry, wherein the computer-executable instructions cause the processor to implement the method performed by a first user equipment (UE) , comprising: determining whether a first initial uplink (UL) bandwidth part (BWP) for the first UE is configured in a system information block; determining whether random access channel (RACH) occasions (ROs) are configured in the first initial UL BWP; and starting a RACH procedure in the first initial UL BWP or in a second UL initial BWP based on the RO configuration.
  • UE user equipment
  • RACH random access channel
  • Fig. 1 illustrates a schematic diagram of a wireless communication system according to some embodiments of the present disclosure.
  • Fig. 2 illustrates a flow chart for the UE obtaining the configurations of initial BWPs according to some embodiments of the present disclosure.
  • Fig. 3 illustrates a random access channel (RACH) procedure according to some embodiments of the present disclosure.
  • Fig. 4 illustrates a configuration of dedicated IBWPs in a set of slots according to some embodiments to the present disclosure.
  • Figs. 5A and 5B illustrate some configurations of dedicated IBWPs in a set of slots according to some embodiments to the present disclosure.
  • Fig. 6 illustrates a PUCCH configuration according to some embodiments to the present disclosure
  • Fig. 7 illustrates a method for wireless communication according to a preferred embodiment of the present disclosure.
  • Fig. 8 illustrates a block diagram of an apparatus according to the embodiments of the present disclosure.
  • Fig. 1 illustrates an exemplary wireless communication system according to some embodiments of the present disclosure.
  • the wireless communication system includes a base station, i.e., BS 102 and some UEs, i.e., UE 101-A and UE 101-B.
  • UE 101-A and UE 101-B are within the coverage of BS 102.
  • UE 101-A may be the first type of UE, e.g., a RedCap UE
  • UE 101-B may be the second type of UE, e.g., a legacy eMBB or URLLC UE.
  • a wireless communication system may include more or fewer BSs, and more or fewer UEs.
  • names of UEs as illustrated and shown in Fig. 1 may be different, e.g., UE 101c, UE 104f, and UE 108g or the like.
  • the RedCap UE i.e. UE 101-A, as shown in Fig. 1 is illustrated in the shape of a camera, it is contemplated that a communication system may include any type of RedCap UE in accordance with some other embodiments of the present disclosure.
  • the UE 101-A may include industrial wireless sensors, video surveillances, computing devices, such as desktop computers, laptop computers, personal digital assistants (PDAs) , tablet computers, smart televisions (e.g., televisions connected to the Internet) , set-top boxes, game consoles, security systems (including security cameras) , vehicle on-board computers, network devices (e.g., routers, switches, and modems) , or the like.
  • the UE 101-A may include a portable wireless communication device, a smart phone, a cellular telephone, a flip phone, a device having a subscriber identity module, a personal computer, a selective call receiver, or any other device that is capable of sending and receiving communication signals on a wireless network.
  • the UE 101-A include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like.
  • the UE 101-A may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or described using other terminology used in the art.
  • the UE 101-A may communicate directly with the BSs 102 via uplink (UL) communication signals.
  • UL uplink
  • Both UE 101-A and UE 101-B in the embodiments of Fig. 1 may transmit information to BS 102 and receive control information from BS 102, for example, via NR Uu interface.
  • BS 102 may define one or more cells, and each cell may have a coverage area. As shown in Fig. 1, both UE 101-A and UE 101-B are within the coverage of BS 102.
  • BS 102 as illustrated and shown in Fig. 1 is not a specific base station, but may be any base station (s) in the communication system.
  • UE 101-A being within a coverage area of any one the two BSs 102 may be considered that UE 101-A is within a coverage of BS 102 in the communication system; and only UE 101-A being outside of coverage area (s) of both BSs 102 can be called as a case that UE 101-A is outside of the coverage of BS 102 in the communication system.
  • the BSs 102 may be distributed over a geographic region.
  • each of the BSs 102 may also be referred to as an access point, an access terminal, a base, a macro cell, a Node-B, an enhanced Node B (eNB) , a gNB, a Home Node-B, a relay node, or a device, or described using other terminology used in the art.
  • the BSs 102 are generally part of a radio access network that may include one or more controllers communicably coupled to one or more corresponding BSs 102.
  • the wireless communication system is compatible with any type of network that is capable of sending and receiving wireless communication signals.
  • the wireless communication system is compatible with a wireless communication network, a cellular telephone network, a time division multiple access (TDMA) -based network, a code division multiple access (CDMA) -based network, an orthogonal frequency division multiple access (OFDMA) -based network, an LTE network, a 3rd generation partnership project (3GPP) -based network, a 3GPP 5G network, a satellite communications network, a high altitude platform network, and/or other communications networks.
  • TDMA time division multiple access
  • CDMA code division multiple access
  • OFDMA orthogonal frequency division multiple access
  • the wireless communication system is compatible with the 5G new radio (NR) of the 3GPP protocol, wherein the BS 102 may transmit data using an orthogonal frequency division multiplexing (OFDM) modulation scheme on the DL and the UEs transmit data on the UL using a single-carrier frequency division multiple access (SC-FDMA) or OFDM scheme. More generally, however, the wireless communication system may implement some other open or proprietary communication protocols, for example, WiMAX, among other protocols.
  • NR 5G new radio
  • NR 5G new radio
  • OFDM orthogonal frequency division multiplexing
  • SC-FDMA single-carrier frequency division multiple access
  • WiMAX Worldwide Interoperability for Microwave Access
  • the BS 102 may communicate using other communication protocols, such as the IEEE 802.11 family of wireless communication protocols. Further, in some embodiments, the BS 102 may communicate over licensed spectrums, whereas in other embodiments the BS 102 may communicate over unlicensed spectrums. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol. In another embodiment, the BS 102 may communicate with the UEs using the 3GPP 5G protocols.
  • initial BWP are defined, which includes initial DL BWP and initial UL BWP.
  • the initial BWPs are used for transmission of common channels such as system information blocks (SIBs) , random access signals, for example, Msg1, Msg2, Msg3, Msg4, and paging signals, etc.
  • SIBs system information blocks
  • the initial BWPs are also used for transmission of UE specific data signal based on the configuration of the BS.
  • the BS may configure common part of initial BWPs (IBWPs) , which includes the following: the position of IBWP in frequency domain, the numerology, the configurations of cell specific physical channels of PDCCH, PDSCH, PUCCH, or PUSCH, etc., which are necessary for data transmission for UEs in initial access procedure.
  • IBWPs initial BWPs
  • the BS may optionally configure dedicated part of initial BWPs for efficient UE specific data transmission in the initial BWP.
  • Fig. 2 illustrates a flow chart for the UE obtaining the configurations of initial BWPs according to some embodiments of the present disclosure.
  • the UE For a UE that is powered on to access the network, or a UE in RRC_IDLE mode or RRC_INACTIVE mode, which is going to switch to the RRC_CONNECTED mode, in step 201, the UE firstly detects the synchronization signal block (SSB) including synchronization signal and the master information block (MIB) , then obtains control resource set zero (CORESET#0) configuration from MIB.
  • the CORESET#0 defines physical resources for the UE to receive physical downlink control channel.
  • One embodiment is that UE is not allowed to access the cell if it is undergoing a poor channel condition, e.g., the measured signal to noise and interference ratio (SINR) or the reference signal received power (RSRP) is below a predefined threshold. If the UE is allowed to access the network, then go to the next step.
  • a poor channel condition e.g., the measured signal to noise and interference ratio (SINR) or the reference signal received power (RSRP) is below a predefined threshold.
  • the UE obtains the initial DL BWP, which is by default defined by the span of CORESET#0.
  • the UE could detect PDCCH in CORESET#0, and obtain the scheduling information for the receiving the system information block (for example, SIB1) .
  • SIB1 system information block
  • UE is not allowed to access the cell if it is undergoing a poor channel condition, e.g., the measured signal to noise and interference ratio (SINR) or the reference signal received power (RSRP) is below a predefined threshold. If the UE is allowed to access the network, then go to the next step.
  • SIB1 system information block
  • the UE detects the SIB1 based on the scheduling information.
  • the UE may obtain the updated configurations of initial DL BWP and the configuration of initial UL BWP.
  • the UE For a UE in RRC_CONNECTED mode camping on an active BWP other than initial BWP, if the UE needs to initiate a random access procedure while the RACH occasions (ROs) are not configured in the active UL BWP, the UE shall switch the active UL BWP to initial UL BWP for performing RACH procedure, since ROs are always configured in the initial UL BWP. Correspondingly, the UE also switches the active DL BWP to the initial DL BWP.
  • ROs RACH occasions
  • Fig. 3 illustrates a random access channel (RACH) procedure according to some embodiments of the present disclosure.
  • the UE In order to access to a cell, the UE need to initiate a random-access (RA) procedure.
  • RA random-access
  • the UE In a four step RACH procedure as depicted in Fig. 3, in step 301, the UE transmits a Msg1 including a Physical Random Access Channel (PRACH) preamble to the network.
  • PRACH Physical Random Access Channel
  • the BS transmits Msg2 including a Random-Access Response (RAR) to the UE, indicating reception of the PRACH preamble and providing a time-alignment (TA) command adjusting the transmission timing of the UE.
  • RAR Random-Access Response
  • TA time-alignment
  • the RAR is scheduled by downlink control information (DCI) in RA search space of CORESET#0, which is scrambled by a Random Access Radio Network Temporary Identifier (RA-RNTI) .
  • DCI downlink control information
  • RA-RNTI Random Access Radio Network Temporary Identifier
  • the RA-RNTI is determined implicitly based on the index of the RACH occasion that Msg1 is transmitted.
  • step 303 the UE transmits Msg 3 to the BS, and in step 304, the BS transmits Msg4 to the UE, the UE and network exchange of messages (uplink Msg3 and subsequent downlink Msg4) with the aim of resolving potential collisions due to simultaneous transmissions of the same preamble from multiple devices within the cell.
  • the UE is in RRC_CONNECTED mode and network-device communication can continue using normal dedicated transmission.
  • the RedCap UEs may access a NR cell in the configured legacy initial BWPs, and could follow the same RACH procedure with the legacy UEs.
  • the RedCap UE might have reduced UE bandwidth than the legacy UE, and dedicated initial BWPs might be introduced for RedCap UEs.
  • dedicated IBWP could be configured to avoid the following issues:
  • legacy UL IBWP is wider than the BW for the RedCap UE
  • PUCCH for Msg4 might fall outside of the BW of the RedCap UE, in this case, the RedCap UE needs a time gap to perform frequency retuning to transmit the 2 nd hop PUCCH.
  • the 2 nd hop PUCCH has to be truncated which might lead to poor PUCCH detection performance at BS side.
  • Msg3 PUSCH might fall outside of the BW of the RedCap UE. Similar with PUCCH for Msg4, Msg3 performance might be impacted.
  • Dedicated IBWP may also be configured to offload the traffic for RedCap UEs, such as the paging, to reduce the impact to legacy UEs.
  • initial BWPs for RedCap UEs may be optionally and adaptatively configured based on needs. If initial BWPs are explicitly configured, the configurations shall be in the system information block (SIB) , for example, SIB1. Consequently, after detecting SIB1, the RedCap UE could have the configurations of both legacy initial BWPs and dedicated initial BWPs. Furthermore, the BS might configure only dedicated DL IBWP, or only dedicated UL IBWP, or both IBWPs for RedCap UEs based on specific needs.
  • SIB system information block
  • ROs are configured in the dedicated IBWP, there might be RAR collision issue between legacy UEs and RedCap UEs, since there will be the same RO index for the ROs configured for legacy UEs and for RedCap UEs.
  • the PUCCH hopping of RedCap UE may hop outside of BW of the RedCap UE.
  • the present disclosure proposes several solutions for solving the above issues by providing methods and apparatus for BWP configuration.
  • the BS may configure dedicated IBWP for the RedCap UE, which includes i) : the dedicated uplink IBWP, ii) : the dedicated downlink IBWP, and iii) the dedicated uplink IBWP and the dedicated downlink IBWP, based on practical requirements. Furthermore, the BS may configure dedicated ROs for the RedCap UE in the dedicated uplink IBWP.
  • dedicated UL IBWP refers to dedicated UL IBWP for RedCap UE
  • dedicated DL IBWP refers to dedicated DL IBWP for RedCap UE
  • dedicated RO refers to dedicated RO for RedCap UE.
  • the RedCap UE first determines if there is a dedicated UL IBWP based on the configuration in the system information block (i.e. SIB1) , then determines if there is dedicated ROs in the dedicated UL IBWP based on a configuration. The RedCap UE then performs random access procedure based on such determinations.
  • SIB1 system information block
  • dedicated UL IBWP is configured, and no dedicated ROs is configurated in the dedicated UL IBWP.
  • the RedCap UE is about to initiate a RACH procedure.
  • RedCap UE For a RedCap UE in RRC_IDLE mode or in RRC_INACTIVE mode the RedCap UE may transmit Msg1 of the RACH procedure in a legacy RO in a legacy IBWP, and then retune or switch to RedCap dedicated IBWP to continue the RACH procedure.
  • the RedCap UE shall firstly perform frequency retuning to a legacy RO in the legacy IBWP, then the RedCap UE transmits Msg1 of the RACH procedure in the legacy RO in the legacy IBWP. After that, the RedCap UE performs BWP switching, and switches from the active BWP to the dedicated UL IBWP to continue the RACH procedure and the following data transmission.
  • the RedCap UE shall switch to the dedicated DL IBWP as well; otherwise, the UE remains camping on the legacy DL IBWP.
  • Fig. 4 illustrates a configuration of dedicated IBWP in a set of slots according to some embodiments to the present disclosure.
  • a frame structure is illustrated, where there are 8 slots (i.e. slot#0, slot#1, slot#2, slot#3, slot#4, slot#5, slot#6, and slot#7) , which are configured as "D, S, U, D, D, D, S, U” , wherein “D” suggests that the slot is for downlink data transmission, "U” suggests that the slot is for uplink data transmission, "S” suggests that the slot is a special slot.
  • slot#0, slot#1, slot#2, slot#3, slot#4, slot#5, slot#6, and slot#7 which are configured as "D, S, U, D, D, D, D, S, U” , wherein "D” suggests that the slot is for downlink data transmission, "U” suggests that the slot is for uplink data transmission, "S” suggests that the slot is a special slot.
  • Such frame structure is just an example for describing the solution, and the solution does not depend on which frame structure is utilized.
  • the solutions of the present disclosure also apply to other frame structures in addition to the frame
  • slot#0, slot#1, slot#3, slot#4, slot#6, and slot#7) are PDCCH monitoring occasions for RA search space.
  • the UEs i.e. both the RedCap UEs and the legacy UEs monitor PDCCH.
  • the RedCap UEs are configured with dedicated IBWPs, including dedicated UL IBWP and dedicated DL IBWP. No RO is configured in the dedicated UL IBWP.
  • the RedCap UEs upon initiating a RACH procedure, the RedCap UEs will send Msg1 of the RACH procedure in a RO in the legacy UL IBWP, as shown in Fig. 4, the RedCap UE transmits Msg1 in RO#0 in the legacy UL IBWP, and then retune or switch to the dedicated UL IBWP to continue the RACH procedure.
  • dedicated UL IBWP is configured, and dedicated ROs are also configured in the dedicated UL IBWP.
  • the RedCap UE is about to perform a RACH procedure to access to the network.
  • the RedCap UEs transmit the Msg1 in the dedicated ROs in the dedicated UL IBWP.
  • the dedicated downlink initial BWP is also configured for the RedCap UE, in this case, the Msg2 for the RedCap UE are scheduled and transmitted in dedicated DL IBWPs.
  • Solution 1 the present disclosure proposes that the RA_RNTI for RAR for the RedCap UEs is determined partly by the UL IBWP index.
  • the RA search space configured for legacy UEs could be shared by the RedCap UEs.
  • the RAR is scheduled by the DCI in RA search space, which is scrambled by a RA-RNTI. Therefore, with different RA-RNTIs for RedCap UEs and for legacy UEs, the RARs are different for RedCap UEs and for legacy UEs, thus RAR collision is avoided.
  • RedCap dedicated IBWP is indexed always with 0, while RedCap dedicated IBWP is indexed with 1.
  • the legacy IBWP is indexed always with 0, while each dedicated IBWP is configured with a specific index.
  • the RA_RNTI may be calculated as follows:
  • the RA-RNTI associated with the PRACH occasion in which the random access preamble is transmitted is computed as:
  • RA-RNTI 1 + s id + 14 ⁇ t id + 14 ⁇ 80 ⁇ f id + 14 ⁇ 80 ⁇ 8 ⁇ ul_carrier id
  • s id is the index of the first OFDM symbol of the PRACH occasion (0 ⁇ s id ⁇ 14) ,
  • t id is the index of the first slot of the PRACH occasion in a system frame (0 ⁇ t id ⁇ 80) ,
  • f id is the index of the PRACH occasion in the frequency domain (0 ⁇ f id ⁇ 8)
  • ul_carrier id is the UL carrier used for random access preamble transmission (0 for normal carrier, and 1 for supplemental UL carrier) .
  • the RA-RNTI is determined as follows:
  • RA-RNTI 1 + s id + 14 ⁇ t id + 14 ⁇ 80 ⁇ fs id + 14 ⁇ 80 ⁇ 8 ⁇ Initial_BWP id
  • ul_carrier id is not needed for RedCap UE, since RedCap UE does not support supplemental UL carrier.
  • the RA-RNTI for the legacy UEs and for the RedCap UEs are different, therefore, even sharing the RA search space configured for legacy UEs, the RAR for RedCap UE and the RAR for legacy UE can be distinguished based on the RA-RNTI.
  • Solution 2 a separate RA search space is configured for the RedCap UEs, so that the PDCCH monitoring occasions for RedCap UEs and for legacy UEs is non-overlapped.
  • the PDCCH for Msg2 RAR for RedCap UEs and for legacy UEs are transmitted in different PDCCH monitoring occasions.
  • the RA-RNTI might be same for legacy UEs and for RedCap UEs.
  • the RedCap UE receives Msg2 in DL IBWP for RedCap UE
  • the legacy UE receives Msg2 in DL IBWP for legacy UE.
  • Other configurations of RA search space might also be different, e.g., the aggregation level or candidates, etc.
  • Figs. 5A and 5B illustrate some configurations of dedicated IBWP in a set of slots according to some embodiments to the present disclosure. These configurations are for solving the RAR collision issue.
  • a frame structure is illustrated, where there are 8 slots (i.e. slot#0, slot#1, slot#2, slot#3, slot#4, slot#5, slot#6, and slot#7) , which are configured as "D, S, U, D, D, D, S, U” , wherein “D” suggests that the slot is for downlink data transmission, "U” suggests that the slot is for uplink data transmission, "S” suggests that the slot is a special slot.
  • slots i.e. slot#0, slot#1, slot#2, slot#3, slot#4, slot#5, slot#6, and slot#7
  • slots i.e. slot#0, slot#1, slot#2, slot#3, slot#4, slot#5, slot#6, and slot#7
  • slots i.e. slot#0, slot#1, slot#2, slot#3, slot#4, slot#5, slot#6, and slot#7
  • slot#7 8 slots
  • the slots marked with forward slash are PDCCH monitoring occasions for RA search space for the legacy UEs
  • the slots marked with backslash are PDCCH monitoring occasions for RA search space for the RedCap UEs.
  • the RedCap UEs are configured with dedicated initial UL BWP, but share the same initial DL BWP with the legacy UEs.
  • ROs are configured in the dedicated IBWP, and the indices of the ROs are the same with those in the legacy IBWP in the same UL slot.
  • the RA-RNTI would be the same for the ROs with same RO index but in the different IBWP.
  • RAR collision issue happens since the RAR is identified by the preamble index only.
  • the RedCap UE may use RO#0 in the dedicated initial uplink IBWP
  • the legacy UE may use RO#0 in the initial uplink IBWP, both RO indices are 0, and the RAR collision happens according to the legacy principle.
  • the UL IBWP for the legacy UE is indexed with 0, while RedCap dedicated IBWP is indexed with 1.
  • the RA-RNTI for the RedCap UE and that for legacy UE are different, and RAR collision is avoided according to the configuration of dedicated IBWP in Fig. 5A.
  • Fig. 5B separate RA search spaces for RedCap UEs and for legacy UEs are introduced.
  • the slots marked with forward slash i.e. slot#0, slot#3, slot#4, and slot#6
  • the slots marked with backslash i.e. slot#1 and slot#4
  • the PDCCH monitoring occasions for legacy UEs and for RedCap UEs are configured to be non-overlapped, so that the RAR for legacy UEs and RedCap UEs are scheduled in different PDCCH monitoring occasions. There is no RAR collision issue even when a legacy UE and a RedCap UEs uses the same RA-RNTI.
  • the RedCap UE when transmitting PUCCH, the RedCap UE utilizes the legacy IBWP. Since the PUCCH is transmitted with the frequency hopping, and the RedCap UE is camping on a legacy UL IBWP which is wider than a bandwidth of the RedCap UE, the PUCCH of the RedCap UE may hop outside of the frequency bandwidth of the bandwidth of the RedCap UE.
  • the present disclosure proposes to introduce a separate PUCCH resource configuration for RedCap UEs.
  • the RedCap UE only hops within the bandwidth which is supported by the RedCap UE.
  • Table 1 shows an exemplary PUCCH resource configuration:
  • the first column indicates the row index
  • the second column indicates the PUCCH format
  • the third column indicates the location of the first symbol of the PUCCH in a slot
  • the fourth column indicates the number of the symbols of the PUCCH
  • the fifth column indicates the PRB offset of the PUCCH
  • the sixth column indicates set of initial cyclic shift CS indexes.
  • the row index is "0"
  • the PUCCH format is PUCCH format 0
  • the first symbol of the PUCCH is the 12th symbol in a slot
  • the total length of the PUCCH is 2 symbols.
  • the PRB offset indicates an offset relative to a starting PRB that is configured for PUCCH for RedCap UEs.
  • the PUCCH HARQ ACK in PUCCH format 0 and PUCCH format 1 (as in the table) is sequence-based transmission, where the sequence is determined based on an initial cyclic shift, i.e. ⁇ 0, 3 ⁇ .
  • the present disclosure proposes to define a hopping bandwidth in the UL IBWP.
  • the hopping bandwidth is configured by the base station, or determined based on the bandwidth of the RedCap UE. After receiving the configuration of starting location (for example, the starting PRB) , and the size of the hopping bandwidth, the hopping bandwidth is determined.
  • the RedCap UE is configured to perform the PUCCH hopping within in the hoping BW, which is equal to or smaller than the BW of the RedCap UE.
  • a dedicated PUCCH configuration for the RedCap UEs during initial access may be configured, for example, it may be included in: pucch-ConfigCommon.
  • the BS may configure a different PUCCH format, or any other PUCCH configurations for RedCap UEs than for legacy UEs.
  • Fig. 6 illustrates a PUCCH configuration according to some embodiments to the present disclosure
  • BW 1 represents a bandwidth of a legacy UL IBWP
  • BW 2 represents a bandwidth of a dedicated UL IBWP
  • BW 3 represents the a bandwidth of the hopping bandwidth.
  • the block marked with back slash represents a block for a legacy PUCCH
  • the block marked with forward slash represents a block for a RedCap PUCCH.
  • a legacy PUCCH is the 3 rd PRB in BW 1 , and after the PUCCH hopping, the PUCCH hops to the (BW 1 -3) th PRB. As can be seen, the 3 rd PRB is outside the bandwidth of the RedCap UE.
  • the PUCCH hopping for RedCap UE is limited within the hopping bandwidth, BW 3 , which is equal to or smaller than the size of the RedCap UE, BW 2 .
  • the RedCap PUCCH is the 1 st PRB in the hopping bandwidth, BW 3
  • the PUCCH is the (BW 3 -1) th PRB. In this way, the RedCap UE transmits the PUCCH with the PUCCH hopping within the bandwidth of the RedCap UE BW 2 .
  • Fig. 7 illustrates a method of a preferred embodiment of the subject disclosure.
  • the BS transmits a first initial UL BWP and/or a second initial UL BWP for the first UE, wherein RACH occasions (ROs) are configured in the first initial UL BWP or in the second initial UL BWP.
  • the first UE may be the RedCap UE
  • the first initial UL BWP may be the dedicated initial UL BWP, which is configured for the RedCap UE
  • the second initial UL BWP may be the legacy initial UL BWP, which may be utilized by both the RedCap UE and the legacy UE.
  • the dedicated initial BWP may include a dedicated initial DL BWP, a dedicated initial UL BWP, or both of the dedicated initial DL BWP and the dedicated initial UL BWP.
  • the UE receives the configuration, and determines whether at least the first initial UL BWP for the first UE is configured in system information block; in step 703, the UE determines if random access channel (RACH) occasions (ROs) are configured in the first BWP, then in step 704, the UE starts a RACH procedure based on the determined RO, and the BS correspondingly performs the RACH procedure, so that the UE can access to the network.
  • RACH random access channel
  • the BS may further transmit a configuration indicating a first initial DL BWP and/or a second initial DL BWP for the RedCap UE, in other words, whether a dedicated initial DL BWP is configured for the RedCap UE, or a legacy initial DL BWP.
  • the RedCap UE determines whether the dedicated initial DL BWP is configured.
  • the initial UL BWP is the dedicated initial UL BWP if configured, and the initial UL BWP is the legacy initial UL BWP if the dedicated initial UL BWP is not configured; and the initial DL BWP is the dedicated initial DL BWP if configured, and the initial DL BWP is a legacy initial DL BWP if the dedicated initial UL BWP is not configured.
  • the ROs are configured in the legacy BWP and no RO is configured in the dedicated initial UL BWP, the UE transmits Msg1 of the RACH procedure in the RO for legacy UE.
  • the UE radio frequency (RF) retunes to the dedicated initial UL BWP to continue the RACH procedure after transmitting the first message.
  • the RedCap UE transmits Msg1 in RO#0 in legacy IBWP, and retune to the UL IBWP of RedCap UE.
  • the RedCap UE For the RedCap UE in the RRC_CONNECTED mode, it switches from an active BWP to the dedicated initial UL BWP after transmitting Msg1. Furthermore, if the dedicated initial DL BWP is also configured, the RedCap UE switches to the dedicated initial DL BWP.
  • the ROs are in the dedicated initial UL BWP
  • the UE transmits Msg 1 of the RACH procedure in the RO in the dedicated initial UL BWP.
  • the RedCap UE may receive DCI for scheduling Msg2, which is associated with an index of the initial UL BWP of the RedCap UE, and the DCI is scrambled by a dedicated RA-RNTI.
  • the dedicated RA-RNTI is determined by an index of the initial UL BWP.
  • the UE receives Msg2, which is associated with an index of the initial UL of BWP the first UE, the index of the initial UL BWP of the first UE is different from an index of the initial UL of a second UE.
  • the initial UL BWP of the RedCap UE is 1, and the initial UL BWP of the legacy UE is 0.
  • the UE may receive DCI for scheduling a second message of the RACH procedure in a dedicated RA search space for the first UE.
  • slot#1 and slot#4 are configured as the dedicated RA search space for the RedCap UE.
  • the RedCap UE may receive Msg2 in dedicated initial DL BWP for the first UE. For example, in Fig. 4, in slot#5, the RedCap UE receives Msg2 in DL IBWP for RedCap UE, and the legacy UE receives Msg2 in DL IBWP for legacy UE. In this way, the RAR collision would not happen.
  • the UE may receive a PUCCH resource configuration indicating a starting PRB and a bandwidth size associated with PUCCH hopping, wherein the starting PRB is within the bandwidth of the first UE and the bandwidth size is equal to or smaller than a bandwidth size of the first UE.
  • the RedCap UE transmits the PUCCH within the hopping bandwidth BW 3 .
  • Fig. 8 illustrates an exemplary block diagram of an apparatus according to an embodiment of the present disclosure.
  • the apparatus may include receiving circuitry, a processor, and transmitting circuitry.
  • the UE may include a non-transitory computer-readable medium having stored thereon computer-executable instructions; receiving circuitry; transmitting circuitry; and a processor coupled to the non-transitory computer-readable medium, the receiving circuitry and the transmitting circuitry.
  • the computer executable instructions can be programmed to implement a method (e.g., the method in Fig. 4) with the receiving circuitry, the transmitting circuitry and the processor.
  • controllers, flowcharts, and modules may also be implemented on a general purpose or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, an integrated circuit, a hardware electronic or logic circuit such as a discrete element circuit, a programmable logic device, or the like.
  • any device that has a finite state machine capable of implementing the flowcharts shown in the figures may be used to implement the processing functions of the present disclosure.

Landscapes

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

Abstract

La présente divulgation concerne un procédé et un appareil de configuration d'une partie de bande passante. Un mode de réalisation de la présente divulgation concerne un procédé exécuté par un premier équipement utilisateur (UE). Le procédé comprend les étapes consistant à : déterminer si au moins une partie de bande passante (BWP) dédiée initiale associée au premier UE est configurée dans un bloc d'informations de système ; déterminer une occasion d'un canal d'accès aléatoire (RACH) (RO) dans une BWP existante ou dans la BWP dédiée ; et exécuter une procédure de RACH sur la base de la RO déterminée.
PCT/CN2021/085628 2021-04-06 2021-04-06 Procédé et appareil de configuration d'une partie de bande passante WO2022213257A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/085628 WO2022213257A1 (fr) 2021-04-06 2021-04-06 Procédé et appareil de configuration d'une partie de bande passante

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/085628 WO2022213257A1 (fr) 2021-04-06 2021-04-06 Procédé et appareil de configuration d'une partie de bande passante

Publications (1)

Publication Number Publication Date
WO2022213257A1 true WO2022213257A1 (fr) 2022-10-13

Family

ID=83545893

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/085628 WO2022213257A1 (fr) 2021-04-06 2021-04-06 Procédé et appareil de configuration d'une partie de bande passante

Country Status (1)

Country Link
WO (1) WO2022213257A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020031588A1 (fr) * 2018-08-07 2020-02-13 シャープ株式会社 Dispositif de station de base, dispositif terminal, procédé de communication et circuit intégré
WO2020067951A1 (fr) * 2018-09-27 2020-04-02 Telefonaktiebolaget Lm Ericsson (Publ) Équipement utilisateur permettant d'obtenir une partie de bande passante pour un accès aléatoire, noeud de réseau et procédés correspondants dans un réseau de communication sans fil
US20210058971A1 (en) * 2019-08-19 2021-02-25 Samsung Electronics Co., Ltd. Repetition of prach preamble transmission for ues
US20210076384A1 (en) * 2019-09-11 2021-03-11 Samsung Electronics Co., Ltd. Random access response and contention resolution

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020031588A1 (fr) * 2018-08-07 2020-02-13 シャープ株式会社 Dispositif de station de base, dispositif terminal, procédé de communication et circuit intégré
WO2020067951A1 (fr) * 2018-09-27 2020-04-02 Telefonaktiebolaget Lm Ericsson (Publ) Équipement utilisateur permettant d'obtenir une partie de bande passante pour un accès aléatoire, noeud de réseau et procédés correspondants dans un réseau de communication sans fil
US20210058971A1 (en) * 2019-08-19 2021-02-25 Samsung Electronics Co., Ltd. Repetition of prach preamble transmission for ues
US20210076384A1 (en) * 2019-09-11 2021-03-11 Samsung Electronics Co., Ltd. Random access response and contention resolution

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL: "Cell access for REDCAP UE with reduced bandwidth", 3GPP DRAFT; R2-2009800, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic; 20201102 - 20201113, 22 October 2020 (2020-10-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051941432 *

Similar Documents

Publication Publication Date Title
EP3661310B1 (fr) Procédé et appareil d'envoi de préambule d'accès aléatoire, et procédé et appareil de réception de préambule d'accès aléatoire
KR102150681B1 (ko) 비면허 대역에서의 랜덤 액세스 과정을 수행하는 방법 및 기기
RU2663220C1 (ru) Беспроводное устройство, первый сетевой узел и способы в них
EP3163967A1 (fr) Procédé et dispositif pour émettre des données dans une bande sans licence
US20220007426A1 (en) Random access method and device
US10637600B2 (en) Method for uplink transmission in unlicensed band, and device using same
KR20150024333A (ko) 무선 통신 시스템에서 d2d(device-to-device) 통신을 위한 신호 송수신 방법 및 장치
US12004141B2 (en) Communication method, access network device, and terminal
JP7496834B2 (ja) ２ステップのランダムアクセスのための方法、端末デバイス及びネットワークデバイス
EP3751943B1 (fr) Procédé et appareil d'émission d'un préambule d'accès aléatoire dans une bande sans licence
CN114208300A (zh) 两步随机接入中接收和发送随机接入响应的方法及装置
US10848217B2 (en) Network node and a wireless communication device for random access in beam-based systems
EP4221423A1 (fr) Procédés et terminaux d'accès aléatoire
CN112997574B (zh) 随机接入的方法、终端设备和网络设备
US10660142B2 (en) Device and method of handling a radio resource control connection
CN113678560A (zh) 随机接入过程中传输信息的方法、终端设备和网络设备
WO2022213257A1 (fr) Procédé et appareil de configuration d'une partie de bande passante
CN117044154A (zh) 用于降低带宽ue的pucch配置
WO2023201624A1 (fr) Procédé et appareil d'indication de structure d'occupation de canal sur un spectre sans licence
WO2023201464A1 (fr) Procédés et appareils de sélection de ressources pour transmission de liaison latérale
CN112771967B (zh) 一种传输参数确定方法及装置、用户设备
US20240098720A1 (en) Terminal, System, and Method for Bandwidth Part Out-of-Sync Detection and Recovery
WO2024073985A9 (fr) Procédés et appareils de réduction de latence de transmission prach
US20220287101A1 (en) Method and apparatus for data transmission

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 14/02/2024)