WO2022056659A1 - Négociation de nssai applicable à un équipement utilisateur - Google Patents

Négociation de nssai applicable à un équipement utilisateur Download PDF

Info

Publication number
WO2022056659A1
WO2022056659A1 PCT/CN2020/115257 CN2020115257W WO2022056659A1 WO 2022056659 A1 WO2022056659 A1 WO 2022056659A1 CN 2020115257 W CN2020115257 W CN 2020115257W WO 2022056659 A1 WO2022056659 A1 WO 2022056659A1
Authority
WO
WIPO (PCT)
Prior art keywords
nssai
list
request
applicable
network
Prior art date
Application number
PCT/CN2020/115257
Other languages
English (en)
Inventor
Nan Zhang
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2020/115257 priority Critical patent/WO2022056659A1/fr
Publication of WO2022056659A1 publication Critical patent/WO2022056659A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data

Definitions

  • aspects of the present disclosure relate to wireless communications, and more particularly, to network slicing enhancements and negotiating a network slice selection assistance information (NSSAI) list.
  • NSSAI network slice selection assistance information
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, etc. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc. ) .
  • available system resources e.g., bandwidth, transmit power, etc.
  • multiple-access systems examples include 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, LTE Advanced (LTE-A) systems, code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems, to name a few.
  • 3GPP 3rd Generation Partnership Project
  • LTE Long Term Evolution
  • LTE-A LTE Advanced
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single-carrier frequency division multiple access
  • TD-SCDMA time division synchronous code division multiple access
  • a wireless multiple-access communication system may include a number of base stations (BSs) , which are each capable of simultaneously supporting communication for multiple communication devices, otherwise known as user equipments (UEs) .
  • BSs base stations
  • UEs user equipments
  • a set of one or more base stations may define an eNodeB (eNB) .
  • eNB eNodeB
  • a wireless multiple access communication system may include a number of distributed units (DUs) (e.g., edge units (EUs) , edge nodes (ENs) , radio heads (RHs) , smart radio heads (SRHs) , transmission reception points (TRPs) , etc.
  • DUs distributed units
  • EUs edge units
  • ENs edge nodes
  • RHs radio heads
  • SSRHs smart radio heads
  • TRPs transmission reception points
  • CUs central units
  • CNs central nodes
  • ANCs access node controllers
  • a set of one or more DUs, in communication with a CU may define an access node (e.g., which may be referred to as a BS, 5G NB, next generation NodeB (gNB or gNodeB) , transmission reception point (TRP) , etc. ) .
  • BS central nodes
  • 5G NB next generation NodeB
  • TRP transmission reception point
  • a BS or DU may communicate with a set of UEs on downlink channels (e.g., for transmissions from a BS or DU to a UE) and uplink channels (e.g., for transmissions from a UE to BS or DU) .
  • downlink channels e.g., for transmissions from a BS or DU to a UE
  • uplink channels e.g., for transmissions from a UE to BS or DU
  • NR e.g., new radio or 5G
  • LTE long term evolution
  • NR is a set of enhancements to the LTE mobile standard promulgated by 3GPP.
  • NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDMA with a cyclic prefix (CP) on the downlink (DL) and on the uplink (UL) .
  • OFDMA orthogonal frequency division multiple access
  • CP cyclic prefix
  • DL downlink
  • UL uplink
  • NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
  • MIMO multiple-input multiple-output
  • wireless networks such as NR and LTE networks
  • Edge computing devices may support dynamic distribution of processing of data and/or content between the edge computing devices and a wireless device, such as a UE.
  • Certain aspects provide a method for wireless communication by a UE.
  • the method generally includes negotiating, with a network entity, at least one applicable network slice selection assistance information (NSSAI) list, sending the network entity a request for one or more NSSAI selected from the negotiated applicable NSSAI list, and receiving, from the network entity, an indication of at least one allowed NSSAI in response to the request.
  • NSSAI network slice selection assistance information
  • Certain aspects provide a method for wireless communication by a network entity.
  • the method generally includes negotiating, with a UE, at least one applicable NSSAI list, receiving, from the UE, a request for one or more NSSAI selected from the negotiated applicable NSSAI list, and sending, to the UE, an indication of at least one allowed NSSAI in response to the request.
  • the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
  • the following description and the appended drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.
  • FIG. 1 is a block diagram conceptually illustrating an example telecommunications system, in accordance with certain aspects of the present disclosure.
  • FIG. 2 is a block diagram conceptually illustrating a design of an example base station (BS) and user equipment (UE) , in accordance with certain aspects of the present disclosure.
  • BS base station
  • UE user equipment
  • FIG. 3 is a block diagram illustrating an example architecture of a core network (CN) and radio access network (RAN) , in accordance with certain aspects of the present disclosure.
  • CN core network
  • RAN radio access network
  • FIG. 4 is an example format of a network slice selection assistance information (NSSAI) information element (IE) .
  • NSSAI network slice selection assistance information
  • IE information element
  • FIG. 5 is an example format of a single NSSAI (S-NSSAI) IE.
  • FIG. 6 is a table showing example NSSAI inclusion modes.
  • FIG. 7 is a call flow illustrating example NSSAI signaling.
  • FIG. 8 illustrates example operations for wireless communications by a UE, in accordance with some aspects of the present disclosure.
  • FIG. 9 illustrates example operations for wireless communications by a network entity, in accordance with some aspects of the present disclosure.
  • FIG. 10 illustrates a communications device that may include various components configured to perform operations for the techniques disclosed herein in accordance with aspects of the present disclosure.
  • FIG. 11 illustrates a communications device that may include various components configured to perform operations for the techniques disclosed herein in accordance with aspects of the present disclosure.
  • a UE may negotiate with a network for a network slice selection assistance information (NSSAI) list, based on relevant applications, application needs, and/or UE capability.
  • NSSAI network slice selection assistance information
  • a CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA) , cdma2000, etc.
  • UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA.
  • cdma2000 covers IS-2000, IS-95 and IS-856 standards.
  • a TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM) .
  • An OFDMA network may implement a radio technology such as NR (e.g.
  • E-UTRA Evolved UTRA
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi
  • IEEE 802.16 WiMAX
  • IEEE 802.20 Flash-OFDMA
  • UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS) .
  • New Radio is an emerging wireless communications technology under development in conjunction with the 5G Technology Forum (5GTF) .
  • 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are releases of UMTS that use E-UTRA.
  • UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP) .
  • cdma2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2) .
  • the techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, while aspects may be described herein using terminology commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, such as 5G and later, including NR technologies.
  • New radio (NR) access may support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or beyond) , millimeter wave (mmW) targeting high carrier frequency (e.g., 25 GHz or beyond) , massive machine type communications MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low-latency communications (URLLC) .
  • eMBB enhanced mobile broadband
  • mmW millimeter wave
  • mMTC massive machine type communications MTC
  • URLLC ultra-reliable low-latency communications
  • These services may include latency and reliability requirements.
  • These services may also have different transmission time intervals (TTI) to meet respective quality of service (QoS) requirements.
  • TTI transmission time intervals
  • QoS quality of service
  • these services may co-exist in the same subframe.
  • FIG. 1 illustrates an example wireless communication network 100 in which aspects of the present disclosure may be performed.
  • a UE 120 may be configured to perform operations 800 of FIG. 8, to achieve network slicing enhancements and negotiate a network slice selection assistance information (NSSAI) list.
  • NSSAI network slice selection assistance information
  • an eNB may be configured to perform the operations 900 of FIG. 9 to achieve network slicing enhancements and negotiate a NSSAI list.
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal FDMA
  • SC-FDMA Single-Carrier FDMA
  • a CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA) , cdma2000, etc.
  • UTRA includes Wideband-CDMA (W-CDMA) and Low Chip Rate (LCR) .
  • cdma2000 covers IS-2000, IS-95 and IS-856 standards.
  • a TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM) .
  • GSM Global System for Mobile Communications
  • An OFDMA network may implement a radio technology such as Evolved UTRA (E-UTRA) , IEEE 802.11, IEEE 802.16, IEEE 802.20, etc.
  • E-UTRA, and GSM are part of Universal Mobile Telecommunication System (UMTS) .
  • Long Term Evolution (LTE) is an upcoming release of UMTS that uses E-UTRA.
  • UTRA, E-UTRA, GSM, UMTS and LTE are described in documents from an organization named “3rd Generation Partnership Project” (3GPP) .
  • cdma2000 is described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2) .
  • SC-FDMA Single carrier frequency division multiple access
  • SC-FDMA Single carrier frequency division multiple access
  • SC-FDMA signal has lower peak-to-average power ratio (PAPR) because of its inherent single carrier structure.
  • PAPR peak-to-average power ratio
  • SC-FDMA has drawn great attention, especially in the uplink communications where lower PAPR greatly benefits the mobile terminal in terms of transmit power efficiency. It is currently a working assumption for uplink multiple access scheme in 3GPP Long Term Evolution (LTE) , or Evolved UTRA.
  • LTE Long Term Evolution
  • FIG. 1 shows a wireless communication network 100 in which aspects of the present disclosure may be practiced.
  • evolved Node Bs 110 may cache content and transmit the cached content to user equipments (UEs) 120 as described herein.
  • UEs user equipments
  • Wireless communication network 100 may be an LTE network.
  • the wireless network 100 may include a number of evolved Node Bs (eNBs) 110 and other network entities.
  • eNB evolved Node Bs
  • An eNB may be a station that communicates with the UEs and may also be referred to as a base station, an access point, etc.
  • a Node B is another example of a station that communicates with the UEs.
  • Each eNB 110 may provide communication coverage for a particular geographic area.
  • the term “cell” can refer to a coverage area of an eNB and/or an eNB subsystem serving this coverage area, depending on the context in which the term is used.
  • An eNB may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cell.
  • a macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription.
  • a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription.
  • a femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG) , UEs for users in the home, etc. ) .
  • CSG Closed Subscriber Group
  • An eNB for a macro cell may be referred to as a macro eNB.
  • An eNB for a pico cell may be referred to as a pico eNB.
  • An eNB for a femto cell may be referred to as a femto eNB or a home eNB.
  • the eNBs 110a, 110b and 110c may be macro eNBs for the macro cells 102a, 102b and 102c, respectively.
  • the eNB 110x may be a pico eNB for a pico cell 102x.
  • the eNBs 110y and 110z may be femto eNBs for the femto cells 102y and 102z, respectively.
  • An eNB may support one or multiple (e.g., three) cells.
  • the wireless network 100 may also include relay stations.
  • a relay station is a station that receives a transmission of data and/or other information from an upstream station (e.g., an eNB or a UE) and sends a transmission of the data and/or other information to a downstream station (e.g., a UE or an eNB) .
  • a relay station may also be a UE that relays transmissions for other UEs.
  • a relay station 110r may communicate with the eNB 110a and a UE 120r in order to facilitate communication between the eNB 110a and the UE 120r.
  • a relay station may also be referred to as a relay eNB, a relay, etc.
  • the wireless network 100 may be a heterogeneous network that includes eNBs of different types, e.g., macro eNBs, pico eNBs, femto eNBs, relays, etc. These different types of eNBs may have different transmit power levels, different coverage areas, and different impact on interference in the wireless network 100.
  • macro eNBs may have a high transmit power level (e.g., 20 Watts) whereas pico eNBs, femto eNBs and relays may have a lower transmit power level (e.g., 1 Watt) .
  • the wireless network 100 may support synchronous or asynchronous operation.
  • the eNBs may have similar frame timing, and transmissions from different eNBs may be approximately aligned in time.
  • the eNBs may have different frame timing, and transmissions from different eNBs may not be aligned in time.
  • the techniques described herein may be used for both synchronous and asynchronous operation.
  • a network controller 130 may couple to a set of eNBs and provide coordination and control for these eNBs.
  • the network controller 130 may communicate with the eNBs 110 via a backhaul.
  • the eNBs 110 may also communicate with one another, e.g., directly or indirectly via wireless or wireline backhaul.
  • the UEs 120 may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile.
  • a UE may also be referred to as a terminal, a mobile station, a subscriber unit, a station, etc.
  • a UE may be a cellular phone, a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, etc.
  • PDA personal digital assistant
  • a UE may be able to communicate with macro eNBs, pico eNBs, femto eNBs, relays, etc.
  • a solid line with double arrows indicates desired transmissions between a UE and a serving eNB, which is an eNB designated to serve the UE on the downlink and/or uplink.
  • a dashed line with double arrows indicates interfering transmissions between a UE and an eNB.
  • LTE utilizes orthogonal frequency division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink.
  • OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc.
  • K orthogonal subcarriers
  • Each subcarrier may be modulated with data.
  • modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM.
  • the spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth.
  • the spacing of the subcarriers may be 15 kHz and the minimum resource allocation (called a ‘resource block’ ) may be 12 subcarriers (or 180 kHz) . Consequently, the nominal FFT size may be equal to 128, 256, 512, 1024 or 2048 for system bandwidth of 1.25, 2.5, 5, 10 or 20 megahertz (MHz) , respectively.
  • the system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.8 MHz (i.e., 6 resource blocks) , and there may be 1, 2, 4, 8 or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10 or 20 MHz, respectively.
  • the wireless network 100 may also include UEs 120 capable of communicating with a core network via one or more radio access networks (RANs) that implement one or more radio access technologies (RATs) .
  • RANs radio access networks
  • RATs radio access technologies
  • the wireless network 100 may include co-located access points (APs) and/or base stations that provide communication through a first RAN implementing a first RAT and a second RAN implementing a second RAT.
  • the first RAN may be a wide area wireless access network (WWAN) and the second RAN may be a wireless local area network (WLAN) .
  • WWAN wide area wireless access network
  • WLAN wireless local area network
  • WWAN may include, but not be limited to, for example, radio access technologies (RATs) such as LTE, UMTS, cdma2000, GSM, and the like.
  • RATs radio access technologies
  • WLAN may include, but not be limited to, for example, RATs such as Wi-Fi or IEEE 802.11 based technologies, and the like.
  • the wireless network 100 may include co-located Wi-Fi access points (APs) and femto eNBs that provide communication through Wi-Fi and cellular radio links.
  • APs Wi-Fi access points
  • femto eNBs that provide communication through Wi-Fi and cellular radio links.
  • co-located generally means “in close proximity to, ” and applies to Wi-Fi APs or femto eNBs within the same device enclosure or within separate devices that are in close proximity to each other.
  • the term “femtoAP” may refer to a co-located Wi-Fi AP and femto eNB.
  • FIG. 2 is a block diagram of an example embodiment of a base station 110 (also known as an access point (AP) ) and a UE 120 in which aspects of the present disclosure may be practiced.
  • a base station 110 also known as an access point (AP)
  • UE 120 may be configured to perform operations 800 of FIG. 8
  • the various processors of the BS 110 may be configured to perform operations 900 of FIG. 9.
  • traffic data for a number of data streams is provided from a data source 212 to a transmit (TX) data processor 214.
  • TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.
  • the coded data for each data stream may be multiplexed with pilot data using OFDM techniques.
  • the pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response.
  • the multiplexed pilot and coded data for each data stream is then modulated (i.e., symbol mapped) based on a particular modulation scheme (e.g., BPSK, QSPK, M-PSK, or M-QAM) selected for that data stream to provide modulation symbols.
  • a particular modulation scheme e.g., BPSK, QSPK, M-PSK, or M-QAM
  • the data rate, coding, and modulation for each data stream may be determined by instructions performed by processor 230.
  • TX MIMO processor 220 may further process the modulation symbols (e.g., for OFDM) .
  • TX MIMO processor 220 then provides N T modulation symbol streams to N T transmitters (TMTR) 222a through 222t.
  • TMTR TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.
  • Each receiver 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel.
  • N T modulated signals from transmitters 222a through 222t are then transmitted from N T antennas 224a through 224t, respectively.
  • the transmitted modulated signals are received by N R antennas 252a through 252r, and the received signal from each antenna 252 is provided to a respective receiver (RCVR) 254a through 254r.
  • Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding “received” symbol stream.
  • An RX data processor 260 then receives and processes the N R received symbol streams from N R receivers 254 based on a particular receiver processing technique to provide N T “detected” symbol streams.
  • the RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream.
  • the processing by RX data processor 260 is complementary to that performed by TX MIMO processor 220 and TX data processor 214 at base station 110.
  • a processor 270 periodically determines which pre-coding matrix to use. Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.
  • the reverse link message may comprise various types of information regarding the communication link and/or the received data stream.
  • the reverse link message is then processed by a TX data processor 238, which also receives traffic data for a number of data streams from a data source 236, modulated by a modulator 280, conditioned by transmitters 254a through 254r, and transmitted back to base station 110.
  • the modulated signals from UE 120 are received by antennas 224, conditioned by receivers 222, demodulated by a demodulator 240, and processed by a RX data processor 242 to extract the reserve link message transmitted by the UE 120.
  • Processor 230 determines which pre-coding matrix to use for determining the beamforming weights and then processes the extracted message.
  • the controllers/processors 230 and 270 may direct the operation at the base station 110 and the UE 120, respectively.
  • the processor 230, TX data processor 214, and/or other processors and modules at the base station 110 may perform or direct processes for the techniques described herein.
  • the processor 270, RX data processor 260, and/or other processors and modules at the UE 120 may perform or direct processes for the techniques described herein.
  • the processor 230, TX data processor 214, and/or other processors and modules at the UE 120 may perform or direct operations 300 of FIG. 3.
  • FIG. 3 is a block diagram illustrating an example architecture of a core network (CN) 300 (e.g., such as the CN 132 in FIG. 1) in communication with a RAN 324, in accordance with certain aspects of the present disclosure.
  • the example architecture includes the CN 300, RAN 324, UE 322, and data network (DN) 328 (e.g. operator services, Internet access or third party services) .
  • DN data network
  • the CN 300 may host core network functions. CN 300 may be centrally deployed. CN 300 functionality may be offloaded (e.g., to advanced wireless services (AWS) ) , in an effort to handle peak capacity.
  • the example CN 300 may be implemented by one or more network entities that perform network functions (NF) including Network Slice Selection Function (NSSF) 304, Network Exposure Function (NEF) 306, NF Repository Function (NRF) 308, Policy Control Function (PCF) 310, Unified Data Management (UDM) 312, Application Function (AF) 314, Authentication Server Function (AUSF) 316, Access and Mobility Management Function (AMF) 318, Session Management Function (SMF) 320; User Plane Function (UPF) 326, and various other functions (not shown) such as Unstructured Data Storage Function (UDSF) ; Unified Data Repository (UDR) ; 5G-Equipment Identity Register (5G-EIR) ; and/or Security Edge Protection Proxy (SEPP) .
  • NF Network Slice Selection Function
  • the AMF 318 may include the following functionality (some or all of the AMF functionalities may be supported in one or more instances of an AMF) : termination of RAN control plane (CP) interface (N2) ; termination of non-access stratum (NAS) (e.g., N1) , NAS ciphering and integrity protection; registration management; connection management; reachability management; mobility management; lawful intercept (for AMF events and interface to L1 system) ; transport for session management (SM) messages between UE 322 and SMF 320; transparent proxy for routing SM messages; access authentication; access authorization; transport for short message service (SMS) messages between UE 322 and a SMS function (SMSF) ; Security Anchor Functionality (SEAF) ; Security Context Management (SCM) , which receives a key from the SEAF that it uses to derive access-network specific keys; Location Services management for regulatory services; transport for Location Services messages between UE 322 and a location management function (LMF) as well as between RAN 324 and LMF; evolved packet service
  • SMF 320 may support: session management (e.g., session establishment, modification, and release) , UE IP address allocation and management, dynamic host configuration protocol (DHCP) functions, termination of NAS signaling related to session management, downlink data notification, and traffic steering configuration for UPF for proper traffic routing.
  • UPF 326 may support: packet routing and forwarding, packet inspection, quality-of-service (QoS) handling, external protocol data unit (PDU) session point of interconnect to DN 328, and anchor point for intra-RAT and inter-RAT mobility.
  • PCF 310 may support: unified policy framework, providing policy rules to control protocol functions, and/or access subscription information for policy decisions in UDR.
  • AUSF 316 may acts as an authentication server.
  • UDM 312 may support: generation of Authentication and Key Agreement (AKA) credentials, user identification handling, access authorization, and subscription management.
  • NRF 308 may support: service discovery function, and maintain NF profile and available NF instances.
  • NSSF may support: selecting of the Network Slice instances to serve the UE 322, determining the allowed network slice selection assistance information (NSSAI) , and/or determining the AMF set to be used to serve the UE 322.
  • NSSAI network slice selection assistance information
  • NEF 306 may support: exposure of capabilities and events, secure provision of information from external application to 3GPP network, translation of internal/external information.
  • AF 314 may support: application influence on traffic routing, accessing NEF 306, and/or interaction with policy framework for policy control.
  • the CN 300 may be in communication with the AS 302, UE 322, RAN 324, and DN 328.
  • the CN 300 communicates with the external AS 302 via the NEF 306 and/or AF 314.
  • the CN 300 communicates with the RAN 324 (e.g., such as the BS 110a in the wireless communication network 100 illustrated in FIG. 1) and/or the UE 322 (e.g., such as the UE 120a in the wireless communication network 100 illustrated in FIG. 1) via the AMF 318.
  • the NSSF 304 may support the following functionality: negotiating, with a UE, at least one applicable network slice selection assistance information (NSSAI) list; receiving, from the UE, a request for one or more NSSAI selected from the negotiated applicable NSSAI list; and/or sending, to the UE, an indication of at least one allowed NSSAI in response to the request.
  • NSSAI network slice selection assistance information
  • a network slice may be defined as a logical network that provides specific network capabilities and network characteristics.
  • a network slice instance may be defined as a set of network function instances and the required resources (e.g., compute, storage, and networking resources) which form a deployed network slice.
  • a network slice is identified by single network slice selection assistance information (S-NSSAI) .
  • NSSAI is a list of one or more S-NSSAIs.
  • An S-NSSAI includes a slice/service type (SST) , which refers to the expected network slice behavior (e.g., features and services) , and a slice differentiator (SD) , which is optional information that complements the SST (s) to differentiate amongst multiple network slices of the same SST.
  • SST slice/service type
  • SD slice differentiator
  • An S-NSSAI can have standard values (e.g., including an SST with a standardized SST value and no SD) or non-standard values (e.g., including an SST and an SD or including an SST without a standardized SST value and no SD) .
  • An S-NSSAI with a non-standard value identifies a single network slice within the PLMN with which it is associated.
  • An S-NSSAI with a non-standard value may not be used by the UE in access stratum procedures in any PLMN other than the one to which the S-NSSAI is associated.
  • Network slices may differ with respects to supported features and network functions optimizations. For example, different S-NSSAIs may have different SSTs. An operator can deploy multiple network slice instances delivering the same features, but for different groups of UEs (e.g., dedicated to a customer different S-NSSAIs with the same SST but different SDs) . The network may serve a single UE with one or more network slice instances simultaneously (e.g., via the 5G-AN) . In some examples, a UE may be associated with up to eight different S-NSSAIs in total.
  • AMF instances can be common to network slice instances serving a UE. Selection of the set of network slice instances for a UE is triggered by the first contacted AMF in a registration procedure normally by interacting with the NSSF.
  • a PDU session may belong to one specific network slice instance per PLMN. Different network slice instances may not share a protocol data unit (PDU) session, though different slices may have slice-specific PDU sessions using the same data network name (DNN) .
  • PDU protocol data unit
  • DNN data network name
  • the UE may request establishment of a PDU session in a network slice towards a DN associated with an S-NSSAI and a (DNN if there is no established PDU session adequate for the PDU transmission.
  • the S-NSSAI included is part of allowed NSSAI of the serving PLMN, which is an S-NSSAI value valid in the serving PLMN, and in roaming scenarios the mapped S-NSSAI is also included for the PDU session if available.
  • S-NSSAI values are provided in an NSSAI information element (IE) .
  • the NSSAI IE identifies a collection of S-NSSAIs.
  • FIG. 4 is an example format of the NSSAI IE. As shown in FIG. 4, the example NSSAI IE may have a length of 4-146 octets.
  • the NSSAI IE may indicate up to eight S-NSSAI values for requested NSSAI (sent by a UE) or an allowed NSSAI (sent by the network) .
  • the NSSAI IE may indicate up to sixteen S-NSSAI values in a configured NSSAI (sent by the UE and/or the network) .
  • the S-NSSAI identifies a network slice.
  • An example format of the S-NSSAI IE is shown in FIG. 5.
  • the S-NSSAI IE may have a length of 3-10 octets.
  • the S-NSSAI value is coded as the length and value part of the example S-NSSAI IE starting with the second octet.
  • the length of S-NSSAI field may indicate the length of the included S-NSSAI contents.
  • the SST field may indicate SST value.
  • the SD field may indicate the SD value.
  • the mapped HPLMN SST field may indicate the SST value of an S-NSSAI in the S-NSSAI (s) of the HPLMN to which the SST value is mapped.
  • the mapped HPLMN SD field may indicate the SD value of an S-NSSAI in the S-NSSAI (s) of the HPLMN to which the SST value is mapped.
  • the NSSAI IE may be exchanged (e.g., between the UE and the network) as part of mobility management procedures.
  • the NSSAI may be sent at both the non-access stratum (NAS) layer and the AS layer.
  • NAS non-access stratum
  • the Requested NSSAI IE can be sent in a REGISTRATION REQUEST message, except when triggered by a periodic update.
  • the Requested NSSAI IE may include up to eight S-NSSAI entries, with a size of up to 74 octets.
  • the Allowed NSSAI IE can be sent in a REGISTRATION ACCEPT message, which may be included if the procedure is triggered by a periodic update.
  • the Allowed NSSAI IE may include up to eighth S-NSSAI entries, with a size of up to 74 octets.
  • the Configured NSSAI IE can be sent in a REGISTRATION ACCEPT message.
  • the Configured NSSAI IE may include up to sixteen S-NSSAI entries, with a size of up to 146 octets.
  • the Allowed NSSAI IE and the Configured NSSAI IE can be sent in a CONFIGURATION UPDATE COMMAND message.
  • the UE NAS layer may provide the lower layers with an NSSAI (either requested NSSAI or allowed NSSAI) when the UE in idle mode sends an initial NAS message.
  • NSSAI either requested NSSAI or allowed NSSAI
  • the UE can be configured to send NSSAI information in the AS layer based on the NSSAI inclusion mode in which it is operating.
  • FIG. 6 is a table showing example NSSAI inclusion modes, based on which different NSSAI information are provided for different NAS procedures.
  • the network e.g., via the AMF
  • the UE 702 After initial registration, the UE 702 includes the Requested NSSAI IE in the REGISTRATION REQUEST message to the AMF 704, except when the procedure is triggered for a periodic update. Also, the Requested NSSAI IE is included in the NAS message during initial registration even if the UE already has a configured NSSAI or an allowed NSSAI from a previous registration. The Requested NSSAI IE (which can be up to 74 octets long) may be considered duplicated if the UE is operating in NSSAI inclusion mode A or B for which the same information is provided via the AS layer.
  • FIG. 7 is a call flow 700 illustrating example NSSAI signaling. As shown in FIG.
  • NSSAI signaling overhead can be occurred during initial attachment (e.g., such as in registration request messages 710 and registration accept messages 708, 712) , during a configuration update (e.g., such as in configuration update commands 714) , and/or during PDU session establishment (e.g., such as in UL NAS transport messages 718 and PDU session accept messages 722) .
  • aspects of the present disclosure relate to wireless communications, and more particularly, to network slicing enhancements and negotiating a network slice selection assistance information (NSSAI) list.
  • NSSAI network slice selection assistance information
  • the UE may advantageously be able to route an application to an appropriate (e.g., preferred or better suited) slicing instance.
  • the UE submits a “Requested NSSAI” list during a registration procedure.
  • the “Requested NSSAI” may be selected from UE configured NSSAI list, and this UE configured NSSAI list (e.g., 8 NW slicing instances maximum) is provided by a cell (e.g., a fifth generation cell (5GC) ) .
  • a cell e.g., a fifth generation cell (5GC)
  • 5GC not the UE, is the one controlling and/or preparing “preferred” NSSAI (or network) slicing instance (s) lists associated with UE applications.
  • network slicing is application-centric instead of network-centric. That is, an application (of a UE) knows which network slicing type it needs, while a given 5GC cannot track and make proper choices for every individual UE as well as each of the potentially many applications in each UE. Additionally, a UE application is not authorized to select preferred network slicing instances from the applicable network slicing instances of the PLMN. Instead the 5GC makes the final decision. This protocol could be a problem that potentially blocks network slicing from being implemented more widely in commercial use.
  • certain aspects provide for network slicing enhancements by negotiating a NSSAI list.
  • a UE may negotiate with a network entity which slicing instances are applicable for a particular application of the UE.
  • FIG. 8 illustrates example operations 800 for wireless communications by a UE.
  • operations 800 may be performed, by a UE (e.g., the UE 120 of FIG. 1 or FIG. 2) to enhance network slicing and negotiating a NSSAI list.
  • a UE e.g., the UE 120 of FIG. 1 or FIG. 2
  • Operations 800 begin, at 802, by negotiating, with a network entity, at least one applicable NSSAI list.
  • the UE sends the network entity a request for one or more NSSAI selected from the negotiated applicable NSSAI list.
  • the UE receives, from the network entity, an indication of at least one allowed NSSAI in response to the request.
  • FIG. 9 illustrates example operations 900 for wireless communications by a network entity.
  • operations 900 may be performed, by a network entity (e.g., the BS 110 of FIG. 1 or FIG. 2) to enhance network slicing and negotiating a NSSAI list.
  • the operations 900 may be considered complementary to the operations 800 of FIG. 8.
  • Operations 900 begin, at 902, by negotiating, with a UE, at least one applicable NSSAI list.
  • the network entity receives, from the UE, a request for one or more NSSAI selected from the negotiated applicable NSSAI list.
  • the network entity sends, to the UE, an indication of at least one allowed NSSAI in response to the request.
  • the negotiation described above may include a submission of a request, by the UE, to the network for a UE applicable NSSAI/network slicing instances lists.
  • the UE may request to get UE-applicable NSSAI lists from an associated PLMN.
  • the UE may provide assistance information in the request related to the request, which may indicate application list (s) , UE capability, and/or other helpful information for the network entity.
  • the network may provide the UE with UE-applicable S-NSSAI list (e.g., network slicing instances lists) , where each S-NSSAI may be associated with a tracking area or registration area limit.
  • UE-applicable S-NSSAI list e.g., network slicing instances lists
  • each S-NSSAI may be associated with a tracking area or registration area limit.
  • the network may provide the UE with a list of 23 different network slicing instances, each having a valid tracking area identity (TAI) list.
  • TAI tracking area identity
  • the UE may determine a requested (e.g., preferred) NSSAI from the UE-applicable S-NSSAI lists based on, for instance, UE application (s) information, UE location info, and/or any other relevant factor. For example, of the 23 different network slicing instances described above, a UE may submit a requested NSSAI list of one or more NSSAIs (e.g., 4 S-NSSAIs) to the network.
  • a requested NSSAI list e.g., 4 S-NSSAIs
  • the network may respond to the UE with allowed NSSAI. For example, the network permits the request and responds with an indication that the 4 S-NSSAIs are allowed NSSAIs.
  • the negotiation for UE applicable NSSAI may be subject to various limitations to avoid frequent updates and signaling burden for the network and/or the UE.
  • FIG. 10 illustrates a communications device 1000 that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated in FIG. 8.
  • the communications device 1000 includes a processing system 1002 coupled to a transceiver 1008 (e.g., a transmitter and/or a receiver) .
  • the transceiver 1008 is configured to transmit and receive signals for the communications device 1000 via an antenna 1010, such as the various signals as described herein.
  • the processing system 1002 may be configured to perform processing functions for the communications device 1000, including processing signals received and/or to be transmitted by the communications device 1000.
  • the processing system 1002 includes a processor 1004 coupled to a computer-readable medium/memory 1012 via a bus 1006.
  • the computer-readable medium/memory 1012 is configured to store instructions (e.g., computer-executable code) that when executed by the processor 1004, cause the processor 1004 to perform the operations illustrated in FIG. 4, or other operations for performing the various techniques discussed herein for adjusting frequency measurement rates.
  • computer-readable medium/memory 1012 stores code 1014 for negotiating, with a network entity, at least one applicable NSSAI list; code 1016 for sending the network entity a request for one or more NSSAI selected from the negotiated applicable NSSAI list; and code 1018 for receiving, from the network entity, an indication of at least one allowed NSSAI in response to the request.
  • the processor 1004 has circuitry configured to implement the code stored in the computer-readable medium/memory 1012.
  • the processor 1004 includes circuitry 1020 for negotiating, with a network entity, at least one applicable NSSAI list; circuitry 1022 for sending the network entity a request for one or more NSSAI selected from the negotiated applicable NSSAI list; and circuitry 1024 for receiving, from the network entity, an indication of at least one allowed NSSAI in response to the request.
  • FIG. 11 illustrates a communications device 1100 that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated in FIG. 9.
  • the communications device 1100 includes a processing system 1102 coupled to a transceiver 1108 (e.g., a transmitter and/or a receiver) .
  • the transceiver 1108 is configured to transmit and receive signals for the communications device 1100 via an antenna 1110, such as the various signals as described herein.
  • the processing system 1102 may be configured to perform processing functions for the communications device 1100, including processing signals received and/or to be transmitted by the communications device 1100.
  • the processing system 1102 includes a processor 1104 coupled to a computer-readable medium/memory 1112 via a bus 1106.
  • the computer-readable medium/memory 1112 is configured to store instructions (e.g., computer-executable code) that when executed by the processor 1104, cause the processor 1104 to perform the operations illustrated in FIG. 9, or other operations for performing the various techniques discussed herein for adjusting frequency measurement rates.
  • computer-readable medium/memory 1112 stores code 1114 for negotiating, with a UE, at least one applicable NSSAI list; code 1116 for receiving, from the UE, a request for one or more NSSAI selected from the negotiated applicable NSSAI list; and code 1118 for sending, to the UE, an indication of at least one allowed NSSAI in response to the request.
  • the processor 1104 has circuitry configured to implement the code stored in the computer-readable medium/memory 1112.
  • the processor 1104 includes circuitry 1120 for negotiating, with a UE, at least one applicable NSSAI list; circuitry 1122 for receiving, from the UE, a request for one or more NSSAI selected from the negotiated applicable NSSAI list; and circuitry 1124 for sending, to the UE, an indication of at least one allowed NSSAI in response to the request.
  • Embodiment 1 A method for wireless communications performed by a user equipment (UE) , comprising negotiating, with a network entity, at least one applicable network slice selection assistance information (NSSAI) list, sending the network entity a request for one or more NSSAI selected from the negotiated applicable NSSAI list, and receiving, from the network entity, an indication of at least one allowed NSSAI in response to the request.
  • NSSAI network slice selection assistance information
  • Embodiment 2 The method of Embodiment 1, wherein the negotiating comprises sending, to a network entity, a request for a network slice selection assistance information (NSSAI) list associated with an application, and receiving an NSSAI list indicating a plurality of slicing instances based on the request.
  • NSSAI network slice selection assistance information
  • Embodiment 3 The method of Embodiment 2, further comprising providing assistance information with the request for the NSSAI list.
  • Embodiment 4 The method of Embodiment 3, wherein the assistance information comprises at least one of: a list of one or more applications or one or more capabilities of the UE.
  • Embodiment 5 The method of Embodiment 3 or 4, wherein the slicing instances indicated in the NSSAI list comprise single NSSAIs (S-NSSAIs) associated with a tracking area or registration area limit.
  • S-NSSAIs single NSSAIs
  • Embodiment 6 The method of any of Embodiments 1-5, further comprising routing an application to at least one of the allowed NSSAI.
  • Embodiment 7 The method of any of Embodiments 1-6, wherein the UE is allowed to negotiate the at least one applicable network slice selection assistance information (NSSAI) list subject to limitations.
  • NSSAI network slice selection assistance information
  • Embodiment 8 A method for wireless communications performed by a network entity, comprising negotiating, with a UE, at least one applicable NSSAI list, receiving, from the UE, a request for one or more NSSAI selected from the negotiated applicable NSSAI list, and sending, to the UE, an indication of at least one allowed NSSAI in response to the request.
  • Embodiment 9 The method of Embodiment 8, wherein the negotiating comprises receiving, from the UE, a request for a NSSAI list associated with an application, and sending the UE an NSSAI list indicating a plurality of slicing instances based on the request.
  • Embodiment 10 The method of Embodiment 9, further comprising receiving assistance information with the request for the NSSAI list.
  • Embodiment 11 The method of Embodiment 10, wherein the assistance information comprises at least one of a list of one or more applications or one or more capabilities of the UE.
  • Embodiment 12 The method of Embodiment 10 or 11, wherein the slicing instances indicated in the NSSAI list comprise single NSSAIs (S-NSSAIs) associated with a tracking area or registration area limit.
  • S-NSSAIs single NSSAIs
  • Embodiment 13 The method of any of Embodiments 8-12, wherein the UE is allowed to negotiate the at least one applicable NSSAI list subject to limitations.
  • Embodiment 14 An apparatus for wireless communications, comprising means for negotiating, with a network entity, at least one applicable NSSAI list, means for sending the network entity a request for one or more NSSAI selected from the negotiated applicable NSSAI list, and means for receiving, from the network entity, an indication of at least one allowed NSSAI in response to the request.
  • Embodiment 15 An apparatus for wireless communications, comprising a memory and a at least one processor configured to negotiate, with a network entity, at least one applicable NSSAI list, send the network entity a request for one or more NSSAI selected from the negotiated applicable NSSAI list, and receive, from the network entity, an indication of at least one allowed NSSAI in response to the request.
  • Embodiment 16 A computer readable medium having instructions stored thereon for negotiating, with a network entity, at least one applicable NSSAI list, sending the network entity a request for one or more NSSAI selected from the negotiated applicable NSSAI list, and receiving, from the network entity, an indication of at least one allowed NSSAI in response to the request.
  • Embodiment 17 An apparatus for wireless communications, comprising means for negotiating, with a UE, at least one applicable NSSAI list, means for receiving, from the UE, a request for one or more NSSAI selected from the negotiated applicable NSSAI list, and means for sending, to the UE, an indication of at least one allowed NSSAI in response to the request.
  • Embodiment 18 An apparatus for wireless communications, comprising a memory and a at least one processor configured to negotiate, with a UE, at least one applicable NSSAI list, receive, from the UE, a request for one or more NSSAI selected from the negotiated applicable NSSAI list, and send, to the UE, an indication of at least one allowed NSSAI in response to the request.
  • Embodiment 19 A computer readable medium having instructions stored thereon for negotiating, with a UE, at least one applicable NSSAI list, receiving, from the UE, a request for one or more NSSAI selected from the negotiated applicable NSSAI list, and sending, to the UE, an indication of at least one allowed NSSAI in response to the request.
  • the methods disclosed herein comprise one or more steps or actions for achieving the methods.
  • the method steps and/or actions may be interchanged with one another without departing from the scope of the claims.
  • the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.
  • a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members.
  • “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c) .
  • determining encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure) , ascertaining and the like. Also, “determining” may include receiving (e.g., receiving information) , accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like.
  • the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions.
  • the means may include various hardware and/or software component (s) and/or module (s) , including, but not limited to a circuit, an application specific integrated circuit (ASIC) , or processor.
  • ASIC application specific integrated circuit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • PLD programmable logic device
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • an example hardware configuration may comprise a processing system in a wireless node.
  • the processing system may be implemented with a bus architecture.
  • the bus may include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints.
  • the bus may link together various circuits including a processor, machine-readable media, and a bus interface.
  • the bus interface may be used to connect a network adapter, among other things, to the processing system via the bus.
  • the network adapter may be used to implement the signal processing functions of the PHY layer.
  • a user interface e.g., keypad, display, mouse, joystick, etc.
  • a user interface e.g., keypad, display, mouse, joystick, etc.
  • the bus may also link various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further.
  • the processor may be implemented with one or more general-purpose and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Those skilled in the art will recognize how best to implement the described functionality for the processing system depending on the particular application and the overall design constraints imposed on the overall system.
  • the functions may be stored or transmitted over as one or more instructions or code on a computer readable medium.
  • Software shall be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • Computer-readable media include both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • the processor may be responsible for managing the bus and general processing, including the execution of software modules stored on the machine-readable storage media.
  • a computer-readable storage medium may be coupled to a processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor.
  • the machine-readable media may include a transmission line, a carrier wave modulated by data, and/or a computer readable storage medium with instructions stored thereon separate from the wireless node, all of which may be accessed by the processor through the bus interface.
  • the machine-readable media, or any portion thereof may be integrated into the processor, such as the case may be with cache and/or general register files.
  • Examples of machine- readable storage media may include, by way of example, RAM (Random Access Memory) , flash memory, ROM (Read Only Memory) , PROM (Programmable Read-Only Memory) , EPROM (Erasable Programmable Read-Only Memory) , EEPROM (Electrically Erasable Programmable Read-Only Memory) , registers, magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof.
  • the machine-readable media may be embodied in a computer-program product.
  • a software module may comprise a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media.
  • the computer-readable media may comprise a number of software modules.
  • the software modules include instructions that, when executed by an apparatus such as a processor, cause the processing system to perform various functions.
  • the software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices.
  • a software module may be loaded into RAM from a hard drive when a triggering event occurs.
  • the processor may load some of the instructions into cache to increase access speed.
  • One or more cache lines may then be loaded into a general register file for execution by the processor.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared (IR) , radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
  • Disk and disc include compact disc (CD) , laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.
  • computer-readable media may comprise non-transitory computer-readable media (e.g., tangible media) .
  • computer-readable media may comprise transitory computer-readable media (e.g., a signal) . Combinations of the above should also be included within the scope of computer-readable media.
  • certain aspects may comprise a computer program product for performing the operations presented herein.
  • a computer program product may comprise a computer-readable medium having instructions stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein.
  • modules and/or other appropriate means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or base station as applicable.
  • a user terminal and/or base station can be coupled to a server to facilitate the transfer of means for performing the methods described herein.
  • various methods described herein can be provided via storage means (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc. ) , such that a user terminal and/or base station can obtain the various methods upon coupling or providing the storage means to the device.
  • storage means e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.
  • CD compact disc
  • floppy disk etc.
  • any other suitable technique for providing the methods and techniques described herein to a device can be utilized.

