Dynamic network capability configuration

By introducing a network capability layer and a network capability profile mechanism, UEs can directly request and configure the required network capabilities, solving the problem that UEs cannot directly indicate network capabilities in the 5G core network. This enables more flexible and efficient network slicing configuration, which is suitable for IoT and V2X applications.

CN118945216APending Publication Date: 2024-11-12INTERDIGITAL PATENT HOLDINGS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411112543.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2019-11-06
Filing Date
2020-03-13
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

In the service-based architecture of 5G core networks, user equipment (UE) cannot directly indicate the required network capabilities, resulting in insufficient flexibility and dynamism in network slice configuration. This is especially true for IoT devices and V2X applications, where existing methods are complex and cannot automatically configure the required network capabilities.

Method used

The introduction of the Network Capability Layer and Network Capability Profile (NCP) mechanism allows UEs to dynamically request and configure network capabilities. Through the collaboration of the Network Capability Management Function (NCMF) and core network entities, it identifies and configures network slices that support the required capabilities, and provides network capability information and update mechanisms.

Benefits of technology

It enables more flexible and dynamic network capability configuration, simplifies the network capability request process for UEs, and improves the adaptability and efficiency of network slicing, especially for complex applications such as IoT and V2X, reducing the complexity of registration and slice updates.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945216A_ABST
    Figure CN118945216A_ABST
Patent Text Reader

Abstract

The disclosure relates to dynamic network capability configuration. Methods and apparatus are described for configuring required network capabilities in a service-based network, including methods for a UE to initiate a network capability-based registration to configure its required network capabilities, methods for UEs to initiate network capability-based registration updates when UEs have registered to a network and want to dynamically reconfigure their network capabilities, and methods for network capability-based UE configuration updates, which allow an NF or AS to initiate updates to network capabilities in a network slice for UEs.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the patent application with international application number PCT / US2020 / 022573 and national application number 202080027816.7, entitled “Dynamic Network Capability Configuration”, filed on March 13, 2020.

[0002] Citation of Related Applications

[0003] This application claims priority to U.S. Patent Application No. 62 / 817,811 filed on March 13, 2019 and U.S. Patent Application No. 62 / 931,376 filed on November 6, 2019, which are incorporated herein by reference in their entirety. Background Art

[0004] The 3rd Generation Partnership Project (3GPP) develops technical standards for cellular telecommunication network technologies, including radio access, core transport networks, and service capabilities - including work on codecs, security, and quality of service. Recent Radio Access Technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), and LTE-Advanced standards. 3GPP has begun work on the standardization of the next generation cellular technology known as New Radio (NR), also referred to as "5G".

[0005] The 5G Core Network (5GC) includes a service-based architecture (SBA) based on the concepts of network slicing and virtualized network functions (NFs). Different network functions, such as access and mobility management function (AMF), session management function (SMF) and policy control function (PCF), provide different network function services via service-based interfaces. This means that service consumers can use the same messages and the same procedures to communicate with service providers. For example, any NF can subscribe to the same events using the event open service provided by AMF. On the other hand, various network capabilities such as non-IP data delivery (NIDD), background data transfer (BDT) and power saving mode (PSM) can be implemented through a set of NF services. Under the current SBA framework, the UE can configure and access the network by indicating the requested network slice selection assistance information (NSSAI) to identify the network slice. There is no way for the UE to directly indicate the required network capabilities. Summary of the invention

[0006] Although under the current SBA framework of 5GC, the UE can configure and access the network by indicating the requested NSSAI that identifies the network slice, the UE has no way to directly indicate the required network capabilities.

[0007] Disclosed herein are methods and apparatus for configuring required network capabilities in a service-based network.

[0008] In one aspect, a new framework is described that includes a network capability layer. UE and AS can dynamically request network capabilities (e.g., background data transfer, non-IP data transfer) to support their applications. In one implementation, UE and AS may not need to know or care which network slice supports the requested network capability, or whether the serving network slice can support the requested network capability. The core network entity can determine and configure the network slice that supports all requested network capabilities.

[0009] In yet another aspect, a method for a UE to initiate network capability-based registration to configure its required network capabilities is described.

[0010] In yet another aspect, a method is described for a UE to initiate a network capability based registration update when the UE is already registered with the network and wants to dynamically reconfigure their network capabilities.

[0011] In another aspect, a method for UE configuration update based on network capabilities is described, which allows an NF or application server to initiate an update to network capabilities in a network slice for a UE.

[0012] An extended service-based architecture is also described, which includes an interface with a user plane function (UPF) and the services provided by the UPF.

[0013] A mechanism by which the network can transmit network capability information of a network slice called Network Capability Profile (NCP) to the UE.

[0014] A method in which the network can notify a UE of alternative network slices with comparable network capability profiles based on the network capabilities requested by the UE. A mechanism for a UE to initiate a network capability-based registration to configure its required network capabilities.

[0015] A mechanism by which a UE may receive a set of allowed NSSAIs and their corresponding NCPs during the normal UE registration procedure. If the capabilities indicated by the received NCPs are insufficient for the application in the UE, the UE may be able to request an alternative network slice based on the NCP list of allowed S-NSSAIs received from the core network.

[0016] A mechanism by which the NCP of a network slice is transmitted to the UE as part of the UE policy during the UE policy update procedure.

[0017] A mechanism by which the core network enforces a maximum number of PDU sessions per network slice during the PDU session establishment process and handles requests received after the maximum limit is reached.

[0018] A mechanism where the core network handles a maximum limit on the number of PDU sessions per network slice, where the network periodically informs the UE via NAS messages that a network slice has reached its maximum limit, so that the UE can wait before retrying.

[0019] A mechanism by which the core network enforces a maximum number of UE registrations per network slice and processes registration requests received after the maximum limit has been reached.

[0020] This summary is provided to introduce some concepts in a simplified form, which will be further described in the detailed description below. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. In addition, the claimed subject matter is not limited to limitations that solve any or all deficiencies mentioned in any part of this disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] A more detailed understanding may be obtained from the following description given by way of example in conjunction with the accompanying drawings, in which:

[0022] Figure 1A illustrates an example communication system;

[0023] Figure 1B is a block diagram of an example device or apparatus, such as a wireless transmit / receive unit (WTRU), configured for wireless communications;

[0024] Figure 1C is a system diagram of an example radio access network (RAN) and core network;

[0025] Figure 1D is another example system diagram of RAN and core network;

[0026] Figure 1E is another example system diagram of RAN and core network;

[0027] Figure 1F is another example system diagram of RAN and core network;

[0028] Figure 1G is a block diagram of an example computing system in which nodes, entities, devices, or other equipment of a communication system may be included;

[0029] Figure 2A represents a non-roaming 5G reference architecture with a service-based interface to the control plane;

[0030] Figure 2B The non-roaming 5G system architecture is shown with reference point representation;

[0031] Figure 3 Examples of network functions, NF services, and NF service operations are presented;

[0032] Figure 4 An example of a "request-response" NF service is shown;

[0033] Figure 5 An example showing a "Subscribe-Notify" NF service;

[0034] Figure 6 Represents a network capability configuration use case;

[0035] Figure 7 represents an example network architecture having a network capability layer;

[0036] Figure 8 represents the method used for network capability-based registration;

[0037] Fig. 9 Represents a method for registration updates based on network capabilities;

[0038] Fig.10 Represents a method for UE configuration update based on network capabilities;

[0039] Fig.11 represents an example extended service-based architecture with UPF and Nupf interfaces; and

[0040] Fig.12 An example graphical user interface (GUI) for configuring network capabilities in a communication network is shown.

[0041] Fig.13 Represents the method for using the registration process for the network capability profile on the requested NSSAI.

[0042] Fig.14 Represents a method for delivering a network capability profile to a UE as part of the UE policy.

[0043] Fig.15 Indicates the method used to handle the maximum number of PDU sessions in a network slice by the network.

[0044] Fig.16 Indicates the method for using NAS notification to handle the maximum number of PDU sessions in a network slice.

[0045] Fig.17 Represents the process of handling the maximum number of UEs in a network slice.

[0046] Fig.18 An example graphical user interface (GUI) is shown showing that a UE receives an NCP from a network and the UE either accepts the NCP or can request a new NCP. DETAILED DESCRIPTION

[0047] The following is a list of acronyms that may appear in the following description. Unless otherwise stated, the acronyms used in this article refer to the corresponding terms listed below.

[0048] 5GC 5G Core

[0049] AF application function

[0050] AMF access and mobility management function

[0051] AS Application Server

[0052] CN Core Network

[0053] CP Control Plane

[0054] DL Downlink

[0055] DNN data network name

[0056] EPC Evolved Packet Core

[0057] GUTI Globally Unique Temporary Identifier

[0058] LTE Long Term Evolution

[0059] MBMS Multimedia Broadcast / Multicast Service

[0060] MME mobility management entity

[0061] NAS non-access layer

[0062] NCMF network capability management function

[0063] NCP Network Capability Profile

[0064] NEF network open function

[0065] NF Network Function

[0066] NIDD Non-IP Data Transfer

[0067] NRF NF storage function

[0068] NSSAI Network Slice Selection Assistance Information

[0069] NSSF network slice selection function

[0070] NSI network slicing example

[0071] PCF policy control function

[0072] PDU protocol data unit

[0073] PSM power saving mode

[0074] QoS Quality of Service

[0075] RAN Radio Access Network

[0076] PLMN Public Land Mobile Network

[0077] SBA Service-Based Architecture

[0078] SCS Service Capability Server

[0079] SD slice specifier

[0080] SM Session Management

[0081] SMF session management function

[0082] SMSF Short Message Service (SMS) Function

[0083] S-NSSAI Single Network Slice Selection Auxiliary Information

[0084] SST Slice / Service Type

[0085] SUPI Subscription Persistent Identifier

[0086] UDM / UDR unified data management / unified data storage

[0087] UE User Equipment

[0088] UL Uplink

[0089] UPF user plane function

[0090] The following terms may have the following meanings:

[0091] "Core Network" refers to the central or core part of a telecommunications network that provides many communication services to customers that are interconnected through a radio access network. A core network typically includes multiple entities that perform the functions of the core network. The term "core network entity" as used herein refers to any entity that performs the functions of a core network, such as AMF, UDR / UDSF, UDM / UDR, NRF, NEF, PCF, NF, SMF, AUSF, NSSF, etc., as described herein. It should be understood that such a core network entity may be a logical entity implemented in the form of software (i.e., computer executable instructions) stored in a device configured for wireless and / or network communications or such as a Figure 1B or Figure 1G The method is stored in the memory of the computer system shown in the figure and executed on the processor of the device or computer system.

[0092] "Network Function (NF)" refers to a processing function in a network, which has a defined functional behavior and a defined interface. NF can be implemented as a network element on dedicated hardware, or as a software instance running on dedicated hardware, or as a virtualized function instantiated on an appropriate platform (e.g., on a cloud infrastructure).

[0093] “Network Function Instance” refers to an identifiable instance of a NF.

[0094] A "network function (NF) service" may be a type of capability exposed by a NF ("NF service provider") to another authorized NF ("NF service consumer") through a service-based interface. A network function may expose one or more NF services. For example, the 5G AMF provides the Namf_EventExposure service, which enables the AMF to send notifications to NFs that subscribe to certain mobility management related events.

[0095] “NF service instance” refers to an identifiable instance of a NF service.

[0096] "Network capabilities" include transport network features that the core network implements and provides to its users (e.g., UE or application server). Examples of network capabilities include background data transfer and event monitoring. Network capabilities are enabled by one or more NF services of one or more NFs.

[0097] A "network slice" is a logical network that provides specific network capabilities and network characteristics.

[0098] A “network slice instance” includes the required resources (e.g., computing, storage, and networking resources) and a set of NF instances to form a deployed network slice.

[0099] A “Network Capability Profile” is an information profile of each network slice maintained by the NCMF, which indicates what network capabilities the network slice supports.

[0100] "Network Capability Management Function" is the NF that configures the network slice to provide a set of required network capabilities to the UE / AS. NCMF can be part of the OAM system.

[0101] The 3rd Generation Partnership Project (3GPP) develops technical standards for cellular telecommunication network technologies, including radio access, core transport networks, and service capabilities - including work on codecs, security, and quality of service. Recent radio access technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), and LTE-Advanced standards. 3GPP has begun work on the standardization of the next generation cellular technology called New Radio (NR) (also referred to as "5G"). 3GPP NR standard development is expected to include the definition of the next generation radio access technology (new RAT), which is expected to include the provision of new flexible radio access below 6 GHz, and the provision of new ultra-mobile broadband radio access above 6 GHz. Flexible radio access is expected to consist of new non-backward compatible radio access in new spectrum below 6 GHz, and is expected to include different operating modes that can be multiplexed together in the same spectrum to address a wide range of 3GPP NR use cases with different requirements. Ultra-mobile broadband is expected to include cmWave and mmWave spectrum, which will provide opportunities for ultra-mobile broadband access for indoor applications and hotspots, for example. In particular, ultra-mobile broadband is expected to share a common design framework with sub-6 GHz flexible radio access, with cmWave and mmWave-specific design optimizations.

[0102] 3GPP has identified a variety of use cases that the New Radio (NR) is expected to support, resulting in a wide variety of user experience requirements for data rates, latency, and mobility. Use cases include the following general categories: enhanced mobile broadband (e.g., broadband access in dense areas, ultra-high broadband access indoors, broadband access in crowds, 50+Mbps everywhere, ultra-low-cost broadband access, mobile broadband in vehicles), emergency communications, massive machine-type communications, network operations (e.g., network slicing, routing, migration and interworking, energy saving), and enhanced vehicle-to-everything (eV2X) communications. Specific services and applications in these categories include, for example, surveillance and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based office, first responder connectivity, car emergency calls, disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality, tactile Internet, and virtual reality, to name a few. All of these and other use cases are contemplated herein.

[0103] Figure 1AThe diagram illustrates one embodiment of an example communication system 100 in which the methods and apparatus described and claimed herein may be embodied. As shown, the example communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, and / or 102d (which may be generally or collectively referred to as WTRUs 102), a radio access network (RAN) 103 / 104 / 105 / 103b / 104b / 105b, a core network 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it should be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each WTRU 102a, 102b, 102c, 102d, 102e may be any type of device or apparatus configured to operate and / or communicate in a wireless environment. Although in the Figures 1A-1G In the figures, each WTRU 102a, 102b, 102c, 102d, 102e is described as a handheld wireless communication device, but it should be understood that for the various use cases envisioned for 5G wireless communications, each WTRU may include or be embodied in any type of device or apparatus configured to send and / or receive wireless signals, including, by way of example only, a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smart phone, a laptop computer, a tablet computer, a netbook, a notebook computer, a personal computer, a wireless sensor, a consumer electronic product, a wearable device such as a smart watch or smart clothing, a medical or e-health device, a robot, an industrial equipment, a drone, a vehicle such as a car, a truck, a train or an airplane, and the like.

