Session management and policy control functions for charging control in non-public networks

Abstract

The Session Management Function (SMF) receives messages from the Access and Mobility Management Function (AMF). These messages include the PLMN identifier of the Public Land Mobile Network (PLMN) for the radio device. The SMF sends a Policy Request message to the Policy Control Function (PCF), which includes the NPN identifier of the Non-Public Network (NPN) and the PLMN identifier of the PLMN, through which the radio device accesses the PLMN. The SMF receives a Policy Response message from the PCF, which includes a charging control policy. Based on the Policy Response message, the SMF sends a Charging Data Request message to the Charging Function (CHF). This Charging Data Request message includes the PLMN identifier.

Description

[0001] This application is a divisional application of PCT application number PCT / US2020 / 025696, filed on March 30, 2020, which entered the Chinese national phase on November 29, 2021, with Chinese national application number 2020800398027, and entitled "Charging control method and system for non-public networks".

[0002] Cross-references to related applications

[0003] This application claims the benefit of U.S. Provisional Application No. 62 / 826,486, filed March 29, 2019, which is incorporated herein by reference in its entirety. Attached Figure Description

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

[0005] Figure 1 This is a diagram illustrating an example 5G system architecture according to aspects of embodiments of this disclosure.

[0006] Figure 2 This is a diagram illustrating an example 5G system architecture according to aspects of embodiments of this disclosure.

[0007] Figure 3 This is a system diagram of an example wireless device and network node in a 5G system according to aspects of embodiments of this disclosure.

[0008] Figure 4 This is a system diagram of an example network node according to an embodiment of the present disclosure.

[0009] Figure 5A and Figure 5B Two registration management state models in UE 100 and AMF 155 are described, representing aspects of embodiments of this disclosure.

[0010] Figure 6A and Figure 6B Two connection management state models in UE 100 and AMF 155 are described according to aspects of embodiments of this disclosure.

[0011] Figure 7 This is a diagram for classifying and labeling traffic according to aspects of embodiments of this disclosure.

[0012] Figure 8 and Figure 9 Example call stream of a registration procedure according to an embodiment of this disclosure.

[0013] Figure 10This is a diagram illustrating an example 5G strategy and charging control system architecture according to aspects of embodiments of this disclosure.

[0014] Figure 11 Example call stream for establishing a charged PDU session according to an embodiment of this disclosure.

[0015] Figure 12A Example diagrams depicting non-public networks that can be deployed as part of a PLMN are provided for embodiments of this disclosure. Figure 12B An example diagram illustrating how a non-public network can be isolated from a PLMN is depicted according to aspects of embodiments of this disclosure.

[0016] Figure 13A An example diagram is depicted to illustrate aspects of embodiments of the present invention, showing that a non-public network may consist of only one CAG. Figure 13B An example diagram is depicted to illustrate aspects of embodiments of this disclosure, showing that a non-public network may include more than one CAG.

[0017] Figure 14 An example diagram is depicted illustrating a UE accessing a different service provider PLMN via a non-public network, according to aspects of embodiments of this disclosure.

[0018] Figure 15 Example call stream according to aspects of embodiments of this disclosure.

[0019] Figure 16 Example diagrams depicting a PCF procedure according to aspects of embodiments of the present disclosure are shown.

[0020] Figure 17 Example diagrams of an SMF procedure are depicted according to aspects of embodiments of the present disclosure.

[0021] Figure 18 Example call stream according to aspects of embodiments of this disclosure.

[0022] Figure 19 Example call stream according to aspects of embodiments of this disclosure.

[0023] Figure 20 Example call stream according to aspects of embodiments of this disclosure.

[0024] Figure 21 A flowchart is provided for an aspect of an exemplary embodiment of this disclosure.

[0025] Figure 22 A flowchart is provided for an aspect of an exemplary embodiment of this disclosure.

[0026] Figure 23 A flowchart is provided for an aspect of an exemplary embodiment of this disclosure.

[0027] Figure 24 A flowchart is provided for an aspect of an exemplary embodiment of this disclosure.

[0028] Figure 25 A flowchart is provided for an aspect of an exemplary embodiment of this disclosure.

[0029] Figure 26 A flowchart is provided for an aspect of an exemplary embodiment of this disclosure. Detailed Implementation

[0030] The exemplary embodiments of the present invention enable the implementation of enhanced features and functionalities in 5G systems. More specifically, embodiments of the techniques disclosed herein may relate to charging controls for non-public networks (e.g., for 5G or future communication systems). Throughout this disclosure, UEs, wireless devices, and mobile devices are interchangeable. Throughout this disclosure, base stations, (radio)access networks ((R)AN), next-generation radio access networks (NG-RAN), new radio node Bs (gNBs), and next-generation eNodeBs (ng-eNBs) are interchangeable.

[0031] The following abbreviations are used throughout this disclosure:

[0032] 5G (Fifth Generation Mobile Network)

[0033] 5GC 5G Core Network

[0034] 5GS 5G system

[0035] 5G-AN 5G Access Network

[0036] 5QI 5G QoS Indicator

[0037] AF application functions

[0038] AMBR Aggregated Maximum Bit Rate

[0039] AMF Access and Mobility Management Functions

[0040] AN access network

[0041] AUSF Authentication Server Functionality

[0042] ARP allocation and retention priority

[0043] BD Billing Domain

[0044] CAG Closed Access Group

[0045] CDR Fee Data Records

[0046] CHF Paid Features

[0047] CN Core Network

[0048] CP control plane

[0049] DL downlink

[0050] DN Data Network

[0051] DNN Data Network Name

[0052] FDD (Frequency Division Duplex)

[0053] Fully Qualified Domain Name (FQDN)

[0054] GPSI General Public Subscription Identifier

[0055] GW gateway

[0056] HTTP (Hypertext Transfer Protocol)

[0057] ID identifier

[0058] IMS IP Multimedia Core Network Subsystem

[0059] IP Internet Protocol

[0060] IP-CAN IP connection access network

[0061] Layer 2 (Data Link Layer)

[0062] Layer 3 (Network Layer)

[0063] LADN Local Area Network Data Network

[0064] LAN (Local Area Network)

[0065] MAC Media Access Control

[0066] MCC Mobile Country Code

[0067] MNC Mobile Network Code

[0068] MICO only initiates connections via mobile.

[0069] N3IWF Non-3GPP Interoperability Function

[0070] NAS Non-Access Layer

[0071] NAT (Network Address Translation)

[0072] NEF Network Exposure Function

[0073] NF Network Functions

[0074] NR New Radio

[0075] NG-RAN NR Radio Access Network

[0076] NPN (Non-Public Network)

[0077] NRF Network Repository Functionality

[0078] NSI Network Slicing Example

[0079] NSSAI Network Slice Selection Auxiliary Information

[0080] NSSF Network Slice Selection Function

[0081] NWDAF Network Data Analysis Function

[0082] OAM Operations Management and Maintenance

[0083] PCC Policy and Fee Control

[0084] PCF policy control function

[0085] PDU (Packet Data Unit)

[0086] PEI Permanent Device Identifier

[0087] PLMN Public Land Mobile Network

[0088] QCI QoS Category Identifier

[0089] QFI QoS Flow Identifier

[0090] QoS (Quality of Service)

[0091] RA Random Access

[0092] RAN (Radio Access Network)

[0093] RAT Radio Access Technology

[0094] RRC Radio Resource Control

[0095] RM Registration Management

[0096] SBA Service-Based Architecture

[0097] SIB System Information Block

[0098] SM Session Management

[0099] SMF Session Management Function

[0100] SMSF SMS Function

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

[0102] SP service provider

[0103] SS synchronization signal

[0104] SSC Session and Service Continuity

[0105] SUPI subscriber permanent identifier

[0106] TA tracking area

[0107] TAI tracks regional identity

[0108] UDR Unified Data Storage

[0109] UDM Unified Data Management

[0110] UE User Equipment

[0111] UL uplink

[0112] UPF User Plane Functions

[0113] Example Figure 1 and Figure 2 A 5G system including an access network and a 5G core network is depicted. An example 5G access network may include an access network connected to the 5G core network. The access network may include NG-RAN 105 and / or non-3GPP AN 165. An example 5G core network may connect to one or more 5G access networks, 5G-AN and / or NG-RAN. The 5G core network may include, as shown in the example... Figure 1 and examples Figure 2 The functional elements or network functions in the system, wherein the interface can be used for communication between functional elements and / or network elements.

[0114] In the example, a network function can be a processing function within a network, which may have functional behaviors and / or interfaces. Network functions can be implemented as network elements on dedicated hardware and / or such as... Figure 3 and Figure 4 The network nodes depicted are either implemented as software instances running on dedicated hardware and / or shared hardware, or as virtual functions instantiated on a suitable platform.

[0115] In the example, the Access and Mobility Management (AMF) 155 may include the following functions (some of the AMF155 functions may be supported in a single instance of AMF 155): termination of the RAN 105CP interface (N2), termination of NAS (N1), NAS encryption and integrity protection, registration management, connection management, reachability management, mobility management, lawful interception (for AMF155 events and interfaces with the LI system), providing transport for session management, SM messages between UE 100 and SMF 160, transparent proxy for routing SM messages, access authentication, access authorization, providing transport for SMS messages between UE 100 and SMSF, security anchor function, SEA, interaction with AMFF 150 and UE 100, receiving intermediate keys established as a result of the UE 100 authentication process, receiving security context management (SCM) keys from the SEA for deriving access network-specific keys, etc.

[0116] In the example, AMF 155 can support non-3GPP access networks through the N2 interface with N3IWF 170, support NAS signaling with UE 100 through N3IWF 170, support authentication, mobility management, and separate security context states for UE 100 connected via non-3GPP access 165 or simultaneously via 3GPP access 105 and non-3GPP access 165, support effective coordination of RM contexts via 3GPP access 105 and non-3GPP access 165, support CM management context for UE 100 for connectivity via non-3GPP access, and so on.

[0117] In the example, an AMF 155 area may include one or more AMF 155 sets. An AMF 155 set may include some AMF 155s serving a given area and / or network slice. In the example, multiple AMF 155 sets may be each AMF 155 area and / or network slice. An application identifier may be an identifier that can be mapped to a specific application traffic detection rule. A configured NSSAI may be an NSSAI that can be provided in UE 100. For DNN, the DN 115 Access Identifier (DNAI) may be an identifier for user plane access to DN 115. Initial registration may be related to UE 100 registration in RM-DEREGISTERED (RM-Deregister) states 500 and 520. An N2AP UE 100 association may be a logical association between a 5G AN node and an AMF 155 based on UE 100. An N2AP UE-TNLA combination may be a combination between an N2AP UE 100 association and a TNL association for a specific transport network layer, for a given UE 100.

[0118] In the example, the session management function SMF 160 may include one or more of the following functions (one or more of the SMF 160 functions may be supported in a single instance of SMF 160): session management (e.g., session establishment, modification, and publication, including tunnel maintenance between UPF 110 and AN 105 nodes), UE 100 IP address allocation and management (including optional authorization), selection and control of UP functions, configuring traffic redirection at UPF 110 to route traffic to the appropriate destination, terminating the interface for policy control functions, controlling policy enforcement and a portion of QoS, lawful interception (for SM events and interfaces with LI systems), termination of the SM portion of NAS messages, downlink data notification, initiating AN-specific SM information, sending via N2 to (R)AN 105 via AMF155, determining the SSC mode of the session, roaming functions, handling local execution to apply QoS SLA (VPLMN), charge data collection and charge interface (VPLMN), lawful interception (in VPLMN, for SM events and interfaces with LI systems), and support for external DN. The interaction of DN 115 is used to transmit signaling for PDU session authorization / authentication by external DN 115, etc.

[0119] In the example, the User Plane Function UPF 110 may include one or more of the following functions (some of the UPF 110 functions may be supported in a single instance of UPF 110): anchor points for movement within / between RATs (if applicable), external PDU session points interconnected to DN115, data packet routing and forwarding, data packet inspection and user plane portion of policy rule enforcement, lawful interception (UP collection), traffic usage reporting, uplink classifier for routed traffic flows supporting data networks, branch points for multihomed PDU sessions, QoS processing in the user plane, uplink traffic authentication (SDF to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering, downlink data notification triggering, etc.

[0120] In the example, UE 100 IP address management may include the allocation and release of UE 100 IP addresses and / or the updating of allocated IP addresses. UE 100 may set the requested PDU type during the PDU session establishment procedure based on its IP stack capabilities and / or configuration. In the example, SMF 160 may select the PDU type for the PDU session. In the example, if SMF 160 receives a request to set the PDU type for IP, SMF 160 may select the PDU type IPv4 or IPv6 based on DNN configuration and / or operator policies. In the example, SMF 160 may provide a reason value to UE 100 to indicate whether other IP versions are supported on the DNN. In the example, if SMF 160 receives a request for the PDU type IPv4 or IPv6, and the requested IP version is supported by the DNN, SMF 160 may select the requested PDU type.

[0121] In the example embodiment, the 5GC element and UE 100 may support the following mechanism: During the PDU session establishment procedure, the SMF 160 may send an IP address to the UE 100 via SM NAS signaling. Once the PDU session can be established, IPv4 address allocation and / or IPv4 parameter configuration can be used via DHCPv4. If IPv6 is supported, IPv6 prefix allocation can be supported via stateless IPv6 autoconfiguration. In the example, the 5GC network element may support IPv6 parameter configuration via stateless DHCPv6.

[0122] 5GC can support the allocation of static IPv4 addresses and / or static IPv6 prefixes based on subscription information in UDM 140 and / or on configurations on a per subscriber, per DNN basis.

[0123] The User Plane Function (UPF 110) can handle the user plane path of PDU sessions. The UPF 110, which provides an interface to the data network, can support the function of PDU session anchoring.

[0124] In the example, the policy control function PCF 135 can support a unified policy framework to control network behavior, provide policy rules for control plane functions to enforce policy rules, implement a front-end for accessing subscription information related to policy decisions in the User Data Repository (UDR), and so on.

[0125] The Network Exposure Function (NEF 125) can provide a means to securely expose services and capabilities provided by 3GPP network functions, switch between information exchanged with AF 145 and information exchanged with internal network functions, receive information from other network functions, and so on.

[0126] In the example, the Network Repository (NRF) 130 can support service discovery functionality that can receive NF discovery requests from NF instances, provide NF instances with information about discovered NF instances (to be discovered), and maintain information about available NF instances and the services they support, etc.

[0127] In the example, NSSF 120 can select a set of network slice instances serving UE 100 and determine the allowed NSSAI. In the example, NSSF 120 can determine the set of AMF 155 to be used to serve UE 100, and / or determine the list of candidate AMF 155 based on configuration by querying NRF 130.

[0128] In the example, the data stored in the UDR may include at least user subscription data, including at least subscription identifiers, security credentials, access and mobility-related subscription data, session-related subscription data, policy data, and so on.

[0129] In the example, AUSF 150 supports authentication server functionality (AUSF 150).

[0130] In the example, application function AF 145 can interact with the 3GPP core network to provide services. In the example, based on operator deployment, the application function can be trusted by the operator to interact directly with the relevant network functions. Application functions that the operator does not allow to directly access network functions can interact with the relevant network functions using an external exposure framework (e.g., via NEF 125).

[0131] In the example, the control plane interface between (R)AN 105 and the 5G core can support connecting various types of ANs (e.g., 3GPP RAN 105, N3IWF 170 for untrusted access 165) to the 5GC via control plane protocols. In the example, the N2 AP protocol can be used for both 3GPP access 105 and non-3GPP access 165. In the example, the control plane interface between (R)AN 105 and the 5G core can support decoupling between AMF 155 and other functions (such as SMF 160) that may need to control services supported by the AN (e.g., control of UP resources in AN 105 for PDU sessions).

[0132] In the example, 5GC can provide policy information from PCF 135 to UE 100. In the example, policy information may include: access network discovery and selection policy, UE 100 routing selection policy (URSP), SSC mode selection policy (SSCMSP), network slice selection policy (NSSP), DNN selection policy, non-seamless offloading policy, etc.

[0133] In the example, such as Figure 5A and Figure 5B As described, the Registration Management (RM) can be used to register or deregister UE / User 100 in the network and establish user contexts in the network. Connection Management can be used to establish and release signaling connections between UE 100 and AMF 155.

[0134] In the example, UE 100 can register on the network to receive services that require registration. In the example, UE 100 can periodically update its registration on the network to maintain reachability (periodic registration update), or update it while on the move (e.g., mobile registration update), or update its capabilities or renegotiate protocol parameters.

[0135] In the example, as shown in the example Figure 8 and Figure 9 The initial registration procedure described may involve performing network access control functions (e.g., user authentication and access authorization based on subscription profiles in UDM 140). Example Figure 9 yes Figure 8 The initial registration procedure described herein continues. Due to the initial registration procedure, the identity of service AMF 155 can be registered in UDM 140.

[0136] In the example, the registration management and RM procedures can be applied to both 3GPP Access 105 and non-3GPP Access 165.

[0137] Example Figure 5A The RM state of UE 100 as observed by UE 100 and AMF 155 can be depicted. In an example embodiment, two RM states reflecting the registration status of UE 100 in the selected PLMN can be employed in UE 100 and AMF 155: RM-Deregistration 500 and RM-Registration 510. In the example, in RM-Deregistration state 500, UE 100 may not be registered in the network. The UE 100 context in AMF 155 may not maintain valid location or routing information for UE 100, therefore UE 100 may not be reachable via AMF 155. In the example, the UE 100 context may be stored in both UE 100 and AMF 155. In the example, in RM-Registration state 510, UE 100 can register on the network. In RM-Registration state 510, UE 100 can receive services that may require registration on the network.

[0138] In the example embodiment, two RM states that reflect the registration status of UE 100 in the selected PLMN can be adopted for UE 100: RM-unregister 520 and RM-register 530.

[0139] As shown in the example Figure 6A and Figure 6B As depicted, the connection management CM may include establishing and releasing a signaling connection between UE 100 and AMF 155 via the N1 interface. This signaling connection can be used to enable NAS signaling exchange between UE 100 and the core network. The signaling connection between UE 100 and AMF 155 may include both the AN signaling connection between UE 100 and (R)AN 105 (e.g., an RRC connection via 3GPP access) and the N2 connection between AN and AMF 155 for UE 100.

[0140] As shown in the example Figure 6A and Figure 6B As described, for NAS signaling connections between UE 100 and AMF 155, CM-IDLE 600, 620, and CM-CONNECTED 610, 630, two CM states can be used. UE 100 in CM-IDLE 600 state can be in RM-registered 510 state and may not have a NAS signaling connection established with AMF 155 via N1. UE 100 can perform cell selection, cell reselection, PLMN selection, etc. UE 100 in CM-CONNECTED 610 state can have a NAS signaling connection with AMF 155 via N1.

[0141] In the example embodiment, two CM states can be used for UE 100 at AMF 155, CM-IDLE 620 and CM-CONNECTED 630.

[0142] In the example, the RRC inactivity state can be applied to NG-RAN (e.g., it can be applied to NR and E-UTRA connected to a 5G CN). Based on network configuration, AMF 155 can provide auxiliary information to NG RAN 105 to assist NG RAN 105 in determining whether UE 100 can be sent to the RRC inactivity state. When UE 100 is in CM-CONNECTED 610 and RRC inactivity state, UE 100 can continue the RRC connection as a response to RAN 105 paging due to pending uplink data, mobile-initiated signaling procedures, etc., to notify the network that it has left the RAN 105 notification area, etc.

[0143] In the example, NAS signaling connection management may include establishing and releasing NAS signaling connections. The NAS signaling connection establishment function can be provided by UE 100 and AMF155 to establish a NAS signaling connection for UE 100 in CM-IDLE 600 state. The procedure for releasing the NAS signaling connection can be initiated by the 5G(R)AN 105 node or AMF 155.

[0144] In the example, UE 100's reachability management can detect whether UE 100 is reachable and can provide UE 100's location (e.g., access node) to the network to reach UE 100. Reachability management can be accomplished by paging UE 100 and UE 100 location tracking. UE 100 location tracking can include both UE 100 registration area tracking and UE 100 reachability tracking. During registration and registration update procedures, UE 100 and AMF 155 can negotiate UE 100 reachability characteristics in CM-IDLE 600, 620 states.

[0145] In this example, two UE100 reachability categories for CM-IDLE 600 and 620 states can be negotiated between UE 100 and AMF 155. 1) When UE 100 is in CM-IDLE 600 mode, UE 100 reachability allows the mobile device to terminate data. 2) Mobile-Initiated Only (MICO) connection mode. 5GC can support a PDU connection service that provides PDU exchange between UE 100 and the data network identified by the DNN. The PDU connection service can be supported via a PDU session established upon request from UE 100.

