WO2022094068A1 - Fourniture de services localisés à la demande par l'intermédiaire de réseaux d'hébergement dans des systèmes de cinquième génération (5g) - Google Patents

Fourniture de services localisés à la demande par l'intermédiaire de réseaux d'hébergement dans des systèmes de cinquième génération (5g) Download PDF

Info

Publication number
WO2022094068A1
WO2022094068A1 PCT/US2021/057035 US2021057035W WO2022094068A1 WO 2022094068 A1 WO2022094068 A1 WO 2022094068A1 US 2021057035 W US2021057035 W US 2021057035W WO 2022094068 A1 WO2022094068 A1 WO 2022094068A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
service
localized
demand
hosting
Prior art date
Application number
PCT/US2021/057035
Other languages
English (en)
Inventor
Ching-Yu Liao
Thomas Luetzenkirchen
Abhijeet Kolekar
Puneet Jain
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Priority to CN202180046340.6A priority Critical patent/CN115997396A/zh
Publication of WO2022094068A1 publication Critical patent/WO2022094068A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/44—Program or device authentication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/52—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow
    • G06F21/53—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow by executing in a restricted environment, e.g. sandbox or secure virtual machine
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/12—Applying verification of the received information
    • H04L63/123—Applying verification of the received information received data contents, e.g. message integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
    • H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/49—Connection to several service providers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8033—Rating or billing plans; Tariff determination aspects location-dependent, e.g. business or home
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8038—Roaming or handoff
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8214—Data or packet based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8228—Session based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/63—Location-dependent; Proximity-dependent
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information