[0104] The communication system 100 may also include a base station 114a and a base station 114b. The base station 114a may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or other networks 112. The base station 114b may be any type of device configured to wiredly and / or wirelessly interface with at least one of the RRHs (remote radio heads) 118a, 118b and / or TRPs (transmit and receive points) 119a, 119b to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or other networks 112. The RRHs 118a, 118b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102c to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or other networks 112. The TRPs 119a, 119b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102d to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or other networks 112. For example, the base stations 114a, 114b may be base transceiver stations (BTS), Node-Bs, eNode Bs, Home Node Bs, Home eNode Bs, site controllers, access points (APs), wireless routers, and the like. Although the base stations 114a, 114b are each depicted as a single element, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0105] The base station 114a may be part of the RAN 103 / 104 / 105, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114b may be part of the RAN 103b / 104b / 105b, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114a may be configured to send and / or receive wireless signals within a specific geographic area, which may be referred to as a cell (not shown). The base station 114b may be configured to send and / or receive wired and / or wireless signals within a specific geographic area, which may be referred to as a cell (not shown). The cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in an embodiment, the base station 114a may include three transceivers, for example, one transceiver for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and thus may use multiple transceivers for each sector of the cell.

[0106] The base station 114a may communicate with one or more of the WTRUs 102a, 102b, 102c over an air interface 115 / 116 / 117, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115 / 116 / 117 may be established using any suitable radio access technology (RAT).

[0107] The base station 114b may communicate with one or more of the RRHs 118a, 118b and / or TRPs 119a, 119b via a wired or air interface 115b / 116b / 117b, which may be any suitable wired (e.g., cable, fiber optic, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115b / 116b / 117b may be established using any suitable radio access technology (RAT).

[0108] The RRHs 118a, 118b and / or the TRPs 119a, 119b may communicate with one or more of the WTRUs 102c, 102d via an air interface 115c / 116c / 117c, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115c / 116c / 117c may be established using any suitable radio access technology (RAT).

[0109] More specifically, as described above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a and the WTRUs 102a, 102b, 102c in the RAN 103 / 104 / 105, or the RRHs 118a, 118b and the TRPs 119a, 119b and the WTRUs 102c, 102d in the RAN 103b / 104b / 105b, may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117 or 115c / 116c / 117c, respectively. WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink Packet Access (HSDPA) and / or High Speed ​​Uplink Packet Access (HSUPA).

[0110] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c, or the RRHs 118a, 118b and TRPs 119a, 119b and the WTRUs 102c, 102d in the RAN 103b / 104b / 105b may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may use Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) to establish the air interface 115 / 116 / 117 or 115c / 116c / 117c, respectively. In the future, the air interface 115 / 116 / 117 may implement 3GPP NR technology.

[0111] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c in the RAN 103 / 104 / 105, or the RRHs 118a, 118b and the TRPs 119a, 119b and the WTRUs 102c, 102d in the RAN 103b / 104b / 105b may implement a radio technology such as IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0112] Figure 1A The base station 114c in the example may be, for example, a wireless router, a Home Node B, a Home eNode B, or an access point, and may utilize any appropriate RAT to facilitate wireless connectivity in a local area (such as a business location, a home, a vehicle, a campus, etc.). In an embodiment, the base station 114c and the WTRU 102e may implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114c and the WTRU 102d may implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In another embodiment, the base station 114c and the WTRU 102e may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a pico cell or a femto cell. Figure 1A As shown in FIG, base station 114b may be directly connected to Internet 110. Thus, base station 114c may not be required to access Internet 110 via core network 106 / 107 / 109.

[0113] The RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b may be in communication with a core network 106 / 107 / 109, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication.

[0114] Although not in Figure 1AAlthough not shown in the figure, it will be appreciated that the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b and / or the core network 106 / 107 / 109 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b, or a different RAT. For example, in addition to being connected to the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b, which may utilize an E-UTRA radio technology, the core network 106 / 107 / 109 may also be in communication with other RANs (not shown) that employ a GSM radio technology.

[0115] The core network 106 / 107 / 109 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d, 102e to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that utilize common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include other core networks connected to one or more RANs, which may employ the same RAT as the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105 or a different RAT.

[0116] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities. For example, the WTRUs 102a, 102b, 102c, 102d, and 102e may include multiple transceivers for communicating with different wireless networks via different wireless links. Figure 1A The WTRU 102e shown in FIG. 1 may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114c, which may employ an IEEE 802 radio technology.

[0117] Figure 1B 1 is a block diagram of an example device or apparatus (such as WTRU 102) configured for wireless communication according to the embodiments illustrated herein. Figure 1BAs shown in , the example WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / indicator 128, a non-removable memory 130, a removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136 and other peripherals 138. It should be appreciated that the WTRU 102 may include any sub-combination of the above elements while still being consistent with the embodiment. In addition, the embodiment contemplates that the base stations 114a and 114b, and / or the nodes that the base stations 114a and 114b may represent, such as (but not limited to) base transceiver stations (BTS), Node-Bs, site controllers, access points (APs), home node-Bs, evolved home node-Bs (eNodeBs), home evolved node-Bs (HeNBs), home evolved node-B gateways and proxy nodes, etc., may be included in Figure 1B Some or all of the elements described in and illustrated herein.

[0118] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, although it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0119] The send / receive element 122 may be configured to send or receive signals to and from a base station (e.g., base station 114a) via an air interface 115 / 116 / 117. For example, in an embodiment, the send / receive element 122 may be an antenna configured to send and / or receive RF signals. In an embodiment, the send / receive element 122 may be a transmitter / detector configured to send and / or receive, for example, IR, UV, or visible light signals. In another embodiment, the send / receive element 122 may be configured to send and receive both RF signals and optical signals. It should be appreciated that the send / receive element 122 may be configured to send and / or receive any combination of wireless signals.

[0120] In addition, although the transmit / receive element 122 is Figure 1BAlthough described as a single element in the embodiment, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in an embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 115 / 116 / 117.

[0121] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122, and to demodulate signals received by the transmit / receive element 122. As described above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as UTRA and IEEE 802.11.

[0122] The processor 118 of the WTRU 102 may be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad / indicator 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), and may receive user input data therefrom. The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad / indicator 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, or the like. In an embodiment, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as memory on a server or a home computer (not shown).

[0123] The processor 118 may receive power from the power source 134 and may be configured to distribute power to and / or control power to the other components in the WTRU 102. The power source 134 may be any suitable device for providing power to the WTRU 102. For example, the power source 134 may include one or more dry cell batteries, solar cells, fuel cells, etc.

[0124] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. The WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 115 / 116 / 117 in addition to or in lieu of the information from the GPS chipset 136, and / or determine its location based on the timing of receiving signals from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0125] The processor 118 may also be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include various sensors such as accelerometers, biometric (e.g., fingerprint) sensors, electronic compasses, satellite transceivers, digital cameras (for photos or videos), universal serial bus (USB) ports or other interconnect interfaces, vibration devices, television transceivers, hands-free headsets, modules, FM radio units, digital music players, media players, video game player modules, Internet browsers, etc.

[0126] The WTRU 102 may be included in other devices or apparatuses, such as sensors, consumer electronics, wearable devices such as smart watches or smart clothing, medical or e-health devices, robots, industrial equipment, drones, vehicles such as cars, trucks, trains, or airplanes. The WTRU 102 may be connected to other components, modules, or systems of such devices or apparatuses via one or more interconnect interfaces, such as an interconnect interface that may include one of the peripheral devices 138.

[0127] Figure 1C 1 is a system diagram of the RAN 103 and the core network 106 according to an embodiment. As described above, the RAN 103 may employ UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 115. The RAN 103 may also be in communication with the core network 106. Figure 1CAs shown in FIG. 1 , the RAN 103 may include Node-Bs 140a, 140b, 140c, each of which may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 115. The Node-Bs 140a, 140b, 140c may be associated with a particular cell (not shown) within the RAN 103. The RAN 103 may also include RNCs 142a, 142b. It will be appreciated that the RAN 103 may include any number of Node-Bs and RNCs while still being consistent with an embodiment.

[0128] like Figure 1C As shown in , Node-B 140a, 140b can communicate with RNC 142. In addition, Node-B 140c can communicate with RNC 142b. Node-B 140a, 140b, 140c can communicate with corresponding RNC 142a, 142b via Iub interface. RNC142a, 142b can communicate with each other via Iur interface. Each RNC 142a, 142b can be configured to control the corresponding Node-B 140a, 140b, 140c to which it is connected. In addition, each RNC 142a, 142b can be configured to perform or support other functions, such as outer loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, data encryption, etc.

[0129] Figure 1C The core network 106 shown in FIG. 1 may include a media gateway (MGW) 144, a mobile switching center (MSC) 146, a serving GPRS support node (SGSN) 148, and / or a gateway GPRS support node (GGSN) 150. Although each of the above elements are described as being part of the core network 106, it should be appreciated that any of these elements may be owned and / or operated by an entity other than the core network operator.

[0130] The RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via an IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.

[0131] The RNC 142a in the RAN 103 may also be connected to the SGSN 148 in the core network 106 via an IuPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0132] As described above, core network 106 may also be connected to networks 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0133] Figure 1D 1 is a system diagram of the RAN 104 and the core network 107 in accordance with an embodiment. As described above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the core network 107.

[0134] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, for example, the eNode-B 160a may use multiple antennas to send and receive wireless signals to and from the WTRU 102a.

[0135] Each eNode-B 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink and / or downlink, etc. Figure 1D As shown in FIG. , eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.

[0136] Figure 1D The core network 107 shown in FIG. 1 may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. Although each of the above elements is described as being part of the core network 107, it should be appreciated that any of these elements may be owned and / or operated by an entity other than the core network operator.

[0137] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.

[0138] The serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an S1 interface. The serving gateway 164 may generally route and forward user data packets to and from the WTRUs 102a, 102b, 102c. The serving gateway 164 may also perform other functions, such as anchoring the user plane during inter-eNode B handovers, triggering paging when downlink data is available for the WTRUs 102a, 102b, 102c, managing and storing the contexts of the WTRUs 102a, 102b, 102c, and the like.

[0139] The serving gateway 164 may also be connected to the PDN gateway 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0140] The core network 107 may facilitate communications with other networks. For example, the core network 107 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the core network 107 may include, or may be in communication with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the core network 107 and the PSTN 108. In addition, the core network 107 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0141] Figure 1E1 is a system diagram of the RAN 105 and the core network 109 according to an embodiment. The RAN 105 may be an access service network (ASN) that employs IEEE 802.16 radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 117. As further described below, the communication links between the different functional entities of the WTRUs 102a, 102b, 102c, the RAN 105, and the core network 109 may be defined as reference points.

[0142] like Figure 1E As shown in , the RAN 105 may include base stations 180a, 180b, 180c and an ASN gateway 182, although it should be appreciated that the RAN 105 may include any number of base stations and ASN gateways while still being consistent with the embodiment. The base stations 180a, 180b, 180c may each be associated with a particular cell in the RAN 105 and may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 117. In an embodiment, the base stations 180a, 180b, 180c may implement MIMO technology. Thus, for example, the base station 180a may use multiple antennas to send wireless signals to the WTRU 102a and receive wireless signals from the WTRU 102a. The base stations 180a, 180b, 180c may also provide mobility management functions, such as handover triggering, tunnel establishment, radio resource management, traffic classification, quality of service (QoS) policy implementation, and the like. The ASN gateway 182 may act as a traffic aggregation point and may be responsible for paging, caching of subscriber profiles, routing to the core network 109, and the like.

[0143] The air interface 117 between the WTRUs 102a, 102b, 102c and the RAN 105 may be defined as an R1 reference point that implements the IEEE 802.16 specification. In addition, each of the WTRUs 102a, 102b, and 102c may establish a logical interface (not shown) with the core network 109. The logical interface between the WTRUs 102a, 102b, 102c and the core network 109 may be defined as an R2 reference point, which may be used for authentication, authorization, IP host configuration management, and / or mobility management.

[0144] The communication link between the base stations 180a, 180b, and 180c may be defined as an R8 reference point, which includes protocols that facilitate WTRU handovers and the transfer of data between base stations. The communication link between the base stations 180a, 180b, 180c and the ASN gateway 182 may be defined as an R6 reference point. The R6 reference point may include protocols that facilitate mobility management based on mobility events associated with the respective WTRUs 102a, 102b, 102c.

[0145] like Figure 1E As shown in , the RAN 105 may be connected to a core network 109. The communication link between the RAN 105 and the core network 109 may be defined as an R3 reference point, which includes, for example, protocols that facilitate data transfer and mobility management capabilities. The core network 109 may include a mobile IP home agent (MIP-HA) 184, an authentication, authorization, accounting (AAA) server 186, and a gateway 188. Although each of the above elements are described as being part of the core network 109, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the core network operator.

[0146] The MIP-HA may be responsible for IP address management and may enable the WTRUs 102a, 102b, and 102c to roam between different ASNs and / or different core networks. The MIP-HA 184 may provide the WTRUs 102a, 102b, and 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, and 102c and IP-enabled devices. The AAA server 186 may be responsible for user authentication and supporting user services. The gateway 188 may facilitate interworking with other networks. For example, the gateway 188 may provide the WTRUs 102a, 102b, and 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, and 102c and traditional land-line communication devices. In addition, the gateway 188 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks that are owned and / or operated by other service providers.

[0147] Although not in Figure 1E 105 may be connected to other ASNs and the core network 109 may be connected to other core networks. The communication link between the RAN and the other ASNs may be defined as an R4 reference point, which may include protocols for coordinating the mobility of the WTRUs 102a, 102b, 102c between the RAN 105 and the other ASNs. The communication link between the core network 109 and the other core networks may be defined as an R5 reference point, which may include protocols for facilitating interworking between the home core network and the visited core network.

[0148] The core network entities described herein and illustrated in Figures 1-6 are identified using the names given to these entities in certain existing 3GPP specifications, although it should be understood that in the future, these entities and functions may be identified by other names, and in future specifications released by 3GPP, including future 3GPP NR specifications, certain entities or functions may be combined. Thus, the specific network entities and functions described and illustrated in Figures 1-6 are provided as examples only, and it should be understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system (whether currently defined or defined in the future).

[0149] Figure 1F The 5G core network 170 shown in the figure may include an access and mobility management function (AMF) 172, a session management function (SMF) 174, a user plane function (UPF) 176, a user data management function (UDM) 178, an authentication server function (AUSF) 180, a network open function (NEF), a policy control function (PCF) 184, a non-3GPP interworking function (N3IWF) 192, and an application function (AF) 188. Although each of the above elements is described as part of the 5G core network 170, it should be appreciated that any of these elements may be owned and / or operated by an entity other than the core network operator. It should also be appreciated that the 5G core network may not be composed of all of these elements, may be composed of additional elements, and may be composed of multiple instances of each of these elements. Figure 1F The network functions are shown as being directly connected to each other, although it should be appreciated that they may communicate via a routing agent (such as a Diameter routing agent) or a message bus.

[0150] The AMF 172 may be connected to each of the RAN 103 / 104 / 105 / 103b / 104b / 105b via an N2 interface and may act as a control node. For example, the AMF 172 may be responsible for registration management, connection management, reachability management, access authentication, access authorization. The AMF 172 may typically route and forward NAS packets to and from the WTRUs 102a, 102b, 102c.