[0146] In the example, a PDU session can support one or more PDU session types. A PDU session can be established, modified (e.g., based on a request from UE 100), and / or published (e.g., based on a request from both UE 100 and 5GC) using NAS SM signaling exchanged via N1 between UE 100 and SMF160. Upon request from the application server, 5GC can trigger a specific application within UE 100. When a trigger is received, UE 100 can send it to the identified application within UE 100. The identified application within UE 100 can establish a PDU session for a specific DNN.

[0147] In the example, the 5G QoS model can support, as shown in the example. Figure 7 The framework described herein is based on QoS flows. The 5G QoS model can simultaneously support QoS flows that require guaranteed flow bit rates and QoS flows that do not require guaranteed flow bit rates. In the example, the 5G QoS model can support reflection QoS. The QoS model may include flow mapping or packet marking at UPF 110 (CN_UP) 110, AN 105, and / or UE 100. In the example, packets can arrive at and / or be assigned to the application / service layer 730 of UE 100, UPF 110 (CN_UP) 110, and / or AF 145.

[0148] In the example, a QoS flow can be a granularity of QoS differentiation within a PDU session. QoS flow IDs and QFIs can be used to identify QoS flows in a 5G system. In the example, user plane traffic with the same QFI within a PDU session can receive the same traffic forwarding processing. The QFI can be carried in the encapsulation header on N3 and / or N9 (e.g., without changing the end-to-end packet header). In the example, the QFI can be applied to PDUs with different types of payloads. The QFI can be unique within a PDU session.

[0149] In the example, the QoS parameters of the QoS flow can be provided as a QoS profile to (R)AN 105 via N2 during PDU session establishment, QoS flow establishment, or each time the user plane is activated using NG-RAN. In the example, each PDU session may require default QoS rules. SMF 160 can assign QFIs to the QoS flow and can derive QoS parameters from information provided by PCF 135. In the example, SMF 160 can provide the (R)AN 105 with the QFIs and a QoS profile containing the QoS parameters of the QoS flow.

[0150] In the example, a 5G QoS flow can be the granularity of QoS forwarding processing in a 5G system. Traffic mapped to the same 5G QoS flow can receive the same forwarding processing (e.g., scheduling policies, queue management policies, rate setting policies, RLC configuration, etc.). In the example, providing different QoS forwarding processing may require separate 5G QoS flows.

[0151] In the example, the 5G QoS indicator can be a scalar that can be used as a reference for specific QoS forwarding behaviors (e.g., packet loss rate, packet delay budget) to be provided to the 5G QoS flow. In the example, the 5G QoS indicator can be implemented in the access network by 5QI reference node-specific parameters (e.g., scheduling weights, admission thresholds, queue management thresholds, link layer protocol configurations, etc.) that control QoS forwarding processing.

[0152] In the example, 5GC supports edge computing and enables operators and third-party services to be hosted close to the UE's attached access point. The 5G core network can select a UPF 110 close to UE 100 and can perform traffic redirection from UPF 110 to the local data network via the N6 interface. In the example, selection and traffic redirection can be based on UE 100's subscription data, UE 100's location, information from application function AF 145, policies, other relevant traffic rules, etc. In the example, the 5G core network can expose network information and capabilities to edge computing application functions. Edge computing functionality support may include: local routing, where the 5G core network can select UPF 110 to route user traffic to the local data network; traffic redirection, where the 5G core network can select traffic to be routed to applications in the local data network; session and service continuity for UE 100 and application mobility; user plane selection and reselection, for example, based on input from application functions; network capability openness, where the 5G core network and application functions can provide information to each other via NEF 125; QoS and charging, where PCF 135 can provide QoS control and charging rules for traffic routed to the local data network; support for LAN data networks, where the 5G core network can provide support for connectivity to LADN in specific areas where applications are deployed; and so on.

[0153] An example 5G system could be a 3GPP system including a 5G access network 105, a 5G core network, and a UE 100. The permitted NSSAI could be an NSSAI provided by the serving PLMN during, for example, the registration process, indicating the network-permitted NSSAI for UE 100 within the serving PLMN of the currently registered area.

[0154] In the example, the PDU connectivity service can provide PDU exchange between UE 100 and the data network. A PDU session can be an association between UE 100 and data network DN 115 that provides the PDU connectivity service. The association type can be IP, Ethernet, and / or unstructured.

[0155] Establishing a user plane connection to a data network via a network slice instance may include: executing the RM procedure to select the AMF 155 that supports the desired network slice, and establishing one or more PDU sessions to the desired data network via the network slice instance.

[0156] In the example, the network slice set of UE 100 can be changed at any time when UE 100 can register on the network, and can be initiated by the network or UE 100.

[0157] In the example, periodic registration updates could mean that UE 100 re-registers when the periodic registration timer expires. The requested NSSAI could be an NSSAI that UE 100 can provide to the network.

[0158] In the example, a service-based interface can represent a set of services that can be provided / exposed by a given NF.

[0159] In the example, service continuity can refer to an uninterrupted user experience of the service, including situations where the IP address and / or anchor point can change. In the example, session continuity can refer to the continuity of a PDU session. For IP-type PDU sessions, session continuity can imply that the IP address is retained throughout the lifetime of the PDU session. The uplink classifier can be a UPF 110 function, designed to redirect uplink traffic to the data network DN 115 based on filter rules provided by SMF 160.

[0160] In the example, the 5G system architecture can support data connectivity and services, enabling deployments using technologies such as network function virtualization and / or software-defined networking. The 5G system architecture can leverage service-based interactions between identified control plane (CP) network functions. In the 5G system architecture, the separation of user plane (UP) functions from control plane functions can be considered. If needed, the 5G system can enable network functions to interact directly with other NFs.

[0161] In this example, a 5G system can reduce the dependency between the access network (AN) and the core network (CN). The architecture may include an aggregated access-agnostic core network with a common AN-CN interface, which can integrate different 3GPP and non-3GPP access types.

[0162] In the example, the 5G system can support a unified authentication framework, stateless network nodes (NFs) with separate compute and storage resources, open capabilities, and simultaneous access to local and centralized services. To support low-latency services and access to local data networks, the UP (Upload and Activation) function can be deployed close to the access network.

[0163] In the example, the 5G system can support roaming within the visited PLMN using home routing traffic and / or local breakout traffic. The example 5G architecture can be service-based, and the interaction between network functions can be represented in two ways: (1) as a service-based representation (in the example...) Figure 1(2) As a reference point representation, it shows the interaction between NF services in the network functions described by the point-to-point reference point (e.g., N11) between any two network functions.

[0164] In the example, network slices may include core network control plane and user plane network functions, 5G radio access networks, N3IWF functions for non-3GPP access networks, and so on. Network slices can vary depending on the supported features and network function implementations. Operators can deploy multiple network slice instances that deliver the same features but are used for different groups of UEs, for example, when they deliver different committed services and / or because they can be dedicated to a customer. The NSSF120 can store mapping information between slice instance IDs and NF IDs (or NF addresses).

[0165] In the example, UE 100 can be served simultaneously by one or more network slice instances via 5G-AN. In the example, UE 100 can be served by k network slices at a time (e.g., k=8, 16, etc.). Logically, the AMF155 instance serving UE 100 can belong to the network slice instance serving UE 100.

[0166] In the example, each PLMN can have a PDU session belonging to a specific network slice instance. Different network slice instances may not share PDU sessions. Different slices can have slice-specific PDU sessions using the same DNN.

[0167] S-NSSAI (Single Network Slice Selection Auxiliary Information) identifies network slices. S-NSSAI may include: Slice / Service Type (SST), which may refer to the expected network slice behavior in terms of characteristics and services; and / or Slice Differentiator (SD). The Slice Differentiator may be optional information that supplements the Slice / Service Type to allow further differentiation to select a network slice instance from multiple potential network slice instances conforming to the indicated Slice / Service Type. In the example, the same network slice instance employing different S-NSSAIs can be selected. The CN portion of the network slice instance serving UE 100 can be selected by the CN.

[0168] In the example, subscription data may include the S-NSSAI of the network slice subscribed by UE 100. One or more S-NSSAIs may be marked as the default S-NSSAI. In the example, k S-NSSAIs may be marked as the default S-NSSAI (e.g., k = 8, 16, etc.). In the example, UE 100 may subscribe to more than 8 S-NSSAIs.

[0169] In the example, UE 100 can be configured by an HPLMN, each PLMN being configured with an NSSAI. After successfully completing the UE's registration procedure, UE 100 can obtain the allowed NSSAI for this PLMN from AMF 155, which may include one or more S-NSSAIs.

[0170] In the example, the allowed NSSAI of the PLMN can take precedence over the configured NSSAI. UE 100 can use the S-NSSAI corresponding to the network slice used in the serving PLMN for subsequent network slice selection procedures within the allowed NSSAI.

[0171] In the example, establishing a user plane connection to the data network via a network slice instance may include: executing the RM procedure to select an AMF 155 that supports the desired network slice, establishing one or more PDU sessions to the desired data network via the network slice instance, and so on.

[0172] In the example, when UE 100 registers with the PLMN, if UE 100 has a configured NSSAI or an allowed NSSAI for the PLMN, UE 100 can provide the requested NSSAI (which includes the S-NSSAI corresponding to the slice UE 100 is attempting to register for), a temporary user ID (if a temporary user ID is assigned to the UE), etc., to the network and NAS layers in the RRC. The requested NSSAI can be a configured NSSAI, an allowed NSSAI, etc.

[0173] In the example, when UE 100 registers with the PLMN, if UE 100 does not have a configured NSSAI or an allowed NSSAI for the PLMN, then RAN 105 can route NAS signaling from UE 100 to the default AMF 155 / route NAS signaling from the default AMF to the UE.

[0174] In the example, based on local policies, subscription changes, and / or UE 100 mobility, the network can change the set of permitted network slices to which UE 100 is registered. In the example, the network can perform the change during the registration process or use an RM procedure (which can trigger the registration process) to notify UE 100 of the change in supported network slices. The network can provide UE 100 with the new list of allowed NSSAI and tracking areas.

[0175] In the example, during the registration process in the PLMN, if the network determines that UE 100 should be served by a different AMF 155 based on network slicing, the AMF 155 that first receives the registration request can redirect the registration request to another AMF 155 via RAN 105 or via direct signaling between the initial AMF 155 and the target AMF 155.

[0176] In the example, the network operator can provide a network slice selection policy (NSSP) to UE 100. The NSSP may include one or more NSSP rules.

[0177] In the example, if UE 100 has one or more PDU sessions established corresponding to a specific S-NSSAI, UE 100 can route application user data within a single PDU session unless other conditions in UE 100 prevent the use of the PDU session. If the application provides a DNN, UE 100 can consider the DNN to determine which PDU session to use. In the example, if UE 100 has not established a PDU session with a specific S-NSSAI, UE 100 can request a new PDU session corresponding to the S-NSSAI and with a DNN that can be provided by the application. In the example, in order for RAN 105 to select appropriate resources to support network slices in RAN 105, RAN 105 can know the network slice used by UE 100.

[0178] In the example, when UE 100 triggers the establishment of a PDU session, AMF 155 can select SMF 160 from the network slice instance based on S-NSSAI, DNN, and / or other information (e.g., UE 100 subscriptions and local operator policies). The selected SMF160 can then establish a PDU session based on S-NSSAI and DNN.

[0179] In the example, to support network control privacy of slice information of slices accessible to UE 100, UE 100 may exclude NSSAI in NAS signaling when UE 100 is aware of or configured to allow privacy considerations to apply to NSSAI, unless UE 100 has a NAS security context and UE 100 may exclude NSSAI in unprotected RRC signaling.

[0180] In the example, for roaming scenarios, network slice-specific network functions (NFs) can be selected in both the VPLMN and HPLMN based on the S-NSSAI provided by the UE 100 during PDU connection establishment. If a standardized S-NSSAI is used, each PLMN can select slice-specific NF instances based on the provided S-NSSAI. In the example, the VPLMN can map the HPLMN's S-NSSAI to the VPLMN's S-NSSAI based on the roaming protocol (e.g., including the default S-NSSAI mapped to the VPLMN). In the example, slice-specific NF instances can be selected in the VPLMN based on the VPLMN's S-NSSAI. In the example, the selection of any slice-specific NF instance in the HPLMN can be based on the HPLMN's S-NSSAI.

[0181] As shown in the example Figure 8 and Figure 9 As described, the UE 100 can perform a registration procedure to obtain authorization for receiving services, to enable mobile tracking, to achieve accessibility, and so on.

[0182] In the example, UE 100 can send AN message 805 to (R)AN 105 (including AN parameters, RM-NAS registration request (registration type, SUCI or SUPI or 5G-GUTI, last accessed TAI (if available), security parameters, requested NSSAI, mapping of the requested NSSAI, UE 100 5GC capability, PDU session status, PDU session to be reactivated, follow-up requests, MICO mode preference, etc.) etc.). In the example, in the case of NG-RAN, AN parameters may include, for example, SUCI or SUPI or 5G-GUTI, selected PLMN ID, and requested NSSAI, etc. In the example, AN parameters may include establishment reason. The establishment reason can provide the reason for requesting to establish an RRC connection. In the example, the registration type can indicate whether UE 100 is to perform initial registration (i.e., UE 100 is in an RM-deregistered state), mobile registration update (e.g., UE 100 is in an RM-registered state and initiates the registration process due to mobility), periodic registration update (e.g., UE 100 is in an RM-registered state and may initiate the registration process due to the expiration of the periodic registration update timer), or emergency registration (e.g., UE 100 is in a limited service state). In the example, if UE 100 performs initial registration to the PLMN (i.e., UE 100 is in an RM-deregistered state) and UE 100 does not yet have a 5G-GUTI, UE 100 can include its SUCI or SUPI in the registration request. SUCI can be included if the home network has provided a public key to protect the SUPI in the UE. If UE 100 receives a UE 100 configuration update command indicating that UE 100 needs to re-register and that the 5G-GUTI is invalid, UE 100 can perform initial registration and can include the SUPI in the registration request message. For emergency registration, if UE 100 does not have a valid 5G-GUTI available, a SUPI may be included; if UE 100 has neither a SUPI nor a valid 5G-GUTI, a PEI may be included. In other cases, a 5G-GUTI may be included, and it may indicate the last serving AMF 155. If UE 100 has already registered via non-3GPP access in a new PLMN different from the 3GPP access (e.g., not the registered PLMN or an equivalent PLMN of the registered PLMN), then during the registration procedure via non-3GPP access, UE 100 may not provide the 5G-GUTI assigned by AMF 155 via 3GPP access.If UE 100 has already registered in a PLMN (e.g., a registered PLMN) that is different from a non-3GPP access PLMN (e.g., not a registered PLMN or an equivalent PLMN of a registered PLMN), then during the registration procedure via 3GPP access, UE 100 may not provide the 5G-GUTI assigned by AMF 155 via non-3GPP access. UE 100 may provide UE usage settings based on its configuration. In the case of initial registration or mobile registration update, UE 100 may include a mapping of requested NSSAIs, which may be a mapping of each S-NSSAI in the requested NSSAIs of the HPLMN to the S-NSSAIs in the configured NSSAIs, to ensure that the network can verify whether the S-NSSAIs in the requested NSSAIs are allowed based on the subscribed S-NSSAIs. If available, the last accessed TAI may be included to help AMF 155 generate the UE's registration area. In the example, security parameters may be used for authentication and integrity protection. The requested NSSAIs may instruct network slice selection auxiliary information. The PDU session status can indicate previously established PDU sessions in the UE. When UE 100 is connected to two AMF 155s belonging to different PLMNs via 3GPP access and non-3GPP access, the PDU session status can indicate the PDU sessions already established in the UE for the current PLMN. It may include PDU sessions awaiting reactivation to indicate that UE 100 may intend to activate a PDU session for its UP connection. When UE 100 is outside the availability area of ​​the LADN, the PDU session corresponding to the LADN may not be included in the PDU sessions awaiting reactivation. When UE 100 may have pending uplink signaling, and UE 100 may not include PDU sessions awaiting reactivation, it may include subsequent requests, or the registration type may indicate that UE 100 may need to perform emergency registration.

[0183] In the example, if including SUPI or 5G-GUTI does not indicate a valid AMF 155, then (R)AN 105 may select 808 AMF 155 based on (R)AT and the requested NSSAI (if available). If UE 100 is in CM-CONNECTED state, then (R)AN 105 may forward the registration request message to AMF 155 based on the UE's N2 connection. If (R)AN 105 can choose not to select an appropriate AMF 155, then it may forward the registration request to an AMF 155 that has been configured in (R)AN 105 to perform AMF 155 selection 808.

[0184] In the example, (R)AN 105 can send N2 message 810 to the new AMF 155 (including: N2 parameters, RM-NAS registration request (registration type, SUPI or 5G-GUTI, last accessed TAI (if available), security parameters, requested NSSAI, mapping of the requested NSSAI, UE 100 5GC capability, PDU session status, PDU session to be reactivated, follow-up requests, and MICO mode preferences), etc.). In the example, when using NG-RAN, the N2 parameters may include the selected PLMN ID, location information, cell identification, and RAT type related to the cell where UE 100 is located. In the example, when using NG-RAN, the N2 parameters may include the establishment reason.

