Network slicing / service type for positioning and sensing

Abstract

Aspects presented herein may improve the accuracy, latency, and / or reliability of UE positioning by enabling private network slices to be defined and configured for UE positioning and sensing. In one aspect, the UE sends, for a network entity, a first indication of a list of NSSAIs, where each NSSAI in the list of NSSAIs is associated with at least one of a positioning mode, a sensing mode, a positioning specific service type, or a sensing specific service type. The UE communicates with the network entity based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type. In some examples, the NSSAI may include at least one of a high accuracy NSSAI, a low latency NSSAI, a low power NSSAI, an SL positioning NSSAI, a hybrid Uu-SL positioning NSSAI, or a positioning NSSAI implemented by ML.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of Greek application serial number 20230100238, filed on March 22, 2023, entitled “NETWORK SLICE / SERVICE TYPE FOR POSITIONING AND SENDING,” the entire text of which is expressly incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to wireless communications with respect to positioning and network slicing. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single-carrier frequency division multiple access (SC-FDMA), and time division synchronous code division multiple access (TD-SCDMA).

[0005] These multiple-access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. One example telecommunication standard is 5G New Radio (NR). 5G NR is part of the ongoing mobile broadband evolution being promulgated by the 3rd Generation Partnership Project (3GPP) to address new requirements related to latency, reliability, security, scalability (e.g., for the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements may also be applicable to other multiple-access technologies and telecommunication standards that employ them. Summary of the Invention

[0006] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary does not identify key or critical elements of all aspects, nor does it delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that will be presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus sends a first indication of a list of network slice selection assistance information (NSSAI) to a network entity, wherein each NSSAI in the list is associated with at least one of a positioning mode, a sensing mode, a positioning specific service type, or a sensing specific service type. The apparatus communicates with the network entity based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus receives a first indication of a NSSAI list from a user equipment (UE), wherein each NSSAI in the NSSAI list is associated with at least one of a positioning mode, a sensing mode, a positioning specific service type, or a sensing specific service type. The apparatus communicates with the UE based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type.

[0009] To achieve the foregoing and related ends, one or more aspects may include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some illustrative features of one or more aspects. However, these features are indicative of only some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0014] Figure 2D is a diagram illustrating an example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0016] Figure 4is a diagram illustrating an example of UE positioning based on reference signal measurement.

[0017] Figure 5 is a diagram illustrating example downlink (DL) positioning reference signal (PRS) resource prioritization according to various aspects of the present disclosure.

[0018] Figure 6 is a diagram illustrating an example format of single network slice selection assistance information (S-NSSAI) according to various aspects of the present disclosure.

[0019] Figure 7A is a diagram illustrating example network slice selection in a 4G Long Term Evolution (LTE) network according to various aspects of the present disclosure.

[0020] Figure 7B is a diagram illustrating example network slice selection in a 5G New Radio (NR) network according to various aspects of the present disclosure.

[0021] Figure 8 is a diagram illustrating an example of managing and identifying network slices through UE Routing Selection Policy (URSP) and S-NSSAI according to various aspects of the present disclosure.

[0022] Figure 9 is a communication flow illustrating an example of a network entity configuring a network slice associated with positioning / sensing for a UE according to various aspects of the present disclosure.

[0023] Figure 10 is a flow chart of a method of conducting wireless communications.

[0024] Figure 11 is a flow chart of a method of conducting wireless communications.

[0025] Figure 12 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0026] Figure 13 is a flow chart of a method of conducting wireless communications.

[0027] Figure 14 is a flow chart of a method of conducting wireless communications.

[0028] Figure 15 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0029] Various aspects presented herein can improve the accuracy, latency, and / or reliability of UE positioning by enabling specialized network slices to be defined and configured for UE positioning and / or sensing (e.g., radio frequency (RF) sensing). In one aspect of the present disclosure, positioning / sensing-specific network slices and slice differentiators (SDs) can be defined / configured for positioning / sensing entities (e.g., UEs, one or more base stations, location servers, etc.). For example, one or more standard slice / service type (SST) values ​​can be introduced / configured for positioning / sensing-related services. If more than one SST value is introduced / configured, the SST value can be (e.g., implicitly) mapped to one or more positioning / sensing modes, wherein one or more positioning modes can be associated with high-accuracy positioning / sensing slices, low-latency positioning / sensing slices, low-power positioning / sensing slices, ML-enabled positioning / sensing slices, and / or Uu / SL hybrid positioning slices, etc. The positioning / sensing-specific network slices and SDs can also be configured to support non-standardized SST values ​​for differentiating positioning services and / or to support SD signaling for various positioning modes.

[0030] Based on the network slicing described herein, enterprises with multiple applications can allocate different latency or bandwidth capabilities to specific systems with larger capacity specifications, such as smart meters enabled by the Internet of Things (IoT). A single network can be used to provide a variety of services based on specifications / user needs and various use cases. Network operators can also allocate the appropriate / correct amount of specific resources based on network slices. Therefore, the various aspects presented herein can provide more effective and efficient utilization of resources. For example, one network slice can be designed / configured to deliver low latency and low data rates, while another network slice can be designed / configured to deliver high throughput, etc. The various aspects presented herein can also enable network operators to reduce operating expenses (OPEX) and capital expenditures (CAPEX). The various aspects presented herein also significantly improve the operational efficiency of network service delivery and shorten time to market.

[0031] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details to provide a thorough understanding of the various concepts. However, these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0032] Several aspects of telecommunications systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0033] As an example, an element or any part of an element or any combination of elements may be implemented as a "processing system" comprising one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, processes, functions, or any combination thereof.

[0034] Thus, in one or more example aspects, implementations, and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other media that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0035] While aspects, implementations, and / or use cases are described herein through the lens of a few examples, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the aspects, implementations, and / or use cases may arise via integrated chip implementations and other non-module component-based devices (e.g., end-user devices, vehicles, communications devices, computing devices, industrial equipment, retail / purchase equipment, medical devices, devices enabled by artificial intelligence (AI), etc.). While some examples may or may not be specifically targeted at use cases or applications, the examples described may have broad applicability. The aspects, implementations, and / or use cases may range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the techniques described herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for both analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a variety of devices of various sizes, shapes, and configurations, including chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, and the like.

[0036] The deployment of a communication system, such as a 5G NR system, can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, a network node, a network entity, a mobility element of the network, a radio access network (RAN) node, a core network node, a network element, or network equipment (such as a base station (BS)), or one or more units (or one or more components) performing base station functionality can be implemented in a converged or disaggregated architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), a NR base station, a 5G NB, an access point (AP), a transmit / receive point (TRP), or a cell) can be implemented as a converged base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station.

[0037] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0038] Base station operation or network design can take into account the aggregated nature of base station functionality. For example, a disaggregated base station can be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (a network configuration such as that promoted by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation can include distributing functionality across two or more units at various physical locations, as well as virtually distributing the functionality of at least one unit, which can enable flexibility in network design. The various units of a disaggregated base station or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0039] Figure 1 Figure 100 illustrates an example of a wireless communication system and access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110, which may communicate directly with a core network 120 via a backhaul link or indirectly with the core network 120 through one or more disaggregated base station elements, such as a near real-time (near-RT) RAN intelligent controller (RIC) 125 via an E2 link, a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. CUs 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. DUs 130 may communicate with one or more RUs 140 via corresponding fronthaul links. RUs 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0040] Each of the units (i.e., CU 110, DU 130, RU 140, as well as near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, referred to as signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the communication interfaces of these units, may be configured to communicate with one or more of the other units via the transmission medium. For example, these units may include a wired interface configured to receive signals or transmit signals to one or more of the other units via the wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or transmit signals to one or more of the other units via the wireless transmission medium.

[0041] In some aspects, the CU 110 may host one or more higher-layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), and the like. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by the CU 110. The CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface, such as the E1 interface. As needed, the CU 110 may be implemented to communicate with the DU 130 for network control and signaling.

[0042] The DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, the DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) based at least in part on a functional split (such as those defined by 3GPP). In some aspects, the DU 130 may further host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 130 or with control functions hosted by the CU 110.

[0043] Lower layer functionality may be implemented by one or more RUs 140. In some deployments, a RU 140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functionality or low PHY layer functionality (such as performing Fast Fourier Transforms (FFTs), Inverse FFTs (iFFTs), digital beamforming, or Physical Random Access Channel (PRACH) extraction and filtering), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and CU 110 in a cloud-based RAN architecture, such as a vRAN architecture.

[0044] The SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 105 can be configured to interact with a cloud computing platform (such as Open Cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces (such as the O2 interface). Such virtualized network elements may include, but are not limited to, the CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, the SMO framework 105 can communicate with hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some implementations, the SMO framework 105 can communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 that is configured to support the functionality of the SMO framework 105 .

[0045] The non-RT RIC 115 may be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or in communication with the near-RT RIC 125 (e.g., via an A1 interface). The near-RT RIC 125 may be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions via an interface (e.g., via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

[0046] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from non-network data sources or from network functions at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns in performance and employ AI / ML models to execute corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or by creating RAN management policies (such as A1 policies).

[0047] At least one of the CU 110, DU 130, and RU 140 may be referred to as a base station 102. Thus, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated with a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides a UE 104 with access to core network 120. Base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmissions from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmissions from RU 140 to UE 104. The communication link may utilize multiple-input, multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be over one or more carriers. Base station 102 / UE 104 may utilize spectrum with a bandwidth of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) for each carrier allocated in a carrier aggregation for transmission in each direction, totaling up to Yx MHz (x component carriers). These carriers may or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0048] Certain UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. D2D communication links 158 may utilize DL / UL wireless wide area network (WWAN) spectrum. D2D communication links 158 may utilize one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSCCH), and a physical sidelink control channel (PSCCH). D2D communication may be accomplished via various wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0049] The wireless communication system may further include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available before communicating.

[0050] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, and so on, based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). Although a portion of FR1 extends beyond 6 GHz, FR1 is often (and interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes arises with FR2, which is often (and interchangeably) referred to as the "millimeter wave" band in documents and articles, despite being distinct from the extremely high frequency (EHF) band (30 GHz to 300 GHz), which is designated as a "millimeter wave" band by the International Telecommunication Union (ITU).

[0051] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR research has identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0052] With the above in mind, unless otherwise specified, if the term "sub-6 GHz" or the like is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless otherwise specified, if the term "millimeter wave" or the like is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0053] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signals 182 to UE 104 in one or more transmit directions. UE 104 may receive beamformed signals from base station 102 in one or more receive directions. UE 104 may also transmit beamformed signals 184 to base station 102 in one or more transmit directions. Base station 102 may receive beamformed signals from UE 104 in one or more receive directions. Base station 102 / UE 104 may perform beam training to determine the optimal receive and transmit directions for each of base station 102 / UE 104. The transmit and receive directions of base station 102 may or may not be the same. The transmit and receive directions of UE 104 may or may not be the same.

[0054] The base station 102 may include and / or be referred to as a gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, network equipment, or some other suitable terminology. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a converged (monolithic) base station having a baseband unit (BBU) (including a CU and DU) and a RU, or as a disaggregated base station including one or more of a CU, DU, and / or RU. A collection of base stations that may include disaggregated base stations and / or converged base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0055] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is a control node that handles signaling between the UE 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. The one or more location servers 168 are exemplified as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. More specifically, however, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, a Position Determination Entity (PDE), a Serving Mobile Location Center (SMLC), a Mobile Positioning Center (MPC), and the like. The GMLC 165 and LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may utilize one or more positioning methods to determine the location of the UE 104. Locating the UE 104 may involve signal measurements, position estimation, and optional rate calculation based on these measurements. Signal measurements may be performed by the UE 104 and / or the base station 102 serving the UE 104. The measured signals may be based on one or more of: a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), NR enhanced cell ID (NR E-CID) methods, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or other systems / signals / sensors.

