Authentication and authorization for localized services

Abstract

The present disclosure provides techniques and skills related to enabling access to localized services. The present disclosure provides mechanisms for authenticating and authorizing for causing a non-public network (NPN) to act as a hosted network for providing access to localized services. In addition, the present disclosure provides mechanisms for enabling a user equipment (UE) to discover, select, and access an NPN acting as a hosted network to receive localized services. In addition, the present disclosure provides mechanisms for enabling access to localized services via a particular hosted network.

Description

[0001] Related Applications

[0002] This application claims priority to U.S. Provisional Application No. 63 / 339,238 filed on May 6, 2022 and U.S. Provisional Application No. 63 / 353,412 filed on June 17, 2022, the contents of each of which are incorporated herein by reference in their entirety. Technical Field

[0003] The present disclosure generally relates to wireless communication technologies, network topologies, network and information security technologies, and more particularly, to technologies and techniques related to accessing localized services. Background Art

[0004] As part of the 3rd Generation Partnership Project (3GPP) Release 18 (Rel-18) enhanced non-public network (eNPN) study, access to localized services is studied. Providing local services refers to providing access to a hosted network and a set of services provided by the hosted network provider and third-party service providers (including other network operators and third-party application providers). Services can be localized (e.g., provided at a specific and / or limited area and bounded in time). Users can become aware of the available access to local services and the processes for obtaining and terminating access to the hosted network and local services. From a user experience perspective, the process should be efficient and convenient.

[0005] The fifth generation (5G) network may act as a hosted network providing access to localized services, either as a public network integrated non-public network (PNI-NPN) or a standalone non-public network (SNPN). Different entities may operate the hosted network and the localized services. The localized services may provide not only data connectivity to the end user, but also additional information / motivation / instructions, for example, for seeking access to the localized services. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The embodiments will be easily understood by the following detailed description in conjunction with the accompanying drawings. For the convenience of this description, the same reference numerals represent the same structural elements. The embodiments are shown in the figures of the accompanying drawings by way of example and not by way of limitation, wherein:

[0007] Figure 1 Describes an example solution for accessing localized services based on AKMA; Figure 2 Describes an example process for accessing localization services based on AKMA; Figure 3 depicts an example solution for digital certificate-based access to localized services; Figure 4 depicts an example process for accessing localization services based on digital certificates; Figure 5depicts an example process for providing access to local services; Figure 6 depicts an example over-the-top (OTT) solution for accessing localized services; Figure 7 Depicts an example OTT-related process for accessing localized services; Figure 8 a. Figure 8b , Fig. 9 depicts an example wireless network; Fig.10 depicts example hardware resources; and Fig.11 , Fig.12 and 13 Depicted are example procedures for practicing the various embodiments discussed herein. DETAILED DESCRIPTION

[0008] 1. Localization services

[0009] Localized services are services that are provided at a specific / limited area and / or may be bounded in time. Services may be implemented via applications (e.g., live or on-demand audio / video streaming, electronic games, IMS, etc.) or connections (e.g., UE to UE, UE to data network, etc.). Localized service providers (LSPs) (e.g., Figure 1 LSP 150 in is to localize its services and provide them via a managed network (e.g. Figure 1 The hosted network 130 in the TS 23501 is provided to an application provider or network operator for an end user (e.g., UE 802). The hosted network 130 may be a non-public network (NPN) (e.g., a stand-alone NPN (SNPN)) or a public network integration (PNI)-NPN. Support for NPN is described by clause 5.30 of [TS 23501].

[0010] 1.1. Authentication and authorization for localization services

[0011] 3GPP TR 23.700-08 ("[TS23700-08]") discusses issues related to authentication and authorization aspects of enabling an NPN to act as a hosted network 130 for providing access to localized services 155 (see, e.g., clause 5.3 in [TS23700-08]), enabling a UE to discover, select and access an NPN as a hosted network 130 and receive localized services 155 (see, e.g., clause 5.4 in [TS23700-08]), and enabling access to localized services 155 via a specific hosted network 130 (see, e.g., clause 5.5 in [TS23700-08]).

[0012] [TS23700-08] is studying capabilities for providing access to a hosted network 130 and a set of services provided by a hosted network provider and third-party service providers (including other network operators and third-party application providers). Access to local services 155 by implementing an NPN as a hosted NPN or a hosted network 130 is being studied, including architectural enhancements for discovering, selecting and accessing an NPN as a hosted network 130 and receiving localized services 155, service availability of the hosted network 130, seamless service continuity for home network services and localized services 155, UE identification, configuration for such services, network selection, authentication and authorization procedures for UE 802 and localized services 155.

[0013] Unauthorized access of UE 802 to hosted network 130 may cause the resources of hosted network 130 to be abused or overloaded. Weak authentication procedures may allow attackers / hackers to impersonate UE 802 to hosted network 130, or vice versa, and thereby gain unauthorized access to hosted network 130, resulting in data leakage.

[0014] In order to access localized services 155, UE 802 needs to be authorized and authenticated to these services. Ways by which UE 802 can authenticate with hosted network 130 and utilize localized services 155 are currently being investigated. This disclosure contemplates processes for obtaining credentials to access localized services 155.

[0015] The UE 802 should be authorized to access the localized services 155. In various implementations, the UE 802 and the hosted network 130 mutually authenticate before granting access to the localized services 155. The 5GS supports a process that allows the UE 802 to access the hosted network 130 to securely utilize the localized services 155.

[0016] 1.1.1. Option 1: Accessing localized services based on AKMA

[0017] The present disclosure addresses authentication and authorization aspects of implementing an NPN as a hosted network 130 for providing UEs 802 with access to localized services 155 .

[0018] Figure 1 An example of authentication between a UE 802 and a hosted network 130 for accessing a localized service 155 using Application Authentication and Key Management (AKMA) as defined in [TS35535] is depicted. The solution uses an AKMA anchor key (K) derived from the AKMA process after a one-time authentication with the UE 802 and the home network 120. AKMA ) as a root of trust to perform authentication between UE 802 and hosted network 130. AKMA A time-limited credential for authentication with the hosted network 130 is generated or otherwise included.

[0019] When UE 802 arrives at a venue (e.g., a stadium) where localized services are provided, the user manually selects the hosted network 130. UE 802 connects to the hosted network 130 and is authenticated by LSP 150 (e.g., using an authentication, authorization, and accounting (AAA) server) in the role of a credential holder (CH) 160 based on a user ID and security credentials for accessing the home network 120. UE 802 requests a PDU session to the provided DNN / S-NSSAI, and accesses the localized services of LSP 150 via the hosted network 130 based on the user ID and security credentials for accessing the LSP 150 server providing the localized services 155.

[0020] The home network 120 pushes time-limited credentials (e.g., one-time credentials, etc.) to the LSP 150 that provides this service. The time-limited credentials include, for example, the following: the SNPN ID and geographic coordinates of the hosted network 130; the user id and security credentials for accessing the home network 120; the user id and AKMA-based security credentials for accessing the LSP 150 server that provides localized services; and the DNN / S-NSSAI for establishing a PDU session in the hosted network 130, optionally with AKMA-based credentials for secondary authentication.

[0021] Figure 2 An example process for accessing localization service 155 based on AKMA is shown. Figure 2 The process can be operated as follows:

[0022] H1. LSP 150 establishes a service agreement with the operator of hosted network 130. LSP 150 also establishes a service agreement with the operator of home network 120 of UE 802 to enable UE 802 to receive the information required to discover / access hosted network 130 and localized services 155.

[0023] H2. The hosted network 130 is configured based on the service agreement (e.g., DNN / S-NSSAI configuration for accessing localized services 155, quality of service (QoS), number of end users, time, location, whether home network services can be accessed via the hosted network 130, etc.). Configuration of the hosted network 130 is performed. UE 802 performs the procedures defined in [TS23502] to obtain 5GC network access. At the end of the network access authentication process (one-time authentication and key agreement in 3GPP TS 33.501 clause 6.1), UE 802 and AUSF have the key K AUSF .

[0024] H3.UE 802 and AUSF derive AKMA keys (e.g., K AKMA), as specified in [TS35535]. AUSF 842 provides the AKMA key (e.g., K AKMA ), as specified in [TS35535].

[0025] H4. Localized service announcement prompts the user of UE 802. UE 802 initiates the application request service procedure with LSP 150 and includes the AKMA key ID (A-KID) in the application service request message. LSP 150 acts as an application function (AF) for AAnF 862 as specified in [TS35535]. If LSP 150 does not store a valid KID for UE 802, LSP , or the AKMA key ID provided by UE 802 is different from the previous AKMA key ID, then LSP 150 contacts AAnF 862 (e.g., using AKMA key ID / A-KID) to obtain the corresponding key K of UE 802. LSP (K AF ). AAnF 862 provides the derived key (K AF ). LSP is the AKMA application key (K AF ) and is derived by both UE 802 and LSP 150 as specified in [TS35535].

[0026] H5.LSP 150 uses key K LSP To derive the key K LSP -PSK.K LSP -PSK is derived and used as a pre-shared key (PSK) to establish transport layer security (TLS) between UE 802 and LSP 150. LSP -PSK, LSP 150 includes in the application service response message the information used to derive K to UE 802 LSP Upon receiving the Application Service Response message, UE 802 uses the received CounterLSP value to derive the K derived by AUSF. LSP -PSK.K LSP -PSK acts as a time-limited credential following the [TS35535] AKMA key lifecycle procedures.

[0027] H6. When UE 802 arrives at a venue (eg, a stadium) that provides localized service 155 , the user manually selects a hosted network 130 .

[0028] H7.UE 802 connects to the hosted network 130 and is authenticated by the LSP 150 (e.g., using an AAA server) in the role of a credential holder using the credentials obtained in step H5. For example, UE 802 establishes an Extensible Authentication Protocol (EAP)-TLS session with the LSP 150 to authenticate with the hosted network 130. Based on a pre-shared key (PSK) (e.g., K ) following TLS 1.2 (see, e.g., Eronen et al., Pre-shared Key Ciphersuites for Transport Layer Security (TLS), Internet Engineering Task Force (IETF), Request for Comments (RFC) 4279 (December 2005)) and / or TLS 1.3 (see, e.g., Rescorla, The Transport Layer Security (TLS) Protocol Version 1.3, IETF RFC 8446 (August 2018) and / or Housley et al., Guidance for External Pre-Shared Key (PSK) Usage in TLS, IETF RFC 9257 (July 2022)). LSP -PSK), mutual authentication is performed between UE 802 and LSP 150 using TLS.

[0029] H8. UE 802 requests a PDU session and accesses the localized services 155 of LSP 150 via the hosted network 130. In parallel, UE 802 can access the services of home network 120 using an OTT (e.g., Nwu interface) connection to N3IWF node 865 in home network 120.

[0030] H9. When the time-limited credential expires, the LSP 150, which plays the role of the credential holder, releases the UE 802 in accordance with [TS35535] AKMA request.

[0031] H10. When the localized service agreement is terminated, the hosting network 130 removes the configured information (configured in step H2).

[0032] 1.1.2. Option 2: Accessing localization services based on digital certificates

[0033] Figure 3 An example solution for accessing localization services 155 based on digital certificates is depicted. Figure 3In the solution shown, UE 802 includes a Subscriber Identity Module (SIM) or a Universal Integrated Circuit Card (UICC) with an LSP security applet. The SIM with the LSP security applet plays the role of a 'Root of Trust' as described in the Common Implementation Guide to Using the SIM as a 'Root of Trust' to Secure IoT Applications, GSMA TM , a SIM for IoT secure applet as defined in clause 3 of official document IoT.04, version 1.0 (December 3, 2019) ("[GSMAIoT.04]"). In addition, LSP 150 includes LSP server middleware. The role played by LSP server middleware is the IoT server middleware described in clause 3 of [GSMAIoT.04].

[0034] exist Figure 3 In the example of FIG. 8 , in step 1, UE 802 connects to LSP 150 whose role is IoT server middleware. In step 2, UE 802 connects to hosted network 130, and in step 2a, UE 802 is authenticated by LSP 150 whose role is CH 160. In step 3, UE 802 accesses localization service 155 via hosted network 130.

[0035] Figure 4 An example process for accessing localization service 155 based on a digital certificate is shown.

[0036] Figure 4 The process can be operated as follows:

[0037] H1. LSP 150 establishes a service agreement with the operator of hosted network 130. LSP 150 also establishes a service agreement with the operator of UE 802 to enable UE 802 to receive the information required to discover / access hosted network 130 and localized services 155.

[0038] H2. The hosted network 130 is configured based on the service agreement (e.g., DNN / S-NSSAI configuration for accessing localized services, QoS, number of end users, time, location, whether home network services can be accessed via the hosted network 130, etc.). Configuration of the hosted network 130 is performed. UE 802 performs the process defined in [TS23502] to obtain 5GC network access.

[0039] H3. Localized service announcement prompts the user of UE 802.

[0040] H4. The user of UE 802 connects to LSP 150, which plays the role of IoT server middleware described in clause 3 of [GSMAIoT.04]. The connection can be established via the home network 120 of UE 802 or via any other type of network or Internet access. UE 802 sends a service provisioning request to LSP 150 to trigger client certificate provisioning. The requested client certificate will be used to perform mutual authentication between UE 802 and managed network 130 through LSP 150. LSP 150 sends the SIM applet certificate and security profile corresponding to LSP 150 to UE802. The security profile associated with SIM contains all necessary data for establishing a TLS tunnel between LSP 150 and UE 802. LSP security service checks whether LSP related data has been downloaded to the SIM with LSP security applet, checks the validity of the client certificate, and determines whether it is necessary to download LSP related data to the SIM with LSM security applet. The LSM security service responds to the LSP 150, indicating whether the LSP related data must be downloaded to the SIM. The SIM with the LSM security applet sends an "Open channel" command. The KSMO security service downloads the client certificate (so that a TLS tunnel can be established between the UE 802 and the LSP 150) and (optionally) the LSP certificate or root certificate to the SIM with the LSM security applet.

[0041] LSP 150 sends the security profile and LSP certificate corresponding to UE 802 to LSP security service. The security profile associated with the SIM contains all necessary data for establishing a TLS tunnel between LSP 150 and UE 802.

[0042] The LSP security service checks whether the LSP related data has been downloaded to the SIM with the LSP security applet, checks the client certificate validity, and determines whether the LSP related data must be downloaded to the SIM with the edge security applet.

[0043] H5. When the UE 802 arrives at a venue (eg, a stadium) that provides localized services, the user performs a manual selection of a hosted network 130 .

[0044] H6. UE 802 connects to hosted network 130 and is authenticated by LSP 150 in the role of credential holder (eg, using AAA server) using the credentials downloaded in H4.

[0045] H7. UE 802 requests a PDU session and accesses the localized services of LSP 150 via hosted network 130. In parallel, UE 802 can access the services of home network 120 using an OTT (e.g., Nwu reference point) connection to N3IWF node 865 in home network 120.

[0046] H8. When the time-limited credential expires, the LSP 150 in the role of the credential holder requests to release the UE 802.

[0047] H10. When the localized service agreement is terminated, the hosting network 130 removes the configured information (configured in step H2).

[0048] 1.2. Over-the-top (OTT) solutions for accessing localized services

[0049] Figure 5 An example process for implementing localized services is shown. A hosted non-public network (NPN) 130 can provide access to localized services 155. However, the home network operator of UE 802 can also utilize the hosted network 130 based on the relationship established between the hosted network operator and the home operator of UE 802, so that UE 802 can access home network services via the hosted network 130 in addition to localized services 155 from the home network subscription. The home network guides its UE 802 to the hosted network 130 taking into account the location, time, coverage of the hosted network 130, and services provided by the home network and the hosted network 130. A localized service agreement is established. When UE 802 is connected to the hosted network 130 and the requested service is available from both the hosted and home networks, the home network operator indicates to the UE 802 which services are preferred to be used from the home network. Based on the localized service agreement, the hosted network 130 provides the required connection and QoS for UE 802 that is simultaneously connected to the hosted network 130 (for localized services 155) and its home network (for home network services). The UE 802 connects to its home network via the hosted network 130 if supported by the hosted network 130 and the home network based on a localized service agreement.

[0050] The OTT solution discussed herein addresses issues related to enabling UE 802 to discover, select and access an NPN as a hosted network 130 and receive localized services 155 (see, e.g., clause 5.4 in [TS23700-08]) and issues related to enabling access to localized services 155 via a specific hosted network 130 (see, e.g., clause 5.5 in [TS23700-08]). In various implementations, UE 802 (user) obtains a time-limited credential from an LSP via a home network and uses this information to select a hosted network and access localized services. The N3IWF node is used to access home network services.

[0051] This solution has no specification impact from the SA WG2 perspective unless identified by SA WG3.

[0052] Figure 6 An example relationship between LSP 150, hosted network 130, and home network 120 of UE 802 is shown. Figure 6 The relationships shown include the following aspects or features.

[0053] LSP 150 has service agreements with home network 120 and hosted network 130 of UE 802. There is no direct agreement between home network 120 and hosted network 130 of UE 802.

[0054] At step 1 , a user of UE 802 connects to the home network operator's web portal 125 to request information for accessing localized services 155 .

[0055] In step 2, LSP 150 issues a time-limited credential for accessing hosted network 130 and localized service 155. Home network 120 obtains the time-limited credential from LSP 150 providing localized service 155. Examples of time-limited credentials include one or more of the following: SNPN ID and geographic coordinates of hosted network 130; user id and security credentials for accessing home network 120; user id and security credentials for accessing LSP 150 server providing localized service 155; and Data Network Name (DNN) / Single Network Slice Selection Assistance Information (S-NSSAI) for establishing a PDU session in hosted network 130, optionally with credentials for secondary authentication; time-based one-time password (TOTP); and / or out-of-band (OOB) one-time password (OTP). The specific type of time-limited credential used may be implementation specific.

[0056] In step 3, the home network 120 (e.g., using a short message service (SMS) message, TOTP, OOB OTP, a third-party authenticator application, etc.) pushes the time-limited credentials to the UE 802. When the UE 802 arrives at a venue (e.g., a stadium) where localized services are provided, the user performs a manual selection of the hosted network 130. The UE 802 connects to the hosted network 130 and is authenticated by the LSP 150 (e.g., using an AAA server) in the role of the CH 160 based on the user id and security credentials for accessing the home network 120.

[0057] In step 4, UE 802 is connected to the hosted network 130, and in step 4a, UE 802 is authenticated by the LSP whose role is CH 155. In step 5, UE 802 accesses the localized service 155 via the hosted network 130. UE 802 requests a PDU session to the provided DNN / S-NSSAI, and accesses the localized service of LSP 150 via the hosted network 130 based on the user id and security (time-limited) credentials for accessing the LSP server 150 providing the localized service 155. In parallel, in step 5a, UE 802 can access the services of the home network 120 using an OTT (NWu) connection to the N3IWF node 865 in the home network 120.

[0058] Figure 7 An example process for accessing a localization service is shown, which may operate as follows:

[0059] H1. LSP 150 establishes a service agreement with the operator of hosted network 130. LSP 150 also establishes a service agreement with the home network operator of UE 802 to enable UE 802 to receive the information required to discover / access hosted network 130 and localized services.

[0060] H2. The hosted network 130 is configured based on the service agreement (e.g., DNN / S-NSSAI configuration for accessing localized services, QoS, number of end users, time, location, whether home network services can be accessed via the hosted network 130, etc.) The configuration of the hosted network 130 is performed by means outside the scope of 3GPP.

[0061] H3. Localized Service Announcement Prompts the User of UE 802 and / or the user of UE 802 is prompted by a localized service announcement.

