Configurable synchronization signal block (SSB) bandwidth and user equipment (UE) radio resource management (RRM) measurements

Abstract

Provided herein is configurable Synchronization Signal Block (SSB) bandwidth and User Equipment (UE) Radio Resource Management (RRM) measurements. The disclosure provides an apparatus comprising interface circuitry; and processor circuitry coupled with the interface circuitry. The processor circuitry is to: determine a time period for time index detection for an SSB of a deactivated cell with an SSB bandwidth of 12 Physical Resource Blocks (PRBs), based on a Discontinuous Reception (DRX) cycle, a measurement cycle for the deactivated cell, and a Carrier Specific Scaling Factor (CSSF); and perform measurement for the SSB based on the time period for the time index detection. Other embodiments are also disclosed and claimed.

Description

[0001] CONFIGURABLE^SYNCHRONIZATION^SIGNAL^BLOCK^(SSB)^BANDWIDTH^AND^USER^ EQUIPMENT^ (UE)^ RADIO^ RESOURCE^ MANAGEMENT^ (RRM)^MEASUREMENTS^ ^ Cross^References^to^Related^Application^[1]^ This^ application^ is^ based^ on^ and^ claims^ priority^ to^ PCT^ patent^ application^ No.^PCT / CN2024 / 123179^filed^on^October^2,^2024,^which^is^incorporated^herein^by^reference^in^its^ entirety.^ ^ Technical^Field^[2]^ Embodiments^of^the^present^disclosure^generally^relate^to^wireless^communications,^and^in^particular^to^configurable^Synchronization^Signal^Block^(SSB)^bandwidth^and^User^Equipment^ (UE)^Radio^Resource^Management^(RRM)^measurements.^ ^ Background^Art^[3]^ Mobile^communication^has^evolved^significantly^ from^early^voice^systems^ to^ today’s^highly^ sophisticated^ integrated^ communication^ platform.^ The^ next^ generation^ wireless^communication^ system,^ the^ fifth^ generation^ (5G),^ or^ new^ radio^ (NR)^ will^ provide^ access^ to^information^and^sharing^of^data^anywhere,^anytime^by^various^terminals^and^applications.^NR^is^expected^ to^ be^ a^ unified^ network / system^ that^ targets^ to^ meet^ vastly^ different^ and^ sometime^conflicting^performance^dimensions^and^services.^Such^diverse^multi-dimensional^requirements^are^driven^by^different^ services^and^applications.^ In^ general,^NR^may^evolve^based^on^ the^3rd^Generation^Partnership^ Project^ (3GPP)^ Long^Term^Evolution^ (LTE)-Advanced^with^ additional^potential^new^Radio^Access^Technologies^(RATs)^to^enrich^people’s^lives^with^better,^simple^and^ seamless^wireless^connectivity^solutions.^NR^may^enable^everything^connected^by^wireless^and^ deliver^fast,^rich^contents^and^services.^ ^ Brief^Description^of^the^Drawings^[4]^ Embodiments^of^the^disclosure^will^be^illustrated,^by^way^of^example^and^not^limitation,^in^ the^ figures^of^ the^ accompanying^ drawings^ in^which^ like^ reference^numerals^ refer^ to^ similar^elements.^[5]^ Figure^ 1^ illustrates^ an^ example^ architecture^ of^ a^ system^ in^ accordance^ with^some^embodiments^of^the^disclosure.^[6]^ Figure^2^ illustrates^an^example^ flowchart^of^a^method^for^UE^RRM^measurements^ in^accordance^with^some^embodiments^of^the^present^disclosure.^[7]^ Figure^3^illustrates^a^network^in^accordance^with^various^embodiments.^[8]^ Figure^ 4^ schematically^ illustrates^ a^ wireless^ network^ in^ accordance^ with^ various^embodiments.^[9]^ Figure^ 5^ is^ a^ block^ diagram^ illustrating^ components,^ according^ to^ some^ example^embodiments,^able^ to^read^ instructions^ from^a^machine-readable^or^computer-readable^medium^(e.g.,^ a^non-transitory^machine-readable^ storage^medium)^and^perform^any^one^or^more^of^ the^methodologies^discussed^herein.^

[0010] ^ Figure^6^illustrates^a^network^in^accordance^with^various^embodiments.^^ Detailed^Description^of^Embodiments^

[0011] ^ Various^aspects^of^the^illustrative^embodiments^will^be^described^using^terms^commonly^employed^by^those^skilled^in^the^art^to^convey^the^substance^of^the^disclosure^to^others^skilled^in^ the^art.^However,^it^will^be^apparent^to^those^skilled^in^the^art^that^many^alternate^embodiments^ may^be^practiced^using^portions^of^the^described^aspects.^For^purposes^of^explanation,^specific^ numbers,^materials,^and^configurations^are^set^forth^in^order^to^provide^a^thorough^understanding^ of^the^illustrative^embodiments.^However,^it^will^be^apparent^to^those^skilled^in^the^art^that^alternate^ embodiments^may^be^practiced^without^the^specific^details.^In^other^instances,^well^known^features^ may^have^been^omitted^or^simplified^in^order^to^avoid^obscuring^the^illustrative^embodiments.^

[0012] ^ Further,^various^operations^will^be^described^as^multiple^discrete^operations,^in^turn,^in^a^manner^that^is^most^helpful^in^understanding^the^illustrative^embodiments;^however,^the^order^of^description^ should^ not^ be^ construed^ as^ to^ imply^ that^ these^ operations^ are^ necessarily^ order^dependent.^In^particular,^these^operations^need^not^be^performed^in^the^order^of^presentation.^

[0013] ^ The^phrases^“in^an^embodiment”^“in^one^embodiment”^and^“in^some^embodiments”^are^used^repeatedly^herein.^The^phrase^generally^does^not^refer^to^the^same^embodiment;^however,^it^may.^The^ terms^ “comprising,”^ “having,”^ and^ “including”^ are^ synonymous,^ unless^ the^ context^dictates^otherwise.^The^phrases^“A^or^B”^and^“A / B”^mean^“(A),^(B),^or^(A^and^B).”^

[0014] ^ The^present^disclosure^is^generally^related^to^wireless^communication,^cellular^networks,^cloud^ computing,^ edge^ computing,^ cloud^ computing,^ data^ centers,^ network^ topologies,^communication^ system^ implementations,^ network^ convergence,^ artificial^ intelligence^(AI) / machine^ learning^ (ML)^ technologies,^ and^ in^ particular,^ to^ technologies^ for^ configurable^Synchronization^ Signal^ Block^ (SSB)^ bandwidth^ and^ User^ Equipment^ (UE)^ Radio^ Resource^Management^(RRM)^measurements.^^

[0015] ^ Fig.^ 1^ illustrates^ an^ example^ architecture^ of^ a^ system^ 100^ in^ accordance^ with^some^embodiments^of^the^disclosure.^The^following^description^is^provided^for^an^example^system^ 100^that^operates^in^conjunction^with^the^as^Long^Term^Evolution^(LTE)^system^standards^and^the^5G^ or^ New^Radio^ (NR)^ system^ standards^ as^ provided^ by^ 3GPP^ technical^ specifications^ (TS).^However,^the^example^embodiments^are^not^limited^in^this^regard^and^the^described^embodiments^ may^apply^to^other^networks^that^benefit^from^the^principles^described^herein,^such^as^future^3GPP^ systems^(e.g.,^Sixth^Generation^(6G))^systems,^Institute^of^Electrical^and^Electronics^Engineers^(IEEE)^ 802.16^ protocols^ (e.g.,^ Wireless^ metropolitan^ area^ networks^ (MAN),^ Worldwide^Interoperability^for^Microwave^Access^(WiMAX),^etc.),^or^the^like.^^

[0016] ^ As^shown^by^Figure^1,^the^system^100^may^include^UE^101a^and^UE^101b^(collectively^referred^to^as^“UEs^101”^or^“UE^101”).^As^used^herein,^the^term^“user^equipment”^or^“UE”^may^ refer^to^a^device^with^radio^communication^capabilities^and^may^describe^a^remote^user^of^network^ resources^in^a^communications^network.^The^term^“user^equipment”^or^“UE”^may^be^considered^synonymous^ to,^and^may^be^ referred^ to^as^client,^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”^ may^ include^ any^ type^ of^wireless / wired^device^or^any^computing^device^including^a^wireless^communications^interface.^In^this^ example,^ UEs^ 101^ are^ illustrated^ as^ smartphones^ (e.g.,^ handheld^ touchscreen^ mobile^computing^devices^connectable^ to^one^or^more^ cellular^networks),^ but^may^also^ comprise^any^mobile^or^non-mobile^computing^device,^such^as^consumer^electronics^devices,^cellular^phones,^smartphones,^ feature^ phones,^ tablet^ computers,^ wearable^ computer^ devices,^ personal^ digital^assistants^ (PDAs),^ pagers,^ wireless^ handsets,^ desktop^ computers,^ laptop^ computers,^ in-vehicle^infotainment^ (IVI),^ in-car^ entertainment^ (ICE)^ devices,^ an^ Instrument^ Cluster^ (IC),^ head-up^display^(HUD)^devices,^onboard^diagnostic^(OBD)^devices,^dashtop^mobile^equipment^ (DME),^mobile^data^terminals^(MDTs),^Electronic^Engine^Management^System^(EEMS),^electronic / engine^control^ units^ (ECUs),^ electronic / engine^ control^ modules^ (ECMs),^ embedded^ systems,^microcontrollers,^ control^modules,^ engine^management^ systems^ (EMS),^ networked^ or^ “smart”^appliances,^machine-type^communications^(MTC)^devices,^machine-to-machine^(M2M),^Internet^ of^Things^(IoT)^devices,^and / or^the^like.^^

[0017] ^ In^some^embodiments,^any^of^the^UEs^101^can^comprise^an^IoT^UE,^which^may^comprise^a^ network^ access^ layer^ designed^ for^ low-power^ IoT^ applications^ utilizing^ short-lived^ UE^connections.^An^IoT^UE^can^utilize^technologies^such^as^M2M^or^MTC^for^exchanging^data^with^ an^MTC^server^or^device^via^a^PLMN,^Proximity-Based^Service^(ProSe)^or^device-to-device^(D2D)^ communication,^sensor^networks,^or^IoT^networks.^The^M2M^or^MTC^exchange^of^data^may^be^a^machine-initiated^exchange^of^data.^An^IoT^network^describes^ interconnecting^ IoT^UEs,^which^may^include^uniquely^identifiable^embedded^computing^devices^(within^the^Internet^infrastructure),^ with^short-lived^connections.^The^IoT^UEs^may^execute^background^applications^(e.g.,^keep-alive^ messages,^status^updates,^etc.)^to^facilitate^the^connections^of^the^IoT^network.^^

[0018] ^ The^UEs^101^may^be^configured^to^connect,^for^example,^communicatively^couple,^with^a^RAN^110.^In^embodiments,^the^RAN^110^may^be^a^next^generation^(NG)^RAN^or^a^5G^RAN,^an^Evolved^ Universal^ Mobile^ Telecommunications^ System^ (UMTS)^ Terrestrial^ Radio^ Access^Network^ (E-UTRAN),^ or^ a^ legacy^RAN,^ such^ as^ a^UTRAN^ (UMTS^Terrestrial^ Radio^Access^Network)^ or^ GERAN^ (GSM^ (Global^ System^ for^ Mobile^ Communications^ or^ Groupe^ Spécial^Mobile)^EDGE^(GSM^Evolution)^Radio^Access^Network).^As^used^herein,^the^term^“NG^RAN”^ or^the^like^may^refer^to^a^RAN^110^that^operates^in^an^NR^or^5G^system^100,^and^the^term^“E- UTRAN”^or^the^like^may^refer^to^a^RAN^110^that^operates^in^an^LTE^or^4G^system^100.^The^UEs^101^ utilize^ connections^ (or^ channels)^ 103^ and^ 104,^ respectively,^ each^ of^ which^ comprises^ a^physical^communications^interface^or^layer^(discussed^in^further^detail^below).^As^used^herein,^the^ term^“channel”^may^refer^to^any^transmission^medium,^either^tangible^or^intangible,^which^is^used^to^ communicate^ data^ or^ a^ data^ stream.^The^ term^ “channel”^ may^ be^ synonymous^ with^ and / or^equivalent^to^“communications^channel,”^“data^communications^channel,”^“transmission^channel,”^ “data^transmission^channel,”^“access^channel,”^“data^access^channel,”^“link,”^“data^link,”^“carrier,”^ “radiofrequency^carrier,”^and / or^any^other^like^term^denoting^a^pathway^or^medium^through^which^ data^is^communicated.^Additionally,^the^term^“link”^may^refer^to^a^connection^between^two^devices^through^ a^ Radio^ Access^ Technology^ (RAT)^ for^ the^ purpose^ of^ transmitting^ and^ receiving^information.^^

[0019] ^ In^this^example,^the^connections^103^and^104^are^illustrated^as^an^air^interface^to^enable^communicative^coupling,^and^can^be^consistent^with^cellular^communications^protocols,^such^as^a^Global^ System^ for^Mobile^ Communications^ (GSM)^ protocol,^ a^ code-division^ multiple^ access^(CDMA)^network^protocol,^a^Push-to-Talk^(PTT)^protocol,^a^PTT^over^Cellular^(POC)^protocol,^a^ Universal^Mobile^Telecommunications^System^(UMTS)^protocol,^a^3GPP^Long^Term^Evolution^ (LTE)^protocol,^a^fifth^generation^(5G)^protocol,^a^New^Radio^(NR)^protocol,^and / or^any^of^the^other^ communications^ protocols^ discussed^ herein.^ In^ embodiments,^ the^UEs^ 101^may^ directly^exchange^ communication^ data^ via^ a^ ProSe^ interface^ 105.^ The^ ProSe^ interface^ 105^ may^alternatively^be^referred^to^as^a^sidelink^(SL)^interface^105^and^may^comprise^one^or^more^logical^ channels,^including^but^not^limited^to^a^Physical^Sidelink^Control^Channel^(PSCCH),^a^Physical^Sidelink^ Shared^ Channel^ (PSSCH),^ a^ Physical^ Sidelink^ Discovery^ Channel^ (PSDCH),^ and^ a^Physical^Sidelink^Broadcast^Channel^(PSBCH).^^

[0020] ^ The^UE^101b^is^shown^to^be^configured^to^access^an^access^point^(AP)^106^(also^referred^to^as^also^referred^to^as^“WLAN^node^106”,^“WLAN^106”,^“WLAN^Termination^106”^or^“WT^ 106”^or^the^like)^via^connection^107.^The^connection^107^can^comprise^a^local^wireless^connection,^such^ as^ a^ connection^ consistent^ with^ any^ IEEE^ 802.11^ protocol,^ wherein^ the^AP^ 106^ would^comprise^a^wireless^fidelity^(WiFi®)^router.^In^this^example,^the^AP^106^is^shown^to^be^connected^ to^the^Internet^without^connecting^to^the^core^network^of^the^wireless^system^(described^in^further^ detail^below).^In^various^embodiments,^the^UE^101b,^RAN^110,^and^AP^106^may^be^configured^to^utilize^ LTE-WLAN^ aggregation^ (LWA)^ operation^ and / or^ WLAN^ LTE / WLAN^ Radio^ Level^Integration^with^IPsec^Tunnel^(LWIP)^operation.^The^LWA^operation^may^involve^the^UE^101b^in^ RRC_CONNECTED^being^configured^by^a^RAN^node^111^to^utilize^radio^resources^of^LTE^and^ WLAN.^LWIP^operation^may^involve^the^UE^101b^using^WLAN^radio^resources^(e.g.,^connection^ 107)^via^Internet^Protocol^Security^(IPsec)^protocol^tunneling^to^authenticate^and^encrypt^packets^ (e.g.,^internet^protocol^(IP)^packets)^sent^over^the^connection^107.^IPsec^tunneling^may^include^ encapsulating^entirety^of^original^IP^packets^and^adding^a^new^packet^header^thereby^protecting^ the^original^header^of^the^IP^packets.^^

[0021] ^ The^RAN^110^can^include^one^or^more^RAN^nodes^111a^and^111b^(collectively^referred^to^as^“RAN^nodes^111”^or^“RAN^node^111”)^that^enable^the^connections^103^and^104.^As^used^herein,^ the^ terms^ “access^ node^ (AN),”^ “access^ point,”^ “RAN^node”,^or^ the^ like^may^describe^equipment^that^provides^the^radio^baseband^functions^for^data^and / or^voice^connectivity^between^ a^network^and^one^or^more^users.^These^access^nodes^can^be^referred^to^as^base^stations^(BS),^next^Generation^NodeBs^ (gNBs),^RAN^nodes,^ evolved^NodeBs^ (eNBs),^NodeBs,^Road^ Side^Units^(RSUs),^Transmission^Reception^Points^(TRxPs^or^TRPs),^and^so^forth,^and^can^comprise^ground^ stations^(e.g.,^terrestrial^access^points)^or^satellite^stations^providing^coverage^within^a^geographic^ area^(e.g.,^a^cell).^As^used^herein,^the^term^“NG^RAN^node”^or^the^like^may^refer^to^a^RAN^node^ 111^that^operates^in^an^NR^or^5G^system^100^(for^example^a^gNB),^and^the^term^“E-UTRAN^node”^ or^the^like^may^refer^to^a^RAN^node^111^that^operates^in^an^LTE^or^4G^system^100^(e.g.,^an^eNB).^ According^to^various^embodiments,^the^RAN^nodes^111^may^be^implemented^as^one^or^more^of^a^ dedicated^physical^device^such^as^a^macrocell^base^station,^and / or^a^low^power^(LP)^base^station^ for^providing^femtocells,^picocells^or^other^like^cells^having^smaller^coverage^areas,^smaller^user^ capacity,^or^higher^bandwidth^compared^to^macrocells.^^