Definitions

  • Various embodiments generally may relate to the field of wireless communications. For example, some embodiments may relate to providing on-demand localized services via a hosting network and using different service operators.
  • Sl-203276 is a study item proposal for Providing Access to Localized Services (PALS).
  • PALS Access to Localized Services
  • the use cases considered are in certain places or areas, like a stadium, arena, airport, university campus, convention center etc., a 5G network can be deployed or available locally; the network could provide services for temporary events and access to services on demand to local users.
  • Such services can be offered by the 5G network operator, other mobile operator(s) or 3rd party content provider(s), generating additional revenue opportunities.
  • Some examples include: a match video coverage & replay/stats at a stadium (e.g.
  • Figure 1 illustrates an example of an overall non-roaming reference architecture of policy and charging control framework for the 5G System (service based representation) in accordance with various embodiments.
  • Figure 2 illustrates an example of an overall non-roaming reference architecture of policy and charging control framework for the 5G System (reference point representation) in accordance with various embodiments.
  • Figure 3 illustrates an example of a UE configuration update procedure for transparent UE Policy delivery in accordance with various embodiments.
  • Figure 4 is a diagram showing an example of a hosting network providing access localized service for UEs of other service providers based on smart contract-based SLA in a BC network in accordance with various embodiments.
  • Figure 5 illustrates an example of a hosting network providing access localized service for UEs of other service providers based on smart contract-based SLA in BC network in accordance with various embodiments.
  • Figure 6 illustrates an example of a diagram for building relationships between network operators using an application layer approach in accordance with various embodiments.
  • Figure 7 schematically illustrates a wireless network in accordance with various embodiments.
  • Figure 8 schematically illustrates components of a wireless network in accordance with various embodiments.
  • Figure 9 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • a machine-readable or computer-readable medium e.g., a non-transitory machine-readable storage medium
  • Figure 10 depicts an example procedure for practicing the various embodiments discussed herein.
  • Figure 11 depicts another example procedure for practicing the various embodiments.
  • Figure 12 depicts another example procedure for practicing the various embodiments.
  • blockchain (BC) technology may be used to enable a smart contract based Service Level Agreement (SC-SLA) for a specific occasion, e.g. time and location, between the network operator providing access to localized service and the other network providers (aka service providers described in this disclosure), which network can be PLMN or SNPN.
  • SC-SLA Service Level Agreement
  • Various embodiments herein provide the following solutions to enhance the localized services with on demand localized services via the hosting network that can be provided by different service operators including hosting network operator, and third parties including other network operators and third parties’ application providers:
  • Solution 1 example for smart contract-based SLA for providing localized service as on demand localized service;
  • Solution 2 service requirements to enable on demand service support with localized services
  • Solution 3 on demand services configuration and subscription
  • Solution 4 on demand services selection and billing
  • Solution 5 concurrent services via hosting network A;
  • Solution 6 example for concurrent traffic towards different networks
  • Solution 7 service provider is the content provider which does not have its own network.
  • Figure 1 and Figure 2 illustrate examples of the overall architecture for policy and charging control framework in the 5G system in both service-based and reference point representation.
  • Figure 1 illustrates an example of an overall non-roaming reference architecture of policy and charging control framework for the 5G System (service based representation)
  • Figure 2 illustrates an example of an overall non-roaming reference architecture of policy and charging control framework for the 5G System (reference point representation).
  • Figure 3 illustrates an example showing how a UE policy can be delivered from the PCF to the UE by using the UE Configuration Update procedure.
  • Figure 3 illustrates an example of a UE Configuration Update procedure for transparent UE Policy delivery.
  • Embodiments of the present disclosure are directed to applying BC technologies in the telecommunication domain and help enable a 5G network to provide on demand services with PALS services that are available only at a specific occasion, e.g. time and location, based on the smart contract-based SLA for a localized service which does not need a middleman involving in the SLA creation procedure.
  • the proposed APIs are standardized northbound APIs over an 3GPP defined interface between an application of a service provider (e.g., BC user) and the 5G network;
  • a service provider e.g., BC user
  • the localized service level agreement can be setup among multiple service providers in application layer.
  • the application server of the service providers can used north bound APIs to provision required network configuration or service policies by o using 3GPP northbound APIs over N33 interface between AF and NEF, o or directly using N5 interface between AF and PCF (if AF is in trusted domain).
  • Some embodiments may include the support of both interfaces for all cases as shown in the reference architecture in Figure 4.
  • the hosting network operator can provision policies of localized services for a service provider to PCF or to UDM via NEF over N33 at the hosting network.
  • the hosting network operator can provide AF (application function) information to a service provider in the SLA of localized services to allow the service provider to provision required localized policies to PCF or UDM via NEF over N33 at the hosting network.
  • AF application function
  • the hosting network provides access to the localized services which can be owned by the hosting network operator or collaborated with third parties including other network operators and application service providers.
  • the localized services include connectivity provided by the hosting network and the services at a data network via hosting network provided connections.
  • SP-A, SP-B, and SP-C are network operators of PLMN or SNPN
  • This use case is motivated by the blockchain (BC) technologies which allow nontrusting members in a distributed peer-to-peer BC network interacting with each other in a verifiable manner without a trusted intermediary.
  • BC blockchain
  • This smart contract based service enabler allows network operators to automate the workflows of building SLAs in a cryptographically verifiable manner and enables the 5GS to facilitate the sharing of services and resources of the networks among network operators and to configure networks accordingly for the creation of localized services provided via a hosting network.
  • the smart contract-based SLA is shared among service operators using private/permissioned BC network, in which the networks of the service operators, denoted as SP-A, SP-B, SP-C, can be PLMN or SNPN and the service providers are BC members (denoted as BC-A, BC-B, BC-C) of a private/permissioned BC network.
  • the SP- A deploys a 5G network-A as hosting network providing access to localized services (PALS services) at specific time and location.
  • SP-A, SP-B, and SP-C have no SLAs in place for the localized services provided by SP-A’s hosting network-A.
  • the localized services can be used by authorized UEs of SP-A.
  • the localized service can be used by authorized UEs of SP-B, and SP-C which subscribe to the localized service based on SC-SLA.
  • the SP-A, SP-B and SP-C can provide their own on demand localized services using PDU sessions for the IP connections provided by the hosting network-A for authenticated UEs based on localized SLA established by the BC network, e.g. SC-SLA.
  • the BC-A application user of SP-A deploys a smart contract-A on the BC network for a localized service and the smart contract-A allows: the BC-A application user to create and terminate network-A services for localized services via hosting network, the BC application users of other service providers, e.g. SP-B, SP-C, etc., to subscribe the localized services from hosting network operator based on the SC-SLA included in smart contract-A deployed by the hosting network operator SP-A, the BC application users of all service providers to post their supported on demand localized services via PDU session for IP connectivity provided by the hosting network-A based on the localized service policies proposed by the posting service providers in smart contract-A. the BC application users of all service providers, e.g.
  • SP-A, SP-B, SP-C, etc. to subscribe the posted on demand localized services with the corresponding on demand localized service policies via hosting network providing access to the localized services.
  • the dedicated services are on demand that may be provided by other service providers or the UEs’ home operator. the BC-A application user to retrieve information from smart contract-A, e.g.
  • subscriber’s network ID e.g. SP-B network ID, e.g. PLMN ID or PLMN ID+NPN ID
  • subscriber’s network setting for user authentication e.g. UDM address of SP-B’ s network.
  • network ID of the Service Provider e.g. PLMN ID or PLMN ID+NPN ID
  • PLMN ID or PLMN ID+NPN ID offering on demand localized services via hosting network
  • dedicated PDU session information e.g. S-NSSAI, DNN, application ID, QoS requirements, URSP rules (referring to traffic and routing descriptors in TS23.502), and required specific services provided by network-A, etc.
  • the application ID is used to indicate the association of the application and required network slice and DNN.
  • the BC-A application user i.e. hosting network operator
  • SP-A network information e.g. AF (application function) address for other service providers to provision or modify or update required service configurations at the hosting network.
  • the provision or modify or update required service configurations at the hosting network can be performed by SP-A based on the smart contract based SLA between SP-A and SP-B/SP-C in the application layer.
  • the BC-B and BC-C application users can subscribe this localized services using smart contractwith the hosting network operator-A on the BC network for their UEs and configures their UEs with localized service.
  • the temporary SLAs subject to a specific service time and areas using smart contract based blockchain technologies are an example for building temporary relationship among hosting network operator and third parties service providers which includes other network operators and third-party application providers.
  • the coverage of this disclosure does not limit the usage of the smart contract based blockchain technologies for SLA.
  • the applications that can provide similar automatic electronic agreement (e-agreement) for building temporary SLA and applying to the network configuration at the hosting network are within coverage of this disclosure, as shown in Figure 6, wherein SP-A/SP-B/SP-C applications are used for general description of application users.
  • Solution! service requirements to enable support for localized services via hosting network based on smart contract based SLA among service providers
  • the 5G network of a hosting network operator providing access localized service may enable mechanisms to configure the following network policies of other service providers for authenticating their UEs that attempt to register and use their home network services via the hosting network:
  • traffic routing policies and network configuration e.g. network address of target service operator, e.g. N3IWF, SMF, UPF, PSA, etc. for routing a UE’s traffic from hosting network to its home network which subscribes to the localized services via hosting network when the UEs’ home network is not available.
  • target service operator e.g. N3IWF, SMF, UPF, PSA, etc.
  • the 5G network of a hosting network operator providing access localized service shall enable appropriate APIs for other service providers subscribing to localized services from the hosting network operator to configure the following network policies of other service providers for authenticating their UEs which attempt to register and use their home network services via the hosting network:
  • traffic routing policies and network configuration at the hosting network e.g. network address of target service operator, e.g. N3IWF, SMF, UPF, PSA, etc. for routing a serving UE’s traffic to its home network which subscribes to the localized services via hosting network when the UEs’ home network is not available.
  • target service operator e.g. N3IWF, SMF, UPF, PSA, etc.
  • the 5G hosting network may enable appropriate APIs to expose network capability based on the following network configuration:
  • the 5G hosting network may enable appropriate APIs to expose network identification information for providing access localized service at a specific occasion, e.g. time and location, to other service operators including other network operators and third party application providers, wherein the network identification information can include:
  • the 5G hosting network providing access to localized service may support appropriate APIs for other service providers to provision the following information related to PDU session parameters for IP connectivity for their on demand localized services via the hosting network, for example:
  • Network configuration for routing the traffic to access on demand localized services at the data network of a service provider hosting network via hosting network.
  • Localized services subscribers information of the third parties network operators, e.g. service provider network ID (PLMN ID or PLMN ID+ NPN ID, or an ID that can identify the service provider of on-demand localized service (of SP-B) via hosting network for charging purpose.
  • service provider network ID PLMN ID or PLMN ID+ NPN ID
  • the 5G network of a hosting network providing access to localized service via the hosting network may be able to allow a UE to manually select eligible on-demand localized services which are provided by other service providers and routed via the hosting network.
  • the 5G network of a hosting network providing access to localized service via the hosting network may be able to collect charging records for on-demand localized service based on service and charging policies provided by the third party service providers including hosting network operator, other network operators and third party application providers.
  • the 5G network of a hosting network providing access to localized service via the hosting network may be able to support required PDU sessions of IP connections at hosting network for UEs to simultaneously use its home network service, and localized services provided by hosting network or other service providers.
  • the UE configured with localized service authorization may be able to simultaneously use home network service and localized services via hosting network in which the localized services are provided by hosting network or third parties service providers (including other network operators and application service operators) via a hosting network providing access localized service when only hosting network is available.
  • hosting network in which the localized services are provided by hosting network or third parties service providers (including other network operators and application service operators) via a hosting network providing access localized service when only hosting network is available.
  • the UE configured with authorization of localized services via the hosting network may be able to simultaneously use home network service directly and localized services provided by hosting network or third parties (including other network operator and application service providers via a hosting network when both home network and hosting network are available.
  • the BC-B application user of SP-B can post on-demand localized services via hosting network of SP-A with services and charging policies.
  • the other BC application users subscribed to hosting network providing to localized services are eligible to subscribe to all posted on-demand localized services.
  • the BC-B application user of SP-B can request SP-B’s network via APIs for configuring service policy of a new on-demand localized service using IP connectivity provided by hosting network-A at a specific time and location and obtains the service configuration from SP-B’s network, which can be subscribed by third parties service operators, that include:
  • N3IWF Network configuration for routing the on demand localized service to the SP-B’s network from the hosting network, e.g. N3IWF, SP-B SMF and UPF addresses.
  • - Required IP connectivity parameters e.g. S-NSSAI, DNN, required QoS parameters, etc.
  • the application ID is used to indicate the association of the application and required network slice and DNN. There can be more than one application IDs for different on demand localized services in one combination of S-NSSAI and DNN.
  • SP- Required specific hosting network s services of the application, e.g. Location based service, timing resilience service, multicast and broadcast service, service function chaining, etc.
  • SP-A network configuration for on demand localized service provided by SP-B via hosting network e.g. Location based service, timing resilience service, multicast and broadcast service, service function chaining, etc.
  • BC-A application user of the SP-A or BC-B application user of the SP-B provision provisions service parameters to SP-A’s network via APIs, including: on-demand localized service provider ID of SP-B, e.g. (PLMN ID or PLMN ID+ NPN ID, or an ID that can identify the service provider
  • service policies of on-demand localized services subscribers information, e.g. service provider ID (PLMN ID or PLMN ID+ NPN ID, or an ID that can identify the service provider of on-demand localized service (of SP- B) for charging purpose.
  • service provider ID PLMN ID or PLMN ID+ NPN ID, or an ID that can identify the service provider of on-demand localized service (of SP- B) for charging purpose.
  • Required IP connectivity parameters e.g. S-NSSAI, DNN, required QoS parameters, etc.
  • the application ID is used to indicate the association of the application and required network slice and DNN. There can be more than one application IDs for different on demand localized services in one combination of S-NSSAI and DNN.
  • Required specific hosting network services of the application, e.g. Location based service, timing resilience service, multicast and broadcast service, service function chaining, etc.
  • the hosting network can establish a default PDU session for IP connection to present the list of on-demand localized services via hosting network to the UE.
  • the hosting network may also instruct the home network to send updated URSP rules to the UE related to on-demand localized services via hosting network.
  • the on demand localized services list presented to the UE are subscribed by UE’s home network operator. It allows UEs to select and use on-demand localized service via hosting network-A which provides required PDU session for IP connections using a S-NSSAI, DNN, and QoS parameters.
  • the hosting network can collect charging records, e.g. usage of applications, etc., and provide to UE’s home network operator based on service and charging policies provided by the on-demand localized service provider in smart contract.
  • the UE can simultaneously use the hosting network of SPA’s PDU session for IP connection to use its home network service of SP-C and a selected on- demand localized service provided by SP-B.
  • the hosting network can forward the traffic of the UEs between hosting-network and SP-B’s network. This feature enables traffic routing using a local breakout via a hosting network for third parties’ provided on demand localized services.
  • the hosting network can forward the traffic of the UEs for on-demand localized service provided by SP-A between UE and hosting network. This feature enables traffic routing using local breakout at a hosting network.
  • the hosting network can forward the traffic of the UEs between its home network of a service provider (e.g. SP-C) and hosting network-A. This feature enables home routed traffic routing via hosting network.
  • a service provider e.g. SP-C
  • the UE can concurrently use any combination of these on demand localized services via hosting network, in which the localized service can be provided by its home network, local hosting network, and third party service providers.
  • SP-A deploys a hosting network-A providing access to localized service via hosting network and creates a smart contract with localized service level agreement for sharing localized services using blockchain technologies at a private data network with application members of service providers, e.g. SP-A, SP-B, and SP-C.
  • SP-B’s network is not available in the island and SP-C’s network is only available at some zones.
  • Both SP-B and SP-C subscribe to the localized service from SP-A for their UEs to access the hosting network and use on demand localized services which may be provided by the hosting network provider or third parties (other network operator or application service providers).
  • SP-A deploys on demand localized services for streaming live video and immersive media in different zones.
  • SP-B also provides on demand localized services via hosting network, e.g. gaming, on demand movies, etc.
  • the hosting network-A starts to provision localized services via hosting network based on localized SLA and broadcast related information for UEs in the hosting network-A coverage.
  • the UE-C has SP-C’s subscription.
  • the SP-C subscribed to SP-A’s localized services configures its UEs with authorization of localized services via hosting network of SP-A.
  • the UE-C configured with localized services authorization found that only SP-A network is available and then selects hosting network to use its home network services of SP-C via hosting network-A after successful user authentication by its home network of SP-C.
  • UE-C configured with localized services can select hosting network of the SP-A and use both SP-A and SP-C networks for different services simultaneously based on UE configuration, e.g. using SP-A network connection for on demand localized service to interact with holograms of live animals in the areas (which enables the specific network-A services) and using SP-C home network connection for sharing live videos in social media.
  • SP-B On demand localized service for watching on demand movie and using SP-A’s on demand localized service to watch the live wildlife’s night life in the areas.
  • the hosting network of SP-A establishes required PDU sessions for IP connections and routes the UE-C’s traffic to SP-A locally and SP-B’s network, respectively.
  • Solution 7 service provider is the content provider which does not have its own network
  • a SP-D is the third party application service provider which does not have its own network. This SP-D can register as a BC application user of the BC network for smart contract based SLA.
  • the SP-D can subscribe to the hosting network-A for localized service and post its on- demand localized service via hosting network-A.
  • the hosting network of SP-A can provision service configuration for service policies, charging policies, traffic routing policy, and PDU session parameters for IP connection (S- NSSAI, DNN, Application ID, URSP rules (referring to traffic and routing descriptors in TS23.502), application server address, etc.)
  • the UE can select this on-demand localized service provided by SP-D if its SP-C home network subscribes localized service of hosting network-A.
  • the UE can be billed for the usage of this SP-D service by its home network of SP-C or online payment method.
  • FIGS 7-8 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
  • Figure 7 illustrates a network 700 in accordance with various embodiments.
  • the network 700 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems.
  • 3GPP technical specifications for LTE or 5G/NR systems 3GPP technical specifications for LTE or 5G/NR systems.
  • the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.
  • the network 700 may include a UE 702, which may include any mobile or non-mobile computing device designed to communicate with a RAN 704 via an over-the-air connection.
  • the UE 702 may be communicatively coupled with the RAN 704 by a Uu interface.
  • the UE 702 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.
  • the network 700 may include a plurality of UEs coupled directly with one another via a sidelink interface.
  • the UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
  • the UE 702 may additionally communicate with an AP 706 via an over-the-air connection.
  • the AP 706 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 704.
  • the connection between the UE 702 and the AP 706 may be consistent with any IEEE 802.11 protocol, wherein the AP 706 could be a wireless fidelity (Wi-Fi®) router.
  • the UE 702, RAN 704, and AP 706 may utilize cellular- WLAN aggregation (for example, LWA/LWIP).
  • Cellular- WLAN aggregation may involve the UE 702 being configured by the RAN 704 to utilize both cellular radio resources and WLAN resources.
  • the RAN 704 may include one or more access nodes, for example, AN 708.
  • AN 708 may terminate air-interface protocols for the UE 702 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 708 may enable data/voice connectivity between CN 720 and the UE 702.
  • the AN 708 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool.
  • the AN 708 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc.
  • the AN 708 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
  • the RAN 704 may be coupled with one another via an X2 interface (if the RAN 704 is an LTE RAN) or an Xn interface (if the RAN 704 is a 5G RAN).
  • the X2/Xn interfaces which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.
  • the ANs of the RAN 704 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 702 with an air interface for network access.
  • the UE 702 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 704.
  • the UE 702 and RAN 704 may use carrier aggregation to allow the UE 702 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell.
  • a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG.
  • the first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.
  • the RAN 704 may provide the air interface over a licensed spectrum or an unlicensed spectrum.
  • the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells.
  • the nodes Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • the UE 702 or AN 708 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications.
  • An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE.
  • An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like.
  • an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs.
  • the RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic.
  • the RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services.
  • the components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.
  • the RAN 704 may be an LTE RAN 710 with eNBs, for example, eNB 712.
  • the LTE RAN 710 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc.
  • the LTE air interface may rely on CSI- RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE.
  • the LTE air interface may operating on sub-6 GHz bands.
  • the RAN 704 may be an NG-RAN 714 with gNBs, for example, gNB 716, or ng-eNBs, for example, ng-eNB 718.
  • the gNB 716 may connect with 5G-enabled UEs using a 5G NR interface.
  • the gNB 716 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface.
  • the ng-eNB 718 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface.
  • the gNB 716 and the ng-eNB 718 may connect with each other over an Xn interface.
  • the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 714 and a UPF 748 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN714 and an AMF 744 (e.g., N2 interface).
  • NG-U NG user plane
  • N-C NG control plane
  • the NG-RAN 714 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data.
  • the 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface.
  • the 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking.
  • the 5G- NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz.
  • the 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.
  • the 5G-NR air interface may utilize BWPs for various purposes.
  • BWP can be used for dynamic adaptation of the SCS.
  • the UE 702 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 702, the SCS of the transmission is changed as well.
  • Another use case example of BWP is related to power saving.
  • multiple BWPs can be configured for the UE 702 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios.
  • a BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 702 and in some cases at the gNB 716.
  • a BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.
  • the RAN 704 is communicatively coupled to CN 720 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 702).
  • the components of the CN 720 may be implemented in one physical node or separate physical nodes.
  • NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 720 onto physical compute/storage resources in servers, switches, etc.
  • a logical instantiation of the CN 720 may be referred to as a network slice, and a logical instantiation of a portion of the CN 720 may be referred to as a network sub-slice.
  • the CN 720 may be an LTE CN 722, which may also be referred to as an EPC.
  • the LTE CN 722 may include MME 724, SGW 726, SGSN 728, HSS 730, PGW 732, and PCRF 734 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 722 may be briefly introduced as follows.
  • the MME 724 may implement mobility management functions to track a current location of the UE 702 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.
  • the SGW 726 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 722.
  • the SGW 726 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the SGSN 728 may track a location of the UE 702 and perform security functions and access control. In addition, the SGSN 728 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 724; MME selection for handovers; etc.
  • the S3 reference point between the MME 724 and the SGSN 728 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.
  • the HSS 730 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 730 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • An S6a reference point between the HSS 730 and the MME 724 may enable transfer of subscription and authentication data for authenticating/ authorizing user access to the LTE CN 720.
  • the PGW 732 may terminate an SGi interface toward a data network (DN) 736 that may include an application/content server 738.
  • the PGW 732 may route data packets between the LTE CN 722 and the data network 736.
  • the PGW 732 may be coupled with the SGW 726 by an S5 reference point to facilitate user plane tunneling and tunnel management.
  • the PGW 732 may further include a node for policy enforcement and charging data collection (for example, PCEF).
  • the SGi reference point between the PGW 732 and the data network 7 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services.
  • the PGW 732 may be coupled with a PCRF 734 via a Gx reference point.
  • the PCRF 734 is the policy and charging control element of the LTE CN 722.
  • the PCRF 734 may be communicatively coupled to the app/content server 738 to determine appropriate QoS and charging parameters for service flows.
  • the PCRF 732 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.
  • the CN 720 may be a 5GC 740.
  • the 5GC 740 may include an AUSF 742, AMF 744, SMF 746, UPF 748, NSSF 750, NEF 752, NRF 754, PCF 756, UDM 758, and AF 760 coupled with one another over interfaces (or “reference points”) as shown.
  • Functions of the elements of the 5GC 740 may be briefly introduced as follows.
  • the AUSF 742 may store data for authentication of UE 702 and handle authentication- related functionality.
  • the AUSF 742 may facilitate a common authentication framework for various access types.
  • the AUSF 742 may exhibit an Nausf service-based interface.
  • the AMF 744 may allow other functions of the 5GC 740 to communicate with the UE 702 and the RAN 704 and to subscribe to notifications about mobility events with respect to the UE 702.
  • the AMF 744 may be responsible for registration management (for example, for registering UE 702), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization.
  • the AMF 744 may provide transport for SM messages between the UE 702 and the SMF 746, and act as a transparent proxy for routing SM messages.
  • AMF 744 may also provide transport for SMS messages between UE 702 and an SMSF.
  • AMF 744 may interact with the AUSF 742 and the UE 702 to perform various security anchor and context management functions.
  • AMF 744 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 704 and the AMF 744; and the AMF 744 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection.
  • AMF 744 may also support NAS signaling with the UE 702 over an N3 IWF interface.
  • the SMF 746 may be responsible for SM (for example, session establishment, tunnel management between UPF 748 and AN 708); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 748 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 744 over N2 to AN 708; and determining SSC mode of a session.
  • SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 702 and the data network 736.
  • the UPF 748 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 736, and a branching point to support multi-homed PDU session.
  • the UPF 748 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering.
  • UPF 748 may include an uplink classifier to support routing traffic flows to a data network.
  • the NSSF 750 may select a set of network slice instances serving the UE 702.
  • the NSSF 750 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed.
  • the NSSF 750 may also determine the AMF set to be used to serve the UE 702, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 754.
  • the selection of a set of network slice instances for the UE 702 may be triggered by the AMF 744 with which the UE 702 is registered by interacting with the NSSF 750, which may lead to a change of AMF.
  • the NSSF 750 may interact with the AMF 744 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 750 may exhibit an Nnssf service-based interface.
  • the NEF 752 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 760), edge computing or fog computing systems, etc.
  • the NEF 752 may authenticate, authorize, or throttle the AFs.
  • NEF 752 may also translate information exchanged with the AF 760 and information exchanged with internal network functions. For example, the NEF 752 may translate between an AF-Service-Identifier and an internal 5GC information.
  • NEF 752 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 752 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 752 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 752 may exhibit an Nnef service-based interface.
  • the NRF 754 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 754 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 754 may exhibit the Nnrf service-based interface.
  • the PCF 756 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior.
  • the PCF 756 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 758.
  • the PCF 756 exhibit an Npcf service-based interface.
  • the UDM 758 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 702. For example, subscription data may be communicated via an N8 reference point between the UDM 758 and the AMF 744.
  • the UDM 758 may include two parts, an application front end and a UDR.
  • the UDR may store subscription data and policy data for the UDM 758 and the PCF 756, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 702) for the NEF 752.
  • the Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 758, PCF 756, and NEF 752 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR.
  • the UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions.
  • the UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management.
  • the UDM 758 may exhibit the Nudm service-based interface.
  • the AF 760 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.
  • the 5GC 740 may enable edge computing by selecting operator/3 rd party services to be geographically close to a point that the UE 702 is attached to the network. This may reduce latency and load on the network.
  • the 5GC 740 may select a UPF 748 close to the UE 702 and execute traffic steering from the UPF 748 to data network 736 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 760. In this way, the AF 760 may influence UPF (re)selection and traffic routing.
  • the network operator may permit AF 760 to interact directly with relevant NFs. Additionally, the AF 760 may exhibit an Naf service-based interface.
  • the data network 736 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/content server 738.
  • FIG 8 schematically illustrates a wireless network 800 in accordance with various embodiments.
  • the wireless network 800 may include a UE 802 in wireless communication with an AN 804.
  • the UE 802 and AN 804 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.
  • the UE 802 may be communicatively coupled with the AN 804 via connection 806.
  • the connection 806 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.
  • the UE 802 may include a host platform 808 coupled with a modem platform 810.
  • the host platform 808 may include application processing circuitry 812, which may be coupled with protocol processing circuitry 814 of the modem platform 810.
  • the application processing circuitry 812 may run various applications for the UE 802 that source/sink application data.
  • the application processing circuitry 812 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations
  • the protocol processing circuitry 814 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 806.
  • the layer operations implemented by the protocol processing circuitry 814 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.
  • the modem platform 810 may further include digital baseband circuitry 816 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 814 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, 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 spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.
  • PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may
  • the modem platform 810 may further include transmit circuitry 818, receive circuitry 820, RF circuitry 822, and RF front end (RFFE) 824, which may include or connect to one or more antenna panels 826.
  • the transmit circuitry 818 may include a digital -to-analog converter, mixer, intermediate frequency (IF) components, etc.
  • the receive circuitry 820 may include an analog-to-digital converter, mixer, IF components, etc.
  • the RF circuitry 822 may include a low-noise amplifier, a power amplifier, power tracking components, etc.
  • RFFE 824 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc.
  • transmit/receive components may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc.
  • the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.
  • the protocol processing circuitry 814 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.
  • a UE reception may be established by and via the antenna panels 826, RFFE 824, RF circuitry 822, receive circuitry 820, digital baseband circuitry 816, and protocol processing circuitry 814.
  • the antenna panels 826 may receive a transmission from the AN 804 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 826.
  • a UE transmission may be established by and via the protocol processing circuitry 814, digital baseband circuitry 816, transmit circuitry 818, RF circuitry 822, RFFE 824, and antenna panels 826.
  • the transmit components of the UE 804 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 826.
  • the AN 804 may include a host platform 828 coupled with a modem platform 830.
  • the host platform 828 may include application processing circuitry 832 coupled with protocol processing circuitry 834 of the modem platform 830.
  • the modem platform may further include digital baseband circuitry 836, transmit circuitry 838, receive circuitry 840, RF circuitry 842, RFFE circuitry 844, and antenna panels 846.
  • the components of the AN 804 may be similar to and substantially interchangeable with like-named components of the UE 802.
  • the components of the AN 808 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.
  • Figure 9 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • Figure 9 shows a diagrammatic representation of hardware resources 900 including one or more processors (or processor cores) 910, one or more memory /storage devices 920, and one or more communication resources 930, each of which may be communicatively coupled via a bus 940 or other interface circuitry.
  • a hypervisor 902 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 900.
  • the processors 910 may include, for example, a processor 912 and a processor 914.
  • the processors 910 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 such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • the memory /storage devices 920 may include main memory, disk storage, or any suitable combination thereof.
  • the memory /storage devices 920 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as 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.
  • DRAM dynamic random access memory
  • SRAM static random access memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory solid-state storage, etc.
  • the communication resources 930 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 904 or one or more databases 906 or other network elements via a network 908.
  • the communication resources 930 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.
  • Instructions 950 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 910 to perform any one or more of the methodologies discussed herein.
  • the instructions 950 may reside, completely or partially, within at least one of the processors 910 (e.g., within the processor’s cache memory), the memory /storage devices 920, or any suitable combination thereof.
  • any portion of the instructions 950 may be transferred to the hardware resources 900 from any combination of the peripheral devices 904 or the databases 906. Accordingly, the memory of processors 910, the memory /storage devices 920, the peripheral devices 904, and the databases 906 are examples of computer-readable and machine-readable media.
  • the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 7-9, or some other figure herein may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof.
  • the process 1000 may include, at 1005, deploying, based on smart contract information associated with a localized service, a smart contract for the localized service on a blockchain (BC) network.
  • the process further includes, at 1010, providing configuration information associated with the localized service to a service provider to provision, modify, or update a service configuration at the hosting network.
  • the process further includes, at 1015, posting an indication of a supported on-demand localized service via a protocol data unit (PDU) session for Internet protocol (IP) connectivity provided by the hosting network based on a localized service policy in the smart contract.
  • PDU protocol data unit
  • IP Internet protocol
  • Figure 11 illustrates another process in accordance with various embodiments.
  • the process 1100 includes, at 1105, determining, for a first network, network policy configuration information associated with a localized service, wherein the network policy configuration information includes an indication of: unified data management (UDM) address information for UE authentication, or a traffic routing policy.
  • the process further includes, at 1110, configuring a network policy service of a second network using the network policy configuration information.
  • the process further includes, at 1115, providing an application programming interface (API) to a service provider to provision information related to protocol data unit (PDU) session parameters for Internet protocol (IP) connectivity for an on- demand localized service.
  • API application programming interface
  • Figure 12 illustrates another process in accordance with various embodiments.
  • the process 1200 includes, at 1205, determining service policy configuration information for an on-demand localized service provided by a hosting network at a predetermined time or location.
  • the process further includes, at 1210, providing the service policy configuration information to a service provider for accessing the on-demand localized service.
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • Example 1 may include a method in which the 5G network shall enable mechanisms for network operator providing access localized service to configure the following network policies of a service provider for authenticating their UEs attempt to register and use their home network services via the hosting network including one or more of:
  • traffic routing policies and network configuration e.g. network address of target service operator, e.g. N3IWF, SMF, UPF, PSA, etc. for routing a roaming UE’s traffic to its home network which subscribes to the PALS service when the UEs’ home network is not available.
  • target service operator e.g. N3IWF, SMF, UPF, PSA, etc.
  • the 5G network shall enable appropriate APIs for a service provider subscribing to PALS service from SP-A to configure one or more of the following network policies of a service provider for authenticating their UEs attempt to register and use their home network services via the hosting network:
  • traffic routing policies and network configuration e.g. network address of target service operator, e.g. N3IWF, SMF, UPF, PSA, etc. for routing a roaming UE’s traffic to its home network which subscribes to the PALS service when the UEs’ home network is not available.
  • target service operator e.g. N3IWF, SMF, UPF, PSA, etc.
  • Example 2 may include the 5G network shall enable appropriate APIs to expose network capability based on one or more of the following network configurations:
  • the 5G network shall enable appropriate APIs to expose network identification information for providing access localized service at a specific occasion, e.g. time and location, to other network operators, wherein the network identification information may include one or more of:
  • PALS Service Group ID which represents all SPs subscribers of the PALS service
  • a configured ID for home network authentication and/or
  • Example 3 may include the 5G network providing access localized service shall support appropriate APIs for other service providers to provision one or more of the following information related to PDU session parameters for IP connectivity for their on demand dedicated service via the hosting network, e.g.
  • subscribers information, e.g. service provider ID (PLMN ID or PLMN ID+ NPN ID, or an ID that can identify the service provider of on-demand dedicated service (of SP- B) for charging purpose.
  • service provider ID PLMN ID or PLMN ID+ NPN ID
  • an ID that can identify the service provider of on-demand dedicated service (of SP- B) for charging purpose PLMN ID or PLMN ID+ NPN ID, or an ID that can identify the service provider of on-demand dedicated service (of SP- B) for charging purpose.
  • Example 4 may include the 5G network providing access localized service shall be able to allow a roaming UE to manually select eligible on-demand dedicated services which are provided by different service providers and routed via the hosting network.
  • Example 5 may include the 5G network providing access localized service shall be able to collect charging records for on-demand dedicated service based on service and charging policies provided by the on-demand dedicated service provider.
  • Example 6 may include the 5G network providing access localized service shall be able to support required PDU sessions of IP connections at hosting network for UEs to simultaneously use its home network service, and on-demand dedicated services provided by hosting network or other service providers.
  • Example 7 may include the UE configured with PALS service shall be able to simultaneously use home network service and on-demand dedicated services provided by hosting network or other service providers via a hosting network providing access localized service when only hosting network is available.
  • Example 8 may include the UE configured with PALS service shall be able to simultaneously use home network service directly and on-demand dedicated services provided by hosting network or other service providers via a hosting network providing access localized service when both home network and hosting network are available.
  • Example XI includes an apparatus of a hosting network comprising: memory to store smart contract information associated with a localized service; and processing circuitry, coupled with the memory, to: deploy, based on the smart contract information, a smart contract for the localized service on a blockchain (BC) network; and provide configuration information associated with the localized service to a service provider to provision, modify, or update a service configuration at the hosting network; and post an indication of a supported on-demand localized service via a protocol data unit (PDU) session for Internet protocol (IP) connectivity provided by the hosting network based on a localized service policy in the smart contract.
  • PDU protocol data unit
  • IP Internet protocol
  • Example X2 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to receive a subscription to the posted on-demand localized service from the service provider.
  • Example X3 includes the apparatus of example XI or some other example herein, wherein the smart contract for the localized service is to allow creation and termination of network services for the localized service.
  • Example X4 includes the apparatus of example XI or some other example herein, wherein the smart contract for the localized service includes information associated with a smart contract based service level agreement (SC-SLA), a network identifier, or a subscriber network setting for user authentication.
  • SC-SLA smart contract based service level agreement
  • Example X5 includes the apparatus of example XI or some other example herein, wherein the smart contract for the localized service includes information associated with the posted on-demand localized service.
  • Example X6 includes the apparatus of example X5 or some other example herein, wherein the information associated with the posted on-demand localized service includes an indication of: a network identifier of a service provider offering the posted on-demand localized service, dedicated PDU session information, a user equipment route selection policy (URSP) rule, a required service, or an application identifier.
  • URSP user equipment route selection policy
  • Example X7 includes the apparatus of any of examples XI -X6 or some other example herein, wherein the processing circuitry is further to provide access to the localized service or the posted on-demand localized service by the service provider within a predetermined time period or location area.
  • Example X8 includes the apparatus of any of examples XI -X7 or some other example herein, wherein the apparatus includes a policy and charging control framework or portion thereof.
  • Example X9 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause one or more functions of a policy and charging control framework to: determine, for a first network, network policy configuration information associated with a localized service, wherein the network policy configuration information includes an indication of: unified data management (UDM) address information for UE authentication, or a traffic routing policy; configure a network policy service of a second network using the network policy configuration information; and provide an application programming interface (API) to a service provider to provision information related to protocol data unit (PDU) session parameters for Internet protocol (IP) connectivity for an on-demand localized service.
  • UDM unified data management
  • API application programming interface
  • Example XI 0 includes the one or more computer-readable media of example X9 or some other example herein, wherein the information related to PDU session parameters for IP connectivity include an indication of: a service identification of the on-demand localized service and a corresponding human-readable identification for the on-demand localized service, a required PDU session for IP connectivity parameter, application information, a user equipment route selection policy (URSP) rule, an on-demand localized service provider identifier, a required service, or a network configuration for routing traffic to access the on- demand localized service.
  • URSP user equipment route selection policy
  • Example XI 1 includes the one or more computer-readable media of example X9 or some other example herein, wherein the network policy configuration information is to provide access to the localized service within a predetermined time period or location area.
  • Example XI 2 includes the one or more computer-readable media of example X9 or some other example herein, wherein the network policy configuration information includes an indication of: a spectrum resource, a network slice allocation, a default protocol data unit (PDU) session for an Internet protocol (IP) connection, or a network service capability.
  • the network policy configuration information includes an indication of: a spectrum resource, a network slice allocation, a default protocol data unit (PDU) session for an Internet protocol (IP) connection, or a network service capability.
  • PDU protocol data unit
  • IP Internet protocol
  • Example XI 3 includes the one or more computer-readable media of any of examples X9-X12 or some other example herein, wherein the media further stores instructions to configure the network policy service via an application programming interface (API).
  • API application programming interface
  • Example XI 4 includes the one or more computer-readable media of example X9 or some other example herein, wherein the media further stores instructions to provide the second network with network identification information.
  • Example XI 5 includes the one or more computer-readable media of example X14 or some other example herein, wherein the network identification information includes an indication of a hosting network identifier or one or more localized service group identifiers.
  • Example XI 6 includes the one or more computer-readable media of example X9 or some other example herein, wherein the media further stores instructions to provide the second network with information for discovering and using the localized service.
  • Example XI 7 includes the one or more computer-readable media of example XI 6 or some other example herein, wherein the information for discovering and using the localized service includes an indication of: an authorization of the localized service, network identity information, or a localized service group identifier.
  • Example XI 8 includes the one or more computer-readable media of any of examples X9-X17 or some other example herein, wherein the policy and charging control framework is implemented by a hosting network or portion thereof.
  • Example XI 9 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause one or more functions of a hosting network to: determine service policy configuration information for an on-demand localized service provided by the hosting network at a predetermined time or location; and provide the service policy configuration information to a service provider for accessing the on-demand localized service.
  • Example X20 includes the one or more computer-readable media of example XI 9 or some other example herein, wherein the service policy configuration information includes a service identification of the on-demand localized service and a corresponding human- readable identification for the on-demand localized service.
  • Example X21 includes the one or more computer-readable media of example XI 9 or some other example herein, wherein the service policy configuration information includes network configuration information for routing the on-demand localized service to a network of the service provider from the hosting network.
  • Example X22 includes the one or more computer-readable media of example XI 9 or some other example herein, wherein the service policy configuration information includes an IP connectivity parameter.
  • Example X23 includes the one or more computer-readable media of example XI 9 or some other example herein, wherein the service policy configuration information includes an application identifier associated with the on-demand localized service.
  • Example X24 includes the one or more computer-readable media of example XI 9 or some other example herein, wherein the service policy configuration information includes a URSP rule for traffic routing.
  • Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-X24, or any other method or process described herein.
  • Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-X24, or any other method or process described herein.
  • Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-X24, or any other method or process described herein.
  • Example Z04 may include a method, technique, or process as described in or related to any of examples 1-X24, or portions or parts thereof.
  • Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-X24, or portions thereof.
  • Example Z06 may include a signal as described in or related to any of examples 1- X24, or portions or parts thereof.
  • 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-X24, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example Z08 may include a signal encoded with data as described in or related to any of examples 1-X24, or portions or parts thereof, or otherwise described in the present disclosure.
  • 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-X24, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-X24, or portions thereof.
  • Example Zll may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-X24, or portions thereof.
  • Example Z12 may include a signal in a wireless network as shown and described herein.
  • Example Z13 may include a method of communicating in a wireless network as shown and described herein.
  • Example Z14 may include a system for providing wireless communication as shown and described herein.
  • Example Z15 may include a device for providing wireless communication as shown and described herein.
  • AMBRAggregate Channel 85 Checksum Maximum Bit Rate BER Bit Error Ratio CCA Clear Channel AMF Access and BFD Beam Assessment Mobility Failure Detection CCE Control
  • DM-RS DMRS Datarates for GSM 80 Physical
  • DSLAM DSL 60 Access, ETWS Earthquake and
  • E-UTRAN Evolved CHannel 70 RAN, GSM EDGE
  • IMS IP Multimedia Provider received power
  • Narrowband Function 80 PBCH Physical
  • PDCP Packet Data Network Function PSCCH Physical Convergence Protocol Descriptor Sidelink Control PDN Packet Data 45 PNFR Physical Channel Network, Public Network Function PSFCH Physical
  • P-GW PDN Gateway PRG Physical Network
  • PHICH Physical resource block
  • PT-RS Phase-tracking hybrid-ARQ 60 group reference signal indicator
  • ProSe Proximity PTT Push-to-Talk channel Services 95 PUCCH Physical
  • Satellite System indicator value 85 Identifier
  • S-GW Serving 55 Management Frequency Time Gateway SCS Subcarrier Diversity, SFN
  • SIM Subscriber 40 Scheduling SSS Secondary Identity Module Request Synchronization SIP Session SRB Signalling 75 Signal Initiated Protocol Radio Bearer SSSG Search Space SiP System in SRS Sounding Set Group
  • SoC System on Chip n Signal based Block SON Self-Organizing Reference TBS Transport Network 65 Signal Received Block Size
  • TRP TRxP Data Storage 100 Terrestrial Radio
  • Descriptor 65 RESponse VNFMVNF Manager XOR exclusive OR
  • circuitry refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality.
  • FPD field-programmable device
  • FPGA field-programmable gate array
  • PLD programmable logic device
  • CPLD complex PLD
  • HPLD high-capacity PLD
  • DSPs digital signal processors
  • the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality.
  • the term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
  • processor circuitry refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data.
  • Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information.
  • processor circuitry may refer to one or more application processors, one or more baseband processors, a physical central processing unit (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, such as program code, software modules, and/or functional processes.
  • Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like.
  • the one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators.
  • CV computer vision
  • DL deep learning
  • application circuitry and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”
  • interface circuitry refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices.
  • interface circuitry may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.
  • user equipment or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network.
  • user equipment or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc.
  • user equipment or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.
  • network element refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services.
  • network element may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.
  • computer system refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.
  • appliance refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource.
  • program code e.g., software or firmware
  • a “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.
  • resource refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like.
  • a “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s).
  • a “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc.
  • network resource or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network.
  • system resources may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.
  • channel refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream.
  • channel may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated.
  • link refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.
  • instantiate refers to the creation of an instance.
  • An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.
  • Coupled may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact 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 the elements that are said to be coupled with each other.
  • directly coupled may mean that two or more elements are in direct contact with one another.
  • communicatively coupled may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like.
  • the term “information element” refers to a structural element containing one or more fields.
  • the term “field” refers to individual contents of an information element, or a data element that contains content.
  • the term “SMTC” refers to an S SB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.
  • SSB refers to an SS/PBCH block.
  • a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.
  • Primary SCG Cell refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.
  • Secondary Cell refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.
  • Secondary Cell Group refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC.
  • the term “Serving Cell” refers to the primary cell for a UE in RRC CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.
  • the term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA/.
  • the term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Theoretical Computer Science (AREA)
  • Multimedia (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Computing Systems (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers modes de réalisation de la présente invention concernent la fourniture de services localisés à la demande par l'intermédiaire d'un réseau d'hébergement et à l'aide de différents opérateurs de services. D'autres modes de réalisation peuvent être divulgués ou revendiqués.
PCT/US2021/057035 2020-10-30 2021-10-28 Fourniture de services localisés à la demande par l'intermédiaire de réseaux d'hébergement dans des systèmes de cinquième génération (5g) WO2022094068A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202180046340.6A CN115997396A (zh) 2020-10-30 2021-10-28 在第五代（5g）系统中经由托管网络提供按需本地化服务

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063108199P 2020-10-30 2020-10-30
US63/108,199 2020-10-30

Publications (1)

Publication Number Publication Date
WO2022094068A1 true WO2022094068A1 (fr) 2022-05-05

Family

ID=81383208

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2021/057035 WO2022094068A1 (fr) 2020-10-30 2021-10-28 Fourniture de services localisés à la demande par l'intermédiaire de réseaux d'hébergement dans des systèmes de cinquième génération (5g)

Country Status (2)

Country Link
CN (1) CN115997396A (fr)
WO (1) WO2022094068A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115085975A (zh) * 2022-05-23 2022-09-20 上海销氪信息科技有限公司 SaaS业务场景下数据私有化部署方法、装置、设备、介质
WO2023215771A1 (fr) * 2022-05-06 2023-11-09 Intel Corporation Authentification et autorisation pour services localisés
WO2023212953A1 (fr) * 2022-05-06 2023-11-09 北京小米移动软件有限公司 Procédé et appareil de fourniture de service local, et support de stockage lisible
WO2024098323A1 (fr) * 2022-11-10 2024-05-16 北京小米移动软件有限公司 Procédé de fourniture d'un service de localisation au moyen d'un réseau d'hébergement, et appareil associé

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130151711A1 (en) * 2005-03-16 2013-06-13 Adaptive Computing Enterprises, Inc. On-demand compute environment
US20130252632A1 (en) * 2008-05-13 2013-09-26 At&T Mobility Ii Llc Location-based services in a femtocell network
KR20170088425A (ko) * 2014-11-28 2017-08-01 후아웨이 테크놀러지 컴퍼니 리미티드 서비스 지향 네트워크 자동 생성에 기초한 맞춤형 가상 무선 네트워크를 제공하기 위한 시스템 및 방법
US20190327097A1 (en) * 2017-05-22 2019-10-24 Alibaba Group Holding Limited Blockchain service acceptance and consensus method and devices

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130151711A1 (en) * 2005-03-16 2013-06-13 Adaptive Computing Enterprises, Inc. On-demand compute environment
US20130252632A1 (en) * 2008-05-13 2013-09-26 At&T Mobility Ii Llc Location-based services in a femtocell network
KR20170088425A (ko) * 2014-11-28 2017-08-01 후아웨이 테크놀러지 컴퍼니 리미티드 서비스 지향 네트워크 자동 생성에 기초한 맞춤형 가상 무선 네트워크를 제공하기 위한 시스템 및 방법
US20190327097A1 (en) * 2017-05-22 2019-10-24 Alibaba Group Holding Limited Blockchain service acceptance and consensus method and devices

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for the 5G system; Stage 1 (Release 17)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 22.261, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG1, no. V17.4.0, 4 October 2020 (2020-10-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 83, XP051961375 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023215771A1 (fr) * 2022-05-06 2023-11-09 Intel Corporation Authentification et autorisation pour services localisés
WO2023212953A1 (fr) * 2022-05-06 2023-11-09 北京小米移动软件有限公司 Procédé et appareil de fourniture de service local, et support de stockage lisible
CN115085975A (zh) * 2022-05-23 2022-09-20 上海销氪信息科技有限公司 SaaS业务场景下数据私有化部署方法、装置、设备、介质
WO2024098323A1 (fr) * 2022-11-10 2024-05-16 北京小米移动软件有限公司 Procédé de fourniture d'un service de localisation au moyen d'un réseau d'hébergement, et appareil associé

Also Published As

Publication number Publication date
CN115997396A (zh) 2023-04-21

Similar Documents

Publication Publication Date Title
US11902985B2 (en) Default PDSCH beam setting and PDCCH prioritization for multi panel reception
US11910433B2 (en) Physical uplink shared channel (PUSCH) transmission scheduling for new radio (NR)
WO2022094064A1 (fr) Fourniture d'accès à des services localisés (pals) dans des systèmes de cinquième génération (5g)
WO2022094068A1 (fr) Fourniture de services localisés à la demande par l'intermédiaire de réseaux d'hébergement dans des systèmes de cinquième génération (5g)
WO2022109184A1 (fr) Politiques de chaînage de fonctions service pour des systèmes 5g
WO2022212688A1 (fr) Commutation entre des configurations de surveillance de canaux physiques de contrôle descendant (pdcch) de groupes d'ensembles d'espaces de recherche (sssg)
US20240007314A1 (en) Converged charging for edge enabling resource usage and application context transfer
WO2022031557A1 (fr) Techniques pour améliorer une disponibilité de tranche dans un réseau cellulaire sans fil
US20240155503A1 (en) Spatial relationship and power control configuration for uplink transmissions
WO2023069653A1 (fr) Commutation d'équipement utilisateur (ue) entre des réseaux au moyen d'intervalles de mesure
WO2022170213A1 (fr) Architecture de communication et de système informatique centrée sur les données
WO2022031556A1 (fr) Activation de service informatique pour des réseaux cellulaires de prochaine génération
WO2022035514A1 (fr) Période de mesure de positionnement d'équipement utilisateur pour de nouveaux systèmes radio
US20240236183A1 (en) Remote direct memory access (rdma) support in cellular networks
US20240147470A1 (en) Flexible uplink control information (uci) transmission with physical uplink shared channel (pusch)
US20230163916A1 (en) Techniques for ue positioning measurement in rrc_inactive or rrc_idle
US20240224268A1 (en) Rate-matching for transport block processing over multiple slots for physical uplink shared channel
US20240235775A1 (en) Configuration and collision handling for simultaneous uplink transmission using multiple antenna panels
US20240236836A1 (en) Radio access network computing service support with distributed units
US20240188097A1 (en) Default beam operations for uplink transmissions
WO2023018779A1 (fr) Support d'accès direct à la mémoire distante (rdma) dans des réseaux cellulaires
WO2023018777A1 (fr) Bloc d'informations système (sib) pour calcul augmenté dans des réseaux cellulaires
WO2022094039A1 (fr) Délestage informatique pour réseaux cellulaires de prochaine génération
WO2023129477A1 (fr) Déploiement de réseau informatique en périphérie pour systèmes de cinquième génération (5g)
WO2023192832A1 (fr) Chaînage de fonctions de service dans un système cellulaire sans fil avec exposition de service à des tiers

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21887511

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21887511

Country of ref document: EP

Kind code of ref document: A1