Monitoring the Attributes of Network Slices

Abstract

Devices, methods, and systems are disclosed for monitoring slice attributes. A device (1000) includes a processor (1005) that determines (1105) data for collecting slice attributes for a network slice. Here, the slice attributes are the number of UEs using the network slice and / or the number of data sessions using the network slice. The processor (1005) requests (1110) a first collection network function to report first usage data (e.g., roaming UE usage) for the network slice according to the slice attributes and requests (1115) a second collection network function to report second usage data (e.g., non-roaming usage) for the network slice according to the slice attributes. The processor (1005) determines (1120) whether a quota associated with the slice attributes is reached. The device (1000) includes a transceiver (1025) that sends (1125) a notification to the network function in response to the quota being met.

Description

Technical Field

[0001] The subject matter disclosed herein generally relates to wireless communications, and more particularly to monitoring slice attributes of network slices. Background Art

[0002] The following abbreviations and acronyms are defined hereinbelow and at least some of them are referred to in the following description.

[0003] 3rd Generation Partnership Project (“3GPP”), 5th Generation Core (“5GC”), Access and Mobility Management Function (“AMF”), Access Point Name (“APN”), Access Stratum (“AS”), Application Programming Interface (“API”), Data Network Name (“DNN”), Downlink (“DL”), Enhanced Mobile Broadband (“eMBB”), evolved Node B (“eNB”), Evolved Packet Core (“EPC”), Evolved UMTS Terrestrial Radio Access Network (“E-UTRAN”), Home Subscriber Server (“HSS”), IP Multimedia Subsystem (“IMS”, also known as “IP Multimedia Core Network Subsystem”), Internet Protocol (“IP”), Long Term Evolution (“LTE”), LTE-Advanced (“LTE-A”), Media Access Control (“MAC”), Mobile Network Operator (“MNO”), Mobility Management Entity (“MME”), Non-Access Stratum (“NAS”), Narrowband (“NB”), Network Function (“NF”), Network Access Identifier (“NAI”), Next Generation (e.g., 5G) Node B (“gNB”), Next Generation Radio Access Network (“NG-RAN”), New Radio (“NR”), Operations, Administration and Maintenance (“OAM”), Policy Control Function (“PCF”), Packet Data Network (“PDN”), Packet Data Unit (“PDU”), PDN Gateway (“PGW”), Public Land Mobile Network (“PLMN”), Quality of Service (“QoS”), Radio Access Network (“RAN”), Radio Access Technology (“RAT”), Radio Resource Control (“RRC”), Receive (“Rx”), Single Network Slice Selection Assistance Information (“S-NSSAI”), Serving Gateway (“SGW”), Session Management Function (“SMF”), Tracking Area Identifier (“TAI”), Transmission Control Protocol (“TCP”), Transmit (“Tx”), Unified Data Management (“UDM”), User Equipment / Terminal (mobile terminal) (“UE”), Uplink (“UL”), User Plane (“UP”), Universal Mobile Telecommunications System (“UMTS”), User Datagram Protocol (“UDP”), Wireless Local Area Network (“WLAN”), and Worldwide Interoperability for Microwave Access (“WiMAX”).

[0004] In some mobile communication networks, a network slice customer can negotiate (or request) slice characteristics (or attributes) with the network operator that deploys the network slice. Possible network slice attributes are described in the GSMA 5GJA working group in the document GSMA 5GJA NG.116 "Generic Network Slice Template". The network operator uses the Generic Network Slice Template (GST) to derive network slice characteristics. Summary of the Invention

[0005] Methods for monitoring slice attributes are disclosed. Devices and systems also perform the functions of these methods.

[0006] A method for a NWDAF to monitor slice attributes includes determining to collect data on slice attributes for a network slice. Here, the slice attributes are the number of user terminal devices using the network slice and / or the number of data sessions using the network slice. The method includes: requesting a first collection network function to report first usage data for the network slice according to the slice attributes, and requesting a second collection network function to report second usage data for the network slice according to the slice attributes. Here, the first usage data indicates the number of roaming user terminal devices using the network slice and / or the number of data sessions of the roaming user terminal devices using the network slice, while the second usage data indicates the number of non-roaming user terminal devices using the network slice and / or the number of data sessions of the non-roaming user terminal devices using the network slice. The method includes using the first usage data and the second usage data to determine whether a quota associated with the slice attributes is reached and notifying a network function in response to the quota being met, where the network function enforces a coercive measure.

[0007] A method for a UDM to monitor slice attributes includes receiving a configuration for monitoring slice attributes of a network slice. Here, the slice attributes include the number of user terminal devices using the network slice and / or the number of data sessions using the network slice. The method includes determining usage data for roaming user terminal devices using the network slice according to the slice attributes. Here, the usage data includes the number of roaming user terminal devices using the network slice and / or the number of data sessions of the roaming user terminal devices using the network slice. The method includes reporting the usage data for roaming user terminal devices using the network slice to the NWDAF. Brief Description of the Drawings

[0008] A more specific description of the embodiments briefly described above will be presented by reference to specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings only depict some embodiments and should not be considered as limiting the scope. The embodiments will be described and explained with additional specificity and detail by using the drawings, in which:

[0009] Figure 1FIG. is an illustration of an embodiment of a wireless communication system for monitoring slice attributes;

[0010] Figure 2 FIG. is an illustration of an embodiment of a network deployment for monitoring slice attributes;

[0011] Figure 3A FIG. is a signal flow diagram of an embodiment of a process for collecting global data on network slice attributes;

[0012] Figure 3B is Figure 3A a continuation of the process depicted in;

[0013] Figure 3C is Figures 3A to 3B a continuation of the process depicted in;

[0014] Figure 4A FIG. is a signal flow diagram of an embodiment of a process for collecting data from a UE;

[0015] Figure 4B is Figure 4A a continuation of the process depicted in;

[0016] Figure 5A FIG. is a signal flow diagram of an embodiment of a process for determining enforcement actions when an attribute quota is reached;

[0017] Figure 5B is Figure 5A a continuation of the process depicted in;

[0018] Figure 5C is Figures 5A to 5B a continuation of the process depicted in;

[0019] Figure 6 FIG. is a signal flow diagram of an embodiment of a process for applying adaptive charging to an S-NSSAI depending on UE or PDU session quotas;

[0020] Figure 7A FIG. is a signal flow diagram of an embodiment of a process for registering a roaming UE subscribed to a specific S-NSSAI;

[0021] Figure 7B is Figure 3A a continuation of the process depicted in;

[0022] Figure 8 FIG. is a signal flow diagram of an embodiment of a process for updating a UE when an S-NSSAI becomes available again;

[0023] Figure 9 FIG. is a block diagram of an embodiment of a user terminal device;

[0024] Figure 10 is a block diagram of an embodiment of an illustrated network terminal device;

[0025] Figure 11 is a flowchart of an embodiment of a method for monitoring slice attributes; and

[0026] Figure 12 is a flowchart of another embodiment of a method for monitoring slice attributes. Detailed Description

[0027] As will be understood by those skilled in the art, aspects of the embodiments can be embodied as a system, apparatus, method, or program product. Accordingly, the embodiments can take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects.

[0028] For example, the disclosed embodiments can be implemented as hardware circuits including custom very large scale integrated ("VLSI") circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments can also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed embodiments can include one or more physical or logical blocks of executable code, which can be organized, for example, as objects, procedures, or functions.

[0029] In addition, the embodiments can take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code hereinafter referred to as code. The storage device can be tangible, non-transitory, and / or non-transmissive. The storage device may not embody a signal. In certain embodiments, the storage device only takes a signal for accessing the code.

[0030] Any combination of one or more computer-readable media can be utilized. The computer-readable media can be a computer-readable storage medium. The computer-readable storage medium can be a storage device storing the code. The storage device can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micro-mechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0031] More specific examples (a non-exhaustive list) of storage devices will include the following: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or flash memory), portable compact disc read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0032] References throughout this specification to “one embodiment,” “an embodiment,” or similar language mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, unless expressly stated otherwise, the appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but rather mean “one or more but not all embodiments.” Unless expressly stated otherwise, the terms “comprises,” “comprising,” “has,” and variations thereof mean “including but not limited to.” Unless expressly stated otherwise, a list of enumerated items does not imply that any or all of the items are mutually exclusive. Unless expressly stated otherwise, the terms “a,” “an,” and “the” also refer to “one or more.”

[0033] As used herein, a list with a conjunction of “and / or” includes any single item in the list or a combination of items in the list. For example, the list of A, B, and / or C includes only A, only B, only C, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B, and C. As used herein, a list using the term “one or more of” includes any single item in the list or a combination of items in the list. For example, one or more of A, B, and C includes only A, only B, only C, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B, and C. As used herein, a list using the term “one of” includes one and only one of any single item in the list. For example, “one of A, B, and C” includes only A, only B, or only C and excludes the combination of A, B, and C. As used herein, “a member selected from the group consisting of A, B, and C” includes one and only one of A, B, or C and excludes the combination of A, B, and C. As used herein, “a member selected from the group consisting of A, B, and C and combinations thereof” includes only A, only B, only C, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B, and C.

[0034] In addition, the features, structures, or characteristics of the described embodiments can be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. However, those skilled in the relevant art will recognize that the embodiments can be practiced without one or more of the specific details or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the embodiments.

[0035] Aspects of the embodiments are described below with reference to the schematic flowcharts and / or schematic block diagrams of methods, apparatuses, systems, and program products according to the embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing device create means for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0036] The code can also be stored in a storage device that can direct a computer, other programmable data processing device, or other device to operate in a specific manner, such that the instructions stored in the storage device produce an article of manufacture including instructions that implement the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0037] The code can also be loaded onto a computer, other programmable data processing device, or other device so that a series of operational steps are performed on the computer, other programmable device, or other device, thereby generating a computer-implemented process, such that the code executed on the computer or other programmable device provides a process for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0038] The schematic flowcharts and / or schematic block diagrams in the drawings illustrate the architecture, functions, and operations of possible implementations of apparatuses, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flowcharts and / or schematic block diagrams can represent a module, segment, or portion of code that includes one or more executable instructions for implementing the specified logical function.

[0039] It should also be noted that in some alternative embodiments, the functions indicated in the blocks may not occur in the order indicated in the figures. For example, two blocks shown in succession may in fact be executed substantially simultaneously, or these blocks may sometimes be executed in the reverse order, depending on the functionality involved. Other steps and methods can be envisioned that are equivalent in function, logic, or effect to one or more blocks or portions thereof of the illustrated figures.

[0040] The description of the elements in each figure may refer to the elements of the figure in progress. In all the figures, like reference numerals refer to like elements, including alternative embodiments of the same element.

[0041] Methods, apparatuses, and systems for monitoring slice attributes are disclosed, such as monitoring the number of users (e.g., UEs) using a network slice and / or monitoring the number of data connections (e.g., PDU sessions) using a network slice. A mobile communication network may deploy a network data analytics function (“NWDAF”) that derives analytics based on information collected by other NFs. The NWDAF is used for data collection and data analytics in a centralized manner and can be used for analytics deployed for one or more network slices.

[0042] As discussed above, a network slice customer can negotiate (or request) slice characteristics (or attributes) with the network operator (e.g., 5GS) that deploys the network slice. However, it has not been defined how to monitor the current global number of UEs or PDU sessions using a specific network slice. Here, “global” means considering all UEs using the network slice, where the UEs can be registered in the H-PLMN and any V-PLMN in which the network slice service is provided. Additionally, it has not been defined how to enforce different measures when the quota of the maximum number of UEs or PDU sessions per network slice is reached.

[0043] One attribute in the GST is the “number of terminals”, which describes the maximum number of terminals that can use the network slice simultaneously. This is an important input for scaling the network slice and providing sufficient resources to the network slice. Assume that the GST “number of UEs per network slice” maps to the number of UEs registered to the S-NSSAI, i.e., the “network slice” from the GST template maps to the S-NSSAI used in the 3GPP specification.

[0044] Another attribute in the GST is the “number of connections”, which describes the maximum number of concurrent sessions supported by the network slice. This is also an important input for scaling the network slice and providing sufficient resources to the network slice. There is a significant difference if the network slice is used to serve 10 users or 1,000,000 users simultaneously. Assume that the number of “connections” starting from the GST template can be mapped to the PDU sessions known from the 3GPP specification.

[0045] It is assumed that one or more UDMs can exist that serve UEs in a PLMN, and more specifically, UEs that subscribe to network slices. This is possible in cases where the network operator deploys several UDM instances (e.g., organized in a UDM set) to serve subscribers to allow for load sharing. For example, a range of subscriber IDs (referred to as SUPI) can be served by one UDM, while another range of subscriber IDs can be served by another UDM.

[0046] To address the above problems, the present disclosure describes an NWDAF that collects information / data regarding at least one quota for a network slice (e.g., the number of UEs using the network slice or the number of PDU sessions established towards the network slice, etc.). The "number of UEs" means the 3GPP network slice attribute that maps to the GST attribute "number of terminals". The "number of PDU sessions" means the 3GPP network slice attribute that maps to the GST attribute "number of connections". In this document, the notation "number of [UE or PDU session]" (alternatively, [UE or PDU session]) is used to denote a parameter that means either one or the other or both of the parameters UE and PDU session. Based on the collected data, the NWDAF provides an analysis related to monitoring network slice attributes based on a Generalized Network Slice Template (GST). The NWDAF can (1) collect data from the serving UDM, or (2) collect data from the serving AMF in the HPLMN (serving the network slice) and from the UDM for roaming UEs, or (3) collect data from the NSSF for both roaming and non-roaming UEs.