[0022] ^ In^some^embodiments,^all^or^parts^of^the^RAN^nodes^111^may^be^implemented^as^one^or^more^software^entities^running^on^server^computers^as^part^of^a^virtual^network,^which^may^be^ referred^to^as^a^cloud^radio^access^network^(CRAN)^and / or^a^virtual^baseband^unit^pool^(vBBUP).^ In^these^embodiments,^the^CRAN^or^vBBUP^may^implement^a^RAN^function^split,^such^as^a^PDCP^ split^wherein^RRC^and^PDCP^layers^are^operated^by^the^CRAN / vBBUP^and^other^Layer^2^(L2)^protocol^ entities^ are^operated^by^ individual^RAN^nodes^111;^a^MAC / PHY^split^wherein^RRC,^PDCP,^RLC,^and^MAC^layers^are^operated^by^the^CRAN / vBBUP^and^the^PHY^layer^is^operated^ by^individual^RAN^nodes^111;^or^a^“lower^PHY”^split^wherein^RRC,^PDCP,^RLC,^MAC^layers^ and^upper^portions^of^the^PHY^layer^are^operated^by^the^CRAN / vBBUP^and^lower^portions^of^the^PHY^ layer^ are^operated^ by^ individual^RAN^nodes^111.^This^ virtualized^ framework^ allows^ the^freed-up^processor^cores^of^the^RAN^nodes^111^to^perform^other^virtualized^applications.^In^some^implementations,^ an^ individual^ RAN^ node^ 111^ may^ represent^ individual^ gNB-DUs^ that^ are^connected^ to^ a^ gNB-CU^ via^ individual^ F1^ interfaces^ (not^ shown^ by^ Figure^ 1).^ In^ these^implementations,^the^gNB-DUs^may^include^one^or^more^remote^radio^heads^or^radio^front^end^ modules^(RFEMs),^and^the^gNB-CU^may^be^operated^by^a^server^that^is^located^in^the^RAN^110^(not^ shown)^ or^ by^ a^ server^ pool^ in^ a^ similar^ manner^ as^ the^ CRAN / vBBUP.^Additionally^ or^ alternatively,^one^or^more^of^the^RAN^nodes^111^may^be^next^generation^eNBs^(ng-eNBs),^which^ are^RAN^nodes^that^provide^E-UTRA^user^plane^and^control^plane^protocol^terminations^towards^ the^UEs^101,^and^are^connected^to^a^5GC^via^an^NG^interface.^

[0023] ^ In^V2X^scenarios^one^or^more^of^the^RAN^nodes^111^may^be^or^act^as^RSUs.^The^term^“Road^Side^Unit”^or^“RSU”^may^refer^to^any^transportation^infrastructure^entity^used^for^V2X^ communications.^An^RSU^may^be^implemented^in^or^by^a^suitable^RAN^node^or^a^stationary^(or^ relatively^stationary)^UE,^where^an^RSU^implemented^in^or^by^a^UE^may^be^referred^to^as^a^“UE- type^RSU”,^an^RSU^implemented^in^or^by^an^eNB^may^be^referred^to^as^an^“eNB-type^RSU,”^an^ RSU^implemented^in^or^by^an^gNB^may^be^referred^to^as^an^“gNB-type^RSU,”^and^the^like.^In^one^example,^ an^ RSU^ is^ a^ computing^ device^ coupled^ with^ radiofrequency^ circuitry^ located^ on^ a^roadside^that^provides^connectivity^support^to^passing^vehicle^UEs^101^(vUEs^101).^The^RSU^may^also^ include^ internal^data^storage^circuitry^ to^store^ intersection^map^geometry,^ traffic^statistics,^media,^as^well^ as^applications / software^ to^sense^ and^control^on-going^vehicular^and^pedestrian^traffic.^The^RSU^may^operate^on^the^5.9^GHz^Direct^Short^Range^Communications^(DSRC)^band^to^ provide^ very^ low^ latency^ communications^ required^ for^ high^ speed^ events,^ such^ as^ crash^avoidance,^traffic^warnings,^and^the^like.^Additionally^or^alternatively,^the^RSU^may^operate^on^ the^cellular^V2X^band^to^provide^the^aforementioned^low^latency^communications,^as^well^as^other^ cellular^communications^services.^Additionally^or^alternatively,^the^RSU^may^operate^as^a^WiFi^ hotspot^(2.4^GHz^band)^and / or^provide^connectivity^to^one^or^more^cellular^networks^to^provide^uplink^ and^ downlink^ communications.^ The^ computing^ device(s)^ and^ some^ or^ all^ of^ the^radiofrequency^circuitry^of^ the^RSU^may^be^packaged^in^a^weatherproof^enclosure^suitable^for^outdoor^ installation,^ and^may^ include^ a^ network^ interface^ controller^ to^ provide^ a^ wired^ (e.g.,^Ethernet)^connection^to^a^traffic^signal^controller^and / or^a^backhaul^network.^

[0024] ^ Any^of^the^RAN^nodes^111^can^terminate^the^air^interface^protocol^and^can^be^the^first^point^of^contact^for^the^UEs^101.^In^some^embodiments,^any^of^ the^RAN^nodes^111^can^fulfill^various^logical^functions^for^the^RAN^110^including,^but^not^limited^to,^radio^network^controller^ (RNC)^functions^such^as^radio^bearer^management,^uplink^and^downlink^dynamic^radio^resource^ management^and^data^packet^scheduling,^and^mobility^management.^^

[0025] ^ In^ embodiments,^ the^ UEs^ 101^ can^ be^ configured^ to^ communicate^ using^ Orthogonal^Frequency-Division^Multiplexing^(OFDM)^communication^signals^with^each^other^or^with^any^of^the^ RAN^ nodes^ 111^ over^ a^ multicarrier^ communication^ channel^ in^ accordance^ various^communication^ techniques,^ such^ as,^ but^ not^ limited^ to,^ an^ Orthogonal^ Frequency-Division^Multiple^Access^(OFDMA)^communication^technique^(e.g.,^for^downlink^communications)^or^a^ Single^Carrier^Frequency^Division^Multiple^Access^(SC-FDMA)^communication^technique^(e.g.,^ for^uplink^and^ProSe^or^sidelink^communications),^although^the^scope^of^the^embodiments^is^not^ limited^in^this^respect.^The^OFDM^signals^can^comprise^a^plurality^of^orthogonal^subcarriers.^

[0026] ^ In^some^embodiments,^a^downlink^resource^grid^can^be^used^for^downlink^transmissions^from^any^of^the^RAN^nodes^111^to^the^UEs^101,^while^uplink^transmissions^can^utilize^similar^techniques.^ The^ grid^ can^ be^ a^ time-frequency^ grid,^ called^ a^ resource^ grid^ or^ time-frequency^resource^grid,^which^is^the^physical^resource^in^the^downlink^in^each^slot.^Such^a^time-frequency^ plane^representation^is^a^common^practice^for^OFDM^systems,^which^makes^it^intuitive^for^radio^ resource^allocation.^Each^column^and^each^row^of^the^resource^grid^corresponds^to^one^OFDM^symbol^and^ one^OFDM^subcarrier,^ respectively.^The^duration^ of^ the^ resource^grid^ in^ the^ time^domain^corresponds^to^one^slot^in^a^radio^frame.^The^smallest^time-frequency^unit^in^a^resource^ grid^is^denoted^as^a^resource^element.^Each^resource^grid^comprises^a^number^of^resource^blocks,^ which^describe^the^mapping^of^certain^physical^channels^to^resource^elements.^Each^resource^block^comprises^ a^ collection^ of^ resource^ elements;^ in^ the^ frequency^ domain,^ this^may^ represent^ the^smallest^quantity^of^resources^that^currently^can^be^allocated.^There^are^several^different^physical^ downlink^channels^that^are^conveyed^using^such^resource^blocks.^^

[0027] ^ According^ to^ various^ embodiments,^ the^ UEs^ 101^ and^ the^ RAN^ nodes^ 111,^ 112^communicate^(for^example,^transmit^and^receive)^data^over^a^licensed^medium^(also^referred^to^as^the^ “licensed^ spectrum”^ and / or^ the^ “licensed^ band”)^ and^ an^ unlicensed^ shared^ medium^ (also^referred^ to^as^ the^“unlicensed^spectrum”^and / or^ the^“unlicensed^band”).^The^ licensed^spectrum^may^ include^ channels^ that^ operate^ in^ the^ frequency^ range^ of^ approximately^ 400^ MHz^ to^approximately^3.8^GHz,^whereas^the^unlicensed^spectrum^may^include^the^5^GHz^band.^^

[0028] ^ To^operate^in^the^unlicensed^spectrum,^the^UEs^101^and^the^RAN^nodes^111,^112^may^operate^ using^ Licensed^Assisted^Access^ (LAA),^ enhanced^LAA^ (eLAA),^ and / or^ further^ eLAA^(feLAA)^mechanisms.^In^these^implementations,^the^UEs^101^and^the^RAN^nodes^111,^112^may^ perform^one^or^more^known^medium-sensing^operations^and / or^carrier-sensing^operations^in^order^ to^determine^whether^one^or^more^channels^in^the^unlicensed^spectrum^is^unavailable^or^otherwise^ occupied^prior^to^transmitting^in^the^unlicensed^spectrum.^The^medium / carrier^sensing^operations^ may^be^performed^according^to^a^listen-before-talk^(LBT)^protocol.^^

[0029] ^ LBT^is^a^mechanism^whereby^equipment^(for^example,^UEs^101,^RAN^nodes^111,^112,^etc.)^ senses^ a^ medium^ (for^ example,^ a^ channel^ or^ carrier^ frequency)^ and^ transmits^ when^ the^medium^is^sensed^to^be^idle^(or^when^a^specific^channel^in^the^medium^is^sensed^to^be^unoccupied).^The^medium^sensing^operation^may^include^clear^channel^assessment^ (CCA),^which^utilizes^at^least^energy^detection^(ED)^to^determine^the^presence^or^absence^of^other^signals^on^a^channel^in^ order^to^determine^if^a^channel^is^occupied^or^clear.^This^LBT^mechanism^allows^cellular / LAA^networks^ to^ coexist^ with^ incumbent^ systems^ in^ the^ unlicensed^ spectrum^ and^ with^ other^ LAA^networks.^ED^may^include^sensing^radiofrequency^(RF)^energy^across^an^intended^transmission^band^ for^ a^period^of^ time^ and^comparing^ the^ sensed^RF^ energy^ to^ a^predefined^or^ configured^threshold.^^

[0030] ^ Typically,^the^incumbent^systems^in^the^5^GHz^band^are^WLANs^based^on^IEEE^802.11^technologies.^WLAN^employs^a^contention-based^channel^access^mechanism,^called^carrier^sense^ multiple^access^with^collision^avoidance^(CSMA / CA).^Here,^when^a^WLAN^node^(e.g.,^a^mobile^ station^(MS)^such^as^UE^101,^AP^106,^or^the^like)^intends^to^transmit,^the^WLAN^node^may^first^ perform^CCA^before^transmission.^Additionally,^a^backoff^mechanism^is^used^to^avoid^collisions^ in^situations^where^more^than^one^WLAN^node^senses^the^channel^as^idle^and^transmits^at^the^same^time.^The^backoff^mechanism^may^ be^ a^ counter^ that^ is^ drawn^ randomly^within^ the^ contention^window^size^(CWS),^which^is^increased^exponentially^upon^the^occurrence^of^collision^and^reset^ to^a^minimum^value^when^the^transmission^succeeds.^The^LBT^mechanism^designed^for^LAA^is^ somewhat^similar^to^the^CSMA / CA^of^WLAN.^In^some^implementations,^the^LBT^procedure^for^ DL^or^UL^transmission^bursts^including^PDSCH^or^PUSCH^transmissions,^respectively,^may^have^ an^LAA^contention^window^that^is^variable^in^length^between^X^and^Y^extended^CCA^(ECCA)^ slots,^where^X^and^Y^are^minimum^and^maximum^values^for^the^CWSs^for^LAA.^In^one^example,^ the^minimum^CWS^for^an^LAA^transmission^may^be^9^microseconds^(μs);^however,^the^size^of^the^ CWS^and^a^maximum^channel^occupancy^time^(MCOT)^(for^example,^a^transmission^burst)^may^ be^based^on^governmental^regulatory^requirements.^

[0031] ^ The^ LAA^mechanisms^ are^ built^ upon^ carrier^ aggregation^ (CA)^ technologies^ of^LTE-Advanced^systems.^In^CA,^each^aggregated^carrier^is^referred^to^as^a^component^carrier^(CC).^A^ CC^may^have^a^bandwidth^of^1.4,^3,^5,^10,^15^or^20^MHz^and^a^maximum^of^five^CCs^can^be^ aggregated,^and^therefore,^a^maximum^aggregated^bandwidth^is^100^MHz.^In^Frequency^Division^Duplexing^(FDD)^systems,^ the^number^of^aggregated^carriers^can^be^different^ for^DL^and^UL,^where^the^number^of^UL^CCs^is^equal^to^or^lower^than^the^number^of^DL^component^carriers.^In^some^cases,^ individual^CCs^ can^have^ a^different^ bandwidth^ than^other^CCs.^ In^Time^Division^Duplexing^(TDD)^systems,^the^number^of^CCs^as^well^as^the^bandwidths^of^each^CC^is^usually^the^ same^for^DL^and^UL.^

[0032] ^ CA^also^comprises^individual^serving^cells^to^provide^individual^CCs.^The^coverage^of^the^ serving^ cells^ may^ differ,^ for^ example,^ due^ to^ that^ CCs^ on^ different^ frequency^ bands^ will^experience^different^pathloss.^A^primary^service^cell^or^primary^cell^(PCell)^may^provide^a^Primary^ CC^(PCC)^for^both^UL^and^DL,^and^may^handle^Radio^Resource^Control^(RRC)^and^Non-Access^ Stratum^(NAS)^related^activities.^The^other^serving^cells^are^referred^to^as^Secondary^Cells^(SCells),^ and^each^SCell^may^provide^an^individual^Secondary^CC^(SCC)^for^both^UL^and^DL.^The^SCCs^may^ be^ added^ and^ removed^ as^ required,^while^ changing^ the^ PCC^may^ require^ the^UE^101^ to^undergo^a^handover.^ In^LAA,^eLAA,^and^feLAA,^some^or^all^of^ the^SCells^may^operate^in^the^unlicensed^spectrum^(referred^to^as^“LAA^SCells”),^and^the^LAA^SCells^are^assisted^by^a^PCell^ operating^in^the^licensed^spectrum.^When^a^UE^is^configured^with^more^than^one^LAA^SCell,^the^UE^may^receive^UL^grants^on^the^configured^LAA^SCells^ indicating^different^Physical^Uplink^Shared^Channel^(PUSCH)^starting^positions^within^a^same^subframe.^

[0033] ^ The^physical^downlink^shared^channel^(PDSCH)^may^carry^user^data^and^higher-layer^signaling^to^the^UEs^101.^The^physical^downlink^control^channel^(PDCCH)^may^carry^information^ about^the^transport^format^and^resource^allocations^related^to^the^PDSCH^channel,^among^other^ things.^It^may^also^inform^the^UEs^101^about^the^transport^format,^resource^allocation,^and^H-ARQ^ (Hybrid^Automatic^Repeat^Request)^information^related^to^the^uplink^shared^channel.^Typically,^ downlink^scheduling^(assigning^control^and^shared^channel^resource^blocks^to^the^UE^101b^within^ a^cell)^may^be^performed^at^any^of^the^RAN^nodes^111^based^on^channel^quality^information^fed^ back^from^any^of^the^UEs^101.^The^downlink^resource^assignment^information^may^be^sent^on^the^ PDCCH^used^for^(e.g.,^assigned^to)^each^of^the^UEs^101.^

[0034] ^ The^PDCCH^may^use^control^channel^elements^(CCEs)^to^convey^the^control^information.^Before^being^mapped^ to^ resource^elements,^ the^PDCCH^complex-valued^symbols^may^ first^be^organized^ into^quadruplets,^which^may^ then^be^permuted^using^a^sub-block^interleaver^for^ rate^matching.^Each^PDCCH^may^be^transmitted^using^one^or^more^of^these^CCEs,^where^each^CCE^ may^correspond^to^nine^sets^of^four^physical^resource^elements^known^as^resource^element^groups^ (REGs).^Four^Quadrature^Phase^Shift^Keying^(QPSK)^symbols^may^be^mapped^to^each^REG.^The^ PDCCH^can^be^transmitted^using^one^or^more^CCEs,^depending^on^the^size^of^the^downlink^control^ information^(DCI)^and^the^channel^condition.^There^can^be^four^or^more^different^PDCCH^formats^ defined^in^LTE^with^different^numbers^of^CCEs^(e.g.,^aggregation^level,^L=1,^2,^4,^or^8).^