[0062] H4. The user of UE 802 connects to the web portal of the home network operator to request information for accessing localized services. The home network 120 obtains a time-limited credential from the LSP 150 that provides the service. The time-limited credential was described above. The home network 120 pushes the time-limited credential to the UE 802 (e.g., using SMS, via a web portal, a third-party authenticator application, etc.). The solution assumes that the LSP has a service agreement with the home network 120 (see, e.g., Figure 5 If UE 802 has a direct service relationship with LSP 150, home network 120 may be bypassed.

[0063] H5. When the UE 802 arrives at a venue that provides localized services (eg, a stadium, a corporate / organization campus, etc.), the user / UE 802 manually selects the hosted network 130 .

[0064] H6. UE 802 connects to hosted network 130 and is authenticated by LSP 150 in the role of CH 160 (eg, using an AAA server).

[0065] H7. UE 802 requests a PDU session and accesses the localized services of LSP 150 via hosted network 130. In parallel, UE 802 can access the services of home network 120 using an OTT (NWu) connection to the N3IWF node in home network 120.

[0066] H8. When the time-limited credential expires, the LSP 150 in the role of the credential holder requests to release the UE 802.

[0067] H9. LSP 150 collects and provides charging information to the home network 120 operator of UE 802 outside of 3GPP specifications.

[0068] H10. When the localized service agreement is terminated, the hosting network 130 removes the configured information (configured in step H2) by means outside the scope of 3GPP.

[0069] 1.3. Access to Localization Services

[0070] In addition to the previously discussed embodiments, the various embodiments discussed herein may include the following aspects.

[0071] 1.3.1. Providing access to local services

[0072] Providing access to local services 155 refers to the ability to provide access to a set of services provided by the hosted network 130 and by the hosted network provider and third-party service providers (including other network operators and third-party application providers). Services 155 may be localized (e.g., provided at a specific / limited area) and may be bounded in time. Users may become aware of available access to local services 155 and the process for obtaining and terminating access to the hosted network 130 and local services 155. From a user experience perspective, the process should be efficient and convenient.

[0073] Providing access to local services 155 creates new opportunities for users and service providers. For example, access can be provided in areas where coverage provided by other networks does not exist (e.g., in an established open-air market far from other infrastructure), or access and local services can be established on an as-needed basis (e.g., on a short-term basis) without requiring long-term business relationships, permanently installed equipment, etc.

[0074] The types of local services 155 and access to localized services 155 via the hosted network 130 may be prompted and arranged through different channels. In principle, the service provider 150 (e.g., traditional businesses, entertainment venues, building contractors, emergency agencies, businesses, etc.) will provide information and appropriate incentives or instructions to potential users so that they will seek access to localized services 155 via the hosted network 130.

[0075] Both the home network 120 and the hosted network 130 may be PLMNs or NPNs. In some examples, only subscribers of public networks may roam into PLMNs. An example of an interworking scenario between a network operator and an application provider for localized services is indicated in Annex H of [TS22261].

[0076] 1.3.1.1. Configuration of localized services in the hosting network

[0077] The 5G system (5GS) supports suitable mechanisms for allowing automatic establishment of localized service agreements for specific occasions (e.g., time and location) and establishing temporary relationships between the hosting network operator and other service providers (including network operators or third-party application providers). The term "localized service provider" also includes third-party service providers.

[0078] 5GS supports a means for service providers to request, via a standard mechanism, that the managed network 130 provide access to third-party services at specific time periods and locations. The time periods are flexible so that changes to service provisioning (e.g., canceling or extending local services at the location where the services are delivered) can be decided at any time based on localized service agreements.

[0079] Based on the localized service agreement, 5GS provides appropriate means to allow service providers to request and provision various localized service requirements, including QoS, expected / maximum number of users, event information for discovery, network slicing, required IP connectivity, etc., as well as routing strategies for applying localized services 155 via the hosted network 130.

[0080] 5GS supports means for the hosted network 130 to create policies and configure resources for the time and location of requests for third-party services based on received requests.

[0081] 5GS supports means for the hosted network 130 to inform the service provider of accepted service parameters and routing policies.

[0082] Subject to regulatory requirements and localized service agreements, 5GS allows the home network operator to automatically negotiate policies with the hosted network 130 for allowing subscribers of the home network 120 to connect at specific times (e.g., time and location) for their home network services.

[0083] Subject to the automatic localization service agreement between the hosted network operator and the home network operator, for UE 802 that only has a home network subscription and has authorization to access the hosted network 130, 5GS supports access to the hosted network 130 and uses the home network services or selected localization services 155 via the hosted network 130, and ensures seamless service continuity for the home network services or selected localization services 155 when moving between two hosted networks or the host network and the home network.

[0084] 5GS supports mechanisms for implementing configuration of a network that provides access to localized services 155 so that the service can be limited in terms of its spatial extent (in terms of a particular topology (e.g., a single cell)) as specified by the service provider of the localized service 155.

[0085] 5GS supports mechanisms for implementing configuration of a network that provides access to localized services 155 so that the service can be limited in terms of available resources or capacity to correspond to the requirements of the location where the service is delivered (as specified by the service provider of the localized service 155).

[0086] 5GS supports means for the hosted network 130 to provide third-party service providers with information for UE 802 to automatically discover the hosted network 130 to allow access to specific third-party services.

[0087] 5GS supports security mechanisms for allowing the home network 120 to coordinate with the hosted network 130 for a subscriber to temporarily access the hosted network 130 at a given time (start time and duration) and location (e.g., based on temporary credentials).

[0088] 1.3.1.2. User manually selects localization service via hosting network

[0089] The hosted network 130 allows the UE 802 to manually select a temporary localized service 155 provided at the hosted network 130 via a local breakout.

[0090] NOTE: The localized services 155 provided at the hosted network 130 via local breakout may be based on the interworking scenarios indicated in Appendix H for hosted network 130 owned / cooperative services.

[0091] 1.3.1.3.UE configuration, provisioning, authentication and authorization

[0092] Subject to localized service agreements, 5GS enables the home network operator to authorize the UE 802 to use its home network services via the hosted network 130 during specific time periods and / or locations.

[0093] 5GS allows a trusted third-party service provider to provide localized service policies (e.g., QoS, network slicing in the hosted network 130 or the home network 120, service restrictions (e.g., time and location)) to UE 802 via the hosted network 130 or the home network 120 of UE 802.

[0094] 5GS enables UE 802 to use credentials provided by hosted network 130, with or without coordination with UE 802's home network 120, to use localized services 155 via hosted network 130 under specific time (including start time and duration) and location validity.

[0095] 5GS is able to allow the home network 120 to guide its UE 802 to the hosted network 130 taking into account the location, time, coverage of the hosted network 130, and the services provided by the home network 120 and the hosted network 130.

[0096] 5GS provides support for implementing secure means for authenticating and authorizing users of UE 802 to access hosted network 130, including situations where UE 802 does not subscribe to hosted network 130 and still needs to be authorized to use localized services 155 via hosted network 130. It can be assumed that the network provider deploying hosted network 130 has access (e.g., through a separate registration process) to corresponding identification information about the user.

[0097] The 5GS is able to authenticate and authorize UE 802 of a user authenticated by the hosted network 130 to access the hosted network 130 and its localized services 155 as requested by the service provider.

[0098] 1.3.1.4.UE discovery, selection and access

[0099] Subject to the operator's policies and agreements between the third-party service provider and the operator, the 5GS should enable the UE 802 to receive and use configurations provided by the third-party service provider to discover and access the hosted network 130 and localized services 155, including taking into account previous service agreements with the third-party service provider and not having previously subscribed to the hosted network 130. If the UE 802 is able to obtain services from both networks simultaneously, it may additionally select the hosted network 130. If the UE 802 cannot maintain a connection to the home network 120 while selecting the hosted network 130, the selection should only be done at the user's request (e.g., using manual selection).

[0100] 5GS supports a secure means for UE 802 to select and access localized services 155 that may be provided by a third-party service provider via hosted network 130, independent of prior subscription to hosted network 130 or the third-party service provider.

[0101] 5GS should enable the home network 120 to allow the UE 802 to automatically select the hosted network 130 for accessing the localized service 155 when specified conditions (e.g., predefined time, location) are met.

[0102] If the authorization for the localized service 155 is no longer valid (e.g., which may be based on certain conditions (e.g., the time or location of the user)), the 5GS should be able to prevent the UE 802 from reaccessing the hosted network 130 after the localized service 155 is terminated.

[0103] The 5GS may support means for a UE 802, which may or may not have a previous subscription to a hosted network 130, to display human-readable information about how to gain access to the hosted network 130 and available third-party services.

[0104] 5GS supports a mechanism for allowing a user to manually select a specific local hosted network 130. Additional information may be presented to the user to facilitate manual network selection.

[0105] The 5GS is able to restrict access of a particular UE 802 to a configurable area of ​​the coverage area of ​​the hosting network 130.

[0106] 5GS is able to maintain the user's privacy with respect to hosted network 130 while UE 802 is not using hosted network 130 (e.g., to prevent hosted network 130 from tracking UE 802).

[0107] 5GS should enable the home network 120 to instruct the UE 802 to select a hosted network 130 with specific conditions (e.g., predefined time, location) based on a request from a service provider.

[0108] The 5GS should enable the home network 120 to allow the UE 802 to select a hosted network 130 or change to another hosted network 130 without any additional user intervention, as long as the delivered services (both localized services 155 and home routed services) do not change.

[0109] 1.3.1.5. Managed network localization services and home operator services

[0110] 5GS should enable the home network operator to indicate to the UE 802 which services are preferred to be used from the home network 120 when the UE 802 is connected to the hosted network 130 and the requested services are available from both the hosted and home networks 120.

[0111] Based on the localized service agreement, the hosted network 130 should be able to provide the required connectivity and QoS for the UE 802 that is simultaneously connected to the hosted network 130 (for localized services) and its home network 120 (for home network services).

[0112] The UE 802 can connect to its home network 120 via the hosted network 130 if supported by the hosted network 130 and the home network 120 based on a localized service agreement.

[0113] 1.3.1.6. Return to home network

[0114] 5GS provides mechanisms for alleviating user plane and control plane overload caused by a large number of UEs 802 returning from temporary local access of a hosted network 130 to their home network 120 within a very short period of time.

[0115] 5GS provides mechanisms for minimizing the impact on UE 802 communications (e.g., to prevent user plane and control plane bursts) when returning to the home network 120 with a large number of other UEs 802 within a very short period of time after terminating their temporary local access to the hosted network 130.

[0116] 1.1.1. Enabling access to localized services

[0117] To enable the PNI-NPN or SNPN to provide access to the localized service 155, the PNI-NPN or SNPN operator configures the network to enable the UE 802 to access the localized service 155 using the PNI-NPN or SNPN based on any validity of the localized service 155, and negotiates with the LSP 150 to determine the information (e.g., an identifier of each localized service (e.g., to be used in UE routing policy (URSP) rules); validity restrictions for each localized service (e.g., validity in time and / or location); service parameters for each localized service (e.g., DNN, S-NSSAI, and QoS requirements); and / or service authorization method (e.g., NSSAA or secondary authentication / authorization during PDU session establishment)).

[0118] In order to allow UE 802 to access the PNI-NPN or SNPN using the HPLMN or subscribed SNPN credentials, the PNI-NPN or SNPN can be configured based on the localized service agreement between the PNI-NPN or SNPN and the HPLMN or subscribed SNPN to allow a single authentication to the HPLMN when the PNI-NPN or SNPN is providing access to the localized service 155, and to allow a single authentication to the subscribed SNPN when the SNPN is providing access to the localized service 155.

[0119] In order to allow UE 802 to access the SNPN that provides access to localized services 155 when new credentials are required, the SNPN may provide the UE access functionality specified in clause 5.30.2.10 of [TS23501] for UE 802 to obtain credentials and information necessary to access the SNPN, or UE 802 may use existing credentials and network connectivity to obtain access to the PVS via the user plane to obtain new credentials.

[0120] To allow UE 802 to access a PNI-NPN that provides access to localized services 155 (requiring NSSAA or secondary authentication / authorization during PDU session establishment), UE 802 may obtain new credentials using remote provisioning functionality as defined in clause 5.39 of [TS23501].

[0121] To allow UE 802 to access HPLMN or subscribed SNPN services while registered in a PNI-NPN or SNPN, the PNI-NPN or SNPN may establish a service agreement and configure interconnection with the HPLMN or subscribed SNPN operator. If the PNI-NPN is providing access to localized services 155, the existing roaming architecture with home-routed PDU sessions is used. If the SNPN is providing access to localized services 155, the UE 802 may access the HPLMN or subscribed SNPN as described in Annex D, clauses D.3, D.6, and D.7 of [TS23501].

[0122] Additionally or alternatively, the UE 802 may obtain localized service information from the application server 838 , the serving networks 150 , 155 , the home network 120 , or the hosted network 130 .

[0123] In some examples, when the full set of new subscriptions / credentials is provided to UE 802 via application server 838, UE 802 ingests information from application server 838. This example has less system impact on 5GS than other solutions. However, the home network subscription / credential is used for UE 802 to establish a PDU connection with the application server, and UE 802 needs to handle the coexistence of multiple subscriptions / credentials on the device. Additionally or alternatively, when the information includes a list of hosted networks 130 and an indication that the home network 120 credentials are to be used, UE 802 ingests information from application server 838, there will be an impact on network selection. It is not necessary for application server 838 to obtain such information via network openness because it is covered as part of the SLA between the localization service provider and the hosted network operator.

[0124] In order to configure PNI-NPN or SNPN (e.g., to create a network slice / DNN for carrying localized service traffic), the existing OAM mechanism can be reused in accordance with clause 6.3.1 of 3GPP TS28.557 (which provides a solution for NPN allocation for network slices of PLMN and for opening the management capabilities of PNI-NPN). The attributes used to support this management are further documented in 3GPP TS28.541.

[0125] For session management level information and interactions (e.g., monitoring PNI-NPN or SNPN performance) and achieving appropriate QoS for UE 802 in the PNI-NPN or SNPN for localized services, the following non-exhaustive options may be used: covered by a service level agreement (SLA) between the PNI-NPN or SNPN operator and the LSP 150; reusing the existing network opening procedure specified in clause 4.15 of [TS23502], where the LSP 150 is assuming the AF role and leveraging the opening capabilities provided by the PNI-NPN or SNPN; enabling the NEF 852 / PCF 856 in the PNI-NPN or SNPN that provides access to the localized service 155 (via the AF of the LSP 150) to receive the validity conditions and QoS requirements of the localized service 155 and forward them to the AMF 844 / SMF 846 by reusing the existing PCF 856-initiated AM / SM policy association procedure described in clause 4.16 of [TS23502].

[0126] UE 802 selects a SNPN that provides access to localized services 155 as described in clauses 5.30.2.4.2 and 5.30.2.4.3 of [TS23501] and in 3GPP TS23.122 ("[TS23122]").

[0127] Access to localized services is made available in a specific area and / or during a specific time period. After UE 802 has successfully registered to a PNI-NPN / SNPN that provides access to localized services, UE 802 can be configured with URSP rules using existing principles (see, e.g., clause 6.6.2.2 of [TS23503]).

[0128] URSP rules may include associations between UE applications and DNN / S-NSSAI that are meaningful for a specific localized service. URSP rules may also include the "Route SelectionValidation Criteria" described in Table 6.6.2.1-3 of [TS23503] with time / location defined for a specific localized service.

[0129] The existing LADN features described in clause 5.6.5 of [TS23501] may also be used to enable the UE to access localized services defined by the LADN DNN. The S-NSSAI for localized services may be restricted to specific areas and times, as described in clause 5.15 of [TS23501].

[0130] When local service 155 in the network is completed, all UEs 802 registered with the network are expected to transfer to other networks or other network resources (e.g., other cells) within the same network potentially within a relatively short time frame. The other network may be a HPLMN, a VPLMN, or another SNPN.

[0131] The UE 802 may stop using network resources for the localization service 155 for a number of reasons (e.g., when one or more of the following conditions apply): the localization service 155 in the network completes; the validity conditions of the network selection information are no longer met; the user decides to stop using the localization services 155 before they complete; and / or the network makes a policy decision with the effect that the UE 802 deregisters before the localization service 155 completes. The list is not exhaustive, and the UE 802 may stop using network resources for the localization service 155 due to other reasons (e.g., the UE 802 loses coverage, loses power).

[0132] When a large number of UEs 802 move to other networks (eg, HPLMN, VPLMN, or another SNPN) or other network resources within a relatively short time frame, the total signaling involved may result in signaling overload in the target network.

[0133] Existing mechanisms for control plane load control, congestion and overload control described in clause 5.19 of [TS23501] and access control and barring described in clause 5.2.5 of [TS23501] may be used to mitigate the signaling overload caused by the returning UE 802. To further enhance the mitigation of signaling overload, additional mechanisms may be implemented to ensure that the load caused by the returning UE 802 is distributed. Such mechanisms are implementation specific, but some guidelines that may be considered include: (i) the time validity of the network selection information given to UE 802 may be set to be slightly longer than the actual duration of the service (e.g., the user disables the localized service itself and then UE 802 stops using the connection to access the localized service, thereby causing UE 802 to move, for example, by performing normal network selection); (ii) the time validity of the network selection information given to UE 802 may be different for each UE 802, so that each UE 802 performs network selection at a different time to disperse the returning UE 802; (iii) when AMF 844 triggers deregistration of UE 802 after the end of localized service 155, deregistration requests may be sent at a specific rate in an adaptive and distributed manner, with the effect that the signaling load on both the source network and the target network is limited; and / or (iv) when AMF 844 triggers UE 802 to deregister after the end of localized service 155, deregistration requests may be sent at a specific rate in an adaptive and distributed manner, with the effect that the signaling load on both the source network and the target network is limited. When configuring an update procedure at 802 (eg, removing an S-NSSAI from the allowed NSSAI (if a dedicated S-NSSAI is used for localized services), requests may be sent at a specific rate, with the effect that the signaling load in the network is limited).

[0134] 2. Network, system and equipment configuration and layout

[0135] Figure 8 800a. The network 800a may operate in a manner consistent with the 3GPP technical specifications for LTE or 5G / NR systems. However, the example embodiments are not limited thereto, and the described examples may be applied to other networks (e.g., future 3GPP systems, etc.) that benefit from the principles described herein.

[0136] The network 800a includes a UE 802, which is any mobile or non-mobile computing device designed to communicate via an air connection with a RAN 804. The UE 802 is communicatively coupled to the RAN 804 via a Uu interface that may be applicable to both LTE systems and NR systems. Examples of UE 802 include, but are not limited to, smartphones, tablet computers, wearable devices (e.g., smart watches, fitness trackers, smart glasses, smart clothing / fabrics, head-mounted displays, smart shows, etc.), desktop computers, workstations, laptop computers, in-vehicle infotainment systems, in-vehicle entertainment systems, instrument clusters, heads-up display (HUD) devices, onboard diagnostic devices, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, connected appliances, machine type communication devices, machine to machine (M2M), device to device (D2D), machine type communication (MTC) devices, Internet of Things (IoT) devices, smart appliances, flying drones or unmanned aerial vehicles (UAVs), ground drones or autonomous vehicles, robots, electronic signs, single board computers (SBCs) (e.g., Raspberry Pi, Arduino, Intel Edison, etc.), plug-in computers, and / or any type of computing device (e.g., any of the devices discussed herein). UE 802 may be the same as or similar to any other UE 802 discussed herein (eg, UE 902, hardware resource 1000, and / or any other UE discussed herein).

[0137] The network 800a may include a group of UEs 802 that are directly coupled to each other via device-to-device (D2D), proximity services (ProSe), PC5, and / or sidelink (SL) interfaces and / or any other suitable interface (e.g., any interface discussed herein). These UEs 802 may be M2M, D2D, MTC, and / or IoT devices and / or V2X systems that communicate using physical sidelink channels (e.g., but not limited to PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.). UE 802 may perform blind decoding attempts of SL channels / links according to various examples herein.

[0138] In some examples, the UE 802 may additionally communicate with the AP 806 via an over-the-air (OTA) connection. The AP 806 manages a WLAN connection, which may be used to offload some / all network traffic from the RAN 804. The connection between the UE 802 and the AP 806 may conform to any IEEE 802.11 protocol. Additionally, the UE 802, the RAN 804, and the AP 806 may utilize cellular-WLAN aggregation / integration (e.g., LWA / LWIP). Cellular-WLAN aggregation may involve the UE 802 being configured by the RAN 804 to utilize both cellular radio resources and WLAN resources.

[0139] The RAN 804 includes one or more network access nodes (NAN) 814 (also referred to as "RAN nodes 814"). The NAN 814 terminates the air interface for the UE 802 by providing access layer protocols including RRC, PDCP, RLC, MAC, and PHY / L1 protocols. In this way, the NAN 814 implements data / voice connectivity between the core network (CN) 840 and the UE 802. The NAN 814 can be a macrocell base station, or a low-power base station for providing a femtocell, a picocell, or other similar cells with a smaller coverage area, smaller user capacity, or higher bandwidth than a macrocell; or some combination thereof. In these implementations, the NAN 814 may be referred to as a base station (BS), a next-generation nodeB (gNB), a RAN node, an eNodeB (eNB), a next-generation (ng)-eNB, a NodeB, an RSU, a TRP, etc.

[0140] One example implementation is a "CU / DU split" architecture, where the NAN 814 is embodied as a gNB-central unit (CU) communicatively coupled to one or more gNB-distributed units (DUs), where each DU may be communicatively coupled to one or more radio units (RUs) (also referred to as RRHs, RRUs, etc.). In some implementations, the one or more RUs may be separate RSUs. In some implementations, the CU / DU split may also include an ng-eNB-CU and one or more ng-eNB-DUs, respectively, instead of or in addition to the gNB-CU and gNB-DU. The NAN 814 employed as a CU may be implemented in a discrete device or as one or more software entities running on a server computer as part of, for example, a virtual network (including a virtual baseband unit (BBU) or a pool of BBUs, a cloud RAN (CRAN), a radio equipment controller (REC), a radio cloud center (RCC), a centralized RAN (C-RAN), a virtualized RAN (vRAN), etc. (although these terms may refer to different implementation concepts)). Any other type of architecture, arrangement, and / or configuration may be used.

[0141] The set of NANs 814 are coupled to each other via respective X2 interfaces (if the RAN 804 is an LTE RAN or an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 810) or respective Xn interfaces (if the RAN 804 is an NG-RAN 804). The X2 / Xn interfaces (which in some examples may be separated into control / user plane interfaces) may allow the ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0142] The ANs of the RAN 804 may each manage one or more cells, cell groups, component carriers, etc. to provide an air interface for network access to the UE 802. The UE 802 may be simultaneously connected to a group of cells provided by the same or different NANs 814 of the RAN 804. For example, the UE 802 and the RAN 804 may use carrier aggregation to allow the UE 802 to connect to a group of component carriers, each corresponding to a Pcell or an Scell. In a dual connectivity scheme, the first AN 808 may be a primary node providing an MCG, and the second AN 808 may be a secondary node providing an SCG. The first / second NAN 814 may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0143] RAN 804 may provide an air interface through a licensed spectrum or an unlicensed spectrum. In order to operate in an unlicensed spectrum, a node may use LAA, eLAA, and / or feLAA mechanisms based on CA technology with PCells / Scell. Before accessing the unlicensed spectrum, a node may perform a medium / carrier sensing operation based on, for example, a listen-before-talk (LBT) protocol.

[0144] Additionally or alternatively, each UE 802 provides radio information to one or more NANs 814 and / or one or more edge computing nodes (e.g., edge servers / hosts, etc.). The radio information may be in the form of one or more measurement reports, and / or may include, for example, signal strength measurements, signal quality measurements, etc. Each measurement report is tagged with a timestamp and location of the measurement (e.g., the current location of the UE 802). As an example, the measurements collected by the UE 802 and / or included in the measurement report may include one or more of the following: bandwidth (BW), network or cell load, latency, jitter, round trip time (RTT), number of interruptions, out-of-order delivery of data packets, transmission power, bit error rate, bit error ratio (BER), block error rate (BLER), packet error rate (PER), packet loss rate, packet reception rate (PRR), data rate, peak data rate, end-to-end (e2e) delay, signal-to-noise ratio (SNR), signal-to-interference-to-noise ratio (SINR), signal-plus-noise-plus-distortion to noise-plus-distortion (SINAD) ratio, carrier-to-interference-to-noise ratio (CINR), additive white Gaussian noise (AWGN), energy per bit to noise power density ratio (Eb / N0), energy per chip to interference power density ratio (Ec / I0), energy per chip to noise power density ratio (Ec / N0), peak to average power ratio (PAPR), reference signal received power (RSRP), reference signal received quality (RSRQ), received signal strength indication (RSSI), received channel power indication (RCPI), received signal to noise indication (RSNI), received signal code power (RSCP), average noise plus interference (ANPI), GNSS timing of cell frames for UE positioning for E-UTRAN or 5G / NR (e.g., AP 806 or RAN node 808 reference time and a GNSS-specific reference time for a given GNSS), GNSS code measurements (e.g., the GNSS code phase (integer and fractional parts) of the spreading code of the ith GNSS satellite signal), GNSS carrier phase measurements (e.g., the number (integer and fractional parts) of the carrier phase cycles of the ith GNSS satellite signal measured since lock on to the signal; also known as accumulated delta range (ADR)), channel interference measurements, thermal noise power measurements, received interference power measurements, power histogram measurements, channel load measurements, STA statistics, and / or other similar measurements.RSRP, RSSI and / or RSRQ measurements may include RSRP, RSSI and / or RSRQ measurements of cell-specific reference signals, channel state information reference signals (CSI-RS) and / or synchronization signals (SS) or SS blocks for 3GPP networks (e.g., LTE or 5G / NR) and RSRP, RSSI, RSRQ, RCPI, RSNI and / or ANPI measurements of various beacons, fast initial link setup (FILS) discovery frames or probe response frames for WLAN / WiFi (e.g., [IEEE80211]) networks. Other measurements may be used in addition or alternatively, such as those discussed in 3GPP TS 36.214 v17.0.0 (2022-03-31) (“[TS36214]”), 3GPP TS 38.215 v17.3.0 (2023-03-30) (“[TS38215]”), 3GPP TS 38.314 v17.2.0 (2023-01-13) (“[TS38314]”), IEEE Standard for Information Technology—Telecommunications and Information Exchange between Systems—Local and Metropolitan Area Networks—Specific Requirements—Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, IEEE Std 802.11-2020, pp. 1-4379 (26 Feb. 2021) ("[IEEE 80211]"), etc. Additionally or alternatively, any of the foregoing measurements (or combinations of measurements) may be collected by one or more NANs 814 and provided to edge computing nodes.

[0145] Additionally or alternatively, the measurements may include one or more of the following measurements: measurements related to data radio bearers (DRBs) (e.g., the number of DRBs attempted to be established, the number of DRBs successfully established, the number of active DRBs released, the intra-session activity time for DRBs, the number of DRBs attempted to be restored, the number of DRBs successfully restored, etc.); measurements related to RRC (e.g., the average number of RRC connections, the maximum number of RRC connections, the average number of inactive RRC connections stored, the maximum number of inactive RRC connections stored, the number of attempted, successful and / or failed RRC connection establishments, etc.); measurements related to UE context (UECNTX); measurements related to radio resource utilization (RRU) (e.g., DL total PRB utilization, UL total PRB utilization, distribution of DL total PRB utilization, distribution of UL total PRB utilization, DL PRBs used for data services, UL PRBs used for data services). PRB, DL total available PRB, UL total available PRB, etc.); measurements related to registration management (RM); measurements related to session management (SM) (e.g., the number of PDU sessions requested to be established, the number of PDU sessions successfully established, the number of PDU sessions that failed to be established, etc.); measurements related to GTP management (GTP); measurements related to IP management (IP); measurements related to policy association (PA); measurements related to mobility management (MM) (e.g., for hetero-RAT, homo-RAT and / or homo-frequency / hetero-frequency handover and / or conditional handover): the requested , number of successful and / or failed handover preparations; number of requested, successful and / or failed handover resource allocations; number of requested, successful and / or failed handover executions; average and / or maximum time of requested handover executions; number of successful and / or failed handover executions per beam pair, etc.); measurements related to virtualized resources (VR); measurements related to the operator (CARR); measurements related to QoS flows (QF) (e.g., number of active QoS flows released, number of QoS flows attempted to be released, session activity time for QoS flows, session activity time for UE 802, the number of QoS flows attempted to be established, the number of QoS flows successfully established, the number of QoS flows that failed to be established, the number of initial QoS flows attempted to be established, the number of initial QoS flows successfully established, the number of initial QoS flows that failed to be established, the number of QoS flows attempted to be modified, the number of QoS flows successfully modified, the number of QoS flows that failed to be modified, etc.); measurements related to application triggers (AT); measurements related to short message services (SMS); measurements related to power, energy and environment (PEE); measurements related to NF services (NFS); measurements related to packet flow description (PFD); measurements related to random access channels (RACH); measurements related to measurement reports (MR);Measurements related to Layer 1 Measurements (L1M); measurements related to Network Slice Selection (NSS); measurements related to Paging (PAG); measurements related to Non-IP Data Delivery (NIDD); measurements related to External Parameter Provisioning (EPP); measurements related to Traffic Impact (TI); measurements related to Connection Establishment (CE); measurements related to Service Parameter Provisioning (SPP); measurements related to Background Data Delivery Policy (BDTP); measurements related to Data Management (DM); and / or any other performance measurements (e.g., performance measurements discussed in 3GPP TS 28.552 v18.2.0 (2023-03-30) (“[TS28552]”), 3GPP TS 32.425 v17.1.0 (2021-06-24) (“[TS32425]”), etc.). ;