[0047] It is also assumed that the AMF can collect information on the number of UEs for network slice attributes 1) per S-NSSAI and 2) the number of PDU sessions per S-NSSAI. In various embodiments, the AMF can internally collect information on the number of UEs registered per S-NSSAI, e.g., S-NSSAIx, by processing the UE's mobility management context and looking for the S-NSSAIx that is part of the allowed NSSAI. In various embodiments, the AMF can internally collect information on the number of PDU sessions per S-NSSAI, e.g., S-NSSAIx, by processing the context of the UE in the AMF and looking for the established PDU sessions towards S-NSSAIx. The AMF typically stores the associated (one or more) S-NSSAIs in the "PDU session-level context" of each established PDU session. If the UE has multiple PDU sessions towards S-NSSAIx, the AMF will count all PDU sessions.

[0048] Information on 1) the number of UEs per S-NSSAI and 2) the number of PDU sessions per S-NSSAI is collected in the HPLMN, i.e., the PLMN that subscribes to network slice customers. In the case where the UE is roaming to any visited PLMN, this information is collected globally for all UEs that subscribe to, for example, a network slice mapped to S-NSSAI x.

[0049] It is possible to maintain a quota for the maximum number of UEs or PDU sessions using a network slice in a business support system (BSS) in a network operator. The BSS system typically contains data on service level agreements with the network operator's customers. A quota for the maximum number of UEs or PDU sessions can also be maintained in an operations support system (OSS). Both the BSS and the OSS are able to dispose of these parameters to operations, administration, and management (OAM), which can configure the corresponding network function (NF) part of the network slice.

[0050] Figure 1 Depict a wireless communication system 100 for monitoring slice attributes according to an embodiment of the present disclosure. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, at least one base station unit 110, at least one access network ("AN") 120, and a mobile core network 130 in a PLMN. The AN 120 may consist of at least one base station unit 110. The remote unit 105 may communicate with the access network 120 using 3GPP communication links and / or non-3GPP communication links according to the radio access technology deployed by the AN 120. Although Figure 1 a specific number of remote units 105, base station units 110, AN 120, and mobile core network 130 are depicted, those skilled in the art will recognize that any number of remote units 105, base station units 110, AN 120, and mobile core network 130 may be included in the wireless communication system 100.

[0051] In one implementation, the wireless communication system 100 conforms to the 5G system specified in the 3GPP specifications. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication networks, such as LTE / EPC (referred to as 4G) or WiMAX, as well as other networks. The present disclosure is not intended to be limited to the implementation of any specific wireless communication system architecture or protocol.

[0052] In one embodiment, the remote unit 105 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant (“PDA”), a tablet computer, a smart phone, a smart TV (e.g., a TV connected to the Internet), a smart appliance (e.g., an appliance connected to the Internet), a set-top box, a gaming console, a security system (including security cameras), an in-vehicle computer, a network device (e.g., a router, a switch, a modem), etc. In some embodiments, the remote unit 105 includes a wearable device such as a smart watch, a fitness band, an optical head-mounted display, etc. Additionally, the remote unit 105 may be referred to as a UE, a subscriber unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a subscriber station, a user terminal, a wireless transmit / receive unit (“WTRU”), a device, or other terms used in the art.

[0053] The remote unit 105 may communicate directly with one or more of the base station units 110 in the access network 120 via uplink (“UL”) and downlink (“DL”) communication signals. Additionally, the UL and DL communication signals may be carried on the communication link 115. Note that the access network 120 is an intermediate network that provides the remote unit 105 with access to the mobile core network 130.

[0054] In some embodiments, the remote unit 105 communicates with an application function (“AF”) 151 (or other communication peer) via a network connection to the mobile core network 130. For example, an application (e.g., a web browser, a media client, a phone / VoIP application) in the remote unit 105 may trigger the remote unit 105 to use the access network 120 to establish a PDU session (or other data connection) with the mobile core network 130. The mobile core network 130 then uses the PDU session to relay traffic between the remote unit 105 and the AF 151 (e.g., in the data network 150). Note that the remote unit 105 may establish one or more PDU sessions (or other data connections) with the mobile core network 130. Thus, the remote unit 105 may have at least one PDU session for communicating with the data network 150. The remote unit 105 may establish additional PDU sessions for communicating with other data networks and / or other communication peers.

[0055] The base station unit 110 can be distributed over a geographical area. In some embodiments, the base station unit 110 may also be referred to as an access terminal, an access point, a base, a base station, a Node B, an eNB, a gNB, a home Node B, a relay node, a device, or any other term used in the art. The base station unit 110 is typically part of a radio access network (“RAN”) such as the access network 120, which may include one or more controllers communicatively coupled to one or more corresponding base station units 110. These and other elements of the radio access network are not illustrated but are generally well known to those of ordinary skill in the art. The base station unit 110 is connected to the mobile core network 130 via the access network 120.

[0056] The base station unit 110 can serve multiple remote units 105 within a service area such as a cell or a cell sector via a communication link 115. The base station unit 110 can communicate directly with one or more of the remote units 105 via communication signals. Generally, the base station unit 110 transmits DL communication signals to serve the remote units 105 in the time domain, the frequency domain, and / or the spatial domain. Additionally, the DL communication signals can be carried on the communication link 115. The communication link 115 can be any suitable carrier in the licensed or unlicensed radio spectrum. The communication link 115 facilitates communication between one or more of the remote units 105 and / or one or more of the base station units 110.

[0057] In one embodiment, the mobile core network 130 is a 5G Core (“5GC”) or an Evolved Packet Core (“EPC”), which can be coupled to a data network (e.g., the data network 150, such as the Internet and private data networks, and other data networks). The remote unit 105 can have a subscription or other account with respect to the mobile core network 130. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0058] The mobile core network 130 includes several network functions (“NFs”). As depicted, the mobile core network 130 includes at least one user plane function (“UPF”) 131 that serves the access network 120. The mobile core network 130 also includes multiple control plane functions, which include but are not limited to an access and mobility management function (“AMF”) 132, a session management function (“SMF”) 133, a policy control function (“PCF”) 134, a network exposure function (“NEF”) 136, a network repository function (“NRF”) 137 (used by various NFs to discover and communicate with each other via APIs), and a unified data management function (“UDM”) 139. In some embodiments, the mobile core network 130 may also include an authentication server function (“AUSF”) or other NFs defined for the 5GC.

[0059] The mobile core network 140 also includes an NWDAF 135 and an OAM / CHF function 138. The NWDAF 135 acts as a central data store for collecting data required for derived analysis from network functions. The OAM / CHF 138 represents an OAM and / or charging function. The network function that collects charging information in 5GS is referred to as a charging function ("CHF"). Here, the CHF is aware of the quota for [UE or PDU session] to which different charging tariffs are applied. The CHF can be configured with various quotas for the number of [UE or PDU session] for S-NSSAIx. The CHF can request data analysis on the quota for the number of [UE or PDU session] for S-NSSAIx. The CHF can enforce different charging policies depending on exceeding various quotas for the number of [UE or PDU session] for S-NSSAIx. Although the OAM / CHF is described as a combined element, in other embodiments, the OAM and CHF can be implemented separately.

[0060] In various embodiments, the mobile core network 130 supports different types of mobile data connections and different types of network slices, where each mobile data connection utilizes a specific network slice. Each network slice includes a set of CP and UP network functions, where each network slice is optimized for a specific type of service or traffic class. For ease of illustration, the different network slices are not shown in Figure 1 but their support is assumed. In one example, each network slice includes an SMF and a UPF, but the individual network slices share the AMF 143, PCF 147, and UDM 139. In another example, each network slice includes an AMF, an SMF, and a UPF. Although a specific number and type of network functions are depicted in Figure 1 those skilled in the art will recognize that any number and type of network functions can be included in the mobile core network 130.

[0061] The network slice (represented by S-NSSAIx) is configured to monitor the quota for the number of remote units 105 (e.g., UEs) or the number of PDU sessions using the network slice. This configuration can be maintained in the UDM / UDR 139 (and it can be configured by a network operator, for example, using the OAM / CHF 138); in the AMF 132 (similar to being able to be configured via the OAM 138 in the UDM / UDR 139); and / or can be requested by the AF 151 via the NEF 136.

[0062] Figure 2Depict a network deployment 200 for monitoring slice attributes according to an embodiment of the present disclosure. The network deployment 200 includes an NWDAF 201 and various nodes it can use to collect and / or report data. The NWDAF 201 is an embodiment of the NWDAF 135. In various embodiments, the NWDAF 201 receives data regarding both roaming UEs 203 and non-roaming UEs 205. Thus, the NWDAF 201 can request all AMFs in the home PLMN (referred to as "hAMF" 209) to report data regarding specific network slice attributes (e.g., the number of non-roaming UEs 205 using the network slice and / or the number of PDU sessions of non-roaming UEs using the network slice). Via the UDM 211, the NWDAF 201 can receive data for roaming UEs 203 whose subscription data includes a specific network slice from AMFs in the visited PLMN (referred to as "vAMF" 207).

[0063] The NWDAF 201 can also establish connections with the NRF 213, NEF / AF 215, the PCF in the home PLMN ("hPCF") 217, the CHF 221, and / or the NSSF 219 to collect data, report analytics, trigger enforcement actions, and / or report data, as further described in detail below.

[0064] In some embodiments, the UDM 211 can request the NWDAF for data analysis regarding network slice attributes (e.g., the number of UEs or PDU sessions for an S-NSSAIx), provided that certain UE quotas (e.g., quota-U) are included in the request. In some embodiments, the UDM 211 requests the AMF (e.g., the vAMF 207 in the V-PLMN) to report the current number of [UEs or PDU sessions] using the S-NSSAIx. Upon receiving the data analysis (e.g., reaching the quota) from the NWDAF, the UDM 211 notifies the AMF (e.g., the vAMF) of the measures to be taken (e.g., not allowing new [UEs or PDU sessions] to use the S-NSSAIx). In certain embodiments, the UDM 211 monitors the global usage of the quota for the number of [UEs or PDU sessions] for an S-NSSAI. Here, if the network operator configures a single UDM 211 to serve all subscribers of an S-NSSA, the UDM 211 internally monitors the global usage of the quota for the number of [UEs or PDU sessions] for the network slice (i.e., the S-NSSAI).

[0065] In some embodiments, the NWDAF 201 is capable of providing data analysis on whether at least one quota of the maximum number of [UE or PDU sessions] for an S-NSSAI (S-NSSAIx) has been reached. In various embodiments, the NWDAF 201 collects data from the serving AMF in the H-PLMN to report the number of [UE or PDU sessions] in the HPLMN and collects data from the serving UDM to report the number of [UE or PDU sessions] in the VPLMN. When at least one analysis event (e.g., reaching at least one quota - A / U / F) is triggered, the NWDAF notifies the corresponding NF, as described in more detail below.

[0066] In some embodiments, the NSSF 219 is capable of reporting data for analysis to the NWDAF. The NSSF can collect information from the AMF about UEs currently using S-NSSAIx or about currently established PDU sessions towards S-NSSAIx.

[0067] In some embodiments, the CHF 221 is capable of requesting the NWDAF 201 to provide data analysis on one or more network slice attributes. For example, the data analysis is intended to monitor whether a certain quota of (one or more) network slice attributes has been reached. The CHF 221 can be configured with the quota of (one or more) network slice attributes via OAM or other means.

[0068] In some embodiments, the PCF 217 (e.g., the PCF for the home PLMN "hPCF") is capable of requesting the NWDAF 201 to provide data analysis on one or more network slice attributes. For example, the data analysis is intended to monitor whether a certain quota of (one or more) network slice attributes has been reached. The PCF 217 can be configured with 1) the quota of (one or more) network slice attributes and 2) the measures to be taken when the quota is reached via OAM or other means. Note that having the PCF 217 configured with mandatory measures to be taken when the quota is reached is Figure 5B an alternative to the embodiment described in (e.g., at step 10), where the measure ID is sent from the AF / NEF. The network operator may be able to configure the measures to be taken when the quota is exceeded by itself, and thus, the network operator does not rely on the measures indicated by an application (e.g., AF). In this case, the network operator configures the NF (here, hPCF) with one or more quotas of network slice attributes and the corresponding measures to be taken when the (one or more) quotas are exceeded. For example, the measures enforced by the hPCF on a specific network slice can be (1) changing the PCC rules to be applied to the already established PDU sessions (e.g., reducing / decreasing (one or more) QoS parameters to allow serving new PDU sessions) or (2) the hPCF can enforce the rejection of new [UE, PDU sessions].

[0069] Figures 3A to 3C Depicts process 300 for collecting global data on network slice attributes according to an embodiment of the present disclosure. Process 300 involves NWDAF 201, one or more UDMs 211, one or more hAMFs 209, NRF 213, NEF / AF 215, vAMF 207, roaming UE 203, and non-roaming UE 205. Note that the NEF / AF 215 element represents AF (e.g., AF 151) and NEF (e.g., NEF 136). The AF acts as a source or receiver of signaling, and the NEF relays and maps (or transforms) such signaling from / to the AF to / from an internal 5GC service request. For example, the NEF is capable of mapping identities and parameters from / to the AF to another identity and parameter of a 5GC network function (NF).

[0070] One principle is that global information on the number of UEs using S-NSSAIx or the number of PDU sessions is collected in the NWDAF 201. The serving UDM 211 collects information / data for the roaming UE 203, and the serving AMF (hAMF 209) in the H-PLMN collects information for the non-roaming UE 205. The serving UDM 211 and the serving hAMF 209 report the collected information to the NWDAF 201.