[0035] ^ Some^ embodiments^ may^ use^ concepts^ for^ resource^ allocation^ for^ control^ channel^information^ that^ are^ an^ extension^ of^ the^ above-described^ concepts.^ For^ example,^ some^embodiments^may^utilize^an^enhanced^physical^downlink^control^channel^(EPDCCH)^ that^uses^ PDSCH^resources^for^control^information^transmission.^The^EPDCCH^may^be^transmitted^using^ one^or^more^enhanced^the^control^channel^elements^(ECCEs).^Similar^to^above,^each^ECCE^may^ correspond^to^nine^sets^of^four^physical^resource^elements^known^as^an^enhanced^resource^element^ groups^(EREGs).^An^ECCE^may^have^other^numbers^of^EREGs^in^some^situations.^^

[0036] ^ The^RAN^nodes^111^may^be^configured^to^communicate^with^one^another^via^interface^112.^ In^embodiments^where^the^system^100^is^an^LTE^system,^the^interface^112^may^be^an^X2^interface^112.^The^X2^interface^may^be^defined^between^two^or^more^RAN^nodes^111^(e.g.,^two^or^ more^eNBs,^and^the^like)^that^connect^to^EPC^120,^and / or^between^two^eNBs^connecting^to^EPC^ 120.^In^some^implementations,^the^X2^interface^may^include^an^X2^user^plane^interface^(X2-U)^ and^an^X2^control^plane^interface^(X2-C).^The^X2-U^may^provide^flow^control^mechanisms^for^ user^data^packets^transferred^over^the^X2^interface,^and^may^be^used^to^communicate^information^about^ the^ delivery^ of^ user^ data^ between^ eNBs.^ For^ example,^ the^ X2-U^may^ provide^ specific^sequence^number^information^for^user^data^transferred^from^a^master^eNB^(MeNB)^to^a^secondary^ eNB^(SeNB);^information^about^successful^in^sequence^delivery^of^PDCP^PDUs^to^a^UE^101^from^an^ SeNB^ for^ user^ data;^ information^ of^ PDCP^ PDUs^ that^ were^ not^ delivered^ to^ a^ UE^ 101;^information^about^a^current^minimum^desired^buffer^size^at^the^SeNB^for^transmitting^to^the^UE^ user^data;^and^the^like.^The^X2-C^may^provide^intra-LTE^access^mobility^functionality,^including^ context^transfers^from^source^to^target^eNBs,^user^plane^transport^control,^etc.;^load^management^ functionality;^as^well^as^inter-cell^interference^coordination^functionality.^

[0037] ^ In^embodiments^where^the^system^100^is^a^5G^or^NR^system,^the^interface^112^may^be^an^Xn^interface^112.The^Xn^interface^is^defined^between^two^or^more^RAN^nodes^111^(e.g.,^two^or^more^gNBs^and^ the^ like)^ that^connect^ to^5GC^120,^between^a^RAN^node^111^ (e.g.,^ a^gNB)^connecting^to^5GC^120^and^an^eNB,^and / or^between^two^eNBs^connecting^to^5GC^120.^In^some^implementations,^ the^Xn^ interface^may^ include^ an^Xn^ user^plane^ (Xn-U)^ interface^ and^ an^Xn^control^ plane^ (Xn-C)^ interface.^The^Xn-U^may^ provide^ non-guaranteed^ delivery^of^user^plane^PDUs^and^support / provide^data^forwarding^and^flow^control^functionality.^The^Xn-C^may^provide^ management^and^error^handling^functionality,^functionality^to^manage^the^Xn-C^interface;^mobility^support^ for^UE^101^ in^ a^ connected^mode^ (e.g.,^CM-CONNECTED)^ including^ functionality^ to^manage^the^UE^mobility^for^connected^mode^between^one^or^more^RAN^nodes^111.^The^mobility^ support^may^include^context^transfer^from^an^old^(source)^serving^RAN^node^111^to^new^(target)^ serving^RAN^node^111;^and^control^of^user^plane^tunnels^between^old^(source)^serving^RAN^node^ 111^to^new^(target)^serving^RAN^node^111.^A^protocol^stack^of^the^Xn-U^may^include^a^transport^ network^layer^built^on^Internet^Protocol^(IP)^transport^layer,^and^a^GTP-U^layer^on^top^of^a^UDP^ and / or^IP^layer(s)^to^carry^user^plane^PDUs.^The^Xn-C^protocol^stack^may^include^an^application^ layer^signaling^protocol^(referred^to^as^Xn^Application^Protocol^(Xn-AP))^and^a^transport^network^ layer^that^is^built^on^SCTP.^The^SCTP^may^be^on^top^of^an^IP^layer,^and^may^provide^the^guaranteed^ delivery^of^application^layer^messages.^In^the^transport^IP^layer^point-to-point^transmission^is^used^ to^deliver^the^signaling^PDUs.^In^other^implementations,^the^Xn-U^protocol^stack^and / or^the^Xn- C^protocol^stack^may^be^same^or^similar^to^the^user^plane^and / or^control^plane^protocol^stack(s)^ shown^and^described^herein.^

[0038] ^ The^RAN^110^ is^ shown^ to^be^ communicatively^ coupled^ to^a^core^network^—^ in^ this^embodiment,^Core^Network^(CN)^120.^The^CN^120^may^comprise^a^plurality^of^network^elements^122,^ which^ are^ configured^ to^ offer^ various^ data^ and^ telecommunications^ services^ to^customers / subscribers^(e.g.,^users^of^UEs^101)^who^are^connected^to^the^CN^120^via^the^RAN^110.^The^ term^“network^element”^may^describe^a^physical^or^virtualized^equipment^used^to^provide^wired^ or^ wireless^ communication^ network^ services.^ The^ term^ “network^ element”^ may^ be^considered^ synonymous^ to^ and / or^ referred^ to^ as^ a^networked^ computer,^ networking^ hardware,^network^equipment,^ router,^switch,^hub,^bridge,^ radio^network^controller,^ radio^access^network^device,^ gateway,^ server,^ virtualized^ network^ function^ (VNF),^ network^ functions^ virtualization^infrastructure^(NFVI),^and / or^the^like.^The^components^of^the^CN^120^may^be^implemented^in^one^ physical^node^or^separate^physical^nodes^including^components^to^read^and^execute^instructions^ from^a^machine-readable^or^computer-readable^medium^(e.g.,^a^non-transitory^machine-readable^ storage^medium).^In^some^embodiments,^Network^Functions^Virtualization^(NFV)^may^be^utilized^ to^virtualize^any^or^all^of^the^above^described^network^node^functions^via^executable^instructions^ stored^in^one^or^more^computer^readable^storage^mediums^(described^in^further^detail^below).^A^ logical^instantiation^of^the^CN^120^may^be^referred^to^as^a^network^slice,^and^a^logical^instantiation^of^ a^portion^of^ the^CN^120^may^be^ referred^ to^ as^ a^network^ sub-slice.^NFV^architectures^ and^infrastructures^may^be^used^to^virtualize^one^or^more^network^functions,^alternatively^performed^ by^proprietary^hardware,^onto^physical^resources^comprising^a^combination^of^industry-standard^server^ hardware,^ storage^ hardware,^ or^ switches.^ In^ other^words,^NFV^ systems^ can^ be^ used^ to^execute^virtual^or^reconfigurable^implementations^of^one^or^more^EPC^components / functions.^^

[0039] ^ Generally,^the^application^server^130^may^be^an^element^offering^applications^that^use^IP^bearer^resources^with^the^core^network^(e.g.,^UMTS^Packet^Services^(PS)^domain,^LTE^PS^data^services,^ etc.).^ The^ application^ server^ 130^ can^ also^ be^ configured^ to^ support^ one^ or^ more^communication^services^(e.g.,^Voice-over-Internet^Protocol^(VoIP)^sessions,^PTT^sessions,^group^ communication^sessions,^social^networking^services,^etc.)^for^the^UEs^101^via^the^EPC^120.^

[0040] ^ In^embodiments,^the^CN^120^may^be^a^5GC^(referred^to^as^“5GC^120”^or^the^like),^and^the^RAN^110^may^be^connected^with^the^CN^120^via^an^NG^interface^113.^In^embodiments,^the^ NG^interface^113^may^be^split^into^two^parts,^an^NG^user^plane^(NG-U)^interface^114,^which^carries^ traffic^data^between^the^RAN^nodes^111^and^a^user^plane^function^(UPF),^and^the^S1^control^plane^ (NG-C)^interface^115,^which^is^a^signaling^interface^between^the^RAN^nodes^111^and^AMFs.^^

[0041] ^ In^embodiments,^the^CN^120^may^be^a^5G^CN^(referred^to^as^“5GC^120”^or^the^like),^while^in^other^embodiments,^the^CN^120^may^be^an^Evolved^Packet^Core^(EPC)).^Where^CN^120^ is^an^EPC^(referred^to^as^“EPC^120”^or^the^like),^the^RAN^110^may^be^connected^with^the^CN^120^ via^an^S1^interface^113.^In^embodiments,^the^S1^interface^13^may^be^split^into^two^parts,^an^S1^ user^plane^(S1-U)^interface^114,^which^carries^traffic^data^between^the^RAN^nodes^111^and^the^ serving^gateway^(S-GW),^and^the^S1-mobility^management^entity^(MME)^interface^115,^which^is^ a^signaling^interface^between^the^RAN^nodes^111^and^MMEs.^^

[0042] ^ Embodiments^ herein^ may^ relate^ to^ provision^ of^ a^ network^ indication^ about^ the^ 12^physical^resource^block^(PRB)^synchronization^signal^block^(SSB)^bandwidth^for^a^target^cell^for^ user^equipment^(UE)^radio^resource^management^(RRM)^measurements.^For^an^unknown^target^ cell,^the^UE^may^not^have^information^regarding^the^target^SSB^bandwidth^because^a^12PRB^SSB^ may^be^possible^in^addition^to^20PRB.^It^may^be^acceptable^for^the^primary^cell^(Pcell)^to^have^an^ SSB^that^is^configured^on^a^sync^raster^that^is^in^accordance^with^one^or^more^specifications^such^ as^third^generation^partnership^project^(3GPP)^specifications^or^some^other^specification.^As^long^ as^the^configured^SSB^frequency^position^is^aligned^with^the^sync^raster^for^12PRB^SSB,^the^UE^may^ use^ a^ 12PRB^ bandwidth^ to^ receive^ the^ SSB,^ and^ so^ measurement^ performance^ may^ be^guaranteed^and^requirements^may^be^fulfilled.^

[0043] ^ Embodiments^herein^may^allow^for^or^relate^to^12PRB^SSB^bandwidth^configurations^for^Secondary^Cells^(SCells)^and^Primary^SCells^(PSCells).^12^PRB^SSB^bandwidth^configurations^ for^SCells^and / or^PSCells^may^provide^a^different^configuration^requirement,^because^there^may^ not^be^a^requirement^that^the^SSB^should^align^with^the^sync^raster^for^SCells^and^PSCells.^On^the^condition^ that^ the^ 12PRB^ SSB^ is^ placed^ off^ the^ sync^ raster,^ it^ may^ be^ desirable^ to^ read^ the^bandwidth^ info^ sent^ in^measurement^ object^ indications^ for^ the^UE^ to^ be^ clear^ about^ the^ SSB^bandwidth.^

[0044] ^ Embodiments^herein^may^include^or^relate^to^definitions^of^bandwidth^indications^in^the^measurement^object^message^from^the^network,^and^how^the^UE^reads^ it^and^carries^out^RRM^measurements^and^other^related^procedures^accordingly.^

[0045] ^ By^the^definition^of^the^indications^and^UE^behaviors,^measurement^performance^may^be^ guaranteed^ by^ UE^ using^ a^measurement^ bandwidth^ that^ is^ aligned^with^ the^ indicated^ SSB^bandwidth.^ Otherwise^ the^ RRM^ measurement^ accuracy^ and^ delay^ performance^ may^ not^ be^guaranteed.^

[0046] ^ In^some^embodiments,^the^UE^may^determine^that^the^SSB^bandwidth^of^a^target^cell^(e.g.,^a^deactivated^SCell^or^a^deactivated^PSCell)^is^12^PRBs^based^on^a^message^received^from^ an^Access^Node^(AN)^(e.g.,^a^gNB).^^

[0047] ^ In^some^embodiments,^the^received^message^may^indicate^that^the^SSB^bandwidth^of^the^target^cell^(e.g.,^the^deactivated^SCell^or^the^deactivated^PSCell)^is^12^PRBs.^For^example,^in^the^ container^of^MeasObjectNR,^there^is^an^Information^Element^(IE)^of^referenceSignalConfig^that^ contains^the^SSB-ConfigMobility^property.^Embodiments^herein^may^include^or^relate^to^one^or^more^ indications^ of^ SSB^ bandwidth^ information^ in^ SSB-ConfigMobility^ property^ item.^ In^ an^example,^SSB-12PRB^may^be^added^as^a^Boolean^type^element.^When^it^is^true,^it^means^the^target^SSB^ bandwidth^ is^ 12PRB^ instead^ of^ 20PRB,^ and^ vice^ versa.^ In^ another^ example,^SSBbandwidthinPRB^may^be^added^as^an^Enumerated^type.^It^has^candidate^values^of^12^and^20^ and^potentially^more.^The^target^SSB^bandwidth^in^PRB^may^be^based^on^the^signaled^value^in^the^ element.^

[0048] ^ An^example^of^how^SSB-ConfigMobility^may^be^updated^accordingly^is^illustrated^below.^As^ shown,^ the^ above^ two^ examples^ (SSB-12PRB^ and^ SSBbandwidthinPRB)^ are^ listed,^ e.g.,^ as^optional^options.^^ ^

[0049] ^ In^ some^embodiments,^ the^ received^message^may^ indicate^a^ carrier^bandwidth^of^ the^target^cell^ (e.g.,^ the^deactivated^SCell^or^ the^deactivated^PSCell).^The^UE^may^derive^the^SSB^bandwidth^ of^ the^ deactivated^ cell^ from^ the^ carrier^ bandwidth.^ For^ example,^ carrier^ bandwidth^smaller^than^20PRB^corresponds^to^12PRB^SSB;^and / or^others^correspond^to^20PRB^SSB.^In^some^ embodiments,^the^received^message^is^applicable^in^handover^and^SCell^addition.^For^example,^ for^handover^command^reconfigurationwithsync,^there^may^be^an^indication^in^servingcellcommon^about^ the^ target^ carrier^ bandwidth^ in^ the^ IE^ carrierBandwidth.^ For^ SCell^ addition^ command^RRCreconfiguration,^there^may^also^be^an^indication^in^servingcellcommon^about^the^target^carrier^ bandwidth.^The^UE^may^derive^the^SSB^bandwidth^based^on^carrier^bandwidth^indicated^in^the^ handover^command^or^the^SCell^addition^command.^In^other^embodiments,^the^received^message^ may^be^applicable^in^any^other^scenarios.^The^disclosure^is^not^limited^in^this^respect.^

[0050] ^ With^the^SSB^bandwidth^indication^introduced,^the^UE^measurement^performance^may^be^ guaranteed^ for^ connected^ mode^ RRM^measurements^ targeting^ any^ cell^ that^ sends^ 12PRB^bandwidth^SSB.^For^a^UE^that^supports^12PRB^SSB^bandwidth^measurements^in^connected^mode,^ the^UE^may^follow^requirements^as^defined^in^the^3GPP^release-19^(Rel-19)^specifications^when^ the^UE^is^configured^with^12PRB^bandwidth^SSB^in^the^measurement^object^configurations.^An^ example^of^such^requirements^may^include^a^test^case^for^measurements^on^target^cell^with^12PRB^ SSB^bandwidth^off^sync^raster^to^test^the^UE^ability^to^use^the^message^conducted^in^the^Managed^ Object^(MO)^configurations.^

[0051] ^ Figure^2^illustrates^an^example^flowchart^of^a^method^200^for^UE^RRM^measurements^in^ accordance^ with^ some^ embodiments^ of^ the^ present^ disclosure.^ The^ method^ 200^ may^ be^performed^by^an^apparatus^e.g.,^for^a^UE.^As^shown,^the^method^200^may^include^operations^210^ and^220.^The^method^200^may^include^more^or^less^or^different^operations,^which^is^not^limited^in^ the^disclosure.^

[0052] ^ At^210,^a^time^period^for^time^index^detection^for^an^SSB^of^a^deactivated^cell^with^an^SSB^bandwidth^of^12^PRBs^is^determined^based^on^a^Discontinuous^Reception^(DRX)^cycle,^a^ measurement^cycle^for^the^deactivated^cell,^and^a^Carrier^Specific^Scaling^Factor^(CSSF).^At^220,^ measurement^for^the^SSB^is^performed^based^on^the^time^period^for^the^time^index^detection.^

[0053] ^ In^ some^ embodiments,^ the^ deactivated^ cell^ may^ include^ a^ deactivated^ SCell^ or^ a^deactivated^ PSCell.^When^ a^UE^ is^ capable^ of^measuring^ on^ 12PRB^ bandwidth^ SSB^ and^ it^ is^ configured^with^measurements^on^either^a^deactivated^SCell^or^a^deactivated^PSCell^with^12PRB^ bandwidth^SSB^in^frequency^range^1^(FR1),^the^UE^may^determine^the^time^period^for^time^index^ detection^for^an^SSB^of^a^deactivated^cell^with^an^SSB^bandwidth^of^12^PRBs^and^follow^the^time^ period^requirements^for^deactivated^SCell^and^deactivated^PSCell^measurements.^