[0151] The SMF 174 may be connected to the AMF 172 via an N11 interface, to the PCF 184 via an N7 interface, and to the UPF 176 via an N4 interface. The SMF 174 may act as a control node. For example, the SMF 174 may be responsible for session management, allocation of IP addresses for the WTRUs 102a, 102b, 102c & management and configuration of traffic steering rules in the UPF 176, and generation of downlink data notifications.

[0152] The SMF 174 may also be connected to the UPF 176, which may provide the WTRUs 102a, 102b, 102c with access to a data network (DN) 190, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The SMF 174 may manage and configure traffic steering rules in the UPF 176 via the N4 interface. The UPF 176 may be responsible for interconnecting packet data unit (PDU) sessions with the data network, packet routing and forwarding, policy rule enforcement, quality of service processing for user plane traffic, and downlink packet buffering.

[0153] The AMF 172 may also be connected to the N3IWF 192 via an N2 interface. The N3IWF facilitates connectivity between the WTRUs 102a, 102b, 102c and the 5G core network 170 via a radio interface technology that is not defined by 3GPP.

[0154] PCF 184 may be connected to SMF 174 via an N7 interface, to AMF 172 via an N15 interface, and to Application Function (AF) 188 via an N5 interface. PCF 184 may provide policy rules to control plane nodes such as AMF 172 and SMF 174, allowing the control plane nodes to implement the rules.

[0155] UDM 178 acts as a repository for authentication credentials and subscription information. UDM can be connected to other functions such as AMF 172, SMF 174 and AUSF 180.

[0156] AUSF 180 performs authentication-related operations, is connected to UDM 178 via an N13 interface, and is connected to AMF 172 via an N12 interface.

[0157] NEF opens capabilities and services in the 5G core network 170. NEF can be connected to AF 188 via an interface, and it can be connected to other control plane functions and user plane functions (180, 178, 172, 172, 184, 176, and N3IWF) to open capabilities and services of the 5G core network 170.

[0158] The 5G core network 170 may facilitate communications with other networks. For example, the core network 170 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the 5G core network 170 and the PSTN 108, or may communicate with the IP gateway. For example, the core network 170 may include a short message service (SMS) service center that facilitates communications via a short message service, or communicate with the short message service (SMS) service center. For example, the 5G core network 170 may facilitate the exchange of non-IP data packets between the WTRUs 102a, 102b, 102c and a server. In addition, the core network 170 may provide the WTRUs 102a, 102b, 102c with access to the network 112, which may include other wired or wireless networks owned or operated by other service providers.

[0159] Figure 1G is a block diagram of an example computing system 90 , which may include one or more devices of the communication network illustrated or described herein, such as certain nodes or functional entities in the RAN 103 / 104 / 105 , the core network 106 / 107 / 109 , the PSTN 108 , the Internet 110 or other networks 112 .

[0160] The computing system 90 may comprise a computer or a server and may be primarily controlled by computer-readable instructions, which may be in the form of software, wherever or however such software is stored or accessed. Such computer-readable instructions may be executed in a processor 91 to cause the computing system 90 to operate. The processor 91 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 91 may perform signal encoding, data processing, power control, input / output processing, and / or any other function that enables the computing system 90 to operate in a communication network. The coprocessor 81 is an optional processor different from the main processor 91 that may perform additional functions or assist the processor 91. The processor 91 and / or the coprocessor 81 may receive, generate, and process data related to the methods and devices disclosed herein.

[0161] In operation, processor 91 retrieves, decodes and executes instructions and transfers information to and from other resources via the computing system's main data transfer path, system bus 80. Such a system bus connects components in computing system 90 and defines a medium for data exchange. System bus 80 generally includes data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and for operating the bus. An example of such a system bus 80 is a PCI (Peripheral Component Interconnect) bus.

[0162] The memory coupled to the system bus 80 includes a random access memory (RAM) 82 and a read-only memory (ROM) 93. Such a memory includes circuits that allow information to be stored and retrieved. ROM 93 generally contains stored data that is not easily modified. The data stored in RAM 82 can be read or changed by the processor 91 or other hardware devices. Access to RAM 82 and / or ROM 93 can be controlled by a memory controller 92. The memory controller 92 can provide an address translation function that converts a virtual address into a physical address when an instruction is executed. The memory controller 92 can also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Thus, a program running in the first mode can only access memory mapped by its own process virtual address space; unless memory sharing between processes is set, it cannot access memory in the virtual address space of other processes.

[0163] In addition, the computing system 90 may include a peripheral device controller 83 , which is responsible for transmitting instructions from the processor 91 to peripheral devices, such as a printer 94 , a keyboard 84 , a mouse 95 , and a disk drive 85 .

[0164] The display 86 controlled by the display controller 96 is used to display the visual output generated by the computing system 90. Such visual output may include text, graphics, animated graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI). The display 86 may be implemented using a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touch panel. The display controller 96 includes the electronic components required to generate the video signal sent to the display 86.

[0165] In addition, the computing system 90 may include communication circuits, such as a network adapter 97, that can be used to connect the computing system 90 to an external communication network (such as the RAN 103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, Internet 110 or other network 112 of Figures 1-6) to enable the computing system 90 to communicate with other nodes or functional entities of these networks. Alone or in combination with the processor 91, the communication circuit can be used to perform the sending and receiving steps of certain devices, nodes or functional entities described herein.

[0166] It should be understood that any or all of the devices, systems, methods, and processes described herein may be embodied in the form of computer executable instructions (e.g., program code) stored on a computer-readable storage medium, which, when executed by a processor (such as processor 118 or 91), causes the processor to perform and / or implement the systems, methods, and processes described herein. Specifically, any steps, operations, or functions described herein may be implemented in the form of such computer executable instructions executed on a processor of a device or computing system configured for wireless and / or wired network communications. Computer-readable storage media include volatile and non-volatile, removable and non-removable media implemented in any non-temporary (e.g., tangible or physical) method or technology for storage of information, but such computer-readable storage media do not include signals. Computer-readable storage media include (but are not limited to) RAM, ROM, EEPROM, flash memory or other storage technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, cassettes, magnetic tape, magnetic disk storage or other magnetic storage, or any other tangible or physical medium that can be used to store the desired information and can be accessed by a computing system.

[0167] Figure 2A is a block diagram of a non-roaming network architecture of a 5G network with a service-based interface within a control plane of the network. Figure 2B Yes means Figure 2A Figure 2 is another view of a 5G network and a block diagram illustrating the reference points through which various network functions interact. Note that the mobility management function and the session management function are separate. A single N1 NAS connection is used for registration management and connection management (RM / CM) and SM related messages and procedures for the UE. The single N1 termination point is located in the AMF. The AMF forwards the SM related NAS information to the SMF. The AMF handles the registration management and connection management part of the NAS signaling exchanged with the UE. The SMF handles the session management part of the NAS signaling exchanged with the UE.

[0168] The 5G system architecture is defined to support data connectivity and services, enabling deployments to use technologies such as Network Function Virtualization (NFV) and Software Defined Networking (SDN). The 5G system architecture is designed to take full advantage of service-based interactions between identified control plane (CP) network functions.

[0169] As mentioned above, NF is a processing function in a network, which has defined functional behavior and defined interfaces. NF can be implemented as a network element on dedicated hardware, or as a software instance running on dedicated hardware, or as a virtualized function instantiated on an appropriate platform (such as on a cloud infrastructure).

[0170] As further described above, a NF service is a type of capability opened by a NF ("NF service provider") to other authorized NFs ("NF service consumers") through a service-based interface. An NF may open one or more NF services. Typically, an NF service provides capabilities to authorized consumers. An NF may provide different capabilities to different consumers, thereby providing different NF services. Each NF service provided by an NF is designed to be self-contained, reusable, and independent of other NF services provided by the same NF using management schemes, such as for scaling, repair, etc. Each NF service is designed to be accessible through an interface. An interface may consist of one or more operations. Figure 3 It shows the relationship between NFs, NF services and their operations.

[0171] The interaction between two network functions (consumer and provider) within this NF service framework follows two mechanisms:

[0172] "Request-Response": A control plane NF_B (NF service provider) is requested by another control plane NF_A (NF service consumer) to provide a certain NF service, which performs actions and / or provides information. NF_B provides NF services based on NF_A's request. In order to satisfy the request, NF_B can consume NF services from other NFs. In this request-response mechanism, the communication between two NFs (consumer and provider) is one-to-one, and the one-time response of the provider to the consumer's request is expected to be completed within a certain time frame. Figure 4 Represents the flow of the request-response communication mechanism.

[0173] "Subscribe-Notify": A control plane NF_A (NF service consumer) subscribes to a NF service provided by another control plane NF_B (NF service provider). Multiple control plane NFs can subscribe to the same control plane NF service. NF_B notifies one or more interested NFs that have subscribed to the NF service of the result of the NF service. The subscription request shall include the notification endpoint (e.g., notification URL) of the NF service consumer to which event notifications from the NF service provider shall be sent. In addition, the subscription request may include notification requests for periodic updates or notifications triggered by certain events (e.g., the requested information is changed, a certain threshold is reached, etc.). Figure 5 It shows the flow of the subscription-notification communication mechanism.

[0174] For example, Table 1 represents the AMF services and AMF service operations defined in 3GPP TS23.502, Procedures for the 5G System; Stage 2, v15.1.0, Release 15, 2018-03.

[0175] Table 1: List of AMF services

[0176]

[0177]

[0178] Network slicing is a mechanism that mobile network operators can use to support multiple "virtual" networks behind the air interface across the fixed portion of the mobile operator's network (both backhaul and core network). This involves "slicing" the network into multiple virtual networks to support different radio access networks (RANs) or different service types running across a single RAN. Network slicing enables operators to create customized networks to provide optimized solutions for different market scenarios that require different requirements in terms of functionality, performance and isolation, for example.

[0179] As described above, a network slice may include a logical network that provides specific network capabilities and network characteristics. A network slice within a PLMN includes a core network control plane and a user plane NF. A network slice instance includes the required resources (e.g., computing, storage, and networking resources) and a set of NF instances to form a deployed network slice.

[0180] Network slices may differ in supported features and network function optimizations, in which case such network slices may have different slice / service types. Operators may deploy multiple network slice instances that deliver the same features but for different groups of UEs, for example, when they deliver different promised services and / or because they are dedicated to customers, in which case such network slices may have the same slice / service type but distinguished by different slice discriminators.

[0181] The network can simultaneously serve a single UE via the 5G-AN with one or more network slice instances associated with a total of up to 8 different S-NSSAIs, regardless of the access type (i.e., 3GPP access and / or N3GPP access) through which the UE is registered. The AMF instance serving the UE logically belongs to each network slice instance serving the UE, i.e., the AMF instance is common to the network slice instance serving the UE.

[0182] Network slices are identified by S-NSSAI, which consists of the following:

[0183] Slice / Service Type (SST), which refers to the expected network slice behavior in terms of characteristics and services;

[0184] Slice Differentiator (SD), which is optional information that supplements the slice / service type to distinguish multiple network slices of the same slice / service type.

[0185] The S-NSSAI can have a standard value (i.e., such an S-NSSAI consists only of SST with a standardized SST value, but without SD), or a non-standard value (i.e., such an S-NSSAI consists of both SST and SD, or consists only of SST without a standardized SST value, but without SD). The S-NSSAI with a non-standard value identifies a single network slice associated with it within a PLMN. The UE should not use the S-NSSAI with a non-standard value in access stratum procedures in any other PLMN other than the PLMN with which the S-NSSAI is associated. Table 2 shows the standardized SST values ​​defined in 3GPP TS23.501, System Architecture for the 5GSystem; Stage 2, v15.1.0, Release 15, 2018-03.

[0186] NSSAI is a set of S-NSSAIs. NSSAI can be a configured NSSAI, a requested NSSAI, or an allowed NSSAI. There can be up to 8 S-NSSAIs in the allowed NSSAI and requested NSSAI sent in the signaling messages between the UE and the network. The requested NSSAI signaled by the UE to the network allows the network to select a serving AMF, network slice, and network slice instance for the UE.

[0187] Table 2: Normalized SST values

[0188] Slice / Serving Type SST value characteristic eMBB 1 Slices suitable for processing of 5G enhanced mobile broadband. URLLC 2 Slices suitable for processing of ultra-reliable low-latency communications. MIoT 3 Slices suitable for large-scale IoT processing.

[0189] Based on the operator's operational or deployment requirements, a network slice instance can be associated with one or more S-NSSAIs, and an S-NSSAI can be associated with one or more network slice instances. Multiple network slice instances associated with the same S-NSSAI can be deployed in the same or different tracking areas. When multiple network slice instances associated with the same S-NSSAI are deployed in the same tracking area, the AMF instance serving the UE can logically belong to more than one network slice instance associated with the S-NSSAI (i.e., shared by more than one network slice instance).

[0190] refer to Figure 6 , and as mentioned above, 5GC defines a service-based architecture (SBA) based on the concepts of network slicing and virtualized network functions (NFs). Different network functions (such as AMF, SMF, and PCF) provide different network function services via service-based interfaces. This means that the service consumer can use the same message and the same process to communicate with the service provider. For example, any NF can subscribe to the same event using the event open service provided by AMF. On the other hand, various network capabilities such as non-IP data delivery (NIDD), background data transfer (BDT), and power saving mode (PSM) can be implemented through a set of NF services. Under the current SBA architecture, the UE can configure and access the network by indicating the requested NSSAI that identifies the network slice. However, the UE has no way to directly indicate the required network capabilities.

[0191] For example, a vehicle running a V2X application may want to use background data transfer (BDT), multimedia broadcast / multicast service (MBMS), and event monitoring capabilities. The UE or the corresponding V2X application server needs to establish a configuration with the core network (CN) so that the network slice serving the UE has the required network capabilities. On the other hand, a smart home device with integrated sensors and cameras may want to use a different set of network capabilities, such as NIDD, data caching, group messaging, and device triggering. The device may not have a graphical interface that allows human intervention, which is common for many IoT devices. It would be desirable for the network to be able to automatically configure network slices based on different levels of input from the device (e.g., the level of network capabilities, the level of network slice identifiers, or the level of NF services).

[0192] As further described above, the service-based architecture of 5GC consists of multiple virtualized network functions. Each network function provides a set of network function services through a service-based interface. Thus, network capabilities (e.g., event monitoring, location services) can be implemented through a set of network function services. Any entity (e.g., NF, UE, and SCS / AS) can subscribe to a service by calling the same operation. However, there are some limitations to the existing SBA defined by 5GC.

[0193] First, the granularity of network function services prevents flexible network capability configuration. Each network function provides various network function services from different aspects (for example, AMF provides mobility management, location management, and event monitoring / open services), and each network capability may require a different set of network function services from different network functions. For example, an IoT device can require MIoT services by setting the value of the slice / service type to MIoT. However, there is no way for the UE to indicate a specific network capability it wants, such as non-IP data transmission or event monitoring / reporting capabilities. In another example, the V2X application server (AS) may need to enable background data transfer (BDT) capabilities. Based on the current network function framework, the BDT capability requires the Npcf_BDTPolicyControl NF service provided by the PCF and the Nnef_BDTPNegotiation NF service provided by the NEF to determine the BDT policy. In addition, the Nsmf_PDUSession provided by the SMF is required to manage the PDU session for future data transmission. It is difficult for UE / AF / AS to figure out what network function services are needed for BDT. In fact, it is not necessary to require UE or SCS / AS to know these network function services to enable BDT. Compared with NF services, UE and AS will be more concerned about network capabilities.