[0071] Process 300 begins at step 0, where the serving UDM 211, the serving hAMF 209, and the NEF / AF 215 are configured to monitor quotas on the number of UEs using the network slice and / or the number of PDU sessions. Here, different NFs are configured with different quotas. At step 0a, the UDM 211 is configured with a quota "UE quota-U" for S-NSSAIx (see box 301). In some embodiments, the UDM 211 is also configured with a mandatory measure to be executed when the UE quota-U is met (e.g., not allowing the roaming UE 203 to use S-NSSAIx). At step 0b, the hAMF 209 is configured with a quota "UE quota-A" for S-NSSAIx (see box 303). In some embodiments, the hAMF 209 is also configured with a mandatory measure to be implemented when the UE quota-A is met (e.g., not allowing the non-roaming UE 205 to use S-NSSAIx). At step 0c, the NEF / AF 215 is configured with a quota "UE quota-F" for S-NSSAIx (see box 305). Optionally, the NEF / AF 215 may be configured with multiple quotas, such as UE quota-U, UE quota-A, and UE quota-F.

[0072] At step 1a, the NEF / AF 215 may request the NWDAF 201 to provide data analysis related to S-NSSAIx (see messaging 307). The NEF / AF 215 selects and discovers the NWDAF 201, which is capable of collecting data analysis for network slice attributes according to GST parameters (e.g., quotas of UEs or PDU sessions using S-NSSAIx). The NWDAF 201 may confirm a successful subscription for the data analysis to the NEF / AF 215. At step 1b, the UDM 211 may request the NWDAF 201 to provide data analysis for (one or more) network slice attributes related to S-NSSAIx (see messaging 309). The UDM 211 selects and discovers the NWDAF 201, which is capable of collecting data analysis for network slice attributes according to GST parameters (e.g., quotas of UEs or PDU sessions using S-NSSAIx). The NWDAF 201 may confirm a successful subscription for the data analysis to the UDM 211. At step 1c, the hAMF 209 may request the NWDAF 201 to provide data analysis related to S-NSSAIx (see messaging 311). The hAMF 209 selects and discovers the NWDAF 201, which is capable of collecting data analysis for network slice attributes according to GST parameters (e.g., quotas of UEs or PDU sessions using S-NSSAIx). The NWDAF 201 may confirm a successful subscription for the data analysis to the hAMF 209.

[0073] If there are multiple instances of the NWDAF in a PLMN, the network operator ensures that all UDMs, AMFs, or NEFs select the same NWDAF instance capable of performing the corresponding analysis, e.g., by requesting the NRF 213 or via taking into account the ability of the NWDAF 201 to collect S-NSSAI-related quotas. If the NWDAF discovery is via the NRF 213, the requesting NF (e.g., UDM, AMF, NEF, PCF, CHF, etc.) can use new parameters in the request to the NRF 213, where the new parameters indicate at least one of the following: (1) a feature ID supported by the NWDAF (e.g., a feature ID meaning to collect data analysis for GST parameters) or (2) specific network slice attributes for data analysis (e.g., quotas of UEs or PDU sessions). The NRF 213 is capable of processing such new parameters and can discover a certain NWDAF instance capable of serving the specific data analysis.

[0074] Multiple different quotas (i.e., thresholds or limits) for the number of UEs or PDU sessions that can be configured in the NF (or requested by the AF) for using S-NSSAIx: for example, quota-F when different charging rules can apply, quota-U when the UDM can start rejecting new roaming UEs from using S-NSSAIx, and quota-A when the AMF can start rejecting new roaming UEs from using S-NSSAIx. Each quota can be associated with a measure, e.g., when the quota-A is reached, the AMF will not allow new UEs to register to S-NSSAIx.

[0075] In step 1a, 1b, or 1c, the source NF (e.g., NEF / AF 215, UDM 21, or hAMF 209) requests the NWDAF 201 to perform data analysis on the number of [UEs or PDU sessions] using the network slice identified by S-NSSAIx. Note that the NF (e.g., AF) can request the analysis of multiple different quotas, as shown in the example using "Analysis Filter #". For example, including multiple Analysis Filter #s can indicate multiple quotas for the [UEs or PDU sessions] to be counted. Alternatively, the NF (e.g., AF) can request each quota using separate signaling, e.g., a separate Nnwdaf_AnalyticsSubscription_Subscribe request. In addition, separate analysis IDs can be used for each network slice attribute, e.g., analysis ID #V for counting the number of UEs for each S-NSSAIx and analysis ID #W for counting the number of PDU sessions for each S-NSSAIx.

[0076] In the case of AF request analysis, the AF can use an existing (or new) service operation towards the NEF, e.g., the Nnef_EventExposure_Subscribe request (request analysis ID: UE count, analysis filter 1: slice = S-NSSAIx, quota = UE quota-F) or the Nnef_AnalyticsExposure_Subscribe request (analysis ID: UE count, analysis filter 1: slice = S-NSSAIx, quota = UE quota-F). If the AF is not aware of the analysis ID and other internal 5GC parameters, the AF can also send Nnef_EventExposure_Subscribe (monitor the number of UEs for S-NSSAIx and threshold = UE quota-F), and the NEF can transform the AF request into a request for data analysis from the NWDAF. The NEF determines, based on the request received from the AF, that the NEF needs to trigger a subscription request for analysis regarding the NWDAF. The NEF transforms this information into a service operation towards the NWDAF, e.g., the Nnwdaf_AnalyticsSubscription_Subscribe request. The NEF can use the NRF to perform NWDAF discovery and selection. Recall that, for ease of illustration, Figures 3A to 3C the AF and the NEF were described as a single element in

[0077] In some embodiments, the service operation request may include an "analysis ID = "UE count"" parameter. Here, the analysis ID uses a new value ("UE count") to indicate the number of UEs and / or PDU sessions using a specific network slice to be tracked. In some embodiments, the service operation request may include an "analysis filter: slice = S-NSSAIx" parameter to indicate the specific network slice (i.e., identified by the S-NSSAI) for which the analysis should be collected. In some embodiments, the service operation request may include a "quota = UE quota-A" parameter to indicate the maximum number of UEs and / or PDU sessions allowed to use a specific network slice.

[0078] At step 2, the NWDAF 201 requests all UDMs 211 serving S-NSSAIx to report data on monitored network slice attributes (e.g., the quota of UEs or PDU sessions using S-NSSAIx). At step 2a, the NWDAF 201 can use the NRF 213 service to discover the UDMs 211 associated with S-NSSAIx (see messaging 313). At step 2b, the NWDAF 201 sends a subscription request to all discovered UDMs 211 (see messaging 315).

[0079] At step 3, the NWDAF 201 requests all AMFs (e.g., hAMF 209) serving S-NSSAIx to report data on monitored network slice attributes (e.g., quotas of UEs or PDU sessions using S-NSSAIx). At step 3a, the NWDAF 201 may use the NRF 213 service to discover the hAMF 209 associated with S-NSSAIx (see messaging 317). Here, the NWDAF 201 discovers the hAMF 209 in the PLMN (i.e., HPLMN). At step 3b, the NWDAF 201 subscribes to the discovered hAMF 209 to report the current number of [UEs or PDU sessions] (see messaging 319). In the depicted example, the NWDAF 201 is able to use the service operation Namf_EventExposure_Subscribe (event ID: number of [UEs, PDU sessions] registered to the network slice, target: any UE, slice: S-NSSAIx, reporting filter (10 changes, or 10 minutes)) to subscribe to the hAMF 209.

[0080] In other embodiments, the NWDAF 201 may be configured to collect data from the NSSF 219. In this case, the NWDAF 210 requests the NSSF 219 (i.e., the appropriate NSSF for S-NSSAIx in the HPLMN) to report the current number of [UEs or PDU sessions] using S-NSSAIx. In the NSSF-based case, the current number is the global number including roaming UEs and non-roaming UEs. The NSSF 219 in the HPLMN (i.e., hNSSF) is configured to collect information on the global number of [UEs or PDU sessions] using S-NSSAIx from a) the hAMF 209 in the HPLMN and b) the NSSF in the VPLMN where UEs using S-NSSAIx are registered. To collect information on currently established PDU sessions towards S-NSSAIx, the AMF is modified to report the number of currently established PDU sessions for S-NSSAIx to the NSSF. For example, a new (or existing) service operation between the hAMF and the hNSSF may be used, which may include a new parameter for indicating the number of PDU sessions. Thus, the hNSSF is able to collect global data and report it to the NWDAF. This alternative is discussed in more detail. Figure 6 This alternative is discussed in more detail.

[0081] In Figure 3BContinue at step 4, where the roaming UE 203 registers via the vAMF 207 (see box 321). Once the UE (preferably, the roaming UE 203 whose subscription data contains S-NSSAIx) successfully registers with the AMF (e.g., the vAMF 207 in the VPLMN), the UDM 211 requests from the AMF to collect information for certain network slice attributes (e.g., the number of UEs using the network slice or the number of PDU sessions, e.g., by using monitoring events). The UDM 211 is able to configure reporting event filters (e.g., 5 or 10 change reports; report every 10 minutes, etc.).

[0082] In the case where the roaming UE 203 is the first to use the slice identified by S-NSSAIx from the HPLMN at this vAMF 207, the UDM 211 performs step 5a to request the vAMF 207 to report data on the current number of [UE or PDU session] (see messaging 323). The vAMF 207 reports the data to the UDM 211, as shown in step 6 (see messaging 325), and the UDM 211 may decide to report the data to the NWDAF 201 (or first wait to collect more data from other vAMF 207).

[0083] The AMF (specifically the vAMF 207, but optionally the hAMF 209) may request to notify the UDM 211 when a certain quota (e.g., quota-A) is reached and which measures the AMF imposes. In step 5b, the vAMF 207 subscribes (or requests) data analysis for an event corresponding to the event from step 5a, i.e., the vAMF 207 subscribes to the UDM 211 for data analysis of the quota for [UE, PDU session] (see messaging 327).

[0084] At step 7, the non-roaming UE 205 successfully registers with the hAMF 209 and S-NSSAIx is included in the allowed NSSAI (see box 329). At step 8, the hAMF 209 may notify the NWDAF 201 of the current number of [UE, PDU session] using S-NSSAIx (see messaging 331). For example, the hAMF 209 may use the service operation Namf_EventExposure_Notify including the event ID, the target S-NSSAIx, the current number of [UE, PDU session] with the parameter "current Nr of [UE, PDU session]", where "Nr" means the current number of all [UE, PDU session] currently served by the hAMF 209. Note that the hAMF 209 may be configured to report the event immediately or may be configured to wait to collect more data before reporting, as discussed above.

[0085] Continuing at Figure 3C this point, the NWDAF 201 collects data from all UDMs 211 and hAMFs 209 serving S-NSSAIx and monitors whether the number of simultaneously registered [UE, PDU session] exceeds any of the configured quotas regarding the maximum number of [UE, PDU session] for S-NSSAIx. The "quota for the maximum number of [UE, PDU session] for S-NSSAI" is configured as described in step 1a, 1b, or 1c.

[0086] At step 9, the NWDAF 201 determines that the UE quota - F is satisfied (see box 333). At step 10, the NWDAF 201 sends a notification to the NF subscribing to the UE quota - F (see messaging 335). Here, the NWDAF 201 uses the service operation Nnwdaf_Analytics Subscription_Notify(Analytics ID, Correlation ID, S-NSSAIx, Reached [UE, PDU session] Quota - F) to notify the NEF / AF 215. Note that the service operation can include at least the following parameters: 1) the S-NSSAI to which the notification is sent, 2) "Quota Exceeded" indicating that the quota / maximum number of [UE, PDU session] for S-NSSAIx has been exceeded or is about to be exceeded.

[0087] At step 11, after notifying the AF that one or more quotas will be exceeded, the AF can determine the measures to be taken in the 5GS based on the AF configuration or implementation logic (see box 337). The AF uses the capabilities exposed via interface N33 to request the 5GS to execute the determined measures. For example, the AF can request the 5GS to restrict new [UE or PDU session] towards S-NSSAIx.

[0088] At step 12, the NWDAF 201 determines that the UE quota - U is satisfied (see box 339). At step 13, the NWDAF 201 sends a notification to the NF subscribing to the UE quota - U. At step 13a, the NWDAF 201 uses the service operation Nnwdaf_AnalyticsSubscription_Notify(Analytics ID, Correlation ID, S-NSSAIx, Reached [UE, PDU session] Quota - U) to notify the NEF / AF 215 (see messaging 341). At step 13b, the NWDAF 201 can use the same service operation to notify the UDM 211 (see messaging 343).

[0089] At step 14a, after notifying the AF that it is about to exceed (or has exceeded) one or more quotas, the AF can determine the measures to be taken in the 5GS based on the AF configuration or implementation logic (see box 345). The AF uses the capabilities exposed via interface N33 to request the 5GS to execute the determined measures. For example, the AF can request the 5GS to restrict new [UE or PDU sessions] towards S-NSSAIx. At step 14b, after notifying the UDM 211 that it is about to exceed (or has exceeded) one or more quotas, the UDM 211 signals to the subscribed vAMF 207 to indicate that the UE quota for S-NSSAIx is met and to indicate the enforcement measures to be implemented (e.g., rejecting new roaming UEs from using S-NSSAIx) (see messaging 347).

[0090] At step 15, the NWDAF 201 determines that the UE quota-A is met (see box 349). At step 16, the NWDAF 201 sends a notification to the NFs subscribed to the UE quota-A. At step 16a, the NWDAF 201 uses the service operation Nnwdaf_AnalyticsSubscription_Notify (analytics ID, correlation ID, S-NSSAIx, [UE, PDU session] quota-A reached) to notify the NEF / AF 215 (see messaging 351).