[0054] ^ In^some^embodiments,^the^time^period^for^the^time^index^detection^may^be^determined^further^based^on^a^scaling^factor^for^an^SSB^frequency^layer^to^be^measured^without^GAP^and^a^ nominal^number^of^SSB^measurement^samples.^^

[0055] ^ In^some^embodiments,^the^deactivated^cell^may^operate^in^a^system^(e.g.,^a^narrowband^system)^having^a^narrow^bandwidth^(e.g.,^less^than^5^MHz^or^the^like).^

[0056] ^ In^some^embodiments,^the^deactivated^cell^may^operate^in^FR1.^

[0057] ^ As^used^herein,^the^term^Frequency^Range^1^(which^may^be^abbreviated^as^“FR-1,^“FR1,”^etc.)^and / or^Frequency^Range^2^(which^may^be^abbreviated^as^“FR-2,”^“FR2,”^etc,)^may^refer^to^ frequency^bandwidths^as^defined^by^the^third^generation^partnership^project^(3GPP),^for^example^in^ technical^specification^(TS)^38.104,^whether^as^previously^defined,^as^defined^at^ the^time^of^filing^ of^ the^ present^ document,^ or^ as^ may^ be^ defined^ at^ some^ future^ time.^ In^ some^ specific^embodiments,^Frequency^Range^1^may^refer^to^frequency^bandwidths^between^approximately^410^ Megahertz^(MHz)^and^approximately^7125^MHz.^In^other^specific^embodiments,^Frequency^Range^1^may^ refer^ to^ frequency^bandwidths^ that^ are^ less^ than^or^ equal^ to^approximately^ 6000^MHz.^Similarly,^ in^ specific^ embodiments,^ Frequency^ Range^ 2^ may^ refer^ to^ bandwidths^ between^approximately^24250^MHz^and^approximately^71000^MHz.^In^some^embodiments,^bandwidths^between^ approximately^ 24250^ MHz^ and^ approximately^ 52600^ MHz^ may^ be^ referred^ to^ as^Frequency^Range^2-1^(which^may^be^abbreviated^as^“FR2-1,”^“FR^2-1,”^etc.).^Bandwidths^between^ approximately^52600^MHz^and^approximately^71000^MHz^may^be^referred^to^as^Frequency^Range^ 2-2^(which^may^be^abbreviated^as^“FR2-2,”^“FR^2-2,”^etc.).^

[0058] ^ For^ example,^ the^ time^ period^ for^ time^ index^ detection^ for^ a^ 12PRB^ SSB^ may^ be^determined^based^on^Table^1^or^Table^2^below^which^may^be^input^into^3GPP^TS^38.133.^ Table^1:^Time^period^for^time^index^detection^for^a^UE^operating^on^a^target^cell^with^ 12PRB^SSB,^deactivated^SCell^(FR1)^ ^ Table^2:^Time^period^for^time^index^detection^for^a^UE^operating^on^a^target^cell^with^ 12PRB^SSB,^deactivated^PSCell^(FR1)^

[0059] ^ As^ above,^ the^ time^ period^ for^ time^ index^ detection^ for^ a^ 12PRB^ SSB^(TSSB_time_index_intra_less_than_5MHz)^may^be^determined^based^on^a^DRX^cycle^(e.g.,^no^DRX,^DRX^ ,^a^measurement^cycle^for^ the^deactivated^cell^(e.g.,^measCycleSCell^or^measCyclePSCell),^and^a^CSSF^(e.g.,^CSSFintra).^^

[0060] ^ As^above,^TSSB_time_index_intra_less_than_5MHz^may^be^determined^further^based^on^Ceil^(7^x^Kp)^which^is^related^to^or^indicates^is^the^number^of^allowed^and^available^measurement^samples.^Kp^ is^a^scaling^factor^for^an^SSB^frequency^layer^to^be^measured^without^GAP.^The^nominal^number^ of^SSB^measurement^samples^is^the^number^of^SSB^measurement^samples^needed^for^the^UE^to^correctly^ process^ and^ obtain^ the^ correct^measurement^ results^ on^ the^ cell^ time^ index^ detection^purpose.^In^the^Tables^above,^the^nominal^number^of^SSB^measurement^samples^is^7.^That^is,^the^requirement^ here^ require^ the^ UE^ to^ finish^ correctly^ the^ time^ index^ detection^ when^needed / configured^ within^ the^ specified^ time^ period^ which^ consists^ basically^ 7^ available^ SSB^samples.^The^nominal^number^of^SSB^measurement^samples^7^is^determined^from^compromise^ between^accuracy^and^effectiveness.^

[0061] ^ In^some^embodiments,^a^time^for^fine^time^tracking^and^acquiring^full^timing^information^of^the^deactivated^PSCell^with^an^SSB^bandwidth^of^12^PRBs^may^be^determined^to^be^triple^that^ for^a^deactivated^PSCell^with^an^SSB^bandwidth^other^than^12^PRBs.^For^example,^T∆^is^the^time^ for^fine^time^tracking^and^acquiring^full^timing^information^of^the^target^cell.^T∆^=^3*Trs^ms^for^target^ PSCell^ operating^ with^ 12^ PRB^ SSB^ BW.^ Otherwise,^ T∆^ =^ 1*Trs^ ms.^ Trs^ is^ the^ SMTC^periodicity^of^the^target^cell^if^the^UE^has^been^provided^with^an^SMTC^configuration^for^the^target^cell^ in^ PSCell^ addition^message,^ otherwise^Trs^ is^ the^ SMTC^ configured^ in^ the^measObjectNR^having^ the^ same^ SSB^ frequency^ and^ subcarrier^ spacing.^ If^ the^ UE^ is^ not^ provided^ SMTC^configuration^or^measurement^object^on^this^frequency,^the^requirement^in^this^clause^is^applied^ with^Trs^=^5^ms^assuming^the^SSB^transmission^periodicity^is^5^ms.^There^is^no^requirement^if^the^ SSB^transmission^periodicity^is^not^5^ms.^The^definition^of^Trs^in^this^example^may^be^substantially^ in^line^with^that^recited^in^clause^8.11^of^3GPP^TS^38.133^V18.6.0^(2024-06)).^

[0062] ^ In^ some^ embodiments,^ the^ time^ for^ fine^ time^ tracking^ and^ acquiring^ full^ timing^information^ of^ the^ deactivated^ PSCell^ with^ an^ SSB^bandwidth^ of^ 12^PRBs^ (e.g.,^T∆)^ may^ be^applicable^ in^ PSCell^ addition^ and^ change.^ In^ some^ embodiments,^ regarding^ PSCell^ addition^ and^PSCell^change^delay,^the^time^may^also^be^longer^when^12PRB^SSB^is^configured^than^that^for^20PRB^SSB.^

[0063] ^ In^some^embodiments,^upon^receiving^PSCell^addition^in^subframe^n,^the^UE^may^be^capable^to^transmit^a^physical^random^access^channel^(PRACH)^preamble^towards^PSCell^in^FR1^or^FR2^no^later^

[0064] ^ In^some^embodiments,^a^time^for^fine^time^tracking^and^acquiring^full^timing^information^of^the^deactivated^SCell^may^be^determined^to^be^a^value^greater^than^zero.^For^example,^T∆^is^the^ additional^time^for^fine^time^tracking^and^acquiring^full^timing^information^of^the^SCell.^T∆^=^2*Trs^ ms^for^SCell^operating^with^12^PRB^SSB^BW.^Otherwise,^T∆^=^0^ms.^Trs^is^the^SMTC^periodicity^ of^the^SCell^being^activated^if^the^UE^has^been^provided^with^an^SMTC^configuration^for^the^SCell^ in^SCell^addition^message,^otherwise^Trs^is^the^SMTC^configured^in^the^measObjectNR^having^the^same^ SSB^ frequency^ and^ subcarrier^ spacing.^ If^ the^ measObjectNRs^ having^ the^ same^ SSB^frequency^ and^ subcarrier^ spacing^ configured^by^MN^and^SN^have^different^SMTC,^Trs^ is^ the^periodicity^of^one^of^ the^SMTC^which^ is^up^ to^UE^ implementation.^ If^ the^UE^ is^not^provided^SMTC^configuration^or^measurement^object^on^this^frequency,^the^requirement^which^involves^Trs^is^ applied^ with^ Trs^ =^ 5^ms^ assuming^ the^ SSB^ transmission^ periodicity^ is^ 5^ms.^ There^ are^ no^requirements^if^the^SSB^transmission^periodicity^is^not^5^ms.^The^definition^of^Trs^in^this^example^may^be^substantially^ in^line^with^that^recited^in^clause^8.11^of^3GPP^TS^38.133^V18.6.0^(2024-06)).^

[0065] ^ In^some^embodiments,^in^the^SCell^activation^delay^requirements,^fine^time^tracking^after^search^of^the^target^cell^may^be^used,^and^when^the^target^SSB^bandwidth^(BW)^is^smaller^than^ 5MHz,^the^legacy^requirement(s)^may^not^apply.^As^a^result,^it^may^be^desirable^to^specify^and / or^ define^new^requirements^for^fine^time^tracking^time^that^is^included^in^the^SCell^activation^delay^ requirements.^As^used^herein,^the^term^“Tactivation_time”^may^refer^to^the^SCell^activation^delay^in^ units^of^milliseconds.^^

[0066] ^ ^ If^the^SCell^is^known^and^belongs^to^FR1,^Tactivation_time^may^be:^-^ TFirstSSB_MAX^+^3^*^Trs^+^5ms,^if^the^measurement^period^of^the^SCell^being^activated^is^larger^than^2400ms^and^the^UE^supporting^12PRB^SSB^bandwidth^UE^feature^is^configured^with^ a^target^SCell^that^is^with^12PRB^SSB^bandwidth.^ ^If^the^SCell^is^unknown^and^belongs^to^FR1,^and^if^one^of^the^following^conditions^is^met:^ -^ ^‘ssb-PositionInBurst’^indicates^only^one^SSB^is^being^actually^transmitted,^or^ -^ ^‘ssb-PositionInBurst’^ indicates^ multiple^ SSBs^ and^ TCI^ indication^ is^provided^in^same^MAC^PDU^with^SCell^activation,^then^ -^ Tactivation_time^may^be^TFirstSSB_MAX^+^TSMTC_MAX^+^4*Trs^+^5ms,^if^the^UE^supporting^12PRB^SSB^bandwidth^UE^ feature^ is^ configured^with^ a^ target^ SCell^ that^ is^with^12PRB^SSB^bandwidth.^ Otherwise^ -^ Tactivation_time^may^be^6ms^+^TFirstSSB_MAX^+^TSMTC_MAX^+^3^*^Trs^+^TL1-RSRP,^measure^+^TL1-RSRP,report^+^THARQ^+^max(Tuncertainty_MAC^+^TFineTiming^+^ 2ms,^Tuncertainty_SP),^ if^semi-persistent^ CSI-RS^ is^ used^ for^ CSI^ reporting,^ and^ the^UE^ supporting^ 12PRB^ SSB^bandwidth^UE^feature^is^configured^with^a^target^SCell^that^is^with^12PRB^SSB^bandwidth,^ -^ Tactivation_time^may^be^3ms^+^TFirstSSB_MAX^+^TSMTC_MAX^+^3^*^Trs^+^TL1-RSRP,^measure^+^TL1-RSRP,report^+^max(THARQ^+^Tuncertainty_MAC^+^5ms^+^TFineTiming,^ Tuncertainty_RRC^+^TRRC_delay),^if^periodic^CSI-RS^is^used^for^CSI^reporting,^and^the^UE^supporting^[12PRB^ SSB^bandwidth^UE^ feature]^ is^ configured^with^ a^ target^SCell^ that^ is^with^12PRB^SSB^bandwidth.^

[0067] ^ As^ above,^ time^ for^ fine^ time^ tracking^ and^ acquiring^ full^ timing^ information^ of^ the^deactivated^SCell^T∆^is^equal^to^2*Trs^ms^for^SCell^operating^with^12^PRB^SSB^BW.^In^this^case,^ TFirstSSB_MAX^+^3^*^Trs^+^5ms^may^be^rewritten^as^TFirstSSB_MAX^+^Trs^+^T∆^+^5ms;^TFirstSSB_MAX^+^ TSMTC_MAX^+^4*Trs^+^5ms^may^be^rewritten^as^TFirstSSB_MAX^+^TSMTC_MAX^+^2*Trs+^T∆^+^5ms;^6ms^ +^TFirstSSB_MAX^+^TSMTC_MAX^+^3^*^Trs^+^TL1-RSRP,^measure^+^TL1-RSRP,report^+^THARQ^+^max(Tuncertainty_MAC^ +^TFineTiming^+^2ms,^Tuncertainty_SP)^may^be^rewritten^as^6ms^+^TFirstSSB_MAX^+^TSMTC_MAX^+^Trs^+^T∆+^ TL1-RSRP,^measure^+^TL1-RSRP,report^+^THARQ^+^max(Tuncertainty_MAC^+^TFineTiming^+^2ms,^Tuncertainty_SP);^and^3ms^ +^ TFirstSSB_MAX^ +^ TSMTC_MAX^ +^ 3^ *^ Trs^ +^ TL1-RSRP,^ measure^ +^ TL1-RSRP,report^ +^ max(THARQ^ +^Tuncertainty_MAC^+^5ms^+^TFineTiming,^Tuncertainty_RRC^+^TRRC_delay)^may^be^rewritten^as^3ms^+^TFirstSSB_MAX^ +^TSMTC_MAX^+^Trs^+^T∆+^TL1-RSRP,^measure^+^TL1-RSRP,report^+^max(THARQ^+^Tuncertainty_MAC^+^5ms^+^ TFineTiming,^Tuncertainty_RRC^+^TRRC_delay).^

[0068] ^ The^ embodiments^ herein^ may^ be^ applicable^ to^ Carrier^ Aggregation^ (CA)^ or^ Dual^Connectivity^(DC)^or^any^other^different^cases,^which^is^not^limited^in^the^disclosure.^^

[0069] ^ In^the^case^of^new^radio^(NR)-dual^connectivity^(DC)^PSCell^change^in^FR1,^when^the^UE^supporting^12PRB^SSB^bandwidth^UE^feature^is^configured^with^a^target^PSCell^that^is^with^ 12PRB^SSB^bandwidth,^the^UE^shall^transmit^PRACH^preamble^towards^the^target^PSCell^no^later^ than^the^delay^requirements^specified^in^3GPP^TS^38.133^clause^8.9.2.^

[0070] ^ With^the^technical^solutions^provided^in^the^disclosure,^network^indication^about^the^12^PRB^ SSB^ bandwidth^ for^ a^ target^ cell^ is^ provided^ for^ UE^ RRM^ measurements^ including^ deactivalted^SCell / PSCell^measurement,^handover^and^SCell^addition,^SCell^activation,^PSCell^ addition^and^change,^or^the^like.^In^this^way,^the^UE^may^perform^RRM^measurements^including^ SSB^measurement^accurately.^

[0071] ^ Figure^3^illustrates^a^network^300^in^accordance^with^various^embodiments.^The^network^300^may^operate^ in^a^manner^consistent^with^3GPP^technical^specifications^for^LTE^or^5G / NR^systems.^However,^ the^ example^ embodiments^ are^ not^ limited^ in^ this^ regard^ and^ the^ described^embodiments^may^apply^to^other^networks^that^benefit^from^the^principles^described^herein,^such^ as^future^3GPP^systems,^or^the^like.^^

[0072] ^ The^network^300^may^include^a^UE^302,^which^may^include^any^mobile^or^non-mobile^computing^device^designed^to^communicate^with^a^RAN^304^via^an^over-the-air^connection.^The^ UE^302^may^be^communicatively^coupled^with^the^RAN^304^by^a^Uu^interface.^The^UE^302^may^be,^ but^ is^ not^ limited^ to,^ a^ smartphone,^ tablet^ computer,^ wearable^ computer^ device,^ desktop^computer,^ laptop^ computer,^ in-vehicle^ infotainment,^ in-car^ entertainment^ device,^ instrument^cluster,^head-up^display^device,^onboard^diagnostic^device,^dashtop^mobile^equipment,^mobile^data^ terminal,^electronic^engine^management^system,^electronic / engine^control^unit,^electronic / engine^ control^module,^embedded^system,^sensor,^microcontroller,^control^module,^engine^management^system,^networked^ appliance,^machine-type^ communication^ device,^M2M^or^D2D^device,^ IoT^device,^etc.^^

[0073] ^ In^some^embodiments,^the^network^300^may^include^a^plurality^of^UEs^coupled^directly^with^one^another^via^a^sidelink^interface.^The^UEs^may^be^M2M / D2D^devices^that^communicate^ using^physical^sidelink^channels^such^as,^but^not^limited^to,^PSBCH,^PSDCH,^PSSCH,^PSCCH,^ PSFCH,^etc.^^^^

[0074] ^ In^some^embodiments,^the^UE^302^may^additionally^communicate^with^an^AP^306^via^an^over-the-air^ connection.^ The^AP^ 306^ may^ manage^ a^WLAN^ connection,^ which^ may^ serve^ to^offload^some / all^network^traffic^from^the^RAN^304.^The^connection^between^the^UE^302^and^the^ AP^306^may^be^consistent^with^any^IEEE^802.11^protocol,^wherein^the^AP^306^could^be^a^wireless^ fidelity^(Wi-Fi®)^router.^In^some^embodiments,^the^UE^302,^RAN^304,^and^AP^306^may^utilize^ cellular-WLAN^aggregation^(for^example,^LWA / LWIP).^Cellular-WLAN^aggregation^may^involve^ the^UE^302^being^configured^by^the^RAN^304^to^utilize^both^cellular^radio^resources^and^WLAN^ resources.^^