[0056] Examples of UE 104 include a cellular phone, a smartphone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet device, a smart device, a wearable device, a vehicle, a utility meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of UE 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart rate monitor, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0057] Reference again Figure 1 In certain aspects, the UE 104 may include a network slice selection assistance information (NSSAI) request component 198, which may be configured to: send a first indication of an NSSAI list to a network entity, wherein each NSSAI in the NSSAI list is associated with at least one of a positioning mode, a sensing mode, a positioning specific service type, or a sensing specific service type; and communicate with the network entity based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type.

[0058] In certain aspects, the base station 102 may have an NSSAI providing component 199 that may be configured to: receive a first indication of an NSSAI list from a UE, wherein each NSSAI in the NSSAI list is associated with at least one of a positioning mode, a sensing mode, a positioning specific service type, or a sensing specific service type; and communicate with the UE based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type.

[0059] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A 、 Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, with subframe 4 configured with slot format 28 (mostly DL), where D stands for DL, U stands for UL, and F stands for flexible use between DL / UL, and subframe 3 configured with slot format 1 (all UL). While subframes 3 and 4 are shown with slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. The other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with the slot format via a received slot format indicator (SFI), either dynamically via DL control information (DCI) or semi-statically / statically via radio resource control (RRC) signaling. Note that the following description also applies to the 5G NR frame structure as TDD.

[0060] Figures 2A to 2D This example illustrates a frame structure, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more slots. A subframe may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each slot may include 14 symbols, and for an extended CP, each slot may include 12 symbols. Downlink symbols may be CP-orthogonal frequency division multiplexing (OFDM) symbols. Uplink symbols may be CP-OFDM symbols (for high-throughput scenarios) or discrete Fourier transform (DFT)-spread OFDM (DFT-s-OFDM) symbols (for power-limited scenarios; limited to single-stream transmission). The number of slots within a subframe depends on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). Symbol length / duration can be scaled with 1 / SCS.

[0061]

[0062] Table 1: Parameter set, SCS and CP

[0063] For normal CP (14 symbols / slot), different parameter sets µ 0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set µ, there are 14 symbols per slot and 2 per subframe. µ time slots. The subcarrier spacing can be equal to , where μ is for parameter sets 0 to 4. Therefore, the subcarrier spacing for parameter set μ = 0 is 15 kHz, and the subcarrier spacing for parameter set μ = 4 is 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A to 2D An example is provided for a normal CP with 14 symbols per slot and a parameter set µ=2 with 4 slots per subframe. The slot duration is 0.25ms, the subcarrier spacing is 60kHz, and the symbol duration is approximately 16.67µs. Within a frame set, there may be one or more different bandwidth parts (BWPs) frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0064] A resource grid can be used to represent the frame structure. Each slot consists of a resource block (RB) (also known as a physical RB (PRB)) that extends over 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0065] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RSs may include a demodulation RS (DM-RS) (indicated as R for one specific configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) used for channel estimation at the UE. The RSs may also include a beamforming RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0066] Figure 2BExamples of various downlink channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs). Each CCE consists of six resource element groups (REGs), with each REG comprising 12 contiguous REs within an OFDM symbol of a RB. The PDCCH within a BWP is referred to as a control resource set (CORESET). During PDCCH monitoring opportunities on a CORESET, a UE is configured to monitor PDCCH search spaces (e.g., common search space, UE-specific search space) for PDCCH candidates with different DCI formats and aggregation levels. Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of specific subframes of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. The secondary synchronization signal (SSS) may be within symbol 4 of specific subframes of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH), which carries the master information block (MIB), can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as the system information block (SIB)), and paging messages.

[0067] like Figure 2C As illustrated, some of the REs carry DM-RSs (indicated as R for a specific configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RSs for the physical uplink control channel (PUCCH) and DM-RSs for the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be sent in the first or first two symbols of the PUSCH. Depending on whether a short or long PUCCH is transmitted and the specific PUCCH format used, the PUCCH DM-RS can be sent in different configurations. The UE can transmit a sounding reference signal (SRS). The SRS can be sent in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the teeth of the comb. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0068] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0069] Figure 3 Figure 3 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0070] The transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-order phase-shift keying (M-PSK), and M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols are then separated into parallel streams. Each stream is then mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying the time-domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0071] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides this information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement Layer 1 functionality associated with various signal processing functions. The RX processor 356 performs spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, the RX processor 356 may combine them into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 310. These soft decisions may be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 310. The data and control signals are then provided to a controller / processor 359, which implements layer 3 and layer 2 functionality.

[0072] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0073] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0074] Channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0075] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0076] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. Memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0077] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform a combined Figure 1 Aspects of the NSSAI request component 198.

[0078] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform a combined Figure 1 The NSSAI provides various aspects of component 199.

[0079] Figure 4 is a diagram 400 illustrating an example of UE positioning based on reference signal measurements (which may also be referred to as "network-based positioning") according to various aspects of the present disclosure. UE 404 may be at time T SRS_TX UL-SRS 412 is sent and at time T PRS_RX Receive DL Positioning Reference Signal (PRS) (DL-PRS) 410. TRP 406 may be at time T SRS_RX Receive UL-SRS 412 and at time T PRS_TX 410. The UE 404 may receive the DL-PRS 410 before transmitting the UL-SRS 412, or may transmit the UL-SRS 412 before receiving the DL-PRS 410. In both cases, the positioning server (eg, location server 168) or the UE 404 may determine the UL-SRS 412 based on the || T SRS_RX – T PRS_TX | – |T SRS_TX – T PRS_RX || to determine RTT 414. Thus, multi-RTT positioning may utilize UE Rx-Tx time difference measurements (ie, |T SRS_TX – T PRS_RX |) and DL-PRS reference signal received power (RSRP) (DL-PRS-RSRP), and the measured TRP Rx-Tx time difference measurement (ie, |T SRS_RX – T PRS_TX|) and UL-SRS-RSRP. UE 404 uses assistance data received from the positioning server to measure the UE Rx-Tx time difference measurement (and / or the DL-PRS-RSRP of the received signal), and TRP 402, 406 uses assistance data received from the positioning server to measure the gNB Rx-Tx time difference measurement (and / or the UL-SRS-RSRP of the received signal). These measurements can be used at the positioning server or UE 404 to determine the RTT, which is used to estimate the position of UE 404. Other methods for determining RTT are possible, such as, for example, using DL-TDOA and / or UL-TDOA measurements.

[0080] The PRS can be defined for network-based positioning (e.g., NR positioning) to enable UEs to detect and measure more neighboring transmit and receive points (TRPs), with multiple configurations supported to enable various deployments (e.g., indoor, outdoor, sub-6, mmW, etc.). To support PRS beam operation, beam scanning can also be configured for the PRS. The UL positioning reference signal can be based on the sounding reference signal (SRS) with enhancements / adjustments for positioning purposes. In some examples, the UL-PRS can be referred to as "SRS for positioning," and a new information element (IE) can be configured for the SRS to facilitate positioning in RRC signaling.

[0081] DL PRS-RSRP can be defined as the linear average of the power contributions (in watts) of the resource elements of the antenna ports carrying the DL PRS reference signal configured for RSRP measurement, within the considered measurement frequency bandwidth. In some examples, for FR1, the reference point for DL ​​PRS-RSRP can be the UE's antenna connector. For FR2, DL PRS-RSRP can be measured based on the combined signal from the antenna elements corresponding to a given receiver branch. For both FR1 and FR2, if the UE uses receiver diversity, the reported DL PRS-RSRP value can be no lower than the corresponding DL PRS-RSRP of any of the individual receiver branches. Similarly, UL SRS-RSRP can be defined as the linear average of the power contributions (in watts) of the resource elements carrying the sounding reference signal (SRS). UL SRS-RSRP can be measured over the configured resource elements, within the considered measurement frequency bandwidth, and during the configured measurement occasions. In some examples, for FR1, the reference point for UL SRS-RSRP can be the antenna connector of the base station (e.g., gNB). For FR2, the UL SRS-RSRP may be measured based on the combined signals from the antenna elements corresponding to a given receiver branch. For FR1 and FR2, if the base station uses receiver diversity, the reported UL SRS-RSRP value may not be lower than the corresponding UL SRS-RSRP of any of the individual receiver branches.

[0082] PRS-Path RSRP (PRS-RSRPP) can be defined as the power of the linear average of the channel response at the i-th path delay of the resource element carrying the DL PRS signal configured for measurement, where the DL PRS-RSRPP for the first path delay is the power contribution corresponding to the first detected path in time. In some examples, the PRS path phase measurement can refer to the phase associated with the i-th path of the channel derived using the PRS resource.

[0083] DL-AoD positioning may utilize the measured DL-PRS-RSRP of downlink signals received at a UE 404 from multiple TRPs 402, 406. The UE 404 uses assistance data received from a positioning server to measure the DL-PRS-RSRP of the received signals, and the resulting measurements, along with the azimuth angle of departure (A-AoD), the zenith angle of departure (Z-AoD), and other configuration information, are used to position the UE 404 relative to neighboring TRPs 402, 406.

[0084] DL-TDOA positioning may utilize DL Reference Signal Time Difference (RSTD) (and / or DL-PRS-RSRP) of downlink signals received at a UE 404 from multiple TRPs 402, 406. The UE 404 uses assistance data received from a positioning server to measure the DL RSTD (and / or DL-PRS-RSRP) of the received signals, and the resulting measurements, along with other configuration information, are used to position the UE 404 relative to neighboring TRPs 402, 406.

[0085] UL-TDOA positioning may utilize the UL relative time of arrival (RTOA) (and / or UL-SRS-RSRP) of uplink signals transmitted from a UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 use assistance data received from a positioning server to measure the UL-RTOA (and / or UL-SRS-RSRP) of the received signals, and the resulting measurements, along with other configuration information, are used to estimate the position of the UE 404.

[0086] UL-AoA positioning may utilize the measured azimuth angle of arrival (A-AoA) and zenith angle of arrival (Z-AoA) of uplink signals transmitted from a UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 measure the A-AoA and Z-AoA of the received signals using assistance data received from a positioning server, and the resulting measurements, along with other configuration information, are used to estimate the position of the UE 404. For purposes of this disclosure, positioning operations in which a UE provides measurements to a base station / positioning entity / server for use in calculating the UE's position may be described as "UE-assisted," "UE-assisted positioning," and / or "UE-assisted position calculation," while positioning operations in which a UE measures and calculates its own position may be described as "UE-based," "UE-based positioning," and / or "UE-based position calculation."

[0087] Additional positioning methods may be used to estimate the position of the UE 404, such as, for example, UE-side UL-AoD and / or DL-AoA. Note that data / measurements from various techniques may be combined in various ways to increase accuracy, determine and / or enhance certainty, supplement / complete measurements, and / or replace / provide missing information.

[0088] It should be noted that the terms "positioning reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "positioning reference signal" and "PRS" may also refer to any type of reference signal that can be used for positioning, such as, but not limited to, PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, and so on, as defined in LTE and NR. Furthermore, the terms "positioning reference signal" and "PRS" may refer to either downlink or uplink positioning reference signals, unless otherwise indicated by the context. To further distinguish between the types of PRS, downlink positioning reference signals may be referred to as "DL PRS," and uplink positioning reference signals (e.g., SRS, PTRS used for positioning) may be referred to as "UL-PRS." Furthermore, for signals that can be transmitted in both the uplink and downlink (e.g., DMRS, PTRS), these signals may be prepended with "UL" or "DL" to distinguish their direction. For example, "UL-DMRS" may be distinguished from "DL-DMRS."

[0089] In addition to network-based UE positioning techniques, wireless devices (e.g., base stations / TRPs, UEs, etc.) may also be configured to include radar capabilities, which may be referred to as "radio frequency (RF) sensing," "cellular-based RF sensing," and / or simply "sensing." For example, a wireless device may transmit a radar reference signal (RRS) and measure the RRS reflected from one or more objects. Based at least in part on the measurements, the wireless device may determine or estimate the distance between the wireless device and the one or more objects. In another example, a first wireless device may also receive RRS transmitted from one or more wireless devices, where the first wireless device may determine or estimate the distance between the first wireless device and the one or more wireless devices based at least in part on the received RRS. Therefore, in some examples, RF sensing techniques may be used for UE positioning and / or for assisting UE positioning. For the purposes of this disclosure, a device capable of performing RF sensing (e.g., transmitting and / or receiving RRS for detecting objects) may be referred to as an "RF sensing node." For example, an RF sensing node may be a UE, a base station, a TRP, a device capable of transmitting RRS, and / or a device configured to perform radar functionality, etc.