[0146] Radio information may be reported in response to a trigger event and / or in a periodic manner. Additionally or alternatively, each UE 802 reports radio information with low or high periodicity depending on the data transmission to occur and / or other information about the data transmission. Additionally or alternatively, the edge computing node may request measurements from the NAN 814 with low or high periodicity, or the NAN 814 may provide measurements to the edge computing node with low or high periodicity. Additionally or alternatively, the edge computing node may obtain other relevant data (e.g., key performance indicators (KPIs)) from other edge computing nodes, core network functions (NFs), application functions (AFs), and / or other UEs 802 together with or separately from the measurement report.

[0147] Additionally or alternatively, in the event that there are discrepancies in the observed data from one or more UEs, one or more RAN nodes and / or core network NFs (e.g., reports are missing, data is erroneous, etc.), simple imputation may be performed to supplement the observed data obtained (e.g., replacing values ​​from previous reports and / or historical data, applying extrapolation filtering, etc.). Additionally or alternatively, acceptable boundaries for observed data may be predetermined or configured. For example, CQI and MCS measurements may be configured to be within a range defined only by an appropriate 3GPP standard. In the event that the reported data values ​​are meaningless (e.g., values ​​are outside an acceptable range / boundary, etc.), such values ​​may be discarded for the current learning / training episode or cycle. For example, a packet delivery delay boundary may be defined or configured, and packets determined to be received only after the packet delivery delay boundary may be discarded.

[0148] UE 802 may also perform reference signal (RS) measurement and reporting procedures to provide the network with information regarding the quality of one or more wireless channels and / or the general communication medium, and this information may be used to optimize various aspects of the communication system. As an example, the measurement and reporting procedures performed by UE 802 may include those discussed in: 3GPP TS 38.211 v17.4.0 (2023-01-04) (“[TS38211]”), 3GPP TS 38.212 v17.5.0 (2023-03-30) (“[TS38212]”), 3GPP TS 38.213 v17.5.0 (2023-03-30) (“[TS38213]”), 3GPP TS 38.214 v17.5.0 (2023-03-30) (“[TS38214]”), [TS38215], 3GPP TS 38.101-1 v18.1.0 (2023-04-07) (“[TS38101-1]”), 3GPP TS 38.104v18.1.0(2023-04-07)("[TS38104]"), 3GPP TS 38.133v18.1.0(2023-04-07)("[TS38133]"), [TS38331], etc. The physical signal and / or reference signal may include a demodulation reference signal (DM-RS), a phase tracking reference signal (PT-RS), a positioning reference signal (PRS), a channel state information reference signal (CSI-RS), a synchronization signal block (SSB), a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a sounding reference signal (SRS).

[0149] In any of the examples discussed herein, any suitable data collection and / or measurement mechanism may be used to collect observation data. For example, data tagging (e.g., sequence numbering, etc.), packet tracking, signal measurement, data sampling, and / or timestamping techniques may be used to determine any of the above metrics / observations. The collection of data may be based on the occurrence of an event that triggers the collection of data. Additionally or alternatively, data collection may occur at the initiation or termination of an event. Data collection may be continuous, discontinuous, and / or have a start and stop time. Data collection techniques / mechanisms may be specific to HW configuration / implementation, or may be non-HW specific, or may be based on various software parameters (e.g., OS type and version, etc.). Various configurations may be used to define any of the above data collection parameters. Such configurations may be provided by appropriate specifications / standards (e.g., 3GPP (e.g., [SA6Edge]), ETSI (e.g., [MEC]), O-RAN (e.g., [O-RAN]), Smart Edge Open (formerly OpenNESS) (e.g., [ISEO]), IETF (e.g., MAMS [RFC8743]), IEEE / WiFi (e.g., [IEEE80211], etc.), and / or any other similar standards (e.g., the standards discussed in this article)).

[0150] In some examples, the RAN 804 is an E-UTRAN having one or more eNBs and provides an LTE air interface (Uu) having parameters and characteristics as discussed at least in 3GPP TS 36.300 v17.2.0 (2022-09-30) ("[TS36300]"). In some examples, the RAN 804 is a next generation (NG)-RAN 804 having a set of RAN nodes 814 (including gNBs 814a and ng-eNBs 814b). Each gNB 814a connects to a 5G-enabled UE 802 using a 5G-NR Uu interface having parameters and characteristics as discussed in [TS38300] (in addition to many other 3GPP standards (including any standards discussed herein)). In the case where the NG-RAN 804 includes a set of ng-eNBs 814b, one or more ng-eNBs 814b connect to the UE 802 via a 5G Uu and / or LTE Uu interface. The gNB 814a and the ng-eNB 814b are connected to the 5GC 840 via respective NG interfaces including an N2 interface, an N3 interface and / or other interfaces. The gNB 814a and the ng-eNB 814b are connected to each other via an Xn interface. Additionally, each gNB 814a is connected to each other via a respective Xn interface, and each ng-eNB 814b is connected to each other via a respective Xn interface. In some examples, the NG interface may be divided into two parts: an NG user plane (NG-U) interface, which carries service data between a node of the NG-RAN 804 and the UPF 848 (e.g., an N3 interface); and an NG control plane (NG-C) interface, which is a signaling interface between a node of the NG-RAN 804 and the AMF 844 (e.g., an N2 interface).

[0151] NG-RAN 804 may provide a 5G-NR air interface (which may also be referred to as a Uu interface) with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polarization codes, repetition codes, simplex codes and Reed-Muller codes for control, and LDPC for data. Similar to the LTE air interface, the 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS. The 5G-NR air interface may not use CRS, but may use: PBCH DMRS for PBCH demodulation; PTRS for phase tracking of PDSCH; and tracking reference signals for time tracking. The 5G-NR air interface may operate on a FR1 band including a sub-6 GHz band or a FR2 band including a band from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include SSBs, which are areas in the DL resource grid that include PSS / SSS / PBCH.

[0152] The 5G-NR air interface can utilize BWP for various purposes. For example, BWP can be used for dynamic adaptation of SCS. For example, UE 802 can be configured with multiple BWPs, each BWP configuration having a different SCS. When the BWP change is indicated to UE 802, the SCS of the transmission also changes. Another use case example of BWP is related to power saving. Specifically, UE 802 can be configured with multiple BWPs with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with a small traffic load while allowing power saving at UE 802 and in some cases at gNB 814a. A BWP containing a larger number of PRBs can be used in scenarios with higher traffic loads.

[0153] In some implementations, each gNB 814a may include a gNB-CU and a set of gNB-DUs. Additionally or alternatively, the gNB 814a may include one or more RUs. In these implementations, the gNB-CU may be connected to each gNB-DU via a corresponding F1 interface. In the case of a shared network with multiple cell ID broadcasts, each cell identity associated with a PLMN subset corresponds to a gNB-DU, and the gNB-CU to which it is connected shares the same physical layer cell resources. For resiliency, the gNB-DU may be connected to multiple gNB-CUs through appropriate implementations. In addition, the gNB-CU may be separated into gNB-CU control plane (gNB-CU-CP) and gNB-CU user plane (gNB-CU-UP) functions. The gNB-CU-CP is connected to the gNB-DU via the F1 control plane interface (F1-C), the gNB-CU-UP is connected to the gNB-DU via the F1 user plane interface (F1-U), and the gNB-CU-UP is connected to the gNB-CU-CP via the E1 interface. In some implementations, a gNB-DU is connected to only one gNB-CU-CP, and a gNB-CU-UP is connected to only one gNB-CU-CP. For resiliency, a gNB-DU and / or gNB-CU-UP may be connected to multiple gNB-CU-CPs by appropriate implementation. A gNB-DU may be connected to multiple gNB-CU-UPs under the control of the same gNB-CU-CP, and a gNB-CU-UP may be connected to multiple DUs under the control of the same gNB-CU-CP. Xn-U may support data forwarding between gNB-CU-UPs during intra-gNB-CU-CP handover within a gNB. Similarly, each ng-eNB 814b may include a ng-eNB-CU and a set of ng-eNB-DUs. In these implementations, the ng-eNB-CU and each ng-eNB-DU are connected to each other via a corresponding W1 interface. The ng-eNB may include a ng-eNB-CU-CP, one or more ng-eNB-CU-UPs, and one or more ng-eNB-DUs. The ng-eNB-CU-CP and ng-eNB-CU-UP are connected via the E1 interface. The ng-eNB-DU is connected to the ng-eNB-CU-CP via the W1-C interface and to the ng-eNB-CU-UP via the W1-U interface. If not explicitly specified otherwise, the general principles described in this document with respect to the gNB aspect also apply to the ng-eNB aspect and the corresponding E1 and W1 interfaces.

[0154] The node hosting the user plane part of the PDCP protocol layer (e.g., gNB-CU, gNB-CU-UP, and for EN-DC, MeNB or SgNB, depending on the bearer offload) performs user inactivity monitoring and further notifies the node having the control plane connection towards the core network (e.g., via E1, X2, etc.) of its inactivity or (re)activation. The node hosting the RLC protocol layer (e.g., gNB-DU) may perform user inactivity monitoring and further notifies the node hosting the control plane (e.g., gNB-CU or gNB-CU-CP) of its inactivity or (re)activation.

[0155] In these implementations, the NG-RAN 804 is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN 804 architecture (e.g., NG-RAN logical nodes and the interfaces between them) is part of the RNL. For each NG-RAN interface (e.g., NG, Xn, F1, etc.), relevant TNL protocols and functions are specified. The TNL provides services for user plane transport and / or signaling transport. In an NG-Flex configuration, each NG-RAN node is connected to all AMFs 844 of an AMF set within an AMF area that supports at least one slice that is also supported by the NG-RAN node. AMF sets and AMF areas are defined in [TS23501].

[0156] The RAN 804 is communicatively coupled to the CN 840, which includes network elements and / or network functions (NFs) for providing various functions supporting data and telecommunication services to customers / subscribers (e.g., UE 802). The components of the CN 840 may be implemented in one physical node, or in separate physical nodes. In some examples, NFV may be utilized to virtualize any or all functions provided by the network elements of the CN 840 onto physical computing / storage resources in servers, switches, etc. A logical instantiation of the CN 840 may be referred to as a network slice, and a logical instantiation of a portion of the CN 840 may be referred to as a network sub-slice.

[0157] exist Figure 8In the example of , CN 840 is 5GC 840, 5GC 840 includes authentication server function (AUSF) 842, access and mobility management function (AMF) 844, session management function (SMF) 846, user plane function (UPF) 848, network slice selection function (NSSF) 850, network open function (NEF) 852, network repository function (NRF) 854, policy control function (PCF) 856, unified data management (UDM) 858, unified data repository (UDR), application function (AF) 860 and AKMA anchor function (AAnF) 862, which are coupled with each other through various interfaces shown. The following briefly introduces the NF in 5GC 840.

[0158] AAnF 862 is an anchor function in the Home Public Land Mobile Network (HPLMN). AAnF 862 stores the AKMA anchor key (K) for AKMA service received from AUSF 842 after UE 802 completes a successful 5G one-time authentication. AKMA ) and SUPI. AAnF 862 also generates key material to be used between UE 802 and AF 860 and maintains the UE AKMA context. The AKMA context includes a set of parameters stored in AAnF 862, including SUPI, K AKMA and an AKMA key identifier (A-KID). A-KID is a globally unique identifier that can be used as a key identifier in the protocol used in the reference point Ua*. The AKMA AF 860 is able to identify the AAnF 862 serving the UE 802 from the A-KID. The AAnF 862 sends the SUPI of the UE 802 to the AF 860 located inside the operator's network, or to the NEF 852 according to the AF request.

[0159] AAnF 862 presents or otherwise includes a Naanf service-based interface presented by AAnF 862. AAnF 862 interacts with AUSF 842 and AF 860 using the service-based interface. When AF 860 is located in the operator's network, AAnF 862 uses the service-based interface to communicate directly with AF 860. When AF 860 is located outside the operator's network, NEF 852 is used to exchange messages between AF 860 and AAnF 862. In addition, various reference points are included to support AKMA, including an N61 reference point between AAnF 862 and AUSF 842; an N62 reference point between AAnF 862 and internal AF 860; an N63 reference point between AAnF 862 and NEF 852; and a Ua* reference point between UE 802 and AF 860.

[0160] The Ua* reference point is application specific. The Ua* protocol can carry the A-KID and can handle K AF expiration; UE 802 and AKMA AF 860 can use AKMA application keys derived from the AKMA anchor key to protect the reference point Ua*. The exact method of protecting the reference point Ua* depends on the application protocol used on the reference point Ua*. AKAM also includes a key hierarchy that includes the following keys: AKMA AUSF key (K AUSF ), K AKMA and AKMA application key (K AF ). AUSF Generated by AUSF 842 as specified in clause 6.1 of 3GPP TS 33.501. Keys for AAnF 862 include K AKMA , K AKMA It was created by ME and AUSF 842 from K AUSF Derived keys. The keys used for AF 860 include K AF , K AF It was created by ME and AAnF 862 from K AKMA The exported key. K AKMA and K AF It is derived according to the procedures of clauses 6.1 and 6.2 of 3GPP TS 35.535v17.8.0 (2023-03-30) (“[TS35535]”).

[0161] K AKMA and A-KID are valid until the next successful authentication is performed (implicit lifecycle), in which case K AKMA and A-KID is replaced. K AF Operator-based strategies use explicit lifecycles. AF The life cycle of the AAnF862 is sent by AAnF862, as described in clauses 6.2 and 6.3 of [TS35535]. AKMA In this case, you can continue to use K AF The duration of the current application session, or until its lifetime expires (whichever comes first). AF When the life cycle expires, based on the current K AKMA Create a new K AF When K AF Life cycle expired and in AAnF 862K AKMA If it has not changed, according to Appendix A.4 of [TS35535], based on the current K AKMA Established K AF Not a new K AF .

[0162] AUSF 842 stores data for authenticating UE 802 and handles authentication related functions. AUSF 842 may facilitate a common authentication framework for various access types. In addition to the functions defined in [TS23501], AUSF 842 also provides SUPI and AKMA key materials (A-KID, K AKMA ), and AUSF 842 performs AAnF selection.

[0163] AMF 844 allows other functions of 5GC 840 to communicate with UE 802 and RAN 804 and subscribe to notifications about mobility events for UE 802. AMF 844 is also responsible for registration management (e.g., for registering UE 802), connection management, reachability management, mobility management, and legal interception of AMF-related events, as well as access authentication and authorization. AMF 844 provides transmission of SM messages between UE 802 and SMF 846 and acts as a transparent agent for routing SM messages. AMF 844 also provides transmission of SMS messages between UE 802 and SMSF. AMF 844 interacts with AUSF 842 and UE 802 to perform various security anchoring and context management functions. In addition, AMF 844 is the termination point of the RAN-CP interface, which includes the N2 reference point between RAN 804 and AMF 844. AMF 844 is also the termination point for NAS (N1) signaling and performs NAS encryption and integrity protection.

[0164] AMF 844 also supports NAS signaling with UE 802 over the N3IWF interface. N3IWF provides access to untrusted entities. N3IWF can be the termination point for the N2 interface between (R)AN 804 and AMF 844 (for the control plane), and can be the termination point for the N3 reference point between (R)AN 804 and 848 (for the user plane). Therefore, AMF 844 handles N2 signaling from SMF 846 and AMF 844 for PDU sessions and QoS, encapsulates / decapsulates packets for IPSec and N3 tunnels, marks N3 user plane packets in UL, and implements QoS corresponding to N3 packet marking taking into account the QoS requirements associated with such marking received over N2. The N3IWF may also relay UL and DL control plane NAS signaling between the UE 802 and the AMF 844 via the N1 reference point between the UE 802 and the AMF 844, and relay UL and DL user plane packets between the UE 802 and the UPF 848. The N3IWF also provides a mechanism for IPsec tunnel establishment with the UE 802. The AMF 844 may expose an interface based on Namf services and may be used for the N14 reference point between two AMFs 844 and for communication between the AMF 844 and the 5G-EIR ( Figure 8 In addition to the functions of AMF 844 described herein, AMF 844 may also provide support for network slice restrictions and network slice instance restrictions based on NWDAF analysis.

[0165] SMF 846 is responsible for SM (e.g., session establishment, tunnel management between UPF 848 and AN 808); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuration of service steering at UPF 848 to route services to the correct destination; termination of interfaces toward policy control functions; control of policy enforcement, charging, and part of QoS; lawful interception (for SM events and interface to LI system); termination of the SM portion of NAS messages; DL data notification; initiation of AN-specific SM information sent via AMF 844 over N2 to AN 808; and determination of the SSC mode for the session. SM refers to the management of PDU sessions, and PDU sessions or "sessions" refer to PDU connection services that provide or enable the exchange of PDUs between UE 802 and DN 836. SMF 846 may also include the following functions to support edge computing enhancements (see, e.g., [TS23548]): select EASDF 861 and provide its address to the UE as a DNS server for the PDU session; use the EASDF 861 services defined in [TS23548]; and support the application layer architecture defined in [TS23558] to provision and update ECS address configuration information to the UE. The discovery and selection process for EASDF 861 is discussed in [TS23501] §6.3.23.

[0166] The UPF 848 acts as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 836, and a branch point for supporting multi-homed PDU sessions. The UPF 848 also performs packet routing and forwarding, packet inspection, implements the user plane portion of policy rules, lawful interception of packets (UP collection), performs service usage reporting, performs QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), performs UL service verification (e.g., SDF to QoS flow mapping), transport level packet marking in UL and DL, and performs DL packet buffering and DL data notification triggering. The UPF 848 may include a UL classifier to support routing of service flows to the data network.

[0167] The NSSF 850 ​​selects a set of network slice instances to serve the UE 802. The NSSF 850 ​​also determines the allowed NSSAI and the mapping to the subscribed S-NSSAI (if necessary). The NSSF 850 ​​also determines the AMF set or list of candidate AMFs 844 to be used to serve the UE 802 based on appropriate configuration and possibly by querying the NRF 854. The selection of a set of network slice instances for the UE 802 can be triggered by the AMF 844 to which the UE 802 is registered, by interacting with the NSSF 850, which may result in a change of the AMF 844. The NSSF 850 ​​interacts with the AMF 844 via the N22 reference point; and may communicate with another NSSF in the visited network via the N31 reference point (not shown).

[0168] NEF 852 securely exposes services and capabilities provided by 3GPP NFs for third parties, internal opening / re-opening, AF 860, edge computing networks / frameworks, etc. In these examples, NEF 852 can authenticate, authorize, or restrict AF 860. NEF 852 uses the Nudr interface to the unified data repository (UDR) to store / retrieve information as structured data. NEF 852 can also convert information exchanged with AF 860 and information exchanged with internal NFs. For example, NEF 852 can convert between AF service identifiers and internal 5GC information (e.g., DNN, S-NSSAI) as described in clause 5.6.7 of [TS23501]. Specifically, NEF 852 handles the shielding of network and user sensitive information of external AF 860 according to network policies. NEF 852 also receives information from other NFs based on the capabilities of the other NFs that are exposed. The information can be stored at NEF 852 as structured data, or stored at the data storage NF using standardized interfaces. The stored information can then be reopened by NEF 852 to other NFs and AF 860, or used for other purposes (e.g., analysis). For example, NWDAF analysis can be securely opened to external parties by NEF 852. In addition, data provided by external parties can be collected by NWDAF via NEF 852 for analysis generation purposes. NEF 852 processes and forwards requests and notifications between NWDAF and AF 860. In addition to the functions defined in [TS23501], NEF 852 also implements and authorizes external AFs to evaluate AKMA services and forward requests toward AAnF 862, and performs AAnF selection.

[0169] NRF 854 supports service discovery functionality, receives NF discovery requests from NF instances, and provides information of discovered NF instances to requesting NF instances. NRF 854 also maintains NF profiles of available NF instances and their supported services. The NF profile of the NF instance maintained in the NRF 854 includes the following information: NF instance ID; NF type; PLMN ID (in case of PLMN), PLMN ID+NID (in case of SNPN); network slice related identifiers (e.g., S-NSSAI, NSI ID); network address of the NF (e.g., FQDN, IP address, etc.), NF capacity information, NF priority information (e.g., for AMF selection), NF set ID, NF service set ID of the NF service instance; NF specific service authorization information; names of supported services (if applicable); endpoint addresses of instances of each supported service; identification of the stored data / information (e.g., for UDR profile and / or other NF profiles); other service parameters (e.g., DNN or DNN list, LADN DNN or LADN DNN list, notification endpoint for each type of notification that the NF service is interested in receiving, etc.); location information for the NF instance (e.g., geographical location, data center, etc.); TAI; NF load information; routing indicator, home network public key identifier (for UDM 858 and AUSF 842); for UDM 858, AUSF 842, For UDM 858 and AUSF 842, and if UDM 858 / AUSF 842 is used to access the SNPN using credentials owned by the credential holder with an AAA server, the identity of the credential holder (e.g., the security realm of the SUPI based on the network specific identifier); for UDM 858 and AUSF 842, and if UDM 858 / AUSF 842 is used to access the SNPN using credentials owned by the credential holder (e.g., the security realm if a SUPI based on the network specific identifier is used, or the MCC and MNC if a SUPI based on the IMSI is used); for AUSF 842 and NSSAAF, in the case of SNPN access using a DCS with an AAA server, the identity of the DCS (e.g., the security realm of the SUPI based on the network specific identifier); for UDM 858 and AUSF 842, and if UDM 858 / AUSF 842 is used to access the SNPN using credentials owned by the credential holder 842 is used as DCS (in case of SNPN access), the identity of the DCS (e.g., security domain if SUPI is based on network specific identifier, or MCC and MNC if SUPI is based on IMSI); one or more GUAMIs (in case of AMF 844); for UPF 848, see clause 5.2.7.2 of [TS23502].2; for UDM 858, it is the UDM group ID, the range of SUPI, the range of GPSI, the range of internal group identifiers, and the range of external group identifiers; for UDR, it is the UDR group ID, the range of SUPI, the range of GPSI, and the range of external group identifiers; for AUSF 842, it is the AUSF group ID and the range of SUPI; for PCF 856, it is the PCF group ID and the range of SUPI; for HSS, it is the HSS group ID, IMPI set, IMPU set, IMSI set, PSI set, and MSISDN set; event IDs supported by AF 860 (in the case of NEF 852); event IDs supported by the event open service of UPF 848; application identifiers supported by AF 860 (in the case of NEF 852); the range of external identifiers, or the range of external group identifiers, or the domain name of NEF service (in the case of NEF 852); in addition, NRF 854 may store mappings between UDM group ID and SUPI, UDR group ID and SUPI, AUSF group ID and SUPI, and PCF group ID and SUPI to enable discovery of UDM 858, UDR, AUSF 842, and PCF 856 using SUPI and SUPI ranges, as specified in clause 6.3 [of TS23501], and / or interact with the UDR to resolve UDM group ID / UDR group ID / AUSF group ID / PCF group ID based on UE identity (e.g., SUPI); 3GPP List of IP domains, range of (UE) IPv4 addresses or range of (UE) IPv6 prefixes, range of SUPI or range of GPSI or BSF Group ID (in case of BSF) as described in clause 6.1.6.2.21 of TS29.510v18.2.0 (2023-03-29) ("[TS29510]"); SCP domain to which the NF belongs; DCCF service area information, NF type of data source, NF set ID of data source (if available) (in case of DCCF 863); list of supported DNAIs (in case of SMF 846); for SNPN, capability to support SNPN onboarding (in case of AMF) and capability to support remote provisioning of user plane (in case of SMF 846); for UPF 848, IP address range, DNAI; additional V2X related NF profile parameters defined in 3GPP TS 23.287; additional ProSe related NF profile parameters defined in 3GPP TS23.304; additional MBS-related NF profile parameters are defined in 3GPP TS23.247; additional UAS-related NF profile parameters are defined in TS23.256; and many other contents discussed in [TS23501]. In some examples, in cases where, for example, a NF instance has exceptional service authorization information, the service authorization information provided by the OAM system is also included in the NF configuration file. .