Landscapes

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

Abstract

Des aspects de la présente divulgation portent sur les communications sans fil, et plus particulièrement, sur des améliorations de découpage en tranches de réseau et la configuration d'un équipement utilisateur pour une sélection de tranche de réseau. Un procédé donné à titre d'exemple des techniques décrites ici comprend généralement la négociation, avec une entité de réseau, d'au moins une liste d'informations d'aide à la sélection de tranches de réseau (NSSAI) applicable, l'envoi, à l'entité de réseau, d'une requête pour une ou plusieurs NSSAI sélectionnées à partir de la liste de NSSAI applicable négociée et la réception, à partir de l'entité de réseau, d'une indication d'au moins une NSSAI autorisée en réponse à la requête.
PCT/CN2020/115257 2020-09-15 2020-09-15 Négociation de nssai applicable à un équipement utilisateur WO2022056659A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/115257 WO2022056659A1 (fr) 2020-09-15 2020-09-15 Négociation de nssai applicable à un équipement utilisateur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/115257 WO2022056659A1 (fr) 2020-09-15 2020-09-15 Négociation de nssai applicable à un équipement utilisateur

Publications (1)

Publication Number Publication Date
WO2022056659A1 true WO2022056659A1 (fr) 2022-03-24

Family

ID=80777590

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/115257 WO2022056659A1 (fr) 2020-09-15 2020-09-15 Négociation de nssai applicable à un équipement utilisateur