[0090] A positioning frequency layer (PFL) (or "frequency layer" in some examples) can refer to a collection of one or more PRS resource sets with identical values ​​for certain parameters across one or more transmission resolutions (TRPs). Specifically, the collection of PRS resource sets can have the same subcarrier spacing and cyclic prefix (CP) type (e.g., meaning that all parameter sets supporting PDSCH also support PRS), the same point A, the same downlink PRS bandwidth value, the same starting PRB (and center frequency), and / or the same comb size. The point A parameter can take the value of the parameter ARFCN-ValueNR (where "ARFCN" stands for "Absolute Radio Frequency Channel Number") and can be an identifier / code that specifies the physical radio channel pair used for transmission and reception. In some examples, the downlink PRS bandwidth can have a granularity of four PRBs, with a minimum of 24 PRBs and a maximum of 272 PRBs. In other examples, up to four frequency layers are configured, and up to two PRS resource sets per frequency layer per TRP can be configured.

[0091] The concept of frequency layers can be similar to component carriers (CCs) and BWPs, where CCs and BWPs can be used by a base station (or a macrocell base station and a small cell base station) to transmit data channels, while frequency layers can be used by multiple (e.g., three or more) base stations to transmit PRSs. A UE can indicate the number of frequency layers it can support when communicating its positioning capabilities to the network (such as during a positioning protocol session). For example, the UE can indicate whether it can support one or four PFLs.

[0092] In some scenarios, a UE may receive multiple PRS resources from multiple TRPs via one or more PFLs, where the UE may not be able to process all of the multiple PRS resources. Therefore, the UE may apply predefined prioritization rules to prioritize the measurement of the PRS resources. Based on the predefined prioritization rules, the UE may measure a subset of the multiple PRS resources, and the UE may skip measuring another subset of the multiple PRS resources.

[0093] Figure 5Figure 500 illustrates example DL PRS resource prioritization according to various aspects of the present disclosure. A UE may be configured with multiple PRS resources in assistance data for a positioning session, where the number of PRS resources to be processed by the UE may exceed the UE's processing capabilities. In one example, the UE may assume that the DL PRS resources in the assistance data are sorted in descending order of measurement priority. For example, if the UE is configured to receive or measure DL PRS resources via multiple frequency layers (e.g., PFLs), where each PFL may include PRS resources transmitted from multiple Transitional Relay Planners (TRPs), the UE may measure the DL PRS resources based on priorities associated with the multiple frequency layers (e.g., from the first frequency layer to the last frequency layer), priorities associated with TRPs in each PFL (e.g., from the first TRP to the last TRP in the PFL), priorities associated with RPS resource sets associated with each TRP (e.g., from the first PRS resource set to the last TRP resource set in the TRP), and priorities associated with RPS resources within each PRS resource set (e.g., from the first PRS resource to the last PRS resource in the resource set).

[0094] For example, as shown in diagram 500, a UE may be configured to receive DL PRS from a first frequency layer 502 (PFL 1) and a second frequency layer 504 (PFL 2). The first frequency layer 502 may include DL PRSs transmitted from a first TRP 506 and a second TRP 508, wherein the first TRP 506 may transmit PRSs using first and second PRS resources 516 and 518 in a first PRS resource set 510 and using first and second PRS resources 520 and 522 in a second PRS resource set 512, and the second TRP 508 may transmit PRSs using first and second PRS resources 524 and 526 in a first PRS resource set 514. Similarly, the UE may also receive DL PRSs from the second frequency layer 504 via multiple TRPs, PRS resource sets, and / or PRS resources.

[0095] In one example, if the UE does not have the capability to process all configured PRS resources, the UE may be configured to receive or measure PRS received from the first frequency layer 502 before processing PRS in the second frequency layer 504. Similarly, if a third frequency layer (PFL 3) and a fourth frequency layer (PFL 4) are also present, the UE may be configured to first receive or measure PRS received from the first frequency layer 502, then PRS received from the second frequency layer 504, then PRS received from the third frequency layer, and then PRS received from the fourth frequency layer (e.g., PRS are processed / measured based on PFL 1 > PFL 2 > PFL 3 > PFL 4). If the UE does not have the capability to process / measure PRS in a frequency layer, the UE may skip measuring PRS in that frequency layer. For example, if the UE is configured to receive PRS via the first frequency layer 502 and the second frequency layer 504, but the UE is just able to process / measure PRS in the first frequency layer 502, the UE may skip PRS measurement for the second frequency layer 504.

[0096] Similarly, within a frequency layer, if the UE does not have the capability to process all PRSs in the frequency layer, the UE may prioritize its PRS measurements based on the priorities associated with the TRPs. For example, the UE may be configured to receive or measure the PRS received from the first TRP 506 before processing the PRS from the second TRP 508. Similarly, if a third TRP (TRP 3) and a fourth TRP (TRP 4) are also present, the UE may be configured to receive or measure the PRS received from the first TRP 506, then receive or measure the PRS from the second TRP 508, then receive or measure the PRS from the third TRP, and then receive or measure the PRS from the fourth TRP (e.g., PRSs are processed / measured based on TRP 1 > TRP 2 > TRP 3 > TRP 4 with frequency layers). If the UE does not have the capability to process / measure PRSs from a TRP, the UE may skip measuring the PRSs in that TRP. For example, if the UE is configured to receive PRS through the first TRP 506 and the second TRP 508 via the first frequency layer 502, but the UE is just able to process / measure the PRS in the first TRP 506, the UE may skip PRS measurement for the second TRP 508.

[0097] Furthermore, within a TRP, if the UE does not have the capability to process all PRSs in that TRP, the UE may prioritize its PRS measurements based on the priorities associated with the PRS resource sets. For example, the UE may be configured to receive or measure PRSs received from the first PRS resource set 510 before processing PRSs from the second PRS resource set 512. Similarly, if a third PRS resource set (PRS resource set 3) and a fourth PRS resource set (PRS resource set 4) are also present, the UE may be configured to first receive or measure PRSs received from the first PRS resource set 510, then PRSs received from the second PRS resource set 512, then PRSs received from the third PRS resource set, and finally PRSs received from the fourth PRS resource set (e.g., PRSs are processed / measured based on the TRP order of PRS resource set 1 > PRS resource set 2 > PRS data set 3 > PRS information set 4). If the UE does not have the capability to process / measure PRSs in a PRS resource set, the UE may skip measuring PRSs in that PRS resource set. For example, if the UE is configured to receive PRS from the first TRP 506 via the first PRS resource set 510 and the second PRS resource set 512, but the UE is just able to process / measure the PRS in the first PRS resource set 510, the UE may skip PRS measurement for the second PRS resource set 512.

[0098] Finally, within a PRS resource set, if the UE does not have the capability to process all PRSs in that PRS resource set, the UE may prioritize its PRS measurements based on the priority associated with the PRS resources. For example, the UE may be configured to receive or measure the PRS received from the first PRS resource 516 before processing the PRS from the second PRS resource 518. Similarly, if a third PRS resource (PRS resource 3) and a fourth PRS resource (PRS resource 4) are also present, the UE may be configured to first receive or measure the PRS received from the first PRS resource 516, then the PRS received from the second PRS resource 518, then the PRS received from the third PRS resource, and finally the PRS received from the fourth PRS resource (e.g., PRSs are processed / measured based on the order PRS resource 1 > PRS resource 2 > PRS resource 3 > PRS resource 4 with the PRS resource set). If the UE does not have the capability to process / measure the PRS in a PRS resource, the UE may skip measuring the PRS in that PRS resource. For example, if the UE is configured to receive PRS via the first PRS resource 516 and the second PRS resource 518 in the first PRS resource set 510 , but the UE is just capable of processing / measuring the PRS in the first PRS resource 516 , the UE may skip PRS measurement for the second PRS resource 518 .

[0099] Thus, if the UE is configured with multiple PRS resources via multiple frequency layers, multiple TRPs, multiple PRS resource sets, and / or multiple PRS resources, the UE may prioritize the frequency layers (e.g., up to four frequency layers), prioritize the TRPs per frequency layer (e.g., up to sixty-four (64) TRPs per frequency layer), prioritize the PRS resource sets per TRP (e.g., up to two resource sets per TRP), and / or prioritize the PRS resources per PRS resource set (e.g., up to sixty-four (64) PRS resources per PRS resource set). In other words, within a positioning frequency layer, the DL PRS resources may be prioritized in descending order of priority for measurement by the UE, with the reference indicated by nr-DL-PRS-ReferenceInfo as the highest priority for measurement, assuming the following priorities: (1) prioritize up to 64 dl-PRS-IDs per frequency layer; and (2) prioritize up to two DL PRS resource sets per dl-PRS-ID per frequency layer.

[0100] The network can be configured to create multiple unique logical and / or virtualized networks on a common multi-domain infrastructure based on network slicing. Network slicing allows network operators to provide customized networks. For example, there may be different specifications regarding functionality (e.g., priority, billing, policy control, security, and / or mobility), differences in performance specifications (e.g., latency, mobility, availability, reliability, and / or data rate), and / or to serve specific users (e.g., Multimedia Priority Service (MPS) users, public safety users, corporate customers, and / or roamers). Network slicing can provide the functionality of a complete network, including radio access network functions, core network functions (e.g., potentially from different vendors), and / or Internet Protocol (IP) Multimedia Subsystem (IMS) functions. A network can support one or several network slices.

[0101] Network slicing can be considered a key feature of 5G NR networks and beyond (e.g., future-generation networks such as 6G). In some examples, network slices can be considered logical end-to-end networks that can be created dynamically. A UE can access multiple slices through the same network entity (e.g., base station, gNB, etc.). Each network slice can be configured to serve a specific service type using an agreed-upon service level agreement (SLA).

[0102] A network slice may be defined within a public land mobile network (PLMN) and include a core (e.g., a 5G core) and a radio access network (RAN) (e.g., a 5G RAN) control plane network and a user plane network. In some implementations, identification of a network slice may be performed via a single network slice selection assistance information (S-NSSAI), where the network slice selection assistance information (NSSAI) may refer to a set of S-NSSAIs. Some networks may allow only a limited number of S-NSSAIs (e.g., up to eight (8) S-NSSAIs) to be included in the NSSAI in signaling messages between the UE and the network. In other words, a single UE may be served by at most a limited number of network slices (e.g., eight network slices) at a time. In some examples, the UE may signal the S-NSSAI to the network to assist the network in selecting a particular network slice instance.

[0103] For the purposes of this disclosure, a network function may refer to a processing function that is specifically adopted or defined (e.g., by 3GPP) within a network, with defined functional behavior and a specific (e.g., by 3GPP) defined interface. A network function may be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, and / or as a virtualized function instantiated on an appropriate platform (e.g., on a cloud infrastructure). A network slice may refer to a logical network that provides specific network capabilities and characteristics. A network slice instance may refer to a collection of network function instances and designated resources (e.g., compute, storage, and networking resources) that form a deployed network slice.

[0104] In some examples, network slices can be categorized as hard slices and soft slices. Under hard slicing, network slices (also referred to as "hard sliced ​​network slices" or "hard network slices") can be designated as completely isolated from each other, while under soft slicing, network slices (also referred to as "soft sliced ​​network slices" or "soft network slices") can share certain network resources.