[0185] In this example, the new AMF 155 can send Namf_Communication_UEContextTransfer (Full Registration Request) 815 to the old AMF 155. In this example, if the UE's 5G-GUTI is included in the registration request and the serving AMF 155 has changed since the last registration procedure, the new AMF 155 can invoke the Namf_Communication_UEContextTransfer service operation 815 (including the integrity-protected full registration request IE) on the old AMF 155 to request the UE's SUPI and MM context. The old AMF 155 can use the integrity-protected full registration request IE to verify that the context transfer service operation call corresponds to the requesting UE 100. In this example, the old AMF 155 can transfer event subscription information for the UE for each NF consumer to the new AMF 155. In this example, if UE 100 identifies itself with a PEI, the SUPI request can be skipped.

[0186] In this example, the legacy AMF 155 can send a response 815 to the new AMF 155 to Namf_Communication_UEContextTransfer (SUPI, MM context, SMF160 information, PCF ID). In this example, the legacy AMF 155 can respond to the new AMF 155 with the UE's SUPI and MM context. In this example, if the legacy AMF 155 maintains information about established PDU sessions, it can include SMF160 information, including S-NSSAI, SMF 160 identification, and PDU session ID. In this example, if the legacy AMF 155 maintains information about active NGAP UE-TNLA to the N3IWF, it can include information about NGAP UE-TNLA bindings.

[0187] In the example, if the SUCI is not provided by UE 100 or retrieved from the legacy AMF 155, the identification request procedure 820 can be initiated by AMF 155 sending an identification request message to the UE 100 requesting the SUCI.

[0188] In the example, UE 100 can respond with an identification response message 820 that includes the SUCI. UE 100 can derive the SUCI using the public key of the provided HPLMN.

[0189] In the example, AMF 155 may decide to initiate UE 100 authentication 825 by calling AUSF 150. AMF 155 may select AUSF 150 based on SUPI or SUCI. In the example, if AMF 155 is configured to support emergency registration for unauthenticated SUPI and emergency registration of the registration type indicated by UE 100, AMF 155 may skip authentication and security settings, or AMF 155 may accept that authentication may fail and continue the registration procedure.

[0190] In the example, authentication 830 can be performed by the Nudm_UEAuthenticate_Get operation. AUSF 150 can discover UDM 140. If AMF 155 provides SUCI to AUSF 150, AUSF 150 can return SUPI to AMF 155 after successful authentication. In the example, if network slicing is used, AMF 155 can decide whether to reroute the registration request if the initial AMF 155 references AMF 155. In the example, AMF 155 can initiate NAS security functions. In the example, upon completing NAS security function settings, AMF 155 can initiate the NGAP procedure so that 5G-AN can use it to protect procedures with the UE. In the example, 5G-AN can store a security context and can acknowledge it to AMF 155. 5G-AN can use the security context to protect messages exchanged with the UE.

[0191] In the example, the new AMF 155 can send a Namf_Communication_RegistrationCompleteNotify 835 to the old AMF 155. If the AMF 155 has changed, the new AMF 155 can notify the old AMF 155 that UE100 can complete its registration in the new AMF 155 by calling the Namf_Communication_RegistrationCompleteNotify service operation. If the authentication / security procedure fails, registration can be refused, and the new AMF 155 can call the Namf_Communication_RegistrationCompleteNotify service operation, with the refusal indication reason code directed to the old AMF 155. The old AMF 155 can continue as if it never received the UE 100 context transport service operation. If one or more of the S-NSSAIs used in the old registration area cannot be served in the target registration area, the new AMF 155 can determine which PDU sessions may not be supported in the new registration area. The new AMF 155 can call the Namf_Communication_RegistrationCompleteNotify service operation to the old AMF 155, including the rejected PDU session ID and the reason for rejection (e.g., S-NSSAI becomes unavailable). The new AMF 155 can modify the PDU session state accordingly. The old AMF 155 can notify the corresponding SMF 160 to release the UE's SM context locally by calling the Nsmf_PDUSession_ReleaseSMContext service operation.

[0192] In the example, the new AMF 155 can send an identification request / response 840 (e.g., PEI) to UE 100. If the PEI is not provided by UE 100 or retrieved from the old AMF 155, the identification request procedure can be initiated by sending an identification request message to UE 100 via AMF 155 to retrieve the PEI. Unless UE 100 performs emergency registration, the PEI may be transmitted encrypted and may not be authenticated. For emergency registration, UE 100 may have already included the PEI in the registration request.

[0193] In the example, the new AMF 155 can initiate an ME identity check 845 by calling the N5g-eir_EquipmentIdentityCheck_Get service operation 845.

[0194] In the example, based on SUPI, the new AMF 155 can be selected as a 905UDM 140. UDM 140 can be selected as a UDR instance. In the example, AMF 155 can be selected as a UDM 140.

[0195] In the example, if AMF 155 has changed since the last registration procedure, or if UE 100 provides a SUPI that may not reference a valid context in AMF 155, or if UE 100 is registered to the same AMF 155 but has already registered to a non-3GPP access (e.g., UE 100 registered via a non-3GPP access and can initiate a registration procedure to add 3GPP access), the new AMF 155 can register with UDM 140 using Nudm_UECM_Registration 910 and can subscribe to be notified by UDM 140 when AMF 155 registration can be cancelled. UDM 140 can store the AMF 155 identifier associated with the access type and may not delete the AMF 155 identifier associated with another access type. UDM 140 can store information provided by Nudr_UDM_Update during registration in the UDR. In the example, AMF 155 can retrieve access and mobile subscription data and SMF 160 select subscription data using Nudm_SDM_Get 915. UDM 140 can retrieve this information (access and mobile subscription data) from the UDR via Nudr_UDM_Query. After receiving a successful response, AMF 155 can subscribe to be notified when the requested data can be modified using Nudm_SDM_Subscribe 920. UDM 140 can subscribe to the UDR via Nudr_UDM_Subscribe. If the GPSI is available in the UE 100 subscription data, it can be provided from UDM 140 to AMF 155 in the subscription data. In the example, the new AMF 155 can provide the access type it serves for UE 100 to UDM 140, and this access type can be set to 3GPP access. UDM 140 can store the associated access type in the UDR along with the serving AMF 155 via Nudr_UDM_Update. The new AMF 155 can create an MM context for UE100 after obtaining mobile subscription data from UDM 140. In the example, when UDM 140 stores the associated access type along with the serving AMF 155, UDM 140 can initiate Nudm_UECM_DeregistrationNotification921 to the old AMF 155 corresponding to the 3GPP access. The old AMF 155 can then remove the UE's MM context. If the reason for service NF deletion indicated by UDM 140 is initial registration, the old AMF 155 can call the Namf_EventExposure_Notify service operation to all associated SMFs 160 of UE100 to notify UE100 to deregister from the old AMF 155. SMF 160 can release the PDU session upon receiving this notification.In the example, the old AMF 155 can use Nudm_SDM_unsubscribe 922 to unsubscribe from UDM 140 for subscription data.

[0196] In the example, if AMF 155 decides to initiate PCF 135 communication, for example, if AMF 155 has not yet obtained the access and mobility policy of UE 100, or if the access and mobility policy in AMF 155 is no longer valid, AMF 155 can choose 925PCF 135. If the new AMF 155 receives a PCF ID from the old AMF 155 and successfully contacts the PCF 135 identified by the PCF ID, AMF 155 can choose the (V-)PCF identified by the PCF ID. If the PCF 135 identified by the PCF ID (e.g., no response from PCF 135) may not be used, or if no PCF ID is received from the old AMF 155, AMF 155 can choose 925PCF 135.

[0197] In the example, the new AMF 155 can perform policy association establishment 930 during the registration process. If the new AMF 155 contacts the PCF 135 identified by the (V-)PCF ID received during movement between AMFs 155, the new AMF 155 can include the PCF-ID in the Npcf_AMPolicyControl Get operation. If the AMF 155 notifies the PCF 135 of movement restrictions (e.g., UE 100 location) for adjustment, or if the PCF 135 updates its own movement restrictions due to certain conditions (e.g., application in use, time and date), the PCF 135 can provide the updated movement restrictions to the AMF 155.

[0198] In the example, PCF 135 can invoke Namf_EventExposure_Subscribe service operation 935 for UE 100 event subscription.

[0199] In the example, AMF 155 can send Nsmf_PDUSession_UpdateSMContext 936 to SMF 160. In the example, if the PDU session to be reactivated is included in the registration request, AMF 155 can invoke Nsmf_PDUSession_UpdateSMContext. AMF 155 can send the Nsmf_PDUSession_UpdateSMContext request to the SMF 160 associated with the PDU session to activate the user plane connection of the PDU session. SMF 160 can decide to trigger, for example, intermediate UPF 110 insertion, removal, or PSA modification. In the case of performing intermediate UPF 110 insertion, removal, or relocation for a PDU session not included in the PDU session to be reactivated, the procedure can be executed without N11 and N2 interaction to update the N3 user plane between (R)AN 105 and 5GC. The AMF 155 can invoke the Nsmf_PDUSession_ReleaseSMContext service operation to the SMF 160 when any PDU session state indicates that it has been released at UE 100. The AMF 155 can invoke the Nsmf_PDUSession_ReleaseSMContext service operation to the SMF 160 to release any network resources associated with the PDU session.

[0200] In the example, the new AMF 155 can send an N2 AMF 155 Mobility Request 940 to the N3IWF. If the AMF 155 has changed, the new AMF 155 can create an NGAP UE 100 association for the N3IWF connected to UE 100. In the example, the N3IWF can respond to the new AMF 155 with an N2 AMF 155 Mobility Response 940.

[0201] In the example, the new AMF 155 can send a Registration Acceptance 955 to UE 100 (including: 5G-GUTI, registration area, mobility restrictions, PDU session state, allowed NSSAI, [mapping of allowed NSSAI], periodic registration update timer, LADN information and accepted MICO mode, indication of IMS voice support via PS session, emergency service support indicator, etc.). In the example, AMF 155 can send a Registration Acceptance message to UE 100 indicating that the registration request has been accepted. If AMF 155 has assigned a new 5G-GUTI, it can include the 5G-GUTI. If AMF 155 has assigned a new registration area, it can send the registration area to UE 100 via the Registration Acceptance message 955. If the registration acceptance message does not include the registration area, UE 100 may consider the old registration area valid. In the example, mobility restrictions can be included if they apply to UE 100 and the registration type may not be emergency registration. AMF 155 can indicate the established PDU session to UE 100 in the PDU session state. UE 100 can locally remove any internal resources associated with a PDU session not marked as established in the received PDU session state. In the example, when UE 100 is connected to two AMF 155s belonging to different PLMNs via 3GPP access and non-3GPP access, UE 100 can locally remove any internal resources associated with the current PLMN's PDU session that are not marked as established in the received PDU session state. If PDU session state information is in the registration request, AMF 155 can indicate the PDU session state to the UE. The mapping of allowed NSSAIs can be a mapping of each S-NSSAI in the allowed NSSAIs of the HPLMN to an S-NSSAI in the configured NSSAIs. AMF 155 can include LADN information of the LADN in the registration acceptance message 955, the LADN being available in the registration area determined by AMF 155 for the UE. If UE100 includes MICO mode in its request, AMF 155 can respond to whether MICO mode can be used. AMF 155 can set an indication to support IMS voice via PS session. In the example, to set the indication to support IMS voice via PS session, AMF 155 can execute a UE / RAN radio information and compatibility request procedure to check the compatibility of UE 100 and RAN radio capabilities related to IMS voice via PS. In the example, an emergency service support indicator can notify UE 100 to support emergency services; for example, UE 100 can request emergency services via a PDU session. In the example, the handover restriction list and UE-AMBR can be provided to the NG-RAN by AMF 155.

[0202] In the example, UE 100 can send a registration complete 960 message to the new AMF 155. In the example, UE 100 can send the registration complete message 960 to AMF 155 to confirm that a new 5G-GUTI can be allocated. In the example, when information about the PDU session to be reactivated is not included in the registration request, AMF 155 can release the signaling connection with UE 100. In the example, when a subsequent request is included in the registration request, AMF 155 may not release the signaling connection after the registration procedure is completed. In the example, if AMF 155 realizes that some signaling is pending in AMF 155 or between UE 100 and 5GC, AMF 155 may not release the signaling connection after the registration procedure is completed.

[0203] In the example, Figure 10 This is a diagram of the 5G policy and charging control system architecture. A reference architecture for the policy and charging control framework for 5G systems may include one or more of the following network functions: Policy Control Function (PCF), Session Management Function (SMF), User Plane Function (UPF), Access and Mobility Management Function (AMF), Network Exposure Function (NEF), Network Data Analysis Function (NWDAF), Charging Function (CHF), Application Function (AF), and Unified Data Repository (UDR).

[0204] In the example, CHF can support at least one charging method: offline charging, online charging, or combined charging.

[0205] In the example, offline billing can be a process that collects billing information for network resource usage simultaneously with the use of that resource. At the end of this process, a CDR file can be generated by the network and transmitted to the network operator's billing domain (BD) for subscriber billing and / or inter-operator accounting purposes (or additional functions determined by the operator, such as statistical data). The BD typically includes post-processing systems, such as the operator's billing system or billing mediation apparatus. In the example's conclusion, offline billing can be a mechanism where billing information does not affect the services provided in real time.

[0206] In the example, online billing can be a process that collects billing information for network resource usage simultaneously with offline billing, in the same manner. The network can obtain authorization for network resource usage before actual usage occurs. In the example, the billing information used in online billing may not necessarily be the same as that used in offline billing. In the example's conclusion, online billing can be a mechanism where billing information can affect the services provided in real time and therefore may require direct interaction between the billing authority and network resource usage control.

[0207] In the example, bundled charging can be a process that combines online charging and offline charging.

[0208] Figure 11 Example call stream for establishing a charged PDU session according to an embodiment of this disclosure.

[0209] In the example, the UE can initiate the PDU session establishment procedure by sending a PDU session establishment request message to the AMF. The PDU session establishment request message may include one or more of the following: PDU session ID, PDU type, SSC mode, user location information, and access technology type information.

[0210] In response to a message received from the UE, the AMF can select an SMF and send a message to the selected SMF (e.g., a Namf_PDUSession_CreateSMContext request). The message sent to the SMF can be used by the AMF to request the establishment of a PDU session. In response to receiving a message from the AMF, the SMF can send a response message to the AMF (e.g., a Namf_PDUSession_CreateSMContext response) to indicate whether it accepts the request from the AMF.

[0211] In the example, the SMF can select the PCF and send a message (e.g., an SM policy association establishment request) to the PCF to request PCC rules. The PCF can then provide the PCC rules to the SMF in a response message (e.g., an SM policy association establishment response).

[0212] In the example, the SMF can create a charge ID for the PDU session and can send a charge data request [initial] message to the CHF to verify the UE's subscriber's authorization to start the PDU session, which is triggered by the start of the PDU session charge event.

[0213] In the example, CHF can open a charge data record (CDR) for a PDU session and can acknowledge the charge data request message by sending a charge data response to SMF.

[0214] In the example, the SMF selects the UPF and can initiate an N4 session creation / modification procedure with the selected UPF.

[0215] SMF can interact with AMF. For example, SMF can send a Namf_Communication_N1N2MessageTransfer message to AMF, which includes one or more of the following: PDU session ID, QoS profile, CN tunnel information, and S-NSSAI from an allowed NSSAI. This SMF / AMF interaction occurs in... Figure 11 The text is marked as SMF AMF interaction.

[0216] In the example, AMF can interact with (R)AN and UE. This interaction is... Figure 11 This is marked as AMF-RAN-UE interaction. As part of the AMF-RAN-UE interaction, the AMF can interact with the (R)AN and the UE by sending an N2 PDU session request message to the (R)AN (including information received from the SMF indicating acceptance of PDU session establishment).

[0217] In the example, and as another part of the AMF-RAN-UE interaction, the (R)AN can send an N2 PDU session response message to the AMF, which includes one or more of the following: PDU session ID, N2 SM information (PDU session ID, AN tunnel information, and a list of accepted / rejected QFIs), wherein the AN tunnel information may correspond to the access network address of the N3 tunnel corresponding to the PDU session.

[0218] In the example, the AMF can send a PDU session update request message (e.g., an Nsmf_PDUSession_UpdateSMContext request message) to the SMF, which includes N2 SM information received from the (R)AN from the SMF.

[0219] In the example, the SMF can initiate an N4 session modification procedure with the UPF. As part of the N4 session modification procedure, the SMF can provide the UPF with AN tunnel information and the corresponding forwarding rules, and the UPF can send a response message to the SMF.

[0220] In the example, the SMF can request quotas from the CHF, for instance, a "Start Service Data Stream" event might require quotas from the CHF. The SMF can send messages to the CHF (e.g., a charge data request [update]). In the example, for online charging or converged charging, the SMF can request quotas from the CHF when allocated quotas are consumed or when a requested quota is triggered.

[0221] In the example, the UPF can report the resource usage of the PDU session to the SMF. In the example, the UPF can report the resource usage of the wireless device to the SMF by enforcing charging control rules, and the SMF can send a message to the CHF including the resource usage information received from the UPF (e.g., a charging data request [update]).

[0222] In the example, the CHF can update the CDR for this PDU session. The CHF can acknowledge the SMF by sending a charge data response message.

[0223] In the example, the SMF can send an Nsmf_PDUSession_UpdateSMContext response message to the AMF.

[0224] In the example, for the PDU session establishment procedure, other interactions can be performed between the SMF, AMF, (R)AN, and UE. Figure 11 The middle part is marked as other interactions.

[0225] In the example, the 5GC may be able to provide policy information to the UE from the PCF, such policy information may include the Access Network Discovery and Selection Policy (ANDSP) and / or the UE Route Selection Policy (URSP).

[0226] In the example, the UE uses ANDSP to select non-3GPP access and selects N3IWF in the PLMN. In the example, the UE uses URSP to determine whether a detected application can be associated with an established PDU session, whether it can be offloaded to non-3GPP access outside the PDU session, or whether it can trigger the establishment of a new PDU session. In the example, URSP rules may include a traffic descriptor specifying matching criteria and one or more of the following components: SSC Mode Selection Policy (SSCMSP), Network Slice Selection Policy (NSSP), DNN Selection Policy, PDU Session Type Policy, Non-Seamless Offload Policy, and / or Access Type Preferences. In the example, the UE uses SSCMSP to associate a matching application with an SSC mode. In the example, the UE uses NSSP to associate a matching application with S-NSSAI. In the example, the UE uses a DNN selection policy to associate a matching application with a DNN. In the example, the UE uses a PDU session type policy to associate a matching application with a PDU session type. In the example, the UE uses a non-seamless offload policy to determine that the matching application should be non-seamlessly offloaded to non-3GPP access (i.e., outside the PDU session). In the example, the access type preference can indicate the preferred access type (3GPP or non-3GPP). This is if the UE needs to establish a PDU session for a matching application. In the example, ANDSP and URSP can be pre-configured in the UE or provided to the UE from the PCF. Pre-configured policies can be applied when the UE has not yet received the same type of policy from the PCF. In the example, the PCF can select the appropriate ANDSP and URSP for the UE based on local configuration, subscribed S-NSSAI, and operator policies, while taking into account factors such as cumulative usage, load level information per network slice instance, and UE location. In the example, in the case of a roaming UE, the V-PCF can retrieve the ANDSP and URSP from the H-PCF via N24 / Npcf. When the UE is roaming and has valid rules from both the HPLMN and VPLMN, the UE may prioritize the valid ANDSP rule from the VPLMN.