Country Status (1)

Country Link
WO (1) WO2022056659A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114710789A (zh) * 2022-06-06 2022-07-05 浪潮通信技术有限公司 网络切片确定方法、装置及电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109391648A (zh) * 2017-08-04 2019-02-26 华为技术有限公司 一种应用与网络切片的关联方法、装置和通信系统
CN109565451A (zh) * 2018-11-15 2019-04-02 北京小米移动软件有限公司 网络切片的使用方法及装置
CN110167094A (zh) * 2018-02-12 2019-08-23 中兴通讯股份有限公司 一种路由选择方法、装置、设备、系统和存储介质
US20200113001A1 (en) * 2017-03-22 2020-04-09 Ntt Docomo, Inc. Information notification method and mobile communication system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200113001A1 (en) * 2017-03-22 2020-04-09 Ntt Docomo, Inc. Information notification method and mobile communication system
CN109391648A (zh) * 2017-08-04 2019-02-26 华为技术有限公司 一种应用与网络切片的关联方法、装置和通信系统
CN110167094A (zh) * 2018-02-12 2019-08-23 中兴通讯股份有限公司 一种路由选择方法、装置、设备、系统和存储介质
CN109565451A (zh) * 2018-11-15 2019-04-02 北京小米移动软件有限公司 网络切片的使用方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhancement of network slicing; Phase 2 (Release 17)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.700-40, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V0.4.0, 19 June 2020 (2020-06-19), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 143, XP051924078 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114710789A (zh) * 2022-06-06 2022-07-05 浪潮通信技术有限公司 网络切片确定方法、装置及电子设备

