WO2022081303A1 - Application inference for 5gs network slicing policies - Google Patents

Abstract

An apparatus and system to assign a network slice for an application are described. New service requirements are described in which a third party is able to provision network slice-related information for applications to configure the association of network slice and application for a UE. A preferred network operators list of the application is used for sponsor connectivity and takes precedence over a steering of roaming policy provided by the home public land mobile network of the UE. The UE stores user preferences of the applications in priority order, which is used to determine whether to move to a different network when different applications are activated and use different network slices in the different networks.

Description

APPLICATION INFERENCE FOR 5GS NETWORK SLICING

POLICIES

PRIORITY CLAIM

[0001] This application claims the benefit of priority to United States Provisional Patent Application Serial No. 63/092,947, filed October 16, 2020, which is incorporated herein by reference in its entirety .

TECHNICAL FIELD

[0002] Embodiments pertain to fifth generation (5G) wireless communications. In particular, some embodiments relate to steering of roaming for network slice selection based on application information.

BACKGROUND

[0003] The use and complexity of wireless systems, which include 4^th generation (4G) and 5^th generation (5G) networks among others, has increased due to both an increase in the types of devices user equipment (UEs) using network resources as well as the amount of data and bandwidth being used by various applications, such as video streaming, operating on these UEs. With the vast increase in number and diversity of communication devices, the corresponding network environment, including routers, swatches, bridges, gateways, firewalls, and load balancers, has become increasingly complicated, especially with the advent of next generation (NG) (or new radio (NR)) systems. As expected, a number of issues abound with the advent of any new technology.

BRIEF DESCRIPTION OF THE FIGURES

[0004] In the figures, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The figures illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document.

[0005] FIG. 1A illustrates an architecture of a network, in accordance with some aspects. [0006] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects.

[0007] FIG. IC illustrates a non-roaming 5G system architecture in accordance with some aspects.

[0008] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments.

[0009] FIG. 3 illustrates UE-initiated UE state indication procedure in accordance with some aspects.

[0010] FIG. 4 illustrates request/response operations in accordance with some aspects.

[0011] FIG. 5 illustrates sendee-specific information provisioning in accordance with some aspects.

[0012] FIG. 6 illustrates a UE Configuration Update procedure for transparent UE Policy delivery/ in accordance with some aspects.

DETAILED DESCRIPTION

[0013] T he following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0014] FIG. 1A illustrates an architecture of a network in accordance with some aspects. The network 140A includes 3GPP LTE/4G and NG network functions that may be extended to 6G functions. Accordingly, although 5G will be referred to, it is to be understood that this is to extend as able to 6G structures, systems, and functions, A network function can be implemented as a discrete network element on a dedicated hardware, as a software instance running on dedicated hardware, and/or as a virtualized function instantiated on an appropriate platform, e.g., dedicated hardware or a cloud infrastructure.

[0015] The network 140A is shown to include user equipment (LIE) 101 and UE 102. The UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as portable (laptop) or desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface. The UEs 101 and 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein.

[0016] Any of the radio links described herein (e.g., as used in the network 140 A or any other illustrated network) may operate according to any exemplary radio communication technology and/or standard. Any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and other frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and other frequencies). Different Single Carrier or Orthogonal Frequency Domain Multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.), and in particular 3GPP NR, may be used by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0017] In some aspects, any of the UEs 101 and 102 can comprise an Internet-of-Things (loT) UE or a Cellular loT (CloT) UE, which can comprise a network access layer designed for low-power loT applications utilizing shortlived UE connections. In some aspects, any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-loT) UE). An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The loT UEs may execute background applications (e.g., keepalive messages, status updates, etc.) to facilitate the connections of the loT network. In some aspects, any of the UEs 101 and 102 can include enhanced MTC (eMFC) UEs or further enhanced MFC (FeMTC) UEs. [0018] The UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110. The RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.

[0019] The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA ) network protocol, a Push-to-Talk (PI T) protocol, a PIT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a 5G protocol, a 6G protocol, and the like.

[0020] In an aspect, the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink (SL) interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery' Channel (PSDCH), a Physical Sidelink Broadcast Channel (PSBCH), and a Physical Sidelink Feedback Channel (PSFCH).

[0021] The UE 102 is shown to be configured to access an access point (AP) 106 via connection 107. The connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[0022] The RAN 110 can include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). In some aspects, the communication nodes 111 and 112 can be transmi ssion/recepti on points (TRPs). In instances when the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs. The RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112. [0023] Any of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102. In some aspects, any of the RAN nodes 111 and 112 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In an example, any of the nodes 111 and/or 112 can be a gNB, an eNB, or another type of RAN node.

[0024] The RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI interface 113. In aspects, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS. 1B-1C). In this aspect, the SI interface 113 is split into two parts: the S1-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the Sl-mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs

121.

[0025] In this aspect, the CN 120 comprises the MMEs 121, the S-GW

122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support. Nodes (SGSN). The MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

[0026] The S-GW 122 may terminate the SI interface 113 towards the RAN 110, and routes data packets between the ILAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.

[0027] The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123 may route data packets between the CN 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125. The P-GW 123 can also communicate data to other external networks 131 A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks. Generally, the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data sendees, etc.). In this aspect, the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125. The application server 184 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120.

[0028] The P-GW 123 may further be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (ATLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123. [0029] In some aspects, the communication network 140A can be an loT network or a 5G or 6G network, including 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum. One of the current enablers of loT is the narrowband-IoT (NB-IoT). Operation in the unlicensed spectrum may include dual connectivity (DC) operation and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in unlicensed spectrum without the use of an "anchor" in the licensed spectrum, called MulteFire. Further enhanced operation of LTE systems in the licensed as well as unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operations can include techniques for sidelink resource allocation and UE processing behaviors for NR sidelink V2X communications.

[0030] An NG system architecture (or 6G system architecture) can include the RAN 110 and a 5G core network (5GC) 120. The NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs. The CN 120 (e.g., a 5G core network/5GC) can include an access and mobility function (AMF) and/or a user plane function (UPF). The AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some aspects, the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces. [0031] In some aspects, the NG system architecture can use reference points between various nodes. In some aspects, each of the gNBs and the NG- eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth. In some aspects, a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.

[0032] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects. In particular, FIG. IB illustrates a 5G system architecture 140B in a reference point representation, which may be extended to a 6G system architecture. More specifically, UE 102 can be in communication with RAN 110 as well as one or more other 5GC network entities. The 5G system architecture 140B includes a plurality of network functions (NFs), such as an AMF 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, UPF 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)/home subscriber server (HSS) 146.

[0033] The UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third- party services. The AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality. The AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of the access technologies. The SMF 136 can be configured to set up and manage various sessions according to network policy. The SMF 136 may thus be responsible for session management and allocation of IP addresses to UEs. The SMF 136 may also select and control the UPF 134 for data transfer. The SMF 136 may be associated with a single session of a UE 101 or multiple sessions of the UE 101. This is to say that the UE 101 may have multiple 5G sessions. Different SMFs may be allocated to each session. The use of different SMFs may permit each session to be individually managed. As a consequence, the functionalities of each session may be independent of each other.