[0194] Second, when the UE registers with the core network, it may provide an indication of the type of slice it wants to connect to - for example, in the requested NSSAI. However, this information may be PLMN-specific and not standardized, and as a result, it may not be known to the UE - for example when the UE first registers, or when the UE is roaming. In this case, it is unlikely that the UE will include this information when it attempts to register with the network.

[0195] Third, some IoT devices are constrained, thereby expecting automatic network capability configuration in the core network to help these devices dynamically configure network capabilities. Based on existing methods, dynamically adding or removing network capabilities (i.e., updating the network slice to which the UE is registered) will trigger the UE configuration update process, which further triggers the registration process and sometimes requires the UE to enter idle mode and repeat the entire registration process. This should not be necessary and may be too complicated for constrained IoT devices.

[0196] Fourth, the scope of existing SBA is limited to the control plane NF. User plane function (UPF) is not involved. UPF has some control functions, such as QoS enforcement and event monitoring. It is expected to define service-based interfaces and UPF services to enhance SBA.

[0197] Fifth, when the UE sends a registration request to the core network, the UE has no way to indicate what network capabilities it requires.

[0198] Sixth, when the UE registers with the network, it receives the allowed NSSAI. The UE does not know whether the allowed NSSAI can support the capabilities required by the UE.

[0199] Seventh, when the UE context changes, such as when the UE moves from EPS to 5G, or when there is a request from the AS, which may update the network capabilities of the slice (e.g., maximum data rate, etc.), it may be necessary to change the PCC rules and network slice information about the UE (thus, changing the NCP). The PCF may be able to communicate such changes to the UE as a UE policy update. The UE policy may need to be enhanced to incorporate the NCP. 5GS does not have a mechanism to convey such enhanced UE policies to the UE.

[0200] Eighth, a network slice may have a limit on how many PDU sessions it can handle at one time. When a UE attempts to establish a PDU session with a network slice, and if the capacity of the network slice has reached its peak, the network slice cannot process the UE's request. The 5G system currently does not handle this situation.

[0201] Ninth, another network capability may be to handle the maximum number of UE registrations per network slice. When a UE attempts to register with a network slice and the network capability for maximum UE registrations in the slice has reached its limit, the UE should not be able to register. The current 5GS does not address this situation.

[0202] When a UE application attempts to initiate a data flow (such as an IP data flow), the UE needs to determine which slice and data network to associate the data flow with. The 5G system provides a way to solve this problem in URSP. URSP rules can include application identifiers, thereby instructing the UE how to route traffic from a given application. The disadvantage of this method is that the UE needs to be provided with an application identifier that matches the application it has installed. Another way to determine which slice and data network to associate the data flow with is to allow the UE to indicate the slice (S-NSSAI) and data network (DNN) with which the data flow should be associated. The disadvantage of this method is that the S-NSSAI and DNN need to be provided to the UE application, and these parameters need to be recognizable to the network.

[0203] Disclosed herein are methods and apparatus that enable a network to indicate to a UE the network capabilities of a slice, and how these capabilities are configured in a slice. This information can be used by the UE in cases where UE applications can indicate to the UE the capabilities they require. The UE can then use this information during route selection (i.e., during the evaluation of the URSP, when determining which slice and PDU session to use for a data flow). Also disclosed are methods for the UE to indicate to the network what network capabilities it expects and their desired configuration, and for the network to provide the UE with a slice identifier that can provide these capabilities in the desired configuration.

[0204] The concept of Network Capability Profile (NCP) is introduced. NCP lists the capabilities of a slice and how to configure each capability. Examples of network capabilities are provided below.

[0205] Disclosed below are technical solutions to the problems of the existing service-based architecture and the corresponding NF framework. These solutions can achieve more dynamic and flexible operations in the service-based architecture, and can improve the programmability of the service-based architecture for end users (i.e., UE and AS). In order to make it easier for users (e.g., UE and AS) to configure the required network capabilities and features through service-based interfaces and processes, the following description is made.

[0206] First, a new framework is described, which includes a network capability layer. UE and AS can dynamically request network capabilities (e.g., background data transmission, non-IP data transmission, maximum UE DL / UL data rate, maximum delay tolerance, maximum guaranteed DL throughput, group characteristics, message transmission options, etc.) to support their applications. In one implementation, UE and AS may not need to know or care which network slice supports the requested network capability, or whether the serving network slice can support the requested network capability. The core network entity can determine and configure the network slice that supports all requested network capabilities.

[0207] Second, a mechanism is described by which the network can convey network capability information, referred to herein as a network capability profile (NCP) of a network slice, to a UE. A method is also described in which the network can notify a UE of alternative network slices with comparable network capability profiles based on the network capabilities requested by the UE.

[0208] Thirdly, a method for a UE to initiate a network capability-based registration to configure its required network capabilities is disclosed.

[0209] Fourth, a method for a UE to initiate network capability-based registration to configure its required network capabilities is described.

[0210] Fifth, a method is described for a UE to initiate a network capability based registration update when the UE is already registered with the network and wants to dynamically reconfigure their network capabilities.

[0211] Sixth, a method for UE configuration update based on network capabilities is described, which allows an NF or application server to initiate a process of updating network capabilities in a network slice for the UE.

[0212] Seventh, a method is disclosed by which a UE may receive a set of allowed NSSAIs and their corresponding NCPs during a general UE registration procedure. If the capabilities indicated by the received NCPs are insufficient for an application in the UE, the UE may be able to request an alternative network slice based on the NCP list of allowed S-NSSAIs received from the core network.

[0213] Eighth, a method is disclosed by which the NCP of a network slice is transmitted to a UE as part of the UE policy during a UE policy update process.

[0214] Ninth, a method is disclosed by which the core network implements a maximum number of PDU sessions per network slice during a PDU session establishment process and processes requests received after the maximum limit is reached.

[0215] Tenth, a method is disclosed in which a core network handles a maximum limit on the number of PDU sessions per network slice, wherein the network periodically notifies a UE via a NAS message that the network slice has reached its maximum limit so that the UE can wait before retrying.

[0216] Eleventh, a method is disclosed by which a core network implements a maximum number of UE registrations per network slice and processes registration requests received after the maximum limit is reached.

[0217] Twelve, an extended service-based architecture is described, which includes an interface with a user plane function (UPF) and the services provided by the UPF.

[0218] According to these aspects, the UE may send a network capability configuration request to configure network capabilities to support its application, and the UE may receive a network capability configuration response with an identification of a network slice that supports the required network capability. Based on these features, the network entity receiving the request may perform one or more of the following operations:

[0219] Checking the network capability profile to determine whether the serving network slice can support the requested network capability;

[0220] Select a new network slice to provide all requested network capabilities to the UE;

[0221] In the event that the UE cannot be served by any existing network slice, a new network slice (instance) is initiated to provide all requested network capabilities to the UE;

[0222] Selecting a new entity that provides the newly selected network slice, which terminates NAS signalling with the UE;

[0223] · Update the network capability profile of the selected network slice; and

[0224] Send a response to the UE with information of the serving network slice and network capabilities.

[0225] The network capability profile may include one or more of the following:

[0226] The identifier of the network slice and the corresponding network slice instance;

[0227] An identifier for the list of supported network capabilities;

[0228] The identifier of the serving PLMN; and

[0229] · Service area information for each network capability.

[0230] The network capability configuration request may include one or more of the following:

[0231] Identification of one or more required network capabilities;

[0232] Identifier of the application that requires network capabilities;

[0233] The NSSAI assigned by the UE during the previous registration procedure, which can be the configured NSSAI or the allowed NSSAI;

[0234] An identifier associated with the UE;

[0235] Service area information of the requested network capabilities;

[0236] Availability scheduling of required network capacity;

[0237] · QoS level of required network capabilities (e.g., service response time);

[0238] The level of multi-tenancy required (e.g., how many applications on the UE will need to use one or more network capabilities).

[0239] In addition, according to the above aspects, the network entity may perform one or more of the following operations:

[0240] · receiving a network capability configuration request from a network entity that triggers a network capability configuration update procedure for the UE;

[0241] Determine whether it is necessary to select a new network slice and / or a new network entity as a NAS signal termination point for the UE;

[0242] Select a new network slice and / or a new NAS termination point for the UE;

[0243] Sending a configuration update message to the UE; and

[0244] • Send a response to the triggering network entity.

[0245] The network entity receiving the request may further perform one or more of the following:

[0246] Checking the network capability profile to determine whether the serving network slice can support the requested network capability;

[0247] Select a new network slice to provide all requested network capabilities to the UE;

[0248] Selecting a new entity that provides the newly selected network slice, which terminates NAS signalling with the UE;

[0249] · Update the network capability profile of the selected network slice; and

[0250] Send a notification to the UE with information of the serving network slice and network capabilities.

[0251] Alternatively, instead of the network entity triggering the network capability configuration update procedure for the UE, the application server may decide to trigger the procedure by sending a network capability configuration request.

[0252] The UE may perform one or more of the following:

[0253] Send a registration request.

[0254] Receive a registration response, which includes the NCP of the network slice.

[0255] In addition, according to the above aspects, one or more of the following operations may be performed:

[0256] The response may come from the AMF.

[0257] The AMF may obtain the NCP of the subscribed S-NSSAI from the UE subscription information in the UDM.

[0258] The AMF may obtain the NCP of the allowed S-NSSAI from other network functions such as UDM, NSSF or NRF.

[0259] • The response may contain S-NSSAIs that were not in the Registration Request, and the response may include the NCP for each S-NSSAI.

[0260] The UE may request alternative network slices based on the NCP list of the S-NSSAI received from the core network.

[0261] The UE may receive the NCP as part of the UE policy received in a NAS message.

[0262] In addition, according to the above aspects, the network entity may perform one or more of the following operations:

[0263] · Receive a trigger to update the UE's NCP policy.

[0264] • Check the latest PSI to find out the UE policy and NCP policy (NCCP) for the S-NSSAI to be sent to the UE.

[0265] Integrate NCPP with UE policies.

[0266] • The NCPP is delivered to the UE using the UE policy container.

[0267] In addition, in accordance with the above aspects, the UE may use information in the NCPP when selecting a route during evaluation of the URSP rules. For example, in the case where the maximum data rate in the slice associated with the higher priority route is lower, the UE may choose to establish a route described in the lower priority RSD.

[0268] The UE may perform one or more of the following:

[0269] Attempt to establish a PDU session with the network.

[0270] Rejected and receives a reason code indicating that the maximum PDU session limit and wait timer for the slice has been reached.

[0271] • PDU Session establishment is not attempted before the wait timer expires or the UE terminates the PDU Session.

[0272] In addition, according to the above aspects, the network entity may perform one or more of the following operations:

[0273] • Employ a counter that counts up or down for each PDU Session that is established or terminated.

[0274] When the maximum limit is reached, the UE's request to establish a PDU session may be blocked and a cause code may be sent to the UE as a response, where the cause code contains the reason for the denial of access and a waiting timer.

[0275] The UE may perform one or more of the following:

[0276] · Receive NAS notification indicating that the maximum PDU session limit has been reached and the wait timer.

[0277] Before requesting PDU Session establishment, wait for the waiting timer to expire or until the UE terminates another PDU Session in the same slice.

[0278] In addition, according to the above aspects, the network entity may perform one or more of the following operations:

[0279] • Employ a counter that counts up or down for each PDU Session that is established or terminated.

[0280] • Notify the UE when the condition is cleared.

[0281] In addition, according to the above aspects, the UE may perform one or more of the following operations:

[0282] • Receiving a NAS message from the network indicating that the condition has cleared.

[0283] Reset the wait timer and retry the PDU session establishment process.

[0284] Wait until the wait timer expires and retry the PDU session establishment process.

[0285] The UE may perform one or more of the following operations:

[0286] Request UE registration procedure.

[0287] • Rejected with a cause code indicating that the maximum UE registration limit has been reached and the waiting timer.

[0288] ·The UE is not requested to register before the waiting timer expires or before a UE is deregistered from the slice.

[0289] In addition, according to the above aspects, the network entity may perform one or more of the following operations:

[0290] • Employ a counter that counts up or down for each UE that registers or deregisters.

[0291] When the maximum limit is reached, the network entity may block the UE's registration request and send a cause code as a response to the UE, where the cause code contains the reason for the denial of access and a waiting timer.

[0292] Notify the UE that the condition has been cleared.

[0293] In addition, according to the above aspects, the UE may perform one or more of the following operations:

[0294] Obey the wait timer.

[0295] A NAS message is received from the network indicating that the condition has cleared.

[0296] Reset the waiting timer and retry and attempt the UE registration request.

[0297] Framework for network slicing in 5G core networks

[0298] Figure 7 Represents a network architecture with a network capability (e.g., BDT, NIDD, and event monitoring) layer between network slices (with corresponding NFs and NF services) and UE / AS. The network capability layer can make the granularity of network slice configuration finer and can make it easier for UE / AS to configure their network features. The new layer may include a logical layer that allows UE and SCS / AS to request required network capabilities by indicating what network capabilities (e.g., BDT, NIDD, and event monitoring) are desired instead of or in addition to indicating what type of network slice is desired.

[0299] The UE / AS can send a request to the core network directly indicating the required network capabilities, and a new NF referred to herein as the Network Capability Management Function (NCMF) can operate to configure the network slice to provide the required network capabilities to the UE / AS. The NCMF can implement the management function of the network capability layer in the core network.

[0300] This new NF enables finer granularity in configuring network services. On the one hand, the UE / AS can directly indicate what network capabilities it wants (e.g., background data transfer, event monitoring, etc.) without knowing the available NFs and NF services. This allows the UE / AS to request specific capabilities without the need for the UE / AS to know how the network slice provides the capabilities. The UE and AS may only care about the level of network capabilities used for their applications. On the other hand, the core network entities can maintain NF and NF service-level operations without any changes in the existing architecture due to network capability-level requests from the UE / AS.

[0301] NCMF can have one or all of the following functions.

[0302] First, NCMF can manage and maintain information that provides mappings between network capabilities and NF services. That is, the mapping information can indicate a set of NFs and corresponding NF services required to support network capabilities. This information can be used to determine whether a network slice can support network capabilities under the condition that which NFs and NF services are included in the network slice.

[0303] Second, NCMF can manage and maintain profiles, which include information identifying a set of network capabilities supported by a network slice. This network capability profile information may be useful when a UE / AS requests to add or update network capabilities for its application.

[0304] Third, NCMF can also interface with the network operation and management (O&M) system to obtain information about network slices, NFs, NF services, and / or network capabilities. NCMF can also request the O&M system to manage network slices, network slice instances, NFs, and / or NF services to support the required network capabilities.