[0105] In terms of network slice identity management, the S-NSSAI can serve as an identifier for a network slice across the core network (e.g., 5GC), the RAN (e.g., 5G-RAN), and at least one UE. The S-NSSAI can be associated with a PLMN (e.g., PLMN ID) and have a network-specific or standard value. Therefore, a UE can use the S-NSSAI to access the network in the PLMN associated with the S-NSSAI. In some implementations, the S-NSSAI can be configured to include a slice / service type (SST) and / or a slice differentiator (SD). The SST can indicate the expected network slice behavior in terms of features and services. The SD can be (optional) information that supplements the SST to distinguish between multiple network slices of the same SST. In some examples, the SST (or SST ID) can be configured to be mandatory and have a specific length (e.g., 8 bits). In other words, including the SST (or SST ID) can be mandatory for the S-NSSAI. On the other hand, since the SD is used to distinguish network slices with the same SST, including the SD may not be mandatory for the S-NSSAI (e.g., may be optional). In some examples, the SD may have a total length of 24 bits.

[0106] In some examples, S-NSSAI can be categorized into standardized S-NSSAI and non-standard S-NSSAI. Standardized S-NSSAI may include only SST without SD, while non-standard S-NSSAI may be defined as only SST (non-standard) or SST+SD.

[0107] Some values ​​of the SST may be standardized and associated with specific slices / service types and / or characteristics, where these standardized values ​​of the SST may be used to address different use cases of the network. For example, standardized values ​​of the SST may address the three main use cases of 5G networks (e.g., enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC)). As an example, if the length of the SST is 8 bits, the SST may provide up to 256 SST values ​​(e.g., 2^8=256), where certain SST values ​​(e.g., value 0 to value 127) may be reserved for standardized SST. Non-standardized values ​​(e.g., value 128 to value 255) may also be used / reserved for SST. In some examples, non-standardized values ​​may allow network operators to introduce network slices that support their own specific service specifications.

[0108] Figure 6Figure 600 illustrates an example format of an S-NSSAI according to various aspects of the present disclosure. The S-NSSAI 602 may include both an SST field 604 and an SD field 606 (in which case the total length of the S-NSSAI 602 may be 32 bits), or the S-NSSAI 602 may include only the SST field 604 (in which case the total length of the S-NSSAI 602 may be only 8 bits). The SST field 604 may indicate the expected network slice behavior in terms of features and services, and the SD field 606 may provide optional information supplementing the slice / service type to distinguish between multiple network slices of the same slice / service type. The SST field 604 may have standardized and non-standardized values. For example, values ​​0 to 127 may belong to the standardized SST range, and values ​​128 to 255 may belong to the operator-specific range. The SD field 606 may have a reserved value, "No SD value associated with SST," defined as hexadecimal FFFFFF. In certain protocols, the SD field may not be included to indicate that no SD value is associated with the SST.

[0109] Table 2 below provides examples of standardized SST values. Standardized SST values ​​can provide a way to establish global interoperability of slices so that PLMNs can more efficiently support roaming use cases for the most commonly used slices / service types.

[0110]

[0111] Table 2 - Examples of Normalized SST Values

[0112] In some implementations, support for all standardized SST values ​​may not be specified in the PLMN. The services indicated for each SST value in Table 2 may also be supported by other SSTs. In some examples, a mapping of network slice types (NEST) defined by the Groupe Mobile Communications Association (GSMA) to standardized SST values ​​may also be defined in the specification / standard.

[0113] Table 3 below provides examples of different types of NSSAI.

[0114]

[0115] Table 3 — Examples of different types of NSSAI.

[0116] Figure 7A FIG700 is a diagram illustrating an example network slice selection in a 4G LTE network according to various aspects of the present disclosure. In a 4G network system / architecture, it may be difficult (eg, almost impossible) to install a new service for a UE in the network.

[0117] Figure 7BFigure 700B illustrates an example network slice selection in a 5G NR network according to various aspects of the present disclosure. In 5G networks, slice selection policies can be dynamically configured via the UE Routing Selection Policy (URSP), whereas slice selection policies may be predefined and cannot be dynamically changed in 4G networks. The URSP feature allows 5G network operators to easily configure new services for UEs. Along with the concepts of network slices and features in the RAN and core networks, the URSP may refer to or provide a means for managing network slice information for UEs. The URSP may be a network slice feature implemented by a policy control function (PCF) that notifies the UE of network slice status via the AMF. The URSP may contain operating system identifiers (OSIds), application identifiers (AppIds), and / or Internet Protocol (IP) descriptors to define applications, as well as S-NSSAI, data network names (DNNs), and session and service continuity (SSC) mode information for application and network slice mapping.

[0118] Figure 8 800 is a diagram illustrating an example of managing and identifying network slices through URSP and S-NSSAI according to various aspects of the present disclosure. In some scenarios, the UE may already know some of the standardized S-NSSAIs defined in the specifications (e.g., signaled to the UE, predefined at the UE, etc.), and the network operator may also introduce some of the non-standardized S-NSSAIs to achieve any UE-specific goals such as latency, throughput and / or power specifications. In one example, the standardized S-NSSAI may be defined in the specifications, while the non-standardized S-NSSAI may be delivered / indicated to the UE via RRC / NAS signaling. In some examples, the UE may be specified / configured to provide a list of suitable or expected S-NSSAI values ​​as part of the registration process.

[0119] If combined Figure 4As described, various types of UE positioning mechanisms may be deployed by the network for performing UE positioning, some of which may have unique requirements from the network and / or some services may require / specify very high positioning accuracy. For example, services that specify high positioning accuracy and low latency may include automated guided vehicle (AGV) tracking for navigation and collision avoidance, and also certain industrial automation use cases. In addition, some positioning services are becoming very complex to implement and manage, such as those related to: (1) DL and UL TDOA, RTT, DL-AOD, and UL-AoA; (2) positioning in RRC inactive mode; (3) Sidelink (SL) Mode 1, SL Mode 2, and SL+Uu; (4) low power and high accuracy modes, frequency hopping modes for reduced capability (Redcap) UEs, carrier phase methods; (5) ML-enabled positioning using site-specific ML models, ML-enhanced classical algorithms; (6) positioning for ambient Internet of Things (IoT) devices (e.g., passive devices with backscatter or minimal energy storage); (7) radio frequency (RF) sensing for multiple home, industrial, and enterprise use cases; and / or (8) NR+Wi-Fi, NR+GNSS fusion, etc. In some examples, these services can be collectively referred to as "non-data services."

[0120] In some examples, performing high-accuracy positioning (e.g., by a UE, a network entity, and / or a location server, etc.) may designate dedicated physical layer resources, such as high bandwidth (BW), and intensive computational engines at radio units (RUs) and / or distributed units (DUs), for processing positioning-related signals (e.g., positioning reference signals (PRS), sounding reference signals (SRS), etc.). In other examples, performing high-accuracy positioning may also designate dedicated hardware (HW) and software (SW) for controlling and managing all transmit receive points (TRPs) and UEs (and Wi-Fi access points (APs)) used for various positioning mechanisms. In another example, performing high-accuracy positioning may also designate dedicated HW and SW in a core network (CN) (e.g., a location server, LMF, etc.) for implementing the final position calculation and handling requests from external servers.