[0170] For NWDAF, the NF profile includes: supported analysis IDs (possibly by service), NWDAF service area information (e.g., a list of TAIs for which NWDAF can provide services and / or data), supported analysis delays by analysis ID (if available), NF type of NF data source, NF set ID of NF data source (if available), analysis aggregation capability (if available), analysis metadata provisioning capability (if available), ML model filtering information parameters S-NSSAI and regions of interest for trained ML models by analysis ID (if available), federated learning (FL) capability type (e.g., FL server or FL client (if available)), time intervals for supporting FL (if available). The service area information of NWDAF is common to all analysis IDs it supports. Analysis IDs supported by NWDAF can be associated with supported analysis delays, for example, analysis reports can be generated with a time less than or equal to the supported analysis delay (including data collection delay and inference delay). Determining supported analysis delays and how NWDAF avoids frequent updates of its supported analysis delays in NRF can be NWDAF implementation specific.

[0171] PCF 856 provides policy rules to the control plane functions to implement them and may also support a unified policy framework to manage network behavior. PCF 856 may also implement a front end to access subscription information related to policy decisions in UDR 859 of UDM 858. In addition to communicating with functions through reference points as shown, PCF 856 also exposes an interface based on Npcf services.

[0172] UDM 858 processes subscription-related information to support the processing of communication sessions by network entities, and stores subscription data of UE 802. For example, subscription data can be transferred via the N8 reference point between UDM 858 and AMF 844. UDM858 may include two parts: an application front end and a UDR. UDR may store subscription data and policy data for UDM 858 and PCF 856, and / or structured data for openness and application data for NEF 852 (including PFD for application detection, application request information for multiple UE 802). UDR may expose a Nudr service-based interface to allow UDM858, PCF 856, and NEF 852 to access a specific set of stored data, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of changes in related data in UDR. UDM 858 may include a UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. Several different front ends may serve the same user in different transactions. UDM-FE accesses subscription information stored in UDR and performs authentication credential processing, user identity processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs through reference points as shown, UDM 858 can also expose Nudm service-based interfaces. In addition to the functions defined in [TS23501], UDM 858 also stores the subscriber's AKMA subscription data. AKMA subscription data is data in the home operator's network (e.g., home network 120) that indicates whether the subscriber is allowed to use AKMA.

[0173] Edge Application Server Discovery Function (EASDF) 861 exposes an interface based on the Neasdf service and connects to SMF 846 via the N88 interface. One or more EASDF instances may be deployed within the PLMN, and the interaction between the 5GC NF and the EASDF 861 occurs within the PLMN. EASDF 861 includes one or more of the following functions: registering with NRF 854 for EASDF 861 discovery and selection; processing DNS messages according to instructions from SMF 846; and / or terminating DNS security (if used). Processing DNS messages according to instructions from SMF 846 includes one or more of the following functions: receiving DNS message processing rules and / or BaselineDNSPattern from SMF 846; exchanging DNS messages from / with UE 802; forwarding DNS messages to C-DNS or L-DNS for DNS queries; adding EDNS Client Subnet (ECS) options to DNS queries about FQDNs; reporting information related to received DNS messages to SMF 846; and / or buffering / discarding DNS messages from UE 802 or DNS servers. The EASDF has a direct user plane connection with the PSA UPF through N6 (e.g., without any NAT) for transporting DNS signaling exchanged with the UE. Deployment of NAT between the EASDF 861 and the PSA UPF 848 may or may not be supported. Additional aspects of the EASDF 861 are discussed in [TS23548].

[0174] AF 860 provides application influence on service routing, provides access to NEF 852, and interacts with the policy framework for policy control. AF 860 can influence UPF 848 (re)selection and service routing. Based on operator deployment, when AF 860 is considered a trusted entity, the network operator can allow AF 860 to interact directly with the relevant NF. In some implementations, AF 860 can be used for edge computing implementations.

[0175] NFs that need to collect data from AF 860 can subscribe / unsubscribe to notifications about data collected from AF 860 directly from AF 860 or via NEF 852. The data collected from AF 860 is used as input for analysis performed by NWDAF. Details about the data collected from AF 860 and the interactions between NEF 852, AF 860, and NWDAF are described in 3GPP TS 23.288. In addition to the functions defined in [TS 23501], AF 860 with AKMA service also implements requesting AKMA application keys (referred to as K-ID) from AAnF using A-KID. AF ). When providing K to AF 860AF Previously, AF 860 was also authenticated and authorized by the operator network. When located inside the operator network, AF 860 performs AAnF selection.

[0176] 5GC 840 can implement edge computing by selecting the operator / third party service to be geographically close to the point where UE 802 attaches to the network. This can reduce latency and load on the network. In an edge computing implementation, 5GC 840 can select UPF 848 close to UE 802 and perform traffic steering from UPF 848 to DN 836 via the N6 interface. This can be based on UE subscription data, UE location and information provided by AF 860, which allows AF 860 to influence UPF (re)selection and traffic routing.

[0177] The data network (DN) 836 may represent various network operator services, Internet access, or third-party services that may be provided by one or more servers (including, for example, application (app) / content server 838). DN 836 may be an operator external public network, a private PDN network, or an operator intra-packet data network (e.g., for provisioning IMS services). In this example, the app server 838 may be coupled to the IMS via an S-CSCF or an I-CSCF. In some implementations, DN 836 may represent one or more local area network DNs (LADNs), which are DNs 836 (or DN names (DNNs)) that are accessible by UE 802 in one or more specific areas. Outside of these specific areas, UE 802 cannot access LADN / DN 836.

[0178] Additionally or alternatively, DN 836 may be an edge DN 836, which is a (local) DN that supports an architecture for implementing edge applications. In these examples, app server 838 may represent a physical hardware system / device that provides app server functionality and / or application software that performs server functionality and resides in the cloud or at an edge computing node. In some examples, app / content server 838 provides an edge hosting environment that provides the support required for edge application server execution.

[0179] In some examples, 5GS may use one or more edge computing nodes to provide an interface and offload the processing of wireless communication services. In these examples, the edge computing nodes may be included in one or more RAN 804 or RAN nodes 814, or co-located with them. For example, the edge computing node may provide a connection between the RAN 804 and the UPF 848 in the 5GC 840. The edge computing node may use one or more NFV instances instantiated on a virtualized infrastructure within the edge computing node to handle wireless connections to and from the RAN 814 and the UPF 848.

[0180] In some implementations, the edge computing node provides a distributed computing environment for application and service hosting, and also provides storage resources and processing resources so that data and / or content can be processed in close proximity to subscribers (e.g., users of UE 802) for faster response times. The edge computing node also supports multi-tenancy runtimes and hosting environments for applications (including virtual device applications that can be delivered as encapsulated virtual machine (VM) images, middleware applications and infrastructure services, content delivery services (including content caching, mobile big data analysis, and computing offloading), etc.). Computing offloading involves: offloading computing tasks, workloads, applications, and / or services from UE 802, CN 840, DN 836, and / or servers 838 to edge computing nodes, and vice versa. For example, a device application or client application operating in UE 802 can offload application tasks or workloads to one or more edge computing nodes. In another example, an edge computing node can offload application tasks or workloads to a group of UE 802 (e.g., for distributed machine learning computing, etc.).

[0181] The edge computing node may include, or be part of, an edge system that employs one or more edge computing technologies (ECTs) (also referred to as "edge computing frameworks," etc.). The edge computing node may also be referred to as an "edge host" or "edge server." The edge system includes a collection of edge servers and edge management systems (not shown) necessary to run edge computing applications within an operator network or a subset of an operator network. An edge server is a physical computer system that may include an edge platform and / or a virtualized infrastructure and provides computing resources, storage resources, and network resources to edge computing applications. Each edge server is disposed at the edge of a corresponding access network and is arranged to provide computing resources and / or various services (e.g., computing tasks and / or workload offloading, cloud computing capabilities, IT services, and other similar resources and / or services discussed herein) in relatively close proximity to the UE 802. The VI of the edge computing node provides a virtualized environment and virtualized resources for the edge host, and the edge computing application can run on top of the VI as a VM and / or application container.

[0182] In one example implementation, the ECT is a MEC framework and / or operates according to a MEC framework, such as those discussed in: ETSI GR MEC 001 v3.1.1 (2022-01), ETSI GS MEC 003 v3.1.1 (2022-03), ETSI GSMEC 009 v3.1.1 (2021-06), ETSI GS MEC 010-1 v1.1.1 (2017-10), ETSI GS MEC 010-2 v2.2.1 (2022-02), ETSI GS MEC 011 v2.2.1 (2020-12), ETSI GS MEC 012 V2.2.1 (2022-02), ETSI GS MEC 013 V2.2.1 (2022-01), ETSI GS MEC 014v2.1.1 (2021-03), ETSI GS MEC 015v2.1.1 (2020-06), ETSI GS MEC 016v2.2.1 (2020-04), ETSI GS MEC 021v2.2.1 (2022-02), ETSI GR MEC 024v2.1.1 (2019-11), ETSI GS MEC 028v2.2.1 (2021-07), ETSI GS MEC 029v2.2.1 (2022-01), ETSI GS MEC 030v2.1.1 (2020-04) and ETSI GR MEC 031v2.1.1 (2020-10) (collectively referred to herein as "[MEC]"), the contents of each of which are hereby incorporated by reference in their entirety.This example implementation (and / or any other example implementation discussed herein) may also include NFV and / or other similar virtualization technologies, such as those discussed in: ETSI GR NFV 001 V1.3.1 (2021-03), ETSI GS NFV 002 V1.2.1 (2014-12), ETSI GR NFV 003 V1.6.1 (2021-03), ETSI GS NFV 006 V2.1.1 (2021-01), ETSI GS NFV-INF001 V1.1.1 (2015-01), ETSI GS NFV-INF 003 V1.1.1 (2014-12), ETSI GS NFV-INF004 V1.1.1 (2015-01), ETSI GS NFV-MAN 001v1.1.1 (2014-12) and / or OSM Release FIVE Technical Overview by Israel et al., ETSI Open Source MANO, OSM White Paper, 1st ed. (Jan. 2019), https: / / osm.etsi.org / images / OSM-Whitepaper-TechContent-ReleaseFIVE-FINAL.pdf (collectively referred to as “[ETSI NFV]”), the contents of each of which are hereby incorporated by reference in their entirety. Other virtualization technologies and / or service orchestration and automation platforms may be used, such as those discussed in: E2E Network Slicing Architecture, GSMA, Official Doc.NG.127, v1.0 (03Jun.2021), https: / / www.gsma.com / newsroom / wp-content / uploads / / NG.127-v1.0-2.pdf, Open Network Automation Platform (ONAP) documentation, Release Istanbul, v9.0.1 (17Feb.2022), https: / / docs.onap.org / en / latest / index.html (“[ONAP]”), 3GPP Service-Based Management Architecture (SBMA) discussed in 3GPP TS28.533 v17.1.0 (2021-12-23) (“[TS28533]”), the contents of each of which are hereby incorporated by reference in their entirety.

[0183] In another example implementation, the ECT is an ORAN framework and / or operates according to an ORAN framework. Typically, front-end and back-end equipment vendors and operators have worked closely to ensure compatibility. The flip side of this working mode is that plug-and-play with other devices becomes difficult and this can hinder innovation. To overcome this problem and promote openness and interoperability at every level, several key players interested in the wireless space (e.g., operators, equipment manufacturers, academic institutions, etc.) formed the Open RAN Alliance ("O-RAN") in 2018. The O-RAN network architecture is a building block for designing a virtualized RAN on programmable hardware, where radio access control is supported by AI / ML.Various aspects of the O-RAN architecture are described in the following: O-RAN Working Group 1 (Use Cases and Overall Architecture): O-RAN Architecture Description, O-RAN Alliance WG1, O-RAN Architecture Description v08.00, Release R003 (March 2023); O-RAN Operations and Maintenance Architecture Specification v04.00, O-RAN Alliance WG1 (February 2021); O-RAN Working Group 2 AI / ML Workflow Description and Requirements v01.03 O-RAN Alliance WG2 (October 2021); O-RAN Working Group 2 (non-RT RIC and A1 Interface WG): R1 Interface: General Aspects and Principles 4.0, v04.00, Release R003 (March 2023); O-RAN Working Group 2 (non-RT RIC and A1 Interface WG): non-RT RIC Architecture v02.01 (October 2022); O-RAN Working Group 3 (Near Real-Time RAN Intelligent Controller and E2 Interface Working Group): near-RT RIC Architecture, v04.00, Release R003 (March 2023); O-RAN Working Group 4 (Open Fronthaul Interface WG) Control, User and Synchronization Plane Specification, v11.00, Release R003 (March 2023); O-RAN Fronthaul Working Group 4 Collaborative Transport Interface Transport Control Plane Specification, v03.00 (October 2022); O-RAN Fronthaul Working Group 4 Collaborative Transport Interface Transport Management Plane Specification, v11.00, Release R003 (March 2023); O-RAN Open X-haul Transport Working Group Management Interface for Transport Network Elements, v05.00, Release R003 (March 2023); O-RAN Open Transport Working Group 9Xh aul Packet Switching Architecture and Solutions, v03.00, Release R003 (March 2023); O-RAN Open X-haul Transport Working Group Synchronized Architecture and Solutions Specification, v03.00 (October 2022); O-RAN Open X-haul Transport WG9 WDM-based Fronthaul Transport, v03.00, Release R003 (March 2023); O-RAN Operation and Maintenance Architecture, v08.00, Release R003 (March 2023); O-RAN Operation and Maintenance Interface Specification, v09.00, Release R003 (March 2023) (collectively referred to as "[O-RAN]"), the contents of each of which are hereby incorporated by reference in their entirety.

[0184] In another example implementation, the ECT is and / or operates in accordance with the 3rd Generation Partnership Project (3GPP) System Aspects Working Group 6 (SA6) architecture for implementing edge applications, as discussed in: 3GPP TS 23.558 v18.1.0 (2022-12-23) (“[TS23558]”), 3GPP TS 23.501 v18.0.0 (2022-12-21) (“[TS23501]”), 3GPP TS 23.502 v18.1.1 (2023-04-05) (“[TS23502]”), 3GPP TS 23.503 v18.1.0 (2023-04-05) (“[TS23503]”), 3GPP TS23.548v18.1.0(2023-04-06)("[TS23548]"), 3GPP TS28.538v18.2.0(2023-03-30)("[TS28538]"), 3GPP TR 23.700-98v18.0.0(2022-12-23)("[TR23700-98]"), 3GPP TS23.222v18.0.0(2022-12-23)("[TS23222]"), 3GPP TS33.122v18.0.0(2022-12-16)("[TS33122]"), 3GPP TS29.222v17.1.0(2021-06-25)("[TS29222]"), 3GPP TS29.522v18.0.0(2022-12-16)("[TS29522]"), 3GPP TS29.122v18.0.0(2022-12-16)("[TS29122]"), 3GPP TS23.682v17.3.0(2022-06-15)("[TS23682]"), 3GPP TS 23.434 v18.3.0(2022-12-23)("[TS23434]") and 3GPP TS 23.401v18.0.0 (2022-12-21) (collectively, “[SA6Edge]”), the contents of each of which are hereby incorporated by reference in their entirety.

[0185] In another example implementation, the ECT is Smart Edge Open framework (formerly known as OpenNESS) and / or operations therein, as discussed in: Smart Edge Open Developer Guide, Version 21.09 (September 30, 2021), available at: https: / / smart-edge-open.github.io / (“[ISEO]”), the contents of which are hereby incorporated by reference in their entirety.

[0186] In another example implementation, the ECT operates according to a Multiple Access Management Service (MAMS) framework, as discussed in: Multi-Access Management Services (MAMS) by Kanugovi et al., Internet Engineering Task Force (IETF), Request for Comments (RFC) 8743 (March 2020) (“[RFC8743]”), TCP Extensions for Multipath Operation with Multiple Addresses by Ford et al., IETF RFC 8684 (March 2020), Multipath Extensions for QUIC (MP-QUIC) by De Coninck et al., IETF draft-deconinck-quic-multipath-07, IETA, QUIC Working Group (May 3, 2021), User-Plane Protocols for Multiple Access Management Service by Zhu et al., IETF draft-zhu-intarea-mams-user-protocol-09, IETA, INTAREA (March 4, 2020), and Generic Protocols by Zhu et al. Multi-Access (GMA) Convergence Encapsulation Protocols, IETF RFC 9188 (February 2022) (collectively, “[MAMS]”), the contents of each of which are hereby incorporated by reference in their entirety.

[0187] It should be understood that the above edge computing framework / ECT and service deployment examples are only illustrative examples of ECT, and the present disclosure may be applicable to many other or additional edge computing / networking technologies in various combinations and layouts of devices at the edge of a network including the various edge computing networks / systems described herein. In addition, the technology disclosed herein may involve other IoT edge network systems and configurations, and other intermediate processing entities and architectures may also be applicable to the present disclosure. Examples of these edge computing / networking technologies include [MEC]; [O-RAN]; [ISEO]; [SA6Edge]; content delivery network (CDN) (also known as "content distribution network", etc.); mobility service provider (MSP) edge computing and / or mobility as a service (MaaS) provider system (e.g., used in AECC architecture); nebula edge cloud system; fog computing system; micro cloud edge cloud system; mobile cloud computing (MCC) system; central office re-architecture as data center (CORD), mobile CORD (M-CORD) and / or converged multi-access and core (COMAC) system; etc. Furthermore, the techniques disclosed herein may relate to other IoT edge network systems and configurations, and other intermediate processing entities and architectures may also be used for the purposes of the present disclosure.

[0188] The interfaces of 5GC 840 include reference points and service-based interfaces. Reference points include: N1 (between UE 802 and AMF 844), N2 (between RAN 814 and AMF 844), N3 (between RAN 814 and UPF 848), N4 (between SMF 846 and UPF 848), N5 (between PCF 856 and AF 860), N6 (between UPF 848 and DN 836), N7 (between SMF 846 and PCF 856), N8 (between UDM 858 and AMF 844), N9 (between two UPFs 848), N10 (between UDM 858 and SMF 846), N11 (between AMF 844 and SMF 846), N12 (between AUSF 842 and AMF 844), N13 (between AUSF 842 and UDM 858), N14 (between two AMFs 844; not shown), N15 (between PCF 856 and AMF 844 in the case of non-roaming scenario, or between PCF 856 and AMF 844 in the visited network in the case of roaming scenario), N16 (between two SMFs 846; not shown) and N22 (between AMF 844 and NSSF 850). Figure 8 Other reference points not shown are indicated. Figure 8The service-based representation represents the NF within the control plane that enables other authorized NFs to access its services. The service-based interfaces (SBIs) include: Namf (SBI presented by AMF 844), Nsmf (SBI presented by SMF 846), Nnef (SBI presented by NEF 852), Npcf (SBI presented by PCF 856), Nudm (SBI presented by UDM 858), Naf (SBI presented by AF 860), Nnrf (SBI presented by NRF 854), Nnssf (SBI presented by NSSF 850), Nausf (SBI presented by AUSF 842). You can also use Figure 8 Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in the figure. In some examples, NEF 852 can provide an interface to edge computing node 836x, which can be used to handle wireless connections with RAN 814.

[0189] Although Figure 8 Not shown, but the system 800a may also include NFs not shown (e.g., UDR, unstructured data storage function (UDSF), network slice admission control function (NSACF), network slice specific and independent non-public network (SNPN) authentication and authorization function (NSSAAF), UE radio capability management function (UCMF), 5G equipment identity registrar (5G-EIR), charging function (CHF), time sensitive network (TSN) AF 860, time sensitive communication and time synchronization function (TSCTSF), network data analysis function (NWDAF), data collection coordination function (DCCF), messaging framework adapter function (MFAF), analysis data repository function (ADRF), non-seamless WLAN offload function (NSWOF), service communication proxy (SCP), security edge protection proxy (SEPP), non-3GPP interworking function (N3IWF), trusted non-3GPP gateway function (TNGF), wired access gateway function (W-AGF) and / or trusted WLAN interworking function (TWIF, as discussed in [TS23501]).

[0190] Figure 8b An example reference architecture 800b for a 5GC 840 with an untrusted non-3GPP access 805 and a non-3GPP interworking function (N3IWF) 865 is shown.

[0191] The functionality of the N3IWF 865 includes support for Internet Protocol Security (IPsec) tunnel establishment with the UE 802 in the case of untrusted non-3GPP access 805. Here, the N3IWF 865 terminates the IKEv2 / IPsec protocol with the UE 802 over the NWu reference point and relays the information required to authenticate the UE 802 and authorize its access to the 5GC 840 over the N2 reference point.

[0192] The N3IWF 865 includes termination of the N2 and N3 interfaces to the 5GC 840 for the control plane and user plane, respectively. The N3IWF 865 relays uplink and downlink control plane NAS (N1) signaling between the UE 802 and the AMF 844, and processes N2 signaling from the SMF 846 (relayed by the AMF 844) related to PDU sessions and QoS. The N3IWF 865 supports the establishment of IPsec security associations (IPsec SAs) to support PDU session services. The N3IWF 865 relays uplink and downlink user plane packets between the UE 802 and the UPF 848, which involves decapsulation and encapsulation of packets for IPSec and N3 tunnels. The N3IWF 865 implements QoS corresponding to N3 packet markings, taking into account the QoS requirements associated with N3 packet markings received in the uplink via N2 and N3 user plane packet markings. N3IWF 865 also supports local mobility anchoring within untrusted non-3GPP access networks using MOBIKE as per IETF RFC 4555 and includes various functions to support the AMF selection discussed in [TS23501].

[0193] According to clause 5.30 of [TS23501], the N3IWF 865 may provide access to SNPN services via the untrusted non-3GPP access network 805. When the UE 802 registers with the SNPN using the SNPN-owned credentials, the UE 802 uses the same N3IWF selection procedure as specified in clause 6.3.6.2a of [TS23501] for accessing SNPN services via the PLMN.

[0194] UE 802 onboarding is supported as follows: When UE 802 registers to SNPN for UE onboarding via untrusted non-3GPP access 805, UE 802 may select N3IWF 865 in SNPN that supports UE onboarding by using the pre-configured N3IWF FQDN for onboarding. If PVS is reachable from a local untrusted non-3GPP access network 805 (e.g., via the Internet) using a local IP connection, UE 802 may connect directly with PVS (e.g., without connecting to N3WIF 865) to obtain SNPN credentials. Additional aspects related to N3WIF 865 are discussed in [TS23501].

[0195] The network 800b also includes a Y1 reference point between the UE 802 and the untrusted non-3GPP access 805 (e.g., WLAN, etc.). This reference point is based on non-3GPP access technology. The network 800b also includes a Y2 reference point between the untrusted non-3GPP access 805 and the N3IWF865 for transmitting NWu services. The network 800b also includes a NWu reference point between the UE 802 and the N3IWF 865 for establishing a secure tunnel between the UE 802 and the N3IWF 865, so that the control plane and user plane exchanged between the UE 802 and the 5GC 840 are securely transmitted through the untrusted non-3GPP access 805.

[0196] Fig. 9 A wireless network 900 is schematically shown. The wireless network 900 includes a UE 902 that wirelessly communicates with a NAN 904. The UE 902 can be the same or similar to any other UE discussed herein (e.g., UE 802, hardware resources 1000, and / or any other UE discussed herein), and is substantially interchangeable. The AN 904 can be the same or similar to any AN (network access node (NAN)) discussed herein (e.g., AP 806, NAN 814, RAN 804, hardware resources 1000, and / or any other AN / NAN discussed herein), and is substantially interchangeable.

[0197] UE 902 may be communicatively coupled to AN 904 via connection 906. Connection 906 is shown as an air interface for implementing the communicatively coupling and may conform to a cellular communication protocol (e.g., an LTE protocol or a 5G NR protocol operating at mmWave or sub-6 GHz frequencies).

[0198] UE 902 includes a host platform 908, which is coupled to a modem platform 910. The host platform 908 includes an application processing circuit 912, which can be coupled to a protocol processing circuit 914 of the modem platform 910. The application processing circuit 912 can run various applications for giving / absorbing application data for the UE 902. The application processing circuit 912 can also implement one or more layer operations to send / receive application data to / from a data network. These layer operations include transport (e.g., UDP) and Internet (e.g., IP) operations.

[0199] The protocol processing circuitry 914 may implement one or more layer operations to facilitate sending or receiving data over the connection 906. The layer operations implemented by the protocol processing circuitry 914 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0200] The modem platform 910 may also include digital baseband circuitry 916, which may implement one or more layer operations that are "lower" layer operations in the network protocol stack performed by the protocol processing circuitry 914. These operations include, for example, PHY operations, which include one or more of the following: HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding (which may include one or more of space-time, space-frequency, or space coding), reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions.

