Method for network slice management based on inactivity

Abstract

An access and mobility management function (AMF) receives, from a network node, a value of a duration associated with inactivity of a network slice for a wireless device. The AMF starts the duration. The AMF determines, based on the value, that the duration expires, and sends, to the wireless device, an indication of removal of the network slice.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 320,911, filed March 17, 2022, the entire contents of which are incorporated herein by reference. Attached Figure Description

[0003] Examples of several embodiments of the various embodiments of this disclosure are described herein with reference to the accompanying drawings.

[0004] Figure 1A and Figure 1B This illustrates an example communication network that includes an access network and a core network.

[0005] Figure 2A , Figure 2B , Figure 2C and Figure 2D Various examples of service-based architecture frameworks within the core network are shown.

[0006] Figure 3 An example communication network containing core network functions is shown.

[0007] Figure 4A and Figure 4B An example of a core network architecture with multiple user plane functions and untrusted access is shown.

[0008] Figure 5 An example of the core network architecture for roaming scenarios is shown.

[0009] Figure 6 An example of a network slice is shown.

[0010] Figure 7A , Figure 7B and Figure 7C It shows the user plane protocol stack, the control plane protocol stack, and the services between the protocol layers set up in the user plane protocol stack.

[0011] Figure 8 An example of a quality of service model for data exchange is shown.

[0012] Figure 9A , Figure 9B , Figure 9C and Figure 9D This shows example states and state transitions of a wireless device.

[0013] Figure 10 An example of a registration procedure for a wireless device is shown.

[0014] Figure 11 This shows an example of a service request procedure for a wireless device.

[0015] Figure 12 This shows an example of the Protocol Data Unit (PDU) session establishment procedure for a wireless device.

[0016] Figure 13 Examples of components shown are examples of elements in a communication network.

[0017] Figure 14A , Figure 14B , Figure 14C and Figure 14D Various examples of physical core network deployments, each having one or more network functions or portions thereof, are shown.

[0018] Figure 15 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0019] Figure 16 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0020] Figure 17 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0021] Figure 18 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0022] Figure 19 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0023] Figure 20 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0024] Figure 21 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0025] Figure 22 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0026] Figure 23 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0027] Figure 24 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0028] Figure 25 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0029] Figure 26 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0030] Figure 27 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0031] Figure 28 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0032] Figure 29 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0033] Figure 30 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0034] Figure 31 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0035] Figure 32 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0036] Figure 33 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0037] Figure 34 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0038] Figure 35 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0039] Figure 36 This is an exemplary diagram of one aspect of the implementation of this disclosure.

[0040] Figure 37 This is an exemplary diagram of one aspect of the implementation of this disclosure. Detailed Implementation

[0041] In this disclosure, various embodiments are presented in the form of examples of how the disclosed techniques can be implemented and / or how the disclosed techniques can be practiced in environments and scenarios. It will be apparent to those skilled in the art that various changes in form and detail may be made therein without departing from the scope of the invention. Indeed, after reading the specification, it will be apparent to those skilled in the art how to implement alternative embodiments. Embodiments of the invention should not be limited to any of the described exemplary embodiments. Embodiments of this disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments may be combined to create additional embodiments within the scope of this disclosure. Any diagrams highlighting functionality and advantages are given for illustrative purposes only. The disclosed architecture is flexible and configurable enough that it can be utilized in ways other than those shown. For example, actions listed in any flowchart may be reordered or optionally used only in certain embodiments.

[0042] The implementation scheme can be configured to operate as needed. For example, in wireless devices, base stations, radio environments, networks, combinations thereof, etc., the disclosed mechanisms can be executed when certain criteria are met. Exemplary criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system setup, packet size, service characteristics, combinations thereof, etc. Various exemplary implementation schemes can be applied when one or more criteria are met. Therefore, exemplary implementation schemes that selectively implement the disclosed protocols can be implemented.

[0043] A base station can communicate with a hybrid of wireless devices. The wireless devices and / or base stations can support multiple technologies and / or multiple versions of the same technology. Wireless devices may have one or more specific capabilities. When this disclosure refers to a base station communicating with multiple wireless devices, this disclosure may refer to a subset of the total number of wireless devices in the coverage area. For example, this disclosure may refer to multiple wireless devices having a given capability and a given LTE or 5G version in a given sector of a base station. Multiple wireless devices in this disclosure may refer to a selected set of wireless devices, and / or a subset of the total number of wireless devices in the coverage area performing according to the disclosed method, etc. Multiple base stations or multiple wireless devices may exist in the coverage area that may not conform to the disclosed method; for example, these wireless devices or base stations may be based on older versions of LTE or 5G technology.

[0044] In this disclosure, the terms “a” and “an” and similar phrases refer to a single instance of a particular element but should not be construed as excluding other instances of that element. For example, a bicycle with two wheels can be described as having “wheels”. Any term ending with the suffix “(s)” will be construed as “at least one” and / or “one or more”. In this disclosure, the term “may” is construed as “may, for example”. In other words, the term “may” indicates that the phrase following the term “may” is an example of one of a number of suitable possibilities that may or may not be used in one or more embodiments of various embodiments. As used herein, the terms “comprising” and “consisting of” enumerate one or more parts of the element being described. The terms “comprising” and “including” are interchangeable and do not exclude the inclusion of unlisted parts in the element being described. In contrast, “consisting of” provides a complete enumeration of the one or more parts of the element being described.

[0045] The phrases “based on,” “in response to,” “depending on,” “adopted,” “used,” and similar phrases indicate the presence and / or influence of a particular factor and / or condition on an event and / or action, but do not exclude the presence and / or influence of uncounted factors and / or conditions on the event and / or action. For example, if action X is performed “based on” condition Y, this is interpreted as the action being performed “at least based on” condition Y. For example, if action X is performed when both conditions Y and Z are satisfied, the execution of action X can be described as “based on Y.”

[0046] The term "configured" can refer to the capabilities of a device, whether the device is in an operational or non-operational state. "Configured" can also mean specific settings within the device that affect its operational characteristics, regardless of whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, etc., can be "configured" within the device to provide specific characteristics to the device, whether the device is in an operational or non-operational state. Similarly, the term "control messages generated in the device" can mean that the control messages have parameters that can be used to configure specific characteristics in the device or to perform certain actions in the device, regardless of whether the device is in an operational or non-operational state.

[0047] In this disclosure, a parameter may include one or more information objects, and an information object may include one or more other objects. For example, if parameter J includes parameter K, and parameter K includes parameter L, and parameter L includes parameter M, then J includes L, and J includes M. A parameter may be referred to as a field or information element. In the example implementation, when one or more messages include multiple parameters, it means that a parameter among the multiple parameters is present in at least one of the one or more messages, but not necessarily in every one of the one or more messages.

[0048] This disclosure may relate to possible combinations of enumerated elements. For brevity and readability, this disclosure does not explicitly describe every permutation that can be obtained by selecting from the optional features of the group. This disclosure should be interpreted as explicitly disclosing all such permutations. For example, the seven possible combinations of enumerated elements A, B, C consist of: (1) “A”; (2) “B”; (3) “C”; (4) “A and B”; (5) “A and C”; (6) “B and C”; and (7) “A, B, and C”. For brevity and readability, these seven possible combinations can be described using any of the following interchangeable expressions: “at least one of A, B, and C”; “at least one of A, B, or C”; “one or more of A, B, and C”; “one or more of A, B, or C”; “A, B, and / or C”. It should be understood that impossible combinations are excluded. For example, “X and / or not X” should be interpreted as “X or not X”. It should also be understood that these expressions may describe alternative terms for overlapping and / or synonymous concepts, such as “identifier, identifier and / or ID number”.

[0049] This disclosure may relate to sets and / or subsets. As an example, a set X may be a set of elements comprising one or more elements. If every element of X is also an element of Y, then X may be called a subset of Y. In this disclosure, only non-empty sets and subsets are considered. For example, if Y consists of elements Y1, Y2, and Y3, then possible subsets of Y are {Y1, Y2, Y3}, {Y1, Y2}, {Y1, Y3}, {Y2, Y3}, {Y1}, {Y2}, and {Y3}.

[0050] Figure 1A An example of a communication network 100 in which embodiments of the present disclosure may be implemented is shown. The communication network 100 may include, for example, a Public Land Mobile Network (PLMN) operated by a network operator. Figure 1A As shown, the communication network 100 includes a wireless device 101, an access network (AN) 102, a core network (CN) 105, and one or more data networks (DN) 108.

[0051] Wireless device 101 can communicate with DN 108 via AN 102 and CN 105. In this disclosure, the term "wireless device" can refer to and encompass any mobile or fixed (non-mobile) device for which wireless communication is required or permitted. For example, a wireless device can be a telephone, smartphone, tablet, computer, laptop computer, sensor, meter, wearable device, Internet of Things (IoT) device, roadside unit (RSU) of a vehicle, relay node, automobile, drone, urban air traffic, and / or any combination thereof. The term "wireless device" encompasses other terms including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handheld device, wireless transmit and receive unit (WTRU), and / or wireless communication equipment.

[0052] AN 102 can connect wireless device 101 to CN 105 in any suitable manner. The communication direction from AN 102 to wireless device 101 is referred to as the downlink, and the communication direction from wireless device 101 to AN 102 is referred to as the uplink. Downlink transmissions can be separated from uplink transmissions using Frequency Division Duplex (FDD), Time Division Duplex (TDD), and / or some combination of these two duplex technologies. AN 102 can be connected to wireless device 101 via radio communication through an air interface. An access network operating at least partially via an air interface can be referred to as a Radio Access Network (RAN). CN 105 can establish one or more end-to-end connections between wireless device 101 and one or more DNs 108. CN 105 can authenticate wireless device 101 and provide billing functionality.

[0053] In this disclosure, the term "base station" can refer to and encompass any element of AN102 that facilitates communication between wireless device 101 and AN 102. Access networks and base stations have many different names and implementations. A base station can be a terrestrial base station fixed to the ground. A base station can be a mobile base station with mobile coverage areas. A base station can be in space, such as on a satellite. For example, WiFi and other standards use the term "access point." As another example, the 3rd Generation Partnership Project (3GPP) has produced specifications for three generations of mobile networks, each using different terminology. Third-generation (3G) and / or Universal Mobile Telecommunications System (UMTS) standards can use the term "node B." 4G, Long Term Evolution (LTE), and / or Evolved Universal Terrestrial Radio Access (E-UTRA) standards can use the term "eNB." 5G and / or New Radio (NR) standards can describe AN 102 as a Next Generation Radio Access Network (NG-RAN) and can refer to the base station as a Next Generation eNB (ng-eNB) and / or gNB (Generation Node B). Future standards (e.g., 6G, 7G, 8G) may use new terminology to refer to elements (e.g., wireless devices, base stations, ANs, CNs, and / or components thereof) that implement the methods described in this disclosure. A base station may be implemented as a repeater or relay node for extending the coverage area of ​​a donor node. A repeater node may amplify and replay radio signals received from a donor node. A relay node may perform the same / similar functions as a repeater node, but may decode radio signals received from a donor node to remove noise before amplifying and replaying the radio signals.

[0054] AN 102 may include one or more base stations, each having one or more coverage areas. The geographical size and / or extent of the coverage area may be defined by the range in which a receiver of AN 102 can successfully receive transmissions from a transmitter (e.g., wireless device 101) operating within the coverage area (and / or vice versa). The coverage area may be referred to as a zone or cell (but in some contexts, the term cell refers to the carrier frequency used in a particular coverage area, rather than the coverage area itself). A base station with a large coverage area may be referred to as a macrocell base station. Other base stations cover smaller areas to provide coverage, for example, in areas with weak macrocell coverage, or to provide additional coverage in areas with high traffic (sometimes referred to as hotspots). Examples of small cell base stations, in descending order of coverage area, include: microcell base stations, picocell base stations, and femtocell base stations or femtocell base stations. The coverage areas of the base stations may together provide wireless device 101 with wireless coverage over a wide geographical area to support wireless device mobility.

[0055] A base station may include one or more sets of antennas for communicating with wireless device 101 via an air interface. Each set of antennas may be controlled independently by the base station. Each set of antennas may have a corresponding coverage area. As an example, a base station may include three sets of antennas to control three coverage areas on three different sides of the base station, respectively. The entire base station (and its corresponding antennas) may be deployed at a single location. Alternatively, a controller at a central location may control one or more sets of antennas at one or more distributed locations. The controller may be, for example, a baseband processing unit, which is part of a centralized or cloud RAN architecture. The baseband processing unit may be centralized in a cluster or virtualized. A set of antennas at distributed locations may be referred to as a remote radio head (RRH).

[0056] Figure 1B Another example communication network 150 is shown, in which embodiments of the present disclosure may be implemented. Communication network 150 may include, for example, a PLMN operated by a network operator. Figure 1B As shown, the communication network 150 includes a UE 151, a Next-Generation Radio Access Network (NG-RAN) 152, a 5G Core Network (5G-CN) 155, and one or more DNs 158. The NG-RAN 152 includes one or more base stations, shown as a Next-Generation Node B (gNB) 152A and a Next-Generation Evolved Node B (ng eNB) 152B. The 5G-CN 155 includes one or more network functions (NFs), which include control plane functions 155A and user plane functions 155B. The one or more DNs 158 may include public DNs (e.g., the Internet), private DNs, and / or carrier-internal DNs. (Relative to...) Figure 1A The corresponding components shown may represent specific implementations and / or terms.

[0057] The base station of NG-RAN 152 can connect to UE 151 via the Uu interface. The base stations of NG-RAN 152 can connect to each other via the Xn interface. The base station of NG-RAN 152 can connect to 5G CN 155 via the NG interface. The Uu interface may include an air interface. The NG and Xn interfaces may include air interfaces, or may consist of direct physical connections and / or indirect connections via an underlying transport network (e.g., an Internet Protocol (IP) transport network).

[0058] Each of the Uu, Xn, and NG interfaces can be associated with a protocol stack. The protocol stack can contain a user plane (UP) and a control plane (CP). Typically, user plane data can contain data about the user of UE 151, such as Internet content downloaded via a web browser application, sensor data uploaded via a tracking application, or email data transmitted to or from an email server. In contrast, control plane data can include signaling and messages that facilitate the packaging and routing of user plane data so that it can be exchanged with the DN. For example, the NG interface can be divided into an NG user plane interface (NG-U) and an NG control plane interface (NG-C). The NG-U interface provides delivery of user plane data between the base station and one or more user plane network functions 155B. The NG-C interface can be used for control signaling between the base station and one or more control plane network functions 155A. The NG-C interface can provide, for example, NG interface management, UE context management, UE mobility management, NAS message delivery, paging, PDU session management, and configuration delivery and / or warning message transmission. In some cases, the NG-C interface can support the transmission of user data (e.g., small data transfers for IoT devices).

[0059] One or more NG-RAN 152 base stations can be split into a Central Unit (CU) and one or more Distribution Units (DUs). A CU can be connected to one or more DUs via an F1 interface. A CU can handle one or more upper layers of the protocol stack, and a DU can handle one or more lower layers of the protocol stack. For example, a CU can handle RRC, PDCP, and SDAP, while a DU can handle RLC, MAC, and PHY. The one or more DUs can be located geographically disparately from the CU and / or from each other. Accordingly, the CU / DU split architecture allows for increased coverage and / or better coordination.

[0060] The gNB 152A and ng-eNB 152B can provide different user plane and control plane protocol terminations for UE 151. For example, the gNB 154A can provide New Radio (NR) protocol termination via the Uu interface associated with the first protocol stack. The ng-eNB 152B can provide Evolved UMTS Terrestrial Radio Access (E-UTRA) protocol termination via the Uu interface associated with the second protocol stack.

[0061] The 5G-CN 155 can authenticate UE 151, establish an end-to-end connection between UE 151 and one or more DNs 158, and provide billing functionality. The 5G-CN 155 can be based on a service-based architecture, wherein the NFs comprising the 5G-CN 155 provide services to each other via interfaces and to other elements of the communication network 150. The 5G-CN 155 can contain any number of other NFs and any number of instances of each NF.

[0062] Figure 2A , Figure 2B , Figure 2C and Figure 2D Various examples of service-based architecture frameworks are shown within the core network. In a service-based architecture, service consumers can seek services, which are then provided by service producers. Before obtaining a specific service, an NF can determine where this service is available. To discover services, an NF can communicate with a Network Repository Function (NRF). As an example, an NF providing one or more services can register with the Network Repository Function (NRF). The NRF can store data related to the one or more services that an NF is prepared to provide to other NFs in the service-based architecture. A consumer NF can query the NRF to discover producer NFs (e.g., by obtaining a list of NF instances providing a specific service from the NRF).

[0063] exist Figure 2A In the example, NF 211 (in this example, the consumer NF) may send request 221 to NF 212 (the producer NF). Request 221 may be a request for a specific service and may be sent based on the discovery that NF 212 is a producer of said service. Request 221 may include data related to NF 211 and / or the requested service. NF 212 may receive request 221, perform one or more actions (e.g., retrieve data) associated with the requested service, and provide response 221. The one or more actions performed by NF 212 may be based on request data contained in request 221, data stored by NF 212, and / or data retrieved by NF 212. Response 222 may notify NF 211 that the one or more actions have been completed. Response 222 may include response data related to NF 212, the one or more actions, and / or the requested service.

[0064] exist Figure 2B In the example, NF 231 sends request 241 to NF 232. In this example, part of the service provided by NF 232 will be sending request 242 to NF 233. NF 233 may perform one or more actions and provide response 243 to NF 232. Based on response 243, NF 232 may send response 244 to NF 231. Figure 2B It will be understood that a single NF can perform the roles of service producer, service consumer, or both. A particular NF service can contain any number of nested NF services generated by one or more other NFs.

[0065] Figure 2C This illustrates an example of a subscription-notification interaction between a consumer NF and a producer NF. Figure 2C In this context, NF 251 sends subscription 261 to NF 252. NF 253 sends subscription 262 to NF 252. For illustrative purposes... Figure 2C The diagram illustrates two NFs (to demonstrate that NF 252 can provide multiple subscription services to different NFs), but it should be understood that a subscription-notification interaction requires only one subscriber. NFs 251 and 253 can operate independently of each other. For example, NFs 251 and 253 can independently discover NF 252 and / or independently determine which services are subscribed to by NF 252. In response to receiving a subscription, NF 252 can provide a notification to the subscribing NF. For example, NF 252 can send notification 263 to NF 251 based on subscription 261, and can send notification 264 to NF 253 based on subscription 262.

[0066] like Figure 2C As illustrated in the example diagram, the sending of notifications 263 and 264 may be based on the determination that a certain condition has occurred. For example, notifications 263 and 264 may be based on the determination that a specific event has occurred, the determination that a specific condition is pending, and / or the determination that the duration associated with the subscription has elapsed (e.g., the period associated with a subscription for periodic notifications). Figure 2C As illustrated in the example diagram, NF 252 may send notifications 263 and 264 to NF 251 and 253 simultaneously and / or in response to the same condition. However, it should be understood that NF 252 may provide notifications at different times and / or in response to different notification conditions. In the example, NF 251 may request notification if a specific parameter measured by NF 252 exceeds a first threshold, and NF 252 may request notification if said parameter exceeds a second threshold different from the first threshold. In the example, the parameter of interest and / or the corresponding threshold may be indicated in subscriptions 261 and 262.

[0067] Figure 2D This shows another example of a subscription-notification interaction. Figure 2D In this context, NF 271 sends subscription 281 to NF 272. In response to receiving subscription 281 and / or determining that a notification condition has occurred, NF 272 may send notification 284. Notification 284 may be sent to NF 273. Unlike... Figure 2C Example in the image (where notifications are sent to the subscribed NF), Figure 2DDisplays, subscriptions, and their corresponding notifications can be associated with different NFs. For example, NF 271 can subscribe to services provided by NF 272 on behalf of NF 273.

[0068] Figure 3 Another example communication network 300 in which embodiments of the present disclosure may be implemented is shown. The communication network 300 includes a user equipment (UE) 301, an access network (AN) 302, and a data network (DN) 308. Figure 3 The remaining elements described herein may be included in and / or associated with the core network. Each element of the core network may be referred to as a network function (NF).

[0069] Figure 3 The NFs described herein include User Plane Functions (UPF) 305, Access and Mobility Management Functions (AMF) 312, Session Management Functions (SMF) 314, Policy Control Functions (PCF) 320, Network Repository Functions (NRF) 330, Network Openness Functions (NEF) 340, Unified Data Management (UDM) 350, Authentication Server Functions (AUSF) 360, Network Slice Selection Functions (NSSF) 370, Charging Functions (CHF) 380, Network Data Analysis Functions (NWDAF) 390, and Application Functions (AF) 399. UPF 305 can be a user plane core network function, while NFs 312, 314, and 320-390 can be control plane core network functions. Although... Figure 3 Not illustrated in the examples, the core network may contain additional instances of the depicted NF and / or any of one or more different NF types providing different services. Other examples of NF types include Gateway Mobility Location Center (GMLC), Location Management Function (LMF), Operations, Administration and Maintenance Function (OAM), Public Alert System (PWS), Short Message Service Function (SMSF), Unified Data Repository (UDR), and Unstructured Data Storage Function (UDSF).

[0070] Figure 3 Each element depicted has an interface with at least one other element. This interface can be a logical connection, rather than, for example, a direct physical connection. Any interface can be identified using reference point representation and / or service-based representation. In reference point representation, the letter 'N' followed by a number indicates the interface between two specific elements. For example, such as... Figure 3As shown, AN 302 and UPF 305 are interfaced via 'N3', while UPF 305 and DN 308 are interfaced via 'N6'. In contrast, in the service-based representation, the letter 'N' is followed by a letter. This letter identifies the NF providing the service to the core network. For example, PCF 320 may provide services via interface 'Npcf'. PCF 320 may provide services to any NF in the core network via 'Npcf'. Accordingly, the service-based representation may correspond to a set of reference point representations. For example, the Npcf interface between PCF 320 and the core network may typically correspond to the N7 interface between PCF 320 and SMF 314, the N30 interface between PCF 320 and NEF 340, and so on.

[0071] UPF 305 can act as a gateway for user plane services between AN 302 and DN 308. UE 301 can connect to UPF 305 via the Uu interface and the N3 interface (also described as the NG-U interface). UPF 305 can connect to DN 308 via the N6 interface. UPF 305 can connect to one or more other UPFs (not shown) via the N9 interface. UE 301 can be configured to receive services via Protocol Data Unit (PDU) sessions, which are the logical connection between UE 301 and DN 308. UPF 305 (or, as needed, multiple UPFs) can be selected by SMF 314 to handle a specific PDU session between UE 301 and DN 308. SMF 314 can control the functionality of UPF 305 relative to the PDU session. SMF 314 can connect to UPF 305 via the N4 interface. UPF 305 can handle any number of PDU sessions (via any number of ANs) associated with any number of UEs. For the purpose of handling the one or more PDU sessions, the UPF 305 can be controlled by any number of SMFs via any number of corresponding N4 interfaces.

[0072] Figure 3 The AMF 312, as depicted, controls the UE's access to the core network. UE 301 can register with the network via the AMF 312. UE 301 may need to register before establishing a PDU session. The AMF 312 manages the UE 301's registration area, enabling the network to track the UE 301's physical location within the network. For UEs in connected mode, the AMF 312 manages UE movement, such as handover from one AN or part thereof to another AN. For UEs in idle mode, the AMF 312 performs registration updates and / or paging the UE to transition it to connected mode.

[0073] AMF 312 can receive Non-Access Plane (NAS) messages transmitted from UE 301 according to the NAS protocol. NAS messages pertain to communication between UE 301 and the core network. Although NAS messages may be relayed to AMF 312 via AN 302, they can be described as communication via the N1 interface. NAS messages can facilitate UE registration and mobility management, for example, by authenticating, identifying, configuring, and / or managing UE 301's connectivity. NAS messages can support session management procedures for maintaining user plane connectivity and Quality of Service (QoS) of the session between UE 301 and DN 309. If the NAS message pertains to session management, AMF 312 can send the NAS message to SMF 314. NAS messages can be used to transmit messages between UE 301 and other components of the core network (e.g., core network components other than AMF 312 and SMF 314). AMF 312 can act on a specific NAS message itself or forward the NAS message to the appropriate core network function (e.g., SMF 314, etc.).

[0074] Figure 3 The SMF 314 described herein can establish, modify, and / or publish PDU sessions based on message reception and delivery received at UE 301. The SMF 314 can, for example, allocate, manage, and / or assign IP addresses to UE 301 after a PDU session is established. Multiple SMFs may exist in the network, each associated with a corresponding group of radio devices, base stations, and / or UPFs. A UE with multiple PDU sessions can be associated with a different SMF for each PDU session. As described above, the SMF 314 can select one or more UPFs to handle PDU sessions, and can control the selected UPF's handling of PDU sessions by providing rules (PDR, FAR, QER, etc.) for packet processing. Rules related to the QoS and / or charging of a specific PDU session can be obtained from PCF 320 and provided to UPF 305.

[0075] The PCF 320 can provide services related to policy rules to other NFs. The PCF 320 can use subscription data and information about network conditions to determine policy rules, and then provide these policy rules to specific NFs that can be responsible for enforcing them. Policy rules may relate to policy control for access and mobility, and can be enforced by the AMF. Policy rules may relate to session management, and can be enforced by the SMF 314. Policy rules can be, for example, network-specific, radio device-specific, session-specific, or data stream-specific.

[0076] The NRF 330 can provide service discovery. The NRF 330 may belong to a specific PLMN. The NRF 330 can maintain NF profiles related to other NFs in the communication network 300. The NF profile may contain, for example, the NF's address, PLMN and / or type, slice identifier, a list of one or more services provided by the NF, and the authorization required to access the service.

[0077] Figure 3 The NEF 340 depicted herein provides an interface to an external domain, allowing the external domain to selectively access the control plane of the communication network 300. The external domain may include, for example, third-party network functions, application functions, etc. The NEF 340 can act as a proxy between external components and network functions such as AMF 312, SMF 314, PCF 320, UDM 350, etc. As an example, the NEF 340 can determine the location or reachability status of the UE 301 based on reports from the AMF 312 and provide this status information to the external component. As an example, the external component can provide information via the NEF 340 to facilitate the setting of parameters used to establish a PDU session. The NEF 340 can determine which control plane data and capabilities are exposed to the external domain. The NEF 340 can provide secure exposure, which authenticates and / or authorizes the data or capabilities of the communication network 300 to be exposed to external entities. The NEF 340 can selectively control exposure, allowing the internal architecture of the core network to be hidden from the external domain.

[0078] The UDM 350 can provide data storage for other NFs. The UDM 350 allows for a consolidated view of network information, which can be used to ensure that most relevant information is available to different NFs from a single resource. The UDM 350 can store and / or retrieve information from the Unified Data Repository (UDR). For example, the UDM 350 can obtain user subscription data related to UE 301 from the UDR.

[0079] AUSF 360 supports authentication of UE 301 by the mutual core network and authentication of the core network by UE 301. AUSF 360 can execute key agreement procedures and provide key materials that can be used to improve security.