[0075] ^ The^RAN^304^may^include^one^or^more^access^nodes,^for^example,^AN^308.^AN^308^may^terminate^air-interface^protocols^for^the^UE^302^by^providing^access^stratum^protocols^including^ RRC,^PDCP,^RLC,^MAC,^and^L1^protocols.^In^this^manner,^the^AN^308^may^enable^data / voice^connectivity^ between^ CN^ 320^ and^ the^ UE^ 302.^ In^ some^ embodiments,^ the^AN^ 308^ may^ be^implemented^in^a^discrete^device^or^as^one^or^more^software^entities^running^on^server^computers^ as^part^of,^for^example,^a^virtual^network,^which^may^be^referred^to^as^a^CRAN^or^virtual^baseband^ unit^pool.^The^AN^308^be^referred^to^as^a^BS,^gNB,^RAN^node,^eNB,^ng-eNB,^NodeB,^RSU,^TRxP,^ TRP,^etc.^The^AN^308^may^be^a^macrocell^base^station^or^a^low^power^base^station^for^providing^femtocells,^picocells^or^other^ like^cells^having^smaller^coverage^areas,^smaller^user^capacity,^or^higher^bandwidth^compared^to^macrocells.^^

[0076] ^ In^embodiments^in^which^the^RAN^304^includes^a^plurality^of^ANs,^they^may^be^coupled^with^one^another^via^an^X2^interface^(if^the^RAN^304^is^an^LTE^RAN)^or^an^Xn^interface^(if^the^ RAN^304^is^a^5G^RAN).^The^X2 / Xn^interfaces,^which^may^be^separated^into^control / user^plane^interfaces^ in^ some^ embodiments,^ may^ allow^ the^ANs^ to^ communicate^ information^ related^ to^handovers,^data / context^transfers,^mobility,^load^management,^interference^coordination,^etc.^

[0077] ^ The^ANs^of^the^RAN^304^may^each^manage^one^or^more^cells,^cell^groups,^component^carriers,^etc.^to^provide^the^UE^302^with^an^air^interface^for^network^access.^The^UE^302^may^be^ simultaneously^connected^with^a^plurality^of^cells^provided^by^the^same^or^different^ANs^of^the^ RAN^304.^For^example,^the^UE^302^and^RAN^304^may^use^carrier^aggregation^to^allow^the^UE^ 302^to^connect^with^a^plurality^of^component^carriers,^each^corresponding^to^a^Pcell^or^Scell.^^In^ dual^connectivity^scenarios,^a^first^AN^may^be^a^master^node^that^provides^an^MCG^and^a^second^ AN^may^be^secondary^node^that^provides^an^SCG.^The^first / second^ANs^may^be^any^combination^ of^eNB,^gNB,^ng-eNB,^etc.^^

[0078] ^ The^RAN^304^may^provide^the^air^interface^over^a^licensed^spectrum^or^an^unlicensed^spectrum.^To^operate^in^the^unlicensed^spectrum,^the^nodes^may^use^LAA,^eLAA,^and / or^feLAA^mechanisms^ based^ on^ CA^ technology^ with^ PCells / Scells.^ Prior^ to^ accessing^ the^ unlicensed^spectrum,^ the^nodes^may^perform^medium / carrier-sensing^operations^ based^on,^ for^ example,^ a^listen-before-talk^(LBT)^protocol.^^

[0079] ^ In^V2X^scenarios^the^UE^302^or^AN^308^may^be^or^act^as^a^RSU,^which^may^refer^to^any^transportation^infrastructure^entity^used^for^V2X^communications.^An^RSU^may^be^implemented^ in^or^by^a^suitable^AN^or^a^stationary^(or^relatively^stationary)^UE.^An^RSU^implemented^in^or^by:^ a^UE^may^be^referred^to^as^a^“UE-type^RSU”;^an^eNB^may^be^referred^to^as^an^“eNB-type^RSU”;^a^ gNB^may^be^ referred^ to^ as^ a^ “gNB-type^RSU”;^ and^ the^ like.^ In^ one^ example,^ an^RSU^ is^ a^computing^ device^ coupled^ with^ radio^ frequency^ circuitry^ located^ on^ a^ roadside^ that^ provides^connectivity^ support^ to^ passing^ vehicle^UEs.^The^RSU^may^ also^ include^ internal^ data^ storage^circuitry^ to^ store^ intersection^ map^ geometry,^ traffic^ statistics,^ media,^ as^ well^ as^applications / software^to^sense^and^control^ongoing^vehicular^and^pedestrian^traffic.^The^RSU^may^ provide^very^low^latency^communications^required^for^high^speed^events,^such^as^crash^avoidance,^traffic^ warnings,^ and^ the^ like.^ Additionally^ or^ alternatively,^ the^ RSU^ may^ provide^ other^cellular / WLAN^ communications^ services.^The^ components^ of^ the^ RSU^may^be^packaged^ in^ a^weatherproof^ enclosure^ suitable^ for^ outdoor^ installation,^ and^may^ include^ a^ network^ interface^controller^to^provide^a^wired^connection^(e.g.,^Ethernet)^to^a^traffic^signal^controller^or^a^backhaul^ network.^

[0080] ^ In^some^embodiments,^the^RAN^304^may^be^an^LTE^RAN^310^with^eNBs,^for^example,^eNB^312.^The^LTE^RAN^310^may^provide^an^LTE^air^interface^with^the^following^characteristics:^ SCS^of^15^kHz;^CP-OFDM^waveform^for^DL^and^SC-FDMA^waveform^for^UL;^turbo^codes^for^ data^and^TBCC^for^control;^etc.^The^LTE^air^interface^may^rely^on^CSI-RS^for^CSI^acquisition^and^ beam^management;^PDSCH / PDCCH^DMRS^for^PDSCH / PDCCH^demodulation;^and^CRS^for^cell^ search^and^initial^acquisition,^channel^quality^measurements,^and^channel^estimation^for^coherent^ demodulation / detection^at^the^UE.^The^LTE^air^interface^may^operating^on^sub-6^GHz^bands.^

[0081] ^ In^some^embodiments,^the^RAN^304^may^be^an^NG-RAN^314^with^gNBs,^for^example,^gNB^316,^or^ng-eNBs,^for^example,^ng-eNB^318.^The^gNB^316^may^connect^with^5G-enabled^UEs^using^a^5G^NR^ interface.^The^gNB^316^may^connect^with^a^5G^core^ through^an^NG^ interface,^which^may^include^an^N2^interface^or^an^N3^interface.^The^ng-eNB^318^may^also^connect^with^the^ 5G^core^through^an^NG^interface,^but^may^connect^with^a^UE^via^an^LTE^air^interface.^The^gNB^ 316^and^the^ng-eNB^318^may^connect^with^each^other^over^an^Xn^interface.^^

[0082] ^ In^some^embodiments,^the^NG^interface^may^be^split^into^two^parts,^an^NG^user^plane^(NG-U)^interface,^which^carries^ traffic^data^between^the^nodes^of^the^NG-RAN^314^and^a^UPF^348^(e.g.,^N3^interface),^and^an^NG^control^plane^(NG-C)^interface,^which^is^a^signaling^interface^ between^the^nodes^of^the^NG-RAN^314^and^an^AMF^344^(e.g.,^N2^interface).^^

[0083] ^ The^NG-RAN^314^may^provide^a^5G-NR^air^interface^with^the^following^characteristics:^variable^SCS;^CP-OFDM^for^DL,^CP-OFDM^and^DFT-s-OFDM^for^UL;^polar,^repetition,^simplex,^ and^Reed-Muller^codes^for^control^and^LDPC^for^data.^The^5G-NR^air^interface^may^rely^on^CSI- RS,^PDSCH / PDCCH^DMRS^similar^to^the^LTE^air^interface.^The^5G-NR^air^interface^may^not^use^ a^CRS,^but^may^use^PBCH^DMRS^for^PBCH^demodulation;^PTRS^ for^phase^ tracking^ for^PDSCH;^and^tracking^reference^signal^for^time^tracking.^The^5G-NR^air^interface^may^operating^ on^FR1^bands^that^include^sub-6^GHz^bands^or^FR2^bands^that^include^bands^from^24.25^GHz^to^ 52.6^GHz.^The^5G-NR^air^interface^may^include^an^SSB^that^is^an^area^of^a^downlink^resource^grid^ that^includes^PSS / SSS / PBCH.^^

[0084] ^ In^some^embodiments,^the^5G-NR^air^interface^may^utilize^BWPs^for^various^purposes.^For^example,^BWP^can^be^used^for^dynamic^adaptation^of^the^SCS.^For^example,^the^UE^302^can^ be^configured^with^multiple^BWPs^where^each^BWP^configuration^has^a^different^SCS.^When^a^ BWP^change^is^indicated^to^the^UE^302,^the^SCS^of^the^transmission^is^changed^as^well.^Another^use^ case^ example^ of^ BWP^ is^ related^ to^ power^ saving.^ In^ particular,^ multiple^ BWPs^ can^ be^ configured^for^the^UE^302^with^different^amount^of^frequency^resources^(for^example,^PRBs)^to^support^data^transmission^under^different^ traffic^loading^scenarios.^A^BWP^containing^a^smaller^number^of^PRBs^can^be^used^for^data^transmission^with^small^traffic^load^while^allowing^power^ saving^at^the^UE^302^and^in^some^cases^at^the^gNB^316.^A^BWP^containing^a^larger^number^of^ PRBs^can^be^used^for^scenarios^with^higher^traffic^load.^^

[0085] ^ The^RAN^304^is^communicatively^coupled^to^CN^320^that^includes^network^elements^to^provide^ various^ functions^ to^ support^ data^ and^ telecommunications^ services^ to^customers / subscribers^(for^example,^users^of^UE^302).^The^components^of^ the^CN^320^may^be^implemented^in^one^physical^node^or^separate^physical^nodes.^In^some^embodiments,^NFV^may^ be^utilized^to^virtualize^any^or^all^of^the^functions^provided^by^the^network^elements^of^the^CN^320^ onto^physical^compute / storage^resources^in^servers,^switches,^etc.^A^logical^instantiation^of^the^CN^ 320^may^be^referred^to^as^a^network^slice,^and^a^logical^instantiation^of^a^portion^of^the^CN^320^ may^be^referred^to^as^a^network^sub-slice.^^

[0086] ^ In^some^embodiments,^the^CN^320^may^be^an^LTE^CN^322,^which^may^also^be^referred^to^as^an^EPC.^The^LTE^CN^322^may^include^MME^324,^SGW^326,^SGSN^328,^HSS^330,^PGW^332,^and^PCRF^334^coupled^with^one^another^over^ interfaces^(or^“reference^points”)^as^shown.^Functions^of^the^elements^of^the^LTE^CN^322^may^be^briefly^introduced^as^follows.^

[0087] ^ The^MME^324^may^implement^mobility^management^functions^to^track^a^current^location^of^the^UE^302^to^facilitate^paging,^bearer^activation / deactivation,^handovers,^gateway^selection,^ authentication,^etc.^^

[0088] ^ The^SGW^326^may^terminate^an^S1^interface^toward^ the^RAN^and^route^data^packets^between^the^RAN^and^the^LTE^CN^322.^The^SGW^326^may^be^a^local^mobility^anchor^point^for^inter-RAN^ node^ handovers^ and^ also^ may^ provide^ an^ anchor^ for^ inter-3GPP^ mobility.^ Other^responsibilities^may^include^lawful^intercept,^charging,^and^some^policy^enforcement.^

[0089] ^ The^SGSN^328^may^track^a^location^of^the^UE^302^and^perform^security^functions^and^access^control.^ In^addition,^ the^SGSN^328^may^perform^ inter-EPC^node^ signaling^ for^mobility^between^different^RAT^networks;^ PDN^and^ S-GW^selection^ as^ specified^by^MME^324;^MME^selection^for^handovers;^etc.^The^S3^reference^point^between^the^MME^324^and^the^SGSN^328^may^ enable^ user^ and^ bearer^ information^ exchange^ for^ inter-3GPP^ access^ network^mobility^ in^idle / active^states.^^

[0090] ^ The^HSS^330^may^include^a^database^for^network^users,^including^subscription-related^information^to^support^the^network^entities’^handling^of^communication^sessions.^The^HSS^330^can^ provide^ support^ for^ routing / roaming,^ authentication,^ authorization,^ naming / addressing^resolution,^location^dependencies,^etc.^An^S6a^reference^point^between^the^HSS^330^and^the^MME^ 324^may^enable^transfer^of^subscription^and^authentication^data^for^authenticating / authorizing^user^ access^to^the^LTE^CN^320.^

[0091] ^ The^PGW^332^may^terminate^an^SGi^interface^toward^a^data^network^(DN)^336^that^may^include^an^application / content^server^338.^The^PGW^332^may^route^data^packets^between^the^LTE^ CN^322^and^the^data^network^336.^The^PGW^332^may^be^coupled^with^the^SGW^326^by^an^S5^reference^ point^ to^ facilitate^user^ plane^ tunneling^ and^ tunnel^management.^The^ PGW^332^may^further^include^a^node^for^policy^enforcement^and^charging^data^collection^(for^example,^PCEF).^ Additionally,^the^SGi^reference^point^between^the^PGW^332^and^the^data^network^336^may^be^an^ operator^external^public,^a^private^PDN,^or^an^intra-operator^packet^data^network,^for^example,^for^ provision^of^IMS^services.^The^PGW^332^may^be^coupled^with^a^PCRF^334^via^a^Gx^reference^ point.^

[0092] ^ The^PCRF^334^is^the^policy^and^charging^control^element^of^the^LTE^CN^322.^The^PCRF^334^may^be^communicatively^coupled^to^the^app / content^server^338^to^determine^appropriate^QoS^ and^charging^parameters^for^service^flows.^The^PCRF^332^may^provision^associated^rules^into^a^ PCEF^(via^Gx^reference^point)^with^appropriate^TFT^and^QCI.^^

[0093] ^ In^some^embodiments,^the^CN^320^may^be^a^5GC^340.^The^5GC^340^may^include^an^AUSF^342,^AMF^344,^SMF^346,^UPF^348,^NSSF^350,^NEF^352,^NRF^354,^PCF^356,^UDM^358,^ and^AF^360^coupled^with^one^another^over^interfaces^(or^“reference^points”)^as^shown.^Functions^ of^the^elements^of^the^5GC^340^may^be^briefly^introduced^as^follows.^

[0094] ^ The^ AUSF^ 342^ may^ store^ data^ for^ authentication^ of^ UE^ 302^ and^ handle^authentication-related^ functionality.^ The^ AUSF^ 342^ may^ facilitate^ a^ common^ authentication^framework^for^various^access^types.^In^addition^to^communicating^with^other^elements^of^the^5GC^ 340^over^reference^points^as^shown,^the^AUSF^342^may^exhibit^an^Nausf^service-based^interface.^

[0095] ^ The^AMF^344^may^allow^other^functions^of^the^5GC^340^to^communicate^with^the^UE^302^and^the^RAN^304^and^to^subscribe^to^notifications^about^mobility^events^with^respect^to^the^UE^ 302.^ The^ AMF^ 344^ may^ be^ responsible^ for^ registration^ management^ (for^ example,^ for^registering^UE^302),^connection^management,^reachability^management,^mobility^management,^ lawful^interception^of^AMF-related^events,^and^access^authentication^and^authorization.^The^AMF^ 344^may^provide^transport^for^SM^messages^between^the^UE^302^and^the^SMF^346,^and^act^as^a^transparent^ proxy^ for^ routing^ SM^ messages.^AMF^ 344^ may^ also^ provide^ transport^ for^ SMS^messages^between^UE^302^and^an^SMSF.^AMF^344^may^interact^with^the^AUSF^342^and^the^UE^302^ to^perform^various^security^anchor^and^context^management^functions.^Furthermore,^AMF^344^may^be^a^termination^point^of^a^RAN^CP^interface,^which^may^include^or^be^an^N2^reference^ point^between^the^RAN^304^and^the^AMF^344;^and^the^AMF^344^may^be^a^termination^point^of^NAS^(N1)^signaling,^ and^perform^NAS^ciphering^ and^ integrity^protection.^AMF^344^may^also^support^NAS^signaling^with^the^UE^302^over^an^N3^IWF^interface.^^

[0096] ^ The^SMF^346^may^be^responsible^for^SM^(for^example,^session^establishment,^tunnel^management^between^UPF^348^and^AN^308);^UE^IP^address^allocation^and^management^(including^ optional^authorization);^selection^and^control^of^UP^function;^configuring^traffic^steering^at^UPF^ 348^to^route^traffic^to^proper^destination;^termination^of^interfaces^toward^policy^control^functions;^controlling^ part^ of^ policy^ enforcement,^ charging,^ and^ QoS;^ lawful^ intercept^ (for^ SM^ events^and^ interface^ to^ LI^ system);^ termination^ of^ SM^ parts^ of^ NAS^ messages;^ downlink^ data^notification;^ initiating^AN^specific^SM^information,^sent^via^AMF^344^over^N2^to^AN^308;^and^determining^SSC^mode^of^a^session.^SM^may^refer^to^management^of^a^PDU^session,^and^a^PDU^ session^or^“session”^may^refer^to^a^PDU^connectivity^service^that^provides^or^enables^the^exchange^ of^PDUs^between^the^UE^302^and^the^data^network^336.^^

[0097] ^ The^ UPF^ 348^ may^ act^ as^ an^ anchor^ point^ for^ intra-RAT^ and^ inter-RAT^ mobility,^an^ external^ PDU^ session^ point^ of^ interconnect^ to^ data^ network^336,^ and^ a^ branching^ point^ to^support^multi-homed^PDU^session.^The^UPF^348^may^also^perform^packet^routing^and^forwarding,^ perform^packet^inspection,^enforce^the^user^plane^part^of^policy^rules,^lawfully^intercept^packets^(UP^ collection),^ perform^ traffic^ usage^ reporting,^ perform^QoS^handling^ for^ a^user^ plane^ (e.g.,^packet^filtering,^gating,^UL / DL^rate^enforcement),^perform^uplink^traffic^verification^(e.g.,^SDF- to-QoS^flow^mapping),^transport^level^packet^marking^in^the^uplink^and^downlink,^and^perform^downlink^packet^buffering^and^downlink^data^notification^ triggering.^UPF^348^may^ include^an^uplink^classifier^to^support^routing^traffic^flows^to^a^data^network.^^

[0098] ^ The^NSSF^350^may^select^a^set^of^network^slice^instances^serving^the^UE^302.^The^NSSF^350^ may^ also^ determine^ allowed^ NSSAI^ and^ the^ mapping^ to^ the^ subscribed^ S-NSSAIs,^ if^needed.^The^NSSF^350^may^also^determine^the^AMF^set^to^be^used^to^serve^the^UE^302,^or^a^list^ of^candidate^AMFs^based^on^a^suitable^configuration^and^possibly^by^querying^the^NRF^354.^The^ selection^of^a^set^of^network^slice^instances^for^the^UE^302^may^be^triggered^by^the^AMF^344^with^ which^the^UE^302^is^registered^by^interacting^with^the^NSSF^350,^which^may^lead^to^a^change^of^AMF.^ The^NSSF^ 350^ may^ interact^ with^ the^AMF^ 344^ via^ an^ N22^ reference^ point;^ and^ may^communicate^with^another^NSSF^in^a^visited^network^via^an^N31^reference^point^(not^shown).^ Additionally,^the^NSSF^350^may^exhibit^an^Nnssf^service-based^interface.^

[0099] ^ The^NEF^352^may^securely^expose^services^and^capabilities^provided^by^3GPP^network^functions^for^third^party,^internal^exposure / re-exposure,^AFs^(e.g.,^AF^360),^edge^computing^or^fog^ computing^systems,^etc.^In^such^embodiments,^the^NEF^352^may^authenticate,^authorize,^or^throttle^the^AFs.^NEF^352^may^also^ translate^ information^exchanged^with^ the^AF^360^and^information^exchanged^with^internal^network^functions.^For^example,^the^NEF^352^may^translate^between^an^ AF-Service-Identifier^and^an^internal^5GC^information.^NEF^352^may^also^receive^information^ from^other^NFs^based^on^exposed^capabilities^of^other^NFs.^This^information^may^be^stored^at^the^NEF^ 352^ as^ structured^ data,^ or^ at^ a^ data^ storage^ NF^ using^ standardized^ interfaces.^ The^stored^ information^can^ then^be^ re-exposed^by^ the^NEF^352^ to^other^NFs^and^AFs,^or^used^for^other^ purposes^ such^ as^ analytics.^ Additionally,^ the^ NEF^ 352^ may^ exhibit^ an^ Nnef^service-based^interface.^

[0100] ^ The^ NRF^ 354^ may^ support^ service^ discovery^ functions,^ receive^ NF^ discovery^requests^from^NF^instances,^and^provide^the^information^of^the^discovered^NF^instances^to^the^NF^instances.^NRF^ 354^ also^maintains^ information^ of^ available^NF^ instances^ and^ their^ supported^services.^As^ used^ herein,^ the^ terms^ “instantiate,”^ “instantiation,”^ and^ the^ like^may^ refer^ to^ the^creation^of^an^instance,^and^an^“instance”^may^refer^to^a^concrete^occurrence^of^an^object,^which^ may^occur,^for^example,^during^execution^of^program^code.^Additionally,^the^NRF^354^may^exhibit^ the^Nnrf^service-based^interface.^

[0101] ^ The^ PCF^ 356^ may^ provide^ policy^ rules^ to^ control^ plane^ functions^ to^ enforce^ them,^and^may^also^support^unified^policy^framework^to^govern^network^behavior.^The^PCF^356^may^ also^implement^a^front^end^to^access^subscription^information^relevant^for^policy^decisions^in^a^UDR^of^ the^UDM^358.^ In^ addition^ to^ communicating^with^ functions^over^ reference^points^as^shown,^the^PCF^356^exhibit^an^Npcf^service-based^interface.^

[0102] ^ The^ UDM^ 358^ may^ handle^ subscription-related^ information^ to^ support^ the^network^entities’^handling^of^communication^sessions,^and^may^store^subscription^data^of^UE^302.^ For^example,^subscription^data^may^be^communicated^via^an^N8^reference^point^between^the^UDM^ 358^and^the^AMF^344.^The^UDM^358^may^include^two^parts,^an^application^front^end^and^a^UDR.^ The^UDR^may^store^subscription^data^and^policy^data^for^the^UDM^358^and^the^PCF^356,^and / or^structured^ data^ for^ exposure^ and^ application^ data^ (including^ PFDs^ for^ application^ detection,^application^request^information^for^multiple^UEs^302)^for^the^NEF^352.^The^Nudr^service-based^ interface^may^be^exhibited^by^the^UDR^to^allow^the^UDM^358,^PCF^356,^and^NEF^352^to^access^a^ particular^ set^ of^ the^ stored^ data,^ as^ well^ as^ to^ read,^ update^ (e.g.,^ add,^ modify),^ delete,^ and^ subscribe^to^notification^of^relevant^data^changes^in^the^UDR.^The^UDM^may^include^a^UDM-FE,^ which^is^in^charge^of^processing^credentials,^location^management,^subscription^management^and^ so^on.^Several^different^front^ends^may^serve^the^same^user^in^different^transactions.^The^UDM- FE^accesses^subscription^information^stored^in^the^UDR^and^performs^authentication^credential^ processing,^user^identification^handling,^access^authorization,^registration / mobility^management,^ and^subscription^management.^In^addition^to^communicating^with^other^NFs^over^reference^points^ as^shown,^the^UDM^358^may^exhibit^the^Nudm^service-based^interface.^^

[0103] ^ The^AF^360^may^provide^application^influence^on^traffic^routing,^provide^access^to^NEF,^and^interact^with^the^policy^framework^for^policy^control.^^

[0104] ^ In^ some^ embodiments,^ the^ 5GC^ 340^ may^ enable^ edge^ computing^ by^ selecting^operator / 3rd^party^services^to^be^geographically^close^to^a^point^that^the^UE^302^is^attached^to^the^network.^ This^ may^ reduce^ latency^ and^ load^ on^ the^ network.^ To^ provide^ edge-computing^implementations,^ the^5GC^340^may^select^ a^UPF^348^ close^ to^ the^UE^302^and^execute^ traffic^steering^from^the^UPF^348^to^data^network^336^via^the^N6^interface.^This^may^be^based^on^the^UE^ subscription^data,^UE^location,^and^information^provided^by^the^AF^360.^In^this^way,^the^AF^360^ may^influence^UPF^(re)selection^and^traffic^routing.^Based^on^operator^deployment,^when^AF^360^ is^considered^to^be^a^trusted^entity,^the^network^operator^may^permit^AF^360^to^interact^directly^ with^relevant^NFs.^Additionally,^the^AF^360^may^exhibit^an^Naf^service-based^interface.^

[0105] ^ The^data^network^336^may^represent^various^network^operator^services,^Internet^access,^or^ third^ party^ services^ that^ may^ be^ provided^ by^ one^ or^ more^ servers^ including,^ for^ example,^application / content^server^338.^^

[0106] ^ Figure^ 4^ schematically^ illustrates^ a^wireless^ network^ 400^ in^ accordance^with^ various^embodiments.^The^wireless^network^400^may^include^a^UE^402^in^wireless^communication^with^ an^AN^404.^The^UE^402^and^AN^404^may^be^similar^to,^and^substantially^interchangeable^with,^ like-named^components^described^elsewhere^herein.^^

[0107] ^ The^UE^402^may^be^communicatively^coupled^with^the^AN^404^via^connection^406.^The^connection^406^ is^ illustrated^as^ an^air^ interface^ to^enable^communicative^coupling,^and^can^be^consistent^with^cellular^communications^protocols^such^as^an^LTE^protocol^or^a^5G^NR^protocol^ operating^at^mmWave^or^sub-6GHz^frequencies.^

[0108] ^ The^UE^402^may^include^a^host^platform^408^coupled^with^a^modem^platform^410.^The^host^platform^408^may^include^application^processing^circuitry^412,^which^may^be^coupled^with^ protocol^processing^circuitry^414^of^the^modem^platform^410.^The^application^processing^circuitry^ 412^may^run^various^applications^for^the^UE^402^that^source / sink^application^data.^The^application^ processing^circuitry^412^may^further^implement^one^or^more^layer^operations^to^transmit / receive^ application^data^to / from^a^data^network.^These^layer^operations^may^include^transport^(for^example^ UDP)^and^Internet^(for^example,^IP)^operations.^^

[0109] ^ The^protocol^processing^circuitry^414^may^implement^one^or^more^of^layer^operations^to^facilitate^ transmission^ or^ reception^ of^ data^ over^ the^ connection^ 406.^ The^ layer^ operations^implemented^by^ the^protocol^ processing^ circuitry^ 414^may^ include,^ for^ example,^MAC,^RLC,^PDCP,^RRC^and^NAS^operations.^^

[0110] ^ The^modem^platform^410^may^further^include^digital^baseband^circuitry^416^that^may^implement^ one^ or^ more^ layer^ operations^ that^ are^ “below”^ layer^ operations^ performed^ by^ the^protocol^processing^circuitry^414^in^a^network^protocol^stack.^These^operations^may^include,^for^example,^ ^ PHY^ operations^ including^ one^ or^ more^ of^ HARQ-ACK^ functions,^scrambling / descrambling,^ encoding / decoding,^ layer^ mapping / de-mapping,^ modulation^symbol^ mapping,^ received^ symbol / bit^ metric^ determination,^ multi-antenna^ port^precoding / decoding,^ which^ may^ include^ one^ or^ more^ of^ space-time,^ space-frequency^ or^spatial^ coding,^ reference^ signal^ generation / detection,^ preamble^ sequence^ generation^and / or^ decoding,^ synchronization^ sequence^ generation / detection,^ control^ channel^ signal^blind^decoding,^and^other^related^functions.^

[0111] ^ The^modem^platform^410^may^further^include^transmit^circuitry^418,^receive^circuitry^420,^RF^circuitry^422,^and^RF^front^end^(RFFE)^424,^which^may^include^or^connect^to^one^or^more^ antenna^panels^426.^Briefly,^the^transmit^circuitry^418^may^include^a^digital-to-analog^converter,^mixer,^ intermediate^ frequency^ (IF)^ components,^ etc.;^ the^ receive^ circuitry^ 420^may^ include^ an^analog-to-digital^converter,^mixer,^IF^components,^etc.;^the^RF^circuitry^422^may^include^a^low- noise^amplifier,^a^power^amplifier,^power^tracking^components,^etc.;^RFFE^424^may^include^filters^(for^ example,^ surface / bulk^ acoustic^ wave^ filters),^ switches,^ antenna^ tuners,^ beamforming^components^(for^example,^phase-array^antenna^components),^etc.^The^selection^and^arrangement^ of^the^components^of^the^transmit^circuitry^418,^receive^circuitry^420,^RF^circuitry^422,^RFFE^424,^ and^antenna^panels^426^(referred^generically^as^“transmit / receive^components”)^may^be^specific^ to^details^of^a^specific^implementation^such^as,^for^example,^whether^communication^is^TDM^or^FDM,^ in^mmWave^ or^ sub-6^ gHz^ frequencies,^ etc.^ In^ some^ embodiments,^ the^ transmit / receive^components^may^be^arranged^in^multiple^parallel^transmit / receive^chains,^may^be^disposed^in^the^ same^or^different^chips / modules,^etc.^^

[0112] ^ In^ some^ embodiments,^ the^ protocol^ processing^ circuitry^ 414^ may^ include^ one^ or^more^instances^of^control^circuitry^(not^shown)^to^provide^control^functions^for^the^transmit / receive^ components.^

[0113] ^ A^UE^reception^may^be^established^by^and^via^the^antenna^panels^426,^RFFE^424,^RF^circuitry^ 422,^ receive^ circuitry^ 420,^ digital^ baseband^ circuitry^ 416,^ and^ protocol^ processing^circuitry^414.^ In^ some^embodiments,^ the^antenna^panels^ 426^may^ receive^a^ transmission^ from^the^AN^404^by^receive-beamforming^signals^received^by^a^plurality^of^antennas / antenna^elements^ of^the^one^or^more^antenna^panels^426.^

[0114] ^ A^UE^transmission^may^be^established^by^and^via^the^protocol^processing^circuitry^414,^digital^baseband^circuitry^416,^transmit^circuitry^418,^RF^circuitry^422,^RFFE^424,^and^antenna^ panels^426.^In^some^embodiments,^the^transmit^components^of^the^UE^404^may^apply^a^spatial^filter^to^ the^data^ to^be^ transmitted^to^ form^a^transmit^beam^emitted^by^the^antenna^elements^of^the^antenna^panels^426.^^

[0115] ^ Similar^ to^ the^UE^402,^ the^AN^ 404^may^ include^ a^host^ platform^428^ coupled^with^ a^modem^platform^430.^The^host^platform^428^may^ include^application^processing^ circuitry^ 432^coupled^with^protocol^processing^circuitry^434^of^the^modem^platform^430.^The^modem^platform^ may^further^include^digital^baseband^circuitry^436,^transmit^circuitry^438,^receive^circuitry^440,^ RF^circuitry^442,^RFFE^circuitry^444,^and^antenna^panels^446.^The^components^of^the^AN^404^ may^be^similar^to^and^substantially^interchangeable^with^like-named^components^of^the^UE^402.^ In^addition^to^performing^data^transmission / reception^as^described^above,^the^components^of^the^ AN^408^may^perform^various^logical^functions^that^include,^for^example,^RNC^functions^such^as^radio^bearer^management,^uplink^and^downlink^dynamic^ radio^ resource^management,^and^data^packet^scheduling.^^

[0116] ^ Figure^ 5^ is^ a^ block^ diagram^ illustrating^ components,^ according^ to^ some^ example^embodiments,^able^ to^read^ instructions^ from^a^machine-readable^or^computer-readable^medium^(e.g.,^ a^non-transitory^machine-readable^ storage^medium)^and^perform^any^one^or^more^of^ the^methodologies^discussed^herein.^Specifically,^Figure^5^shows^a^diagrammatic^ representation^of^hardware^resources^500^including^one^or^more^processors^(or^processor^cores)^510,^one^or^more^ memory / storage^devices^520,^and^one^or^more^communication^resources^530,^each^of^which^may^ be^communicatively^coupled^via^a^bus^540^or^other^interface^circuitry.^For^embodiments^where^node^ virtualization^ (e.g.,^ NFV)^ is^ utilized,^ a^ hypervisor^ 502^ may^ be^ executed^ to^ provide^ an^execution^environment^for^one^or^more^network^slices / sub-slices^to^utilize^the^hardware^resources^ 500.^^

[0117] ^ The^processors^510^may^include,^for^example,^a^processor^512^and^a^processor^514.^The^processors^510^may^be,^for^example,^a^central^processing^unit^(CPU),^a^ reduced^ instruction^set^computing^(RISC)^processor,^a^complex^instruction^set^computing^(CISC)^processor,^a^graphics^ processing^unit^(GPU),^a^DSP^such^as^a^baseband^processor,^an^ASIC,^an^FPGA,^a^radio-frequency^integrated^circuit^ (RFIC),^another^processor^ (including^ those^discussed^herein),^or^any^ suitable^combination^thereof.^

[0118] ^ The^memory / storage^devices^520^may^include^main^memory,^disk^storage,^or^any^suitable^combination^thereof.^The^memory / storage^devices^520^may^ include,^but^are^not^ limited^ to,^any^type^of^volatile,^non-volatile,^or^semi-volatile^memory^such^as^dynamic^random^access^memory^(DRAM),^ static^ random^ access^ memory^ (SRAM),^ erasable^ programmable^ read-only^ memory^(EPROM),^ electrically^ erasable^ programmable^ read-only^ memory^ (EEPROM),^ Flash^memory,^solid-state^storage,^etc.^^

[0119] ^ The^ communication^ resources^ 530^may^ include^ interconnection^ or^ network^ interface^controllers,^components,^or^other^suitable^devices^ to^communicate^with^one^or^more^peripheral^devices^504^ or^one^ or^more^ databases^ 506^ or^other^network^ elements^ via^ a^ network^ 508.^ For^example,^the^communication^resources^530^may^include^wired^communication^components^(e.g.,^for^ coupling^ via^USB,^ Ethernet,^ etc.),^ cellular^ communication^ components,^NFC^ components,^Bluetooth®^ (or^ Bluetooth®^ Low^ Energy)^ components,^ Wi-Fi®^ components,^ and^ other^communication^components.^^