[0201] The modem platform 910 may also include a transmit circuit 918, a receive circuit 920, an RF circuit 922, and an RF front end (RFFE) 924 (which may include or be connected to one or more antenna panels 926). In brief, the transmit circuit 918 includes a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc.; the receive circuit 920 includes an analog-to-digital converter, a mixer, an IF component, etc.; the RF circuit 922 includes a low noise amplifier, a power amplifier, a power tracking component, etc.; the RFFE 924 includes a filter (e.g., a surface / bulk acoustic wave filter), a switch, an antenna tuner, a beamforming component (e.g., a phased array antenna component), etc. The selection and arrangement of the components of the transmit circuit 918, the receive circuit 920, the RF circuit 922, the RFFE 924, and the antenna panel 926 (generally referred to as "transmit / receive components" or "Tx / Rx components") may be specific to the details of a particular implementation (e.g., whether the communication is TDM or FDM, in mmWave or sub-6gHz frequencies, etc.). In some examples, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be provided in the same or different chips / modules, etc.

[0202] In some examples, protocol processing circuitry 914 includes one or more instances of control circuitry (not shown) to provide control functionality for the transmit / receive components.

[0203] UE reception may be established by and via antenna panel 926, RFFE 924, RF circuitry 922, receive circuitry 920, digital baseband circuitry 916, and protocol processing circuitry 914. In some examples, antenna panel 926 may receive transmissions from AN 904 via receive beamformed signals received by a set of antennas / antenna elements of one or more antenna panels 926.

[0204] UE transmission can be established by and via protocol processing circuitry 914, digital baseband circuitry 916, transmit circuitry 918, RF circuitry 922, RFFE 924, and antenna panel 926. In some examples, the transmit component of UE 904 can apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of antenna panel 926.

[0205] Similar to UE 902, AN 904 includes a host platform 928, which is coupled to a modem platform 930. The host platform 928 includes an application processing circuit 932, which is coupled to a protocol processing circuit 934 of the modem platform 930. The modem platform may also include a digital baseband circuit 936, a transmit circuit 938, a receive circuit 940, an RF circuit 942, an RFFE circuit 944, and an antenna panel 946. The components of AN 904 may be similar to the components of the same name of UE 902 and are substantially interchangeable. In addition to performing data transmission / reception as described above, the components of AN 908 may also perform various logical functions, including, for example, RNC functions (e.g., radio bearer management, UL and DL dynamic radio resource management, and data packet scheduling).

[0206] Examples of antenna elements of antenna panel 926 and / or antenna elements of antenna panel 946 include a planar inverted-F antenna (PIFA), a monopole antenna, a dipole antenna, a loop antenna, a patch antenna, a Yagi antenna, a parabolic dish antenna, an omnidirectional antenna, etc.

[0207] Fig.10 Components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and executing any one or more of the methods discussed herein are shown. Specifically, Fig.10A diagrammatic representation of hardware resources 1000 is shown, including one or more processors (or processor cores) 1010, one or more memory / storage devices 1020, and one or more communication resources 1030, each of which may be communicatively coupled via a bus 1040 or other interface circuitry. For examples utilizing node virtualization (e.g., NFV), a hypervisor 1002 may be executed to provide an execution environment for one or more network slices / subslices to utilize hardware resources 1000.

[0208] Processor 1010 may include, for example, processor 1012 and processor 1014. Processor 1010 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP (e.g., a baseband processor), an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0209] The memory / storage device 1020 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1020 may include, but is not limited to, any type of volatile, non-volatile, or semi-volatile memory (e.g., dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.).

[0210] The communication resources 1030 may include interconnect or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1004 or one or more databases 1006 or other network elements via the network 1008. For example, the communication resources 1030 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, (or low power consumption ) components, components and other communication components.

[0211] The instructions 1050 may include software, programs, applications, applet, apps, or other executable code for causing at least any processor 1010 to perform any one or more of the methods discussed herein. The instructions 1050 may reside in whole or in part in at least one of the processor 1010 (e.g., within a cache memory of the processor), the memory / storage device 1020, or any suitable combination thereof. In addition, any portion of the instructions 1050 may be transmitted to the hardware resources 1000 from any combination of the peripheral device 1004 or the database 1006. Therefore, the memory of the processor 1010, the memory / storage device 1020, the peripheral device 1004, and the database 1006 are examples of computer-readable and machine-readable media.

[0212] 3. Example Implementation

[0213] Fig.11 An example process to be performed by UE 802 is shown. Fig.11 The process includes: identifying an indication that the UE 802 is authorized to access the localized service based on a message sent from the LSP 150 (1101); and accessing the localized service 155 based on the indication (1102).

[0214] Fig.12 An example process to be performed by LSP 150 is shown. Fig.12 The process includes: receiving a request related to authorizing UE 802 to access localization service 155 (1201); and sending an indication of authorization of UE 802 (1202).

[0215] Fig.13 Another example process to be performed by UE 802 is shown. Fig.13 The process includes: identifying a time-limited and / or time-limited credential associated with a localized service provider of an NPN different from the home network 120 of the UE 802 (1301); and accessing services of the NPN based on the credential (1302).

[0216] Additional examples of the presently described methods, devices, systems, and networks discussed herein include the following non-limiting example implementations. Each of the following non-limiting examples may exist independently or may be combined with any one or more other examples provided below or throughout the present disclosure in any permutation or combination.

[0217] Example 1 includes: A method for authentication and authorization of a localization service.

[0218] Example 2 includes: a method as described in Example 1 and / or some other examples herein, wherein the localization service provider (LSP) acts as an AKMA application function (AF).

[0219] Example 3 includes: a method as described in Examples 1-2 and / or some other examples herein, wherein the role played by the LSP server middleware is the IoT server middleware described in Clause 3 of [GSMAIoT.04].

[0220] Example 4 includes: the method as described in Example 2 and / or some other examples herein, wherein K AKMA The key is used as an anchor key to generate KLSP-PSK for mutual authentication between the UE and the hosting network, where the LSP acts as the credential holder.

[0221] Example 5 may include a method as described in Example 3 and / or some other examples herein, wherein the client certificate and the security profile are downloaded from the LSP to the UE.

[0222] Example 6 includes: a method as described in Example 5 and / or some other examples herein, wherein the security profile is used to enable mutual authentication between the UE and the hosting network to provide the UE with access to localized services.

[0223] Example 7 includes: a method to be performed by a user equipment (UE), one or more elements of a UE, or an electronic device that includes and / or implements a UE, wherein the method includes: identifying an indication authorizing the UE to access a localized service based on a message sent from a localized service provider (LSP); and accessing the localized service by the UE based on the indication.

[0224] Example 8 includes: a method as described in Example 7 and / or some other examples herein, wherein the indication is related to the functionality of AKMA AF.

[0225] Example 9 includes: a method as described in Examples 7-8 and / or any other examples herein, wherein the LSP is used at least in part as an AKMA AF.

[0226] Example 10 includes: a method as described in any of Examples 7-9 and / or some other examples herein, wherein the authorization is associated with an AKMA key.

[0227] Example 11 includes: a method as described in any of Examples 7-10 and / or some other examples herein, wherein the indication is related to authorization performed by the IoT server middleware.

[0228] Example 12 includes: a method as described in Example 7 or 11 and / or any other example herein, wherein the LSP is used at least in part as IoT server middleware.

[0229] Example 13 includes: a method to be performed by a localization service provider (LSP), one or more elements of the LSP, and / or an electronic device that implements or includes the LSP, wherein the method includes: receiving a request for authorizing a user equipment (UE) to access localization services; and sending an indication of the UE's authorization.

[0230] Example 14 includes: a method as described in Example 13 and / or some other examples herein, wherein the indication is related to the functionality of the AKMAAF.

[0231] Example 15 includes: a method as described in Examples 13-14 and / or any other examples herein, wherein the LSP is used at least in part as an AKMA AF.

[0232] Example 16 includes: a method as described in any of Examples 13-15 and / or some other examples herein, wherein the authorization is associated with an AKMA key.

[0233] Example 17 includes: a method as described in any of Examples 13-16 and / or some other examples herein, wherein the indication is related to authorization performed by the IoT server middleware.

[0234] Example 18 includes: a method as described in any of Examples 13 or 17 and / or some other examples herein, wherein the LSP is used at least in part as IoT server middleware.

[0235] Example 19 includes: A method for a UE to access a localized service using a time-limited / time-limited credential.

[0236] Example 20 includes the method of Example 19 and / or some other examples herein, wherein the home network obtains a time-limited credential from a localized service provider providing the service.

[0237] Example 21 includes: a method as described in Example 20 and / or some other examples herein, wherein the time-limited credentials include, for example, the SNPN ID and geographic coordinates of the hosted network, a user ID and security credentials for accessing the home network, a user ID and security credentials for accessing an LSP server providing localized services, and a DNN / S-NSSAI for establishing a PDU session in the hosted network with optional credentials with the aid of secondary authentication.

[0238] Example 22 includes: a method as described in Example 21 and / or some other examples herein, wherein the UE is connected to a hosted network and is authenticated by an LSP in the role of a credential holder based on a user id and security credentials (e.g., using an authentication, authorization, and accounting (AAA) server) for accessing a home network.

[0239] Example 23 includes: a method to be performed by a user equipment (UE) in a cellular network, one or more elements of the UE, and / or an electronic device including the UE, wherein the method includes: identifying a time-limited and / or time-limited credential associated with a localized service provider of a non-public network (NPN) that is different from the home network of UE 802; and based on the credential, accessing services of the NPN.

[0240] Example 24 includes: a method as described in Example 23 and / or some other examples herein, wherein the credentials are provided by a home network of UE 802.

[0241] Example 25 includes: a method as described in any of Examples 23-24 and / or some other examples herein, wherein the credentials include one or more of: an SNPN ID of the NPN, geographic coordinates of the hosted network, a user ID and security credentials for accessing the home network, a user ID and security credentials for accessing an LSP server providing localized services, and / or a DNN / S-NSSAI for establishing a PDU session in the hosted network with optional credentials with the aid of secondary authentication.

[0242] Example Z01 may include an apparatus comprising means for performing one or more elements of a method described in or related to any of Examples 1-25, or any other method or process described herein.

[0243] Example Z02 may include one or more non-transitory computer-readable media, including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of Examples 1-25, or any other method or process described herein.

[0244] Example Z03 may include an apparatus comprising logic, modules, or circuits for performing one or more elements of a method described in or related to any of Examples 1-25, or any other method or process described herein.

[0245] Example Z04 may include methods, techniques, or processes as described in or related to any of Examples 1-25, or portions or sections thereof.

[0246] Example Z05 may include a device comprising: one or more processors and one or more computer-readable media, the media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in or related to any one or portion of Examples 1-25.

[0247] Example Z06 may include signals as described in or related to any of Examples 1-25, or portions or sections thereof.

[0248] Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of Examples 1-25 or a portion or section thereof or otherwise described in the present disclosure.

[0249] Example Z08 may include a signal encoded with data as described in or related to any of Examples 1-25, or a portion or section thereof, or otherwise described in this disclosure.

[0250] Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of Examples 1-25 or a portion or section thereof or otherwise described in the present disclosure.

[0251] Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein one or more processors execute the computer-readable instructions to cause the one or more processors to perform a method, technique, or process described in or related to any one or a portion thereof of Examples 1-25.

[0252] Example Z11 may include a computer program including instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process described in or related to any one of Examples 1-25 or a portion thereof.

[0253] Example Z12 may include a signal in a wireless network as shown and described herein.

[0254] Example Z13 may include a method of communicating in a wireless network as shown and described herein.

[0255] Example Z14 may include a system for providing wireless communications as shown and described herein.

[0256] Example Z15 may include an apparatus for providing wireless communications as shown and described herein.

[0257] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be obtained from the practice of the various embodiments.

[0258] 4. Terminology

[0259] For the purposes of this document, the following terms and definitions apply to the examples and embodiments discussed herein. As used herein, the singular forms "a", "an", and "the" are also intended to include the plural forms, unless the context clearly indicates otherwise. It will be further understood that the terms "comprise" and / or "comprising" when used in this specification specifically refer to the presence of the claimed features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. The phrase "A and / or B" means (A), (B), or (A and B). For the purposes of this disclosure, the phrase "A, B, and / or C" means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C). The phrase "X" means one or more X or a set of X. The description may use the phrases "in an embodiment", "in some embodiments", "in one implementation", "in some implementations", "in some examples", etc., each of which may refer to one or more of the same or different embodiments, implementations, and / or examples. Furthermore, the terms "comprising," "including," "having," and the like used in connection with the present disclosure are synonymous.

[0260] The terms "master" and "slave" refer, at least in some examples, to a model of asymmetric communication or control, in which one device, process, element or entity ("master") controls one or more other devices, processes, elements or entities ("slaves"). The terms "master" and "slave" are used in this disclosure only for their technical meanings. The terms "master" or "grandmaster" may be replaced by any of the following terms "main", "source", "primary", "initiator", "requestor", "transmitter", "host", "maestro", "controller", "provider", "producer", "client", "source", "mix", "parent", "chief", "mannager", "reference" (e.g., as in "reference clock", etc.), etc. Additionally, the term "slave" may be replaced with any of the following terms: "receiver", "secondary", "subordinate", "replica", "target", "responder", "device", "performer", "agent", "standby", "consumer", "peripheral", "follower", "server", "child", "helper", "worker", "node", etc.

[0261] The terms "coupled", "coupled in a communicative manner", and their derivatives are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between elements referred to as being coupled to each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "coupled in a communicative manner" may mean that two or more elements may contact each other by communication (including by wired or other interconnection connection, by wireless communication channels or links, etc.).

[0262] The term "establish" or "establishment" refers, at least in some examples (partially or completely), to an action, task, operation, etc. (e.g., opening a device identity or an entity identity) related to actively or passively playing or preparing to play something. Additionally or alternatively, the term "establish" or "establishment" refers, at least in some examples (partially or completely), to an action, task, operation, etc. (e.g., establishing a session, establishing a session, etc.) related to initiating, starting or preheating a communication or initiating, starting or preheating a relationship between two entities or elements. Additionally or alternatively, the term "establish" or "establishment" refers, at least in some examples, to initiating something to enter a working ready state. The term "established" refers, at least in some examples, to an operational or ready-to-use state (e.g., fully established). In addition, any definition of the term "establish" or "establishment" defined in any specification or standard may be used for the purposes of this disclosure, and these definitions are not overturned by the aforementioned definitions.

[0263] The term "obtain" refers, at least in some examples (partially or completely), to an action, task, operation, etc. of intercepting, moving, copying, retrieving, or acquiring (e.g., from memory, an interface, or a buffer) on an original packet stream or on a copy (e.g., a new instance) of a packet stream. Other aspects of obtaining or receiving may involve: instantiating, implementing, or controlling capabilities for obtaining or receiving a packet stream (or the following parameters and templates or template values).

[0264] The term "receive" refers, at least in some examples, to any action (or set of actions) related to receiving or obtaining an object, data, data unit, etc. and / or the fact of receiving an object, data, data unit, etc. The term "receive" refers, at least in some examples, to an object, data, data unit, etc. being pushed to a device, system, element, etc. (e.g., generally referred to as a push model), being pulled by a device, system, element, etc. (e.g., generally referred to as a pull model), etc.

[0265] The term "element" refers, at least in some examples, to a unit that is indivisible and has well-defined boundaries at a given level of abstraction, wherein an element may be any type of entity, including, for example, one or more devices, systems, controllers, network elements, modules, engines, components, etc., or combinations thereof. The term "entity" refers, at least in some examples, to a unique element of a component, architecture, platform, device, and / or system. Additionally or alternatively, the term "entity" refers, at least in some examples, to information transmitted as a payload.

[0266] The term "measurement" refers to the observation and / or quantification of the properties of an object, event or phenomenon in at least some examples. Additionally or alternatively, the term "measurement" refers to an actual instance or set of operations performed with an object that determines a measured value or measurement result and / or an operation that causes a measured value in at least some examples. Additionally or alternatively, the term "measurement" refers to data recorded during testing in at least some examples. The term "metric" refers to a quantity generated in the evaluation of the measured value in at least some examples. Additionally or alternatively, the term "metric" refers to data derived from a measurement set in at least some examples. Additionally or alternatively, the term "metric" refers to a set of events that are combined or otherwise grouped into one or more values ​​in at least some examples. Additionally or alternatively, the term "metric" refers to a combination of measurements or a set of collected data points in at least some examples. Additionally or alternatively, the term "metric" refers to a standard definition of a quantity generated in the evaluation of the performance and / or reliability of a network in at least some examples, which has an expected practicality and is carefully specified to convey the exact meaning of the measured value.

[0267] The term "signal" refers, at least in some examples, to an observable change in quality and / or quantity. Additionally or alternatively, the term "signal" refers, at least in some examples, to a function of conveying information about an object, event, or phenomenon. Additionally or alternatively, the term "signal" refers, at least in some examples, to any time-varying voltage, current, or electromagnetic wave that may or may not carry information. The term "digital signal" refers, at least in some examples, to a signal consisting of a collection of discrete waveforms of physical quantities so as to represent a sequence of discrete values.

[0268] The terms "self" (as in, for example, "self device") and "subject" (as in, for example, "data subject"), at least in some examples, refer to an entity, element, device, system, etc. to be considered or being considered. The terms "neighbor" and "neighboring" (as in, for example, "neighboring device"), at least in some examples, refer to an entity, element, device, system, etc. other than the self device or subject device.

[0269] The term "identifier" refers to a value or set of values ​​that uniquely identifies an identity within a specific range, at least in some examples. Additionally or alternatively, the term "identifier" refers to a character sequence that identifies or otherwise indicates the identity of a unique object, element or entity or a unique class of an object, element or entity, at least in some examples. Additionally or alternatively, the term "identifier" refers to a character sequence used to identify or reference an application, program, session, object, element, entity, variable, data set, etc., at least in some examples. The aforementioned "character sequence" refers to one or more names, labels, words, numbers, letters, symbols and / or any combination thereof, at least in some examples. Additionally or alternatively, the term "identifier" refers to a name, address, label, distinguishing index and / or attribute, at least in some examples. Additionally or alternatively, the term "identifier" refers to an instance of an identification, at least in some examples. The term "permanent identifier" refers to an identifier that is reused by a device or another device associated with the same person or a group of people for an indefinite period of time, at least in some examples. The term "identification" refers, at least in some examples, to the process of identifying an identity that is distinct from other identities in a particular scope or context, which may involve processing an identifier to reference an identity in an identity database. The term "application identifier," "application ID," or "app ID" refers, at least in some examples, to an identifier that can be mapped to a particular application, application instance, or application instance. In the context of 3GPP 5G / NR, an "application identifier" refers, at least in some examples, to an identifier that can be mapped to a particular application traffic detection rule.

[0270] The term "circuit" refers to a circuit or a system of multiple circuits configured to perform a specific function in an electronic device, at least in some examples. A circuit or a system of circuits may be part of or include one or more hardware components (e.g., logic circuits, processors (shared, dedicated or group) and / or memories (shared, dedicated or group), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), programmable logic controllers (PLCs), single board computers (SBCs), systems on chips (SoCs), systems in packages (SiPs), multi-chip packages (MCPs), digital signal processors (DSPs), etc.) configured to provide the described functions. In addition, the term "circuit" may also refer to a combination of one or more hardware elements and the program code that perform the functions of a program code. Some types of circuits may execute one or more software or firmware programs to provide at least some of the described functions. This combination of hardware elements and program code may be referred to as a specific type of circuit.

[0271] The term "processor circuitry" refers, at least in some examples, to, is a part of, or includes circuitry that is capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, and / or transmitting digital data. The term "processor circuitry" refers, at least in some examples, to one or more application processors, one or more baseband processors, a physical CPU, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions (e.g., program code, software modules, and / or functional processes). The terms "application circuitry" and / or "baseband circuitry" may be considered synonymous with and may be referred to as "processor circuitry."

[0272] The terms "memory" and / or "memory circuit" refer, at least in some examples, to one or more hardware devices for storing data, including random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), magnetoresistive RAM (MRAM), conductive bridge random access memory (CB-RAM), spin transfer torque (STT)-MRAM, phase change RAM (PRAM), core memory, read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrical EPROM (EEPROM), flash memory, non-volatile RAM (NVRAM), magnetic disk storage media, optical storage media, flash memory devices, or other machine-readable media for storing data. The term "computer-readable medium" includes, but is not limited to, memory, portable or fixed storage devices, optical storage devices, and various other media capable of storing, containing or carrying instructions or data.

[0273] The term "interface circuitry" refers, at least in some examples, to, is a part of, or includes circuitry that enables information to be exchanged between two or more components or devices. The term "interface circuitry" refers, at least in some examples, to one or more hardware interfaces (e.g., a bus, an I / O interface, a peripheral component interface, a network interface card, etc.).

[0274] The term "infrastructure processing unit" or "IPU" refers, at least in some examples, to an advanced network device with hardened accelerators and network connectivity (e.g., Ethernet, etc.) that accelerate and manage infrastructure functions using tightly coupled, dedicated programmable cores. In some implementations, the IPU provides full infrastructure offload and provides an additional layer of security by acting as a control point for hosts running infrastructure applications. The IPU is able to offload the entire infrastructure stack from the host and can control how the host attaches to the infrastructure. This gives the service provider an additional layer of security and control implemented in hardware by the IPU.