[0305] NCMF can be an independent network function, a logical function residing in other network functions such as AMF, SMF or PCF, or a service provided by a network function.

[0306] Mapping information between network capabilities and NF services

[0307] In order to determine whether a network slice can support a certain network capability, it is necessary to maintain mapping information to indicate what NF services are required to support the network capability. For example, the Background Data Transfer (BDT) capability requires the Npcf_BDTPolicyControl service provided by the PCF and the Nnef_BDTPNegotiation service provided by the NEF in order to determine the BDT policy. In addition, the Nsmf_PDUSession service provided by the SMF is required to manage the PDU session for future data transmission. Table 3 shows an example of a data structure for providing mapping information between network capabilities and their required NF services.

[0308] Table 3: Mapping information between network capabilities and NF services

[0309]

[0310]

[0311] NCMF can obtain mapping information from the O&M system of the network. The mapping information can be managed and stored in NCMF. NCMF can be co-located with NSSF or NRF, so that the above mapping information can also be managed and stored in NSSF or NRF.

[0312] Network Capability Profile

[0313] The Network Capability Profile may include an information profile for each network slice maintained by the NCMF, which indicates what network capabilities each network slice supports. Table 4 shows an example of information fields that may be included in the Network Capability Profile for a given network slice. Note that the Network Capability Profile (NCP) is a collection of information elements for each slice.

[0314] Table 4: Network Capability Profile

[0315]

[0316]

[0317] NCMF can manage and maintain the information shown in Table 3 and Table 4. When the core network NF receives a request from the UE / AS to add network capabilities or update network capabilities (for example, to modify one or more parameters of the network capabilities), the request can be forwarded to the NCMF to determine whether the service network slice already supports the requested network capabilities. If not, the NCMF can further determine whether the service network slice can be configured to support the requested network capabilities. That is, whether the service slice is functionally capable of being configured to support the network capabilities, and whether the service slice has sufficient resources (for example, available processor and storage resources) to be configured to support the network capabilities.

[0318] Alternatively, the information in Tables 3 and 4 may be managed and maintained at the NSSF or NRF instead or in addition, in which case the NCMF may be co-located with the NSSF or NRF where the NF and NF service information is maintained.

[0319] Another alternative is to store this information in the UDR. This can provide an easier way for any NF to obtain this information by accessing the data storage device without the need to discover and communicate with the NCMF, NSSF or NRF.

[0320] As another alternative, the network capability profile may be implemented as an embodiment of a slice distinguisher (SD) in the S-NSSAI, so that it may be indicated what network capabilities the network slice supports. This may allow differentiation of network slices having the same slice / service type (SST) value of the network slice (e.g., MIoT, eMBB) but supporting different network capabilities.

[0321] On the UE / AS side, once the registration or registration update process is completed, the UE / AS can maintain information about what network capabilities the serving network slice supports. In addition, the UE / AS can maintain information about which application the network capabilities supported by the network slice are used for, because there may be multiple network slices serving different applications running on the UE.

[0322] Network slicing capability configuration

[0323] The network capability profile of Table 4 includes a network slice capability field for each network slice capability supported by the slice. This field indicates the specific capabilities supported by the slice. Examples of capabilities that a slice may support are listed below; the network may indicate support for these capabilities to the UE:

[0324] Maximum number of UEs per network slice

[0325] Maximum number of PDU sessions per network slice

[0326] Maximum UL and DL data rates per UE in the network slice

[0327] Support for deterministic communications

[0328] Support for group communication

[0329] Support for indicated isolation levels

[0330] Support for location-based messaging

[0331] Support for maximum packet size

[0332] Support for mission-critical communications

[0333] Support for MMTel

[0334] Support for performance monitoring

[0335] Support for indicated session and service continuity (SSC) modes

[0336] Non-IP Data Delivery (NIDD) and / or Reliable Data Service (RDS) support

[0337] Support for some RATs

[0338] Support for specific device speeds

[0339] Support for specific vertical applications such as V2X communications and mIoT communications

[0340] Support for a specific service area, where only those UEs located in that service area are allowed to access / connect to the network slice. A service area can be expressed in terms of a tracking area, a registration area, or a geographic area.

[0341] The maximum number of network slice instances that can be instantiated for a network slice.

[0342] Support for some relay mechanisms

[0343] Support for multiple tunneling mechanisms (L2TP tunnel, GRE tunnel or VPN tunnel).

[0344] Support for coverage of network slices (global, national, regional, limited to cells, sectors, base stations, etc.)

[0345] • Support for delay tolerance on UEs.

[0346] • Support for guaranteed DL throughput for UEs.

[0347] • Support for prediction frequency describing how often KQI and KPI prediction values ​​are provided to the UE. The UE can send requests in advance and receive prediction information about quality degradation (and thereby switch slices if needed).

[0348] SSC mode support (SSC mode 1, SSC mode 2, SSC mode 3, SSC mode 4)

[0349] Support for periodic traffic (deterministic communication), which can help optimize UE scheduling / performance.

[0350] Support for multiple radio spectrums, as some terminals may be restricted in the frequencies to use (e.g. n1, n77, n38, etc.).

[0351] Support for various access technologies.

[0352] Support for uplink throughput per network slice, which defines the achievable data rate for a network slice instance in uplink that is generally available within the coverage area of ​​the network slice.

[0353] Support for user data access, which defines how a network slice (or mobile network) should handle user data. For example, a UE can access the Internet, data can be routed to a dedicated network via tunneling, or all UE data can stay local. Support for slice quality of service parameters, which defines all QoS related parameters supported by a network slice.

[0354] Support for the maximum packet size supported by the slice, which may be important for URLLC (Ultra-Reliable Low Latency Communication) and MIoT (Massive IoT), or indicates the supported Maximum Transmission Unit (MTU). Thus, the UE may need to comply with this slice.

[0355] Support for network slice isolation levels (physical or logical isolation). This may affect or support UE isolation based on slices.

[0356] Note that some of the capabilities listed above may require additional configuration. For example, the "support for guaranteed DL throughput for UE" capability may be associated with a specific DL throughput value (e.g., 100 Mbps). This information will be captured in the "parameters of network capabilities" field of Table 4. The "parameters of network capabilities" may be indicated by the network to the UE.

[0357] Network Capability-Based Registration

[0358] Through the form of NCMF Figure 7 In the network capability layer, the UE can request the network capabilities it needs, and the UE does not need to know whether specific NFs and NF services are available in a certain network slice.

[0359] Figure 8 An example of a method for network capability-based registration is shown. When a UE registers, the UE may include an indication of a set of required network capabilities to support its applications, and the network may reply with an NSSAI and NSI ID that identify the network slice that supports all requested network capabilities. The network's response may also indicate which S-NSSAI is associated with each capability. Figure 8The steps of the registration method are shown in FIG. 1. Note that for the purpose of description, only information related to network capability configuration is described below. During the registration process, other information is involved, such as information related to mobility management, session management, etc.

[0360] In step 1, the UE may send a registration request message to the RAN node of the communication network. In the request message, the UE may indicate the following information:

[0361] ·A list of requested network capabilities, each of which is identified by a network capability identifier (ID). This information may be captured in a network capability profile as described in Table 4. This information may be associated with the request NSSAI, and a network capability profile may be provided per S-NSSAI in the NSSAI. When the UE first initiates registration, it may not have network capability mapping information. The UE may insert some requirements for network capabilities so that network entities (e.g., AMF, NCMF) can determine whether the existing network slice is able to serve the UE based on these requirements. Some requirements such as required network capability availability scheduling, required network capability QoS level, and required multi-tenant level are discussed below. The UE may determine the type of requested network capability based on the type of application running on the UE. An application may require multiple network capabilities. Therefore, the UE may need to maintain some information about which applications require what network capabilities in the 5G core network. When the UE communicates with the AS, the UE can obtain this information through application layer signaling.

[0362] Previous NSSAI: If available, the UE may include one or more S-NSSAIs to which it was assigned, if the UE was previously registered to the PLMN. This may assist the RAN node in selecting the AMF and may be used by the AMF to configure / select a network slice that supports the requested network capabilities. The included NSSAI may be the configured NSSAI or the allowed NSSAI provided to the UE in a previous registration procedure. This parameter is optional.

[0363] · Application ID: Indicates a set of applications that are requesting the requested network capability. It is possible that the UE is served by multiple network slices, and each network slice may serve a different set of applications, such as mIoT and eMBB. Accordingly, applications and network capabilities may be divided and supported by different network slices. The UE can then maintain information indicating which application is served by which network slice with a set of network capabilities. It is possible that a certain network capability is supported by more than one network slice serving different applications in the UE. Alternatively, the UE may provide application IDs without binding them to any network capability, and the SCS / AS will be contacted to determine which application is associated with which network capability. This may reduce the responsibility of the UE and may be useful for constrained devices.

[0364] PLMN ID: This indicates the PLMN that the UE intends to register with, if the UE has this information. Since different PLMNs can configure different network slices to provide the same network capabilities, the PLMN ID can facilitate network slicing and AMF selection.

[0365] • UE identifier such as GUTI and / or SUPI, if available.

[0366] Area information: used to select the network slice serving the UE. This information can be in the form of TAI, registration area or geographical area.

[0367] · Scheduling of required network capacity availability.

[0368] • Required network capability QoS level (e.g., service response time).

[0369] The required multi-tenancy level (e.g., how many applications on the UE will need to use the network capabilities). This information, along with the above network capability requirements, can be used by the network O&M system to determine whether existing slice instances, NFs, and NF services can be used to satisfy the request for network capabilities, or whether new instances need to be instantiated (e.g., based on availability and scalability requirements).

[0370] In step 2, upon receiving the registration request, the RAN node may select an AMF based on the requested network capabilities and the following information:

[0371] NSSAI and AMF association information, which indicates which AMF serves which network slice identified by NSSAI; and

[0372] Mapping information between network capabilities and S-NSSAI.

[0373] The AMF attaches the above information to the N2 message and sends it to the RAN node, so that the RAN node can obtain the above information. Alternatively, the core network periodically sends the above information to the RAN node to advertise its network slice information and supported network capability information, so that the RAN node can obtain the above information.

[0374] If the RAN node does not have any of the above information, or is not aware of any AMF that supports the requested network capabilities, the RAN node may select a default AMF based on its local configuration. In this case, another AMF may be selected later to serve the UE.

[0375] In step 3, the RAN node may forward the registration request to the selected AMF.

[0376] In step 4, the AMF may choose to contact the UDM to retrieve some subscription information, and / or contact the UDR to obtain some UE context information and network capability information.

[0377] In step 5, the AMF then queries the NCMF to obtain information about which network slice or slices can support the requested network capabilities and network capability usage requirements of the UE (such as the required network capability availability scheduling, the required network capability QoS level, and the required multi-tenant level as described above). The AMF may include the requested network capability information in the message. Alternatively, the AMF may query the NCMF to check whether the S-NSSAI in the requested NSSAI can provide the capabilities indicated in the network capability profile in step 1.

[0378] In step 6, the NCMF may check the mapping information of existing network slices to network capabilities and may return the NSSAI to the AMF to identify the network slice that supports all requested network capabilities. If the NCMF cannot identify any existing network slice that can support all requested network capabilities, the NCMF may indicate this in the response message. The NCMF may provide the AMF with a new set of S-NSSAIs that the UE can use to obtain the requested services. The NCMF may provide the AMF with the NSID of each S-NSSAI. The NCMF may provide the AMF with a network capability profile for each S-NSSAI.

[0379] In step 7, the AMF may compare the received NSSAI with the locally stored network slice information to decide whether the AMF can serve all NSSAIs required for all requested network capabilities. If the AMF is able to do so, the AMF shall update the UE context and proceed to step 10. Otherwise, the AMF may request the NSSF to perform network slice selection and proceed to steps 8 and 9 for any of the following cases: (1) the AMF cannot serve all NSSAIs; (2) the AMF cannot decide whether it can serve the NSSAI; or (3) the NCMF indicates that no existing network slices can support all requested network capabilities.

[0380] In step 8, the AMF requests the NSSF to select a network slice instance by providing the requested network capability information, PLMN ID and UE information (if available) such as 5G-GUTI capabilities and SUPI.

[0381] In step 9, based on the UE ID and PLMN ID, the NSSF can verify the NSSAI in the request and can select a network slice instance to provide all requested network capabilities to the UE. If a new AMF set is selected to serve the network slice, the NSSF can also select the NRF so that the new AMF can select the NF instance and NF service instance in the selected network slice. The NSSF can return one or all of the following information in the response:

[0382] NSSAI;

[0383] The selected NSI ID corresponding to the NSSAI in the request;

[0384] NRF address; and

[0385] The selected AMF set and / or AMF address.

[0386] If the existing network slice cannot serve the UE, the NSSF can contact the operation and management (O&M) system to initiate a new network slice and the corresponding network slice instance to serve the UE.

[0387] In step 10, once the response is received, AMF can inform NCMF of the mapping information between the selected network slice and the network capabilities. This is necessary for the case where NCMF does not find any network slice that supports all the requested network capabilities, for example in step 7.

[0388] In step 11, NCMF may update the mapping information between the selected network slice and the network capabilities.

[0389] In step 12a, if the current AMF is able to serve the UE, the AMF may send a registration response to the RAN node, which forwards the response to the UE. The N2 message from the AMF to the RAN node may contain the network capability profile of the selected network slice, i.e., the selected network slice information and all information related to the network capabilities supported by the network slice. In addition, location information or registration area information may be included in the response and provided to the RAN node and the UE so that the information can be mapped or associated with the selected network slice.

[0390] The registration accept message may include the network capability profile of each S-NSSAI in the allowed NSSAI. The network capability profile is an indication or description of the capabilities of the network slice. Table 4 lists the contents of the network capability profile of the network slice.

[0391] In the case where a UE is served by multiple network slices, the UE may maintain information identifying which application is served by which network slice instance with what network capabilities.

[0392] If the network slice cannot support the capabilities requested by the UE, the AMF may send a reject message including an error / reason code indicating the reason why the request cannot be supported.

[0393] Alternatively, the network may send the UE a network capability profile of a network slice that closely matches the requested network capability profile. For example, if the UE requires a guaranteed DL throughput network capability of 10 Gbps, the network may be able to scan matching network capability profiles for available network slices, and if the best available network capability for guaranteed DL throughput is 8 Gbps, the network may send the network capability profile to the UE to indicate whether the UE can accept the network capability profile and agree to register with the network slice. On the other hand, the network capability profile of the slice may provide more network capabilities and / or better quality of service (e.g., average UE UL / DL data rate, average latency, etc.) than the UE expects.

[0394] If the network sends a counter network capability profile to the UE, the UE may reject or accept the provided network capability profile.

[0395] If the UE accepts the offered network capability profile, the UE may send an acknowledgement to the AMF to indicate acceptance.

[0396] If the UE rejects the offered network capability profile, it may reject by sending a reject message (reject code) to the AMF. In this case, the AMF may reply with the default network slice and its network capability profile.

[0397] Alternatively, if the requested network capabilities are not available, the network may give the UE an NCP with a default slice with standard network capabilities.