[0091] At step 17, after notifying the AF that it is about to exceed (or has exceeded) one or more quotas, the AF can determine the measures to be taken in the 5GS based on the AF configuration or implementation logic, and use the capabilities exposed via interface N33 to request the 5GS to execute the determined measures (see box 301).

[0092] At step 16b, the NWDAF 201 can use the same service operation to notify the subscribed hAMF 209 (see messaging 355). After notifying the hAMF 209 that the quota for [UE or PDU session] has been reached, the hAMF 209 can inform the UEs that request to register to S-NSSAIx during the registration process or request information about the UES-NSSAIx for the PDU session establishment process towards S-NSSAIx that it is unavailable or that the PDU session establishment is currently not possible. Process 300 ends.

[0093] Although process 300 uses the NWDAF to collect global information about the number of UEs using S-NSSAIx or the number of PDU sessions, in an alternative implementation, the global information can be collected directly in the UDM, especially in the case where the network operator deploys a single UDM serving all subscribers of S-NSSAIx. In this case, the NWDAF is not involved.

[0094] Figures 4A to 4B Depict process 400 for collecting data from a UE according to an embodiment of the present disclosure. Process 400 involves NWDAF 201, one or more UDMs 211, one or more hAMFs 209, NRF 213, NEF / AF 215, vAMF 207, roaming UE 203, and non-roaming UE 205. Process 400 represents an alternative solution for collecting data by NWDAF, where the data is collected from roaming UE 203 and non-roaming UE 205, rather than via UDM 211 and hAMF 209.

[0095] Process 400 begins with steps 0a, 0b, and 0c, where UDM 211, hAMF 209, and NEF / AF 215 are configured with UE quotas for S-NSSAIx, as described above with reference to Figure 3A (see boxes 301, 303, and 305). At steps 1a, 1b, and 1c, NEF / AF 215, UDM 211, and hAMF 209 subscribe to NWDAF 201, as described above with reference to Figure 3B (see message passing 307, 309, and 311).

[0096] Note that NWDAF 201 does not subscribe to data collection from UDM 211 and hAMF 209, as the data is collected directly from roaming UE 203 and non-roaming UE 205 (see box 405).

[0097] At step 4, roaming UE 203 successfully registers via vAMF 207 (see box 407). Here, UDM 211 instructs vAMF 207 that the number of [UE or PDU sessions] using S-NSSAIx is subject to quota restrictions. In the case where the number of UEs is the subject of the quota restriction, the registration acceptance message sent to roaming UE 203 indicates that the UE should report to the network (e.g., NWDAF 201) when S-NSSAIx is part of the allowed NSSAI or the UE should report to the network (e.g., NWDAF 201) how many PDU sessions are established towards S-NSSAIx. In the case where the number of PDU sessions is the subject of the quota restriction, vAMF 207 can indicate to roaming UE 203 in the registration acceptance message or in the NAS N1-MM message carrying the N1-SM PDU session establishment acceptance message that the UE should report to the network (e.g., NWDAF 201) the number of PDU sessions established towards S-NSSAIx. At step 5a, roaming UE 203 reports to NWDAF 201 (see message passing 409).

[0098] At step 5b, vAMF 207 subscribes to UDM 211, as described above with reference to Figure 3B (see Messaging 327). vAMF 207 subscribes if it receives an indication during registration of a roaming UE 203 that the number of [UE or PDU sessions] using S-NSSAIx is subject to a quota limit.

[0099] At step 7, non-roaming UE 205 successfully registers with hAMF 209 and S-NSSAIx is included in the allowed NSSAI (see box 411). In one embodiment, UDM 211 indicates to hAMF 209 during registration that the number of [UE or PDU sessions] using S-NSSAIx is subject to a quota limit. Alternatively, hAMF 209 may be configured (e.g., by OAM 138) to have the number of [UE or PDU sessions] using S-NSSAIx subject to a quota limit. hAMF indicates to the UE that it needs to report to the network (e.g., NWDAF) the number of [UE or PDU sessions] using S-NSSAIx. At step 8, non-roaming UE 205 notifies NWDAF 201 that S-NSSAIx is part of the allowed NSSAI and / or reports the number of PDU sessions established towards S-NSSAI (see Messaging 413).

[0100] Note that process 400 continues Figure 3C with steps 9-17 (these steps are not shown in Figure 4B ). Process 400 ends.

[0101] Figures 5A to 5C Depicts process 500 for determining enforcement actions when a quota associated with a monitored network slice attribute is reached, according to an embodiment of the present disclosure. Process 500 involves NWDAF 201, one or more UDMs 211, one or more hAMFs 209, NRF 213, NEF 501, AF 503, and hPCF 217. Process 500 shows how an application function (AF) 503 can determine actions to be taken in the network based on data analysis provided by NWDAF 201, as mentioned above with reference to Figure 3C (see). Note that Figures 5A to 5B the NEF / AF elements are depicted with their separate NEF and AF components.

[0102] Procedure 500 starts at step 0, where AF 503 is configured with a quota - W of the number of [UE or PDU sessions], at which access to the network slice identified by S - NSSAI - 1 should be restricted (see box 505). The network slice identifier "S - NSSAI - 1" is assigned by the 5GS network and sent to AF 503 via an SLA or other signaling means not described herein. Alternatively, the network (5GS) can also expose S - NSSAI - 1 to AF 503, and AF 503 can associate S - NSSAI - 1 with the service.

[0103] At step 1a, if an event of reaching a specific upper - limit number (e.g., quota - W) of [UE or PDU sessions] using network slice S - NSSAI - 1 occurs, AF 503 requests to inform the network (see messaging 507). This is similar to step 1a from Figure 3A AF 503 can use an existing (or new) service operation towards NEF 501, e.g., Nnef_EventExposure_Subscribe request (request analysis ID: UE count, analysis filter: slice = S - NSSAI - 1, quota = UE quota - W).

[0104] NEF 501 may need to query NRF 213 to discover NWDAF 201, which is responsible for performing the analysis to collect the number of [UE or PDU sessions] using the network slice. At step 1b, NEF 501 sends a request to NWDAF 201 (see messaging 509). At step 1c, NWDAF 201 responds to AF 503 regarding whether the establishment of the analysis collection was successful (see messaging 511).

[0105] At step 2, NWDAF 201 is configured on how to collect the data required to perform the analysis requested by AF 503 via NEF501 (see box 513). This is similar to steps 2a, 2b, 3a, 3b, 6, 8 from Figures 3A to 3B At step 3, NWDAF201 collects data for S - NSSAI - 1 and monitors whether the number of simultaneously registered [UE, PDU sessions] exceeds any of the configured quotas regarding the maximum number of [UE, PDU sessions] for S - NSSAI - 1, e.g., quota - W. At a certain moment, NWDAF 201 determines that the quota has been reached (see box 515).

[0106] At step 4a, NWDAF 201 sends Nnwdaf_AnalyticsSubscription_Notify (UE quota for S-NSSAI-1 reached - W) to NEF 501 (see messaging 517). At step 4b, NEF 501 forwards the notification to AF503 (see messaging 519). NEF 501 may transform the service operation into Nnef_EventExposure_Notify (UE quota for S-NSSAI-1 reached - W), however the exposure parameters may be newly defined parameters. At step 5, AF 503 determines which measure to execute based on the configuration (see box 521). For example, AF 503 may determine that access to further [UE or PDU session] towards S-NSSAI-1 should be restricted.

[0107] At step 6, AF 503 sends a request to NEF 501 to start applying a policy to restrict access to S-NSSAI-1 (see messaging 523). For example, AF 503 may use a new service operation Nnef_ApplyPolicy_Create request (AF-ID, target slice = S-NSSAI-1, policy / measure ID), where the new "policy / measure ID" should be specified to have the meaning of restricting access to further [UE or PDU session] of the network slice identified by S-NSSAI-1. At step 7, NEF 501 may need to discover the target network function (NF) to which the new policy should be applied (see messaging 525). For this purpose, NEF 501 may request NRF 213 to obtain the NF ID.

[0108] At Figure 5B Continuing at, in an alternative scenario (Alt#1), NEF 501 may be configured to apply the new policy towards UDM211. In this case, at step 8, NEF 501 sends a request to UDM / UDR to apply (or provide) a policy to restrict access of [UE or PDU session] to S-NSSAI-1 (see messaging 527). NEF 501 may use a new service operation (or reuse an existing service operation, e.g., Nudm_parameter_provision_update service operation). For example, NEF 501 may send a new service operation Nudm_PolicyProvision_Create (measure ID = restrict [UE, PDU session] for S-NSSAI-1) to create a new policy with "measure ID = restrict [UE, PDU session] for S-NSSAI-1".

[0109] At step 9, the UDM 211 enforces the start of the rejection of the [UE or PDU session] for S-NSSAI-1 at the AMF in the HPLMN (hAMF 209) and the AMF in the VPLMN (vAMF 207) (see box 529). This can be similar to steps 6b and 19 from Fehler! Verweisquelle konnte nicht gefunden werden (for roaming UEs), but similar steps can be performed between the hAMF 209 and the UDM 211.

[0110] At step 10, in the second alternative (Alt#2), the NEF 501 can be configured to apply a new policy towards the PCF in the HPLMN (hPCF 217). The NEF 501 may need to discover the hPCF 217 responsible for the policy of S-NSSAI-1. Then, the NEF 501 can send a request to the hPCF 217 to apply (or provide) a policy to restrict the access of the [UE or PDU session] to S-NSSAI-1 (see messaging 531). Again, the NEF 501 can use a new service operation (or re-use an existing service operation). For example, the NEF 501 can send a new service operation Npcf_PolicyProvision_Create (measure ID = restrict [UE, PDU session] for S-NSSAI-1), where the new policy identified by "measure ID = restrict [UE, PDU session] for S-NSSAI-1" is sent to the hPCF 217.

[0111] At step 11, hPCF 217 can enforce the rejection of [UE, PDU session] for S-NSSAI-1 in different ways (see messaging 533). Assume that hPCF 217 is the PCF for mobility management and access management (MM&AM) policies. Two options are described here: Option A) In the HPLMN, hPCF 217 is already associated with the hAMF 209 serving the UE from the S-NSSAI. hPCF 217 sends a new (or updated) MM&AM policy to all hAMF 209s. hAMF 209 starts enforcing the rejection of new [UE or PDU session] attempting to use S-NSSAI-1. Option B) In any VPLMN, hPCF 217 will be associated with the PCF in the VPLMN (i.e., vPCF) serving the UE in the VPLMN. The vPCF is able to instruct the vAMF 207 to reject requests for new [UE or PDU session] attempting to use S-NSSAI-1 (or the S-NSSAI value mapped in the VPLMN). Alternatively, to enforce the rejection of [UE, PDU session] for S-NSSAI-1, hPCF 217 can change the PCC rules to be applied to the PDU sessions already established for S-NSSAI-1. For example, hPCF 217 can determine to reduce the aggregated maximum bit rate (AMBR) for the (one or more) PDU sessions so that the network slice S-NSSAI-1 can accept and serve the (one or more) new PDU sessions. At step 12, NEF 501 responds to step 6 (see messaging 535). For example, NEF 501 confirms the successful creation of the new policy in the network.

[0112] Continuing at Figure 5C step 13, at any time, NWDAF 201 can determine that the number of [UE or PDU session] using S-NSSAI-1 falls below Quota-W (see box 537). At step 14, NWDAF 201 sends Nnwdaf_AnalyticsSubscription_Notify (underrun of UE Quota-W for S-NSSAI-1) to indicate to NEF 501 that the number of [UE or PDU session] using S-NSSAI-1 falls below Quota-W (see messaging 539). NEF 501 can map this information into appropriate information towards AF 503 (see messaging 541).

[0113] At step 15, the AF 503 may determine to stop applying the access restriction to S-NSSAI-1 based on the reports of a smaller number of [UE or PDU sessions] (see box 543). Thus, the AF 503 may also determine to perform application-level measures, for example, sending application layer signaling to the UE and reconfiguring the corresponding application in the UE. At step 16, the AF 503 sends a request to the NEF 501 to delete the policy created previously in step 6 (see messaging 545). For this purpose, the AF 503 may perform the service operation Nnef_ApplyPolicy_Delete(AF-ID, target slice = S-NSSAI-1, policy = delete).