[0275] The term "device" refers, at least in some examples, to a physical entity that is embedded internally or attached to another physical entity in its vicinity, with the ability to communicate digital information from or to the physical entity. The term "controller" refers, at least in some examples, to an element or entity that has the ability to affect a physical entity, such as by changing its state or moving the physical entity. The term "scheduler" refers, at least in some examples, to an entity or element that allocates resources (e.g., processor time, network link, memory space, etc.) to perform a task. The term "network scheduler" refers, at least in some examples, to a node, element, or entity that manages network packets in the send and / or receive queues of one or more protocol stacks of a network access circuit (e.g., a network interface controller (NIC), a baseband processor, etc.). The term "network scheduler" can be used interchangeably with the terms "packet scheduler", "queuing order" or "qdisc" and / or "queuing algorithm" at least in some examples.

[0276] The term "terminal" refers, at least in some examples, to a point where a conductor from a component, device, or network ends. Additionally or alternatively, the term "terminal" refers, at least in some examples, to an electrical connector that acts as an interface to a conductor and creates a point to which an external circuit can be connected. In some examples, a terminal can include an electrical lead, an electrical connector, an electrical connector, a solder cup or barrel, and the like.

[0277] The term "computing node" or "computing device" refers, at least in some examples, to an identifiable entity that implements aspects of computing operations, whether part of a larger system, a collection of distributed systems, or a stand-alone device. In some examples, a computing node may be referred to as a "computing device," "computing system," etc., whether operating as a client, server, or intermediate entity. Specific implementations of computing nodes may be incorporated into servers, base stations, gateways, roadside units, residential units, user equipment, end consumer devices, appliances, etc. For purposes of this disclosure, the term "node" refers, at least in some examples, to and / or may be interchangeable with the terms "device," "component," "subsystem," etc.

[0278] The term "computer system" refers, at least in some examples, to any type of interconnected electronic device, computer device, or components thereof. Additionally, the terms "computer system" and / or "system" refer, at least in some examples, to various components of a computer that are communicatively coupled to one another. Furthermore, the terms "computer system" and / or "system" refer, at least in some examples, to multiple computer devices and / or multiple computing systems that are communicatively coupled to one another and configured to share computing and / or networking resources.

[0279] The term "server" refers to a computing device or system including processing hardware and / or processing space, associated storage media (e.g., storage devices or databases), and suitable applications known in the art in some cases, at least in some examples. The terms "server system" and "server" can be used interchangeably herein, and these terms refer to one or more computing systems that provide access to physical and / or virtual resource pools, at least in some examples. The various servers discussed herein include computer devices having rack-mounted computing architecture components, tower computing architecture components, blade computing architecture components, etc. A server can represent a server cluster, a server farm, a cloud computing service, or other server group or pool that can be located in one or more data centers. The server can also be connected to one or more data storage devices (not shown) or otherwise associated therewith. In addition, the server includes an operating system (OS), which provides executable program instructions for general management and operation of a separate server computer device, and includes a computer-readable medium storing instructions, which, when executed by a processor of the server, can allow the server to perform its intended function. Suitable implementations of the OS and general functions of the server are known or commercially available, and can be easily implemented by a person of ordinary skill in the art.

[0280] The term "platform" refers, at least in some examples, to an environment in which instructions, program codes, software elements, and the like can be executed or otherwise operated, examples of which include an architecture (e.g., a motherboard, a computing system, etc.), one or more hardware elements (e.g., an embedded system, etc.), a cluster of computing nodes, a distributed collection of computing nodes or a network, an operating system, a virtual machine (VM), a virtualization container, a software framework, a client application (e.g., a web browser, etc.) and associated application programming interfaces, cloud computing services (e.g., platform as a service (PaaS)), or other underlying software that executes instructions, program codes, software elements, and the like.

[0281] The term "architecture" refers, at least in some examples, to computer architecture or network architecture. "Computer architecture" refers, at least in some examples, to the physical and logical design or arrangement of software and / or hardware elements in a computing system or platform, including technical standards for interaction therebetween. The term "network architecture" refers, at least in some examples, to the physical and logical design or arrangement of software and / or hardware elements in a network, including communication protocols, interfaces, and media transports.

[0282] The terms "appliance", "computer appliance", etc. refer, at least in some examples, to a computer device or computer system with program code (e.g., software or firmware) specifically designed to provide specific computing resources. The term "virtual device" refers, at least in some examples, to a virtual machine image to be implemented by a device equipped with a hypervisor that virtualizes or emulates a computer appliance or is otherwise dedicated to providing specific computing resources. The terms "security appliance", "firewall", etc. refer, at least in some examples, to a computer appliance designed to protect a computer network from unwanted business and / or malicious attacks. The term "policy appliance" refers, at least in some examples, to a technical control and logging mechanism for implementing or coordinating policy rules (information usage rules) and ensuring accountability in information systems. The term "gateway" refers, at least in some examples, to a network appliance that allows data to flow from one network to another or a computing system or application configured to perform these tasks. Examples of gateways include IP gateways, Internet to Rail (I2O) gateways, IoT gateways, cloud storage gateways, etc.

[0283] The term "user equipment" or "UE" in some examples refers to a device with radio communication capabilities and can describe a remote user of network resources in a communication network. The term "user equipment" or "UE" can be considered synonymous with and can be referred to as a client, mobile, mobile device, mobile terminal, user terminal, mobile unit, station, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio device, reconfigurable radio device, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" includes any type of wireless / wired device or any computing device that includes a wireless communication interface. Examples of UE, client device, etc. include desktop computers, workstations, laptop computers, mobile data terminals, smart phones, tablet computers, wearable devices, machine-to-machine (M2M) devices, machine type communication (MTC) devices, Internet of Things (IoT) devices, embedded systems, sensors, self-driving cars, drones, robots, in-vehicle infotainment systems, dashboards, onboard diagnostic devices, dashboard mobile devices, electronic engine management systems, electronic / engine control units / modules, microcontrollers, control modules, server devices, network appliances, head-up display (HUD) devices, helmet-mounted display devices, augmented reality (AR) devices, virtual reality (VR) devices, mixed reality (MR) devices, and / or other similar systems or devices. The term "station" or "STA" refers, at least in some examples, to a logical entity that is a separately addressable instance of a medium access control (MAC) and physical layer (PHY) interface to a wireless medium (WM). The term "wireless medium" or "WM" refers, at least in some examples, to the medium used to enable transmission of protocol data units (PDUs) between peer physical layer (PHY) entities of a wireless local area network (LAN).

[0284] The term "network element" refers to a physical or virtualized device and / or infrastructure used to provide wired or wireless communication network services in at least some examples. The term "network element" may be considered synonymous with and / or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, network access node (NAN), base station, access point (AP), RAN equipment, RAN node, gateway, server, network appliance, network function (NF), virtualized NF (VNF), etc. The term "network controller" refers to a functional block that centralizes some or all control and management functions of a network domain and can provide an abstract view of the network domain to other functional blocks via an interface in at least some examples. The term "network access node" or "NAN" refers to a network element in a radio access network (RAN) that is responsible for sending and receiving radio signals to or from a UE or station in one or more cells or coverage areas. A "network access node" or "NAN" may have an integrated antenna or may be connected to an antenna array via a feeder cable. Additionally or alternatively, a "network access node" or "NAN" includes dedicated digital signal processing, network function hardware and / or computing hardware to operate as a computing node. In some examples, for flexibility, cost and performance, a "network access node" or "NAN" can be split into multiple functional blocks that operate in software. In some examples, a "network access node" or "NAN" can be a base station (e.g., an evolved Node B (eNB) or a next generation Node B (gNB)), an access point and / or a wireless network access point, a router, a switch, a hub, a radio unit or a remote radio head, a transmit receive point (TRxP), a gateway device (e.g., a residential gateway, a wired 5G access network, a wired 5G cable access network, a wired BBF access network, etc.), a network appliance and / or some other network access hardware. The term "access point" or "AP" refers to an entity that includes a station (STA) and provides access to distribution services to associated STAs via a wireless medium (WM), at least in some examples. The AP includes a STA and a distribution system access function (DSAF).

[0285] The term "cell" refers, at least in some examples, to a radio network object that can be uniquely identified by a UE according to an identifier (e.g., a cell ID) broadcast over a geographic area from a network access node (NAN). Additionally or alternatively, the term "cell" refers, at least in some examples, to a geographic area covered by a NAN. The term "serving cell" refers, at least in some examples, to a primary cell (PCell) for a UE that is in a connected mode or state (e.g., RRC_CONNECTED) and is not configured with carrier aggregation (CA) and / or dual connectivity (DC). Additionally or alternatively, the term "serving cell" refers, at least in some examples, to a UE that is in a connected mode or state (e.g., RRC_CONNECTED) and is configured with CA, to a group of cells including zero or more special cells and one or more secondary cells. The term "primary cell" or "PCell" refers, at least in some examples, to a primary cell group (MCG) cell operating on a primary frequency, in which the UE performs an initial connection establishment procedure or initiates a connection reestablishment procedure. The term "secondary cell" or "SCell", at least in some examples, for a UE configured with CA, refers to a cell that provides additional radio resources in addition to a special cell (SpCell). The term "special cell" or "SpCell", at least in some examples, refers to a PCell for non-DC operation, or a PCell of an MCG or a PSCell of an SCG for DC operation. The term "primary cell group" or "MCG", at least in some examples, refers to a group of service cells associated with a "master node" that includes a SpCell (PCell) and optionally one or more SCells. The term "secondary cell group" or "SCG", at least in some examples, for a UE configured with DC, refers to a subset of service cells that includes a primary SCell (PSCell) and zero or more SCells. The term "primary SCG cell", for DC operation, refers to an SCG cell to which a UE performs random access when performing a reconfiguration with a synchronization process. The term "handover", at least in some examples, refers to transferring a user's connection from one radio channel to another (which may be the same or a different cell). Additionally or alternatively, the term "handover" refers, at least in some examples, to a process by which a radio access network changes radio transmitters, radio access modes and / or radio systems used to provide a bearer service while maintaining a defined bearer service QoS.

[0286] The term "primary node" or "MN" refers, at least in some examples, to a NAN that provides a control plane connection to a core network. The term "secondary node" or "SN" refers, at least in some examples, to a NAN that provides resources to a UE in addition to the resources provided by the MN and / or NAN without a control plane connection to the core network. The term "E-UTEAN NodeB", "eNodeB" or "eNB" refers, at least in some examples, to a RAN node that provides E-UTRA user plane (e.g., PDCP, RLC, MAC, PHY) and control plane (e.g., RRC) protocol terminations toward a UE and is connected to an evolved packet core (EPC) via an S1 interface. Two or more eNBs are interconnected with each other (and / or with one or more en-gNBs) by means of an X2 interface. The term "next generation eNB" or "ng-eNB" refers, at least in some examples, to a RAN node that provides E-UTRA user plane and control plane protocol terminations toward a UE and is connected to a 5GC via an NG interface. Two or more ng-eNBs are interconnected with each other (and / or with one or more gNBs) by means of an Xn interface. The term "Next Generation Node B", "gNodeB" or "gNB" refers, at least in some examples, to a RAN node that provides NR user plane and control plane protocol termination towards the UE and is connected to the 5GC via an NG interface. Two or more gNBs are interconnected with each other (and / or with one or more ng-eNBs) by means of an Xn interface. The term "E-UTRA-NR gNB" or "en-gNB" refers, at least in some examples, to a RAN node that provides NR user plane and control plane protocol termination towards the UE and acts as a secondary node in an E-UTRA-NR dual connectivity (EN-DC) scenario (see, for example, 3GPP TS 37.340 v17.0.0 (2022-04-15) ("[TS37340]")). Two or more en-gNBs are interconnected with each other (and / or with one or more eNBs) by means of an X2 interface.

[0287] The term "next generation RAN node" or "NG-RAN node" refers to a gNB or ng-eNB in ​​at least some examples. The term "IAB node" refers to a RAN node that supports a new radio (NR) access link to a user equipment (UE) and an NR backhaul link to a parent node and a child node in at least some examples. The term "IAB donor" refers to a RAN node (e.g., a gNB) that provides network access to a UE via a network of backhaul and access links in at least some examples. The term "transmit receive point" or "TRxP" refers to an antenna array having one or more antenna elements that can be used by a network located at a specific geographic location in a specific area in at least some examples. The term "central unit" or "CU" refers to a logical node of the RRC and PDCP protocols of an en-gNB that hosts the radio resource control (RRC), service data adaptation protocol (SDAP), and / or packet data convergence protocol (PDCP) protocols / layers of a NG-RAN node, or controls the operation of one or more DUs; the CU terminates the F1 interface connected to the DU and can be connected to multiple DUs. The term "distributed unit" or "DU" refers, at least in some examples, to a logical node hosting the Backhaul Adaptation Protocol (BAP), F1 Application Protocol (F1AP), Radio Link Control (RLC), Medium Access Control (MAC), and Physical (PHY) layers of an NG-RAN node or en-gNB, whose operations are partially controlled by the CU; one DU supports one or more cells, and one cell is supported by only one DU; and the DU terminates the F1 interface connected to the CU. The term "radio unit" or "RU" refers, at least in some examples, to a logical node hosting the PHY layer or Low-PHY layer and the radio frequency (RF) processing based on the split of lower layer functions. The term "split architecture" refers, at least in some examples, to an architecture in which the CU, DU, and / or RU are physically separated from each other. Additionally or alternatively, the term "split architecture" refers, at least in some examples, to a RAN architecture such as the architecture discussed in 3GPP TS 38.401 v17.4.0 (2023-04-03) ("[TS38401]"), 3GPP TS 38.410 v 17.1.0 (2022-06-23), and 3GPP TS 38.473 v17.4.1 (2023-04-05) ("[TS38473]"), the contents of each of which are hereby incorporated by reference in their entirety. The term "integrated architecture" refers, at least in some examples, to an architecture in which the RU and DU are implemented on one platform and / or an architecture in which the DU and CU are implemented on one platform.

[0288] The term "residential gateway" or "RG" refers, at least in some examples, to a device that provides, for example, voice, data, broadcast video, video on demand, etc. to other devices in a customer's premises. The term "wired 5G access network" or "W-5GAN" refers, at least in some examples, to a wired AN connected to the 5GC via the N2 and N3 reference points. The W-5GAN may be a W-5GBAN or a W-5GCAN. The term "wired 5G cable access network" or "W-5GCAN" refers, at least in some examples, to an access network defined in / by CableLabs. The term "wired BBF access network" or "W-5GBAN" refers, at least in some examples, to an access network defined in / by the Broadband Forum (BBF). The term "wired access gateway function" or "W-AGF" refers, at least in some examples, to a network function in the W-5GAN that provides connectivity to the 3GPP 5G core network (5GC) to the 5G-RG and / or FN-RG. The term "5G-RG" refers, at least in some examples, to an RG capable of connecting to a 5GC that plays the role of a user equipment with respect to the 5GC; it supports security elements and exchanges N1 signaling with the 5GC. The 5G-RG may be a 5G-BRG or a 5G-CRG.

[0289] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration. The term "SSB" refers to the SS / PBCH block.

[0290] The term "primary cell" refers to an MCG cell operating on the primary frequency, in which the UE performs an initial connection establishment procedure or initiates a connection reestablishment procedure. The term "primary SCG cell" refers to an SCG cell to which the UE performs random access when performing a reconfiguration with synchronization procedure for DC operation. The term "secondary cell" refers to a cell that provides additional radio resources in addition to special cells for a UE configured with CA. The term "secondary cell group" refers to a subset of service cells including a PSCell and zero or more secondary cells for a UE configured with DC. The term "serving cell" refers to a primary cell for a UE in RRC_CONNECTED that is not configured with CA / DC, and there is only one serving cell including the primary cell. The term "serving cell" or "each serving cell" refers to a set of cells including a special cell and all secondary cells for a UE in RRC_CONNECTED that is configured with CA. The term "special cell" refers to a PCell of an MCG or a PSCell of an SCG for DC operation; otherwise, the term "special cell" refers to a Pcell.

[0291] The term "edge computing" refers, at least in some examples, to the implementation or arrangement of distributed computing elements that move processing activities and resources (e.g., computing resources, storage resources, acceleration resources, and / or network resources) toward the "edge" of a network to reduce latency and increase throughput for endpoint users (client devices, user devices, etc.). Additionally or alternatively, the term "edge computing" refers, at least in some examples, to a set of services hosted at an access point of attachment to a network relatively close to a client / UE to achieve relatively efficient service delivery by reducing end-to-end latency and / or load on a transport network. In some examples, edge computing implementations involve providing services and / or resources in cloud-like systems, functions, applications, and subsystems from one or more locations accessible via a wireless network. Additionally or alternatively, the term "edge computing" refers, at least in some examples, to the concept described in [TS23501]: enabling operator and third-party services to be hosted near a UE's access point of attachment to achieve efficient service delivery by reducing end-to-end latency and load on a transport network. The term "edge computing node" or "edge computing device" refers, at least in some examples, to an identifiable entity that implements aspects of edge computing operations, whether part of a larger system, a distributed system collection, or a stand-alone device. In some examples, a computing node may be referred to as an "edge node," "edge device," "edge system," whether operating as a client, server, or intermediate entity. Additionally or alternatively, the term "edge computing node" refers, at least in some examples, to a real-world, logical, or virtualized implementation of a computing-capable element in the form of a device, gateway, bridge, system or subsystem, component, whether operating in server, client, endpoint, or peer-to-peer mode, and whether located at the "edge" of a network or at a more distant connected location within the network. However, references to an "edge computing system" generally refer to a distributed architecture, organization, or collection of multiple nodes and devices, and which are organized to complete or provide some aspects of services or resources in an edge computing environment. The term "edge computing platform" or "edge platform" refers, at least in some examples, to a set of functions for instantiating, executing, or running edge applications on a particular edge computing node (e.g., a virtualized infrastructure, etc.) so that such edge applications can provide and / or consume edge services, and / or otherwise provide one or more edge services. The term "edge application" or "edge app" refers, at least in some examples, to an application that can be instantiated on or executed by an edge computing node within an edge computing network, system, or framework and can potentially provide and / or consume edge computing services. The term "edge service" refers, at least in some examples, to a service provided either by the edge platform itself and / or by an edge application via an edge computing node and / or edge platform.

[0292] The term "cloud computing" or "cloud" refers, at least in some examples, to a paradigm for enabling network access to a scalable, elastic pool of shareable computing resources through on-demand self-service provisioning and management without the need for active management by the user. Cloud computing provides cloud computing services (or cloud services), which are one or more capabilities provided by cloud computing invoked using defined interfaces (e.g., APIs, etc.).

[0293] The term "network function" or "NF" refers, at least in some examples, to a functional block of a network infrastructure having one or more external interfaces and defined functional behaviors. The term "network instance" refers, at least in some examples, to information identifying a domain; in some examples, the UPF uses a network instance for service detection and routing. The term "network service" or "NS" refers, at least in some examples, to a composition or collection of NFs and / or network services defined by their functional and behavioral specifications. The term "NF service instance" refers, at least in some examples, to an identifiable instance of a NF service. The term "NF instance" refers, at least in some examples, to an identifiable instance of a NF. The term "NF service" refers, at least in some examples, to a function exposed by a NF through a service-based interface and consumed by other authorized NFs.

[0294] The term "application function" or "AF" refers, at least in some examples, to an element or entity that interacts with the 3GPP core network in order to provide a service. Additionally or alternatively, the term "application function" or "AF" refers, at least in some examples, to an edge computing node or ECT framework from the perspective of the 5G core network. The term "management function" refers, at least in some examples, to a logical entity that plays the role of a service consumer and / or a service producer. The term "management service" refers, at least in some examples, to a set of management capabilities provided. The term "network function virtualization" or "NFV" refers, at least in some examples, to the principle of separating network functions from the hardware on which they run by using virtualization techniques and / or virtualization technology. The term "virtualized network function" or "VNF" refers, at least in some examples, to an implementation of a NF that can be deployed on a network function virtualization infrastructure (NFVI). The term "network function virtualization infrastructure manager" or "NFVI" refers, at least in some examples, to the sum of all hardware and software components that build an environment for deploying VNFs. The term "virtualization infrastructure manager" or "VIM" refers, at least in some examples, to a functional block that is typically responsible for controlling and managing NFVI computing resources, storage resources, and network resources within an operator's infrastructure domain. The term "virtualization container," "execution container," or "container" refers, at least in some examples, to a partition of a computing node that provides an isolated virtualized computing environment. The term "operating system container" refers, at least in some examples, to a virtualized container that utilizes a shared operating system (OS) kernel of its host, where the host providing the shared OS kernel can be a physical computing node or another virtualized container. Additionally or alternatively, the term "container" refers, at least in some examples, to a standard software unit (or package) including code and its related dependencies and / or an abstraction at the application layer that encapsulates code and dependencies together. Additionally or alternatively, the term "container" or "container image" refers, at least in some examples, to a lightweight, standalone executable software package that includes everything needed to run an application (e.g., code, runtime environment, system tools, system libraries, and settings). The term "virtual machine" or "VM" refers, at least in some examples, to a virtualized computing environment that behaves in the same or similar manner as a physical computer and / or server. The term "hypervisor" refers, at least in some examples, to a software element that partitions the underlying physical resources of a computing node, creates VMs, manages resources for VMs, and isolates individual VMs from each other.

[0295] The term "data network" or "DN" refers, at least in some examples, to a network hosting a data center service (e.g., such as a carrier service, the Internet, a third-party service, or an enterprise network). Additionally or alternatively, the DN refers, at least in some examples, to a service network belonging to a carrier or a third party that is provided as a service to a client or user equipment (UE). The DN is sometimes referred to as a "packet data network" or "PDN". The term "local area data network" or "LADN" refers, at least in some examples, to a DN that is accessible only to UEs in a specific location, which provides connectivity to a specific DNN, and whose availability is provided to the UE.

[0296] The term "non-public network" or "NPN" refers, at least in some examples, to a network intended for non-public use. Additionally or alternatively, the term "non-public network" or "NPN" refers, at least in some examples, to a fifth generation system (5GS) deployed for non-public use (see, for example, 3GPP TS22.261v19.2.0 (2023-03-31) ("[TS22261]")). In some examples, the NPN is a stand-alone NPN (SNPN) or a public network integrated NPN (PNI-NPN). The term "stand-alone non-public network" or "SNPN" refers, at least in some examples, to an NPN operated by an NPN operator and not dependent on network functions provided by a PLMN. The term "public network integrated non-public network" or "PNI-NPN" refers, at least in some examples, to a non-public network deployed with the support of a PLMN.

[0297] The term "local service" or "localized service" refers, at least in some examples, to a service that is localized (e.g., provided at a specific / limited area) and / or may be bounded in time. In some examples, a localized service may be implemented via an application (e.g., live or on-demand audio / video streaming, electronic gaming, IMS, etc.) or a connection (e.g., UE to UE, UE to data network, etc.).

[0298] The term "localization service provider" refers, at least in some examples, to an application provider or network operator that localizes its services and provides them to end users via a hosted network.

[0299] The term "hosted network" refers, at least in some examples, to a network that provides access to local / localized services.

[0300] The term "hosted service" or "hosted service" refers, at least in some examples, to a service that includes the operator's own applications and / or trusted third-party applications in a service hosting environment that can be accessed by a user. The term "service hosting environment" refers, at least in some examples, to an environment located within a 5G network and fully controlled by the operator that provides the hosted service.

[0301] The term "home network" refers to the network that has the subscription / credentials currently in use of the UE in at least some examples. In some examples, the home network is a PLMN or NPN. In some SNPN-related examples, the UE uses credentials owned by a credential holder separate from the SNPN for access.

[0302] The term "home network services" refers, at least in some examples, to services provided to a UE based on a subscription agreed upon with a home network operator.

[0303] The term "return to the home network" refers, at least in some examples, to when the UE leaves the hosted network (e.g., when local / localized services terminate) and resumes using the subscription / credentials of the home network. In some examples, returning to the home network may involve network selection (e.g., selecting an HPLMN or a VPLMN) and may involve deactivation / activation of an SNPN access mode.

[0304] The term "Internet of Things" or "IoT" refers, at least in some examples, to a system of interrelated computing devices, mechanical and digital machines capable of communicating data with little or no human interaction, and may involve technologies such as real-time analytics, machine learning and / or AI, embedded systems, wireless sensor networks, control systems, automation (e.g., smart home, smart building, and / or smart city technologies), etc. IoT devices are typically low-power devices without heavy computing or storage capabilities.