[0120] ^ Instructions^550^may^comprise^software,^a^program,^an^application,^an^applet,^an^app,^or^other^executable^code^for^causing^at^least^any^of^the^processors^510^to^perform^any^one^or^more^of^the^methodologies^ discussed^ herein.^ The^ instructions^ 550^may^ reside,^ completely^ or^ partially,^within^ at^ least^ one^ of^ the^ processors^ 510^ (e.g.,^ within^ the^ processor’s^ cache^ memory),^ the^memory / storage^devices^520,^or^any^suitable^combination^thereof.^Furthermore,^any^portion^of^the^ instructions^550^may^be^transferred^to^the^hardware^resources^500^from^any^combination^of^the^peripheral^ devices^ 504^ or^ the^ databases^ 506.^Accordingly,^ the^memory^ of^ processors^ 510,^ the^memory / storage^devices^520,^the^peripheral^devices^504,^and^the^databases^806^are^examples^of^ computer-readable^and^machine-readable^media.^

[0121] ^ Figure^6^illustrates^a^network^600^in^accordance^with^various^embodiments.^The^network^600^may^operate^in^a^matter^consistent^with^3GPP^technical^specifications^or^technical^reports^for^ 6G^systems.^In^some^embodiments,^the^network^600^may^operate^concurrently^with^network^300.^For^ example,^ in^ some^ embodiments,^ the^ network^ 600^ may^ share^ one^ or^ more^ frequency^ or^bandwidth^resources^with^network^300.^As^one^specific^example,^a^UE^ (e.g.,^UE^602)^may^be^ configured^to^operate^in^both^network^600^and^network^300.^Such^configuration^may^be^based^on^ a^UE^including^circuitry^configured^for^communication^with^frequency^and^bandwidth^resources^ of^both^networks^300^and^600.^In^general,^several^elements^of^network^600^may^share^one^or^more^ characteristics^with^elements^of^network^300.^For^the^sake^of^brevity^and^clarity,^such^elements^ may^not^be^repeated^in^the^description^of^network^600.^

[0122] ^ The^network^600^may^include^a^UE^602,^which^may^include^any^mobile^or^non-mobile^computing^device^designed^to^communicate^with^a^RAN^608^via^an^over-the-air^connection.^The^UE^602^may^be^similar^ to,^for^example,^UE^302.^The^UE^602^may^be,^but^ is^not^ limited^ to,^a^smartphone,^tablet^computer,^wearable^computer^device,^desktop^computer,^laptop^computer,^in-vehicle^ infotainment,^ in-car^ entertainment^ device,^ instrument^ cluster,^ head-up^ display^ device,^onboard^diagnostic^ device,^ dashtop^mobile^ equipment,^mobile^ data^ terminal,^ electronic^ engine^management^system,^electronic / engine^control^unit,^electronic / engine^control^module,^embedded^ system,^sensor,^microcontroller,^control^module,^engine^management^system,^networked^appliance,^ machine-type^communication^device,^M2M^or^D2D^device,^IoT^device,^etc.^^

[0123] ^ Although^not^specifically^shown^in^Figure^6,^in^some^embodiments^the^network^600^may^include^a^plurality^of^UEs^coupled^directly^with^one^another^via^a^sidelink^interface.^The^UEs^may^ be^M2M / D2D^devices^that^communicate^using^physical^sidelink^channels^such^as,^but^not^limited^ to,^PSBCH,^PSDCH,^PSSCH,^PSCCH,^PSFCH,^etc.^Similarly,^although^not^specifically^shown^in^ Figure^6,^the^UE^602^may^be^communicatively^coupled^with^an^AP^such^as^AP^306^as^described^with^ respect^ to^ Figure^ 3.^Additionally,^ although^ not^ specifically^ shown^ in^ Figure^ 6,^ in^ some^embodiments^ the^RAN^608^may^ include^one^or^more^ANss^such^as^AN^308^as^described^with^respect^to^Figure^3.^The^RAN^608^and / or^the^AN^of^the^RAN^608^may^be^referred^to^as^a^base^ station^(BS),^a^RAN^node,^or^using^some^other^term^or^name.^^

[0124] ^ The^UE^602^and^the^RAN^608^may^be^configured^to^communicate^via^an^air^interface^that^may^be^referred^to^as^a^sixth^generation^(6G)^air^interface.^The^6G^air^interface^may^include^ one^or^more^features^such^as^communication^in^a^terahertz^(THz)^or^sub-THz^bandwidth,^or^joint^communication^ and^sensing.^As^used^herein,^ the^ term^“joint^communication^and^sensing”^may^refer^to^a^system^that^allows^for^wireless^communication^as^well^as^radar-based^sensing^via^various^ types^of^multiplexing.^As^used^herein,^THz^or^sub-THz^bandwidths^may^refer^to^communication^in^ the^ 80^ GHz^ and^ above^ frequency^ ranges.^ Such^ frequency^ ranges^ may^ additionally^ or^alternatively^be^referred^to^as^“millimeter^wave”^or^“mmWave”^frequency^ranges.^

[0125] ^ The^RAN^608^may^allow^for^communication^between^the^UE^602^and^a^6G^core^network^(CN)^610.^Specifically,^the^RAN^608^may^facilitate^the^transmission^and^reception^of^data^between^ the^UE^602^and^the^6G^CN^610.^The^6G^CN^610^may^include^various^functions^such^as^NSSF^350,^ NEF^352,^NRF^354,^PCF^356,^UDM^358,^AF^360,^SMF^346,^and^AUSF^342.^The^6G^CN^610^may^ additional^include^UPF^348^and^DN^336^as^shown^in^Figure^6.^

[0126] ^ Additionally,^the^RAN^608^may^include^various^additional^functions^that^are^in^addition^to,^or^alternative^to,^functions^of^a^legacy^cellular^network^such^as^a^4G^or^5G^network.^Two^such^functions^ may^ include^ a^ Compute^ Control^ Function^ (Comp^ CF)^ 624^ and^ a^ Compute^ Service^Function^(Comp^SF)^636.^The^Comp^CF^624^and^the^Comp^SF^636^may^be^parts^or^functions^of^the^ Computing^ Service^ Plane.^ Comp^ CF^ 624^ may^ be^ a^ control^ plane^ function^ that^ provides^functionalities^ such^ as^ management^ of^ the^ Comp^ SF^ 636,^ computing^ task^ context^ generation^and^ management^ (e.g.,^ create,^ read,^ modify,^ delete),^ interaction^ with^ the^ underlaying^computing^infrastructure^for^computing^resource^management,^etc..^Comp^SF^636^may^be^a^user^ plane^function^that^serves^as^the^gateway^to^interface^computing^service^users^(such^as^UE^602)^ and^computing^nodes^behind^a^Comp^SF^instance.^Some^functionalities^of^the^Comp^SF^636^may^include:^ parse^ computing^ service^ data^ received^ from^ users^ to^ compute^ tasks^ executable^ by^computing^nodes;^hold^service^mesh^ingress^gateway^or^service^API^gateway;^service^and^charging^ policies^enforcement;^performance^monitoring^and^telemetry^collection,^etc.^In^some^embodiments,^ a^Comp^SF^636^instance^may^serve^as^the^user^plane^gateway^for^a^cluster^of^computing^nodes.^A^ Comp^CF^624^instance^may^control^one^or^more^Comp^SF^636^instances.^^

[0127] ^ Two^other^such^functions^may^include^a^Communication^Control^Function^(Comm^CF)^628^ and^ a^ Communication^ Service^ Function^ (Comm^ SF)^ 638,^ which^ may^ be^ parts^ of^ the^Communication^Service^Plane.^The^Comm^CF^628^may^be^the^control^plane^function^for^managing^the^ Comm^ SF^ 638,^ communication^ sessions^ creation / configuration / releasing,^ and^ managing^communication^session^context.^The^Comm^SF^638^may^be^a^user^plane^function^for^data^transport.^ Comm^CF^628^and^Comm^SF^638^may^be^considered^as^upgrades^of^SMF^346^and^UPF^348,^which^were^described^with^ respect^ to^ a^5G^system^ in^Figure^3.^The^upgrades^ provided^by^ the^Comm^CF^628^and^the^Comm^SF^638^may^enable^service-aware^transport.^For^legacy^(e.g.,^4G^or^ 5G)^data^transport,^SMF^346^and^UPF^348^may^still^be^used.^^

[0128] ^ Two^other^such^functions^may^include^a^Data^Control^Function^(Data^CF)^622^and^Data^Service^Function^(Data^SF)^632^may^be^parts^of^the^Data^Service^Plane.^Data^CF^622^may^be^a^ control^plane^function^and^provides^functionalities^such^as^Data^SF^632^management,^Data^service^ creation / configuration / releasing,^Data^service^context^management,^etc.^Data^SF^632^may^be^a^ user^plane^function^and^serve^as^the^gateway^between^data^service^users^(such^as^UE^602^and^the^various^ functions^ of^ the^ 6G^CN^610)^ and^data^ service^ endpoints^behind^ the^gateway.^Specific^functionalities^may^include:^parse^data^service^user^data^and^forward^to^corresponding^data^service^ endpoints,^generate^charging^data,^report^data^service^status.^^

[0129] ^ Another^such^function^may^be^the^Service^Orchestration^and^Chaining^Function^(SOCF)^620,^ which^ may^ discover,^ orchestrate^ and^ chain^ up^ communication / computing / data^ services^provided^by^functions^in^the^network.^Upon^receiving^service^requests^from^users,^SOCF^620^may^ interact^with^one^or^more^of^Comp^CF^624,^Comm^CF^628,^and^Data^CF^622^to^identify^Comp^SF^636,^Comm^SF^638,^and^Data^SF^632^ instances,^ configure^service^ resources,^and^generate^ the^service^ chain,^which^ could^ contain^multiple^Comp^SF^ 636,^Comm^SF^ 638,^ and^Data^ SF^ 632^instances^and^their^associated^computing^endpoints.^Workload^processing^and^data^movement^may^ then^be^conducted^within^the^generated^service^chain.^The^SOCF^620^may^also^responsible^for^ maintaining,^updating,^and^releasing^a^created^service^chain.^^

[0130] ^ Another^such^function^may^be^the^service^registration^function^(SRF)^614,^which^may^ act^as^a^registry^for^system^services^provided^in^the^user^plane^such^as^services^provided^by^service^ endpoints^behind^Comp^SF^636^and^Data^SF^632^gateways^and^services^provided^by^the^UE^602.^^The^SRF^614^may^be^considered^a^ counterpart^of^NRF^354,^which^may^act^ as^ the^ registry^ for^network^functions.^^^

[0131] ^ Other^such^functions^may^include^an^evolved^service^communication^proxy^(eSCP)^and^service^ infrastructure^ control^ function^ (SICF)^ 626,^which^may^provide^ service^ communication^infrastructure^for^control^plane^services^and^user^plane^services.^The^eSCP^may^be^related^to^the^service^ communication^ proxy^ (SCP)^ of^ 5G^ with^ user^ plane^ service^ communication^ proxy^capabilities^being^added.^The^eSCP^is^therefore^expressed^in^two^parts:^eCSP-C^612^and^eSCP-U^ 634,^for^control^plane^service^communication^proxy^and^user^plane^service^communication^proxy,^ respectively.^The^SICF^626^may^control^and^configure^eCSP^instances^in^terms^of^service^traffic^ routing^policies,^access^rules,^load^balancing^configurations,^performance^monitoring,^etc.^^

[0132] ^ Another^such^function^is^the^AMF^644.^The^AMF^644^may^be^similar^to^344,^but^with^additional^functionality.^Specifically,^the^AMF^644^may^include^potential^ functional^repartition,^such^as^move^the^message^forwarding^functionality^from^the^AMF^644^to^the^RAN^608.^

[0133] ^ Another^such^function^is^the^service^orchestration^exposure^function^(SOEF)^618.^The^SOEF^may^be^configured^to^expose^service^orchestration^and^chaining^services^to^external^users^ such^as^applications.^

[0134] ^ The^UE^602^may^include^an^additional^function^that^is^referred^to^as^a^computing^client^service^ function^ (comp^ CSF)^ 604.^ The^ comp^ CSF^ 604^ may^ have^ both^ the^ control^plane^functionalities^and^user^plane^functionalities,^and^may^interact^with^corresponding^network^ side^functions^such^as^SOCF^620,^Comp^CF^624,^Comp^SF^636,^Data^CF^622,^and / or^Data^SF^632^ for^service^discovery,^request / response,^compute^task^workload^exchange,^etc.^The^Comp^CSF^604^ may^also^work^with^network^side^functions^to^decide^on^whether^a^computing^task^should^be^run^ on^the^UE^602,^the^RAN^608,^and / or^an^element^of^the^6G^CN^610.^

[0135] ^ The^UE^ 602^ and / or^ the^Comp^CSF^604^may^ include^ a^ service^mesh^proxy^606.^The^ service^mesh^proxy^606^may^act^as^a^proxy^for^service-to-service^communication^in^the^user^plane.^ Capabilities^of^the^service^mesh^proxy^606^may^include^one^or^more^of^addressing,^security,^load^ balancing,^etc.^

[0136] ^ The^following^paragraphs^describe^examples^of^various^embodiments.^

[0137] ^ Example^1^includes^an^apparatus,^comprising:^interface^circuitry;^and^processor^circuitry^coupled^with^the^interface^circuitry,^wherein^the^processor^circuitry^is^to:^determine^a^time^period^ for^time^index^detection^for^a^Synchronization^Signal^Block^(SSB)^of^a^deactivated^cell^with^an^SSB^bandwidth^ of^12^Physical^Resource^Blocks^ (PRBs),^ based^on^ a^Discontinuous^Reception^(DRX)^cycle,^a^measurement^cycle^for^the^deactivated^cell,^and^a^Carrier^Specific^Scaling^Factor^(CSSF);^ and^ perform^measurement^ for^ the^ SSB^ based^ on^ the^ time^ period^ for^ the^ time^ index^detection.^

[0138] ^ Example^2^includes^the^apparatus^of^Example^1,^wherein^the^deactivated^cell^includes^a^deactivated^Secondary^Cell^(SCell)^or^a^deactivated^Primary^SCell^(PSCell).^

[0139] ^ Example^3^includes^the^apparatus^of^Example^1^or^2,^wherein^the^processor^circuitry^is^further^to:^determine^the^time^period^for^the^time^index^detection^further^based^on^a^scaling^factor^for^ an^ SSB^ frequency^ layer^ to^ be^ measured^ without^ GAP^ and^ a^ nominal^ number^ of^ SSB^measurement^samples,^wherein^the^nominal^number^of^SSB^measurement^samples^is^7.^

[0140] ^ Example^4^includes^the^apparatus^of^any^of^Examples^1^to^3,^wherein^the^deactivated^cell^is^to^operate^in^a^system^having^a^bandwidth^less^than^5^MHz.^

[0141] ^ Example^5^includes^the^apparatus^of^any^of^Examples^1^to^4,^wherein^the^deactivated^cell^is^to^operate^in^Frequency^Range^1^(FR1).^

[0142] ^ Example^6^includes^the^apparatus^of^any^of^Examples^1^to^5,^wherein^the^deactivated^cell^includes^a^deactivated^Primary^Secondary^Cell^(PSCell),^and^wherein^the^processor^circuitry^is^further^ to:^determine^a^ time^for^ fine^time^tracking^and^ acquiring^ full^ timing^ information^of^ the^deactivated^PSCell^to^be^triple^that^for^a^deactivated^PSCell^with^an^SSB^bandwidth^other^than^12^ PRBs.^

[0143] ^ Example^7^includes^the^apparatus^of^any^of^Examples^1^to^5,^wherein^the^deactivated^cell^includes^a^deactivated^Secondary^Cell^(SCell),^and^wherein^the^processor^circuitry^is^further^to:^ determine^a^time^for^fine^time^tracking^and^acquiring^full^timing^information^of^the^deactivated^ SCell^to^be^a^value^greater^than^zero.^

[0144] ^ Example^8^includes^the^apparatus^of^Example^7,^wherein^the^processor^circuitry^is^further^to:^activate^the^deactivated^SCell^based^on^a^SCell^activation^delay^requirement,^wherein^the^SCell^ activation^delay^requirement^is^based^on^the^time^for^fine^time^tracking^and^acquiring^full^timing^ information^of^the^deactivated^SCell.^

[0145] ^ Example^ 9^ includes^ the^ apparatus^of^ any^ of^Examples^ 1^ to^ 8,^wherein^ the^processor^circuitry^is^further^to:^determine^that^the^SSB^bandwidth^of^the^deactivated^cell^is^12^PRBs^based^ on^a^message^received^from^an^Access^Node^(AN)^via^the^interface^circuitry.^

[0146] ^ Example^10^includes^the^apparatus^of^Example^9,^wherein^the^message^is^to^indicate^that^the^SSB^bandwidth^of^the^deactivated^cell^is^12^PRBs.^

[0147] ^ Example^11^includes^the^apparatus^of^Example^9,^wherein^the^message^is^to^indicate^a^carrier^bandwidth^of^the^deactivated^cell,^and^wherein^the^processor^circuitry^is^further^to:^derive^ the^SSB^bandwidth^of^the^deactivated^cell^from^the^carrier^bandwidth.^