[0398] In step 12b, if a new AMF is selected to serve the UE, the current AMF may initiate an AMF relocation procedure by contacting the target AMF according to the procedure described in 3GPP TS 23.502, Procedures for the 5G System; Stage 2, v15.1.0, Release 15, 2018-0.

[0399] Typically, the network capability request information transmitted in step 1 can be encapsulated in any NAS message, such as NAS-MM signaling between the UE and AMF, or NAS-SM between the UE and SMF. In this sense, the information can be encapsulated in service request messages as well as session management related request messages. The UE can include the network capability request in the NAS-SM message. For example, the UE can launch a new application that needs to use network capabilities X, Y, and Z. The UE may already be registered and have a PDU session on a network slice. The UE can issue a PDU session establishment request with an indication to start a new PDU session on the same network slice that supports network capabilities X, Y, and Z. The AMF or SMF can trigger an exchange with the NCMF to see if slice 1 is sufficient for this PDU session or if a new slice is needed.

[0400] Network-capable registration updates

[0401] Even after registration is complete and the UE is served by a network slice, the UE may require new network capabilities. For example, a new IoT application may be launched in the UE and require NIDD features that are not supported by the serving network slice. Fig. 9 An example of a method for UE initiated network capability based registration update is shown.

[0402] The network capability information provided in step 1 may be considered as NCP.

[0403] In step 1, the UE may initiate a registration update procedure using a registration update request message. The registration update request message may include one or all of the following information:

[0404] NSSAI: This is the configured NSSAI and / or allowed NSSAI obtained by the UE during the previous registration procedure;

[0405] PLMN ID: This is used to indicate the PLMN in which the UE is served by the network slice;

[0406] NSI ID: This indicates the network slice instance that is serving the UE;

[0407] Application ID: This is the identifier of the application on the UE that requires the new network capability;

[0408] Requested network capabilities: The UE may determine the type of network capabilities requested based on the type of new application that starts running on the UE. An application may require multiple network capabilities.

[0409] Information related to the UE's network capability usage requirements, such as required network capability availability schedule, required network capability QoS level (e.g., service response time, etc.), and required multi-tenancy level (e.g., how many applications on the UE will need to use the network capability).

[0410] · Scheduling of required network capacity availability

[0411] Required network capability QoS level (e.g., service response time)

[0412] The required multi-tenancy level (e.g., how many applications on the UE will need to use the network capabilities). This information, along with the above network capability requirements, can be used by the network O&M system to determine whether existing slice instances, NFs, NF services can be used to meet the request, or whether new instances need to be instantiated (e.g., based on availability and scalability requirements).

[0413] In step 2, the serving AMF may verify whether the UE is allowed to request new network capabilities and whether the information provided by the UE is valid.

[0414] In step 3, the serving AMF may optionally choose to contact the UDM / UDR to retrieve some more information about the UE and UE context in the UDR.

[0415] In step 4, the serving AMF may decide whether the newly requested network capability can be supported by any network slice served by the AMF. If the serving AMF is able to support the requested network capability, whether this is supported by the serving network slice or a different network slice, the AMF will proceed to step 12.

[0416] In step 5, if the serving AMF cannot support the UE's required network capabilities and network capability usage requirements, or if the serving AMF cannot decide whether it can support the UE's required network capabilities and network capability usage requirements, the serving AMF may send a network capability configuration request to the NCMF, which includes the UE context, NSSAI and required network capability information stored in the AMF.

[0417] In step 6, when the request is received, the NCMF may check the mapping information between the available network slices and their network capabilities, as well as the network capability profile, to find a network slice that supports the requested network capability.

[0418] In step 7, the NCMF can then determine whether the requested network capabilities can be supported by any network slice without changing the serving AMF.

[0419] In step 8a, if the NCMF determines that the serving network slice cannot support the network capabilities requested by the UE, it will request the NSSF to select a new network slice.

[0420] In step 9a, NSSF may select one or more network slice instances and, potentially, a new AMF set and NRF. NSSF may return any selection results, including NSI ID, NSSAI, NRF address, and AMF set. If a new AMF is selected, the AMF relocation process may be triggered in step 12b. If a new network slice is selected without changing the AMF, the UE may be connected to two network slices simultaneously. If the existing network slice cannot serve the UE, the NSSF may contact the operations and management (O&M) system to initiate a new network slice and corresponding network slice instance to serve the UE.

[0421] In step 8b, if NCMF determines that the serving network slice can support the network capability requested by the UE, and the network capability has not yet been enabled, NCMF may send a request to NSSF to update the serving network slice information to indicate that the network slice will support the network capability. NCMF may include the requested network capability information, the NSIID serving the UE, and the NSSAI being served by the AMF in the request message.

[0422] In step 9b, NSSF may update the network slice information and may reply to NCMF for confirmation.

[0423] In step 10, the NCMF may also update the mapping information to indicate that the network slice supports the network capabilities requested by the UE.

[0424] In step 11, the NCMF may send a response to the serving AMF with all or some of the following information:

[0425] NSSAI;

[0426] A new NSI ID for case "a" where a new network slice is selected;

[0427] A new AMF set for case "a" where a new network slice is selected; and

[0428] The serving AMF and the serving network slice are able to support the configuration result of case “b” of the network capability.

[0429] In step 12, the serving AMF may update the UE context and serving network slice information for case "b", or may initiate a process of relocating the AMF for case "a".

[0430] In step 13, if the serving AMF has not been changed, the serving AMF may reply to the UE with a registration update response to indicate the serving network slice information. If the NSSF selects a new AMF, the target AMF may contact to confirm the registration update with the new network capabilities enabled.

[0431] UE configuration update based on network capabilities

[0432] In addition to the UE, the network or AS may also initiate an update of the UE configuration due to a network capability update in the serving network slice. For example, the following events may trigger the network or AS to start the process:

[0433] A new application is started in the SCS / AS, and the UE subscribes to the new application service in the SCS / AS. As a result, new network capabilities are required to support the new application.

[0434] Due to some reasons like load balancing issues or downsizing of the network functions / network slice instances in the serving network slice, the network wants to switch to a new network slice to serve the UE.

[0435] Fig.10 A method for UE configuration update based on network capabilities is presented.

[0436] In step 0, this is a prerequisite step assuming that the UE has completed registration with the network and the UE has a connection to an Application Server (AS) through the network.

[0437] In step 1a, the AS may decide to add or update network capabilities in the network slice serving the UE due to certain events (e.g., a new application session is required). In the case of a new application, the AS may determine the type of network capabilities requested based on the type of the new application.

[0438] In step 1b, AMF decides to change the network slice serving the UE for some reason (such as load balancing of the serving network slice).

[0439] In step 2a, the AS sends a network capability configuration request message to the NCMF via the NEF. The information provided in this step may be the NCP, and may include the following information:

[0440] UE ID, such as SUPI, GUTI or external UE ID;

[0441] NSSAI, which indicates the serving network slice used for the connection between the UE and the AS;

[0442] New network capability information to be added to the network slice to support communication between UE and AS;

[0443] Information related to network capability usage requirements for communications between the UE and the AS, such as required network capability availability schedule, required network capability QoS level (e.g., service response time, etc.), and required multi-tenancy level (e.g., how many applications on the UE or AS will need to use the requested network capability);

[0444] An application ID, which indicates the application associated with the requested network capability;

[0445] A reference ID used to refer to this network capability configuration process; this may be assigned by the NEF; and

[0446] NSI ID: Indicates the network slice instance serving the UE.

[0447] In step 2b, AMF sends a network capability configuration request message to NCMF.

[0448] In step 3, upon receiving the request, the NCMF may optionally choose to contact the UDM / UDR to retrieve the UE context and some more subscription information of the UE in the UDR.

[0449] In step 4, the NCMF may check the network slice information and the requested network capability information. The purpose of these checks is to:

[0450] Verify the information provided by the AS or network function, such as network slice information, network slice instance information; and

[0451] Determine whether the serving network slice is able to support the requested network capabilities and network capability usage requirements of the UE and AS. This can be achieved by checking the network capability profile of the network slice. If not, proceed to step 5.

[0452] In step 5, if NCMF finds that the service network slice cannot support the requested network capabilities, NCMF can turn to NSSF to select a new network slice or formulate a new network slice. It is also possible that NCMF finds that the service network slice is overloaded, if so, it can request NSSF to select a new slice.

[0453] In step 6, NCMF or NSSF informs AMF to continue with the network configuration process. If the process is triggered by AS (i.e., steps 1a and 2a), AMF will be provided with UE ID, NSSAI, NSI ID, SCS / AS ID, NEF ID and Reference ID. This information can be used by AMF to contact NEF later.

[0454] In step 7, the AMF communicates with the UE to trigger the UE configuration update. In the message, the AMF will inform the UE of the NCP of the slice, and the NCP includes one or more of the following information:

[0455] New network capability information;

[0456] Identify the NSSAI of the network slice, especially if a new network slice is selected;

[0457] Reference ID; and

[0458] SCS / AS ID.

[0459] In step 8, the UE initiates Fig. 9 The registration update process represented in .

[0460] In step 9, once the registration update process is completed, in the case where the AS initiates the process, the AMF sends a reply message to the AS via the NEF.

[0461] Notice, Fig.10 The scenario where the AMF starts the process is shown as an example of a network entity initiating the process. Other network entities may also initiate the process. For example, the PCF may initiate the process due to a UE policy change or a network slice selection policy change. The PCF may then trigger the network slice selection process, which may potentially affect the network capability provisioning to the UE.

[0462] Registration process for the requested NSSAI network capability profile

[0463] The NCMF may configure network capabilities for network slices and establish a Network Capability Profile (NCP) for each slice. This section details the methods described earlier in this document and describes how the NCP may be transmitted to the UE along with the NSSAI (e.g., one NCP per S-NSSAI). Fig.13 The method is depicted in , and illustrates how the initial registration procedure may be enhanced to support configuration of network capabilities, however it should be appreciated that the same enhancements may apply to mobility registration update procedures and periodic registration update procedures.

[0464] Fig.13 It illustrates how the initial registration procedure, the mobility registration procedure, and the periodic registration procedure defined in 3GPP TS 23.502 may be updated. Fig.13 Particular emphasis is placed on the parts of the registration process that could be enhanced or need the most enhancement. Some steps have been omitted. Note that Fig.13 Indicates that NCMF is an independent NF or logical function. It can be part of the OAM system or other NFs such as SMF or AMF instead.

[0465] like Fig.13As shown in , the AMF can determine the capabilities of the slice to which the UE will register and provide the capability information to the UE. In addition, the UE can request certain capabilities. In addition, the network can provide the UE with a list of S-NSSAIs and associated NCPs to which the UE can register.

[0466] In step 1, the UE sends a registration request including the requested NSSAI, and the UE sends the request to the AMF via the (R)AN node. The registration request can be an initial registration, a mobility registration update, or a periodic registration update. As described earlier in this document, the registration request can include an NCP to indicate to the network what capabilities are expected for each S-NSSAI in the NSSAI.

[0467] In step 2, the (R)AN node selects an AMF as described in TS 23.501 [1], clause 6.3.5.

[0468] In step 3, the (R)AN node forwards the registration request message to the AMF.

[0469] In step 4, based on the registration request from the UE, the AMF may query the UDM / UDR to obtain the UE's subscription. The UE subscription may include the subscribed S-NSSAI.

[0470] In step 5, if no information is obtained in the previous step, then for each S-NSSAI in the allowed NSSAI, the AMF may request the network capability profile from the NCMF. The key of such a query shall include S-NSSAI (ie, NSSAI).

[0471] Alternatively, the AMF may obtain the NCP associated with each S-NSSAI by querying other NFs such as NSSF or NRF to obtain the NCP associated with each S-NSSAI.

[0472] In step 6, the NCMF may send the NCP of the requested S-NSSAI back to the AMF.

[0473] In step 7, as part of the Registration Accept message, the AMF sends the allowed NSSAI and the configured NSSAI, as well as the NCP for each S-NSSAI in the allowed NSSAI and the NCP for each S-NSSAI in the configured NSSAI to the UE. The NCP may be considered as part of the allowed NSSAI and the configured NSSAI.

[0474] Optionally, the network may send an advertising NSSAI to the UE. The advertising NSSAI is a list of S-NSSAIs and their corresponding NCPs. The list and the corresponding S-NSSAI may be an indication of which slices the UE can get advertisements for and the capabilities of each slice. The S-NSSAI in the advertising NSSAI may not be part of the requested NSSAI or the allowed NSSAI. The purpose of the advertising NSSAI may be to provide the UE with information about which slices it can request to be added to its configured NSSAI or allowed NSSAI. Alternatively, the advertising NSSAI may be part of the configured NSSAI.

[0475] In step 8, if the UE determines that the allowed NSSAI and / or any NCP provided with the S-NSSAI are insufficient, in the sense that the capabilities of the slice are insufficient, the UE may evaluate the advertised NSSAI and, if it finds a suitable S-NSSAI within the advertised NSSAI, start a registration update procedure and include the S-NSSAI in the advertised NSSAI in the requested NSSAI. The UE and the network may then perform a registration update procedure and the network may update the UE's allowed NSSAI and configured NSSAI accordingly.

[0476] Network capability profile delivery using UE policy updates

[0477] UE policy related to NCP may be referred to as NCP policy or NCPP. This section describes a method by which the core network may be able to deliver NCP to the UE as part of the UE policy. Note that the NCP policy may be sent to the UE via a UE configuration update using the transparent UE policy delivery procedure defined in 3GPP TS 23.502. Fig.14 The method is illustrated by focusing on how existing processes can be enhanced.The method can be triggered by a number of events as described in step 0.

[0478] In step 0, an event may occur. Notification of the event may be sent to the PCF so that the PCF can determine whether the NCP policy needs to be updated. Examples of events are:

[0479] The OAM system or authorized AS may send a request for an update and NCP. The request may be sent via the NEF. For example, the AS or OAM may send a request to the NEF to increase the maximum UL or DR data rate allowed for the UE in a slice, or to increase or decrease the maximum number of PDU sessions allowed in a slice.

[0480] The PCF receives notification from the AMF that the UE has changed location (e.g., UE policy may be limited to a geographical area, so a new policy may need to be updated).

[0481] The PCF receives notification that the subscribed S-NSSAI has changed for a UE or a group of UEs (e.g., a network administrator may update the UE subscription with a new S-NSSAI).

[0482] The PCF receives notification that the UE has moved from EPS to 5GS. The UE will receive a new set of UE policies for 5GS.

[0483] UE sends a policy update request to PCF (via NAS). The UE's request for a UE policy update may be in response to downloading, launching and / or installing an application that requires new network capabilities. For example, a user may download a gaming application that requires AR / VR settings. This may require a new set of policies to accommodate changes in data rates and other CN resources. The request may include an application or OS identifier.

[0484] The PCF receives notifications from OAM or from NRF that the network functions associated with the slice are reconfigured (e.g., new NFs are instantiated or removed, existing NFs are scaled up or down).

[0485] ·NCMF sends the updated NCP information of S-NSSAI to PCF.