[0121] Various aspects presented herein may improve the accuracy, latency, and / or reliability of UE positioning / sensing by enabling dedicated network slices to be defined and configured for UE positioning / sensing (e.g., RF sensing). In one aspect of the present disclosure, positioning / sensing specific network slices and slice differentiators (SDs) may be defined and configured for positioning / sensing entities (e.g., UE, base station / TRP, LMF, etc.). For example, one or more standard SST values ​​may be introduced / configured for positioning / sensing related services. If more than one SST value is introduced / configured, the SST values ​​may be (e.g., implicitly) mapped to one or more positioning / sensing patterns, where (e.g., as combined Figure 4 One or more positioning modes (described above) may be associated with a high-accuracy positioning / sensing slice, a low-latency positioning / sensing slice, a low-power positioning / sensing slice, a positioning / sensing slice implemented by ML, and / or a Uu / SL hybrid positioning slice, etc. Positioning / sensing specific network slices and SDs may also be configured to support non-standardized SST values ​​for distinguishing positioning / sensing services and / or support SD signaling for various positioning / sensing modes.

[0122] In another aspect of the present disclosure, the UE may indicate positioning or sensing-specific slice information to the AMF during the registration process, and the AMF may forward this information to a location server (e.g., LMF) when initiating a positioning / sensing session. In one implementation, the UE may indicate the positioning-specific slice information directly to the location server (e.g., via the LTE Positioning Protocol (LPP)) when initiating a positioning session. In another implementation, if one or more S-NSSAIs or SDs are indicated to the location server (by a network entity), the location server may indicate one S-NSSAI or SD to the UE. The one S-NSSAI or SD may also be specified to be provided to the AMF directly or by the UE. In another implementation, if the UE is in RRC inactive mode or RRC idle mode, the UE may provide the positioning NSSAI (e.g., an appropriate or desired NSSAI) for initiating the positioning / sensing session in an RRC Connection Request message or an RRC Resume Request message.

[0123] In another aspect of the present disclosure, after a UE is registered with the network and in RRC connected mode (e.g., connected to a base station or network entity), the UE may provide an accepted S-NSSAI value or a list of S-NSSAI values ​​to a location server, such as via a Registration Accept message. Alternatively or additionally, the UE may provide this information as part of a Positioning Session Request message. In one example, the location server may recommend an S-NSSAI value to the RAN (e.g., to a TRP involved in a positioning / sensing session) based on (e.g., from) the list of S-NSSAI values ​​provided by the UE. In some scenarios, the location server may also recommend an S-NSSAI value outside the list of S-NSSAI values ​​provided by the UE. In this case, the UE may be instructed to re-register / update the S-NSSAI value with the network. In another example, the location server may include the capability to provide different S-NSSAI values ​​for different positioning modes and / or the location server may include the capability to provide different S-NSSAI values ​​for different positioning links (e.g., Uu link, SL link, etc.).

[0124] In another aspect of the present disclosure, for a UE in RRC inactive mode and / or RRC idle mode, the location server may provide the UE with a list of suitable or expected S-NSSAIs in the assistance data. In some examples, how the S-NSSAI list in the assistance data is used may depend on the specific implementation of the UE. In some scenarios, the UE may be configured with an S-NSSAI associated with radio resource management (RRM) (e.g., data services, certain non-positioning / sensing services, etc.) and an S-NSSAI associated with positioning / sensing, and the UE may be specified to prioritize the RRM S-NSSAI over the positioning / sensing S-NSSAI, or vice versa.

[0125] Based on the network slicing described herein, enterprises with multiple applications can allocate different latency or bandwidth capabilities to specific systems with greater capacity specifications, such as smart meters enabled by the IoT. A single network can be used to provide a variety of services based on specifications / user needs and various use cases. Network operators can also allocate the correct amount of specific resources based on network slices. Therefore, the various aspects presented herein can provide more effective and efficient resource utilization. For example, one network slice can be designed / configured to deliver low latency and low data rates, while another network slice can be designed / configured to deliver high throughput, etc. The various aspects presented herein can also enable network operators to reduce operating expenses (OPEX) and capital expenditures (CAPEX). The various aspects presented herein also significantly improve the operational efficiency of network service delivery and shorten time to market. The various aspects presented herein can also overcome the shortcomings associated with Differentiated Services (DiffServ), one of the most popular QoS solutions. DiffServ can refer to a computer networking architecture that specifies mechanisms for classifying and managing network traffic, or to a protocol for classifying and controlling network traffic to prioritize certain types of traffic.

[0126] Figure 9 9 is a communication flow 900 illustrating an example of a network entity configuring a network slice associated with positioning / sensing for a UE according to various aspects of the present disclosure. The numbers associated with the communication flow 900 do not specify a particular time order and are merely used as a reference for the communication flow 900.

[0127] At 920, the UE 920 may send an indication 906 indicating a list of NSSAIs to the network entity 904, where each NSSAI in the list may be associated with at least one of a positioning mode, a sensing mode, a positioning specific service type, a sensing specific service type, etc. In one example, the UE 902 may send the indication 906 via a positioning session request message during RRC connected mode. For the purposes of this disclosure, positioning mode, sensing mode, positioning specific service type, and / or sensing specific service type may include at least positioning / sensing modes associated with the following: (1) DL and UL TDOA, RTT, DL-AOD, and UL-AoA; (2) positioning in RRC inactive mode; (3) SL Mode 1, SL Mode 2, and SL+Uu; (4) low power and high accuracy mode, frequency hopping mode for reduced capability UEs, carrier phase method; (5) ML-enabled positioning using site-specific ML models, ML-enhanced classical algorithms; (6) positioning for ambient IoT devices (e.g., passive devices with backscatter or minimal energy storage); (7) RF sensing for multiple home, industrial, and enterprise use cases, (8) NR+Wi-Fi, NR+GNSS fusion, or a combination thereof. In some examples, these services may be collectively referred to as "non-data services."

[0128] At 922, based at least in part on the indication 906, the UE 902 may communicate with the network entity based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type. In one example, the UE 902 may also communicate with the network entity 904 based on an NSSAI that is not in the NSSAI list. For example, if the network entity 904 determines that the NSSAI list provided by the UE 902 is not applicable to the UE 902 (or the network entity 904 cannot provide the NSSAI list provided by the UE 902), the network entity 904 may provide the UE 902 with an NSSAI that is not in the NSSAI list provided by the UE 902.

[0129] In one aspect of the present disclosure, as shown at 924, NSSAI (or NSSAI list) may include high-accuracy NSSAI, low-latency NSSAI, low-power NSSAI, SL positioning NSSAI, hybrid UE-UTRAN (Uu)-SL positioning NSSAI and / or positioning NSSAI implemented by machine learning (ML), etc. For example, high-accuracy NSSAI may be associated with a positioning / sensing mechanism / mode that specifies the accuracy / reliability of positioning / sensing to meet a defined accuracy / reliability threshold (e.g., a high accuracy / reliability threshold); low-latency NSSAI may be associated with a positioning / sensing mechanism / mode that specifies the latency of positioning / sensing to meet a latency / time threshold (e.g., a low latency threshold); low-power NSSAI may be associated with a positioning / sensing mechanism / mode that specifies the power consumption of positioning / sensing to meet a power threshold (e.g., a low power threshold); SL ​​positioning NSSAI / Uu-SL positioning NSSAI may be associated with a positioning / sensing mechanism / mode that is at least partially based on SL communication; and positioning NSSAI implemented by ML may be associated with a positioning / sensing mechanism / mode that specifies the use of at least one ML model for positioning / sensing, etc.

[0130] In another aspect of the present disclosure, Figure 6 As described, each NSSAI in the NSSAI list may include at least one SST value or at least one SD value, and different SST values ​​or different SD values ​​may correspond to different positioning modes or services, or to different sensing modes or services. For example, a first SST value may correspond to a first positioning mode (e.g., TDoA-based positioning), a second SST value may correspond to a first sensing mode (e.g., monostatic sensing), a third SST value may correspond to a second positioning mode (e.g., AoA-based positioning), and a fourth SST value may correspond to a second sensing mode (e.g., bistatic sensing). Furthermore, SD values ​​may be used to define different services for the same positioning / sensing mode. For example, a first SD value associated with a first SST value (e.g., TDoA positioning) may indicate high-accuracy positioning, while a second SD value associated with the first SST value may indicate lower-accuracy positioning.

[0131] In another aspect of the present disclosure, as shown at 926, based on the indication 906 including the NSSAI list from the UE 902, the network entity 904 may send an indication 908 to the UE 902, the indication indicating at least one of the positioning mode, the sensing mode, the positioning-specific service type, or the sensing-specific service type. For example, based on the NSSAI list, the network entity 904 may select an appropriate NSSAI from the NSSAI list and indicate the selected NSSAI to the UE 902. As an example, at 920, the UE 902 may indicate an NSSAI list that includes NSSAIs for a first positioning mode (e.g., TDoA-based positioning), a second positioning mode (e.g., AoA / AoD-based positioning), a first sensing mode (e.g., monostatic sensing), and a second sensing mode (e.g., bistatic sensing). In response, at 926, the network entity 904 may provide the UE 902 with the NSSAI for the second positioning mode. In one example, the network entity 904 may determine which NSSAI to provide / select based on the availability of NSSAI / resources at the network entity 904, based on the accuracy / reliability specified for positioning / sensing, based on the capabilities of the UE 902, and / or based on certain predefined conditions / factors. In some examples, the network entity 904 may be a LMF, and in order to send an indication 906 to the LMF for the UE 902, the UE 902 may send the indication 906 to the LMF directly or via the AMF. In response, the LMF may also send an indication 908 to the UE directly or via the AMF.

[0132] In another aspect of the present disclosure, as shown at 928, the UE 902 may send an indication 910 during RRC inactive mode and / or RRC idle mode that indicates a suitable or desired NSSAI based on the NSSAI list to initiate a positioning session or a sensing session. In some examples, the UE 902 may send the indication 910 to the network entity 904 via an RRC connection request message or an RRC resume request message.

[0133] In another aspect of the present disclosure, as shown at 930, the network entity 904 may send assistance data 912 to the UE 902, where the assistance data 912 may include a list of suitable or desired NSSAIs. In response, the UE 902 may (e.g., at 920) select an NSSAI list based on the list of suitable or desired NSSAIs from the network entity 904. In some examples, the network entity 904 may send the list of suitable or desired NSSAIs to the UE 902 while the UE is in RRC inactive mode or RRC idle mode. For example, at 930, the network entity 904 may provide an NSSAI list that includes NSSAIs for a first positioning mode (e.g., TDoA-based positioning), a second positioning mode (e.g., AoA / AoD-based positioning), a first sensing mode (e.g., monostatic sensing), a second sensing mode (e.g., bistatic sensing), and the like. In response, the UE 902 may select an NSSAI for the first positioning mode and the first sensing mode and indicate / include the selected NSSAI in the indication 906 at 920 .

[0134] In another aspect of the present disclosure, as shown at 932, in some scenarios, the UE 902 may be configured with NSSAI associated with positioning / sensing and / or NSSAI associated with radio resource management (RRM) (e.g., for communication, non-positioning / sensing operations, etc.). In such scenarios, if the UE 902 is unable (e.g., lacks resources) to utilize all NSSAIs, the UE 902 may be configured to prioritize these NSSAIs, such as based on predefined rules or based on its resources. For example, the UE 902 may be specified to prioritize positioning / sensing-related NSSAI over RRM-related NSSAI, or to prioritize RRM-related NSSAI over positioning / sensing-related NSSAI. In some examples, the UE 902 may also be specified to prioritize different priority positioning / sensing-related NSSAIs. For example, if the UE 902 receives or is configured with two NSSAIs associated with different positioning / sensing modes, the UE 902 may be specified to prioritize one of the positioning / sensing modes, such as by selecting the positioning / sensing mode with the highest accuracy / reliability.

[0135] Figure 10 1000 is a flow chart of a method for wireless communication. The method may be performed by a UE (e.g., UE 104, 404, 902; device 1204). The method may enable the UE to indicate NSSAI associated with positioning and / or sensing to a network entity and communicate with the network entity based on the indicated NSSAI.

[0136] At 1004, the UE may send a first indication of a NSSAI list to a network entity, wherein each NSSAI in the NSSAI list is associated with at least one of a positioning mode, a sensing mode, a positioning specific service type, or a sensing specific service type, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 920 of FIG, UE 902 may send an indication 906 to network entity 904, wherein the indication 906 may include a list of NSSAIs associated with one or more sensing or positioning modes / service types. The sending of the first indication may be performed by, for example, Figure 12 The NSSAI request component 198, the application processor 1206, the cellular baseband processor 1224 and / or the transceiver 1222 of the device 1204 are executed.

[0137] In an example, the NSSAI may include at least one of the following: high-accuracy NSSAI, low-latency NSSAI, low-power NSSAI, SL positioning NSSAI, hybrid Uu-SL positioning NSSAI, or positioning NSSAI implemented by ML.

[0138] In another example, each NSSAI in the NSSAI list may include at least one SST value or at least one SD value, and different SST values ​​or different SD values ​​correspond to different positioning modes or services, or correspond to different sensing modes or services.

[0139] In another example, the first indication may be sent via a positioning session request message during RRC connected mode.

[0140] At 1012, the UE may communicate with the network entity based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 922, UE 902 may communicate with network entity 904 based on at least one of the positioning or sensing modes / service types. Communication with the network entity may be performed by, for example, Figure 12 The NSSAI request component 198, the application processor 1206, the cellular baseband processor 1224 and / or the transceiver 1222 of the device 1204 are executed.

[0141] In one example, the UE may communicate with the network entity based on an NSSAI that is not in the NSSAI list.

[0142] In another example, at 1008, the UE may receive a second indication of at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type from the network entity before communicating with the network entity, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 926 of FIG. , UE 902 may receive an indication 908 from network entity 904 prior to communicating with network entity 904, the indication indicating at least one of the positioning or sensing modes / service types. Receipt of the second indication may be performed by, for example Figure 12 The NSSAI request component 198, the application processor 1206, the cellular baseband processor 1224, and / or the transceiver 1222 of the device 1204 in the embodiment of the present invention are executed. In some specific implementations, the network entity may correspond to a LMF, and the UE may send the first indication directly to the LMF or send the first indication to the LMF via an AMF. Then, the UE may receive the second indication directly from the LMF or receive the second indication from the LMF via the AMF.

[0143] In another example, at 1006, the UE may send a second indication via an RRC connection request message or an RRC resume request message during RRC inactive mode or RRC idle mode, the second indication indicating a suitable or desired NSSAI based on the NSSAI list to initiate a positioning session, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 928 of FIG, UE 902 may send an indication 910 to the network entity 904 during RRC inactive / idle mode, the indication indicating the appropriate or desired NSSAI to initiate the positioning / sensing session. The sending of the second indication may be performed by, for example Figure 12 The NSSAI request component 198, the application processor 1206, the cellular baseband processor 1224 and / or the transceiver 1222 of the device 1204 are executed.

[0144] In another example, at 1002, the UE may receive a list of suitable or desired NSSAIs from a network entity via assistance data (AD), and select the NSSAI list based on the list of suitable or desired NSSAIs, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 930 of FIG, UE 902 may receive a list of suitable or desired NSSAIs from network entity 904 via assistance data 912, and UE 902 may select the NSSAI list based on the list of suitable or desired NSSAIs. Receipt of the list of suitable or desired NSSAIs and / or selection of the NSSAI list may be performed by, for example Figure 12 The NSSAI request component 198 of the apparatus 1204, the application processor 1206, the cellular baseband processor 1224, and / or the transceiver 1222 may be executed. In some implementations, the list of suitable or desired NSSAIs may be received during RRC inactive mode or RRC idle mode.

[0145] In another example, at 1010, the UE may perform prioritization between the NSSAI list and a second NSSAI list, wherein the second NSSAI list is associated with RRM, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 932, UE 902 performs prioritization between the NSSAI associated with positioning / sensing and the NSSAI associated with RRM. The prioritization between the NSSAI list and the second NSSAI list may be performed by, for example Figure 12 The NSSAI request component 198, the application processor 1206, the cellular baseband processor 1224 and / or the transceiver 1222 of the device 1204 are executed.

[0146] Figure 11 1100 is a flow chart of a method for wireless communication. The method may be performed by a UE (e.g., UE 104, 404, 902; device 1204). The method may enable the UE to indicate NSSAI associated with positioning and / or sensing to a network entity and communicate with the network entity based on the indicated NSSAI.

[0147] At 1104, the UE may send a first indication of a NSSAI list to a network entity, wherein each NSSAI in the NSSAI list is associated with at least one of a positioning mode, a sensing mode, a positioning specific service type, or a sensing specific service type, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 920 of FIG, UE 902 may send an indication 906 to network entity 904, wherein the indication 906 may include a list of NSSAIs associated with one or more sensing or positioning modes / service types. The sending of the first indication may be performed by, for example, Figure 12 The NSSAI request component 198, the application processor 1206, the cellular baseband processor 1224 and / or the transceiver 1222 of the device 1204 are executed.

[0148] In an example, the NSSAI may include at least one of the following: high-accuracy NSSAI, low-latency NSSAI, low-power NSSAI, SL positioning NSSAI, hybrid Uu-SL positioning NSSAI, or positioning NSSAI implemented by ML.

[0149] In another example, each NSSAI in the NSSAI list may include at least one SST value or at least one SD value, and different SST values ​​or different SD values ​​correspond to different positioning modes or services, or correspond to different sensing modes or services.

[0150] In another example, the first indication may be sent via a positioning session request message during RRC connected mode.

[0151] At 1112, the UE may communicate with the network entity based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 922, UE 902 may communicate with network entity 904 based on at least one of the positioning or sensing modes / service types. Communication with the network entity may be performed by, for example, Figure 12 The NSSAI request component 198, the application processor 1206, the cellular baseband processor 1224 and / or the transceiver 1222 of the device 1204 are executed.

[0152] In one example, the UE may communicate with the network entity based on an NSSAI that is not in the NSSAI list.

[0153] In another example, the UE may receive a second indication of at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type from the network entity before communicating with the network entity, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 926 of FIG. , UE 902 may receive an indication 908 from network entity 904 prior to communicating with network entity 904, the indication indicating at least one of the positioning or sensing modes / service types. Receipt of the second indication may be performed by, for example Figure 12 The NSSAI request component 198, the application processor 1206, the cellular baseband processor 1224, and / or the transceiver 1222 of the device 1204 in the embodiment of the present invention are executed. In some specific implementations, the network entity may correspond to a LMF, and the UE may send the first indication directly to the LMF or send the first indication to the LMF via an AMF. Then, the UE may receive the second indication directly from the LMF or receive the second indication from the LMF via the AMF.

[0154] In another example, the UE may send a second indication via an RRC connection request message or an RRC resume request message during RRC inactive mode or RRC idle mode, the second indication indicating a suitable or desired NSSAI based on the NSSAI list to initiate a positioning session, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 928 of FIG. , UE 902 may send an indication 910 to network entity 904 during RRC inactive / idle mode, the indication indicating a suitable or desired NSSAI to initiate a positioning / sensing session. The sending of the second indication may be performed by, for example, Figure 12 The NSSAI request component 198, the application processor 1206, the cellular baseband processor 1224 and / or the transceiver 1222 of the device 1204 are executed.

[0155] In another example, the UE may receive a list of suitable or desired NSSAIs from a network entity via assistance data (AD) and select the NSSAI list based on the list of suitable or desired NSSAIs, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 930 of FIG, UE 902 may receive a list of suitable or desired NSSAIs from network entity 904 via assistance data 912, and UE 902 may select the NSSAI list based on the list of suitable or desired NSSAIs. Receipt of the list of suitable or desired NSSAIs and / or selection of the NSSAI list may be performed by, for example Figure 12 The NSSAI request component 198 of the apparatus 1204, the application processor 1206, the cellular baseband processor 1224, and / or the transceiver 1222 may be executed. In some implementations, the list of suitable or desired NSSAIs may be received during RRC inactive mode or RRC idle mode.

[0156] In another example, the UE may perform prioritization between the NSSAI list and a second NSSAI list, wherein the second NSSAI list is associated with RRM, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 932, UE902 performs prioritization between the NSSAI associated with positioning / sensing and the NSSAI associated with RRM. The prioritization between the NSSAI list and the second NSSAI list may be performed by, for example Figure 12 The NSSAI request component 198, the application processor 1206, the cellular baseband processor 1224 and / or the transceiver 1222 of the device 1204 are executed.

[0157] Figure 1212 is a diagram illustrating an example of a hardware implementation for an apparatus 1204. The apparatus 1204 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1204 may include a cellular baseband processor 1224 (also referred to as a modem) coupled to one or more transceivers 1222 (e.g., a cellular RF transceiver). The cellular baseband processor 1224 may include on-chip memory 1224′. In some aspects, the apparatus 1204 may further include one or more subscriber identity module (SIM) cards 1220 and an application processor 1206 coupled to a secure digital (SD) card 1208 and a screen 1210. The application processor 1206 may include on-chip memory 1206′. In some aspects, the device 1204 may further include a Bluetooth module 1212, a WLAN module 1214, an SPS module 1216 (e.g., a GNSS module), an ultra-wideband (UWB) module 1236, one or more sensor modules 1218 (e.g., a barometric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1226, a power supply 1230, and / or a camera 1232. The Bluetooth module 1212, the WLAN module 1214, the UWB module 1236, and the SPS module 1216 may include an on-chip transceiver (TRX) (or, in some cases, only a receiver (RX)). The Bluetooth module 1212, WLAN module 1214, UWB module 1236, and SPS module 1216 may include their own dedicated antennas and / or utilize antenna 1280 for communication. The cellular baseband processor 1224 communicates with the UE 104 and / or with the RU associated with the network entity 1202 via one or more antennas 1280 through the transceiver 1222. The cellular baseband processor 1224 and the application processor 1206 may each include computer-readable media / memory 1224', 1206', respectively. The additional memory module 1226 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1224', 1206', 1226 may be non-transitory. The cellular baseband processor 1224 and the application processor 1206 are each responsible for general processing, including executing software stored on the computer-readable media / memory. The software, when executed by the cellular baseband processor 1224 / application processor 1206, causes the cellular baseband processor 1224 / application processor 1206 to perform the various functions described above. The computer-readable medium / memory may also be used to store data that is manipulated by the cellular baseband processor 1224 / application processor 1206 when executing the software.The cellular baseband processor 1224 / application processor 1206 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1204 may be a processor chip (modem and / or applications) and include only the cellular baseband processor 1224 and / or the application processor 1206, and in another configuration, the device 1204 may be the entire UE (e.g., see. Figure 3 UE 350 ) and includes additional modules of device 1204.

[0158] As discussed above, the NSSAI requesting component 198 can be configured to send a first indication of a list of NSSAIs to a network entity, wherein each NSSAI in the list is associated with at least one of a positioning mode, a sensing mode, a positioning-specific service type, or a sensing-specific service type. The NSSAI requesting component 198 can also be configured to communicate with the network entity based on at least one of the positioning mode, the sensing mode, the positioning-specific service type, or the sensing-specific service type. The NSSAI requesting component 198 can be within the cellular baseband processor 1224, the application processor 1206, or both the cellular baseband processor 1224 and the application processor 1206. The NSSAI requesting component 198 can be one or more hardware components specifically configured to perform the recited processes / algorithms, implemented by one or more processors configured to perform the recited processes / algorithms, stored on a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the apparatus 1204 can include multiple components configured for various functions. In one configuration, the apparatus 1204 (and specifically, the cellular baseband processor 1224 and / or the application processor 1206) may include means for sending a first indication of a NSSAI list to a network entity, wherein each NSSAI in the NSSAI list is associated with at least one of a positioning mode, a sensing mode, a positioning specific service type, or a sensing specific service type. The apparatus 1204 may further include means for communicating with the network entity based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type.

[0159] In one configuration, the NSSAI may include at least one of: high-accuracy NSSAI, low-latency NSSAI, low-power NSSAI, SL positioning NSSAI, hybrid Uu-SL positioning NSSAI, or ML-enabled positioning NSSAI.

[0160] In another configuration, each NSSAI in the NSSAI list may include at least one SST value or at least one SD value, and wherein different SST values ​​or different SD values ​​correspond to different positioning modes or services, or correspond to different sensing modes or services.

[0161] In another configuration, the first indication may be sent via a positioning session request message during RRC connected mode.

[0162] In another configuration, the device 1204 may communicate with the network entity based on an NSSAI that is not in the NSSAI list.

[0163] In another configuration, the apparatus 1204 may further include: means for receiving, before communicating with the network entity, a second indication of at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type from the network entity. In some implementations, the network entity may correspond to a LMF, and the apparatus 1204 may further include: means for sending the first indication directly to the LMF; or means for sending the first indication to the LMF via an AMF. The apparatus 1204 may further include: means for receiving the second indication directly from the LMF; or means for receiving the second indication from the LMF via the AMF.

[0164] In another configuration, the apparatus 1204 may further include means for sending a second indication via an RRC connection request message or an RRC resume request message during an RRC inactive mode or an RRC idle mode, the second indication indicating a suitable or desired NSSAI based on the NSSAI list to initiate a positioning session.

[0165] In another configuration, the apparatus 1204 may further include: means for receiving a list of suitable or expected NSSAIs from the network entity via assistance data (AD); and means for selecting the NSSAI list based on the list of suitable or expected NSSAIs. In some implementations, the list of suitable or expected NSSAIs may be received during RRC inactive mode or RRC idle mode.

[0166] In another configuration, the apparatus 1204 may further include means for performing prioritization between the NSSAI list and a second NSSAI list, wherein the second NSSAI list may be associated with the RRM.

[0167] This means may be the NSSAI requesting component 198 of the apparatus 1204 configured to perform the functions recited by this means. As described above, the apparatus 1204 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, this means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by this means.

[0168] Figure 13 1300 is a flow chart of a method for wireless communication. The method may be performed by a network entity (e.g., base station 102; network entity 904, 1502). The method may enable the network entity to provide positioning and / or sensing-associated NSSAI to a UE based on an NSSAI list provided / requested by the UE.

[0169] At 1304, the network entity may receive a first indication of a NSSAI list from the UE, wherein each NSSAI in the NSSAI list may be associated with at least one of a positioning mode, a sensing mode, a positioning specific service type, or a sensing specific service type, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 920 of FIG, the network entity 904 may receive an indication 906 from the UE 902, wherein the indication 906 may include a list of NSSAIs associated with one or more sensing or positioning modes / service types. The receipt of the first indication may be performed by, for example Figure 15 The NSSAI provision component 199, RU processor 1542 and / or transceiver 1546 of the network entity 1502 is executed.

[0170] In an example, the NSSAI may include at least one of the following: high-accuracy NSSAI, low-latency NSSAI, low-power NSSAI, SL positioning NSSAI, hybrid Uu-SL positioning NSSAI, or positioning NSSAI implemented by ML.

[0171] In another example, each NSSAI in the NSSAI list may include at least one SST value or at least one SD value, and different SST values ​​or different SD values ​​correspond to different positioning modes or services, or correspond to different sensing modes or services.

[0172] In another example, the first indication may be received via a positioning session request message during an RRC connected mode of the UE.

[0173] At 1310, the network entity may communicate with the UE based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 922, the network entity 904 may communicate with the UE 902 based on at least one of the positioning or sensing modes / service types. The communication with the UE may be performed by, for example Figure 15 The NSSAI provision component 199, RU processor 1542 and / or transceiver 1546 of the network entity 1502 is executed.

[0174] In one example, at 1308, the network entity may send a second indication of at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type to the UE before communicating with the UE, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 926 of FIG, the network entity 904 may send an indication 908 to the UE 902 before communicating with the UE 902, the indication indicating at least one of the positioning or sensing modes / service types. The sending of the second indication may be performed by, for example Figure 15 The NSSAI providing component 199, the RU processor 1542, and / or the transceiver 1546 of the network entity 1502 in the embodiment of the present invention are executed. In some specific implementations, the network entity may correspond to an LMF, and the network entity may receive the first indication directly from the UE or receive the first indication from the UE via an AMF. Then, the network entity may send the second indication directly to the UE or send the second indication to the UE via the AMF.

[0175] In another example, at 1306, the network entity may receive a second indication via an RRC connection request message or an RRC resume request message during an RRC inactive mode or an RRC idle mode of the UE, the second indication indicating a suitable or desired NSSAI based on the NSSAI list to initiate a positioning session, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 928 of FIG. , the network entity 904 may receive an indication 910 from the UE 902 during an RRC inactive / idle mode of the UE 902 indicating an appropriate or desired NSSAI to initiate a positioning / sensing session. Receipt of the second indication may be by, for example, Figure 15 The NSSAI provision component 199, RU processor 1542 and / or transceiver 1546 of the network entity 1502 is executed.

[0176] In another example, the network entity may correspond to an LMF, and the network entity may send a list of suitable or expected NSSAIs to a RAN associated with the UE. In some implementations, the list of suitable or expected NSSAIs may be selected from the NSSAI list, or may be selected outside the NSSAI list.

[0177] In another example, at 1302, the network entity may send a list of suitable or expected NSSAIs for the UE via assistance data, and receive a first indication of the NSSAI list based on the list of suitable or expected NSSAIs, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 930 of FIG, the network entity 904 may send a list of suitable or desired NSSAIs to the UE 902 via the assistance data 912, and the UE 902 may select the NSSAI list based on the list of suitable or desired NSSAIs. The sending of the assistance data and / or the receiving of the first indication may be performed by, for example Figure 15 The NSSAI providing component 199, the RU processor 1542 and / or the transceiver 1546 of the network entity 1502 in the embodiment of the present invention are executed. In some implementations, the list of suitable or expected NSSAIs may be sent during the RRC inactive mode or RRC idle mode of the UE.

[0178] Figure 14 1400 is a flow chart of a method of wireless communication. The method may be performed by a network entity (e.g., base station 102; network entity 904, 1502). The method may enable the network entity to provide positioning and / or sensing-associated NSSAI to a UE based on an NSSAI list provided / requested by the UE.

[0179] At 1404, the network entity may receive a first indication of a NSSAI list from the UE, wherein each NSSAI in the NSSAI list may be associated with at least one of a positioning mode, a sensing mode, a positioning specific service type, or a sensing specific service type, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 920 of FIG, the network entity 904 may receive an indication 906 from the UE 902, wherein the indication 906 may include a list of NSSAIs associated with one or more sensing or positioning modes / service types. The receipt of the first indication may be performed by, for example Figure 15 The NSSAI provision component 199, RU processor 1542 and / or transceiver 1546 of the network entity 1502 is executed.

[0180] In an example, the NSSAI may include at least one of the following: high-accuracy NSSAI, low-latency NSSAI, low-power NSSAI, SL positioning NSSAI, hybrid Uu-SL positioning NSSAI, or positioning NSSAI implemented by ML.

[0181] In another example, each NSSAI in the NSSAI list may include at least one SST value or at least one SD value, and different SST values ​​or different SD values ​​correspond to different positioning modes or services, or correspond to different sensing modes or services.

[0182] In another example, the first indication may be received via a positioning session request message during an RRC connected mode of the UE.

[0183] At 1410, the network entity may communicate with the UE based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 922, the network entity 904 may communicate with the UE 902 based on at least one of the positioning or sensing modes / service types. The communication with the UE may be performed by, for example Figure 15 The NSSAI provision component 199, RU processor 1542 and / or transceiver 1546 of the network entity 1502 is executed.

[0184] In one example, the network entity may send a second indication of at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type to the UE before communicating with the UE, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 926 of FIG, the network entity 904 may send an indication 908 to the UE 902 before communicating with the UE 902, the indication indicating at least one of the positioning or sensing modes / service types. The sending of the second indication may be performed by, for example Figure 15 The NSSAI providing component 199, the RU processor 1542, and / or the transceiver 1546 of the network entity 1502 in the embodiment of the present invention are executed. In some specific implementations, the network entity may correspond to an LMF, and the network entity may receive the first indication directly from the UE or receive the first indication from the UE via an AMF. Then, the network entity may send the second indication directly to the UE or send the second indication to the UE via the AMF.

[0185] In another example, the network entity may receive a second indication via an RRC connection request message or an RRC resume request message during an RRC inactive mode or an RRC idle mode of the UE, the second indication indicating a suitable or desired NSSAI based on the NSSAI list to initiate a positioning session, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 928 of FIG. , the network entity 904 may receive an indication 910 from the UE 902 during an RRC inactive / idle mode of the UE 902 indicating an appropriate or desired NSSAI to initiate a positioning / sensing session. Receipt of the second indication may be by, for example, Figure 15 The NSSAI provision component 199, RU processor 1542 and / or transceiver 1546 of the network entity 1502 is executed.

[0186] In another example, the network entity may correspond to an LMF, and the network entity may send a list of suitable or expected NSSAIs to a RAN associated with the UE. In some implementations, the list of suitable or expected NSSAIs may be selected from the NSSAI list, or may be selected outside the NSSAI list.

[0187] In another example, the network entity may send a list of suitable or expected NSSAIs for the UE via assistance data, and receive a first indication of the NSSAI list based on the list of suitable or expected NSSAIs, such as in conjunction with Figure 9 For example, as described in Figure 9 As shown at 930 of FIG, the network entity 904 may send a list of suitable or desired NSSAIs to the UE 902 via the assistance data 912, and the UE 902 may select the NSSAI list based on the list of suitable or desired NSSAIs. The sending of the assistance data and / or the receiving of the first indication may be performed by, for example Figure 15 The NSSAI providing component 199, the RU processor 1542 and / or the transceiver 1546 of the network entity 1502 in the embodiment of the present invention are executed. In some implementations, the list of suitable or expected NSSAIs may be sent during the RRC inactive mode or RRC idle mode of the UE.

[0188] Figure 15Figure 1500 illustrates an example hardware implementation for a network entity 1502. Network entity 1502 may be a base station (BS), a component of a BS, or may implement BS functionality. Network entity 1502 may include at least one of a CU 1510, a DU 1530, or a RU 1540. For example, depending on the layer functionality handled by NSSAI provisioning component 199, network entity 1502 may include CU 1510; both CU 1510 and DU 1530; each of CU 1510, DU 1530, and RU 1540; DU 1530; both DU 1530 and RU 1540; or RU 1540. CU 1510 may include a CU processor 1512. CU processor 1512 may include on-chip memory 1512′. In some aspects, CU 1510 may further include an additional memory module 1514 and a communication interface 1518. The CU 1510 communicates with the DU 1530 via a midhaul link (such as an F1 interface). The DU 1530 may include a DU processor 1532. The DU processor 1532 may include on-chip memory 1532′. In some aspects, the DU 1530 may further include an additional memory module 1534 and a communication interface 1538. The DU 1530 communicates with the RU 1540 via a fronthaul link. The RU 1540 may include a RU processor 1542. The RU processor 1542 may include on-chip memory 1542′. In some aspects, the RU 1540 may further include an additional memory module 1544, one or more transceivers 1546, an antenna 1580, and a communication interface 1548. The RU 1540 communicates with the UE 104. The on-chip memories 1512′, 1532′, 1542′ and the additional memory modules 1514, 1534, 1544 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of processors 1512, 1532, 1542 is responsible for general processing, including executing software stored on the computer-readable medium / memory. This software, when executed by the corresponding processor, enables the processor to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0189] As discussed above, the NSSAI providing component 199 can be configured to receive a first indication of an NSSAI list from a UE, wherein each NSSAI in the NSSAI list is associated with at least one of a positioning mode, a sensing mode, a positioning specific service type, or a sensing specific service type. The NSSAI providing component 199 can also be configured to communicate with the UE based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type. The NSSAI providing component 199 can be within one or more processors of one or more of the CU 1510, DU 1530, and RU 1540. The NSSAI providing component 199 can be one or more hardware components specifically configured to perform the recited processes / algorithms, implemented by one or more processors configured to perform the recited processes / algorithms, stored on a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 1502 can include a variety of components configured for various functions. In one configuration, the network entity 1502 may include means for receiving a first indication of an NSSAI list from a UE, wherein each NSSAI in the NSSAI list is associated with at least one of a positioning mode, a sensing mode, a positioning specific service type, or a sensing specific service type. The network entity 1502 may further include means for communicating with the UE based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type.

[0190] In one configuration, the NSSAI may include at least one of: high-accuracy NSSAI, low-latency NSSAI, low-power NSSAI, SL positioning NSSAI, hybrid Uu-SL positioning NSSAI, or ML-enabled positioning NSSAI.

[0191] In another configuration, each NSSAI in the NSSAI list may include at least one SST value or at least one SD value, and wherein different SST values ​​or different SD values ​​correspond to different positioning modes or services, or correspond to different sensing modes or services.

[0192] In another configuration, the first indication may be received via a positioning session request message during an RRC connected mode of the UE.

[0193] In another configuration, the network entity 1502 may further include: means for sending a second indication of at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type to the UE before communicating with the UE. In some implementations, the network entity 1502 may correspond to an LMF, and the network entity 1502 may further include: means for receiving the first indication directly from the UE; or means for receiving the first indication from the UE via an AMF. The network entity 1502 may further include: means for sending the second indication directly to the UE; or means for sending the second indication to the UE via the AMF.

[0194] In another configuration, the network entity 1502 may further include: a component for receiving a second indication via an RRC connection request message or an RRC resume request message during an RRC inactive mode or an RRC idle mode of the UE, the second indication indicating a suitable or desired NSSAI to initiate a positioning session based on the NSSAI list.

[0195] In another configuration, the network entity 1502 may correspond to a LMF, and the network entity 1502 may further include: means for sending a list of suitable or expected NSSAIs to the RAN associated with the UE. In some implementations, the list of suitable or expected NSSAIs may be selected from the NSSAI list, or may be selected outside the NSSAI list.

[0196] In another configuration, the network entity 1502 may further include: means for transmitting a list of suitable or expected NSSAIs for the UE via assistance data; and means for receiving a first indication of the NSSAI list based on the list of suitable or expected NSSAIs. In some implementations, the list of suitable or expected NSSAIs may be transmitted during an RRC inactive mode or an RRC idle mode of the UE.

[0197] This means may be the NSSAI providing component 199 of the network entity 1502 configured to perform the functions recited by this means. As described above, the network entity 1502 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, this means may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by this means.

[0198] It should be understood that the specific order or hierarchy of blocks in the disclosed process / flowchart is merely illustrative of an exemplary method. It should be understood that the specific order or hierarchy of blocks in the process / flowchart may be rearranged based on design preferences. In addition, some blocks may be combined or omitted. The accompanying method claims provide elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0199] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not imply a direct temporal relationship or reaction. That is, these phrases, such as "when...", do not mean immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but there is no need for a specific or immediate time limit for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having an advantage over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, which may include multiple As, multiple Bs, or multiple Cs. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be only A, only B, only C, A and B, A and C, B and C, or A, B, and C, where any such combination may include one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If a first device receives data from or sends data to a second device, the data may be received / sent directly between the first and second devices, or indirectly between the first and second devices through a collection of devices. A device configured to "output" data (such as a transmission, signal, or message) may, for example, transmit the data using a transceiver or transmit the data to the device that transmitted the data. A device configured to "obtain" data (such as a transmission, signal, or message) may, for example, receive the data using a transceiver or obtain the data from the device that received the data. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims.Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. Words such as "module," "mechanism," "element," and "device" are not intended to replace the word "component." Therefore, no claim element is to be construed as a functional component unless the element is explicitly recited using the phrase "means for..."

