[go: up one dir, main page]

WO2022040955A1 - Appareil et procédés pour la mise à jour de listes d'informations d'aide à la sélection de tranches de réseau - Google Patents

Appareil et procédés pour la mise à jour de listes d'informations d'aide à la sélection de tranches de réseau Download PDF

Info

Publication number
WO2022040955A1
WO2022040955A1 PCT/CN2020/111221 CN2020111221W WO2022040955A1 WO 2022040955 A1 WO2022040955 A1 WO 2022040955A1 CN 2020111221 W CN2020111221 W CN 2020111221W WO 2022040955 A1 WO2022040955 A1 WO 2022040955A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
nssai
applications
policy rules
list
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2020/111221
Other languages
English (en)
Inventor
Nan Zhang
Yongjun XU
Long HAN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
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 Inc filed Critical Qualcomm Inc
Priority to PCT/CN2020/111221 priority Critical patent/WO2022040955A1/fr
Publication of WO2022040955A1 publication Critical patent/WO2022040955A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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

Definitions

  • the present disclosure relates generally to wireless communication systems, and more particularly, to generating and updating network slice selection assistance information (NSSAI) lists.
  • NSSAI network slice selection assistance information
  • Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (for example, time, frequency, and power) .
  • Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems.
  • 4G systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems
  • 5G systems which may be referred to as New Radio (NR) systems.
  • a wireless multiple-access communications system may include a number of base stations or network access nodes, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE) .
  • UE user equipment
  • Some wireless communications systems may be packet-switched (PS) Internet Protocol (IP) networks so that the networks deliver data traffic in IP packets.
  • PS packet-switched
  • IP Internet Protocol
  • a user equipment (UE) join a network and a Packet Data Network (PDN) address may be assigned to the UE for connecting the UE to the PDN.
  • PDN Packet Data Network
  • a Protocol Data Unit (PDU) session defines the association between the UE and the data network that provides a PDU connectivity service. From Release 16, 3GPP, the UE may request proper network slicing instances during a registration procedure for initiating a PDU session.
  • a network slice may be logical network that provides specific network capabilities and network characteristics.
  • a network slice instance may be a set of network function instances and the requested resources (e.g., computing, storage, and networking resources) which form a deployed network slice.
  • a network slice may be a service type such as enhanced mobile broadband (eMBB) , ultra-reliable low latency communications (URLLC) , a massive internet of things (MIoT) , or the like.
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable low latency communications
  • MIoT massive internet of things
  • a method for wireless communication by a user equipment includes selecting an application of one or more applications stored in the UE, wherein the application is associated with a traffic descriptor of a plurality of traffic descriptors.
  • the method also includes generating a network slice selection assistance information (NSSAI) list including at least one single NSSAI (S-NSSAI) that is based on the application and the traffic descriptor.
  • the method further includes transmitting the NSSAI list to a base station.
  • NSSAI network slice selection assistance information
  • a user equipment includes a transceiver for wirelessly communicating with a base station.
  • the UE also includes one or more processors electronically coupled to the transceiver.
  • the one or more processors are configured to select an application of one or more applications stored in the UE, wherein the application is associated with a traffic descriptor of a plurality of traffic descriptors.
  • the one or more processors are also configured to generate a network slice selection assistance information (NSSAI) list including at least one single NSSAI (S-NSSAI) that is based on the application and the traffic descriptor.
  • the one or more processors are further configured to transmit the NSSAI list to a base station.
  • NSSAI network slice selection assistance information
  • a non-transitory, processor-readable storage medium, having instructions stored thereon is provided.
  • the instructions When the instructions are executed by a processing circuit, the instructions cause the processing circuit to select an application of one or more applications stored in the UE, wherein the application is associated with a traffic descriptor of a plurality of traffic descriptors.
  • the instructions When the instructions are executed by the processing circuit, the instructions also cause the processing circuit to generate a network slice selection assistance information (NSSAI) list including at least one single NSSAI (S-NSSAI) that is based on the application and the traffic descriptor.
  • NSSAI network slice selection assistance information
  • S-NSSAI single NSSAI
  • a user equipment includes a means for selecting an application of one or more applications stored in the UE, wherein the application is associated with a traffic descriptor of a plurality of traffic descriptors.
  • the UE also includes a means for generating a network slice selection assistance information (NSSAI) list including at least one single NSSAI (S-NSSAI) that is based on the application and the traffic descriptor.
  • NSSAI network slice selection assistance information
  • S-NSSAI single NSSAI
  • FIG. 1 is a diagram illustrating an example of a wireless communication system.
  • FIG. 2 is a conceptual illustration of an example of a radio access network.
  • FIG. 3 is a block diagram illustrating an example of a 5G wireless communication system (5GS) .
  • FIG. 4 is a conceptual illustration of an example wireless communication system for generating and updating network slice selection assistance information (NSSAI) lists in accordance with some aspects of the disclosure.
  • NSSAI network slice selection assistance information
  • FIG. 5 is a block diagram conceptually illustrating an example hardware implementation for a UE in accordance with some aspects of the disclosure.
  • FIG. 6 is a flow chart illustrating an example method performed at a UE for generating and updating network slice selection assistance information (NSSAI) lists in accordance with some aspects of the disclosure.
  • NSSAI network slice selection assistance information
  • FIG. 7 is a block diagram conceptually illustrating an example hardware implementation for a base station in accordance with some aspects of the disclosure.
  • FIG. 8 is a flow chart illustrating an example method performed at a base station for generating and updating network slice selection assistance information (NSSAI) lists in accordance with some aspects of the disclosure.
  • NSSAI network slice selection assistance information
  • FIG. 9 is a block diagram conceptually illustrating an example hardware implementation for an AMF in accordance with some aspects of the disclosure.
  • FIG. 10 is a flow chart illustrating an example method performed at an AMF for generating and updating network slice selection assistance information (NSSAI) lists in accordance with some aspects of the disclosure.
  • NSSAI network slice selection assistance information
  • one or more wireless devices may seek to receive one or more unicast services or one or more multicast or broadcast services (hereinafter referred to collectively as “multicast broadcast services” ) .
  • a unicast transmission is a transmission from a single point in the network (for example, a base station) to another single point in the network (for example, a user equipment (UE) ) .
  • a multicast or broadcast transmission (hereinafter referred to collectively as a “multicast broadcast transmission ” ) is a single point to multi-point transmission, such as from a base station to a group of UEs in a cell of the base station.
  • a base station may provide unicast services to multiple UEs via individual unicast transmissions to the respective UEs as well as multicast broadcast services to a group of UEs via multicast broadcast transmissions to the group of UEs.
  • networks may be packet-switched (PS) Internet Protocol (IP) networks so that the networks deliver data traffic in IP packets.
  • PS Internet Protocol
  • IP Internet Protocol
  • a user equipment (UE) join a network and a Packet Data Network (PDN) address may be assigned to the UE for connecting the UE to the PDN.
  • PDN Packet Data Network
  • a Protocol Data Unit (PDU) session defines the association between the UE and the data network that provides a PDU connectivity service.
  • the UE may request proper network slicing instances during a registration procedure for initiating a PDU session.
  • a network slice may be logical network that provides specific network capabilities and network characteristics.
  • a network slice instance may be a set of network function instances and the required resources (e.g., computing, storage, and networking resources) which form a deployed network slice.
  • a network slice may be a service type such as enhanced mobile broadband (eMBB) , ultra-reliable low latency communications (URLLC) , a massive internet of things (MIoT) , or the like.
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable low latency communications
  • MIoT massive internet of things
  • hundreds of different network slicing instances may be included within a particular public land mobile network (PLMN) .
  • a UE supporting as many as eight (8) network slicing instances, may request proper network slicing instances during a registration procedure (e.g., an RRCSetupComplete message) .
  • a UE may transmit a requested network slice selection assistance information (NSSAI) list to the network during registration and in response receive an allowed NSSAI list.
  • NSSAI network slice selection assistance information
  • Network slicing is application-centric instead of UE-centric such that an application knows which network slicing type is needed to run the application, but the UE may not.
  • the UE may generate and update NSSAI lists to maintain the proper list for commercialization on the UE.
  • the UE may request proper network slicing, for example, in response to establishing connection with a new PLMN, at one or more time intervals, after initiating use of a new application, when an application stored on the UE changes a use rank relative to one or more other applications stored on the UE, or the like.
  • the described techniques can be used to monitor or improve the reliability of providing multicast broadcast services via feedback from a group of UEs while maintaining quality of service and reducing congestion. For example, by delaying the transmission of an access request message, by a UE seeking multicast broadcast services to a base station providing the multicast broadcast services, the base station may more efficiently or effectively obtain feedback for improving the reliability or quality of multicast broadcast services while preventing an overload condition.
  • Implementations may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations.
  • devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described embodiments.
  • transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (for example, hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor (s) , interleaver, adders/summers, etc. ) .
  • innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, or the like of varying sizes, shapes, and constitution.
  • the various concepts presented throughout this disclosure may be implemented across a broad variety of telecommunication systems, network architectures, and communication standards.
  • the wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106.
  • the UE 106 may be enabled to carry out data communication with an external data network 110, such as (but not limited to) the Internet.
  • the RAN 104 may implement any suitable wireless communication technology or technologies to provide radio access to the UE 106.
  • the RAN 104 may operate according to 3rd Generation Partnership Project (3GPP) New Radio (NR) specifications, often referred to as 5G.
  • 3GPP 3rd Generation Partnership Project
  • NR New Radio
  • the RAN 104 may operate under a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, often referred to as Long-Term Evolution (LTE) .
  • eUTRAN Evolved Universal Terrestrial Radio Access Network
  • LTE Long-Term Evolution
  • the 3GPP refers to this hybrid RAN as a next-generation RAN, or NG-RAN.
  • NG-RAN next-generation RAN
  • the RAN 104 includes a plurality of base stations 108 (e.g., a RAN entity, RAN node, or the like) .
  • a base station is a network element in a radio access network responsible for radio transmission and reception in one or more cells to or from a UE.
  • a base station may variously be referred to by those skilled in the art as a base transceiver station (BTS) , a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , an access point (AP) , a Node B (NB) , an eNode B (eNB) , a gNode B (gNB) , or some other suitable terminology.
  • BTS basic service set
  • ESS extended service set
  • AP access point
  • NB Node B
  • eNB eNode B
  • gNB gNode B
  • the radio access network 104 is further illustrated supporting wireless communication for multiple mobile apparatuses.
  • a mobile apparatus may be referred to as user equipment (UE) in 3GPP standards, but may also be referred to by those skilled in the art as a mobile station (MS) , a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT) , a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology.
  • a UE may be an apparatus that provides a user with access to network services.
  • a “mobile” apparatus need not necessarily have a capability to move and may be stationary.
  • the term mobile apparatus or mobile device broadly refers to a diverse array of devices and technologies.
  • UEs may include a number of hardware structural components sized, shaped, and arranged to help in communication; such components can include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. electrically coupled to each other.
  • a mobile apparatus examples include a mobile, a cellular (cell) phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal computer (PC) , a notebook, a netbook, a smartbook, a tablet, a personal digital assistant (PDA) , and a broad array of embedded systems, e.g., corresponding to an “Internet of Things” (IoT) .
  • IoT Internet of Things
  • a mobile apparatus may additionally be an automotive or other transportation vehicle, a remote sensor or actuator, a robot or robotics device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-copter, a quad-copter, a remote control device, a consumer and/or wearable device, such as eyewear, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., MP3 player) , a camera, a game console, etc.
  • GPS global positioning system
  • a mobile apparatus may additionally be a digital home or smart home device such as a home audio, video, and/or multimedia device, an appliance, a vending machine, intelligent lighting, a home security system, a smart meter, etc.
  • a mobile apparatus may additionally be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device controlling electric power (e.g., a smart grid) , lighting, water, etc.; an industrial automation and enterprise device; a logistics controller; agricultural equipment; military defense equipment, vehicles, aircraft, ships, and weaponry, etc.
  • a mobile apparatus may provide for connected medicine or telemedicine support, i.e., health care at a distance.
  • Telehealth devices may include telehealth monitoring devices and telehealth administration devices, whose communication may be given preferential treatment or prioritized access over other types of information, e.g., in terms of prioritized access for transport of critical service data, and/or relevant QoS for transport of critical service data.
  • Wireless communication between a RAN 104 and a UE 106 may be described as utilizing an air interface.
  • Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) may be referred to as downlink (DL) transmission.
  • DL downlink
  • the term downlink may refer to a point-to-multipoint transmission originating at a scheduling entity (described further below; e.g., base station 108) .
  • Another way to describe this scheme may be to use the term broadcast channel multiplexing.
  • Uplink Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) may be referred to as uplink (UL) transmissions.
  • UL uplink
  • the term uplink may refer to a point-to-point transmission originating at a scheduled entity (described further below; e.g., UE 106) .
  • a scheduling entity e.g., a base station 108 allocates resources for communication among some or all devices and equipment within its service area or cell.
  • the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communication, UEs 106, which may be scheduled entities, may utilize resources allocated by the scheduling entity 108.
  • Base stations 108 are not the only entities that may function as scheduling entities. That is, in some examples, a UE may function as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs) .
  • a scheduling entity 108 may broadcast downlink traffic 112 to one or more scheduled entities 106.
  • the scheduling entity 108 is a node or device responsible for scheduling traffic in a wireless communication network, including the downlink traffic 112 and, in some examples, uplink traffic 116 from one or more scheduled entities 106 to the scheduling entity 108.
  • the scheduled entity 106 is a node or device that receives downlink control information 114, including but not limited to scheduling information (e.g., a grant) , synchronization or timing information, or other control information from another entity in the wireless communication network such as the scheduling entity 108.
  • the uplink and/or downlink control information and/or traffic information may be time-divided into frames, subframes, slots, and/or symbols.
  • a symbol may refer to a unit of time that, in an orthogonal frequency division multiplexed (OFDM) waveform, carries one resource element (RE) per sub-carrier.
  • a slot may carry 7 or 14 OFDM symbols.
  • a subframe may refer to a duration of 1ms. Multiple subframes or slots may be grouped together to form a single frame or radio frame.
  • OFDM orthogonal frequency division multiplexed
  • a slot may carry 7 or 14 OFDM symbols.
  • a subframe may refer to a duration of 1ms. Multiple subframes or slots may be grouped together to form a single frame or radio frame.
  • these definitions are not required, and any suitable scheme for organizing waveforms may be utilized, and various time divisions of the waveform may have any suitable duration.
  • base stations 108 may include a backhaul interface for communication with a backhaul portion 120 of the wireless communication system.
  • the backhaul 120 may provide a link between a base station 108 and the core network 102.
  • a backhaul network may provide interconnection between the respective base stations 108.
  • Various types of backhaul interfaces may be employed, such as a direct physical connection, a virtual network, or the like using any suitable transport network.
  • the core network 102 may be a part of the wireless communication system 100, and may be independent of the radio access technology used in the RAN 104.
  • the core network 102 may be configured according to 5G standards (e.g., 5GC) .
  • the core network 102 may be configured according to a 4G evolved packet core (EPC) , or any other suitable standard or configuration.
  • 5G standards e.g., 5GC
  • EPC 4G evolved packet core
  • the 5GS 200 may be the same wireless communication system 100 described above and illustrated in FIG. 1.
  • the 5GS 200 includes a user equipment (UE) 202, a NR-RAN 204, and a core network 206.
  • the UE 202 may be enabled to carry out data communication with an external data network 214, such as (but not limited to) the Internet or an Ethernet network.
  • the core network 206 may include, for example, an access and mobility management function (AMF) 208, a session management function (SMF) 210, and a user plane function (UPF) 212.
  • the AMF 208 and SMF 210 employ control plane (e.g., Non Access Stratum (NAS) ) signaling to perform various functions related to mobility management and session management for the UE 202.
  • control plane e.g., Non Access Stratum (NAS)
  • NAS Non Access Stratum
  • the AMF 208 provides connectivity, mobility management and authentication of the UE 202
  • the SMF 210 provides session management of the UE 202 (e.g., processes signaling related to protocol data unit (PDU) sessions between the UE 202 and the external DN 214) .
  • the UPF 212 provides user plane connectivity to route 5G (NR) packets to/from the UE 202 via the NR-RAN 204.
  • NR 5G
  • the core network 206 may further include other functions, such as a policy control function (PCF) 216, authentication server function (AUSF) 218, unified data management (UDM) 220, network slice selection function (NSSF) 222, and other functions (not illustrated, for simplicity) .
  • the PCF 216 provides policy information (e.g., rules) for control plane functions, such as network slicing, roaming, and mobility management.
  • policy information e.g., rules
  • control plane functions such as network slicing, roaming, and mobility management.
  • QoS 5G quality of service
  • the AUSF 218 performs authentication of UEs 202.
  • the UDM 220 facilitates generation of authentication and key agreement (AKA) credentials, performs user identification and manages subscription information and UE context.
  • AKA authentication and key agreement
  • the NSSF 222 redirects traffic to a network slice.
  • Network slices may be defined, for example, for different classes of subscribers or use cases, such as smart home, Internet of Things (IoT) , connected car, smart energy grid, etc.
  • IoT Internet of Things
  • Each use case may receive a unique set of optimized resources and network topology (e.g., a network slice) to meet the connectivity, speed, power, and capacity requirements of the use case.
  • the UE 202 may transmit a registration request and PDU session establishment request to the 5G core network 206 via the NR-RAN 204.
  • the AMF 208 and SMF 210 may process the registration request and PDU session establishment request and establish a data network session (DNS) between the UE 202 and the external DN 214 via the UPF 212.
  • DNS may include one or more sessions (e.g., data sessions or data flows) and may be served by multiple UPFs 212 (only one of which is shown for convenience) . Examples of data flows include, but are not limited to, IP flows, Ethernet flows and unstructured data flows.
  • the RAN 300 may be the same as the RAN 104 described above and illustrated in FIG. 1 and/or the NR-RAN 204 described above and illustrated in FIG. 2.
  • the geographic area covered by the RAN 300 may be divided into cellular regions (cells) that can be uniquely identified by a user equipment (UE) based on an identification broadcasted from one access point or base station.
  • FIG. 3 illustrates macrocells 302, 304, and 306, and a small cell 308, each of which may include one or more sectors (not shown) .
  • a sector is a sub-area of a cell. All sectors within one cell are served by the same base station.
  • a radio link within a sector can be identified by a single logical identification belonging to that sector.
  • the multiple sectors within a cell can be formed by groups of antennas with each antenna responsible for communication with UEs in a portion of the cell.
  • FIG. 3 two base stations 310 and 312 are shown in cells 302 and 304; and a third base station 314 is shown controlling a remote radio head (RRH) 316 in cell 306. That is, a base station can have an integrated antenna or can be connected to an antenna or RRH by feeder cables.
  • the cells 302, 304, and 306 may be referred to as macrocells, as the base stations 310, 312, and 314 support cells having a large size.
  • a base station 318 is shown in the small cell 308 (e.g., a microcell, picocell, femtocell, home base station, home Node B, home eNode B, etc.
  • the cell 308 may be referred to as a small cell, as the base station 318 supports a cell having a relatively small size.
  • Cell sizing can be done according to system design as well as component constraints.
  • the radio access network 300 may include any number of wireless base stations and cells. Further, a relay node may be deployed to extend the size or coverage area of a given cell.
  • the base stations 310, 312, 314, 318 provide wireless access points to a core network for any number of mobile apparatuses. In some examples, the base stations 310, 312, 314, and/or 318 may be the same as the base station/scheduling entity 108 described above and illustrated in FIG. 1.
  • the cells may include UEs that may be in communication with one or more sectors of each cell.
  • each base station 310, 312, 314, and 318 may be configured to provide an access point to a core network (e.g., as illustrated in FIG. 1 and/or 2) for all the UEs in the respective cells.
  • UEs 322 and 324 may be in communication with base station 310;
  • UEs 326 and 328 may be in communication with base station 312;
  • UEs 330 and 332 may be in communication with base station 314 by way of RRH 316; and
  • UE 334 may be in communication with base station 318.
  • the UEs 322, 324, 326, 328, 330, 332, 334, 338, 340, and/or 342 may be the same as the UE/scheduled entity 106 described above and illustrated in FIG. 1 and/or the UE 202 described above and illustrated in FIG. 2.
  • an unmanned aerial vehicle (UAV) 320 which may be a drone or quadcopter, can be a mobile network node and may be configured to function as a UE.
  • the UAV 320 may operate within cell 302 by communicating with base station 310.
  • the ability for a UE to communicate while moving, independent of its location, is referred to as mobility.
  • the various physical channels between the UE and the radio access network are generally set up, maintained, and released under the control of the AMF 208, illustrated in FIG. 2.
  • a RAN 300 may utilize DL-based mobility or UL-based mobility to enable mobility and handovers (i.e., the transfer of a UE’s connection from one radio channel to another) .
  • a UE may monitor various parameters of the signal from its serving cell as well as various parameters of neighboring cells. Depending on the quality of these parameters, the UE may maintain communication with one or more of the neighboring cells.
  • the UE may undertake a handoff or handover from the serving cell to the neighboring (target) cell.
  • UE 324 illustrated as a vehicle, although any suitable form of UE may be used
  • the UE 324 may transmit a reporting message to its serving base station 310 indicating this condition.
  • the UE 324 may receive a handover command, and the UE may undergo a handover to the cell 306.
  • UL reference signals from each UE may be utilized by the network to select a serving cell for each UE.
  • the base stations 310, 312, and 314/316 may broadcast unified synchronization signals (e.g., unified Primary Synchronization Signals (PSSs) , unified Secondary Synchronization Signals (SSSs) and unified Physical Broadcast Channels (PBCH) ) .
  • PSSs Primary Synchronization Signals
  • SSSs unified Secondary Synchronization Signals
  • PBCH Physical Broadcast Channels
  • the UEs 322, 324, 326, 328, 330, and 332 may receive the unified synchronization signals, derive the carrier frequency and slot timing from the synchronization signals, and in response to deriving timing, transmit an uplink pilot or reference signal.
  • the uplink pilot signal transmitted by a UE may be concurrently received by two or more cells (e.g., base stations 310 and 314/316) within the radio access network 300.
  • Each of the cells may measure a strength of the pilot signal, and the radio access network (e.g., one or more of the base stations 310 and 314/316 and/or a central node within the core network) may determine a serving cell for the UE 324.
  • the radio access network e.g., one or more of the base stations 310 and 314/316 and/or a central node within the core network
  • the network may continue to monitor the uplink pilot signal transmitted by the UE 324.
  • the network 300 may handover the UE 324 from the serving cell to the neighboring cell, with or without informing the UE 324.
  • the synchronization signal transmitted by the base stations 310, 312, and 314/316 may be unified, the synchronization signal may not identify a particular cell, but rather may identify a zone of multiple cells operating on the same frequency and/or with the same timing.
  • the use of zones in 5G networks or other next generation communication networks enables the uplink-based mobility framework and improves the efficiency of both the UE and the network, since the number of mobility messages that need to be exchanged between the UE and the network may be reduced.
  • the air interface in the radio access network 300 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum.
  • Licensed spectrum provides for exclusive use of a portion of the spectrum, generally by virtue of a mobile network operator purchasing a license from a government regulatory body.
  • Unlicensed spectrum provides for shared use of a portion of the spectrum without need for a government-granted license. While compliance with some technical rules is generally still required to access unlicensed spectrum, generally, any operator or device may gain access.
  • Shared spectrum may fall between licensed and unlicensed spectrum, wherein technical rules or limitations may be required to access the spectrum, but the spectrum may still be shared by multiple operators and/or multiple RATs.
  • the holder of a license for a portion of licensed spectrum may provide licensed shared access (LSA) to share that spectrum with other parties, e.g., with suitable licensee-determined conditions to gain access.
  • LSA licensed shared access
  • the air interface in the radio access network 300 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of the various devices.
  • 5G NR specifications provide multiple access for UL transmissions from UEs 322 and 324 to base station 310, and for multiplexing for DL transmissions from base station 310 to one or more UEs 322 and 324, utilizing orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) .
  • OFDM orthogonal frequency division multiplexing
  • CP cyclic prefix
  • 5G NR specifications provide support for discrete Fourier transform-spread-OFDM (DFT-s-OFDM) with a CP (also referred to as single-carrier FDMA (SC-FDMA) ) .
  • DFT-s-OFDM discrete Fourier transform-spread-OFDM
  • SC-FDMA single-carrier FDMA
  • multiplexing and multiple access are not limited to the above schemes, and may be provided utilizing time division multiple access (TDMA) , code division multiple access (CDMA) , frequency division multiple access (FDMA) , sparse code multiple access (SCMA) , resource spread multiple access (RSMA) , or other suitable multiple access schemes.
  • multiplexing DL transmissions from the base station 310 to UEs 322 and 324 may be provided utilizing time division multiplexing (TDM) , code division multiplexing (CDM) , frequency division multiplexing (FDM) , orthogonal frequency division multiplexing (OFDM) , sparse code multiplexing (SCM) , or other suitable multiplexing schemes.
  • the air interface in the radio access network 300 may further utilize one or more duplexing algorithms.
  • Duplex refers to a point-to-point communication link where both endpoints can communicate with one another in both directions.
  • Full duplex means both endpoints can simultaneously communicate with one another.
  • Half duplex means only one endpoint can send information to the other at a time.
  • a full duplex channel generally relies on physical isolation of a transmitter and receiver, and suitable interference cancellation technologies.
  • Full duplex emulation is frequently implemented for wireless links by utilizing frequency division duplex (FDD) or time division duplex (TDD) .
  • FDD frequency division duplex
  • TDD time division duplex
  • transmissions in different directions operate at different carrier frequencies.
  • TDD transmissions in different directions on a given channel are separated from one another using time division multiplexing. That is, at some times the channel is dedicated for transmissions in one direction, while at other times the channel is dedicated for transmissions in the other direction, where the direction may change very rapidly, e.g.,
  • sidelink or device-to-device (D2D) signals 327 may be communicated directly between UEs on resources allocated by a base station 312 for sidelink or D2D communication.
  • the sidelink or D2D signals 327 include one or more of sidelink/D2D traffic and sidelink/D2D control.
  • two or more UEs e.g., UEs 326 and 328
  • a UE may function as a scheduling entity to schedule D2D or sidelink signals 327 on the network-allocated resources in a D2D, vehicle-to-vehicle (V2V) , or vehicle-to-everything (V2X) network.
  • a scheduling entity e.g., a UE 326
  • one or more scheduled entities e.g., one or more other UEs 328
  • 5GS networks may be packet-switched (PS) Internet Protocol (IP) networks so that the networks deliver data traffic in IP packets.
  • PS Internet Protocol
  • IP Internet Protocol
  • a user equipment (UE) join a network and a Packet Data Network (PDN) address may be assigned to the UE for connecting the UE to the PDN.
  • PDN Packet Data Network
  • a Protocol Data Unit (PDU) session defines the association between the UE and the data network that provides a PDU connectivity service. From Release 16, 3GPP, the UE may request proper network slicing instances during a registration procedure for initiating a PDU session.
  • a network slice may be logical network that provides specific network capabilities and network characteristics.
  • a network slice instance may be a set of network function instances and the requested resources (e.g., computing, storage, and networking resources) which form a deployed network slice.
  • a network slice may be a service type such as enhanced mobile broadband (eMBB) , ultra-reliable low latency communications (URLLC) ,
  • hundreds of different network slicing instances may be included within a particular public land mobile network (PLMN) .
  • a UE supporting as many as eight (8) network slicing instances, may request proper network slicing instances during a registration procedure (e.g., an RRCSetupComplete message) .
  • a UE may transmit a requested network slice selection assistance information (NSSAI) list to the network during registration and in response receive an allowed NSSAI list.
  • NSSAI network slice selection assistance information
  • Network slicing is application-centric instead of UE-centric such that an application knows which network slicing type is needed to run the application, but the UE may not.
  • the UE may generate and update NSSAI lists to maintain the proper list for commercialization on the UE.
  • the UE may request proper network slicing, for example, in response to establishing connection with a new PLMN, at one or more time intervals, after initiating use of a new application, when an application stored on the UE changes a use rank relative to one or more other applications stored on the UE, or the like.
  • the UE may store one or more applications in the UE.
  • the UE may then collect one or more use-statistics associated with each of the one or more applications stored in the UE.
  • the UE may rank each application of the one or more applications based on the one or more use-statistics.
  • the UE may rank each application of the one or more applications according to a recency of use among each of the one or more applications.
  • the UE may then select an application of the one or more applications stored in the UE based on a rank of the application.
  • the UE may generate a network slice selection assistance information (NSSAI) list including at least one single NSSAI (S-NSSAI) that is based on the application the associated traffic descriptor.
  • NSSAI network slice selection assistance information
  • the UE may store a plurality of sets of policy rules in the UE, where each set of policy rules of the plurality of sets of policy rules comprises a traffic descriptor, match a traffic descriptor from one set of policy rules of the plurality of sets of policy rules with the traffic descriptor associated with the application, select the set of policy rules identifying the traffic descriptor that matches the traffic descriptor associated with the application, and generate at least one S-NSSAI including an identification of the application and the selected set of policy rules.
  • Each S-NSSAI may be representative of or associated with a network slice, discuss herein.
  • the NSSAI list may include up to eight (8) S-NSSAIs in accordance with TS38.300.16.3.1 and TS23.501.5.15.2.1.
  • the UE may transmit the NSSAI list to the base station.
  • the base station may receive the NSSAI list and transmit the NSSAI list to an AMF.
  • the AMF may select at least one of a serving AMF, one or more network slices, or one or more network slice instances based on the S-NSSAI contained in the NSSAI and transmit an indication of the selection to the base station.
  • the base station may receive the indication of the selection of at least one of a serving AMF, one or more network slices, or one or more network slice instances based on the S-NSSAI contained in the NSSAI and transmit an approved NSSAI list to the UE.
  • the UE and the base station may then establish a protocol data unity (PDU) session.
  • PDU protocol data unity
  • FIG. 4 is a conceptual illustration of an example wireless communication system 400 for generating and updating network slice selection assistance information (NSSAI) lists in accordance with some aspects of the disclosure.
  • Wireless communication networks may include a user equipment (UE) 402, a base station 404, and a AMF 406 and may be configured for generating and updating network slice selection assistance information (NSSAI) lists.
  • UE user equipment
  • base station 404 base station
  • AMF 406 AMF
  • the UE 402 may store one or more applications in the UE 402.
  • one or more application may have been stored on the UE 402 before an initial use of the UE.
  • a user of the UE 402 may have downloaded and stored the one or more applications on the UE after an initial use.
  • Application may include, for example, a NETFLIX TM application, a WECHAT TM application, a BLIBLI TM application, an OFFICE TM application, or the like.
  • each of the one or more applications may be associated with a traffic descriptor of a plurality of traffic descriptors.
  • a traffic descriptor may be information associated with a particular application that, when provided to a network, such as an AMF (e.g., AMF 406) , informs the network of the particular kind of traffic that the application utilizes and the performance requirements of that traffic.
  • a traffic descriptors may include a requested service type, one or more traffic parameters of each data flow in both directions, and quality of service (QoS) parameters requested in each direction.
  • services types may include constant bit rate (CBR) , real-time variable bit rate (rt-VBR) , non-real-time variable bit rate (nrt-VBR) , available bit rate (ABR) , and unspecified bit rate (UBR) .
  • CBR constant bit rate
  • rt-VBR real-time variable bit rate
  • nrt-VBR non-real-time variable bit rate
  • ABR available bit rate
  • UBR unspecified bit rate
  • traffic parameters may include peak cell rate (PCR) , sustainable cell rate (SCR) , maximum burst size (MBS) , and minimum cell rate (MCR) .
  • QoS parameters may include cell transfer delay (CTD) , peak-to-peak cell delay variation (CDV) , and cell loss ratio (CLR) .
  • the UE 402 may collect one or more use-statistics associated with each of the one or more applications.
  • the UE 402 may determine an amount of a time that each application is used. For example, the UE 402 may determine a total amount of time that each application has been used on the UE 402. As another example, the UE 402 may determine the average amount of time that each application is used over a predetermined time period (e.g., a day, a week, a month, a year, or the like) .
  • the UE 402 may determine a recency of use of each of the one or more applications. For example, the UE 402 may determine which applications were most recently used. In some cases, when the UE 402 has not been used, the UE 402 may determine that each of the one or more applications have not been used and assign a default use statistic to each of the one or more applications.
  • the UE 402 may rank each application of the one or more applications based on the one or more use-statistics. In some cases, the UE 402 may rank each application of the one or more applications according to a total amount of time that each applications is used. For example, the UE 402 may assign a highest rank to a first application that has been used the most, a second highest rank to a second application that has been used less than only the first application, and a lowest rank to a third application that has been used the least of all of the other one or more applications. In some cases, the UE 402 may rank each application of the one or more applications according to an averaged amount of time that each applications is used over a predetermined period of time.
  • the UE 402 may assign a highest rank to a first application that has a highest averaged amount of use time over the predetermined time, a second highest rank to a second application that has an averaged amount of use time over the predetermined time that is less than only the first application, and a lowest rank to a third application that has an averaged amount of use time over the predetermined time that is less than all of the other one or more applications.
  • the UE 402 may rank each application of the one or more applications according to a recency of use among each of the one or more applications. For example, the UE 402 may assign a highest rank to a first application that was most recently used, a second highest rank to a second application that was used most recently relative to every other application of the one or more applications except the first application, and a lowest rank to a third application that was last used at a time before all of the other one or more applications were used. In some cases, when the UE 402 has not been used, and thus none of the one or more applications have been used, the UE 402 may assign a same rank or a default rank to each of the one or more applications.
  • the UE 402 may select an application of the one or more applications stored in the UE based on a rank of the application. In some cases, the UE 402 may select at least one application of the one or more applications having a rank above a minimum threshold rank. For example, the UE 402 may select only the highest-ranking application of the one or more applications. As another example, the UE 402 may select the eight (8) highest ranking applications (e.g., a top eight (8) ) of the one or more applications.
  • the eight (8) highest ranking applications e.g., a top eight (8)
  • the UE 402 when the UE 402 can select a threshold quantity of applications based on rank, but the quantity of applications that have a use statistic and a rank (i.e., not default rank) is below the threshold quantity, the UE 402 may select only those applications that have a rank (i.e., not default rank) . In some cases, when the UE 402 can select a threshold quantity of applications based on rank, but the quantity of applications that have a use statistic and a rank (i.e., not default rank) is below the threshold quantity, the UE 402 may select those applications that have a rank (i.e., not default rank) and one or more default applications so that the quantity of selected applications meet the threshold quantity. In some cases, when the UE 402 has not been used, and thus none of the one or more applications have been used, the UE 402 may select one or more default applications of the one or more applications.
  • the UE 402 may generate a network slice selection assistance information (NSSAI) list including at least one single NSSAI (S-NSSAI) that is based on the application the associated traffic descriptor. For example, after the UE 402 selects at least one application of the one or more applications, the UE 402 may generate a network slice selection assistance information (NSSAI) list including at least one single NSSAI (S-NSSAI) that is based on the at least one selected application and each traffic descriptor associated with each application. In some cases, for example, when the UE 402 has not been used, and thus none of the one or more applications have been used, the UE 402 may generate a default NSSAI list. The default NSSAI list be including one or more S-NSSAIs that are associated with a predetermined set of one or more applications.
  • NSSAI network slice selection assistance information
  • generating an NSSAI list may include storing a plurality of sets of policy rules in the UE 402, where each set of policy rules of the plurality of sets of policy rules comprises a traffic descriptor.
  • the UE 402 may search for and record or store a plurality of UE route selection policy (URSP) rules and/or a plurality of network slice selection policy (NSSP) rules.
  • URSP UE route selection policy
  • NSSP network slice selection policy
  • the plurality of sets of policy rules stored in the UE may include at least one of one or more sets of policy rules configured by the UE or one or more sets of policy rules received from the base station.
  • generating an NSSAI list may include matching a traffic descriptor from one set of policy rules of the plurality of sets of policy rules with the traffic descriptor associated with the application. For example, after storing a plurality of URSP rules and/or a plurality of NSSP rules, the UE 402 may match a traffic descriptor contained in a URSP rule of the plurality of USRP rules or contained in an NSSP rule of the plurality of NSSP rules with a traffic descriptor associated with a selected application.
  • generating an NSSAI list may include selecting the set of policy rules identifying the traffic descriptor that matches the traffic descriptor associated with the application. For example, after matching a traffic descriptor contained in a URSP rule of the plurality of URSP rules or contained in an NSSP rule of the plurality of NSSP rules with a traffic descriptor associated with a selected application, the UE 402 may select the URSP rule and/or the NSSP rule having the traffic descriptor that matches the traffic descriptor associated with the selected application. Additionally, or alternatively, generating an NSSAI list may include generating at least one S-NSSAI including an identification of the application and the selected set of policy rules.
  • the UE 402 may generate an NSSAI list including at least one S-NSSAI.
  • the UE 402 may generate the S-NSSAI for inclusion in the NSSAI list and using an identification of the selected application and the selected set of policy rules.
  • Each S-NSSAI may be representative of or associated with a network slice, discuss herein.
  • the NSSAI list may include up to eight (8) S-NSSAIs in accordance with TS38.300.16.3.1 and TS23.501.5.15.2.1.
  • the UE 402 transmits the NSSAI list to the base station 404.
  • the UE 402 may transmit a requested NSSAI list to the base station 404.
  • the base station 404 transmits the NSSAI list to the AMF 406.
  • the base station 404 may transmit the requested NSSAI list to an AMF 406 associated with the base station 404.
  • the AMF 406 selects at least one of a serving AMF, one or more network slices, or one or more network slice instances based on the S-NSSAI contained in the NSSAI.
  • the AMF 406 may determine that the AMF 406 itself has the appropriate network slicing instance and/or is associated with the appropriate network slice for one or more applications identified by the S-NSSAIs in the NSSAI and select the AMF 406 itself for providing network slicing instances. As another example, the AMF 406 may determine that another AMF has the appropriate network slicing instance and/or is associated with the appropriate network slice for one or more applications identified by the S-NSSAIs in the NSSAI and select the other AMF for providing network slicing instances. As yet another example, the AMF 406 may identify one or more network slices and select appropriate network slices for one or more applications identified by the S-NSSAIs in the NSSAI.
  • the AMF 406 may identify one or more network slice instances and select appropriate network slice instances for one or more applications identified by the S-NSSAIs in the NSSAI.
  • the AMF 406 may determine a serving AMF, a network slice, and/or a network slice instance for each S-NSSAI and thus for each application selected by the UE.
  • the base station 404 receives an indication of a selection of at least one of a serving AMF, one or more network slices, or one or more network slice instances based on the S-NSSAI contained in the NSSAI.
  • the base station 404 may receive the indication of the selection of at least one of the serving AMF, one or more network slices, or one or more network slicing instances and determine that the requested NSSAI list is an approved NSSAI list.
  • the base station may transmit the selection of at least one of a serving AMF, one or more network slices, or one or more network slice instances based on the S-NSSAI contained in the NSSAI, and thus for each application selected by the UE.
  • the base station 404 transmits an approved NSSAI list to the UE 402. For example, in response to receiving the indication of a selection of at least one of the serving AMF, one or more network slices, or one or more network slicing instances and determining that the requested NSSAI list is an approved NSSAI list, the base station 404 may transmit the approved NSSAI to the UE 402.
  • the UE 402 and the base station 404 establish a protocol data unit (PDU) session. For example, the UE 402 and the base station 404 may establish a PDU session for each application selected by the UE.
  • PDU protocol data unit
  • system 400 including the UE 402, the base station 404, and the AMF 406 may implement any one or more procedures described herein in addition to the procedure described herein with respect to FIG. 4.
  • the system 400 including the UE 402 and the base station 404 may implement any one or more procedures described herein with respect to any one or more of FIGS. 1, 2, 3, and 5-10.
  • FIG. 5 is a block diagram conceptually illustrating an example hardware implementation for a UE 500 in accordance with some aspects of the disclosure.
  • the UE 500 may be a UE as illustrated in any one or more of FIGS. 1-4 and 6-10.
  • the UE 500 may be implemented with a processing system 514 that includes one or more processors 504.
  • processors 504 include microprocessors, microcontrollers, digital signal processors (DSPs) , field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • DSPs digital signal processors
  • FPGAs field programmable gate arrays
  • PLDs programmable logic devices
  • state machines gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • the UE 500 may be configured to perform any one or more of the functions described herein. That is, the processor 504, as utilized in the UE 500, may be used to implement any one or more of the processes and procedures described and illustrated in FIGS. 1-4 and 6-10.
  • the processing system 514 may be implemented with a bus architecture, represented generally by the bus 502.
  • the bus 502 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 514 and the overall design constraints.
  • the bus 502 communicatively couples together various circuits including one or more processors (represented generally by the processor 504) , a memory 505, and computer-readable media (represented generally by the computer-readable medium 506) .
  • the bus 502 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.
  • a bus interface 508 provides an interface between the bus 502 and a transceiver 510.
  • the transceiver 510 may provide a communication interface or means for wirelessly communicating with various other apparatus over a transmission medium.
  • a user interface 512 for example, keypad, display, speaker, microphone, joystick
  • keypad for example, keypad, display, speaker, microphone, joystick
  • the processor 504 may include a selecting circuit 540 configured to perform various functions, including, for example, selecting an application of one or more applications stored in the UE, where the application is associated with a traffic descriptor of a plurality of traffic descriptors.
  • the selecting circuit 540 may be configured to perform various functions, including, for example, storing one or more applications in the UE, each of the one or more applications associated with a traffic descriptor of a plurality of traffic descriptors.
  • the processor 504 may include a generating circuit 542 configured to perform various functions, including, for example, generating a network slice selection assistance information (NSSAI) list including at least one single NSSAI (S-NSSAI) that is based on the application and the traffic descriptor. Additionally, or alternatively, the generating circuit 542 may be configured to perform various functions, including, for example, storing a plurality of sets of policy rules in the UE, where each set of policy rules of the plurality of sets of policy rules comprises a traffic descriptor.
  • NSSAI network slice selection assistance information
  • S-NSSAI single NSSAI
  • the generating circuit 542 may be configured to perform various functions, including, for example, matching a traffic descriptor from one set of policy rules of the plurality of sets of policy rules with the traffic descriptor associated with the application. Additionally, or alternatively, the generating circuit 542 may be configured to perform various functions, including, for example, selecting the set of policy rules identifying the traffic descriptor that matches the traffic descriptor associated with the application. Additionally, or alternatively, the generating circuit 542 may be configured to perform various functions, including, for example, generating the at least one S-NSSAI including an identification of the application and the selected set of policy rules.
  • the processor 504 may include a collecting circuit 544 configured to perform various functions, including, for example, collecting one or more use-statistics associated with each of the one or more applications stored in the UE. In some aspects of the disclosure, the processor 504 may include a ranking circuit 546 configured to perform various functions, including, for example, ranking each application of the one or more applications based on the one or more use-statistics. In some aspects of the disclosure, the processor 504 may include a transmitting circuit 548 configured to perform various functions, including, for example, transmitting the NSSAI list to a base station. In some aspects of the disclosure, the processor 504 may include a receiving circuit 549 configured to perform various functions, including, for example, receiving an approved NSSAI list. In some examples, the transmitting circuit 548 and/or the receiving circuit 549 may be configured to perform various functions, including, for example, establishing a protocol data unit (PDU) session.
  • PDU protocol data unit
  • the processor 504 may be responsible for managing the bus 502 and general processing, including the execution of software stored on the computer-readable medium 506.
  • the software when executed by the processor 504, causes the processing system 514 to perform the various functions described herein, including those functions describe with respect to FIGS. 1-4 and 6-10.
  • the computer-readable medium 506 and the memory 505 may also be used for storing data that is manipulated by the processor 504 when executing software.
  • One or more processors 504 in the processing system may execute software.
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • the software may reside on a computer-readable medium 506.
  • the computer-readable medium 506 may be a non-transitory computer-readable medium.
  • a non-transitory computer-readable medium includes, by way of example, a magnetic storage device (for example, hard disk, floppy disk, magnetic strip) , an optical disk (for example, a compact disc (CD) or a digital versatile disc (DVD) ) , a smart card, a flash memory device (for example, a card, a stick, or a key drive) , a random access memory (RAM) , a read only memory (ROM) , a programmable ROM (PROM) , an erasable PROM (EPROM) , an electrically erasable PROM (EEPROM) , a register, a removable disk, and any other suitable medium for storing software or instructions that may be accessed and read by a computer.
  • a magnetic storage device for example, hard disk, floppy disk, magnetic strip
  • an optical disk for example, a compact disc (CD) or a digital versatile disc (DVD)
  • a smart card for example, a flash memory device (for example,
  • the computer-readable medium 506 may reside in the processing system 514, external to the processing system 514, or distributed across multiple entities including the processing system 514.
  • the computer-readable medium 506 may be embodied in a computer program product.
  • a computer program product may include a computer-readable medium in packaging materials.
  • the computer-readable storage medium 506 may include selecting software or instructions 550, generating software or instructions 552, collecting software or instructions 554, ranking software or instructions 556, transmitting software or instructions 558, or receiving software or instructions 659.
  • the circuitry included in the processor 504 is merely provided as an example, and other means for carrying out the described functions may be included within various aspects of the present disclosure, including but not limited to the instructions stored in the computer-readable storage medium 506, or any other suitable apparatus or means described in any one of the FIGS. 1-4 and 6-10 and utilizing, for example, the processes or algorithms described herein.
  • FIG. 6 is a flow chart illustrating an example method 600 performed at a UE for generating and updating network slice selection assistance information (NSSAI) lists in accordance with some aspects of the disclosure.
  • the method 600 may be carried out by any suitable apparatus or means for carrying out the functions or algorithm described herein.
  • the UE 500 may store one or more applications in a user equipment (UE) , each of the one or more applications associated with a traffic descriptor of a plurality of traffic descriptors.
  • UE user equipment
  • one or more application may have been stored on the UE before an initial use of the UE.
  • a user of the UE may have downloaded and stored the one or more applications on the UE after an initial use.
  • Application may include, for example, a NETFLIX TM application, a WECHAT TM application, a BLIBLI TM application, an OFFICE TM application, or the like.
  • each of the one or more applications may be associated with a traffic descriptor of a plurality of traffic descriptors.
  • a traffic descriptor may be information associated with a particular application that, when provided to a network, such as an AMF (e.g., AMF 406) , informs the network of the particular kind of traffic that the application utilizes and the performance requirements of that traffic.
  • a traffic descriptors may include a requested service type, one or more traffic parameters of each data flow in both directions, and quality of service (QoS) parameters requested in each direction.
  • services types may include constant bit rate (CBR) , real-time variable bit rate (rt-VBR) , non-real-time variable bit rate (nrt-VBR) , available bit rate (ABR) , and unspecified bit rate (UBR) .
  • CBR constant bit rate
  • rt-VBR real-time variable bit rate
  • nrt-VBR non-real-time variable bit rate
  • ABR available bit rate
  • UBR unspecified bit rate
  • traffic parameters may include peak cell rate (PCR) , sustainable cell rate (SCR) , maximum burst size (MBS) , and minimum cell rate (MCR) .
  • QoS parameters may include cell transfer delay (CTD) , peak-to-peak cell delay variation (CDV) , and cell loss ratio (CLR) .
  • the UE 500 may collect one or more use-statistics associated with each of the one or more applications stored in the UE.
  • the UE may determine an amount of a time that each application is used. For example, the UE may determine a total amount of time that each application has been used on the UE. As another example, the UE may determine the average amount of time that each application is used over a predetermined time period (e.g., a day, a week, a month, a year, or the like) .
  • the UE may determine a recency of use of each of the one or more applications. For example, the UE may determine which applications were most recently used. In some cases, when the UE has not been used, the UE may determine that each of the one or more applications have not been used and assign a default use statistic to each of the one or more applications.
  • the UE 500 may rank each application of the one or more applications based on the one or more use-statistics.
  • the UE may rank each application of the one or more applications according to a total amount of time that each applications is used. For example, the UE may assign a highest rank to a first application that has been used the most, a second highest rank to a second application that has been used less than only the first application, and a lowest rank to a third application that has been used the least of all of the other one or more applications.
  • the UE may rank each application of the one or more applications according to an averaged amount of time that each applications is used over a predetermined period of time.
  • the UE may assign a highest rank to a first application that has a highest averaged amount of use time over the predetermined time, a second highest rank to a second application that has an averaged amount of use time over the predetermined time that is less than only the first application, and a lowest rank to a third application that has an averaged amount of use time over the predetermined time that is less than all of the other one or more applications.
  • the UE may rank each application of the one or more applications according to a recency of use among each of the one or more applications. For example, the UE may assign a highest rank to a first application that was most recently used, a second highest rank to a second application that was used most recently relative to every other application of the one or more applications except the first application, and a lowest rank to a third application that was last used at a time before all of the other one or more applications were used. In some cases, when the UE has not been used, and thus none of the one or more applications have been used, the UE may assign a same rank or a default rank to each of the one or more applications.
  • the UE 500 may select an application of the one or more applications stored in the UE based on a rank of the application. In some cases, the UE may select at least one application of the one or more applications having a rank above a minimum threshold rank. For example, the UE may select only the highest-ranking application of the one or more applications. As another example, the UE may select the eight (8) highest ranking applications (e.g., a top eight (8) ) of the one or more applications.
  • the UE when the UE can select a threshold quantity of applications based on rank, but the quantity of applications that have a use statistic and a rank (i.e., not default rank) is below the threshold quantity, the UE may select only those applications that have a rank (i.e., not default rank) . In some cases, when the UE can select a threshold quantity of applications based on rank, but the quantity of applications that have a use statistic and a rank (i.e., not default rank) is below the threshold quantity, the UE may select those applications that have a rank (i.e., not default rank) and one or more default applications so that the quantity of selected applications meet the threshold quantity. In some cases, when the UE has not been used, and thus none of the one or more applications have been used, the UE may select one or more default applications of the one or more applications.
  • the UE 500 may generate a network slice selection assistance information (NSSAI) list including at least one single NSSAI (S-NSSAI) that is based on the selected application and the associated traffic descriptor. For example, after the UE selects at least one application of the one or more applications, the UE may generate a network slice selection assistance information (NSSAI) list including at least one single NSSAI (S-NSSAI) that is based on the at least one selected application and each traffic descriptor associated with each application. In some cases, for example, when the UE has not been used, and thus none of the one or more applications have been used, the UE may generate a default NSSAI list. The default NSSAI list be including one or more S-NSSAIs that are associated with a predetermined set of one or more applications.
  • NSSAI network slice selection assistance information
  • generating an NSSAI list may include storing a plurality of sets of policy rules in the UE, where each set of policy rules of the plurality of sets of policy rules comprises a traffic descriptor.
  • the UE may search for and record or store a plurality of UE route selection policy (URSP) rules and/or a plurality of network slice selection policy (NSSP) rules.
  • URSP UE route selection policy
  • NSSP network slice selection policy
  • the plurality of sets of policy rules stored in the UE may include at least one of one or more sets of policy rules configured by the UE or one or more sets of policy rules received from the base station.
  • generating an NSSAI list may include matching a traffic descriptor from one set of policy rules of the plurality of sets of policy rules with the traffic descriptor associated with the application. For example, after storing a plurality of URSP rules and/or a plurality of NSSP rules, the UE may match a traffic descriptor contained in a URSP rule of the plurality of USRP rules or contained in an NSSP rule of the plurality of NSSP rules with a traffic descriptor associated with a selected application.
  • generating an NSSAI list may include selecting the set of policy rules identifying the traffic descriptor that matches the traffic descriptor associated with the application. For example, after matching a traffic descriptor contained in a URSP rule of the plurality of URSP rules or contained in an NSSP rule of the plurality of NSSP rules with a traffic descriptor associated with a selected application, the UE may select the URSP rule and/or the NSSP rule having the traffic descriptor that matches the traffic descriptor associated with the selected application. Additionally, or alternatively, generating an NSSAI list may include generating at least one S-NSSAI including an identification of the application and the selected set of policy rules.
  • the UE may generate an NSSAI list including at least one S-NSSAI.
  • the UE may generate the S-NSSAI for inclusion in the NSSAI list and using an identification of the selected application and the selected set of policy rules.
  • Each S-NSSAI may be representative of or associated with a network slice, discuss herein.
  • the NSSAI list may include up to eight (8) S-NSSAIs in accordance with TS38.300.16.3.1 and TS23.501.5.15.2.1.
  • the UE 500 may transmit the NSSAI list to a base station. For example, during a registration procedure (e.g., using an RRCSetupComplete message) , the UE 402 may transmit a requested NSSAI list to the base station 404.
  • the UE 500 may receive an approved NSSAI list.
  • a base station may transmit the requested NSSAI list to an AMF associated with the base station.
  • the AMF may determine that the AMF itself has the appropriate network slicing instance and/or is associated with the appropriate network slice for one or more applications identified by the S-NSSAIs in the NSSAI and select the AMF itself for providing network slicing instances.
  • the AMF 406 may determine that another AMF has the appropriate network slicing instance and/or is associated with the appropriate network slice for one or more applications identified by the S-NSSAIs in the NSSAI and select the other AMF for providing network slicing instances. Additionally, or alternatively, the AMF may identify one or more network slices and select appropriate network slices for one or more applications identified by the S-NSSAIs in the NSSAI. Additionally, or alternatively, the AMF may identify one or more network slice instances and select appropriate network slice instances for one or more applications identified by the S-NSSAIs in the NSSAI.
  • the base station may receive the indication of the selection of at least one of the serving AMF, one or more network slices, or one or more network slicing instances and determine that the requested NSSAI list is an approved NSSAI list. After the base station determines that the requested NSSAI list is an approved NSSAI list, the base station may transmit the approved NSSAI list for reception by the UE.
  • the UE 500 may establish a protocol data unit (PDU) session. For example, the UE and the base station may establish a PDU session for each application selected by the UE.
  • PDU protocol data unit
  • a UE includes a means for selecting an application of one or more applications stored in the UE.
  • the application is associated with a traffic descriptor of a plurality of traffic descriptors.
  • the UE also includes a means for generating a network slice selection assistance information (NSSAI) list including at least one single NSSAI (S-NSSAI) that is based on the application and the traffic descriptor.
  • NSSAI network slice selection assistance information
  • S-NSSAI single NSSAI
  • the UE further includes a means for transmitting the NSSAI list to a base station.
  • the UE includes a means for collecting one or more use-statistics associated with each of the one or more applications stored in the UE.
  • the UE includes a means for ranking each application of the one or more applications based on the one or more use-statistics. In some aspects the UE includes a means for receiving an allowed NSSAI list from the RAN entity in response to transmitting the requested NSSAI list.
  • FIG. 7 is a conceptual diagram illustrating an example of a hardware implementation for an example base station 700 in accordance with some aspects of the disclosure.
  • the base station 700 may perform any of the functions illustrated and described in FIGS. 1-6 and 8-10.
  • the base station 700 may be implemented with a processing system 714 that includes one or more processors 704.
  • processors 704 include microprocessors, microcontrollers, digital signal processors (DSPs) , field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • DSPs digital signal processors
  • FPGAs field programmable gate arrays
  • PLDs programmable logic devices
  • state machines gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • the base station 700 may be configured to perform any one or more of the functions described herein. That is, the processor 704, as utilized in the base station 700, may be used to implement any one or more of the processes and procedures described in FIGS. 1-6 and 8-10 and further illustrated in the flow diagrams discussed herein.
  • the processing system 714 may be implemented with a bus architecture, represented generally by the bus 702.
  • the bus 702 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 714 and the overall design constraints.
  • the bus 702 communicatively couples together various circuits including one or more processors (represented generally by the processor 704) , a memory 705, and computer-readable media (represented generally by the computer-readable medium 706) .
  • the bus 702 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.
  • a bus interface 708 provides an interface between the bus 702 and a transceiver 710.
  • the transceiver 710 provides a communication interface or means for communicating with various other apparatus over a transmission medium.
  • a user interface 712 for example, keypad, display, speaker, microphone, joystick
  • a user interface 712 for example, keypad, display, speaker, microphone, joy
  • the processor 704 may include a receiving circuit 740 configured for various functions, including, for example, receiving a network slice selection assistance information (NSSAI) list including at least one single-NSSAI (S-NSSAI) that is based on an application and an associated traffic descriptor.
  • the receiving circuit 740 may also be configured for various functions, including, for example, receiving a selection of at least one of a serving AMF, one or more network slices, or one or more network slice instances based on the S-NSSAI contained in the NSSAI.
  • the processor 704 may include an approving circuit 742 configured for various functions, including, for example, approving a requested NSSAI from a UE based on receiving a selection of at least one of a serving AMF, one or more network slices, or one or more network slice instances.
  • the processor 704 may include a transmitting circuit 744 configured for various functions, including, for example, transmitting an approved NSSAI list to a UE.
  • the transmitting circuit 744 and/or the receiving circuit 740 may also be configured for various functions, including, for example, establishing a protocol data unit (PDU) session between the base station and a UE.
  • PDU protocol data unit
  • the processor 704 is responsible for managing the bus 702 and general processing, including the execution of software stored on the computer-readable medium 706.
  • the software when executed by the processor 704, causes the processing system 714 to perform the various functions described below for any particular apparatus.
  • the computer-readable medium 706 and the memory 705 may also be used for storing data that is manipulated by the processor 704 when executing software.
  • One or more processors 704 in the processing system may execute software.
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • the software may reside on a computer-readable medium 706.
  • the computer-readable medium 706 may be a non-transitory computer-readable medium.
  • a non-transitory computer-readable medium includes, by way of example, a magnetic storage device (for example, hard disk, floppy disk, magnetic strip) , an optical disk (for example, a compact disc (CD) or a digital versatile disc (DVD) ) , a smart card, a flash memory device (for example, a card, a stick, or a key drive) , a random access memory (RAM) , a read only memory (ROM) , a programmable ROM (PROM) , an erasable PROM (EPROM) , an electrically erasable PROM (EEPROM) , a register, a removable disk, and any other suitable medium for storing software or instructions that may be accessed and read by a computer.
  • a magnetic storage device for example, hard disk, floppy disk, magnetic strip
  • an optical disk for example, a compact disc (CD) or a digital versatile disc (DVD)
  • a smart card for example, a flash memory device (for example,
  • the computer-readable medium 706 may reside in the processing system 714, external to the processing system 714, or distributed across multiple entities including the processing system 714.
  • the computer-readable medium 706 may be embodied in a computer program product.
  • a computer program product may include a computer-readable medium in packaging materials.
  • the computer-readable storage medium 706 may include receiving software or instructions 750, approving software or instructions 752, and transmitting software or instructions 754.
  • the circuitry included in the processor 704 is merely provided as an example, and other means for carrying out the described functions may be included within various aspects of the present disclosure, including but not limited to the instructions stored in the computer-readable storage medium 706, or any other suitable apparatus or means described in any one of the FIGS. 1-6 and 8-10 and utilizing, for example, the processes or algorithms described herein.
  • FIG. 8 is a flow chart illustrating an example method 800 performed at a base station for generating and updating network slice selection assistance information (NSSAI) lists in accordance with some aspects of the disclosure.
  • the method 800 may be carried out by any suitable apparatus or means for carrying out the functions or algorithm described herein.
  • the base station 700 may receive a network slice selection assistance information (NSSAI) list including at least one single-NSSAI (S-NSSAI) that is based on an application and an associated traffic descriptor. For example, during a registration procedure (e.g., using an RRCSetupComplete message) , the base station may receive a requested NSSAI list from a UE.
  • the base station 700 may transmit the NSSAI list to an access and mobility management function (AMF) .
  • AMF access and mobility management function
  • a base station may transmit the requested NSSAI list to an AMF associated with the base station.
  • the AMF may determine that the AMF itself has the appropriate network slicing instance and/or is associated with the appropriate network slice for one or more applications identified by the S-NSSAIs in the NSSAI and select the AMF itself for providing network slicing instances. Additionally, or alternatively, the AMF 406 may determine that another AMF has the appropriate network slicing instance and/or is associated with the appropriate network slice for one or more applications identified by the S-NSSAIs in the NSSAI and select the other AMF for providing network slicing instances. Additionally, or alternatively, the AMF may identify one or more network slices and select appropriate network slices for one or more applications identified by the S-NSSAIs in the NSSAI. Additionally, or alternatively, the AMF may identify one or more network slice instances and select appropriate network slice instances for one or more applications identified by the S-NSSAIs in the NSSAI.
  • the base station 700 may receive a selection of at least one of a serving AMF, one or more network slices, or one or more network slice instances based on the S-NSSAI contained in the NSSAI. For example, the base station may receive the indication of the selection of at least one of the serving AMF, one or more network slices, or one or more network slicing instances and determine that the requested NSSAI list is an approved NSSAI list.
  • the base station 700 may transmit an approved NSSAI list. For example, after the base station determines that the requested NSSAI list is an approved NSSAI list, the base station may transmit the approved NSSAI list for reception by the UE.
  • the base station 700 may establish a protocol data unit (PDU) session. For example, the UE and the base station may establish a PDU session for each application selected by the UE.
  • PDU protocol data unit
  • FIG. 9 is a conceptual diagram illustrating an example of a hardware implementation for an example AMF 900 in accordance with some aspects of the disclosure.
  • the AMF 900 may perform any of the functions illustrated and described in FIGS. 1-8 and 10.
  • the AMF 900 may be implemented with a processing system 914 that includes one or more processors 904.
  • processors 904 include microprocessors, microcontrollers, digital signal processors (DSPs) , field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • the base station 700 may be configured to perform any one or more of the functions described herein. That is, the processor 904, as utilized in the AMF 900, may be used to implement any one or more of the processes and procedures described in FIGS. 1-8 and 10 and further illustrated in the flow diagrams discussed herein.
  • the processing system 914 may be implemented with a bus architecture, represented generally by the bus 902.
  • the bus 902 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 914 and the overall design constraints.
  • the bus 902 communicatively couples together various circuits including one or more processors (represented generally by the processor 904) , a memory 905, and computer-readable media (represented generally by the computer-readable medium 906) .
  • the bus 902 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.
  • a bus interface 908 provides an interface between the bus 902 and a transceiver 910.
  • the transceiver 910 provides a communication interface or means for communicating with various other apparatus over a transmission medium.
  • a user interface 912 for example, keypad, display, speaker, microphone, joystick
  • a user interface 912 for example, keypad, display, speaker, microphone, joy
  • the processor 904 may include a receiving circuit 940 configured for various functions, including, for example, receive a network slice selection assistance information (NSSAI) list including at least one single-NSSAI (S-NSSAI) that is based on an application and an associated traffic descriptor.
  • the processor 904 may include a selecting circuit 942 configured for various functions, including, for example, selecting at least one of a serving AMF, one or more network slices, or one or more network slice instances based on the S-NSSAI contained in the NSSAI.
  • the processor 904 may include a transmitting circuit 944 configured for various functions, including, for example, transmitting an indication of the selection.
  • the processor 904 is responsible for managing the bus 902 and general processing, including the execution of software stored on the computer-readable medium 906.
  • the software when executed by the processor 904, causes the processing system 914 to perform the various functions described below for any particular apparatus.
  • the computer-readable medium 906 and the memory 905 may also be used for storing data that is manipulated by the processor 904 when executing software.
  • One or more processors 904 in the processing system may execute software.
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • the software may reside on a computer-readable medium 906.
  • the computer-readable medium 906 may be a non-transitory computer-readable medium.
  • a non-transitory computer-readable medium includes, by way of example, a magnetic storage device (for example, hard disk, floppy disk, magnetic strip) , an optical disk (for example, a compact disc (CD) or a digital versatile disc (DVD) ) , a smart card, a flash memory device (for example, a card, a stick, or a key drive) , a random access memory (RAM) , a read only memory (ROM) , a programmable ROM (PROM) , an erasable PROM (EPROM) , an electrically erasable PROM (EEPROM) , a register, a removable disk, and any other suitable medium for storing software or instructions that may be accessed and read by a computer.
  • a magnetic storage device for example, hard disk, floppy disk, magnetic strip
  • an optical disk for example, a compact disc (CD) or a digital versatile disc (DVD)
  • a smart card for example, a flash memory device (for example,
  • the computer-readable medium 906 may reside in the processing system 914, external to the processing system 914, or distributed across multiple entities including the processing system 914.
  • the computer-readable medium 906 may be embodied in a computer program product.
  • a computer program product may include a computer-readable medium in packaging materials.
  • the computer-readable storage medium 906 may include receiving software or instructions 950, selecting software or instructions 952, and transmitting software or instructions 954.
  • the circuitry included in the processor 904 is merely provided as an example, and other means for carrying out the described functions may be included within various aspects of the present disclosure, including but not limited to the instructions stored in the computer-readable storage medium 906, or any other suitable apparatus or means described in any one of the FIGS. 1-8 and 10 and utilizing, for example, the processes or algorithms described herein.
  • FIG. 10 is a flow chart illustrating an example method 1000 performed at an AMF for generating and updating network slice selection assistance information (NSSAI) lists in accordance with some aspects of the disclosure.
  • the method 1000 may be carried out by any suitable apparatus or means for carrying out the functions or algorithm described herein.
  • the AMF 900 may receive a network slice selection assistance information (NSSAI) list including at least one single-NSSAI (S-NSSAI) that is based on an application and an associated traffic descriptor.
  • NSSAI network slice selection assistance information
  • a base station may transmit the requested NSSAI list to an AMF associated with the base station.
  • the AMF may determine that the AMF itself has the appropriate network slicing instance and/or is associated with the appropriate network slice for one or more applications identified by the S-NSSAIs in the NSSAI and select the AMF itself for providing network slicing instances.
  • the AMF 406 may determine that another AMF has the appropriate network slicing instance and/or is associated with the appropriate network slice for one or more applications identified by the S-NSSAIs in the NSSAI and select the other AMF for providing network slicing instances. Additionally, or alternatively, the AMF may identify one or more network slices and select appropriate network slices for one or more applications identified by the S-NSSAIs in the NSSAI. Additionally, or alternatively, the AMF may identify one or more network slice instances and select appropriate network slice instances for one or more applications identified by the S-NSSAIs in the NSSAI.
  • the AMF 900 may select at least one of a serving AMF, one or more network slices, or one or more network slice instances based on the S-NSSAI contained in the NSSAI.
  • the AMF 900 may transmit an indication of the selection.
  • a or b may include a only, b only, or a combination of a and b.
  • a phrase referring to “at least one of” or “one or more 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 the examples of: a only, b only, c only, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a and b and c.

Landscapes

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

Abstract

La présente invention concerne des techniques pour générer et mettre à jour une liste d'informations d'aide à la sélection de tranches de réseau (NSSAI). Un équipement utilisateur (UE) sélectionne une application parmi une ou plusieurs applications stockées dans l'UE, l'application étant associée à un descripteur de trafic d'une pluralité de descripteurs de trafic. L'UE génère également une liste d'informations d'aide à la sélection de tranches de réseau (NSSAI) comprenant au moins un élément unique de NSSAI (S-NSSAI) basé sur l'application et le descripteur de trafic. L'UE transmet en outre la liste de NSSAI à une station de base.
PCT/CN2020/111221 2020-08-26 2020-08-26 Appareil et procédés pour la mise à jour de listes d'informations d'aide à la sélection de tranches de réseau Ceased WO2022040955A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/111221 WO2022040955A1 (fr) 2020-08-26 2020-08-26 Appareil et procédés pour la mise à jour de listes d'informations d'aide à la sélection de tranches de réseau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/111221 WO2022040955A1 (fr) 2020-08-26 2020-08-26 Appareil et procédés pour la mise à jour de listes d'informations d'aide à la sélection de tranches de réseau

Publications (1)

Publication Number Publication Date
WO2022040955A1 true WO2022040955A1 (fr) 2022-03-03

Family

ID=80352394

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/111221 Ceased WO2022040955A1 (fr) 2020-08-26 2020-08-26 Appareil et procédés pour la mise à jour de listes d'informations d'aide à la sélection de tranches de réseau

Country Status (1)

Country Link
WO (1) WO2022040955A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023185374A1 (fr) * 2022-03-26 2023-10-05 华为技术有限公司 Procédé de communication, appareil de communication et système de communication

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110506439A (zh) * 2017-06-20 2019-11-26 摩托罗拉移动有限责任公司 创建网络切片选择策略规则
EP3627799A1 (fr) * 2018-09-24 2020-03-25 Ntt Docomo, Inc. Terminal de communication et procédé permettant d'établir une session de communication
WO2020091636A1 (fr) * 2018-10-29 2020-05-07 Telefonaktiebolaget Lm Ericsson (Publ) Procédés, dispositifs de communication sans fil et systèmes adaptés à des scénarios de découpage de réseau
CN111226465A (zh) * 2017-10-11 2020-06-02 日本电气株式会社 利用网络切片选择策略的ue配置和更新

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110506439A (zh) * 2017-06-20 2019-11-26 摩托罗拉移动有限责任公司 创建网络切片选择策略规则
CN111226465A (zh) * 2017-10-11 2020-06-02 日本电气株式会社 利用网络切片选择策略的ue配置和更新
EP3627799A1 (fr) * 2018-09-24 2020-03-25 Ntt Docomo, Inc. Terminal de communication et procédé permettant d'établir une session de communication
WO2020091636A1 (fr) * 2018-10-29 2020-05-07 Telefonaktiebolaget Lm Ericsson (Publ) Procédés, dispositifs de communication sans fil et systèmes adaptés à des scénarios de découpage de réseau

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MOTOROLA MOBILITY, LENOVO, HUAWEI: "Update to solution 8 – Routing media traffic via different 5G network slices", 3GPP DRAFT; S2-184457_124_REV3743_UPDATE_TO_IMS_SOLUTION_V0.5, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Sanya, China; 20180416 - 20180420, 19 April 2018 (2018-04-19), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051432823 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023185374A1 (fr) * 2022-03-26 2023-10-05 华为技术有限公司 Procédé de communication, appareil de communication et système de communication

Similar Documents

Publication Publication Date Title
US11985557B2 (en) Signaling for conditional primary secondary cell addition/change configuration
US11374853B2 (en) Interworking with legacy radio access technologies for connectivity to next generation core network
US10165565B2 (en) Legacy and new radio coexistence frame and control design
US10862581B2 (en) Dynamic time division duplex (TDD) frame structure for hopping superframes
US11671902B2 (en) Apparatus and methods for new radio broadcast and multicast access control
US20230104381A1 (en) Delay management in wireless networks
US11611985B2 (en) Grant of resources for downlink and uplink communication via one or more relay user equipment
US12010508B2 (en) Peer-to-peer link security setup for relay connection to mobile network
US12035299B2 (en) Scheduling communication for multiple subscriber identity modules over a single communication link
US20240015798A1 (en) Random access channel parameter prioritization with network slice differentiation and access identity differentiation
US11805477B2 (en) Method to reduce recovery time from out-of-service event in dual receive (DR) or dual sim dual access (DSDA) capable user equipment
EP4193621B1 (fr) Coordination de connexions multiples avec un équipement utilisateur à l'aide de multiples abonnements
WO2021243598A1 (fr) Optimisation de mises à jour de politiques ursp sur des dispositifs à deux sim
US20230171590A1 (en) Capability information for a user equipment
WO2022040955A1 (fr) Appareil et procédés pour la mise à jour de listes d'informations d'aide à la sélection de tranches de réseau
WO2022041036A1 (fr) Mise à jour de flux de trafic à l'aide d'un message de temps de cycle de réception discontinue
WO2024156076A1 (fr) Commutation de groupe de cellules pour mobilité déclenchée par une couche inférieure
WO2022036668A1 (fr) Amélioration de la mobilité de mise en tranche de réseau
WO2024098182A1 (fr) Prach déclenché pour une cellule candidate
WO2024092600A1 (fr) Procédures de transfert intercellulaire de couche 1 et de couche 2
WO2022000252A1 (fr) Appareil et procédés de transfert intercellulaire d'un réseau d'évolution à long terme à un réseau de nouvelle radio de cinquième génération pour module d'identification à double abonné
WO2023010271A1 (fr) Préférence de connectivité de réseau d'équipement utilisateur

Legal Events

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

Ref document number: 20950628

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20950628

Country of ref document: EP

Kind code of ref document: A1