[0034] The UPF 134 can be deployed in one or more configurations according to the desired service type and may be connected with a data network. The PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

[0035] The AF 150 may provide information on the packet flow⁷ to the PCF 148 responsible for policy control to support a desired QoS. The PCF 148 may set mobility and session management policies for the UE 101. To this end, the PCF 148 may use the packet flow information to determine the appropriate policies for proper operation of the AMF 132 and SMF 136. The AUSF 144 may store data for UE authentication.

[0036] In some aspects, the 5G system architecture I40B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) I64B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions such as routing an emergency request to the correct emergency center or PSAP. The I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. In some aspects, the I-CSCF 166B can be connected to another IP multimedia network 170E, e.g. an IMS operated by a different network operator.

[0037] In some aspects, the UDM/HSS 146 can be coupled to an application server 160E, which can include a telephony application server (TAS) or another application server (AS). The AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.

[0038] A reference point representation shows that interaction can exist between corresponding NF services. For example, FIG. IB illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 1 10 and the AMF 132), N3 (between the RAN 1 10 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), N11 (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM 146, not shown), N14 (between two AMFs 132, not shown), N15 (between the PCF 148 and the AMF 132 in case of a non-roaming scenario, or between the PCF 148 and a visited network and AMF 132 in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Other reference point representations not shown in FIG. IB can also be used.

[0039] FIG. 1C illustrates a 5G system architecture 140C and a servicebased representation. In addition to the network entities illustrated in FIG. IB, system architecture 140C can also include a network exposure function (NEF) 154 and a network repository' function (NRF) 156. In some aspects, 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

[0040] In some aspects, as illustrated in FIG. 1C, sendee-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this regard, 5G system architecture 140C can include the following servicebased interfaces: Namf 158H (a sendee-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a senice-based interface exhibited by the NEF 154), Npcf 158D (a sendee-based interface exhibited by the PCF 148), a Nudm 158E (a sendeebased interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a sendee-based interface exhibited by the NRF 156), Nnssf 158A (a sendee-based interface exhibited by the NSSF 142), Nausf 158G (a sendee-based interface exhibited by the AUSF 144). Other sendee-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in FIG. 1C can also be used.

[0041] NR-V2X architectures may support high-reliability low latency sidelink communications with a variety of traffic patterns, including periodic and aperiodic communications with random packet arrival time and size. Techniques disclosed herein can be used for supporting high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.

[0042] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments. The communication device 200 may be a UE such as a specialized computer, a personal or laptop computer (PC), a tablet PC, or a smart phone, dedicated network equipment such as an eNB, a server running software to configure the server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. For example, the communication device 200 may be implemented as one or more of the devices shown in FIGS. 1 A-1 C. Note that communications described herein may be encoded before transmission by the transmitting entity (e.g., UE, gNB) for reception by the receiving entity (e.g., gNB, UE) and decoded after reception by the receiving entity.

[0043] Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on a machine readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

[0044] Accordingly, the term “module” (and “component”) is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general-purpose hardware processor configured using software, the general -purpose hardware processor may be configured as respecti ve different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.

[0045] The communication device 200 may include a hardware processor (or equivalently processing circuitry) 202 (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory 204 and a static memory 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208. The main memory 204 may contain any or all of removable storage and non-removable storage, volatile memory or non-volatile memory. The communication device 200 may further include a display unit 210 such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse). In an example, the display unit 210, input device 212 and UI navigation device 214 may be a touch screen display. The communication device 200 may additionally include a storage device (e.g., drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The communication device 200 may further include an output controller, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

[0046] The storage device 216 may include a non-transitory machine readable medium 222 (hereinafter simply referred to as machine readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 224 may also reside, completely or at least partially, within the main memory' 204, within static memory' 206, and/or within the hardware processor 202 during execution thereof by the communication device 200. While the machine readable medium 222 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers} configured to store the one or more instructions 224.

[0047] The term “machine readable medium” may include any' medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 200 and that cause the communication device 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of machine readable media may include: non-volatile memory', such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory' devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM: and DVD-ROM: disks.

[0048] The instructions 224 may further be transmitted or received over a communications network using a transmission medium 226 via the network interface device 220 utilizing any one of a number of wireless local area network (WLAN) transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks. Communications over the networks may include one or more different protocols, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi, IEEE 802.16 family of standards known as WiMax, IEEE

802. 15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, a next generation (NG)/5^th generation (5G) standards among others. In an example, the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phonejacks) or one or more antennas to connect to the transmission medium 226.

[0049] Note that the term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry- may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to cany out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

|0050| The term “processor circuitry” or “processor” as used herein thus refers to, is part of, or includes circuitry' capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. The term “processor circuitry” or “processor” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single- or multi-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes.

[00511 Any of the radio links described herein may operate according to any one or more of the following radio communication technologies and/or standards including but not limited to: a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3 GPP) radio communication technology, for example Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP Long Term Evolution Advanced (LTE Advanced), Code division multiple access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-Speed Circuit- Switched Data (HSCSD), Universal Mobile Telecommunications System (Third Generation) (UMTS (3G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), High Speed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), High Speed Packet Access Plus (HSPA+), Universal Mobile Telecommunications System-Time-Division Duplex (UMTS-TDD), Time Division-Code Division Multiple Access (TD-CDMA), Time Division- Synchronous Code Division Multiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8 (Pre-4th Generation) (3 GPP Rel. 8 (Pre-4G)), 3GPP Rel. 9 (3rd Generation Partnership Project Release 9), 3GPP Rel. 10 (3rd Generation Partnership Project Release 10) , 3GPP Rel. 11 (3rd Generation Partnership Project Release 1 1), 3 GPP Rel. 12 (3rd Generation Partnership Project Release 12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3GPP Rel. 14 (3rd Generation Partnership Project Release 14), 3GPP Rel. 15 (3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rd Generation Partnership Project Release 16), 3GPP Rel. 17 (3rd Generation Partnership Project Release 17) and subsequent Releases (such as Rel. 18, Rel. 19, etc.), 3GPP 5G, 5G, 5GNew Radio (5GNR), 3GPP 5G New Radio, 3GPP LTE Extra, LTE-Advanced Pro, LTE Licensed-Assisted Access (LAA), MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G), Code division multiple access 2000 (Third generation) (CDMA2000 (3G)), Evolution-Data Optimized or Evolution-Data Only (EV-DO), Advanced Mobile Phone System (1 st Generation) (AMPS (IG)), Total Access Communication SystemZExtended Total Access Communication System (TACSZETACS), Digital AMPS (2nd Generation) (D-AMPS (2G )), Push-to-talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Telephone System ( AMTS), OUT (Norwegian for Offentlig Landmobil Telefoni, Public Land Mobile Telephony), MTD (Swedish abbreviation for

Mobiitelefoni system D, or Mobile telephony system D), Public Automated Land Mobile (Autotel/PALM), ARP (Finnish for Autoradiopuhelin, "car radio phone"), NMT (Nordic Mobile Telephony), High capacity version of NTT (Nippon Telegraph and Telephone) (Hicap), Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handyphone System (PUS), Wideband Integrated Digital Enhanced Network (WIDEN), iBurst, Unlicensed Mobile Access ( UM. A), also referred to as also referred to as 3 GPP Generic Access Network, or GAN standard), Zigbee, Bluetooth(r), Wireless Gigabit Alliance (WiGig) standard, mmWave standards in general (wireless systems operating at 10-300 GHz and above such as WiGig, IEEE 802. 1 l ad, IEEE 802.1 lay, etc.), technologies operating above 300 GHz and THz bands, (3GPPZLTE based or IEEE 802.1 Ip or IEEE 802. 1 Ibd and other) Vehicle-to- Vehicle (V2V) and Vehicie-to-X (V2X) and Vehicle-to- Infrastructure (V2I) and Infrastructure-to- Vehicle (I2V) communication technologies, 3GPP cellular V2X, DSRC (Dedicated Short Range

Communications) communication systems such as Intelligent-Transport-Systems and others (typically operating in 5850 MHz to 5925 MHz or above (typically up to 5935 MHz following change proposals in CEPT Report 71)), the European ITS-G5 system (i.e. the European flavor of IEEE 802.1 Ip based DSRC, including ITS-G5A (i.e., Operation of ITS-G5 in European ITS frequency bands dedicated to ITS for safety re-lated applications in the frequency range 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., Operation in European ITS frequency bands dedicated to ITS non- safety applications in the frequency range 5,855 GHz to 5,875 GHz), ITS-G5C (i.e., Operation of ITS applications in the frequency range 5,470 GHz to 5,725 GHz)), DSRC in Japan in the 700MHz band (including 715 MHz to 725 MHz), IEEE 802.1 Ibd based systems, etc.