[0200] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0201] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0202] Aspect 1 is a method for wireless communication at a UE, the method comprising: sending a first indication of an NSSAI list to a network entity, wherein each NSSAI in the NSSAI list is associated with at least one of a positioning mode, a sensing mode, a positioning specific service type, or a sensing specific service type; and communicating with the network entity based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type.

[0203] Aspect 2 is a method according to aspect 1, wherein the NSSAI includes at least one of the following: high-accuracy NSSAI, low-latency NSSAI, low-power NSSAI, SL positioning NSSAI, hybrid Uu-SL positioning NSSAI, or positioning NSSAI implemented by ML.

[0204] Aspect 3 is a method according to Aspect 1 or 2, wherein each NSSAI in the NSSAI list includes at least one SST value or at least one SD value, and wherein different SST values ​​or different SD values ​​correspond to different positioning modes or services, or correspond to different sensing modes or services.

[0205] Aspect 4 is a method according to any one of Aspects 1 to 3, the method further comprising: receiving a second indication of at least one of the positioning mode, the sensing mode, the positioning specific service type or the sensing specific service type from the network entity before communicating with the network entity.

[0206] Aspect 5 is a method according to aspect 4, wherein the network entity corresponds to LMF, and wherein sending the first indication of the NSSAI list includes: sending the first indication directly to the LMF, or sending the first indication to the LMF via the AMF.