[0114] At step 17, in the case of alternative scenario 1 (Alt#1), the NEF 501 may send a message indicating the deletion of the policy established in step 8 to the UDM 211 (see messaging 547). For example, the NEF 501 may perform the service operation Nudm_PolicyProvision_Delete(measure ID = delete). The UDM 211 then updates the corresponding AMF (hAMF 209 and vAMF 207) such that new [UE or PDU sessions] are allowed to access the S-NSSAI-1.

[0115] At step 18, in the case of alternative scenario 2 (Alt#2), the NEF 501 is able to send a message indicating the deletion of the policy established in step 10 to the hPCF 217 (see messaging 549). For example, the NEF 501 is able to perform the service operation Npcf_PolicyProvision_Delete(measure ID = delete). The hPCF 217 deletes the indicated policy in all vPCFs. The vPCF will correspondingly update the vAMF 207, which allows new [UE or PDU sessions] to access the S-NSSAI-1. Process 500 ends.

[0116] Figure 6 A process 600 for applying adaptive charging to an S-NSSAI depending on the quota of a UE or PDU session according to an embodiment of the present disclosure is depicted. Process 600 involves a CHF 601, an OAM system 603, an NWDAF 201, one or more hAMF209, one or more UDM211, and an NSSF 605. The CHF 601 may be an implementation of the CHF 221 and / or the OAM / CHF138 discussed above. The OAM system 603 may be an implementation of the OAM / CHF 138 discussed above. The NSSF 605 may be an implementation of the NSSF 219 discussed above.

[0117] Procedure 600 starts at step 0 where CHF 601 is configured with one or more quotas C1, C2 of the number of [UE or PDU sessions], and different charging tariffs are applied to S-NSSAI-1 at these quotas C1, C2 if the quotas are exceeded. There are different alternative ways of how CHF 601 can be configured.

[0118] Step 0a represents the first alternative where the OAM system 603 configures CHF 601 (statically or dynamically) with different charging quotas of [UE or PDU sessions] (see messaging 605). The charging quotas C1 or C2 can be derived from the SLA negotiated between the network operator and the network slice customer. Step 0b identifies the second alternative where CHF 601 can be configured by other means, e.g., manually configured with [UE or PDU session] quotas C1, C2 for S-NSSAI-1 (see box 607).

[0119] At step 1a, if at least one of the quotas (e.g., C1 and C2) of the number of [UE or PDU sessions] using network slice S-NSSAI-1 is reached, then CHF 601 requests to inform NWDAF 201 (see messaging 609). This is similar to step 1b or 1c from Figure 3A CHF 601 can use an existing (or new) service operation towards NWDAF 201. For example, CHF601 can send an Nnwdaf_AnalyticsSubscription_Subscribe request (Analytics ID: UE count, Analytics Filter #1: slice = S-NSSAI-1, quota = UE quota - C1, Analytics Filter #2: slice = S-NSSAI-1, quota = UE quota - C2). CHF601 may need to query NRF 213 to discover NWDAF 201 which is responsible for performing the analysis for collecting the number of [UE or PDU sessions] using network slice S-NSSAI-1. At step 1b, NWDAF 201 responds to CHF 601 whether the establishment of the analysis collection was successful (see messaging 611).

[0120] At step 2, NWDAF 201 starts collecting data from the corresponding NF (see box 613). For example, as Figure 3A described, NWDAF 201 can request UDM 211, hAMF 209 or NSSF 605 to report data on the number of [UE or PDU sessions] using network slice S-NSSAI-1.

[0121] At step 3, the NWDAF 201 determines that the quota for [UE or PDU session] has reached C1 (see box 615). At step 4, the NWDAF 201 notifies the CHF 601 that the quota C1 has been reached (see messaging 617). For example, the NWDAF 201 may perform the service operation Nnwdaf_AnalyticsSubscription_Notify (quota C1 for UE for S-NSSAI-1 reached).

[0122] At step 5, the CHF 601 adjusts the charging for S-NSSAI-1 according to the charging policy configured for quota C1 (see box 619). For example, when the quota C1 is exceeded, the CHF 601 may increase the charging by 50% from the regular charging policy.

[0123] At step 6, the NWDAF 201 continues to collect analytics data and is able to determine that the quota for [UE or PDU session] has reached C2 (see box 621). At step 7, the NWDAF 201 notifies the CHF 601 that the quota C1 has been reached (see messaging 623). For example, the NWDAF 201 is able to perform the service operation Nnwdaf_AnalyticsSubscription_Notify (quota C1 for UE for S-NSSAI-1 reached).

[0124] At step 8, the CHF 601 adjusts the charging for S-NSSAI-1 according to the charging policy configured for quota C2 (see box 625). For example, when the quota C2 is exceeded, the CHF 601 may increase the charging by 100% from the regular charging policy. Process 600 ends.

[0125] Figures 7A to 7BDescribe process 700 for registering a roaming UE for subscribing to a specific network slice "S-NSSAIx" according to an embodiment of the present disclosure. Process 700 involves roaming UE 203, vAMF 207, and vNSSF 701 in the V-PLMN, and also involves one or more UDMs 211 and NWDAF 201 in the H-PLMN. Note that the multiple UDMs shown are intended to serve different UEs. Process 700 describes collecting information on the number of UEs or the number of PDU sessions using an S-NSSAI (denoted as S-NSSAIx) for which a quota of the number of UEs or PDU sessions to be monitored should be determined. In one example, the process applies to a roaming scenario where UEs using S-NSSAIx are served by the visited PLMN (V-PLMN). The process shows how to monitor / count the number of UEs (or PDU sessions) registered for a network slice and enforce measures when the limit of the maximum number of UEs is reached. Since the process applies to monitoring both 1) the number of UEs or 2) the number of PDU sessions, it is hereinafter referred to as the number of [UE or PDU session].

[0126] Process 700 begins at step 0, where UDM 211 is configured with a network slice (i.e., S-NSSAI) for which a quota of at least 1) the maximum number of UEs registered simultaneously for the network slice or 2) the maximum number of PDU sessions established simultaneously within the network slice of the UE should be monitored (see block 705). This is a characteristic of the S-NSSAI. In one example, the operation, administration, and management (OAM) system 603 can configure UDM 211.

[0127] In addition, UDM 211 can be configured with a quota of the maximum number of (e.g., UEs or PDU sessions) allowed to use the network slice (i.e., using the S-NSSAI). This parameter can be configured based on a general network slice template (GST) negotiated during a service level agreement (SLA) between the network operator and the network slice customer.

[0128] At step 1a, UDM 211 requests an analysis for a specific S-NSSAI from NWDAF 201 (see messaging 707). For this purpose, UDM 211 subscribes to (or at some point, UDM 211 can unsubscribe from) NWDAF201 to be notified of analysis information for a specific network slice (e.g., S-NSSAIx).

[0129] In various embodiments, the UDM 211 may use a service operation Nnwdaf_AnalyticsSubscription that includes at least the following new parameters: ((one or more) analytics IDs, (one or more) analytics report parameters, analytics filter information, notification target address): [(one or more) analytics IDs, (one or more) quotas, target list].

[0130] In some embodiments, the subscription request includes one or more new analytics IDs for collecting (one or more) quotas of parameters for an S-NSSAI. For example, a new analytics ID can be 1) to collect information on the number of UEs simultaneously registered for a network slice or 2) to collect information on the number of PDU sessions simultaneously established within a network slice. In some embodiments, the subscription request includes (one or more) quotas for the maximum number of [UEs or PDU sessions] that can be registered to the S-NSSAI. The maximum number of [UEs or PDU sessions] can be configured in the UDM 211 based on GST parameters negotiated with the slice customer. In some embodiments, the subscription request includes a target list of NFs from which information can be collected, e.g., a list of AMFs in the HPLMN where UEs subscribed to the network slice are registered. For example, this can be encoded in the notification target address parameter. The NWDAF 201 may confirm a successful subscription to the UDM 211 for analytics collection.

[0131] At step 1b, the NWDAF 201 subscribes to the UDM 211 to be notified of the current number of UEs or PDU sessions using the S-NSSAI (see messaging 709). This step is performed if data collection in the NWDAF 201 is required for data analysis. The NWDAF 201 may include an event filter [granularity] parameter that indicates the frequency at which the UDM 211 is to report, e.g., periodically (e.g., every 10 minutes) after a predetermined number of changes (e.g., 10 changes) or after a predetermined amount of time. The UDM 211 may confirm a successful subscription to the NWDAF 201 for data collection.

[0132] At steps 2 to 7, the UE 203 initiates a registration procedure (see block 711). In various embodiments, the registration procedure is similar to that described in clause 4.2.2.2 of 3GPP TS 23.502 (v16.3.0), which is incorporated herein by reference. The UE 203 may include a specific S-NSSAI (e.g., S-NSSAIx) in the requested NSSAI information element (IE). At least one modification to the known registration procedure is at step 5: if the UDM 211 identifies that one or more of the S-NSSAIs subscribed for the UE 203 are objects for monitoring the maximum number of UEs using network slices simultaneously, the UDM 211 sends an appropriate indication to the vAMF 207. For example, the indication has the following meaning for the vAMF 207: for this S-NSSAIx, the number of UEs registered to the slice should be counted (or monitored), where the UDM 211 is able to include new parameters associated with the S-NSSAI (object of quota monitoring) indicating the current state of the S-NSSAI.

[0133] In some embodiments, the UDM 211 may include the status "quota reached" for the S-NSSAI for which the quota has currently been reached. This indication helps the vAMF 207 to know that this (subscribed) S-NSSAI is currently unavailable and should not be included in the allowed NSSAI sent to the UE 203 at step 7. If the status of the S-NSSAI is "quota reached", the vAMF 207 does not use this S-NSSAI in the exchange with the vNSSF 701 to determine the allowed S-NSSAI that includes the S-NSSAIs that can be in the current registration area for the UE 203.

[0134] Continue Figure 7B , at step 8a, if this is the first vAMF 207 for which the UE subscription data contains S-NSSAIx, the UDM 211 determines the current number of UEs or PDU sessions subscribed to the vAMF 207 to be notified of the use of this S-NSSAI (see block 713).

[0135] In step 8b, the UDM 211 may use, for example, the service operation Namf_EventExposure_Subscribe (event ID (NrUEsPerS-NSSAIx)…, event filter()), where the event ID means, for example, the type of quota to be monitored (UE or PDU session) (see messaging 715). Here, the Event Filter() parameter indicates the reporting frequency, e.g., to report after a predetermined number of changes (e.g., 10 changes) or periodically (e.g., every 20 minutes) after a predetermined amount of time.

[0136] In step 8c, vAMF 207 may report / notify UDM 211 of the current number of UE / PDU sessions using S-NSSAIx (see messaging 717). If the UE or a group of UEs 1) deregisters from the network slice or 2) releases one or more PDU sessions to the network slice, vAMF 207 is able to determine the change and vAMF 207 notifies the changed number to one or more UDMs 211. For example, vAMF 207 may use the service operation Namf_EventExposure_Notify(event ID(), S-NSSAIx, current Nr[UE, PDU session]).

[0137] In step 9, if this is the first UE 203 whose list of subscribed S-NSSAIs contains S-NSSAIx and vAMF207 has not subscribed to the threshold (or "quota reached") for this S-NSSAIx, then vAMF 207 requests to be notified by UDM 211 when the threshold or quota has been reached (see messaging 719). For example, vAMF 207 may perform the service operation Nudm_EventExposure_Subscribe(event ID(Threshold_S-NSSAIx)), where "Threshold_S-NSSAIx" means the threshold / quota for S-NSSAIx.

[0138] At step 10, if monitoring of the number of UEs registered to the S-NSSAI is performed at UDM 211, then UDM211 is able to internally count the number of UEs registered to S-NSSAIx (see messaging 721). UDM 211 sends a notification message to NWDAF 201 to report the current number of [UE, PDU session] using S-NSSAIx. For example, UDM 211 is able to use the existing service operation Nnwdaf_EventExposure_Notify(S-NSSAIx, actual NrUEsPerS-NSSAIx) that includes at least the following new parameters: 1) S-NSSAIx indicating which S-NSSAI is the target of the update, 2) the actual Nr UE or PDU session using S-NSSAIx. Alternatively, UDM 211 is able to use a new service operation to indicate to NWDAF 201 an increase or decrease in the number of UEs.

[0139] At step 11, the NWDAF 201 collects the actual number of UEs (or PDU sessions) from all UDMs 211 and / or hAMFs 209 and monitors whether the quota for S-NSSAIx is reached (see box 723). If the quota for S-NSSAIx is exceeded (or nearly exceeded), the NWDAF 201 notifies the (one or more) UDMs that have subscribed to the analysis according to step 1a.

[0140] At step 12, the NWDAF 201 notifies all subscribed UDMs that have subscribed to the analysis according to step 1a (see messaging 725). The notification to multiple UDMs is shown by multiple arrows in Figure 7B For example, the NWDAF 201 can use the service operation Nwdaf_AnalyticsSubscription_Notify(S-NSSAIx, status "quota exceeded"), where the parameter status "quota exceeded" means that the quota has been reached.

[0141] At step 13, if the quota for the maximum [UE, PDU session] using S-NSSAIx has been reached, the UDM 211 determines the required measures based on the configuration in the UDM 211. For example, if the quota is reached and the UDM 211 is configured to restrict further access of [UE or PDU session], the UDM 211 determines to enforce the restriction on access to S-NSSAIx. The UDM 211 notifies all vAMFs 207 that have subscribed to the notification according to step 10 (see messaging 727). For example, the existing (or new) service operation Nudm_EventExposure_Notify(S-NSSAIx, status "quota exceeded", measure ID) can be used. Alternatively, the UDM 211 can use a new service operation. The "measure ID" indicates to the vAMF 207 how to handle (1) an additional UE attempting to register with S-NSSAIx or (2) a UE attempting to establish a PDU session towards S-NSSAIx.

[0142] For example, the "measure ID" can indicate at least one of the following: (1) only "gold" subscribers can be allowed to successfully use S-NSSAIx, that is, register with S-NSSAIx or establish a PDU session towards S-NSSAIx; for non-gold subscribers, requests for registration with S-NSSAIx or establishment of a PDU session to S-NSSAIx are rejected with an appropriate cause value; or (2) requests from all UEs are rejected with an appropriate cause value.

[0143] At step 14, vAMF 207 restricts the use of S-NSSAIx according to the indication(s) in step 13 (e.g., according to the "Measure ID" instruction) (see box 729). If the exceeded quota is the maximum number of UEs per network slice, vAMF 207 considers the corresponding S-NSSAIx unavailable for new UE registration. vAMF 207 does not consider S-NSSAIx when determining the registration area (e.g., TAI list), and when S-NSSAI is included in the list of rejected S-NSSAIs, vAMF 207 may include S-NSSAIx with an appropriate rejection reason value in the list of rejected S-NSSAIs.