[0052] Aspects described herein can be used in the context of any spectrum management scheme including dedicated licensed spectrum, unlicensed spectrum, license exempt spectrum, (licensed) shared spectrum (such as ESA = Licensed Shared Access in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies and SAS = Spectrum Access System / CBRS = Citizen Broadband Radio System in 3.55-3.7 GHz and further frequencies). Applicable spectrum bands include IMT (International Mobile Telecommunications) spectrum as well as other types of spectrum/bands, such as bands with national allocation (including 450 - 470 MHz, 902-928 MHz (note: allocated for example in US (FCC Part 15)), 863-868.6 MHz (note: allocated for example in European Union (ETSI EN 300 220)), 915.9-929.7 MHz (note: allocated for example in Japan), 917-923.5 MHz (note: allocated for example in South Korea), 755-779 MHz and 779-787 MHz (note: allocated for example in China), 790 - 960 MHz, 1710 - 2025 MHz, 2110 - 2200 MHz, 2300 - 2400 MHz, 2.4-2.4835 GHz (note: it is an ISM band with global availability and it is used by Wi-Fi technology family (l lb/g/n/ax) and also by Bluetooth), 2500 - 2690 MHz, 698-790 MHz, 610 - 790 MHz, 3400 - 3600 MHz, 3400 - 3800 MHz, 3800 -- 4200 MHz, 3.55- 3.7 GHz (note: allocated for example in the US for Citizen Broadband Radio Sendee), 5.15-5.25 GHz and 5.25-5.35 GHz and 5.47-5.725 GHz and 5.725-5.85 GHz bands (note: allocated for example in the US (FCC part 15), consists four U-NII bands in total 500 MHz spectrum), 5.725-5.875 GHz (note: allocated for example in EU (ETSI EN 301 893)), 5,47-5.65 GHz (note: allocated for example in South Korea, 5925-7125 MHz and 5925-6425MHz band (note: under consideration in US and EU, respectively. Next generation Wi-Fi system is expected to include the 6 GHz spectrum as operating band but it is noted that, as of December 2017, Wi-Fi system is not yet allowed in this band. Regulation is expected to be finished in 2019-2020 time frame), IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800 MHz, 3800 - 4200 MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range, etc.), spectrum made available under FCC’s "Spectrum Frontier" 5G initiative (including 27.5 - 28.35 GHz, 29.1 - 29.25 GHz, 31 - 31 .3 GHz, 37 - 38.6 GHz, 38.6 - 40 GHz, 42 - 42.5 GHz, 57 - 64 GHz, 71 - 76 GHz, 81 - 86 GHz and 92 - 94 GHz, etc), the ITS (Intelligent Transport Systems) band of 5.9 GHz. (typically 5.85-5.925 GHz) and 63-64 GHz, bands currently allocated to WiGig such as WiGig Band 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz) and WiGig Band 3 (61.56-63.72 GHz) and WiGig Band 4 (63.72-65.88 GHz), 57- 64/66 GHz (note: this band has near-global designation for Multi-Gigabit.

Wireless Systems (MGWS)/WiGig . In US (FCC part 15) allocates total 14 GHz spectrum, while EU (ETSI EN 302 567 and ETSI EN 301 217-2 for fixed P2P) allocates total 9 GHz spectrum), the 70.2 GHz - 71 GHz band, any band between 65.88 GHz and 71 GHz, bands currently allocated to automotive radar applications such as 76-81 GHz, and future bands including 94-300 GHz and above. Furthermore, the scheme can be used on a secondary basis on bands such as the TV White Space bands (typically below 790 MHz) where in particular the 400 MHz and 700 MHz bands are promising candidates. Besides cellular applications, specific applications for vertical markets may be addressed such as PMSE (Program Making and Special Events), medical, health, surgery', automotive, low-latency, drones, etc. applications.

[0053] Aspects described herein can also implement a hierarchical application of the scheme is possible, e.g., by introducing a hierarchical prioritization of usage for different types of users (e.g., low/medium/high priority, etc.), based on a prioritized access to the spectrum e.g., with highest priority to tier-1 users, followed by tier-2, then tier-3, etc. users, etc.

[0054] Aspects described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0055| Some of the features in this document are defined for the network side, such as APs, eNBs, NR or gNBs - note that this term is typically used in the context of 3GPP fifth generation (5G) communication systems, etc. Still, a UE may take this role as well and act as an AP, eNB, or gNB; that is some or all features defined for network equipment may be implemented by a UE.

[0056] Network slicing has been supported since 3 GPP release 15. However, the UE’s network slices are disjoint within a single operator’s network. The UE does not have information to access the network slices based on user preference and active applications, which results in undesirable latency and decreased service experiences. Considering enhanced access to and support of network slices, in 3GPP TR 22.835, clause 5.7, use case 7 Slice Access with Application Preference may consider application policy for network slices, but no service requirements have been agreed. Note that. 3 GPP TS 22.261, TS 23.502, TR22.835- Study on Enhanced Access to and Support of Network Slice, TS 22.011 and TS 24.501 are all discussed and incorporated by reference herein. [0057] Based on service requirements of network slicing at 3GPP TS 22.261 and solutions for network slicing at 3GPP TS 23.501, the 5G network may provision an allowed network slicing list to the UE based on UE subscription, UE capabilities, the access technology being used by the UE, operator’s policies and services provided by the network slice. The following issues remain open:

[0058] Issue 1: the 5G network (gNB) provides an ‘‘Operator defined access category” to the UE during the registration procedure. The gNB provides potential association between an AppID and Single - Network Slice Selection Assistance Information (S-NSSAI) for the UE to establish a packet data unit (PDU) session with an allowed S-NSSAI when receiving an upper layer request from the application identified by the AppID. However, the manner in which the network is to properly assign a network slice for an application remains unclear. Note that the S-NSSAI identifies a Network Slice using a Slice/Service type (SST), which refers to the expected Network Slice behavior in terms of features and sendees, and a Slice Differentiator (SD) that complements the SST(s) to differentiate amongst multiple Network Slices of the same SST.

[0059] Issue 2: the manner in which the UE can select proper network slices for an application provided by a third party which may have a Service Level Agreement (SLA) with different network operators and have preferred public land mobile networks (PLMNs) of its applications is unclear. That is, the third party service provider may provide separate sponsor connectivity in preferred PLMNs for its users.

[0060] Issue 3 : the manner in which the LIE prioritizes the use of network slices used by different applications is unclear. For example, the prioritization between application 1, which is to use network slice 1 and cannot use network slice 2, and application 2, which is to use network slice 2 and cannot use network slice 1, is unclear. In this case, when a UE uses network 2 for application 2 and initiates application 1, which is to use network slice I but is not supported in the serving PLMN, a mechanism is to be added for the UE to determine whether or not to proceed to re-select to a new PLMN that, supports application 1.

[0061] 3GPP TS 24.501 describes operator-defined access categories to provide information of access categories related to a S-NSSAI, Data Network Name (DNN), and OSId+OS App ID. The OSId is sent in a LIE STATE INDICATION message during the registration procedure.

[0062] 4.5.3 Operator-defined access categories

[0063] Operator-defined access category definitions can be signalled to the UE using non-access stratum (NAS) signalling. Each operator-defined access category definition includes the following parameters: a precedence value that indicates in which order the UE shall evaluate the operator-defined category definition for a match; an operator-defined access category number, i.e. access category number in the 32-63 range that uniquely identifies the access category' in the PLMN or Standalone Non-Public Networks (SNPN) in which the access categories are being sent to the UE; and criteria that includes one or more access category' criteria type and associated access category' criteria type values. The access category criteria type can be set to: DNN, a 5G Quality of Service (QoS) Identifier (5QI), OS Id + OS App Id of application triggering the access attempt, or S-NSSAI. An access category criteria type can be associated with more than one access category criteria values. An access attempt matches the criteria of an operator-defined access category' definition, if the access attempt matches all access category criteria types included in the criteria with any of the associated access criteria type values. Each operator-defined access category definition has a different precedence value. Several operator-defined access category definitions can have the same operator-defined access category' number.

[0064] FIG. 3 illustrates UE-initiated UE state indication procedure in accordance with some aspects. As shown, the UE sends the UE STATE INDICATION message using the registration procedure. During the UE- initiated UE state indication procedure accepted by the network, upon receipt of the UE STATE INDICATION message, the PCF operates as described in 3GPP TS 23.502 and 3GPP TS 29.525.

[0065] The UE state indication message is sent by the UE to the PCF. The UE state indication message delivers the UE Policy Section Identifier (UPSI(s)) of the UE policy section(s) stored in the UE, indicates whether the UE supports Access Network Discovery' and Selection Policy (ANDSP), and delivers one or more OS IDs of the UE.

Table D.5.4.1.1: UE STATE INDICATION message content

[0066] FIG. 4 illustrates request/response operations in accordance with some aspects. FIG. 4 illustrates the NEF service operations information flow in which at operation 0 the NF subscribes to UDM notifications of the UE and/or Group Subscription data updates. The NF can subscribe to Group Subscription data from UDM in this step and be notified of Group Subscription data updates in step 7 using the Shared Data feature defined in TS 29.503.

[0067] At operation Ob, which is conditional on using Network Data Analytics Function (NWDAF)-assisted values, the AF may subscribe to the NWDAF via the NEF in order to learn the UE mobility analytics and/or UE Communication analytics for a UE or group of UEs by applying the procedure specified in TS 23.288 clause 6.1 .1.2. The Analytics Id is set to any of the values specified in TS 23.288 clause 6.7.1.

[0068] At operation 0c, which is conditional on using NWDAF-assisted values, the AF validates the received data and derives any of the Expected UE behaviour parameters defined in TS 23.502 clause 4.15.6.3 for a UE or group of UEs.

[0069] At operation 1, the AF provides one or more parameter(s) to be created or updated in a Nnef_ParameterProvision_Create or

Nnef ParameterProvi si on Update or Nnef ParameterProvision Delete Request to the NEF. The Generic Public Subscription Identifier (GPSI) identifies the UE and the Transaction Reference ID identifies the transaction request between the NEF and the AF. For the case of Nnef_ParameterProvision_Create, the NEF assigns a Transaction Reference ID to the Nnef ParameterProvision Create request.

[0070] The NEF checks whether the requestor is allowed to perform the requested service operation by checking requestor's identifier (i.e., AF ID). For a Create request associated with a 5G VN group, the External Group ID identifies the 5G VN Group. The payload of the Nnef_ParameterProvision_Update Request includes one or more of the following parameters: expected UE Behavior parameters (see TS 23.502 clause 4.15.6.3), Network Configuration parameters (see TS 23.502 clause 4.15.6.3a), External Group Id and 5G VN group data (i.e., 5G-VN configuration parameters) (see TS 23.502 clause 4.15.6.3b), 5G VN group membership management parameters (see TS 23.502 clause 4.15.6.3c), or Location Privacy Indication parameters of the "LCS privacy" Data Subset of the Subscription Data (see TS 23.502 clause 5.2.3.3.1 and TS 23.273 clause 7.1). The AF may request to delete a 5G VN configuration by sending a Nnef_ParameterProvision_Delete to the NEF.

[0071] At operation 2, if the AF is authorized by the NEF to provision the parameters, the NEF requests to create, update and store, or delete the provi sioned parameters as part of the subscriber data via Nudm_ParameterProvision_Create, Nudm_ParameterProvision_Update or Nudm ParameterProvision Delete Request message, the message includes the provisioned data and NEF reference ID. If the AF is not authorized to provision the parameters, then the NEF continues in operation 6 indicating the reason to failure in Nnef_ParameterProvision_Create/Update/Delete Response message. Operation 7 does not apply in this case. For a non-roaming case and no authorization or validation by the UDM is required and if the request is not associated with a 5G VN group, the NEF can directly forward the external parameter to the UDR via a Nudr __DM__Update Request message. In this case, the UDR responds to NEF via a Nudr_DM_Update Response message.