[0080] The NSSF 370 can select one or more network slices to be used by the UE 301. The NSSF 370 can select a slice based on slice selection information. For example, the NSSF 370 can receive a single network slice selection assistance information (S-NSSAI) and map the S-NSSAI to a network slice instance identifier (NSI).

[0081] CHF 380 can control billing-related tasks associated with UE 301. For example, UPF 305 can report service usage associated with UE 301 to SMF 314. SMF 314 can collect usage data from UPF 305 and one or more other UPFs. Usage data may indicate how much data is exchanged, with which DN is data exchanged, the network slice associated with the data, or any other information that may affect billing. SMF 314 can share the collected usage data with CHF. CHF can use the collected usage data to perform billing-related tasks associated with UE 301. CHF may, depending on the billing status of UE 301, instruct SMF 314 to restrict or affect UE 301's access and / or provide billing-related notifications to UE 301.

[0082] The NWDAF 390 can collect and analyze data from other network functions and provide data analytics services to those functions. For example, the NWDAF 390 can collect data related to the load levels of specific network slice instances from UPF 305, AMF 312, and / or SMF 314. Based on the collected data, the NWDAF 390 can provide load level data to PCF 320 and / or NSSF 370, and / or notify PCF 320 and / or NSSF 370 slices whether their load levels have reached and / or exceeded load level thresholds.

[0083] AF 399 can operate outside the core network but can interact with it to provide information about QoS requirements or service routing preferences associated with specific applications. AF 399 can access the core network based on the open constraints imposed by NEF 340. However, the core network operator can treat AF 399 as a trusted domain with direct network access.

[0084] Figure 4A , 4B And 5 show similarities in some aspects Figure 3 Other examples of the core network architecture of the core network architecture 300 described herein are omitted for brevity. Figure 3 Some of the core network components described in the document. Figure 4A , 4B Many of the elements depicted in 5 are similar in some respects to Figure 3 The components depicted are shown in the image. For the sake of brevity, some details related to their function or operation have been omitted.

[0085] Figure 4AAn example of a core network architecture 400A is shown, comprising an arrangement of multiple UPFs. The core network architecture 400A includes UE 401, AN 402, AMF 412, and SMF 414. This differs from the previous example of the core network architecture described above. Figure 4A This describes multiple UPFs, including UPF 405, UPF 406, and UPF 407, and multiple DNs, including DN 408 and DN 409. Each of the multiple UPFs 405, 406, and 407 can communicate with the SMF 414 via the N4 interface. DNs 408 and 409 communicate with UPFs 405 and 406, respectively, via the N6 interface. Figure 4A As shown, multiple UPF 405, 406, and 407 can communicate with each other via the N9 interface.

[0086] UPF 405, 406, and 407 can perform service detection, whereby the UPF identifies and / or classifies packets. Packet identification can be performed based on Packet Detection Rules (PDRs) provided by SMF 414. A PDR may contain packet detection information including one or more of the following: source interface, UE IP address, core network (CN) tunnel information (e.g., the CN address corresponding to the N3 / N9 tunnel of a PDU session), network instance identifier, Quality of Service Flow Identifier (QFI), filter set (e.g., IP packet filter set or Ethernet packet filter set), and / or application identifier.

[0087] In addition to indicating how a specific packet will be detected, the PDR may further indicate the rules for processing the packet after it has been detected. These rules may include, for example, Forwarding Action (FAR) rules, Multiple Access (MAR) rules, Usage Reporting (URR) rules, QoS Enforcement (QER) rules, etc. For instance, the PDR may include one or more FAR identifiers, MAR identifiers, URR identifiers, and / or QER identifiers. These identifiers indicate the rules specified for processing the specific detected packet.

[0088] UPF 405 can perform traffic forwarding based on FAR. For example, FAR can instruct packets associated with a specific PDR to be forwarded, copied, dropped, and / or buffered. FAR can instruct the destination interface, such as "access" for downlink or "core" for uplink. If packets will be buffered, FAR can instruct a Buffer Action Rule (BAR). As an example, UPF 405 can perform data buffering of a specific number of downlink packets upon termination of the PDU session.

[0089] The UPF 405 can perform QoS enforcement based on a QER. For example, a QER can indicate an authorized guaranteed bit rate and / or a maximum bit rate to be enforced for packets associated with a particular PDR. The QER can indicate that a specific guaranteed and / or maximum bit rate is available for uplink and / or downlink packets. The UPF 405 can use a corresponding QFI to mark packets belonging to a specific QoS flow. This marking enables the packet receiver to determine the packet's QoS.

[0090] UPF 405 can provide usage reports to SMF 414 according to URRs. URRs can indicate one or more triggering conditions for the generation and reporting of usage reports, such as immediate reporting, periodic reporting, thresholds for incoming uplink traffic, or any other suitable triggering conditions. URRs can indicate methods for measuring network resource usage, such as data volume, duration, and / or events.

[0091] As described above, DNs 408 and 409 may include public DNs (e.g., the Internet), private DNs (e.g., dedicated, internally owned DNs), and / or carrier-owned DNs. Each DN can provide carrier services and / or third-party services. The services provided by the DN may be the Internet, IP Multimedia Subsystem (IMS), augmented or virtual reality networks, edge computing or mobile edge computing (MEC) networks, etc. Each DN can be identified using a Data Network Name (DNN). UE 401 can be configured to establish a first logical connection with DN 408 (first PDU session), a second logical connection with DN 409 (second PDU session), or both simultaneously (first and second PDU sessions).

[0092] Each PDU session may be associated with at least one UPF configured to operate as a PDU session anchor (PSA or "anchor"). The anchor may be a UPF that provides an N6 interface to the DN.

[0093] exist Figure 4AIn the example, UPF 405 could be an anchor for a first PDU session between UE 401 and DN 408, while UPF 406 could be an anchor for a second PDU session between UE 401 and DN 409. The core network can use anchors to provide service continuity (e.g., IP address continuity) for a specific PDU session as UE 401 moves from one access network to another. For example, suppose UE 401 establishes a PDU session using a data path to DN408 from an access network other than AN 402. The data path may include UPF 405, which acts as an anchor. Further suppose UE 401 later moves to the coverage area of ​​AN 402. In this scenario, SMF 414 can select a new UPF (UPF 407) to bridge the gap between the newly entered access network (AN 402) and the anchor UPF (UPF 405). The continuity of the PDU session can be maintained by adding or removing any number of UPFs from the data path. When a UPF is added to the data path, such as... Figure 4A As shown, it can be described as an intermediate UPF and / or a cascaded UPF.

[0094] As mentioned above, UPF 406 can be an anchor for a second PDU session between UE 401 and DN 409. Although Figure 4A The anchors used for the first and second PDU sessions are associated with different UPFs, but it should be understood that this is only an example. It will also be understood that multiple PDU sessions with a single DN can correspond to any number of anchors. When multiple UPFs exist, the UPF at the branch point (UPF 407 in Figure 4) can operate as an uplink classifier (UL-CL). UL-CL allows uplink user plane traffic to be offloaded to different UPFs.

[0095] SMF 414 can, for example, allocate, manage, and / or assign IP addresses to UE 401 after a PDU session is established. SMF 414 can maintain an internal set of IP addresses to be assigned. If necessary, SMF 414 can assign IP addresses provided by a Dynamic Host Configuration Protocol (DHCP) server or an Authentication, Authorization, and Accounting (AAA) server. IP address management can be performed according to Session and Service Continuity (SSC) modes. In SSC mode 1, the IP address of UE 401 can be maintained as the wireless device moves within the network (and the same anchor UPF can be used). In SSC mode 2, the IP address of UE 401 changes as UE 401 moves within the network (e.g., the old IP address and UPF can be discarded, and a new IP address and anchor UPF can be established). In SSC mode 3, it is possible to temporarily maintain the old IP address (similar to SSC mode 1) when a new IP address is established (similar to SSC mode 2), thus combining features of SSC modes 1 and 2. Applications sensitive to IP address changes can operate according to SSC mode 1.

[0096] UPF selection can be controlled by SMF 414. For example, after establishing and / or modifying a PDU session between UE 401 and DN 408, SMF 414 can select UPF 405 as the anchor for the PDU session and / or select UPF 407 as an intermediate UPF. Criteria for UPF selection include path efficiency and / or speed between AN 402 and DN 408. Reliability, load status, location, slicing support, and / or other capabilities of the candidate UPFs may also be considered.

[0097] Figure 4B This illustrates an example of a core network architecture 400B adapted for untrusted access. Similar to... Figure 4A ,like Figure 4B The UE 401 depicted is connected to DN 408 via AN 402 and UPF 405. AN 402 and UPF 405 constitute a trusted (e.g., 3GPP) access to DN 408. In contrast, UE 401 can also access DN 408 using an untrusted access network, AN 403, and the non-3GPP network interoperability function (N3IWF) 404.

[0098] AN 403 can be, for example, a Wireless Land Area Network (WLAN) operating according to the IEEE 802.11 standard. UE 401 can connect to AN 403 via interface Y1 in any way specified for AN 403. The connection to AN 403 may or may not involve authentication. UE 401 can obtain an IP address from AN 403. UE 401 can determine to connect to core network 400B and select untrusted access for this purpose. AN 403 can communicate with N3IWF 404 via interface Y2. After selecting untrusted access, UE 401 can provide N3IWF 404 with sufficient information to select an AMF. The selected AMF can be, for example, the same AMF used by UE 401 for 3GPP access (in this example, AMF 412). N3IWF 404 can communicate with AMF 412 via interface N2. UPF 405 can be selected, and N3IWF 404 can communicate with UPF 405 via the N3 interface. UPF 405 can be a PDU session anchor (PSA) and remains an anchor for the PDU session even as UE 401 switches between trusted and untrusted access.

[0099] Figure 5 An example of a core network architecture 500 in which UE 501 is in a roaming scenario is shown. In the roaming scenario, UE 501 is a subscriber to a first PLMN (Home PLMN or HPLMN) but attached to a second PLMN (Visit PLMN or VPLMN). The core network architecture 500 includes UE 501, AN 502, UPF 505, and DN 508. AN 502 and UPF 505 may be associated with a VPLMN. The VPLMN can manage AN 502 and UPF 505 using core network elements associated with the VPLMN, including AMF 512, SMF 514, PCF 520, NRF 530, NEF 540, and NSSF 570. AF 599 may be adjacent to the VPLMN's core network.

[0100] UE 501 may not be a VPLMN subscriber. AMF 512 may authorize UE 501 to access the network based on, for example, roaming restrictions imposed on UE 501. To obtain network services provided by the VPLMN, the VPLMN's core network may need to interact with the core network elements of UE 501's HPLMN, specifically PCF 521, NRF 531, NEF 541, UDM 551, and / or AUSF 561. The VPLMN and HPLMN can communicate using an N32 interface that connects to their respective Secure Edge Protection Agents (SEPPs). Figure 5In this context, the corresponding SEPPs are described as VSEPP 590 and HSEPP 591.

[0101] VSEPP 590 and HSEPP 591 communicate via the N32 interface for defined purposes, while hiding information about each PLMN from another PLMN. SEPP can apply roaming policies based on communications via the N32 interface. PCF 520 and PCF521 can communicate via SEPP to exchange policy-related signaling. NRF 530 and NRF 531 can communicate via SEPP to enable service discovery for NFs in their respective PLMNs. VPLMN and HPLMN can independently maintain NEF 540 and NEF 541. NSSF 570 and NSSF571 can communicate via SEPP to coordinate slice selection for UE 501. HPLMN handles all authentication and subscription-related signaling. For example, when UE 501 registers or requests service via VPLMN, VPLMN can authenticate UE 501 and / or obtain UE 501's subscription data by accessing HPLMN via SEPP's UDM 551 and AUSF 561.