[0144] For example, the rejection reason value can be simply "overloaded", "S-NSSAI unavailable due to reaching the maximum number of UEs", or "S-NSSAI unavailable due to resource constraints". UE 203 does not attempt to use the rejected S-NSSAI unless the list of rejected S-NSSAIs is updated in the UE, as described below with reference to Figure 8 If all S-NSSAIs in the possible allowed NSSAI are subject to monitoring the maximum number of UEs using network slices simultaneously and the result of all S-NSSAIs is "unavailable" (i.e., there are no other S-NSSAIs that can be included in the allowed NSSAI), the AMF sends a registration rejection message.

[0145] The registration rejection message may include at least some of the following parameters: 1) a new mobility management (MM) rejection reason indicating that the registration is rejected because there are no available network slices due to exceeding the quota for all requested S-NSSAIs; 2) a list of rejected S-NSSAIs including all S-NSSAIs indicated as "unavailable" by the NWDAF / UDM. The rejection reason value of the S-NSSAI can be similar to that described in step 12b); 3) a fallback time during which the UE should not re-attempt a registration request for the S-NSSAI in the list of rejected S-NSSAIs. The AMF can generate the time value based on the network configuration.

[0146] If the exceeded quota is the maximum number of connections per network slice, the vAMF 207 considers the corresponding S-NSSAIx not available for establishing a new PDU session. During the PDU session establishment procedure, the vAMF 207 may reject the PDU session by using a cause value indicating the reason for exceeding the quota for connections to the S-NSSAI. The UE 203 does not attempt further PDU session establishment requests towards that S-NSSAI. The UE 203 shall store the PDU session establishment re-detection in the MM context so that the UE 203 can internally check whether a new PDU session establishment request is targeted at S-NSSAIx. If so, the UE NAS MM layer shall internally reject the PDU session establishment request to the NAS SM layer. Procedure 700 ends.

[0147] The benefit of this solution is to monitor the number of UEs simultaneously registered to S-NSSAIx during the registration procedure and be able to inform the UE whether S-NSSAIx is allowed or rejected during the registration acceptance message.

[0148] Figure 8 Procedure 800 depicting a process for updating a UE when an S-NSSAI becomes available again (e.g., when the quota for network slice attributes is underloaded) according to an embodiment of the present disclosure. Procedure 800 involves UE 801, vAMF 207, hAMF 209, UDM 211, OAM system 603, and NWDAF 201. If the maximum number of UEs registered for an S-NSSAI or (2) the maximum number of PDU sessions has been reached, the NF (e.g., UDM or NWDAF, or other NF) responsible for counting the UEs registered for the S-NSSAI can enforce measures to restrict further UE registration to the S-NSSAI. The network can determine at a certain moment that the [UE, PDU session] using the S-NSSAI has decreased and the quota is underloaded. Then, the network can inform the AMF of the resources available for that S-NSSAI.

[0149] Procedure 800 applies when either of the following two situations occurs: (1) the S-NSSAIx or PDU session establishment has been rejected due to exceeding the quota of UEs or PDU sessions and (2) when the S-NSSAI becomes available again (i.e., the quota for UEs or PDU sessions using S-NSSAIx is underloaded). Procedure 800 starts at step 0 where the NWDAF 201 has determined that the quota / threshold of (1) the maximum number of UEs registered for the S-NSSAI or (2) the maximum number of PDU sessions has been reached and the NWDAF 201 has notified the UDM 211 or AMF 207 - 209, e.g., as shown in steps 12a and 13 of FIG. 7 (see block 805).

[0150] At step 1, the NWDAF 201 determines that the number of UEs registered for the S-NSSAI has fallen below the maximum allowed number, i.e., the S-NSSAI is available again for new UEs. For example, this can occur in one of the following ways: In step 1a, the OAM 603 can notify the NWDAF 201 that the quota has increased (see messaging 807). In step 1b, the AMF 207-209 or the UDM 211 can notify the NWDAF 201 of the reduced number of [UE, PDU session] using the S-NSSAIx (see messaging 809). The NWDAF 201 determines that the actual number of [UE, PDU session] using the S-NSSAI has fallen below the quota / limit.

[0151] At step 2a, in the case of roaming, the NWDAF 201 notifies all UDMs 211 subscribed to the data analysis of the availability of the S-NSSAIx (see messaging 505). The NWDAF 201 can also send the specific number of available [UE, PDU session] that can be allowed. For example, the NWDAF 201 can indicate "10" as the number of available [UE, PDU session] for the S-NSSAIx. This would mean for the UDM 211 that there are still ten UEs 801 that can register with the S-NSSAI. The NWDAF 201 can use the service operation Nwdaf_AnalyticsSubscription_Notify(S-NSSAIx, status "available", number of [UE, PDU session]) to notify the UDM 211 of the availability of the S-NSSAIx and optionally the number of available [UE, PDU session]. In step 2b, the UDM 211 sends the notification to the vAMF 207 (all AMFs in the V-PLMN) subscribed to the data analysis of the availability of the S-NSSAIx (see messaging 813).

[0152] At step 3, in the case of non-roaming, the NWDAF 201 informs all hAMFs 209 (all AMFs in the H-PLMN) subscribed to the data analysis of the availability of the S-NSSAIx (see messaging 815). Similar to step 2a, the NWDAF 201 can indicate the specific number of available [UE, PDU session] that can be allowed and that can use the same service operation.

[0153] At step 4a, the AMF 207-209 can identify which UEs have been rejected for exceeding the quota for the S-NSSAIx. The rejection can be due to exceeding the quota of UEs for the S-NSSAIx. The rejection can be due to exceeding the quota of PDU sessions for the S-NSSAIx.

[0154] The AMF 207 - 209 can store, in the context of a UE in the AMF, the status of a rejected S-NSSAI or PDU session sent to the UE. Thus, the AMF 207 - 209 can determine which UEs 805 are eligible for an update (see boxes 817 and 819), i.e., (1) remove from the list of rejected S-NSSAIs the S-NSSAI that was rejected due to "quota exceeded for the UE"; or (2) inform the UE that a PDU session that was previously rejected due to "quota exceeded for the PDU session" is now available. When determining which UEs are to be updated, the AMF 207 - 209 can consider the subscriber type of the UE801 (e.g., "gold", "silver", "bronze", "priority service", etc.). For example, if the UE 801 subscribes to a priority service (MPS) or a mission-critical (MCS) service, the AMF can decide to first update those UEs by removing the S-NSSAI from the list of rejected S-NSSAIs.

[0155] At step 4b, the AMF can perform a UE Configuration Update (UCU) procedure to update the UE 801 (see box 819). An example of the UCU procedure is described in clause 4.2.4 of 3GPP TS 23.502. The AMF includes a list of the new rejected S-NSSAIs, which does not include the S-NSSAI indicated in step 2. At step 5, after updating the UE 801, the UE 801 can decide to use the service of the S-NSSAIx. For example, if the S-NSSAIx is available for registration, the UE can initiate a registration procedure, e.g., send a registration request message, to register to the S-NSSAI (see message passing 821). As another example, if a new PDU session can be established towards the S-NSSAIx, the UE can decide to establish a PDU session towards the S-NSSAIx. In the case where the UE801 is roaming, it sends a registration request message to the vAMF 207 to register to the now-available S-NSSAI. In the case where the UE 801 is in the HPLMN (e.g., not roaming), it sends a registration request message to the hAMF 209 to register to the now-available S-NSSAI. Procedure 800 ends.

[0156] The benefit of this solution is that as soon as the S-NSSAI becomes available for a new registration or a new PDU session, the UE can be dynamically updated and allowed to register to the S-NSSAI or establish a PDU session.

[0157] Figure 9Depict an embodiment of a user terminal device 900 that can be used to monitor slice attributes of a network slice according to an embodiment of the present disclosure. The user terminal device 900 can be an embodiment of the remote unit 105, the roaming UE 203, and / or the non-roaming UE 205. In addition, the user terminal device 900 can include a processor 905, a memory 910, an input device 915, an output device 920, and a transceiver 925. In some embodiments, the input device 915 and the output device 920 are combined into a single device, such as a touch screen. In certain embodiments, the user terminal device 900 does not include any input device 915 and / or output device 920.

[0158] As depicted, the transceiver 925 includes at least one transmitter 930 and at least one receiver 935. Here, the transceiver 925 communicates with a mobile core network (e.g., 5GC) via an access network. In addition, the transceiver 925 can support at least one network interface 940. Here, the at least one network interface 940 facilitates communication with an eNB or gNB (e.g., using the "Uu" interface). In addition, the at least one network interface 940 can include interfaces for communicating with the AMF, SMF, and / or UPF.

[0159] In one embodiment, the processor 905 can include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 905 can be a microcontroller, a microprocessor, a central processing unit ("CPU"), a graphics processing unit ("GPU"), an auxiliary processing unit, a field-programmable gate array ("FPGA"), or a similar programmable controller. In some embodiments, the processor 905 executes instructions stored in the memory 910 to perform the methods and routines described herein. The processor 905 is communicatively coupled to the memory 910, the input device 915, the output device 920, and the transceiver 925. The processor 905 can control the user terminal device 900 to perform the UE behaviors described herein.

[0160] In various embodiments, the transceiver 925 can receive a request (e.g., from the NWDAF) to report usage data for a network slice. In certain embodiments, the processor 905 can report usage data related to non-roaming instances of slice attributes (e.g., the number of non-roaming UEs and / or the number of non-roaming PDU sessions). In some embodiments, the processor 905 receives a configuration for monitoring slice attributes from the NWDAF (via the transceiver 925).

[0161] In some embodiments, the processor 905 may receive subscription requests from network functions (NFs) such as the UDM and / or NWDAF. Here, the subscription request may indicate slice attributes or events to be monitored. In response to the subscription request, the processor 905 may monitor and report the occurrence of events related to the slice attributes. In some embodiments, the processor 905 may receive instructions to enforce countermeasures (e.g., via the transceiver 925). For example, if the monitored slice attributes exceed the quota, the NWDAF and / or UDM may instruct the user terminal device 900 to enforce countermeasures.

[0162] In one embodiment, the memory 910 is a computer-readable storage medium. In some embodiments, the memory 910 includes volatile computer storage media. For example, the memory 910 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). In some embodiments, the memory 910 includes non-volatile computer storage media. For example, the memory 910 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 910 includes both volatile and non-volatile computer storage media. In some embodiments, the memory 910 stores data related to registration with a mobile network via another mobile network, such as storing a security context, an IP address, etc. In certain embodiments, the memory 910 also stores program code and related data, such as an operating system ("OS") or other controller algorithms running on the user terminal device 900 and one or more software applications.

[0163] In one embodiment, the input device 915 may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device 915 may be integrated with the output device 920, for example, as a touch screen or a similar touch-sensitive display. In some embodiments, the input device 915 includes a touch screen such that text can be input using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device 915 includes two or more different devices, such as a keyboard and a touch panel.

[0164] In one embodiment, output device 920 may include any known electronically controllable display or display device. Output device 920 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 920 includes an electronic display capable of outputting visual data to a user. For example, output device 920 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, output device 920 may include a wearable display, such as a smartwatch, smart glasses, a head-up display, etc. Additionally, output device 920 may be a component of a smartphone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0165] In certain embodiments, output device 920 includes one or more speakers for generating sound. For example, output device 920 may generate an audible alert or notification (e.g., a beep or a ringtone). In some embodiments, output device 920 includes one or more haptic devices for generating vibration, movement, or other tactile feedback. In some embodiments, all or part of output device 920 may be integrated with input device 915. For example, input device 915 and output device 920 may form a touchscreen or a similar touch-sensitive display. In other embodiments, all or part of output device 920 may be located near input device 915.

[0166] As discussed above, transceiver 925 communicates with one or more network functions of a mobile communication network via one or more access networks. Transceiver 925 operates under the control of processor 905 to transmit messages, data, and other signals and also to receive messages, data, and other signals. For example, processor 905 may selectively activate transceiver (or a portion thereof) at a particular time to send and receive messages.

[0167] Transceiver 925 may include one or more transmitters 930 and one or more receivers 935. Although only one transmitter 930 and one receiver 935 are illustrated, user terminal device 900 may have any suitable number of transmitters 930 and receivers 935. For example, (one or more) transmitters 930 and (one or more) receivers 935 may be any suitable type of transmitter and receiver. In one embodiment, transceiver 925 includes a first transmitter / receiver pair for communicating with a mobile communication network on an authorized radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network on an unlicensed radio spectrum.

[0168] In some embodiments, a first transmitter / receiver pair for communicating with a mobile communication network over an authorized radio spectrum and a second transmitter / receiver pair for communicating with the mobile communication network over an unlicensed radio spectrum may be combined into a single transceiver unit, e.g., a single chip that performs functions for use with both the authorized and unlicensed radio spectrums. In some embodiments, the first transmitter / receiver pair and the second transmitter / receiver pair may share one or more hardware components. For example, certain transceivers 925, transmitters 930, and receivers 935 may be implemented as physically separate components that access shared hardware resources and / or software resources, such as network interface 940.

[0169] In various embodiments, one or more transmitters 930 and / or one or more receivers 935 may be implemented and / or integrated into a single hardware component, such as a multi-transceiver chip, a system-on-chip, an ASIC, or other types of hardware components. In certain embodiments, one or more transmitters 930 and / or one or more receivers 935 may be implemented and / or integrated into a multi-chip module. In some embodiments, other components such as network interface 940 or other hardware components / circuits may be integrated with any number of transmitters 930 and / or receivers 935 into a single chip. In such embodiments, the transmitters 930 and receivers 935 may be logically configured as a transceiver 925 using one more common control signal, or configured as modular transmitters 930 and receivers 935 in the same hardware chip or in a multi-chip module.

