CN117796077A - Method for monitoring tracking reference signal and related equipment - Google Patents
Method for monitoring tracking reference signal and related equipment Download PDFInfo
- Publication number
- CN117796077A CN117796077A CN202280052813.8A CN202280052813A CN117796077A CN 117796077 A CN117796077 A CN 117796077A CN 202280052813 A CN202280052813 A CN 202280052813A CN 117796077 A CN117796077 A CN 117796077A
- Authority
- CN
- China
- Prior art keywords
- trs
- csi
- indication
- pei
- availability indication
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 139
- 238000012544 monitoring process Methods 0.000 title claims description 128
- 125000004122 cyclic group Chemical group 0.000 claims description 5
- 230000004048 modification Effects 0.000 description 127
- 238000012986 modification Methods 0.000 description 127
- 101150096310 SIB1 gene Proteins 0.000 description 36
- 230000011664 signaling Effects 0.000 description 33
- 230000005540 biological transmission Effects 0.000 description 32
- ZRBFEDMQRDRUDG-UHFFFAOYSA-N silicon hexaboride Chemical compound B12B3[Si]45B3B2B4B51 ZRBFEDMQRDRUDG-UHFFFAOYSA-N 0.000 description 32
- 238000004891 communication Methods 0.000 description 28
- 230000004044 response Effects 0.000 description 27
- 238000010586 diagram Methods 0.000 description 22
- 235000019527 sweetened beverage Nutrition 0.000 description 18
- 238000001514 detection method Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 10
- 230000008569 process Effects 0.000 description 10
- 238000011084 recovery Methods 0.000 description 10
- 230000009471 action Effects 0.000 description 7
- 230000007246 mechanism Effects 0.000 description 7
- 238000005259 measurement Methods 0.000 description 6
- 102100022734 Acyl carrier protein, mitochondrial Human genes 0.000 description 5
- 101000678845 Homo sapiens Acyl carrier protein, mitochondrial Proteins 0.000 description 5
- 230000006978 adaptation Effects 0.000 description 5
- 230000008859 change Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 239000000725 suspension Substances 0.000 description 5
- 101100274486 Mus musculus Cited2 gene Proteins 0.000 description 4
- 101150096622 Smr2 gene Proteins 0.000 description 4
- 230000009977 dual effect Effects 0.000 description 4
- 238000007726 management method Methods 0.000 description 3
- 238000013468 resource allocation Methods 0.000 description 3
- 238000001228 spectrum Methods 0.000 description 3
- 101150039363 SIB2 gene Proteins 0.000 description 2
- 238000013475 authorization Methods 0.000 description 2
- 230000006399 behavior Effects 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 230000001276 controlling effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000011218 segmentation Effects 0.000 description 2
- CSRZQMIRAZTJOY-UHFFFAOYSA-N trimethylsilyl iodide Substances C[Si](C)(C)I CSRZQMIRAZTJOY-UHFFFAOYSA-N 0.000 description 2
- 101150064138 MAP1 gene Proteins 0.000 description 1
- 101100533725 Mus musculus Smr3a gene Proteins 0.000 description 1
- 229920002873 Polyethylenimine Polymers 0.000 description 1
- -1 SIB7 Chemical compound 0.000 description 1
- 230000003044 adaptive effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001427 coherent effect Effects 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000010287 polarization Effects 0.000 description 1
- 229920001601 polyetherimide Polymers 0.000 description 1
- 238000007639 printing Methods 0.000 description 1
- 238000012913 prioritisation Methods 0.000 description 1
- 230000000644 propagated effect Effects 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 238000000060 site-specific infrared dichroism spectroscopy Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000153 supplemental effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
- 238000004929 transmission Raman spectroscopy Methods 0.000 description 1
- 230000007723 transport mechanism Effects 0.000 description 1
- 238000012384 transportation and delivery Methods 0.000 description 1
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
A method for a User Equipment (UE) to decide on Tracking Reference Signal (TRS) resource set availability is provided. The method includes receiving a TRS configuration from a Base Station (BS), the TRS configuration indicating one or more TRS resource sets for a UE to monitor a reference signal; deciding whether a layer 1 (L1) -based availability indication for one or more TRS resource sets is received from the BS; when the UE decides that an L1-based availability indication has not been received from the BS, it decides that one or more TRS resource sets are not available.
Description
Cross Reference to Related Applications
The present application claims the benefit and priority of U.S. provisional application Ser. No. 63/228,986, filed 8/2021, entitled "PAGING EARLY INDICATION", and the benefit and priority of U.S. provisional application Ser. No. 63/203,974, filed 8/2021, entitled "TRACKING REFERENCE SIGNAL IN IDLE AND INACTIVE", the contents of which are incorporated herein by reference in their entirety.
Technical Field
The present application relates generally to wireless communications, and more particularly, to a method for monitoring tracking reference signals and related devices configured to employ the method.
Background
With the tremendous increase in the number of connected devices and the rapid increase in user/network traffic, various efforts have been made to improve various aspects of the next generation wireless communication system, such as the fifth generation (5G) New Radio (NR) system, by various efforts to improve data rate, latency, reliability, and mobility.
The 5G NR system is intended to provide flexibility and configurability to optimize network services and types to accommodate various use cases, such as enhanced mobile broadband (enhanced Mobile Broadband, eMBB), large-scale Machine-type communication (emtc) and Ultra-Reliable and Low-delay communication (URLLC).
However, as the demand for radio access continues to increase, there is a need for further improvements in wireless communication of next-generation wireless communication systems.
Disclosure of Invention
The application provides a monitoring method and a related device for tracking a reference signal TRS.
According to an aspect of the present application, there is provided a method for a user equipment UE to monitor a tracking reference signal TRS, the method comprising: receiving a TRS configuration from a base station BS, the TRS configuration indicating one or more TRS resource sets for the UE monitoring reference signals; deciding whether to receive a layer 1L 1-based availability indication for the one or more TRS resource sets from the BS; and when the UE decides that the layer 1L1 based availability indication has not been received from the BS, deciding that one or more of the TRS resource sets are not available.
According to another aspect of the present application, a UE for monitoring a Tracking Reference Signal (TRS) is provided. The UE includes at least one processor and at least one memory coupled to the at least one processor and storing computer-executable instructions that, when executed by the at least one processor, cause the UE to perform the above disclosed method of monitoring the TRS.
Drawings
Aspects of the present exemplary disclosure are best understood from the following detailed description when read with the accompanying drawing figures. The various features are not drawn to scale for clarity of discussion and the dimensions of the various features may be arbitrarily increased or reduced.
Fig. 1 shows a timing diagram of a discontinuous reception (discontinuous reception, DRX) cycle according to one of the exemplary embodiments of the present application.
Fig. 2 illustrates a timing diagram of paging downlink control information (Downlink Control Information, DCI), short messages, and paging messages according to one of the exemplary embodiments of the present application.
Fig. 3 shows a timing diagram of Cell-specific reference signals (Cell-specific Reference Signal, CRS) in a DRX cycle according to one of the exemplary embodiments of the present application.
Fig. 4 illustrates a timing diagram of Search Space (SS)/physical broadcast channel (Physical Broadcast Channel, PBCH) block (SSB) in a DRX cycle according to one of the exemplary embodiments of the present application.
Fig. 5 illustrates a timing diagram of a TRS/channel state information reference signal (TRS/CSI-RS) in a DRX cycle according to one of the exemplary embodiments of the present application.
Fig. 6 shows a timing diagram of DCI-based paging early indication (Paging Early Indication, PEI) in a DRX cycle according to one of the exemplary embodiments of the present application.
Fig. 7 shows a timing diagram of sequence-based PEI in a DRX cycle according to one of the exemplary embodiments of the present application.
Fig. 8 illustrates a timing diagram of TRS/CSI-RS active time for paging DCI according to one of the exemplary embodiments of the present application.
Fig. 9 shows a timing diagram of TRS/CSI-RS active time for PEI according to one of the exemplary embodiments of the present application.
Fig. 10 shows a timing diagram of overlapping physical downlink control channel (Physical Downlink Control Channel, PDCCH) monitoring occasions according to one of the exemplary embodiments of the present application.
Fig. 11 shows a flowchart of a method/process for monitoring a TRS according to one of the exemplary embodiments of the present application.
Fig. 12 illustrates a block diagram of a node for wireless communication according to one of the exemplary embodiments of the present application.
Detailed Description
The abbreviations in this application are defined as follows, with the following meanings unless otherwise indicated:
abbreviation full scale
Acknowledgement (Acknowledges, ACK)
Automatic gain control (Automatic Gain Control, AGC)
Access layer (Access Stratum, AS)
Partial bandwidth (Bandwidth Adaptation, BA)
Broadcast control channel (Broadcast Control Channel, BCCH)
Base Station (Base Station, BS)
Buffer status report (Buffer Status Report BSR)
Bandwidth portion (Bandwidth portion, BWP)
Contention-based random access (Contention Based Random Access, CBRA)
Common control channel (Common Control Channel, CCCH)
Control channel element (Control Channel Element, CCE)
Control Element (Control Element, CE)
Non-contention random access (Contention Free Random Access, CFRA)
Configuration authorization (Configured Grant, CG)
Commercial mobile alert system (Commercial Mobile Alert System, CMAS)
Control resource set (Control Resource Set, CORESET)
Cell radio network temporary identifier (Cell-Radio Network Temporary Identifier, C-RNTI)
Cell-specific reference signals (Cell-specific Reference Signal, CRS)
Channel state information (Channel State Information, CSI)
Configured scheduling RNTI (Configured Scheduling RNTI, CS-RNTI)
Public search space (Common Search Space, CSS)
Downlink control information (Downlink Control Information, DCI)
Downlink feedback information (Downlink Feedback Information, DFI)
Dynamic license (DG)
Downlink (DL)
Demodulation reference signal (Demodulation Reference Signal, DMRS)
Data radio bearers (Data Radio Bearer, DRB)
Discontinuous reception (discontinuous reception, DRX)
Evolution Node B (evolved Node B, eNB)
Earthquake and tsunami warning system (Earthquake and Tsunami Warning System, ETWS)
Evolved universal terrestrial radio access (Evolved Universal Terrestrial Radio Access, E-UTRA)
Frequency Range (FR)
Next generation node B (Next Generation Node B, gNB)
Hybrid automatic repeat request (Hybrid Automatic Repeat request, HARQ)
Information element (Information Element, IE)
Physical Layer 1 (L1)
Logical Channel (LCH)
Logical channel priority (Logical Channel Prioritization, LCP)
Media access control (Medium Access Control, MAC)
Main cell group (Master Cell Group, MCG)
Modulation and coding strategy (Modulation and Coding Scheme, MCS)
Maximum allowable exposure (Maximum Permissible Exposure, MPE)
Message (Message, msg)
Non-acknowledgement (Non-Acknowledges, NACK)
Non-Access Stratum (Non-Access Stratum, NAS)
New Radio (New Radio, NR)
Network (Network, NW)
Normal Uplink (NUL)
Physical broadcast channel (Physical Broadcast Channel, PBCH)
Primary Cell (Primary Cell, PCell)
Packet data convergence protocol (Packet Data Convergence Protocol, PDCP)
Physical downlink control channel (Physical Downlink Control Channel, PDCCH)
Physical downlink shared channel (Physical Downlink Shared Channel, PDSCH)
Protocol data unit (Protocol Data Unit, PDU)
Early paging indicator (Paging Early Indication, PEI)
Paging Frames (PF)
Paging Occasion (PO)
Physical Layer (Physical Layer, PHY)
Physical random access channel (Physical Random Access Channel PRACH)
Physical resource block (Physical Resource Block PRB)
Paging RNTI (Paging-RNTI, P-RNTI)
Primary and secondary cells (Primary Secondary Cell, PScell)
Physical uplink control channel (Physical Uplink Control Channel, PUCCH)
Physical uplink shared channel (Physical Uplink Shared Channel, PUSCH)
Public warning system (public warning system PWS)
Quasi-parity (Quasi Co Location QCL)
Random Access (RA)
Random access channel (Random Access Channel, RACH)
Random access response (Random Access Response, RAR)
Release (Release, rel)
Radio link control (Radio Link Control, RLC)
RAN notification area (RAN Notification Area, RNA)
Residual minimum system information (Remaining Minimum System Information, RMSI)
Radio network temporary identifier (Radio Network Temporary Identifier, RNTI)
RACH opportunity (RACH Occasion, RO)
Radio resource control (Radio Resource Control, RRC)
Radio resource management (Radio Resource Management, RRM)
Reference Signal (Reference Signal, RS)
Reference signal received power (Reference Signal Receiving Power, RSRP)
Reception (Reception Rx)
Secondary Cell (SCell)
Secondary cell group (Secondary Cell Group, SCG)
Subcarrier spacing (Subcarrier Spacing, SCS)
Service data adaptation protocol (Service Data Application Protocol, SDAP)
Small data transfer (Small Data Transmission, SDT)
Service data unit (Service Data Unit, SDU)
System frame number (System Frame Number SFN)
System information (System Information, SI)
System information block (System Information Block, SIB)
Semi-persistent scheduling (Semi-Persistent Scheduling, SPS)
Special Cell (SpCell)
Signaling radio bearers (Signaling Radio Bearer, SRB)
Scheduling request (Scheduling Request, SR)
Channel sounding reference signal (Sounding Reference Signal, SRS)
Search Space (Search Space, SS)
SS/PBCH Block (SS/PBCH Block, SSB)
Synchronous signal block (Synchronization Signal Block, SSB)
Synchronization signal RSRP (Synchronization Signal-RSRP, SS-RSRP)
Supplementary uplink (Supplementary Uplink, SUL)
Time alignment (Timing Alignment or Time Advance, TA)
Transport Block (Transport Block, TB)
Time calibration timer (Timing Alignment Timer TAT)
Transmission configuration indication (Transmission Configuration Indicator, TCI)
Transmitting and receiving point (Transmission Reception Point, TRP)
Tracking reference signal (Tracking Reference Signal, TRS)
Technical specification (Technical Specification, TS)
Transmission (Tx)
Transport block size (Transport Block Size, TBS)
Transmitting and receiving points (Transmission and Reception Point, TRP)
Uplink control information (Uplink Control Information, UCI)
User Equipment (User Equipment, UE)
Uplink (UL)
User equipment specific search space (UE-specific Search Space, USS)
Virtual resource block (Virtual Resource Block, VRB)
The following disclosure contains specific information pertaining to exemplary embodiments in the present application. The drawings in the present application and their accompanying detailed description are directed to merely exemplary embodiments. However, the present application is not limited to such exemplary embodiments. Other variations and embodiments of the present application will occur to those skilled in the art. Unless otherwise indicated, identical or corresponding components in the figures may be indicated by identical or corresponding reference numerals. Moreover, the drawings and illustrations in the present application are not generally drawn to scale and are not intended to correspond to actual relative dimensions.
For consistency and ease of understanding, similar features are identified by reference indicators in the exemplary figures (although not shown in some embodiments). However, the features of the different embodiments may differ in other respects and therefore should not be narrowly limited to what is shown in the drawings.
The phrases "in one implementation" and "in some implementations" may each refer to one or more of the same or different implementations. The term "coupled" is defined as connected, whether directly or indirectly through intervening components, and is not necessarily limited to a physical connection. The term "comprising" may mean "including but not necessarily limited to" and specifically indicates an open inclusion or membership in a disclosed combination, group, series, and equivalent.
The term "and/or" is used herein merely to describe an association relationship of associated objects, meaning that there may be three relationships, e.g., a and/or B may represent: a is present alone, A and B are present simultaneously, and B is present alone. "A and/or B and/or C" may mean that at least one of A, B and C is present, A and B are present at the same time, A and C are present at the same time, B and C are present at the same time. At the same time A, B, C is present. Further, the character "/" used herein generally indicates that the front-rear association object is an or relationship.
The UE may be referred to AS PHY/MAC/RLC/PDCP/SDAP/RRC/AS/NAS layer/entity. The PHY/MAC/RLC/PDCP/SDAP/RRC/AS/NAS layer/entity may be referred to AS a UE.
NW may be a network node, TRP, cell (e.g., spCell, PCell, PSCell and/or SCell), eNB, gNB, and/or base station.
The serving cell: PCell, PSCell or SCell (secondary cell). The serving cell may be an active or a deactivated serving cell.
SpCell: for dual connectivity operation, the term "special cell" refers to the PCell of the MCG or the PSCell of the SCG, depending on whether the MAC entity is associated with the MCG or SCG. Otherwise, the term "special cell" refers to "PCell".
The terms "initiate," "trigger," "apply," "store," and "begin" may be used interchangeably in some embodiments of the present application.
The terms "terminate," "stop," "release," "suspend," "discard," "end," "complete," "suspend," and "cancel" may be used interchangeably in some embodiments of the present disclosure.
The terms "period," "process," "stage," and "duration" may be used interchangeably in some embodiments of the present application.
The terms "resource" and "occasion" may be used interchangeably in some implementations of the present application.
The terms "ongoing", "operating" and "pending" may be used interchangeably in some embodiments of the present application.
The terms "mechanism," "scheme," and "function" may be used interchangeably in some embodiments of the present application.
The terms "mapped to" and "associated with" are used interchangeably in some embodiments of the present application.
Furthermore, any two or more of the following paragraphs, (sub) terms, gist, action, behavior, terms, alternatives, examples, or claims in this application may be combined logically, reasonably, and appropriately to form a particular method. Any sentence, paragraph, (sub) item, gist, action, behavior, term, or claim in the present disclosure may be implemented independently and individually to form a specific method. Dependencies in this disclosure, such as "based on", "more specifically", "preferably", "in one embodiment", "in one implementation", "in one alternative", may refer to only one possible example that does not limit a particular method.
For non-limiting explanation, specific details are set forth, such as functional entities, techniques, protocols, standards, etc. in order to provide an understanding of the disclosed technology. In other instances, detailed disclosure of well-known methods, techniques, systems and structures have been omitted so as not to obscure the disclosure with unnecessary detail.
Those of skill in the art will immediately recognize that any of the network function(s) or algorithm(s) described in the present application can be implemented in hardware, software, or a combination of software and hardware. The described functions may correspond to modules, which may be software, hardware, firmware, or any combination thereof. The software implementation may include computer-executable instructions stored on a computer-readable medium such as a memory or other type of storage device. For example: one or more microprocessors or general purpose computers with communication processing capabilities may be programmed with corresponding executable instructions and perform the described network function(s) or algorithm(s). The microprocessor or general purpose computer may be comprised of an application specific integrated circuit (Applications Specific Integrated Circuitry, ASIC), a programmable logic array, and/or using one or more digital signal processors (Digital Signal Processor, DSP). While several exemplary embodiments described in this specification are directed to software installed and executed on computer hardware, alternative exemplary embodiments implemented as firmware or as hardware or a combination of hardware and software are also within the scope of the disclosure.
The computer-readable medium may include, but is not limited to, random access Memory (Random Access Memory, RAM), read Only Memory (ROM), erasable programmable Read Only Memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable programmable Read Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), flash Memory, compact disc Read Only Memory (Compact Disc Read-Only Memory, CD-ROM), magnetic cassettes, magnetic tape, magnetic disk storage devices, or any other equivalent medium capable of storing computer-readable instructions.
A Radio communication network architecture, such as a long term evolution (Long Term Evolution, LTE) system, an LTE-Advanced (LTE-a) system, an LTE-Advanced Pro system, or a New Radio (NR), typically includes at least one Base Station (BS), at least one UE, and one or more optional network elements that provide connectivity within the network. The UE communicates with a Network, such as a Core Network (CN), an evolved packet Core (Evolved Packet Core, EPC) Network, an evolved universal terrestrial radio access Network (Evolved Universal Terrestrial Radio Access Network, E-UTRAN), a Next-Generation Core (NGC), a 5G Core (5G Core,5 gc), or the internet, through a radio access Network (Radio Access Network, RAN) established by one or more BSs.
A UE according to the present application may include, but is not limited to, a mobile station, a mobile terminal or device, or a user communication radio terminal. The UE may be a portable radio, including but not limited to a mobile phone, tablet, wearable device, sensor or personal digital assistant (Personal Digital Assistant, PDA) with wireless communication capability. The UE may be configured to receive signals over an air interface and transmit signals to one or more cells in the RAN.
The BSs may include, but are not limited to, a Node B (NB) in a universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS), AN evolved Node B (eNB) in LTE-a, a radio network controller (Radio Network Controller, RNC) in UMTS, a base station controller (Base Station Controller, BSC) in a GSM enhanced data rate (GSM Enhanced Data rates for GSM Evolution EDGE) RAN (GSM Enhanced Data rates for GSM Evolution RAN, GERAN) of a global system for mobile communications (Global System for Mobile communications, GSM)/GSM evolved RAN, a next generation eNB (next-generation Node B, gNB) in a 5G-RAN (or in a 5G access network (5G Access Network,5G-AN)), AN evolved universal terrestrial radio access (Evolved Universal Terrestrial Radio Access, E-UTRA) BS, a next generation eNB (next-generation eNB) in a 5G-UTRA BS, and any other device capable of controlling radio communications and managing radio resources within a cell. The BS may connect to a network over a radio interface to serve one or more UEs.
The base station may be configured to provide communication services according to at least one of the following radio access technologies (Radio Access Technology, RAT): worldwide interoperability for microwave access (Worldwide Interoperability for Microwave Access, wiMAX), GSM (commonly referred to as 2G), GERAN, general packet radio service (General Packet Radio Service, GPRS), UMTS based on Wideband code division multiple access (Wideband-Code Division Multiple Access, W-CDMA) (commonly referred to as 3G), high-speed packet access (High-Speed Packet Access, HSPA), LTE-a, evolved LTE (eLTE), NR (commonly referred to as 5G), and/or LTE-a Pro. However, the scope of the present application is not limited to these protocols.
The BS is operable to provide radio coverage to a particular geographical area using a plurality of cells forming the RAN. The BS may support operation of the cell. Each cell is operable to provide service to at least one UE within its radio coverage area. More specifically, each cell (commonly referred to as a serving cell) may provide services to serve one or more UEs within its radio coverage area (e.g., each cell schedules Downlink (DL) resources and optionally Uplink (UL) resources to at least one UE within its radio coverage area for DL packet transmission and optionally UL packet transmission). The BS may communicate with one or more UEs in a radio communication system through a plurality of cells.
A cell may allocate Sidelink (SL) resources for supporting proximity services (Proximity Service, proSe), LTE SL services, and LTE/NR internet of vehicles (V2X) services. Each cell may have a coverage area that overlaps with other cells. In the case of Multi-RAT dual connectivity (Multi-RAT Dual Connectivity, MR-DC), the primary Cell of the primary Cell group (Master Cell Group, MCG) or secondary Cell group (Secondary Cell Group, SCG) may be referred to as a Special Cell (SpCell). A Primary Cell (PCell) may refer to the SpCell of an MCG. A Primary SCG Cell (PSCell) may refer to the SpCell of an SCG. MCG may refer to a set of serving cells associated with a Master Node (MN) including a SpCell and optionally one or more Secondary cells (scells). SCG may refer to a set of serving cells associated with a Secondary Node (SN), including a SpCell and optionally one or more scells.
As described above, the frame structure of the NR supports flexible configuration to accommodate various next generation (e.g., 5G) communication requirements, such as: enhanced mobile broadband (enhanced Mobile Broadband, emmbb), large-scale machine type communication (Massive Machine Type Communication, mctc), ultra-Reliable and Low-delay communication (URLLC), while meeting high reliability, high data rate and Low-delay requirements. As agreed in 3GPP, orthogonal frequency division multiplexing (Orthogonal Frequency Division Multiplexing, OFDM) techniques can be used as a baseline for NR waveforms. An extensible OFDM parameter set may also be used, such as: adaptive subcarrier spacing, channel bandwidth and Cyclic Prefix (CP). In addition, two coding schemes for NR are considered: (1) Low-Density Parity-Check (LDPC) and (2) polarization codes. Coding scheme adaptation may be configured based on channel conditions and/or service applications.
Furthermore, in the transmission time interval of a single NR frame, at least Downlink (DL) transmission data, guard-time segmentation and Uplink (UL) transmission data should be included, wherein the respective parts of DL transmission data, guard-time segmentation, UL transmission data should also be configurable, for example: NR based network dynamics. SL resources may also be provided through NR frames to support ProSe services or V2X services.
UE power in rrc_inactive/rrc_idle state
The UE may wake up in advance before a configured Paging Occasion (PO) and perform the following steps:
step 1: the UE sets the wake-up time before the PO based on the expected preparation time of the paging downlink control information (Downlink Control Information, DCI) and paging message decoding because the UE is unaware of the exact camping cell and the received signal quality of the physical downlink control channel (Physical Downlink Control Channel, PDCCH) and the physical downlink shared channel (Physical Downlink Shared Channel, PDSCH) after the UE transitions from deep sleep mode to wake-up time. During sleep mode, most of the UE components are turned off and the UE's local oscillator is in free running mode. During a preparation period prior to the PO, the UE adjusts all components of the front-end processor of the UE to prepare for data reception (e.g., warm-up time). The preparation period is used to meet everywhere requirements.
Step 2: timing acquisition from a Search Space (SS)/Physical Broadcast Channel (PBCH) block (SSB) and coarse synchronization-the UE may be out of synchronization with the network after sleep mode (e.g., out of synchronization after 160-320 milliseconds (ms)). The UE's local oscillator is in free running mode without the need to calibrate frequency stability from the Downlink (DL) received signal. The UE uses the timing reference generated by the local oscillator for cell search and timing acquisition. The UE may use the first detected SSB for initial timing acquisition and automatic gain control (Automatic Gain Control, AGC) tuning after sleep mode by peak detection of the primary synchronization signal (Primary Synchronization Signal, PSS)/secondary synchronization signal (Secondary Synchronization Signal, SSS).
Step 3: frequency and time tracking after coarse synchronization-after coarse synchronization, the UE starts a front-end algorithm (front-end algorism) for frequency and time offset estimation.
Step 4: calibration of local oscillator-reference timing clock from local oscillator requires calibration by received signal and fine adjustment of time and frequency offset to correct frequency drift of local oscillator to achieve 0.1 parts per million (ppm) frequency stability requirement. The UE needs to use an additional SSB with frequency and timing offset fine tuning to achieve calibration of the local oscillator.
Step 5: time and frequency offset compensation of the received signal.
Step 6: paging DCI is demodulated/decoded from PDCCH for paging indication.
Step 7: demodulates/decodes PDSCH and acquires paging information.
Step 8: if the paging message contains a UE ID, the UE performs subsequent processing, such as a contention-based physical random access channel (Physical Random Access Channel, PRACH). Otherwise, the UE returns to sleep mode.
Paging
To reduce power consumption in the rrc_idle/rrc_inactive state, the UE may apply a Discontinuous Reception (DRX) mechanism for paging (DCI) monitoring, which may mean that the UE may not need to continuously monitor the PDCCH in the rrc_idle/rrc_inactive state. Fig. 1 is a timing diagram illustrating a DRX mechanism for paging monitoring according to an embodiment of the present application. As shown in fig. 1, the UE may be configured with a DRX cycle and several parameters for deciding a PO. It should be noted that the UE may monitor only one PO per DRX cycle. In some cases (e.g., multi-beam operation, operation with shared spectrum channel access), the UE may monitor multiple PDCCH monitoring occasions in one PO. In addition, the PO may include a set of "S" consecutive PDCCH monitoring occasions, where "S" may be the number of SSBs actually transmitted, which is decided according to SSB-PositionInBurst configured in system information block 1 (SIB 1).
Paging allows the Network (NW) to communicate with the UE via paging messages (e.g., radio Resource Control (RRC) messages sent by PDSCH/PCCH) and to inform the UE of system information modification indications and/or earthquake and tsunami warning systems (Earthquake and Tsunami Warning System, ETWS)/commercial mobile warning systems (Commercial Mobile Alert System, CMAS) by short message indications (e.g., included in the short message field of DCI format 1_0). Fig. 2 is a timing diagram illustrating paging DCI, short message, and paging message according to an embodiment of the present application. As shown in fig. 2, the UE may monitor the PDCCH to receive Paging DCI (e.g., transmitted via DCI format 1_0 with a cyclic redundancy check (cyclic redundancy check, CRC) scrambled by a Paging radio network temporary identifier (Paging-Radio Network Temporary Identifier, P-RNTI). When the UE receives the paging DCI, the UE checks a short message indicator field in the paging DCI to determine whether a short message is included in the paging DCI and to determine whether scheduling information for the paging message is presented. The UE may also receive a paging message on the PDSCH based on the scheduling information indicated by the paging DCI if the short message indicator indicates scheduling information for the paging message (e.g., the bit field is "01" or "11"). When the UE in the rrc_idle/rrc_inactive state receives the paging message, the UE may perform the following actions:
When the UE receives the paging message, the UE may
1> if the UE is in rrc_idle state, for each pagerecord contained in the paging message:
2> if the UE-Identity included in the PagingRecord matches the UE Identity allocated by an upper layer (e.g., non-Access Stratum (NAS)):
3> the UE forwards UE-Identity and accessType (if present) to the upper layer of the UE;
1> if the UE is in rrc_inactive state, for each pagerecord contained in the paging message:
2> if the UE-Identity included in the PagingRecord matches the UE-stored fulll i-RNTI:
3> if the UE is configured by the upper layer to access identity 1:
4> the UE initiates an RRC connection recovery procedure by setting resumeCAuse to mps-PrioritityAccess;
3> otherwise if the UE is configured by the upper layer of the UE with access identity 2:
4> the UE initiates an RRC connection recovery procedure by setting resumeCAuse to mcs-PrioritiyAccess;
3> otherwise if the UE is configured by the upper layers of the UE to have one or more access identities equal to 11-15:
4> the ue initiates an RRC connection recovery procedure by setting resumecase to highpriorityiaccess;
3> otherwise:
4> UE initiates RRC connection recovery procedure by setting resumeCAuse as mt-Access;
2> otherwise if the UE-Identity contained in the pagengrecord matches the UE Identity assigned by the UE upper layer:
3> UE forwards UE-Identity to upper layer of UE and accessType (if present) to upper layer;
3> ue performs an operation based on 3gpp ts38.331 when entering the rrc_idle state with release cause "other".
System information (System Information, SI) and ETWS/CMAS
SI modification
System information modification/change (in addition to ETWS/CMAS) may occur at a particular radio frame (e.g., the concept of modification period may be used). The system information may be transmitted multiple times with the same content during a modification period. The modification period may be configured by the system information.
When the network changes/modifies the system information(s), the network first informs the UE of the modification (e.g., in a modification period). In the next modification period, the network transmits updated system information. Upon receiving the SI modification notification (e.g., by receiving the SI modification notification via a short message in paging DCI), the UE may attempt to acquire new system information from the beginning of the next modification period. The UE may apply the previously acquired system information until the UE acquires new system information.
Public early warning system
An NR connected to the 5GC can provide support for a public warning system (public warning system, PWS) through a system information broadcasting capability. The NR is responsible for scheduling and broadcasting the early warning message and paging the UE to provide an indication that the early warning message has been broadcast:
the ETWS is a public warning system aimed at meeting the regulatory requirements of warning notices related to earthquake and/or tsunami events. The ETWS alert notification may be a primary notification (e.g., a short notification) or a secondary notification.
CMAS is a common warning system that is intended to send a variety of warning notifications.
Different SIBs are defined for the ETWS primary notification, the ETWS secondary notification, and the CMAS notification. Paging (e.g., paging a short message in DCI) is used to inform the UE of the ETWS indication and CMAS indication. The UE monitors the ETWS/CMAS indication in the PO while the UE is in rrc_idle/rrc_inactive state. While the UE is in rrc_connected state, the UE monitors the ETWS/CMAS indication in any PO. Paging (e.g., paging a short message in DCI) indicating an ETWS/CMAS notification triggers acquisition of system information.
Modification period
The modification period boundary is defined by a system frame number (System Frame Number, SFN) value, where SFN mod m = 0, where m is the number of radio frames comprising the modification period.
The UE in rrc_idle/rrc_inactive state may monitor SI modification indications in the PO every DRX cycle. When a UE is provided with a common search space (e.g., including pagingSearchSpace, searchSpaceSIB1 and/or searchSpaceOtherSystemInformation) on an active bandwidth portion (BWP) to monitor paging, the UE in rrc_connected state may monitor SI modification indications in any PO at least once per modification period.
The ETWS/CMAS capable UE in rrc_idle/rrc_inactive state may monitor paging DCI (including short messages) per DRX cycle to indicate the ETWS/CMAS notification in the PO. When a UE is provided with a common search space (e.g., including pagingSearchSpace, searchSpaceSIB, and searchspaceothersystem information) on active BWP to monitor paging DCI, an ETWS/CMAS capable UE in rrc_connected state may monitor paging DCI (including short message) for indicating PWS notification in any PO at least once per defaultpaging cycle.
When the UE receives the short message (included in paging DCI), the UE may perform the following operations:
1> if the UE is ETWS-capable (ETWS-capable) or CMAS-capable (CMAS-capable), an etwsandcmassindindensaction bit of a Short Message (Short Message) is set and the UE is provided with the searchspace ib1 and searchspace information on active BWP or initial BWP:
2> ue immediately reacquires SIB1;
2> if the UE is ETWS capable and si-scheduling info includes scheduling information of SIB 6:
3> ue immediately acquires SIB6;
2> if the UE has the ETWS capability and the si-scheduling info includes scheduling information of SIB 7:
3> ue immediately acquires SIB7;
2> if the UE has CMAS capability and si-scheduling info includes scheduling information of SIB 8:
3> ue immediately acquires SIB8;
in the case where SIB6, SIB7, or SIB8 overlaps with the measurement gap, the UE may decide to acquire SIB6, SIB7, or SIB8 immediately.
1> if the systemInfoModification bit of the short message is set:
2> ue applies SI acquisition procedure from the beginning of the next modification period.
Tracking reference signal (TrackingReference Signal, TRS)/channel state information reference signal (Channel State Information ReferenceSignal, CSI-RS) in RRC_IDLE/RRC_INACTIVE state
For a UE operating in the rrc_idle/rrc_inactive state, the UE may consume power for various activities such as AGC, time/frequency synchronization, RRM measurements, paging monitoring, and the like. Fig. 3 is a timing diagram illustrating Cell-specific reference signals (Cell-specific Reference Signal, CRS) in a DRX cycle according to an embodiment of the present application. As shown in fig. 3, LTE supports always-on CRS in every subframe. Fig. 4 shows a timing diagram of SSB in a DRX cycle according to an embodiment of the present application. As shown in fig. 4, if SSB is transmitted with a longer period (e.g., 20 ms) than LTE CRS, NR supports SSB as shown in fig. 3. NR UEs need to wake up earlier, longer, more frequently for subsequent activities than LTE UEs. Therefore, the power consumption of the NR UE in the RRC_IDLE/RRC_INACTIVE state is much higher than that of the LTE UE in the RRC_IDLE state. As shown in the figure. Fig. 5 shows a timing diagram of TRS/CSI-RS in a DRX cycle according to an embodiment of the present application. As shown in fig. 5, TRS/CSI-RS opportunities are provided to a UE in an rrc_idle/rrc_inactive state for enhancing UE power saving capabilities.
It should be noted that the TRS/CSI-RS occasions provided to the UE in rrc_idle/rrc_inactive state are used to assist time/frequency tracking, potential RRM measurements and paging reception indications compared to SSB in order to reduce the total wake-up time.
The TRS/CSI-RS occasion for the UE in the rrc_connected state may be shared with the UE in the rrc_idle/rrc_inactive state.
In some embodiments, the gNB may potentially share TRS/CSI-RS opportunities with UEs in rrc_idle/rrc_inactive state (e.g., NW may decide whether to share).
In some embodiments, the TRS/CSI-RS in the TRS/CSI-RS occasion may or may not be transmitted.
In some embodiments, always-on TRS/CSI-RS transmission over the gNB may not be necessary.
In some embodiments, TRS/CSI-RS occasions corresponding to periodic TRSs may be supported.
The UE in rrc_idle/rrc_inactive state may use TRS/CSI-RS occasions to implement the following functions:
automatic Gain Control (AGC);
time/frequency tracking;
RRM measurement of the serving cell;
neighboring cell RRM measurements; and/or
Paging receiving indication.
Even when the UE in the rrc_connected state does not need the TRS/CSI-RS (e.g., when there is a UE in the rrc_connected state in the cell but the UE does not use the TRS/CSI-RS any more, or when there is no more UE in the rrc_connected state in the cell), the gNB may decide whether to transmit the TRS/CSI-RS to the UE in the rrc_idle/rrc_inactive state.
Configuration of TRS/CSI-RS occasions for UEs in rrc_idle/rrc_inactive state is provided by higher layer signaling.
In some embodiments, the higher layer signaling may be SIB, dedicated RRC, RRC release message, etc.
In some embodiments, the SIB may provide configuration of TRS/CSI-RS occasions for UEs in rrc_idle/rrc_inactive state.
The configuration of TRS/CSI-RS occasions for a UE in rrc_idle/rrc_inactive state may include at least:
-powerControlOffsetSS:{-3,0,3,6}dB；
-scramblingID 0 to 1023;
first OFDMSymbolInTimeDomain 0 to 9;
-first ofdm symbol inoltimedomain indicates a first symbol in a slot and a second symbol in the same slot can be implicitly derived, wherein the symbol index of the second symbol is first ofdm symbol inoltimedomain +4;
-startingRB 0 to 274;
-nrofRBs 24 to 276;
-periodicityAndOffset {10,20,40,80} ms; and
the frequency domain allocation frequencydomaimallocation of row1 has an applicable value from {0,1,2,3} to indicate the offset of the first RE in RB to RE # 0.
The subcarrier spacing (Subcarrier Spacing, SCS) configuration for TRS/CSI-RS occasions for UEs in rrc_idle/INACTIVE state may be:
alternative 1: the same as the initial BWP.
Alternative 2: parameters may be configured.
Multiple RS resources may be configured for a UE in rrc_idle/rrc_inactive state for TRS/CSI-RS occasions.
The configuration of the frequency position of the TRS/CSI-RS occasion for the UE in rrc_idle/rrc_inactive state may be:
alternative 1: within the initial DL BWP.
Alternative 2: is not limited by the initial BWP.
Quasi Co-Location (QCL) information of TRS/CSI-RS occasion for UE in rrc_idle/rrc_inactive state may be:
alternative 1: from higher layer configurations (e.g., qcl-infosperiodicsl-RS).
Alternative 2: QCL is assumed to be implicitly associated with the transmitted SSB (e.g., similar to PDCCH monitoring in the PO).
It should be noted that QCL information for TRS/CSI-RS occasions of UEs in rrc_idle/rrc_inactive state may be indicated by SSB indexes ranging from 0 to 63.
The SCS for the TRS/CSI-RS occasion of the UE in rrc_idle/rrc_inactive state may be the same as the SCS controlling the resource set (e.g., core # 0).
Paging DCI and short message
Paging DCI (P-RNTI scrambled DCI Format 1_0)
The following information is transmitted over DCI format 1_0 with P-RNTI scrambled CRC:
1. the short message indicator is a 2-bit field as shown in table 1 below. Table 1 shows the short message indicator.
2. Short message-8 bits according to 3gpp TS 38.331, clause 6.5. If the short message carries paging scheduling information, the bit field is reserved.
3. Frequency domain resource allocationBits. If the short message carries a frequency domain resource allocation, the bit domain is reserved. />Is the size of CORESET 0.
4. Time domain resource allocation-4 bits as defined in clause 5.1.2.1 of 3gpp TS 38.214. If the short message carries the time domain resource allocation, the bit domain is reserved.
Vrb to PRB map-1 bit. If the short message carries a VRB-to-PRB mapping, then the bit field is reserved.
6. Modulation and coding strategy-5 bits as defined in 3gpp TS 38.214, clause 5.1.3. If the short message is carried by adopting a modulation coding strategy, the bit field is reserved.
Tb scaling-2 bits defined in clause 5.1.3.2 of 3gpp TS 38.214. If the short message carries TB scaling, the bit field is reserved.
8. Reserved bits-8 bits for operation in a cell with shared spectrum channel access; otherwise 6 bits.
Table 1: short message indicator
| Bit field | Short message indicator |
| 00 | Reservation of |
| 01 | Scheduling information for paging only in DCI |
| 10 | Only short messages exist in DCI |
| 11 | Scheduling information for paging and short messages both exists in DCI |
Short message
The short message may be sent on the PDCCH by using the P-RNTI, whether or not there is an associated paging message using the short message field in DCI format 1_0.
Table 2 shows an 8-bit short message in which bit 1 is the most significant bit.
Table 2: short message
Early paging indicator (Paging Early Indication, PEI)
The PEI before the PO may indicate whether the UE needs to monitor the PDCCH addressed to the P-RNTI at the PO. With PEI, the UE can reduce unnecessary paging DCI and/or paging message reception.
In some embodiments, the PEI configuration may be configured for (and/or applied by) the UE when the UE is in the rrc_inactive/rrc_idle state. The UE may receive system information and/or RRC messages including PEI configuration. For example, the UE may be configured with a PEI configuration when/after receiving the PEI configuration.
In some embodiments, the PEI may be configured by system information (e.g., SIB1 or "other SI").
More specifically, PEI may be configured by a DownlinkConfigCommonSIB and/or a ServerCellConfigCommonSIB.
In some embodiments, PEI may be configured by RRC release message (no or no suspension configuration).
In some embodiments, PEI may be configured by RRC reconfiguration messages.
In some implementations, the PEI configuration may include a Search Space (SS). The UE may monitor the SS to receive PEI (e.g., when the UE is in rrc_inactive/rrc_idle state).
The SS of PEI may be a common search space configured in PDCCH-ConfigCommon, a type 1PDCCH Common Search Space (CSS) set configured by ra-SearchSpace, a type 3PDCCH CSS set, search space zero, a new common search space set configured by system information (e.g., SIB) or RRC release message, a search space with search space parameters configured in initial BWP, paging search space (paging search space), search space SIB1, etc.
In some implementations, the PEI may be transmitted by the NW to the UE via one or more of the following indications:
1. based on the indication of the DCI (e.g., based on the DCI format (e.g., DCI format 1_0, DCI format 2_6, etc.)).
2. Based on reference signals (RS-based) and/or sequence-based indications (e.g., TRS/CSI-RS and/or SSS-based).
In some embodiments, the PEI may indicate to the UE to perform one or more of the following actions:
in some embodiments, the PEI may instruct the UE to monitor the POs (e.g., if the group/subgroup of the UE is indicated by the PEI). For example, the UE may be required to monitor the PO when the UE detects the PEI of the PO at one or more PEI occasions. For another example, the UE may not be required to monitor the PO when the UE does not detect PEI on any or all PEI occasions of the PO.
In some embodiments, the PEI may indicate whether the UE should monitor the PO (e.g., via a bit (e.g., when the group/subgroup of the UE is indicated by the PEI)). For example, if the bit indicates a first value, the UE may be required to monitor the PO. In another example, if the bit indicates the second value, the UE may not be required to monitor the PO. Preferably, the UE may be required to monitor the PO when the UE does not detect PEI on any or all PEI occasions for the PO.
In some embodiments, the PEI may indicate one or more of the following information (but is not limited to):
UE sub-packet information (e.g., each PO may support one or more (e.g., 2, 4, 8) sub-groups);
TRS/CSI-RS availability (e.g., available/unavailable);
a system information modification indication; and/or
The ETWS/CMAS indication.
DCI-based PEI
Fig. 6 shows a timing diagram of DCI-based PEI according to one of the exemplary embodiments of the present application. As shown in fig. 6, PEI may be indicated by DCI for the UE to monitor PDCCH before PO. The decoding of DCI is coherent demodulation with polar decoding. The performance requirements for channel compensation of DCI based PEI may be the same as the performance requirements for DCI format 1_0 decoding of paging DCI. For PEI, SSB and/or TRS/CSI-RS may be measured by the UE in combination to perform channel tracking and local oscillator calibration (e.g., prior to monitoring the PEI). The DCI-based PEI may indicate whether the UE monitors/decodes paging DCI in a subsequent PO. When the UE detects/receives DCI-based PEI, the UE may be instructed to wake up to monitor the PDCCH at the next PO (and/or receive paging messages on the scheduled PDSCH). Otherwise, the UE may continue to sleep after receiving the DCI-based PEI (and may not monitor the next PO).
Sequence-based PEI
The sequence-based PEI may be indicated by some RS types, such as SSS and/or TRS/CSI-RS. The detection of the sequence-based PEI may be incoherent peak detection (e.g., similar to PSS/SSS detection) based on correlation with the received signal. Fig. 7 shows a timing diagram of a sequence-based PEI according to embodiments of the present application. In fig. 7, the sequence-based paging indication may not be used for PEI via incoherent detection, but may be used as a reference signal for channel tracking. The sequence-based PEI may be combined with SSB to indicate whether the UE monitors/decodes paging DCI in subsequent POs. When the UE detects the sequence-based PEI, the UE may wake up to monitor/decode the paging DCI at the next PO (and/or receive paging messages on the scheduled PDSCH). Otherwise, the UE may continue to sleep after receiving the sequence-based PEI (and may not monitor the next PO). Furthermore, one SSB burst set along with sequence-based PEI can be used for AGC, frequency/time tracking and compensation to support RRM measurements and channel tracking.
The UE may be referred to AS a Physical Layer (PHY), medium Access control (Medium Access Control, MAC), radio link control (Radio Link Control, RLC), packet data convergence protocol (Packet Data Convergence Protocol, PDCP), service data adaptation protocol (Service Data Adaptation Protocol, SDAP), radio resource control (Radio Resource Control, RRC), access Stratum (AS), or Non-Access Stratum (NAS) Layer/entity. The PHY/MAC/RLC/PDCP/SDAP/RRC/AS/NAS layer/entity may be referred to AS a UE.
The Network (NW) may be a network node, a Transmission/Reception Point (TRP), a Cell (e.g., a Special Cell, spCell, primary Cell, PCell), primary SCell, and/or Secondary Cell), eNB, gNB, and/or base station.
The serving cell: PCell, PSCell, or SCell. The serving cell may be an activated serving cell or a deactivated serving cell.
SpCell: for dual connectivity operation, the term "special cell" refers to the PCell of the primary cell group (Master Cell Group, MCG) or the PSCell of the secondary cell group (Secondary Cell Group, SCG), depending on whether the MAC entity is associated with the MCG or SCG, respectively. Otherwise, the term "special cell" refers to "PCell".
TRS/CSI-RS availability indication
For TRS/CSI-RS occasions configured to UEs in rrc_idle/rrc_inactive state, NW may be based on explicit indication. Thus, the UE may not perform blind detection for the presence/absence of TRS/CSI-RS (e.g., TRS resource sets). In other words, when the NW does not indicate that the TRS/CSI-RS is available (or indicates that the TRS/CSI-RS is not available), the UE may decide that the TRS/CSI-RS is not present.
In some embodiments, a UE in rrc_idle/rrc_inactive state may receive layer 1 (L1) (L1-based) based signaling (e.g., paging DCI or PEI) for TRS/CSI-RS availability indication.
In some embodiments, the UE may monitor paging DCI on the PO in each paging cycle. When the UE detects/receives paging DCI on the PO, the UE may decide whether the paging DCI includes a TRS/CSI-RS availability indication. If the paging DCI includes a TRS/CSI-RS availability indication, the UE may decide whether a TRS/CSI-RS on the configured TRS/CSI-RS occasion is available/valid based on the TRS/CSI-RS availability indication.
More specifically, the paging DCI may be DCI format 1_0 scrambled by the P-RNTI.
More specifically, the TRS/CSI-RS availability indication may be indicated by paging DCI.
More specifically, the TRS/CSI-RS availability indication may be indicated in a short message indicator of paging DCI.
More specifically, the TRS/CSI-RS availability indication may be indicated in a short message paging DCI.
In some embodiments, the UE may monitor the PEI before the PO when configuring the PEI. When the UE detects/receives PEI, the UE may decide whether the PEI includes a TRS/CSI-RS availability indication. If the PEI includes a TRS/CSI-RS availability indication, the UE may decide whether a TRS/CSI-RS on the configured TRS/CSI-RS occasion is available/valid based on the TRS/CSI-RS availability indication.
More specifically, the PEI may be DCI-based PEI or sequence-based PEI.
In some embodiments, a UE in rrc_idle/rrc_inactive state may receive SI-based signaling for TRS/CSI-RS availability indication.
In some embodiments, the UE may receive SI (e.g., by applying an SI acquisition procedure). When the UE receives the SI, the UE may decide whether the SI includes a TRS/CSI-RS availability indication. If the SI includes a TRS/CSI-RS availability indication, the UE may decide whether a TRS/CSI-RS on the configured TRS/CSI-RS occasion is available/valid based on the TRS/CSI-RS availability indication.
More specifically, the SI may be a minimum SI (e.g., MIB, SIB 1) and/or other SI (e.g., SIB2, SIB3, SIB4, SIB5, SIB6, SIB7, SIB8, SIB9, SIB10, SIB11, etc.).
More specifically, the UE may receive SI on a broadcast control channel (Broadcast Control Channel, BCCH) and/or a DL-shared channel (DL-SCH).
For information provided in a TRS/CSI-RS availability indication (e.g., indicated by paging DCI, PEI, and/or SI) of configured TRS/CSI-RS occasions, availability/unavailability information (e.g., a TRS configuration including/indicating at least one TRS resource set) of configured TRS/CSI-RS resources may be indicated via a bitmap or a code point.
In some embodiments, the bitmap may indicate an available/unavailable status of one or more sets of configured TRS/CSI-RS resources. Each bit of the bit map may be associated with at least one TRS/CSI-RS resource in the set of TRS/CSI-RS resources.
In some embodiments, the code point/index may indicate the available/unavailable status of all or some of the configured TRS/CSI-RS resources. An index may be associated with one or more TRS/CSI-RS resources or one or more sets of TRS/CSI-RS resources.
TRS/CSI-RS availability indication using SI and L1 based
It should be noted that the TRS/CSI-RS available/unavailable status may be indicated by L1-based signaling (e.g., paging DCI, PEI) or SI-based signaling. More specifically, the NW may configure/indicate information/configuration to let the UE know that the UE may receive TRS/CSI-RS availability information via L1 based signaling (e.g., paging DCI, PEI) or SI based signaling. The TRS/CSI-RS availability information may be referred to as an L1 based availability indication.
In some implementations, the NW may not use both L1-based signaling and SI-based signaling to indicate whether TRS/CSI-RS is available/valid on the configured TRS/CSI-RS occasion. For example, when the NW configures/indicates SI-based signaling for TRS/CSI-RS availability information, the NW may not configure/indicate L1-based signaling for TRS/CSI-RS availability information. For another example, when the NW configures/indicates L1-based signaling for TRS/CSI-RS availability information, the NW may not configure/indicate SI-based signaling for TRS/CSI-RS availability information.
In some embodiments, the UE may not desire to receive the TRS/CSI-RS availability information in the L1-based signaling when the UE is configured with SI-based signaling for the TRS/CSI-RS availability information or if the received SI includes the TRS/CSI-RS availability information.
In some embodiments, the UE may expect to receive the TRS/CSI-RS availability information in the L1-based signaling (e.g., if the UE is configured with a TRS/CSI-RS function) if the TRS/CSI-RS availability information is not included in the SI-based signaling or if the TRS/CSI-RS availability information is not in the SI-based signaling.
In some embodiments, the UE may expect to receive the TRS/CSI-RS availability information if the TRS/CSI-RS availability information is not included in the L1-based signaling or if the TRS/CSI-RS availability information is not included in the L1-based signaling. CSI-RS availability information in SI-based signaling (e.g., if the UE is configured with TRS/CSI-RS functionality).
In some implementations, the NW can use both L1-based signaling and SI-based signaling for the TRS/CSI-RS availability information to indicate whether the TRS/CSI-RS is available/valid on the configured TRS/CSI-RS occasion. For example, the NW may indicate the available/unavailable status of the TRS/CSI-RS using both an SI-based TRS/CSI-RS availability indication and an L1-based TRS/CSI-RS availability indication.
Thus, the UE may decide whether the TRS/CSI-RS is available/valid based on both L1-based signaling (e.g., paging DCI, PEI) and SI-based signaling. In some embodiments, the SI-based TRS/CSI-RS availability indication and the L1-based TRS/CSI-RS availability indication may indicate different information (e.g., different sets of TRS/CSI-RS resources, different availability/unavailability status for TRS/CSI-RS, different validity times, etc.).
Content of SI-based and L1-based TRS/CSI-RS availability indication
In some implementations, the SI-based and L1-based TRS/CSI-RS availability indications may include the same information for the TRS/CSI-RS (e.g., the same set/group/index of TRS/CSI-RS resources).
In some embodiments, if the SI-based TRS/CSI-RS availability indication indicates (a set/group/index of) the first TRS/CSI-RS resource and (a set/group/index of) the second TRS/CSI-RS resource, the L1-based TRS/CSI-RS availability indication may indicate (a set/group/index of) the first TRS/CSI-RS resource and (a set/group/index of) the second TRS/CSI-RS resource. In other words, the L1-based TRS/CSI-RS availability indication may not indicate (the set/group/index of) the third TRS/CSI-RS resource.
In some implementations, the SI-based and L1-based TRS/CSI-RS availability indications may include different information for the TRS/CSI-RS (e.g., different sets/groups/indexes of TRS/CSI-RS resources).
In some embodiments, if the SI-based TRS/CSI-RS availability indication indicates (a set/group/index of) the first TRS/CSI-RS resource and (a set/group/index of) the second TRS/CSI-RS resource, the L1-based TRS/CSI-RS availability indication may not indicate (a set/group/index of) the first TRS/CSI-RS resource and (a set/group/index of) the second TRS/CSI-RS resource.
In some embodiments, if the SI-based TRS/CSI-RS availability indication includes a (set/group/index) of TRS/CSI-RS resources, then L1-based (set/group/index) of TRS/CSI-RS resources may be indicated, which is not indicated by the SI-based TRS/CSI-RS availability indication.
In some implementations, the SI-based and L1-based TRS/CSI-RS availability indications may include the same format/field for the TRS/CSI-RS or different formats/fields for the TRS/CSI-RS.
In some embodiments, the number/fields of TRS/CSI-RS resources (sets/groups/indexes) indicated by the SI-based and L1-based TRS/CSI-RS availability indications may be the same. Preferably, the bits used for the field indicating (the set/group/index of) the TRS/CSI-RS resource may be identical.
In some embodiments, if the SI-based TRS/CSI-RS availability indication is applied with a bitmap to indicate a TRS/CSI-RS availability status/unavailability status, an L1-based TRS/CSI-RS availability indication may also be applied with a bitmap to indicate a TRS/CSI-RS availability status/unavailability status. Preferably, if the SI-based TRS/CSI-RS availability indication is applied together with a code point/index to indicate a TRS/CSI-RS availability status/unavailability status, the L1-based TRS/CSI-RS availability indication may also be applied with a code point/index to indicate a TRS/CSI-RS availability status/unavailability status.
In some implementations, the SI-based and L1-based TRS/CSI-RS availability indications may include different formats/fields for the TRS/CSI-RS.
In some embodiments, the number/fields of TRS/CSI-RS resources (sets/groups/indexes) indicated by the SI-based and L1-based TRS/CSI-RS availability indications may be different. Preferably, the bits used for the field indicating (the set/group/index of) the TRS/CSI-RS resource may be different.
In some embodiments, if the SI-based TRS/CSI-RS availability indication is applied with the bitmap to indicate an available/unavailable status of the TRS/CSI-RS, the L1-based TRS/CSI-RS availability indication may be applied with the code point/index to indicate an available/unavailable status of the TRS/CSI-RS. Preferably, if the SI-based TRS/CSI-RS availability indication is applied together with the code point/index to indicate the available status/unavailable status of the TRS/CSI-RS, the L1-based TRS/CSI-RS availability indication may be applied together with the bitmap to indicate the available status/unavailable status of the TRS/CSI-RS.
TRS/CSI-RS availability indication function based on SI and L1
In some embodiments, an SI-based TRS/CSI-RS availability indication may be used to configure which TRS/CSI-RS resource (set/group/index) indicates the availability status/unavailability status of the TRS/CSI-RS by an L1-based TRS/CSI-RS availability indication.
In some embodiments, the SI-based TRS/CSI-RS availability indication may configure (the set/group/index of) the first TRS/CSI-RS resource and (the set/group/index of) the second TRS/CSI-RS resource. The L1-based TRS/CSI-RS availability indication may indicate an availability status/unavailability status of TRS/CSI-RS for the first TRS/CSI-RS resource (set/group/index) and the second TRS/CSI-RS resource (set/group/index).
In some embodiments, the L1-based TRS/CSI-RS availability indication may indicate an availability status/unavailability status of TRS/CSI-RS for (a set/group/index of) one, more, a subset, or all of the TRS/CSI-RS resources. Wherein one, more, a subset or all (sets/groups/indexes) of TRS/CSI-RS resources are configured by SI-based TRS/CSI-RS availability indication.
In some embodiments, the SI-based TRS/CSI-RS availability indication may be used to indicate a default/initial state of availability/unavailability of the TRS/CSI-RS for (sets/groups/indexes of) TRS/CSI-RS resources.
In some embodiments, the SI-based TRS/CSI-RS availability indication may indicate a default/initial state of availability/unavailability of the TRS/CSI-RS for (a set/group/index of) TRS/CSI-RS resources. Thus, the L1-based TRS/CSI-RS availability indication may be used to change/switch the available/unavailable status of the TRS/CSI-RS for (sets/groups/indexes of) TRS/CSI-RS resources.
In some embodiments, when the UE is in rrc_idle/rrc_inactive state, the UE may decide (set/group) the availability status/unavailability status of the TRS/CSI-RS based on the SI-based TRS/CSI-RS availability indication before receiving the L1-based TRS/CSI-RS availability indication. When the UE is receiving the L1-based TRS/CSI-RS availability indication, the UE may follow the indication of the L1-based TRS/CSI-RS availability indication. Preferably, the UE may ignore the SI-based TRS/CSI-RS availability indication after receiving the L1-based TRS/CSI-RS availability indication.
In some embodiments, when the UE is in rrc_idle/rrc_inactive state, the UE may ignore the L1-based TRS/CSI-RS availability indication if the UE has not received the SI-based TRS/CSI-RS availability indication.
In some embodiments, the default/initial state of the TRS/CSI-RS indicated in the SI-based TRS/CSI-RS availability indication may be available/valid.
In some embodiments, the default/initial state of the TRS/CSI-RS indicated in the SI-based TRS/CSI-RS availability indication may be unavailable/invalid.
In some implementations, an SI-based TRS/CSI-RS availability indication may be used to indicate that all configured TRS/CSI-RS are available/unavailable at the same time (e.g., by a bit).
In some embodiments, if the SI-based TRS/CSI-RS availability indication indicates a first value (e.g., 1), the UE may decide that all configured TRS/CSI-RS are available.
In some embodiments, if the SI-based TRS/CSI-RS availability indication indicates a second value (e.g., 0), the UE may decide that all configured TRS/CSI-RS are not available.
In some implementations, an L1-based TRS/CSI-RS availability indication may be used to indicate that all configured TRS/CSI-RS are available/unavailable at the same time (e.g., by a bit).
In some embodiments, if the L1-based TRS/CSI-RS availability indication indicates a first value (e.g., 1), the UE may decide that all configured TRS/CSI-RS are available.
In some embodiments, if the L1-based TRS/CSI-RS availability indication indicates a second value (e.g., 0), the UE may decide that all configured TRS/CSI-RS are not available.
Priority of SI-based and L1-based TRS/CSI-RS availability indication
In some embodiments, the UE may decide whether the TRS/CSI-RS on the configured TRS/CSI-RS occasion is available/valid based on the newly received signaling indicating the available/unavailable status of the TRS/CSI-RS.
In some embodiments, when the UE receives the SI-based TRS/CSI-RS availability indication and the UE receives the L1-based TRS/CSI-RS availability indication after the SI-based TRS/CSI-RS availability indication, the UE may decide whether the TRS/CSI-RS on the configured TRS/CSI-RS occasion is available/valid according to the L1-based TRS/CSI-RS availability indication.
In some embodiments, when the UE receives the L1-based TRS/CSI-RS availability indication and the UE receives the SI-based TRS/CSI-RS availability indication after the L1-based TRS/CSI-RS availability indication, the UE may decide whether the TRS/CSI-RS on the configured TRS/CSI-RS occasion is available/valid according to the SI-based TRS/CSI-RS availability indication.
In some embodiments, the priority of the SI-based TRS/CSI-RS availability indication may be higher than the priority of the L1-based TRS/CSI-RS availability indication.
In some embodiments, when the UE receives the SI-based TRS/CSI-RS availability indication and the L1-based TRS/CSI-RS availability indication, the UE may decide whether the TRS/CSI-RS on the configured TRS/CSI-RS occasion is available/valid according to the SI-based TRS/CSI-RS availability indication.
In some embodiments, when the UE receives the SI-based TRS/CSI-RS availability indication and the L1-based TRS/CSI-RS availability indication, the UE may ignore the L1-based TRS/CSI-RS availability indication.
In some embodiments, when the UE receives the SI-based TRS/CSI-RS availability indication, the indication indicates that the first TRS/CSI-RS on the configured TRS/CSI-RS occasion is unavailable/invalid, but the L1-based TRS/CSI-RS availability indication indicates that the first TRS/CSI-RS on the configured TRS/CSI-RS occasion is available/valid, the UE may decide that the first TRS/CSI-RS on the configured TRS/CSI-RS occasion is unavailable/invalid.
In some embodiments, the priority of the L1-based TRS/CSI-RS availability indication may be higher than the SI-based TRS/CSI-RS availability indication.
In some embodiments, when the UE receives the SI-based TRS/CSI-RS availability indication and the L1-based TRS/CSI-RS availability indication, the UE may decide whether the TRS/CSI-RS on the configured TRS/CSI-RS occasion is available/valid according to the SI-based TRS/CSI-RS availability indication.
In some embodiments, when the UE receives the SI-based TRS/CSI-RS availability indication and the L1-based TRS/CSI-RS availability indication, the UE may ignore the SI-based TRS/CSI-RS availability indication.
In some embodiments, when the UE receives an L1-based TRS/CSI-RS availability indication indicating that the first TRS/CSI-RS on the configured TRS/CSI-RS occasion is unavailable/invalid, but the SI-based TRS/CSI-RS availability indication indicates that the first TRS/CSI-RS on the configured TRS/CSI-RS occasion is available/valid, the UE may decide that the first TRS/CSI-RS on the configured TRS/CSI-RS occasion is unavailable/invalid.
SI-based and L1-based restriction of TRS/CSI-RS availability indication
In some embodiments, the SI-based TRS/CSI-RS availability indication may be used to indicate whether a TRS/CSI-RS on the configured TRS/CSI-RS occasion is available/valid, while the L1-based TRS/CSI-RS availability indication may be used to indicate whether a TRS/CSI-RS on the configured TRS/CSI-RS occasion is unavailable/invalid.
In some embodiments, an L1-based TRS/CSI-RS availability indication may be used to indicate whether a TRS/CSI-RS on a configured TRS/CSI-RS occasion is available/valid, while an SI-based TRS/CSI-RS availability indication may be used to indicate whether a TRS/CSI-RS on a configured TRS/CSI-RS occasion is unavailable/invalid.
In some embodiments, if the SI-based TRS/CSI-RS availability indication indicates that the TRS/CSI-RS on the configured TRS/CSI-RS occasion is available/valid, the L1-based TRS/CSI-RS availability indication may not indicate that the TRS/CSI-RS on the configured TRS/CSI-RS occasion is unavailable/invalid. Preferably, if the L1-based TRS/CSI-RS availability indication indicates that the TRS/CSI-RS on the configured TRS/CSI-RS occasion is not available/invalid, the UE may ignore the L1-based TRS/CSI-RS availability indication.
In some embodiments, if the SI-based TRS/CSI-RS availability indication indicates that the TRS/CSI-RS on the configured TRS/CSI-RS occasion is unavailable/inactive, the L1-based TRS/CSI-RS availability indication may not indicate that the TRS/CSI-RS on the configured TRS/CSI-RS occasion is available/active. Preferably, if the L1-based TRS/CSI-RS availability indication indicates TRS/CSI-RS availability/valid on the configured TRS/CSI-RS occasion, the UE may ignore the L1-based TRS/CSI-RS availability indication.
In some embodiments, if the L1-based TRS/CSI-RS availability indication indicates that the TRS/CSI-RS on the configured TRS/CSI-RS occasion is available/valid, the SI-based TRS/CSI-RS availability indication may not indicate that the TRS/CSI-RS on the configured TRS/CSI-RS occasion is unavailable/invalid. Preferably, if the SI-based TRS/CSI-RS availability indication indicates that the TRS/CSI-RS on the configured TRS/CSI-RS occasion is not available/invalid, the UE may ignore the SI-based TRS/CSI-RS availability indication.
In some embodiments, if the L1-based TRS/CSI-RS availability indication indicates that the TRS/CSI-RS on the configured TRS/CSI-RS occasion is unavailable/inactive, the SI-based TRS/CSI-RS availability indication may not indicate that the TRS/CSI-RS on the configured TRS/CSI-RS occasion is available/active. Preferably, if the SI-based TRS/CSI-RS availability indication indicates that the TRS/CSI-RS is available/valid on the configured TRS/CSI-RS occasion, the UE may ignore the SI-based TRS/CSI-RS availability indication.
In some embodiments, if the TRS/CSI-RS on the configured TRS/CSI-RS occasion is indicated as available/valid, the L1-based TRS/CSI-RS availability indication may indicate a status of the TRS/CSI-RS on the configured TRS/CSI-RS occasion.
In some implementations, if the TRS/CSI-RS on the configured TRS/CSI-RS is indicated as unavailable/invalid, the L1-based TRS/CSI-RS availability indication may indicate a status of the TRS/CSI-RS on the configured TRS/CSI-RS occasion.
TRS/CSI-RS active time
The TRS/CSI-RS validity time is the duration for which the UE decides that the TRS/CSI-RS availability indication is valid. If the TRS/CSI-RS availability indication is received within the TRS/CSI-RS validity time, the UE may not reacquire other TRS/CSI-RS availability indications within the same TRS/CSI-RS validity time.
In some embodiments, the UE may not receive/acquire SIBs for SI-based TRS/CSI-RS availability indication for the TRS/CSI-RS validity time.
In some embodiments, the UE may ignore the TRS/CSI-RS availability/unavailability information included in the SI-based TRS/CSI-RS availability indication for the TRS/CSI-RS validity time (e.g., if the UE receives the SI-based TRS/CSI-RS availability indication).
In some embodiments, the UE may ignore TRS/CSI-RS availability/unavailability information included in the L1-based TRS/CSI-RS availability indication in the TRS/CSI-RS validity time (e.g., if the UE receives the SI-based TRS/CSI-RS availability indication).
In some embodiments, when SI is used for the TRS/CSI-RS availability indication, SI may indicate TRS/CSI-RS available/unavailable. Preferably, the TRS/CSI-RS active time may begin when the UE receives SI (which indicates TRS/CSI-RS availability indication).
In some embodiments, the TRS/CSI-RS validity time may be a duration between a first SI (which indicates a TRS/CSI-RS availability indication) and a second SI.
More specifically, the second SI may be the next SI after the first SI (which indicates the TRS/CSI-RS availability indication).
More specifically, the second SI may be one or more SIs after the first SI (indicating TRS/CSI-RS availability indication).
More specifically, the duration between the first SI (indicating TRS/CSI-RS availability indication) and the second SI may be configured by the Periodicity of the SI (e.g., SI-Periodicity).
In some embodiments, the TRS/CSI-RS validity time may be a duration between SI (indicating TRS/CSI-RS availability indication) and PO.
More specifically, the PO may be the next PO after SI (indicating TRS/CSI-RS availability indication).
More specifically, the POs may be one or more POs after SI (indicating TRS/CSI-RS availability indication).
More specifically, the TRS/CSI-RS active time may end at the first symbol, slot, subframe, SFN, or PDCCH monitoring occasion of the PO.
More specifically, the TRS/CSI-RS active time may end at the last symbol, slot, subframe, SFN, or PDCCH monitoring occasion of the PO.
In some embodiments, the TRS/CSI-RS validity time may be the duration between SI (indicating TRS/CSI-RS availability indication) and PEI monitoring occasions.
More specifically, the PEI monitoring occasion may be the next PEI monitoring occasion after SI (which indicates TRS/CSI-RS availability indication).
More specifically, the PEI monitoring occasions may be one or more PEI monitoring occasions after SI (which indicates TRS/CSI-RS availability indication).
More specifically, the TRS/CSI-RS active time may end at the first symbol, slot, subframe, SFN, or PDCCH monitoring of the PEI monitoring occasion.
More specifically, the TRS/CSI-RS active time may end at the last symbol, slot, subframe, SFN, or PDCCH monitoring occasion of the PEI monitoring occasion.
In some embodiments, when paging DCI is used for the TRS/CSI-RS availability indication, the paging DCI may indicate that the TRS/CSI-RS is available/unavailable. Preferably, the TRS/CSI-RS validity time may start when the UE receives paging DCI (which indicates a TRS/CSI-RS availability indication).
In some embodiments, the TRS/CSI-RS validity time may be a duration between a first paging DCI (which indicates a TRS/CSI-RS availability indication) and a second paging DCI.
More specifically, the second paging DCI may be a next received paging DCI after the first paging DCI (which indicates a TRS/CSI-RS availability indication).
More specifically, the second paging DCI may be one or more paging DCIs received after the first paging DCI (which indicates a TRS/CSI-RS availability indication).
More specifically, the duration between the first paging DCI (which indicates the TRS/CSI-RS availability indication) and the second paging DCI may be configured by a DRX cycle.
In some embodiments, the TRS/CSI-RS validity time may be a duration between paging DCI (which indicates a TRS/CSI-RS availability indication) and the PO.
More specifically, the PO may be the next PO after paging DCI (which indicates TRS/CSI-RS availability indication).
More specifically, the POs may be one or more POs following paging DCI (which indicates a TRS/CSI-RS availability indication).
More specifically, the TRS/CSI-RS active time may end at the first symbol, slot, subframe, SFN, or PDCCH monitoring occasion of the PO.
More specifically, the TRS/CSI-RS active time may end at the last symbol, slot, subframe, SFN, or PDCCH monitoring occasion of the PO.
In some embodiments, the TRS/CSI-RS validity time may be a duration between paging DCI (which indicates a TRS/CSI-RS availability indication) and a PEI monitoring occasion.
More specifically, the PEI monitoring occasion may be the next PEI monitoring occasion after paging DCI (which indicates TRS/CSI-RS availability indication).
More specifically, the PEI monitoring occasions may be one or more PEI monitoring occasions after paging DCI (which indicates TRS/CSI-RS availability indication).
More specifically, the TRS/CSI-RS active time may end at the first symbol, slot, subframe, SFN, or PDCCH monitoring occasion of the PEI monitoring occasion.
More specifically, the TRS/CSI-RS active time may end at the last symbol, slot, subframe, SFN, or PDCCH monitoring occasion of the PEI monitoring occasion.
Fig. 8 is a timing diagram illustrating TRS/CSI-RS active times for paging DCI according to one embodiment of the present application. In the embodiment shown in fig. 8, the validity time may be the duration between paging DCI and the (subsequent) PO.
In some embodiments, when PEI is used for the TRS/CSI-RS availability indication, PEI may indicate TRS/CSI-RS available/unavailable. Preferably, the TRS/CSI-RS active time may begin when the UE receives PEI (which indicates a TRS/CSI-RS availability indication).
In some embodiments, the TRS/CSI-RS validity time may be a duration between the first PEI (which indicates the TRS/CSI-RS availability indication) and the second PEI.
More specifically, the second PEI may be the next received PEI after the first PEI (which indicates the TRS/CSI-RS availability indication).
More specifically, the second PEI may be one or more PEIs received after the first PEI (which indicates a TRS/CSI-RS availability indication).
More specifically, the duration between the first PEI (which indicates the TRS/CSI-RS availability indication) and the second PEI may be configured by the DRX cycle and/or cycles used for the PEI (e.g., configured in the PEI configuration).
In some embodiments, the TRS/CSI-RS validity time may be the duration between PEI (indicating TRS/CSI-RS availability indication) and PO.
More specifically, the PO may be the next PO after PEI (indicating TRS/CSI-RS availability indication).
More specifically, the PO may be one or more POs after PEI (indicating TRS/CSI-RS availability indication).
More specifically, the TRS/CSI-RS active time may end at the first symbol, slot, subframe, SFN, or PDCCH monitoring occasion of the PO.
More specifically, the TRS/CSI-RS active time may end at the last symbol, slot, subframe, SFN, or PDCCH monitoring occasion of the PO.
In some embodiments, the TRS/CSI-RS validity time may be the duration between PEI (indicating TRS/CSI-RS availability indication) and PEI monitoring occasion.
More specifically, the PEI monitoring occasion may be the next PEI monitoring occasion after the PEI (which indicates the TRS/CSI-RS availability indication).
More specifically, the PEI monitoring occasions may be one or more PEI monitoring occasions after PEI (indicating TRS/CSI-RS availability indication).
More specifically, the TRS/CSI-RS active time may end at the first symbol, slot, subframe, SFN, or PDCCH monitoring occasion of the PEI monitoring occasion.
More specifically, the TRS/CSI-RS active time may end at the last symbol, slot, subframe, SFN, or PDCCH monitoring occasion of the PEI monitoring occasion.
Fig. 9 shows a timing diagram of TRS/CSI-RS active times of PEI according to one of the embodiments of the present application. In the embodiment shown in fig. 9. The TRS/CSI-RS active time may be the duration between PEI and the (subsequent) PO.
Timer/window based
In some implementations, the timer/window may be configured for TRS/CSI-RS validity indication. The UE may decide whether the status of the TRS/CSI-RS indicated in the TRS/CSI-RS availability indication is valid based on the timer/window. Preferably, the timer/window unit may be a symbol, a slot, a subframe, an SFN, ms, seconds, a DRX cycle number, a PO number, a Paging Frame (PF) number, a PDCCH monitoring occasion number, etc.
In some embodiments, the UE may decide that the state of the TRS/CSI-RS indicated in the TRS/CSI-RS availability indication is valid when the timer/window is running.
Preferably, the UE may decide whether the TRS/CSI-RS is available/valid based on the TRS/CSI-RS availability indication when the timer/window is running.
Preferably, when the timer/window is running, the UE may decide whether the TRS/CSI-RS is available/valid according to an L1-based TRS/CSI-RS availability indication or an SI-based TRS/CSI-RS availability indication.
In some embodiments, when the timer/window is not running (or expired), the UE may decide that the state of the TRS/CSI-RS indicated in the TRS/CSI-RS availability indication is invalid.
Preferably, when the timer/window is not running (or expired), the UE may not decide whether the TRS/CSI-RS is available/valid based on the TRS/CSI-RS availability indication.
Preferably, when the timer/window is not running (or expired), the UE may decide whether the TRS/CSI-RS is available/valid according to the SI-based TRS/CSI-RS availability indication, and may decide whether the TRS/CSI-RS is available/valid not according to the L1-based TRS/CSI-RS availability indication.
Preferably, when the timer/window is not running (or expired), the UE may decide that (all) TRS/CSI-RS is not available/valid.
In some embodiments, the timer/window configured for the TRS/CSI-RS validity indication may be configured to infinity. If the timer/window is configured to infinity, the UE may decide that the state of the TRS/CSI-RS indicated in the TRS/CSI-RS availability indication is always valid.
In some implementations, the timer/window may be used/configured for SI-based TRS/CSI-RS availability indication and/or L1-based TRS/CSI-RS availability indication.
In some embodiments, a timer/window may be used/configured for SI-based TRS/CSI-RS availability indication.
Preferably, when a timer/window used/configured for the SI-based TRS/CSI-RS availability indication is running, the UE may decide whether the TRS/CSI-RS is available/valid according to the SI-based TRS/CSI-RS availability indication.
Preferably, when the timer/window used/configured for the SI-based TRS/CSI-RS availability indication is not running (or expired), the UE may decide whether the TRS/CSI-RS is available/valid according to the L1-based TRS/CSI-RS availability indication.
In some embodiments, a timer/window may be used/configured for an L1-based TRS/CSI-RS availability indication.
Preferably, when a timer/window used/configured for the L1-based TRS/CSI-RS availability indication is running, the UE may decide whether the TRS/CSI-RS is available/valid according to the L1-based TRS/CSI-RS availability indication.
Preferably, when the timer/window used/configured for the L1-based TRS/CSI-RS availability indication is not running (or expired), the UE may decide whether the TRS/CSI-RS is available/valid according to the SI-based TRS/CSI-RS availability indication.
In some embodiments, a timer/window may be used/configured for both SI-based TRS/CSI-RS availability indication and L1-based TRS/CSI-RS availability indication.
Preferably, when a timer/window used/configured for the SI-based TRS/CSI-RS availability indication and for the L1-based TRS/CSI-RS availability indication is running, the UE may decide whether the TRS/CSI-RS is available/valid according to the SI-based TRS/CSI-RS availability indication and the L1-based RS/CSI-RS availability indication.
Preferably, the UE may maintain one timer/window for both the SI-based TRS/CSI-RS availability indication and for the L1-based TRS/CSI-RS availability indication.
Preferably, the UE may maintain/apply a first timer/window for SI-based TRS/CSI-RS availability indication and maintain/apply a second timer/window for L1-based TRS/CSI-RS availability indication.
Preferably, the UE may maintain one timer/window for the paging DCI based TRS/CSI-RS availability indication and the PEI based TRS/CSI-RS availability indication.
Preferably, the UE may maintain/apply a first timer/window for paging DCI based TRS/CSI-RS availability indication and maintain/apply a second timer/window for PEI based TRS/CSI-RS availability indication.
In some embodiments, the UE may (re) start a timer/window configured for (L1-based and/or SI-based) TRS/CSI-RS availability indication on one or more of the following conditions.
In some embodiments, when receiving an SI-based TRS/CSI-RS availability indication (indicating TRS/CSI-RS available/valid and/or unavailable/invalid), the UE may (re) start a timer/window configured for (L1-based and/or SI-based) TRS/CSI-RS availability indication.
In some embodiments, when receiving an L1-based TRS/CSI-RS availability indication (indicating TRS/CSI-RS available/valid and/or unavailable/invalid), the UE may (re) start a timer/window configured for the (L1-based and/or SI-based) TRS/CSI-RS availability indication.
In some embodiments, upon receiving the RRC message (e.g., RRCResume, RRCSetup, RRCRelease, RRCRelease, RRCReestablishment with suspend conf and/or rrcrreject), the UE may (re) start a timer/window configured for (L1-based and/or SI-based) TRS/CSI-RS availability indication.
More specifically, the RRC message may be used to (re) configure (availability of) TRS/CSI-RS (resources/configuration).
In some embodiments, the UE may stop/release the timer/window configured for the TRS/CSI-RS availability indication in one or more of the following conditions.
In some embodiments, when receiving the SI-based TRS/CSI-RS availability indication (i.e., indicating TRS/CSI-RS is unavailable/invalid), the UE may stop/release the timer/window configured as the (L1-based and/or SI-based) TRS/CSI-RS availability indication.
In some embodiments, when receiving an L1-based TRS/CSI-RS availability indication (i.e., indicating TRS/CSI-RS is unavailable/inactive), the UE may stop/release the timer/window configured as the (L1-based and/or SI-based) TRS/CSI-RS availability indication.
In some embodiments, when receiving the RRC message (e.g., RRCResume, RRCSetup, RRCRelease, RRCRelease, RRCReestablishment with suspend conf iotag, and/or rrcrreject), the UE may stop/release the timer/window configured as a (L1-based and/or SI-based) TRS/CSI-RS availability indication.
More specifically, the RRC message may be used to release (availability of) TRS/CSI-RS (resources/configuration).
In some embodiments, the UE may stop/release the timer/window configured as the (L1-based and/or SI-based) TRS/CSI-RS availability indication during cell selection or reselection.
In some embodiments, when the UE moves to another RAT (e.g., E-UTRA), the UE may stop/release the timer/window configured for (L1-based and/or SI-based) TRS/CSI-RS availability indication.
In some embodiments, when the UE performs suspension of connection establishment (e.g., by an upper layer), the UE may stop/release the timer/window configured for the TRS/CSI-RS availability indication (L1-based and/or SI-based).
In some embodiments, the UE may stop/release the timer/window configured as a (L1-based and/or SI-based) TRS/CSI-RS availability indication during a RAN announcement Region (RNA) update.
In some embodiments, the UE may stop/release the timer/window configured for the (L1-based and/or SI-based) TRS/CSI-RS availability indication when the UE changes the serving cell to another cell or when the UE camps on a new (suitable/acceptable) cell.
In some embodiments, when the UE initiates the RRC reestablishment procedure, the UE may stop/release the timer/window configured for the TRS/CSI-RS availability indication (L1-based and/or SI-based). For example, the timer/window may be stopped/released when the UE sends an RRC re-establishment request to the network.
When the UE is instructed to perform carrier switching (e.g., switching from Normal Uplink (NUL) to supplemental Uplink (Supplementary Uplink, SUL) or vice versa) over the network, the UE may stop/release the timer/window configured as a (L1-based and/or SI-based) TRS/CSI-RS availability indication.
When the UE is instructed to perform BWP handover through the network, the UE may stop/release the timer/window configured as the TRS/CSI-RS availability indication (L1-based and/or SI-based).
In some embodiments, when the timer/window configured for the TRS/CSI-RS availability indication expires, the UE may perform one or more of the following actions:
In some embodiments, when the configured timer/window for the TRS/CSI-RS availability indication expires, the UE may decide whether the TRS/CSI-RS on the configured TRS/CSI-RS occasion is available/valid.
More specifically, the SI-based TRS/CSI-RS availability indication may be used to indicate a default/initial state of (set/group/index of) TRS/CSI-RS availability/unavailability of TRS/CSI-RS resources.
More specifically, the default/initial state of the TRS/CSI-RS indicated in the SI-based TRS/CSI-RS availability indication may be available/valid.
More specifically, the default/initial state of the TRS/CSI-RS indicated in the SI-based TRS/CSI-RS availability indication may be unavailable/invalid.
In some embodiments, the UE may release (availability of) the TRS/CSI-RS (resource/configuration) when the timer/window configured for the TRS/CSI-RS availability indication expires.
In some embodiments, the UE may apply the SI acquisition procedure when a timer/window configured for the TRS/CSI-RS availability indication expires.
In some embodiments, the UE may (immediately) (re) acquire SI when the timer/window configured for the TRS/CSI-RS availability indication expires.
More specifically, the SI may be a minimum SI (e.g., MIB, SIB 1) and/or other SI (e.g., SIB2, SIB3, SIB4, SIB5, SIB6, SIB7, SIB8, SIB9, SIB10, SIB11, etc.).
More specifically, SI may be received on the BCCH and/or DL-SCH.
In some embodiments, the UE may decide, by the TRS/CSI-RS availability indication, that the indicated status of the TRS/CSI-RS is invalid when a timer/window configured for the TRS/CSI-RS availability indication expires.
In some embodiments, when a timer/window configured for the TRS/CSI-RS availability indication expires, the UE may not decide whether a TRS/CSI-RS based on the indicated TRS/CSI-RS indication is available/valid.
In some embodiments, when the timer/window configured for the TRS/CSI-RS availability indication expires, the UE may decide whether the TRS/CSI-RS is available/valid according to the SI-based TRS/CSI-RS availability indication, and may not decide whether the TRS/CSI-RS is available/valid according to the L1-based TRS/CSI-RS availability indication.
In some embodiments, the UE may decide that (all) TRS/CSI-RS is unavailable/invalid when a timer/window configured for TRS/CSI-RS availability indication expires.
In some embodiments, the UE may enter the rrc_idle state when a timer/window configured for TRS/CSI-RS availability indication expires.
In some embodiments, the UE may stay in rrc_inactive state when the timer/window configured for TRS/CSI-RS availability indication expires.
In some embodiments, the UE may initiate an RRC setup procedure (e.g., by an rrcsetup request) when the timer/window configured for the TRS/CSI-RS availability indication expires.
In some embodiments, the UE may initiate an RRC reestablishment procedure (e.g., by an rrcresistigmentrequest) when the timer/window configured for the TRS/CSI-RS availability indication expires.
In some embodiments, the UE may initiate an RRC connection recovery procedure (e.g., by rrcresmerequest) when the timer/window configured for the TRS/CSI-RS availability indication expires.
Based on duration of time
In some implementations, the UE may be configured with an effective duration of units (e.g., number of symbols, slots, subframes, SFN, ms, s, DRX cycles, number of POs, number of PFs, number of PDCCH monitoring occasions).
In some embodiments, the UE may decide whether the TRS/CSI-RS is available/valid based on the TRS/CSI-RS availability indication for the active duration.
In some embodiments, during the validity duration, the UE may decide whether the TRS/CSI-RS is available/valid based on the L1-based TRS/CSI-RS availability indication and/or the SI-based TRS/CSI-RS availability indication.
In some embodiments, the effective duration with units may be configured in a configuration for TRS/CSI-RS (which may be configured by SIB and/or RRC messages).
In some embodiments, outside the validity duration, the UE may not decide whether the TRS/CSI-RS is available/valid based on the TRS/CSI-RS availability indication.
In some embodiments, outside the validity duration, the UE may decide whether the TRS/CSI-RS is available/valid according to the SI-based TRS/CSI-RS availability indication, and may decide whether the TRS/CSI-RS is available/valid not according to the L1-based TRS/CSI-RS availability indication.
In some embodiments, outside the active duration, the UE may decide that (all) TRS/CSI-RS is not available/inactive.
In some embodiments, when the UE receives SI (indicating TRS/CSI-RS availability indication), paging DCI (indicating TRS/CSI-RS availability indication) and/or PEI (indicating TRS/CSI-RS availability indication), having a unit of active duration may start timing.
In some embodiments, the valid duration with units may be ended based on the configured values of the valid duration and the units.
In some embodiments, the valid duration with units may be counted by a counter. In some embodiments, the effective duration may be configured by periodicity.
In some embodiments, the effective duration may be configured to infinity. If the validity duration is configured to infinity, the UE may decide that the state of the TRS/CSI-RS indicated in the TRS/CSI-RS availability indication is always valid.
PEI indicates SI modification and/or ETWS/CMAS
SI modification indication
PEI may include SI modification indications.
More specifically, SI modification may refer to BCCH modification (e.g., in addition to SIB6, SIB7, and SIB 8).
In some embodiments, the UE may decide whether to apply the SI acquisition procedure (from the beginning of the next modification period) based on the SI modification indication included in the PEI.
In some embodiments, when the UE receives PEI, and if the SI modification indication included in the PEI is set to a first value (e.g., 1), the UE may apply the SI acquisition procedure (from the beginning of the next modification period).
In some embodiments, when the UE receives the PEI, and if the SI modification indication included in the PEI is set to a second value (e.g., 0), the UE may not apply the SI acquisition procedure.
The first value and the second value may be different.
In some embodiments, when the UE receives PEI, and if the SI modification indication is not included (e.g., absent) in the PEI, the UE may not apply the SI acquisition procedure.
In some embodiments, when the UE is configured with PEI (and/or if the UE receives PEI), the UE may decide whether to apply the SI acquisition procedure based on the first SI modification indication included in the PEI, and may or may not decide whether to apply the SI acquisition procedure (from the next modification period) based on the second SI modification indication included in the short message (of paging DCI). More specifically, when the UE receives PEI, the PEI may indicate whether the UE needs to monitor for subsequent POs. If the PEI instructs the UE to listen to the subsequent PO, the UE may receive a short message (of paging DCI) on the subsequent PO.
In some embodiments, when the UE is configured with PEI (and/or if the UE receives PEI), the UE may decide whether to apply the SI acquisition procedure (from the next modification period) based on the SI modification indication contained in the PEI. Then, if the UE receives a short message (e.g., on a subsequent PO) in the paging DCI, the UE may ignore/skip the second SI modification indication included in the short message (of the paging DCI).
Preferably, if the first SI modification indication is set to a first value (e.g., 1) to instruct the UE to apply the SI acquisition procedure (from the next modification period), the UE can only ignore/skip the second SI modification indication included in the short message (of paging DCI).
Preferably, if the first SI modification indication is set to a second value (e.g., 0) to indicate that the UE does not apply the SI acquisition procedure (from the next modification period), the UE can only ignore/skip the second SI modification indication included in the short message (of paging DCI).
More specifically, the first SI modification indication included in the PEI may have a higher priority than the second SI modification indication included in the short message (of the paging DCI).
In some embodiments, when the UE is configured with PEI (and/or if the UE receives PEI), the UE may decide whether to apply the SI acquisition procedure (from the next modification period) based on the SI modification indication contained in the PEI. Then, when the UE receives the short message (of the paging DCI) (e.g., on a subsequent PO), the UE may consider that the second SI modification indication is not present (or absent) in the short message (of the paging DCI).
Preferably, if the first SI modification indication is set to a first value (e.g., 1) to instruct the UE to apply the SI acquisition procedure (from the next modification period), the UE may decide that the second SI modification indication is not present (or absent) in the short message (of the paging DCI).
Preferably, if the first SI modification indication is set to a second value (e.g., 0) to indicate that the UE does not apply the SI acquisition procedure (from the next modification period), the UE may decide that the second SI modification indication is not present (or absent) in the short message (of the paging DCI).
In some embodiments, when the UE is configured with PEI (and/or if the UE receives PEI), the UE may decide whether to apply the SI acquisition procedure (from the next modification period) based on the SI modification indication contained in the PEI. Then, when the UE receives the short message (of the paging DCI) (e.g., on a subsequent PO), the UE may decide whether to apply the SI acquisition procedure (from the beginning of the next modification period) based on the second SI modification indication contained in the short message (of the paging DCI).
In some embodiments, when the UE receives a first SI modification indication included in the PEI and then receives a second SI modification indication included in a short message (of paging DCI), the UE may ignore the first SI modification indication and apply the second SI modification indication.
In some embodiments, when the UE receives a first SI modification indication included in the PEI and then receives a second SI modification indication included in the short message (of the paging DCI), the UE may replace the first SI modification indication with the second SI modification indication.
In some embodiments, if a first SI modification indication included in the PEI indicates that the UE applies the SI acquisition procedure (from the beginning of the next modification period), but a second modification indication included in the short message (of the paging DCI) indicates that the UE does not apply the SI acquisition procedure (from the beginning of the next modification period), the UE may follow (or replace) instructions from the second SI modification indication. For example, the UE may not apply the SI acquisition procedure (starting from the next modification period).
Preferably, if the first SI modification indication is set to a first value (e.g., 1) to instruct the UE to apply the SI acquisition procedure (from the beginning of the next modification period), the UE may also decide whether to apply the SI acquisition procedure (from the beginning of the next modification period) based on the second SI modification indication included in the short message (of paging DCI).
The UE may ignore the first SI modification indication if the first SI modification indication is set to a first value (e.g., 1) and the UE receives a second SI modification indication included in a short message (of paging DCI). In this case, the UE may decide whether to apply the SI acquisition procedure (from the beginning of the next modification period) based on the second SI modification indication included in the short message (of the paging DCI).
Preferably, if the first SI modification indication is set to a second value (e.g., 0) to indicate that the UE does not apply the SI acquisition procedure (from the beginning of the next modification period), the UE may also decide whether to apply the SI acquisition procedure (from the beginning of the next modification period) based on the second SI modification indication included in the short message (of paging DCI).
The UE may ignore the first SI modification indication if the first SI modification indication is set to a second value (e.g., 0) and the UE receives the second SI modification indication included in the short message (of paging DCI). In this case, the UE may decide whether to apply the SI acquisition procedure (from the beginning of the next modification period) based on the second SI modification indication included in the short message (of the paging DCI).
Preferably, if the first SI modification indication is not included (absent) in the PEI, the UE may also decide whether to apply the SI acquisition procedure (from the beginning of the next modification period) based on the second SI modification indication included in the short message (of the paging DCI).
Preferably, if the device first SI modification indication is a specific value (e.g., 1 or 0) in the PEI, the UE may also decide whether to apply the SI acquisition procedure (from the beginning of the next modification period) based on the second SI modification indication included in the short message (of the paging DCI).
More specifically, the second SI modification indication included in the short message (of the paging DCI) may have a higher priority than the first SI modification indication included in the PEI.
In some embodiments, when the UE is configured with PEI (and/or if the UE receives PEI), the UE may decide whether to apply the SI acquisition procedure based on the first SI modification indication included in the PEI, and the UE may expect the second SI modification indication included in the short message (of the paging DCI) to indicate the same information as the first SI modification indication included in the PEI.
In some embodiments, the NW may indicate to the UE the same information as in the second SI modification indication by the first SI modification indication included in the PEI.
In some embodiments, if the information of the first SI modification indication included in the PEI is different from the information of the second modification indication included in the short message (of the paging DCI), the UE may apply the second SI modification indication and may ignore the first SI modification indication.
In some embodiments, if the information of the first SI modification indication included in the PEI is different from the information of the second modification indication included in the short message (of the paging DCI), the UE may apply the first SI modification indication and may ignore the second SI modification indication.
In some embodiments, when the UE receives PEI indicating the SI modification indication, the UE may decide whether to monitor a subsequent PO (to detect paging DCI), whether to decode the short message indicator, whether to decode the short message, and/or receive the paging message based on the SI modification indication contained in the PEI.
In some embodiments, when the UE receives PEI indicating the SI modification indication and the SI modification indication is set to a first value (e.g., 1), the UE may or may not monitor for subsequent POs (to detect paging DCI), decode the short message indicator, decode the short message, and/or receive the paging message.
In some embodiments, when the UE receives PEI indicating the SI modification indication and the SI modification indication is set to a first value (e.g., 1), the UE may apply the SI acquisition procedure (from the beginning of the next modification period) and the UE may not monitor the subsequent POs (to detect paging DCI), decode the short message indicator, decode the short message, and/or receive the paging message.
In some embodiments, when the UE receives PEI indicating the SI modification indication and the SI modification indication is set to a second value (e.g., 0), the UE may not apply the SI acquisition procedure (from the next modification period), and the UE may monitor for subsequent POs (to detect paging DCI), decode the short message indicator, decode the short message, and/or receive the paging message.
In some embodiments, when the UE receives PEI and the SI modification indication is not included (or not present) in PEI, the UE may not apply the SI acquisition procedure (from the next modification period), and the UE may monitor for subsequent POs (to detect paging DCI), decode the short message indicator, decode the short message, and/or receive the paging message.
ETWS/CMAS indication
PEI may include an ETWS/CMAS indication.
More specifically, the ETWS/CMAS indication may be used to provide the UE with ETWS/CMAS capabilities.
More specifically, the ETWS/CMAS indication may be for UEs provided with searchSpaceSIB1 and searchspaceothersystem information on active BWP or initial BWP.
When the UE receives the ETWS/CMAS indication contained in the PEI, the UE may perform one or more of the following actions (but is not limited to):
immediately reacquiring SIB1;
acquiring SIB6 (if the UE has ETWS capability and si-scheduling info includes scheduling information of SIB 6);
Acquiring SIB7 (if the UE has ETWS capability and si-scheduling info includes scheduling information of SIB 7); and
SIB8 is acquired (if the UE has CMAS capability and si-scheduling info includes scheduling information for SIB 8).
In some embodiments, the UE may decide whether to re-acquire SIB1 and/or acquire SIB6/SIB7/SIB8 immediately based on the ETWS/CMAS indication included in the PEI.
In some embodiments, when the UE receives PEI, and if the ETWS/CMAS indication included in PEI is set to a first value (e.g., 1), the UE may immediately reacquire SIB1 and/or acquire SIB6/SIB7/SIB8.
In some embodiments, when the UE receives PEI, and if the ETWS/CMAS indication included in PEI is set to a second value (e.g., 0), the UE may not immediately reacquire SIB1 and/or may not immediately acquire SIB6/SIB7/SIB8.
The first value and the second value may be different.
In some embodiments, when the UE receives PEI, and if the ETWS/CMAS indication is not included (e.g., not present, absent) in the PEI, the UE may not immediately reacquire SIB1 and/or may not immediately acquire SIB6/SIB7/SIB8.
In some embodiments, when the UE is configured with PEI (and/or if the UE receives PEI), the UE may decide whether to re-acquire SIB1 immediately based on a first ETWS/CMAS indication included in the PEI, and may or may not decide whether to re-acquire SIB1 immediately and/or acquire SIB6/SIB7/SIB8 based on a second ETWS/CMAS indication included in the short message (of paging DCI). More specifically, when the UE receives PEI, the PEI may indicate whether the UE needs to monitor for subsequent POs. If the PEI instructs the UE to listen to the subsequent PO, the UE may receive a short message (of paging DCI) on the subsequent PO.
In some embodiments, when the UE is configured with PEI (and/or if the UE receives PEI), the UE may decide whether to re-acquire SIB1 and/or acquire SIB6/SIB7/SIB8 immediately based on the ETWS/CMAS indication contained in the PEI. Then, when the UE receives the short message (of paging DCI) (e.g., on a subsequent PO), the UE may ignore/skip the second ETWS/CMAS indication included in the short message (of paging DCI).
Preferably, if the first ETWS/CMAS indication is set to a first value (e.g., 1) to instruct the UE to immediately reacquire SIB1 and/or acquire SIB6/SIB7/SIB8, the UE may ignore/skip the second ETWS/CMAS indication included in the short message (of paging DCI).
Preferably, if the first ETWS/CMAS indication is set to a second value (e.g., 0) to indicate that the UE does not immediately reacquire SIB1 and/or acquire SIB6/SIB7/SIB8, the UE may ignore/skip the second ETWS/CMAS indication included in the short message (of paging DCI).
More specifically, the priority of the first ETWS/CMAS indication included in the PEI may be higher than the priority of the second ETWS/CMAS indication included in the short message (of the paging DCI).
In some embodiments, when the UE is configured with PEI (and/or if the UE receives PEI), the UE may decide whether to re-acquire SIB1 and/or acquire SIB6/SIB7/SIB8 immediately based on the ETWS/CMAS indication contained in the PEI. Then, when the UE receives a short message (of paging DCI) (e.g., on a subsequent PO), the UE may decide that there is no (or lack of) a second ETWS/CMAS indication in the short message (of paging DCI).
Preferably, if the first ETWS/CMAS indication is set to a first value (e.g., 1) to instruct the UE to immediately reacquire SIB1 and/or acquire SIB6/SIB7/SIB8, the UE may decide that the second ETWS/CMAS indication is not present (or absent) in the short message (paging DCI).
Preferably, if the first ETWS/CMAS indication is set to a second value (e.g., 0) to indicate that the UE does not immediately reacquire SIB1 and/or acquire SIB6/SIB7/SIB8, the UE may decide that the second ETWS/CMAS indication is not present (or absent) in the short message (paging DCI).
In some embodiments, when the UE is configured with PEI (and/or if the UE receives PEI), the UE may decide whether to re-acquire SIB1 and/or acquire SIB6/SIB7/SIB8 immediately based on the ETWS/CMAS indication contained in the short message (of paging DCI). Then, when the UE receives the short message (of the paging DCI) (e.g., on a subsequent PO), the UE may also decide whether to re-acquire SIB1 and/or acquire SIB6/SIB7/SIB8 immediately based on the second ETWS/CMAS indication contained in the short message (of the paging DCI).
In some embodiments, if the first ETWS/CMAS indication included in the PEI indicates that the UE is immediately reacquiring SIB1 and/or acquiring SIB6/SIB7/SIB8, but the second ETWS/CMAS indication included in the short message (in the paging DCI) indicates that the UE is not immediately reacquiring SIB1 and/or not immediately acquiring SIB6/SIB7/SIB8, the UE may follow (or be replaced with) instructions from the second ETWS/CMAS indication. For example, the UE may not immediately reacquire SIB1 and/or not immediately acquire SIB6/SIB7/SIB8.
Preferably, if the first ETWS/CMAS indication is set to a first value (e.g., 1) to instruct the UE to immediately reacquire SIB1 and/or acquire SIB6/SIB7/SIB8, the UE may also decide whether to immediately reacquire SIB1 and/or acquire SIB6/SIB7/SIB8 based on the second ETWS/CMAS indication included in the short message (of the paging DCI).
Preferably, if the first ETWS/CMAS indication is set to a second value (e.g., 0) to indicate to the UE that SIB1 is not immediately reacquired and/or SIB6/SIB7/SIB8 is not immediately acquired, the UE may also decide whether to immediately reacquire SIB1 and/or acquire SIB6/SIB7/SIB8 based on the second ETWS/CMAS indication included in the short message (of the paging DCI).
Preferably, if the first ETWS/CMAS indication is not included (or not present) in the PEI, the UE may also decide whether to re-acquire SIB1 and/or acquire SIB6/SIB7/SIB8 immediately based on the second ETWS/CMAS indication included in the short message (of the paging DCI).
More specifically, the priority of the second ETWS/CMAS indication included in the short message (of the paging DCI) may be higher than the priority of the first ETWS/CMAS indication included in the PEI.
In some embodiments, when the UE is configured with PEI (and/or if the UE receives PEI), the UE may decide whether to re-acquire SIB1 and/or acquire SIB6/SIB7/SIB8 immediately based on the first ETWS/CMAS indication included in the PEI, and the UE may expect the information of the second ETWS/CMAS indication included in the short message (of paging DCI) to be the same as the information of the first ETWS/CMAS indication included in the PEI.
In some embodiments, the NW may indicate the same information to the UE as in the second ETWS/CMAS indication by the first ETWS/CMAS indication included in the PEI.
In some embodiments, if the information of the first ETWS/CMAS indication included in the PEI is different from the information of the second ETWS/CMAS indication included in the short message (of the paging DCI), the UE may apply the second ETWS/CMAS indication and may ignore the first ETWS/CMAS indication.
In some embodiments, if the information of the first ETWS/CMAS indication included in the PEI is different from the information of the second ETWS/CMAS indication included in the short message (of the paging DCI), the UE may apply the first ETWS/CMAS indication and may ignore the second ETWS/CMAS indication.
In some embodiments, when the UE receives PEI indicating an ETWS/CMAS indication, the UE may decide whether to monitor a subsequent PO (to detect paging DCI), whether to decode a short message indicator, whether to decode a short message, and/or receive a paging message based on an ETWS/CMAS indication included in the PEI.
In some embodiments, when the UE receives PEI indicating an ETWS/CMAS indication and the ETWS/CMAS indication is set to a first value (e.g., 1), the UE may or may not monitor subsequent POs (to detect paging) DCIs, to decode the short message indicator, to decode the short message, and/or to receive the paging message.
In some embodiments, when the UE receives PEI indicating the ETWS/CMAS indication and the ETWS/CMAS indication is set to a first value (e.g., 1), the UE may immediately reacquire SIB1 and/or acquire SIB6/SIB7/SIB8 and the UE may not monitor for subsequent POs (to detect paging DCI), to decode the short message indicator, to decode the short message, and/or to receive the paging message.
In some embodiments, when the UE receives PEI indicating the ETWS/CMAS indication and the ETWS/CMAS indication is set to a second value (e.g., 0), the UE may not immediately reacquire SIB1 and/or acquire SIB6/SIB7/SIB8 and the UE may monitor for subsequent POs (to detect paging DCI), to decode the short message indicator, to decode the short message, and/or to receive the paging message.
In some embodiments, when the UE receives PEI implicitly indicating the ETWS/CMAS indication and the ETWS/CMAS indication is not explicitly included in the PEI, the UE may not immediately reacquire SIB1 and/or acquire SIB6/SIB7/SIB8 and the UE may monitor for subsequent POs (to detect paging DCI), to decode the short message indicator, to decode the short message, and/or to receive the paging message.
PEI and Small data Transmission (Small Data Transmission, SDT)
The UE in rrc_inactive/rrc_idle state may apply the PEI mechanism and the SDT mechanism at the same time. The purpose of PEI is to save energy. For example, a UE in rrc_inactive/rrc_idle state may reduce unnecessary monitoring of paging monitoring/detection. The purpose of SDT is to provide an opportunity for a UE in rrc_inactive state to transmit UL data without transitioning to rrc_connected state.
Configuration of PEI and SDT
In some embodiments, the NW configures one or both of the PEI configuration and the SDT configuration to the UE (e.g., in rrc_inactive/rrc_idle state).
In some embodiments, the NW may configure both the PEI configuration and the SDT configuration to the UE.
In some embodiments, the UE may apply both PEI configuration and SDT configuration simultaneously.
In some embodiments, the NW may configure only one of the PEI configuration and the SDT configuration to the UE (e.g., in rrc_inactive/rrc_idle state).
In some embodiments, the SDT configuration may have a higher priority than the PEI configuration.
In some embodiments, when the NW configures the SDT configuration to the UE, the NW may not configure the PEI configuration to the UE.
In some embodiments, when the UE is configured with an SDT configuration, the UE may not be configured with a PEI configuration.
In some embodiments, the UE may not apply PEI configuration when the UE applies SDT configuration.
In some embodiments, the PEI configuration may have a higher priority than the SDT configuration.
In some embodiments, when the NW configures PEI configuration to the UE, the NW may not configure SDT configuration to the UE and/or in the cell.
In some embodiments, when the UE is configured with a configuration, the UE may not be configured with an SDT configuration.
In some embodiments, the UE may not apply the SDT configuration when the UE applies the PEI configuration.
In some embodiments, the NW may decide whether to configure PEI and/or SDT based on UE capabilities and/or UE assistance information (e.g., when the UE is in rrc_inactive/rrc_idle state). More specifically, UE capability and/or UE assistance information may be sent by the UE to the NW (e.g., when the UE is in rrc_ CONNECTED, RRC _inactive and/or rrc_idle state).
In some embodiments, the UE may send UE capabilities and/or UE assistance information indicating whether the UE supports PEI, SDT, and/or both.
In some embodiments, the NW may configure the PEI configuration to the UE (and may not configure the SDT configuration to the UE) when the UE sends UE capabilities indicating that the UE supports PEI and/or UE assistance information. On the other hand, when the UE transmits UE capability and/or UE assistance information indicating that the UE supports PEI, the UE may apply PEI configuration (and may not apply SDT configuration).
In some embodiments, the NW may configure the SDT configuration to the UE (and may not configure the PEI configuration to the UE) when the UE sends UE capabilities indicating that the UE supports SDT and/or UE assistance information. On the other hand, when the UE transmits UE capability and/or UE assistance information indicating that the UE supports SDT, the UE may apply SDT configuration (and may not apply PEI configuration).
In some embodiments, the NW may configure both the PEI configuration and the SDT configuration to the UE when the UE sends UE capabilities and/or UE assistance information indicating that the UE supports both PEI and SDT. On the other hand, when the UE transmits UE capability and/or UE assistance information indicating that the UE supports both PEI and SDT, the UE may apply both PEI configuration and SDT configuration.
PEI in SDT procedure
In some embodiments, the NW may configure one or both of the PEI configuration and the SDT configuration to the UE (e.g., in rrc_inactive/rrc_idle state).
In some embodiments, the NW may configure both the PEI configuration and the SDT configuration to the UE.
In some embodiments, the UE may apply both PEI configuration and SDT configuration simultaneously.
In some embodiments, the UE may initiate the SDT procedure when the SDT-initiated criteria are met (e.g., when the UE is in rrc_inactive/rrc_idle state). After the UE initiates the SDT procedure, the UE may decide whether to monitor the PEI during the SDT procedure (e.g., on the SS/PDCCH for the PEI). More specifically, the SDT procedure may be a Random Access (RA) SDT (RA-SDT) and/or a configuration authorization (CG) SDT (CG-SDT).
In some embodiments, the UE may decide whether to monitor the PEI during the SDT procedure based on the configuration/IE received from the NW (e.g., on the SS/PDCCH for the PEI).
In some embodiments, if the configuration/information element (information element, IE) indicates the first value, the UE may monitor the PEI (e.g., on the SS/PDCCH for the PEI) during the SDT procedure.
In some embodiments, if the configuration/IE indicates the second value, the UE may not monitor the PEI during the SDT procedure (e.g., on the SS/PDCCH for the PEI).
More specifically, the configuration/IE may include a bit to indicate to the UE to enable/disable PEI monitoring.
More specifically, the configuration/IE may be configured in a PEI configuration and/or an SDT configuration. More specifically, the configuration/IE may be configured by system information (e.g., SIB1 or "other SI"). More specifically, the configuration/IE may be configured by an RRC release message (e.g., with or without a suspension configuration).
Note that the configuration/IE may be included in the RRC message.
In some embodiments, the UE may monitor the PEI during the SDT procedure (e.g., on the SS/PDCCH for the PEI).
In some embodiments, the UE may monitor the PEI during the SDT procedure, before and/or within a subsequent transmission period.
In some embodiments, the UE may monitor the PEI during the SDT procedure, before (successfully) completing the RA procedure (for SDT), and/or after.
If the UE decides that contention resolution of the RA procedure is successful, the UE may decide/consider that the RA procedure is successfully completed.
In some embodiments, the UE may monitor the PEI during the SDT procedure, before or after the UE receives the response from the NW.
In some embodiments, the response may be Msg2/Msg4/MsgB.
In some embodiments, the response may be used for contention resolution for RA-SDT procedures.
In some embodiments, the response may be feedback for a (first/initial) UL transmission via CG resources (in CG-SDT procedures). The response/feedback may include hybrid automatic repeat request (Hybrid Automatic Repeat request, HARQ) Acknowledgement (ACK)/non-acknowledgement (NACK) messages, and/or downlink feedback information (Downlink Feedback Information, DFI) (e.g., for (first) UL transmission via CG resources)). The response may represent a UL grant for transmitting the HARQ process for transmitting a (first/initial) UL transmission (e.g., in CG-SDT process over CG resources).
In some embodiments, the response may be a PDCCH addressed to an RNTI (e.g., cell-Radio Network Temporary Identifier, C-RNTI), configured scheduling RNTI (Configured Scheduling RNTI, CS-RNTI), dedicated RNTI, RNTI for SDT, and/or RNTI for CG.
In some embodiments, the response may include RRCResume, RRCSetup, RRCRelease, RRCRelease with SuspendConfig, RRCRebuiltment, RRCReconfiguration, and/or RRCReject, among others.
In some embodiments, if the timer/window (e.g., for SDT) is not running, the UE may monitor the PEI during the SDT procedure.
In some embodiments, the timer/window may be a CG-SDT response timer/window,
in some embodiments, a timer/window may be used to monitor the response/feedback of the PDCCH (e.g., including ACK/NACK/DFI).
In some embodiments, a timer/window may be used to monitor PDCCH from NW for new transmission/retransmission schedule.
In some embodiments, the timer/window may be ra-ResponseWindow, msgB-ResponseWindow, ra-ContentionResolutionTimer, configuredGrantTimer, cg-RetransmissionTimer, drx-onDurationTimer, drx-InactivityTimer, drx-retransmission timerdl and/or drx-retransmission timersl.
In some embodiments, the timer/window may be an SDT failure detection timer. The timers/windows may be T300, T301, T302, T304, T310, T311, T312, T316, T319, T320, T321, T322, T325, T330, T331, T342, and/or T345.
In some embodiments, the timer/window may be a TA timer and/or an SDT TA timer.
In some embodiments, if the SDT procedure is a CG-SDT procedure, the UE may monitor the PEI during the SDT procedure. In some embodiments, if the SDT procedure is an RA-SDT procedure, the UE may monitor the PEI during the SDT procedure.
In some embodiments, the UE may not monitor the PEI (e.g., on the SS/PDCCH for the PEI) during the SDT procedure. Preferably, the UE not monitoring PEI (e.g., on SS/PDCCH for PEI) may mean that the UE skips/ignores monitoring PEI (e.g., on SS/PDCCH for PEI).
In some embodiments, the UE may not monitor the PEI during the SDT procedure before or after entering a subsequent transmission period.
In some embodiments, when the UE is performing an RA procedure (for SDT), the UE may not monitor the PEI during the SDT procedure.
In some embodiments, the UE may not monitor the PEI during the SDT procedure, before or after the UE sends the UL message.
The UL message may be sent via Msg1/Msg3/MsgA/CG resources/UL resources scheduled by Msg2/MsgB/Msg4 (during SDT procedure).
The UL message may include an RRC resume request message (e.g., rrrceumerequest or rrrceumerequest 1).
The UL message may include small data (e.g., UL data associated with a particular signaling radio bearer (Signaling Radio Bearer, SRB)/data radio bearer (Data Radio Bearer, DRB)/Logical Channel (LCH) for SDT).
The UL message may include a MAC Control Element (CE) (e.g., buffer status report (Buffer Status Report, BSR) MAC CE).
If the UL message is (re) sent based on CG resources/configuration, a timer/window corresponding to CG configuration may be (re) started.
If the UL message is sent on UL resources scheduled by a dynamic grant and the dynamic grant is used for retransmission of HARQ processes transmitting UL data via CG resources, a timer/window corresponding to the CG configuration may be (re) started.
In some embodiments, the UE may not monitor the PEI during the SDT procedure before or after the UE receives the response from the NW.
In some embodiments, the response may be Msg2/Msg4/MsgB. This response may be used for contention resolution for RA-SDT procedures.
In some embodiments, the response may be feedback for a (first/initial) UL transmission via CG resources (in CG-SDT procedures). The response/feedback may include (HARQ) ACK/NACK messages and/or DFI (e.g., for (first) UL transmissions via CG resources). The response may represent a UL grant for transmitting the HARQ process for transmitting a (first/initial) UL transmission (e.g., in CG-SDT process over CG resources).
In some embodiments, the response may be a PDCCH addressed to an RNTI (e.g., a C-RNTI, a CS-RNTI, a dedicated RNTI, an RNTI for SDT, and/or an RNTI for CG).
In some embodiments, the response may include RRCResume, RRCSetup, RRCRelease, RRCRelease with SuspendConfig, RRCRebuiltment, RRCReconfiguration, and/or RRCReject, among others.
In some embodiments, if a timer/window (e.g., for SDT) is running, the UE may not monitor PEI during the SDT procedure.
In some embodiments, the timer/window may be a CG-SDT response timer/window.
In some embodiments, a timer/window may be used to monitor the response/feedback of the PDCCH (e.g., including ACK/NACK/DFI).
In some embodiments, a timer/window may be used to monitor the PDCCH for new transmission/retransmission schedules from the NW.
In some embodiments, the timer/window may be ra-ResponseWindow, msgB-ResponseWindow, ra-ContentionResolutionTimer, configuredGrantTimer, cg-RetransmissionTimer, drx-ondurationTimer, drx-InactivityTimer, drx-RetransmissionTimer DL, and/or drx-RetransmissionTimer UL.
In some embodiments, the timer/window may be an SDT failure detection timer. The timers/windows may be T300, T301, T302, T304, T310, T311, T312, T316, T319, T320, T321, T322, T325, T330, T331, T342, and/or T345.
In some embodiments, the timer/window may be a TA timer and/or an SDT TA timer.
In some embodiments, if the SDT procedure is a CG-SDT procedure, the UE may not monitor the PEI during the SDT procedure. In some embodiments, if the SDT procedure is an RA-SDT procedure, the UE may not monitor the PEI during the SDT procedure.
In some embodiments, the UE may decide during the SDT procedure (e.g., where the UE is configured with PEI (and/or if the PEI includes SI modification and/or ETWS/CMAS indication)) whether to monitor/detect/receive pages (e.g., paging DCI, short message indicator, short message, and/or paging message).
In some embodiments, where the UE is configured with PEI (and/or if PEI includes SI modification and/or ETWS/CMAS indication), the UE may not monitor/detect/receive pages (e.g., paging DCI, short message indicator, short message, and/or paging message) during the SDT procedure.
Preferably, the UE not monitoring/not detecting/not receiving pages (e.g., paging DCI, short message indicator, short message, and/or paging message) may mean that the UE skips/ignores monitoring/detecting/receiving pages (e.g., paging DCI, short message indicator, short message, and/or paging message).
In some embodiments, where the UE is configured with PEI, but the PEI does not include SI modification and/or ETWS/CMAS indication, the UE may monitor/detect/receive pages (e.g., paging DCI, short message indicator, short message, and/or paging message) during the SDT procedure.
In some embodiments, where the UE is not configured with PEI, the UE may monitor/detect/receive pages (e.g., paging DCI, short message indicator, short message, and/or paging message) during the SDT procedure.
SS collision for PEI and SS collision for SDT/other
The UE (e.g., in rrc_inactive/rrc_idle state) may be configured with different PDCCH monitoring occasions for different purposes (e.g., for PEI, for SDT, for paging DCI/short message, for system information, for RA). The PDCCH monitoring occasion may be determined by SS, CORESET and/or some parameters.
1. For paging DCI/short message.
The PDCCH monitoring occasions for paging (e.g., paging occasions) may be decided according to the paging security space (as specified in 3gpp TS 38.213) and the first PDCCH-monitoringOccionofPO and nrofPDCCH-monitoringOccionoPerSSB-InPO (if configured) (as specified in 3gpp TS 38.331).
Specifically, the UE may monitor the PDCCH according to the paging occasion to acquire a system information change indication and/or a PWS notification (e.g., ETWS or CMAS).
2. For system messages.
For SIB1, the PDCCH monitoring occasion may be decided according to searchspace ib 1.
For acquisition of other SI and/or SI messages, PDCCH monitoring occasions may be determined according to searchSpaceOtherSystemInformation and/or searchSpaceSIB 1.
3. For RA.
The RA-SearchSpace may be configured to monitor PDCCH for RA procedure (e.g., for monitoring random access response (Random Access Response, RAR)).
The configuration of PDCCH monitoring occasions for UE monitoring (e.g., when the UE is in rrc_inactive state) may be included in a PDCCH-ConfigCommon IE (e.g., as shown in table 3). The configuration may be controlResourceSetZero, commonControlResourceSet, searchSpaceZero, commonSearchSpaceList, searchSpaceSIB1searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, firstPDCCH-MonitoringOccasionOfPO and/or common SearchSpaceListExt-r16, etc.
TABLE 3 Table 3
Based on 3GPP TS 38.213, a set of PDCCH candidates to be monitored by a UE can be defined from the PDCCH search space set. The set of search spaces may be a set of CSS or a set of UE-specific search spaces (USS). The UE may monitor the PDCCH candidate set in one or more of the following search space sets:
-Type 0-PDCCH CSS set configured by PDCCH-ConfigSIB1 in MIB or by searchSpaceIB 1 in PDCCH-ConfigCommon or by searchSpacezero in PDCCH-ConfigCommon for DCI format with CRC scrambled by SI-RNTI on the primary cell of MCG;
-a Type0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for DCI format with CRC scrambled by SI-RNTI on the primary cell of MCG;
-Type 1-PDCCH CSS set configured by RA-SearchSpace in PDCCH-ConfigCommon for DCI formats with CRC scrambled by RA-RNTI, msgB-RNTI or TC-RNTI on the primary cell;
-Type 2-PDCCH CSS set configured by the pagingsetspace in PDCCH-ConfigCommon for DCI format with CRC scrambled by P-RNTI on the primary cell of MCG;
-a Type3-PDCCH CSS set configured by SearchSpace in PDCCH-Config with searchspactype = typically used in DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, or CI-RNTI, and only for primary cell, C-RNTI, MCS-C-RNTI, CS-RNTI or PS-RNTI; and/or
-a USS set configured by SearchSpace in PDCCH-Config with searchspactype, wherein searchspactype = ue-is specific to a DCI format with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI(s), SL-RNTI, SL-CS-RNTI, or SL semi-persistent scheduling V-RNTI.
For PEI, the UE (e.g., in rrc_inactive/rrc_idle state) may be configured with one or more SSs for PDCCH monitoring.
The SS for PEI may be used to monitor the PDCCH to detect PEI (e.g., before the PO).
The SS of the PEI may be configured in a PEI configuration.
The SS of the PEI may be configured by RRC release messages (with or without suspension configuration) and/or by system information (e.g., SIB1 or "other SI").
The SS of the PEI may be a common search space configured in PDCCH-ConfigCommon, a type 1PDCCH CSS set configured by ra-SearchSpace, a type 3PDCCH CSS set, search space zero, a new common search space set configured by system information (e.g., SIB) or RRC release message, a search space with parameters configured in initial BWP, a digingsearchspace, searchSpace ib1, etc.
For SDT, the UE (e.g., in rrc_inactive/rrc_idle state) may be configured with one or more SSs for PDCCH monitoring (e.g., during an SDT procedure).
The SS of the SDT may be configured as CG-SDT.
The SS for the SDT may be configured in the CG configuration for the SDT and/or in the SDT configuration.
The SS of the SDT may be configured as RA-SDT.
The SS for SDT may be configured in RA configuration for SDT and/or in SDT configuration.
The SS for the SDT may be configured by RRC release message (with or without suspension configuration) and/or by system information (e.g., SIB1 or "other SI").
The SS for SDT may be used to monitor PDCCH to receive Msg2/MsgB/Msg4 during RA-SDT procedure.
The SS for SDT may be used to monitor PDCCH to obtain responses/feedback/scheduling from NW for CG-SDT procedure and/or RA-SDT procedure.
The SS for SDT may be used to monitor PDCCH at timer/window run time.
The timer/window may be a CG-SDT response timer/window.
A timer/window may be used to monitor the response/feedback of the PDCCH (e.g., including ACK/NACK/DFI).
A timer/window may be used to monitor the PDCCH for new transmission/retransmission scheduling from the NW.
The timer/window may be ra-ResponseWindow, msgB-ResponseWindow, ra-ContentionResolutionTimer, configuredGrantTimer, cg-RetransmissionTimer, drx-onDurationTimer, drx-InactivityTimer, drx-remossiontimerdl and/or drx-remossiontimerul.
The timer/window may be an SDT failure detection timer. The timers/windows may be T300, T301, T302, T304, T310, T311, T312, T316, T319, T320, T321, T322, T325, T330, T331, T342, and/or T345.
The timer/window may be a TA timer and/or an SDT TA timer.
The SS for the SDT may be a common SS (e.g., a type 1PDCCH CSS configured by ra-SearchSpace, a type 3PDCCH CSS, and/or a new common SS configured by a system information/RRC release message). The SS for the SDT may be a UE-specific SS (e.g., a UE-specific SS configured from an RRC release message, and/or a UE-specific SS configured from Msg 4/MsgB).
In some examples, different PDCCH monitoring opportunities partially/fully overlap/collide in the time domain (e.g., in the same symbol, slot, subframe, system frame, etc.) and/or in the frequency domain. Fig. 10 shows a timing diagram of overlapping PDCCH monitoring opportunities according to one of the embodiments of the present application. Referring to the embodiment shown in fig. 10, in the time domain, an overlap period occurs between a first PDCCH monitoring occasion (e.g., PDCCH monitoring occasion # 1) and a second PDCCH monitoring occasion (e.g., PDCCH monitoring occasion # 2). More specifically, the first PDCCH monitoring occasion may be configured for SDT. More specifically, the second PDCCH monitoring occasion may be configured for other purposes (e.g., for paging/short messages, for system information, for RA, etc.). During this overlap period, the UE may not be able to monitor both the first PDCCH monitoring occasion and the second PDCCH monitoring occasion (due to UE capability). To solve this problem, some methods are disclosed as follows.
When the UE is configured with at least two PDCCH monitoring occasions, a first PDCCH candidate monitored in a first PDCCH monitoring occasion may be configured for PEI purposes and a second PDCCH candidate monitored in a second PDCCH monitoring occasion may be configured for other purposes (e.g., for SDT, paging/short message, for system information, for RA, etc.).
In some examples, the first PDCCH monitoring occasion (e.g., for PEI) may be configured by the first SS and/or the first CORESET.
The first SS may be a common search space configured in PDCCH-ConfigCommon, a type 1PDCCH CSS set configured by ra-SearchSpace, a type 3PDCCH CSS set, search space zero, a new common search space set configured by system information (e.g., SIB) or RRC release message, a search space with parameters configured in initial BWP, a pagengsearchspace, searchSpace ib1, etc.
The first SS may be a common SS (e.g., a type 1PDCCH CSS configured by ra-SearchSpace, a type 3PDCCH CSS, and/or a new common SS configured according to a system information/RRC release message).
The first SS may be a UE-specific SS (e.g., a UE-specific SS configured from an RRC release message, and/or a UE-specific SS configured from Msg 4/MsgB).
The first SS may be a set of (UE-specific) search spaces configured by configuration for SDT.
The first SS may be a set of search spaces identified as a particular set of SDTs.
The first CORSET may be a common CORESET (e.g., CORESET 0, common control resource set).
In some examples, the second PDCCH monitoring occasion (e.g., for SDT, paging/short message, for system information, for RA, etc.) may be configured by the second SS and/or the second CORESET.
The second SS may be searchSpaceZero, commonSearchSpaceList, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, commonSearchSpaceListExt-r16, etc.
In some implementations, the UE may not desire (by the NW) to configure/provide the first PDCCH monitoring occasion and the second PDCCH monitoring occasion that partially/fully overlap in the time domain (e.g., in the same symbol, slot, subframe, system frame, etc.) and/or in the frequency domain. In other words, the NW may not configure the first and second PDCCH monitoring occasions that partially/completely overlap in the time domain (e.g., in the same symbol, slot, subframe, system frame, etc.) and/or in the frequency domain to the UE.
In some embodiments, the UE may not desire to monitor the first PDCCH monitoring occasion and the second PDCCH monitoring occasion simultaneously. For example, the network may not be able to configure on the first PDCCH monitoring occasion and the second PDCCH monitoring occasion that overlap completely/partially in the time domain.
In some embodiments, the UE may select/prioritize one of the first and second PDCCH monitoring occasions for monitoring in case of partial/complete overlap/collision (e.g., in the same symbol, slot, subframe, system frame, etc.).
In some examples, the UE may select/prioritize the first PDCCH monitoring occasion. For example, in the case of partial/complete overlap/collision of the first PDCCH monitoring occasion and the second PDCCH monitoring occasion (e.g., in the same symbol, slot, subframe, system frame, etc.), the UE may monitor the first PDCCH monitoring occasion. More specifically, the UE may not monitor the second PDCCH monitoring occasion.
In some examples, the UE may select/prioritize the second PDCCH monitoring occasion. For example, in the case of a partial/complete overlap/collision of the first PDCCH monitoring occasion and the second PDCCH monitoring occasion (e.g., in the same symbol, slot, subframe, system frame, etc.), the UE may monitor the second PDCCH monitoring occasion. More specifically, the UE may not monitor the first PDCCH monitoring occasion.
In some embodiments, in case of partial/complete overlap/collision of the first and second PDCCH monitoring occasions (e.g. in the same symbol, slot, subframe, system frame, etc.), the PDCCH monitoring occasions that should be selected/preferentially monitored by the UE may be configured by the network (e.g. by configuration/information elements).
Specifically, if the UE is configured with a configuration/IE indicating a first value, the UE may select/prioritize the first PDCCH monitoring occasion. For example, the UE may monitor a first PDCCH monitoring occasion. More specifically, the UE may not monitor the second PDCCH monitoring occasion.
Specifically, if the UE is configured with a configuration/IE indicating a second value, the UE may select/prioritize the second PDCCH monitoring occasion. For example, the UE may monitor a second PDCCH monitoring occasion. More specifically, the UE may not monitor the first PDCCH monitoring occasion.
In some embodiments, in case of deciding the maximum number of non-overlapping CCEs in each slot and/or the maximum number of PDCCH candidates monitored in each slot (for UEs in rrc_inactive/rrc_idle state):
in some examples, the first PDCCH candidate may be allocated before the second PDCCH candidate.
In some examples, if the DCI format associated with the first PDCCH candidate and the DCI format associated with the second PDCCH candidate have the same size, the UE may receive the first PDCCH candidate and the second PDCCH candidate on the same CCE set, or/and the first PDCCH candidate and the second PDCCH candidate have the same scrambling, the UE may only listen to the first PDCCH candidate.
In some examples, the first PDCCH candidate may always correspond to the lowest SSID.
Fig. 11 is a flow chart illustrating a method/process 1100 for monitoring a TRS according to one embodiment of the present application. In act 1102, the UE receives a TRS configuration from the BS, the configuration indicating one or more TRS resource sets for the UE to monitor for reference signals. In act 1104, the UE decides whether an L1-based availability indication (e.g., a TRS/CSI-RS availability indication) for one or more TRS resource sets is received from the BS. In act 1106, when the UE decides not to receive the L1-based availability indication from the BS, the UE decides that one or more TRS resource sets are not available.
In some examples, when the UE decides that an L1-based availability indication has been received from the BS and that the L1-based availability indication indicates a first value of one or more TRS resource sets, the UE also decides that one or more TRS resource sets are present.
In some examples, the UE further decides that one or more TRS resource sets are present in a number of frames based at least on the validity period and the paging cycle.
In some examples, the validity duration is configured by the BS through SIBs.
In some examples, the TRS resources in the one or more sets of TRS resources include CSI-RS resources.
In some examples, the L1-based availability indication includes a bitmap, each bit of the bitmap being associated with at least one corresponding one of the one or more TRS resource sets.
In some examples, the L1-based availability indication is indicated by the BS through a TRS availability indication included in DCI format 1_0 and a CRC scrambled by the P-RNTI.
In some examples, the L1-based availability indication is indicated by the BS through PEI. The UE monitors the PEI on the PEI search space.
In some examples, the TRS configuration is configured by the BS through SIBs.
In some examples, the UE is in an rrc_idle state or an rrc_inactive state.
Fig. 12 is a block diagram of a node 1200 for wireless communication according to an embodiment of the disclosure.
As shown in fig. 12, node 1200 may include a transceiver 1220, a processor 1228, a memory 1234, one or more presentation components 1238, and at least one antenna 1236. Node 1200 may also include a (Radio Frequency) band module, a BS communication module, a network communication module, and a system communication management module, input/output (I/O) ports, I/O components, and a power supply (not shown in fig. 12).
Each of these components may communicate with each other directly or indirectly through one or more buses 1240. Node 1200 may be a UE or BS performing the various disclosed functions shown in fig. 11 and examples/embodiments of the present application.
Transceiver 1220 may include a transmitter 1222 (with transmit circuitry) and a receiver 1224 (with receive circuitry), and may be configured to transmit and/or receive time and/or frequency resource partition information. Transceiver 1220 may be configured to transmit in different types of subframes and slots, including but not limited to usable, unusable, and flexibly usable subframe and slot formats. Transceiver 1220 may be configured to receive data and control channels.
Node 1200 may include a variety of computer-readable media. Computer readable media can be any medium that can be accessed by node 1200 and includes both volatile (and nonvolatile) media, removable (and non-removable) media. Computer readable media may include computer storage media and communication media. Computer storage media may include volatile (and/or nonvolatile) and removable (and/or non-removable) media implemented in accordance with any method or technology for storage of information such as computer readable media.
Computer storage media may include RAM, ROM, EPROM, EEPROM, flash memory (or other storage technology), CD-ROM, digital Versatile Disks (DVD) (or other optical disk storage), magnetic cassettes, magnetic tape, magnetic disk storage (or other magnetic storage devices), and the like. The computer storage medium does not include a propagated data signal.
Communication media may typically be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. The term "modulated data signal" may mean a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. Communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, rf, infrared and other wireless media. Combinations of any of the disclosed media should be included within the scope of computer readable media.
The memory 1234 may include computer storage media in the form of volatile and/or nonvolatile memory. The memory 1234 may be removable, non-removable, or a combination thereof. For example, the memory 1234 may include solid state memory, a hard disk drive, an optical disk drive, etc., as shown in fig. 12, the memory 1234 may store computer-readable and/or computer-executable instructions 1232 (e.g., software code) configured to, when executed, cause the processor 1228 (e.g., processing circuitry) to perform the various disclosed functions. Alternatively, the instructions 1232 may not be directly executable by the processor 1228, but may be configured to cause the node 1200 (e.g., when compiled and executed) to perform the various disclosed functions.
The processor 1228 may include intelligent hardware devices, central processing units (central processing unit, CPU), microcontrollers, ASICs, and the like. The processor 1228 may include a memory. Processor 1228 may process data 1230 and instructions 1232 received from memory 1234 as well as information received via transceiver 1220, a baseband communication module, and/or a network communication module. Processor 1228 may also process information to be sent to transceiver 1220 for transmission via antenna 1236 and to a network communication module for transmission to a CN.
One or more presentation components 1238 can present data to a person or other device. The presentation component 1238 may include a display device, a speaker, a printing component, a vibrating component, and the like.
Paging mechanism
Paging through DRX
In some embodiments, paging allows the network to reach UEs in rrc_idle and rrc_inactive states through paging messages, and to notify UEs in rrc_idle, rrc_inactive, and rrc_connected states of system information change and ETWS/CMAS indication through short messages. Both paging messages and short messages are addressed on the PDCCH by the P-RNTI, but when the former is sent on the PCCH, the latter is sent directly on the PDCCH.
The UE in rrc_idle state monitors the paging channel for CN initiated paging, while the UE in rrc_inactive state monitors the paging channel for RAN initiated paging. The UE does not continuously monitor the paging channel during paging DRX. Paging DRX is applied to UEs in either the rrc_idle state or the rrc_inactive state, so the UE only needs to monitor the paging channel during one Paging Occasion (PO) per DRX cycle (defined in 3gpp TS 38.304). The paging DRX cycle is configured by the network by:
-broadcasting a default period in the system information for CN initiated paging;
for CN initiated paging, UE specific periods may be configured by NAS signaling;
-configuring UE-specific periods by RRC signaling for RAN-initiated paging.
The UE uses the shortest available DRX cycle. For example, the UE in the rrc_idle state uses the shortest one of the first two periods, and the UE in the rrc_inactive state uses the shortest one of the three periods.
The POs for the CN-initiated paging and RAN-initiated paging UEs are based on the same UE ID, resulting in overlap of the POs for both. The number of different POs in the DRX cycle may be configured by the system information, and the network may allocate the UE to these POs based on the ID of the UE.
The UE in rrc_connected monitors the paging channel in any PO signaled in the system information to obtain SI change indication and PWS notification. In the case of BA, a UE in rrc_connected state may monitor a paging channel on an active BWP with a common search space.
For operation using shared spectrum channel access, the UE may be configured for an additional number of PDCCH monitoring occasions in the PO to monitor for paging. However, when a UE detects a PDCCH transmission in a PO of a UE addressed with a P-RNTI, the UE need not monitor subsequent PDCCH monitoring occasions in the PO.
The UE may apply the DRX mechanism in rrc_idle and rrc_inactive states in order to reduce power consumption. The UE monitors one PO per DRX cycle. The PO is a set of PDCCH monitoring occasions and may include a plurality of slots (e.g., subframes or OFDM symbols) in which paging DCI may be transmitted (defined in 3gpp TS 38.213). A PF is a radio frame and may include one or more POs or starting points of POs.
In multi-beam operation, the UE decides to repeat the same paging message and the same short message in all transmitted beams, and thus selection of a beam for receiving the paging message and the short message is decided to be performed by the UE. The paging messages for RAN-initiated paging and CN-initiated paging are the same.
The UE initiates an RRC connection recovery procedure upon receiving the RAN-initiated page. If the UE receives a CN initiated page in the RRC_INACTIVE state, the UE moves to the RRC_IDLE state and informs the NAS layer.
Paging monitoring occasion (for paging DCI) decision
The paging PFs and POs are determined by the following formula:
the SFN of the PF is determined by the following equation:
-(SFN+PF_offset)mod T＝(T div N)*(UE_ID mod N).
index (i_s), the Index representing PO is determined by the following formula:
-i_s＝floor(UE_ID/N)mod Ns.
the PDCCH monitoring occasions for paging are decided according to the paging security space, as specified in 3gpp TS38.213, and the first PDCCH-monitoringOccasionofpo and nrofPDCCH-monitoringOccasioPerSSB-InPO, if configured, as specified in 3gpp TS 38.331. When searchspace=0 is configured for the pagesearchspace, the PDCCH monitoring occasion for paging is the same as RMSI, as defined in 3gpp TS 38.213.
When searchspace=0 is configured for the pagesearchspace, ns is 1 or 2. When ns=1, there is only one PO in the PF to page from the first PDCCH listening occasion. When ns=2, PO is located in the first half frame (i_s=0) or the second half frame (i_s=1) of the PF.
When a non-0 searchspace is configured for the pagesearchspace, the UE listens to the (i_s+1) th PO. PO is a set of "S X" consecutive PDCCH monitoring occasions, where "S" is the number of actually transmitted SSBs determined from SSB-PositionInBurst in SIB1, and X is nrofPDCCH-MonitoringOccionPerSSB-InPO (if configured) or otherwise equal to 1. The [ X s+k ] PDCCH monitoring occasions for paging in PO correspond to the K-th transmitted SSB, where x=0, 1, …, X-1, k=1, 2, …, S. Paging PDCCH monitoring occasions that do not overlap with UL symbols (determined according to tdd-UL-DL-configuration command) are numbered sequentially starting from the first PDCCH monitoring occasion in the PF for paging, with the numbering starting from zero. When the first PDCCH-MonitoringOccasionofPO exists, the initial PDCCH monitoring time number of the (i_s+1) th PO is the (i_s+1) th value of the first PDCCH-MonitoringOccasionofPO parameter; otherwise, it is equal to i_s×s×x. If X >1, when the UE detects a PDCCH transmission addressed to the P-RNTI within its PO, the UE does not need to monitor the subsequent PDCCH monitoring occasions of the PO.
The PO associated with the PF may start in the PF or after the PF.
The PDCCH monitoring occasion for the PO may span multiple radio frames. When a non-0 SearchSpace is configured for paging-SearchSpace, the PDCCH monitoring opportunity for the PO may span multiple periods of the paging search space.
The following parameters were used for the calculation of PF and i_s described above:
t: the DRX cycle of the UE (if configured by RRC and/or upper layers, T is determined by the shortest one of the UE-specific DRX values and the default DRX value broadcasted in the system information in rrc_idle state, if UE-specific DRX is not configured by upper layers, default values are applied).
N: total number of paging frames in T.
Ns: the paging occasion number of the PF.
Pf_offset: offset for PF determination.
UE_ID:5G-S-TMSI mod 1024。
Parameters Ns, nAndPagingFrameOffset, nrofPDCCH-MonitoringOccasionPerSSB-InPO and the length of the default DRX period are signaled in SIB 1. The values of N and pf_offset are derived from the parameter nandpnagingframeoffset defined in 3gpp TS 38.331. The parameter first-PDCCH-monitoringoccidioofpo is signaled in SIB1 for paging in the initial DL BWP. For paging in DL BWP other than the initial DL BWP, the parameter first-PDCCH-monitoringoccidioofpo is signaled in the corresponding BWP configuration.
If the UE does not have a 5G-S-TMSI, for example when the UE has not been registered with the network, the UE shall use ue_id=0 in the above PF and i_s equations as default identity.
Paging message reception
When the UE receives the paging message, the UE should:
1> if in rrc_idle, the pagerecord is included in the paging message for each PagingRecord, UE:
2> if the UE-Identity contained in the PagingRecord matches the UE Identity allocated by the upper layer:
3> the UE forwards the ue-Identity and the accessType to an upper layer;
1> if in rrc_inactive, pagerecord is included in the paging message for each PagingRecord, UE:
2> if the UE-Identity included in the PagingRecord matches the UE-stored fulll i-RNTI:
3> if the UE is configured by the upper layer to access identity 1:
4> the UE initiates an RRC connection recovery procedure by setting resumeCAuse to mps-PrioritityAccess;
3> otherwise if the UE is configured by the upper layer with access identity 2:
4> the UE initiates an RRC connection recovery procedure by setting resumeCAuse to mcs-PrioritiyAccess;
3> otherwise, if the UE is configured by the upper layer with one or more access identities equal to 11-15:
4> the ue initiates an RRC connection recovery procedure by setting resumecase to highpriorityiaccess;
3> otherwise:
4> UE initiates RRC connection recovery procedure by setting resumeCAuse as mt-Access;
2> otherwise if the UE-Identity contained in the pagengrecord matches the UE Identity allocated by the upper layer:
3> the UE forwards the ue-Identity and the accessType to an upper layer;
3> ue performs an action when transitioning to rrc_idle state with release cause "other".
It will be apparent from this application that the disclosed concepts may be implemented using a variety of techniques without departing from the scope of these concepts. Furthermore, although specific reference has been disclosed to particular embodiments, workers skilled in the art will recognize that changes may be made in form and detail without departing from the scope of the concepts. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive. It should also be understood that the present disclosure is not limited to the particular embodiments disclosed, but is capable of numerous rearrangements, modifications, and substitutions without departing from the scope of the disclosure.
Claims (20)
1. A method for a user equipment UE to monitor a tracking reference signal TRS, the method comprising:
receiving a TRS configuration from a base station BS, the TRS configuration indicating one or more TRS resource sets for the UE monitoring reference signals;
Deciding whether to receive a layer 1L 1-based availability indication for the one or more TRS resource sets from the BS; and
when the UE decides that the layer 1L1 based availability indication has not been received from the BS, it decides that one or more of the TRS resource sets are not available.
2. The method of claim 1, wherein the method further comprises:
when the UE decides that the layer 1L1 based availability indication has been received from the BS and the layer 1L1 based availability indication indicates a first value for the one or more TRS resource sets, it decides that the one or more TRS resource sets are present.
3. The method of claim 2, wherein the method further comprises:
the presence of the one or more TRS resource sets for a plurality of frames is determined based at least on the validity duration and the paging cycle.
4. The method of claim 3, wherein the validity duration is configured by the BS via a system information block, SIB.
5. The method of claim 1, wherein the TRS resources in the one or more sets of TRS resources comprise channel state information reference signal, CSI-RS, resources.
6. The method of claim 1, wherein the layer 1L 1-based availability indication comprises a bitmap, each bit of the bitmap being associated with at least one corresponding one of the one or more TRS resource sets.
7. The method of claim 1, wherein the layer 1L 1-based availability indication is indicated by the BS via a TRS availability indication included in a downlink control information DCI format 1_0, the TRS availability indication having a cyclic redundancy check, CRC, scrambled by a paging radio network temporary identifier, P-RNTI.
8. The method of claim 1, wherein the layer 1L1 based availability indication is indicated by the BS via a paging early indication, PEI, that is monitored by the UE in a PEI search space.
9. The method of claim 1, wherein the TRS configuration is configured by the BS via a system information block SIB.
10. The method of claim 1, wherein the UE is in a radio resource control IDLE rrc_idle state or a radio resource control IDLE INACTIVE state rrc_inactive state.
11. A user equipment, UE, for monitoring a tracking reference signal, TRS, the UE comprising:
At least one processor; and
at least one memory coupled to the at least one processor and storing computer-executable instructions that, when executed by the at least one processor, cause the UE to:
receiving a TRS configuration from a base station BS, the TRS configuration indicating one or more TRS resource sets for the UE monitoring reference signals;
deciding whether to receive a layer 1L 1-based availability indication for the one or more TRS resource sets from the BS; and
when the UE decides that the layer 1L1 based availability indication has not been received from the BS, it decides that one or more of the TRS resource sets are not available.
12. The UE of claim 11, wherein the computer-executable instructions, when executed by the at least one processor, further cause the UE to:
when the UE decides that the layer 1L1 based availability indication has been received from the BS and the layer 1L1 based availability indication indicates a first value for the one or more TRS resource sets, it decides that the one or more TRS resource sets are present.
13. The UE of claim 12, wherein the computer-executable instructions, when executed by the at least one processor, further cause the UE to:
The presence of the one or more TRS resource sets for a plurality of frames is determined based at least on the validity duration and the paging cycle.
14. The UE of claim 13, wherein the validity duration is configured by the BS via a system information block, SIB.
15. The UE of claim 11, wherein the TRS resources in the one or more sets of TRS resources comprise channel state information reference signal, CSI-RS, resources.
16. The UE of claim 11, wherein the layer 1L 1-based availability indication comprises a bitmap, each bit of the bitmap associated with at least one corresponding one of the one or more TRS resource sets.
17. The UE of claim 11, wherein the layer 1L 1-based availability indication is indicated by the BS via a TRS availability indication included in a downlink control information DCI format 1_0, the TRS availability indication having a cyclic redundancy check, CRC, scrambled by a paging radio network temporary identifier, P-RNTI.
18. The UE of claim 11, wherein the layer 1L1 based availability indication is indicated by the BS via a paging early indication, PEI, that is monitored by the UE in a PEI search space.
19. The UE of claim 11, wherein the TRS configuration is configured by the BS via a system information block SIB.
20. The UE of claim 11, wherein the UE is in a radio resource control IDLE rrc_idle state or a radio resource control IDLE INACTIVE state rrc_inactive state.
Applications Claiming Priority (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US63/228986 | 2021-08-03 | ||
| US202163203974P | 2021-08-05 | 2021-08-05 | |
| US63/203974 | 2021-08-05 | ||
| PCT/CN2022/109973 WO2023011524A1 (en) | 2021-08-03 | 2022-08-03 | Method for monitoring tracking reference signal and related device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117796077A true CN117796077A (en) | 2024-03-29 |
Family
ID=90381876
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202280052813.8A Pending CN117796077A (en) | 2021-08-03 | 2022-08-03 | Method for monitoring tracking reference signal and related equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117796077A (en) |
-
2022
- 2022-08-03 CN CN202280052813.8A patent/CN117796077A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113906795B (en) | Method for monitoring paging and apparatus using the same | |
| US11582790B2 (en) | User equipment and method for small data transmission | |
| CN114600502B (en) | Method and user equipment for wireless communication | |
| CN112771911B (en) | Method and device for system information modification and acquisition process | |
| CN112335287B (en) | Method and apparatus for performing cell selection in wireless communication system | |
| US20210099860A1 (en) | Method and apparatus for system information delivery | |
| US20230209464A1 (en) | User equipment and method for power saving in rrc inactive or rrc idle states | |
| KR20230006497A (en) | Small data transmission with Radio Resource Control (RRC) disabled | |
| US20210112590A1 (en) | Method for performing random access procedure and apparatus therefor | |
| CN115004780A (en) | Method and user equipment for sidelink packet switched operation | |
| JP2023518502A (en) | Method and User Equipment for Configured Grant Setup | |
| CN114762407B (en) | Method for monitoring paging occasion and related equipment | |
| US20230397224A1 (en) | User equipment and method for power saving | |
| US20230209462A1 (en) | User equipment and method for power saving | |
| WO2022111542A1 (en) | Method of performing small data transmission in radio resource control inactive state and related device | |
| US20230051117A1 (en) | Method for monitoring tracking reference signal and related device | |
| WO2020187288A1 (en) | System information update in next generation wireless networks | |
| CN117796077A (en) | Method for monitoring tracking reference signal and related equipment | |
| WO2024036444A1 (en) | Power reduction method and apparatus | |
| CN116491192A (en) | User equipment and method for small data transmission |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |