WO2022164706A1 - Recherche et sélection de cellules pour réseaux ng - Google Patents

Recherche et sélection de cellules pour réseaux ng Download PDF

Info

Publication number
WO2022164706A1
WO2022164706A1 PCT/US2022/013119 US2022013119W WO2022164706A1 WO 2022164706 A1 WO2022164706 A1 WO 2022164706A1 US 2022013119 W US2022013119 W US 2022013119W WO 2022164706 A1 WO2022164706 A1 WO 2022164706A1
Authority
WO
WIPO (PCT)
Prior art keywords
coverage
cell
area
network
rrc
Prior art date
Application number
PCT/US2022/013119
Other languages
English (en)
Inventor
Fatemeh HAMIDI-SEPEHR
Sangeetha L. Bangolae
Sudeep K. Palat
Qian Li
Youn Hyoung Heo
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Publication of WO2022164706A1 publication Critical patent/WO2022164706A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • Embodiments pertain to next generation (NG) wireless communications.
  • NG next generation
  • some embodiments relate to cell search and selection in NG networks.
  • NR new radio
  • 5G 5 th generation
  • 6G sixth generation
  • the use and complexity of new radio (NR) wireless systems which include 5 th generation (5G) networks and are starting to include sixth generation (6G) networks among others, has increased due to both an increase in the types of devices UEs using network resources as well as the amount of data and bandwidth being used by various applications, such as video streaming, operating on these UEs.
  • the corresponding network environment including routers, switches, bridges, gateways, firewalls, and load balancers, has become increasingly complicated.
  • a number of issues abound with the advent of any new technology.
  • FIG. 1 A illustrates an architecture of a network, in accordance with some aspects.
  • FIG. 1B illustrates a non-roaming 5G system architecture in accordance with some aspects.
  • FIG. 1 C illustrates a non-roaming 5G system architecture in accordance with some aspects.
  • FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments.
  • FIG. 3 illustrates 5G NR control plane (CP) state transitions in accordance with some aspects.
  • FIG. 4A illustrates 5G NR radio resource control (RRC) state transitions in accordance with some aspects.
  • RRC radio resource control
  • FIG. 4B illustrates 5G NR RRC states of the RRC state transitions in FIG. 4A in accordance with some aspects.
  • FIG. 5 illustrates RRCJDLE and RRCJNACTIVE Cell Selection and Reselection in accordance with some aspects.
  • FIG. 6 illustrates public/private network scenarios in accordance with some aspects.
  • FIG. 7 illustrates radio link failure (RLF) actions in accordance with some aspects.
  • FIG. 8 illustrates a 5GNR initial access procedure in accordance with some aspects.
  • FIG. 1 A illustrates an architecture of a network in accordance with some aspects.
  • the network 140A includes 3GPP LTE/4G and NG network functions that may be extended to 6G functions. Accordingly, although 5G will be referred to, it is to be understood that this is to extend as able to 6G structures, systems, and functions.
  • a network function can be implemented as a discrete network element on a dedicated hardware, as a software instance running on dedicated hardware, and/or as a virtualized function instantiated on an appropriate platform, e.g., dedicated hardware or a cloud infrastructure.
  • the network 140A is shown to include user equipment (UE) 101 and UE 102.
  • the UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as portable (laptop) or desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface.
  • the UEs 101 and 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein.
  • Any of the radio links described herein may operate according to any exemplary radio communication technology and/or standard.
  • Any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and other frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and other frequencies).
  • LSA Licensed Shared Access
  • SAS Spectrum Access System
  • OFDM Orthogonal Frequency Domain Multiplexing
  • SC-FDMA SC-FDMA
  • SC-OFDM filter bank-based multicarrier
  • OFDMA OFDMA
  • 3GPP NR 3GPP NR
  • any of the UEs 101 and 102 can comprise an Intemet-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing short- lived UE connections.
  • any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE).
  • NB narrowband
  • eNB-IoT enhanced NB-IoT
  • FeNB-IoT Further Enhanced
  • An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks.
  • M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the loT UEs may execute background applications (e.g., keep- alive messages, status updates, etc.) to facilitate the connections of the loT network.
  • any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.
  • the UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110.
  • the RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Evolved Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • NG RAN NextGen RAN
  • the UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); 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 5G protocol, a 6G protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT Push-to-Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE 3GPP Long Term Evolution
  • the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105.
  • the ProSe interface 105 may alternatively be referred to as a sidelink (SL) interface comprising 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), a Physical Sidelink Broadcast Channel (PSBCH), and a Physical Sidelink Feedback Channel (PSFCH).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • PSFCH Physical Sidelink Feedback Channel
  • the UE 102 is shown to be configured to access an access point (AP) 106 via connection 107.
  • the connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router.
  • WiFi® wireless fidelity
  • 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).
  • the RAN 110 can include one or more access nodes that enable the connections 103 and 104.
  • These access nodes can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • the communication nodes 111 and 112 can be transmission/reception points (TRPs). In instances when the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs.
  • TRPs transmission/reception points
  • RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112.
  • RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102.
  • any of the RAN nodes 111 and 112 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.
  • RNC radio network controller
  • any of the nodes 111 and/or 112 can be a gNB, an eNB, or another type of RAN node.
  • the RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI interface 113.
  • the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS. 1B-1C).
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the S1 interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the Sl-mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121.
  • S-GW serving gateway
  • MME Sl-mobility management entity
  • the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124.
  • the MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • the MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 122 may terminate the SI interface 113 towards the RAN 110, and routes data packets between the RAN 110 and the CN 120.
  • the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility.
  • Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.
  • the P-GW 123 may terminate an SGi interface toward a PDN.
  • the P-GW 123 may route data packets between the CN 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125.
  • the P-GW 123 can also communicate data to other external networks
  • the application server 184 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 P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125.
  • the application server 184 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 and 102 via the CN 120.
  • VoIP Voice-over-Internet Protocol
  • the P-GW 123 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120.
  • PCRF Policy and Charging Rules Function
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • the PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.
  • the communication network 140 A can be an loT network or a 5G or 6G network, including 5G new radio network using communications in the licensed (5GNR) and the unlicensed (5GNR-U) spectrum.
  • NB-IoT narrowband-IoT
  • Operation in the unlicensed spectrum may include dual connectivity (DC) operation and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in unlicensed spectrum without the use of an “anchor” in the licensed spectrum, called MulteFire.
  • Further enhanced operation of LTE systems in the licensed as well as unlicensed spectrum is expected in future releases and 5G systems.
  • Such enhanced operations can include techniques for sidelink resource allocation and UE processing behaviors for NR sidelink V2X communications.
  • An NG system architecture can include the RAN 110 and a 5G core network (5GC) 120.
  • the NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs.
  • the CN 120 e.g., a 5G core network/5GC
  • the AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some aspects, the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces.
  • the gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.
  • the NG system architecture can use reference points between various nodes.
  • each of the gNBs and the NG- eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth.
  • a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.
  • MN master node
  • SN secondary node
  • FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects.
  • FIG. IB illustrates a 5G system architecture 140B in a reference point representation, which may be extended to a 6G system architecture.
  • UE 102 can be in communication with RAN 110 as well as one or more other 5GC network entities.
  • the 5G system architecture 140B includes a plurality of network functions (NFs), such as an AMF 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, UPF 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)/home subscriber server (HSS) 146.
  • NFs network functions
  • AMF session management function
  • PCF policy control function
  • AF application function
  • UPF network slice selection function
  • AUSF authentication server function
  • UDM unified data management
  • HSS home subscriber server
  • the UPF 134 can provide a connection to a data network (DN)
  • the AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality.
  • the AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of the access technologies.
  • the SMF 136 can be configured to set up and manage various sessions according to network policy. The SMF 136 may thus be responsible for session management and allocation of IP addresses to UEs.
  • the SMF 136 may also select and control the UPF 134 for data transfer.
  • the SMF 136 may be associated with a single session of a UE 101 or multiple sessions of the UE 101. This is to say that the UE 101 may have multiple 5G sessions. Different SMFs may be allocated to each session. The use of different SMFs may permit each session to be individually managed. As a consequence, the functionalities of each session may be independent of each other.
  • the UPF 134 can be deployed in one or more configurations according to the desired service type and may be connected with a data network.
  • the PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system).
  • the UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).
  • the AF 150 may provide information on the packet flow to the
  • the PCF 148 responsible for policy control to support a desired QoS.
  • the PCF 148 may set mobility and session management policies for the UE 101. To this end, the PCF 148 may use the packet flow information to determine the appropriate policies for proper operation of the AMF 132 and SMF 136.
  • the AUSF 144 may store data for UE authentication.
  • the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B.
  • the P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B.
  • the S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions such as routing an emergency request to the correct emergency center or PSAP.
  • the I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area.
  • the I-CSCF 166B can be connected to another IP multimedia network 170E, e.g. an IMS operated by a different network operator.
  • the UDM/HSS 146 can be coupled to an application server 160E, which can include a telephony application server (TAS) or another application server (AS).
  • the AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.
  • FIG. IB illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), Nl 1 (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM
  • FIG. 1C illustrates a 5G system architecture 140C and a service- based representation.
  • system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156.
  • NEF network exposure function
  • NRF network repository function
  • 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.
  • service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services.
  • 5G system architecture 140C can include the following service-based interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), aNudm 158E (a service-based interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the AUSF
  • NR-V2X architectures may support high-reliability low latency sidelink communications with a variety of traffic patterns, including periodic and aperiodic communications with random packet arrival time and size. Techniques disclosed herein can be used for supporting high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.
  • FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments.
  • the communication device 200 may be a UE such as a specialized computer, a personal or laptop computer (PC), a tablet PC, or a smart phone, dedicated network equipment such as an eNB, a server running software to configure the server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine.
  • the communication device 200 may be implemented as one or more of the devices shown in FIGS. 1A-1C. Note that communications described herein may be encoded before transmission by the transmitting entity (e.g., UE, gNB) for reception by the receiving entity (e.g., gNB, UE) and decoded after reception by the receiving entity.
  • the transmitting entity e.g., UE, gNB
  • the receiving entity e.g., gNB, UE
  • Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.
  • Modules and components are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner.
  • circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
  • the whole or part of one or more computer systems e.g., a standalone, client or server computer system
  • one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
  • the software may reside on a machine readable medium.
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • module (and “component”) is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein.
  • each of the modules need not be instantiated at any one moment in time.
  • the modules comprise a general-purpose hardware processor configured using software
  • the general-purpose hardware processor may be configured as respective different modules at different times.
  • Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
  • the communication device 200 may include a hardware processor (or equivalently processing circuitry) 202 (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memoiy 204 and a static memoiy 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208.
  • the main memory 204 may contain any or all of removable storage and non-removable storage, volatile memory or non-volatile memory.
  • the communication device 200 may further include a display unit 210 such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse).
  • UI user interface
  • the display unit 210, input device 212 and UI navigation device 214 may be a touch screen display.
  • the communication device 200 may additionally include a storage device (e.g., drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor.
  • GPS global positioning system
  • the communication device 200 may further include an output controller, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • a serial e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • USB universal serial bus
  • IR infrared
  • NFC near field communication
  • the storage device 216 may include a non-transitory machine readable medium 222 (hereinafter simply referred to as machine readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • the instructions 224 may also reside, completely or at least partially, within the main memory 204, within static memory 206, and/or within the hardware processor 202 during execution thereof by the communication device 200.
  • the machine readable medium 222 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 224.
  • machine readable medium may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 200 and that cause the communication device 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions.
  • Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media.
  • machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks.
  • non-volatile memory such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices
  • EPROM Electrically Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory devices e.g., electrically Erasable Programmable Read-Only Memory (EEPROM)
  • EPROM Electrically Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory devices e.g
  • the instructions 224 may further be transmitted or received over a communications network using a transmission medium 226 via the network interface device 220 utilizing any one of a number of wireless local area network (WLAN) transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.).
  • WLAN wireless local area network
  • Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks.
  • LAN local area network
  • WAN wide area network
  • POTS Plain Old Telephone
  • Communications over the networks may include one or more different protocols, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi, IEEE 802.16 family of standards known as WiMax, IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, a next generation (NG)/5 th generation (5G) standards among others.
  • the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phonejacks) or one or more antennas to connect to the transmission medium 226.
  • circuitry refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality.
  • FPD field-programmable device
  • FPGA field-programmable gate array
  • PLD programmable logic device
  • CPLD complex PLD
  • HPLD high-capacity PLD
  • DSPs digital signal processors
  • the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality.
  • the term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
  • processor circuitry or “processor” as used herein thus refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data.
  • processor circuitry or “processor” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single- or multi-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes.
  • any of the radio links described herein may operate according to any one or more of the following radio communication technologies and/or standards including but not limited to: a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3GPP) radio communication technology, for example Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP Long Term Evolution Advanced (LTE Advanced), Code division multiple access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-Speed Circuit-Switched Data (HSCSD), Universal Mobile Telecommunications System (Third Generation) (UMTS (3G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), High Speed Packet Access (HSPA), High Speed Packe
  • 3GPP ReL 9 (3rd Generation Partnership Project Release 9), 3GPP Rel. 10 (3rd Generation Partnership Project Release 10) , 3GPP Rel. 11 (3rd Generation Partnership Project Release 11), 3GPP Rel. 12 (3rd Generation Partnership Project Release 12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3GPP Rel. 14 (3rd Generation Partnership Project Release 14), 3GPP Rel. 15 (3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rd Generation Partnership Project Release 16), 3GPP Rel. 17 (3rd Generation Partnership Project Release 17) and subsequent Releases (such as Rel. 18, Rel.
  • IEEE 802.1 Ip based DSRC including TTS-G5A (i.e., Operation of ITS-G5 in European ITS frequency bands dedicated to ITS for safety re-lated applications in the frequency range 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., Operation in European ITS frequency bands dedicated to ITS non- safety applications in the frequency range 5,855 GHz to 5,875 GHz), ITS-G5C (i.e., Operation of ITS applications in the frequency range 5,470 GHz to 5,725 GHz)), DSRC in Japan in the 700MHz band (including 715 MHz to 725 MHz), IEEE 802.1 Ibd based systems, etc.
  • TTS-G5A i.e., Operation of ITS-G5 in European ITS frequency bands dedicated to ITS for safety re-lated applications in the frequency range 5,875 GHz to 5,905 GHz
  • ITS-G5B i.e., Operation in European ITS frequency bands
  • LSA Licensed Shared Access in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies
  • Applicable spectrum bands include IMT (International Mobile Telecommunications) spectrum as well as other types of spectrum/bands, such as bands with national allocation (including 450 - 470 MHz, 902-928 MHz (note: allocated for example in US (FCC Part 15)), 863-868.6 MHz (note: allocated for example in European Union (ETSI EN 300220)), 915.9-929.7 MHz (note: allocated for example in Japan), 917-923.5 MHz (note: allocated for example in South Korea), 755-779 MHz and 779-787 MHz (note: allocated for example in China), 790 - 960 MHz, 1710 - 2025 MHz, 2110 - 2200 MHz, 2300 - 2400 MHz, 2.4-2.4835 GHz (note: it is an ISM band with global availability and it is used by Wi-Fi technology family (1 Ib/g/n/ax) and also by Bluetooth), 2500 - 2690 MHz, 698-790 MHz, 610 - 790
  • Next generation Wi-Fi system is expected to include the 6 GHz spectrum as operating band but it is noted that, as of December 2017, Wi-Fi system is not yet allowed in this band. Regulation is expected to be finished in 2019-2020 time frame), IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800 MHz, 3800 - 4200 MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range, etc.), spectrum made available under FCC's "Spectrum Frontier" 5G initiative (including 27.5 - 28.35 GHz, 29.1 - 29.25 GHz, 31 - 31.3 GHz, 37 - 38.6 GHz, 38.6 - 40 GHz, 42 - 42.5 GHz, 57 - 64 GHz, 71 - 76 GHz, 81 - 86 GHz and 92 - 94 GHz, etc), the ITS (Intelligent Transport Systems) band of 5.9 GHz (typically 5.85-5.925 GHz) and
  • aspects described herein can also implement a hierarchical application of the scheme is possible, e.g., by introducing a hierarchical prioritization of usage for different types of users (e.g., low/medium/high priority, etc.), based on a prioritized access to the spectrum e.g., with highest priority to tier-1 users, followed by tier-2, then tier-3, etc. users, etc.
  • a hierarchical prioritization of usage for different types of users e.g., low/medium/high priority, etc.
  • a prioritized access to the spectrum e.g., with highest priority to tier-1 users, followed by tier-2, then tier-3, etc. users, etc.
  • APs eNBs, NR or gNBs - note that this term is typically used in the context of 3GPP 5G and 6G communication systems, etc. Still, a UE may take this role as well and act as an AP, eNB, or gNB; that is some or all features defined for network equipment may be implemented by a UE.
  • Target key performance indicators include supporting wider bandwidths compared to 5G (e.g., at least 2 GHz or larger), supporting higher peak data rates (such as beyond 100 Gbps), and providing lower physical layer latency (such as under 100 ⁇ sec turnaround time). 6G is also expected to enable better support of vertical industries, including support for private networks.
  • a key enabler in 6G is operation in high- frequency spectrum, i.e., THz band.
  • THz band high- frequency spectrum
  • challenges include high pathloss and penetration loss, very short communication/coverage range, and frequent blockages.
  • the system design should inherently address short term or longer periods of blockage. The high-band characteristics and needs further exacerbate the challenge of data transfer during the transient in-coverage durations.
  • the transmission channel may be frequently blocked due to stationary and/or mobile blocking objects. Blockages occur due to link instability and are normally expected to have shorter duration than out of coverage events; however, the blockage duration may still be significant compared to the overall transient in-coverage duration.
  • one of the goals of the future technology is to develop a system design that enables accessing the network and transferring uplink (UL) or downlink (DL) data (large or small payload) with the least possible incurred latency and overhead before the link becomes unavailable (likely in a very short time).
  • UL uplink
  • DL downlink
  • Such design involves both RAN and core network aspects.
  • the limitations, potential bottlenecks, and any room for enhancement or optimization of the current system design (from both control plane (CP) and user plane (UP) perspectives) are identified under limited coverage with potentially frequent link blockages within the nominal coverage area/duration.
  • the radio resource control idle (RRC_IDLE) state plays the role of a fallback state. For example, when the UE faces a radio link failure (RLF) event from which the UE is unable to recover or the UE goes out of network coverage, the UE enters the RRC_IDLE state. To transfer/receive data, the UE generally transitions to the RRC_CONNECTED state, although there are some exceptions for transmission of very small payload sizes in the RRC_INACTIVE state. However, the overhead and latency of idle- to-active transitions in the core network is not tolerable in scenarios in which the in-coverage duration of the UE is transient.
  • RLF radio link failure
  • the RRC_INACTIVE state may be adjusted, such as being the fallback state, for operation under limited coverage (e.g., in deployments with coverage islands, etc.), to enable making better use of the transient time that the UE spends in network coverage.
  • limited coverage e.g., in deployments with coverage islands, etc.
  • the UE may reside in different states depending on the traffic activity.
  • the core network states CM_IDLE and CM_CONNECTED are defined based on whether or not the UE has established a connection with the core network.
  • FIG. 3 illustrates 5G NR CP state transitions in accordance with some aspects.
  • An NR device can be in one of three RRC states, RRC_IDLE, RRC_CONNECTED, and RRC_INACTIVE.
  • FIG. 4A illustrates 5G NR RRC state transitions in accordance with some aspects.
  • FIG. 4B illustrates 5GNR RRC states of the RRC state transitions in FIG. 4A in accordance with some aspects.
  • the mobility, handover, and corresponding measurements aspects have not been mentioned in FIG.
  • the RRC_IDLE state there is no RRC context (i.e., the parameters for communication between the UE and the network) in the RAN, and the UE does not belong to a specific cell. From a core network perspective, the device is in the CM_IDLE state. No data transfer may take place as the UE sleeps most of the time to reduce battery consumption.
  • a UE in the idle state periodically wakes up to receive paging messages, if any, from the network. Uplink synchronization is not maintained and hence the only uplink transmission activity that may take place is random access, to move to a connected state. As part of moving to a connected state, the RRC context is established in both the UE and the network.
  • the RRC_CONNECTED state the RRC context is established and parameters used for communication between the UE and the radio-access network are known to both entities.
  • the UE is in the CM_CONNECTED state.
  • the cell to which the UE belongs is known and an identity of the UE, the Cell Radio-Network Temporary Identifier (C-RNTI), used for signaling purposes between the UE and the network, has been configured.
  • C-RNTI Cell Radio-Network Temporary Identifier
  • the connected state is intended for data transfer to/from the UE. Uplink time alignment may or may not exist but are established using random access and maintained for data transmission to take place.
  • the UE context is kept in both the UE and the gNB.
  • the core network connection is also kept, that is, the UE is in the CM_CONNECTED state from a core network perspective.
  • transition to a connected state for data transfer is fast.
  • No core network signaling is used; in terms of messaging, only Resume Request and Resume messages are exchanged, upon which the UE enters the RRC_CONNECTED state.
  • the RRC context is already in place in the network and idle-to-active transitions can be handled in the radio-access network.
  • the UE is expected to monitor broadcast downlink signals (system information, paging, etc.) as part of physical downlink control channel (PDCCH) monitoring just like in the RRC_CONNECTED state.
  • broadcast downlink signals system information, paging, etc.
  • PDCCH physical downlink control channel
  • a UE in the RRC_IDLE or RRC_INACTIVE state can be in different (sub-)states: ‘Any cell selection’ state refers to a UE that is out of network coverage and is not associated with a serving cell on any carrier, as defined in 3GPP TS 38.304. This state is applicable for the RRC_IDLE state and RRC_INACTIVE state. In this state, the UE performs cell selection to find a suitable cell (one for which the measured cell attributes satisfy cell selection criteria).
  • the UE attempts to find an acceptable cell (one for which the measured cell attributes satisfy cell selection criteria and the cell is not barred) of any PLMN to camp on, trying all RATs that are supported by the UE and searching first for a high-quality cell (defined in clause 5.1.1.2 of TS 38.304).
  • the UE which is not camped on any cell, remains in this state.
  • FIG. 5 illustrates RRC_IDLE and RRC_INACTIVE Cell Selection and Reselection in accordance with some aspects. The terms in quotes refer to the states in FIG. 5.
  • the ‘Camped Normally’ state is applicable for the RRC_IDLE and RRC_INACTIVE state.
  • the UE When camped normally, amongst other actions, the UE performs monitoring of paging channel of the cell according to information broadcast in SIB1, monitoring of Short Messages transmitted with the paging RNTI (P-RNTI) over downlink channel information (DCI), and relevant System Information (SI), etc.
  • This state includes a period between cell selection criteria not being met and the UE entering the "any cell selection" state (See TS 38.133).
  • the ‘Camped on Any Cell’ state is only applicable for the RRC_IDLE state.
  • the UE performs monitoring of Short Messages transmitted with P-RNTI over DCI, monitoring of relevant System Information, and regularly attempting to find a suitable cell trying all frequencies of all RATs that are supported by the UE. If the UE supports voice services and the current cell does not support IMS emergency calls as indicated by the field ims- EmergencySupport in SIB1 as specified in TS 38.331, the UE performs cell selection/reselection to an acceptable cell that supports emergency calls in any supported RAT regardless of priorities provided in system information from current cell, if no suitable cell is found. If a suitable cell is found, the UE moves to the camped normally state.
  • PLMN public land mobile network
  • SNPN Stand-alone Non-Public Network
  • the UE can do so by initially accessing the network on a control channel of the cell on which the UE is camped. If the network is to send a message or deliver data to the registered UE, the network knows (in most cases) the set of tracking areas (in the RRC_IDLE state) or RAN-based notification area (RNA) (in the RRC_INACTIVE state) in which the UE is camped.
  • the set of tracking areas in the RRC_IDLE state
  • RNA RAN-based notification area
  • the network can then send a "paging" message for the UE on the control channels of all the cells in the corresponding set of areas.
  • the UE then receives the paging message and can respond.
  • the UE may receive Earthquake and Tsunami Warning System (ETWS) and Commercial Mobile Alert System (CMAS) notifications.
  • EWS Earthquake and Tsunami Warning System
  • CMAS Commercial Mobile Alert System
  • operation 1 is entered whenever a new PLMN selection or new SNPN selection is performed (TS 38.304).
  • the RRC_IDLE state and RRC_INACTIVE state tasks can be subdivided into three processes: PLMN/SNPN selection, Cell selection, and Location registration and RNA update.
  • a PLMN or a SNPN is selected by non-access stratum (NAS) - the UE NAS layer identifies a selected PLMN and equivalent PLMNs.
  • NAS non-access stratum
  • one or more associated RAT(s) may be set, as specified in TS 23.122.
  • the NAS provides a list of equivalent PLMNs, if available, that the access stratum (AS) uses for cell selection and cell reselection.
  • a ‘cell selection’ process takes place, as described in TS 38.304.
  • This process allows UE to select a suitable cell on which to camp to access available services.
  • the UE can use stored information [for several RATs, if available] (Stored information cell selection, to expedite the process) or not (Initial cell selection).
  • Stored information cell selection to expedite the process
  • the UE searches for a suitable cell of the selected PLMN or selected SNPN, chooses that cell to provide available services, and monitors its control channel. This procedure is defined as "camping on the cell”.
  • the UE selects a suitable cell based on RRC_IDLE or RRC_INACTIVE state measurements and cell selection criteria.
  • measurement quantity of a cell is up to UE implementation.
  • cell quality is derived amongst the beams corresponding to the same cell (TS 38.300 subclause 9.2).
  • RNA update procedure is performed.
  • PLMN selection, SNPN selection, cell selection/reselection procedures, and location registration are common for both the RRC_IDLE state and RRC_INACTIVE state.
  • the RNA update is only applicable for RRC_INACTIVE state.
  • a new PLMN/SNPN is selected automatically (automatic mode), or an indication of available PLMNs/SNPNs is given to the user so that a manual selection can be performed (manual mode).
  • the AS reports available SNPN identifiers together with their Human-Readable Network Name (HRNN) (if broadcast) to the NAS.
  • HRNN Human-Readable Network Name
  • Cell search and cell selection are based on Cell Defining (CD) signaling signal broadcasts (SSBs) located on a synchronization raster.
  • CD Cell Defining
  • a primary cell (PCell) is always associated to a CD-SSB located on the synchronization raster.
  • Cell search is the procedure by which a UE acquires time and frequency synchronization with a cell and detects the Cell ID of that cell.
  • NR cell search is based on the primary and secondary synchronization signals, and physical broadcast channel (PBCH) demodulation reference signals (DMRS), located on the synchronization raster.
  • PBCH physical broadcast channel
  • DMRS demodulation reference signals
  • the possible SS block locations for each frequency band are a limited set of frequencies referred to as the synchronization raster.
  • Cell selection is performed by initial cell selection in which the UE has no prior knowledge of which RF channels are NR frequencies, cell selection leveraging stored information, or cell selection when leaving the RRC_CONNECTED mode.
  • the UE scans all RF channels in the NR bands (searches NR frequency bands) according to its capabilities to find a suitable cell.
  • the UE may or may not search each carrier in turn as discussed below.
  • the UE searches for the strongest cell (except for operation with shared spectrum channel access where the UE may search for the next strongest cell(s)) as per CD-SSB.
  • this cell is selected - the UE then reads cell system info broadcast to identify its PLMN(s).
  • Cell selection leveraging stored information which speeds up the procedure, uses stored information related to carrier frequencies (to shorten the search) and optionally also information on cell parameters retrieved from previously received measurement control information elements or from previously detected cells and pre-existing SI messages. Once the UE has found a suitable cell, the UE selects the cell. If no suitable cell is found, the initial cell selection procedure using initial cell selection is started.
  • Cell selection when leaving the RRC_CONNECTED mode applies to the UE transitioning to the RRC_IDLE or RRC_INACTIVE mode.
  • the network can direct the UE towards a specific RF carrier by including ‘redirectedCarrierlnfo’ within the RRCRelease message; otherwise the UE is free to search any RF carrier.
  • the UE may not sequentially follow Global Synchronization Channel Number (GSCN), i.e., 1 candidate every X MHz, where X may be equal to 1.44MHz, etc.
  • GSCN Global Synchronization Channel Number
  • the UE may avoid brute force searching, via a smart receiver implementation.
  • the receiver may enable a large bandwidth for sensing and senses (subsets) of spectrum. If the receiver detects an expected spectrum, e.g., a OFDM waveform look alike spectrum, the UE will search for a GSCN near the center of the detected spectrum.
  • the UE On recovery from out of coverage, the UE seeks to identify a suitable cell (stored information or initial cell selection). If the UE is not able to identify a suitable cell (on any frequency or RAT), the UE seeks to identify an acceptable cell. When a suitable cell is found or if only an acceptable cell is found, the UE camps on that cell and commences a cell reselection procedure.
  • the UE may camp on the last cell for which the UE was in the RRC_CONNECTED state or a cell/any cell of set of cells or frequency be assigned by RRC in the state transition message (see TS 38.300).
  • the UE performs cell selection using selection-related parameters from the system information or from a RRC Connection Release message received from the network (since RRC connection release procedure can also be used to release and redirect a UE to another frequency). If the UE is provided with a redirection in Release, the UE follows the redirection.
  • Which type of cell selection the UE performs (e.g., with or without stored information), at what times, and how, are not specified, and left up to the UE implementation. It may be the case that the UE first attempts to select most recent cell on which the UE has camped in Connected mode, or the UE selects a Suitable Cell on a frequency that is allocated through the RRC Connection Release message (if included). If such a cell is not available, the UE may attempt to find a suitable cell by performing the Stored Information Cell Selection procedure. If the UE fails to find a suitable cell, the UE may perform the initial cell selection procedure. The primary function of cell selection is to ensure that the cell the UE is going to use is suitable.
  • the UE attempts to camp on a suitable cell according to redirectedCarrierlnfo if included in the RRCRelease message. If the UE cannot find a suitable cell, the UE is allowed to camp on any suitable cell of the indicated RAT. If the RRCRelease message does not contain the redirectedCarrierlnfo, the UE attempts to select a suitable cell on an NR carrier. If no suitable cell is found according to the above, the UE performs cell selection using stored information to find a suitable cell to camp on.
  • the UE When returning to the RRC_IDLE state after the UE moved to the RRC_CONNECTED state from the camped on any cell state, the UE attempts to camp on an acceptable cell according to redirectedCarrierlnfo, if included in the RRCRelease message. If the UE cannot find an acceptable cell, the UE is allowed to camp on any acceptable cell of the indicated RAT. If the RRCRelease message does not contain redirectedCarrierlnfo, the UE attempts to select an acceptable cell on an NR frequency. If no acceptable cell is found according to the above, the UE continues to search for an acceptable cell of any PLMN in state any cell selection (see TS 38.304, 5.2.6).
  • the RRC_IDLE state and CM_IDLE state may not be used.
  • the fact that the RRC_IDLE state is deemed as the initial/reset state is carried over from the LTE design. Accordingly, whenever the UE faces an unsuccessful resume, an integrity check failure upon reestablishment, etc., the UE transitions into the RRC_IDLE state. On the other hand, the UE’s initial state has not been spelled out in the 3 GPP specification (TS 38.304).
  • properly defining the UE (fallback/reset) state for operation under the limited coverage may help to characterize the proper data transfer scheme.
  • the UE When the UE cannot find any cell and the reestablishment fails, then the UE enters the RRC_IDLE state and performs a NAS recovery, where the UE will continue to find a cell, and as soon as the UE finds one, triggers either a service request or a tracking area update.
  • a common Reestablishment procedure is defined for all scenarios. Further, optimization of the RRC reestablishment procedure (compared to LTE) is lacking since generally the UE is assumed to be in coverage. Also, facing an RLF is a very rare situation/event.
  • the price is the network’s configuration resources.
  • gNBs are distributed units with limited memory
  • populating all gNBs with large memory is a significant cost; but for small area deployment, cost of memory may not be an issue.
  • CU/DU central unit/distributed unit
  • the memory in the CU may not be a significant issue. If resources are critical, radio delay due to RRC_IDLE to RRC_CONNECTED state transition may occur, in which case reduced delay may be designed.
  • the new gNB fetches/ retrieves the UE context from the previous gNB. This can be done using a resume ID, which is unique within the RAN. The delay is due to the context fetch and potential inter-gNB handover latency.
  • the RRC_INACTIVE state may be set as the fallback/reset state to enable the UE to stay in RRC_INACTIVE state even when going out of coverage, to address the requirements, etc., for operation under limited coverage and make best use of the transient time that the UE is in coverage.
  • the network does not release the UE context/configurations. That is, the UE maintains the context, last connected cell, time stamp/location for when the UE goes out of coverage. Accordingly, cell search/cell selection procedures, as well as their requirements and triggers (e.g., from current or future’s RRC_IDLE/RRC_INACTIVE states) are (re-)defmed.
  • the cell search and frequency scanning process consumes a significant amount of time, which can be even larger than the total amount of time a mobile UE may spend in the coverage area with high-band (non-blocked) link availability.
  • the time for the UE to complete cell search may be roughly estimated as Nfreq*Tsearch for cell search without stored information, where Nfreq is the number of candidate frequencies the UE is to scan and Tsearch is the time to select a cell (e.g., latency of cell selection and initial beam acquisition in addition to the latency of SIB1 acquisition).
  • Both the Nfreq and Tsearch values can be relatively large numbers, especially for a beam-centric design with beam search, and also for high-frequency band operation.
  • the latency of cell search is expected to be significant compared to latency of other procedures to establish/ reestablish the connection (i.e., beam acquisition, MIB/SIB acquisition, random access procedure, beam refinement, and RRC connection (re-)establishment procedure).
  • finding the synchronization signal blocks (SSBs) may take minutes (before even performing any beam switching), since the UE scans for every frequency raster.
  • the large bandwidth available in higher frequency bands exacerbates the problem, due to the increased number of carrier frequencies to be scanned. Given that no device is built optimized or even tested to operate in such limited-coverage scenarios and deployments, it is likely that a typical NR UE may not be even able to operate in such a situation due to the cell search/selection procedures.
  • the UE when UE goes out of the coverage of a cell, the UE tries to find other cell on different frequencies, and if the UE does not find any suitable cell, the UE keeps searching. This is because the current design of cell selection primarily supports looking for cells constantly until one is found to camp on. Depending on the number of frequencies on the frequency raster, the UE may end up searching even for hours. Even assuming that the UE starts with scanning the latest carrier frequency first, when the UE does not find any suitable cell during the transient in-coverage duration, the UE may be stuck in this stage and miss all in-coverage and link-availability opportunities.
  • the reason that the UE may not find a suitable cell may be that in a particular time that the UE is searching on a certain frequency (e.g., the latest carrier frequency, first), the UE may be out of the coverage island; by the time the UE is back to the coverage, the UE will no longer search for that carrier frequency and miss the (likely only) cell to select.
  • the time that takes the UE to return to searching the (right) frequency again can be very large, e.g., depending on the number of frequencies, etc., and the UE may lose the coverage by that time.
  • the UE Even if all cells (or coverage islands) in the sparse deployment are on the same carrier frequency, the UE is to be enabled to search for that frequency for proper amount of time and start and stop the search at the right times.
  • Cell search with stored information is not configurable by the network, and currently, the UE decides what information is stored.
  • proper definition of how to manage the UE cell search and cell selection procedures, when to start and when to stop these procedures, UE behaviors, etc. is desired to enable operation in the sparse deployments.
  • the 3GPP specification specifies the triggers, and cell selection procedure for initial cell access and connection establishment, as well as for connection reestablishment.
  • RRC signaling manages control signaling between UEs and the network, including (re-establishing and releasing connections. Going out of the network’s coverage area (e.g., in deployments with non-ubiquitous coverage), as well as facing link blockages inside the network coverage area, amongst other reasons such as handover failures, can make the RRC_CONNECTED UE undergo physical RLF.
  • the RRC re-establishment procedure which, if failed, ends up transitioning the UE into the RRC_IDLE state.
  • Cell selection is performed on transition from the CM-IDLE to CM- CONNECTED state (e.g., for initial cell access), and when leaving connected mode, e.g., on transition from the CM-CONNECTED to CM-IDLE state (related to performing RRC reestablishment, e.g., if it is failed; the UE is not in the CM- IDLE state while performing RRC re-establishment). More accurately, the cell selection is not directly related to the transitions. For example, once the UE is camped normally, the UE may transition from the CM-IDLE to CM- CONNECTED state without cell selection. However, upon taking a particular set of actions, including cell selection, the UE may go through the state transition.
  • both initial connection establishment and connection re-establishment procedures involve the cell search and cell selection procedure.
  • proper definition of the cell selection procedure, its requirements, and its triggers is desirable in order to enable operation in the desired and described deployments.
  • the network indicates that the UE is to store and use information on the cell(s) to be selected.
  • This information may include the carrier frequency (to avoid frequency raster scan) and (potentially all) essential cell and system information. This information may be used by the UE for the next time(s) that the UE (re-)enters the coverage, or upon facing and recovering from RLF.
  • Such an indication from the network can be broadcasted or unicasted, e.g., based on the type of information to be stored, UE category, particular deployment, etc. The less information available at the UE at the time of entering the coverage, the more overhead and delay is expected to select and camp on the cell.
  • Directing the UE cell search and cell selection procedure can be, to some extent, similar to the RRC connection release procedure used to redirect a UE to another frequency or perform cell selection by leveraging stored information to speed up the procedure.
  • the extent of the information to be stored to direct the cell selection procedure in the current scenarios of interest is likely broader compared to any existing cell-selection aiding/directing mechanism. To some extent, this is more towards reducing the time taken for cell selection by optimizing cell selection process (or the sub-procedures of cell selection), and also if possible for some cases, evading the core of the cell selection procedure and transitioning into a more cell selection-less operation.
  • the primary function of cell selection is to ensure that the cell the UE is going to use is suitable, possibilities and scenarios where the UE can assume suitability of a cell should also be considered.
  • knowledge-based operation may not be optional and/or be left up to UE implementation in the scenarios of interest.
  • the embodiments herein enable the functionality/operation in sparse deployments with limited coverage.
  • the cell selection may take longer than the subsequent instances, it may still be possible to expedite the first cell selection procedure. For example, assuming the UE is already registered to the network, some prior knowledge may be also defined and considered to help with first time access as well, e.g., even the initial MIB acquisition may be performed faster.
  • the UE acquires information on the MIB and SIB1. Once camped on the cell, rest of the SIBs are also acquired, and cell-reselection process starts to find any better cell.
  • the cell initial access can proceed with SIB1 acquisition (to ensure that the cell is acceptable/suitable and also make the random access configuration available to the UE).
  • the beams used to obtain information from SSBs can also be used for SIB1 acquisition and retraining of beams for SIB1 decoding may be avoided.
  • the UE after the first time the UE enters a coverage island/cell, when the UE goes out of the coverage and re-enter the coverage, the UE relies on the previously acquired system information, including SIB1.
  • SIB1 previously acquired system information
  • a certain time period may be defined and if the UE has not been out of the coverage longer than the period, the UE can rely on the previously acquired system information, including SIB1.
  • the UE may rely on pre-defined essential system information and proceed with the rest of the operation on the cell.
  • one or more value tag(s) may be introduced inside the MIB to provide essential information of SIB1 and to help bypassing SIB1 acquisition, at least in certain scenarios and deployments. This approach also depends on the available space in the MIB.
  • a System Information Value Tag is included within SIB 1 to provide an indication of whether or not the content of SIB 2 to SIB 9 or SIB 13 has changed and is to be re-acquired.
  • the value tag is currently not applicable to the MIB, SIB 1, SIB 10, SIB 11 nor SIB 12.
  • UEs can use the System Info Value Tag to verify if the previously stored (other) system information messages are still valid or if a change has occurred in the system information messages.
  • the UE uses information about any previous cell(s) in the deployment that the UE had camped on before to facilitate cell selection and/or even MIB/SIB acquisition. For example, by entering the coverage and trying to access the cell, the UE may assume that the UE is in one of the cells previously accessed (e.g., by acquiring MIB, UE knows and checks the Physical Cell ID (PCI)). In this embodiment, the UE does not acquire the SIB (at least if value tag has not changed). The modification period may be set to be the shortest duration where modification is allowed, and the SIB may remain the same for a number of modification periods. The UE can check the value tag to see if the SIB has changed. Thus, the value tag may be applied in herein to, for example, SIB1.
  • SIB1 Physical Cell ID
  • the MIB and PCI information may be reused from previous times, or such information may be pre-configured.
  • the UE may rely on the acquired system information from a previous cell or previous times that UE has been in that cell, or from pre- configuration, i.e., default values always being pre-configured to the UE. Such pre-configuration is not available in NR.
  • certain coverage areas/islands of the deployment or the whole (private) deployment may be identified as a cell group over which, the UE may assume certain essential system information without critical changes.
  • the UE may avoid re-acquiring information, re-selecting the cells, and/or performing conventional re-establishment procedures.
  • the deployment may contain one cell or multiple distant cells, either with potentially uniform coverage within each cell or spotty coverage even within the cell(s), such that the deployment area is not fully covered.
  • the whole deployment may uniformly assume and rely on certain essential system information.
  • Example networks and scenarios and corresponding triggers of cell selection procedures [00114]
  • the UE In the scenarios of interest in opportunistic access, it is assumed that the UE had already performed a PLMN selection before the UE lost coverage. As such, the UE first attempts cell selection based on the same frequencies stored before coverage was lost. If that is not successful, the UE goes through an initial cell selection, and during that process, it is unlikely (in scenarios of interest) that the UE finds itself in a different PLMN to re-perform a PLMN selection. For the latter, exceptional, cases, cell access may take an extended amount of time. However, in the scenarios of interest, more common cases are considered, in which registration is not required upon coming back from out of coverage (re-entering coverage).
  • PLMN selection with registration may take several sections depending on where the UE starts. However, this amount of time may be significantly curtailed if the UE is registering in the same PLMN and does not fetch the authentication vector.
  • FIG. 6 illustrates public/private network scenarios in accordance with some aspects.
  • examples of private network use only and a combination of public and private network use is shown in FIG. 6.
  • each of the scenarios a and b depicted in FIG. 6 may use a different solution.
  • different scenarios and corresponding embodiments may be classified. Any difference(s) in terms of the procedures for initial access and/or reestablishment in each of the scenarios should be identified, and the embodiments should address corresponding roadblocks.
  • scenario a1/a2 the UE is out of coverage when outside of the private clouds in FIG. 6. During this time, the UE continuously searches for a cell; how frequently the UE searches is left up to the UE implementation (e.g., depending on the batteiy and many other factors).
  • scenario b1/b2 when the UE is in the PLMN (assuming that the UE is in PLMN coverage and allowed to access the PLMN, and PLMN has a proper deployment without huge coverage hole), when the UE comes (back) into the private network coverage (the small cloud), the UE may still be under the PLMN coverage, e.g., overlapping between the PLMN coverage and SNPN coverage (scenario b2).
  • prioritization may be defined to help the UE find the private network since otherwise, once a UE is in a cell in which the UE receives the service, the UE will stay in that cell and will not look for another cell, another private network, another carrier, etc., unless there is a different trigger.
  • a UE enters a factory setting (e.g., scenario b1/b2) with available uplink or downlink data that can (e.g., only) be exchanged through the private network (assuming that the PDU sessions are established and in place), the search for and accessing the private network is initiated (data-based triggering).
  • a factory setting e.g., scenario b1/b2
  • available uplink or downlink data that can (e.g., only) be exchanged through the private network (assuming that the PDU sessions are established and in place)
  • the search for and accessing the private network is initiated (data-based triggering).
  • the UE goes out of coverage of the PLMN while entering the SNPN area, e.g., the SNPN covers the PLMN’s non-covered areas.
  • the trigger for the UE to look for a (private) cell may not be taken care of separately, i.e., the trigger may happen more naturally as a result of going out of (PLMN) coverage.
  • proximity indication is defined as an UL message from the UE.
  • the trigger for the UE to search for home cells is based on location information stored in the UE - either GPS or an RF fingerprint, which triggers the proximity indication to the network.
  • the network uses this to initiate measurements of the home cell with the intention of performing handover to the home cell. Accordingly, the UE can remember the proximity in which the UE had found a private/home network with the previous RF conditions. It is left up to UE implementation whether the UE uses actual geographical coordinates, or only uses the RF map to remember the previous detection. Consequently, when similar conditions are triggered, the UE starts searching for the private network.
  • a UE uses information of coverage map(s) built, updated, and maintained by potentially different networks (and the corresponding UEs) to manage its procedures and triggers (and even the state transitions) when the UE (potentially frequently) goes out of the coverage of a (private or public) network and comes back into the coverage of same or different network.
  • a UE in an RRC_IDLE mode of a network knows that in a certain proximity the UE had previously been in a (same or different) network coverage (i.e., the UE knows the location either in terms of the RF map or the GPS geographical coordinates), then the UE can trigger looking for/identify the corresponding cell and camp on the corresponding cell.
  • the UE has access to the map so that when the UE enters geographical coordinates of a cell, the UE identifies the cell to camp on (when camped on a (suitable) cell, the UE performs the requirements for the RRC_IDLE state camped on any cell state, such as monitoring for PWS and emergency call).
  • the disclosed embodiments may be indicated as the expected operation in certain deployments, e.g., where the network may configure specific operations/procedures, or can be applied or triggered based on knowledge of a map (coverage and/or blockage map), as well as knowledge of the location.
  • the disclosed embodiments equip the UE with (prior) knowledge on a cell existence and that the UE can already determine that the cell is a suitable cell, and the UE can have essential system information from a previous connection and/or pre-configuration, the cell selection process and/or the sub-procedures of cell selection can be optimized for the deployments of interest.
  • the current design of cell selection primarily supports looking for cells constantly until one is found to camp on. This is inspired by the current system design principle that coverage should always be available everywhere and the UE should always be anchored on a cell. However, it is not practical or feasible for the UE to keep searching for SSBs in deployments with sporadic coverage.
  • One of the bottlenecks and infeasibilities discussed in section 5.1.2 the efficiency of running communications for high bands is also quite challenging (power amplification (PA), wider bandwidth, etc.), and the power consumption is high.
  • PA power amplification
  • the embodiment herein enable proper management of when the UE starts and/or stops the cell search procedure and enables the UE to find and select the right cell (which may be the only available cell) at the right time.
  • a trigger of the cell search function is used for the UE to find the private cell . While such a trigger may be based on data availability, other embodiments are possible. For example, the trigger can be based on RF conditions or location. For example, if the UE has GPS coordinates, the UE is able to determine that the UE is entering the coordinates where the UE knows there is a private network. Then, the UE can initiate the private network cell search. While the UE may, in addition, have continuously been searching for the private network, such a search is not efficient.
  • the UE Once the UE has found the private network and can camp on the private network, whether the UE stays in the RRC_INACTIVE state (i.e., whether the UE performs an RNA or whether the UE performs RRC_IDLE state procedures to the connected transition), depends on whether the RNA is supported between these two boundaries (e.g., inter-PLMN RNA update and RRC_INACTIVE state transfer being possible).
  • the RNA is supported between these two boundaries (e.g., inter-PLMN RNA update and RRC_INACTIVE state transfer being possible).
  • E-PLMNs equivalent PLMNs
  • a unique identifier is defined to enable finding the old context, as well as an interface defined to retrieve the RRC_INACTIVE context from the PLMN base station to a private network base station.
  • the UE is then able to stay in the RRC_INACTIVE state and continue operation from this state.
  • I-RNTI inactive RNTI
  • E-PLMNs E-PLMNs
  • PLMN component similar to network sharing
  • a UE when a UE enters a factory setting (e.g., scenario b1/b2), with some available uplink or downlink data that can (only) be exchanged through the private network, the UE is triggered to stay in the RRC_INACTIVE state. This may occur even when the UE exits the private network coverage, e.g., while being active in the PLMN.
  • a factory setting e.g., scenario b1/b2
  • scenario b1/b2 e.g., scenario b1/b2
  • the UE is triggered to stay in the RRC_INACTIVE state. This may occur even when the UE exits the private network coverage, e.g., while being active in the PLMN.
  • the UE keeps searching for a suitable cell (any cell selection state), and after not finding any suitable cell to camp on, the UE finally ends up camped on any cell state (RRC_IDLE).
  • RRC_IDLE any cell state
  • it is not possible to exactly quantify how long these transitions take e.g., at what point the UE drops its context, at what point the UE enters the RRC_IDLE state once the UE is out of coverage, etc.). While the amount of time depends on how quickly the UE loses the cell, etc., about 10s may be a reasonable rough estimate of the incurred time.
  • the UE has lost the cunent cell and has not found a suitable cell.
  • the latency depends on how rapidly the UE loses the coverage of the cell and ends up in a state where the UE cannot find a suitable cell. This is not specified in 3GPP standards and depends on how rapidly the RF conditions change and the UE finds itself in that state.
  • the UE context is stored such that the context can be reused when the UE comes back into the coverage.
  • the UE transitions into the RRC_IDLE state the UE releases the stored UE context.
  • an infinity timer may be used for a determination whether to delete the stored UE context; the network and the UE are synchronized such that the network will also store the UE context indefinitely. In this case, the UE is able to go out of the network coverage, keep storing the UE context, and reuse the previous stored context whenever the UE comes back into the coverage.
  • the UE may avoid performing all the (conventional) actions/procedures when in the RRC_INACTIVE state, e.g., cell reselection, paging monitoring, measurement and checking the criteria, etc.
  • the UE When the UE is out of the coverage, the UE only stores the context. Accordingly, when the UE is in any cell selection state (i.e., out of coverage) and in the RRC_INACTIVE state, when the UE finds a suitable cell, the UE remains in the RRC_INACTIVE state, and continue operation from there. This may be defined as a new extension of the UE states, which lies between any cell selection state and the RRC INACTIVE state.
  • UEs in either the RRC_IDLE state or the RRC_INACTIVE state can be in any cell selection state, while only UEs in the RRC_IDLE state are able to camp on a suitable cell if found after the search. This means that when such a cell is found, inactive UEs may enter idle and then camp on the cell. Otherwise, an inactive UE may continue in any cell selection state searching for a suitable cell.
  • FIG. 7 illustrates RLF actions in accordance with some aspects.
  • the RRC connection re-establishment procedure in NR and prior technologies permits re-establishment of the RRC connection (see, e.g., TS 38.331).
  • a UE in the RRC_CONNECTED state for which AS security has been activated with SRB2 and at least one data radio bearer (DRB) setup, may initiate the procedure to continue the RRC connection, e.g., upon facing an RLF, which may be due to a relatively long term link blockage or by going out of the coverage.
  • DRB data radio bearer
  • the UE upon declaring RLF, the UE tries to find a suitable cell; if found, the UE initiates connection re-establishment procedure as shown in FIG. 7.
  • the connection re-establishment succeeds if the network is able to find and verify a valid UE context or, if the UE context cannot be retrieved and the network responds with an RRCSetup message according to clause 5.3.3.4 (fallback to RRC establishment).
  • the network applies the procedure as follows: when AS security has been activated and the network retrieves or verifies the UE context: re- activate AS security without changing algorithms and re-establish and resume the SRB1; when UE is re-establishing an RRC connection and the network is not able to retrieve or verify the UE context: discard the stored AS Context and release all RBs and fallback to establish a new RRC connection.
  • the UE does not initiate the procedure but instead moves directly to the RRC_IDLE state with a release cause 'other' or 'RRC connection failure', respectively.
  • the UE performs cell selection when going to the IDLE state from the connected state (the box “cell selection up on leaving connected state” in FIG. 5), which normally may not involve any latency, as the current cell in which the UE was connected satisfies the suitability requirement in almost all cases and the UE simply camps on the same cell. Further, the cell selection procedure is used in such situation instead of cell reselection procedure to speed up the procedure. Cell selection in these cases is faster than cell reselection as the UE finds only a suitable cell (which is relatively fast as the UE already has measurements of the current cell), while during reselection the UE also measures neighboring cells to find the “best” cell to camp on.
  • the AS security can then be immediately re-activated without changing algorithms and SRB1 can be resumed.
  • the cell selection procedure can be performed only under limited circumstances and in a directed way.
  • the knowledge may include coverage/cell existence by proximity detection based on location and/or RF conditions, coverage map, blockage map, etc. This may permit the cell selection procedure to be performed quickly, especially combined with cell selection based on stored knowledge of carrier frequency and/or cell/system information as above, for example, eliminating a significant amount of hypothesis testing and other uncertainties to be figured out by the UE.
  • both the triggering of cell selection, as well as the process of cell selection itself, can be directed based on certain information/ knowledge by (and/or between) the UE and network. Consequently, the process of recovery from RLF and/or losing and gaining coverage can be handled quickly and seamlessly, with minimized overhead.
  • TS 38.331 a set of actions following cell selection while RLF has been declared (i.e., T311 timer is running) has been specified.
  • the UE upon selecting a suitable NR cell, the UE ensures having valid and up to date essential system information, applies the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in SIB1, and initiates transmission of the RRCReestablishmentRequest message. This procedure applies also if the UE returns to the source PCell.
  • the reestablishment request may be immediately sent, and the operation can be quickly continued/started.
  • even the RRCReestablishmentRequest message may not be transmitted in certain conditions. These conditions include when network also has enough level of knowledge and prediction about the UE’s situation.
  • the UE In order for the UE to start the initial access in a new cell, the UE should identify itself in the new cell. For example, the UE may identify itself in a cell based on location information, coverage map, etc.
  • the UE may be provided with a dedicated random access channel (RACK). While in current systems this option may not be feasible due to level of RACK resources to be reserved, but in future system design, this may be addressed. Examples of re-accessing the same cell are discussed below.
  • RACK dedicated random access channel
  • T310 timer also called RLF declaration timer
  • the UE returns to normal operation. If T310 timer expires without the UE observing enough in-sync indications, the UE considers itself in a RLF condition. As specified in TS 38.331 subclause 5.3.10.3, RLF detection may be due to T310 timer expiry, which may happen due to blockages and/or coverage limitations.
  • the UE After RLF declaration, the UE initiates the steps for connection reestablishment. This includes performing cell selection to identify a cell to perform reestablishment. Each UE, upon detecting an RLF, starts a timer which expires after a predetermined configured time period (RLF timer duration) as part of a reestablishment procedure. In NR and prior technologies, this timer is called T311 timer, and ends once the UE finds a suitable cell for RRC connection reestablishment or expires after a predetermined time period. If the UE identifies and selects a suitable cell for reestablishment within the T311 time period, the UE transmits an RRC reestablishment request message.
  • RLF timer duration a predetermined configured time period
  • the UE actions upon RLF T311 timer expiry have also been specified. Particularly, if the procedure was initiated due to RLF or handover failure, the noSuitableCellFound in the VarRLF-Report is set to true, and the UE performs actions upon entering the RRC_IDLE state, with release cause 'RRC connection failure'. Similarly, if the selected cell becomes no longer suitable according to cell selection criteria specified in TS 38.304, the UE performs actions upon going to the RRC_IDLE state, with release cause 'RRC connection failure'. [00139] The reestablishment procedure allows the UE to access another cell if the UE has any problem with its current serving cell.
  • the RLF timer may not be triggered/used or may be set to a sufficiently large value (or to infinity) to avoid transitioning to the RRC_IDLE state before likely reentry to coverage in the particular area of sparse deployment (e.g., the value may increase as the coverage island size decreases/size between islands increase).
  • the T311 timer is proportional to the distance between islands.
  • expiry of the T311 timer before finding a suitable cell is avoided.
  • the UE upon expiry of a T311-like timer, the UE transitions to the RRC_INACTIVE state, while the UE context is stored.
  • the UE does not wait until the T310 timer expires to initiate a Connection Reestablishment procedure (or a shortened procedure that is faster and less involved than the current reestablishment procedure), if the UE has knowledge of availability/unavailability of another cell coverage or the same cell coverage.
  • the use of the T310 timer allows the UE to avoid ending up looking for another cell when the UE can potentially recover faster in the same cell.
  • the UE can accordingly adjust the UE behavior and triggering of any procedure such as reestablishment and cell search/selection.
  • the UE can perform more optimized actions, e.g., using a shorter timer or bypassing some of the steps/procedures.
  • the UE in response to a determination that the UE is in the same cell, the UE can avoid the reestablishment procedure (upon facing RLF) and only perform a random access procedure to re-access the cell (similar to beam failure recovery).
  • the system information does not change before and after the RLF, and the reestablishment (if any) for the same cell can be much quicker than reestablishment to a different cell.
  • the UE may avoid performing the random access procedure.
  • the UE may perform cell search and cell selection every time the UE goes in and out of the coverage or faces a link blockage. In particular, for the case of blockage, the UE may be better off staying in the same cell and attempt recovery in the same cell.
  • the UE may be redirected to the desired cell (e.g., same cell) after facing an RLF. The redirection may be based on prior information of the deployment, location, etc., or based on network configuration upon the first time the UE has entered the coverage, etc.
  • certain coverage areas/islands of the deployment or the whole (private) deployment may be identified as a (cell) group over which the UE may assume certain essential system information without critical changes.
  • the UE may avoid re-acquiring information, re- selecting the cell(s), and/or performing conventional re-establishment procedures.
  • the UE may not stay in the cell.
  • the UE may try finding a suitable cell and attempting the random access procedure in another cell.
  • the UE may re-perform the random access procedure using the previous/original selected beams after waiting a predetermined amount of time. This time may depend on characteristics of the link problem, UE speed, location e.g., the duration of blockage or coverage problem.
  • the UE is able to realize/identify the nature of the link problem, based on whether the UE has moved and/or its speed, and take actions accordingly. For example, if the UE realizes that no meaningful movement has been made, the UE waits until the (mobile) blockage is cleared and assumes that the UE is (most likely) in the same cell. In this case, meaningful movement may be movement that could result in a link problem. This behavior would be beneficial if there is no other alternative cell available.
  • the UE may have identified the unavailability of other cells based on the measurements performed during connected mode operation. The UE may check whether its serving cell before the blockage is still suitable, which may be done quickly.
  • the UE may avoid reading the SIB, etc., and can immediately access the cell.
  • the UE instead of checking whether the serving cell is still suitable before the out-of-coverage event or before blockage, the UE can assume the serving cell is suitable. As above, this may be assumed by the UE if the UE has not moved, etc. (also relevant to the statistic and nature of blockage). In other words, in sparse deployments, a suitable cell can be assumed to be the most recent cell on which the UE was operating. In such case, the functionality of the T311 timer is evaded, as the suitable cell is immediately identified, and use of the T311 timer may be avoided.
  • the OOC duration may be comparable or of the same order as the in-coverage duration. If the UE does not go OOC for an extended period, the UE may not lose all aspects of the previous serving cell (which is also the current cell). Particularly, the UE may be assumed to be in the same cell (and is able to determine this just by acquiring the MIB, as the PCI has not changed). The UE may avoid acquiring the SIB (at least if modification period has not changed). As such, some of the access delays may not be applicable.
  • FIG. 8 illustrates a 5G NR initial access procedure in accordance with some aspects.
  • FIG. 8 entails different sub-procedures to acquire cell access.
  • a synchronization raster scan is used that currently outweighs the latency of the remaining initial access operations.
  • the UE identifies the strongest cell as per the CD-SSB located on the synchronization raster and proceed to decode the system information. If the UE discovers a set of SSBs without any associated system information, the UE moves to another set of SSBs as cells without SIB1 cannot be used as a PCell.
  • Cell selection given the carrier frequency and initial beam acquisition without the burden of the raster scan also occurs in FIG. 8.
  • the latency of beam acquisition outweighs the remaining initial access operations.
  • the cell detection and selection can be faster by relying on information provided by the network, or from previous occasions that the UE accessed the cell, and from location and map knowledge.
  • Finding the beam to establish the connection with the identified cell remains a challenge in terms of latency, including finding the PSS/SSS, taking measurements, and decoding the MIB.
  • the UE may continue with measurements of cells in parallel and pick the strongest/suitable PSS/SSS as initial beam acquisition is performed as part of finding a suitable cell.
  • the UE compares RSRP across different Rx beams and chooses the highest. By doing so, the UE selects best Rx beam. To find the strongest cell, the UE completes measurements of all neighboring cells and compares the signal strength and quality of all the cells. If the UE is to obtain immediate access after coming back into coverage, the UE is allowed to do cell selection and make access on a cell that is acceptable (i.e., as long as it can do measurements for one cell and it is acceptable, the cell may not be the strongest cell). In limited coverage scenario, the likelihood of availability of neighboring cell(s) is low and the UE may measure the only available cell.
  • the UE proceeds with SIB1 acquisition, and then the CP procedure (RACK and RRC connection establishment) shown in FIG. 8.
  • Each step of the high-band access and connection establishment procedure is subject to blockage occurrence which can significantly increase the corresponding latency, although the exact characterization of blockage depends on many untraceable factors. Further, the higher initial access latency (the longer procedures), the more likely blockage happens during the access procedures. This implies a two-fold negative impact from blockage.
  • the UE may not constantly perform scanning for cell search/sel ection to save UE power. As such, additional latency may be added.
  • cell selection itself can require a significant time due to sync frequency raster scan, and is likely the bottleneck of UE’s operation under limited coverage.
  • an NR UE in limited coverage deployments may get stuck at the cell search/sel ection step and operation may be infeasible, e.g., by missing the target cell frequency due to OOC/blockage and not coming back to that frequency shortly enough, etc.
  • PLMN selection with registration is also used, depending on where the UE starts, this selection may add several seconds to the access latency. However, if the UE is registering in the same PLMN and does not fetch the authentication vector, the selection may take shorter.
  • the coverage range is estimated (via link-budget analysis) for a single cell. Consequently, an estimate of the average per UE coverage-time can be obtained based on the UE speed, cell load (#UEs), and overall overhead channels (SSB, CSI-RS, DMRS, SRS, PTRS), beam tracking, etc.
  • cell diameter may be about 94m, resulting in a max of 30s (6s) in coverage duration for 3m/s (60km/h) mobility, and assuming simple linear UE trajectory.
  • cell diameter may be about 66m, resulting in a max of 20s (3.7s) in coverage duration for 3m/s (60km/h) mobility, and assuming simple linear UE trajectory.
  • 28 GHz pathloss is ⁇ 12dB lower than 100 GHz, requiring 12dB more antenna gains for same coverage.
  • the 64x64 antennas provides 6dB gain at each Rx and Tx compared to 16x16 antennas.
  • the antenna size is reverse proportional to carrier frequency. Comparing carrier frequencies of 100 and 28 GHz, about 4 times reduction in antenna size, and inter-antenna distance is expected.
  • the Tx antenna should be installed at a very high height (very directional). At ⁇ 10-15m street lam height, the area coverage area becomes smaller with the same ⁇ angle, with more concentrated power. This can achieve higher supported throughput in a more limited area.
  • the total available time resource for a UE’s data transfer can be roughly estimated as (in-coverage duration - access delay)x(1 - DL OH%)x(1 - UL OH%) _ #active UEs per cell (e.g.,at the time of data transfer phase for UE of interest) .
  • enhancements targeting reduced access latency due to any of the procedures/steps of the initial access may enable operation in certain deployment scenarios.
  • the time duration within THz coverage in non-blocked state is transient and valuable. As such, even small amount of latency reduction can translate into a significant amount of additional data transfer due to the high throughput.
  • the evolvements of access procedure may target reducing how frequent the corresponding procedure is required, as well as how long each round of performing the procedure may take.
  • the UE may spend a significant amount of time in the blocked state, and infeasibility problem may be even more severe (e.g., may need to subtract the total (significant) amount of time UE spends in the blocked state as well as the latency of blockage recovery procedures, from in-coverage duration). Accordingly, proper handling/accel erating of both access procedure as well as link issues and blockages for standalone high-band operation with sparse coverage described herein may be used.
  • Example 1 is an apparatus for a user equipment (UE), the apparatus comprising: processing circuitry configured to: determine that the UE has entered a coverage area within an area of sparse deployment of cells; determine whether the UE has stored cell information of a cell in the coverage area, the cell information comprising carrier frequency and system information broadcast 1 (SIB 1 ); and in response to a determination that the UE has previously entered the coverage area, use the cell information to establish communications with the cell; and a memory configured to store the cell information.
  • SIB 1 carrier frequency and system information broadcast 1
  • Example 2 the subject matter of Example 1 further includes that the processing circuitry is further configured to: decode a master information block (MIB) comprising a Physical Cell identifier (PCI) and a value tag, the value tag including information of the SIB1 of a cell in the coverage area; determine whether the UE has previously entered the coverage area based on the cell information and the PCI; and in response to a determination that the UE has previously entered the coverage area, determine whether to bypass acquisition of the SIB1, determination of whether to bypass acquisition of the SIB1 based on at least one of: the value tag, or a modification period decoded from the cell or predetermined that defines a time period over which system information modification is allowed.
  • MIB master information block
  • PCI Physical Cell identifier
  • Example 3 the subject matter of Example 2 further includes that: the cell information comprises a previously obtained value tag, and the processing circuitry is configured to determine whether to bypass acquisition of the SIB1 based on whether the value tag is different from the previously obtained value tag.
  • Example 4 the subject matter of Examples 2-3 further includes that: the time period is predefined or indicated in the MIB, and in response to a determination that the UE has not been out of coverage longer than the time period, the processing circuitry is configured to rely on previously acquired system information, including SIB1.
  • Example 5 the subject matter of Examples 1-4 further includes that: the cell information comprises a master information block (MIB) comprising a Physical Cell identifier (PCI) of a cell in the coverage area, and the processing circuitry is further configured to use the MIB and the PCI of the cell information to bypass acquisition of the SIB1.
  • MIB master information block
  • PCI Physical Cell identifier
  • Example 6 the subject matter of Examples 1-5 further includes that the processing circuitry is further configured to: perform public land mobile network (PLMN) selection to register with a PLMN after entry into the coverage area; determine that the UE has lost coverage provided by the coverage area after PLMN selection; upon reentering coverage, determine based on UE characteristics, that the coverage is still provided by the PLMN; and bypass authentication in response to a determination that the coverage is still provided by the PLMN.
  • PLMN public land mobile network
  • Example 7 the subject matter of Examples 1-6 further includes that the processing circuitry is further configured to: determine that the UE has lost coverage provided by the coverage area, the area of sparse deployment of cells being a private network, the UE remaining in an INACTIVE state with stored UE context after the coverage of the private network is lost; after a determination of lost coverage, obtain coverage from a public network, the coverage of the public network overlapping the coverage of the private network; and upon reentering coverage provided by the private network and the coverage from the public network remaining, access the private network and drop the coverage of the public network based on prioritization between the private network and the public network.
  • Example 8 the subject matter of Examples 1-7 further includes that the processing circuitry is further configured to: determine that the UE has lost coverage provided by the coverage area, the area of sparse deployment of cells being a private network, the UE remaining in an INACTIVE state with stored UE context after the coverage of the private network is lost; after a determination of lost coverage, obtain coverage from a public network, the coverage of the public network overlapping the coverage of the private network; and upon reentering coverage provided by the private network and the coverage from the public network remaining, access the private network and drop the coverage of the public network based on an exchange of data with the private network, the data limited in availability to the private network.
  • Example 9 the subject matter of Examples 1-8 further includes that the processing circuitry is further configured to: determine that the UE has lost coverage provided by the coverage area, the area of sparse deployment of cells being a private network, the UE remaining in an INACTIVE state with stored UE context after the coverage of the private network is lost; after a determination of lost coverage, obtain coverage from a public network, the coverage of the public network overlapping the coverage of the private network; and upon reentering coverage provided by the private network and the coverage from the public network remaining: determine reentry of coverage provided by the private network based on or more of: radio frequency (RF) conditions of private network stored in the memory, or geographical location and private network coverage map information; and in response to a determination of reentry of coverage provided by the private network, access the private network and drop the coverage of the public network.
  • RF radio frequency
  • Example 10 the subject matter of Examples 1-9 further includes that the processing circuitry is configured to: determine that the UE has lost coverage provided by the cell; after a determination of lost coverage, determine whether the UE remains within the area of sparse deployment from a radio frequency (RF) or coverage map of the area of sparse deployment; and in response to a determination that the UE remains within the area of sparse deployment, identify, select, and camp on a corresponding cell based on the map or location knowledge.
  • RF radio frequency
  • Example 11 the subject matter of Examples 1-10 further includes that the processing circuitry is configured to use a unique identifier to support an inter-public land mobile network (PLMN) INACTIVE state and enable finding a prior UE context, the identifier comprising a PLMN component that is specific to the PLMN.
  • PLMN inter-public land mobile network
  • Example 12 the subject matter of Examples 1-11 further includes that in response to a determination that the UE is in the area of sparse deployment, the processing circuitry is configured to at least one of: initiate a Connection Reestablishment procedure prior to expiration of a radio link failure (RLF) T310 timer; or one of: avoid triggering a T311 timer or set the T311 timer to a value to avoid expiry of T311 timer before finding a suitable cell and remain in an INACTIVE state.
  • RLF radio link failure
  • Example 13 the subject matter of Examples 1-12 further includes that in response to a determination that the UE is in the area of sparse deployment and is in a same cell before and after radio link failure (RLF), the processing circuitry is configured to avoid a reestablishment procedure and limit procedures to re-access the cell to a random access procedure, determination that the UE is in the same cell before and after RLF based on at least one of knowledge of UE location, radio frequency (RF) conditions, or a coverage map.
  • RLF radio link failure
  • Example 14 the subject matter of Examples 1-13 further includes that the cell information is acquired one of: from another cell in the area of sparse deployment with which the UE previously established communications, from a previous time that UE has established communication with the cell, or from pre-configured default values.
  • Example 15 the subject matter of Examples 1-14 further includes that the processing circuitry is configured to use predetermined cell or system information within at least one of a portion of the area of sparse deployment without at least one of: re-acquisition of at least a portion of the system information, re-selection of cells within the area of sparse deployment, or performance of re-establishment procedures used outside the area of sparse deployment.
  • Example 16 the subject matter of Examples 1-15 further includes that the processing circuitry is configured to determine an INACTIVE state with stored UE context is a fallback state, based on a determination that the UE is within the area of sparse deployment, and at least one of: the UE is out of coverage of a previously acquired primary cell or a T311 timer has expired.
  • Example 17 is an apparatus for a cell, the apparatus comprising: processing circuitry configured to: generate, based on information from user equipments (UEs) and other cells within an area of sparse deployment that contains the cell, a radio frequency (RF) map; encode, to a first UE, the RF map and an indication to store system information associated with the cell; and decode, from the first UE while the first UE is in at least one of an RRC_INACTIVE state or an RRC_IDLE state, communications based on the RF map; and a memory configured to store the RF map.
  • UEs user equipments
  • RF radio frequency
  • Example 18 the subject matter of Example 17 further includes that the processing circuitry is configured to: encode, for transmission to the first UE, an indication of a radio link failure (RLF) T311 timer with a value that avoids transition of the first UE to the RRC_IDLE state, or decode, from the first UE, a Connection Reestablishment procedure prior to expiration of a radio link failure (RLF) T310 timer.
  • RLF radio link failure
  • Example 19 is a non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of a user equipment (UE), the one or more processors to configure the UE to, when the instructions are executed: determine that the UE has entered a coverage area within an area of sparse deployment of cells; determine whether the UE has stored cell information of a cell in the coverage area, the cell information comprising carrier frequency and system information broadcast 1 (SIB1); and in response to a determination that the UE has previously entered the coverage area, use the cell information to establish communications with the cell.
  • SIB1 carrier frequency and system information broadcast 1
  • Example 20 the subject matter of Example 19 further includes that the instructions, when executed, further configure the one or more processors to configure the UE to: determine that the UE has lost coverage provided by the cell; after a determination of lost coverage, determine whether the UE remains within the area of sparse deployment from a radio frequency (RF) map of the area of sparse deployment; and in response to a determination that the UE remains within the area of sparse deployment, identify and camp on a corresponding cell based on the RF map.
  • RF radio frequency
  • Example 21 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement of any of Examples 1-20.
  • Example 22 is an apparatus comprising means to implement of any of Examples 1-20.
  • Example 23 is a system to implement of any of Examples 1-20.
  • Example 24 is a method to implement of any of Examples 1-20.

Landscapes

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

Abstract

Sont décrits un appareil et un système pour améliorer des processus de recherche et de sélection de cellules. Un UE dans une zone de déploiement épars utilise des informations stockées d'une cellule à sélectionner qui a été obtenue lorsque l'UE a d'abord sélectionné la cellule. L'UE utilise des informations de système acquises précédemment lors de la sortie et de la ré-entrée dans la couverture de la cellule, sauf indication contraire par la cellule. L'UE, lors de la ré-entrée dans la couverture, utilise une carte RF pour déterminer si les informations stockées doivent être utilisées pour identifier et résider sur la cellule. Lorsque l'UE est dans la zone de déploiement épars, le minuteur T311 est ajusté pour permettre à l'UE de limiter la transition vers l'état RRC_IDLE et l'UE déclenche un processus de rétablissement de connexion avant l'expiration du minuteur T310.
PCT/US2022/013119 2021-01-26 2022-01-20 Recherche et sélection de cellules pour réseaux ng WO2022164706A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163141674P 2021-01-26 2021-01-26
US63/141,674 2021-01-26

Publications (1)

Publication Number Publication Date
WO2022164706A1 true WO2022164706A1 (fr) 2022-08-04

Family

ID=82654887

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2022/013119 WO2022164706A1 (fr) 2021-01-26 2022-01-20 Recherche et sélection de cellules pour réseaux ng

Country Status (1)

Country Link
WO (1) WO2022164706A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070275717A1 (en) * 2006-03-07 2007-11-29 Qualcomm, Incorporated Network selection by wireless terminals
US20150111594A1 (en) * 2013-10-21 2015-04-23 At&T Mobility Ii Llc Network based speed dependent load balancing
WO2020180071A1 (fr) * 2019-03-01 2020-09-10 Samsung Electronics Co., Ltd. Procédure de rétablissement de rrc d'irat et procédure de reprise d'irat

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070275717A1 (en) * 2006-03-07 2007-11-29 Qualcomm, Incorporated Network selection by wireless terminals
US20150111594A1 (en) * 2013-10-21 2015-04-23 At&T Mobility Ii Llc Network based speed dependent load balancing
WO2020180071A1 (fr) * 2019-03-01 2020-09-10 Samsung Electronics Co., Ltd. Procédure de rétablissement de rrc d'irat et procédure de reprise d'irat

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 16)", 3GPP DRAFT; DRAFT_36300-G40_V2, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 5 January 2021 (2021-01-05), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051967533 *
ERICSSON: "Cell selection and reselection for NPN", 3GPP DRAFT; R2-2002593, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online Meeting ;20200420 - 20200430, 9 April 2020 (2020-04-09), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051870088 *

Similar Documents

Publication Publication Date Title
US20210051530A1 (en) 5G NR Voice Call EPS Fallback Enhancements
US20190394714A1 (en) Method and apparatus for lte cell search using multiple receivers of a mobile device
US9730157B2 (en) Wireless local area network assisted network detection for user equipment
US11540195B2 (en) Cellular enhancements for application mobility
JP2020530219A (ja) セル選択および／または再選択を処理するための無線デバイスおよびその方法
WO2022146767A1 (fr) Comportement d'instance d'intervalle dans des motifs d'intervalle concurrents
EP4233348A1 (fr) Mesure rrm relaxée pour ue redcap
WO2022150197A1 (fr) Capacité d'ue pour mesures avec intervalle préconfiguré
WO2022151209A1 (fr) Détection d'économie d'énergie pour ue à détection réduite faisant appel à une réévaluation de ressources et à une préemption de ressources
US20210022181A1 (en) Mechanisms to operate downlink wideband carrier in unlicensed band
CN115066960A (zh) 处理多SCell激活中断的方法和装置
US20220272660A1 (en) Musim ue connection release, paging restriction and rejection
US20210368435A1 (en) Method and apparatus for essential slice service processing and recovery of service
WO2021065748A1 (fr) Procédé et appareil pour effectuer un transfert d'un ue multi-usim à compatibilité radio sur des systèmes identiques ou différents
EP4218275A1 (fr) Accès efficace à des tranches de réseau d'opérateur unique
WO2022164706A1 (fr) Recherche et sélection de cellules pour réseaux ng
CN115486131A (zh) 独立模式plmn选择
CN113286334A (zh) Uli小区选择优先化
US20240129790A1 (en) Sdt and cn buffering co-existence in inactive state
US20230138190A1 (en) Ai-based model use for network energy savings
US20230180186A1 (en) Power saving sensing for reduced sensing ues using partial sensing and additional sensing with a prioritized resource selection window
WO2022056431A1 (fr) Accès efficace à des tranches de réseau d'opérateur unique
US20240223323A1 (en) Ue capability to activate pre-configured measurement gap
US20240236930A1 (en) Validity conditions for positioning assistance data
WO2023216115A1 (fr) Procédé, dispositif et système de configuration de cellule auxiliaire dans des réseaux sans fil

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22746414

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22746414

Country of ref document: EP

Kind code of ref document: A1