[0170] Figure 10 Depicted is an embodiment of a network terminal device 1000 that may be used to monitor slice attributes according to embodiments of the present disclosure. The network terminal device 1000 may include a processor 1005, a memory 1010, an input device 1015, an output device 1020, and a transceiver 1025. In some embodiments, the input device 1015 and the output device 1020 are combined into a single device, such as a touch screen. In certain embodiments, the network terminal device 1000 does not include any input device 1015 and / or output device 1020.

[0171] As depicted, the transceiver 1025 includes at least one transmitter 1030 and at least one receiver 1035. Here, the transceiver 1025 communicates with one or more network functions in a mobile communication network (e.g., a PLMN). Additionally, the transceiver 1025 may support at least one network interface 1040. In some embodiments, the transceiver 1025 supports different interfaces for communicating with various network functions in a mobile core network (e.g., 5GC).

[0172] In one embodiment, the processor 1005 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 1005 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field-programmable gate array (“FPGA”), or a similar programmable controller. In some embodiments, the processor 1005 executes instructions stored in the memory 1010 to perform the methods and routines described herein. The processor 1005 is communicatively coupled to the memory 1010, the input device 1015, the output device 1020, and the transceiver 1025.

[0173] In various embodiments, the network terminal device 1000 acts as an NWDAF in a PLMN. Here, the processor 1005 determines to collect data on slice attributes for a network slice. In one embodiment, the slice attribute is the number of UEs using the network slice. In another embodiment, the slice attribute is the number of data sessions (e.g., PDU sessions) using the network slice. In certain embodiments, the processor 1005 determines to collect data on multiple slice attributes for a network slice, such as tracking both the number of UEs using the network slice and the number of PDU sessions using the network slice. In certain embodiments, the processor 1005 determines to collect data on slice attributes for multiple network slices.

[0174] After determining to collect data on at least one slice attribute, the processor 1005 requests (e.g., via the transceiver 1025) a first collection NF to report first usage data for the network slice according to the slice attribute, and requests a second collection NF to report second usage data for the network slice according to the slice attribute. Here, the first usage data may indicate the number of roaming user terminal devices using the network slice and / or the number of data sessions of the roaming user terminal devices using the network slice, while the second usage data indicates the number of non-roaming user terminal devices using the network slice and / or the number of data sessions of the non-roaming user terminal devices using the network slice. In certain embodiments, the processor 1005 discovers the first collection NF and the second collection NF by sending a discovery request to the NRF, where the first collection NF and the second collection NF serve the network slice.

[0175] In some embodiments, requesting the first collection NF to report first usage data for the network slice according to the slice attribute includes sending a configuration for monitoring the slice attribute to the first collection NF. In certain embodiments, the first collection NF is the UDM and the second collection NF is the AMF. In other embodiments, the first collection NF is the AMF and the second NF function is the UE.

[0176] The processor 1005 uses the first usage data and the second usage data to determine whether a quota associated with a slice attribute is reached. In some embodiments, a request for data analysis indicates multiple quotas for a slice attribute. In such embodiments, different quotas may indicate different analyses to be sent to the requesting NF.

[0177] In response to determining that the quota is met, the processor 1005 controls the transceiver 1025 to send a notification to a network function, where the network function enforces a countermeasure. In some embodiments, different quotas may implicitly indicate specific countermeasures to be enforced by the requesting NF. In some embodiments, it is determined that the collection of data is triggered by a request for data analysis of at least one quota for a slice attribute for a network slice from a requesting NF (e.g., NEF, UDM, AMF, etc.). In such embodiments, notifying the network function when the quota is met may include notifying the requesting NF.

[0178] In some embodiments, the processor 1005 detects an underload of a quota associated with a slice attribute and instructs the network function to stop enforcing the countermeasure (via the transceiver 1025). In some embodiments, the first collection NF and the second collection NF are the same NF of the NSSF that includes performing global usage data collection for non-roaming user terminal devices and / or roaming user terminal devices using a network slice.

[0179] In various embodiments, the network terminal device 1000 acts as a UDM in a PLMN. Here, the transceiver 1025 receives a configuration for monitoring slice attributes of a network slice, where the slice attributes include the number of user terminal devices using the network slice and / or the number of data sessions using the network slice.

[0180] In some embodiments, receiving a configuration for monitoring slice attributes of a network slice includes receiving a quota for a slice attribute. In some embodiments, receiving a configuration for monitoring slice attributes of a network slice includes receiving multiple quotas for a slice attribute. In such embodiments, each quota may be associated with a countermeasure.

[0181] The processor 1005 determines usage data for roaming user terminal devices using a network slice based on the slice attributes, where the usage data includes the number of roaming user terminal devices using the network slice and / or the number of data sessions of the roaming user terminal devices using the network slice. Additionally, the processor 1005 may enforce a countermeasure in response to determining that an associated quota is reached.

[0182] In some embodiments, determining usage data for a roaming user terminal device using a network slice includes subscribing to a serving AMF by requesting the serving AMF for the network slice to report current slice attributes. In such an embodiment, the serving AMF reports the current slice attributes in response to detecting a reporting event, which is a change in the slice attributes that is at least a predetermined amount since the last report and / or a predetermined amount of time that has elapsed since the last report.

[0183] The transceiver 1025 reports usage data for a roaming user terminal device using a network slice to the NWDAF. In some embodiments, the processor 1005 selects a NWDAF capable of collecting data analysis for slice attributes, where the usage data is reported to the selected NWDAF. In some embodiments, the processor 1005 requests the NWDAF to perform data analysis using the slice attributes for the network slice.

[0184] In some embodiments, the processor 1005 instructs the serving AMF to perform a coercive measure in response to determining that a quota associated with the slice attributes is met. In such an embodiment, the processor 1005 may detect an underload of the quota associated with the slice attributes and instruct the serving AMF to stop performing the coercive measure.

[0185] In various embodiments, the network terminal device 1000 acts as an NF in a PLMN, which is configured to monitor and report the occurrence of an event. Here, the transceiver 1025 may receive a request (e.g., from the NWDAF) to report usage data for a network slice. In certain embodiments, the processor 1005 may collect and report usage data related to a non-roaming instance of the slice attributes (e.g., the number of non-roaming UEs and / or the number of non-roaming PDU sessions). In other embodiments, the processor 1005 may collect and report usage data related to a roaming instance of the slice attributes (e.g., the number of roaming UEs and / or the number of roaming PDU sessions). In some embodiments, the processor 1005 receives a configuration for monitoring slice attributes from the NWDAF (via the transceiver 1025).

[0186] In certain embodiments, the processor 1005 may control the transceiver 1025 to request network data analysis for slice attributes. In certain embodiments, the processor 1005 may receive a subscription request from another NF (such as the UDM and / or the NWDAF). Here, the subscription request may indicate the slice attributes or events to be monitored. In response to the subscription request, the processor 1005 may monitor and report the occurrence of events related to the slice attributes.

[0187] In some embodiments, the processor 1005 may receive instructions to enforce a countermeasure (e.g., via transceiver 1025). For example, if the monitored slice attributes exceed a quota, the NWDAF and / or UDM may instruct the network terminal device 1000 to enforce a countermeasure.

[0188] In one embodiment, the memory 1010 is a computer-readable storage medium. In some embodiments, the memory 1010 includes volatile computer storage media. For example, the memory 1010 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). In some embodiments, the memory 1010 includes non-volatile computer storage media. For example, the memory 1010 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 1010 includes both volatile and non-volatile computer storage media. In some embodiments, the memory 1010 stores data related to data collection, such as storage quotas, network slice attribute data, countermeasures, monitoring configurations, etc. In certain embodiments, the memory 1010 also stores program code and related data, such as an operating system ("OS") or other controller algorithms running on the network terminal device 1000 and one or more software applications.

[0189] In one embodiment, the input device 1015 may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device 1015 may be integrated with the output device 1020, for example, as a touch screen or a similar touch-sensitive display. In some embodiments, the input device 1015 includes a touch screen such that text can be input using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device 1015 includes two or more different devices, such as a keyboard and a touch panel.

[0190] In one embodiment, output device 1020 may include any known electronically controllable display or display device. Output device 1020 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 1020 includes an electronic display capable of outputting visual data to a user. For example, output device 1020 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, output device 1020 may include a wearable display, such as a smartwatch, smart glasses, a heads-up display, etc. Additionally, output device 1020 may be a component of a smartphone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0191] In certain embodiments, output device 1020 includes one or more speakers for generating sound. For example, output device 1020 may generate an auditory alert or notification (e.g., a beep or a ring). In some embodiments, output device 1020 includes one or more haptic devices for generating vibration, movement, or other tactile feedback. In some embodiments, all or part of output device 1020 may be integrated with input device 1015. For example, input device 1015 and output device 1020 may form a touchscreen or a similar touch-sensitive display. In other embodiments, all or part of output device 1020 may be located near input device 1015.

[0192] As discussed above, transceiver 1025 may communicate with one or more remote units and / or with one or more interworking functions providing access to one or more PLMNs. Transceiver 1025 may also communicate with one or more network functions (e.g., in mobile core network 140). Transceiver 1025 operates under the control of processor 1005 to transmit messages, data, and other signals and also to receive messages, data, and other signals. For example, processor 1005 may selectively activate the transceiver (or a portion thereof) at a particular time for sending and receiving messages.

[0193] The transceiver 1025 may include one or more transmitters 1030 and one or more receivers 1035. In some embodiments, one or more of the transmitters 1030 and / or one or more of the receivers 1035 may share transceiver hardware and / or circuitry. For example, one or more of the transmitters 1030 and / or one or more of the receivers 1035 may share one or more antennas, one or more antenna tuners, one or more amplifiers, one or more filters, one or more oscillators, one or more mixers, one or more modulators / demodulators, power supplies, etc. In one embodiment, the transceiver 1025 implements multiple logical transceivers using a common physical hardware while using different communication protocols or protocol stacks simultaneously.

[0194] Figure 11 Depicts an embodiment of a method 1100 for monitoring slice attributes according to an embodiment of the present disclosure. In various embodiments, the method 1100 is performed by an NWDAF such as the NWDAF 135, NWDAF 201, and / or the network terminal device 1000 described above. In some embodiments, the method 1100 is performed by a processor such as a microcontroller, a microprocessor, a central processing unit (CPU), a graphics processing unit (GPU), an auxiliary processing unit, an FPGA, etc.

[0195] The method 1100 begins and determines 1105 to collect data on slice attributes for a network slice. Here, the slice attributes are the number of user terminal devices using the network slice and / or the number of data sessions using the network slice. The method 1100 includes requesting 1110 a first collection network function to report first usage data for the network slice according to the slice attributes. Here, the first usage data indicates the number of roaming user terminal devices using the network slice and / or the number of data sessions of the roaming user terminal devices using the network slice. The method 1100 includes requesting 1115 a second collection network function to report second usage data for the network slice according to the slice attributes. Here, the second usage data indicates the number of non-roaming user terminal devices using the network slice and / or the number of data sessions of the non-roaming user terminal devices using the network slice. The method 1100 includes using the first usage data and the second usage data to determine 1120 whether a quota associated with the slice attributes is reached. The method 1100 includes notifying 1125 the network function when the quota is met, where the network function enforces countermeasures. The method 1100 ends.

[0196] Figure 12Depict an embodiment of method 1200 for monitoring slice attributes according to an embodiment of the present disclosure. In various embodiments, method 1200 is performed by a user data management function such as UDM / UDR 139, UDM 211, and / or network terminal device 1000. In some embodiments, method 1200 is performed by a processor such as a microcontroller, microprocessor, central processing unit (CPU), graphics processing unit (GPU), auxiliary processing unit, FPGA, etc.

[0197] Method 1200 begins and receives 1205 a configuration for monitoring slice attributes of a network slice, where the slice attributes include the number of user terminal devices using the network slice and / or the number of data sessions using the network slice. Method 1200 includes determining 1210 usage data for roaming user terminal devices using the network slice according to the slice attributes, where the usage data includes the number of roaming user terminal devices using the network slice and / or the number of data sessions of the roaming user terminal devices using the network slice. Method 1200 includes reporting 1215 the usage data for roaming user terminal devices using the network slice to the NWDAF. Method 1200 ends.

[0198] Disclosed herein is a first apparatus for monitoring slice attributes according to an embodiment of the present disclosure. The first apparatus may be implemented by an NWDAF such as NWDAF 135, NWDAF 201, and / or network terminal device 1000. The first apparatus includes a processor that determines to collect data on slice attributes for a network slice. Here, the slice attributes are the number of user terminal devices using the network slice and / or the number of data sessions using the network slice. The processor requests a first collection network function to report first usage data for the network slice according to the slice attributes, and requests a second collection network function to report second usage data for the network slice according to the slice attributes. Here, the first usage data indicates the number of roaming user terminal devices using the network slice and / or the number of data sessions of the roaming user terminal devices using the network slice, while the second usage data indicates the number of non-roaming user terminal devices using the network slice and / or the number of data sessions of the non-roaming user terminal devices using the network slice. The processor uses the first usage data and the second usage data to determine whether a quota associated with the slice attributes is reached. The first apparatus includes a transceiver that sends a notification to a network function in response to the quota being met, where the network function performs a coercive measure.

[0199] In certain embodiments, the processor discovers the first collection network function and the second collection network function by sending a discovery request to the NRF, where the first collection network function and the second collection network function serve the network slice.

[0200] In some embodiments, determining that data collection is triggered by a request for analysis of at least one quota for slice attributes for a network slice from a requesting network function (e.g., NEF, UDM, AMF, etc.). In such embodiments, notifying the network function in response to the quota being met may include notifying the requesting network function. In certain embodiments, the request for analysis indicates multiple quotas for slice attributes. In such embodiments, different quotas may indicate different analyses to be sent to the requesting network function. In certain embodiments, different quotas may implicitly indicate specific enforcement actions to be performed by the requesting network function.

[0201] In some embodiments, requesting a first collection network function to report first usage data for a network slice according to slice attributes includes sending a configuration for monitoring slice attributes to the first collection network function. In certain embodiments, the first collection network function is a UDM and the second collection network function is an AMF. In other embodiments, the first collection network function is an AMF and the second collection network function is a UE.

[0202] In certain embodiments, the processor detects an underload of a quota associated with slice attributes and instructs the network function to stop performing enforcement actions. In some embodiments, the first collection network function and the second collection network function are the same collection network function of an NSSF that includes performing global usage data collection for non-roaming user terminal devices and / or roaming user terminal devices using the network slice.

[0203] Disclosed herein is a first method for monitoring slice attributes according to embodiments of the present disclosure. The first method may be performed by an NWDAF such as NWDAF 135, NWDAF 201, and / or network terminal device 1000. The first method includes determining data for slice attributes for a network slice. Here, the slice attributes are the number of user terminal devices using the network slice and / or the number of data sessions using the network slice. The method includes requesting a first collection network function to report first usage data for the network slice according to the slice attributes, and requesting a second collection network function to report second usage data for the network slice according to the slice attributes. Here, the first usage data indicates the number of roaming user terminal devices using the network slice and / or the number of data sessions of the roaming user terminal devices using the network slice, while the second usage data indicates the number of non-roaming user terminal devices using the network slice and / or the number of data sessions of the non-roaming user terminal devices using the network slice. The method includes using the first usage data and the second usage data to determine whether a quota associated with the slice attributes is reached and notifying the network function in response to the quota being met, where the network function performs enforcement actions.

[0204] In some embodiments, the first method further includes discovering a first collection network function and a second collection network function by sending a discovery request to the NRF, where the first collection network function and the second collection network function serve a network slice.

[0205] In some embodiments of the first method, it is determined that the collection of data is triggered by a request for data analysis of at least one quota for slice attributes for a network slice from a requesting network function (e.g., NEF, UDM, AMF, etc.). In such an embodiment, notifying the network function in response to the quota being met may include notifying the requesting network function. In certain embodiments, the request for data analysis indicates multiple quotas for slice attributes. In such an embodiment, different quotas may indicate different analyses to be sent to the requesting network function. In certain embodiments, different quotas may implicitly indicate specific enforcement actions to be performed by the requesting network function.

[0206] In some embodiments of the first method, requesting the first collection network function to report first usage data for a network slice according to slice attributes includes sending a configuration for monitoring slice attributes to the first collection network function.

[0207] In some embodiments of the first method, the first collection network function is the UDM and the second collection network function is the AMF. In other embodiments of the first method, the first collection network function is the AMF and the second collection network function is the UE.

[0208] In certain embodiments, the first method further includes detecting an underload of a quota associated with slice attributes and instructing the network function to stop performing enforcement actions. In some embodiments of the first method, the first collection network function and the second collection network function are the same collection network function of the NSSF that includes performing global usage data collection for non-roaming user terminal devices and / or roaming user terminal devices using the network slice.

[0209] Disclosed herein is a second apparatus for monitoring slice attributes according to embodiments of the present disclosure. The second apparatus may be implemented by a user data management function such as UDM 139, UDM 211, and / or network terminal apparatus 1000. The second apparatus includes a transceiver that receives a configuration for monitoring slice attributes of a network slice, where the slice attributes include the number of user terminal devices using the network slice and / or the number of data sessions using the network slice. The second apparatus includes a processor that determines usage data for roaming user terminal devices using the network slice according to the slice attributes, where the usage data includes the number of roaming user terminal devices using the network slice and / or the number of data sessions of the roaming user terminal devices using the network slice, and where the transceiver reports the usage data for the roaming user terminal devices using the network slice to the NWDAF.

[0210] In some embodiments, receiving a configuration for monitoring slice attributes of a network slice includes receiving a quota for the slice attributes. In certain embodiments, receiving a configuration for monitoring slice attributes of a network slice includes receiving a plurality of quotas for the slice attributes. In such embodiments, each quota may be associated with a coercive measure. Additionally, the processor may execute a coercive measure in response to determining that an associated quota has been reached.

[0211] In certain embodiments, determining usage data for a roaming user terminal device using a network slice includes subscribing to a serving AMF by requesting the serving AMF for the network slice to report current slice attributes for the network slice. In such embodiments, the serving AMF reports the current slice attributes in response to detecting a reporting event, which is a change in the slice attributes that is at least a predetermined amount since the last report and / or a predetermined amount of time that has elapsed since the last report.

[0212] In some embodiments, the processor instructs the serving AMF to execute a coercive measure in response to determining that a quota associated with the slice attributes has been met. In such embodiments, the processor may detect an underload of a quota associated with the slice attributes and instruct the serving AMF to stop executing the coercive measure.

[0213] In some embodiments, the processor selects an NWDAF capable of collecting data analysis for the slice attributes, and the usage data is reported to the selected NWDAF. In some embodiments, the processor requests the NWDAF to perform data analysis using the slice attributes for the network slice.

[0214] Disclosed herein is a second method for monitoring slice attributes according to embodiments of the present disclosure. The second method may be executed by a user data management function such as UDM 139, UDM 211, and / or network terminal device 1000. The second method includes receiving a configuration for monitoring slice attributes of a network slice, where the slice attributes include the number of user terminal devices using the network slice and / or the number of data sessions using the network slice. The second method includes determining usage data for a roaming user terminal device using the network slice according to the slice attributes, where the usage data includes the number of roaming user terminal devices using the network slice and / or the number of data sessions of the roaming user terminal devices using the network slice. The second method includes reporting the usage data for the roaming user terminal device using the network slice to the NWDAF.

[0215] In some embodiments of the second method, receiving a configuration for monitoring slice attributes of a network slice includes receiving a quota for the slice attributes. In some embodiments of the second method, receiving a configuration for monitoring slice attributes of a network slice includes receiving multiple quotas for the slice attributes. In certain embodiments, each quota is associated with a coercive measure, and the method further includes performing the coercive measure in response to determining that the associated quota has been reached.

[0216] In some embodiments of the second method, determining usage data of a roaming user terminal for using a network slice includes subscribing to a serving AMF by requesting the serving AMF for the network slice to report current slice attributes of the network slice. In such an embodiment, the serving AMF may report the current slice attributes in response to detecting a reporting event. Here, the reporting event is a change in the slice attributes that is at least a predetermined amount since the last report and / or a predetermined amount of time that has elapsed since the last report.

[0217] In certain embodiments, the second method includes instructing the serving AMF to perform a coercive measure in response to determining that a quota associated with the slice attributes is met. In such an embodiment, the second method may further include detecting an underload of the quota associated with the slice attributes and instructing the serving AMF to stop performing the coercive measure.

[0218] In certain embodiments, the second method includes selecting an NWDAF capable of collecting data analysis for the slice attributes, where the usage data is reported to the selected NWDAF. In certain embodiments, the second method includes requesting the NWDAF to perform data analysis using the slice attributes for the network slice.

[0219] Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only illustrative and not restrictive. Thus, the scope of the invention is indicated by the appended claims rather than by the foregoing description. All changes within the meaning and scope of equivalents of the claims are to be included within their scope.

Claims

1. A method for a network function, comprising: Receiving a first request from an Application Function (AF) or a Network Exposure Function (NEF), wherein the first request includes an event identifier indicating a reporting event corresponding to the number of User Equipments (UEs) registered to a network slice or the number of data connections established for the network slice, and wherein the first request includes event reporting information indicating a reporting condition; Sending an acknowledgement message to the AF or NEF in response to the first request; And Sending a first notification message to the AF or NEF in response to the reporting condition being met, the first notification message including an event report corresponding to the reporting condition and the event identifier, wherein the event report indicates one or more of the number of UEs registered to the network slice, the number of data connections established for the network slice, an acknowledgement of exceeding the reporting condition, an acknowledgement of not meeting the reporting condition, an acknowledgement of exceeding a threshold, and an acknowledgement of not meeting the threshold.

2. The method according to claim 1, wherein, The first request includes Single Network Slice Selection Assistance Information (S-NSSAI) identifying the network slice.

3. The method according to claim 1, wherein The first request includes a subscription request for network slice event exposure.

4. The method according to claim 1, Among them, wherein the reporting condition includes a time interval for periodic reporting, and determining that the reporting condition is met includes determining that the time interval has expired; and wherein the event reporting information includes the current number of remote units registered to the network slice or the current number of data connections established on the remote slice.

5. The method according to claim 1, Among them, wherein the reporting condition includes a corresponding threshold for threshold-based reporting, wherein determining that the reporting condition is met includes determining: the number of remote units registered in the network slice exceeds the threshold, or the number of remote units registered in the network slice does not meet the threshold by decreasing from above the threshold to below the threshold; and wherein the event reporting information includes an acknowledgement of exceeding the threshold or an acknowledgement of not meeting the threshold.

6. The method according to claim 1, Among them, wherein the reporting condition includes a corresponding threshold for threshold-based reporting, wherein determining that the reporting condition is met includes determining: the number of data connections established in the network slice exceeds the threshold, or the number of data connections established in the network slice does not meet the threshold by decreasing from above the threshold to below the threshold; and wherein the event reporting information includes an acknowledgement of exceeding the threshold or an acknowledgement of not meeting the threshold.

7. A device for a network function, comprising: a memory; and a processor, the processor being coupled to the memory and configured to cause the device to: Receive a first request from an Application Function (AF) or a Network Exposure Function (NEF), where the first request includes an event identifier indicating a reporting event corresponding to the number of User Equipments (UEs) registered to a network slice or the number of data connections established for the network slice, and where the first request includes event reporting information indicating a reporting condition In response to the first request, send an acknowledgement message to the AF or NEF; And In response to the reporting condition being met, send a first notification message to the AF or NEF, the first notification message including an event report corresponding to the reporting condition and the event identifier, where the event report indicates one or more of the number of UEs registered to the network slice, the number of data connections established for the network slice, an acknowledgement of exceeding the reporting condition, an acknowledgement of not meeting the reporting condition, an acknowledgement of exceeding a threshold, and an acknowledgement of not meeting the threshold.

8. The device according to claim 7, wherein, The first request includes Single Network Slice Selection Assistance Information (S-NSSAI) identifying the network slice.

9. The apparatus according to claim 7, wherein The first request includes a subscription request for network slice event exposure.

10. The apparatus according to claim 7, Among them, The reporting condition includes a time interval for periodic reporting, where, to determine that the reporting condition is met, the processor is configured to cause the apparatus to determine that the time interval has expired; and where the event reporting information includes the current number of remote units registered to the network slice or the current number of data connections established on the remote slice.

11. The apparatus according to claim 7, Among them, The reporting condition includes a corresponding threshold for threshold-based reporting, where, to determine that the reporting condition is met, the processor is configured to cause the apparatus to determine: The number of remote units registered in the network slice exceeds the threshold, or The number of remote units registered in the network slice fails to meet the threshold by decreasing from above the threshold to below the threshold; and where the event reporting information includes an acknowledgement of exceeding the threshold or an acknowledgement of not meeting the threshold.

12. The apparatus according to claim 7, Among them, The reporting condition includes a corresponding threshold for threshold-based reporting, where, to determine that the reporting condition is met, the processor is configured to cause the apparatus to determine: The number of data connections established in the network slice exceeds the threshold, or The number of data connections established in the network slice fails to meet the threshold by decreasing from above the threshold to below the threshold; and where the event reporting information includes an acknowledgement of exceeding the threshold or an acknowledgement of not meeting the threshold.

13. An apparatus comprising a Network Exposure Function (NEF), comprising: A memory; And A processor, the processor being coupled to the memory and configured to cause the NEF to: Receive a first subscription request for network slice notification reporting from an Application Function (AF), where the first subscription request includes an event identifier indicating a reporting event corresponding to the number of User Equipments (UEs) registered to a network slice or the number of data connections established for the network slice, and where the first subscription request includes event reporting information indicating a reporting condition; Discover a network function supporting network slice notification reporting; Send a second subscription request to the network function, the second subscription request including the event identifier and the event reporting information; Receive a first notification message from the network function, the first notification message including an event report corresponding to the reporting condition and the event identifier, where the event report indicates one or more of the number of UEs registered to the network slice, the number of data connections established for the network slice, confirmation of exceeding the reporting condition, confirmation of not meeting the reporting condition, confirmation of exceeding a threshold, and confirmation of not meeting the threshold; And Send a second notification message to the AF, the second notification message including the event identifier and the event report.

14. The apparatus according to claim 13, wherein, The first subscription request includes a Single Network Slice Selection Assistance Information (S-NSSAI) identifying the network slice, and the second subscription request includes the S-NSSAI.

15. The device according to claim 13, wherein, The first subscription request includes a subscription request for network slice event exposure.

16. The apparatus according to claim 13, Among them, The reporting condition includes a time interval for periodic reporting, where the event report contains the current number of remote units registered to the network slice or the current number of data connections established on the remote slice.

17. The apparatus according to claim 13, Among them, The reporting condition includes a corresponding threshold for the number of remote units registered in the network slice, and where the event report contains confirmation of exceeding the threshold or confirmation of not meeting the threshold.

18. The apparatus according to claim 13, Among them, The reporting condition includes a corresponding threshold for the number of data connections established in the network slice, and where the event report contains confirmation of exceeding the threshold or confirmation of not meeting the threshold.

Images