Similar Documents

Publication Publication Date Title
US11528603B2 (en) Access stratum security for efficient packet processing
US11160014B2 (en) Connection gateway selection in a mobile communications device
EP4115596B1 (fr) Contournement de système de noms de domaine (dns) pour l'informatique en périphérie
KR20140126727A (ko) 모바일 엔티티에 의한 백색 공간 동작을 위한 방법 및 장치
WO2021031060A1 (fr) Intervalle de planification pour équipement utilisateur multi-sim
EP4133766B1 (fr) Retardement de la mise à jour d'identifiant de capacité radio d'équipement utilisateur (urcid) pour eplmn
US20210385192A1 (en) Access to home operator services with separate wireless network
US20230308918A1 (en) Method and apparatus for transmitting and receiving data in wireless communication system
US20210099945A1 (en) Reduced overhead network slice selection assistance information (nssai) signaling
WO2022056659A1 (fr) Négociation de nssai applicable à un équipement utilisateur
CN115134888B (zh) 用于处理用户设备入网的用户设备和方法
WO2022011665A1 (fr) Découpage en tranches de réseau nssp/ursp et mise à jour de configuration locale d'ue
US20230141754A1 (en) Ensuring compatibility between network slice operating frequencies and user equipment (ue) radio capabilities
WO2022000129A1 (fr) Routage de tranchage multi-réseau pour des plmn doubles d'équipements utilisateurs de module d'identité d'abonné doubles
WO2022000106A1 (fr) Mise en évidence de découpage de réseau
WO2022000327A1 (fr) Amélioration de découpage de réseau
US12035229B2 (en) Slice-aware PLMN selection
US20210282084A1 (en) Slice-aware plmn selection
WO2022067623A1 (fr) Informations d'aide à la sélection unique d'une tranche de réseau (s-nssai) mappées pour des réseaux mobiles terrestres publics équivalents (eplmn)
WO2022036542A1 (fr) Sélection et resélection de cellule sensible à la tranche, basées sur des informations de système de diffusion

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20953520

Country of ref document: EP

Kind code of ref document: A1