WO2022151465A1 - Contrôle de procédure rach en cas de conflit d'état rrc - Google Patents

Contrôle de procédure rach en cas de conflit d'état rrc Download PDF

Info

Publication number
WO2022151465A1
WO2022151465A1 PCT/CN2021/072399 CN2021072399W WO2022151465A1 WO 2022151465 A1 WO2022151465 A1 WO 2022151465A1 CN 2021072399 W CN2021072399 W CN 2021072399W WO 2022151465 A1 WO2022151465 A1 WO 2022151465A1
Authority
WO
WIPO (PCT)
Prior art keywords
field
msg3
base station
mac
rach procedure
Prior art date
Application number
PCT/CN2021/072399
Other languages
English (en)
Inventor
Jinglin Zhang
Haojun WANG
Hao Zhang
Original Assignee
Qualcomm Incorporated
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 Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2021/072399 priority Critical patent/WO2022151465A1/fr
Publication of WO2022151465A1 publication Critical patent/WO2022151465A1/fr

Links

Images

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA

Definitions

  • the present disclosure generally relates to communication systems, and more particularly, to a method and/or apparatus to control a random access channel (RACH) procedure in a radio resource control (RRC) state mismatch situation.
  • RACH random access channel
  • RRC radio resource control
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
  • Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single-carrier frequency division multiple access
  • TD-SCDMA time division synchronous code division multiple access
  • 5G New Radio is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT) ) , and other requirements.
  • 3GPP Third Generation Partnership Project
  • 5G NR includes services associated with enhanced mobile broadband (eMBB) , massive machine type communications (mMTC) , and ultra-reliable low latency communications (URLLC) .
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communications
  • URLLC ultra-reliable low latency communications
  • Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard.
  • LTE Long Term Evolution
  • the apparatus may include a user equipment (UE) and/or a base station.
  • the UE may transmit, to a base station, a message 3 (Msg3) of a random access channel (RACH) procedure, the Msg3 being associated with a medium access control (MAC) control element (CE) (MAC-CE) , receive, from the base station, downlink control information (DCI) including at least one field, a first field of the at least one field indicating to stop the RACH procedure, and initiate, upon receiving the DCI including the at least one field, an end to the RACH procedure.
  • the Msg3 may include a cell radio network temporary identifier (RNTI) (C-RNTI) MAC-CE.
  • the UE may be a dedicated data subscription (DDS) subscriber (SUB) .
  • DDS dedicated data subscription
  • the UE may initiate, upon receiving the DCI including the at least one field, a radio link failure (RLF) , perform, upon initiating the RLF, an RRC reestablishment procedure, and transmit, in response to performing the RRC reestablishment procedure, an RRC reestablishment request to the base station.
  • RLF radio link failure
  • the UE may also initiate, upon initiating the end to the RACH procedure, an RRC release, and enter into an RRC idle state.
  • the DCI may be scrambled using a temporary cell (TC) radio network temporary identifier (RNTI) (TC-RNTI) .
  • TC temporary cell
  • RNTI radio network temporary identifier
  • the first field of the at least one field indicating to stop the RACH procedure may be a frequency domain resource assignment field.
  • the frequency domain resource assignment field may include one or more bits, where all of the one or more bits are set to a value of one (1) indicating to stop the RACH procedure.
  • the DCI including at least one field may be received via a physical downlink control channel (PDCCH) .
  • PDCCH physical downlink control channel
  • the UE may receive, from a base station, DCI including at least one field, a first field of the at least one field indicating to stop RACH procedure, determine whether the UE transmitted a Msg3 of a RACH procedure including a C-RNTI MAC-CE to the base station, and determine, upon determining that the UE did not transmit the Msg3 of the RACH procedure including the C-RNTI MAC-CE to the base station, to disregard the DCI including the at least one field.
  • the base station may receive a Msg3 of a RACH procedure, the Msg3 being associated with a MAC-CE, determine whether a UE is associated with the Msg3, and transmit, upon determining that no UE may be associated with the Msg3, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure.
  • the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
  • the following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.
  • FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.
  • FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.
  • FIG. 2B is a diagram illustrating an example of DL channels within a subframe, in accordance with various aspects of the present disclosure.
  • FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.
  • FIG. 2D is a diagram illustrating an example of UL channels within a subframe, in accordance with various aspects of the present disclosure.
  • FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network.
  • UE user equipment
  • FIG. 4 illustrates a call-flow chart of a method of wireless communication.
  • FIG. 5 illustrates a call-flow chart of a method of wireless communication.
  • FIG. 6 is a flowchart of a method of wireless communication.
  • FIG. 7 is a flowchart of a method of wireless communication.
  • FIG. 8 illustrates a call-flow chart of a method of wireless communication.
  • FIG. 9 is a flowchart of a method of wireless communication.
  • FIG. 10 is a diagram illustrating an example of a hardware implementation for an example apparatus.
  • FIG. 11 is a diagram illustrating an example of a hardware implementation for an example apparatus.
  • processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems on a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • processors in the processing system may execute software.
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer.
  • such computer-readable media can comprise a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
  • RAM random-access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable ROM
  • optical disk storage magnetic disk storage
  • magnetic disk storage other magnetic storage devices
  • combinations of the aforementioned types of computer-readable media or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
  • FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100.
  • the wireless communications system (also referred to as a wireless wide area network (WWAN) ) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G Core (5GC) ) .
  • the base stations 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station) .
  • the macrocells include base stations.
  • the small cells include femtocells, picocells, and microcells.
  • the base stations 102 configured for 4G LTE may interface with the EPC 160 through first backhaul links 132 (e.g., S1 interface) .
  • the base stations 102 configured for 5G NR may interface with core network 190 through second backhaul links 184.
  • the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity) , inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS) , subscriber and equipment trace, RAN information management (RIM) , paging, positioning, and delivery of warning messages.
  • NAS non-access stratum
  • RAN radio access network
  • MBMS multimedia broadcast multicast service
  • RIM RAN information management
  • the base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with each other over third backhaul links 134 (e.g., X2 interface) .
  • the first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless.
  • the base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102’ may have a coverage area 110’ that overlaps the coverage area 110 of one or more macro base stations 102.
  • a network that includes both small cell and macrocells may be known as a heterogeneous network.
  • a heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) .
  • eNBs Home Evolved Node Bs
  • HeNBs Home Evolved Node Bs
  • CSG closed subscriber group
  • the communication links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104.
  • the communication links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity.
  • the communication links may be through one or more carriers.
  • the base stations 102 /UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc.
  • the component carriers may include a primary component carrier and one or more secondary component carriers.
  • a primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .
  • D2D communication link 158 may use the DL/UL WWAN spectrum.
  • the D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) .
  • sidelink channels such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) .
  • sidelink channels such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) .
  • D2D communication may be through a variety of wireless D2D communications systems, such as for example, WiMedia, Bluetooth, ZigBe
  • the wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like.
  • AP Wi-Fi access point
  • STAs Wi-Fi stations
  • communication links 154 e.g., in a 5 GHz unlicensed frequency spectrum or the like.
  • the STAs 152 /AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
  • CCA clear channel assessment
  • the small cell 102’ may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102’ may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz, or the like) as used by the Wi-Fi AP 150. The small cell 102’, employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.
  • the small cell 102’ may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz, or the like) as used by the Wi-Fi AP 150.
  • the small cell 102’, employing NR in an unlicensed frequency spectrum may boost coverage to and/or increase capacity of the access network.
  • the electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc.
  • two initial operating bands have been identified as frequency range designations FR1 (410 MHz –7.125 GHz) and FR2 (24.25 GHz –52.6 GHz) .
  • the frequencies between FR1 and FR2 are often referred to as mid-band frequencies.
  • FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles.
  • FR2 which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz –300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
  • EHF extremely high frequency
  • ITU International Telecommunications Union
  • sub-6 GHz or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies.
  • millimeter wave or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.
  • a base station 102 may include and/or be referred to as an eNB, gNodeB (gNB) , or another type of base station.
  • Some base stations, such as gNB 180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave frequencies, and/or near millimeter wave frequencies in communication with the UE 104.
  • the gNB 180 may be referred to as a millimeter wave base station.
  • the millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for the path loss and short range.
  • the base station 180 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate the beamforming.
  • the base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 182’.
  • the UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 182” .
  • the UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions.
  • the base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions.
  • the base station 180 /UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 180 /UE 104.
  • the transmit and receive directions for the base station 180 may or may not be the same.
  • the transmit and receive directions for the UE 104 may or may not be the same.
  • the EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172.
  • MME Mobility Management Entity
  • MBMS Multimedia Broadcast Multicast Service
  • BM-SC Broadcast Multicast Service Center
  • PDN Packet Data Network
  • the MME 162 may be in communication with a Home Subscriber Server (HSS) 174.
  • HSS Home Subscriber Server
  • the MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160.
  • the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172.
  • IP Internet protocol
  • the PDN Gateway 172 provides UE IP address allocation as well as other functions.
  • the PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176.
  • the IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, and/or other IP services.
  • the BM-SC 170 may provide functions for MBMS user service provisioning and delivery.
  • the BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and may be used to schedule MBMS transmissions.
  • PLMN public land mobile network
  • the MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.
  • MMSFN Multicast Broadcast Single Frequency Network
  • the core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195.
  • the AMF 192 may be in communication with a Unified Data Management (UDM) 196.
  • the AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190.
  • the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195.
  • the UPF 195 provides UE IP address allocation as well as other functions.
  • the UPF 195 is connected to the IP Services 197.
  • the IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services.
  • IMS IP Multimedia Subsystem
  • PS Packet Switch
  • PSS Packet
  • the base station may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a transmit reception point (TRP) , or some other suitable terminology.
  • the base station 102 provides an access point to the EPC 160 or core network 190 for a UE 104.
  • Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player) , a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device.
  • SIP session initiation protocol
  • PDA personal digital assistant
  • the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc. ) .
  • the UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
  • the UE 104 may include a RACH procedure component 198 configured to transmit, to a base station, a Msg3 of a RACH procedure, the Msg3 being associated with a MAC-CE, receive, from the base station, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure, and initiate, upon receiving the DCI including the at least one field, an end to the RACH procedure.
  • a RACH procedure component 198 configured to transmit, to a base station, a Msg3 of a RACH procedure, the Msg3 being associated with a MAC-CE, receive, from the base station, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure, and initiate, upon receiving the DCI including the at least one field, an end to the RACH procedure.
  • the base station 180 may include a RACH procedure component 199 configured to receive the Msg3 of the RACH procedure, the Msg3 being associated with a MAC-CE, determine whether the UE is associated with the Msg3, and transmit, upon determining that no UE is associated with the Msg3, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure.
  • a RACH procedure component 199 configured to receive the Msg3 of the RACH procedure, the Msg3 being associated with a MAC-CE, determine whether the UE is associated with the Msg3, and transmit, upon determining that no UE is associated with the Msg3, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure.
  • FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure.
  • FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe.
  • FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure.
  • FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe.
  • the 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for both DL and UL.
  • FDD frequency division duplexed
  • TDD time division duplexed
  • the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL) , where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe 3 being configured with slot format 1 (with all UL) . While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols.
  • UEs are configured with the slot format (dynamically through DL control information (DCI) , or semi-statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI) .
  • DCI DL control information
  • RRC radio resource control
  • SFI received slot format indicator
  • a frame (10 ms) may be divided into 10 equally sized subframes (1 ms) .
  • Each subframe may include one or more time slots.
  • Subframes may also include mini-slots, which may include 7, 4, or 2 symbols.
  • Each slot may include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot may include 14 symbols, and for slot configuration 1, each slot may include 7 symbols.
  • the symbols on DL may be cyclic prefix (CP) orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols.
  • CP cyclic prefix
  • OFDM orthogonal frequency division multiplexing
  • the symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also referred to as single carrier frequency-division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to a single stream transmission) .
  • the number of slots within a subframe is based on the slot configuration and the numerology. For slot configuration 0, different numerologies ⁇ 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For slot configuration 1, different numerologies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe. Accordingly, for slot configuration 0 and numerology ⁇ , there are 14 symbols/slot and 2 ⁇ slots/subframe.
  • the subcarrier spacing and symbol length/duration are a function of the numerology.
  • the subcarrier spacing may be equal to 2 ⁇ *15 kHz, where ⁇ is the numerology 0 to 4.
  • the symbol length/duration is inversely related to the subcarrier spacing.
  • the slot duration is 0.25 ms
  • the subcarrier spacing is 60 kHz
  • the symbol duration is approximately 16.67 ⁇ s.
  • Each BWP may have a particular numerology.
  • a resource grid may be used to represent the frame structure.
  • Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs) ) that extends 12 consecutive subcarriers.
  • RB resource block
  • PRBs physical RBs
  • the resource grid is divided into multiple resource elements (REs) . The number of bits carried by each RE depends on the modulation scheme.
  • the RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE.
  • DM-RS demodulation RS
  • CSI-RS channel state information reference signals
  • the RS may also include beam measurement RS (BRS) , beam refinement RS (BRRS) , and phase tracking RS (PT-RS) .
  • BRS beam measurement RS
  • BRRS beam refinement RS
  • PT-RS phase tracking RS
  • FIG. 2B illustrates an example of various DL channels within a subframe of a frame.
  • the physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs) , each CCE including six RE groups (REGs) , each REG including 12 consecutive REs in an OFDM symbol of an RB.
  • CCEs control channel elements
  • REGs RE groups
  • a PDCCH within one BWP may be referred to as a control resource set (CORESET) .
  • CORESET control resource set
  • a UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and/or lower frequencies across the channel bandwidth.
  • a primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe/symbol timing and a physical layer identity.
  • a secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing.
  • the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the aforementioned DM-RS.
  • the physical broadcast channel (PBCH) which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) /PBCH block (also referred to as SS block (SSB) ) .
  • the MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) .
  • the physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and paging messages.
  • SIBs system information blocks
  • some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station.
  • the UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH) .
  • the PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH.
  • the PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used.
  • the UE may transmit sounding reference signals (SRS) .
  • the SRS may be transmitted in the last symbol of a subframe.
  • the SRS may have a comb structure, and a UE may transmit SRS on one of the combs.
  • the SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.
  • FIG. 2D illustrates an example of various UL channels within a subframe of a frame.
  • the PUCCH may be located as indicated in one configuration.
  • the PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) information (ACK /negative ACK (NACK) ) feedback.
  • UCI uplink control information
  • the PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and/or UCI.
  • BSR buffer status report
  • PHR power headroom report
  • FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network.
  • IP packets from the EPC 160 may be provided to a controller/processor 375.
  • the controller/processor 375 implements layer 3 and layer 2 functionality.
  • Layer 3 includes a radio resource control (RRC) layer
  • layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer.
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC medium access control
  • the controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs) , RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release) , inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression /decompression, security (ciphering, deciphering, integrity protection, integrity verification) , and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs) , demultiplexing of MAC SDU
  • the transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions.
  • Layer 1 which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing.
  • the TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M-QAM) ) .
  • BPSK binary phase-shift keying
  • QPSK quadrature phase-shift keying
  • M-PSK M-phase-shift keying
  • M-QAM M-quadrature amplitude modulation
  • the coded and modulated symbols may then be split into parallel streams.
  • Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream.
  • IFFT Inverse Fast Fourier Transform
  • the OFDM stream is spatially precoded to produce multiple spatial streams.
  • Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing.
  • the channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350.
  • Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318 TX.
  • Each transmitter 318 TX may modulate an RF carrier with a respective spatial stream for transmission.
  • each receiver 354 RX receives a signal through its respective antenna 352.
  • Each receiver 354 RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356.
  • the TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions.
  • the RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream.
  • the RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT) .
  • FFT Fast Fourier Transform
  • the frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal.
  • the symbols on each subcarrier, and the reference signal are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358.
  • the soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel.
  • the data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.
  • the controller/processor 359 can be associated with a memory 360 that stores program codes and data.
  • the memory 360 may be referred to as a computer-readable medium.
  • the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160.
  • the controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
  • the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression /decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
  • RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting
  • PDCP layer functionality associated with
  • Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing.
  • the spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.
  • the UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350.
  • Each receiver 318RX receives a signal through its respective antenna 320.
  • Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.
  • the controller/processor 375 can be associated with a memory 376 that stores program codes and data.
  • the memory 376 may be referred to as a computer-readable medium.
  • the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 350. IP packets from the controller/processor 375 may be provided to the EPC 160.
  • the controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
  • At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects in connection with 198 of FIG. 1.
  • At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 may be configured to perform aspects in connection with 199 of FIG. 1.
  • a UE may perform an RACH procedure to establish an RRC connection with, and communicate data transmissions, with a base station.
  • the UE may first receive a system information block (SIB) from the base station and decode the SIB.
  • SIB system information block
  • the UE may decode the SIB to retrieve the parameters for basic RACH configurations.
  • the UE may use plurality of resource information including the RACH configurations from the SIB to transmit a first message (Msg1) including a RACH preamble to the base station.
  • Msg1 first message
  • the base station may generate a random access response (RAR) as a response to the RACH preamble transmitted by the UE and transmit a second message (Msg2) including the RAR to the UE.
  • RAR random access response
  • Msg2 second message
  • the base station may use a TC-RNTI to generate the RAR. That is, a medium access control (MAC) layer of the base station may generate the RAR as a response to the RACH preamble transmitted by the UE.
  • the RAR may include the TC-RNTI, and the UE may use the TC-RNTI for the rest of the RA procedure.
  • the UE may use the TC-RNTI received in the Msg2 including the RAR to scramble a third message (Msg3) including an RRC connection request corresponding to the RAR grant via the PUSCH.
  • the base station may transmit a fourth message (Msg4) including the result of the RACH and the uplink grant via the PDSCH.
  • the UE may start monitoring and detecting the PDCCH for receiving the Msg4 via the PDSCH.
  • a UE without a C-RNTI may use the TC-RNTI from the RACH procedure as the C-RNTI of the UE in response to successfully establishing the RRC connection and secure the contention.
  • a UE that already has a C-RNTI may resume using the C-RNTI and discard the TC-RNTI received in RAR in response to successfully completing the RACH procedure.
  • a unique identification of C-RNTI may be dedicated to the UE, and the C-RNTI may be used for identifying an RRC connection and scheduling the data transmission.
  • the base station may use the C-RNTI to allocate the UE with uplink grants, downlink assignments, PDCCH order, etc.
  • the C-RNTI may also be used by the base station to differentiate the uplink transmissions, e.g., a PUSCH or a PUCCH, of the UE from the other UEs.
  • an RRC state mismatch may occur between the UE and the base station. That is, for some reason, the UE may be configured in an RRC connected state with the base station, where the base station may have released the RRC connection with the UE and consider that the UE is in an RRC idle state.
  • a UE may be a dedicated data subscription (DDS) subscriber (SUB) that may support the DDS, and two UEs including the DDS SUB and a non-DDS UE may share radio frequency resources.
  • DDS dedicated data subscription
  • SUB dedicated data subscription subscriber
  • the DDS SUB may be operating in connected mode, and in response to the non-DDS UE having a higher priority service, e.g., tracking area update (TAU) , the DDS SUB may perform a tuneaway (i.e., DDS SUB hand up) , and the non-DDS UE may occupy the shared radio frequency resources.
  • the DDS SUB may run a tuneaway timer during performing the tuneaway, and the DDS SUB may perform the tuneaway until the tuneaway timer expires.
  • the DDS SUB may not send and/or receive data with the base station. Accordingly, some abnormal issue may occur from the UE performing the tuneaway.
  • the base station may determine to release the RRC connection of the cell with the UE.
  • FIG. 4 illustrates a call-flow chart 400 of a method of wireless communication.
  • the call-flow chart 400 may include a DDS SUB 402 and a base station 404, and illustrates an example of RRC state mismatch occurring from the DDS SUB 402 performing a tuneaway.
  • the DDS SUB may connect with the base station.
  • a non-DDS may have a higher priority service and occupy the radio frequency resources, and the DDS SUB may perform the DDS tuneaway.
  • the base station may still schedule a DL data transmission to the DDS SUB.
  • the base station may send a downlink data transmission to the DDS SUB while the DDS SUB performs the tuneaway.
  • the DDS SUB performing the tuneaway may not be able to transmit an ACK /NACK feedback in response to the downlink data transmission from the base station, which may be due to the DDS SUB performing the tuneaway not using the radio frequency resources.
  • the base station may determine a DL RLC ARQ failure, and the base station may release the RRC connection with the UE.
  • the base station may determine that no ACK/NACK feedback is received from the UE in response to the DL data transmission schedule, and determine the DL RLC ARQ failure.
  • the base station may determine to release the RRC connection with the DDS SUB.
  • the base station may send an RRC release command (RRC OTA message) to the DDS SUB.
  • RRC OTA message RRC OTA message
  • the DDS SUB may not receive a release command. That is, the base station may transmit an RRC connection release to the DDS SUB.
  • the DDS SUB performing the tuneaway may not send and/or receive data transmissions with the base station, and the DDS SUB performing the tuneaway may not receive the RRC connection release command.
  • the DDS SUB may perform a DDS tuneback in response to the DDS SUB having a higher priority service.
  • a DDS SUB tuneback i.e., the DDS SUB determines to use the radio frequency resources
  • the UE may determine to send a schedule request to the base station to request a UL grant, if UE has UL data to transmit.
  • the DDS SUB may have UL data to transmit, and the DDS SUB may initiate a schedule request.
  • the base station has released the RRC connection of the DDS SUB at 412, and the base station may not transmit a UL DCI to the DDS SUB in response to the schedule request.
  • the DDS UE may not receive any UL DCI response from the base station in response to the schedule request.
  • the DDS SUB may repeat transmitting the schedule request to the base station.
  • the DDS SUB may determine the schedule request failure in response to the number of the schedule request transmissions reaching a maximum number of the schedule request transmissions. That is, the DDS SUB may be configured with the maximum number of schedule request transmissions, and the DDS SUB may determine the schedule request failure in response to the number of the schedule request transmissions meeting the maximum number of the schedule request transmissions.
  • the DDS SUB may trigger a contention-based RACH procedure in response to determining the schedule request failure.
  • the call-flow chart 400 illustrates one failed attempt of the RACH procedure 430.
  • the DDS SUB may send a Msg1 to the base station, receive a Msg2 from the base station, and send a C-RNTI MAC-CE in a Msg3 to the base station.
  • the base station may determine that the C-RNTI is not associated with any UE and the RRC connection with the DDS SUB is released, and not respond with the Msg4 to the DDS SUB in response to the Msg3 received from the DDS SUB.
  • the DDS SUB may transmit a Msg1 to the base station, and at 434, the base station may transmit the Msg2 in response to the received Msg1.
  • the UE may scramble the Msg3 using the TC-RNTI received in msg2, and include C-RNTI MAC CE in Msg3.
  • the base station may receive the Msg3 and determine that the C-RNTI received from the DDS SUB is released. The base station may not respond with the Msg4 to the DDS SUB in response to the received Msg3. Since the DDS SUB may not receive the Msg4 from the base station, the DDS SUB may repeat the RACH attempt.
  • the DDS SUB may trigger radio link failure (RLF) based on the repeated RACH attempt. That is, the DDS SUB may determine RLF in response to the number of RACH attempts reaching a value of the parameter preambleTransMax, which indicates the maximum number of RACH preamble transmissions. At 442, the DDS SUB may declare the RLF to the base station.
  • RLF radio link failure
  • the DDS SUB may trigger the RLF, and the time delay between the DDS SUB performing the tuneback at 416 and triggering the RLF at 442 may be long and useless, which may affect the user experience.
  • FIG. 4 illustrates an example of RRC state mismatch occurring from the DDS SUB performing a tuneaway, but the aspects of the present disclosure are not limited thereto. That is, other scenarios may cause the base station to release the RRC connection with the UE while the UE may maintain the RRC connection configuration to cause the RRC state mismatch between the UE and the base station.
  • the base station may schedule an UL data transmission and receive no PUSCH transmission, the base station may determine UL out-of-sync and trigger a PDCCH order RACH. After a RACH failure or an expiration of a timer, the base station may trigger the RLF to release the RRC connection with the UE.
  • the UE and the base station may be configured to stop the RACH procedure.
  • the base station may reuse the TC-RNTI DCI with a new field definition (may be referred to as a new TC-RNTI DCI) to indicate the UE to stop the RACH procedure. That is, the UE may receive the new TC-RNTI DCI from the base station, and determine to initiate an end to the RACH procedure.
  • the new TC-RNTI DCI may include a “frequency domain resource assignment” field indicating the UE to stop the RACH procedure.
  • a value of every bit of the “frequency domain resource assignment” field of the new TC-RNTI DCI may be set to one (1) to indicate the UE to stop the RACH procedure.
  • the UE may receive the new TC-RNTI DCI with the new field defined indicating the UE to stop the RACH procedure, and initiate an end to the RACH procedure in response to receiving the DCI indicating the end to the RACH procedure.
  • a second UE may also receive the DCI indicating the end to the RACH procedure when the second UE is not in an RRC state mismatch. That is, the second UE that is not in the RRC state mismatch may initiate a separate RACH procedure by sending the same Msg1 (the same RACH preamble and the same RACH occasion) as the first UE that is in the RRC state mismatch. Since the base station considers that the first UE is in an RRC idle state, the second UE may initiate the RACH procedure using the same RACH preamble and the same RACH occasion.
  • the base station may transmit the new TC-RNTI DCI with the new field defined indicating the first UE to stop the RACH procedure, and the second UE may also receive the new TC-RNTI DCI with the new field defined indicating the first UE to stop the RACH procedure triggered by the UE in the RRC state mismatch.
  • the second UE that is not in the RRC state mismatch may determine to ignore the new TC-RNTI DCI indicating the first UE to stop the RACH procedure in response to determining that the second UE did not transmit a Msg3 with a C-RNTI MAC-CE.
  • the second UE that is not in the RRC state mismatch with the base station may determine that the new TC-RNTI DCI with the new field defined indicating the first UE to stop the RACH procedure is not intended for the second UE by determining that the second UE did not transmit a Msg3 with a C-RNTI MAC-CE, and the second UE that is not in the RRC state mismatch may disregard the new TC-RNTI DCI indicating the first UE to stop the RACH procedure.
  • a UE may perform the process represented as follows:
  • the network including the base station may reuse the TC-RNTI DCI with a new field defined to indicate the UE to stop the RACH procedure in case there is an RRC state mismatch between the UE and the base station.
  • the base station may receive the Msg3 with a C-RNTI MAC-CE from a UE, and determine that no UE entity can be found to be associated with the C-RNTI MAC-CE. That is, the base station may have released the RRC connection with the UE, and the C-RNTI previously assigned to the UE may be released. Therefore, the base station may determine that the C-RNTI is not associated with the UE.
  • the base station instead of not responding to the Msg3 received from the UE, may send the new TC-RNTI DCI to indicate the UE to stop the RACH procedure.
  • the base station may define the new TC-RNTI DCI by scrambling DCI format 0_0 or DCI format 1_0 using the TC-RNTI and set at least one field of the new TC-RNTI DCI to indicate the UE to stop the RACH procedure.
  • the base station may set a “frequency domain resource assignment” field of the new TC-RNTI DCI to indicate the UE to stop the RACH procedure.
  • the base station may set the value of at least one bit of the “frequency domain resource assignment” field of the new TC-RNTI DCI to one (1) to indicate the UE to stop the RACH procedure.
  • the base station may set the value of every bit of the “frequency domain resource assignment” field of the new TC-RNTI DCI to one (1) to indicate the UE to stop the RACH procedure.
  • the DCI format 0_0 may be configured for stopping an ongoing random access procedure, with all remaining fields may be set as “reserved bits.
  • the DCI format 1_0 may be configured for stopping an ongoing random access procedure, with all remaining fields may be set as “reserved bits. ”
  • the UE may, in response to transmitting a Msg3 in a RACH procedure, receive a PDCCH transmission from the base station.
  • the UE may be configured to stop the current RACH procedure and indicate the RRC layer to perform the RRC reestablishment procedure or perform the RRC release procedure.
  • the UE may discard the TC-RNTI and consider the present contention resolution not successful.
  • the RACH attempt may be reduced and the interruption time may be reduced. That is, a base station may receive a Msg3 including a C-RNTI from a UE, detect an RRC state mismatch between the UE and the base station, and transmit the new TC-RNTI DCI to the UE indicating the UE to stop the RACH procedure. The UE may receive the new TC-RNTI DCI in response to the Msg3 including the C-RNTI from the base station, and initiate an end to the current RACH procedure to avoid or reduce the unnecessary time delay from the RACH failure due to the RRC state mismatch.
  • FIG. 5 illustrates a call-flow chart 500 of a method of wireless communication.
  • the call-flow chart 500 may include a UE 502 and a base station 504, and may illustrate an example of an RRC state mismatch between the UE 502 and the base station 504. That is, the UE may be configured in an RRC connected state with the base station, where the base station may have released the RRC connection with the UE and consider that the UE is in the RRC idle state. The UE may be configured in the RRC connected state, and the UE may, in response to determining the schedule request failure, initiate the RACH procedure with Msg3 include C-RNTI MAC CE. In one aspect, the UE may be a DDS SUB.
  • the UE may, as a part of the RACH procedure, transmit, to a base station, a Msg3 of a RACH procedure, the Msg3 being associated with a MAC-CE.
  • the base station may receive the Msg3 of the RACH procedure, the Msg3 being associated with a MAC-CE.
  • the Msg3 may include the C-RNTI MAC-CE.
  • the C-RNTI may be configured during the previous RACH procedure before the base station released the RRC connection with the UE.
  • the base station may determine whether the UE is associated with the Msg3 received from the UE at 506.
  • the base station may determine that the C-RNTI MAC-CE of the Msg3 received from the UE is not associated with any UE, and the base station may determine that the UE and the base station are in an RRC state mismatch.
  • the base station may transmit, upon determining that no UE is associated with the Msg3, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure.
  • the UE may receive, from the base station, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure.
  • the DCI may be scrambled using a TC-RNTI.
  • the first field of the at least one field indicating to stop the RACH procedure may be a frequency domain resource assignment field.
  • the frequency domain resource assignment field includes one or more bits, where all of the one or more bits are set to a value of one (1) indicating to stop the RACH procedure.
  • the value of every bit of the frequency domain resource assignment field of the TC-RNTI DCI may be set to one (1) to indicate the UE to stop the RACH procedure.
  • the UE may initiate, upon receiving the DCI including the at least one field from the base station, an end to the RACH procedure.
  • the UE may declare an RLF.
  • the UE may perform an RRC reestablishment procedure.
  • the UE may transmit, to the base station, an RRC reestablishment request.
  • the UE may initiate an RRC release and enter into an RRC idle state.
  • FIG. 6 is a flowchart 600 of a method of wireless communication. The method may be performed by a UE (e.g., the UE 104/502; the apparatus 1002) .
  • a UE e.g., the UE 104/502; the apparatus 1002 .
  • the UE may be configured to transmit, to a base station, a Msg3 of a RACH procedure, the Msg3 being associated with a MAC-CE (i.e., as at 506) .
  • the Msg3 may include the C-RNTI MAC-CE.
  • the C-RNTI may be configured during the previous RACH procedure before the base station released the RRC connection with the UE.
  • 602 may be performed by a RACH procedure component 1040.
  • the UE may be configured to receive, from the base station, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure (i.e., as at 510) .
  • the DCI may be scrambled using a TC-RNTI.
  • the first field of the at least one field indicating to stop the RACH procedure may be a frequency domain resource assignment field.
  • the frequency domain resource assignment field includes one or more bits, where all of the one or more bits are set to a value of one (1) indicating to stop the RACH procedure.
  • the value of every bit of the frequency domain resource assignment field of the TC-RNTI DCI may be set to one (1) to indicate the UE to stop the RACH procedure.
  • 604 may be performed by the RACH procedure component 1040.
  • the UE may be configured to initiate, upon receiving the DCI including the at least one field from the base station, an end to the RACH procedure (i.e., as at 512) .
  • 606 may be performed by the RACH procedure component 1040.
  • the UE may be configured to declare an RLF (i.e., as at 514) .
  • the UE may be configured to perform an RRC reestablishment procedure (i.e., as at 516) .
  • the UE may transmit, to the base station, an RRC reestablishment request (i.e., as at 518) .
  • 608, 610, and 612 may be performed by the RACH procedure component 1040.
  • the UE in response to initiating the end to the RACH procedure at 606, the UE may be configured to initiate an RRC release and enter into an RRC idle state (i.e., as at 520) .
  • 614 may be performed by the RACH procedure component 1040.
  • FIG. 7 is a flowchart 700 of a method of wireless communication.
  • the method may be performed by a base station (e.g., the base station 102/180/504; the apparatus 1102) .
  • a base station e.g., the base station 102/180/504; the apparatus 1102 .
  • the base station may be configured to receive the Msg3 of the RACH procedure, the Msg3 being associated with a MAC-CE (i.e., as at 506) .
  • the Msg3 may include the C-RNTI MAC-CE.
  • the C-RNTI may be configured during the previous RACH procedure before the base station released the RRC connection with the UE.
  • 702 may be performed by a RACH procedure component 1140.
  • the base station may be configured to determine whether the UE is associated with the Msg3 received from the UE at 702 (i.e., as at 508) .
  • the base station may determine that the C-RNTI MAC-CE of the Msg3 received from the UE is not associated with any UE, the base station may determine that the UE and the base station are in the RRC state mismatch.
  • 704 may be performed by the RACH procedure component 1140.
  • the base station may be configured to transmit, upon determining that no UE is associated with the Msg3, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure (i.e., as at 510) .
  • the DCI may be scrambled using a TC-RNTI.
  • the first field of the at least one field indicating to stop the RACH procedure may be a frequency domain resource assignment field.
  • the frequency domain resource assignment field includes one or more bits, where all of the one or more bits are set to a value of one (1) indicating to stop the RACH procedure.
  • the value of every bit of the frequency domain resource assignment field of the TC-RNTI DCI may be set to one (1) to indicate the UE to stop the RACH procedure.
  • 706 may be performed by the RACH procedure component 1140.
  • FIG. 8 illustrates a call-flow chart 800 of a method of wireless communication.
  • the call-flow chart 800 may include a UE 802 and a base station 804, and the UE 802 and the base station 804 may not have an RRC state mismatch.
  • the UE may receive, from a base station, DCI including a at least one field, a first field of the at least one field indicating to stop RACH procedure.
  • the DCI may be scrambled using a TC-RNTI.
  • the first field of the at least one field indicating to stop the RACH procedure may be a frequency domain resource assignment field.
  • the frequency domain resource assignment field includes one or more bits, where all of the one or more bits are set to a value of one (1) indicating to stop the RACH procedure.
  • the value of every bit of the frequency domain resource assignment field of the TC-RNTI DCI may be set to one (1) to indicate the UE to stop the RACH procedure.
  • the UE may determine whether the UE transmitted a Msg3 of a RACH procedure including a C-RNTI MAC-CE to the base station.
  • the UE may determine, upon determining that the UE did not transmit the Msg3 of the RACH procedure including the C-RNTI MAC-CE to the base station, to disregard the DCI including the at least one field.
  • FIG. 9 is a flowchart 900 of a method of wireless communication. The method may be performed by a UE (e.g., the UE 104; the apparatus 1002) .
  • a UE e.g., the UE 104; the apparatus 1002 .
  • the UE may be configured to receive, from a base station, DCI including a at least one field, a first field of the at least one field indicating to stop RACH procedure (i.e., as at 810) .
  • the DCI may be scrambled using a TC-RNTI.
  • the first field of the at least one field indicating to stop the RACH procedure may be a frequency domain resource assignment field.
  • the frequency domain resource assignment field includes one or more bits, where all of the one or more bits are set to a value of one (1) indicating to stop the RACH procedure.
  • the value of every bit of the frequency domain resource assignment field of the TC-RNTI DCI may be set to one (1) to indicate the UE to stop the RACH procedure.
  • 902 may be performed by a RACH procedure component 1040.
  • the UE may be configured to determine whether the UE transmitted a Msg3 of a RACH procedure including a C-RNTI MAC-CE to the base station (i.e., as at 812) .
  • 904 may be performed by the RACH procedure component 1040.
  • the UE may be configured to determine, upon determining that the UE did not transmit the Msg3 of the RACH procedure including the C-RNTI MAC-CE to the base station, to disregard the DCI including the at least one field (i.e., as at 814) .
  • 906 may be performed by the RACH procedure component 1040.
  • FIG. 10 is a diagram 1000 illustrating an example of a hardware implementation for an apparatus 1002.
  • the apparatus 1002 is a UE and includes a cellular baseband processor 1004 (also referred to as a modem) coupled to a cellular RF transceiver 1022 and one or more subscriber identity modules (SIM) cards 1020, an application processor 1006 coupled to a secure digital (SD) card 1008 and a screen 1010, a Bluetooth module 1012, a wireless local area network (WLAN) module 1014, a Global Positioning System (GPS) module 1016, and a power supply 1018.
  • the cellular baseband processor 1004 communicates through the cellular RF transceiver 1022 with the UE 104 and/or BS 102/180.
  • the cellular baseband processor 1004 may include a computer-readable medium /memory.
  • the computer-readable medium /memory may be non-transitory.
  • the cellular baseband processor 1004 is responsible for general processing, including the execution of software stored on the computer-readable medium /memory.
  • the software when executed by the cellular baseband processor 1004, causes the cellular baseband processor 1004 to perform the various functions described supra.
  • the computer-readable medium /memory may also be used for storing data that is manipulated by the cellular baseband processor 1004 when executing software.
  • the cellular baseband processor 1004 further includes a reception component 1030, a communication manager 1032, and a transmission component 1034.
  • the communication manager 1032 includes the one or more illustrated components.
  • the components within the communication manager 1032 may be stored in the computer-readable medium /memory and/or configured as hardware within the cellular baseband processor 1004.
  • the cellular baseband processor 1004 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359.
  • the apparatus 1002 may be a modem chip and include just the baseband processor 1004, and in another configuration, the apparatus 1002 may be the entire UE (e.g., see 350 of FIG. 3) and include the aforediscussed additional modules of the apparatus 1002.
  • the communication manager 1032 includes a RACH procedure component 1040 that is configured to transmit, to a base station, a Msg3 of a RACH procedure, the Msg3 being associated with a MAC-CE, receive, from the base station, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure, initiate, upon receiving the DCI including the at least one field from the base station, an end to the RACH procedure, declare an RLF, perform an RRC reestablishment procedure, transmit, to the base station, an RRC reestablishment request, initiate an RRC release and enter into an RRC idle state, determine whether the UE transmitted a Msg3 of a RACH procedure including a C- RNTI MAC-CE to the base station, and determine, upon determining that the UE did not transmit the Msg3 of the RACH procedure including the C-RNTI MAC-CE to the base station, to disregard the DCI including the at least one field, e.g.,
  • the apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowcharts of FIGs. 5, 6, and 8. As such, each block in the aforementioned flowcharts of FIGs. 5, 6, and 8 may be performed by a component and the apparatus may include one or more of those components.
  • the components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.
  • the apparatus 1002 includes means for transmitting, to a base station, a Msg3 of a RACH procedure, the Msg3 being associated with a MAC-CE, means for receiving, from the base station, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure, and means for initiating, upon receiving the DCI including the at least one field, an end to the RACH procedure.
  • the apparatus 1002 includes means for initiating, upon receiving the DCI including the at least one field, an RLF, means for performing, upon initiating the RLF, an RRC reestablishment procedure, and means for transmitting, in response to performing the RRC reestablishment procedure, an RRC reestablishment request to the base station.
  • the apparatus 1002 includes means for initiating, upon initiating the end to the RACH procedure, an RRC release, and means for entering into an RRC idle state.
  • the apparatus 1002 includes means for receiving, from a base station, DCI including a at least one field, a first field of the at least one field indicating to stop RACH procedure, means for determining whether the UE transmitted a Msg3 of a RACH procedure including a C-RNTI MAC-CE to the base station, and means for determining, upon determining that the UE did not transmit the Msg3 of the RACH procedure including the C-RNTI MAC-CE to the base station, to disregard the DCI including the at least one field.
  • the aforementioned means may be one or more of the aforementioned components of the apparatus 1002 configured to perform the functions recited by the aforementioned means.
  • the apparatus 1002 may include the TX Processor 368, the RX Processor 356, and the controller/processor 359.
  • the aforementioned means may be the TX Processor 368, the RX Processor 356, and the controller/processor 359 configured to perform the functions recited by the aforementioned means.
  • FIG. 11 is a diagram 1100 illustrating an example of a hardware implementation for an apparatus 1102.
  • the apparatus 1102 is a BS and includes a baseband unit 1104.
  • the baseband unit 1104 may communicate through a cellular RF transceiver 1122 with the UE 114.
  • the baseband unit 1104 may include a computer-readable medium /memory.
  • the baseband unit 1104 is responsible for general processing, including the execution of software stored on the computer-readable medium /memory.
  • the software when executed by the baseband unit 1104, causes the baseband unit 1104 to perform the various functions described supra.
  • the computer-readable medium /memory may also be used for storing data that is manipulated by the baseband unit 1104 when executing software.
  • the baseband unit 1104 further includes a reception component 1130, a communication manager 1132, and a transmission component 1134.
  • the communication manager 1132 includes the one or more illustrated components.
  • the components within the communication manager 1132 may be stored in the computer-readable medium /memory and/or configured as hardware within the baseband unit 1104.
  • the baseband unit 1104 may be a component of the BS 310 and may include the memory 376 and/or at least one of the TX processor 316, the RX processor 370, and the controller/processor 375.
  • the communication manager 1132 includes a RACH procedure component 1140 that is configured to receive the Msg3 of the RACH procedure, the Msg3 being associated with a MAC-CE, determine whether the UE is associated with the Msg3 received from the UE, and transmit, upon determining that no UE is associated with the Msg3, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure, e.g., as described in connection with 702, 704, and 706.
  • a RACH procedure component 1140 is configured to receive the Msg3 of the RACH procedure, the Msg3 being associated with a MAC-CE, determine whether the UE is associated with the Msg3 received from the UE, and transmit, upon determining that no UE is associated with the Msg3, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure, e.g., as described in connection with 702, 704, and 706.
  • the apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowcharts of FIGs. 5 and 7. As such, each block in the aforementioned flowcharts of FIGs. 5 and 7 may be performed by a component and the apparatus may include one or more of those components.
  • the components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.
  • the apparatus 1102 includes means for receiving a Msg3 of a RACH procedure, the Msg3 being associated with a MAC-CE, means for determining whether a UE is associated with the Msg3, and means for transmitting, upon determining that no UE is associated with the Msg3, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure.
  • the aforementioned means may be one or more of the aforementioned components of the apparatus 1102 configured to perform the functions recited by the aforementioned means.
  • the apparatus 1102 may include the TX Processor 316, the RX Processor 370, and the controller/processor 375.
  • the aforementioned means may be the TX Processor 316, the RX Processor 370, and the controller/processor 375 configured to perform the functions recited by the aforementioned means.
  • a UE may transmit, to a base station, a Msg3 of a RACH procedure, the Msg3 being associated with a MAC-CE, receive, from the base station, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure, and initiate, upon receiving the DCI including the at least one field, an end to the RACH procedure.
  • the Msg3 may include a C-RNTI MAC-CE.
  • the UE may be a DDS SUB.
  • the UE may initiate, upon receiving the DCI including the at least one field, an RLF, perform, upon initiating the RLF, an RRC reestablishment procedure, and transmit, in response to performing the RRC reestablishment procedure, an RRC reestablishment request to the base station.
  • the UE may also initiate, upon initiating the end to the RACH procedure, an RRC release, and enter into an RRC idle state.
  • the DCI may be scrambled using a TC-RNTI.
  • the first field of the at least one field indicating to stop the RACH procedure may be a frequency domain resource assignment field.
  • the frequency domain resource assignment field may include one or more bits, where all of the one or more bits are set to a value of one (1) indicating to stop the RACH procedure.
  • the DCI including the at least one field may be received via a PDCCH.
  • the UE may receive, from a base station, DCI including a at least one field, a first field of the at least one field indicating to stop RACH procedure, determine whether the UE transmitted a Msg3 of a RACH procedure including a C-RNTI MAC-CE to the base station, and determine, upon determining that the UE did not transmit the Msg3 of the RACH procedure including the C-RNTI MAC-CE to the base station, to disregard the DCI including the at least one field.
  • the base station may receive a Msg3 of a RACH procedure, the Msg3 being associated with a MAC-CE, determine whether a UE is associated with the Msg3, and transmit, upon determining that no UE may be associated with the Msg3, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure.
  • Combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C.
  • combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C.
  • a UE may transmit, to a base station, a Msg3 of a RACH procedure, the Msg3 being associated with a MAC-CE, receive, from the base station, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure, and initiate, upon receiving the DCI including the at least one field, an end to the RACH procedure.
  • the Msg3 may include a C-RNTI MAC-CE.
  • the UE may be a DDS SUB.
  • the UE may also transmit, upon receiving the DCI including at least one field, an indication of an RLF to the base station.
  • the UE may perform, upon transmitting the indication of the RLF, an RRC reestablishment procedure.
  • the UE may transmit, to the base station, a request for a current fallback RRC establish procedure.
  • the UE may also initiate, upon initiating the end to the RACH procedure, an RRC release, and enter into an RRC idle state.
  • the DCI may be scrambled using a TC-RNTI.
  • the first field of the at least one field indicating to stop the RACH procedure may be a frequency domain resource assignment field.
  • the frequency domain resource assignment field may include one or more bits, where all of the one or more bits are set to a value of one (1) indicating to stop the RACH procedure.
  • the DCI including at least one field may be received via a PDCCH.
  • the UE may receive, from a base station, DCI including at least one field, a first field of the at least one field indicating to stop RACH procedure, determine whether the UE transmitted a Msg3 of a RACH procedure including a C-RNTI MAC-CE to the base station, and determine, upon determining that the UE did not transmit the Msg3 of the RACH procedure including the C-RNTI MAC-CE to the base station, to disregard the DCI including the at least one field.
  • a base station may receive a Msg3 of a RACH procedure, the Msg3 being associated with a MAC-CE, determine whether a UE is associated with the Msg3, and transmit, upon determining that no UE may be associated with the Msg3, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure.
  • the base station may receive the Msg3 including the C-RNTI from the UE, detect the RRC state mismatch between the UE and the base station, and transmit the new TC-RNTI DCI to the UE instructing the UE to stop the RACH procedure.
  • the UE may receive the new TC-RNTI DCI in response to the Msg3 including the C-RNTI from the base station, and initiate an end to the current RACH procedure to avoid or reduce the unnecessary time delay from the RACH failure due to the RRC state mismatch.
  • Aspect 1 is a method of a wireless communication of a UE, where the method includes transmitting, to a base station, a Msg3 of a RACH procedure, the Msg3 being associated with a MAC-CE, receiving, from the base station, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure, and initiating, upon receiving the DCI including the at least one field, an end to the RACH procedure.
  • Aspect 2 is the method of aspect 1, where the Msg3 includes a C-RNTI MAC-CE.
  • Aspect 3 is the method of any of aspects 1 and 2, where the DCI is scrambled using a TC-RNTI.
  • Aspect 4 is the method of any of aspects 1 to 3, where the first field of the at least one field indicating to stop the RACH procedure is a frequency domain resource assignment field.
  • Aspect 5 is the method of aspect 4, where the frequency domain resource assignment field includes one or more bits, where all of the one or more bits are set to a value of one (1) indicating to stop the RACH procedure.
  • Aspect 6 is the method of any of aspects 1 to 5, where the DCI including the at least one field is received via a PDCCH.
  • Aspect 7 is the method of any of aspects 1 to 6, the method further includes initiating, upon receiving the DCI including the at least one field, an RLF.
  • Aspect 8 is the method of aspect 7, the method further includes performing, upon initiating the RLF, an RRC reestablishment procedure.
  • Aspect 9 is the method of aspect 8, the method further includes transmitting, in response to performing the RRC reestablishment procedure, a radio resource control (RRC) reestablishment request to the base station.
  • RRC radio resource control
  • Aspect 10 is the method of any of aspects 1 to 6, the method further includes initiating, upon initiating the end to the RACH procedure, an RRC release, and entering into an RRC idle state.
  • Aspect 11 is the method of any of aspects 1 to 10, where the UE is a DDS SUB.
  • Aspect 12 is an apparatus for wireless communication including at least one processor coupled to a memory and configured to implement a method as in any of aspects 1 to 11.
  • Aspect 13 is an apparatus for wireless communication including means for implementing a method as in any of aspects 1 to 11.
  • Aspect 14 is a computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement a method as in any of aspects 1 to 11.
  • Aspect 15 is a method of a wireless communication of a UE, where the method includes receiving, from a base station, DCI including a at least one field, a first field of the at least one field indicating to stop RACH procedure, determining whether the UE transmitted a Msg3 of a RACH procedure including a C-RNTI MAC-CE to the base station, and determining, upon determining that the UE did not transmit the Msg3 of the RACH procedure including the C-RNTI MAC-CE to the base station, to disregard the DCI including the at least one field.
  • Aspect 16 is the method of aspect 15, where the DCI is scrambled using a TC-RNTI.
  • Aspect 17 is the method of any of aspects 15 and 16, where the first field of the at least one field indicating to stop the RACH procedure is a frequency domain resource assignment field.
  • Aspect 18 is the method of aspect 17, where the frequency domain resource assignment field includes one or more bits, where all of the one or more bits are set to a value of one (1) indicating to stop the RACH procedure.
  • Aspect 19 is the method of any of aspects 15 to 18, where the DCI including the at least one field is received via a PDCCH.
  • Aspect 20 is an apparatus for wireless communication including at least one processor coupled to a memory and configured to implement a method as in any of aspects 15 to 19.
  • Aspect 21 is an apparatus for wireless communication including means for implementing a method as in any of aspects 15 to 19.
  • Aspect 22 is a computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement a method as in any of aspects 15 to 19.
  • Aspect 23 is a method of a wireless communication of a UE, where the method includes receiving a Msg3 of a RACH procedure, the Msg3 being associated with a MAC-CE, determining whether a UE is associated with the Msg3, and transmitting, upon determining that no UE is associated with the Msg3, DCI including at least one field, a first field of the at least one field indicating to stop the RACH procedure.
  • Aspect 24 is the method of aspect 23, where the Msg3 includes a C-RNTI MAC-CE.
  • Aspect 25 is the method of any of aspects 23 and 24, where the DCI is scrambled using a TC-RNTI.
  • Aspect 26 is the method of any of aspects 23 to 25, where the first field of the at least one field indicating to stop the RACH procedure is a frequency domain resource assignment field.
  • Aspect 27 is the method of aspect 26, where the frequency domain resource assignment field includes one or more bits, where all of the one or more bits are set to a value of one (1) indicating to stop the RACH procedure.
  • Aspect 28 is the method of any of aspects 23 to 27, where the DCI including the at least one field is transmitted via a PDCCH.
  • Aspect 29 is an apparatus for wireless communication including at least one processor coupled to a memory and configured to implement a method as in any of aspects 23 to 28.
  • Aspect 30 is an apparatus for wireless communication including means for implementing a method as in any of aspects 23 to 28.
  • Aspect 31 is a computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement a method as in any of aspects 23 to 28.