[0072] At operati on 3, the UDM may read from the UDR, by means of a Nudr_DM_Query, corresponding subscription information in order to validate data updates and authorize these changes for this subscriber or Group for the corresponding AF.

[0073] At operation 4, if the AF is authorized by the UDM to provision the parameters for this subscriber, the UDM resolves the GPSI to the SUPI, and requests to create, update or delete the provisioned parameters as part of the subscriber data via Nudr_DM_Create/Update/Delete Request message, the message includes the provisioned data.

[0074] If a new 5G VN group is created, the UDM assigns a unique

Internal Group ID for the 5G VN group and includes the newly assigned Internal Group ID in the Nudr DM Create Request message. If the list of 5G VN group members is changed or if 5G VN group data has changed, the UDM updates the UE and/or Group subscription data according to the AF/NEF request. The UDR stores the provisioned data as part of the UE and/or Group subscription data and responds with a Nudr DM Create/Update/Delete Response message.

[0075] When the 5G VN group data (as described in TS 23.502 clause 4.15.6.3b) is updated, the UDR notifies to the subscribed PCF by sending Nudr_DM_Notify as defined in TS 23.502 clause 4.16.12.2. [0076] If the AF is not authorized to provision the parameters, then the

UDM continues in operation 5 indicating the reason to failure in a

Nudm ParameterProvision Update Response message and operation 7 is not executed.

[0077] The UDM classifies the received parameters (i ,e., Expected UE Behaviour parameters or the Network Configuration parameters or the 5G VN configuration parameters or Location Privacy Indication parameters), into AMF- Associated and SMF -Associated parameters. The UDM may use the AF ID received from the NEF in operation 2 to relate the received parameter with a particular subscribed DNN and/or S-NSSAI. The UDM stores the SMF- Associated parameters under corresponding Session Management Subscription data type.

[0078] Each parameter or parameter set may be associated with a validity time. The validity time is stored at the UDM/UDR and in each of the NFs, to which parameters are provisioned (e.g., in AMF or SMF). Upon expiration of the validity time, each node deletes the parameters autonomously without explicit signalling.

[0079] At operation 5, the UDM responds to the request with a Nudm_Param eterProvision_Create/U pdate/Del ete Respon se . If the procedure failed, the cause value indicates the reason.

[0080] At operation 6, the NEF responds to the request with a

Nnef ParameterProvision Create/Update/Delete Response. If the procedure failed, the cause value indicates the reason.

[0081] At operation 7, which is conditional and occurs only after a successful operation 4, the UDM notifies the subscribed Network Function (e.g., AMF) of the updated UE and/or Group subscription data via a Nudm SDM Notification Notify message.

[0082] a) If the NF is the AMF, the UDM performs a

Nudm SDM Notification (SUPI or Internal Group Identifier, AMF- Associated parameters, etc. ) service operation. The AMF identifies whether there are overlapping parameter set(s) and merges the parameter set(s) in the Expected UE Behavior. The AMF uses the received AMF- Associated parameters to derive the appropriate UE configuration of the NAS parameters and to derive Core Network assisted RAN parameters. The AMF may determine a Registration area based on parameters Stationary indication or Expected UE Moving Trajectory.

[0083] b) if the NF is the SMF, the UDM performs a Nudm_SDM_Notification (SUPI or Internal Group Identifier, SMF-Associated parameter set, DNN/S-NSSAI, etc.) service operation.

[0084] The SMF stores the received SMF-Associated parameters and associates the SMF-Associated parameters with a PDU Session based on the DNN and S-NSSAI included in the message from UDM. The SME identifies whether there are overlapping parameter set(s) in the Expected LIE behaviour and merges the parameter set(s). The SMF may use the SMF-Associated parameters as follows:

[0085] The SMF configures the UPF accordingly. The SMF can use the Scheduled Communication Type parameter or Suggested Number of Downlink Packets parameter to configure the UPF with how many downlink packets to buffer. The SMF may use the parameter Communication duration time to determine to deactivate the user plane (UP) connection and to perform core network (CN)-initiated selective deactivation of UP connection of an existing PDU Session.

[0086] The SMF may derive the SMF-derived CN-assisted RAN information for the PDU Session. The SMF provides the SMF derived CN assisted RAN information to the AMF as described in PDU Session establishment procedure or PDU Session modification procedure. The NEF or the UDM can also update the corresponding UDR data via a Nudr_DM_Create/Delete service operation as appropriate.

[0087] The AF request sent to the NEF contains the information as b el owe

[0088] 1) Service Description. The Service Description is the information to identify a service the Service Parameters are applied to. The Service Description in the AF request can be represented by the combination of DNN and S-NSSAI, an AF-Service-Identifier or an application identifier.

[0089] 2) Service Parameters. The Service Parameters are the service specific information to be provisioned in the Network and delivered to the UE in order to support the service identified by the Sendee Description. [0090] 3) Target UE(s) or a group of UEs. The target UE(s) or a group of UEs indicate the UE(s) to whom the Sendee Parameters are to be delivered. Individual UEs can be identified by GPSI, or an IP address/Prefix or a MAC address. Groups of UEs can be identified by an External Group Identifiers as defined in TS 23,682. If identifiers of target UE(s) or a group of UEs are not provided, then the Sendee Parameters are be delivered to any UEs using the service identified by the Service Description.

[0091] The NEF authorizes the AF request received from the AF and stores the information in the UDR as "Application Data". The Service Parameters are delivered to the targeted UE by the PCF when the UE is reachable.

[0092] FIG. 5 illustrates service-specific information provisioning in accordance with some aspects. The AF uses Nnef_SendceParameter service shown in FIG. 5 to provide the service specific parameters to the PLMN and the UE.

[0093] At operation 1, to create a new request, the AF invokes an Nnef_ServiceParameter_Create sendee operation. To update or remove an existing request, the AF invokes an Nnef ServiceParameter Update or Nnef_ServiceParameter_Delete service operation together with the corresponding Transaction Reference ID which was provided to the AF in a Nnef_ServiceParameter_Create response message. The content of this sendee operation (AF request) includes the information described in TS 23.502 clause 5.2.6.1 1 .

[0094] At operation 2, the AF sends its request to the NEF. The NEF authorizes the AF request. The NEF performs the following mappings: map the AF-Service-Identifier into a DNN and S-NSSAI combination, determined by local configuration; map the GPSI in the Target UE Identifier into the SUPI, according to information received from the UDM; and map the External Group Identifier in the Target UE Identifier into Internal Group Identifier, according to information received from UDM. For a Nnef_ServiceParameter_Create service operation, the NEF assigns a Transaction Reference ID to the Nnef_ServiceParameter Create request.

[0095] At operation 3, for a Nnef ServiceParameter Create or Update service operation, the NEF stores the AF request information in the UDR as the "Application Data" (Data Subset setting to "Service specific information") together with the assigned Transaction Reference ID. For a

Nnef ServiceParameter ...delete service operation, the NEF deletes the AF request information from the UDR.