[0227] In the example, ANDSP and URSP can be provided from PCF to AMF via N15 / Namf interface, and then from AMF to UE via N1 interface. AMF cannot modify the ANDSP and URSP provided by PCF.

[0228] In the example, the PCF can be responsible for delivering the UE policy. If the PCF is notified that the UE policy delivery failed (e.g., due to the UE being unreachable), the PCF can subscribe to the "Connectivity State Change (Idle or Connected)" event. After receiving a notification message indicating that the UE has entered the CM connected state, the PCF can retry delivering the UE policy.

[0229] In the example, the 5G core network can support the collection of charging information for 5G LAN-type services based on resource usage (e.g., licensed or unlicensed spectrum, QoS, applications).

[0230] In the example, when a UE joins or leaves a specific private communication, the 5G core network can support the collection of billing information for 5G LAN-type services.

[0231] In the example, the 5G core network can support the collection of billing information for 5G LAN-type services for home and roaming UEs based on the UE's HPLMN.

[0232] In the example, a non-public network can be uniquely identified by a combination of a PLMN ID and a non-public network ID. In the example, a non-public network can be isolated from the PLMN (e.g., a standalone non-public network), in which case a reserved private PLMN ID can be used, allocated globally (e.g., MCC=999 and MNC=3GPP specified values) or domestically (e.g., specific MCC and MNC values ​​specified by local regulators). In the example, a non-public network can be deployed as part of a PLMN, using the PLMN operator's PLMN ID. Figure 12A This is an example diagram depicting a non-public network that can be deployed as part of a PLMN. Figure 12B This is an example diagram depicting how non-public networks can be isolated from PLMNs.

[0233] In the example, a non-public network may include only one CAG (e.g., an NPN ID mapped to a CAG ID). In the example, a non-public network may include more than one CAG (e.g., an NPN ID mapped to more than one CAG ID). Figure 13A To illustrate an example diagram of a non-public network that may consist of only one CAG, Figure 13B An example diagram depicting a non-public network may include more than one CAG.

[0234] In the example, the Non-Public Network ID (NPN-ID) identifies a non-public network. NPN-IDs can support two allocation models. A human-readable network name can identify a non-public network. A human-readable name can be unique. In the example, a PLMN ID composed of MCC999 (assigned by the ITU for private networks) and an MNC defined by 3GPP can identify a cell as part of a non-public network.

[0235] In the example, the Closed Access Group (CAG) ID uniquely identifies the Closed Access Group (CAG) within the PLMN. In the example, the human-readable network name identifies the CAG. The human-readable name can be unique. In the example, the following information can be broadcast in the SIB for PLMNs that support CAGs: a CAG indication identifying the cell as a Closed Access Group cell; a cellReservedForOtherUse indication (to prevent unsupported UEs from accessing the cell), which UEs supporting non-public networks consider cells broadcasting cellReservedForOtherUse and CAG indications to be not prohibited; the CAG ID; and optionally, the human-readable network name.

[0236] In the example, the UE can maintain a whitelist of CAG IDs. In the example, a UE configured to only access CAG cells may not be allowed to register via any non-CAG cells of any PLMN. In the example, the UE can automatically select and attempt to register only via CAG cells whose identities are included in the whitelist. In the example, for manual CAG selection, the UE can present a list of available CAG IDs and their associated human-readable names (if available). If the UE successfully registers to a CAG not yet listed in the whitelist, the CAG ID can be added to the CAG whitelist.

[0237] In the example, the subscription may contain a list of CAGs that the UE is authorized to access. In the example, the subscription may also contain an indication of whether only CAG cells are allowed for UE access (and the UE is configured accordingly), to address factory-installed devices that should be retained on CAG cells.

[0238] Figure 14 This illustration depicts an example of a UE accessing a different Service Provider PLMN via a non-public network, according to aspects of embodiments of this disclosure. In the example, the network can be identified using a Non-Public Network Identifier (NPN ID) advertised in the broadcast channel of the non-public network cell. The non-public network may support services provided by one or more Service Providers (SPs), which may include an MNO or a third-party service provider. Figure 14As shown, UE#A and UE#B can register to a non-public network (NPN) identified by a non-public network ID (NPN-ID). Service provider 1, represented by SP#1 (which may be a PLMN), provides authorized services to UE#A. Service provider 2, represented by SP#N (which may be a third-party service provider), provides authorized services to UE#B. In this example, a UE may have subscriptions to one or more service providers, each of which can be identified by an SP ID. For a UE with a subscription to a service provider that is a PLMN, the UE's subscription data and authentication credentials may be stored at the service provider's UDM / AUSF. The network identification of the non-public network may be given by the NPN ID.

[0239] In the example, the SP-ID, which is the identifier of the service provider, can be advertised by a non-public network cell in the system information. A given non-public network identified by the NPN ID can support multiple SP-IDs. For a service provider that is a PLMN, the SP-ID can be the PLMN-ID. For a service provider that is not a PLMN, the SP-ID can be a domain name, and the selection procedure can be based on the domain name. In the example, the UE can have subscriptions with one or more service providers. In the example, the RAN node in the non-public network can broadcast a non-public network indicator, which can be, for example: a new non-public network indicator; or PLMN-MCC=999 to suppress "public UE" access to the non-public network; or a cellReservedForOtherUse indicator: an existing bit in the SIB. In the example, the RAN node in the non-public network can broadcast the NPN-ID. In the example, the RAN node in the non-public network can broadcast a list of supported SP-IDs. In the example, the UE can be configured with at least one SP-ID for the service provider that has the UE subscription. In the example, the UE can be configured with an NPN ID or a list of NPN-IDs, whereby the NPN can provide the UE with access to an SP that has a subscription to the UE. In the example, the UE can be configured with authentication parameters including credentials and / or a configured SP-ID authentication method.

[0240] Operators may require different charging standards for public networks than for non-public networks (e.g., dedicated networks for vertical industries and / or enterprises). If the same charging control rules are applied to different types of UEs, such as a first type of UE using CAG and a second type of UE using a different type of CAG or not using CAG, the operator may be unable to charge UE-specific rates. Existing technologies may present challenges in supporting charging control for NPNs and / or CAGs and / or implementing quota control for NPNs and / or CAGs. For example, a PCF using existing technologies may find it difficult to determine the charging control rules for NPNs and / or CAGs. Similarly, an SMF using existing technologies may find it difficult to determine the charging control rules for NPNs and / or CAGs. An SMF using existing technologies may also find it difficult to map charging control rules to user plane rules for NPNs and / or CAGs.

[0241] Embodiments of this disclosure provide enhanced mechanisms for implementing charge control over NPN and / or CAG. Embodiments of this disclosure provide enhanced mechanisms enabling the PCF to determine charge control rules based on the NPN and / or CAG of a specific UE. Embodiments of this disclosure provide enhanced mechanisms enabling the SMF to determine charge control rules based on the NPN and / or CAG of a specific UE. Embodiments of this disclosure provide enhanced mechanisms enabling the SMF to map charge control rules to user plane rules of the NPN and / or CAG of a specific UE. Embodiments of this disclosure provide enhanced mechanisms enabling the CHF to determine quota information for NPN and / or CAG and send that quota information to the SMF for execution. These enhanced mechanisms can provide efficient solutions supporting charge control over NPN and / or CAG, and can meet the operator's requirements for different charges (e.g., different charge rates) for public and non-public networks.

[0242] Figure 15An example call flow that may include one or more actions is shown. The UE may determine to initiate a PDU session and send a NAS message to the AMF that includes at least one of the following: S-NSSAI and / or the NSI ID of S-NSSAI, DNN, PDU session ID, request type, or N1 SM container (PDU session establishment request). The UE may initiate a UE-requested PDU session establishment procedure by transmitting a PDU session establishment request message within the N1 SM container of the NAS message. The PDU session establishment request message may include at least one of the following: PDU session ID, requested PDU session type, or requested SSC mode, etc. In the example, the NAS message may include an NPN ID and / or a CAG ID. In the example, the PDU session establishment request message may include an NPN ID and / or a CAG ID. The NPN ID and / or CAG ID may be applied to the PDU session and / or the UE and / or the network slice (e.g., S-NSSAI and / or the NSI ID of S-NSSAI) and / or the DNN. In the example, the UE may transmit the NAS message via a RAN node (e.g., gNB, base station). The UE can transmit Radio Resource Control (RRC) messages, including NAS messages, to the RAN node (e.g., Uplink (UL) Information Transmission Message, RRC Setup Complete Message, RRC Recovery Complete Message, RRC Reconfiguration Complete Message, etc.). The RAN node can transmit N2 messages, including NAS messages, to the AMF (e.g., NG Message, Initial UE Message, Uplink NAS Transmission Message, Rerouting NAS Request Message, Handover Request Message, Initial Context Setup Request Message, PDU Session Resource Setup / Modification Response Message, PDU Session Resource Modification Required Message, etc.).

[0243] In response to a NAS message received from the UE, the AMF may select an SMF and send a message to the selected SMF including at least one of the following (e.g., a PDU session ID request): SUPI, DNN, S-NSSAI and / or the NSI ID of S-NSSAI, PDU session ID, AMF ID, request type, preferred access, N1 SM container (PDU session establishment request), user location information, access type, PEI. The message sent to the SMF can be used by the AMF to request the establishment of a PDU session. In response to a PDU session ID request message received from the AMF, the SMF may send a response message to the AMF including at least one of the following (e.g., a PDU session rejection (reason)): reason, SM context ID, or N1 SM container (PDU session rejection (reason)).

[0244] The SMF can take one or more actions. In an example action, if a PCC is deployed, the SMF can send a message to the PCF including at least one of the following (e.g., a policy establishment request): NPN ID and / or CAG ID, at least one UE identity (e.g., SUPI, PEI, and / or GPSI), at least one UE IP address (e.g., UE IPv4 address and / or UE IPv6 network prefix), default 5QI and default ARP, PDU session type (e.g., IPv4, IPv6, IPv4v6, Ethernet, unstructured); access type (e.g., 3GPP access); RAT type (e.g., 3GPP-NR-FDD); PLMN identifier; application identifier; assigned application instance identifier; DNN, S-NSSAI and / or S-NSSAI NSI ID, PDU session ID, user location information, or SMF information for the PDU session (e.g., SMF identifier, IP address, or SMF FQDN).

[0245] In response to a policy establishment request message received from the SMF, the PCF may send a message to the UDR requesting user subscription information (e.g., a subscription retrieval request). The subscription retrieval request message sent to the UDR may include at least one of the following: NPN ID and / or CAG ID, at least one UE identity (e.g., SUPI, PEI, and / or GPSI), at least one UE IP address (e.g., UE IPv4 address and / or UE IPv6 network prefix), default 5QI and default ARP, PDU session type (e.g., IPv4, IPv6, IPv4v6, Ethernet, unstructured); access type (e.g., 3GPP access); RAT type (e.g., 3GPP-NR-FDD); PLMN identifier; application identifier; assigned application instance identifier; DNN, S-NSSAI and / or S-NSSAI NSI ID, PDU session ID, user location information, or SMF information for the PDU session (e.g., SMF identifier, IP address, or SMF FQDN).

[0246] In response to a subscription retrieval request message received from the PCF, the UDR may take one or more actions. In an example action, the UDR may determine that charge control information for the NPN and / or CAG applies to the radio device and / or network slice and / or PDU session, wherein the radio device may be identified by at least one UE identity, the NPN may be identified by an NPN ID, the CAG may be identified by a CAG ID, the network slice may be identified by an S-NSSAI and / or an NSI ID of the S-NSSAI, and the PDU session may be identified by a PDU session ID. In the example, the UDR may determine the charge control information for the NPN and / or CAG based on operator policies, local policies, and / or configuration. In the example, user subscription information may include an indication that charge control applies to the NPN and / or CAG of the radio device. In the example, user subscription information may include at least one of the following: the charge rate of the NPN and / or CAG, the charge method of the NPN and / or CAG (e.g., offline charge, online charge, or converged charge), or the address of the charge function of the NPN and / or CAG. In the example, the UDR may determine the charge control information based on the user subscription information. In the example, charge control information may include at least one of the following: charge rate, charge method, or address of charge function. The charge method may include at least one of the following: offline charge, online charge, or combined charge. In the example action, the UDR may send response information (e.g., a subscription retrieval response) to the PCF, the response information including at least one of the following: charge control information for NPN and / or CAG; NPN ID and / or CAG ID.

[0247] In response to a subscription retrieval response message received from the UDR, the PCF may take one or more actions. In example actions, the PCF may determine the charging control policy for the NPN and / or CAG. The PCF may determine the charging control rules for the NPN ID and / or CAG ID based on information received from the UDR (e.g., charging control information) and / or information received from the SMF (e.g., NPN ID and / or CAG ID) and / or operator-local policies. The charging control rules may include at least one of the following: charging rate, charging method, or address of the charging function. The charging method may include at least one of the following: offline charging, online charging, or bundled charging. In the example, the PCF may determine the charging rate (e.g., fixed rate) for the NPN and / or CAG based on the charging control information received from the UDR and / or operator-local policies. In the example, the PCF may determine the charging method (e.g., offline charging) for the NPN and / or CAG based on the charging control information received from the UDR and / or local operator policies. In the example, the PCF can select the CHF (e.g., a specific CHF for the NPN and / or CAG) based on charge control information received from the UDR and / or local operator policies. In the example, the charge control rules determined by the PCF can be applied to PDU sessions, network slices (e.g., S-NSSAI and / or the NSI ID of S-NSSAI), QoS flows, and / or service data flows of the NPN and / or CAG.

[0248] In the example action, the PCF may send a message to the SMF that includes at least one of the following (e.g., a policy establishment response): the toll control rules of the NPN and / or CAG; the NPN ID and / or CAG ID; the PDU session ID; and the NSI ID of the S-NSSAI and / or S-NSSAI.

[0249] In response to a policy establishment response message received from the PCF, the SMF may take one or more actions. In an example action, the SMF may send a message to the CHF that includes at least one of the following (e.g., a charge data request): the PDU session and / or the UE's NPN ID and / or CAG ID; the PDU session ID; at least one UE identity; or the S-NSSAI and / or the S-NSSAI's NSI ID.

[0250] In response to a charge data request message, the CHF can determine the quotas for the NPN and / or CAG based on information received from the SMF (e.g., NPN ID and / or CAG ID). In the example, the quota may include at least one of the following: authorization unit; time quota threshold; or quantity quota threshold. In the example, the CHF can determine the higher authorization unit for the NPN and / or CAG. The CHF can send response information (e.g., a charge data response) to the SMF including the quota and / or NPN ID and / or CAG ID.

[0251] In response to a charge data response, the SMF can take one or more actions. In the example actions, the SMF can enforce quotas. In the example actions, the SMF can enforce charge control rules. In the example actions, the SMF can select the UPF for the NPN and / or CAG based on the NPN ID and / or CAG ID. In the example actions, the SMF can select the UPF for the NPN and / or CAG based on quota and / or charge control rules. In the example actions, the SMF can determine at least one of the following user plane rules for the PDU session and / or NPN and / or CAG based on quota and / or charge control rules: at least one packet detection rule; at least one forwarding action rule; at least one QoS enforcement rule; or at least one usage reporting rule. In the example, the SMF can map charge control rules to user plane rules for the NPN and / or CAG. In the example actions, the SMF can send a message to the UPF including at least one user plane rule and / or the NPN ID and / or CAG ID.

[0252] In response to messages received from the SMF, the UPF can install user plane rules, send response messages to the SMF (e.g., N4 session establishment / modification response), and execute user plane rules received from the SMF.

[0253] In the example, UPF can execute at least one packet detection rule by matching user data / traffic packets with service flow templates (e.g., service flow filters and / or application identifiers), and can apply other user plane rules (e.g., forwarding action rules, QoS enforcement rules, and usage reporting rules) to data / traffic packets that match the packet detection rule.

[0254] In the example, the UPF can execute at least one forwarding action rule by forwarding, copying, dropping, or buffering data / traffic packets, respectively. In the example, the UPF can redirect traffic to the operator's network portal.

[0255] In the example, the UPF can execute at least one QoS enforcement rule by applying at least one of the QoS parameters (5QI, ARP, MBR, GBR) to the service data stream. In the example, the UPF can execute at least one QoS enforcement rule by applying at least one of the QoS parameters (session AMBR and default 5QI / ARP combination) to the PDU session.

[0256] In the example, the UPF can execute at least one usage reporting rule by measuring the use of network resources in terms of traffic data volume, duration (i.e., time) and / or events according to the measurement method in the usage reporting rule; the UPF can report network resource usage to the SMF when quotas / thresholds are reached and / or when events and / or another trigger are met.

[0257] In the example, the network resource usage reported by the UPF to the SMF may include the amount of traffic data, the duration (i.e., time) applied to at least one of the following: NPN ID and / or CAG ID, UE, PDU session, QoS flow, service data flow, application, network slice, or data network.

[0258] The SMF can map received network resource usage to NPN ID and / or CAG ID and / or PDU session and / or network slice and / or UE. The SMF can send a message to the CHF including network resource usage and / or NPN ID and / or CAG ID (e.g., Charged Data Request [Update]). The CHF can determine / update the new quota and send the new quota to the SMF in a response message (e.g., Charged Data Response [Update]). Figure 16 Example diagrams depicting a PCF procedure according to aspects of embodiments of the present disclosure are shown. Figure 17 Example diagrams of an SMF procedure are depicted according to aspects of embodiments of the present disclosure.

[0259] Figure 18An example call flow that may include one or more actions is shown. The UE may have established a PDU session through a base station, AMF, SMF, PCF, and / or UPF. The UE may send its NPN ID and / or CAG ID to the AF via application signaling messages (e.g., SIP / SDP). The AF may send a message (e.g., an application / service information provision) to the PCF, providing application / service information to the PCF. The application / service information provision message may be sent to the PCF via the NEF. The application / service information provision message may include at least one of the following: NPN ID and / or CAG ID, Service Provider Public Land Mobile Network Identifier (SP PLMNID); at least one UE IP address (e.g., UE IPv4 address and / or UE IPv6 network prefix), at least one UE identity (e.g., SUPI, PEI, and / or GPSI), DNN, or application / service information. Application / service information may include one or more of the following information elements: IP filtering information that identifies the service data stream of the application service, application identifier, media / application / service type, and requested media / application / service QoS (e.g., 5QI, ARP, and / or bandwidth).