Landscapes

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

Abstract

Un EU peut transmettre, à une station de base, un message Msg3 d'une procédure RACH associée à un élément de contrôle MAC-CE, recevoir, en provenance de la station de base, des informations DCI comprenant au moins un champ, un premier champ du/des champ(s) indiquant d'arrêter la procédure RACH, et initier, lors de la réception des informations DCI comprenant le(s) champ(s), une fin de la procédure RACH. Le message Msg3 peut comprendre un élément de contrôle C-RNTI MAC-CE. La station de base peut recevoir le message Msg3 de l'EU, déterminer si l'EU est associé au message Msg3 et transmettre, lors de la détermination qu'aucun EU n'est associé au message Msg3, des informations DCI comprenant au moins un champ, un premier champ du/des champ(s) indiquant d'arrêter la procédure RACH.
PCT/CN2021/072399 2021-01-18 2021-01-18 Contrôle de procédure rach en cas de conflit d'état rrc WO2022151465A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/072399 WO2022151465A1 (fr) 2021-01-18 2021-01-18 Contrôle de procédure rach en cas de conflit d'état rrc

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/072399 WO2022151465A1 (fr) 2021-01-18 2021-01-18 Contrôle de procédure rach en cas de conflit d'état rrc

Publications (1)

Publication Number Publication Date
WO2022151465A1 true WO2022151465A1 (fr) 2022-07-21