[0096] At operation 4, the NEF responds to the AF. For a Nnef_ServiceParameter_Create response message, the response message includes the assigned Transaction Reference ID. If the LIE is registered to the network and the PCF performs the subscription to notification to the data modified in the UDR by invoking a Nudr ..DM Subscribe (AF service parameter provisioning information, SUPI, Data Set setting to "Application Data", Data Subset setting to "Service specific information") at operation 0, the following operations are performed:

[0097] At operation 5, the PCF(s) receive(s) a Nudr_DM_Notify notification of a data change from the UDR. The PCF does not have to subscribe for each UE the application specific information, e.g., if the PCF has already received the application specific information for a group of UE or for a DNN by a subscription of other UE. The same application specific information is delivered to every UE in a group or a DNN.

[0098] At operation 6, the PCF initiates UE Policy delivery as specified in TS 23.502 clause 4.2.4.3.

[0099] The UE Configuration Update procedure for transparent UE Policy delivery is initiated when the PCF wants to update UE policy information (i.e., UE policy) in the UE configuration. In the non-roaming case, the V-PCF is not involved and the role of the H-PCF is performed by the PCF. For the roaming scenarios, the V-PCF interacts with the AMF and the H-PCF interacts with the V-PCF.

[00100] FIG. 6 illustrates a UE Configuration Update procedure for transparent UE Policy delivery' in accordance with some aspects. In FIG. 6, at operation 0, the PCF decides to update UE policy based on triggering conditions such as an initial registration, registration with the 5GS when the UE moves from the EPS to the 5GS, or for updating UE policy as follows:

[00101] For initial registration and registration with the 5GS when the UE moves from the EPS to the 5GS, the PCF compares the list of PSIs included in the UE policy information in the Npcf_UEPolicyControl_Create request and determines, as described in clause 6.1.2.2.2 of TS 23.503, whether UE policy information is to be updated and be provided to the UE via the AMF using a DL NAS TRANSPORT message. For network-triggered UE policy update (e.g., the change of UE location, the change of Subscribed S-NSSAIs as described in clause 6. 1.2.2.2 of TS 23.503), the PCF checks the latest list of PSIs to decide which UE policies are to be sent to the UE.

[00102] The PCF checks if the size of the resulting UE policy information exceeds a predefined limit. If the size is under the limit, UE policy information is included in a single Namf Communication NlN2MessageTransfer service operation as described below. If the size exceeds the predefined limit, the PCF splits the UE policy information into smaller, logically independent UE policy information, thereby ensuring that the size of each is under the predefined limit. Each piece of UE policy information is then sent in separated

Namf __Communication___NIN2MessageTransfer service operations as described below.

[00103] NAS messages from the AMF to UE do not exceed the maximum size limit allowed in NG-RAN (PDCP layer), so the predefined size limit in the PCF is related to that limitation. The mechanism used to split the UE policy information is described in TS 29.507.

[00104] At operation 1, the PCF invokes a

Namf_Communication_NlN2MessageTransfer service operation provided by the AMF. The message includes the SUPI, UE Policy Container.

[00105] At operation 2, if the UE is registered and reachable by the AMF in either 3GPP access or non-3GPP access, the AMF transfers the UE Policy container transparently to the UE via the registered and reachable access. If the UE is registered in both 3GPP and non-3GPP accesses and reachable on both access and served by the same AMF, the AMF transfers the UE Policy container transparently to the UE via one of the accesses based on the AMF local policy. If the UE is not reachable by the AMF over both 3 GPP access and non-3GPP access, the AMF reports to the PCF that the UE Policy container could not be delivered to the UE using

Namf_Communication_N1N2TransferFailureNotification as in operation 5 in TS 23.502 clause 4.2.3.3. [00106] If AMF decides to transparently transfer the UE Policy container to the UE via 3GPP access, e.g., the UE is registered and reachable by the AMF in 3 GPP access only, or if the UE is registered and reachable by the AMF in both 3 GPP and non-3GPP accesses served by the same AMF and the AMF decides to transparently transfer the UE Policy container to the UE via 3GPP access based on local policy, and the UE is in CM- IDLE and reachable by the AMF in 3 GPP access, the AMF starts the paging procedure by sending a Paging message described in operation 4b of Network Triggered Service Request (in TS 23.502 clause 4.2.3.3). Upon reception of the paging request, the UE initiates the UE Triggered Service Request procedure (TS 23.502 clause 4.2.3.2).

[00107] At operation 3, if the UE is in a CM-CONNECTED mode over 3GPP access or non-3GPP access, the AMF transparently transfers the UE Policy container (UE policy information) received from the PCF to the UE. The UE Policy container includes the list of Policy Sections as described in TS 23.503.

[00108] At operation 4, the UE updates the UE policy provided by the PCF and sends the result to the /AMF.

[00109] At operation 5, if the AMF received the UE Policy container and the PCF subscribed to be notified of the reception of the UE Policy container then the AMF forwards the response of the UE to the PCF using a Namf_Communication_NlMessageNotify service operation. The PCF maintains the latest list of PSIs delivered to the UE and updates the latest list of PSIs in the UDR by invoking a Nudr_DM_Update (SUPI, Policy Data, Policy- Set Entry, updated PSI data) sendee operation. If the PCF is notified about a UE Policy delivery failure, the PCF may initiate a UE Policy Association Modification procedure to provide a new trigger "Connectivity state changes" in Policy Control Request Trigger of UE Policy Association to AMF as defined in 23.502 clause 4.16.12.2.

[00110] For backward compability, the PCF may subscribe the "Connectivity state changes (IDLE or CONNECTED)" event in Rel-15 AMF as defined in 23.502 clause 5.2.2.3.

[00111] SoR list related TSs: TS 22.011 subclause 3.2.2.8, TS 22.261 subclause 6.30 for SoR and 6.1 for network slicing, TS 23.122 - The purpose of the control plane solution for steering of roaming in the 5GS procedure is to allow the HPLMN to update the "Operator Controlled PLMN Selector with Access Technology" list in the UE by providing the HPLMN protected list of preferred PLMN/access technology combinations via NAS signalling, TS 24.501 : SoR list PLMN ID and access technology identifier are provided in decreasing order of priority, i.e., PLMN ID 1 indicates highest priority and PLMN ID n indicates lowest priority.

[00112] Various solutions may be used to resolve three open issues based on the association of an application and applicable network slices in the same or different PLMNs. Solution 1 : new service requirements. Solution 2: an AF request may be used for PCF inferencing of application classification and specific parameters update via a UE policy configuration update procedure for application policies. Solution 3 and Solution 4: an AF request for specific parameters update via a UE policy configuration update procedure for application specific steering of roaming policies, which takes precedence over a steering of roaming policy provided by the HPLMN. Solution 5: user preferences setting for the applications which can be used before the change of the PLMN is triggered for the network slice of an application.