[0260] In response to an application / service information provision message received from the AF, the PCF may take one or more actions. In an example action, the PCF may map the SP PLMN ID and / or NPN ID and / or CAG ID and / or application / service information to the radio device's PDU session and / or network slice based on at least one UE IP address and / or DNN and / or NPN ID and / or CAG ID (e.g., the same at least one UE IP address and / or DNN and / or NPN ID and / or CAG ID received from the AF as received from the SMF). In another example, the PCF may map the SP PLMN ID and / or NPN ID and / or CAG ID and / or application / service information to the PDU session and / or the S-NSSAI and / or the NSI ID of the S-NSSAI associated with the PDU session.

[0261] In the example action, based on local operator policies and / or information received from the SMF and / or the AF, the PCF can determine / update the charging control rules for the SP PLMN and / or NPN and / or CAG applied to the UE's PDU sessions and / or network slices. In the example, the PCF can determine the charging rate (e.g., fixed rate) for the SP PLMN and / or NPN and / or CAG based on the SP PLMN ID and / or NPN ID and / or CAG ID and / or information received from the UDR and / or local operator policies. In the example, the PCF can determine the charging method (e.g., converged charging) for the SP PLMN and / or NPN and / or CAG based on the SP PLMN ID and / or NPN ID and / or CAG ID and / or information received from the UDR and / or local operator policies. In the example, the PCF can select the CHF (e.g., a specific CHF for the SP PLMN and / or NPN and / or CAG) based on the SP PLMN ID and / or NPN ID and / or CAG ID and / or charge control information received from the UDR and / or local operator policies. In the example, the charge control rules determined by the PCF can be applied to PDU sessions, network slices (e.g., S-NSSAI and / or the NSI ID of S-NSSAI), QoS flows of NPN and / or CAG, and / or service data flows.

[0262] In the example action, the PCF may send a message to the SMF that includes at least one of the following (e.g., policy association modification): the charge control rules for the SP PLMN and / or NPN and / or CAG; the SP PLMN ID; the NPN ID and / or CAG ID; the PDU session ID; and the NSI ID of the S-NSSAI and / or S-NSSAI.

[0263] In response to a policy association modification message received from the PCF, the SMF may take one or more actions. In an example action, the SMF may send a message to the CHF that includes at least one of the following (e.g., a charge data request): SP PLMNID; PDU session and / or UE NPN ID and / or CAG ID; PDU session ID; at least one UE identity; or S-NSSAI and / or S-NSSAI NSI ID.

[0264] In response to a charge data request message, the CHF can determine the quotas for the SP PLMN and / or NPN and / or CAG based on information received from the SMF (e.g., SP PLMN ID, NPN ID, and / or CAG ID). In the example, the quota may include at least one of the following: authorized units; time quota threshold; or quantity quota threshold. In the example, the CHF can identify different authorized units for different SP PLMNs and / or NPNs and / or CAGs. The CHF can send response information (e.g., a charge data response) to the SMF including the quota and / or SP PLMN ID and / or NPN ID and / or CAG ID.

[0265] In response to a charge data response, the SMF can take one or more actions. In the example actions, the SMF can enforce quotas. In the example actions, the SMF can enforce charge control rules. In the example actions, the SMF can reuse an existing UPF for a PDU session. In the example actions, the SMF can select a new UPF for the SP PLMN and / or NPN and / or CAG ID based on the SP PLMN ID and / or NPN and / or CAG ID. In the example actions, the SMF can select the UPF for the SP PLMN and / or NPN and / or CAG based on quota and / or charge control rules. In the example actions, the SMF can determine at least one of the following user plane rules for the PDU session and / or SP PLMN and / or NPN and / or CAG based on quota and / or charge control rules: at least one packet detection rule; at least one forwarding action rule; at least one QoS enforcement rule; or at least one usage reporting rule. In the example, the SMF can map charge control rules to user plane rules for the SP PLMN and / or NPN and / or CAG. In the example action, the SMF can send a message to the UPF that includes at least one user plane rule and / or SP PLMN ID and / or NPN ID and / or CAG ID.

[0266] In response to messages received from the SMF, the UPF can install user plane rules, send response messages to the SMF (e.g., N4 session establishment / modification response), and execute user plane rules received from the SMF.

[0267] In the example, UPF can execute at least one packet detection rule by matching user data / traffic packets with service flow templates (e.g., service flow filters and / or application identifiers), and can apply other user plane rules (e.g., forwarding action rules, QoS enforcement rules, and usage reporting rules) to data / traffic packets that match the packet detection rule.

[0268] In the example, the UPF can execute at least one forwarding action rule by forwarding, copying, dropping, or buffering data / traffic packets, respectively. In the example, the UPF can redirect traffic to the operator's network portal.

[0269] In the example, the UPF can execute at least one QoS enforcement rule by applying at least one of the QoS parameters (5QI, ARP, MBR, GBR) to the service data stream. In the example, the UPF can execute at least one QoS enforcement rule by applying at least one of the QoS parameters (session AMBR and default 5QI / ARP combination) to the PDU session.

[0270] In the example, the UPF can execute at least one usage reporting rule by measuring the use of network resources in terms of traffic data volume, duration (i.e., time) and / or events according to the measurement method in the usage reporting rule; the UPF can report network resource usage to the SMF when quotas / thresholds are reached and / or when events and / or another trigger are met.

[0271] In the example, the network resource usage reported by the UPF to the SMF may include the amount of traffic data, the duration (i.e., time) applied to at least one of the following: SP PLMN ID and / or NPN ID and / or CAG ID, UE, PDU session, service data stream, application, network slice, or data network.

[0272] The SMF can map received network resource usage to SP PLMN ID and / or NPN ID and / or CAG ID and / or PDU session and / or network slice and / or UE. The SMF can send a message to the CHF including network resource usage and / or SP PLMN ID and / or NPN ID and / or CAG ID (e.g., Charged Data Request [Update]). The CHF can determine / update the new quota and send the new quota to the SMF in a response message (e.g., Charged Data Response [Update]).

[0273] Figure 19An example call flow that may include one or more actions is shown. The UE may determine to initiate a PDU session and send a NAS message to the AMF that includes at least one of the following: S-NSSAI and / or the NSI ID of S-NSSAI, DNN, PDU session ID, request type, or N1 SM container (PDU session establishment request). The UE can initiate a UE-requested PDU session establishment procedure by transmitting a PDU session establishment request message within the N1 SM container of the NAS message. The PDU session establishment request message may include at least one of the following: PDU session ID, requested PDU session type, or requested SSC mode, etc. In the example, the NAS message may include an NPN ID and / or a CAG ID. In the example, the PDU session establishment request message may include an NPN ID and / or a CAG ID. The NPN ID and / or CAG ID can be applied to the PDU session and / or the UE. In the example, the UE may transmit the NAS message via a RAN node (e.g., gNB, base station). The UE can transmit Radio Resource Control (RRC) messages, including NAS messages, to the RAN node (e.g., Uplink (UL) Information Transmission Message, RRC Setup Complete Message, RRC Recovery Complete Message, RRC Reconfiguration Complete Message, etc.). The RAN node can transmit N2 messages, including NAS messages, to the AMF (e.g., NG Message, Initial UE Message, Uplink NAS Transmission Message, Rerouting NAS Request Message, Handover Request Message, Initial Context Setup Request Message, PDU Session Resource Setup / Modification Response Message, PDU Session Resource Modification Required Message, etc.).

[0274] In response to a NAS message received from the UE, the AMF may select an SMF and send a message to the selected SMF including at least one of the following (e.g., a PDU session ID request): SUPI, DNN, S-NSSAI and / or the NSI ID of S-NSSAI, PDU session ID, AMF ID, request type, preferred access, N1 SM container (PDU session establishment request), user location information, access type, PEI. The message sent to the SMF can be used by the AMF to request the establishment of a PDU session. In response to a PDU session ID request message received from the AMF, the SMF may send a response message to the AMF including at least one of the following (e.g., a PDU session rejection (reason)): reason, SM context ID, or N1 SM container (PDU session rejection (reason)).

[0275] The SMF can take one or more actions. In an example action, if PCC is not deployed, the SMF can send a message to the UDM requesting user subscription information (e.g., a subscription retrieval request). The subscription retrieval request message sent to the UDM may include at least one of the following: NPN ID and / or CAG ID, at least one UE identity (e.g., SUPI, PEI, and / or GPSI), at least one UE IP address (e.g., UE IPv4 address and / or UE IPv6 network prefix), default 5QI and default ARP, PDU session type (e.g., IPv4, IPv6, IPv4v6, Ethernet, unstructured); access type (e.g., 3GPP access); RAT type (e.g., 3GPP-NR-FDD); PLMN identifier; application identifier; assigned application instance identifier; DNN, S-NSSAI and / or S-NSSAI NSI ID, PDU session ID, user location information, or SMF information for the PDU session (e.g., SMF identifier, IP address, or SMF FQDN).

[0276] In response to a subscription retrieval request message received from the SMF, the UDM may take one or more actions. In an example action, the UDM may determine that charge control information for the NPN and / or CAG applies to the radio device and / or network slice and / or PDU session and / or DNN, wherein the radio device may be identified by at least one UE identity, the NPN may be identified by an NPN ID, the CAG may be identified by a CAG ID, the network slice may be identified by an S-NSSAI and / or an NSI ID of the S-NSSAI, the PDU session may be identified by a PDU session ID, and the data network may be identified by a DNN. In the example, the UDM may determine the charge control information for the NPN and / or CAG based on operator policies, local policies, and / or configuration. In the example, user subscription information may include indications that charge control applies to the NPN and / or CAG of the radio device. In the example, user subscription information may include at least one of the following: the charge rate of the NPN and / or CAG, the charge method of the NPN and / or CAG (e.g., offline charge, online charge, or converged charge), or the address of the charge function of the NPN and / or CAG. In the example, the UDM can determine charge control information based on user subscription information. In the example, charge control information may include at least one of the following: charge rate, charge method, or address of chargeable function. The charge method may include at least one of the following: offline charge, online charge, or combined charge. In the example action, the UDM may send a response message (e.g., a subscription retrieval response) to the SMF, the response message including at least one of the following: charge control information for NPN and / or CAG; NPN ID and / or CAG ID.

[0277] In response to a subscription retrieval response message received from the UDM, the SMF can determine the charging control policies for the NPN and CAG. The SMF can determine the charging control rules for the NPN ID and / or CAG ID based on information received from the UDM (e.g., charging control information) and / or information received from the AMF (e.g., NPN ID and / or CAG ID) and / or local operator policies. The charging control rules may include at least one of the following: charging rate, charging method, or address of the charging function. The charging method may include at least one of the following: offline charging, online charging, or bundled charging. In the example, the SMF can determine the charging rate (e.g., a fixed rate) for the NPN and / or CAG based on the charging control information received from the UDM and / or local operator policies. In the example, the SMF can determine the charging method (e.g., offline charging) for the NPN and / or CAG based on the charging control information received from the UDM and / or local operator policies. In the example, the SMF can select the CHF (e.g., a specific CHF for the NPN and / or CAG) based on charge control information received from the UDM and / or operator-local policies. In the example, the charge control rules determined by the SMF can be applied to PDU sessions, network slices (e.g., S-NSSAI and / or the NSI ID of S-NSSAI), QoS flows, and / or service data flows of the NPN and / or CAG.

[0278] In the example action, the SMF may send a message to the CHF that includes at least one of the following (e.g., a charge data request): the PDU session and / or the UE's NPN ID and / or CAG ID; the PDU session ID; at least one UE identity; or the S-NSSAI and / or the S-NSSAI's NSI ID.

[0279] In response to a charge data request message, the CHF can determine the quotas for the NPN and / or CAG based on information received from the SMF (e.g., NPN ID and / or CAG ID). In the example, the quota may include at least one of the following: authorization unit; time quota threshold; or quantity quota threshold. In the example, the CHF can determine the higher authorization unit for the NPN and / or CAG. The CHF can send response information (e.g., a charge data response) to the SMF including the quota and / or NPN ID and / or CAG ID.

[0280] In response to a charge data response, the SMF can take one or more actions. In the example actions, the SMF can enforce quotas. In the example actions, the SMF can enforce charge control rules. In the example actions, the SMF can select the UPF for the NPN and / or CAG based on the NPN ID and / or CAG ID. In the example actions, the SMF can select the UPF for the NPN and / or CAG based on quota and / or charge control rules. In the example actions, the SMF can determine at least one of the following user plane rules for the PDU session and / or NPN and / or CAG based on quota and / or charge control rules: at least one packet detection rule; at least one forwarding action rule; at least one QoS enforcement rule; or at least one usage reporting rule. In the example, the SMF can map charge control rules to user plane rules for the NPN and / or CAG. In the example actions, the SMF can send a message to the UPF including at least one user plane rule and / or the NPN ID and / or CAG ID.

[0281] In response to messages received from the SMF, the UPF can install user plane rules, send response messages to the SMF (e.g., N4 session establishment / modification response), and execute user plane rules received from the SMF.

[0282] In the example, UPF can execute at least one packet detection rule by matching user data / traffic packets with service flow templates (e.g., service flow filters and / or application identifiers), and can apply other user plane rules (e.g., forwarding action rules, QoS enforcement rules, and usage reporting rules) to data / traffic packets that match the packet detection rule.

[0283] In the example, the UPF can execute at least one forwarding action rule by forwarding, copying, dropping, or buffering data / traffic packets, respectively. In the example, the UPF can redirect traffic to the operator's network portal.

[0284] In the example, the UPF can execute at least one QoS enforcement rule by applying at least one of the QoS parameters (5QI, ARP, MBR, GBR) to the service data stream. In the example, the UPF can execute at least one QoS enforcement rule by applying at least one of the QoS parameters (session AMBR and default 5QI / ARP combination) to the PDU session.

[0285] In the example, the UPF can execute at least one usage reporting rule by measuring the use of network resources in terms of traffic data volume, duration (i.e., time) and / or events according to the measurement method in the usage reporting rule; the UPF can report network resource usage to the SMF when quotas / thresholds are reached and / or when events and / or another trigger are met.

[0286] In the example, the network resource usage reported by the UPF to the SMF may include the amount of traffic data, the duration (i.e., time) applied to at least one of the following: SP PLMN ID and / or NPN ID and / or CAG ID, UE, PDU session, service data stream, application, network slice, or data network.

[0287] The SMF can map received network resource usage to NPN ID and / or CAG ID and / or PDU session and / or network slice and / or UE. The SMF can send a message to the CHF including the NPN ID and / or CAG ID of the network resource usage (e.g., a charged data request [update]). The CHF can determine / update the new quota and send the new quota to the SMF in a response message (e.g., a charged data response [update]).

[0288] Figure 20 An example call flow that may include one or more actions is shown. The UE may send a NAS message (e.g., a service request message) to the AMF that includes at least one of the following: S-NSSAI and / or the S-NSSAI's NSI ID, DNN, PDU session ID, or request type. In the example, the NAS message may include an NPN ID and / or a CAG ID. The NPN ID and / or CAG ID may be applied to the PDU session and / or the UE and / or the network slice (e.g., the S-NSSAI and / or the S-NSSAI's NSI ID) and / or the DNN. In the example, the UE may transmit the NAS message via a RAN node (e.g., a gNB, a base station). The UE may transmit Radio Resource Control (RRC) messages (e.g., uplink (UL) information transmission messages, RRC setup complete messages, RRC recovery complete messages, RRC reconfiguration complete messages, etc.) that include the NAS message to the RAN node. The RAN node can transmit N2 messages, including NAS messages, to the AMF (e.g., NG messages, initial UE messages, uplink NAS transmission messages, rerouting NAS request messages, handover request messages, initial context setting request messages, PDU session resource setting / modification response messages, PDU session resource modification required messages, etc.).

[0289] In response to a NAS message received from the UE, the AMF may select an SMF and send a message to the selected SMF including at least one of the following (e.g., a PDUession_UpdateSMContext request): SUPI, DNN, S-NSSAI and / or the NSI ID of S-NSSAI, PDU session ID, AMF ID, request type, preferred access, user location information, access type, PEI. In response to a PDUession_UpdateSMContext request message received from the AMF, the SMF may send a response message to the AMF including at least one of the following (e.g., a PDUession_UpdateSMContext response): reason, SM context ID, or N1 SM container (PDU session rejection (reason)).

[0290] The SMF can take one or more actions. In an example action, if a PCC is deployed, the SMF can send a message to the PCF including at least one of the following (e.g., a policy establishment / modification request): NPN ID and / or CAG ID, at least one UE identity (e.g., SUPI, PEI, and / or GPSI), at least one UE IP address (e.g., UE IPv4 address and / or UE IPv6 network prefix), default 5QI and default ARP, PDU session type (e.g., IPv4, IPv6, IPv4v6, Ethernet, unstructured); access type (e.g., 3GPP access); RAT type (e.g., 3GPP-NR-FDD); PLMN identifier; application identifier; assigned application instance identifier; DNN, S-NSSAI and / or S-NSSAI NSI ID, PDU session ID, user location information, or SMF information for the PDU session (e.g., SMF identifier, IP address, or SMF FQDN).

[0291] In response to a policy establishment / modification request message received from the SMF, the PCF may send a message to the UDR requesting user subscription information (e.g., a subscription retrieval request). The subscription retrieval request message sent to the UDR may include at least one of the following: NPN ID and / or CAG ID, at least one UE identity (e.g., SUPI, PEI, and / or GPSI), at least one UE IP address (e.g., UE IPv4 address and / or UE IPv6 network prefix), default 5QI and default ARP, PDU session type (e.g., IPv4, IPv6, IPv4v6, Ethernet, unstructured); access type (e.g., 3GPP access); RAT type (e.g., 3GPP-NR-FDD); PLMN identifier; application identifier; assigned application instance identifier; DNN, S-NSSAI and / or S-NSSAI NSI ID, PDU session ID, user location information, or SMF information for the PDU session (e.g., SMF identifier, IP address, or SMF FQDN).