Family

ID=82446809

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/072399 WO2022151465A1 (fr) 2021-01-18 2021-01-18 Contrôle de procédure rach en cas de conflit d'état rrc

Country Status (1)

Country Link
WO (1) WO2022151465A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110475371A (zh) * 2018-05-09 2019-11-19 夏普株式会社 用户设备执行的方法、用户设备和基站
US20200221504A1 (en) * 2019-01-03 2020-07-09 Comcast Cable Communications, Llc Access procedures in wireless communications

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110475371A (zh) * 2018-05-09 2019-11-19 夏普株式会社 用户设备执行的方法、用户设备和基站
US20200221504A1 (en) * 2019-01-03 2020-07-09 Comcast Cable Communications, Llc Access procedures in wireless communications

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Further discussion on the impact of DCI-based PDCCH skipping", 3GPP DRAFT; R2-1906904 FURTHER DISCUSSION ON THE IMPACT OF DCI-BASED PDCCH SKIPPING, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, USA; 20190513 - 20190517, 13 May 2019 (2019-05-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051730356 *
INTERDIGITAL INC.: "Random Access procedure on SUL", 3GPP DRAFT; R2-1712783 (R15 NR WI AI103144 RA PROCEDURE ON THE SUL), 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, USA; 20171127 - 20171201, 17 November 2017 (2017-11-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051371686 *
NTT DOCOMO, INC.: "Discussion on RRC state mismatch issue", 3GPP DRAFT; R2-167140_DISCUSSION ON RRC STATE MISMATCH ISSUE#95BIS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Kaohsiung, Taiwan; 20161010 - 20161014, 9 October 2016 (2016-10-09), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051151534 *

Similar Documents

Publication Publication Date Title
US11770870B2 (en) Methods and apparatus related to beam recovery in the secondary cell
US11405094B2 (en) Default quasi co-location assumption after beam failure recovery for single-downlink control information-based multiple transmit receive point communication
EP3925371B1 (fr) Système et procédé de hiérarchisation de procédures d'accès aléatoire
US11611999B2 (en) Procedures for concurrent MSG2 PDCCH monitoring
WO2020154992A1 (fr) Procédure d'accès aléatoire basée sur une procédure de canal d'accès aléatoire en deux étapes et sur une procédure de canal d'accès aléatoire en quatre étapes
US11991751B2 (en) Identification of user equipment in a random access procedure
US11832309B2 (en) Message2 or MessageB with PDCCH inside PDSCH resources
US11665742B2 (en) RACH type selection and different sets of RACH parameters
WO2021092820A1 (fr) Accès aléatoire basé sur des ressources d'accès aléatoire en semi-duplex et des ressources d'accès aléatoire en duplex intégral
US20230199852A1 (en) Interaction of prach repetition and request of msg3 repetition
WO2023035208A1 (fr) Demande de répétition pour l'amélioration de la couverture
US11617203B2 (en) Sounding reference signals triggered by random access message 2 for random access message 4 quasi co-location
WO2022021154A1 (fr) Procédé et appareil de transmission de données dans des procédures rach
US20220132584A1 (en) Ra-rnti formula for extended random access response windows
WO2022151465A1 (fr) Contrôle de procédure rach en cas de conflit d'état rrc
US20240129958A1 (en) Random access configuration and procedure in full-duplex operation
US11627609B2 (en) Multi-segment RAR window for PRACH retransmission
WO2022160254A1 (fr) Ressource de liaison montante préconfigurée assistée par un signal de liaison montante
US20220361255A1 (en) Additional rach reference slots
WO2022087939A1 (fr) Évitement d'un rejet d'enregistrement dû à un transfert vers un nr lors d'une mise à jour de zone de suivi
WO2022056830A1 (fr) Retransmission rapide d'une demande d'établissement de session pdu après une défaillance de couche inférieure
WO2022036701A1 (fr) Amélioration de la libération rapide de non-dds

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21918667

Country of ref document: EP

Kind code of ref document: A1