[00113] An S-NSSAI can have standard values (i.e., such a S-NSSAI may only contain an SST with a standardized SST value, see clause 5.15.2.2, and no SD) or non-standard values (i.e., such S-NSSAI may contain both an SST and an SD, or only an SST without a standardized SST value and no SD). An S-NSSAI with a non-standard value identifies a single Network Slice within the PLMN with which the S-NSSAI is associated. An S-NSSAI with a non-standard value is not used by the UE in access stratum procedures in any PLMN other than the one to which the S-NSSAI is associated.

[00114] Based on TS23.501, clause 5.15.2.2: Standardized SST value: Standardized SST values provide a way for establishing global interoperability for slicing so that PLMNs can support the roaming use case more efficiently for the most commonly used SSTs, The standardized SSTs are provided in the following Table 5.15.2.2-1. Table 5.15.2.2-1 - Standardized SST values

[00115] The solutions to the issues above are applicable and extendable for the standardized SST values that are defined in future releases.

[00116] Solution 1: new service requirements. A first service requirement is that the 5G network provides a mechanism for the third party to provision network slice-related information, e.g., priority, QoS level, network slice type, etc. for its applications users for the network to configure the association of proper network slice and the application for the UE. A second sendee requirement is that the 5G network provides a mechanism to configure the UE with a network slicing configuration related to a preferred network operators list of an application that is considered for sponsor connectivity and precedence over the steering of roaming (SoR) policy provided by the HPLMN. A third sendee requirement is that the 5G system allows the LIE to store user preferences of the applications in priority order that is used to determine whether to move to preferred network when different applications are activated and use different network slices in different network.

[00117] Solution 2: AF request for PCF inferencing of application classification and specific parameters update via UE policy configuration update procedure for application policies. This supports an AF request for provisioning parameters related to the association of application and the SST shown in FIG. 4 based on the following procedure:

[00118] Operation 0: the NF is the PCF.

[00119] Operation 1 : the AF provides one or more parameter(s) to be created or updated in a Nnef ParameterProvi si on Create or

Nnef_ParameterProvision_Update or Nnef_ParameterProvision_Delete Request to the NEF. [00120] The payload of the Nnef_ParameterProvision_Update Request includes one or more of the following parameters:

Tabie-1: Description of Expected Application Configuration parameters

[00121] The parameters are classified in the UDM as PCF-Associated parameters and sent to the PCF .

[00122] Operation 2, 3 and 7: the message contains the Expected Application Configuration parameters.

[00123] Solution 2.1 :

[00124] Following solution 2, the PCF can further use the parameters of SST and OSID+APPID(s) to configure the S-NSSAI with a configured SST for an OSID+APPID, in which the OSID is based on a UE state indication included in the registration request message from the UE. The AMF can include an Operator defined access categoiy with both the S-NSSAI and OSID+APPID(s) in the registration accept message to the UE.

[00125] With Operator defined access categoiy information, the UE can determine the association between the OSID+AppID and S-NSSAI and can establish a PDU session with an allowed S-NSSAI when receiving an upper layer request from the application identified by the OSID+AppID.

[00126] Solution 2.2:

[00127] Also following solution 2, if preferred QoS sendee requirements are provided, the PCF can further use the parameters to provide sendee differentiation to the UEs based on the SD among S-NSSAIs with the same SST of the application. Two methods may be used to provide sendee differentiation for different UEs: [00128] The SD of the S-NSSAI can be used in configuring S-NSSAIs wdth different QoS requirements. As such, the 5G network can allocate S- NSSAI&1 with a higher QoS requirement for user!, who has a platinum membership of an application, and allocate S-NSSAI #2 wdth regular QoS requirements for user 2, who has a regular membership. Such an association can be provided in the Operator defined access category. Further, the precedence value of the Operator defined access category’ can be set between S-NSSAI(s) with the same configured SSI' and an OSID+APPID. For example, user! (platinum membership) can have a higher precedence value of one Operator defined access category of S-NSSAI#1 and OSID+APPID than user2 (regular membership), while user2 can have a higher precedence value of one Operator defined access category of S-NSSAI&2 and OSID+APPID than userl.

[00129] Solution 3:

[00130] This provides a manner in which the network is to properly assign a network slice for an application. Specifically, the AF issues requests on behalf of applications not owned by the PLMN serving the UE by referring to TS 23.502 clause 4.15.6.7, in which the AF request contains service description, service parameters and target UE or a group of UEs, and in which Service Parameters are the service specific information which is to be provisioned in the Network and delivered to the UE in order to support the sendee identified by the Service Description.

[00131] The addition to TS 23.502 clause 4.15.6.7 includes, as shown in FIG. 5: the service description includes the SST type of network slice or SST type + preferred SD of the network slice for the application identified by the OSID+APPID. The PCF uses service parameters and service descriptions to configure the association of the network slice and Application. During the registration procedure shown in FIG. 5, the AMF can configure the Operator defined access category information and provide the information to the target UEs. The PCF uses service parameters and service descriptions to configure the association of the network slice and Application and provision the association to the target UEs. With both information of sendee parameters and Operator defined access category', the UE can determine the association between the OSID+AppID and S-NSSAI and can establish a PDU session with an allowed S- NSSAI when receiving an upper layer request from the application identified by the OSID+AppID.

[00132] Solution 4:

[00133] The AF requests for a specific parameters update via a UE policy configuration update procedure for application specific SoR policies. These parameters take precedence over SoR policy provided by the HPLMN.

Following solution 3, this may permit the UE to select proper network slices for an application provided by a third party having an SLA with different network operators and have preferred PLMNs of its applications by altering FIG. 5 so that the service parameters include the application preferred PLMN ID lists. [00134] If the UE stores the SOR list with a network slices combination and the service parameters of a combination of DNN/SST or S-

NSSAI/ Appli cation ID and the application preferred PLMN ID lists, the UE selects a preferred PLMN with the highest priority in coverage based on application preferred PLMN ID lists. That is, the application-preferred PLMN ID lists takes precedence over the SOR list with the network slice combination. \ [00135] Solution 4.1 :

[00136] Following solution 4, the sendee parameters of the application preferred PLMN ID lists is for sponsor connectivity, in which the chargeable party of sponsor connectivity is the third-party service provider. This permits a third-party that has SLAs with some network operators to provide sponsor connectivity for its application users. As such, the UE takes precedence of the application preferred PLMN ID lists precedence over the SOR list with the network slice combination only when the preferred PLMN ID lists are for sponsoring the PDU sessions of the network slice.

[00137] Solution 5:

[00138] This solution may permit the UE to prioritize the use of network slices used by different applications. The UE configures user preference with the priority of APPID&1, APPID&2, etc. When APP#X is activated, the UE checks user preferences of the APP preference list and decides whether to stay in the current PLMN if the preferred PLMN ID lists of the APP#X is different from the senring PLMN. Alternatively, the UE presents a notification information to obtain user consent before continuing the procedure to change the PLMN for the APP#X if the preferred PLMN ID iists of the APP#X is different from the servi ng PLMN.

[00139] Although an embodiment has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