[0292] In response to a subscription retrieval request message received from the PCF, the UDR may take one or more actions. In an example action, the UDR may determine that charge control information for the NPN and / or CAG applies to the radio device and / or network slice and / or PDU session, wherein the radio device may be identified by at least one UE identity, the NPN may be identified by an NPN ID, the CAG may be identified by a CAG ID, the network slice may be identified by an S-NSSAI and / or an NSI ID of the S-NSSAI, and the PDU session may be identified by a PDU session ID. In the example, the UDR may determine the charge control information for the NPN and / or CAG based on operator policies, local policies, and / or configuration. In the example, user subscription information may include an indication that charge control applies to the NPN and / or CAG of the radio device. In the example, user subscription information may include at least one of the following: the charge rate of the NPN and / or CAG, the charge method of the NPN and / or CAG (e.g., offline charge, online charge, or converged charge), or the address of the charge function of the NPN and / or CAG. In the example, the UDR may determine the charge control information based on the user subscription information. In the example, charge control information may include at least one of the following: charge rate, charge method, or address of charge function. The charge method may include at least one of the following: offline charge, online charge, or combined charge. In the example action, the UDR may send response information (e.g., a subscription retrieval response) to the PCF, the response information including at least one of the following: charge control information for NPN and / or CAG; NPN ID and / or CAG ID.

[0293] In response to a subscription retrieval response message received from the UDR, the PCF may take one or more actions. In example actions, the PCF may determine the charging control policy for the NPN and / or CAG. The PCF may determine the charging control rules for the NPN ID and / or CAG ID based on information received from the UDR (e.g., charging control information) and / or information received from the SMF (e.g., NPN ID and / or CAG ID) and / or operator-local policies. The charging control rules may include at least one of the following: charging rate, charging method, or address of the charging function. The charging method may include at least one of the following: offline charging, online charging, or bundled charging. In the example, the PCF may determine the charging rate (e.g., fixed rate) for the NPN and / or CAG based on the charging control information received from the UDR and / or operator-local policies. In the example, the PCF may determine the charging method (e.g., offline charging) for the NPN and / or CAG based on the charging control information received from the UDR and / or local operator policies. In the example, the PCF can select the CHF (e.g., a specific CHF for the NPN and / or CAG) based on charge control information received from the UDR and / or local operator policies. In the example, the charge control rules determined by the PCF can be applied to PDU sessions, network slices (e.g., S-NSSAI and / or the NSI ID of S-NSSAI), QoS flows, and / or service data flows of the NPN and / or CAG.

[0294] In the example action, the PCF may send a message to the SMF that includes at least one of the following (e.g., a policy establishment / modification response): the toll control rules of the NPN and / or CAG; the NPN ID and / or CAG ID; the PDU session ID; and the S-NSSAI and / or the S-NSSAI NSI ID.

[0295] In response to a policy establishment / modification response message received from the PCF, the SMF may take one or more actions. In an example action, the SMF may send a message to the CHF that includes at least one of the following (e.g., a charge data request): the PDU session and / or the UE's NPN ID and / or CAG ID; the PDU session ID; at least one UE identity; or the S-NSSAI and / or the S-NSSAI's NSI ID.

[0296] In response to a charge data request message, the CHF can determine the quotas for the NPN and / or CAG based on information received from the SMF (e.g., NPN ID and / or CAG ID). In the example, the quota may include at least one of the following: authorization unit; time quota threshold; or quantity quota threshold. In the example, the CHF can determine the higher authorization unit for the NPN and / or CAG. The CHF can send response information (e.g., a charge data response) to the SMF including the quota and / or NPN ID and / or CAG ID.

[0297] In response to a charge data response, the SMF can take one or more actions. In the example actions, the SMF can enforce quotas. In the example actions, the SMF can enforce charge control rules. In the example actions, the SMF can select the UPF for the NPN and / or CAG based on the NPN ID and / or CAG ID. In the example actions, the SMF can select the UPF for the NPN and / or CAG based on quota and / or charge control rules. In the example actions, the SMF can determine at least one of the following user plane rules for the PDU session and / or NPN and / or CAG based on quota and / or charge control rules: at least one packet detection rule; at least one forwarding action rule; at least one QoS enforcement rule; or at least one usage reporting rule. In the example, the SMF can map charge control rules to user plane rules for the NPN and / or CAG. In the example actions, the SMF can send a message to the UPF including at least one user plane rule and / or the NPN ID and / or CAG ID.

[0298] In response to messages received from the SMF, the UPF can install user plane rules, send response messages to the SMF (e.g., N4 session establishment / modification response), and execute user plane rules received from the SMF.

[0299] In the example, UPF can execute at least one packet detection rule by matching user data / traffic packets with service flow templates (e.g., service flow filters and / or application identifiers), and can apply other user plane rules (e.g., forwarding action rules, QoS enforcement rules, and usage reporting rules) to data / traffic packets that match the packet detection rule.

[0300] In the example, the UPF can execute at least one forwarding action rule by forwarding, copying, dropping, or buffering data / traffic packets, respectively. In the example, the UPF can redirect traffic to the operator's network portal.

[0301] In the example, the UPF can execute at least one QoS enforcement rule by applying at least one of the QoS parameters (5QI, ARP, MBR, GBR) to the service data stream. In the example, the UPF can execute at least one QoS enforcement rule by applying at least one of the QoS parameters (session AMBR and default 5QI / ARP combination) to the PDU session.

[0302] In the example, the UPF can execute at least one usage reporting rule by measuring the use of network resources in terms of traffic data volume, duration (i.e., time) and / or events according to the measurement method in the usage reporting rule; the UPF can report network resource usage to the SMF when quotas / thresholds are reached and / or when events and / or another trigger are met.

[0303] In the example, the network resource usage reported by the UPF to the SMF may include the amount of traffic data, the duration (i.e., time) applied to at least one of the following: NPN ID and / or CAG ID, UE, PDU session, QoS flow, service data flow, application, network slice, or data network.

[0304] The SMF can map received network resource usage to NPN ID and / or CAG ID and / or PDU session and / or network slice and / or UE. The SMF can send a message to the CHF including network resource usage and / or NPN ID and / or CAG ID (e.g., Charged Data Request [Update]). The CHF can determine / update the new quota and send the new quota to the SMF in a response message (e.g., Charged Data Response [Update]). Figure 16 Example diagrams depicting a PCF procedure according to aspects of embodiments of the present disclosure are shown. Figure 17 Example diagrams of an SMF procedure are depicted according to aspects of embodiments of the present disclosure.

[0305] In the example, the Policy Control Function (PCF) can receive a first message from the Session Management Function (SMF) requesting the establishment of a policy for a Packet Data Unit (PDU) session of a radio device. This first message includes at least one Closed Access Group Identifier (CAG ID). In the example, the PCF can receive a subscription response message from the Unified Data Storehouse (UDR), which includes at least one CAG ID and charging control information for that CAG ID. In the example, the PCF can determine charging control rules for at least one CAG ID for a PDU session based on the at least one CAG ID and its charging control information. These charging control rules include: a charging rate for at least one CAG ID; a charging method for at least one CAG ID; and the address of the charging function for at least one CAG ID. In the example, the PCF can send a second message to the SMF including the charging control rules. In the example, the first message also includes at least one of the following: the identity of the radio device; a PDU session identifier; a first Single Network Slice Selection Auxiliary Information (S-NSSAI); or a first network slice instance identifier of the first S-NSSAI. In the example, at least one CAG ID may include at least one identifier of a non-public network (NPN ID). In the example, the PCF can send a subscription request message to the UDR containing at least one CAG ID and a first PDU session, the subscription request message including at least one of the following: at least one CAG ID; the identity of the radio device; or a PDU session identifier. In the example, the SMF can receive a PDU session creation request message including at least one CAG ID from the Access and Mobility Management Function (AMF). In the example, the SMF can send a first charge request message containing at least one CAG ID and a PDU session including at least one CAG ID to the CHF. In the example, the CHF can determine first quota information for at least one CAG ID based on at least one CAG ID, wherein the first quota information includes at least one of the following: at least one CAG ID; an authorization unit; a time quota threshold; or a quantity quota threshold. In the example, the CHF can send a first charge response message including the first quota information to the SMF. In the example, the SMF can determine at least one user plane rule for at least one CAG ID based on the first quota information. In the example, the SMF can determine at least one user plane rule for at least one CAG ID based on a charge control rule. In the example, the SMF can send at least one user plane rule and at least one CAG ID to the UPF. In the example, at least one user plane rule includes at least one of the following: at least one group detection rule; or at least one usage reporting rule. In the example, UPF can detect and collect resource usage for at least one CAG ID.In the example, resource usage may include at least one of the following: time usage for at least one CAG ID; or quantity usage for at least one CAG ID. In the example, the UPF may send the resource usage of at least one CAG ID to the SMF. In the example, the SMF may send a second charge request message including the resource usage to the CHF. In the example, the CHF may determine second quota information for at least one CAG ID based on the resource usage. In the example, the CHF may send a second charge response message including the second quota information to the SMF. In the example, the charge control information for at least one CAG ID may include the subscription charge rate for at least one CAG ID. In the example, the charge control information for at least one CAG ID includes the subscription address of the CHF for at least one CAG ID.

[0306] In the example, the Session Management Function (SMF) can receive an establishment request message for a Packet Data Unit (PDU) session for a radio device from the Access and Mobility Management Function (AMF). This establishment request message may include a Closed Access Group Identifier (CAG ID) for the PDU session and the radio device. In the example, the SMF can send a policy establishment request including the CAG ID to the Policy Control Function (PCF). In the example, the SMF can receive a policy establishment response message from the PCF including charging control rules, where the charging control rules include: the charging rate for the CAG ID; the charging method for the CAG ID; and the CHF address for the CAG ID. In the example, the SMF can send a charge data request message including the CAG ID to the Charging Function (CHF). In the example, the SMF can receive a charge data response message including quota information for the CAG ID from the CHF. In the example, the SMF can determine the user plane rules for the CAG ID based on the charging control rules and quota information. In the example, the SMF can select a User Plane Function (UPF) based on the CAG ID. In the example, the SMF can send user plane rules to the UPF, where the user plane rules include: at least one packet detection rule; or at least one usage reporting rule.

[0307] In the example, the Charging Function (CHF) can receive a Charging Data Request message from the Session Management Function (SMF), which includes a Closed Access Group Identifier (CAG ID) for a Packet Data Unit (Packet Data Unit) session. In the example, the CHF can determine quota information for the CAG ID, wherein the quota information includes at least one of the following: an Authorization Unit; a Time Quota Threshold; a Concurrent Quota Threshold; and quota information sent by the CHF to the SMF.

[0308] In the example, the Policy Control Function (PCF) can receive provisional service information messages from the Application Function (AF). These messages include: a Closed Access Group Identifier (CAG ID); a Service Provider Public Land Mobile Network Identifier (SP PLMN ID); a radio device identifier; and service information for the radio device. In the example, the PCF can map the SP PLMN ID and service information to an Internet Protocol Connectivity Access Network (IP-CAN) session based on the CAG ID and the radio device identifier. In the example, the PCF can update / create charging control rules for the CAG ID and SP PLMN ID, where the charging control rules include: the charging rate for the CAG ID and SP PLMN ID; the charging method for the CAG ID and SP PLMN ID; and the address of the charging function for the CAG ID and SP PLMN ID. In the example, the PCF can send the charging control rules to the Service Provider Function (SMF).

[0309] According to various embodiments, apparatuses such as wireless devices, off-grid wireless devices, base stations, session management functions, policy control functions, application functions, access and mobility management functions, user plane functions, unified data management, and charging functions may include one or more processors and a memory. The memory may store instructions that, when executed by the one or more processors, cause the apparatus to perform a series of actions. Examples of exemplary actions are illustrated in the accompanying drawings and description. Features from various embodiments can be combined to create other embodiments.

[0310] According to various embodiments, the Session Management Function (SMF) can receive a message from the Access and Mobility Management Function (AMF) including the PLMN identifier of the Public Land Mobile Network (PLMN) of the radio device. According to various embodiments, the SMF can send a policy request message to the Policy Control Function (PCF), the policy request message including: the NPN identifier of a Non-Public Network (NPN) through which the radio device accesses the PLMN; and the PLMN identifier of the PLMN. According to various embodiments, the SMF can receive a policy response message from the PCF including a charging control policy. According to various embodiments, the SMF can send a charging data request message to the Charging Function (CHF) based on the policy response message, wherein the charging data request message includes the PLMN identifier.

[0311] According to various embodiments, charging control policies can be determined based on NPN identifiers and PLMN identifiers. According to various embodiments, the message may also include at least one of the following: an NPN identifier; a radio device identifier for the radio device; a data network name (DNN); single network slice selection assistance information (S-NSSAI); and / or a packet data unit (PDU) session identifier. According to various embodiments, the message may also include a PDU session establishment request message, wherein the PDU session establishment request message may include at least one of the following: an NPN identifier; and / or a packet data unit (PDU) session identifier. According to various embodiments, the NPN identifier is applied to at least one of the following: a radio device; a DNN; a network slice identified by the S-NSSAI; and a PDU session identified by the PDU session identifier. According to various embodiments, the policy request message may also include at least one of the following: a radio device identifier; a data network name (DNN); single network slice selection assistance information (S-NSSAI); or a packet data unit (PDU) session identifier. According to various embodiments, the PCF can send NPN subscription request messages and Packet Data Unit (PDU) sessions to the Unified Data Store (UDR), wherein the subscription request message may include at least one of the following: an NPN identifier; a PLMN identifier; a radio device identifier; a PDU session identifier; or Single Network Slice Selection Auxiliary Information (S-NSSAI). According to various embodiments, the UDR can determine charging control information applied to at least one of the following: an NPN; a radio device; a PDU session; S-NSSAI; and / or a DNN. According to various embodiments, the PCF can receive subscription response messages from the UDR, which include at least one of the following: charging control information for the NPN; and / or an NPN identifier. According to various embodiments, based on the NPN charging control information, the PCF can determine NPN charging control rules, wherein the charging control rules may include at least one of the following: an NPN charging rate; an NPN charging method; and / or the address of the NPN charging function. According to various embodiments, the PCF can send a policy response message to the SMF, the policy response message including at least one of the following: charging control rules; NPN identifier; PDU session identifier; and / or S-NSSAI. According to various embodiments, the AMF can receive non-access stratum messages from the radio device, the non-access stratum messages including at least one of the following: S-NSSAI; DNN; and / or PDU session identifier.

[0312] According to various embodiments, the AMF can receive a non-access stratum message including a PDU session establishment request message from a radio device, wherein the PDU session establishment request message may include at least one of the following: an NPN identifier; and / or a PDU session identifier. According to various embodiments, a charge data request message may also include at least one of the following: an NPN identifier; a radio device identifier; a PDU session identifier; or single network slice selection assistance information (S-NSSAI). According to various embodiments, based on the NPN identifier, the CHF can determine first quota information for the NPN, wherein the first quota information may include at least one of the following: an NPN identifier; an authorization unit; a time quota threshold; and / or a quantity quota threshold. According to various embodiments, the CHF can send a charge response message including the first quota information to the SMF. According to various embodiments, the SMF can send a user plane message to the UPF, the user plane message including at least one of the following: user plane rules; and / or identifiers. According to various embodiments, the UPF can detect and collect resource usage of the NPN, wherein resource usage may include at least one of the following: time usage of the NPN; and / or quantity usage of the NPN. According to various embodiments, the UPF can send the resource usage of the NPN to the SMF. According to various embodiments, the SMF can send a second charge request message including the resource usage of the NPN to the CHF.

[0313] Figure 21 This is a flowchart illustrating an aspect of an exemplary embodiment according to the present disclosure. At 2110, the Session Management Function (SMF) may send a policy request message to the Policy Control Function (PCF), the policy request message including: an NPN identifier of a non-public network (NPN) through which the radio device accesses a Public Land Mobile Network (PLMN); and / or a PLMN identifier. At 2120, the SMF may receive a policy response message from the PCF including a charge control policy.

[0314] According to various embodiments, charging control policies can be determined based on NPN identifiers and PLMN identifiers. According to various embodiments, the SMF can receive messages from the Access and Mobility Management Function (AMF) including one or more of the NPN identifier and PLMN identifier. According to various embodiments, the SMF can send a charging data request message to the Charging Function (CHF) based on a policy response message. According to various embodiments, the charging data request message may include the PLMN identifier. According to various embodiments, the policy request message may also include at least one of the following: a radio device identifier for the radio device; a data network name (DNN); a single network slice selection aid information (S-NSSAI); and / or a packet data unit (PDU) session identifier. According to various embodiments, the Session Management Function (SMF) can send a policy request message to the Policy Control Function (PCF), the policy request message including: an NPN identifier for a non-public network (NPN) through which the radio device accesses a public land mobile network (PLMN); and / or a PLMN identifier for the PLMN. According to various embodiments, the SMF can receive a policy response message from the PCF including a charge control policy, wherein the charge control policy can be determined based on an NPN identifier and a PLMN identifier. According to various embodiments, the SMF can send a charge data request message to the Charging Function (CHF) based on the policy response message, wherein the charge data request message can include a PLMN identifier. According to various embodiments, the SMF can receive a message from the Access and Mobility Management Function (AMF) including one or more of an NPN identifier and a PLMN identifier. According to various embodiments, the policy request message may also include at least one of the following: a radio device identifier of a radio device; a data network name (DNN); a single network slice selection assistance information (S-NSSAI); and / or a packet data unit (PDU) session identifier. According to various embodiments, the Session Management Function (SMF) can receive messages from the Access and Mobility Management Function (AMF) including a radio device identifier, a Public Land Mobile Network (PLMN) identifier, an NPN identifier of a non-public network (NPN) (through which the radio device accesses the PLMN), and one or more of the following: a Data Network Name (DNN); Single Network Slice Selection Auxiliary Information (S-NSSAI); and / or a Packet Data Unit (PDU) session identifier. According to various embodiments, the SMF can send a policy request message to the Policy Control Function (PCF), which includes a radio device identifier, a PLMN identifier, an NPN identifier, and one or more of the following: a DNN; an S-NSSAI; and / or a PDU session identifier.According to various embodiments, the PCF can determine a charging control policy based on the NPN identifier, the PLMN identifier, and charging control information for the NPN received from the Unified Data Repository (UDR). According to various embodiments, the SMF can receive a policy response message from the PCF including the charging control policy. According to various embodiments, the SMF can send a charging data request message to the Charging Function (CHF) based on the policy response message, wherein the charging data request message may include the PLMN identifier.

[0315] Figure 22 This is a flowchart illustrating an aspect of an exemplary embodiment according to the present disclosure. At 2210, the Policy Control Function (PCF) may receive a message from the Session Management Function (SMF) including: a PLMN identifier for a Public Land Mobile Network (PLMN); and / or an NPN identifier for a Non-Public Network (NPN). At 2220, the PCF may send a subscription request message including the PLMN identifier and the NPN identifier to the Unified Data Repository (UDR). At 2230, the PCF may receive a subscription response message from the UDR, which includes charge control information for the NPN. At 2240, the PCF may determine charge control rules for the NPN of the PDU session based on the charge control information. At 2250, the PCF may send a second message including the charge control rules to the SMF.