[0486] In step 1, the PCF checks the latest list of PSIs to decide which policies related to UE access selection and / or PDU session selection must be sent to the UE. Alternatively, the PCF must contact the NCMF to obtain a new set of NCPs for the S-NSSAI, or the NCMF can send new NCP information for the S-NSSAI to the PCF. The PCF populates the enhanced UE policies including the NCPPs.

[0487] In step 2, PCF invokes the Namf_Communication_N1N2MessageTransfer service operation of AMF. The message includes SUPI, UE policy container. The UE policy container includes NCPP for the UE. In other words, NCP is treated as UE policy by 5GS like any other UE policy; they are either stand-alone policies or the information is integrated with ANDSP or URSP policy.

[0488] In step 3, if the UE is registered with 3GPP access or non-3GPP access and is reachable by the AMF, the AMF shall transparently deliver the UE policy container (which includes the NCPP) to the UE via one of the registered and reachable accesses based on the AMF local policy.

[0489] The UE receives and stores the NCPP policy at step 4. The policy may be considered as a standalone policy, or the NCP information described herein as part of the policy may be provided to the UE as part of the URSP rules or ANDSP.

[0490] Examples of how the UE can act based on policies are:

[0491] If the NCP policy indicates a new periodic traffic rule, the UE may need to update the reception or transmission period of the periodic traffic. On the other hand, if the UE does not have a policy regarding periodic traffic, the UE may implement the new policy by sending and receiving messages within a specified time period. For example, the UE may need to continuously send sensor readings to the server every 10 seconds, which may be updated to 5 seconds when the UE is expected to travel at high speed. By enhancing the validation criteria of the URSP, the periodic traffic rules can be integrated into the URSP rules so that the communication period can be indicated to the UE. The UE can then take this information into account when evaluating the URSP rules.

[0492] ·If the NCP policy indicates a maximum UL and / or DL ​​data rate, then when the UE evaluates the URSP rules, it may take into account the maximum UL and DL data rates provided in the NCP information. The UE may choose not to establish the route described in the RSD or URSP, and instead establish a lower priority route. For example, a lower priority route may allow a higher UL or DL ​​maximum data rate. When the route is established, the UE may provide the maximum UL and / or DL ​​data rate to the application that initiated the traffic and to any other applications that use the same route after the route is established. In addition, if the NCP indicates a maximum UL throughput per slice, the UE enforces this limitation by monitoring the total throughput of all PDU sessions in the slice.

[0493] If the NCP policy indicates location-based messaging and the UE appears to be in a restricted location, the UE may need to stop receiving or sending data in messages. The network may provide this information to the UE as a validation criterion in the URSP rules, or the network may provide this information to the UE as a separate NCP policy that is considered when evaluating all URSP rules. In other words, the policy may be considered when evaluating all routes that include S-NSSAI from the NCP policy.

[0494] The UE may send a registration update request to the network to register with a different slice that may allow for a more favorable NCP policy. In other words, the UE may send a mobility registration update request and the request may include an updated requested NSSAI and the updated requested NSSAI may not include the S-NSSAI for which the UE has just received a policy.

[0495] Maximum number of PDU sessions to process

[0496] This section describes the procedure for how the network handles the pre-defined limit on the number of PDU Sessions per network slice and how the UE may handle the request if it finds that no more PDU Sessions can be established.

[0497] Handling of Maximum PDU Session during PDU Session Establishment Process

[0498] The network may support a maximum limit on the number of PDU Sessions that may be established within a network slice. There may be situations where a network slice may reach its maximum limit, but it may still receive PDU Session establishment requests from UEs. This section describes how such requests may be handled. Fig.15 The method is described and illustrates how the existing PDU session establishment procedure defined in 3GPP TS 23.502 can be enhanced. Fig.15 Particular emphasis is placed on the parts of the registration process that should be enhanced or need the most enhancement.

[0499] At step 0, the network slice is configured with a limit on the maximum allowed number of PDU sessions per slice. This is configured in the NCMF. The NCMF includes a PDU session counter that counts the number of PDU sessions that join the network slice. For each PDU session established or released, the session counter increments or decrements the number by 1 respectively. The NCMF may receive a notification from the SMF when a PDU session is established.

[0500] In step 1, the UE sends a PDU session establishment request to the AMF via the (R)AN node.

[0501] In step 2, upon receiving a PDU session establishment request from the UE, the AMF or SMF sends a request to the NCMF to check whether a new PDU session can be established in the slice. The request includes the S-NSSAI. The NCMF checks the PDU session counter of the slice to see if the number of PDU sessions in the slice is lower than the maximum value. If the NCMF indicates that the number of PDU sessions is lower than the maximum value, the PDU session will be allowed, otherwise it will not be allowed and the PDU session establishment request will be rejected.

[0502] In step 3, the rest of the PDU session establishment process of TS23.501 is executed and a PDU session establishment response is sent to the UE. If the NCMF indicates to the AMF or SMF that the PDU session should not be allowed (i.e., the slice has reached the maximum number of PDU sessions), the AMF or SMF may send an error / cause code to the UE to indicate that the network slice has reached its maximum limit on the PDU session count and reject the request. In this case, the UE may reevaluate its URSP rules and attempt to establish a PDU session in a different slice. The response may also include a waiting timer indicating how long the UE must wait before attempting to establish a PDU session in the same slice. However, if the UE terminates the PDU session with the same slice before the waiting timer expires, the UE may reset the waiting timer and try again. The waiting time may be integrated into the time window (routing verification criterion) in the URSP rule. Thus, the URSP rules are reevaluated before retrying to establish the PDU session.

[0503] After receiving the PDU Session Establishment Reject message, the UE may:

[0504] Re-evaluate its URSP rules knowing that the rejected slice is not available and attempt to establish a PDU session based on lower priority URSP or RSD rules.

[0505] Wait for the duration of the wait timer, then re-evaluate its URSP rules and try to establish a PDU Session again within the same slice.

[0506] Terminate the PDU Session with the same slice, clear / invalidate the wait timer if it has not expired, then re-evaluate its URSP rules and try to establish the PDU Session again within the same slice. It is proposed to modify the PDU Session Establishment Request to allow the UE to indicate the PDU Session ID in the slice that can be terminated. This enhancement to the PDU Session Establishment procedure may be desirable if the slice is PDU Session Restricted and the UE is willing to terminate the lower priority PDU Session, under the condition that the UE can immediately re-establish a new, higher priority PDU Session.

[0507] Using NAS notification to handle maximum PDU session

[0508] This section describes a method in which NAS notification is used to inform the UE that a network slice has reached its maximum limit. Fig.16 The method is described.

[0509] At step 0, the network slice is configured with a limit on the maximum allowed number of PDU Sessions per slice. This is configured in the NCMF. The NCMF includes a PDU Session counter which counts the number of PDU Sessions joining the network slice. For each PDU Session established or released, the session counter increments or decrements the number by 1 respectively. The NCMF can receive a notification from the SMF when a PDU Session is established. The AMF and SMF within a slice subscribe to the NCMF to be notified when the number of PDU Sessions within the slice reaches the maximum value or falls below the maximum value.

[0510] In step 1, the UE and the network perform the PDU session establishment procedure as described in section 4.3.2.2.1 of 3GPP TS23.502. Upon receiving a PDU session establishment request from the UE, the AMF or SMF sends a request to the NCMF to check whether a new PDU session can be established in the slice. The request includes the S-NSSAI. The NCMF checks the PDU session counter of the slice to see if the number of PDU sessions in the slice is lower than the maximum value. If the NCMF indicates that the number of PDU sessions is lower than the maximum value, the PDU session will be allowed, otherwise it will not be allowed and the PDU session establishment request will be rejected. The situation where the PDU session is rejected is described earlier in this document. In the example of this process, it is assumed that the PDU session establishment is successful.

[0511] In step 2, the AMF or SMF receives a notification from the NCMF that the network slice has reached the maximum number of PDU sessions.

[0512] In step 3, the AMF sends a NAS notification to all UEs registered to the slice. The NAS notification includes a waiting timer that indicates how long the UE must wait before attempting to establish a PDU session within the slice. However, if the UE terminates the PDU session with the same slice before the waiting timer expires, the UE can reset the waiting timer and try again. The waiting time can be integrated into the time window of the routing validation criteria in the URSP rules. The URSP rules will be re-evaluated before retrying to establish a PDU session.

[0513] In step 4, wait for the timer to expire or the UE to terminate the PDU session with the same slice.

[0514] In step 5, the PDU session termination process decrements the NCMF counter, so that the PDU session counter drops below a predetermined value. When the number of PDU sessions in a slice is lower than a predetermined value, the NCMF sends a notification to the AMF and SMF.

[0515] In step 6, the AMF sends a NAS notification to all UEs registered to the slice. The NAS notification indicates that the condition has been cleared so that a PDU session can now be established in the slice. Alternatively, the notification may be sent only to the UE whose PDU session establishment request was rejected with a cause code.

[0516] In step 7, the UE may reset the waiting timer and attempt to establish a PDU session in the slice.

[0517] Maximum number of UEs to be handled in a network slice

[0518] The network may be equipped with the capability to limit the maximum number of UEs that can be registered to a network slice simultaneously. There may be situations where the network may receive a request from a UE to register to a network slice that has reached its maximum registered UE limit. This section describes methods for handling this situation. Fig.17 The method is described.

[0519] In step 0, a counter may be maintained in the NCMF. For each UE that registers or deregisters, the counter increments or decrements by 1. When a UE registers or deregisters, the AMF may send an indication / notification to the NCMF so that the counter may be incremented or decremented accordingly. The NCMF may have subscribed to all AMFs in the slice so that it can receive notifications when a UE registers to the slice. The subscription request may indicate the S-NSSAI, and the notification from the AMF may include the UE ID and the S-NSSAI, so that the NCMF can track which UEs are registered, query the status of registered UEs, and avoid counting errors in the event of a notification about the registration or deregistration of a UE. The NCMF may also indicate to the AMF that the number of UEs registered to the slice is limited, so that the AMF knows to verify with the NCMF for permission to register a new UE (i.e., check that the limit has not been reached).

[0520] In step 1, the UE (UE1) and the network perform the UE registration procedure as described in section 4.2.2.2.2 of 3GPP TS23.502. When receiving a UE registration request from UE1, the AMF sends a request to the NCMF, or calls the NCMF service, to check whether a new UE can be registered in the slice. The request includes the S-NSSAI. The NCMF checks the UE registration counter of the slice to see if the number of UEs registered in the slice is lower than the maximum value. If the NCMF indicates that the number of UEs registered in the slice is lower than the maximum value, the UE registration is allowed, otherwise the UE registration will not be allowed and the UE registration request will be rejected. In this step of the process, it is assumed that the UE registration from UE1 is successful.

[0521] In step 2, the AMF may receive a notification from the NCMF that the network slice has reached the maximum number of UEs. The NCMF may provide a waiting timer to the AMF to indicate how long the UE should wait before retrying to register with the S-NSSAI.

[0522] In step 3, a different UE (e.g., UE2) may send a UE registration request to the network. For each slice, the request may indicate that if registration for the slice is rejected, the UE wishes to be notified when the rejection reason is cleared.

[0523] NOTE: If the AMF has not received a notification from the NCMF that the network slice has reached the maximum number of UEs, the AMF may query the NCMF to check whether the UE can be registered as described in step 1.

[0524] In step 4, if the AMF has been notified that the network slice has reached its maximum UE registration limit, the AMF may send a UE Registration Response message to UE2 indicating that the request has been rejected and a cause value indicating that the request is rejected because the slice has reached the maximum number of registered UEs. The rejection may also provide a wait timer to the UE, which the UE should use to determine when it can attempt to request UE registration again in the same slice. Otherwise, if the slice limit has not been reached, UE2 and the network perform the registration procedure as described in section 4.2.2.2.2 of 3GPP TS23.502.

[0525] In step 5, a UE (e.g., UE3) that has been registered in the network slice may deregister from the network slice.

[0526] In step 6, the AMF may notify the NCMF of the UE deregistration. The NCMF may decrement the counter. Additionally, the NCMF may send a notification to let the AMF know that the network slice is now below its maximum limit.

[0527] In step 7, the AMF may send a NAS notification to any UE (e.g. UE2) whose registration was rejected with a cause code (i.e., a message about the network slice reaching the maximum limit and waiting timer) and has a waiting timer still running. The NAS notification indicates that the restriction condition has been removed.

[0528] In step 8, when receiving a NAS message from the network, UE2 can reset the waiting timer and attempt to register with the slice.

[0529] Alternatively, the UE may attempt UE registration after the waiting timer expires.

[0530] Note that this process can be viewed as an extension or enhanced interpretation of the network capability-based registration process described earlier in this document.

[0531] Handling of maximum UL and DL data rates within a slice

[0532] As described above, the network can provide the UE with the maximum UL and DL data rates that the UE can use within a slice. These maximum data rates apply to all PDU sessions within the slice.

[0533] The network can also provide this information to the UE whenever a PDU session is established within a slice.

[0534] Whenever the network detects that the UE has exceeded the maximum UL or DL ​​data rate within a slice, the network may send a NAS notification to the UE. The notification may indicate the maximum UL or DL ​​data rate to the UE so that the UE may implement the maximum UL or DL ​​data rate.

[0535] NCMF Services

[0536] As mentioned above, the NCMF is responsible for managing and maintaining information related to network capabilities and network slices. Table 5 shows a list of NCMF services that can be provided to enable these operations.

[0537] Table 1: List of NCMF services

[0538]

[0539] Alternatively, if the NCMF is co-located with the NSSF or UDM / UDR, the NCMF services shown in Table 5 may be defined as NSSF services or UDM / UDR services.

[0540] New UPF Services

[0541] In the 5G service-based architecture, UPF is not involved as a user plane function. However, it can be seen that UPF has some control functions, such as QoS enforcement, data caching, and event monitoring. By extending the service-based architecture to UPF, some UPF services can be added. Fig.11 The extended service-based architecture with UPF and Nupf interfaces is shown. Table 6 shows the list of UPF services.

[0542] Table 2: List of UPF services

[0543]

[0544] Nupf_EventExposure

[0545] This service allows other NFs to subscribe to certain events at the UPF and be notified when the subscribed events occur. The UPF can provide subscription services for the following events:

[0546] · DL data packets buffered in UPF are discarded due to timeout threshold or limited storage space. This can be per QoS flow, per session, per UE or per UPF.

[0547] The UPF is selected as the uplink classifier for the local data network or as the branching point for multi-homed PDU sessions.

[0548] • The UPF is selected as the anchor point for the PDU session via 3GPP access or non-3GPP access (ie, through the N3IWF).

[0549] The packet is dropped because of policy rules enforced by the UPF for specific traffic, including information about the SCS / AS that originated the traffic, and what specific rules were enforced.

[0550] The total number of connected UEs supported by the UPF exceeds a certain threshold.

[0551] The total number or ratio of rejected or failed connection attempts exceeds a threshold. If the total number or ratio of rejected or failed connection attempts with a specific reason value exceeds a threshold, this may further qualify for a request for notification.

[0552] Computing resources are below the threshold.

[0553] The total number of sessions being managed by the UPF exceeds a certain threshold.