[0207] Aspect 6 is a method according to aspect 5, wherein receiving the second indication includes: receiving the second indication directly from the LMF, or receiving the second indication from the LMF via the AMF.

[0208] Aspect 7 is a method according to any one of Aspects 1 to 6, the method further comprising: sending a second indication via an RRC connection request message or an RRC recovery request message during an RRC inactive mode or an RRC idle mode, the second indication indicating a suitable or desired NSSAI based on the NSSAI list to initiate a positioning session.

[0209] Aspect 8 is a method according to any one of aspects 1 to 7, wherein the first indication is sent via a positioning session request message during RRC connected mode.

[0210] Aspect 9 is a method according to any one of Aspects 1 to 8, wherein communicating with the network entity based on at least one of the positioning mode, the sensing mode, the positioning specific service type or the sensing specific service type includes: communicating with the network entity based on an NSSAI that is not in the NSSAI list.

[0211] Aspect 10 is a method according to any one of aspects 1 to 9, the method further comprising: receiving a list of suitable or expected NSSAIs from the network entity via assistance data; and selecting the NSSAI list based on the list of suitable or expected NSSAIs.

[0212] Aspect 11 is a method according to aspect 10, wherein the list of suitable or desired NSSAI is received during RRC inactive mode or RRC idle mode.

