Neighbor cell transmission configuration indicator (TCI) state switch
Patent Information
- Application Number
- IN202317065794
- Authority / Receiving Office
- IN · IN
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-09-29
- Publication Date
- 2026-10-28
- Estimated Expiration
- 2041-04-01
Abstract
Description
[0001] Fifth generation mobile network (5G) is a wireless standard that aims to improveupon data transmission speed, reliability, availability, and more. In 5G new radio (NR), atransmission configuration indication (TCI) state is used to establish the quasi co-location(QCL) connection between a target reference signal (RS) and a source RS. TCI states areconfigured for a physical downlink control channel (PDCCH) or a physical downlink sharedchannel (PDSCH) in order to convey the QCL indication for the respective RS.BRIEF DESCRIPTION OF THE DRAWINGS
[0002] Figure 1 illustrates an example of a network environment, in accordance with someembodiments.
[0003] Figure 2 illustrates an example of a layer | or layer 2 (L1 / L2) inter-cell mobilitybased on a transmission configuration indication (TCI) state switch, in accordance with someembodiments.
[0004] Figure 3 illustrates an example of determining whether a state of a neighbor cell isknown or unknown, in accordance with some embodiments.
[0003] Figure 4 illustrates an example of determining whether a TCI state of a neighborcell is known or unknown, in accordance with some embodiments.
[0006] Figure 5 illustrates another example of determining whether a TCI state of aneighbor cell is known or unknown, in accordance with some embodiments.
[0007] Figure 6 illustrates an cxample of a timeline for a TCI state switch, in accordancewith some embodiments.
[0008] Figure 7 illustrates an example of a sequence diagram between a user equipment(UE) and a network for L1 / L2 inter-cell mobility based on a TCI state switch command, inaccordance with some embodiments.
[0009] Figure 8 illustrates an example of an operational flow / algorithmic structure forL1 / L2 inter-cell mobility based on a TCI state switch command associated with a neighborcell, in accordance with some embodiments.
[0010] Figure 9 illustrates an example of receive components, in accordance with someembodiments.
[0011] Figure 10 illustrates an example of a UE, in accordance with some embodiments.
[0012] Figure 11 illustrates an example of a base station, in accordance with someembodiments.DETAILED DESCRIPTION
[0013] The following detailed description refers to the accompanying drawings. The samereference numbers may be used in different drawings to identify the same or similar elements.In the following description, for purposes of explanation and not limitation, specific detailsare set forth such as particular structures, architectures, interfaces, techniques, etc. in order toprovide a thorough understanding of the various aspects of various embodiments. However, itwill be apparent to those skilled in the art having the benefit of the present disclosure that thevarious aspects of the various embodiments may be practiced in other examples that departfrom these specific details. In certain instances, descriptions of well-known devices, circuits,and methods are omitted so as not to obscure the description of the various embodiments withunnecessary detail. For the purposes of the present document, the phrase "A or B" means (A),(B), or (A and B).
[0014] Generally, a user equipment (UE) may be configured to reccive and transmit in aserving cell, whereby the UE uses a transmission configuration indication (TCI) state for thereception. A neighbor cell may exist. It may be desired to switch this TCT state to a TCT stateof the neighbor cell in order to enable the UE to reccive in the neighbor cell. To do so, a TCIstate switch command can be sent from the network to the UE, requesting the UE to switch tothe neighbor cell's TCI state. In an example, the network can send the TCI state switchcommand by using layer | (L1) signaling (e.g., downlink control information (DCD) or layer2 (L2) signaling (e.g., a media control access (MAC) control element (CE)) to trigger ahandover from the serving cell to the neighbor cell. By using L1 or L2 (L1 / L2) signaling, thehandover can take less time relative to when radio resource control (RRC) reconfigurationsignaling is used.
[0015] This type of TCT switch command can be enabled for inter-frequency and intra-frequency cells. The UE can determine whether the state of the neighbor cell is known orunknown and / or whether the TCI state of the neighbor cell is known or unknown. Such TCIstate switch conditions can impact the total delay time needed to complete the switch to theneighbor cell's TCI state and, in the case of the handover, to complete the handover. Otherfactors can also impact the total delay time and include, for instance, whether a MAC CE orDCTis used for the TCI state switch command, time for timing offset / frequency offset(TO / FO) tracking, time for active bandwidth part (BWP) switch, or UE processing time.Further, the UE can send a random access channel (RACH) message to indicate thecompletion, in which case the total delay time may also depend on RACH occasionuncertainty. During the TCI state switching, the UE interruptions to reception and / ortransmission on another serving component carriers (CC) may be allowed, where the timelength of the interruptions may be based on the numerology or slot length of the other servingCC.
[0016] In addition, the UE can signal its capability to monitor TCI states of neighbor cells.If capable of doing so, the UE maymaintain the TCI state of the neighbor cell in a list ofactive TC] states prior to receiving the TCI state switch command. Further, the UE can signalits capability to perform neighbor cell TCI state switching in support of L1 / L2 centric inter-cell handover.
[0017] The following is a glossary of terms that may be used in this disclosure.
[0018] The term "circuitry" as used herein refers to, is part of, or includes hardwarecomponents such as an electronic circuit, a logic circuit, a processor (shared, dedicated, orgroup) or memory (shared, dedicated, or group), an Application Specific Integrated Circuit(ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), aprogrammable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD),a structured ASIC, or a programmable system-on-a-chip (SoC)), digital signal processors(DSPs), etc., that are configured to provide the described functionality. In someembodiments, the circuitry may execute one or more software or firmware programs toprovide at least some of the described functionality. The term "circuitry" may also refer to acombination of one or more hardware elements (or a combination of circuits used in anelectrical or electronic system) with the program code used to carry out the functionality ofthat program code. In these embodiments, the combination of hardware elements andprogram code may be referred to as a particular type of circuitry.
[0019] The term "processor circuitry" as used herein refers to, is part of, or includescircuitry capable of sequentially and automatically carrying out a sequence of arithmetic orlogical operations, or recording, storing, or transferring digital data. The term "processorcircuitry" may refer to an application processor, baseband processor, a central processing unit(CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwiseoperating computer-execultable instructions, such as program code, software modules, orfunctional processes.
[0020] The term "interface circuitry" as used herein refers to, is part of, or includescircuitry that enables the exchange of information between two or more components ordevices. The term "interface circuitry" may refer to one or more hardware interfaces, forexample, buses, I / O interfaces, peripheral component interfaces, network interface cards, orthe like.
[0021] The term "user equipment" or "UE" as used herein refers to a device with radiocommunication capabilities and may describe a remote user of network resources in acommunications network. The term "user equipment" or "UE" may be consideredsynonymous to, and may be referred to as, clicnt, mobile, mobile device, mobile terminal,user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station,access agent, user agent, receiver, radio equipment, reconfigurable radio equipment,reconfigurable mobile device, etc. Furthermore, the term "user equipment" or "UE" mayinclude any type of wireless / wired device or any computing device including a wirelesscommunications interface.
[0022] The term "base station" as used herein refers to a device with radio communicationcapabilities, that is a network element of a communications network (or, more briefly,network), and that may be configured as an access node in the communications network. AUE's access to the communications network may be managed at least in part by the basestation, whereby the UE connects with the base station to access the communications network.Depending on the radio access technology (RAT), the base station can be referred to as agNodcB (gNB), cNodcB (cNB), access point, etc.
[0023] The term "computer system" as used herein refers to any type of interconnectedelectronic devices, computer devices, or components thereof. Additionally, the term"computer system" or "system" may refer to various components of a computer that arecommunicatively coupled with one another. Furthermore, the term "computer system" or"system" may refer to multiple computer devices or multiple computing systems that arecommunicatively coupled with one another and configured to share computing or networkingresources.
[0024] The term "resource" as used herein refers to a physical or virtual device, a physicalor virtual component within a compuling environment, or a physical or virtual componentwithin a particular device, such as computer devices, mechanical devices, memory space,processor / CPU time, processor / CPU usage, processor and accelerator loads, hardware time orusage, electrical power, input / output operations, ports or network sockets, channel / linkallocation, throughput, memory usage, storage, network, database and applications, workloadunits, or the like. A "hardware resource" may refer to compute, storage, or network resourcesprovided by physical hardware element(s). A "virtualized resource" may refer to compute,storage, or network resources provided by virtualization infrastructure to an application,device, system, etc. The term "network resource" or "communication resource" may refer toresources that are accessible by computer devices / systems via a communications network.The term "system resources" may refer to any kind of shared entities to provide services, andmay include computing or network resources. System resources may be considered as a set ofcoherent functions, network data objects or services, accessible through a server where suchsystem resources reside on a single host or multiple hosts and are clearly identifiable.
[0025] The term "channel" as used herein refers to any transmission medium, eithertangible or intangible, which is used to communicate data or a data stream. The term"channel" may be synonymous with or equivalent to "communications channel," "datacommunications channel," "transmission channel," "data transmission channel," "accesschannel," "data access channel," "link," "data link," "carrier," "radio-frequency carrier," orany other like term denoting a pathway or medium through which data is communicated.Additionally, the term "link" as used herein refers to a connection between two devices forthe purpose of transmitting and receiving information.
[0026] The terms "instantiate," "instantiation," and the like as used herein refer to thecreation of an instance. An "instance" also refers to a concrete occurrence of an object, whichmay occur, for example, during execution of program code.
[0027] The term "connected" may mean that two or more elements, at a commoncommunication protocol layer, have an established signaling relationship with one anotherover a communication channel, link, interface, or reference point.
[0028] The term "network element" as used herein refers to physical or virtualizedequipment or infrastructure used to provide wired or wireless communication networkservices. The term "network element" may be considered synonymous to or referred to as anetworked computer, networking hardware, network equipment, network node, virtualizednetwork function, or the like.
[0029] The term "information element" refers to a structural element containing one ormore fields. The term "field" refers to individual contents of an information element, or adata element that contains content. An information element may include one or moreadditional information elements.
[0030] Figure 1 illustrates a network environment 100, in accordance with someembodiments. The network environment 100 may include a UE 104 and a gNB 108. ThegNB 108 may be a base station that provides a wireless access cell, for example, a ThirdGeneration Partnership Project (3GPP) New Radio (NR) cell, through which the UE 104 maycommunicate with the gNB 108. The UE 104 and the gNB 108 may communicate over an airinterface compatible with 3GPP technical specifications such as those that define FifthGeneration (5G) NR system standards.
[0031] The gNB 108 may transmit information (for example, data and control signaling) inthe downlink direction by mapping logical channels on the transport channels, and transportchannels onto physical channels. The logical channels may transfer data between a radio linkcontrol (RLC) and MAC layers; the transport channels may transfer data between the MACand PHY layers; and the physical channels may transfer information across the air interface.The physical channels may include a physical broadcast channel (PBCH), a physicaldownlink control channel (PDCCH), and a physical downlink shared channel (PDSCH).
[0032] The PBCH may be used to broadcast system information that the UE 104 may usefor initial access to a serving cell. The PBCH may be transmitted along with physicalsynchronization signals (PSS) and secondary synchronization signals (SSS) in asynchronization signal ($S) / PBCH block. The $S / PBCH blocks (SSBs) may be used by theUE 104 during a cell search procedure (including cell selection and reselection) and for beamselection.
[0033] The PDSCH may be used to transfer end-user application data, signaling radiobearer (SRB) messages, system information messages (other than, for example, MIB), andpaging messages.
[0034] The PDCCH may transfer DCI that is used by a scheduler of the gNB 108 toallocate both uplink and downlink resources. The DCT may also be used to provide uplinkpower control commands, configure a slot format, or indicate that preemption has occurred.
[0035] The gNB 108 may also transmit various reference signals to the UE 104. Thereference signals may include demodulation reference signals (DMRSs) for the PBCH,PDCCH, and PDSCH. The UE 104 may compare a received version of the DMRS with aknown DMRS sequence that was transmitted to estimate an impact of the propagationchannel. The UE 104 may then apply an inverse of the propagation channel during ademodulation process of a corresponding physical channel transmission.
[0036] The reference signals may also include channel status information reference signals(CSI-RS). The CSI-RS may be a multi-purpose downlink transmission that may be used forCSI reporting, beam management, connected mode mobility, radio link failure detection,beam failure detection and recovery, and fine tuning of time and frequency synchronization.
[0037] The reference signals and information from the physical channels may be mapped toresources of a resource grid. There is one resource grid for a given antenna port, subcarrierspacing configuration, and transmission direction (for example, downlink or uplink). Thebasic unit of an NR downlink resource grid may be a resource element, which may be definedby one subcarrier in the frequency domain and one orthogonal frequency divisionmultiplexing (OFDM) symbol in the time domain. Twelve consecutive subcarriers in thefrequency domain may compose a physical resource block (PRB). A resource clement group(REG) may include one PRB in the frequency domain and one OFDM symbol in the timedomain, for example, twelve resource elements. A control channel element (CCE) mayrepresent a group of resources used to transmit PDCCH. One CCE may be mapped to anumber of REGs, for example, six REGs.
[0038] The UE 104 may transmit data and control information to the gNB 108 usingphysical uplink channels. Different types of physical uplink channels are possible including,for instance, a physical uplink control channel (PUCCH) and a physical uplink sharedchannel (PUSCH). Whereas the PUCCH carries control information from the UE 104 to thegNB 108, such as uplink control information (UCD, the PUSCH carries data traffic (e.g., end-user application data) and can carry UCI.
[0039] The UE 104 and the gNB 108 may perform beam management operations toidentify and maintain desired beams for transmission in the uplink and downlink directions.The beam management may be applied to both PDSCH and PDCCH in the downlinkdirection, and PUSCH and PUCCH in the uplink direction.
[0040] In an example, communications with the gNB 108 and / or the base station can usechannels in the frequency range 1 (FR1) band (between 40 Megahertz (MHz) and 7,125 MHz)and / or frequency range 2 (FR2) band (between 24,250 MHz and 52,600 MHz). The FR1band includes a licensed band and an unlicensed band. The NR unlicensed band (NR-U)includes a frequency spectrum that is shared with other types of radio access technologics(RATS) (e.g., LTE-LAA, WiFi, etc.). A listen-before-talk (LBT) procedure can be used toavoid or minimize collision between the different RATs in the NR-U, whereby a deviceshould apply a clear channel assessment (CCA) check before using the channel.
[0041] As further illustrated in FIG. 1, the network environment 100 may further include abase station 112 with which the UE 104 may also connect. The base station 112 supports thesame RAT as the gNB 108 (e.g., the base station 112 is also a gNB). Additionally oralternatively, the base station 112 supports a different RAT (e.g., Long-Term Evolution (LTE)eNB).
[0042] In an example, the UE 104 supports carrier aggregation (CA), whereby the UE 104can connect and exchange data simultaneously over multiple component carriers (CCs) withthe gNB 108 and / or the base station 112. The CCs can belong to the same frequency band, inwhich case they are referred to as intra-band CCs. Intra-band CCs can be contiguous or non-contiguous. The CCs can also belong to different frequency bands, in which case they arereferred to as inter-band CCs. A serving cell can be configured for the UE 104 to use a CC. Aserving cell can be a primary (PCell), a primary secondary cell (PSCell), or a secondary cell(SCell). Multiple SCells can be activated via an SCcll activation procedures where thecomponent carriers of these serving cells can be intra-band contiguous, intra-band noon-contiguous, or inter-band. The serving cells can be collocated or non-collocated.
[0043] Transmissions that use different antenna ports may experience different radiochannels. However, in some situations, different antenna ports may share common radiochannel characteristics. For example, different antenna ports may have similar Doppler shifts,Doppler spreads, average delay, delay spread, or spatial receive parameters (for example,properties associated with a downlink received signal angle of arrival at a UE). Antenna portsthat share one or more of these large-scale radio channel characteristics may be said to bequasi co-located with one another. 3GPP has specified four types of QCL to indicate whichparticular channel characteristics are shared. In QCL Type A, antenna ports share Dopplershift, Doppler spread, average delay, and delay spread. In QCL Type B, antenna ports shareDoppler shift and Doppler spread. In QCL Type C, antenna ports share Doppler shift andaverage delay. In QCL Type D, antenna ports share spatial receiver parameters.
[0044] The gNB 108 may provide TCT state information to the UE 104 to indicate QCLrelationships between antenna ports used for reference signals (for example, synchronizationsignal / PBCH or CSI-RS) and downlink data or control signaling, for example, PDSCH orPDCCH. The gNB 108 may use a combination of RRC signaling, MAC control elementsignaling, and DCI to inform the VE 104 of these QCL relationships.
[0045] TCI states are configured for PDCCH, PDSCH and CSI-RS in order to convey theQCL indication for the respective reference signal (RS). In FR1 QCL Types A-C and in FR2QCL types A-D are applicable. The QCL Type D for FR2 indicates thatPDCCH / PDSCH / CSIL-RS is transmitted with the same spatial filter as the reference signalassociated with that TCI. In FR2, the network can indicate a transmit beam change forPDSCH or PDCCH by switching the TCI state.
[0046] The UE 104 may be configured with a TCI list for PDSCH and PDCCH via RRC.The TCI states for PDCCH is a subset of those for PDSCH. For PDCCH, the networkconfigures the active TCI state via MAC CE. RRC can configure up to one-hundred twenty-eight TCI states for PDSCH. The UE can have up to eight activated TCI states via MAC CE,although the embodiments of the present disclosure are not limited as such.
[0047] When the UE 104 is configured with the higher layer parameter tei-Present(InDCIthat is set as 'enabled' for the CORESET scheduling the PDSCH, the TCI field is present inDCT format 1_1. If the scheduling offset between scheduling and PDSCH is larger thanThreshold-Sched-Offset and TCI field is present, the TCI state for PDSCH is indicated viaDCL If the tci-PresentlnDC] is not configured or PDSCH is scheduled using DCI format 1_0or the scheduling offset between PDCCH and PDSCH is smaller than Threshold-Sched-Offset, PDSCH follows the TCI of PDCCH. Thresh-old-Sched-Offset is based on UEcapability timeDuration-ForQCL.
[0048] TCI state change and corresponding beam switch may be initiated via MAC CE orDCI When TCI for PDSCH is indicated by DCI, the TCI state or beam switch can beconfigured via DCI. DCI based TCI state switch is applicable to PDSCH. When PDSCHfollows the TCI state of PDCCH, [for a beam switch, the TCI state of PDCCH is first initiatedvia MAC CE. Hence, MAC CE-based TCI state switch can be applicable to PDCCH.
[0049] When the network activates a new TCI state via MAC CE for PDCCH or via DCIfor PDSCH, the UE 104 is allowed some time to prepare to receive with the new TCI state. Inorder to successfully receive with the new TCI state, the UE 104 needs to know the receive(RX) beam corresponding to the new TCT state and the relevant time offset / frequency offset(TO / FO). The network could indicate a TCI state change for PDCCH via MAC CE and forPDSCH via DCI. As further described herein below, this change can be to a TCI state of aneighbor cell and can occur within the context of a handover from a serving cell associatedwith the current TCI state to the neighbor cell that is the target of the TCI state switch.
[0050] Figure 2 illustrates an example of a layer 1 or layer 2 (L1 / L2) inter-cell mobilitybased on a transmission configuration indication (TCI) state switch, in accordance with someembodiments. In the illustration of Figure 2, the L1 / L2 inter-cell mobility refers to ahandover from a serving cell to a neighbor cell, where this handover is triggered with L1signaling or L2 signaling, rather than RRC reconfiguration signaling.
[0051] A handover can be performed to move communications of a UE 210 from a currentserving cell 220 to a neighbor cell 230 (e.g., an adjacent cell), while the UE 210 movesthrough the network coverage area. The handover can be an inter-frequency handover (e.g.,the two cells 220 and 230 use the same frequency band) or an intra-frequency handover (e.g.,the two cells 220 and 230 use different frequency bands). The L1 signaling can be DCIindicating a TCI state change, whereas the L2 signaling can be MAC CE indicating a TCIstage change. In both cases, the target cell associated with the TCI stage change is theneighbor cell 230.
[0052] In an example, the network sends in the serving cell 220, a TCI state switchcommand 222 to the UE 104. This state switch command 222 triggers a switch from thecurrent TCI state associated with the serving cell 220 to the TCI state of the neighbor cell 230.This TCI state switch command 222 can be DCI or MAC CE. Upon completion of the switch,the neighbor cell's 230 TCI state is usable by the UE 104 for communications, including atleast reception, in the neighbor cell 230. For instance, the TCI state switch command 222represents a trigger for the handover.
[0053] The neighbor cell 230 can be indicated (e.g., its cell ID) to the UE 210 via RRCsignaling or the TCI state switch command 222 (e.g., the DCI or MAC CE). Further, prior tothe TCI state switch command 222 being sent, the network can configure the UE 210 withparameters of the neighbor cell 230 (e.g., radio bearer configuration, measurementconfiguration, SCell group configuration, and the like). This configuration can beaccomplished via RRC signaling other than a RRC reconfiguration message.
[0054] A RS 321 can be sent in the neighbor cell 230. Upon completion of the TCT stateswitch (or, similarly, the handover), the UE 210 can receive the RS 321 with the TCIindicated by the TCI state associated with the neighbor cell 230.
[0055] As such, L1 / L2 based handover can be achieved via DCI or MAC-CE TCI Stateswitch. Doing so can reduce handover time compared to L3 / RRC based handover. The TCIstate switch can support an intra-frequency handover and an inter-frequency handover. Asfurther described herein below, the completion of the TCI switch from the serving cell 220 tothe neighbor cell 230 (or, similarly, the L1 / L2 based handover) can be performed within atotal delay time that is subject to whether the state of the neighbor cell is known or unknownand / or whether the state of the neighbor cell's 230 TCI state is known or unknown, amongother factors. The TCI state switching can impact transmit or receive operations of the UE210 on other serving CCs, in which case permitted interruptions may be defined.
[0056] Figure 3 illustrates an example of determining whether a state of a neighbor cell isknown or unknown, in accordance with some embodiments. Generally, the neighbor cell is atarget cell. The state of the neighbor cell is known to a UE 310 if, at least, this target cell hasbeen detected previously by the UE 310. Otherwise, the state of the neighbor cell is unknownto the UE 310. This type of state condition is illustrated in Figure 3. Additional stateconditions may be defined, whereby, for instance, the state is known if an RX beam usable bythe UE 310 to receive in the neighbor cell is also known to the UE 310 and / or if the TCT stateof the neighbor cell is part of active states maintained by the UE 310.
[0057] In an cxample, a base station 320 (e.g., a gNB) provides communications to UEs ina neighbor cell. The UE 310 is communicating with another base station 330 (e.g., a gNB) ofa serving cell. No handover of the UE 310 from the serving cell to the neighbor cell may haveoccurred yet.
[0058] The state of the neighbor cell is known to the UE 310 if the neighbor cell is detectedby the UE 310 (illustrated as a cell detection 301 in Figure 3). Otherwise, the state isunknown. The cell detection 310 can include, for instance, receiving and detecting asynchronization signal 322 from the base station 322 (e.g., a primary a synchronization signal(PSS) or a secondary synchronization signal (SSS) transmitted in an SSB), detecting an SSBindex, and / or performing an SSB measurement.
[0059] In the illustration of Figure 3, subsequent to the cell detection 301, the network maytrigger a switch of a TCI state from the serving cell to the neighbor cell. The start of thisswitch is illustrated as a TCI state switch start 302 and corresponds to receiving a TCI stateswitch command 332. In an example, the TCI state switch command 332 can be sent from thenetwork via the base station 330, whereby the base station 330 transmits it to the UE 310 inDCT or MAC CE.
[0060] Next, and as part of performing the TCI state switch to the neighbor cell, the UE310 determines the state of the neighbor cell (illustrated as a TCI state switch condition 303,which in the context of Figure 3 includes determining the state condition of the neighbor cell(e.g., being known or unknown to the UE 310)). Here, this state is known 312 because the UE310 has previously detected the neighbor cell 320 (e.g., per the cell detection 301). However,if the neighbor cell was not detected prior to receiving the TCI switch command 322, the UE310 would determine that the neighbor cell's state is unknown.
[0061] Figure 4 illustrates an example of determining whether a TCI state of a neighborcell is known or unknown, in accordance with some embodiments. Generally, the neighborcell is a target cell and its TCI state is a target TCI state. The target TCI state is known to aUE 410 if, at least, an RX beam usable by the UE 410 to receive on the target cell is knownto the VE 410. Otherwise, the target TCI state is unknown to the UE 410. The RX beam isknown to the UE 410 if the UE 410 has measured and report a measurement on an RS (e.g.,an L1-RSRP measurement) for the target TCI state within a certain time prior to receiving aTCT state switch command associated with switching the UE 410 to the target TCT state. Thistype of state condition is illustrated in Figure 4. Additional state conditions may be defined,whereby, for instance, the target TCI state is known if the state of the neighbor cell is known(e.g., the neighbor cell is detected) and / or if the target TCI state is part of active statesmaintained by the UE 410.
[0062] In an cxample, a base station 420 (c.g., a gNB) provides communications to UEs ina neighbor cell. The UE 410 is communicating with another base station 430 (e.g., a gNB) ofa serving cell. No handover of the UE 410 from the serving cell to the neighbor cell may haveoccurred yet.
[0063] The neighbor cell is known to the UE 410 if the neighbor cell is detected by the UE410 (illustrated as a cell detection 401 in Figure 4). Otherwise, the neighbor cell is unknownto the UE 410. The cell detection 410 can include, for instance, receiving and detecting asynchronization signal 422 from the base station 422 (e.g.,a PSS or an SSS transmitted in anSSB), detecting an SSB index, and / or performing an SSB measurement.
[0064] In the illustration of Figure 4, an RX beam detection 402 includes the UE 410detecting whether an RX beam is in the neighbor cell is known to the UE 410. When the RXbeam detection 402 occurs within a certain time period prior to receiving a TCI switchcommand 432, the TCT state of the neighbor cell may be known to the UE 402. This RXbeam detection 402 can include, for instance, the UE 410 recciving an RS 424 from the basestation 420, performing measurements (e.g., LI-RSRP) on the RS, and reporting thesemeasurements to the network.
[0065] Subsequent to the RX beam detection 402, the network may trigger a switch of aTCI state from the serving cell to the neighbor cell. The start of this switch is illustrated as aTCI state switch start 403 and corresponds to receiving a TCI state switch command 432. Inan example, the TCI state switch command 432 can be sent from the network via the basestation 430, whereby the base station 430 transmits it to the UE 410 in DCI or MAC CE.
[0066] Next, and as part of performing the TC] state switch to the neighbor cell, the UE410 determines the whether the TCI state of the neighbor cell is known or unknown(illustrated as a TCI state switch condition 404). Here, the TCI state of the neighbor cell isknown 412 because the UE 410 has previously detected the neighbor cell 420 (e.g., per thecell detection 401) and has previously detected the RX beam within a certain time periodprior to receiving the TCI state switch command 432. However, if the neighbor cell was notdetected prior to receiving the TCT switch command 422, or if the RX beam was unknown ordetected long ago (c.g., longer than the certain time period), the UE 410 would determine thatthe neighbor cell's TCI state is unknown. In this approach, if the target TCI state is known,the UE 510 can determine implicitly that the state of the neighbor cell is also known.
[0067] In an example, the neighbor's cell TCT state is known to the UE 410 only if thefollowing conditions are met. During the period from the last transmission of an RS resourceused for LI-RSRP measurement reporting for the TCI state to the completion of active TCIstate switch, where the RS resource for L1-RSRP measurement is the RS in TCI state orQCLed to the TCI state: (7) the TCI state switch command 432 is received within a certaintime (e.g., 1,280 ms) upon the last transmission of the RS resource for beam reporting ormeasurement, (11) the UE 410 has sent at Ieast one L1-RSRP report for the TCI state beforethe TCI state switch command 432, (iii) the TCI state remains detectable during the TCI stateswitching period, (iv) the SSB associated with the TCT state remain detectable during the TCIswitching period, and (y) the signal to noise ratio (SNR) of the TCI state is equal or largerthan a certain value (e.g., -3dB). If any of these conditions is not met, the neighbor's cell TCIstate is unknown to the UE 410.
[0068] Figure 5 illustrates another example of determining whether a TCT state of aneighbor cell is known or unknown, in accordance with some embodiments. Generally, theneighbor cell is a target cell and its TCI state is a target TCI state. The target TCI state isknown to a UE 510 if, at least, the target TCI state is identified in a list of active TCI statesthat the UE 510 maintains.
[0069] In an example, the UE 510 monitors multiple TCI state (illustrated as TCI statemonitoring 501). The network configures TCI states for the UE 510 and activates some ofconfigured TCI states. For instance, RRC signaling can be used to configure up to one-hundred twenty-eight TCI states for PDSCH. MAC CE is then used to activate up to eight ofthe one-hundred twenty-eight TCI states. The UE 510 maintains a list 512 identifying theseeight active TCI states. Further, the UE 510 may have indicated, to the network, UEcapability of monitoring TCI states of neighbor cells. In this case, the RRC signaling mayhave included the target TCT state in the configuration, and the MAC CE may have activatedthe TCI state.
[0070] In the illustration of Figure 5, subsequent to the TCI state monitoring 501, thenetwork may trigger a switch of a TCI state from the serving cell to the neighbor cell. Thestart of this switch is illustrated as a TCT state switch start 502 and corresponds to receiving aTCI state switch command 532. In an example, the TCI state switch command 332 can besent from the network via a base station 520 of the serving cell, whereby the base station 520transmits it to the UE 510 in DCI or MAC CE.
[0071] Next, and as part of performing the TCT state switch to the neighbor cell, the UE510 determines the whether the TCI state of the neighbor cell is known or unknown(illustrated as a TCI state switch condition 503). Here, the TCI state of the neighbor cell isknown 514 because the UE 510 this target TCI state is one of the active TCI states identifiedin the list 512. However, if the target TCI state was not an active TCI state, the UE 410 mayhave determine that target TCI state is unknown. In this approach, if the target TCI state isknown, the UE 510 can determine implicitly that the state of the neighbor cell is also known.
[0072] Figure 6 illustrates an example of a timeline for a TCI state switch, in accordancewith some embodiments. The timeline 600 includes a total delay time 610 between receptionof a TCT state switch command 620 to completion 630 of a TCI state switch, where the TCTstate switch is for switching to a TC] state of a neighbor cell. In particular, when the networkactivates a new TCI state via MAC CE for PDCCH or via DCI for PDSCH, a UE is allowedsome time to prepare to receive with the new TCT state. The total delay time 610 represents afirst period of time needed by the UE to do so and can depend on a number of factors, such aswhether the neighbor cell is known or unknown to the UE, whether the neighbor cell's TCIstate is known or unknown to the UE, whether MAC CE or DCT is used for the activation,whether TO / FO tracking is needed, whether an active BWP switch is needed, UE processingtime, and whether a RACH message 640 is sent or not.
[0073] The total delay time 610 can be shorter than a second period of time that is an upperbound on the total delay time 610. For example, the second period of time is a predefinedmaximum time for the switch and corresponds to the worst case scenario (e.g., the total delaytime 610 is equal or less than a certain maximum allowable time, where this upper boundcorresponds to the state of the neighbor cell being unknown, the neighbor cell's TCI statebeing unknown, the use of MAC CE, the need for an active BWP switch, the need for TO / FOtracking the transmission of a RACH message, and the like).
[0074] Further, the UE can send a RACH message 640 to the network upon the completion630 of the TCI state switch. In particular, the UE can determine the first available physicalrandom access channel (PRACH) occasion to send the RACH message 640. Uncertaintyabout the timing of the PRACH occasion can exist and is shown as uncertainty time 642 inFigure 6 (e.g., the time needed to send the RACH message 640). In an example, the processof performing the TCI state switch includes sending the RACH message 640. In this case, theuncertainty time 642 can be part of the total delay time 610. In either cases, sending theRACH message 640 can be beneficial because the exact length of the total delay ime 610varies depending on the above factors. Thus, the RACH message 640 can indicate to thecompletion 630 to the network such to reduce the impact of this variability and enable thetransmission to the UE without the need to wait until the end of the maximum time. If thisTCT state switch is part of a handover, the RACH message 640 may alternatively be sent atthe completion of the handover.
[0075] In ancxample, the total delay time 610 includes MAC CE processing time or DCIparsing time, a time for TO / FO tracking, time for RX bean refinement, time for cellidentification, time for BWP switch, UE processing time, and / or the uncertainty time 642.The MAC CE processing time is used when the TC] switch command is MAC CE and can bedefined as "Traro + predefined time value (e.g., three milliseconds)." Tyarg is the time(which can be defined in a number of slots) needed to send acknowledgement / negativeacknowledgement (ACK / NACK) in response to the MAC CE. The DCI parsing time is usedif the TCI switch command is DCI. This DCI parsing time can have a predefined time value(e.g., six-hundred microseconds).
[0076] The time for TO / FO tracking is included in the total delay time 610 only if TO / FOtracking is needed before using the TCI state of the neighbor cell. This can be the case whenthis TCI state is not part of the active TCI state list monitored by UE (e.g., the list 512 ofFigure 5). The time for TO / FO tracking can be defined as "Tyra-ssp + Tssp-proe', Where "Thirst.SSB' 1s time to receive the first SSB, "Tssp-proc" is ime needed for processing this SSB.
[0077] The for RX bean refinement is included in the total delay ime 610 only if the TCIstate of the neighbor cell is unknown. The time for RX beam refinement can be defined as"Tri-rsrp', which is the measurement period for performing L1-RSRP measurement.
[0078] The time for cell identification is included in the total delay time 610 only if thestate of the neighbor cell is unknown (e.g., this target cell for the TCI state switch has notbeen detected by the UE). Cell identification time includes PSS / SSS detection, SSBmeasurement time, and time for SSB index detection. Accordingly, the time for cellidentification can be "Tidentity intra_without index" Specified in section 9.2.5.1 of 3GPP TS 38.133V17.0.0 (2021-01) for intra frequency neighbor cell in FR2 if deriveSSB-IndexFromCell isenabled and the target ccll is on the same frequency as serving cell. The time for cellidentification can be "Tidentity intra_with index' Specified in the same for intra frequency neighborcell in FR1 and FR2 if deriveSSB-IndexFromCell is not enabled. Alternatively, the time forcell identification can be "Tidentity inter_with_index" Specified in section 9.3.4 of 3GPP TS 38.133V 17.0.0 (2021-01) for inter-frequency neighbor cell.
[0079] Incase the neighbor cell is in a different frequency layer (inter- frequency) or thebandwidth of initial or active BWP of the neighbor cell is different from the serving cell,additional time for BWP switch is included in the total delay time 610. The time for BWPswitch can be defined as based on a timer or a DCI-based BWP switching delay for singlecomponent carrier similar to the definition in section 8.6.2 of 3GPP TS 38.133 V17.0.0(2021-01).
[0080] The UE processing time represents additional processing ime the UE may need toreceive and apply all the parameters and configuration to complete a handover to theneighbor cell. This time can be predefined to a certain value (e.g., up to ten milliseconds) andis included in the total delay time 610 when the TCI state switch is used as a trigger for thehandover.
[0081] As explained herein above, the completion 630 of the TCT State switch to theneighbor cell can be indicated by a RACH message 640 such that the UE can start reccivingon the TCI State of the neighbor cell. The uncertainty to transmit the RACH message 640 isthe uncertainty in acquiring the first available PRACH occasion in the neihbor cell which canbe up to the summation of SSB to PRACH occasion association period and a predefined timevalue (¢e.g., a few milliseconds). This uncertainty time 642 is included in the total delay time610 when RACH messaging is used to indicate completion of TCI state switching.
[0082] To illustrate, the MAC CE processing time, the DCT parsing time, the RX beamrefinement time, and the TO / FO tracking time can be expressed in the total delay ime 610 asfollowing. Upon receiving the TCI state switch command in slot n, the UE should be able toreceive PDCCH with the target TCI state of the neighbor cell in which TCI state switchoccurs at the first slot that is after slot n+ (THARQO + BN Seeremeey Tursep*K1 + TOK (Taste.SSB + TSSB-proc) / NR slot length)*K2+ TDCL parsing Time*K3. The UE should be able to receivePDCCH with the old TCI state until slot n+ THARQ + 3N subframe,μ. Similar definilions can beused to include the times of the other factors, whereby a binary multiple "K" can be used perfactor to account for the corresponding time depending on whether the correspondingcondition is met or not.
[0083] K1 is "0" if the TCI state of the neighbor cell is known; otherwise, K1 is "1". K2 is"1" when MAC CE is used; otherwise K2 1s "0." Conversely, K3 is "1" if DCT is used and,otherwise, K3 is "0". Tyarg is the timing between DL data transmission andacknowledgement. Trirs-ssp is time to first SSB transmission after MAC CE command isdecoded by the UE; The SSB shall be the QCL-TypeA or QCL-TypeC to target TCI state.Tssp-proe = 2 ms. TO, = 1 if target TCI state is not in the active TCI state list for PDSCH, "0"otherwise. T 11-rspp is the time for Rx beam refinement. Ta-«-ssp is time to first SSBtransmission after L1-RSRP measurement when TCI state switching involves QCL-TypcD.Trist-ssp is time to first SSB transmission after MAC CE command is decoded by the VE forother QCL types.
[0084] Within the total delay time 610, one or more interruptions 650 of one or moreoperations (c.g., reccive and / or transmit opcrations) related to one or more other serving CCscan occur. If so, interruption time 652 can be defined as the maximum allowable time for theinterruption(s) 650. In an example, the TCI state switch to the neighbor cell can cause aninterruption on another serving component carrier if any of the following scenarios occur: (i)the switch is accompanied with a subcarrier spacing (SCS) change (e.g., the neighbor celluses a CC having an SCS different from that of the CC of the serving cell in the followingcases), (ii) a bandwidth change or a center frequency change (e.g., the CC of the neighbor cellhas a different bandwidth or uses a different center frequency than the serving CC), or (iii)the UE does not support a measurement gap per frequency range (e.g., per-FR gap). Any ofthese scenarios, or other scenarios impacting receive or transmit operations (e.g., by needingadjustment to the receiver chain and / or transmit change), may cause the interruption to theother serving CC. As such, the UE should be able to support the interruption, whereby thisinterruption can be time length of the interruption is bounded by the interruption time 652.The interruption time 652 can be similarly defined as the time allowed for an active BWPswitch. An example for defining the interruption time 652 is shown in Table 1 below. Inparticular, the length of the interruption time 652 can depend on the numerology or a slotlength of the other serving CC that is impacted by the interruption. For instance, if the otherserving CC has a zero for its numerology, the interruption lime 652 can set to one slot, andthis slot is equal to one milliseconds. This interruption should also allowed only during thetotal delay time 610 for the neighbor cell on all other serving CCs.Table 1.
[0085] Figure 7 illustrates an cxample of a sequence diagram 700 between a UE 710 and anetwork 720 for L1 / L2 inter-cell mobility based on a TCI state switch command, inaccordance with some embodiments. Communications of the UE 710 with the network 720can be carricd via one or morc basc stations of the nctwork 720. The UE 710 can be inaserving cell provided by a base station and using a TCI state of the serving cell. The TCI stateswitch command can be used for a handover of the UE 710 to a neighbor cell (e.g., providedby the same base station or a different base station of the network 720), whereby the neighborcell's TCI state is the target TCI state of the switch.
[0086] In an example, the sequence diagram 700 includes the UE 710 sending a first UEcapability (e.g., tci-StateSwitch-neighborCell) to the network 720 (e.g. before the handover),whereby the first UE capabilily indicates a capability of the UE 710 for neighbor cell TCIstate switching only or for neighbor cell TCI state switching in support of handovers that aretriggered by TCI state switch commands. For example, tci-StateSwitch-neighborCellindicates UE's 710 capability to support TCI State switching for neighbor cell in support ofan L1 / L2 centric inter-cell handover. This UE capability could be mandatory. Further, tci-StateSwitch-neighborCell can signal this switching capability per band.
[0087] The sequence diagram 700 also includes the UE 710 sending a second UEcapability (e.g., tci-State-neighborCell) to the network 720 (e.g. before the handover),whereby the first UE capability indicates a capability of the UE 710 for neighbor cell TCIstate monitoring only or for neighbor ccll TCI state monitoring in support of TCI stateswitching. This capability signaling can be mandatory if UE indicates support of TCI Stateswitching for neighbor cell per the first UE capability. Further, tci-State-neighborCell cansignal this monitoring capability per band. for neighbor cell TC] state monitoring. Anexample illustration of tci-State-neighborCell is shown below. If the UE supports thismonitoring capability, the network 720 may configure the UE 720 to maintain the TCI stateof the neighbor cell in a list of active TCI states.tci-State-neighborCellDefines support of TCI-States for PDCCH / PDSCH for neighbor cell. The capabilitysignalling comprises the following parameters:- maxNumberConfiguredT Cistates PerCC-neighborCell indicates the maximumnumber of configured TCI-states per CC for PDCCH / PDSCH.- maxNumberActiveT CI-PerBWP-neighborCell indicates the maximum number ofactivated TCT-states per BWP per CC, including control and data for neighbor cell.
[0088] As further illustrated in Figure 7, the sequence diagram 700 includes the network720 sending configuration information about the neighbor cell. For example, theconfiguration information can define parameters for detecting the neighbor cell, performingmeasurements on signals sent for the neighbor cell, and any other information needed forconnecting or performing a handover to the neighbor cell. Such information can configure theUE 710 to perform measurement and reporting including, for instance, any or a combinationof L1-RSRP, Layer 3 (L3)-RSRP, time- or spatial-domain-filtered L1-RSRP, or L1-SINR.Further, this information can configure the UE 710 to send a RACH message [or indicalingthe completion of a TCI state switch or handover. This can include an indication of a specificuplink beam for RACH or, alternatively, a candidate set of uplink beams for the RACH. Inaddition, the configuration information can configure the neighbor cell's TCI state for the VE710 and indicate whether this TCT state should be activated. In an example, the configurationinformation can be sent via RRC signaling (other than an RRC Reconfiguration signaling)and / or L2 signaling (other than or the same as a MAC CE for a TCI state switch).
[0089] At some point, and as illustrated with the fourth step in the sequence diagram 700,the network 720 sends an L1 / L2 TCI state switch command to the UE 710. The L1 / L2 TCTstale switch command can be a MAC CE or DCI and can, for instance, indicate the neighborcell and the target TCI state. Depending on the configuration information, this L1 / L2 TCIstate switch command can also indicate the UL beam for the RACH.
[0090] In response to the L1 / L2 TCT state switch command, the sequence diagram 700includes the UE 710 performing a TCI state switch process from the TC] state of the servingcell to the TCI state of the neighbor cell. This process can include determining TCI stateswitch conditions, such as whether the state of the neighbor cell is known or unknown to theUE 710 and whether the neighbor cell's TCI state is known or unknown to the UE 710,performing measurements, performing tracking, and the like. The process may be completedwithin a total delay time.
[0091] The sequence diagram 700 can also include the UE 710 sending a TCI state switchcompletion message upon completion of the TCI state switch process (or completion of thehandover). The TCI state switch completion message can be a RACH message sent on a ULbeam of the serving cell or the neighbor cell depending on, for example, how the network 720configures the UE 710.
[0092] Figure 8 illustrates an example of an operational flow / algorithmic structure 800 forL1 / L2 inter-cell mobility based on a TCI state switch command, in accordance with someembodiments. A UE can implement the operational flow / algorithmic structure 800 to performa TCI state switch associated with a neighbor cell. This switch may, but need not, be part of ahandover from a serving cell to the neighbor cell. The operation flow / algorithmic structure800 may be performed or implemented by the UE such as, for example, the UE 104, 310, 410,510, 710, 310, 410, 1000, or components thereof, for example, processors 1004. The UE cancommunicate with a network by being communicatively coupled with one more base stations,each providing a cell.
[0093] The opcration flow / algorithmic structure 800 may include, at 802, sending, to thenetwork , UE capability information indicating a capability of the UE for neighbor cell TCIstate monitoring. For example, this UE capability information includes tci-State-neighborCell.
[0094] The operation flow / algorithmic structure 800 may include, at 804, sending, to thenetwork, UE capability information indicating a capability of the UE for neighbor cell TCIstate switching in support of handovers that are triggered by TCI state switch commands. Forexample, this UE capability information includes tci-StateSwitch-neighborCell.
[0093] The operation flow / algorithmic structure 800 may include, at 806, receiving, fromthe network, RRC configuration of the neighbor cell. For example, the RRC configurationincludes information to configure the UE to perform L1-RSRP, L3-RSRP, time- or spatial-domain-filtered L1-RSRP, or L1-SINR measurements on RS of the neighbor cell and to senda RACH message on a UL beam, among other things.
[0096] The operation flow / algorithmic structure 800 may include, at 808, recciving, fromthe network while the UE is connected to the serving cell (e.g., by using a serving CCprovided by a base station of the serving cell), a TCI state switch command associated withthe neighbor cell. The TCI switch command can be MAC CE or DCI that triggers a switch toa TCI state of the neighbor cell.
[0097] The operation flow / algorithmic structure 800 may include, at 810, determining aTCT state switch condition associated with the neighbor cell. The TCT state switch conditionindicates at least one of whether a state of the neighbor cell is known or unknown to the UE,or whether the TCI state of the neighbor cell is known or unknown to the UE. As described inconnection with Figures 3-5, different definitions can be used to enable this determination.
[0098] The operation flow / algorithmic structure 800 may include, at 812, completing aswitch to the TCI state of the neighbor cell within a first period of time or a second period oftime based on at least the TCI state switch condition. For example, the first period can be atotal delay time that depends on the determined state condition in addition to, for instance,whether MAC CE or DCT is used to trigger the switching, whether TO / FO tracking is needed,whether an active BWP switch is needed, UE processing time, and whether a RACH messageis to be sent or not. The TCI state switching can include performing detecting the ncighborcell, performing the needed measurements per the RRC configuration, and the like.
[0099] The operation flow / algorithmic structure 800 may include, at 814, sending, to thenetwork, a RACH message indicating at least one of a completion of the switch to the TCTstate of the neighbor cell or a capability of the UE to receive signals using the TCI state of theneighbor cell. The capability indication can correspond to indicating that the handover iscomplete.
[0100] Figure 9 illustrates receive components 900 of the UE 104 in accordance with someembodiments. The receive components 900 may include an antenna pancl 904 that includes anumber of antenna elements. The panel 904 is shown with four antenna elements, but otherembodiments may include other numbers.
[0101] The antenna panel 904 may be coupled to analog beamforming (BF) componentsthat include a number of phase shifters 908(1) - 908(4). The phase shifters 908(1) - 908(4)may be coupled with a radio-frequency (RF) chain 912. The RF chain 912 may amplify areceive analog RF signal, down-convert the RF signal to baseband, and convert the analogbaseband signal to a digital baseband signal that may be provided to a baseband processor forfurther processing.
[0102] In various embodiments, control circuitry, which may reside in a basebandprocessor, may provide BF weights (for cxample W1 - W4), which may represent phase shiftvalues, to the phase shifters 908(1) - 908(4) to provide a receive beam at the antenna panel904. These BF weights may be determined based on the channel-based beamforming.
[0103] Figure 10 illustrates a UE 1000 in accordance with some embodiments. The UE1000 may be similar to and substantially interchangeable with UE 104 of Figure 1.
[0104] Similar to that described above with respect to UE 104, the UE 1000 may be anymobile or non-mobile computing device, such as, for example, mobile phones, computers,tablets, industrial wireless sensors (for example, microphones, carbon dioxide sensors,pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laserscanners, fluid level sensors, inventory sensors, electric voltage / current meters, actuators,etc.), video surveillance / monitoring devices (for example, cameras, video cameras, etc.),wearable devices, or relaxed-IoT devices. In some embodiments, the UE may be a reducedcapacity UE or NR-Light UE.
[0103] The UE 1000 may include processors 1004, RF interface circuitry 1008,memory / storage 1012, user interface 1016, sensors 1020, driver circuitry 1022, powermanagement integrated circuit (PMIC) 1024, and battery 1028. The components of the UE1000 may be implemented as integrated circuits (ICs), portions thereof, discrete electronicdevices, or other modules, logic, hardware, software, firmware, or a combination thereof. Theblock diagram of Figure 10 is intended to show a high-level view of some of the componentsof the UE 1000. However, some of the components shown may be omitted, additionalcomponents may be present, and different arrangements of the components shown may occurin other implementations.
[0106] The components of the UE 1000 may be coupled with various other componentsover one or more interconnects 1032, which may represent any type of interface, input / output,bus (local, system, or expansion), transmission line, trace, optical connection, etc. that allowsvarious circuit components (on common or different chips or chipsets) to interact with oneanother.
[0107] The processors 1004 may include processor circuitry such as, for example,baseband processor circuitry (BB) 1004A, central processor unit circuitry (CPU) 1004B, andgraphics processor unit circuitry (GPU) 1004C. The processors 1004 may include any type ofcircuitry or processor circuitry that executes or otherwise operates computer-executableinstructions, such as program code, software modules, or functional processes frommemory / storage 1012 to cause the VE 1000 to perform operations as described herein.
[0108] In some embodiments, the baseband processor circuitry LOO4A may access acommunication protocol stack 1036 in the memory / storage 1012 to communicate over a3GPP compatible network. In general, the baseband processor circuitry 1004A may accessthe communication protocol stack to: perform user plane functions at a PHY layer, MAClayer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control planefunctions at a PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and a non-accessstratum "NAS" layer. In some embodiments, the PHY layer operations mayadditionally / alternatively be performed by the components of the RF interface circuitry 1008.
[0109] The bascband processor circuitry 1004A may gencrate or process bascband signalsor waveforms that carry information in 3GPP-compatible networks. In some embodiments,the waveforms for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink ordownlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.
[0110] The bascband processor circuitry 1004A may also access group information 1024from memory / storage 1012 to determine search space groups in which a number ofrepetitions of a PDCCH may be transmitted.
[0111] The memory / storage 1012 may include any type of volatile or non-volatile memorythat may be distributed throughout the UE 1000. In some embodiments, some of thememory / storage 1012 may be located on the processors 1004 themselves (for example, L1and L2 cache), while other memory / storage 1012 is external to the processors 1004 butaccessible thereto via a memory interface. The memory / storage 1012 may include anysuitable volatile or non-volatile memory such as, but not limited to, dynamic random accessmemory (DRAM), static random access memory (SRAM), erasable programmable read onlymemory (EPROM), electrically erasable programmable read only memory (EEPROM), Flashmemory, solid-state memory, or any other type of memory device technology.
[0112] The RF interface circuitry 1008 may include transceiver circuitry and a radiofrequency front module (RFEM) that allows the UE 1000 to communicate with other devicesover a radio access network. The RF interface circuitry 1008 may include various elementsarranged in transmit or receive paths. These clements may include, for example, switches,mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.
[0113] In the receive path, the RFEM may receive a radiated signal from an air interfacevia an antenna 1024 and proceed to filter and amplify (with a low-noise amplifier) the signal.The signal may be provided to a receiver of the transceiver that down-converts the RF signalinto a baseband signal that is provided to the baseband processor of the processors 1004.
[0114] In the transmit path, the transmitter of the transceiver up-converts the basebandsignal received from the baseband processor and provides the RF signal to the RFEM. TheRFEM may amplify the RF signal through a power amplifier prior to the signal beingradiated across the air interface via the antenna 1024.
[0115] In various embodiments, the RF interface circuitry 1008 may be configured totransmit / receive signals in a manner compatible with NR access technologies.
[0116] The antenna 1024 may include a number of antenna elements that each convertelectrical signals into radio waves to travel through the air and to convert received radiowaves into electrical signals. The antenna elements may be arranged into one or moreantenna panels. The antenna 1024 may have antenna panels that are omnidirectional,directional, or a combination thereof to enable beamforming and multiple input, multipleoutput communications. The antenna 1024 may include microstrip antennas, printed antennasfabricated on the surface of one or more printed circuit boards, patch antennas, phased arrayantennas, etc. The antenna 1024 may have one or more panels designed for specificfrequency bands including bands in FR1 or FR2.
[0117] The user interface circuitry 1016 includes various input / output (I / O) devicesdesigned to enable user interaction with the UE 1000. The user interface 1016 includes inputdevice circuitry and output device circuitry. Input device circuitry includes any physical orvirtual means for accepting an input including, inter alia, one or more physical or virtualbuttons (for example, a resect button), a physical keyboard, keypad, mousc, touchpad,touchscreen, microphones, scanner, headset, or the like. The output device circuitry includesany physical or virtual means for showing information or otherwise conveying information,such as sensor readings, actuator position(s), or other like information. Output devicecircuitry may include any number or combinations of audio or visual display, including, interalia, one or more simple visual outputs / indicators (for example, binary status indicators suchas light emitting diodes (LEDs) and multi-character visual outputs, or more complex outputssuch as display devices or touchscreens (for example, liquid crystal displays (LCDs), LEDdisplays, quantum dot displays, projectors, etc.), with the output of characters, graphics,multimedia objects, and the like being generated or produced from the operation of the UE1000.
[0118] The sensors 1020 may include devices, modules, or subsystems whose purpose is todetect events or changes in its environment and send the information (sensor data) about thedetected events to some other device, module, subsystem, etc. Examples of such sensorsinclude, inter alia, inerlia measurement unils comprising accelerometers; gyroscopes; ormagnetometers; microelectromechanical systems or nanoelectromechanical systemscomprising 3-axis accelerometers; 3-axis gyroscopes; or magnetometers; level sensors; flowsensors; temperature sensors (for example, thermistors); pressure sensors; barometricpressure sensors; gravimeters; altimeters; image capture devices (for example; cameras orIensless apertures); light detection and ranging scnsors; proximity sensors (for example,infrared radiation detector and the like); depth sensors; ambient light sensors; ultrasonictransceivers; microphones or other like audio capture devices; etc.
[0119] The driver circuitry 1022 may include software and hardware elements that operateto control particular devices that are embedded in the VE 1000, attached to the VE 1000, orotherwise communicatively coupled with the UE 1000. The driver circuitry 1022 may includeindividual drivers allowing other components to interact with or control various input / output(I / O) devices that may be present within, or connected to, the UE 1000. For example, drivercircuitry 1022 may include a display driver to control and allow access to a display device, atouchscreen driver to control and allow access to a touchscreen interface, sensor drivers toobtain sensor readings of sensor circuitry 1020 and control and allow access to sensorcircuitry 1020, drivers to obtain actuator positions of electro-mechanic components or controland allow access to the clectro-mechanic components, a camera driver to control and allowaccess to an capture device, audio drivers to control and allow access to oneor more audio devices.
[0120] The PMIC 1024 may manage power provided to various components of the UE1000. In particular, with respect to the processors 1004, the PMIC 1024 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
[0121] In some embodiments, the PMIC 1024 may control, or otherwise be part of, variouspower saving mechanisms of the UE 1000. For example, if the platform UE is in anRRC_Connected state, where it is still connected to the RAN node as it expects to receivetraffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) aftera period of inactivity. During this state, the UE 1000 may power down for brief intervals oftime and thus save power. If there is no data traffic activity for an extended period of time,then the UE 1000 may transition off to an RRC_Idle state, where it disconnects from thenetwork and does not perform operations such as channel quality feedback, handover, etc.The UE 1000 goes into a very low power state and it performs paging where again itperiodically wakes up to listen to the network and then powers down again. The UE 1000may not receive data in this state; in order to receive data, it must transition back toRRC_Connected state. An additional power saving mode may allow a device to beunavailable to the network for periods longer than a paging interval (ranging from seconds toa few hours). During this time, the device is totally unreachable to the network and maypower down completely. Any data sent during this time incurs a large delay and it is assumedthe delay is acceptable.
[0122] A battery 1028 may power the VE 1000, although in some examples the UE 1000may be mounted deployed in a fixed location, and may have a power supply coupled to anelectrical grid. The battery 1028 may be a lithium ion battery, a metal-air battery, such as azinc-air battery, an aluminum-air battery, a lithium-air ballery, and the like. In someimplementations, such as in vehicle-based applications, the battery 1028 may be a typicalIcad-acid automotive battery.
[0123] Figure 11 illustrates a gNB 1100 in accordance with some embodiments. The gNBnode 1100 may be similar to and substantially interchangeable with gNB 98. A base station,such as the base station 112, can have the same or similar components as the gNB 1100.
[0124] The gNB 1100 may include processors 1104, RF interface circuitry 1108, corenetwork (CN) interface circuitry 1112, and memory / storage circuitry 1116.
[0125] The components of the gNB 1100 may be coupled with various other componentsover one or more interconnects 1128.
[0126] The processors 1104, RF interface circuitry 1108, memory / storage circuitry 1116(including communication protocol stack 1110), antenna 1124, and interconnects 1128 maybe similar to like-named elements shown and described with respect to Figure 9.
[0127] The CN interface circuitry 1112 may provide connectivity to a core network, forexample, a 5" Generation Core network (5GC) using a 5GC-compatible network interfaceprotocol such as carrier Ethernet protocols, or some other suitable protocol. Networkconnectivity may be provided to / from the gNB 1100 via a fiber optic or wireless backhaul.The CN interface circuitry 1112 may include one or more dedicated processors or FPGAs tocommunicate using one or more of the aforementioned protocols. In some implementations,the CN interface circuitry 1112 may include multiple controllers to provide connectivity toother networks using the same or different protocols.
[0128] It is well understood that the use of personally identifiable information shouldfollow privacy policies and practices that are generally recognized as meeting or exceedingindustry or governmental requirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handled so as to minimizerisks of unintentional or unauthorized access or use, and the nature of authorized use shouldbe clearly indicated to users.
[0129] For one or more embodiments, at least one of the components set forth in one ormore of the preceding figures may be configured to perform one or more operations,techniques, processes, or methods as set forth in the example section below. For example, thebaseband circuitry as described above in connection with one or more of the precedingfigures may be configured to operate in accordance with one or more of the examples setforth below. For another cxample, circuitry associated with a UE, base station, nctworkelement, etc. as described above in connection with one or more of the preceding figures maybe configured to operate in accordance with one or more of the examples set forth below inthe example section.Examples
[0130] In the following sections, further exemplary embodiments are provided.
[0131] Example 1 includes a method. The method is implemented on a user equipment(UE). The method comprises: receiving, from the network while the UE is connected to aserving cell, a transmission configuration indicator (TCI) state switch command associatedwith a neighbor cell; determining a TCI state switch condition associated with the neighborcell, the TCI state switch condition indicating at least one of: whether a state of the neighborcell is known or unknown to the UE, or whether a TCT state of the neighbor cell is known orunknown to the UE; and completing a switch to the TCI state of the neighbor cell within afirst period of time or a sccond period of time based on at Icast the TCI state switch condition.
[0132] Example 2 includes a method of example 1, whercin the first period of time isshorter than the second period of time, wherein the second period of time is a predefinedmaximum delay time for the switch, and wherein the switch is completed within the firstperiod of time based on at Icast one of the state of the neighbor cell or the TCI state beingknown.
[0133] Example 3 includes a method of any preceding examples 1-2, wherein the TCI stateswitch command comprises a downlink control information (DCT) or a media access control(MAC) control element (CE) requesting the switch to the TCI state.
[0134] Example 4 includes a method of example 3, wherein the DCI or the MAC CEtriggers a handover from the serving cell to the neighbor cell based on the switch to the TCIstate, and wherein the serving cell and the neighbor cell have a same frequency or differentfrequencies.
[0135] Example 5 includes a method of any preceding examples 1-4, wherein the state ofthe neighbor cell is determined to be known upon a detection by the UE of the neighbor cell.
[0136] Example 6 includes a method of example 5 further comprising: prior to receivingthe TCI state switch command: receiving, from the network, a radio resource control (RRC)configuration of the neighbor cell; and detecting at least a primary synchronization signal(PSS) or a secondary synchronization signal (SSS) of the neighbor cell.
[0137] Example 7 includes a method of any preceding examples 1-6, wherein the TCI stateof the neighbor cell is determined to be known upon a detection by the UE that a receive (RX)beam from the neighbor cell is known, wherein the RX beam is used for reception from theneighbor cell of a reference signal (RS) associated with the TCI state of the neighbor cell.
[0138] Example 8 includes a method of example 7 further comprising: determining that theRX beam is known by at least determining that the UE has measured and reported a layer 1(L1) measurement on the RS within a predefined time prior to receiving the TCI state switchcommand.
[0139] Example 9 includes a method of any preceding examples 1-8, wherein the TCT stateof the neighbor cell is determined to be known a detection by the EU of the neighbor cell andupon a detection by the UE that a receive (RX) beam from the neighbor cell is known.
[0140] Example 10 includes a method of any preceding examples 1-9, wherein the firstperiod of time is a total delay time for the switch, wherein the second period of time is anupper bound on the total delay time, wherein the total delay time is longer when the state ofthe neighbor cell is unknown relative to when the state of the neighbor cell is known, andwherein the total delay time is longer when the TCI state is unknown relative to when theTCI state is known.
[0141] Example 11 includes a method of any preceding examples 1-10, wherein the firstperiod of time is a total delay time for the switch, wherein the TCI state switch commandcomprises either a downlink control information (DCI) or a media access control (MAC)control element (CE) requesting the switch to the TCI state, and wherein the total delay imeis longer when the TCT state switch command comprises the MAC CE relative to when theTCI state switch command comprises the DCI.
[0142] Example 12 includes a method of any preceding examples 1-11, wherein the firstperiod of time is a total delay time for the switch, and the method further comprisingmaintaining a list of active TCT states; and determining whether the TCI state of the neighborcell is one of the active TCI states, whercin the total delay time is shorter when the TC] stateis one of the active TCI states relative to when the TCI state is not one of the active TCIStates.
[0143] Example 13 includes a method of any preceding examples 1-12, wherein the firstperiod of time is a total delay time for the switch, whercin the state of the neighbor cell isdetected to be unknown, and wherein the total delay time comprises a time to complete a cellidentification of the neighbor cell.
[0144] Example 14 includes a method of any preceding examples 1-13, wherein the firstperiod of time is a total delay time for the switch, whercin the neighbor cell has at Icast one ofa different frequency or a different bandwidth part (BWP) from the serving cell, and whereinthe total delay time comprises a time to complete a BWP switch.
[0145] Example 15 includes a method of any preceding examples 1-14, wherein the firstperiod of time is a total delay time for the switch, wherein the TCI state switch commandtriggers a handover from the serving cell to the neighbor cell, and wherein the total delaytime comprises UE processing time to complete the handover.
[0146] Example 16 includes a method of any preceding examples 1-15 further comprising:sending, to the network, a random access channel (RACH) message indicating at least one of:a completion of the switch to the TCT state of the neighbor cell or a completion of a handoverto the neighbor cell.
[0147] Example 17 includes a method of example 16, whercin the first period of time is atotal delay time for the switch, wherein the total delay time comprises time to acquire a firstavailable physical random access channel (PRACH) occasion.
[0148] Example 18 includes a method of example 16, wherein the RACH message is senton an uplink (UL) beam, wherein the UL beam is configured in a radio resource control(RRC) configuration and activated by the TCI state switch command.
[0149] Example 19 includes a method of example 16, wherein the RACH message is senton an uplink (UL) beam, wherein the UL beam is configured by the TC] state switchcommand.
[0150] Example 20 includes a method of any examples 1-19, wherein completing theswitch to the TCI state causes an interruption of a process on a component carrier (CC) basedon the UE not supporting a measurement gap per frequency range or in the neighbor cellhaving a different subcarrier frequency, a different bandwidth, or a diffcrent center frequencyfrom the serving cell.
[01351] Example 21 includes a method of example 20, wherein the interruption is associatedwith a total interruption time, and wherein the total interruption time is based on anumerology or a slot length of the component carrier.
[0152] Example 22 includes a method of any examples 1-21 further comprising: sending,to the network and prior to receiving the TCI state switch command, UE capabilityinformation indicating a capability of the UE for neighbor cell TCI state monitoring.
[0153] Example 23 includes a method of example 22 further comprising: maintaining theTCI state of the neighbor cell in a list of active TCI states based on the capability of the UE.
[0154] Example 24 includes a method of example 22, wherein the UE capabilityinformation indicates the capability per frequency band.
[0155] Example 25 includes a method of any examples 1-24 further comprising: sending,to the nctwork and prior to receiving the TCI state switch command, UE capabilityinformation indicating a capability of the UE for neighbor cell TCI state switching in supportof handovers that are triggered by TCI state switch commands.
[0156] Example 26 includes a method of example 25, wherein the UE capabilityinformation indicates the capability per frequency band.
[0157] Example 27 includes a UE comprising one or more processors and one or morememories storing computer-readable instructions that, upon execution by the one or moreprocessors, configure the UE to perform one or more elements of a method described in orrelated to any of the examples 1-26.
[0158] Example 28 includes a UE comprising means to perform one or more clements of amethod described in or related to any of the examples 1-26.
[0159] Example 29 includes one or more non-transitory computer-readable media storinginstructions, that upon execution on a user equipment (UE), cause the UE to perform one ormore clements of a method described in or related to any of the cxamples 1-26.
[0160] Example 30 includes a UE comprising logic, modules, or circuitry to perform onc ormore elements of a method described in or related to any of the examples 1-26.
[0161] Any of the above-described examples may be combined with any other example (orcombination of examples), unless explicitly stated otherwise. The foregoing description ofone or more implementations provides illustration and description, but is not intended to beexhaustive or to limit the scope of embodiments to the precise form disclosed. Modificationsand variations are possible in light of the above teachings or may be acquired from practice ofvarious embodiments.
[0162] Although the embodiments above have been described in considerable detail,numerous variations and modifications will become apparent to those skilled in the art oncethe above disclosure is fully appreciated. It is intended that the following claims beinterpreted to embrace all such variations and modifications.
Claims
1. A method implemented on a user equipment (UE) that is communicatively coupled with a network, the method comprising: receiving, from the network while the UE is connected to a serving cell, a transmission configuration indicator (TCI) state switch command associated with a neighbor cell; determining a TCI state switch condition associated with the neighbor cell, the TCI state switch condition indicating at least one of: whether a state of the neighbor cell is known or unknown to the UE, or whether a TCI state of the neighbor cell is known or unknown to the UE; and completing a switch to the TCT state of the neighbor cell within a first period of time or a second period of time based on at least the TCI state switch condition.
2. The method of claim 1, wherein the first period of time is shorter than the second period of time, wherein the second period of time is a predefined maximum delay time for the switch, and wherein the switch is completed within the first period of time based on at least one of the state of the neighbor cell or the TCI state being known.
3. The method of claim 1, wherein the TCT state switch command comprises a downlink control information (DCI) or a media access control (MAC) control element (CE) requesting the switch to the TCI state.
4. The method of claim 3, wherein the DCI or the MAC CE triggers a handover from the serving cell to the neighbor cell based on the switch to the TCI state and wherein the serving cell and the neighbor cell have a same frequency or different frequencies.
5. The method of claim 1, wherein the state of the neighbor cell is determined to be known upon a detection by the UE of the neighbor cell.
6. The method of claim 5 further comprising: prior to receiving the TCI state switch command: receiving, from the network, a radio resource control (RRC) configuration of the neighbor cell; and detecting at Ieast a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) of the neighbor cell.
7. The method of claim 1, wherein the TCT state of the neighbor cell is determined to be known upon a detection by the UE that a receive (RX) beam from the neighbor cell is known, wherein the RX beam is used for reception from the neighbor cell of a reference signal (RS) associated with the TCI state of the neighbor cell.
8. The method of claim 7 further comprising: determining that the RX beam is known by at least determining that the UE has measured and reported a layer 1 (L1) measurement on the RS within a predefined time prior to receiving the TCI state switch command.
9. The method of any of claims 1-8, wherein the TCI state of the neighbor cell is determined to be known a detection by the EU of the neighbor cell and upon a detection by the UE that a receive (RX) beam from the neighbor cell is known.
10. A user equipment (UE) comprising: one or more processors; and one or more memories storing computer-readable instructions that, upon execution by the one or more processors, configure the UE to: receive, from a network while the UE is connected to a serving cell, a transmission configuration indicator (TCI) state switch command associated with a neighbor cell; determine a TCI state switch condition associated with the neighbor cell, the TCT state switch condition indicating at least one of: whether a state of the neighbor cell is known or unknown to the UE, or whether a TCI state of the neighbor cell is known or unknown to the UE; and complete a switch to the TCI state of the neighbor cell within a first period of time or a second period of time based on at least the TCI state switch condition.
11. The VE of claim 10, wherein the first period of time is a total delay time for the switch, wherein the second period of time is an upper bound on the total delay time, wherein the total delay time is longer when the state of the neighbor cell is unknown relative to when the state of the neighbor cell is known, and wherein the total delay time is longer when the TCI state is unknown relative to when the TCI state is known.
12. The UE of claim 10, wherein the first period of time is a total delay time for the switch, wherein the TCI state switch command comprises cither a downlink control information (DCD or a media access control (MAC) control element (CE) requesting the switch to the TCI state, and wherein the total delay time is longer when the TCI state switch command comprises the MAC CE relative to when the TCI state switch command comprises the DCI.
13. The VE of claim 10, wherein the first period of time is a total delay time for the switch, wherein the execution of the computer-readable instructions further configures the UE to: maintain a list of active TCI states; and determine whether the TCT state of the neighbor cell is one of the active TCI states, wherein the total delay time is shorter when the TCI state is one of the active TCI states relative to when the TCI state is not one of the active TCI states.
14. The VE of claim 10, wherein the first period of time is a total delay time for the switch, wherein the state of the neighbor cell is detected to be unknown, and wherein the total delay time comprises a time to complete a cell identification of the neighbor cell.
15. The UE of claim 10, wherein the first period of time is a total delay time for the switch, wherein the neighbor cell has at least one of a different frequency or a different bandwidth part (BWP) from the serving cell, and wherein the total delay time comprises a time to complete a BWP switch.
16. The UE of claim 10, wherein the first period of time is a total delay time for the switch, wherein the TCT state switch command triggers a handover from the serving cell to the neighbor cell, and wherein the total delay time comprises UE processing lime to complete the handover.
17. The VE of claim 10, wherein the execution of the computer-readable instructions further configures the UE to: send, to the network, a random access channel (RACH) message indicating at least one of: a completion of the switch to the TCI state of the neighbor cell or a completion of a handover to the neighbor cell.
18. The UE of claim 17, wherein the first period of time is a total delay time for the switch, wherein the total delay time comprises time to acquire a first available physical random access channel (PRACH) occasion.
19. The VE of claim 17, wherein the RACH message is sent on an uplink (UL) beam, wherein the UL beam is configured in a radio resource control (RRC) configuration and activated by the TCI state switch command.
20. The UE of claim 17, wherein the RACH message is sent on an uplink (UL) beam, wherein the UL beam is configured by the TCI state switch command.
21. The UE of any of claims 10-20, wherein completing the switch to the TCI state causes an interruption of a process on a component carrier (CC) based on the UE not supporting a measurement gap per frequency range or on the neighbor cell having a different subcarrier frequency, a different bandwidth, or a different center frequency from the serving cell.
22. The UE of claim 21, wherein the interruption is associated with a total interruption time, and wherein the total interruption time is based on a numerology or a slot length of the component carrier.
23. One or more computer-readable storage media storing instructions that, upon execution on a user equipment (UE), cause the UE to perform operations comprising: receiving, from a network while the UE is connected to a serving cell, a transmission configuration indicator (TCI) state switch command associated with a neighbor cell; determining a TCT state switch condition associated with the neighbor cell, the TCI state switch condition indicating at least one of: whether a state of the neighbor cell is known or unknown to the UE, or whether a TCI state of the neighbor cell is known or unknown to the UE; and completing a switch to the TCI state of the neighbor cell within a first period of time or a second period of time based on at Ieast the TCI state switch condition.
24. The one or more computer-readable storage media of claim 23, wherein the operations further comprise: sending, to the network and prior to receiving the TCI state switch command, UE capability information indicating a capability of the UE for neighbor cell TCI state monitoring.
25. The one or more computer-readable storage media of claim 24, wherein the operations further comprise: maintaining the TCI state of the neighbor cell in a list of active TCI states based on the capability of the UE.
26. The one or more computer-readable storage media of claim 24, wherein the UE capability information indicates the capability per frequency band.
27. The one or more computer-readable storage media of any of claims 23-26, wherein the operations further comprise: sending, to the network and prior to receiving the TCI state switch command, UE capability information indicating a capability of the UE for neighbor cell TCI state switching in support of handovers that are triggered by TCT state switch commands.
28. The one or more computer-readable storage media of claim 27, wherein the UE capability information indicates the capability per frequency band.