[0316] According to various embodiments, the message may include a request for policy establishment for a Packet Data Unit (PDU) session of a radio device. According to various embodiments, an NPN identifier may identify an NPN, through which the radio device accesses a PLMN associated with a PLMN identifier. According to various embodiments, the subscription response message may also include an NPN identifier. According to various embodiments, determining the charging control rules may also be based on the PLMN identifier and the NPN identifier. According to various embodiments, the charging control rules may include one or more of the following: the NPN's charging rate; the NPN's charging method; and / or the address of the NPN's charging function. According to various embodiments, the Policy Control Function (PCF) may receive from the Session Management Function (SMF) a message including a request for policy establishment for a Packet Data Unit (PDU) session of a radio device, the message including: a PLMN identifier for a Public Land Mobile Network (PLMN); and / or an NPN identifier for a Non-Public Network (NPN), through which the radio device accesses the PLMN. According to various embodiments, the PCF may send a subscription request message including a PLMN identifier and an NPN identifier to a Unified Data Repository (UDR). According to various embodiments, the PCF can receive a subscription response message from the UDR, the subscription response message including charge control information for the NPN. According to various embodiments, the PCF can determine the charge control rules for the NPN of the PDU session based on the charge control information. According to various embodiments, the PCF can send a second message including the charge control rules to the SMF. According to various embodiments, the charge control rules may include one or more of the following: the NPN charge rate; the NPN charge method; and / or the address of the NPN charge function. According to various embodiments, the Policy Control Function (PCF) can receive a message from the Session Management Function (SMF) including a request for policy establishment for a Packet Data Unit (PDU) session of a radio device, the message including: a PLMN identifier for a Public Land Mobile Network (PLMN); and / or an NPN identifier for a Non-Public Network (NPN), through which the radio device accesses the PLMN. According to various embodiments, the PCF can send a subscription request message including a PLMN identifier and an NPN identifier to the Unified Data Repository (UDR). According to various embodiments, the PCF can receive a subscription response message from the UDR, the subscription response message including charge control information for the NPN. According to various embodiments, the PCF can determine the charging control rules for the NPN of a PDU session based on charging control information, the PLMN identifier, and / or the NPN identifier. The charging control rules may include one or more of the following: the NPN's charging rate; the NPN's charging method; and / or the address of the NPN's charging function. According to various embodiments, the PCF may send a second message including the charging control rules to the SMF.

[0317] According to various embodiments, the Policy Control Function (PCF) can receive a message from the Session Management Function (SMF) including a request for policy establishment for a Packet Data Unit (PDU) session of a radio device. The message includes: a PLMN identifier for a Public Land Mobile Network (PLMN); and an NPN identifier for a Non-Public Network (NPN) through which the radio device accesses the PLMN. According to various embodiments, the PCF can send a subscription request message including the PLMN identifier and the NPN identifier to a Unified Data Repository (UDR). According to various embodiments, the PCF can receive a subscription response message from the UDR, including charge control information for the NPN. According to various embodiments, the PCF can determine charge control rules for the NPN of a PDU session based on the charge control information, the PLMN identifier, and / or the NPN identifier. The charge control rules may include one or more of the following: the NPN charge rate; the NPN charge method; and / or the address of the NPN charge function. According to various embodiments, the PCF can send a second message including the charge control rules to the SMF.

[0318] Figure 23 This is a flowchart of an example embodiment according to the present disclosure. At 2310, the Charging Function (CHF) can receive a Charging Data Request message from the Session Management Function (SMF). The Charging Data Request message may include an identifier of a Non-Public Network (NPN) for a Packet Data Unit (PDU) session. At 2320, based on the NPN identifier, the CHF can determine the NPN's quota information. At 2330, the CHF can send a response message including the quota information to the SMF.

[0319] According to various embodiments, quota information may include an authorization unit of the NPN. According to various embodiments, quota information may include a time quota threshold of the NPN. According to various embodiments, quota information may include a quantity quota threshold of the NPN. According to various embodiments, the response message may also include an NPN identifier. According to various embodiments, the CHF may receive a second charge request message from the SMF that includes resource usage of the NPN. According to various embodiments, the Charging Function (CHF) may receive a charge data request message from the Session Management Function (SMF) that includes an identifier for a non-public network (NPN) for a Packet Data Unit (PDU) session. According to various embodiments, based on the NPN identifier, the CHF may determine the quota information of the NPN. Quota information may include one or more of the following: an authorization unit of the NPN; a time quota threshold of the NPN; a quantity quota threshold of the NPN. According to various embodiments, the CHF may send a response message including quota information to the SMF. According to various embodiments, the response message may also include an NPN identifier.

[0320] According to various embodiments, the Charging Function (CHF) can receive a charging data request message from the Session Management Function (SMF). The charging data request message may include an identifier of a non-public network (NPN) for a Packet Data Unit (PDU) session. According to various embodiments, based on the NPN identifier, the CHF can determine the NPN's quota information. The quota information may include one or more of the following: the NPN's authorization unit; the NPN's time quota threshold; and the NPN's quantity quota threshold. According to various embodiments, the CHF can send a response message to the SMF. The response message may include quota information and the NPN identifier. According to various embodiments, the CHF can receive a second charging request message from the SMF that includes resource usage of the NPN. According to various embodiments, the second charging request message may include the NPN identifier.

[0321] According to various embodiments, a Session Management Function (SMF) may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to receive from an Access and Mobility Management Function (AMF) a message including a PLMN identifier of a Public Land Mobile Network (PLMN) for a radio device. According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to send a Policy Request message to a Policy Control Function (PCF) including: an NPN identifier of a Non-Public Network (NPN) through which the radio device accesses the PLMN; and a PLMN identifier of the PLMN. According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to receive from the PCF a Policy Response message including a charging control policy. According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to send a Charging Data Request message to a Charging Function (CHF) based on a Policy Response message, wherein the Charging Data Request message may include a PLMN identifier.

[0322] According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to send a policy request message to a Policy Control Function (PCF). The policy request message may include an NPN identifier for a non-public network (NPN) through which a radio device accesses a Public Land Mobile Network (PLMN); and a PLMN identifier for the PLMN. According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to receive a policy response message from the PCF, including a charging control policy.

[0323] According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to send a policy request message to a Policy Control Function (PCF). The policy request message includes: an NPN identifier of a non-public network (NPN) through which a radio device accesses a Public Land Mobile Network (PLMN); and a PLMN identifier of the PLMN. According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to receive a policy response message from the PCF including a charging control policy, wherein the charging control policy may be determined based on the NPN identifier and the PLMN identifier. According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to send a charging data request message to a Charging Function (CHF) based on a policy response message, wherein the charging data request message includes the PLMN identifier.

[0324] According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to receive messages from the Access and Mobility Management Function (AMF). These messages include a radio device identifier for the radio device, a Public Land Mobile Network (PLMN) identifier for the radio device, an NPN identifier for a non-public network (NPN) through which the radio device accesses the PLMN, and one or more of the following: a Data Network Name (DNN); Single Network Slice Selection Auxiliary Information (S-NSSAI); and / or a Packet Data Unit (PDU) session identifier.

[0325] According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to send a policy request message including a Radio Device Identifier, a PLMN identifier, an NPN identifier, and one or more of the following: DNN; S-NSSAI; and / or PDU session identifier. According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to receive a policy response message including a charging control policy. According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to send a charging data request message to a Charging Function (CHF) based on a policy response message, wherein the charging data request message includes a PLMN identifier.

[0326] According to various embodiments, a policy control function (PCF) may include one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the PCF to receive a policy request message. According to various embodiments, a policy control function (PCF) may include one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the PCF to determine a charging control policy based on an NPN identifier, a PLMN identifier, and charging control information for the NPN received from a unified data store (UDR). According to various embodiments, a policy control function (PCF) may include one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the PCF to send a policy response message.

[0327] According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to receive a message from the Session Management Function (SMF), the message including: a PLMN identifier for a Public Land Mobile Network (PLMN); and an NPN identifier for a Non-Public Network (NPN). According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to send a subscription request message including a PLMN identifier and an NPN identifier to a Unified Data Repository (UDR). According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to receive a subscription response message from the UDR, the subscription response message including charge control information for the NPN. According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to determine charge control rules for the NPN of a PDU session based on the charge control information. According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to send a second message including charge control rules to the SMF.

[0328] According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to receive from the Session Management Function (SMF) a message including a request for policy establishment for a Packet Data Unit (PDU) session of a radio device, the message including: a PLMN identifier for a Public Mobile Network (PLMN); and an NPN identifier for a Non-Public Network (NPN), through which the radio device accesses the PLMN. According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to send a subscription request message including a PLMN identifier and an NPN identifier to a Unified Data Repository (UDR). According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to receive a subscription response message from the UDR, the subscription response message including charge control information for the NPN. According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to determine charge control rules for the NPN of the PDU session based on the charge control information. According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to send a second message to the SMF including toll control rules.

[0329] According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to receive from the Session Management Function (SMF) a message including a request for policy establishment for a Packet Data Unit (PDU) session of a radio device, the message including: a PLMN identifier for a Public Mobile Network (PLMN); and an NPN identifier for a Non-Public Network (NPN), through which the radio device accesses the PLMN. According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to send a subscription request message including a PLMN identifier and an NPN identifier to a Unified Data Repository (UDR). According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to receive a subscription response message from the UDR, the subscription response message including charge control information for the NPN. According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to determine charge control rules for the NPN of a PDU session based on the charge control information, the PLMN identifier, and the NPN identifier. According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to send a second message to the SMF including toll control rules.

[0330] According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to receive from the Session Management Function (SMF) a message including a request for policy establishment of a Packet Data Unit (PDU) session for a radio device. The message includes: a PLMN identifier for a Public Mobile Network (PLMN); and an NPN identifier for a Non-Public Network (NPN), through which the radio device accesses the PLMN. According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to send a subscription request message including a PLMN identifier and an NPN identifier to a Unified Data Repository (UDR). According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to receive a subscription response message from the UDR, the subscription response message including charge control information for the NPN. According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the PCF to determine a charging control rule for the NPN of a PDU session based on charging control information, a PLMN identifier, and an NPN identifier, wherein the charging control rule includes one or more of the following: an NPN charging rate; an NPN charging method; and an address of the NPN charging function. According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the PCF to send a second message including the charging control rule to the SMF.

[0331] According to various embodiments, a charging function (CHF) may include one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the CHF to receive a charging data request message from a session management function (SMF) including an identifier for a non-public network (NPN) for a packet data unit (PDU) session. According to various embodiments, the charging function (CHF) may include one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the CHF to determine quota information for the NPN based on the NPN's identifier. According to various embodiments, the charging function (CHF) may include one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the CHF to send a response message including quota information to the SMF.

[0332] According to various embodiments, a charging function (CHF) may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the CHF to receive a charging data request message from a session management function (SMF) including an identifier for a non-public network (NPN) for a packet data unit (PDU) session. According to various embodiments, the charging function (CHF) may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the CHF to determine quota information for the NPN based on the NPN's identifier. The quota information may include one or more of the following: an NPN's authorization unit; an NPN's time quota threshold; and / or an NPN's quantity quota threshold. According to various embodiments, the charging function (CHF) may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the CHF to send a response message including quota information to the SMF.

[0333] According to various embodiments, the Session Management Function (SMF) can receive a message from the Access and Mobility Management Function (AMF) including the Closed Access Group Identifier (CAG ID) of a Packet Data Unit (PDU) session of a radio device. According to various embodiments, the SMF can send a policy request message including the CAG ID to the Policy Control Function (PCF). According to various embodiments, the SMF can receive a policy response message from the PCF including a charging control rule. The charging control rule may include: a charging rate for the CAG ID; and a charging method for the CAG ID. According to various embodiments, based on the policy response message, the SMF can send a charging data request message to the Charging Function (CHF), wherein the charging data request message may include the CAG ID. According to various embodiments, the CAG ID may be applied to at least one of: a radio device; a PDU session; a network slice; and / or a Data Network Name (DNN). According to various embodiments, the policy request message may further include at least one of the following: a radio device identifier for the radio device; a PLMN identifier for the public land mobile network (PLMN) of the radio device; a data network name (DNN); single network slice selection assistance information (S-NSSAI); and / or a PDU session identifier for the PDU session. According to various embodiments, the PCF may send a subscription request message for a CAG ID and a PDU session to the Unified Data Repository (UDR), wherein the subscription request message includes at least one of the following: a radio device identifier for the radio device; a PLMN identifier for the public land mobile network (PLMN) of the radio device; a data network name (DNN); single network slice selection assistance information (S-NSSAI); and / or a PDU session identifier for the PDU session. According to various embodiments, the UDR may determine charge control information applicable to at least one of the following: CAG; radio device; PDU session; S-NSSAI; and / or DNN. According to various embodiments, the PCF may receive a subscription response message from the UDR, which includes at least one of the following: charge control information for the CAG; and / or the CAG ID. According to various embodiments, based on the charging control information of the CAG, the PCF can determine the charging control rules of the CAG, wherein the charging control rules include at least one of the following: the charging rate of the CAG; the charging method of the CAG; and / or the address of the charging function of the CAG. According to various embodiments, the policy response message may also include at least one of the following: the CAG ID; the PDU session identifier of the PDU session; and / or individual network slice selection assistance information (S-NSSAI).

[0334] According to various embodiments, the AMF can receive non-access stratum messages from a radio device, the non-access stratum messages including at least one of the following: Single Network Slice Selection Assistance Information (S-NSSAI); Data Network Name (DNN); and / or PDU Session Identifier of a PDU session. According to various embodiments, the AMF can receive non-access stratum messages from a radio device including a PDU Session Establishment Request message, wherein the PDU Session Establishment Request message includes at least one of the following: CAG ID; and / or PDU Session Identifier of a PDU session. According to various embodiments, a charge data request message may also include at least one of the following: Radio Device Identifier of the radio device; PDU Session Identifier of a PDU session; and / or Single Network Slice Selection Assistance Information (S-NSSAI). According to various embodiments, based on the CAG ID, the CHF can determine first quota information for the CAG, wherein the first quota information may include at least one of the following: CAG ID; Authorization Unit; Time Quota Threshold; and / or Volume Quota Threshold. According to various embodiments, the CHF can send a charge response message including the first quota information to the SMF. According to various embodiments, the SMF can send a user plane message to the UPF including at least one of the following: user plane rules; and / or CAG ID. According to various embodiments, user plane rules can be determined based on at least one of the following: quota information of CAGs received from the CHF; and / or charging control rules of CAGs received from the PCF. According to various embodiments, the UPF can detect and collect resource usage of CAGs, wherein resource usage can include at least one of the following: time usage of CAGs; and / or quantity usage of CAGs. According to various embodiments, the UPF can send the resource usage of CAGs to the SMF. According to various embodiments, the SMF can send a second charging request message including the resource usage of CAGs to the CHF. According to various embodiments, based on resource usage, the CHF can determine second quota information of CAGs. According to various embodiments, the CHF can send a second charging response message including the second quota information to the SMF.

[0335] Figure 24 This is a flowchart illustrating an aspect of an exemplary embodiment according to the present disclosure. At 2410, the Session Management Function (SMF) may send a Policy Request message to the Policy Control Function (PCF) including the Closed Access Group Identifier (CAG ID) of the Packet Data Unit (PDU) session of the radio device. At 2420, the SMF may receive from the PCF a Policy Response message including a charging control policy indicating one or more of the following: a charging rate for the CAG ID; and a charging method for the CAG ID. At 2430, based on the Policy Response message, the SMF may send a Charge Data Request message including the CAG ID to the Charging Function (CHF).

[0336] According to various embodiments, the CAG ID can be used for a Packet Data Unit (PDU) session of a radio device. According to various embodiments, the charging control policy may include charging control rules indicating charging rates and charging methods. According to various embodiments, the SMF can receive a message including the CAG ID from the Access and Mobility Management Function (AMF). According to various embodiments, the policy request message may also include at least one of the following: a radio device identifier for the radio device; a PLMN identifier for the public land mobile network (PLMN) of the radio device; a data network name (DNN); single network slice selection assistance information (S-NSSAI); and / or a PDU session identifier for the PDU session. According to various embodiments, the policy response message may also include at least one of the following: the CAG ID; a PDU session identifier for the PDU session; and / or single network slice selection assistance information (S-NSSAI). According to various embodiments, the SMF may send a user plane message to the UPF including at least one of the following: user plane rules; and / or the CAG ID. According to various embodiments, user plane rules can be determined based on at least one of the following: quota information of CAGs received from the charging function (CHF); and / or charging control rules of CAGs received from the PCF. According to various embodiments, the UPF can detect and collect resource usage of CAGs, wherein resource usage may include at least one of the following: time usage of CAGs; and / or quantity usage of CAGs. According to various embodiments, the UPF can send the resource usage of CAGs to the SMF. According to various embodiments, the SMF can send a second charging request message including the resource usage of CAGs to the CHF.

[0337] According to various embodiments, the Policy Control Function (PCF) can receive a policy request message from the Session Management Function (SMF) including the Closed Access Group Identifier (CAG ID) of a Packet Data Unit (PDU) session of a radio device. According to various embodiments, the PCF can send a subscription request message including the CAG ID to the Unified Data Repository (UDR). According to various embodiments, the PCF can receive a subscription response message from the UDR, which includes: the CAG ID; and charging control information for the CAG ID. According to various embodiments, based on the CAG ID and the charging control information, the PCF can determine the charging control rules for the CAG of the PDU session. The charging control rules may include: the charging rate of the CAG; the charging method of the CAG; and the address of the charging function of the CAG. According to various embodiments, the PCF can send a policy response message including the charging control rules to the SMF. According to various embodiments, the policy request message may further include at least one of the following: a radio device identifier for the radio device; a PLMN identifier for the public land mobile network (PLMN) of the radio device; a data network name (DNN); single network slice selection assistance information (S-NSSAI); and / or a PDU session identifier for the PDU session. According to various embodiments, the subscription request message may include at least one of the following: a radio device identifier for the radio device; a PLMN identifier for the public land mobile network (PLMN) of the radio device; a data network name (DNN); single network slice selection assistance information (S-NSSAI); and / or a PDU session identifier for the PDU session. According to various embodiments, the UDR may determine charge control information applicable to at least one of the following: CAG; radio device; PDU session; S-NSSAI; and / or DNN.

[0338] Figure 25 This is a flowchart illustrating an aspect of an example embodiment according to the present disclosure. At 2510, the Policy Control Function (PCF) can receive a policy request message including a Closed Access Group Identifier (CAG ID) from the Session Management Function (SMF). At 2520, the PCF can send a subscription request message including the CAG ID to the Unified Data Repository (UDR). At 2530, the PCF can receive a subscription response message from the UDR, which includes charge control information for the CAG ID. At 2540, the PCF can determine the charge control rules for the CAG of the PDU session based on the CAG ID and the charge control information. At 2550, the PCF can send a policy response message including the charge control rules to the SMF.