[0554] • The total (guaranteed) data rate of the sessions being managed by the UPF exceeds a certain threshold.

[0555] The utilization of the memory allocated for downlink data buffering exceeds a certain threshold.

[0556] In case no PDR is suitable for the application data, the mapping of DL data flow to QoS flow fails.

[0557] The following information may be included in a (un)subscription request or notification message:

[0558] Subscription ID

[0559] Notification address / ID

[0560] Event ID and corresponding parameters: For example, if the event is PDU session congestion, it will include PDU session ID, QFI and resource utilization. If the event is packet discard, the reason for discard, session ID, QFI and the number of packets buffered in UPF will be provided.

[0561] In case the AF cannot directly access the UPF via a service-based interface, the NEF can be the service consumer.

[0562] Nupf_StatusMonitoring

[0563] This service provides the NF with the opportunity to obtain information about the PDU session status and QoS implementation status from the UPF. The UPF can provide the following information through this service:

[0564] • Number of PDU sessions for which the UPF acts as an anchor point, branch point or uplink classifier respectively.

[0565] The amount of downlink data buffered in the UPF. This can be per application, per UE, per group of UEs, per PDU session, per QoS flow or per location (i.e. within a network area).

[0566] • Number of PDU sessions connecting UEs via non-3GPP accesses.

[0567] • The currently achieved bit rate. This can be per application, per UE, per group of UEs, per PDU session, per QoS flow or per location (ie within a network area).

[0568] Packet error rate (loss rate). This can be per application, per UE, per group of UEs, per PDU session, per QoS flow or per location (ie within a network area).

[0569] The percentage of storage resources used for data caching. Information related to billing, such as CDR.

[0570] In case the AF cannot directly access the UPF via a service-based interface, the NEF can be the service consumer.

[0571] Nupf_PDUSession

[0572] This service provides the SMF with the ability to initiate certain processes to manage PDU sessions (such as creating, updating, and releasing PDU sessions). The SMF may include the following information for PDU session related processes:

[0573] PDU session ID and associated network slice ID, such as S-NSSAI and network slice instance ID

[0574] DNN

[0575] PDU session type, such as non-IP, Ethernet, or IP

[0576] Session and Service Continuity (SSC) mode

[0577] QFI and related QoS parameters, such as maximum bit rate per QoS, maximum aggregate bit rate per session, and maximum packet loss rate

[0578] Support reflective QoS indication

[0579] Packet detection rules (PDR) for both DL and UL traffic

[0580] SMF information, such as SMF ID, SMF instance ID

[0581] Tunnel information for N3 and N6 (e.g., for NIDD forwarding) tunnels respectively

[0582] Billing policy ID

[0583] • An indication to add or remove a UPF as an uplink classifier or branching point associated with a PDU session.

[0584] UE ID, such as 5G-GUTI and SUPI

[0585] IP address and port number

[0586] Example GUI

[0587] Fig.12 An example user interface that can be used to configure network capabilities in a 5G network is shown. The user interface can be displayed by or for a terminal device (UE), a service provider (SCS / AS), a network operator, or other network entity or user. For example, the user interface can be displayed on Figure 1B and 1G on display 128 or 86.

[0588] Fig.18 A user interface is described through which a UE can receive an NCP of allowed S-NSSAI from the network. Based on the application requirements, the UE can accept the network slice based on the received NCP or request a new NCP / network slice from the core network.

[0589] It should be understood that the above network entities, including Figure 8-10 The network entities of the steps shown in the figure, such as UE, (R)AN, AMF, NCMF, NSSF, UDR / UDSF, UDM / UDR, NRF, NEF, PCF, NF, SCS / AS, (R)AN, SMF, etc., can be logical entities that can be implemented in the form of software (i.e., computer-executable instructions), and the software is stored in a device configured for wireless and / or network communication or such as Figure 1B or Figure 1G in the memory of the computer system shown in and executed on its processor. That is, Figure 8-10 The method shown in can be implemented in the form of software (ie, computer executable instructions) stored in a computer such as Figure 1B or Figure 1G The computer executable instructions are stored in a memory of a device such as a computer system or a computer system, and when executed by a processor of the device, the computer executable instructions perform Figure 8-10 It should also be understood that Figure 8-10 The functions shown in can be implemented as a set of virtualized network functions. The network functions do not necessarily communicate directly, instead, they can communicate via forwarding or routing functions. It should also be understood that Figure 8-10 Any sending and receiving steps shown in can be performed by the communication circuit of the device under the control of the processor of the device and the computer-executable instructions (such as software) executed by the processor.

[0590] Additional embodiments may include:

[0591] 1. A device, comprising a processor and a memory, the memory storing computer executable instructions, which, when executed by the processor, cause the device to perform operations comprising:

[0592] sending a network capability configuration request to an entity of a core network of a communication network, the request comprising a list of one or more network capabilities requested by the device; and

[0593] A response is received from an entity of the core network including an identifier of a network slice that supports the requested one or more network capabilities.

[0594] 2. The apparatus of embodiment 1, wherein the request further comprises one or more of the following:

[0595] an identifier of each of the one or more network capabilities requested;

[0596] Network slice selection information and / or one or more network slice IDs for supporting the requested one or more network capabilities; and

[0597] An identifier of each of one or more applications hosted on the device that require the requested network capability.

[0598] 3. The apparatus as described in embodiment 2, wherein the request further includes one or more of the following:

[0599] an identifier of the device;

[0600] an identifier of a public land mobile network (PLMN) to which the device may be registered;

[0601] Information associated with the geographic region in which the device is requesting network capabilities.

[0602] 4. The apparatus as described in embodiment 2, wherein the request further includes one or more of the following:

[0603] information specifying an availability schedule associated with the requested one or more network capabilities;

[0604] information specifying a quality of service (QoS) level associated with the requested one or more network capabilities; and

[0605] Specifies multi-tenancy level information associated with the requested network capability or capabilities.

[0606] 5. A method performed by a user equipment (UE), comprising:

[0607] Sending a network capability configuration request to an entity of a core network of a communication network, the request comprising a list of one or more network capabilities requested by the UE; and

[0608] A response is received from an entity of the core network including an identifier of a network slice that supports the requested one or more network capabilities.

[0609] 6. The method as described in embodiment 5, wherein the request further includes one or more of the following:

[0610] an identifier of each of the one or more network capabilities requested;

[0611] Network slice selection information and / or one or more network slice IDs for supporting the requested one or more network capabilities; and

[0612] An identifier of each of one or more applications hosted on the UE that require the requested network capability.

[0613] 7. The method as described in embodiment 6, wherein the request further includes one or more of the following:

[0614] an identifier of the UE;

[0615] an identifier of a public land mobile network (PLMN) with which the UE may be registered;

[0616] Information associated with the geographical area in which the UE is requesting network capabilities.

[0617] 8. The method as described in embodiment 6, wherein the request further includes one or more of the following:

[0618] information specifying an availability schedule associated with the requested one or more network capabilities;

[0619] information specifying a quality of service (QoS) level associated with the requested one or more network capabilities; and

[0620] Specifies multi-tenancy level information associated with the requested network capability or capabilities.

[0621] 9. A device for implementing an entity of a core network, the device comprising a processor and a memory, the memory storing computer executable instructions, when executed by the processor, the computer executable instructions cause the entity of the core network to perform operations, the operations comprising:

[0622] receiving, from a user equipment (UE), a request including a list of one or more network capabilities requested by the UE;

[0623] Determining, based on a network capability profile associated with a network slice currently serving the UE, whether the network slice currently serving the UE supports the requested one or more network capabilities;

[0624] If the network slice currently serving the UE cannot support the requested one or more network capabilities, formulate or select a new network slice that can support the requested one or more network capabilities to serve the UE; and

[0625] A response is sent to the UE including an identifier of a network slice selected to support the requested one or more network capabilities.

[0626] 10. The apparatus of embodiment 9, wherein the network capability profile comprises one or more of the following:

[0627] The identifier of the network slice and the corresponding network slice instance;

[0628] a list of identifiers of supported network capabilities;

[0629] an identifier of the serving PLMN; and

[0630] Service area information for each network capability.

[0631] 11. The apparatus of embodiment 9, wherein the request further comprises one or more of the following:

[0632] an identifier of each of the one or more network capabilities requested;

[0633] Network slice selection information and / or one or more network slice IDs for supporting the requested one or more network capabilities; and

[0634] An identifier of each of one or more applications hosted on the user device that requires the requested network capability.

[0635] 12. An apparatus as described in Example 9, wherein the instruction further causes an entity of the core network to perform operations including initiating a new network slice.

[0636] 13. An apparatus as described in Example 9, wherein the instruction further causes the entity of the core network to perform operations including: selecting a new core network entity that terminates non-access stratum (NAS) signaling with the UE and serves the newly selected network slice.

[0637] 14. An apparatus as described in Example 9, wherein the instructions also cause an entity of the core network to perform operations including updating a network capability profile associated with a newly selected network slice.

[0638] 15. A method performed by an entity of a core network, comprising:

[0639] receiving, from a user equipment (UE), a request including a list of one or more network capabilities requested by the UE;

[0640] Determining, based on a network capability profile associated with a network slice currently serving the UE, whether the network slice currently serving the UE supports the requested one or more network capabilities;

[0641] If the network slice currently serving the UE cannot support the requested one or more network capabilities, formulate or select a new network slice that can support the requested one or more network capabilities to serve the UE; and

[0642] A response is sent to the UE including an identifier of a network slice selected to support the requested one or more network capabilities.

[0643] 16. The method of embodiment 15, wherein the network capability profile includes one or more of the following:

[0644] The identifier of the network slice and the corresponding network slice instance;

[0645] a list of identifiers of supported network capabilities;

[0646] an identifier of the serving PLMN; and

[0647] Service area information for each network capability.

[0648] 17. The method of embodiment 15, wherein the request further comprises one or more of the following:

[0649] an identifier of each of the one or more network capabilities requested;

[0650] Network slice selection information and / or one or more network slice IDs for supporting the requested one or more network capabilities; and

[0651] An identifier of each of one or more applications hosted on the user device that requires the requested network capability.

[0652] 18. The method as described in Example 15 also includes initiating a new network slice.

[0653] 19. The method as described in Example 15 also includes selecting a new core network entity that terminates non-access stratum (NAS) signaling with the UE to serve the newly selected network slice.

[0654] 20. The method as described in Example 15 also includes updating the network capability profile associated with the newly selected network slice.

[0655] 21. A device comprising a processor and a memory, the memory storing computer executable instructions, which when executed by the processor cause the device to perform operations comprising:

[0656] receiving a message from an access and mobility management function (AMF) of a network slice in a core network of the communications network, wherein the message comprises a request to determine whether a threshold is met; and

[0657] A response to the message is sent to the AMF.

[0658] 22. A device as described in Example 21, wherein the device may have subscribed to access and mobility management functions in the network slice, so that when a user device requests to register with the slice or attempts to establish a PDU session with the network slice, the device can receive a notification.

[0659] 23. An apparatus as described in Example 21, wherein the request includes a network slice identifier and a user equipment identifier.

[0660] 24. An apparatus as described in Example 21, wherein the apparatus employs a counter that increments or decrements for each user device that registers or deregisters with a network slice of a core network.

[0661] 25. A device as described in Example 21, wherein the device uses a counter that increments or decrements for each PDU session established or terminated between the user equipment and a network slice of the core network.

[0662] 26. An apparatus as described in Example 21, wherein the response to the AMF includes a notification indicating that the network slice has reached its threshold.

[0663] 27. An apparatus as described in Example 21, wherein the response to the access and mobility management function includes a waiting timer, wherein the waiting timer indicates how long the user equipment should wait before retrying to register with the network slice or retrying to establish a PDU session with the network slice when the threshold is reached.

[0664] The description of the various aspects described herein is intended to provide a general understanding of the structure, function and operation of various aspects. The description is not intended to be used as a complete description of all elements and features of the equipment and system utilizing the structure or method described herein. For those skilled in the art, many other aspects may be clear after reading the disclosure. Other aspects can be utilized and derived from the disclosure so that structural and logical replacements and changes can be made without departing from the scope of the disclosure. Therefore, the disclosure and the accompanying drawings should be considered to be illustrative rather than restrictive.

[0665] The description of these aspects is provided to enable the manufacture or use of these aspects. Various modifications to these aspects will be clear, and the general principles defined here can be applied to other aspects without departing from the scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the aspects shown here, but to conform to the possible widest scope consistent with the principles and novel features defined by the appended claims.

Claims

1. A device for implementing a first network function, the device comprising a processor and a memory, the memory storing instructions, the instructions when executed by the processor causing the device to perform a plurality of operations including the following: receiving, by a first network function, a first message from a wireless transmit / receive unit WTRU, wherein the first message indicates a request for an operation to be performed by a network slice, and wherein the operation comprises slice registration; sending, by the first network function, a second message to the second network function, wherein the second message indicates a request for a determination whether a threshold related to the operation is met, wherein the threshold is associated with a maximum number of WTRUs that can register with the network slice; receiving, by the first network function, a first response from the second network function, the first response indicating a determination of whether a threshold is satisfied; as well as sending, by the first network function, a second response to the WTRU, the second response including an indication of whether the operation is allowed; Wherein, when the operation is not allowed, the second response includes an indication that the operation is rejected because the network slice has reached a maximum number of registered WTRUs; The second response includes a maximum number of rejection reasons directed to the WTRU.

2. The apparatus according to claim 1, wherein the first network function comprises an access and mobility management function (AMF).

3. The apparatus according to claim 1, wherein the second network function comprises a network capability management function NCMF.

4. The apparatus of claim 1 , wherein the second response includes an indication of an amount of time the WTRU will wait before sending another message indicating a request for an action to be performed.

5. The apparatus of claim 1 , wherein the instructions further cause the apparatus to send a non-access stratum (NAS) message to the WTRU, the NAS message including an indication that the WTRU is capable of sending other messages indicating a request for an operation to be performed.

6. A wireless transmit / receive unit WTRU, the WTRU comprising a processor and a memory, the memory storing instructions, the instructions when executed by the processor causing the WTRU to perform a plurality of operations including: sending a first message to a network function, the first message indicating a request for an operation to be performed by a network slice, wherein the operation comprises slice registration; and receiving a response from the network function, the response comprising an indication that the operation is rejected because the network slice has reached a maximum number of registered WTRUs; in, The response includes the maximum number of reject causes directed to the WTRU.

7. The WTRU according to claim 6, wherein the network functions include an access and mobility management function (AMF).

8. The WTRU of claim 6, wherein the response further includes an indication of an amount of time the WTRU will wait before sending another message indicating a request for an action to be performed.

9. The WTRU of claim 8, wherein the instructions further cause the WTRU to send a further message indicating a request for an action to be performed after the amount of time has expired.

10. The WTRU of claim 6, wherein the instruction further causes the WTRU to terminate slice registration based on the response.

11. The WTRU of claim 6, wherein the instructions further cause the WTRU to: receiving a non-access stratum (NAS) message from the network function, the NAS message including an indication that the operation can be requested again; and In response to the NAS message, a further message is sent indicating a request for the operation to be performed.