[0305] The term "protocol" refers, at least in some examples, to a predefined process or method for performing one or more operations. Additionally or alternatively, the term "protocol" refers, at least in some examples, to a common means (sometimes also referred to as an interface) for unrelated objects to communicate with each other. The term "communication protocol" refers, at least in some examples, to a standardized set of rules or instructions implemented by a communication device and / or system to communicate with other devices and / or systems, including instructions for encapsulating / decapsulating data, modulating / demodulating signals, implementation of a protocol stack, etc. In various implementations, "protocol" and / or "communication protocol" can be represented using a protocol stack, a finite state machine (FSM), and / or any other suitable data structure. The term "standard protocol" refers, at least in some examples, to a protocol whose specifications are published and known to the public and controlled by a standards body. The term "protocol stack" or "network stack" refers, at least in some examples, to an implementation of a protocol suite or protocol family. In various implementations, a protocol stack includes a set of protocol layers, wherein the lowest protocol handles low-level interactions with hardware and / or communication interfaces, and each higher layer adds additional capabilities. Additionally or alternatively, the term "protocol" refers, at least in some examples, to a formal set of procedures applicable to ensuring communication between two or more functions within the same layer of a hierarchy of functions.

[0306] The term "application layer" refers, at least in some examples, to an abstraction layer that specifies shared communication protocols and interfaces used by hosts in a communication network. Additionally or alternatively, the term "application layer" refers, at least in some examples, to an abstraction layer that interacts with software applications that implement communication components and includes identifying communication partners, determining resource availability, and synchronizing communications. Examples of application layer protocols include HTTP, HTTPs, File Transfer Protocol (FTP), Dynamic Host Configuration Protocol (DHCP), Internet Message Access Protocol (IMAP), Lightweight Directory Access Protocol (LDAP), MQTT (MQ Telemetry Transport), Remote Authentication Dial-In User Service (RADIUS), Diameter Protocol, Extensible Authentication Protocol (EAP), RDMA over Converged Ethernet Version 2 (RoCEv2), Real-time Transport Protocol (RTP), RTP Control Protocol (RTCP), Real-time Streaming Protocol (RTSP), SBMV Protocol, Thin Client Control Protocol (SCCP), Session Initiation Protocol (SIP), Session Description Protocol (SDP), Simple Mail Transfer Protocol (SMTP), Simple Network Management Protocol (SNMP), Simple Service Discovery Protocol (SSDP), Small Computer System Interface (SCSI), Internet SCSI (iSCSI), iSCSI Extensions for RDMA (iSER), Transport Layer Security (TLS), Voice over IP (VoIP), Virtual Private Network (VPN), Extensible Messaging and Presence Protocol (XMPP), etc.

[0307] The term "session layer" refers, at least in some examples, to controlling conversations and / or connections between entities or elements, and may include an abstraction layer that establishes, manages, and terminates connections between entities or elements.

[0308] The term "transport layer" refers, at least in some examples, to a protocol layer that provides end-to-end (e2e) communication services (e.g., connection-oriented communication, reliability, flow control, and multiplexing). Examples of transport layer protocols include Datagram Congestion Control Protocol (DCCP), Fiber Channel Protocol (FBC), Generic Routing Encapsulation (GRE), GPRS Tunneling (GTP), Micro Transport Protocol (μTP), Multipath TCP (MPTCP), Multipath QUIC (MPQUIC), Multipath UDP (MPUDP), Quick UDP Internet Connections (QUIC), Remote Direct Memory Access (RDMA), Resource Reservation Protocol (RSVP), Stream Control Transmission Protocol (SCTP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), etc.

[0309] The term "network layer" refers, at least in some examples, to a protocol layer including means for transmitting network packets from a source to a destination via one or more networks. Additionally or alternatively, the term "network layer" refers, at least in some examples, to a protocol layer responsible for packet forwarding and / or routing through intermediate nodes. Additionally or alternatively, the term "network layer" or "internet layer" refers, at least in some examples, to a protocol layer including intercommunication methods, protocols, and specifications for transmitting network packets across networks. For example, network layer protocols include Internet Protocol (IP), IP Security (IPsec), Internet Control Message Protocol (ICMP), Internet Group Management Protocol (IGMP), Open Shortest Path First Protocol (OSPF), Routing Information Protocol (RIP), RDMA over Converged Ethernet Version 2 (RoCEv2), Subnet Access Protocol (SNAP), and / or some other Internet or network protocol layers.

[0310] The term "link layer" or "data link layer" refers, at least in some examples, to a protocol layer that transfers data between nodes on a network segment across the physical layer. Examples of link layer protocols include Logical Link Control (LLC), Media Access Control (MAC), Ethernet, RDMA over Converged Ethernet Version 1 (RoCEv1), etc.

[0311] The terms "radio resource control", "RRC layer" or "RRC" refer, at least in some examples, to a protocol layer or sublayer that performs: system information handling; paging; establishment, maintenance and release of RRC connections; security functions; establishment, configuration, maintenance and release of signaling radio bearers (SRBs) and data radio bearers (DRBs); mobility functions / services; QoS management; and some sidelink specific services and functions over the Uu interface (see, for example, 3GPP TS 36.331 v17.4.0 (2023-03-30) ("[TS36331]") and / or 3GPP TS 38.331 v17.4.0 (2023-03-30) ("[TS38331]")).