[0213] Aspect 12 is a method according to any one of aspects 1 to 11, the method further comprising: performing priority sorting between the NSSAI list and a second NSSAI list, wherein the second NSSAI list is associated with RRM.

[0214] Aspect 13 is an apparatus for wireless communication at a UE, the apparatus comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and, based at least in part on information stored in the memory, the at least one processor being configured to implement any of Aspects 1 to 12.

[0215] Aspect 14 is the apparatus of aspect 13, further comprising: at least one of a transceiver or an antenna, the at least one of the transceiver or the antenna coupled to the at least one processor.

[0216] Aspect 15 is an apparatus for wireless communication, comprising: means for implementing any of aspects 1 to 12.

[0217] Aspect 16 is a computer-readable medium (eg, non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any of aspects 1 to 12.

[0218] Aspect 17 is a method for wireless communication at a network entity, the method comprising: receiving a first indication of a list of NSSAIs from a UE, wherein each NSSAI in the NSSAI list is associated with at least one of a positioning mode, a sensing mode, a positioning specific service type, or a sensing specific service type; and communicating with the UE based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type.

[0219] Aspect 18 is a method according to aspect 17, wherein the NSSAI includes at least one of the following: high-accuracy NSSAI, low-latency NSSAI, low-power NSSAI, SL positioning NSSAI, hybrid Uu-SL positioning NSSAI, or positioning NSSAI implemented by ML.

[0220] Aspect 19 is a method according to Aspect 17 or 18, wherein each NSSAI in the NSSAI list includes at least one SST value or at least one SD value, and wherein different SST values ​​or different SD values ​​correspond to different positioning modes or services, or correspond to different sensing modes or services.

[0221] Aspect 20 is a method according to any one of aspects 17 to 19, the method further comprising: sending a second indication of at least one of the positioning mode, the sensing mode, the positioning specific service type or the sensing specific service type to the UE before communicating with the UE.

[0222] Aspect 21 is a method according to aspect 20, wherein the network entity corresponds to an LMF, and wherein receiving the first indication of the NSSAI list includes: receiving the first indication directly from the UE, or receiving the first indication from the UE via an AMF.

[0223] Aspect 22 is a method according to aspect 21, wherein sending the second indication includes: sending the second indication directly to the UE, or sending the second indication to the UE via the AMF.

[0224] Aspect 23 is a method according to any one of aspects 17 to 22, the method further comprising: receiving a second indication via an RRC connection request message or an RRC recovery request message during an RRC inactive mode or an RRC idle mode of the UE, the second indication indicating a suitable or desired NSSAI based on the NSSAI list to initiate a positioning session.

[0225] Aspect 24 is a method according to any one of aspects 17 to 23, wherein the first indication is received via a positioning session request message during an RRC connected mode of the UE.

[0226] Aspect 25 is a method according to any one of aspects 17 to 24, wherein the network entity corresponds to an LMF, the method further comprising: sending a list of suitable or expected NSSAIs to a RAN associated with the UE.

[0227] Aspect 26 is a method according to aspect 25, wherein the list of suitable or desired NSSAIs is selected from the NSSAI list or is selected from outside the NSSAI list.

[0228] Aspect 27 is a method according to any one of aspects 17 to 26, the method further comprising: sending a list of suitable or expected NSSAIs for the UE via assistance data; and receiving the first indication of the NSSAI list based on the list of suitable or expected NSSAIs.

[0229] Aspect 28 is a method according to aspect 27, wherein the list of suitable or expected NSSAI is sent during an RRC inactive mode or an RRC idle mode of the UE.

[0230] Aspect 29 is an apparatus for wireless communication at a network entity, the apparatus comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and, based at least in part on information stored in the memory, the at least one processor being configured to implement any of Aspects 17 to 28.

[0231] Aspect 30 is the apparatus of aspect 29, further comprising: at least one of a transceiver or an antenna, the at least one of the transceiver or the antenna coupled to the at least one processor.

[0232] Aspect 31 is an apparatus for wireless communication, comprising: means for implementing any of aspects 17 to 28.

[0233] Aspect 32 is a computer-readable medium (eg, non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any of aspects 17 to 28.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory, and configured to: sending, to a network entity, a first indication of a network slice selection assistance information (NSSAI) list, wherein each NSSAI in the NSSAI list is associated with at least one of a positioning mode, a sensing mode, a positioning specific service type, or a sensing specific service type; as well as Communicating with the network entity is performed based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type.

2. The apparatus of claim 1 , wherein the NSSAI comprises at least one of: high-accuracy NSSAI, low-latency NSSAI, low-power NSSAI, sidelink (SL) positioning NSSAI, hybrid UE-UTRAN (Uu)-SL positioning NSSAI, or positioning NSSAI implemented by machine learning (ML).

3. The apparatus of claim 1 , wherein each NSSAI in the NSSAI list comprises at least one slice / service type (SST) value or at least one slice differentiator (SD) value, and wherein different SST values ​​or different SD values ​​correspond to different positioning modes or services, or correspond to different sensing modes or services.

4. The apparatus of claim 1 , wherein the at least one processor is further configured to: A second indication of at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type is received from the network entity prior to the communicating with the network entity.

5. The apparatus of claim 4 , wherein the network entity corresponds to a location management function (LMF), and wherein to send the first indication of the NSSAI list, the at least one processor is configured to: Send the first instruction directly to the LMF, or The first indication is sent to the LMF via an Access and Mobility Management Function (AMF).

6. The apparatus of claim 5, wherein to receive the second indication, the at least one processor is configured to: receiving the second indication directly from the LMF, or The second indication is received from the LMF via the AMF.

7. The apparatus of claim 1 , wherein the at least one processor is further configured to: A second indication is sent via a radio resource control (RRC) connection request message or an RRC resume request message during a radio resource control (RRC) inactive mode or an RRC idle mode, the second indication indicating a suitable NSSAI based on the NSSAI list to initiate a positioning session. 8 . The apparatus of claim 1 , wherein the at least one processor is configured to send the first indication via a positioning session request message during a radio resource control (RRC) connected mode.

9. The apparatus of claim 1 , wherein to communicate with the network entity based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type, the at least one processor is configured to: Communicating with the network entity based on an NSSAI that is not in the NSSAI list.

10. The apparatus of claim 1 , wherein the at least one processor is further configured to: receiving a list of suitable NSSAIs from the network entity via assistance data (AD); and The NSSAI list is selected based on the list of suitable NSSAIs.

11. The apparatus of claim 10, wherein the at least one processor is configured to receive the list of suitable NSSAIs during a radio resource control (RRC) inactive mode or an RRC idle mode.

12. The apparatus of claim 1 , wherein the at least one processor is further configured to: Prioritization is performed between the NSSAI list and a second NSSAI list, wherein the second NSSAI list is associated with radio resource management (RRM).

13. A method of wireless communication at a user equipment (UE), the method comprising: sending, to a network entity, a first indication of a network slice selection assistance information (NSSAI) list, wherein each NSSAI in the NSSAI list is associated with at least one of a positioning mode, a sensing mode, a positioning specific service type, or a sensing specific service type; as well as Communicating with the network entity is performed based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type.

14. The method of claim 13, wherein the NSSAI comprises at least one of: high-accuracy NSSAI, low-latency NSSAI, low-power NSSAI, sidelink (SL) positioning NSSAI, hybrid UE-UTRAN (Uu)-SL positioning NSSAI, or positioning NSSAI implemented by machine learning (ML).

15. The method according to claim 13, further comprising: A second indication of at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type is received from the network entity prior to the communicating with the network entity.

16. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and at least one processor coupled to the memory, and configured to: receiving a first indication of a network slice selection assistance information (NSSAI) list from a user equipment (UE), wherein each NSSAI in the NSSAI list is associated with at least one of a positioning mode, a sensing mode, a positioning specific service type, or a sensing specific service type; as well as Communicating with the UE is performed based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type.

17. The apparatus of claim 16, wherein the NSSAI comprises at least one of: high-accuracy NSSAI, low-latency NSSAI, low-power NSSAI, sidelink (SL) positioning NSSAI, hybrid UE-UTRAN (Uu)-SL positioning NSSAI, or positioning NSSAI enabled by machine learning (ML).

18. The apparatus of claim 16, wherein each NSSAI in the NSSAI list comprises at least one slice / service type (SST) value or at least one slice differentiator (SD) value, and wherein different SST values ​​or different SD values ​​correspond to different positioning modes or services, or correspond to different sensing modes or services.

19. The apparatus of claim 16, wherein the at least one processor is further configured to: A second indication of at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type is sent to the UE before the communication with the UE.

20. The apparatus of claim 19, wherein the network entity corresponds to a location management function (LMF), and to receive the first indication of the NSSAI list, the at least one processor is configured to: directly receiving the first indication from the UE, or The first indication is received from the UE via an Access and Mobility Management Function (AMF).

21. The apparatus of claim 20, wherein to send the second indication, the at least one processor is configured to: directly sending the second indication to the UE, or Sending the second indication to the UE via the AMF.

22. The apparatus of claim 16, wherein the at least one processor is further configured to: A second indication is received via a radio resource control (RRC) connection request message or an RRC resume request message during a radio resource control (RRC) inactive mode or an RRC idle mode of the UE, the second indication indicating a suitable NSSAI based on the NSSAI list to initiate a positioning session.

23. The apparatus of claim 16, wherein the at least one processor is configured to receive the first indication via a positioning session request message during a radio resource control (RRC) connected mode of the UE.

24. The apparatus of claim 16, wherein the network entity corresponds to a location management function (LMF), wherein the at least one processor is further configured to: A list of appropriate NSSAIs is sent to a random access network (RAN) associated with the UE.

25. The apparatus of claim 24, wherein the at least one processor is configured to select the list of appropriate NSSAIs from within the NSSAI list or from outside the NSSAI list.

26. The apparatus of claim 16, wherein the at least one processor is further configured to: sending a list of appropriate NSSAIs for the UE via assistance data (AD); and The first indication of the NSSAI list is received based on the list of suitable NSSAIs.

27. The apparatus of claim 26, wherein the at least one processor is configured to transmit the list of suitable NSSAIs during a radio resource control (RRC) inactive mode or an RRC idle mode of the UE.

28. A method of wireless communication at a network entity, the method comprising: receiving a first indication of a network slice selection assistance information (NSSAI) list from a user equipment (UE), wherein each NSSAI in the NSSAI list is associated with at least one of a positioning mode, a sensing mode, a positioning specific service type, or a sensing specific service type; as well as Communicating with the UE is performed based on at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type.

29. The method of claim 28, wherein the NSSAI comprises at least one of: high-accuracy NSSAI, low-latency NSSAI, low-power NSSAI, sidelink (SL) positioning NSSAI, hybrid UE-UTRAN (Uu)-SL positioning NSSAI, or positioning NSSAI enabled by machine learning (ML).

30. The method of claim 28, further comprising: A second indication of at least one of the positioning mode, the sensing mode, the positioning specific service type, or the sensing specific service type is sent to the UE before the communication with the UE.

Images