[00140] The subject matter may be referred to herein, individually and/or collectively, by the term “embodiment” merely for convenience and without intending to voluntarily limit the scope of this application to any single inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description. [00141] In this document, the terms "a" or "an" are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a nonexclusive or, such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise indicated. In this document, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, that is, a system, UE, article, composition, formulation, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

[00142] The Abstract of the Disclosure is provided to comply with 37 C.F.R. § 1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

Claims

CLAIMS What is claimed is:

1. An apparatus for a user equipment (UE), the apparatus comprising: processing circuitry configured to: decode, from a public land mobile network (PLMN), network slice-related information of a third party, the network slice-related information comprising an association between network slice and applications, the applications including an application of the third party, activate the application after reception of the network slice- related information; and in response to activation of the application, select a network slice based on the network slice-related information; and a memory configured to store the network slice-related information.

2. The apparatus of claim I, wherein: the network slice-related information comprises a network slicing configuration that is based on a preferred network operators list of applications considered for sponsor connectivity, and the processing circuitry is further configured to use the network slicing configuration over a steering of roaming (SoR) policy provided by a home PLAIN (HPLMN) of the UE.

3. The apparatus of claim 1, wherein: the processing circuitry is further configured to decode the network slice- related information from a serving PLMN, the serving PLMN is one of a home PLMN (HPLMN) or visiting PLMN, the network slice-related information is based on service specific information to support a service identified by a service description, and the sendee specific information is contained in sendee parameters in an application function (AF) request that contains the service description, the sendee parameters, and a target UE or group of UEs.

4. The apparatus of claim 3, wherein the sendee description includes a Slice/Service type (SST) type of a network slice or an SST type and preferred service differentiator (SD) of the network slice for an application identified by an operating system identifier (OSID) and application identifier (APPID).

5. The apparatus of claim 3, wherein: the network slice-related information containing an association between network slices and applications from an access and mobility function (AMF) or a policy and charging function (PCF), the association configured by the PCF using sendee parameters and sendee descriptions in AF request, and after registration with the serving PLMN, the processing circuitry is further configured to decode operator-defined access category' information from the AMF.

6. The apparatus of claim 5, wherein the processing circuitry' is further configured to: determine, based on the sendee parameters and operator-defined access category information, an association between an operating system identifier (OSID) and application identifier (AppID) of an application and Single - Network Slice Selection Assistance Information (S-NSSAI), and establish a packet data unit (PDU) session with arequested S-NSSAI within allowed S-NSSAIs in response to reception of an upper layer request from the application identified by a particular OSID and AppID.

7. The apparatus of claim 3, wherein: the sendee parameters include application preferred PLMN ID lists, and the processing circuitry' is further configured to use the applicationpreferred PLMN ID lists over a steering of roaming (SoR) list with network slice combinations provided by a home public land mobile network (HPLMN) of the UE.

8. The apparatus of claim 7, wherein the processing circuitry/ is further configured to select a preferred PLMN with a highest priority in coverage based on the application preferred PLMN ID lists.

9. The apparatus of claim 8, wherein service parameters of the application preferred PLMN ID lists is for sponsor connectivity, in which a chargeable party of the sponsor connectivity is a service provider of the third-party.

10. The apparatus of claim 1, wherein the processing circuitry' is further configured to: activate another application; determine that the application and the other application are to use different network slices in different PLMNs; and determine whether to move from the PLMN to a different PLMN based on stored user preferences of the application and the other application in priority order.

11 . The apparatus of claim 10, wherein the processing circuitry is further configured to determine whether to move from the PLMN to the different PLMN based on priorities of applications identified by application IDs in an application preference list, a determination of whether to stay in the PLMN based on whether a preferred PLMN ID of the application is different from the PLMN .

12. The apparatus of claim 11 , wherein the processing circuitry is further configured to, in response to a determination to switch to the other PLMN, generate a notification to obtain user consent to switch to the other PLMN prior to switching to the other PLMN.

13. The apparatus of claim 1, wherein the network slice-related information includes priority, quality of sendee (QoS) level, and slice/service type (SST).

14. An apparatus for policy and control function (PCF), the apparatus comprising: processing circuitry- configured to: encode, for transmission to a unified data management (UDM), a Nudm SDM Subscribe Request; and decode, from the UDM in response to the Nudm_SDM_Subscribe Request, a Nudm_SDM_Notifi cation that contains expected application configuration parameters from an application function (AF) to a network exposure function (NEF) in a Nnef_ParameterProvision_Update Request, the expected application configuration parameters comprising: an operating system identifier (OSID) and application identifier (AppID) that identifies an application to which a user equipment (UE) has subscribed, and a slice/service type (SST) that identifies an associated SST used for the application for a network slice of a serving network; and a memory configured to store the expected application configuration parameters.

15. The apparatus of claim 14, wherein: the processing circuitry is further configured to configure a Single - Network Slice Selection Assistance Information (S-NSSAI) using the SST for an associated OSID and AppID, and the OSID is based on a UE state indication included in a registration request message from the UE and an operator-defined access category with the S-NSSAI and OSID and APPID in a registration accept message to the UE.

16. The apparatus of claim 14, wherein the expected application configuration parameters further comprise preferred quality of service (QoS) service requirements that identify QoS parameters for the UE using the application.

17. The apparatus of claim 16, wherein: the processing circuitry' is further configured to use the expected application configuration parameters to provide sendee differentiation to the UE based on a service differentiator (SD) among Single - Network Slice Selection Assistance Information (S-NSSAIs) with the same SST of the application, and at least some of the S-NSSAIs with different SDs have different QoS requirements, the QoS requirements associated with different user membership levels for the application.

18. The apparatus of claim 14, wherein: the processing circuitry is further configured to: decode AF requests sent on behalf of applications not owned by a public land mobile network (PLMN) serving the UE, each request contains service description, service parameters and target UE or a group of UEs, in which the service parameters are service specific information to be provisioned in the PLAIN and delivered to the UE to support the service identified by the sendee description, and use the sendee parameters and sendee description to configure an association of the network slice and application and provision the association to target UEs, and the service description includes an SST of a network slice or SST and a preferred sendee differentiator (SD ) of the network slice for the application identified by the OSID and AppID.

19. A non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of a user equipment (UE), the one or more processors to configure the UE to, when the instructions are executed: decode, from a public land mobile network (PLMN), network slice- related information comprising an association between network slices and applications; activate a first application after reception of the network slice-related information; select a network slice of the PLMN based on the network slice-related information and stored user preferences; activate a second application after activation of the first application; and in response to activation of the second application: determine that a preferred PLMN of the second application is different from the PLMN, and determine which of the preferred PLMN of the second application and the PLMN to use based on the user preferences, the user preferences containing an app preference list that contains priorities of the first and second applications.

20. The medium of claim 19, wherein the instructions when executed further configure the one or more processors to configure the UE to in response to a determination to switch from the PLMN to the preferred PLMN of the second application, obtain user consent of the switch prior to switching from the PLMN to the preferred PLMN of the second application.