[0312] The terms "Service Data Adaptation Protocol", "SDAP layer", or "SDAP" refer, at least in some examples, to a protocol layer or sublayer that performs mapping between QoS flows and data radio bearers (DRBs) and marks QoS flow IDs (QFIs) in both DL and UL packets (see, for example, 3GPP TS 37.324 v17.0.0 (2022-04-13) ("[TS37324]").

[0313] The terms "Packet Data Convergence Protocol", "PDCP layer", or "PDCP" refer, at least in some examples, to a protocol layer or sublayer that performs: transmitting user plane or control plane data; maintaining PDCP sequence numbers (SNs); header compression and decompression using Robust Header Compression (ROHC) and / or Ethernet Header Compression (EHC) protocols; encryption and decryption; integrity protection and integrity verification; providing timer-based SDU discard; routing for split bearers; duplication and duplicate discard; reordering and in-order delivery; and / or out-of-order delivery (see, for example, 3GPP TS 36.323v17.2.0 (2023-01-13) and / or 3GPP TS38.323v17.4.0 (2023-03-28) ("[TS38323]")).

[0314] The terms "radio link control layer", "RLC layer" or "RLC" refer, at least in some examples, to a protocol layer or sublayer that performs delivery of upper layer PDUs; sequence numbering independent of sequence numbering in PDCP; error correction through ARQ; segmentation and / or resegmentation of RLC SDUs; reassembly of SDUs; duplicate detection; RLC SDU discard; RLC reconstruction; and / or protocol error detection (see, for example, 3GPP TS 36.322 v17.0.0 (2022-04-15) and 3GPP TS 38.322 v17.2.0 (2023-01-13) ("[TS38322]")).

[0315] The term "medium access control protocol", "MAC protocol" or "MAC" refers, at least in some examples, to a protocol that manages access to a transmission medium in a network to enable the exchange of data between stations in the network. Additionally or alternatively, the term "medium access control layer", "MAC layer" or "MAC" refers, at least in some examples, to a protocol layer or sublayer that performs functions to provide frame-based connectionless mode (e.g., datagram style) data transfer between stations or devices. Additionally or alternatively, the term "medium access control layer", "MAC layer" or "MAC", at least in some examples, refers to a protocol layer or sublayer that: performs mapping between logical channels and transport channels; multiplexing / demultiplexing MAC SDUs belonging to one or different logical channels into / from transport blocks (TBs) delivered to / from the physical layer on the transport channel; scheduling information reporting; error correction through HARQ (one HARQ entity per cell in the case of CA); priority handling between UEs by means of dynamic scheduling; priority handling between logical channels of a UE by means of logical channel prioritization; priority handling between overlapping resources of a UE; and / or padding (see, for example, 3GPP TS 36.321v17.3.0 (2023-01-13) and 3GPP TS 38.321v17.4.0 (2023-03-29) ("[TS38321]").

[0316] The terms "physical layer", "PHY layer" or "PHY" refer, at least in some examples, to a protocol layer or sublayer that includes the capability to send and receive modulated signals for communication in a communication network (see, for example, 3GPP TS 36.201 v17.0.0 (2022-03-31) and 3GPP TS 38.201 v17.0.0 (2022-01-05) ("[TS38201]").

[0317] The term "access technology" refers, at least in some examples, to the technology used for the underlying physical connection to a communication network. The term "radio access technology" or "RAT" refers, at least in some examples, to the technology used for the underlying physical connection to a radio-based communication network. The term "radio technology" refers, at least in some examples, to the technology used for wireless transmission and / or reception of electromagnetic radiation for information transmission. The term "RAT type" may identify, at least in some examples, the transmission technology and / or communication protocol used in the access network. Examples of access technologies include wireless access technology / RAT, wired, wired cable, wired broadband forum (wireline-BBF), Ethernet (see, e.g., IEEE Standard for Ethernet, IEEE Std802.3-2018 (August 31, 2018) ("[IEEE8023]")) and its variants, fiber optic networks (e.g., ITU-T G.651, ITU-T G.652, Optical Transport Network (OTN), Synchronous Optical Networking (SONET) and Synchronous Digital Hierarchy (SDH), Digital Subscriber Line (DSL) and its variants, Data over Cable Service Interface Specification (DOCSIS) technology, Hybrid Fiber Coaxial (HFC) technology, etc. Examples of RATs (or RAT types) and / or communication protocols include Advanced Mobile Phone System (AMPS) technologies (e.g., Digital AMPS (D-AMPS), Total Access Communication System (TACS) and its variants (e.g., Extended TACS (ETACS)), etc.); Global System for Mobile Communications (GSM) technologies (e.g., Circuit Switched Data (CSD), High Speed ​​CSD (HSCSD), General Packet Radio Service (GPRS), and Enhanced Data Rates for GSM Evolution (EDGE)); Third Generation Partnership Project (3GPP) technologies (e.g., Universal Mobile Telecommunications System (UMTS) and its variants (e.g., UMTS Terrestrial Radio Access (UTRA), Wideband Code Division Multiple Access (W-CDMA), Freedom of Multi-Media Access (FOMA), Time Division-Code Division Multiple Access (TD-CDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), etc.), Generic Access Network (GAN) / Unlicensed Mobile Access (UMA), High Speed ​​Packet Access (HSPA) and its variants (e.g., HSPA Plus (HSPA+)), Long Term Evolution (LTE) and its variants (e.g., LTE-Advanced (LTE-A), Evolved UTRA (E-UTRA), LTE Extra, LTE-A Pro, LTE LAA, MuLTEfire, etc.), fifth generation (5G) or new radio (NR), narrowband IoT (NB-IOT), 3GPP proximity services (ProSe), etc.); ETSI RAT (e.g., High Performance Radio Metropolitan Area Network (HiperMAN), Intelligent Transportation System (ITS) (e.g., ITS-G5, ITS-G5B, ITS-G5C, etc.), etc.); Institute of Electrical and Electronics Engineers (IEEE) technology and / or WiFi (e.g., IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture, IEEE Std 802-2014, pp.1-74 (June 30, 2014) ("[IEEE802]"), IEEEStandard for Information Technology--Telecommunications and InformationExchange between Systems-Local and Metropolitan Area Networks--SpecificRequirements-Part 11: Wireless LAN Medium Access Control(MAC) and PhysicalLayer(PHY)Specifications,IEEE Std 802.11-2020, pp.1-4379 (February 26, 2021) ("[IEEE80211]"), IEEE 802.15 technology (e.g., IEEE Standard for Low-Rate Wireless Networks, IEEE Std802.15.4-2020, pp.1-800 (July 23, 2020) ("[IEEE802154]") and its variants (e.g., ZigBee, WirelessHART, MiWi, ISA100.11a, Thread, IPv6 over low-power WPAN (6LoWPAN)), IEEE Standard for Local and metropolitan area networks-Part15.6:Wireless Body Area Networks, IEEE Std 802.15.6-2012, pp.1-271 (February 29, 2012)), WLAN V2X RAT (e.g., IEEE Standard for Information technology--Local and metropolitan area networks--Specific requirements--Part 11:Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications Amendment 6:Wireless Access in Vehicular Environments, IEEE Std 802.11p-2010,pp.1-51 (July 15, 2010) ("[IEEE80211p]") (which is now part of [IEEE80211]), IEEE Guide for Wireless Access in Vehicular Environments (WAVE) Architecture, IEEE Standards Association, IEEE 1609.0-2019 (April 10, 2019) ("[IEEE16090]"), IEEE 802.11bd, Dedicated Short Range Communications (DSRC) and others), Worldwide Interoperability for Microwave Access (WiMAX) (e.g., IEEE Standard for Air Interface for Broadband Wireless Access Systems, IEEE Std 802.16-2017, pp. 1-2726 (March 2, 2018) ("[WiMAX]")), Mobile Broadband Wireless Access (MBWA) / iBurst (e.g., IEEE 802.20 and its variants), Wireless Gigabit Alliance (WiGig) standards (e.g., IEEE 802.11ad, IEEE 802.11ay, etc.); integrated digital enhanced network (iDEN) and its variants (e.g., broadband integrated digital enhanced network (WiDEN)); millimeter wave (mmWave) technology / standards (e.g., wireless systems operating above 10-300 GHz and 3GPP 5G); short-range and / or wireless personal area network (WPAN) technology / standards (e.g., IEEE 802.15 technology (e.g., as described above); Bluetooth and its variants (e.g., Bluetooth 5.3, Bluetooth Low Energy (BLE), etc.), WiFi-direct, Miracast, ANT / ANT+, Z-Wave, Universal Plug and Play (UPnP), low power wide area network (LPWAN), long range wide area network (LoRA or LoRaWAN. TM) etc.); optical and / or visible light communication (VLC) technologies / standards (e.g., IEEE Standard for Local and metropolitan area networks--Part 15.7: Short-Range Optical Wireless Communications, IEEE Std802.15.7-2018, pp.1-407 (April 23, 2019) etc.); Sigfox; Mobitex; 3GPP2 technologies (e.g., cdmaOne (2G), Code Division Multiple Access 2000 (CDMA) 2000) and Evolution Data Optimized or Evolution Data Only (EV-DO); Push-to-Talk (PTT), Mobile Telephone System (MTS) and its variants (e.g., Improved MTS (IMTS), Advanced MTS (AMTS), etc.); Personal Digital Cellular (PDC); Personal Handyphone System (PHS), Cellular Digital Packet Data (CDPD); Cellular Digital Packet Data (CDPD); DataTAC; Digital Enhanced Cordless Telecommunications (DECT) and its variants (e.g., DECT Ultra Low Energy (DECT ULE), DECT-2020, DECT-5G, etc.); Ultra High Frequency (UHF) communications; Very High Frequency (VHF) communications; and / or any other suitable RAT or protocol. In addition to the above RATs / standards, for the purposes of this disclosure, any number of satellite uplink technologies may be used, including, for example, radios that comply with standards published by the International Telecommunication Union (ITU), or ETSI, etc. The examples provided herein should therefore be understood to be applicable to a variety of other communication technologies, both existing and yet to be developed.

[0318] The term "channel" refers, at least in some examples, to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous with and / or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" and / or any other similar term representing a path or medium through which data is transmitted. Additionally, the term "link" refers, at least in some examples, to a connection between two devices over a RAT for the purpose of sending and receiving information.

[0319] The term "carrier" refers, at least in some examples, to a modulated waveform that conveys one or more physical channels (e.g., 5G / NR, E-UTRA, UTRA, and / or GSM / EDGE physical channels). The term "carrier frequency" refers, at least in some examples, to the center frequency of a cell.

[0320] The term "bearer" refers, at least in some examples, to an information transmission path of defined capacity, delay, bit error rate, etc. The term "radio bearer" refers, at least in some examples, to a service provided by Layer 2 (L2) for the transmission of user data between a user equipment (UE) and a radio access network (RAN). The term "radio access bearer" refers, at least in some examples, to a service provided by an access stratum to a non-access stratum for the transmission of user data between a UE and a CN.

[0321] The term "subframe" refers, at least in some examples, to a time interval for transmitting a signal. In some implementations, a subframe is equal to 1 millisecond (ms). The term "time slot" refers, at least in some examples, to an integer multiple of consecutive subframes. The term "superframe" refers, at least in some examples, to a time interval comprising two time slots.

[0322] The term "channel coding" refers, at least in some examples, to a process and / or technique for adding redundancy to a message or packet so as to make it more robust against noise, channel interference, limited channel bandwidth, and / or other errors. For the purposes of this disclosure, the term "channel coding" may be used interchangeably with the following terms: "forward error correction" or "FEC"; "error correction coding", "error correction code" or "ECC"; and / or "network coding" or "NC". The term "network coding" refers, at least in some examples, to a process and / or technique for encoding and decoding transmitted data to improve network performance. The term "code rate" refers, at least in some examples, to the proportion of useful or non-redundant data streams or flows (e.g., for a code rate of k / n, for every k bits of useful information, the encoder generates a total of n bits of data, where n–k is redundant). The term "systematic code" refers, at least in some examples, to any error correction code in which the input data is embedded in the encoded output. The term "non-systematic code" refers, at least in some examples, to any error correction code in which the input data is not embedded in the encoded output. The term "interleaving" refers, at least in some examples, to the process of rearranging code symbols so that a burst of errors is spread over multiple code words that can be corrected by ECC. The terms "code word" or "codeword" refer, at least in some examples, to the elements of a code or protocol that are assembled according to the specific rules of the code or protocol.

[0323] The term "network address" refers, at least in some examples, to an identifier for a node or host in a computer network, and may be a unique identifier across the network and / or may be unique to a locally managed portion of the network. Examples of identifiers and / or network addresses may include an am application identifier, a Bluetooth hardware device address (BD_ADDR), a cellular network address (e.g., an access point name (APN), an AMF name and / or an AMF identifier (ID), an AF service identifier, a closed access group identifier (CAG-ID), an edge application server (EAS) ID, a data network access identifier (DNAI), a data network name (DNN), an EPS bearer identity (EBI), an equipment identity register (EIR) and / or a 5G-EIR, an extended unique identifier (EUI), a network selection group ID (GIN), a general public subscription identifier (GPSI), a globally unique AMF identifier (GUAMI), a globally unique temporary identifier (GUTI) and / or a 5G-GUTI, a gNB identifier (gNB ID), a global gNB ID, International Mobile Equipment Identity (IMEI), IMEI Type Assignment Code (IMEA / TAC), International Mobile Subscriber Identity (IMSI), IMSI Software Version (IMSISV), Permanent Equipment Identifier (PEI), Local Area Data Network (LADN) DNN, Local NG-RAN Node Identifier, Mobile Subscriber Identification Number (MSIN), Mobile Subscriber / Station ISDN Number (MSISDN), Network Identifier (NID), NR Cell Global Identifier (NCGI), Network Slice Instance (NSI) ID, Network Slice AS Group (NSAG), Permanent Equipment Identifier (PEI), Public Land Mobile Network (PLMN) ID, Physical Cell Identifier (PCI), QoS Flow ID (QFI) and / or 5G QoS Identifier (5QI), RAN ID, Routing Indicator, Radio Network Temporary Identifier (RNTI) and its variants (e.g., 3GPP TS 38.300v17.4.0 (2023-03-28) (“anything discussed in clause 8 of [TS38300]) and / or previously discussed NCR-RNTI), SMS Function (SMSF) ID, Standalone Non-Public Network (SNPN) ID, Single Network Slice Selection Assistance Information (S-NSSAI), Sidelink Identities (e.g., Source Layer 2 ID, Target Layer 2 ID, PC5 Link Identifier, etc.), Subscription Hidden Identifier (SUCI), Subscription Permanent Identifier (SUPI), Temporary Mobile Subscriber Identity (TMSI) and its variants, Tracking Area Identity (TAI), UE Access Category and Identity and / or other cellular network related identifiers), CA G-ID, driver's license number, Global Trade Item Number (GTIN) (e.g., Australian Product Number (APN), EPC, European Article Number (EAN), Universal Product Code (UPC), etc.), email address, Enterprise Application Server (EAS) ID, endpoint address, Electronic Product Code (EPC) defined by the EPCglobal Tag Data Standard, Fully Qualified Domain Name (FQDN), flow ID and / or flow hash, hash, index, Internet Protocol (IP) address in an IP network (e.g., IP version 4 (IPv4), IP version 6 (IPv6), etc.), Internet Packet Exchange (IPX) address, LAN ID, MAC address, personal area network (PAN) ID, port number (e.g., TCP port number, UDP port number, etc.), price lookup code (PLC), product key, QUIC connection ID, RFID tag, serial number, service set identifier (SSID) and its variants, screen name, serial number, stock keeping unit (SKU), socket address, social security number (SSN), telephone number (e.g., in public switched telephone network (PTSN)), unique identifier (UID) (e.g., including global UID, universal unique identifier (UUID) (e.g., as specified in ISO / IEC 11578:1996), etc.), uniform resource locator (URL) and / or uniform resource identifier (URI), username (e.g., ID used to log into a service provider platform (e.g., a social network and / or some other service)), vehicle identification number (VIN), virtual LAN (VLAN) ID, X.21 address, X.25 address, . The device network ID and / or any other suitable network address and components thereof.

[0324] The term "endpoint address" refers, at least in some examples, to an address (e.g., a URI and / or any other network address (e.g., an address discussed herein)) used to determine the host / authority portion of a target network address, where the target network address (e.g., a URI and / or any other network address (e.g., an address discussed herein)) is used to access a NF service of a NF service producer (e.g., to invoke a service operation) or for notification to a NF service consumer. The term "port" in the context of a computer network refers, at least in some examples, to a communication endpoint, a virtual point where a virtual data connection and / or network connection between two or more entities begins and ends. Additionally or alternatively, a "port" is associated with a specific process or service, at least in some examples. Additionally or alternatively, the term "port" refers, at least in some examples, to a specific interface of a specified device (apparatus) with an electromagnetic environment (e.g., any connection point on a device intended for a cable connection to or from the device is considered a port).

[0325] The term "application" or "app" refers, at least in some examples, to a computer program designed to perform specific tasks other than those related to the operation of the computer itself. Additionally or alternatively, the term "application" or "app" refers, at least in some examples, to a complete and deployable software package, environment for achieving specific functions in an operating environment. The term "process" refers, at least in some examples, to an instance of a computer program executed by one or more threads. In some implementations, a process may consist of multiple threads of execution executing instructions concurrently. The term "algorithm" refers, at least in some examples, to an unambiguous specification of how to solve a problem or a class of problems by performing calculations, input / output operations, data processing, automated reasoning tasks, and the like.

[0326] The term "application programming interface" or "API" refers, at least in some examples, to a collection of subroutine definitions, communication protocols, and tools for building software. Additionally or alternatively, the term "application programming interface" or "API" refers, at least in some examples, to a collection of well-defined methods for communication between various components. In some examples, an API may be defined or otherwise used for a Web-based system, an operating system, a database system, computer hardware, a software library, and the like.

[0327] The terms "instantiate," "instantiation," and the like refer, at least in some examples, to the creation of an instance. In some examples, an "instance" refers to a specific occurrence of an object that may occur, for example, during execution of program code.

[0328] The term "reference point" refers, at least in some examples, to a conceptual point at which two non-overlapping functional groups, elements, or entities are joined. The term "service-based interface" refers, at least in some examples, to a representation of how a particular NF provides and / or exposes a set of services.

[0329] The term "use case" refers, at least in some examples, to a description of a system from the user's perspective. Use cases sometimes treat the system as a black box, with interactions with the system (including system responses) viewed as coming from outside the system. Use cases typically avoid technical jargon, preferring instead the language of end users or domain experts.

[0330] The term "user" refers, at least in some examples, to an abstract representation of any entity that issues commands, requests, and / or data to a computing node or system and / or otherwise consumes or uses services. Additionally or alternatively, the term "user" refers, at least in some examples, to an entity that uses 3GPP system services without being part of the 3GPP system (e.g., a person using a 3GPP system mobile station as a portable phone). The term "user profile" refers, at least in some examples, to a collection of information that provides a consistent, personalized service environment for a user, regardless of the user's location or the terminal used (within the limitations of the terminal and the service network).

[0331] The term "quality of service" or "QoS" refers, at least in some examples, to a description or measurement of the overall performance of a service (e.g., telephone and / or cellular services, network services, wireless communication / connectivity services, cloud computing services, etc.). In some cases, QoS can be described or measured from the perspective of the user of the service, and therefore, QoS can be a common effect of service performance that determines the satisfaction of the user of the service. In other cases, QoS, at least in some examples, refers to business priority and resource reservation control mechanisms, rather than the perception of the quality of service achieved. In these cases, QoS is the ability to provide different priorities to different applications, users, or flows, or to guarantee a specific level of performance for a flow. In either case, QoS is characterized by a combination of performance factors (e.g., service operability performance, service accessibility performance; service reservation capability performance; service reliability performance, service integrity performance, and other factors specific to each service) applicable to one or more services. When quantifying QoS, several relevant aspects of the service can be considered, including packet loss rate, bit rate, throughput, transmission delay, availability, reliability, jitter, signal strength and / or quality measurements and / or other measurements (e.g., the measurements discussed herein). Additionally or alternatively, the term "quality of service" or "QoS" refers, at least in some examples, to a mechanism for providing service forwarding treatment based on flow-specific service classification. In some examples, additionally or alternatively, the term "quality of service" or "QoS" is based, at least in some examples, on the definition provided by SERIES E: OVERALL NETWORK OPERATION, TELEPHONE SERVICE, SERVICE OPERATION AND HUMAN FACTORS Quality of telecommunication services: concepts, models, objectives and dependability planning - Terms and definitions related to the quality of telecommunication services, Definitions of terms related to quality of service, ITU-T Recommendation E.800 (09 / 2008) ("[ITU E800]"), the contents of which are hereby incorporated by reference in their entirety.

[0332] The term "service consumer" or "consumer" refers, at least in some examples, to an entity that consumes one or more services. The term "service producer" or "producer" refers, at least in some examples, to an entity that supplies, services, or otherwise provides one or more services. The term "service provider" or "provider" refers, at least in some examples, to an organization or entity that provides one or more services to at least one service consumer. For the purposes of this disclosure, the terms "service provider" and "service producer" may be used interchangeably, even though these terms may refer to different concepts. Examples of service providers include cloud service providers (CSPs), network service providers (NSPs), application service providers (ASPs) (e.g., application software service providers (ASSPs) in a service-oriented architecture), Internet service providers (ISPs), telecommunication service providers (TSPs), online service providers (OSPs), payment service providers (PSPs), managed service providers (MSPs), storage service providers (SSPs), SAML service providers, and the like.

[0333] The term "service level agreement" or "SLA" refers, at least in some examples, to the level of service expected from a service provider. In at least some examples, an SLA may represent a complete agreement between a service provider and a service consumer that specifies the provision of one or more services, how to provide or otherwise support one or more services, time, location, cost, performance, priorities for different business classes and / or QoS classes (e.g., highest priority for first responders, lower priority for non-critical data streams, etc.), and the responsibilities of the parties involved. The term "service level objective" or "SLO" refers, at least in some examples, to one or more measurable characteristics, metrics, or other aspects of an SLA (e.g., availability, throughput, frequency, response time, latency, QoS, QoE, and / or other similar performance metrics / measurements). In at least some examples, a set of SLOs may define the expected service (or service level expectation (SLE)) between a service provider and a service consumer, and may vary depending on the urgency, resources, and / or budget of the service. The term "service level indicator" or "SLI" refers, at least in some examples, to a measurement of the level of service provided by a service provider to a service consumer. In at least some examples, SLI forms the basis of SLO, which in turn forms the basis of SLA. Examples of SLI include latency (including end-to-end latency), throughput, availability, error rate, persistence, correctness and / or other similar performance metrics / measurements. In at least some examples, the term "service level indicator" or "SLI" may be referred to as "SLA metrics" or the like. The term "service level expectation" or "SLE" refers to unmeasurable service-related requests in at least some examples, but may be explicitly or implicitly provided in the SLA even if there is little or no way to determine whether the SLE is met. In at least some examples, the SLO may include a set of SLIs that generate, define or specify SLO achievement values. As an example, an availability SLO may depend on multiple components that may each have QoS availability measurements. Combining QoS measurements into SLO achievement values ​​may depend on the nature and / or architecture of the service.

[0334] The terms "configuration," "policy," "rule set," and / or "operating parameters" refer, at least in some examples, to machine-readable information objects that contain instructions, conditions, parameters, guidelines, data, metadata, and / or other information related to components, devices, systems, networks, service producers, service consumers, and / or other elements / entities.

[0335] The term "datagram" refers, at least in some examples, to the basic transmission unit associated with a packet-switched network; a datagram may be structured to have a header segment and a payload segment. The term "datagram" may be synonymous with any of the following terms, at least in some examples, even though they may refer to different aspects: "data unit", "protocol data unit" or "PDU", "service data unit" or "SDU", "frame", "packet", "network packet", "segment", "block", "cell", "chunk", "type-length-value" or "TLV", etc. Examples of datagrams, network packets, etc. include Internet Protocol (IP) packets, Internet Control Message Protocol (ICMP) packets, UDP packets, TCP packets, SCTP packets, ICMP packets, Ethernet frames, RRC messages / packets, SDAP PDUs, SDAP SDUs, PDCP PDUs, PDCP SDUs, MAC PDUs, MAC SDUs, BAP PDUs. BAP SDU, RLC PDU, RLC SDU, WiFi frames discussed in IEEE 802 protocols / standards (e.g., [IEEE80211], etc.), type-length-value (TLV), and / or other similar data structures. The term "packet" refers, at least in some examples, to a unit of information identified by a tag at layer 3 of the OSI reference model. In some examples, a "packet" may also be referred to as a "network protocol data unit" or "NPDU". The term "protocol data unit" refers, at least in some examples, to a unit of data specified in a (N) protocol layer, and includes (N) protocol control information and possibly (N) user data.

[0336] The term "information element" or "IE" refers to a structural element containing one or more fields in at least some examples. Additionally or alternatively, the term "information element" or "IE" refers to a field or field set defined in a standard or specification for conveying data and / or protocol information in at least some examples. The term "field" refers to a separate content of an information element or a data element containing content in at least some examples. The term "data frame", "data field" or "DF" refers to a data type containing more than one data element in a predetermined order in at least some examples. The term "data element" or "DE" refers to a data type containing a single data in at least some examples. Additionally or alternatively, the term "data element" refers to an atomic state of a specific object having at least one specific property at a specific point in time and may include a data element name or identifier, a data element definition, one or more representation items, an enumerated value or code (e.g., metadata) and / or a list of synonyms with data elements in other metadata registers. Additionally or alternatively, a "data element" refers to a data type containing a single data in at least some examples. A data element can store data that can be referred to as the content (or "content item") of a data element. Content items may include textual content, attributes, properties, and / or other elements referred to as "sub-elements". Additionally or alternatively, a data element may include zero or more properties and / or zero or more attributes, each of which may be defined as a database object (e.g., a field, a record, etc.), an object instance, and / or other data elements. "Attribute" refers, at least in some examples, to a markup construct comprising a name-value pair present within a start tag or an empty element tag. Attributes contain data associated with their element and / or control the behavior of the element.

[0337] The term "reference," at least in some examples, refers to data that can be used to locate other data and can be implemented in various ways (eg, pointer, index, handle, key, identifier, hyperlink, etc.).

[0338] The term "data set" or "dataset" refers, at least in some examples, to a collection of data; a "data set" or "dataset" may be formed or arranged in any type of data structure. In some examples, one or more characteristics may define or affect the structure and / or properties of a data set (e.g., the number and type of attributes and / or variables) and various statistical measures (e.g., standard deviation, kurtosis, etc.). The term "data structure" refers, at least in some examples, to a data organization, management, and / or storage format. Additionally or alternatively, the term "data structure" refers, at least in some examples, to a collection of data values, relationships between these data values, and / or functions, operations, tasks, etc. that may be applied to the data. Examples of data structures include primitives (e.g., Boolean values, characters, floating point numbers, fixed point numbers, integers, references or pointers, enumeration types, etc.), composite types (e.g., arrays, records, strings, unions, tagged unions, etc.), abstract data types (e.g., data containers, lists, tuples, associative arrays, maps, dictionaries, sets (or data sets), multisets or bags, stacks, queues, graphs (e.g., trees, heaps, etc.)), routing tables, symbol tables, quads, blockchains, purely functional data structures (e.g., stacks, queues, (multi) sets, random access lists, hash consing, zipper data structures, etc.).

[0339] The term "authorization" refers to a provision that a specific behavior must not be prevented, at least in some examples. The term "authentication" refers to the process of proving or verifying an identity, at least in some embodiments. Additionally or alternatively, the term "authentication" refers to a mechanism by which a computer system checks or verifies that a user or entity is indeed the user or entity being claimed, at least in some embodiments. Examples of authentication and / or authorization techniques include the use of API keys, basic access authentication ("basic authentication"), open authorization (OAuth), hash-based message authentication code (HMAC), Kerberos protocol, OpenID, WebID and / or other authentication and / or authorization techniques. The term "consistency check" refers to a test or evaluation performed to determine whether data has any internal conflicts, conflicts with other data and / or whether there are any contradictions, at least in some examples. In some examples, a "consistency check" can be operated according to a "consistency model", which at least in some examples refers to a set of rules or policies for performing consistency checks and / or determining whether data is consistent (or predictable). The term "integrity" refers to a mechanism to ensure that data has not been changed in an unapproved manner, at least in some examples. Examples of cryptographic mechanisms that may be used for integrity protection include digital signatures, message authentication codes (MACs), and secure hashes.The term "verify" refers, at least in some examples, to a process, method, function, or any other means of confirming the correctness of information or data.

[0340] The term "certificate" or "digital certificate" refers to an information object (e.g., an electronic document or other data structure) used to prove the validity of a piece of data (e.g., a public key in a public key infrastructure (PKI) system) in at least some examples. Examples of digital certificates include X.509 format and / or some other suitable formats, and can be signed using any suitable encryption mechanism (e.g., elliptic curve encryption digital signature algorithm (ECDSA) or some other suitable algorithm (e.g., any algorithm discussed herein)). Additionally or alternatively, the digital certificates discussed herein may include various certificates issued by other entities defined by the issuer, verification subject, notified subject, certificate authority (CA) (e.g., root CA, etc.), registration authority (EA), certification authority (AA) and / or relevant certificate authority security committee (CASC) standards, common computing security standards forum (CCSF) standards, CA / browser forum standards, GSMA standards, ETSI standards, GlobalPlatform standards and / or some other suitable standards. The term "certificate revocation list" or "CRL" refers to a signed list of a collection of certificates that are no longer considered valid by the certificate issuer in at least some examples. The terms "signature" or "digital signature" refer, at least in some examples, to a mathematical scheme, process, or method for verifying the authenticity of a digital message or information object (eg, an electronic document or other data structure).

[0341] The term "confidential data" refers, at least in some examples, to any form of information that a person or entity is legally or contractually obligated to protect from unauthorized access, use, disclosure, modification, or destruction. Additionally or alternatively, "confidential data" refers, at least in some examples, to any data owned or licensed by a person or entity that is not intended to be shared with the general public or classified by a person or entity with a designation that precludes sharing with the general public.

[0342] The term "encryption mechanism" refers, at least in some examples, to any encryption protocol and / or encryption algorithm. Examples of cryptographic mechanisms include cryptographic hash algorithms, such as functions in the Secure Hash Algorithm (SHA) 2 cryptographic hash algorithm (e.g., SHA-226, SHA-256, SHA-512, etc.) set, SHA 3, etc., or any type of keyed or unkeyed cryptographic hash function and / or any other function discussed herein; elliptic curve cryptography (ECC) algorithms (e.g., elliptic curve cryptographic key agreement algorithm (ECKA) algorithm, elliptic curve cryptographic digital signature algorithm (ECDSA), Lenstra elliptic curve factorization or elliptic curve factorization method (ECM), Menezes-Qu-Vanstone (MQV) or elliptic curve MQV (ECMQV), elliptic curve Diffie-Hellman (ECDH) key agreement, elliptic curve integrated encryption scheme (ECIES) or elliptic curve enhanced encryption scheme, Edwards curve digital signature algorithm (EdDSA)), etc.); Rivest-Shamir-Adleman (RSA) encryption; Merkle signature scheme, Advanced Encryption System (AES) algorithm; Triple Data Encryption Algorithm (3DES); quantum encryption algorithm; etc. Additionally or alternatively, the term "cryptographic protocol" refers, at least in some examples, to a sequence of steps that precisely specifies the actions required by two or more entities to achieve a particular security goal (e.g., a cryptographic protocol for key agreement). Additionally or alternatively, the term "cryptographic algorithm" refers, at least in some examples, to an algorithm that specifies the steps followed by a single entity to achieve a particular security goal (e.g., a cryptographic algorithm for symmetric key encryption). The term "public key encryption" or "asymmetric encryption" refers, at least in some examples, to an encryption system that uses an associated key pair including, for example, a public key for generating ciphertext and a corresponding private key for decrypting the ciphertext to obtain the original message (e.g., plaintext); in some examples, these key pairs are generated using a cryptographic algorithm based on a one-way function.

[0343] The term "cryptographic hash function," "hash function," or "hash") refers, at least in some examples, to a mathematical algorithm that maps data of arbitrary size (sometimes called a "message") to a fixed-size array of bits (sometimes called a "hash," "hash," or "message digest." A cryptographic hash function is typically a one-way function, which is a function that is practically infeasible to invert.

[0344] The term "encryption key" or "key" refers, at least in some examples, to a piece of information, typically a string of numbers or letters stored in a file, which, when processed through an encryption algorithm, can encode or decode encrypted data. The term "symmetric key algorithm" refers, at least in some examples, to an encryption algorithm that uses the same encryption key for both encryption of plain text and decryption of ciphertext; the key can be the same, or there can be a simple transformation between the two keys. The term "anchor key" refers, at least in some examples, to an encryption key used to generate other keys. In some examples, an "anchor key" is used in a key management system to create keys and distribute them to users. In some examples, an "anchor key" is stored in a secure location and is not used directly to encrypt or decrypt data. Examples of anchor keys include master keys, subkeys, and session keys.

[0345] The term "encryption" refers, at least in some examples, to the process of encoding an original representation of information (called "plain text") into an alternate form (called "cipher text"). In some examples, an encryption scheme includes using a pseudo-random encryption key generated by an encryption mechanism or some other algorithm to generate an encryption key that can be used to encrypt and / or decrypt plain text.

[0346] The term "one-time credential" refers, at least in some examples, to a type of authentication that is valid only for a single use. In some examples, one-time credentials are used for two-factor authentication (2FA), which is a security measure that requires two different forms of authentication to access an account. Examples of one-time credentials include a time-based one-time password (TOTP) (e.g., a one-time credential generated by a time-based algorithm that is valid for a short period of time (e.g., 30 seconds, etc.; in some examples, the TOTP is generated by a mobile app or hardware token)) and an out-of-band (OOB) one-time password (OTP) (e.g., a one-time credential sent to a user's phone (via an SMS message), an email address, etc.; in some examples, an OOB OTP is valid for a single use and can only be used once).

[0347] The term "data breach" refers, at least in some examples, to a breach of security that results in the accidental or unlawful destruction, loss, alteration, unauthorized disclosure, or access to transmitted, stored, or otherwise processed data (including personal, sensitive, and / or confidential data).

[0348] The term "information security" or "InfoSec" refers, at least in some examples, to any practices, techniques, and technologies used to protect information by mitigating information risks, and typically involves preventing or reducing the probability of unauthorized / inappropriate access to data, or the unlawful use, disclosure, disruption, deletion, damage, modification, inspection, recording, or devaluation of information; and the information to be protected can take any form, including electronic information, physical or tangible (e.g., computer-readable media storing information, paperwork, etc.) or intangible (e.g., knowledge, intellectual property assets, etc.).

[0349] While many of the previous examples are provided using specific cellular / mobile network terminology, including using 4G / 5G 3GPP network components (or anticipated terahertz-based 6G / 6G+ technologies), it will be understood that these examples can be applied to many other deployments of wide-area and local wireless networks as well as integration of wired networks (including optical networks and associated optical fibers, transceivers, etc.). In addition, various standards (e.g., 3GPP, ETSI, etc.) may define various message formats, PDUs, containers, frames, etc. as including a series of optional or mandatory data elements (DEs), data frames (DFs), information elements (IEs), etc. However, it should be understood that the requirements of any particular standard should not limit the examples discussed herein, and thus, any combination of containers, frames, DFs, DEs, IEs, values, actions, and / or features are possible in various examples, including any combination of containers, DFs, DEs, values, actions, and / or features that are strictly required to be followed in order to comply with these standards, or any combination of containers, frames, DFs, DEs, IEs, values, actions, and / or features that are strongly recommended and / or used with or without the presence / absence of optional elements.

[0350] Aspects of the subject matter of the present invention may be referred to herein individually and / or jointly, for convenience only, and if more than one aspect is actually disclosed, it is not intended to voluntarily limit the scope of the present application to any single aspect or inventive concept. Therefore, although specific aspects have been shown and described herein, it should be understood that any arrangement calculated to achieve the same purpose may be replaced for the specific aspects shown. The present disclosure is intended to cover any and all adaptations or variations of various aspects. When browsing the above description, the combination of the above aspects and other aspects not specifically described herein will be apparent to those skilled in the art.

Claims

1. A method of operating a user equipment (UE), the method comprising: Receive reminders for accessing localized services through localized service announcements; requesting information for accessing a localized service from a home network, wherein the request causes the home network to obtain a time-limited credential from a localized service provider (LSP) providing the localized service; receiving the time-limited credential from the home network; Using the limited-time credential to establish a connection with the hosting network; and After authenticating the UE based on the time-limited credential, accessing the localized services of the LSP via the hosted network.

2. The method of claim 1, wherein: The information requested for access to the localization service includes: A connection request is made to a home network operator's web portal for accessing information of said localized service.

3. The method of claim 2, wherein: Receiving the time-limited voucher includes: The time-limited credential is received from the home network via the web portal.

4. The method according to claims 1 to 4, wherein: Receiving the time-limited voucher includes: The time-limited credential is received from the home network via a short message service (SMS) message.

5. The method according to claims 1 to 4, wherein: The method comprises: When the UE arrives at a location where the localized service will be provided, the hosted network is selected.

6. The method according to claims 1 to 5, wherein: Establishing a connection with the hosted network enables the LSP to authenticate the UE.

7. The method of claim 6, wherein: The role of the LSP is to authenticate the credential holder of the UE.

8. The method according to claims 6-7, wherein: The role of the LSP is to authenticate the Application Authentication and Key Management (AKMA) Application Function (AF) of the UE.

9. The method of claims 1-7, wherein: Access to the localization services includes: A protocol data unit (PDU) session is requested to access the localized service.

10. The method of claims 1 to 9, wherein: Access to the localization services includes: In parallel with accessing the localized services, services of the home network are accessed using an over-the-top (OTT) connection to the home network.

11. The method of claim 10, wherein: The OTT connection includes a NWu connection to a non-3GPP interworking function (N3IWF) node in the home network.

12. The method of claims 1 to 11, wherein: The method comprises: When the time-limited credential expires, request to release the UE.

13. The method of claims 1 to 12, wherein: The time-limited credential includes one or more of the following: a standalone non-public network (SNPN) identifier (ID), geographic coordinates of the hosted network, a UE ID, security credentials for accessing the home network, an AKMA anchor key (K AKMA ), a data network name (DNN) for establishing a PDU session in the hosted network, a single network slice selection assistance information (S-NSSAI) for establishing a PDU session in the hosted network, a credential for secondary authentication, and a time-based one-time password (TOTP).

14. A method of operating a localization service provider (LSP) server, the method comprising: Sending a localized service announcement to a user equipment (UE) to prompt the UE to access the localized service provided by the LSP server; Based on the UE requesting information from the home network for accessing the localized service, providing the home network with a time-limited credential for transmission to the UE; authenticating the UE based on the time-limited credential in response to the UE attempting to establish a connection with a hosted network using the time-limited credential; as well as After authenticating the UE based on the time-limited credential, access to the localized service is provided via the hosted network.

15. The method of claim 14, wherein: The method comprises: establishing a service agreement with an operator of the hosted network, wherein the service agreement defines how access to the localized service is provided; and Based on the service agreement, the hosted network is configured.

16. The method of claims 14-15, wherein: The role of the LSP is to authenticate the credential holder of the UE.

17. The method of claims 14-16, wherein: The role of the LSP is to authenticate the Application Authentication and Key Management (AKMA) Application Function (AF) of the UE.

18. The method of claim 17, wherein: The method comprises: receiving an AKMA key identifier (A-KID) from the UE in an application service request; Obtain the AKMA key (K AKMA ) corresponding to the AKMA application key (K AF );as well as Use the K AF deriving a pre-shared key; and Sending an application service response to the UE, the application service response including a method to be used by the UE to derive the K AF The counterLSP value.

19. The method of claim 18, wherein: The K AF It is the limited-time voucher.

20. The method of claims 18-19, wherein: Authenticating the UE comprises: When the UE attempts to access the localized service via the hosted network, the UE uses the service based on the K AF The UE and the LSP are mutually authenticated using Transport Layer Security (TLS).

21. The method of claims 14-16, wherein: The LSP server includes an Internet of Things (IoT) server middleware, and authenticating the UE includes: receiving a service provisioning request from the UE requesting a client certificate; sending a Subscriber Identity Module (SIM) applet certificate and a security profile corresponding to the LSP to an LSP security applet implemented by the UE; and When the UE attempts to access the localized service via the hosted network, the UE is authenticated based on the SIM applet certificate and the security profile.

22. The method of claims 14-21, wherein: The method comprises When the time limit of the limited-time credential expires, a request is made to release the UE.

23. The method of claims 14-22, wherein: The time-limited credential includes one or more of the following: a standalone non-public network (SNPN) identifier (ID), geographic coordinates of the hosted network, a UE ID, security credentials for accessing the home network, an AKMA anchor key (K AKMA ), a data network name (DNN) for establishing a PDU session in the hosted network, a single network slice selection assistance information (S-NSSAI) for establishing a PDU session in the hosted network, a credential for secondary authentication, and a time-based one-time password (TOTP).

24. One or more computer-readable media comprising instructions, wherein the instructions are executed by a processor circuit to cause the processor circuit to perform the method of claims 1-23.

25. A computer program comprising instructions as claimed in claim 24.

26. An application programming interface defining functions, methods, variables, data structures and / or protocols for a computer program as claimed in claim 25.

27. An apparatus comprising circuitry loaded with the instructions of claim 24.

28. An apparatus comprising circuitry operable to execute the instructions of claim 24.

29. An integrated circuit comprising the processor circuit of claim 24 and one or more of the one or more computer-readable media of claim 24.

30. A computing system comprising one or more computer readable media as recited in claim 24 and a processor circuit.

31. An apparatus comprising means for executing the instructions of claim 24.

32. A signal generated as a result of executing the instructions of claim 24.

33. A data unit generated as a result of executing the instructions of claim 24.

34. The data unit of claim 33, the data unit being a datagram, a network packet, a data frame, a data segment, a protocol data unit (PDU), a service data unit (SDU), a message, or a database object.

35. A signal encoded with a data unit as claimed in claim 33 or 34.

36. An electromagnetic signal carrying the instructions of claim 24.

37. An apparatus comprising means for performing the method of claims 1-23.

Images