[0339] According to various embodiments, the CAG ID can be used for a Packet Data Unit (PDU) session of a radio device. According to various embodiments, the charging control rules can include a charging rate for the CAG. According to various embodiments, the charging control rules can include a charging method for the CAG. According to various embodiments, the charging control rules can include the address of the charging function of the CAG. According to various embodiments, the charging function (CHF) can receive a charging data request message from the session management function (SMF). The charging data request message can include the Closed Access Group Identifier (CAG ID) of the Packet Data Unit (PDU) session of the radio device. According to various embodiments, based on the CAG ID, the CHF can determine the quota information of the CAG, wherein the quota information can include at least one of the following: the CAG's authorized unit; the CAG's time quota threshold; and / or the CAG's quantity quota threshold. According to various embodiments, the CHF can send a response message including the CAG ID and quota information to the SMF.

[0340] According to various embodiments, a Session Management Function (SMF) may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to receive from an Access and Mobility Management Function (AMF) a message including a Closed Access Group Identifier (CAG ID) for a Packet Data Unit (PDU) session of a radio device. According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to send a policy request message including the CAG ID to a Policy Control Function (PCF). According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to receive from the PCF a policy response message including a charging control policy, wherein the charging control policy may include: a charging rate for the CAG ID; and a charging method for the CAG ID. According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to send a charging data request message to a Charging Function (CHF) based on a policy response message, wherein the charging data request message includes the CAG ID. According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to send a policy request message to a Policy Control Function (PCF), the policy request message including a Closed Access Group Identifier (CAG ID) of a Packet Data Unit (PDU) session of the radio device. According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to receive a policy response message from the PCF including a charging control policy. The charging control policy may indicate one or more of the following: a charging rate for the CAG ID; and / or a charging method for the CAG ID. According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to send a charging data request message including the CAG ID to a Charging Function (CHF) based on the policy response message.

[0341] According to various embodiments, a Policy Control Function (PCF) may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to receive a policy request message from a Session Management Function (SMF) including a Closed Access Group Identifier (CAG ID) for a Packet Data Unit (PDU) session of a radio device. According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to send a subscription request message including the CAG ID to a Unified Data Storehouse (UDR). According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to receive a subscription response message from the UDR, the subscription response message including: the CAG ID; and charge control information for the CAG ID. According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to determine charge control rules for the CAG of a PDU session based on the CAG ID and charge control information. The charge control rules may include: a charge rate for the CAG; a charge method for the CAG; and an address for the charge function of the CAG. According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to send a policy response message to the SMF, including toll control rules.

[0342] According to various embodiments, a Policy Control Function (PCF) may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to receive a policy request message including a Closed Access Group Identifier (CAG ID) from a Session Management Function (SMF). According to various embodiments, a PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to send a subscription request message including a CAG ID to a Unified Data Repository (UDR). According to various embodiments, a PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to receive a subscription response message from a UDR, the subscription response message including charge control information for the CAG ID. According to various embodiments, a PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to determine charge control rules for a PDU session's CAG based on the CAG ID and charge control information. According to various embodiments, a PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to send a policy response message including charge control rules to the SMF.

[0343] According to various embodiments, a charging function (CHF) may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the CHF to receive a charging data request message from a session management function (SMF) including a Closed Access Group Identifier (CAG ID) of a Packet Data Unit (PDU) session of a radio device. According to various embodiments, the CHF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the CHF to determine quota information of a CAG based on the CAG ID, wherein the quota information may include at least one of: the CAG's granting unit; a CAG's time quota threshold; and / or a CAG's quantity quota threshold. According to various embodiments, the CHF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the CHF to send a response message to the SMF including the CAG ID and quota information.

[0344] Figure 26 This is a flowchart illustrating an aspect of an exemplary embodiment according to the present disclosure. At 2610, the Session Management Function (SMF) may receive a first message from the Access and Mobility Management Function (AMF), the first message including: a Closed Access Group Identifier (CAG ID); a Public Land Mobile Network (PLMN) identifier for the radio device; and a Non-Public Network (NPN) identifier through which the radio device accesses the PLMN. At 2620, the SMF may send a policy request message to the Policy Control Function (PCF), the policy request message including: the CAG ID; the PLMN identifier; and the NPN identifier. At 2630, the SMF may receive a policy response message from the PCF including a charging control policy. At 2640, the SMF may send a charging data request message to the Charging Function (CHF) based on the policy response message. The charging data request message may include the CAG ID; the PLMN identifier; and / or the NPN identifier.

[0345] According to various embodiments, the charging control policy may be determined based on at least one of the following: CAG ID; PLMN identifier; and / or NPN identifier. According to various embodiments, the first message may also include at least one of the following: radio device identifier; data network name (DNN); single network slice selection assistance information (S-NSSAI); and / or packet data unit (PDU) session identifier (ID). According to various embodiments, the first message may also include a PDU session establishment request message, wherein the PDU session establishment request message may include at least one of the following: CAG ID; PLMN identifier; NPN identifier; and / or packet data unit (PDU) session identifier. According to various embodiments, the CAG ID and / or NPN identifier may be applied to at least one of the following: radio device; PDU session identified by the PDU session identifier; network slice identified by S-NSSAI; and / or DNN. According to various embodiments, the policy request message may also include at least one of the following: radio device identification; data network name (DNN); single network slice selection assistance information (S-NSSAI); and / or packet data unit (PDU) session identifier. According to various embodiments, the PCF can send an NPN subscription request message, a Closed Access Group Identifier (CAG ID), or a Packet Data Unit (PDU) session to the Unified Data Store (UDR), wherein the subscription request message may include at least one of the following: CAG ID; NPN identifier; PLMN identifier; Radio Device Identifier; PDU session identifier; and / or Single Network Slice Selection Auxiliary Information (S-NSSAI). According to various embodiments, the UDR can determine charge control information applicable to at least one of the following: CAG; NPN; Radio Device; PDU session; S-NSSAI; and / or DNN. According to various embodiments, the PCF can receive a subscription response message from the UDR, which includes at least one of the following: charge control information for the NPN; charge control information for the CAG; CAG ID; and / or the NPN identifier. According to various embodiments, based on the NPN charge control information, the PCF can determine the NPN charge control rules, wherein the charge control rules may include at least one of the following: NPN charge rate; NPN charge method; and / or the address of the NPN charge function. According to various embodiments, based on the charge control information for the CAG, the PCF can determine the charge control rules for the CAG, wherein the charge control rules may include at least one of the following: the charge rate of the CAG; the charge method of the CAG; and / or the address of the charge function of the CAG.According to various embodiments, the PCF can send a policy response message to the SMF, the policy response message including at least one of the following: NPN charging control rules; CAG charging control rules; NPN identifier; CAG identifier; PDU session identifier; and / or S-NSSAI. According to various embodiments, the AMF can receive non-access stratum messages from the radio device, the non-access stratum messages including at least one of the following: S-NSSAI; DNN; and / or PDU session identifier. According to various embodiments, the AMF can receive non-access stratum messages from the radio device including a PDU session establishment request message, wherein the PDU session establishment request message may include at least one of the following: NPN identifier; CAG ID; and / or PDU session identifier. According to various embodiments, the charging data request message may also include at least one of the following: radio device identifier; PDU session identifier; and / or single network slice selection assistance information (S-NSSAI). According to various embodiments, based on the CAG ID, the CHF can determine first quota information of the CAG, wherein the first quota information may include at least one of the following: CAG ID; authorization unit; time quota threshold; and / or quantity quota threshold. According to various embodiments, based on the NPN identifier, the CHF can determine first quota information of the NPN, wherein the first quota information may include at least one of the following: NPN identifier; authorization unit; time quota threshold; and / or quantity quota threshold. According to various embodiments, the CHF can send a charge response message including the first quota information to the SMF. According to various embodiments, the SMF can send a user plane message to the UPF, the user plane message including at least one of the following: user plane rule; NPN identifier; and / or CAG ID. According to various embodiments, the UPF can detect and collect resource usage of the NPN or CAG, wherein resource usage may include at least one of the following: time usage of the NPN; quantity usage of the NPN; time usage of the CAG; and / or quantity usage of the CAG. According to various embodiments, the UPF can send the resource usage of the NPN or CAG to the SMF. According to various embodiments, the SMF may send a second charge request message to the CHF, including NPN or CAG, for resource usage.

[0346] According to various embodiments, a Session Management Function (SMF) may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to receive a first message from an Access and Mobility Management Function (AMF). The first message includes: a Closed Access Group Identifier (CAG ID); a Public Land Mobile Network (PLMN) identifier for the radio device; and a Non-Public Network (NPN) identifier, through which the radio device accesses the PLMN. According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to send a policy request message to a Policy Control Function (PCF). This policy request message includes: a CAG ID; a PLMN identifier; and an NPN identifier. According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to receive a policy response message from the PCF, including a charging control policy. According to various embodiments, the SMF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the SMF to send a charging data request message to the charging function (CHF) based on a policy response message, wherein the charging data request message may include: a CAG ID; a PLMN identifier; and an NPN identifier.

[0347] According to various embodiments, the Policy Control Function (PCF) can receive provisional service information messages from the Application Function (AF), which may include: an identifier of a Non-Public Network (NPN); an identifier of a Service Provider Public Land Mobile Network (SP PLMN); an identifier of a radio device; service information for the radio device; a UE IP address; and / or a Data Network Adapter (DNN). According to various embodiments, the PCF can map the SP PLMN identifier and service information to Packet Data Unit (PDU) sessions based on: the NPN identifier; the radio device identifier; the UE IP address; and / or the DNN. According to various embodiments, the PCF can determine charging control rules for the NPN and SP PLMN, wherein the charging control rules may include: charging rates for the NPN and SP PLMN; charging methods for the NPN and SP PLMN; and / or addresses of charging functions for the NPN and SP PLMN. According to various embodiments, the PCF can send the charging control rules to the Service Management Function (SMF).

[0348] According to various embodiments, a policy control function (PCF) may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to receive a provisional service information message from an application function (AF). This provisional service information message includes: an identifier of a non-public network (NPN); an identifier of a service provider public land mobile network identifier (SP PLMN); an identifier of a radio device; service information for the radio device; a UE IP address; and / or a data management network (DNN). According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to map the SP PLMN identifier and service information to a packet data unit (PDU) session based on: the NPN identifier; the radio device identifier; the UE IP address; and the DNN. According to various embodiments, a policy control function (PCF) may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to determine charging control rules for the NPN and SP PLMN, wherein the charging control rules may include: charging rates for the NPN and SP PLMN; charging methods for the NPN and SP PLMN; and / or addresses of charging functions for the NPN and SP PLMN. According to various embodiments, the policy control function (PCF) may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to send the charging control rules to the SMF.

[0349] According to various embodiments, the Policy Control Function (PCF) can receive provisional service information messages from the Application Function (AF), which may include: a Closed Access Group (CAG) ID; an identifier of the Service Provider Public Land Mobile Network (SP PLMN); an identifier of the radio device; service information for the radio device; a UE IP address; and / or a Data Network Name (DNN). According to various embodiments, the PCF can map the SP PLMN identifier and service information to a Packet Data Unit (PDU) session based on: the CAG ID; the radio device identifier; the UE IP address; and / or the DNN. According to various embodiments, the PCF can determine charging control rules for the CAG and SP PLMN, wherein the charging control rules may include: charging rates for the CAG and SP PLMN; charging methods for the CAG and SP PLMN; and / or addresses of charging functions for the CAG and SP PLMN. According to various embodiments, the PCF can send the charging control rules to the Service Management Function (SMF).

[0350] According to various embodiments, a Policy Control Function (PCF) may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to receive a provisional service information message from an Application Function (AF). This provisional service information message may include: a Closed Access Group (CAG) ID; an identifier of the Service Provider Public Land Mobile Network (SP PLMN); an identifier of the radio device; service information for the radio device; a UE IP address; and / or a Data Network Adapter (DNN). According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to map the SP PLMN identifier and service information to a Packet Data Unit (PDU) session based on: the CAG ID; the radio device identifier; the UE IP address; and / or the DNN. According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to determine charging control rules for the CAG and SP PLMN, wherein the charging control rules may include: charging rates for the CAG and SP PLMN; charging methods for the CAG and SP PLMN; and / or addresses of charging functions for the CAG and SP PLMN. According to various embodiments, the PCF may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the PCF to send toll control rules to the SMF.

[0351] In this specification, “a” (“a” and “an”) and similar phrases will be interpreted as “at least one” and “one or more”. In this specification, the term “may” is interpreted 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 variety of suitable possibilities that may or may not be used in one or more of various examples. If A and B are sets, and every element in A is an element of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}.

[0352] Various examples are disclosed in this specification. Limitations, features, and / or elements from the disclosed example embodiments may be combined to create further examples within the scope of this disclosure.

[0353] Various examples are disclosed in this specification. Limitations, features, and / or elements from the disclosed example embodiments may be combined to create further examples within the scope of this disclosure.

[0354] In this specification, a parameter (information element: IE) may include one or more objects, and one of these objects may include one or more other objects. For example, if parameter (IE)N includes parameter (IE)M, and parameter (IE)M includes parameter (IE)K, and parameter (IE)K includes parameter (information element)J, then, for example, N includes K, and N includes J. In the example, 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 one of the one or more messages.

[0355] Many of the elements described in the disclosed examples can be implemented as modules. A module is defined herein as a separable element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure can be implemented in hardware, software combined with hardware, firmware, wet hardware (i.e., hardware with biological elements), or combinations thereof, some of which are behaviorally equivalent. For example, a module can be implemented as software routines written in a computer language configured to be executed by a hardware machine (e.g., C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (e.g., Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). Alternatively, 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, application-specific integrated circuits (ASICs); field-programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, and C++. 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 relatively few internal hardware modules on a programmable device. Finally, it is important to emphasize that the above techniques are often used in combination to achieve the result of functional modules.

[0356] The disclosure of this patent document incorporates copyrighted material. The copyright holder does not object to anyone making an exact copy of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office's patent documents or records for limited purposes required by law, but otherwise reserves all copyright rights.

[0357] Although various examples have been described above, it should be understood that they are presented by way of example rather than limitation. It will be apparent to those skilled in the art that various changes in form and detail may be made without departing from the spirit and scope of this disclosure. Indeed, after reading the above description, it will be apparent to those skilled in the art how to implement alternative examples. Therefore, the present examples should not be limited to any of the exemplary examples described above. In particular, it should be noted that for illustrative purposes, the above explanation has focused on examples using 5G AN. However, those skilled in the art will recognize that examples of the invention can be implemented in systems including one or more legacy systems or LTE. The disclosed methods and systems can be implemented in wireless or wired systems. Features of the various examples presented in this invention can be combined. One or more features (methods or systems) of one example can be implemented in other examples. A limited number of example combinations are shown to indicate to those skilled in the art the possibility of combining features from various examples to create enhanced transmission and reception systems and methods.

[0358] Furthermore, it should be understood that any diagrams highlighting features and benefits are presented 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, the actions listed in any flowchart can be reordered or used only optionally in certain examples.

[0359] Furthermore, the purpose of this abstract is to enable the U.S. Patent and Trademark Office and the general public, especially scientists, engineers, and practitioners unfamiliar with patent or legal terminology, to quickly determine the nature and substance of the technical disclosure of this application through a cursory examination. This abstract is not intended to limit the scope in any way.

[0360] Finally, the applicant's intention is that only claims containing the explicit language "apparatus for..." or "steps for..." should be interpreted according to 35 U.SC 112. Claims that do not explicitly contain the phrases "apparatus for..." or "steps for..." should not be interpreted according to 35 U.SC 112.

Claims

1. A Session Management Function (SMF) comprising one or more processors and a memory storing instructions, the instructions causing the SMF to: Send a policy request message to the Policy Control Function (PCF), the policy request message including: The NPN identifier of a non-public network NPN, through which a wireless device accesses a public terrestrial mobile network (PLMN); and The PLMN identifier of the PLMN; as well as The SMF receives a policy response message, including the charging control policy, from the PCF.

2. The SMF of claim 1, wherein the instructions further cause the SMF to receive a first message from the Access and Mobility Management Function (AMF) including one or more of the NPN identifier and the PLMN identifier.

3. The SMF of claim 2, wherein the first message comprises at least one of the following: Data network name: DNN; Single network slice selection auxiliary information S-NSSAI; and Packet Data Unit (PDU) Session Identifier.

4. The SMF of claim 2, wherein sending the policy request message is based on receiving the first message from the AMF.

5. The SMF according to claim 1, wherein the instruction further causes the SMF to send a charging data request message to the charging function based on the policy response message.

6. The SMF of claim 5, wherein the charging data request message includes the PLMN identifier.

7. The SMF of claim 1, wherein the policy request message further comprises at least one of the following: The wireless device identifier of the wireless device; Data network name: DNN; Select auxiliary information for a single network slice; or Grouped Data Unit Session Identifier.

8. The SMF of claim 1, wherein the policy response message includes at least one of the following: Fee control rules; The NPN identifier; Single network slice selection auxiliary information S-NSSAI; and Packet Data Unit (PDU) Session Identifier.

9. The SMF of claim 1, wherein the instructions further cause the SMF to determine one or more user plane rules for the NPN based on the charging control policy.

10. The SMF of claim 9, further comprising sending one or more user plane rules for the NPN to the User Plane Function (UPF).

11. A policy control function (PCF) comprising one or more processors and a memory storing instructions, the instructions causing the PCF to: Receive a policy request message from the Session Management Function (SMF), the policy request message including: The NPN identifier of a non-public network NPN, through which a wireless device accesses a public terrestrial mobile network (PLMN); and The PLMN identifier of the PLMN; as well as The PCF sends a policy response message, which includes the charging control policy, to the SMF.

12. The PCF of claim 11, wherein the instructions further cause the PCF to determine the toll control strategy.

13. The PCF of claim 12, wherein the determination of the charging control policy is based on the NPN identifier.

14. The PCF of claim 12, wherein the determination of the toll control strategy is based on the PLMN identifier.

15. The PCF of claim 12, wherein the instruction further causes the PCF to send a subscription request message to the Unified Data Repository (UDR), the subscription request message including the PLMN identifier and the NPN identifier.

16. The PCF of claim 15, wherein the instruction further causes the PCF to receive charge control information for the NPN from the UDR.

17. The PCF of claim 16, wherein the instructions further cause the PCF to determine, from the UDR, the charge control information for the NPN to determine the charge control rules for the NPN.

18. The PCF of claim 16, wherein the determination of the charge control policy is based on charge control information for the NPN received from the UDR.

19. The PCF of claim 11, wherein the policy request message further comprises at least one of the following: The wireless device identifier of the wireless device; Data network name; Select auxiliary information for a single network slice; or Grouped Data Unit Session Identifier.

20. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to: Send a policy request message to the Policy Control Function (PCF), the policy request message including: The NPN identifier of a non-public network NPN, through which a wireless device accesses a public terrestrial mobile network (PLMN); and The PLMN identifier of the PLMN; and Receive a policy response message from the PCF, which includes the charging control policy.

Images