[0148] ^ Example^12^includes^the^apparatus^of^any^of^Examples^1^to^11,^wherein^the^apparatus^is^applicable^to^a^User^Equipment^(UE).^

[0149] ^ Example^13^includes^a^computer-readable^medium^having^instructions^stored^thereon,^wherein^the^instructions,^when^executed^by^processing^circuitry,^cause^the^processing^circuitry^to:^ determine^a^time^period^for^time^index^detection^for^a^Synchronization^Signal^Block^(SSB)^of^a^deactivated^ cell^with^ an^ SSB^ bandwidth^ of^ 12^ Physical^ Resource^Blocks^ (PRBs),^ based^ on^ a^Discontinuous^ Reception^ (DRX)^ cycle,^ a^ number^ of^ available^ SSB^ measurement^ samples,^ a^measurement^cycle^ for^ the^deactivated^cell,^and^a^Carrier^Specific^Scaling^Factor^ (CSSF);^and^perform^measurement^for^the^SSB^based^on^the^time^period^for^the^time^index^detection.^

[0150] ^ Example^ 14^ includes^ the^ computer-readable^ medium^ of^ Example^ 13,^ wherein^ the^deactivated^ cell^ includes^ a^deactivated^Secondary^Cell^ (SCell)^ or^ a^ deactivated^ Primary^SCell^(PSCell).^

[0151] ^ Example^15^includes^the^computer-readable^medium^of^Example^13^or^14,^wherein^the^number^of^available^SSB^measurement^samples^is^based^on^a^scaling^factor^for^an^SSB^frequency^ layer^to^be^measured^without^GAP^and^a^nominal^number^of^SSB^measurement^samples,^wherein^ the^nominal^number^of^SSB^measurement^samples^is^7.^

[0152] ^ Example^ 16^ includes^ the^ computer-readable^ medium^ of^ any^ of^ Examples^ 13^ to^ 15,^wherein^the^deactivated^cell^is^to^operate^in^a^system^having^a^bandwidth^less^than^5^MHz.^

[0153] ^ Example^ 17^ includes^ the^ computer-readable^ medium^ of^ any^ of^ Examples^ 13^ to^ 16,^wherein^the^deactivated^cell^is^to^operate^in^Frequency^Range^1^(FR1).^

[0154] ^ Example^ 18^ includes^ the^ computer-readable^ medium^ of^ any^ of^ Examples^ 13^ to^ 17,^wherein^the^deactivated^cell^includes^a^deactivated^Primary^Secondary^Cell^(PSCell),^and^wherein^ the^instructions,^when^executed^by^the^processing^circuitry,^cause^the^processing^circuitry^further^ to:^determine^a^time^for^fine^time^tracking^and^acquiring^full^timing^information^of^the^deactivated^ PSCell^to^be^triple^that^for^a^deactivated^PSCell^with^an^SSB^bandwidth^other^than^12^PRBs.^

[0155] ^ Example^ 19^ includes^ the^ computer-readable^ medium^ of^ any^ of^ Examples^ 13^ to^ 17,^wherein^ the^ deactivated^ cell^ includes^ a^ deactivated^ Secondary^ Cell^ (SCell),^ and^ wherein^ the^instructions,^when^executed^by^the^processing^circuitry,^cause^the^processing^circuitry^further^to:^ determine^a^time^for^fine^time^tracking^and^acquiring^full^timing^information^of^the^deactivated^ SCell^to^be^a^value^greater^than^zero.^

[0156] ^ Example^ 20^ includes^ the^ computer-readable^ medium^ of^ Example^ 19,^ wherein^ the^instructions,^when^executed^by^the^processing^circuitry,^cause^the^processing^circuitry^further^to:^ activate^the^deactivated^SCell^based^on^a^SCell^activation^delay^requirement,^wherein^the^SCell^ activation^delay^requirement^is^based^on^the^time^for^fine^time^tracking^and^acquiring^full^timing^ information^of^the^deactivated^SCell.^

[0157] ^ Example^ 21^ includes^ the^ computer-readable^ medium^ of^ any^ of^ Examples^ 13^ to^ 20,^ wherein^the^instructions,^when^executed^by^the^processing^circuitry,^cause^the^processing^circuitry^ further^to:^determine^that^the^SSB^bandwidth^of^the^deactivated^cell^is^12^PRBs^based^on^a^message^ received^from^an^Access^Node^(AN).^

[0158] ^ Example^ 22^ includes^ the^ computer-readable^ medium^ of^ Example^ 21,^ wherein^ the^message^is^to^indicate^that^the^SSB^bandwidth^of^the^deactivated^cell^is^12^PRBs.^

[0159] ^ Example^ 23^ includes^ the^ computer-readable^ medium^ of^ Example^ 21,^ wherein^ the^message^is^to^ indicate^a^carrier^bandwidth^of^the^deactivated^cell,^and^wherein^the^instructions,^when^executed^by^the^processing^circuitry,^cause^the^processing^circuitry^further^to:^derive^the^SSB^ bandwidth^of^the^deactivated^cell^from^the^carrier^bandwidth.^

[0160] ^ Example^24^includes^a^method,^comprising:^determining^a^ time^period^for^ time^index^detection^for^a^Synchronization^Signal^Block^(SSB)^of^a^deactivated^cell^with^an^SSB^bandwidth^of^12^Physical^Resource^Blocks^ (PRBs),^ based^on^ a^Discontinuous^Reception^ (DRX)^cycle,^a^measurement^cycle^ for^ the^deactivated^cell,^and^a^Carrier^Specific^Scaling^Factor^ (CSSF);^and^performing^measurement^for^the^SSB^based^on^the^time^period^for^the^time^index^detection.^

[0161] ^ Example^25^includes^the^method^of^Example^24,^wherein^the^deactivated^cell^includes^a^deactivated^Secondary^Cell^(SCell)^or^a^deactivated^Primary^SCell^(PSCell).^

[0162] ^ Example^26^includes^the^method^of^Example^24^or^25,^further^comprising:^determine^the^time^period^for^the^time^index^detection^further^based^on^a^scaling^factor^for^an^SSB^frequency^ layer^to^be^measured^without^GAP^and^a^nominal^number^of^SSB^measurement^samples,^wherein^ the^nominal^number^of^SSB^measurement^samples^is^7.^

[0163] ^ Example^27^includes^the^method^of^any^of^Examples^24^to^26,^wherein^the^deactivated^cell^is^to^operate^in^a^system^having^a^bandwidth^less^than^5^MHz.^

[0164] ^ Example^28^includes^the^method^of^any^of^Examples^24^to^27,^wherein^the^deactivated^cell^is^to^operate^in^Frequency^Range^1^(FR1).^

[0165] ^ Example^29^includes^the^method^of^any^of^Examples^24^to^28,^wherein^the^deactivated^cell^ includes^ a^ deactivated^ Primary^ Secondary^ Cell^ (PSCell),^ and^wherein^ the^method^ further^ comprises:^determine^a^time^for^fine^time^tracking^and^acquiring^full^timing^information^of^the^ deactivated^PSCell^to^be^triple^that^for^a^deactivated^PSCell^with^an^SSB^bandwidth^other^than^12^ PRBs.^

[0166] ^ Example^30^includes^the^method^of^any^of^Examples^24^to^28,^wherein^the^deactivated^cell^ includes^a^deactivated^Secondary^Cell^ (SCell),^and^wherein^ the^method^further^comprises:^determine^a^time^for^fine^time^tracking^and^acquiring^full^timing^information^of^the^deactivated^ SCell^to^be^a^value^greater^than^zero.^

[0167] ^ Example^ 31^ includes^ the^ method^ of^ Example^ 30,^ further^ comprising:^ activate^ the^deactivated^SCell^based^on^ a^SCell^ activation^delay^ requirement,^wherein^ the^SCell^ activation^delay^requirement^is^based^on^the^time^for^fine^time^tracking^and^acquiring^full^timing^information^ of^the^deactivated^SCell.^

[0168] ^ Example^ 32^ includes^ the^ method^ of^ any^ of^ Examples^ 24^ to^ 31,^ further^ comprising:^determine^that^the^SSB^bandwidth^of^the^deactivated^cell^is^12^PRBs^based^on^a^message^received^ from^an^Access^Node^(AN).^

[0169] ^ Example^33^includes^the^method^of^Example^32,^wherein^the^message^is^to^indicate^that^the^SSB^bandwidth^of^the^deactivated^cell^is^12^PRBs.^

[0170] ^ Example^34^includes^the^method^of^Example^32,^wherein^the^message^is^to^indicate^a^carrier^bandwidth^of^the^deactivated^cell,^and^wherein^the^method^further^comprises:^derive^the^ SSB^bandwidth^of^the^deactivated^cell^from^the^carrier^bandwidth.^

[0171] ^ Example^35^includes^the^method^of^any^of^Examples^24^to^34,^wherein^the^method^is^applicable^to^a^User^Equipment^(UE).^

[0172] ^ Example^36^includes^a^system^comprising:^the^apparatus^of^any^of^Examples^1^to^12;^and^a^Radio^Frequency^(RF)^circuitry^coupled^with^the^apparatus.^

[0173] ^ Although^certain^embodiments^have^been^illustrated^and^described^herein^for^purposes^of^ description,^ a^wide^ variety^ of^ alternate^ and / or^ equivalent^ embodiments^ or^ implementations^calculated^ to^ achieve^ the^ same^ purposes^may^ be^ substituted^ for^ the^ embodiments^ shown^ and^ described^without^departing^from^the^scope^of^the^present^disclosure.^This^application^is^intended^to^ cover^ any^ adaptations^ or^ variations^ of^ the^ embodiments^ discussed^ herein.^ Therefore,^ it^ is^manifestly^intended^that^embodiments^described^herein^be^limited^only^by^the^appended^claims^ and^the^equivalents^thereof.^

Claims

What^is^claimed^is:^ ^ 1.^An^apparatus^for^a^User^Equipment^(UE),^comprising:^ interface^circuitry;^and^ processor^circuitry^coupled^with^the^interface^circuitry,^ wherein^the^processor^circuitry^is^to:^ determine^a^time^period^for^time^index^detection^for^a^Synchronization^Signal^Block^ (SSB)^ of^ a^ deactivated^ cell^ with^ an^ SSB^ bandwidth^ of^ 12^ Physical^Resource^ Blocks^(PRBs),^based^on^a^Discontinuous^Reception^(DRX)^cycle,^a^measurement^cycle^for^the^ deactivated^cell,^and^a^Carrier^Specific^Scaling^Factor^(CSSF);^and^ perform^ measurement^ for^ the^ SSB^ based^ on^ the^ time^ period^ for^ the^ time^ index^detection.^ ^ 2.^The^apparatus^of^claim^1,^wherein^the^deactivated^cell^includes^a^deactivated^Secondary^Cell^ (SCell)^or^a^deactivated^Primary^SCell^(PSCell).^ ^ 3.^The^apparatus^of^claim^1^or^2,^wherein^the^processor^circuitry^is^further^to:^ determine^the^time^period^for^the^time^index^detection^further^based^on^a^scaling^factor^for^an^ SSB^frequency^layer^to^be^measured^without^GAP^and^a^nominal^number^of^SSB^measurement^ samples,^wherein^the^nominal^number^of^SSB^measurement^samples^is^7.^ ^4.^The^apparatus^of^any^of^claims^1^to^3,^wherein^the^deactivated^cell^is^to^operate^ in^a^system^having^a^bandwidth^less^than^5^MHz.^ ^ 5.^The^apparatus^of^any^of^claims^1^to^4,^wherein^the^deactivated^cell^is^to^operate^in^Frequency^ Range^1^(FR1).^ ^6.^ The^ apparatus^ of^ any^ of^ claims^ 1^ to^ 5,^wherein^ the^ deactivated^ cell^ includes^ a^ deactivated^Primary^Secondary^Cell^(PSCell),^and^wherein^the^processor^circuitry^is^further^to:^ determine^a^time^for^fine^time^tracking^and^acquiring^full^timing^information^of^the^deactivated^ PSCell^to^be^triple^that^for^a^deactivated^PSCell^with^an^SSB^bandwidth^other^than^12^PRBs.^ ^7.^ The^ apparatus^ of^ any^ of^ claims^ 1^ to^ 5,^wherein^ the^ deactivated^ cell^ includes^ a^ deactivated^Secondary^Cell^(SCell),^and^wherein^the^processor^circuitry^is^further^to:^determine^a^time^for^fine^time^tracking^and^acquiring^full^timing^information^of^the^deactivated^ SCell^to^be^a^value^greater^than^zero.^ ^ 8.^The^apparatus^of^claim^7,^wherein^the^processor^circuitry^is^further^to:^ activate^ the^deactivated^ SCell^ based^ on^ a^ SCell^ activation^ delay^ requirement,^wherein^ the^SCell^activation^delay^requirement^is^based^on^the^time^for^fine^time^tracking^and^acquiring^full^ timing^information^of^the^deactivated^SCell.^ ^ 9.^The^apparatus^of^any^of^claims^1^to^8,^wherein^the^processor^circuitry^is^further^to:^ determine^ that^ the^SSB^bandwidth^of^ the^deactivated^cell^ is^ 12^PRBs^based^on^a^message^received^from^an^Access^Node^(AN)^via^the^interface^circuitry.^ ^ 10.^The^apparatus^of^claim^9,^wherein^the^message^is^to^indicate^that^the^SSB^bandwidth^of^the^ deactivated^cell^is^12^PRBs.^ ^11.^ The^ apparatus^ of^ claim^ 9,^ wherein^ the^ message^ is^ to^ indicate^ a^ carrier^ bandwidth^ of^ the^deactivated^cell,^and^wherein^the^processor^circuitry^is^further^to:^ derive^the^SSB^bandwidth^of^the^deactivated^cell^from^the^carrier^bandwidth.^ ^12.^A^ computer-readable^medium^having^ instructions^ stored^ thereon,^wherein^ the^ instructions,^when^executed^by^processing^circuitry,^cause^the^processing^circuitry^to:^ determine^a^time^period^for^time^index^detection^for^a^Synchronization^Signal^Block^(SSB)^of^a^deactivated^cell^with^an^SSB^bandwidth^of^12^Physical^Resource^Blocks^ (PRBs),^based^on^a^Discontinuous^ Reception^ (DRX)^ cycle,^ a^ number^ of^ available^ SSB^ measurement^ samples,^ a^measurement^cycle^for^the^deactivated^cell,^and^a^Carrier^Specific^Scaling^Factor^(CSSF);^and^ perform^measurement^for^the^SSB^based^on^the^time^period^for^the^time^index^detection.^ ^13.^ The^ computer-readable^ medium^ of^ claim^ 12,^ wherein^ the^ deactivated^ cell^ includes^ a^deactivated^Secondary^Cell^(SCell)^or^a^deactivated^Primary^SCell^(PSCell).^ ^14.^ The^ computer-readable^medium^ of^ claim^ 12^ or^ 13,^wherein^ the^ number^ of^ available^ SSB^measurement^ samples^ is^ based^on^a^scaling^ factor^ for^an^SSB^frequency^ layer^ to^be^measured^without^GAP^and^a^nominal^number^of^SSB^measurement^samples,^wherein^the^nominal^number^ of^SSB^measurement^samples^is^7.^ ^15.^The^computer-readable^medium^of^any^of^claims^12^to^14,^wherein^the^deactivated^cell^is^to^ operate^in^a^system^having^a^bandwidth^less^than^5^MHz.^ ^ 16.^The^computer-readable^medium^of^any^of^claims^12^to^15,^wherein^the^deactivated^cell^is^to^ operate^in^Frequency^Range^1^(FR1).^ ^ 17.^The^computer-readable^medium^of^any^of^claims^12^to^16,^wherein^the^deactivated^cell^includes^ a^deactivated^Primary^Secondary^Cell^(PSCell),^and^wherein^the^instructions,^when^executed^by^ the^processing^circuitry,^cause^the^processing^circuitry^further^to:^ determine^a^time^for^fine^time^tracking^and^acquiring^full^timing^information^of^the^deactivated^ PSCell^to^be^triple^that^for^a^deactivated^PSCell^with^an^SSB^bandwidth^other^than^12^PRBs.^ ^ 18.^The^computer-readable^medium^of^any^of^claims^12^to^16,^wherein^the^deactivated^cell^includes^a^ deactivated^ Secondary^ Cell^ (SCell),^ and^ wherein^ the^ instructions,^ when^ executed^ by^ the^processing^circuitry,^cause^the^processing^circuitry^further^to:^ determine^a^time^for^fine^time^tracking^and^acquiring^full^timing^information^of^the^deactivated^ SCell^to^be^a^value^greater^than^zero.^ ^ 19.^The^computer-readable^medium^of^claim^18,^wherein^the^instructions,^when^executed^by^the^ processing^circuitry,^cause^the^processing^circuitry^further^to:^ activate^ the^deactivated^ SCell^ based^ on^ a^ SCell^ activation^ delay^ requirement,^wherein^ the^SCell^activation^delay^requirement^is^based^on^the^time^for^fine^time^tracking^and^acquiring^full^ timing^information^of^the^deactivated^SCell.^ ^20.^The^computer-readable^medium^of^ any^of^claims^12^ to^19,^wherein^ the^ instructions,^when^executed^by^the^processing^circuitry,^cause^the^processing^circuitry^further^to:^^ determine^ that^ the^SSB^bandwidth^of^ the^deactivated^cell^ is^ 12^PRBs^based^on^a^message^received^from^an^Access^Node^(AN).^

Images