[0102] Figure 5 The core network architecture 500 described can be referred to as a local breakout configuration, where UE 501 accesses DN 508 using one or more UPFs (i.e., UPF 505) of the VPLMN. However, other configurations are possible. For example, in a home-routed configuration ( Figure 5 (Not shown in the diagram) UE 501 can access the DN using one or more UPFs of the HPLMN. In the home routing configuration, the N9 interface can operate in parallel with the N32 interface, crossing the boundary between the VPLMN and HPLMN to carry user plane data. One or more SMFs of the corresponding PLMN can communicate via the N32 interface to coordinate session management for UE 501. The SMF can control its corresponding UPF on either side of the boundary.

[0103] Figure 6 An example of network slicing is shown. Network slicing can refer to dividing shared infrastructure (e.g., physical infrastructure) into distinct logical networks. These distinct logical networks can be controlled independently, isolated from each other, and / or associated with dedicated resources.

[0104] Network architecture 600A illustrates a non-sliced ​​physical network corresponding to a single logical network. Network architecture 600A includes a user plane, where UEs 601A, 601B, and 601C (collectively referred to as UE 601) have physical and logical connections to DN 608 via AN 602 and UPF 605. Network architecture 600A also includes a control plane, where AMF 612 and SMF 614 control various aspects of the user plane.

[0105] Network architecture 600A may have a specific set of characteristics (e.g., related to maximum bit rate, reliability, latency, bandwidth usage, power consumption, etc.). This set of characteristics may be influenced by the nature of the network elements themselves (e.g., processing power, availability of free memory, proximity to other network elements, etc.) or by their management (e.g., optimization to maximize bit rate or reliability, reduce latency or power bandwidth usage, etc.). The characteristics of network architecture 600A may change over time, for example, by upgrading equipment or by modifying procedures to target specific characteristics. However, at any given time, network architecture 600A will have a single set of characteristics that may or may not be optimized for a specific use case. For example, UEs 601A, 601B, and 601C may have different requirements, but network architecture 600A may be optimized for only one of the three.

[0106] Network Architecture 600B is an example of a sliced ​​physical network divided into multiple logical networks. Figure 6 In this configuration, the physical network is divided into three logical networks, called slice A, slice B, and slice C. For example, UE 601A can be served by AN 602A, UPF 605A, AMF 612, and SMF 614A. UE 601B can be served by AN 602B, UPF 605B, AMF 612, and SMF 614B. UE 601C can be served by AN 602C, UPF 605C, AMF 612, and SMF 614C. Although logically the corresponding UE 601 communicates with different network elements, these network elements can be deployed by the network operator using the same physical network elements.

[0107] Each network slice can be customized for network services with a different set of characteristics. For example, slice A could correspond to enhanced mobile broadband (eMBB) service. Mobile broadband refers to internet access typically associated with mobile users and smartphones. Slice B could correspond to ultra-reliable low-latency communication (URLLC), which focuses on reliability and speed. Compared to eMBB, URLLC improves the feasibility of use cases such as autonomous driving and remote surgery. Slice C could correspond to massive machine-type communication (mMTC), which focuses on low-power services delivered to a large number of users. For example, slice C could be optimized for dense networks of battery-powered sensors that provide small amounts of data at regular intervals. Many mMTC use cases would be prohibitively expensive to operate using eMBB or URLLC networks.

[0108] If the service requirements for one of UE 601 change, the network slice for the UE service can be updated to provide better service. Furthermore, the set of network characteristics corresponding to eMBB, URLLC, and mMTC can vary, enabling the provision of differentiated types of eMBB, URLLC, and mMTC. Alternatively, network operators can provide entirely new services in response to, for example, customer demands.

[0109] Figure 6 In example UE 601, each UE has its own network slice. However, it should be understood that a single slice can serve any number of UEs, and a single UE can use any number of slices for operation. Furthermore, in example network architecture 600B, AN602, UPF 605, and SMF 614 are divided into three separate slices, while AMF 612 is non-sliced. However, it should be understood that network operators can deploy any architecture that selectively utilizes any mixture of sliced ​​and non-sliced ​​network elements, where different network elements are divided into different numbers of slices. Although... Figure 6 Only three core network functions are described, but it should be understood that other core network functions can also be sliced. A PLMN that supports multiple network slices can maintain a separate Network Repository Function (NFR) for each slice, enabling other NFs to discover network services associated with said slice.

[0110] Network slice selection can be controlled by the AMF or by a separate Network Slice Selection Function (NSSF). For example, the network operator can define and implement distinct Network Slice Instances (NSIs). Each NSI can be associated with a single Network Slice Selection Assistance Information (S-NSSAI). The S-NSSAI can contain a specific slice / service type (SST) indicator (indicating eMBB, URLLC, mMTC, etc.). As an example, a specific tracking area can be associated with one or more configured S-NSSAIs. The UE can identify one or more requested and / or subscribed S-NSSAIs (e.g., during registration). The network can indicate one or more allowed and / or denied S-NSSAIs to the UE.

[0111] S-NSSAI may further include a slice distinguisher (SD) to differentiate between different tenants for a specific slice and / or service type. For example, a tenant could be a customer of a network operator (e.g., a vehicle manufacturer, service provider, etc.) that obtains (e.g., purchases) guaranteed network resources and / or specific policies for processing its subscribers. The network operator can configure different slices and / or slice types and use the SD to determine which tenant is associated with a specific slice.

[0112] Figure 7A , Figure 7B and Figure 7C This shows the user plane (UP) protocol stack, the control plane (CP) protocol stack, and the services between the protocol layers set up in the UP protocol stack.

[0113] The layers can be associated with the Open Systems Interconnection (OSI) model, which describes the functionality of computer networking. In the OSI model, Layer 1 may correspond to the bottom layer, with higher layers on top of the bottom layer. Layer 1 may correspond to the physical layer, which relates to the physical infrastructure (e.g., cables, optical fibers, and / or radio frequency transceivers) used to transmit signals. In New Radio (NR), Layer 1 may include the Physical Layer (PHY). Layer 2 may correspond to the Data Link Layer. Layer 2 may relate to the physical infrastructure that packages data (e.g., data frames) for transmission between nodes in the network using Layer 1. In NR, Layer 2 may include the Media Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Layer (PDCP) layer, and Service Data Application Protocol (SDAP) layer.

[0114] Layer 3 may correspond to the network layer. Layer 3 may relate to the routing of data already encapsulated in Layer 2. Layer 3 may handle the prioritization of data and traffic avoidance. In NR, Layer 3 may include the Radio Resource Control (RRC) layer and the Non-Access Layer (NAS) layer. Layers 4 through 7 may correspond to the transport layer, session layer, presentation layer, and application layer. The application layer interacts with the end user to provide application-related data. In the example, the end user implementing the application may generate application-related data and initiate the transmission of said information to a target data network (e.g., the Internet, application server, etc.). Starting at the application layer, each layer in the OSI model may manipulate and / or re-encapsulate information and deliver it to the next layer. At the lowest layer, manipulated and / or re-encapsulated information may be exchanged via physical infrastructure (e.g., electrically, optically, and / or electromagnetically). As it approaches the target data network, the information is decapsulated and provided to increasingly higher layers until it reaches the application layer again in a form available to the target data network (e.g., the same form it was provided by the end user). In response to end users, the data network can reverse-execute this procedure.

[0115] Figure 7A The user plane protocol stack is shown. The user plane protocol stack can be a New Radio (NR) protocol stack for the Uu interface between UE 701 and gNB 702. In layer 1 of the UP protocol stack, UE 701 can implement PHY 731 and gNB 702 can implement PHY 732. In layer 2 of the UP protocol stack, UE 701 can implement MAC 741, RLC 751, PDCP 761, and SDAP 771. gNB 702 can implement MAC 742, RLC 752, PDCP 762, and SDAP 772.

[0116] Figure 7B The control plane protocol stack is shown. The control plane protocol stack can be an NR protocol stack for the Uu interface between UE 701 and gNB 702 and / or the N1 interface between UE 701 and AMF 712. In layer 1 of the CP protocol stack, UE 701 can implement PHY 731 and gNB 702 can implement PHY 732. In layer 2 of the CP protocol stack, UE 701 can implement MAC 741, RLC 751, PDCP 761, RRC 781, and NAS 791. gNB 702 can implement MAC 742, RLC 752, PDCP 762, and RRC 782. AMF 712 can implement NAS 792.

[0117] NAS can relate to the non-access layer, specifically communication between UE 701 and the core network (e.g., AMF 712). Lower layers can relate to the access layer, such as communication between UE 701 and gNB 702. Messages sent between UE 701 and the core network can be referred to as NAS messages. In this example, NAS messages may be relayed by gNB 702, but the content of the NAS message (e.g., the information elements of the NAS message) may not be visible to gNB 702.

[0118] Figure 7C Showing the setting in Figure 7A The diagram illustrates an example of services between protocol layers of the NR user plane protocol stack. UE 701 can receive services via a PDU session, which can be a logical connection between UE 701 and a data network (DN). UE 701 and the DN can exchange data packets associated with the PDU session. The PDU session may include one or more Quality of Service (QoS) flows. SDAP 771 and SDAP 772 can perform mapping and / or demapping between the one or more QoS flows and one or more radio bearers (e.g., data radio bearers) of the PDU session. The mapping between QoS flows and data radio bearers can be determined by gNB 702 in SDAP 772 and can inform UE 701 of the mapping (e.g., based on control signaling and / or reflection mapping). For reflection mapping, SDAP 772 of gNB 220 can tag downlink packets with QoS Flow Indicators (QFIs) and deliver the downlink packets to UE 701. UE 701 can determine the mapping based on the QFI of the downlink packets.

[0119] PDCP 761 and PDCP 762 can perform header compression and / or decompression. Header compression reduces the amount of data transmitted at the physical layer. PDCP 761 and PDCP 762 can perform encryption and / or decryption. Encryption reduces unauthorized decoding of data transmitted at the physical layer (e.g., intercepted at the air interface) and protects data integrity (e.g., ensuring control messages originating from a designated source). PDCP 761 and PDCP 762 can perform retransmission of undelivered packets, packet delivery and reordering, packet duplication, and / or identification and removal of duplicate packets. In dual connectivity scenarios, PDCP 761 and PDCP 762 can perform splitting the mapping between radio bearers and RLC channels.

[0120] RLCs 751 and 752 can perform segmentation and retransmission via Automatic Repeat Request (ARQ). RLCs 751 and 752 can remove duplicate data units received from MACs 741 and 742, respectively. RLCs 213 and 223 can serve the RLC channel as a service to PDCPs 214 and 224, respectively.

[0121] MAC 741 and MAC 742 can perform multiplexing and / or demultiplexing of logical channels. MAC 741 and MAC 742 can map logical channels to transport channels. In the example, UE 701 can multiplex data elements of one or more logical channels into a transport block in MAC 741. UE 701 can use PHY 731 to transmit the transport block to gNB 702. gNB 702 can use PHY 732 to receive the transport block and demultiplex the data elements of the transport block back into the logical channels. MAC 741 and MAC 742 can perform error correction via Hybrid Automatic Repeat Request (HARQ), logical channel prioritization, and / or padding.

[0122] PHY 731 and PHY 732 can perform transmission channel to physical channel mapping. PHY 731 and PHY 732 can perform digital and analog signal processing functions (e.g., decoding / decoding and modulation / demodulation) for transmitting and receiving information (e.g., transmission via air interface). PHY 731 and PHY 732 can perform multi-antenna mapping.

[0123] Figure 8 An example of a Quality of Service (QoS) model for differentiated data exchange is shown. Figure 8 In the QoS models, there are UE 801, AN 802, and UPF 805. QoS models promote the prioritization of certain packets or Protocol Data Units (PDUs) (also known as packets). For example, higher priority packets can be exchanged faster and / or more reliably compared to lower priority packets. The network can allocate more resources to exchanging high QoS packets.

[0124] exist Figure 8 In the example, a PDU session 810 is established between UE 801 and UPF 805. PDU session 810 may be a logical connection enabling UE 801 to exchange data with a specific data network (e.g., the Internet). UE 801 may request the establishment of PDU session 810. When establishing PDU session 810, UE 801 may, for example, identify the target data network based on its Data Network Name (DNN). PDU session 810 may, for example, be managed by a Session Management Function (SMF, not shown). To facilitate the exchange of data associated with PDU session 810 between UE 801 and the data network, the SMF may select UPF 805 (and optionally, one or more other UPFs, not shown).

[0125] One or more applications associated with UE 801 may generate uplink packets 812A-812E associated with PDU session 810. To operate within the QoS model, UE 801 may apply QoS rule 814 to uplink packets 812A-812E. QoS rule 814 may be associated with PDU session 810 and may be determined and / or provided to UE 801 when PDU session 810 is established and / or modified. Based on QoS rule 814, UE 801 may classify uplink packets 812A-812E, mapping each of them to a QoS flow, and / or tagging uplink packets 812A-812E with a QoS flow indicator (QFI). As the packets travel through the network and potentially mix with other packets from other UEs with potentially different priorities, the QFI indicates how the packets should be processed according to the QoS model. In the current diagram, uplink packets 812A and 812B are mapped to QoS flow 816A, uplink packet 812C is mapped to QoS flow 816B, and the remaining packets are mapped to QoS flow 816C.

[0126] QoS flows can be the finest granular level of QoS differentiation within a PDU session. The diagram shows three QoS flows 816A-816C. However, it should be understood that any number of QoS flows can exist. Some QoS flows may be associated with a guaranteed bit rate (GBR QoS flow), while others may have a non-guaranteed bit rate (non-GBR QoS flow). QoS flows may also experience per-UE and per-session total bit rates. One of the QoS flows can be the default QoS flow. QoS flows can have different priorities. For example, QoS flow 816A may have a higher priority than QoS flow 816B, and QoS flow 816B may have a higher priority than QoS flow 816C. Different priorities can be reflected by different QoS flow characteristics. For example, QoS flows can be associated with a flow bit rate. A specific QoS flow can be associated with a guaranteed flow bit rate (GFBR) and / or a maximum flow bit rate (MFBR). A QoS flow can be associated with a specific packet delay budget (PDB), packet error rate (PER), and / or maximum packet loss rate. QoS flows can also experience total bit rates per UE and per session.

[0127] To function within the QoS model, UE 801 can apply resource mapping rule 818 to QoS flows 816A-816C. The air interface between UE 801 and AN 802 can be associated with resource 820. In the current illustration, QoS flow 816A is mapped to resource 820A, while QoS flows 816B and 816C are mapped to resource 820B. Resource mapping rule 818 can be provided by AN 802. To meet QoS requirements, resource mapping rule 818 can specify more resources for relatively high-priority QoS flows. With more resources, high-priority QoS flows, such as QoS flow 816A, are more likely to obtain high stream bit rates, low packet delay budgets, or other characteristics associated with QoS rule 814. Resource 820 may include, for example, radio bearers. Radio bearers (e.g., data radio bearers) can be established between UE 801 and AN 802. The 5G radio bearer between UE 801 and AN 802 may differ from the LTE bearer, such as the evolved packet system (EPS) bearer between the UE and the packet data network gateway (PGW), the S1 bearer between the eNB and the service gateway (SGW), and / or the S5 / S8 bearer between the SGW and the PGW.

[0128] Once a packet associated with a specific QoS flow is received at AN 802 via resource 820A or resource 820B, AN 802 separates the packet into the corresponding QoS flows 856A-856C based on QoS profile 828. QoS profile 828 may be received from the SMF. Each QoS profile may correspond to a QFI, such as the QFI marked on uplink packets 812A-812E. Each QoS profile may contain QoS parameters such as a 5G QoS identifier (5QI) and allocation and retention priority (ARP). QoS profiles for non-GBR QoS flows may further contain additional QoS parameters such as reflection QoS attributes (RQA). QoS profiles for GBR QoS flows may further contain additional QoS parameters such as guaranteed flow bit rate (GFBR), maximum flow bit rate (MFBR), and / or maximum packet loss rate. The 5QI may be a standardized 5QI with a one-to-one mapping from each well-known service to a standardized combination of 5G QoS features. 5QI can be dynamically assigned, and its standardized 5QI value is not defined. 5QI can represent 5G QoS characteristics. 5QI can include resource type, default priority, packet delay budget (PDB), packet error rate (PER), maximum data burst size, and / or average window. Resource type can indicate a non-GBR QoS flow, a GBR QoS flow, or a delay-critical GBR QoS flow. Average window can represent the duration experienced during the calculation of GFBR and / or MFBR. ARP can include priorities for preemption and preemption capabilities. Based on ARP, AN 802 can apply admission control to QoS flows under resource constraints.

[0129] AN 802 may select one or more N3 tunnels 850 for transmitting QoS flows 856A-856C. After the packets are segmented into QoS flows 856A-856C, the packets may be sent to UPF 805 (e.g., toward DN) via the selected one or more N3 tunnels 850. UPF 805 may verify that the QFI of uplink packets 812A-812E is aligned with QoS rule 814 provided to UE 801. UPF 805 may measure packets and / or count packets and / or provide packet metrics to, for example, PCF.

[0130] The diagram also illustrates the process used for the downlink. Specifically, one or more applications may generate downlink packets 852A-852E. UPF 805 may receive downlink packets 852A-852E from one or more DNs and / or one or more other UPFs. According to the QoS model, UPF 805 may apply Packet Detection Rule (PDR) 854 to downlink packets 852A-852E. Based on PDR 854, UPF 805 may map packets 852A-852E to QoS flows. In the current diagram, downlink packets 852A and 852B are mapped to QoS flow 856A, downlink packet 852C is mapped to QoS flow 856B, and the remaining packets are mapped to QoS flow 856C.

[0131] QoS flows 856A-856C can be sent to AN 802. AN 802 can apply resource mapping rules to QoS flows 856A-856C. In the current diagram, QoS flow 856A is mapped to resource 820A, while QoS flows 856B and 856C are mapped to resource 820B. To meet QoS requirements, resource mapping rules can specify more resources for high-priority QoS flows.

[0132] Figures 9A to 9D Example states and state transitions of a wireless device (e.g., a UE) are shown. At any given time, a wireless device may be in a Radio Resource Control (RRC) state, a Registration Management (RM) state, and a Connection Management (CM) state.

[0133] Figure 9A This is an example diagram illustrating the RRC state transitions of a wireless device (e.g., a UE). A UE may be in one of three RRC states: RRC Idle 910 (e.g., RRC_IDLE), RRC Inactive 920 (e.g., RRC_INACTIVE), or RRC Connected 930 (e.g., RRC_CONNECTED). A UE may implement different RAN-related control plane procedures depending on its RRC state. Other elements of the network (e.g., base stations) may track the RRC states of one or more UEs and implement RAN-related control plane procedures appropriate to each UE's RRC state.

[0134] In an RRC connection 930, it is possible for the UE to exchange data with the network (e.g., a base station). Parameters necessary for establishing this data exchange are known to both the UE and the network. These parameters may be mentioned and / or included in the UE's RRC context (sometimes referred to as the UE context). These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. The base station connected to the UE may store the UE's RRC context.

[0135] When in an RRC connection 930, the UE's mobility can be managed by the access network, while the UE itself can manage mobility when in an RRC idle 910 and / or RRC inactive 920. When in an RRC connection 930, the UE can manage mobility by measuring signal levels (e.g., reference signal levels) from the serving cell and neighboring cells and reporting these measurements to the base station currently serving the UE. The network can initiate a handover based on the reported measurements. The RRC state can transition from an RRC connection 930 to an RRC idle 910 via a connection release procedure 930, and to an RRC inactive 920 via a connection termination procedure 932.

[0136] In RRC idle 910, an RRC context may not be established for the UE. In RRC idle 910, the UE may not have an RRC connection with the base station. When in RRC idle 910, the UE may be in a dormant state most of the time (e.g., to conserve battery power). The UE may periodically wake up (e.g., once per discontinuous reception cycle) to monitor paging messages from the access network. The UE's mobility can be managed by the UE through a procedure called cell reselection. The RRC state can transition from RRC idle 910 to RRC connection 930 via connection establishment procedure 913, which may involve a random access procedure, as discussed in more detail below.

[0137] In RRC inactivity 920, the previously established RRC context is maintained in both the UE and the base station. This allows for a faster transition to RRC connection 930 with reduced signaling overhead compared to the transition from RRC idle 910 to RRC connected 930. The RRC state can be transitioned to RRC connected 930 via connection restoration procedure 923. The RRC state can be transitioned to RRC idle 910 via connection release procedure 921, which may be the same as or similar to connection release procedure 931.

[0138] RRC status can be associated with mobility management mechanisms. In RRC Idle 910 and RRC Inactive 920, mobility can be managed by the UE via cell reselection. The purpose of mobility management in RRC Idle 910 and / or RRC Inactive 920 is to allow the network to notify the UE of an event via a paging message, without having to broadcast the paging message across the entire mobile network. The mobility management mechanisms used in RRC Idle 910 and / or RRC Inactive 920 allow the network to track the UE at the cell-group level, enabling paging messages to be broadcast on cells within the cell group where the UE is currently camped, rather than across the entire network. Tracking can be based on different packet granularities. For example, there can be three levels of cell packet granularity: a single cell; cells within a RAN area identified by a RAN Area Identifier (RAI); and cells within a group of RAN areas referred to as a tracking area and identified by a Tracking Area Identifier (TAI).

[0139] A tracking area can be used to track the UE at the CN level. The CN can provide the UE with a list of TAIs associated with the UE's registration area. If the UE moves to a cell associated with a TAI not included in the list of TAIs associated with the UE's registration area via cell reselection, the UE can perform a registration update with the CN to allow the CN to update the UE's location and provide the UE with a new UE registration area.

[0140] RAN areas can be used to track UEs at the RAN level. For a UE in the RRC inactive 920 state, a RAN notification area can be assigned to that UE. A RAN notification area can include one or more cell identities, a list of RAIs, and / or a list of TAIs. In the example, a base station can belong to one or more RAN notification areas. In the example, a cell can belong to one or more RAN notification areas. If a UE moves via cell reselection to a cell not included in its assigned RAN notification area, the UE can perform a notification area update to update its RAN notification area.

[0141] The base station that stores the RRC context for the UE, or the UE's last serving base station, may be referred to as the anchor base station. The anchor base station may maintain the UE's RRC context at least during the time period during which the UE remains in the anchor base station's RAN notification area and / or during the time period during which the UE remains in RRC inactivity.

[0142] Figure 9B This is an example diagram illustrating the registration management (RM) state transitions of a wireless device (e.g., a UE). The state is RM deregistration 940 (e.g., RM-DEREGISTERED) and RM registration 950 (e.g., RM-REGISTERED).

[0143] In RM deregistration 940, the UE does not register with the network, and the network cannot reach the UE. To become reachable by the network, the UE must perform an initial registration. As an example, the UE may register with the network's AMF. If registration is rejected (registration rejection 944), the UE remains in RM deregistration 940. If registration is accepted (registration acceptance 945), the UE transitions to RM registration 950. While the UE is in RM registration 950, the network may store, maintain, and / or sustain the UE's UE context. The UE context may be referred to as the radio device context. The UE context corresponding to network registration (maintained by the core network) may differ from the RRC context corresponding to the RRC state (maintained by the access network, such as a base station). The UE context may include a record of the UE identifier and various information associated with the UE, such as UE capability information, policy information for UE access and mobility management, a list of allowed or established slices or PDU sessions, and / or the UE's registration area (i.e., a list of tracking areas covering the geographic area where radio devices are likely to be found).

[0144] When a UE is in RM Registration 950, the network can store the UE's UE context and use it to reach the UE when necessary. Furthermore, some services cannot be provided by the network unless the UE is registered. A UE can update its UE context while remaining in RM Registration 950 (Registration Update Acceptance 955). For example, if a UE leaves one tracking area and enters another, the UE can provide the tracking area identifier to the network. The network can deregister the UE, or the UE can deregister itself (Deregistration 954). For example, the network can automatically deregister a radio device if it remains inactive for a specific amount of time. After deregistration, the UE can proceed to RM Deregistration 940.

[0145] Figure 9C This is an example diagram illustrating the connection management (CM) state transitions of a wireless device (e.g., a UE) from the perspective of the wireless device. The UE may be in CM idle 960 (e.g., CM-IDLE) or CM connected 970 (e.g., CM-CONNECTED).

[0146] In CM idle 960, the UE does not have a Non-Access Layer (NAS) signaling connection with the network. Therefore, the UE may not communicate with core network functions. The UE can transition to CM connection 970 by establishing an AN signaling connection (AN signaling connection establishment 967). This transition can be initiated by sending an initial NAS message. The initial NAS message can be a registration request (e.g., if the UE is in RM deregistration 940) or a service request (e.g., if the UE is in RM registration 950). If the UE is in RM registration 950, the UE can initiate AN signaling connection establishment by sending a service request, or the network can send a paging message, thereby triggering the UE to send a service request.

[0147] In CM Connection 970, the UE can use NAS signaling to communicate with core network functions. As an example, the UE can exchange NAS signaling with the AMF for registration management purposes, service request procedures, and / or authentication procedures. As another example, the UE can exchange NAS signaling with the SMF to establish and / or modify PDU sessions. The network can disconnect the UE, or the UE can disconnect itself (AN signaling connection release 976). For example, if the UE transitions to RM Deregistration 940, the UE can also transition to CM Idle 960. When the UE transitions to CM Idle 960, the network can terminate the user plane connection of the UE's PDU session.

[0148] Figure 9D This is an example diagram illustrating the CM state transitions of a wireless device (e.g., UE) from a network perspective (e.g., AMF). The CM state of the UE tracked by the AMF can be either CM Idle 980 (e.g., CM-IDLE) or CM Connected 990 (e.g., CM-CONNECTED). When the UE transitions from CM Idle 980 to CM Connected 990, the AMF can establish the UE's N2 context (N2 context establishment 989). When the UE transitions from CM Connected 990 to CM Idle 980, the AMF can release the UE's N2 context (N2 context release 998).

[0149] Figure 10-12 Example procedures are shown for UE registration, service requests, and PDU session establishment.

[0150] Figure 10 An example of a registration procedure for a wireless device (e.g., a UE) is shown. Based on the registration procedure, the UE can transition from, for example, RM deregistration 940 to RM registration 950.

[0151] Registration can be initiated by the UE for purposes such as obtaining authorization to receive services, enabling mobility tracking, enabling reachability, or other purposes. The UE may perform initial registration as the first step in connecting to the network (e.g., when the UE is powered on, airplane mode is off, etc.). Registration can also be performed periodically to keep the network aware of the UE's presence (e.g., when in CM-IDLE state), or in response to changes in UE capabilities or registration area. Deregistration can be performed (…). Figure 10 (Not shown in the image) to stop network access.

[0152] At position 1010, the UE transmits a registration request to the AN. As an example, the UE may have moved from the coverage area of ​​a previous AMF (shown as AMF#1) to the coverage area of ​​a new AMF (shown as AMF#2). The registration request can be a NAS message. The registration request may contain the UE identifier. The AN may select an AMF for the UE's registration. For example, the AN may select a default AMF. For example, the AN may select an AMF already mapped to the UE (e.g., a previous AMF). The NAS registration request may contain a network slice identifier, and the AN may select an AMF based on the requested slice. After selecting an AMF, the AN may send the registration request to the selected AMF.

[0153] At position 1020, the AMF (AMF#2) receiving the registration request performs a context transfer. The context can be the UE context, such as the UE's RRC context. As an example, AMF#2 can send a message to AMF#1 requesting the UE's context. This message may contain the UE identifier. This message may be a Namf_Communication_UEContextTransfer message. AMF#1 can send a message to AMF#2 containing the requested UE context. This message may be a Namf_Communication_UEContextTransfer message. After receiving the UE context, AMF#2 can coordinate the UE's authentication. After authentication is complete, AMF#2 can send a message to AMF#1 indicating that the UE context transfer is complete. This message may be a Namf_Communication_UEContextTransfer response message.

[0154] Authentication may require the participation of the UE, AUSF, UDM, and / or UDR (not shown). For example, the AMF may request the AUSF to authenticate the UE. For example, the AUSF may perform UE authentication. For example, the AUSF may obtain authentication data from the UDM. For example, the AUSF may send a Subscription Permanent Identifier (SUPI) to the AMF based on successful authentication. For example, the AUSF may provide an intermediate key to the AMF. The intermediate key can be used to derive the UE's access-specific security key, enabling the AMF to perform Security Context Management (SCM). The AUSF may obtain subscription data from the UDM. Subscription data may be based on information obtained from the UDM (and / or UDR). Subscription data may include subscription identifiers, security credentials, access and mobility-related subscription data, and / or session-related data.

[0155] At point 1030, the new AMF (AMF#2) registers and / or subscribes to the UDM. AMF#2 can perform registration using the UDM's UE Context Management Service (Nudm_UECM). AMF#2 can obtain the UE's subscription information using the UDM's Subscriber Data Management Service (Nudm_SDM). AMF#2 can further request the UDM to notify AMF#2 whether the UE's subscription information has changed. With the new AMF registering and subscribing, the old AMF (AMF#1) can be deregistered and unsubscribed. After deregistration, AMF#1 no longer has responsibilities for UE mobility management.

[0156] At position 1040, AMF#2 retrieves Access and Mobility (AM) policies from the PCF. As an example, AMF#2 can provide the UE's subscription data to the PCF. The PCF can determine access and mobility policies for the UE based on the subscription data, network operator data, current network conditions, and / or other suitable information. For instance, the owner of a first UE may purchase a higher service tier than the owner of a second UE. The PCF can provide rules associated with different service tiers. Based on the respective UE's subscription data, the network can apply different policies that promote different service tiers.

[0157] For example, access and mobility policies may involve service area restrictions, RAT / Frequency Selection Priority (RFSP, where RAT stands for Radio Access Technology), authorization and prioritization of access type (e.g., LTE versus NR), and / or selection of non-3GPP access (e.g., Access Network Discovery and Selection Policy (ANDSP)). Service area restrictions may include a list of tracking areas in which service is permitted (or prohibited) for the UE. Access and mobility policies may include UE route selection policies (URSP) that affect the routing of established or new PDU sessions. As mentioned above, different policies may be obtained and / or implemented based on the UE's subscription data, the UE's location (i.e., the location of the AN and / or AMF), or other suitable factors.

[0158] At 1050, AMF#2 can update the context of the PDU session. For example, if the UE has an existing PDU session, AMF#2 can coordinate with the SMF to activate the user plane connection associated with the existing PDU session. The SMF can update and / or release the session management context of the PDU session (Nsmf_PDUSession_UpdateSMContext, Nsmf_PDUSession_ReleaseSMContext).

[0159] At position 1060, AMF#2 sends a registration accept message to the AN, which forwards the registration accept message to the UE. The registration accept message may contain a new UE identifier and / or a new configured slice identifier. The UE may transmit a registration complete message to the AN, which forwards the registration complete message to AMF#2. The registration complete message acknowledges receipt of the new UE identifier and / or the new configured slice identifier.

[0160] At position 1070, AMF#2 can obtain UE policy control information from the PCF. The PCF can provide Access Network Discovery and Selection Policy (ANDSP) to facilitate non-3GPP access. The PCF can provide UE Route Selection Policy (URSP) to facilitate the mapping of specific data services to specific PDU session connectivity parameters. As an example, URSP can indicate that data services associated with a specific application should be mapped to a specific SSC mode, network slice, PDU session type, or preferred access type (3GPP or non-3GPP).

[0161] Figure 11 An example of a service request procedure for a wireless device (e.g., a UE) is shown. Figure 11 The service request procedure described herein is a network-triggered service request procedure for UEs in CM-IDLE state. However, see also [reference needed]. Figure 11Learn about other service request procedures (e.g., UE-triggered service request procedures), which will be discussed in more detail below.

[0162] At 1110, the UPF receives data. The data may be downlink data for transmission to the UE. The data may be associated with an existing PDU session between the UE and the DN. The data may be received, for example, from the DN and / or another UPF. The UPF may buffer the received data. In response to receiving data, the UPF may notify the SMF of the received data. The identity of the SMF to be notified may be determined based on the received data. The notification may be, for example, an N4 session report. The notification may indicate that the UPF has received data associated with the UE and / or a specific PDU session associated with the UE. In response to receiving the notification, the SMF may send PDU session information to the AMF. The PDU session information may be sent in an N1N2 message pass for forwarding to the AN. The PDU session information may include, for example, UPF tunnel endpoint information and / or QoS information.

[0163] At 1120, the AMF determines that the UE is in CM-IDLE state. This determination at 1120 is made in response to the receipt of PDU session information. Based on the determination that the UE is in CM-IDLE, the service request procedure can proceed to 1130 and 1140, as follows... Figure 11 As described in the document. However, if the UE is not in CM-IDLE (e.g., the UE is in CM-CONNECTED), steps 1130 and 1140 can be skipped, and the service request procedure can proceed directly to step 1150.

[0164] At 1130, the AMF pages the UE. Paging at 1130 can be performed based on the UE being in CM-IDLE. To perform paging, the AMF can send the paging message to the AN. This paging may be referred to as a paging message or a paging request message. The paging message may be an N2 request message. The AN may be one of multiple ANs in the UE's RAN notification area. The AN can send the paging message to the UE. The UE may be within the coverage area of ​​the AN and may receive the paging message.

[0165] At point 1140, the UE can request service. The UE can transmit the service request to the AMF via the AN. For example... Figure 11 As described, the UE can request service at 1140 in response to receiving a paging at 1130. However, as mentioned above, this is a specific case for a network-triggered service request procedure. In some scenarios (e.g., if uplink data becomes available at the UE), the UE can initiate a UE-triggered service request procedure. A UE-triggered service request procedure can begin at 1140.

[0166] At 1150, the network can authenticate the UE. Authentication may require the participation of the UE, AUSF, and / or UDM, such as authentication similar to that described elsewhere in this disclosure. In some cases (e.g., if the UE has recently been authenticated), authentication at 1150 can be skipped.

[0167] At 1160, AMF and SMF can perform PDU session updates. As part of the PDU session update, SMF can provide AMF with one or more UPF tunnel endpoint identifiers. In some cases ( Figure 11 (Not shown in the figure), an SMF may have to coordinate with one or more other SMFs and / or one or more other UPFs to set up the user face.

[0168] At 1170, the AMF can send PDU session information to the AN. The PDU session information can be included in the N2 request message. Based on the PDU session information, the AN can configure user plane resources for the UE. To configure user plane resources, the AN can, for example, perform an RRC reconfiguration of the UE. The AN can acknowledge receipt of the PDU session information to the AMF. The AN can notify the AMF that user plane resources have been configured and / or provide information related to user plane resource configuration.

[0169] In the event of a UE-triggered service request procedure, the UE can receive a NAS service acceptance message from the AMF via the AN at 1170. After configuring user plane resources, the UE can transmit uplink data (e.g., uplink data that caused the UE to trigger the service request procedure).

[0170] At 1180, the AMF can update the Session Management (SM) context of the PDU session. For example, the AMF can notify the SMF (and / or one or more other associated SMFs) that user plane resources have been configured, and / or provide information related to user plane resource configuration. The AMF can provide the SMF (and / or one or more other associated SMFs) with one or more AN tunnel endpoint identifiers. After the SM context update is complete, the SMF can send an Update SM Context Response message to the AMF.

[0171] Based on updates to the Session Management Context (SMF), the SMF can update the PCF for policy control purposes. For example, if the UE's location has changed, the SMF can notify the PCF of the UE's new location.

[0172] Based on updates to the session management context, the SMF and UPF can perform session modifications. Session modifications can be performed using the N4 session modification message. After the session modification is complete, the UPF can transmit downlink data (e.g., downlink data that causes the UPF to trigger a network-triggered service request procedure) to the UE. The transmission of downlink data can be based on one or more AN tunnel endpoint identifiers of the AN.

[0173] Figure 12 An example of a Protocol Data Unit (PDU) session establishment procedure for a wireless device (e.g., a UE) is shown. The UE may determine to transmit a PDU session establishment request to create a new PDU session, to hand over an existing PDU session to the 3GPP network, or for any other suitable reason.

[0174] At 1210, the UE initiates PDU session establishment. The UE may transmit the PDU session establishment request to the AMF via the AN. The PDU session establishment request may be a NAS message. The PDU session establishment request may indicate: PDU session ID; the requested PDU session type (new or existing); the requested DN (DNN); the requested network slice (S-NSSAI); the requested SSC mode; and / or any other suitable information. The PDU session ID may be generated by the UE. The PDU session type may be, for example, an Internet Protocol (IP) based type (e.g., IPv4, IPv6, or dual-stack IPv4 / IPv6), an Ethernet type, or an unstructured type.

[0175] The AMF can select an SMF based on a PDU session establishment request. In some scenarios, the requested PDU session may already be associated with a specific SMF. For example, the AMF may store the UE's UE context, and the UE context may indicate that the PDU session ID of the requested PDU session is already associated with a specific SMF. In some scenarios, the AMF can select an SMF based on determining that the SMF is ready to handle the requested PDU session. For example, the requested PDU session may be associated with a specific DNN and / or S-NSSAI, and the SMF can be selected based on determining that it can manage PDU sessions associated with a specific DNN and / or S-NSSAI.

[0176] At 1220, the context of the network management PDU session is established. After selecting the SMF at 1210, the AMF sends a PDU session context request to the SMF. The PDU session context request may include the PDU session establishment request received from the UE at 1210. The PDU session context request may be an Nsmf_PDUSession_CreateSMContext request and / or an Nsmf_PDUSession_UpdateSMContext request. The PDU session context request may indicate the UE's identifier; the requested DN; and / or the requested network slice. Based on the PDU session context request, the SMF may retrieve subscription data from the UDM. The subscription data may be the UE's session management subscription data. The SMF may subscribe to updates to the subscription data, allowing the PCF to send new information if the UE's subscription data changes. After obtaining the UE's subscription data, the SMF may transmit the PDU session context response to the AMG. The PDU session context response may be an Nsmf_PDUSession_CreateSMContext response and / or an Nsmf_PDUSession_UpdateSMContext response. The PDU session context response may include the session management context ID.

[0177] At point 1230, secondary authorization / authentication can be performed if necessary. Secondary authorization / authentication can involve the UE, AMF, SMF, and DN. The SMF can access the DN via the Data Network Authentication, Authorization, and Accounting (DN AAA) server.

[0178] At 1240, the network configures the data path for uplink data associated with a PDU session. The SMF can select a PCF and establish a session management policy association. Based on this association, the PCF can provide an initial set of policy control and charging rules (PCC rules) for the PDU session. When targeting a specific PDU session, the PCF can instruct the SMF on the method for assigning IP addresses to the PDU session, the default charging method for the PDU session, the address of the corresponding charging entity, the triggering factor for requesting a new policy, etc. The PCF can also target Service Data Flows (SDFs) that include one or more PDU sessions. When targeting an SDF, the PCF can instruct the SMF on policies for applying QoS requirements, monitoring services (e.g., for charging purposes), and / or offloading services (e.g., by using one or more specific N6 interfaces).

[0179] SMF can determine and / or assign IP addresses for PDU sessions. SMF can select one or more UPFs (in Figure 12In the example, a single UPF handles the PDU session. The SMF can send N4 session messages to the selected UPF. N4 session messages can be N4 session establishment requests and / or N4 session modification requests. N4 session messages can contain packet detection, enforcement, and reporting rules associated with the PDU session. In response, the UPF can acknowledge by sending N4 session establishment responses and / or N4 session modification responses.

[0180] The SMF can send PDU session management information to the AMF. PDU session management information can be a session service request (e.g., Namf_Communication_N1N2MessageTransfer) message. PDU session management information can include the PDU session ID. PDU session management information can be a NAS message. PDU session management information can include N1 session management information and / or N2 session management information. N1 session management information can include a PDU session establishment acceptance message. The PDU session establishment acceptance message can include the UPF's tunneling endpoint information and the Quality of Service (QoS) information associated with the PDU session.

[0181] The AMF can send an N2 request to the AN. The N2 request may include a PDU session establishment acceptance message. Based on the N2 request, the AN can determine the AN resources for the UE. AN resources can be used by the UE to establish a PDU session with the DN via the AN. The AN can determine the resources to be used for the PDU session and indicate the determined resources to the UE. The AN can send a PDU session establishment acceptance message to the UE. For example, the AN can perform an RRC reconfiguration for the UE. After setting the AN resources, the AN can send an N2 request acknowledgment to the AMF. The N2 request acknowledgment may include N2 session management information, such as the PDU session ID and the AN's tunneling endpoint information.

[0182] After setting the data path for uplink data at position 1240, the UE can optionally transmit uplink data associated with the PDU session. For example... Figure 12 As shown, uplink data can be sent to the DN associated with the PDU session via AN and UPF.

[0183] At position 1250, the network can update the PDU session context. The AMF can transmit a PDU session context update request to the SMF. The PDU session context update request can be an Nsmf_PDUSession_UpdateSMContext request. The PDU session context update request can include N2 session management information received from the AN. The SMF can acknowledge the PDU session context update. The acknowledgment can be an Nsmf_PDUSession_UpdateSMContext response. The acknowledgment can include a request to notify the SMF of any UE mobility event subscriptions. Based on the PDU session context update request, the SMF can send an N4 session message to the UPF. The N4 session message can be an N4 session modification request. The N4 session message can contain tunneling endpoint information of the AN. The N4 session message can contain forwarding rules associated with the PDU session. In response, the UPF can acknowledge by sending an N4 session modification response.

[0184] After receiving the tunneling endpoint information from the AN, the UPF can relay downlink data associated with the PDU session. For example... Figure 12 As shown in the diagram, downlink data can be received from the DN associated with the PDU session via the AN and UPF.

[0185] Figure 13 Examples of components shown are examples of elements in a communication network. Figure 13 A physical deployment 1330 (hereinafter "deployment 1330") includes a wireless device 1310, a base station 1320, and one or more network functions. Any wireless device described in this disclosure may have similar components and may be implemented in a similar manner to wireless device 1310. Any other base station (or any part thereof, depending on the architecture of the base station) described in this disclosure may have similar components and may be implemented in a similar manner to base station 1320. Any physical core network deployment (or any part thereof, depending on the architecture of the base station) in this disclosure may have similar components and may be implemented in a similar manner to deployment 1330.

[0186] Wireless device 1310 can communicate with base station 1320 via air interface 1370. The communication direction from wireless device 1310 to base station 1320 via air interface 1370 is called the uplink, and the communication direction from base station 1320 to wireless device 1310 via air interface 1370 is called the downlink. Downlink transmission can be separated from uplink transmission using a combination of FDD, TDD, and / or duplex technologies. Figure 13 A single wireless device 1310 and a single base station 1320 are shown, but it should be understood that the wireless device 1310 can communicate with any number of base stations or other access network components via air interface 1370, and the base station 1320 can communicate with any number of wireless devices via air interface 1370.

[0187] Wireless device 1310 may include processing system 1311 and memory 1312. Memory 1312 may include one or more computer-readable media, such as one or more non-transitory computer-readable media. Memory 1312 may contain instructions 1313. Processing system 1311 may process and / or execute instructions 1313. Processing and / or execution of instructions 1313 may cause wireless device 1310 and / or processing system 1311 to perform one or more functions or activities. Memory 1312 may contain data (not shown). One of the functions or activities performed by processing system 1311 may be storing data in memory 1312 and / or retrieving previously stored data from memory 1312. In the example, downlink data received from base station 1320 may be stored in memory 1312, and uplink data for transmission to base station 1320 may be retrieved from memory 1312. Figure 13 As shown, wireless device 1310 can communicate with base station 1320 using transmission processing system 1314 and / or reception processing system 1315. Alternatively, transmission processing system 1314 and reception processing system 1315 can be implemented as a single processing system, or both can be omitted, and all processing in wireless device 1310 can be performed by processing system 1311. Although Figure 13 Not shown in the diagram, but the transmission processing system 1314 and / or the reception processing system 1315 may be coupled to a dedicated memory similar to but separate from memory 1312, and containing instructions that can be processed and / or executed to perform one or more of their respective functionalities. The wireless device 1310 may include one or more antennas 1316 for access to the air interface 1370.

[0188] Wireless device 1310 may include one or more other elements 1319. These other elements 1319 may include software and / or hardware providing features and / or functionality, such as speakers, microphones, keypads, displays, touchpads, satellite transceivers, Universal Serial Bus (USB) ports, hands-free headsets, FM radio units, media players, internet browsers, electronic control units (e.g., for motor vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, light sensors, ultrasonic sensors, light sensors, cameras, GPS sensors, etc.). Wireless device 1310 may receive user input data from and / or provide user output data to these other elements 1319. These other elements 1319 may include a power source. Wireless device 1310 may receive power from the power source and may be configured to distribute power to other components within wireless device 1310. The power source may include one or more power sources, such as batteries, solar cells, fuel cells, or any combination thereof.

[0189] Wireless device 1310 can transmit uplink data to and / or receive downlink data from base station 1320 via air interface 1370. To perform transmission and / or reception, one or more of processing system 1311, transmission processing system 1314, and / or receiving system 1315 can implement Open Systems Interconnection (OSI) functionality. As an example, transmission processing system 1314 and / or receiving system 1315 can implement Layer 1 OSI functionality, and processing system 1311 can implement higher-layer functionality. Wireless device 1310 can use one or more antennas 1316 to transmit and / or receive data via air interface 1370. In scenarios where said one or more antennas 1316 include multiple antennas, the multiple antennas can be used to perform one or more multi-antenna techniques, such as spatial multiplexing (e.g., single-user multiple-input multiple-output (MIMO) or multi-user MIMO), transmit / receive diversity, and / or beamforming.

[0190] Base station 1320 may include processing system 1321 and memory 1322. Memory 1322 may include one or more computer-readable media, such as one or more non-transitory computer-readable media. Memory 1322 may contain instructions 1323. Processing system 1321 may process and / or execute instructions 1323. Processing and / or execution of instructions 1323 may cause base station 1320 and / or processing system 1321 to perform one or more functions or activities. Memory 1322 may contain data (not shown). One of the functions or activities performed by processing system 1321 may be storing data in memory 1322 and / or retrieving previously stored data from memory 1322. Base station 1320 may communicate with wireless device 1310 using transmission processing system 1324 and reception processing system 1325. Although Figure 13 Not shown in the diagram, but the transmission processing system 1324 and / or the reception processing system 1325 may be coupled to a dedicated memory similar to but separate from memory 1322, and containing instructions that can be processed and / or executed to perform one or more of their respective functionalities. The wireless device 1320 may include one or more antennas 1326 for access to the air interface 1370.

[0191] Base station 1320 can transmit downlink data to and / or receive uplink data from wireless device 1310 via air interface 1370. To perform transmission and / or reception, one or more of processing system 1321, transmission processing system 1324, and / or receiving system 1325 can implement OSI functionality. As an example, transmission processing system 1324 and / or receiving system 1325 can implement Layer 1 OSI functionality, and processing system 1321 can implement higher-layer functionality. Base station 1320 can use one or more antennas 1326 to transmit and / or receive data via air interface 1370. In scenarios where said one or more antennas 1326 include multiple antennas, the multiple antennas can be used to perform one or more multi-antenna techniques, such as spatial multiplexing (e.g., single-user multiple-input multiple-output (MIMO) or multi-user MIMO), transmit / receive diversity, and / or beamforming.

[0192] Base station 1320 may include interface system 1327. Interface system 1327 may communicate with one or more base stations and / or one or more elements of the core network via interface 1380. Interface 1380 may be wired and / or wireless, and interface system 1327 may include one or more components adapted for communication via interface 1380. Figure 13In this configuration, interface 1380 connects base station 1320 to a single deployment 1330; however, it should be understood that wireless device 1310 may communicate with any number of base stations and / or CN deployments via interface 1380, and deployment 1330 may communicate with any number of base stations and / or other CN deployments via interface 1380. Base station 1320 may include one or more other elements 1329 similar to one or more of the other elements 1319.

[0193] Deployment 1330 may include any number of portions of any number of instances of one or more Network Functions (NFs). Deployment 1330 may include processing system 1331 and memory 1332. Memory 1332 may include one or more computer-readable media, such as one or more non-transitory computer-readable media. Memory 1332 may contain instructions 1333. Processing system 1331 may process and / or execute instructions 1333. Processing and / or execution of instructions 1333 may cause deployment 1330 and / or processing system 1331 to perform one or more functions or activities. Memory 1332 may contain data (not shown). One of the functions or activities performed by processing system 1331 may be storing data in memory 1332 and / or retrieving previously stored data from memory 1332. Deployment 1330 may access interface 1380 using interface system 1337. Deployment 1330 may include one or more other elements 1339 similar to one or more of the other elements 1319.

[0194] One or more of systems 1311, 1314, 1315, 1321, 1324, 1325, and / or 1331 may include one or more controllers and / or one or more processors. The one or more controllers and / or processors may include, for example, general-purpose processors, digital signal processors (DSPs), microcontrollers, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) and / or other programmable logic devices, discrete gate and / or transistor logic, discrete hardware components, onboard units, or any combination thereof. One or more of systems 1311, 1314, 1315, 1321, 1324, 1325, and / or 1331 may perform signal decoding / processing, data processing, power control, input / output processing, and / or any other functionality that enables wireless device 1310, base station 1320, and / or deployment 1330 to operate in a mobile communication system.

[0195] Many elements described in the disclosed embodiments can be implemented as modules. A module is defined herein as an element that performs the defined function and has defined interfaces to other elements. Modules described in this disclosure can be implemented in hardware, software combined with hardware, firmware, wet hardware (e.g., hardware with biological elements), or combinations thereof, all of which may be behaviorally equivalent. For example, a module can be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEW MathScript. It is possible to implement modules using physical hardware incorporating discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include computers, microcontrollers, microprocessors, DSPs, ASICs, FPGAs, and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors can be programmed using languages ​​such as assembly, C, C++, etc. FPGAs, ASICs, and CPLDs are frequently programmed using hardware description languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog. These languages ​​configure connections between limited internal hardware modules on a programmable device. The aforementioned techniques are often combined to achieve the desired functional module results.

[0196] Wireless device 1310, base station 1320, and / or deployment 1330 may implement timers and / or counters. A timer / counter may be started at an initial value. As used herein, starting may include restarting. Once started, the timer / counter can operate. The operation of the timer / counter may be associated with an event. When the event occurs, the value of the timer / counter may change (e.g., increment or decrement). The event may be, for example, an exogenous event (e.g., receiving a signal, measuring conditions, etc.), an endogenous event (e.g., transmitting a signal, calculating, comparing, performing an action, or making a decision thus performed, etc.), or any combination thereof. In the case of a timer, the event may be the elapsed amount of time. However, it should be understood that a timer may be described and / or implemented as a counter that counts the elapsed time units. The timer / counter may operate in the direction of the final value until it reaches the final value. The reaching of the final value may be referred to as the timer / counter expiration. The final value may be referred to as the threshold. The timer / counter may be paused, wherein the current value of the timer / counter is maintained, sustained, and / or extended, even after one or more events that would otherwise have changed the value of the timer / counter have occurred. The timer / counter can be canceled from pause or resumed, wherein the value, which has been held, maintained, and / or extended, begins to change again upon the occurrence of one or more of the events. The timer / counter can be set and / or reset. Setting may include resetting, as used herein. When a timer / counter is set and / or reset, its value may be set to an initial value. The timer / counter can be started and / or restarted. Starting may include restarting, as used herein. In some embodiments, when the timer / counter is restarted, its value may be set to an initial value and the timer / counter may begin running.

[0197] Figure 14A , 14B Figures 14C and 14D illustrate various example arrangements of physical core network deployments, each having one or more network functions or portions thereof. Core network deployments include deployments 1410, 1420, 1430, 1440, and / or 1450. Each deployment may, for example, be similar to... Figure 13Deployment 1330 is depicted in the description. Specifically, each deployment may include a processing system for performing one or more functions or activities, a memory for storing data and / or instructions, and an interface system for communicating with other network elements (e.g., other core network deployments). Each deployment may include one or more network functions (NFs). The term NF may refer to a particular set of functions and / or one or more physical elements configured to perform those functions (e.g., a processing system and memory including instructions that, when executed by the processing system, cause the processing system to perform the functions). For example, in this disclosure, when a network function is described as performing X, Y, and Z, it should be understood that this means the one or more physical elements are configured to perform X, Y, and Z, regardless of how or where the one or more physical elements are deployed. The term NF may refer to a network node, network element, and / or network device.

[0198] As will be discussed in more detail below, there are many different types of NFs, and each type of NF can be associated with different sets of functionalities. Multiple different NFs can be flexibly deployed in different locations (e.g., in different physical core network deployments) or in the same location (e.g., co-located in the same deployment). A single NF can be flexibly deployed in different locations (implemented using different physical core network deployments) or in the same location. Furthermore, a physical core network deployment can also implement one or more base stations, application functions (AFs), data networks (DNs), or any part thereof. NFs can be implemented in many ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtual functions instantiated on a platform (e.g., a cloud-based platform).

[0199] Figure 14A An example arrangement of a core network deployment is shown, where each deployment includes a network function. Deployment 1410 includes NF 1411, deployment 1420 includes NF 1421, and deployment 1430 includes NF 1431. Deployments 1410, 1420, and 1430 communicate via interface 1490. Deployments 1410, 1420, and 1430 may have different physical locations with different signal propagation delays relative to other network elements. This diversity of physical locations of deployments 1410, 1420, and 1430 enables services to be delivered to a wide area with improved speed, coverage, security, and / or efficiency.

[0200] Figure 14B An example layout is shown where a single deployment comprises more than one NF. Unlike... Figure 14A (Each NF is deployed in a separate deployment), Figure 14BThe diagram illustrates multiple NFs in deployments 1410 and 1420. In this example, deployments 1410 and 1420 may implement Software-Defined Networking (SDN) and / or Network Functions Virtualization (NFV).

[0201] For example, deployment 1410 includes an additional network function NF 1411A. NF 1411 and 1411A may consist of multiple instances of the same NF type, cooperatively located at the same physical location within the same deployment 1410. NF 1411 and 1411A may be implemented independently of each other (e.g., isolated and / or independently controlled). For example, NF 1411 and 1411A may be associated with different network slices. The processing systems and memory associated with deployment 1410 may perform all the functions associated with NF 1411 in addition to those associated with NF 1411A. In this example, NF 1411 and 1411A may be associated with different PLMNs, but deployment 1410 implementing NF 1411 and 1411A may be owned and / or operated by a single entity.

[0202] exist Figure 14B Elsewhere, deployment 1420 includes NF 1421 and additional network function NF 1422. NFs 1421 and 1422 can be different NF types. Similar to NFs 1411 and 1411A, NFs 1421 and 1422 can be co-located within the same deployment 1420, but implemented separately. As an example, a first PLMN may own and / or operate deployment 1420 with NFs 1421 and 1422. As another example, a first PLMN may implement NF 1421, and a second PLMN may obtain (e.g., lease, borrow, acquire, etc.) at least a portion of the capabilities of deployment 1420 (e.g., processing power, data storage, etc.) from the first PLMN to implement NF 1422. As yet another example, the deployment may be owned and / or operated by one or more third parties, and the first PLMN and / or the second PLMN may obtain corresponding portions of the capabilities of deployment 1420. When multiple NFs are provided at a single deployment, the network can operate with greater speed, coverage, security, and / or efficiency.

[0203] Figure 14C An example arrangement of core network deployment is shown, in which a single instance of an NF is implemented using multiple different deployments. Specifically, a single instance of NF 1422 is implemented at deployments 1420 and 1440. As an example, the functionality provided by NF 1422 can be implemented as a bundle or a series of sub-services. Each sub-service can be implemented independently, for example, at different deployments. Each sub-service can be implemented in different physical locations. By implementing sub-services of a single NF distributed across different physical locations, the mobile communication network can operate with greater speed, coverage, security, and / or efficiency.

[0204] Figure 14D This illustrates an example layout for a core network deployment, where one or more network functions are implemented using data processing services. Figure 14D In this context, NFs 1411, 1411A, 1421, and 1422 are included in deployment 1450, which is implemented as a data processing service. Deployment 1450 may include, for example, a cloud network and / or a data center. Deployment 1450 may be owned and / or operated by a PLMN or by a non-PLMN third party. NFs 1411, 1411A, 1421, and 1422 implemented using deployment 1450 may belong to the same PLMN or different PLMNs. The PLMN may obtain (e.g., lease, borrow, acquire, etc.) at least a portion of the capabilities of deployment 1450 (e.g., processing power, data storage, etc.). By providing one or more NFs through the data processing service, the mobile communication network can operate at greater speed, coverage, security, and / or efficiency.

[0205] As shown in the figure, different network elements (e.g., NFs) may be located in different physical deployments or co-located in a single physical deployment. It should be understood that, in this disclosure, the sending and receiving of messages between different network elements is not limited to inter-deployment or intra-deployment transmissions, unless explicitly indicated.

[0206] In the example, the deployment can be a 'black box' that pre-configures one or more NFs and is pre-configured to communicate with other 'black box' deployments (e.g., via interface 1490) in a prescribed manner. Alternatively, the deployment can be configured to operate according to open-source instructions (e.g., software) designed to implement the NF and to communicate with other deployments transparently. The deployment can operate according to the Open RAN (O-RAN) standard.

[0207] In this implementation, a service provider (e.g., a game operator, factory operator, etc.) can request a dedicated network slice from a network operator for its services. Based on the request, the network operator can configure and provide the dedicated network slice. The service provider can then allow its users to access its application servers via the dedicated network slice. If users access application servers via the dedicated network slice, the service provider may want to sponsor its users. For example, to provide its users with reliable connectivity, the service provider can set a maximum number of users accessing the dedicated network slice.

[0208] In its implementation, for network slicing, to support the maximum number of users accessing a dedicated network slice, the Network Slice Admission / Access Control Function (NSACF) can manage multiple registered UEs and / or multiple PDU sessions established for the network slice. For example, a network slice can be subject to admission control to limit the number of UEs registered to the network slice and / or limit the number of PDU sessions established for the network slice. The NSACF can be configured with the maximum number of registered UEs and / or the maximum number of PDU sessions established for the network slice. The NSACF can also be configured with information about the network slice's access type. For example, the access type can be 3GPP access and / or non-3GPP access.

[0209] In its implementation, the NSACF can track the number of UEs registered for a network slice and ensure that this number does not exceed the maximum number of UEs registered for a network slice. The NSACF can maintain a list of UE identities registered for a network slice. If the number of UEs registered for a network slice needs to be increased for a given UE, the NSACF can determine whether the UE's identity is included in the list of UE identities registered for a network slice. If the UE's identity is not included in the list, the NSACF can determine whether the number of UEs registered for a network slice for network slices has reached the maximum number of UEs registered for a network slice. If it is determined that the maximum number of UEs registered for a network slice has been reached, the NSACF can apply admission control. For example, the NSACF may disallow a UE from registering for a network slice.

[0210] In its implementation, NSACF can track the number of PDU sessions established for a network slice and ensure that this number does not exceed the maximum number of PDU sessions established for a network slice. If a PDU session for the UE causes an increase in the number of PDU sessions established for a network slice, NSACF determines whether the number of PDU sessions established for the network slice has reached the maximum number of PDU sessions established for a network slice. If it is determined that the maximum number of PDU sessions established for a network slice has been reached, NSACF can apply admission control. For example, NSACF may disallow the establishment of a PDU session for the UE.

[0211] Figure 15 An example implementation of controlling access to a network slice by limiting the number of UEs registered for the network slice is described.

[0212] In the implementation, for network slices, the AMF can be configured with information indicating whether the network slice is subject to Network Slice Admission Control (NSAC). For network slices subject to NSAC, the AMF can perform an NSACF discovery procedure to find the NSACF responsible for the network slice. For example, the AMF can send an Nnrf_NFDiscovery request message to the NRF to request information about the NSACF responsible for the network slice. Based on the Nnrf_NFDiscovery request, the AMF can receive an Nnrf_NFDiscovery response message from the NRF. The Nnrf_NFDiscovery response message may include NSACF information. Based on the NSACF information received from the NRF, the AMF can send an Nnsacf_NSAC_NumOfUEsUpdate request message to the NSACF. The Nnsacf_NSAC_NumOfUEsUpdate request may include at least one of the following: the identity of the network slice (e.g., S-NSSAI), the identity of the UE (e.g., SUPI), the NF ID, the access type, and an update flag. The NF ID may indicate the identity of the network node sending the Nnsacf_NSAC_NumOfUEsUpdate request. The access type indicates the access type the UE is requesting to register. The update flag indicates whether the number of UEs registered to the network slice needs to be increased or decreased. In response to the Nnsacf_NSAC_NumOfUEsUpdate request, the AMF can receive the Nnsacf_NSAC_NumOfUEsUpdate response message from the NSACF. The Nnsacf_NSAC_NumOfUEsUpdate response message may include a result indication. The result indication may include the result of the update and / or check operation in the NSACF, and may include an indication that "the maximum number of UEs for S-NSSAI has not been reached" or "the maximum number of UEs for S-NSSAI has been reached".

[0213] exist Figure 15In the example, the NSACF can send an Nnsacf_NSAC_EACNotify message to the AMF. The NSACF can send an Nnsacf_NSAC_EACNotify message to one or more network nodes (e.g., the AMF) to indicate the activation or deactivation of the Early Availability Check (EAC) mode for the network slice. The EAC mode can indicate to the AMF whether it needs to check the NSACF before determining whether to allow a UE to register with the network slice. For example, for a network slice subject to NSAC, the NSACF can activate the EAC mode when the number of UEs registering with the network slice exceeds a certain threshold (e.g., 100 UEs, 500 UEs, 20%, 50%). The NSACF can send an Nnsacf_NSAC_EACNotify message to one or more network nodes (e.g., the AMF) to indicate the deactivation of the Early Availability Check (EAC) mode for the network slice. For example, for a network slice subject to NSAC, the NSACF can deactivate the EAC mode when the number of UEs registering with the network slice falls below a certain threshold (e.g., 90 UEs, 400 UEs, 10%, 40%). The Nnsacf_NSAC_EACNotify message may include at least one of the network slice's identity and / or EAC flags. The EAC flags indicate whether EAC mode is deactivated or activated for the network slice. When the number of registered UEs for a network slice is low, EAC mode can be deactivated to reduce signaling between the AMF and NSACF. Figure 15 In the example, NSACF can indicate to AMF that EAC mode is activated.

[0214] In this implementation, the AMF can receive a registration request message from the UE. The registration message may include the UE's identity and / or at least one of a list of one or more identities of the requested network slices. The one or more network slices requested by the UE may be subject to NSAC. For the one or more network slices subject to NSAC, the AMF can determine which network slices(s) require NSAC. For the one or more requested network slices that require NSAC, the AMF can determine whether EAC mode is activated.

[0215] In the implementation, for a requested network slice where EAC mode is activated, the AMF can send an Nnsacf_NSAC_NumOfUEsUpdate request message to the NSACF. The Nnsacf_NSAC_NumOfUEsUpdate request may include an update flag indicating that the number of UEs registered for the network slice will increase. Based on the received Nnsacf_NSAC_NumOfUEsUpdate request, the NSACF can determine whether the number of UEs registered for the network slice has reached the maximum number of UEs registered for the network slice. If the maximum number of UEs registered for the network slice has not been reached, the NSACF can send an Nnsacf_NSAC_NumOfUEsUpdate response to the AMF including an indication that the maximum number of UEs registered for the network slice has not been reached. If the maximum number of UEs registered for the network slice has been reached, the NSACF can send an Nnsacf_NSAC_NumOfUEsUpdate response to the AMF including an indication that the maximum number of UEs registered for the network slice has been reached.

[0216] In the implementation, based on the received Nnsacf_NSAC_NumOfUEsUpdate response, the AMF can send a registration response message to the UE. For example, the registration response message can include at least one of the UE's registration acceptance or registration rejection messages. For example, the registration response message can include at least one of a list of one or more accepted network slices and / or a list of at least one or more rejected network slices. Based on a response from the NSACF indicating that the maximum number of UEs registered to a network slice has been reached, the AMF can include the network slice in one or more lists of rejected network slices. Based on a response from the NSACF indicating that the maximum number of UEs registered to a network slice has been reached, the AMF can include the network slice in one or more lists of accepted network slices.

[0217] Figure 16 An example implementation of network slice admission control is described. Figure 16 In the example, the NSACF can determine that the EAC mode applied to its network slice is not activated. For example, the AMF can determine that the EAC mode for the network slice has been deactivated based on the fact that the NSACF has not sent any Nnsacf_NSAC_EACNotify messages to the AMF used for the network slice. Alternatively, the AMF can determine that the EAC mode for the network slice has been deactivated based on the fact that the NSACF has sent an Nnsacf_NSAC_EACNotify message indicating the deactivation of the EAC mode for the network slice.

[0218] In this implementation, the AMF can receive registration requests from the UE. The registration request may include one or more identities of one or more requested network slices. The identities of one or more requested network slices may include at least the network slice to which NSAC applies. Based on the network slice's EAC mode being deactivated, the AMF can determine that the network slice is permitted for the UE. For example, the AMF can send a registration acceptance message to the UE including a list of one or more accepted network slices containing the network slice. Based on sending the registration acceptance message to the UE, the AMF can send an Nnsacf_NSAC_NumOfUEsUpdate request message to the NSACF. The Nnsacf_NSAC_NumOfUEsUpdate request may include at least an update flag indicating that the number of UEs registered for the network slice will increase and / or the UE's identity. Based on the received Nnsacf_NSAC_NumOfUEsUpdate request, the NSACF can determine whether the UE is already included in the list of UEs registered for the network slice. Based on the received Nnsacf_NSAC_NumOfUEsUpdate request, the NSACF can determine whether the number of UEs registered for the network slice has reached the maximum number of UEs registered for the network slice. If the maximum number of UEs registered for a network slice has not been reached, the NSACF can send an Nnsacf_NSAC_NumOfUEsUpdate response to the AMF, indicating that the maximum number of UEs registered for a network slice has not been reached. If the maximum number of UEs registered for a network slice has been reached, the NSACF can send an Nnsacf_NSAC_NumOfUEsUpdate response to the AMF, indicating that the maximum number of UEs registered for a network slice has been reached.

[0219] Figure 17 An example implementation of controlling access to a network slice by limiting the number of PDU sessions established for the network slice is described.

[0220] In this implementation, for network slices, the SMF can be configured with information indicating whether the network slice is subject to NSAC (Network Slice Admission Control). For network slices subject to NSAC, the SMF can execute an NSACF discovery procedure. For example, the SMF can send an Nnrf_NFDiscovery request message to the NRF to request information from the NSACF responsible for the network slice. Based on the Nnrf_NFDiscovery request, the SMF can receive an Nnrf_NFDiscovery response message from the NRF. The Nnrf_NFDiscovery response message may include NSACF information.

[0221] In this implementation, the SMF can receive a PDU session establishment request message from the UE. The PDU session establishment request may include at least one of the following: the PDU session ID used for the PDU session, the identity of the network slice on which the PDU session will be established, and the QoS parameters of the PDU session. Based on the identity of the network slice in the PDU session establishment request, the SMF can send an Nnsacf_NSAC_NumOfPDUsUpdate request message to the NSACF. The Nnsacf_NSAC_NumOfPDUsUpdate request may include at least one of the following: the identity of the network slice (e.g., S-NSSAI), the identity of the UE (e.g., SUPI), the PDU session, the NF ID, the access type, and an update flag. The NF ID may indicate the identity of the network node sending the Nnsacf_NSAC_NumOfPDUsUpdate request. The PDU session ID may indicate the identity of the PDU session requested by the UE. The access type may indicate the access type by which the UE establishes the PDU session through its request. The update flag may indicate whether the number of PDU sessions established for the network slice needs to be increased or decreased. In response to the Nnsacf_NSAC_NumOfPDUsUpdate request, the SMF can receive an Nnsacf_NSAC_NumOfPDUsUpdate response message from the NSACF. The Nnsacf_NSAC_NumOfPDUsUpdate response message may include a result indication. This result indication may include the result of update and / or check operations in the NSACF for network slicing, and may include an indication of whether the maximum number of PDU sessions for S-NSSAI has not been reached or whether the maximum number of PDU sessions for S-NSSAI has been reached. Based on the received Nnsacf_NSAC_NumOfPDUsUpdate response message, the SMF may send a response message to the UE. The response message may include at least one of a PDU session establishment acceptance message and / or a PDU session establishment rejection message. For example, if the response from the NSACF includes an indication that the maximum number of PDU sessions for S-NSSAI has not been reached, the SMF may send a PDU session establishment acceptance message to the UE. For example, if the response from NSACF includes an indication that the maximum number of PDU sessions for S-NSSAI has been reached, SMF can send a PDU session establishment rejection message to the UE.

[0222] In the example, a timer can start running once started and continues running until it stops or expires. If the timer is not running, it can be started, or if it is running, it can be restarted. The timer can be associated with a value (e.g., a timer can start or restart from a certain value, or it can start from zero and expire once it reaches that value). The duration of the timer can be updated until the timer stops or expires (e.g., due to a change in value). The timer can be used for a time period / window of a measurement procedure. When the specification refers to implementations and procedures related to one or more timers, it should be understood that there are multiple ways to implement the one or more timers. For example, it should be understood that one or more of these multiple ways of implementing a timer can be used for a time period / window of a measurement procedure. For example, a network slice inactivity window timer (e.g., an NS UE monitoring timer, an NS PDU monitoring timer) can be used to measure a time window used to measure network slice inactivity. In the example, instead of the start and expiration of the network slice inactivity time window, the time difference between two timestamps can be used. When the timer restarts, the measurement procedure for the time window can be restarted. Other exemplary implementations can be provided to restart the measurement of the time window.

[0223] Figure 18An example implementation is described, in which one or more UEs perform registration with a network slice (slice A) to which the NSAC applies. The one or more UEs may include a first UE (UE1), a second UE (UE2), and / or a third UE (UE3). In the example, the NSACF, responsible for the NSAC used for the network slice, can be configured with a maximum number of UEs registering for the network slice. In one example, the maximum number can be set to two UEs. The first UE may send a first registration request message to the AMF, which includes a list of requested network slices containing the network slice (slice A). Based on the received first registration request message and the NSAC applied to the network slice, the AMF may send a first Nnsacf_NSAC_NumOfUEsUpdate request message to the NSACF. The first Nnsacf_NSAC_NumOfUEsUpdate request message may include the identifier of the first UE and / or the identifier of the network slice. Based on the first Nnsacf_NSAC_NumOfUEsUpdate request message and the fact that the number of UEs registering for the network slice is zero, the NSACF can determine that registration of the first UE for the network slice is permitted. Based on the determination, the NSACF can increase the number of UEs registered to the network slice from zero to one. Based on the determination, the NSACF can send a first Nnsacf_NSAC_NumOfUEsUpdate response message to the AMF, including an indication that the maximum number of UEs registered for the network slice has not been reached. Based on the first response message from the NSACF, the AMF can send a first registration acceptance message to the first UE, including a list of one or more accepted network slices. The list of one or more accepted network slices may include the identifier of the network slice (e.g., slice A). The second UE can send a second registration request message to the AMF, which includes a list of requested network slices containing network slice (slice A). Based on the received second registration request message and the NSAC applied to the network slice, the AMF can send a second Nnsacf_NSAC_NumOfUEsUpdate request message to the NSACF. The second Nnsacf_NSAC_NumOfUEsUpdate request message may include the identifier of the second UE and / or the identifier of the network slice. Based on the second Nnsacf_NSAC_NumOfUEsUpdate request message and the fact that the number of UEs registered to the network slice is one, the NSACF can determine that a second UE is allowed to register for the network slice. Based on this determination, the NSACF can increase the number of UEs registered to the network slice from one to two. Based on this determination, the NSACF can send a second Nnsacf_NSAC_NumOfUEsUpdate response message to the AMF, including an indication that the maximum number of UEs registered for the network slice has not been reached.Based on the second response message from NSACF, AMF can send a second registration acceptance message to the second UE, including a list of one or more accepted network slices. The list of one or more accepted network slices may include the identifier of the network slice (e.g., slice A). The third UE can send a third registration request message to AMF, which includes a list of requested network slices containing the network slices. Based on the received third registration request message and NSAC applied to the network slice, AMF can send a third Nnsacf_NSAC_NumOfUEsUpdate request message to NSACF. The third Nnsacf_NSAC_NumOfUEsUpdate request message may include the identifier of the third UE and / or the identifier of the network slice. Based on the third Nnsacf_NSAC_NumOfUEsUpdate request message and the fact that the number of UEs registered to the network slice is two, NSACF can determine whether to reject / deny the registration of the third UE for the network slice. Based on this determination, NSACF can send a third Nnsacf_NSAC_NumOfUEsUpdate response message to AMF, including an indication of the result that the maximum number of UEs registered for the network slice has been reached. Based on the third response message from NSACF, AMF can send a registration response message (e.g., a registration acceptance message and / or a registration rejection message) to the third UE, which includes a list of at least one or more rejected network slices. The list of one or more rejected network slices may include network slice (slice A).

[0224] In the example, the first UE may be used by an application (e.g., a user, software) that has data to send and / or receive via a network slice. In the example, the second UE may not have an application with data to send via a network slice. In the example, the third UE may be used by an application with data to send via a network slice. In existing implementations, the AMF and / or NSACF may not consider whether one or more UEs have data to send for a network slice. For example, the AMF and / or NSACF may allow the second UE to register with the network slice and / or respond to the second UE by utilizing a list of one or more accepted network slices, including the network slice. For example, the AMF and / or NSACF may not allow the third UE to register with the network slice and / or respond to the third UE by utilizing a list of one or more rejected network slices, including the network slice. In the prior art, the AMF and / or NSACF may not consider the actual activity of one or more UEs (e.g., UEs with data to send and / or receive via a network slice). Therefore, the AMF and / or NSACF may be unable to allocate network slice resources to one or more UEs that have data to send and / or receive via network slices, resulting in a degraded user service experience for those UEs. In the prior art, the AMF and / or NSACF may disregard the actual activity of one or more UEs (e.g., UEs that do not have data to send and / or receive via network slices). Consequently, the AMF and / or NSACF may allocate network slice resources to one or more UEs that do not have data to send and / or receive via network slices, leading to inefficient use of network resources.

[0225] Figure 19An example implementation is described where one or more UEs perform a PDU session establishment procedure for a network slice (e.g., slice A) to which the NSAC is applied. The one or more UEs may include a first UE (UE4), a second UE (UE5), and / or a third UE (UE6). In the example, the NSACF responsible for the NSAC used for the network slice may be configured with a maximum number of PDU sessions established for the network slice. In one example, the maximum number may be set to 2. The first UE may send a first PDU session establishment request message to the SMF, including the identifier of the network slice. Based on the received first PDU session establishment request message and the fact that the NSAC is applied to the network slice, the SMF may send a first nsacf_NSAC_NumOfPDUsUpdate request message to the NSACF. The first nsacf_NSAC_NumOfPDUsUpdate request message may include the identifier of the first UE and / or the identifier of the network slice and / or the identifier of the PDU session. Based on the first nsacf_NSAC_NumOfPDUsUpdate request message and the fact that the number of PDU sessions established with the network slice is zero, the NSACF may determine that a PDU session for the first UE is allowed to be established for the network slice. Based on this determination, the NSACF can increase the number of PDU sessions established with the network slice from zero to one. Based on this determination, the NSACF can send a first Nnsacf_NSAC_NumOfPDUsUpdate response message to the SMF, including an indication that the maximum number of PDU sessions for the network slice has not been reached. Based on the first response message from the NSACF, the SMF can send a first PDU session establishment acceptance message to the first UE. The second UE can send a second PDU session establishment request message to the SMF, including the identifier of the network slice. Based on the received second PDU session establishment request message and the fact that NSAC is applied to the network slice, the SMF can send a second nsacf_NSAC_NumOfPDUsUpdate request message to the NSACF. The second Nnsacf_NSAC_NumOfPDUsUpdate request message may include the identifier of the second UE and / or the identifier of the network slice. Based on the second Nnsacf_NSAC_NumOfPDUsUpdate request message and the fact that the number of PDU sessions established with the network slice is one, the NSACF can determine that establishing a PDU session for the second UE for the network slice is permitted. Based on this determination, NSACF can increase the number of PDU sessions established with the network slice from one to two. Based on this determination, NSACF can send a second Nnsacf_NSAC_NumOfPDUsUpdate response message to SMF, including an indication that the maximum number of PDU sessions has not been reached.Based on the second response message from NSACF, SMF can send a second PDU session establishment acceptance message to the second UE. The third UE can send a third PDU session establishment request message to SMF, including the identifier of the network slice. Based on the received third PDU session establishment request message and the application of NSAC to the network slice, SMF can send a third nsacf_NSAC_NumOfPDUsUpdate request message to NSACF. The third nsacf_NSAC_NumOfPDUsUpdate request message may include the identifier of the third UE and / or the identifier of the network slice. Based on the third nsacf_NSAC_NumOfPDUsUpdate request message and the fact that the number of PDU sessions established with the network slice is two, NSACF can determine to reject the establishment of a PDU session for the third UE for the network slice. Based on this determination, NSACF can send a third nsacf_NSAC_NumOfPDUsUpdate response message to SMF, including an indication that the maximum number of PDU sessions has not been reached. Based on the third response message from NSACF, SMF can send a first PDU session establishment rejection message to the third UE.

[0226] In the example, the first UE may be used by an application (e.g., a user, software) that has data to send and / or receive via network slices. In the example, the second UE may not have an application with data to send via network slices. In the example, the third UE may be used by an application with data to send via network slices. In existing implementations, the SMF and / or NSACF do not consider whether one or more UEs have data to send. For example, the SMF and / or NSACF may allow the second UE to establish a PDU session for network slices. For example, the SMF and / or NSACF may not allow the third UE to establish a PDU session for network slices. In the prior art, the SMF and / or NSACF do not consider the actual activity of one or more UEs and do not allocate network slice resources to one or more UEs with data to send and / or receive via network slices, thus degrading the user service experience. In the prior art, the SMF and / or NSACF do not consider the actual activity of one or more UEs and allocate network slice resources to one or more UEs without data to send and / or receive via network slices, resulting in inefficient use of network resources.

[0227] like Figure 20As described herein, example embodiments of this disclosure improve system efficiency and network slice resource management by using signaling enhancements between network nodes, UEs, etc. For example, by utilizing configuration information delivery for network slice quota management, one or more network nodes can determine the activity of one or more UEs and / or one or more PDU sessions on a network slice. For example, based on the determined activity on the network slice for network slice quota management, one or more network nodes can report and / or share information to adjust network slice usage for one or more UEs and / or for one or more PDU sessions. For example, for a network slice, one or more network nodes can track the activity status for one or more PDU sessions and / or for one or more UEs for network slice quota management. For example, for a network slice, based on data communication activity associated with the network slice and / or the status of the network slice quota, one or more network nodes can determine whether to release one or more PDU sessions and / or cancel one or more PDU sessions and / or maintain one or more PDU sessions. For example, for a network slice, based on the activity of one or more UEs and / or the status of the network slice quota, one or more network nodes can determine whether to update the registration status of one or more UEs. The example implementations disclosed herein support the efficient allocation of network slice resources among one or more UEs and / or one or more PDU sessions.

[0228] In the specification, the term "NG-RAN" can be interpreted as a base station, which may include at least one of gNB, eNB, ng-eNB, NodeB, access node, access point, N3IWF, relay node, base station central unit (e.g., gNB-CU), base station distributed unit (e.g., gNB-DU), etc.

[0229] In this specification, the term "AMF" can be interpreted as a core network device, which may include at least one of mobility management functions / entities, access management functions, etc. In this specification, the term "SMF" can be interpreted as a core network device, which may include at least one of session management functions / entities, serving gateways, PDN gateways, etc.

[0230] In the specification, the term "NSACF" can be interpreted as a core network device, which may include at least one of network slice admission management function / entity, network slice access management function, network slice quota management function / entity, activity-based network slice admission control function / entity, etc.

[0231] In this specification, the term "core network node" can be interpreted as a core network device, which may include at least one of AMF, SMF, NSSF, UPF, NRF, UDM, PCF, NSACF, etc. In this specification, the term "core network" can be interpreted as a core network node. In this specification, the term "access node" can be interpreted as a base station, which may include NG-RAN, etc. In this specification, the term "network node" can be interpreted as a core network node and / or an access node and / or a UE, etc.

[0232] In this specification, the term "network slice quota" used for network slicing can be interpreted as the maximum number of UEs allowed to register for a network slice, the maximum number of PDU sessions allowed to be established for a network slice, the maximum number of PDU sessions allowed to be activated for a network slice, the maximum number of PDU sessions allowed to be terminated for a network slice, and / or the maximum number of countable resources used for network slicing, etc. The term "quota" used for network slicing in this specification can be interpreted as network slice quota.

[0233] In this specification, the term "Network Slice Admission Control (NSAC)" can be interpreted as network slice quota management. In this specification, network slice quota management for network slices may include controlling access to network slices. Network slice quota management for network slices may include controlling admission to network slices used for UEs and / or for PDU sessions, etc. For example, network slice quota management may allow or may not allow the establishment of PDU sessions for network slices. For example, network slice quota management may determine or may not determine whether registration for network slices is allowed.

[0234] In this specification, the term "activity-based network slice quota management" can be interpreted as network slice quota management based on the activities of UE and / or PDU sessions used for network slices. In this specification, the term "activity-based network slice quota management" can also be interpreted as activity-based network slice admission control (ABNSAC). For example, ABNSAC can determine whether there is activity (e.g., data exchange, signaling) for a network slice permitted for use by the UE. For example, ABNSAC can determine whether there is activity (e.g., data exchange) for / via a PDU session established for a network slice. For example, based on this determination, ABNSAC can release / activate / deactivate / maintain a PDU session and / or can refuse / maintain / disallow / deactivate registration of a network slice allocated for the UE and / or can update / change the allocation of network resources for the network slice. For example, ABNSAC may include activating / deactivating / releasing resources allocated to a network slice. For example, ABNSAC may allow or may disallow activation of established PDU sessions for network slices. For example, ABNSAC may determine or may not determine the deactivation of established PDU sessions for network slices. For example, ABNSAC may or may not determine whether to release an established PDU session used for a network slice. For example, ABNSAC may or may not determine whether a request for deregistration of a network slice has been made.

[0235] Figure 21 An example implementation of this disclosure is depicted. In the example, one or more network nodes can generate and / or receive ABNSAC configurations for one or more UEs.

[0236] In the example, the UE (UE 1) can perform a network registration procedure by sending a registration request message to the AMF. The registration request message may include a list of requested network slices. The list of requested network slices may include information about one or more network slices that the UE (UE 1) wants to register with. For example, the information about one or more network slices may include one or more S-NSSAIs (Single Network Slice Selection Auxiliary Information) indicating one or more identifiers of one or more network slices. For example, the list of requested network slices may include a first network slice (e.g., S-NSSAI 1), a second network slice (e.g., S-NSSAI 2), a fourth network slice (e.g., S-NSSAI 4), and / or a fifth network slice (e.g., S-NSSAI 5). In response to the registration request, the AMF may determine whether to allow or deny registration for each network slice indicated by the list of requested network slices for the UE (UE 1). For example, based on the fact that the EAC mode for one or more network slices indicated in the list of requested network slices is not activated, the AMF may determine that the UE is allowed to register for one or more network slices. Based on the determination that one or more network slices are allowed, the AMF may respond to the UE (UE 1) by sending a registration acceptance message. The registration acceptance message may include at least one of a list of accepted network slices and / or a list of rejected network slices. The list of accepted network slices may include information about one or more network slices that the AMF allows the UE (UE 1) to register for. For example, the list of accepted network slices may include the identifier of a first network slice (e.g., S-NSSAI1). The list of rejected network slices may include information about one or more network slices that the AMF rejects the UE (UE 1) from registering for. For example, the list of rejected network slices may include the identifier of a second network slice (e.g., S-NSSAI2).

[0237] In the example, for the registration procedure, the AMF can send an Nnsacf service request (e.g., an Nnsacf_NSAC_NumOfUEsUpdate request) message to the NSACF. If one or more first-type network slices (e.g., S-NSSAI 1, S-NSSAI 2) indicated by the list of requested network slices in the registration request message are set to be subject to NSAC, the Nnsacf service request message to the NSACF can indicate one or more first-type network slices. If one or more second-type network slices (e.g., S-NSSAI 4, S-NSSAI 5) in the list of requested network slices in the registration request message are not set to be subject to NSAC, the Nnsacf service request message to the NSACF may not indicate one or more second-type network slices. The Nnsacf service request may include at least one of the following: UE ID, information about one or more first-type network slices (e.g., S-NSSAI 1, S-NSSAI 2) subject to NSAC, and / or update flags. Update flags can indicate whether the number of UEs registered to a first-type network slice (e.g., one or more first-type network slices) needs to be increased or decreased. For example, an update flag in an Nnsacf service request can indicate that the number of UEs registered to one or more first-type network slices (e.g., S-NSSAI 1) needs to be increased. Similarly, an update flag in an Nnsacf service request can indicate that the number of UEs registered to one or more second-type network slices (e.g., S-NSSAI-2, S-NSSAI 3) needs to be decreased.

[0238] In the example, based on the received Nnsacf service request (e.g., Nnsacf_NSAC_NumOfUEsUpdate request) message, NSACF can determine whether to activate and / or configure ABNSAC. For example, if the number of UEs registered for a first-type network slice (e.g., S-NSSAI 1) is higher than a threshold (e.g., 100 UEs, 200 UEs, 80% of the quota, 90% of the quota), NSACF can determine to activate ABNSAC for the first-type network slice (e.g., S-NSSAI 1). For example, if the number of UEs registered for a first-type network slice (e.g., S-NSSAI 2) is lower than a threshold (e.g., 90 UEs, 150 UEs, 75% of the quota, 85% of the quota), NSACF can determine not to activate ABNSAC for the first-type network slice (e.g., S-NSSAI 2). For example, to determine whether to activate ABNSAC, NSACF can use ABNSAC request information, such as... Figure 27 As shown in the example.

[0239] In the example, in response to a received Nnsacf service request, NSACF may send an Nnsacf service response (e.g., an Nnsacf_NSAC_NumOfUEsUpdate response) message to AMF. Based on the determination that ABNSAC is activated for one or more network slices (e.g., S-NSSAI 1), the Nnsacf service response message may include ABNSAC configuration information for one or more network slices. For example, the ABNSAC configuration information may indicate which one or more network slices (e.g., S-NSSAI 1) ABNSAC is applied to. For example, the ABNSAC configuration information may include at least one of the following: one or more values ​​of one or more network slice UE surveillance timers (NS UE surveillance timers) for which ABNSAC is applied, valid time period information, and / or area information. In the example, the NS UE watchdog timer for network slicing (e.g., the NS UE watchdog timer in the NS US watchdog timer of the ABNSAC configuration information) can be used to indicate / control the time periods during which the UE can remain inactive for the network slice, the UE can not use the network slice, the UE can not send or receive signaling messages for the network slice, and / or the UE can not send or receive user data for the network slice. For example, for the first network slice (e.g., S-NSSAI 1), the value of the NS UE watchdog timer can be set to 30 seconds, 500 milliseconds, 60 seconds, etc. In the example, the valid time period information can include information on when the ABNSAC configuration information is used for one or more network slices and / or is valid for one or more network slices. For example, the valid time period information can indicate the start time (e.g., 9:00 AM) and / or the end time (e.g., 10:00 AM). In the example, the area information can include information on under what conditions the ABNSAC configuration information is used for one or more network slices and / or is valid for one or more network slices. For example, the area information can include one or more GPS coordinates, TA lists, cell lists, etc. The AMF can receive NNSACF service response messages sent by the NNSACF. The AMF can store the ABNSAC configuration information received in the NNSACF service response messages. Based on the ABNSAC configuration information, the AMF can determine which network slices to apply ABNSAC to, as indicated by the ABNSAC configuration information. The AMF can store the ABNSAC configuration information.

[0240] In the example, UE (UE 2) can perform a network registration procedure by sending a registration request message to the AMF. The registration request message may include a list of requested network slices. The list of requested network slices may include information about one or more network slices that UE (UE 2) wants to register. For example, the information about one or more network slices may include one or more S-NSSAIs (e.g., S-NSSAI 1, S-NSSAI 3).

[0241] In response to a registration request received from the UE (UE 2), the AMF can determine whether ABNSAC applies to one or more network slices indicated by the requested list of network slices. For example, if one or more network slices are indicated in the ABNSAC configuration information, the AMF can determine that ABNSAC applies to one or more network slices. For example, if the ABNSAC configuration information includes information about S-NSSAI 1 and / or the requested list of network slices includes S-NSSAI 1, the AMF can determine that ABNSAC applies to S-NSSAI 1. For example, if the ABNSAC configuration does not include information about S-NSSAI 3 and / or the requested list of network slices includes S-NSSAI 3, the AMF can determine that ABNSAC does not apply to S-NSSAI 3. In response to a received registration request message, the AMF can respond to the UE (UE 2) using a registration acceptance message. The registration acceptance message may include at least one of the allowed list of network slices and / or the ABNSAC configuration information. For example, the list of allowed network slices for registering acceptance messages may include information about one or more network slices (e.g., S-NSSAI 1, S-NSSAI 3). For example, the ABNSAC configuration information for registration acceptance may include one or more pieces of information from the ABNSAC configuration information held by the AMF. For example, the ABNSAC configuration information held by the AMF may be the ABNSAC configuration information from the Nnsacf service response. Figure 28 , Figure 29 , Figure 30 , Figure 31 , Figure 32 , Figure 33 , Figure 34 The document further describes examples of using the ABNSAC configuration.

[0242] Figure 22 An example implementation of this disclosure is depicted. In the example, one or more network nodes can generate and / or receive ABNSAC configurations for one or more UEs.

[0243] In the example, a UE (UE 1) can perform a network registration procedure by sending a registration request message to the AMF. The registration request message may include a list of requested network slices. The list of requested network slices may include information about one or more network slices that the UE (UE 1) wants to register with. For example, the information about one or more network slices may include one or more S-NSSAIs (Single Network Slice Selection Auxiliary Information) indicating one or more identifiers of one or more network slices. For example, the list of requested network slices may include a first network slice (e.g., S-NSSAI 1), a second network slice (e.g., S-NSSAI 2), a fourth network slice (e.g., S-NSSAI 4), and / or a fifth network slice (e.g., S-NSSAI 5). In response to the registration request, the AMF may determine whether to allow or deny each network slice indicated by the list of requested network slices for the UE (UE 1). For example, based on the activation of the EAC mode for one or more network slices indicated in the list of requested network slices, the AMF may determine to send an Nnsacf service request (e.g., Nnsacf_NSAC_NumOfUEsUpdate request) message to the NSACF.

[0244] In the example, if one or more Type 1 network slices (e.g., S-NSSAI 1, S-NSSAI 2) indicated by the list of requested network slices in the registration request message are set to be subject to NSAC, then the Nnsacf service request message to NSACF may indicate one or more Type 1 network slices. If one or more Type 2 network slices (e.g., S-NSSAI 4, S-NSSAI 5) indicated by the list of requested network slices in the registration request message are not set to be subject to NSAC, then the Nnsacf service request message to NSACF may not indicate one or more Type 2 network slices. The Nnsacf service request may include at least one of the following: UE ID, information about one or more Type 1 network slices (e.g., S-NSSAI 1, S-NSSAI 2) subject to NSAC, and / or update flags. The update flags may indicate whether the number of UEs registered to (e.g., one or more Type 1 network slices) a Type 1 network slice needs to be increased or decreased. For example, an update flag in an Nnsacf service request can indicate that the number of UEs registered to one or more network slices (e.g., S-NSSAI 1, S-NSSAI 2) needs to be increased. Alternatively, an update flag in an Nnsacf service request can indicate that the number of UEs registered to one or more second-type network slices (e.g., S-NSSAI 3) needs to be reduced.

[0245] In the example, based on the received Nnsacf service request (e.g., Nnsacf_NSAC_NumOfUEsUpdate request) message, NSACF can determine whether to activate ABNSAC and / or configure ABNSAC. Figure 21 Examples can be used to determine this.

[0246] In the example, in response to a received Nnsacf service request, NSACF can send an Nnsacf service response (e.g., an Nnsacf_NSAC_NumOfUEsUpdate response) message to AMF. Based on the determination of ABNSAC activation for one or more network slices (e.g., S-NSSAI 1, S-NSSAI 4, etc.), the Nnsacf service response message may include ABNSAC configuration information for one or more network slices.

[0247] In the example, the AMF can receive Nnsacf service response messages. The AMF can store ABNSAC configuration information from the Nnsacf service response messages. Based on the received Nnsacf service response and / or based on a registration request message from the UE (UE 1), the AMF can send a registration acceptance message to the UE (UE 1). The registration acceptance message may include at least one of a list of accepted network slices, a list of rejected network slices, and / or ABNSAC configuration information. The list of accepted network slices may include information about one or more network slices that the AMF allows the UE (UE 1) to register for. For example, the list of accepted network slices may include information about a first network slice (e.g., S-NSSAI 1). The list of rejected network slices may include information about one or more network slices that the AMF rejects the UE (UE 1) from registering for. For example, the list of rejected network slices may include information about a second network slice (e.g., S-NSSAI 2). For example, the ABNSAC configuration information for registration acceptance may include one or more pieces of information based on the ABNSAC configuration information from the Nnsacf service response. Figure 28 , Figure 29 , Figure 30 , Figure 31 , Figure 32 , Figure 33 , Figure 34 The document further describes examples of using the ABNSAC configuration.

[0248] In the example, UE (UE 2) can perform a network registration procedure by sending a registration request message to the AMF. The registration request message may include a list of requested network slices. The list of requested network slices may include information about one or more network slices that UE (UE 2) wants to register. For example, the information about one or more network slices may include one or more identifiers of one or more network slices (e.g., S-NSSAI 1, S-NSSAI 3). In response to the registration request, the AMF may determine whether to allow or deny each network slice indicated by the list of requested network slices for UE (UE 2). For example, based on the activation of EAC mode for one or more network slices indicated in the list of requested network slices, based on ABNSAC being applied to one or more network slices indicated by the list of requested network slices, and / or based on the stored ABNSAC configuration, the AMF may determine to send an Nnsacf service request (e.g., Nnsacf_NSAC_NumOfUEsUpdate request) message to the NSACF.

[0249] In the example, if one or more network slices (e.g., S-NSSAI 1, S-NSSAI 3) indicated by the list of requested network slices in the registration request message are set to be subject to NSAC, then the AMF can send an Nnsacf service request message to the NSACF for one or more network slices. The Nnsacf service request message may include at least one of the following: UE ID, information about the one or more network slices subject to NSAC (e.g., S-NSSAI 1, S-NSSAI 3), and / or update flags.

[0250] In the example, based on ABNSAC applied to one or more network slices of the received Nnsacf service request message, NSACF can determine whether to keep ABNSAC active and / or deactivate ABNSAC. For example, if the number of UEs registered for a network slice (e.g., in one or more network slices) is higher than a threshold, NSACF can keep ABNSAC active for the network slice. For example, if the number of UEs registered for a network slice (e.g., in one or more network slices) is lower than a threshold, NSACF can deactivate ABNSAC for the network slice.

[0251] In the example, in response to a received Nnsacf service request, NSACF can send an Nnsacf service response (e.g., an Nnsacf_NSAC_NumOfUEsUpdate response) message to AMF. Based on the determination that ABNSAC remains active for one or more network slices (e.g., S-NSSAI 1), the Nnsacf service response message may include ABNSAC configuration information for one or more network slices.

[0252] In the example, based on the received Nnsacf service response and / or based on the registration request message from the UE (UE 2), the AMF can send a registration acceptance message to the UE. The registration acceptance message may include at least one of a list of accepted network slices, a list of rejected network slices, and / or ABNSAC configuration information. The list of accepted network slices may include information about one or more network slices that the AMF allows the UE (UE 2) to register with. For example, the list of accepted network slices may include information about a first network slice (e.g., S-NSSAI 1). For example, the ABNSAC configuration information for registration acceptance may include one or more pieces of ABNSAC configuration information based on the Nnsacf service response. The UE (UE 2) may store the received ABNSAC configuration information. Figure 28 , Figure 29 , Figure 30 , Figure 31 , Figure 32 , Figure 33 , Figure 34 The document further describes examples of using the ABNSAC configuration.

[0253] Figure 23 An example implementation of this disclosure is depicted. In the example, one or more network nodes can generate and / or receive ABNSAC configurations for one or more UEs.

[0254] like Figure 21 As shown in the example, a UE (UE 1) can perform a network registration procedure by sending a registration request message to the AMF, the AMF can send a registration acceptance message to the UE, the AMF can send an Nnsacf service request message to the NSACF, and / or the AMF can receive an Nnsacf service response from the NSACF. In the example, the NSACF can store information about the AMF (e.g., contact information, address). For example, the NSACF can use the stored information to communicate updated information about ABNSAC.

[0255] In the example, NSACF can determine whether EAC mode is activated for a network slice. For instance, if the number of UEs registered for a first-type network slice (e.g., S-NSSAI 1) exceeds a threshold (e.g., 100 UEs, 200 UEs, 80% of the quota, 90% of the quota), NSACF can determine that EAC mode is activated for the first-type network slice (e.g., S-NSSAI 1). Conversely, if the number of UEs registered for a first-type network slice (e.g., S-NSSAI 3) is below a threshold (e.g., 90 UEs, 150 UEs, 75% of the quota, 85% of the quota), NSACF can determine that EAC mode is not activated for the first-type network slice (e.g., S-NSSAI 3). If NSACF determines that EAC mode is activated, NSACF can determine whether ABNSAC is activated. For instance, to determine whether ABNSAC is activated, NSACF can use information received from the AF (e.g., ABNSAC request information), such as... Figure 27 As shown in the example. Based on the determination of activating EAC mode and / or ABNSAC, the NSACF can send an Nnsacf_NSAC_EACNotify message to the AMF to indicate the activation of EAC mode and / or ABNSAC. The Nnsacf_NSAC_EACNotify message may include ABNSAC configuration information. The AMF can store the ABNSAC configuration information received from the NSACF. Figure 28 , Figure 29 , Figure 30 , Figure 31 , Figure 32 , Figure 33 , Figure 34 The document further describes examples of using the ABNSAC configuration.

[0256] In the example, such as Figure 21 As shown in the example, UE (UE 2) may send a registration request message to AMF, and / or AMF may send a registration acceptance message to UE. Based on the ABNSAC configuration information, including one or more network slices indicated by a list of requested network slices, AMF may determine that ABNSAC applies to one or more network slices requested by UE (UE 2). Based on the application of ABNSAC to one or more network slices, AMF may respond to UE (UE 2) using a registration acceptance message. The registration acceptance message may include at least one of the list of allowed network slices and / or the ABNSAC configuration information.

[0257] Figure 24 An example implementation of this disclosure is depicted. In the example, one or more network nodes can generate and / or receive ABNSAC configurations for one or more UEs.

[0258] In the example, NSACF can send Nudm service request messages (e.g., Nudm_ParameterProvision_Create, Nudm_ServiceSpecificAuthorization_Create, etc.) to UDM. Nudm service request messages can include at least one of the following:

[0259] - ABNSAC Auxiliary Information. This may include at least one of ABNSAC configuration information and / or auxiliary information related to determining the ABNSAC configuration information. For example, this information may include timer values ​​used to determine whether a UE and / or PDU session is idle / inactive for a network slice. For example, this information may include timer values ​​used to determine whether a UE and / or PDU session needs to be terminated or released. For example, this information may include information required to determine the value of a timer.

[0260] - Expected UE behavior parameters: This can include information related to the UE's potential mobility.

[0261] - Network configuration parameters: This can include information related to the UE's communication availability and / or reachability.

[0262] - Service parameters: These can be service-specific information that needs to be provided in the network and / or UE for services associated with network slices.

[0263] Upon receiving a Nudr service request message, the UDM can store the received information. The UDM can send a Nudr service request message (e.g., Nudr_DM_Create, etc.) to the UDR. A Nudr service request message can include at least the following items:

[0264] -ABNSAC auxiliary information:

[0265] -AF Service Impact Request Information: This can include information on service routing.

[0266] - Access and mobility subscription data: This can include information related to the processing of UE access and mobility.

[0267] - Session management subscription data: This can include information related to packet data session processing.

[0268] For received Nudr service request messages, the UDR can store the information delivered by the Nudr service request message. For received Nudr service request messages, the UDR can send Nudr service response messages (e.g., Nudr_DM_Create, etc.) to the UDM. For received Nudm service request messages, the UDM can send Nudm service response messages (e.g., Nudm_ParameterProvision_Create and / or Nudm_ServiceSpecificAuthorization_Create, etc.) to the NSACF. In one example, the NSACF can directly send Nudr service request messages to the UDR. For Nudr service request messages received from the NSACF, the UDR can send Nudr service response messages to the NSACF.

[0269] In one example, the NSACF can send an Npcf service request message (e.g., Nnsacf_SliceEventExposure and / or Npcf_AMPolicyAuthorization and / or Npcf_SMPolicyAuthorization, etc.) to the PCF. The Npcf service request message may include at least one of ABNSAC assistance information, a list of one or more UEs to which the ABNSAC assistance information is applied, and / or a list of one or more network slices to which the ABNSAC assistance information is applied. In the example, to select the PCF to which the Npcf service request is sent, the NSACF can query the NRF to receive a list of one or more PCFs associated with one or more network slices to which the ABNSAC assistance information is applied.

[0270] In the example, a UE (UE 1) can perform a network registration procedure by sending a registration request message to the AMF. The registration request message may include the UE's identity and / or at least one of the requested network slices. The list of requested network slices may include information about one or more network slices that the UE (UE 1) wants to register with. For example, the information about one or more network slices may include one or more identifiers of one or more network slices (e.g., S-NSSAI). For example, the list of requested network slices may include a first network slice (e.g., S-NSSAI 1).

[0271] In the example, based on the received registration request message, the AMF can send a request to the UDM to retrieve the UE's subscription information. The UE's subscription information may include a list of one or more network slices subscribed to by the UE, and / or ABNSAC auxiliary information applicable to one or more network slices. In response to the request from the AMF, the UDM can send a response message to the AMF. In the example, the AMF can receive a response message from the UDM including the subscription information. Based on the UE's subscription information received from the UDM, the AMF can send an Npcf service request (e.g., Npcf_AMPolicyControl_Create request) message to the PCF to obtain policy decisions for the UE and / or for one or more network slices. The Npcf service request may include at least one of the UE's identifier, a list of one or more network slices, and / or ABNSAC auxiliary information.

[0272] In the example, upon receiving an Npcf service request message, the PCF may determine to retrieve policy subscription information for one or more network slices and / or for ABNSAC. For example, the PCF may send a Nudr service request (e.g., a Nudr_DM_Query request) to the UDR. The Nudr service request may include one or more identifiers for one or more network slices. In response to the Nudr service request, the UDR may send a Nudr service response message. The PCF may receive a Nudr service response (e.g., a Nudr_DM_Query response) message from the UDR. The Nudr service response message may include at least one of policy subscription information for one or more network slices and / or ABNSAC auxiliary information. In one example, the PCF may determine to send an Nnsacf service request to retrieve ABNSAC information from an NSACF. For example, to select the NSACF to which to send the Nnsacf service request (a request for ABNSAC auxiliary information), the PCF may query the NRF to receive a list of one or more NSACFs handling one or more network slices. Based on the response from the NRF, the PCF can select the NSACF to which to send the Nnsacf service request message. For the selected NSACF, the PCF can send an Nnsacf service request message to request ABNSAC auxiliary information. In response to the Nnsacf service request message, the NSACF can send an Nnsacf service response message including the ABNSAC auxiliary information. The PCF can receive the Nnsacf service response message from the NSACF. In the example, based on information received from the AMF, information received from the UDR, and / or information received from the NSACF, the PCF can determine ABNSAC policy information. The ABNSAC policy information may include at least one of policy information associated with one or more network slices and / or ABNSAC configuration information and / or ABNSAC auxiliary information for one or more network slices.

[0273] In the example, based on information received from the UDM (e.g., ABNSAC auxiliary information) and / or information received from the PCF (e.g., ABNSAC policy information), the AMF can determine the ABNSAC configuration information for the UE. Based on the determined ABNSAC configuration information, the AMF can send a registration acceptance message to the UE. The registration acceptance message may include at least one of a list of accepted network slices and / or ABNSAC configuration information. The UE (UE 1) may store the received ABNSAC configuration information. Figure 28 , Figure 29 , Figure 30 , Figure 31 , Figure 32 , Figure 33 , Figure 34 The document further describes examples of using the ABNSAC configuration.

[0274] Figure 25 An example implementation of this disclosure is depicted. In the example, one or more network nodes can receive ABNSAC configuration for one or more PDU sessions.

[0275] In the example, to establish a PDU session, the UE (UE 1) can perform a PDU session establishment procedure by sending a PDU session establishment request message to the SMF. The PDU session establishment request message may include at least one of a network slice identifier, a PDU session ID, and / or the requested session type. For example, the network slice identifier may indicate which network slice is used for PDU session establishment. For example, the requested session type may indicate whether an IP session or an Ethernet session is required. For example, the network slice identifier may indicate S-NSSAI (e.g., S-NSSAI 1).

[0276] In the example, based on the received PDU session establishment request message, the SMF can send an Nnsacf service request message (e.g., an Nnsacf_NSAC_NumOfPDUsUpdate request) to the NSACF. For example, if the network slice indicated by the PDU session establishment request message is set to be NSAC-enabled, the SMF can send the Nnsacf service request message to the NSACF. For example, if the network slice indicated by the PDU session establishment request message is not set to be NSAC-enabled, the SMF may not send the Nnsacf service request message to the NSACF. The Nnsacf service request may include at least one of the following: UE ID, network slice identifier, update flag, and / or PDU session ID. The update flag may indicate whether the number of PDU sessions established with the network slice needs to be increased or decreased. For example, the update flag may indicate that the number of PDU sessions established with the network slice needs to be increased. The NSACF can receive the Nnsacf service request sent by the SMF.

[0277] In the example, based on the received Nnsacf service request message (e.g., Nnsacf_NSAC_NumOfPDUsUpdate request), Nnsacf can determine whether to activate ABNSAC for PDU sessions used for network slices. For example, if the number of PDU sessions established for network slice (e.g., S-NSSAI 1) is higher than a threshold (e.g., 100 PDU sessions, 200 PDU sessions, 80% of the quota, 90% of the quota), Nnsacf can determine whether to activate ABNSAC for network slice (e.g., S-NSSAI 1). For example, if the number of PDU sessions established for network slice (e.g., S-NSSAI 3) is lower than a threshold (e.g., 90 PDU sessions, 150 PDU sessions, 75% of the quota, 85% of the quota), Nnsacf can determine whether to activate ABNSAC for network slice (e.g., S-NSSAI 3). For example, if the number of PDU sessions activated for a network slice (e.g., S-NSSAI 1) exceeds a threshold (e.g., 110 PDU sessions, 210 PDU sessions, 85% of the quota, 95% of the quota), the NSACF can determine that ABNSAC is activated for the network slice (e.g., S-NSSAI 1). Conversely, if the number of PDU sessions established for a network slice (e.g., S-NSSAI 3) is below a threshold (e.g., 95 PDU sessions, 155 PDU sessions, 80% of the quota, 90% of the quota), the NSACF can determine that ABNSAC is not activated for the network slice (e.g., S-NSSAI 3).

[0278] In the example, in response to a received Nnsacf service request, the NNSACF may send an Nnsacf service response (e.g., an Nnsacf_NSAC_NumOfPDUsUpdate response) message to the SMF. Based on the determination that ABNSAC is activated for a PDU session, the Nnsacf service response message may include ABNSAC configuration information. For example, the ABNSAC configuration information may instruct the SMF that ABNSAC is applied to the PDU session. For example, the ABNSAC configuration information may include at least one of the following: the value of the network slice PDU watchdog timer (NS PDU watchdog timer) to which ABNSAC is applied, valid time period information, and / or valid area information. In the example, the value of the NS PDU watchdog timer may be used to indicate / control the time period during which the PDU session can remain inactive, the PDU session does not use the network slice, the PDU session does not send or receive signaling messages for the network slice, and / or the PDU session does not send or receive user data for the network slice. For example, for a network slice (e.g., S-NSSAI 1), the value of the NS PDU watchdog timer may be set to 30 seconds or 60 seconds. In the example, the effective time period information may include information about when the ABNSAC configuration information is used for network slicing and / or for PDU sessions and / or is valid for network slicing and / or for PDU sessions. For example, the effective time period information may indicate the start time and / or end time. In the example, the area information may include information about under what circumstances the ABNSAC configuration information is used for network slicing and / or for PDU sessions and / or is valid for network slicing and / or for PDU sessions. For example, the effective area information may include at least one of one or more GPS coordinates, TA lists, cell lists, etc. The SMF may receive Nnsacf service response messages sent by the NSACF. The SMF may store the received ABNSAC configuration information in the Nnsacf service response messages. Based on the ABNSAC configuration information, the SMF may determine whether to apply ABNSAC to the PDU session. Based on the Nnsacf service response messages, the SMF may send a PDU session establishment acceptance message to the UE. The PDU session establishment acceptance message may include ABNSAC configuration information. For example, the ABNSAC configuration information in the PDU session establishment acceptance may include one or more pieces of information from the ABNSAC configuration information in the Nnsacf service response. For example, the SMF can send ABNSAC configuration information to the UPF and / or NG-RAN that handles the PDU session. In the example, the PDU session establishment procedure for UE (UE1) can be applied to UE (UE2). Figure 28 , Figure 29 , Figure 30 , Figure 31 , Figure 32 , Figure 33 , Figure 34 The document further describes examples of using the ABNSAC configuration.

[0279] Figure 26 An example implementation of this disclosure is depicted. In the example, one or more network nodes can generate and / or receive ABNSAC configurations for one or more PDU sessions.

[0280] like Figure 24 As shown in the example, NSACF can send Nudm service request messages (e.g., Nudm_ParameterProvision_Create, Nudm_ServiceSpecificAuthorization_Create, etc.) to UDM. UDM can store the received information. UDM can send Nudr service request messages (e.g., Nudr_DM_Create, etc.) to UDR. UDR can store the received information. NSACF can send Nudr service request messages to UDR. UDR can send Nudr service response messages (e.g., Nudr_DM_Create, etc.). UDM can send Nudm service response messages (e.g., Nudm_ParameterProvision_Create, Nudm_ServiceSpecificAuthorization_Create, etc.).

[0281] Return to Figure 26In the example, the NSACF can send an Npcf service request message (e.g., Nnsacf_SliceEventExposure, Npcf_AMPolicyAuthorization, Npcf_SMPolicyAuthorization, etc.) to the PCF. The Npcf service request message may include at least one of the following: ABNSAC auxiliary information, a list of one or more UEs to which the ABNSAC auxiliary information is applied, a list of one or more network slices to which the ABNSAC auxiliary information is applied, and / or a list of one or more PDU sessions to which the ABNSAC auxiliary information is applied. In the example, to select the PCF to which the Npcf service request is sent, the NSACF can query the NRF to receive a list of one or more PCFs that serve one or more network slices to which the ABNSAC auxiliary information is applied and / or serve one or more PDU sessions associated with the network slices to which the ABNSAC auxiliary information is applied. In response to the query, the NRF can send PCF information to the NSACF. In response to the Npcf service request message, the PCF can store the information delivered via the Npcf service request message. The PCF can send an Npcf service response to the NSACF.

[0282] In the example, the UE (UE 1) can perform a PDU session establishment procedure to establish a PDU session for a network slice by sending a PDU session establishment request message to the SMF. The PDU session establishment request message may include at least one of the UE's identifier, the network slice's identity, and / or the PDU session ID of the PDU session. In the example, based on the received PDU session establishment request message, the SMF can send a request to the UDM to retrieve the UE's subscription information. The UE's subscription information may include session-related subscription information applicable to the network slice and / or ABNSAC auxiliary information. The UDM can send a response including the subscription information to the SMF. Based on the subscription information received from the UDM, the SMF can send an Npcf service request (e.g., an Npcf_SMPolicyControl_Create request) message to the PCF to obtain policy information for the PDU session. The Npcf service request may include at least one of the UE's identifier, the network slice's identifier, ABNSAC auxiliary information, and / or the subscription information received from the UDM. The PCF can receive the Npcf service request message.

[0283] In the example, upon receiving an Npcf service request message, the PCF can determine to retrieve policy-related subscription data from the UDR. For example, the PCF can send a Nudr service request (e.g., a Nudr_DM_Query request) to the UDR. The Nudr service request may include an identifier of the network slice on which a PDU session is established. In response to the Nudr service request, the UDR can send a Nudr service response (e.g., a Nudr_DM_Query response) message. The PCF can receive the Nudr service response from the UDR. The Nudr service response message may include at least one of policy-related subscription data for the PDU session, policy-related subscription data for the network slice, and / or ABNSAC auxiliary information for the network slice. Based on the Npcf service request received from the SMF, the PCF can send an Nnsacf service request message to the NSACF to request ABNSAC auxiliary information. For example, to select the NSACF to which to send the Nnsacf service request, the PCF can query the NRF to receive information about the NSACF handling the network slice. Based on the response from the NRF, the PCF can select the NSACF and / or can send an Nnsacf service request message to the NSACF. In response to the Nnsacf service request message received from the PCF, the NSACF can send an Nnsacf service response message to the PCF. The PCF can receive the Nnsacf service response message from the NSACF. The Nnsacf service response message may include ABNSAC auxiliary information. In the example, based on information from the SMF, information from the UDR, and / or information from the NSACF, the PCF can determine ABNSAC policy information for the PDU session. The ABNSAC policy information may include at least one of policy information associated with a network slice, policy information associated with a PDU session, ABNSAC configuration information, and / or ABNSAC auxiliary information. The PCF can send an Npcf service response message including the ABNSAC policy information to the SMF.

[0284] Based on information from the UDM and / or the PCF, the SMF can determine the ABNSAC configuration information for the PDU session. Based on the determined ABNSAC configuration information, the SMF can send a PDU session establishment accept message to the UE. The PDU session establishment accept message may include at least one of the QoS information and / or the ABNSAC configuration information for the PDU session. Based on the determined ABNSAC configuration information, the SMF can send an N2 message (e.g., a PDU session resource establishment request) to the NG-RAN and / or an N4 message (e.g., an N4 session configuration message) to the UPF. For example, the N2 message may include ABNSAC configuration information and / or the N4 message may include ABNSAC configuration information. Figure 28, Figure 29 , Figure 30 , Figure 31 , Figure 32 , Figure 33 , Figure 34 The document further describes examples of the use of ABNSAC configuration information.

[0285] Figure 27 An example implementation of this disclosure is described. In the example, AF can provide information to assist in determining ABNSAC configuration information.

[0286] exist Figure 24 and / or Figure 26 In the example, NSACF can store ABNSAC auxiliary information in the UDR, UDM, and / or PCF. Return to Figure 27 To generate ABNSAC auxiliary information, NSACF can use information delivered from Application Functions (AFs). For example, to help the network effectively manage network slices, an AF can send ABNSAC request information to the network. An AF can be the owner of the network slice to which ABNSAC is applied, the administrator of the network slice to which ABNSAC is applied, and / or an application server whose services can be delivered through the network slice.

[0287] In the example, to assist the network, the AF can send Nnef service request messages to the NEF (e.g., Nnef_ParameterProvision_Create request, Nnef_ServiceParameter_Create request, and / or Nnef_ApplyPolicy_Create request, etc.). Nnef service requests can include at least one of the following:

[0288] - Expected UE behavior parameters: This can include information related to the UE's potential mobility.

[0289] - Network configuration parameter information: This may include information related to the UE's communication availability and / or reachability.

[0290] - Service description information: This can be information used to identify the service. This can include DNN, S-NSSAI, AF service identifier and / or application identifier.

[0291] -ABNSAC Request Information: This may include at least one of the following: information associated with a network slice, information associated with ABNSAC configuration information, information associated with ABNSAC auxiliary information, and / or information about one or more network slices. For example, this information may include information about how to determine the inactivity of a UE and / or PDU session on a network slice. For example, this information may include information about the time period during which the UE and / or PDU session is expected to be active. For example, based on this time period, NSACF may determine the value of a timer (e.g., NS UE monitoring timer, NS PDU monitoring timer).

[0292] In the example, based on an Nnef service request message received from the AF, the NEF can determine the NSACF associated with one or more network slices indicated by the Nnef service request message. Based on the determination of the NSACF, the NEF can send an Nnsacf service request message (e.g., an Nnsacf_NSAC_Authorization request, etc.) to the determined NSACF. The Nnsacf service request message (e.g., an Nnsacf_NSAC_Authorization request, etc.) may include ABNSAC request information. For example, the ABNSAC request information of the Nnsacf service request message may include one or more pieces of information from the ABNSAC request information of the Nnef service request message. The NSACF can receive the Nnsacf service request message sent by the NEF and / or store the ABNSAC request information from the Nnsacf service request message. In response to the received Nnsacf service request message, the NSACF can send an Nnsacf service response message (e.g., an Nnsacf_NSAC_Authorization response, etc.) to the NEF.

[0293] In the example, based on the Nnef service request message received from the AF, the NEF can determine the PCF associated with one or more network slices indicated by the Nnef service request message. Based on the determination of the PCF, the NEF can send an Npcf service request message (e.g., Nnsacf_SliceEventExposure request, Npcf_AMPolicyAuthorization request, Npcf_SMPolicyAuthorization request, etc.) to the determined PCF. The Npcf service request message may include ABNSAC request information. For example, the ABNSAC request information of the Npcf service request message may include one or more pieces of information from the ABNSAC request information of the Nnef service request message. The PCF can receive the Npcf service request message sent by the NEF. Based on the Npcf service request message, the PCF can store the ABNSAC request information and / or determine the network slicing policy for the network slice indicated by the Nnef service request. In response to a received NPCF service request message, the PCF can send an NPCF service response message (e.g., Nnsacf_SliceEventExposure response, Npcf_AMPolicyAuthorization response, Npcf_SMPolicyAuthorization response, etc.) to the NEF. Based on the received ABNSAC request information, the PCF can send an NPCF service request message (e.g., Nnsacf_NSAC_Authorization request, etc.) to the NSACF. The NPCF service request message may include ABNSAC request information. Based on the received ABNSAC request information, the NSACF can generate ABNSAC configuration information.

[0294] In the example, based on the Nnef service request message received from the AF, the NEF can determine the UDM / UDR associated with one or more network slices indicated by the Nnef service request message. Based on the determination of the UDM / UDR, the NEF can send a Nudm / udr service request message (e.g., Nudm_ParameterProvision_Create and / or Nudm_ServiceSpecificAuthorization_Create, etc.) to the determined UDM / UDR. The Nudm / udr service request message may include ABNSAC request information. For example, the ABNSAC request information of the Nudm / udr service request message may include one or more pieces of information from the ABNSAC request information of the Nnef service request message. The UDM / UDR can receive the Nudm / udr service request message sent by the NEF. The UDM / UDR can store the ABNSAC request information of the Nudm / udr service request message. In response to a received Nudm / udr service request message, the UDM / UDR can send a Nudm / udr service response message (e.g., a Nudm_ParameterProvision_Create response, a Nudm_ServiceSpecificAuthorization_Create response, etc.) to the NEF. In the example, based on the received ABNSAC request information, the UDM / UDR can determine the NSACF associated with the network slice of the ABNSAC request information. Based on the determined NSACF, the UDM / UDR can send an Nnsacf service request message (e.g., an Nnsacf_NSAC_Authorization request, etc.). The Nnsacf service request may include ABNSAC request information. For example, the ABNSAC request information of the Nnsacf service request message may include one or more pieces of information from the ABNSAC request information of the Nudm / udr service request message. The NSACF can receive the Nnsacf service request message sent by the UDM / UDR. The NSACF can store the ABNSAC request information of the Nnsacf service request message.

[0295] Figure 28 An example implementation of this disclosure is depicted. In the example, a network node can use ABNSAC configuration to monitor UE activity for network slice quota management. In the example, a network node can use ABNSAC configuration to manage resources used for the UE.

[0296] In the example, one or more network nodes (e.g., NSACF and / or SMF and / or AMF and / or UPF and / or NG-RAN and / or UE) can receive ABNSAC configuration information. To receive ABNSAC configuration information, one can use methods such as... Figure 21 , Figure 22 , Figure 23 , Figure 24 , Figure 25 , Figure 26 , Figure 27 One or more examples are shown.

[0297] In the example, ABNSAC configuration information may include information for one or more network slices configured for NSAC and / or ABNSAC. ABNSAC configuration information may include at least one of the following:

[0298] -NS is the value of the UE monitoring timer.

[0299] - Value of NS PDU monitoring timer

[0300] - Valid time period information.

[0301] - Valid area information.

[0302] - Identifier for network slices.

[0303] - Information on whether one or more reports are required: This can indicate whether the network node (e.g., UE, AMF, SMF, UPF, NG-RAN, and / or NSACF) managing the timer (e.g., NS UE monitoring timer, NS PDU monitoring timer) needs to report when the timer expires.

[0304] - Information on where to report: This indicates which network node (e.g., UE, AMF, SMF, UPF, NG-RAN, NSACF, AF, PCF) should be notified when the timer expires.

[0305] - Information to be reported: This indicates what information needs to be reported when a network node (e.g., UE, AMF, SMF, UPF, NG-RAN) reports the expiration of a timer. For example, the information may include the identifier of the network slice for which its timer expires, the activity status of one or more network slices, the activity status of one or more PDU sessions, the amount of data exchanged on the network slice, the identifier of the UE associated with the timer, the identifier of the PDU session associated with the timer, etc.

[0306] - Information on actions to be performed when a timer expires: This indicates what actions network nodes (e.g., UE, AMF, SMF, UPF, NG-RAN, NSACF) need to take when a timer expires. For example, a UE may initiate registration-related procedures (e.g., a registration update procedure for deregistering a network slice whose timer has expired, a deregistration procedure for deregistering a UE from the network), PDU session-related procedures (e.g., a PDU session release procedure for releasing a PDU session established on a network slice, and / or a PDU session deregistration procedure for releasing a PDU session established on a network slice), and / or connection management procedures (e.g., an RRC connection release request for releasing an RRC connection, an RRC connection release request for requesting a transition to an RRC inactive state, a NAS connection release request for releasing an N1 connection). For example, an AMF may initiate procedures (e.g., a UE configuration update procedure for deassigning / removing / rejecting a network slice whose timer has expired, or a UE deregistration procedure for deregistering a UE) to update the list of allowed network slices for the UE. For example, an SMF can initiate procedures (e.g., a PDU session release / removal procedure, an N2 procedure for releasing resources allocated to a PDU session, and an N4 procedure for releasing / removing N3 resources used for a PDU session) to manage PDU sessions whose timers have expired. Similarly, a UPF can initiate procedures to manage N3 resources allocated for PDU sessions whose timers have expired. NG-RAN can initiate procedures (e.g., releasing one or more radio bearers allocated / established for a PDU session on a network slice, releasing RRC connections, and transitioning the UE to an RRC inactive state when there are no other active PDU sessions) to manage RRC resources allocated for PDU sessions whose timers have expired. For example, information about the actions to be performed when a timer expires can instruct network nodes to report timer expiration.

[0307] - Information about the target being monitored: For example, this could indicate one or more UEs and / or one or more PDU sessions. For one or more UEs and / or for one or more PDU sessions, monitoring activity / inactivity can be performed by applying ABNSAC configuration and / or managing timers.

[0308] - Information on when to start the timer: This can include information on one or more criteria for when the timer needs to be started. For example, this could indicate when a network slice is allowed / registered for the UE, when the AMF sends a registration accept message to the UE including the network slice, when the UE receives the registration accept message, when the SMF establishes a PDU session with the UE for the network slice, when the SMF sends a PDU session establishment accept message to the UE for the network slice, when the UPF activates resources for the PDU session for the network slice, and / or when the NG-RAN establishes resources for the PDU session for the network slice.

[0309] - Information on when to stop the timer: This can include information based on one or more criteria for when the timer needs to be stopped. For example, the timer can be stopped when the UE deregisters from a network slice and / or when the UE establishes a PDU session through a network slice.

[0310] - Information on when to restart the timer: This can include information on one or more criteria for when the timer needs to be restarted. For example, the timer can be restarted when signaling messages are exchanged between the UE and SMF, and / or when packets are delivered for a PDU session targeting a network slice. For example, the timer can be restarted when packets are exchanged between the UE and / or UPF and / or NG-RAN, and / or when packets are delivered for a PDU session targeting a network slice.

[0311] - Time Period Information: This indicates the period during which the UE may not request network slices and / or PDU sessions on network slices if the timer expires. For example, when the timer expires, the UE may not request registration for the network slice, establishment of PDU sessions for the network slice, and / or activation of PDU sessions for the network slice until the time period indicated by the Time Period Information has elapsed.

[0312] For example, to provide information for one or more network slices, ABNSAC configuration information may include information for one or more network slices. For example, if the ABNSAC configuration includes information for network slice K and / or for network slice M, then the ABNSAC configuration may include a first value for the NS UE monitoring timer for network slice K and / or a second value for the NS UE monitoring timer for network slice M. For example, to provide information for one or more network slices, one or more ABNSAC configuration information may be used (e.g., using a first ABNSAC configuration and / or a second ABNSAC configuration). For example, the first ABNSAC configuration may include information for network slice K, and / or the second ABNSAC configuration may include information for network slice M.

[0313] In the example, for the network slices to which ABNSAC can be applied, the AMF can receive ABNSAC configuration information from network nodes (e.g., UDM, NSACF, PCF). In one example, the ABNSAC configuration information can be configured locally within the AMF.

[0314] In the example, based on ABNSAC configuration information, the AMF can start an NS UE monitoring timer for the UE. For instance, the AMF can start the NS UE monitoring timer by sending a NAS message (e.g., a registration acceptance message, a UE configuration update message) to the UE that includes the identifier of the NS UE monitoring timer and its associated network slice. The NAS message can indicate that the network slice is allowed / registered for the UE. For instance, based on ABNSAC configuration information, the AMF can start the NS UE monitoring timer with a value for the NS UE monitoring timer. For instance, if the conditions indicated by the information indicating when to start the timer are met, the AMF can start the NS UE monitoring timer for the network slice used by the UE.

[0315] In the example, based on ABNSAC configuration information, the AMF can manage the NS UE monitoring timer for the UE. For instance, when the AMF receives a NAS message for network slicing from the UE (e.g., a registration request message including network slice information, or PDU session-related messages for network slicing (e.g., PDU session establishment request message, PDU session modification request message)), the AMF can restart the NS UE monitoring timer for the network slice used by the UE. Similarly, when the AMF sends a NAS message for network slicing to the UE (e.g., a registration acceptance message including network slice information, or PDU session-related messages for network slicing (e.g., PDU session establishment acceptance message, PDU session modification acceptance message)), the AMF can restart the NS UE monitoring timer for the network slice used by the UE. Finally, when the AMF sends and / or receives an N2 message (e.g., a PDU session resource setting request / accept) for the network slice associated with the timer from the NG-RAN, the AMF can restart the NS UE monitoring timer for the network slice used by the UE. For example, when the AMF detects network slice activity (e.g., when the AMF receives and / or sends messages associated with a network slice, or when the UE sends and / or receives data for a network slice), the AMF can restart the network slice for the UE.

[0316] In the example, based on ABNSAC configuration information, the AMF can determine whether an event has occurred for the network slice used by the UE. For example, the event may include the expiration of the NS UE monitoring timer for the network slice used by the UE. If the timer expires, the AMF can send a report message (e.g., an NNSACF, indicated by information on where to report) to a network node (e.g., an Nnsacf_NSAC_NumOfUEsUpdate request, etc.) indicating the expiration of the timer for the network slice used by the UE. The report message sent by the AMF may include at least one of the UE's identifier, the network slice's identifier, and / or the indication of the timer expiration.

[0317] In the example, the NSACF can receive report messages sent by the AMF. Based on the report messages, the NSACF can determine whether to release / retain the network slice used for the UE. For this determination, the NSACF can use information about the number of UEs registered for the network slice. For example, if conditions are met (e.g., the number of UEs registered for the network slice reaches the maximum number of UEs registered for the network slice, the number of UEs registered for the network slice exceeds a threshold, and / or a timer expires), the NSACF can determine to release the network slice used for the UE. Releasing a network slice used for the UE can be done by removing the network slice from the list of accepted network slices for the UE, the network not accepting the UE's registration for the network slice, and / or the network revoking / rejecting the UE's registration for the network slice. Conversely, if conditions are not met, the NSACF can determine to retain the network slice used for the UE. Retaining a network slice used for the UE can be done by the network slice not being removed from the list of accepted network slices for the UE, the network continuing to accept the UE's registration for the network slice, and / or the network not revoking / rejecting the UE's registration for the network slice.

[0318] In the example, in response to a report request message, the NSACF can send a report response message to the AMF (e.g., an Nnsacf_NSAC_NumOfUEsUpdate response, etc.). The report response message may include at least one of the following: network slice information, information on whether to retain / release the network slice for the UE, information on the time period during which the UE cannot request the network slice, and / or the UE's identifier. The network slice information may indicate the identifier of the network slice associated with the report response message. The information on whether to retain / release the network slice may indicate whether to retain or release the UE's registration for the network slice. If the network slice is to be released, the information on the time period during which the UE cannot request the network slice may indicate the time period during which the UE cannot re-request registration for the network slice. Based on the received report response message, the AMF can determine whether to retain / release the registration for the network slice for the UE. For example, if the received report response message indicates that the network slice will be released for the UE, the AMF can send a message to the UE (e.g., a UE configuration update message, a deregistration request message). The message sent to the UE may include at least one of the following: a list of network slices that have been rejected / removed, a reason value indicating that a network slice will be released due to inactivity, a reason value indicating that a quota for a network slice has been reached (e.g., the maximum number of UEs registered for a network slice has been reached), information about a time period during which the UE cannot request a network slice, and / or information that a network slice has been deregistered due to inactivity.

[0319] Figure 29 An example implementation of this disclosure is depicted. In the example, a network node can use ABNSAC configuration to monitor UE activity for network slice quota management. In the example, a network node can use ABNSAC configuration to manage resources used for the UE.

[0320] In the example, one or more network nodes (e.g., NSACF, SMF, AMF, UPF, NG-RAN, and / or UE) can receive ABNSAC configuration information. To receive ABNSAC configuration information, one can use methods such as... Figure 21 , Figure 22 , Figure 23 , Figure 24 , Figure 25 , Figure 26 , Figure 27 One or more examples are shown.

[0321] In the example, AMF can determine the expiration of timers based on the ABNSAC configuration, such as... Figure 28 As shown in the example.

[0322] In the example, the information about the action to be performed when the timer expires can indicate one or more actions to be performed by the AMF and / or can be configured locally. When the timer for a network slice used by the UE expires, the AMF can perform one or more actions. For example, the AMF can perform one or more actions based on the information about the action to be performed when the timer expires. For example, the action information can indicate whether the AMF needs to maintain / release the UE's registration for the network slice whose timer has expired. For example, the AMF can determine whether to release / deregister / revoke the registration for the network slice used by the UE. Based on the determination, the AMF can send a message to the UE (e.g., a UE configuration update message, a deregistration request message). For example, the message sent to the UE can include at least one of the following: a list of rejected / removed network slices containing the network slice, a list of accepted network slices excluding the network slice, a reason value indicating that the network slice is released due to inactivity, a reason value indicating that the network slice quota has been reached (e.g., the maximum number of UEs registered for the network slice has been reached), information about the time period during which the UE cannot request the network slice, and / or information that the network slice is deregistered due to inactivity. The UE can receive the message sent by the AMF.

[0323] Figure 30 An example implementation of this disclosure is depicted. In the example, a network node can use ABNSAC configuration to monitor network slice activity for network slice quota management. In the example, a network node can use ABNSAC configuration to manage resources used for network slices.

[0324] In the example, one or more network nodes (e.g., NSACF, SMF, AMF, UPF, NG-RAN, UE) can receive ABNSAC configuration information and / or can configure locally using the ABNSAC configuration information. To receive ABNSAC configuration information, one can use methods such as... Figure 21 , Figure 22 , Figure 23 , Figure 24 , Figure 25 , Figure 26 , Figure 27 One or more examples are shown.

[0325] In the example, the UE can use NAS messages (e.g., registration acceptance messages, UE configuration update messages, etc.) to receive ABNSAC configuration information from network nodes (e.g., AMF, UDM, NSACF, PCF, SMF) for the network slices to which ABNSAC can be applied. If the UE supports ABNSAC applied to one or more network slices, the ABNSAC configuration information can include information for one or more network slices.

[0326] In the example, based on the received ABNSAC configuration information, the UE can start an NS UE monitoring timer for the network slice to which the ABNSAC configuration information is applied. For example, the UE can start an NS UE monitoring timer based on receiving a NAS message (e.g., a registration acceptance message, a UE configuration update message) that includes a list of allowed network slices containing that network slice and / or ABNSAC configuration information for the network slice. For example, the UE can start an NS UE monitoring timer for a network slice based on receiving ABNSAC configuration information associated with the network slice.

[0327] In the example, based on ABNSAC configuration information, the UE can manage the NS UE monitoring timer for network slices. For instance, when the UE sends and / or receives NAS messages for network slices (e.g., registration request / accept messages including network slice information, PDU session-related messages for network slices (e.g., PDU session establishment request / accept messages, PDU session modification request / accept messages)), the UE can restart the NS UE monitoring timer for the network slice. Similarly, when the UE sends and / or receives network slice services, the UE can restart the NS UE monitoring timer for the network slice.

[0328] In the example, the UE can determine whether an event has occurred for the network slice used by the UE. For example, the event could be the expiration of a UE monitoring timer for the network slice NS. When the timer for the network slice expires, the UE can perform one or more actions. For example, the UE can perform one or more actions based on information about the actions to be performed when the timer expires. For example, the action information could indicate whether the UE needs to maintain / release the registration of the network slice whose timer has expired. For example, the UE can determine to release the registration of the network slice and / or deregister the network slice. Based on the determination, the UE can send a message to the AMF (e.g., a registration request message, a deregistration request). The message sent by the UE can include a list of requested network slices and / or a reason value. The list of requested network slices may not include network slices whose timers have expired. The reason value can indicate that inactivity was detected for the network slice and / or that the timer for the network slice has expired.

[0329] In the example, for a network slice whose timer expires, if a PDU session has been established for the network slice, the UE can determine to release the PDU session. Based on this determination, the UE can send an SM-related message (e.g., a PDU session release message) to the SMF that controls the PDU session.

[0330] Figure 31An example implementation of this disclosure is depicted. In the example, a network node can use ABNSAC configuration to monitor PDU session activity for network slice quota management. In the example, a network node can use ABNSAC configuration to manage resources used for PDU sessions.

[0331] In the example, one or more network nodes (e.g., NSACF, SMF, AMF, UPF, NG-RAN, UE) can receive ABNSAC configuration information. To receive ABNSAC configuration information, one can use methods such as... Figure 21 , Figure 22 , Figure 23 , Figure 24 , Figure 25 , Figure 26 , Figure 27 One or more examples are shown. In the examples, ABNSAC configuration information can be as follows: Figure 28 The example shows the ABNSAC configuration.

[0332] In the example, the SMF can receive ABNSAC configuration information from network nodes (e.g., UDM, NSACF, PCF) for PDU sessions that can be applied to the network slices for which ABNSAC can be used.

[0333] In the example, the SMF can start an NS PDU monitoring timer for the UE's PDU session. For example, the SMF can start the NS PDU monitoring timer based on sending a NAS message (e.g., a PDU session establishment accept message) to the UE for the PDU session of the network slice associated with the NS PDU monitoring timer. For example, the SMF can start the NS PDU monitoring timer for the UE's PDU session based on ABNSAC configuration information. For example, the SMF can start the NS PDU monitoring timer for the PDU session if conditions indicated by information on when to start the timer are met. For example, the SMF can start the NS PDU monitoring timer based on a notification from the UPF managing the PDU session. For example, the UPF can monitor for the presence of activity for the PDU session. When the UPF detects inactivity for the PDU session within a configured time period (e.g., no data sent from the UE and / or no data sent to the UE), the UPF can report the inactivity to the SMF. For the UPF to detect inactivity, the SMF can send information about the configured time period to the UPF. Based on notifications of PDU session inactivity from the UPF, the SMF can start a timer (NS PDU monitoring timer) for the PDU session.

[0334] In the example, the SMF can manage NS PDU monitoring timers for PDU sessions. For instance, based on ABNSAC configuration information, the SMF can manage NS PDU monitoring timers for PDU sessions. For example, when the SMF sends and / or receives from the UE NAS messages (e.g., PDU session establishment request / accept message, PDU session modification request / accept message) for a PDU session in a network slice, the SMF can restart the NS PDU monitoring timer for that PDU session. For example, when the SMF sends (and / or receives from) the NG-RAN N2 message (e.g., PDU session resource message) and / or when the SMF sends (and / or receives from) the AMF N11 message (e.g., Nsmf_PDUSession_UpdateSMcontext message) for a PDU session in a network slice, the SMF can restart the NS PDU monitoring timer for that PDU session. For example, when the SMF detects activity in a PDU session for a network slice and / or when the SMF receives a notification for a PDU session for a network slice, the SMF can restart / stop a timer for the PDU session for the network slice. For example, when the NG-RAN and / or UPF receive data for a PDU session for a network slice, the NG-RAN and / or UPF can send a notification to the SMF that data service activity of the PDU session has been detected.

[0335] In the example, the SMF can determine whether an event has occurred for a PDU session targeting a network slice. For example, based on ABNSAC configuration information, the SMF can determine whether an event has occurred for a PDU session targeting a network slice. For example, the event could be the expiration of a network slice NS PDU monitoring timer used for the PDU session. For example, if the timer expires, the SMF can send a report message (e.g., an Nnsacf_NSAC_NumOfPDUsUpdate request, etc.) to a network node (e.g., the NSACF, indicated by information on where to report ABNSAC configuration information). The report can indicate that a timer for a PDU session targeting a network slice has expired. The report message sent by the SMF can include at least one of the UE identifier, the PDU session identifier, the network slice identifier, and / or an indication of timer expiration.

[0336] In the example, NSACF can receive report messages sent by SMF. Based on the report messages, NSACF can determine whether to release / retain the PDU session of the network slice.

[0337] In one example, to determine whether to release / retain a PDU session for a network slice, the NSACF can use information about the number of PDU sessions established for the network slice. For example, if conditions are met (e.g., the number of PDU sessions established for the network slice reaches the maximum number of PDU sessions established for the network slice, the number of PDU sessions established for the network slice exceeds a threshold, or a timer expires), the NSACF can determine to release the PDU session for the network slice. The release of the PDU session for the network slice can be performed by the SMF and / or the UE. For example, if conditions are not met, the NSACF can determine to retain the PDU session for the network slice. Retaining the PDU session for the network slice may mean that the PDU session is not released and / or the PDU session for the network slice is terminated and / or the state of the PDU session for the network slice (e.g., active / inactive) remains unchanged.

[0338] In one example, to determine whether to release / retain a PDU session for a network slice, the NSACF can use information about the number of PDU sessions active for the network slice. For example, if conditions are met (e.g., the number of PDU sessions active for the network slice reaches the maximum number of PDU sessions active for the network slice, the number of PDU sessions active for the network slice exceeds a threshold, or a timer expires), the NSACF can determine to release the PDU session used for the network slice. Releasing a PDU session for the network slice can mean the PDU session is terminated and / or released. Conversely, if conditions are not met, the NSACF can determine to retain the PDU session used for the network slice. Retaining a PDU session used for the network slice can mean the PDU session may not be released and / or the PDU session used for the network slice may be terminated and / or the state of the PDU session used for the network slice may remain unchanged.

[0339] In one example, to determine whether to release / retain PDU sessions for a network slice, the NSACF can use information about the number of PDU sessions active for the network slice and / or the number of PDU sessions established for the network slice. For example, if a first condition is met (e.g., the number of PDU sessions established for the network slice reaches the maximum number of PDU sessions established for the network slice), the NSACF can determine to release the PDU sessions used for the network slice. For example, if a second condition is met (e.g., the number of PDU sessions established for the network slice does not reach the maximum number of PDU sessions established for the network slice, the number of PDU sessions active for the network slice reaches the maximum number of PDU sessions active for the network slice, and / or a timer expires), the NSACF can determine to terminate and / or release the PDU sessions used for the network slice. For example, if a third condition is met (e.g., the number of PDU sessions active for the network slice does not reach the maximum number of PDU sessions active for the network slice, and a timer expires), the NSACF can determine to retain the PDU sessions used for the network slice.

[0340] For example, the NSACF can manage the number of PDU sessions active for a network slice and / or the maximum number of PDU sessions active for a network slice. The number of PDU sessions active for a network slice can be used to calculate the total number of PDU sessions active for a network slice. If the network resources used for the PDU session are allocated in NG-RAN and / or in the UPF, the PDU session for the network slice can be interpreted as active. For example, NG-RAN can allocate network resources (e.g., radio resources, RLC, MAC, PDCP) for the PDU session. For example, the UPF can allocate network resources (e.g., N3 tunnel endpoints for NG-RAN, etc.) for the PDU session. For an established PDU session, the PDU session can be active (activated) or inactive (deactivated). The number of established PDU sessions for a network slice can be the sum of the number of active PDU sessions for the network slice and the number of inactive PDU sessions for the network slice. If one or more PDU sessions for a network slice are deactivated, the number of PDU sessions active for the network slice can be equal to or less than the number of PDU sessions established for the network slice.

[0341] In the example, based on the determination of whether to release / maintain the PDU session for the network slice, the NSACF can send a report response message (e.g., an Nnsacf_NSAC_NumOfPDUsUpdate response, etc.) to the SMF. The report response message may include at least one of the following: network slice information, information on whether to maintain / release / cancel the PDU session used for the network slice, time period information (e.g., the time period during which the UE may not request the activation of the PDU session and / or the time period during which the UE may not request the establishment of the PDU session used for the network slice), the identifier of the PDU session, and the identifier of the UE. Based on the received report response message, the SMF can determine whether to maintain / release / cancel the PDU session for the network slice for the UE.

[0342] In the example, if the received report response message indicates that the PDU session used for network slicing should be released, the SMF can send a message to the UE (e.g., a PDU session release command). In the example, if the received report response message indicates that the PDU session used for network slicing will be retained (cancelled), the SMF can send a message to the UE (e.g., a PDU session cancellation command). The message sent to the UE may include at least one of the following: the identifier of the PDU session, the identifier of the UE, the identifier of the network slice, the reason for release / cancellation (e.g., the PDU session will be released / cancelled due to inactivity, the network slice quota has been reached (e.g., the maximum number of PDU sessions established for the network slice has been reached, the maximum number of PDU sessions activated for the network slice has been reached)), information about the time period during which the UE cannot request the activation of the PDU session, information about the time period during which the UE cannot request the establishment of the PDU session used for network slicing, and / or information that the PDU session is released / cancelled due to inactivity.

[0343] In the example, the UE can receive messages sent by the SMF. If the message sent by the SMF includes time period information during which the UE cannot request activation of a PDU session, the UE can start a timer based on the time period information. If the timer is running and / or if the time period has not elapsed, the UE cannot request activation of the PDU session. If the message sent by the SMF includes time period information during which the UE cannot request the establishment of a PDU session for network slicing, the UE can start a timer based on the time period information. If the timer is running and / or if the time period has not elapsed, the UE cannot request the establishment of a PDU session for network slicing.

[0344] In the example, if the received report response message indicates that the PDU session used for network slicing will be released (cancelled), the SMF can send an N2 message (e.g., an N2 SM resource release request) to the NG-RAN. Based on the received N2 message, the NG-RAN can release the RRC connection with the UE, release the radio resources allocated for the PDU session, and / or switch the UE to RRC inactive mode. In the example, if the received report response message indicates that the PDU session used for network slicing will be released and / or cancelled, the SMF can send an N4 message (e.g., an N4 session release request) to the UPF. Based on the received message, the UPF can release the N3 resources of the PDU session.

[0345] Figure 32 An example implementation of this disclosure is depicted. In the example, a network node can use ABNSAC configuration to monitor PDU session activity for network slice quota management. In the example, a network node can use ABNSAC configuration to manage resources used for PDU sessions.

[0346] In the example, one or more network nodes (e.g., NSACF, SMF, AMF, UPF, NG-RAN, and / or UE) can receive ABNSAC configuration information. To receive ABNSAC configuration information, one can use methods such as... Figure 21 , Figure 22 , Figure 23 , Figure 24 , Figure 25 , Figure 26 , Figure 27 One or more examples are shown. In the examples, ABNSAC configuration information can be as follows: Figure 28 , 31 The example shows the ABNSAC configuration. In the example, the SMF can determine the expiration of the timer, such as... Figure 31 As shown in the example.

[0347] In the example, when the timer for a PDU session used for network slicing expires, the SMF can perform one or more actions. For example, one or more actions can be based on information about the actions to be performed when the timer expires, and / or on local configuration information. One or more actions can indicate one or more actions to be performed by the SMF when the timer expires. For example, when the timer for a PDU session used for network slicing expires, the SMF can determine whether to maintain / release / cancel the PDU session used for network slicing based on one or more actions. For example, based on one or more actions indicating release, the SMF can determine to release the PDU session used for network slicing. Based on the determination of release, the SMF can send a message to the UE (e.g., a PDU session release command message), such as... Figure 31As illustrated in the example. For instance, based on one or more action indications for release, the SMF can determine to release a PDU session used for network slicing. Based on the determination of release, the SMF can send messages to the NG-RAN and / or to the UPF (e.g., N2 messages (e.g., N2 SM resource release request) and / or N4 messages (e.g., N4 session release request)), such as... Figure 31 As shown in the example.

[0348] Figure 33 An example implementation of this disclosure is depicted. In the example, a network node can use ABNSAC configuration to monitor PDU session activity for network slice quota management. In the example, a network node can use ABNSAC configuration to manage resources used for PDU sessions.

[0349] In the example, one or more network nodes (e.g., NSACF, SMF, AMF, UPF, NG-RAN, and / or UE) can receive ABNSAC configuration information. To receive ABNSAC configuration information, one can use methods such as... Figure 21 , Figure 22 , Figure 23 , Figure 24 , Figure 25 , Figure 26 , Figure 27 One or more examples are shown. In the examples, ABNSAC configuration information can be as follows: Figure 28 The example shows the ABNSAC configuration.

[0350] In the example, the UE can receive ABNSAC configuration information from network nodes (e.g., AMF, UDM, NSACF, PCF, SMF) using NAS messages (e.g., PDU session establishment accept messages, UE configuration updates, etc.) for the network slices to which ABNSAC can be applied. If the UE supports ABNSAC applied to one or more network slices, the ABNSAC configuration information may include information for one or more network slices and / or for one or more PDU sessions.

[0351] In the example, based on ABNSAC configuration information, the UE can start an NS PDU monitoring timer for a PDU session used for network slicing. For example, the UE can start the NS PDU monitoring timer based on receiving a NAS message (e.g., a PDU session establishment accept message, a UE configuration update, etc.). For example, based on receiving ABNSAC configuration information associated with a PDU session used for network slicing, the UE can start the NS PDU monitoring timer for that PDU session. For example, the UE can start the NS PDU monitoring timer using the timer value from the ABNSAC configuration information.

[0352] In the example, based on ABNSAC configuration information, the UE can manage NS PDU monitoring timers for network slices. For instance, when the UE sends and / or receives NAS messages for PDU sessions used in network slices (e.g., PDU session modification request / accept message), the UE can restart the NS PDU monitoring timer for the network slice. Similarly, when the UE sends and / or receives services for PDU sessions used in network slices, the UE can restart the NS PDU monitoring timer for the PDU sessions used in network slices.

[0353] In the example, the UE can determine whether an event has occurred for a PDU session used for network slicing. For example, based on ABNSAC configuration information, the UE can determine whether an event has occurred for a PDU session used for network slicing. For example, the UE can determine whether the NS PDU monitoring timer for the PDU session used for network slicing has expired. When the timer for the PDU session used for network slicing expires and / or when an event occurs, the UE can perform one or more actions. For example, information about the actions to be performed when the timer expires can indicate one or more actions to be performed by the UE when the timer expires. For example, the UE can determine whether to maintain / release / deactivate the PDU session used for the network slice whose timer has expired. For example, based on one or more actions indicating release, the UE can determine to release the PDU session used for the network slice. Based on the determination, the UE can send a message (e.g., a PDU session release message) to the SMF. The message sent by the UE can include at least one of the PDU session identifier and / or a cause value. The cause value can indicate that inactivity was detected for the PDU session used for network slicing, and / or that the PDU session timer has expired. For example, based on one or more action indications, the UE may determine that it requests the termination of a PDU session for a network slice, requests the release of an RRC connection, and / or requests a transition to an RRC inactive state. Based on this determination, the UE may send a message to the SMF (e.g., a PDU session termination request message), to the AMF (e.g., a service request message, a service release message, an N1 release message), and / or to the NG-RAN (e.g., an RRC connection release message, an RRC inactive state request). Messages sent by the UE to the SMF may include at least one of the PDU session identifier, a cause value, and / or a termination request. The cause value may indicate that inactivity was detected for the PDU session used for the network slice, and / or that a PDU session timer has expired. Messages sent by the UE to the AMF may include at least one of the PDU session identifier, a cause value, a termination request for the PDU session, and / or a request to release an N1 connection. The message sent by the UE to the NG-RAN may include at least one of the following: a PDU session identifier, a cause value, a request for a state transition to the RRC-inactive state, and / or information about radio resources associated with a PDU session whose timer has expired. Based on the message sent by the UE, the AMF, SMF, and / or NG-RAN may release resources used for PDU sessions associated with network slices.

[0354] Figure 34 An example implementation of this disclosure is depicted. In the example, a network node can use ABNSAC configuration to monitor PDU session activity for network slice quota management. In the example, a network node can use ABNSAC configuration to manage resources used for PDU sessions.

[0355] In the example, one or more network nodes (e.g., NSACF, SMF, AMF, UPF, NG-RAN, and / or UE) can receive ABNSAC configuration information. To receive ABNSAC configuration information, one can use methods such as... Figure 21 , Figure 22 , Figure 23 , Figure 24 , Figure 25 , Figure 26 , Figure 27 One or more examples are shown. In the examples, ABNSAC configuration information can be as follows: Figure 28 The example shows the ABNSAC configuration.

[0356] In the example, for a PDU session, the PCF can determine one or more parameters used for the PDU session. For example, the PCF can determine one or more configuration information for the PDU session. One or more configuration information may include a first time interval (e.g., inactivity detection time) and / or a second time interval (NS monitoring time). The first time interval can be used to manage resources at the UPF and / or NG-RAN (e.g., N3 tunnel resources). For example, when there is no data traffic for the PDU session during the duration of the first time interval, the UPF can report to the SMF that data inactivity was detected during the first time interval. Based on the report, the SMF can determine to release resources used for the PDU session (e.g., N3 tunnel resources, RRC resources). For example, when there is no data traffic for the PDU session during the duration of the second time interval, the UPF can report to the SMF that data inactivity was detected during the second time interval. Based on the lack of activity during the second time interval, the SMF can determine to release the PDU session. For the configuration of the second time interval, the PCF can send a request to the NSACF associated with the network slice for which the PDU session was established. Based on the network slice information, the NSACF can send information about the value of the second time interval to the SMF. For example, the second time interval can be the value of the NS PDU monitoring timer. The PCF can send one or more determined configuration parameters to the SMF.

[0357] In the example, the SMF can receive one or more configuration parameters sent by the PCF. The SMF can receive information about a first time interval and / or a second time interval for a PDU session used for network slicing. If the PCF does not send information about the second time interval, the SMF can use information from its local configuration for the second time interval and / or can receive information about the second time interval from the NSACF. For example, the SMF can obtain the second time interval information based on ABNSAC configuration information. Based on the information about the first time interval and / or the second time interval, the SMF can send an N4 message (e.g., an N4 session configuration message) to the UPF. The N4 message may include information about the first time interval and / or the second time interval.

[0358] In the example, the UPF can receive information about a first time interval and / or a second time interval from the SMF for a PDU session. The UPF can monitor activity on the PDU session. If the UPF does not detect activity on the PDU session during the duration of the first time interval, the UPF can send a first N4 session report message to the SMF. The first N4 session report message can indicate at least one of the following: inactivity of the PDU session, inactivity during the duration of the first time interval, and / or inactivity of the N3 interface. Based on the received first N4 session report message, the SMF can determine to terminate the PDU session. If the UPF does not detect activity on the PDU session during the duration of the second time interval, the UPF can send a second N4 session report message to the SMF. The second N4 session report message can indicate the inactivity of the PDU session used for network slicing, inactivity during the duration of the second time interval, and / or inactivity of the network slice. Based on the received second N4 session report message, the SMF can determine to release the PDU session and / or can determine to send a report message (e.g., Nnsacf_NSAC_NumOfPDUsUpdate) to the NSACF responsible for the network slice associated with the PDU session. Based on the report message from the SMF, the NSACF can determine whether to maintain / release / release the PDU session used for the network slice. For example, when the SMF receives the second N4 session report message from the UPF, it can use a method such as... Figure 31 , 32 The example shown is for timer expiration.

[0359] Figure 35 An example implementation of this disclosure is depicted. In the example, a network node can use ABNSAC configuration to monitor PDU session activity for network slice quota management. In the example, a network node can use ABNSAC configuration to manage resources used for PDU sessions.

[0360] In the example, NG-RAN can monitor the activity of a PDU session. For instance, NG-RAN can start an NS PDU monitoring timer. NG-RAN can also report timer expiration to the SMF and / or NSACF.

[0361] Figure 36 An example implementation of this disclosure is depicted. In the example, a network node can use ABNSAC configuration to monitor UE activity for network slice quota management. In the example, a network node can use ABNSAC configuration to manage resources used for the UE.

[0362] In the example, a first network node (e.g., AMF, SMF) can receive configuration parameters (e.g., ABNSAC configuration information) from a second network node (e.g., NSACF, UDM, PCF, UDR, AF). The configuration parameters may include at least one value of one or more timers for one or more network slices and / or at least one identifier of one or more network slices. The one or more network slices may include at least one of a first network slice and / or a second network slice. The configuration parameters (e.g., ABNSAC configuration information) may include at least one of a first value of a first timer for the first network slice and / or a second value of a second timer for the second network slice.

[0363] In the example, the first network node can receive a NAS request (e.g., registration request, PDU session establishment request) message from the UE for the first network slice. For example, the NAS request message may include the identifier of the first network slice.

[0364] In the example, based on the NAS request message received from the UE, the first network node can send a NAS response message (e.g., registration acceptance, PDU session establishment acceptance) to the UE. The NAS response message may include the identifier of the first network slice.

[0365] In the example, the first network node can start a first timer. For example, based on receiving a NAS request message from the UE, based on sending a NAS response message to the UE, and / or based on configuration parameters for the first network slice, the first network node can start a first timer for the first network slice with the value of the first timer in the configuration parameters. For example, based on a notification of inactivity of the first network slice, the first network node can start the first timer.

[0366] In the example, the first network node can determine whether a first timer for a first network slice used by the UE has expired. For example, the first network node can restart the first timer based on one or more events. For example, if the first network node receives a message associated with the first network slice, the first network node can restart the first timer. For example, if the UE sends and / or receives data for the first network slice, the first network node can restart the first timer.

[0367] In the example, based on the determination that the first timer has expired, the first network node can send a message to the third network node (e.g., NSACF, AF). The message may include information such as the expiration of the first timer for the UE used for the first network slice, the detection of inactivity in the first network slice, the need to decrement the counter for the first network slice, the identifier of the PDU session for the first network slice, the identifier of the UE, the identifier of the first network slice, the release of the PDU session, and the cancellation of the UE for the first network slice.

[0368] In the example, the first network node may send a second message to the UE (e.g., a UE configuration update message, a PDU session release command). For example, the first network node may determine to release and / or terminate the PDU session used for the first network slice. For example, the first network node may determine to deregister the UE for the first network slice. For example, the first network node may determine to release / deregister / deregister based on a response. For example, a third network node may send a response to the first network node.

[0369] Figure 37 An example implementation of this disclosure is depicted. In the example, a network node can use ABNSAC configuration to monitor network slice activity for network slice quota management. In the example, a network node can use ABNSAC configuration to manage resources used for network slices.

[0370] In the example, the UE can send a first NAS request (e.g., registration request, PDU session establishment request) message to a network node (e.g., AMF, SMF) for one or more network slices. The one or more network slices may include at least the first network slice.

[0371] In the example, based on the first NAS request message, the UE can receive a first NAS response message (e.g., registration response, PDU session establishment response) from the network node.

[0372] In the example, the UE can receive configuration parameters (e.g., ABNSAC configuration information) from a network node. For example, based on the first NAS request message including information about a first network slice, the UE can receive configuration parameters including information associated with the first network slice. The configuration parameters may include at least one of one or more values ​​of one or more timers for one or more network slices and / or at least one or more identifiers of one or more network slices. The one or more network slices may include at least the first network slice. The configuration parameters may include at least a first value of a first timer for the first network slice. For example, the configuration parameters may include ABNSAC configuration information.

[0373] In the example, the UE can start a first timer based on configuration parameters. For example, based on receiving a first NAS response message from a network node and / or based on configuration parameters for a first network slice, the UE can start a first timer for the first network slice with a first value of the first timer.

[0374] In the example, the UE can determine whether a first timer for the first network slice has expired. For example, the UE can restart the first timer based on one or more events. For example, one or more events could be the UE sending and / or receiving messages associated with the first network slice, and / or the UE sending and / or receiving data for the first network slice.

[0375] In the example, based on the determination that the first timer has expired, the UE can send a message to the network node. The message may include information such as the expiration of the first timer for the first network slice, the detection of inactivity in the first network slice, the need to decrement the counter for the first network slice, the identifier of the PDU session for the first network slice, the identifier of the UE, and / or the identifier of the first network slice.

[0376] In the example, the UE can send a second NAS request message (e.g., a registration request, a PDU session release request) to the network node. The second NAS message may include at least one of a request to release the PDU session, a request to deregister the first network slice, etc.

[0377] In the example, a first network node (e.g., AMF) can receive configuration information for quota management (e.g., network slice quota management) from a second network node (e.g., NSACF, PCF, UDM, UDR, AF). For example, for network slices, quota management can be network slice admission control. Network slice admission control can include admission control of radio device and / or packet data unit (PDU) sessions based on at least one of the following: the number of registered radio devices for the network slice, the number of established PDU sessions for the network slice, the number of active radio devices for the network slice, the number of activated PDU sessions for the network slice, and / or the number of deactivated PDU sessions for the network slice. For example, quota management (e.g., network slice admission control) can allow / request the registration / deregistration of radio devices for network slices, and / or can allow / request the establishment / release / deactivation of PDU sessions of radio devices for network slices.

[0378] In the example, based on sending a request to the second network node (e.g., an Nnsacf_NSAC_NumOfUEsUpdate request), the first network node can receive configuration information for quota management from the second network node. For example, the request sent by the first network node to the second network node may include at least one of the following: an indication of whether to increase the number of wireless devices registered to the network slice, the identity of the wireless devices, the allowed access type for the network slice, the identity of the network slice, and the identity of the first network node. For example, the second network node can use the number of wireless devices registered to the network slice to track the number of wireless devices registered for the network slice, and / or can manage the list of wireless devices allowed for the network slice. For example, when it is necessary to register wireless devices for the network slice, the indication of whether to increase the number of wireless devices registered to the network slice may indicate an increase.

[0379] In the example, based on receiving a registration request message from the wireless device, the first network node may send a request (e.g., an Nnsacf_NSAC_NumOfUEsUpdate request) to the second network node. The registration request message may include at least one of the following: information containing a list of requested network slices (e.g., S-NSSAI) and / or the identity of the wireless device. In response to receiving the registration request message from the wireless device, the first network node may send a response message to the wireless device including one or more identities permitted for use with the wireless device's network slices. The one or more identities permitted for use with the wireless device's network slices may include at least the network slices associated with a timer (e.g., an NS UE monitoring timer).

[0380] In the example, the configuration information received from the second network node may include at least one of the following: a timer value associated with quota management of the network slice, the identity of the network slice, and / or an indication of whether the maximum number of wireless devices registered to the network slice has been reached. For example, the second network node may use the maximum number of wireless devices registered to the network slice to limit the number of wireless devices registered for the network slice. For example, when the number of wireless devices registered to the network slice reaches the maximum number of wireless devices registered to the network slice, the second network node may send a rejection of the indication received from the first network node. Based on this rejection from the second network node, the first network node may reject the registration request for the network slice from the wireless devices. The second network node may determine the configuration information sent to the first network node based on information from the application server. The application server may use the network slice and / or may manage the network slice. In the example, the configuration information may also include at least one of the following: an indication of whether the number of wireless devices registered for the network slice has reached a threshold, an indication of whether the number of wireless devices registered for the network slice has not reached a threshold, whether the first network node needs to start a timer for the wireless devices, and / or information on the time period during which registration requests for the network slice are not allowed.

[0381] In the example, the second network node can perform admission control for at least one of the wireless devices on a network slice basis. For example, the second network node may include a Network Slice Admission Control Function (NSACF). In the example, the first network node can manage access and mobility control for the wireless devices. For example, the first network node may include an Access and Mobility Control Function (AMF).

[0382] In the example, the first network node can start a timer for the wireless device using a timer value configured in the configuration information. For example, the timer can be associated with network slicing and / or quota management for network slicing. For instance, the first network node can start the timer when a network slice is allowed for use with the wireless device, when the first network node sends a message including one or more identities of the network slice allowed for use with the wireless device, when a PDU session established through a network slice is released, and / or when no more PDU sessions established through a network slice exist.

[0383] In the example, for a wireless device, the first network node can restart a timer associated with a network slice. For example, the first network node can restart the timer when a PDU session is established for a network slice, when a message for a PDU session is received, and / or when a message associated with a network slice is received from the wireless device.

[0384] In the example, for a wireless device, the first network node can stop the timer associated with the network slice. For example, the first network node can stop the timer when a PDU session is established for the network slice and / or when the network slice is deregistered for the wireless device.

[0385] In the example, the first network node can determine whether a timer used for the wireless device has expired. For example, a timer may expire if it does not stop for the period indicated by the value of the persistent timer after the timer is started and / or restarted. Similarly, a timer may expire if it runs for the period indicated by the value of the persistent timer after the timer is started or restarted.

[0386] In the example, based on the determination of the timer expiration for the wireless device, the first network node can send an indication to the second network node. The indication may include at least one of the following: an indication of the timer expiration for the wireless device, the identity of the wireless device, and / or the identity of the network slice.

[0387] In the example, based on an indication received from the first network node (e.g., an indication of a timer expiring for a wireless device), the second network node may determine that a network slice is not allowed for a wireless device associated with a timer expiring, request the deregistration / release of the network slice for a wireless device, and / or update the number of wireless devices registered for the network slice.

[0388] In the example, based on an indication that a timer associated with a network slice for a wireless device has expired, the first network node can receive from the second network node a message including at least one of a request to deregister / release a network slice for the wireless device and / or an indication that the maximum number of UEs registered for the network slice has been reached. Based on the message received from the second network node, the first network node can send to the wireless device a message including at least one of the following (e.g., UE configuration update, registration rejection): an indication to deregister, release, or reject a network slice for the wireless device; an indication of the reason for deregistering the network slice based on the inactivity of the wireless device; a period during which registration requests for the network slice are not allowed; one or more allowed network slices (allowed S-NSSAIs) and / or one or more rejected network slices (rejected S-NSSAIs).

[0389] In the example, a third network node (e.g., SMF) can receive configuration information for quota management from a second network node (e.g., NSACF, PCF, UDM, UDR, AF).

[0390] In the example, based on sending a request to the second network node (e.g., an Nnsacf_NSAC_NumOfPDUsUpdate request), the third network node can receive configuration information for quota management from the second network node. For example, the request sent by the third network node to the second network node may include at least one of the following: an indication of whether to increase the number of established PDU sessions for network slices; an indication of whether to increase the number of active PDU sessions for network slices; the identity of the wireless device; the identity of the PDU session; the access type for establishing the PDU session; the identity of the network slice; and / or the identity of the third network node. For example, the second network node can use the number of established PDU sessions for network slices to track the number of PDU sessions established for network slices. For example, the second network node can use the number of active PDU sessions for network slices to track the number of active PDU sessions for network slices. For example, the second network node can manage a list of wireless devices that have established PDU sessions for network slices. For example, the indication of whether to increase the number of established PDU sessions for network slices when it is necessary to establish a PDU session for a network slice may indicate an increase. For example, when it is necessary to activate PDU sessions for a network slice, an indication of whether to increase the number of activated PDU sessions for the network slice can indicate an increase.

[0391] In the example, a third network node may send a request to a second network node based on receiving PDU session-related messages (e.g., PDU session establishment request message, PDU session modification message, Nsmf_PDUSession_UpdateSMContext) from a wireless device and / or a first network node (e.g., AMF). PDU session-related messages may include at least one of network slice information (e.g., S-NSSAI), the identity of the wireless device, and / or the identity of the PDU session. In response to receiving the PDU session-related request message from the wireless device and / or the first network node, the third network node may send a response message (e.g., PDU session establishment acceptance message, Namf_Communication_N1N2MessageTransfer). The response message may include at least one of the identity of the network slice, the identity of the PDU session, and / or the result. The identity of the network slice may be associated with a timer (e.g., an NS PDU monitoring timer).

[0392] In the example, the configuration information received from the second network node may include at least one of the following: the value of a timer associated with quota management for the network slice; the identity of the network slice; an indication of whether the maximum number of established PDU sessions for the network slice has been reached; and / or an indication of whether the maximum number of active PDU sessions for the network slice has been reached. For example, the second network node may use the maximum number of established PDU sessions for the network slice to limit the number of PDU sessions established for the network slice. For example, when the number of established PDU sessions for the network slice reaches the maximum number of established PDU sessions for the network slice, the second network node may determine to reject an indication from the third network node (e.g., the need to increase the number of established PDU sessions). Based on this rejection determination, the third network node may reject PDU session-related messages (e.g., PDU session establishment requests) from the wireless device for the network slice. For example, the second network node may use the maximum number of active PDU sessions for the network slice to limit the number of active PDU sessions for the network slice. For example, when the number of active PDU sessions for network slicing reaches the maximum number of active PDU sessions for network slicing, the second network node can determine to reject an instruction from the third network node (e.g., the need to increase the number of active PDU sessions). Based on this rejection determination, the third network node can reject messages related to PDU sessions for network slicing (e.g., Namf_Communication_N1N2MessageTransfer). For example, to determine configuration information, the second network node can use information from an application server. The application server can use network slicing and / or can manage network slicing. In the example, the configuration information may also include at least one of the following: whether the number of established PDU sessions for network slicing has reached a threshold, whether the number of active PDU sessions for network slicing has reached a threshold, the result of a timer for whether the third network node needs to start a PDU session for network slicing, and / or information about time periods during which requests related to PDU sessions for network slicing are not allowed for wireless devices.

[0393] In the example, the second network node can perform admission control (e.g., quota management) on at least one PDU session for a network slice. For example, the second network node can include at least a Network Slice Admission Control Function (NSACF). In the example, the third network node can manage sessions for wireless devices (e.g., PDU sessions). For example, the third network node can include a Session Management Function (SMF).

[0394] In the example, the third network node can start a timer for a PDU session using a timer value configured in the configuration information. For example, the timer can be associated with network slicing, quota management for network slicing, and / or quota management for PDU sessions. For instance, the third network node can start the timer when a PDU session for network slicing is established for a wireless device, when the third network node sends session-related messages (e.g., PDU session establishment request, Namf_Communication_N1N2MessageTransfer) for a PDU session for network slicing, when the PDU session is activated, and / or when the inactivity of a PDU session is notified.

[0395] In the example, for a PDU session, the third network node can restart a timer associated with a network slice. For example, the third network node can restart the timer when the PDU session is activated, when a session-related message for the PDU session is received, and / or when activity is detected for the PDU session.

[0396] In the example, for a PDU session, the third network node can stop the timer associated with the network slice. For example, the third network node can stop the timer when releasing the PDU session for the network slice, and / or when deregistering the network slice for a wireless device.

[0397] In the example, the third network node can determine whether a timer used for a PDU session has expired. For example, if the timer does not stop within the time period following its start and / or restart, the timer has expired.

[0398] In the example, based on the determination of the timer expiration for the PDU session, the third network node can send an indication to the second network node. The indication may include at least one of the following: an indication of the timer expiration for the PDU session, the identity of the wireless device, the identity of the network slice, and / or the identity of the PDU session.

[0399] In the example, based on an indication received from the third network node (e.g., an indication that a PDU session's timer has expired), the second network node can determine whether to release / cancel / hold the PDU session for the wireless device associated with the timer expiration, whether to request the release / cancel / hold of the PDU session for a network slice, whether to update the number of established PDU sessions, and / or whether to update the number of active PDU sessions. For example, the second network can send determining information to the third network node.

[0400] In the example, based on an indication of a timer associated with the expiration of a network slice for a PDU session, the third network node can receive a message associated with the determination from the second network node. The message may include at least one of a request to release / cancel a PDU session used for the network slice, an indication that the maximum number of established PDU sessions for the network slice has been reached, and / or an indication that the maximum number of active PDU sessions for the network slice has been reached. Based on the message received from the second network node, the third network node may send a message to the wireless device including at least one of the following (e.g., a PDU session release command and / or a PDU session termination command): an indication that a PDU session needs to be released / canceled, an indication of the reason for the release / cancel of the PDU session based on the inactivity of the wireless device, and / or information regarding a period during which requests for PDU sessions (e.g., service requests, PDU session establishment requests) are not permitted.

[0401] In the example, a first network node (e.g., AMF, SMF) can receive configuration information for quota management from a second network node (e.g., NSACF, PCF, UDM, UDR, AF). For example, the configuration information received from the second network node may include at least one of a timer value associated with quota management for a network slice, the identity of the network slice, and / or an indication of whether a quota for the network slice has been reached. In the example, the first network node may start a timer using the timer value from the configuration information. In the example, the first network node may determine whether the timer has expired. In the example, based on the determination that the timer has expired, the first network node may send a timer expiration indication to the second network node.

[0402] In the example, a first network node (e.g., AMF) can receive configuration information for quota management from a fourth network node (e.g., PCF, UDM, UDR, AF). For example, the configuration information received from the fourth network node may include at least one of the following: a timer value associated with quota management for a network slice, the identity of the network slice, and / or an indication of whether a quota for the network slice has been reached. In the example, the first network node can determine whether a timer has expired. In the example, based on the determination of timer expiration, the first network node can send a timer expiration indication to a second network node (e.g., NSACF).

[0403] In the example, a first network node (e.g., AMF) can receive configuration information for quota management from a fourth network node (e.g., PCF, UDM, UDR, AF, NSACF). For example, the configuration information received from the fourth network node may include at least one of a timer value associated with quota management for a network slice, the identity of the network slice, and / or an indication of whether a quota for the network slice has been reached. In the example, the first network node may start a timer with a timer value for configuration information for a wireless device.

[0404] In the example, a third network node (e.g., SMF) can receive configuration information for quota management from a fourth network node (e.g., PCF, UDM, UDR, AF, NSACF). For example, the configuration information received from the fourth network node may include at least one of the following: a timer value associated with quota management for a network slice, the identity of the network slice, an indication of whether a quota for the network slice has been reached, and / or the identity of the PDU session. In the example, a first network node can determine whether a timer has expired. In the example, based on the determination of timer expiration, the first network node can send a timer expiration indication to a second network node (e.g., NSACF).

[0405] In the example, a third network node (e.g., SMF) can receive configuration information for quota management from a fourth network node (e.g., PCF, UDM, UDR, AF, NSACF). For example, the configuration information received from the fourth network node may include at least one of the following: a timer value associated with quota management for a network slice, the identity of the network slice, an indication of whether a quota for the network slice has been reached, and / or the identity of the PDU session. In the example, the third network node may start a timer with a timer value for configuration information used by the wireless device.

[0406] In the example, a first network node (e.g., AMF) can receive configuration information for quota management from a second network node (e.g., NSACF, PCF, UDM, UDR, AF). For example, the configuration information received from the second network node may include at least one of the following: a timer value associated with quota management for a network slice, the identity of the network slice, an indication of whether a quota for the network slice has been reached, and / or the identity of the PDU session. In the example, the first network node may start a timer with a timer value for the configuration information of the wireless device. In the example, the first network node may determine whether the timer has expired. In the example, based on the determination of timer expiration, the first network node may send at least one of the following to the wireless device: an indication that the timer has expired and / or an indication that the network slice of the wireless device is not allowed / rejected.

[0407] In the example, a third network node (e.g., SMF) can receive configuration information for quota management from a second network node (e.g., NSACF, PCF, UDM, UDR, AF). For example, the configuration information received from the second network node may include at least one of the following: a timer value associated with quota management for a network slice, the identity of the network slice, an indication of whether a quota for the network slice has been reached, and / or the identity of the PDU session. In the example, the third network node may start a timer with the timer value of the configuration information for the PDU session. In the example, the third network node may determine whether the timer has expired. In the example, based on the determination of timer expiration, the third network node may send at least one of the following to the wireless device: an indication that the timer has expired and / or an indication to the wireless device to release / cancel the PDU session.

[0408] In the example, a second network node (e.g., NSACF) can receive an indication from a first network node (e.g., AMF) that a timer associated with a network slice for a wireless device has expired. The second network node can then determine, based on this indication, to remove the wireless device from registration with the network slice. Based on this determination, the second network node can send a message to the first network node indicating that the wireless device's registration with the network slice will be rejected or removed.

[0409] In the example, the second network node (e.g., NSACF) can receive an indication from the third network node (e.g., SMF) that a timer associated with the network slice used for the PDU session has expired. The second network node can determine the status of the updated PDU session based on this indication. Based on the determination of the updated PDU session status, the second network node can send a message to the third network node indicating the updated status of the PDU session for the network slice.

[0410] In the example, a third network node (e.g., SMF) may send to a fifth network node (e.g., UPF, NG-RAN) at least one of a first configuration information for a timer associated with quota management for network slicing and / or a second configuration information for a timer associated with a PDU session. In the example, the third network node may receive from the fifth network node an indication of timer expiration associated with quota management for network slicing.

[0411] In the example, the fifth network node (e.g., UPF, NG-RAN) can receive from the third network node (e.g., SMF) at least one of a first configuration information for a timer associated with quota management for network slicing and / or a second configuration information for a timer associated with a PDU session. In the example, the fifth network node can send an indication to the third network node that a timer associated with quota management for network slicing has expired.

Claims

1. A method for managing network slices based on inactivity, comprising: The Access and Mobility Management Function (AMF) receives a value from the Unified Data Management (UDM) for the duration of inactivity associated with network slices used for wireless devices; as well as The AMF sends an instruction to the wireless device to remove the network slice when the duration expires.

2. The method of claim 1, further comprising: The duration is initiated by the AMF; as well as The duration expires based on the AMF and the value.

3. The method of claim 2, wherein the AMF initiates the duration based on at least one of the following: The network slice is permitted for use with the wireless device; Send a second message to the wireless device including one or more identities that are permitted for network slicing of the wireless device; Release the Protocol Data Unit (PDU) session established for the network slice for the wireless device; or PDU sessions will no longer be established on the network slice.

4. The method of claim 2, further comprising stopping the duration by the AMF based on at least one of the following: Establish a Protocol Data Unit (PDU) session for the network slice; The network slice is not permitted for use with the wireless device; or The network slice is deregistered for the wireless device.

5. The method of claim 2, further comprising restarting the duration by the AMF based on at least one of the following: The wireless device receives a message associated with a Protocol Data Unit (PDU) session established for the network slice; or Send a message associated with the network slice to the wireless device.

6. The method of claim 1, wherein the indication of removing the network slice indicates that the network slice is not permitted for use with the wireless device.

7. The method of claim 1, wherein the indication for removing the network slice includes a cause value indicating the inactivity of the network slice.

8. The method of claim 1, wherein the AMF receives the value from the UDM as part of configuration information for the network slice.

9. The method of claim 1, further comprising, before the AMF receives the value from the UDM, the AMF receiving a first message from the wireless device including an identifier of the network slice.

10. The method of claim 9, wherein the first message is a registration request message.

11. The method of any one of claims 1 to 10, further comprising sending an indication of the expiration of the duration to the Network Slice Access Control Function (NSCAF) by the AMF based on the expiration of the duration.

12. The method of claim 11, further comprising the AMF receiving a message from the NSCAF requesting the deregistration of the network slice for the wireless device.

13. The method of claim 12, further comprising sending an instruction from the AMF to the wireless device based on the message requesting the deregistration of the network slice for the wireless device.

14. An Access and Mobility Management Function (AMF), the AMF including one or more processors and a memory storing instructions, which, when executed by the one or more processors, cause the AMF to perform the method as described in any one of claims 1 to 13.

15. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method as described in any one of claims 1 to 13.

Images