EP4385184A1 - Procédés et appareil de gestion de cycle de vie améliorée dans des serveurs informatiques périphériques 5g - Google Patents

Procédés et appareil de gestion de cycle de vie améliorée dans des serveurs informatiques périphériques 5g

Info

Publication number
EP4385184A1
EP4385184A1 EP22856512.3A EP22856512A EP4385184A1 EP 4385184 A1 EP4385184 A1 EP 4385184A1 EP 22856512 A EP22856512 A EP 22856512A EP 4385184 A1 EP4385184 A1 EP 4385184A1
Authority
EP
European Patent Office
Prior art keywords
eas
request
instantiation
deployment
ecsp
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
EP22856512.3A
Other languages
German (de)
English (en)
Other versions
EP4385184A4 (fr
Inventor
Joey Chou
Yizhi Yao
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
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 Corp filed Critical Intel Corp
Publication of EP4385184A1 publication Critical patent/EP4385184A1/fr
Publication of EP4385184A4 publication Critical patent/EP4385184A4/fr
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/289—Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
    • 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/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • 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/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components

Definitions

  • This disclosure generally relates to field of wireless communications, and more particularly relates to methods and apparatus related to lifecycle management in edge computing servers.
  • next generation mobile networks in particular Third Generation Partnership Project (3GPP) systems such as Fifth Generation (5G) and Long-Term Evolution (LTE) and the evolutions thereof, are among the latest cellular wireless technologies developed to deliver ten times faster data rates than LTE and are being deployed with multiple carriers in the same area and across multiple spectrum bands.
  • 5G changes the network architecture from previous wireless networks by fundamentally shifting network provisioning to an application-centric concept.
  • 5G New Radio (NR) introduces edge computing with a distributed computing framework implementing network slicing and composable networking that provide faster and more thorough data processing, faster response times, by bringing enterprise applications closer to data sources such local edge servers.
  • the improvements in network architecture enable data to be processed closer to where the data is created. What is needed is a system and method for provisioning edge application servers to take advantage of the data processing available in 5G edge computing.
  • FIG. 1 illustrates an exemplary block diagram showing roles and relationships of service providers that deploy edge computing services in accordance with an embodiment of the disclosure.
  • FIG. 2 illustrates a block diagram of a management system framework to support the lifecycle management in accordance with an embodiment of the disclosure.
  • FIG. 3 is a timing flow diagram illustrating deployment of edge computing services in accordance with an embodiment of the disclosure.
  • FIG. 4 is timing flow diagram illustrating a termination of edge computing services in accordance with an embodiment of the disclosure.
  • FIG. 5 illustrates a flow diagram of a method in accordance with an embodiment of the disclosure.
  • FIG. 6 illustrates an exemplary network in accordance with various embodiments of the disclosure.
  • FIG. 7 illustrates an exemplary wireless network in accordance with various embodiments of the disclosure.
  • FIG. 8 illustrates a non-transitory machine-readable storage medium in accordance with various embodiments of the disclosure.
  • this disclosure is generally directed to systems and methods for supporting provisioning for edge servers and Application Service Providers (ASP) in 5G systems.
  • ASP Application Service Providers
  • a or B and A/B mean (A), (B), or (A and B).
  • Fifth Generation (5G) networks are becoming increasingly complex with the densification of millimeter wave small cells, and various new services, such as eMBB (enhanced Mobile Broadband), URLLC (Ultra Reliable Low Latency Communications), and mMTC (massive Machine Type Communications) that are characterized by high speed high data volume, low speed ultra-low latency, and infrequent transmitting low data volume from huge number of emerging smart devices, respectively.
  • eMBB enhanced Mobile Broadband
  • URLLC Ultra Reliable Low Latency Communications
  • mMTC massive Machine Type Communications
  • an application service provider may be responsible for the creation of edge application servers (EASs) and application clients (ACs).
  • EAS resides in an edge data network (EDN) to perform a server function.
  • An AC resides in a user equipment (UE) device to perform a client function.
  • EDN edge data network
  • UE user equipment
  • An edge computing service provider is responsible for the deployment of an EDN that includes an EAS and edge enable server (EES), which provides configuration information to an edge enabler client (EEC), enabling an AC in the UE to exchange application data traffic with the EAS.
  • ECS edge enable server
  • a PLMN operator is responsible for the deployment of 5G network functions, such as 5GC (5G core) and 5G NR (5G new radio).
  • a goal of the present disclosure is to enable an ASP to deploy the EAS in the EDN by requesting the provisioning MnS producer with the deployment requirements (e.g., the topological or geographical service areas. Software image information, and QoS) to deploy the EAS.
  • the provisioning MnS producer returns a response indicating the operation is in progress to prevent the consumer from waiting, as the deployment in the edge cloud may take a while. It then analyses the deployment requirements to determine where and how many EAS VNF instance(s) should be instantiated, and requests the NFVO in ETSI NFV MANO to instantiate the EAS VNF instance(s).
  • the provisioning MnS producer sends a notification to the ASP indicating the result of instantiation (e.g., success, failure, or partially failure) when a notification is received from a NFVO indicating the result of instantiation operation.
  • requirements may include the provisioning MnS producer having a capability allowing an authorized consumer to request the deployment of EAS based on the given deployment requirements, the provisioning MnS producer having a capability to inform the authorized consumer about the progress of instantiation as the response to the deployment request, and the provisioning MnS producer having a capability to notify the authorized consumer the result (e.g., success, failure, or partially failure) of instantiation operation.
  • a goal of the present disclosure is to terminate the EAS in the EDN by requesting the provisioning MnS producer to terminate the EAS VNF instance.
  • the provisioning MnS producer requests the NFVO in ETSI NFV MANO to terminate the EAS VNF instances.
  • the provisioning MnS producer sends a notification to ASP indicating the termination is in progress when a notification is received from NFVO indicating the start of termination operation.
  • the provisioning MnS producer sends another notification to ASP indicating the result of termination (e.g., success, failure, or partially failure) when a notification is received from NFVO indicating the result of termination operation.
  • requirements may include the provisioning MnS producer having a capability allowing an authorized consumer to request the termination of the EAS VNF instance, the provisioning MnS producer having a capability to inform the authorized consumer about the progress of termination as the response to the termination request, and the provisioning MnS producer having a capability to notify the authorized consumer the result (e.g., success, failure, partially failure) of termination operation.
  • a provisioning MnS (Management Service) producer at the ECSP management system may receive the createMOI request from the ASP as the consumer of provisioning MnS with the deployment requirements to request the deployment of EAS; send the createMOI response to ASP with output parameter indicating the deployment is in progress; analyze the deployment requirements to determine which EDN and how many EAS instance(s) should be instantiated to satisfy the deployment requirements; download the EAS VNF software image from the software image location; request NFVO (NFV Orchestration) to instantiate one or more EAS VNF instance(s); evaluate the results of EAS VNF instantiation(s); and send a notification to ASP to indicate the result of EAS deployment, based on the result of EAS VNF instantiation.
  • NFVO NFV Orchestration
  • the deployment requirements are contained in the E AS Lem IOC (Information Object Class), and include (but not limited to) the following attributes: the service areas (i.e., geographical, or topological) where the UEs can access the edge computing service; software image information (e.g., software image location, minimum RAM, disk requirements); and QoS requirements.
  • the service areas i.e., geographical, or topological
  • software image information e.g., software image location, minimum RAM, disk requirements
  • QoS requirements QoS requirements.
  • the ECSP provisioning MnS producer may invoke the InstantiateNsRequest operation to request NFVO via the Os-Ma-nfvo interface to instantiate an EAS VNF instance; receive the NS lifecycle change notification from NFVO indicating the start of instantiation procedure; and receive the NS Eifecycle Change notification from NFVO indicating the result of instantiation procedure.
  • the ECSP provisioning MnS producer may create the MOI for EASFunction IOC; send a notification notifyMOICreation to ASP to indicate that the EASFunction MOI has been created; and send a notification notifyMOICreation to ECSP to indicate that the EASFunction MOI has been created.
  • the ECSP provisioning MnS producer may send a notification notifyMOICreation to ASP to indicate that the EASFunction MOI has not been created due to failure; and send a notification notifyMOICreation to ECSP to indicate that the EASFunction MOI has not been created due to failure.
  • the evaluation of EAS VNF instantiation(s) may indicate one of the following results: all VNF instance(s) have been successfully instantiated; not all VNF instance(s) have been successfully instantiated; or no VNF instance has been successfully instantiated.
  • the ECSP provisioning MnS producer may create the MOI for EASLcm IOC; send a notification notifyMOICreation to ASP to indicate that the EASLcm MOI has been created; and send a notification notifyMOICreation to ECSP to indicate that the EASLcm MOI has been created.
  • the ECSP provisioning MnS producer may create the MOI for EASLcm IOC; send a notification notifyMOICreation to ASP to indicate that the EASLcm MOI has been partially created; and send a notification notifyMOICreation to ECSP to indicate that the EASLcm MOI has been partially created.
  • the ECSP provisioning MnS producer may send a notification notifyMOICreation to ASP to indicate that no EASLcm MOI has been created; and send a notification notifyMOICreation to ECSP to indicate that no EASLcm MOI has been created.
  • a provisioning MnS (Management Service) producer at the ECSP management system may receive the deleteMOI operation for EASFunction MOI from the ASP as the consumer of provisioning MnS to terminate the EAS VNF instance; send the deleteMOI response to ASP with output parameter indicating the termination is in progress; invoke the TerminateNsRequest operation to request NFVO via the Os-Ma-nfvo interface to terminate an EAS VNF instance; receive the NS lifecycle change notification from NFVO indicating the start of termination procedure; receive the NS Lifecycle Change notification from NFVO indicating the result of termination procedure; and send a notification to ASP to indicate the result of EAS deployment, based on the result of EAS VNF termination.
  • Management Service Management Service
  • the ECSP provisioning MnS producer may delete the MOI for EASFunction IOC; send a notification notifyMOICreation to ASP to indicate that the EASFunction MOI has been deleted; and send a notification notifyMOICreation to ECSP to indicate that the EASFunction MOI has been deleted.
  • the ECSP provisioning MnS producer may send a notification notifyMOICreation to ASP to indicate that the deletion of EASFunction MOI has failed; and send a notification notifyMOICreation to ECSP to indicate that the deletion of EASFunction MOI has failed.
  • a block diagram illustrates the roles and relationships of service providers that deploy edge computing services.
  • a public land mobile network (PLMN) operator 102 is responsible for the deployment of 5G network functions, such as 5G Core network functions 106 and 5G New Radio (NR) 108.
  • the PLMN operator 102 is coupled to an edge computing service provider 110 representing edge data networks 114 including Edge Application Servers 116 and Edge Enable Servers (EES) 118.
  • Edge computing service provider 110 is shown connecting EAS servers 116 to Application service provider 120 via edge computing applications orchestration 122.
  • Application service provider 120 holds edge applications 124 represented by EAS servers and application clients (AC) 128.
  • the application service provider (ASP) 120 is responsible for the creation of the EAS servers that reside in the edge data network (EDN) to perform server functions.
  • Application clients (AC) generally reside in user equipment (UE) and perform client functions.
  • Each edge computing service provider (ECSP) 110 is responsible for the deployment if the edge data network that hold EAS and EES.
  • the EAS and EES provide the configuration information to an edge enabler client (EEC), and enable application clients in the UE to exchange application data traffic with the EAS application client 128.
  • EAC edge enabler client
  • FIG. 2 a block diagram illustrates management system framework 200 that supports the lifecycle management for edge computing.
  • Application Service Provider (ASP) 202 holds Management Services Consumer (MnS-C) 204, and Edge Computing Service Provider (ECSP) 210 also hold an MnS-C 214.
  • MnS-C Management Services Consumer
  • ECSP Edge Computing Service Provider
  • Provisioning Management Services (MnS) 220 is shown as part of an ECSP management system 230, which is responsible for provisioning management service (MnS-P) 232 and MnS-P 234.
  • Edge Application Server Virtual network function (EAS VNF) 240 and EAS VNF 242 are shown coupled to ECSP management system 230.
  • ECSP management system 230 is shown connected to ETSI Network Function Virtualization Management and Orchestration (NFV MANO) 260 which hosts a Network Function Virtualization Orchestrator (NFVO) 266. More specifically, ECSP management system 230 is coupled to NFVO 266 via an interface known as the Open Source Managed Orchestration Network Function Virtualization Orchestrator (Os-Ma-nfvo) interface 250.
  • NFV MANO ETSI Network Function Virtualization Management and Orchestration
  • Os-Ma-nfvo Open Source Managed Orchestration Network Function Virtualization Orchestrator
  • Embodiments herein are directed to support the lifecycle management of edge application servers (EASs). More importantly, one or more embodiments of this disclosure are applicable to 3GPP TS 28.538, and embodiments are directed to Mobility Robustness Optimization (MRO).
  • EASs edge application servers
  • MRO Mobility Robustness Optimization
  • One or more embodiments are directed to enabling an ASP to deploy the edge application server in an edge data network (EDN), by requesting the provisioning MnS (MnS- P) producer with deployment requirements such as topological and geographical service areas, software image information, and quality of service requirements (QoS) to deploy the EAS.
  • ESN edge data network
  • MnS- P provisioning MnS
  • QoS quality of service requirements
  • MnS-P 232 and 234 producer return a response to ASP 202 indicating operation provisioning is in progress to prevent a consumer from waiting because the deployment in an edge cloud may take a while.
  • ECSP management system 230 including MnS-Ps 232 and 234 analyze the deployment requirements to determine where and how many EAS VNF instance(s), such as EAS VNFs 240 and 242 should be instantiated, and requests the NFVO 266 in ETSI NFV MANO 260 to instantiate the EAS VNF instance(s) such as EAS VNF 240 and 242.
  • the provisioning MnS producer such as MnS-P 232 sends a notification to ASP 202 indicating the result of instantiation (success, failure, or partially failure) when a notification is received from NFVO 266 indicating the result of instantiation operation.
  • a command, REQ-EAS-INST-FUN-1 from provisioning MnS producers allows an authorized consumer to request the deployment of EAS based on the given deployment requirements.
  • a command REQ-EAS-INST-FUN-2 provides for provisioning MnS producer to inform the authorized consumer about the progress of instantiation as the response to the deployment request.
  • a command REQ-EAS-INST-FUN-3 provides for provisioning MnS producer to notify the authorized consumer the result of an instantiation operation, such as success, failure or partial failure.
  • termination of an EAS in an edge data network by requesting the provisioning MnS producer to terminate the EAS VNF instance. More specifically, as shown in FIG. 2, provisioning MnS producer 232 and 234 request the NFVO 266 over the Os-Ma-nfvo interface 250, (ETSI NFV MANO) to terminate the EAS VNF instances 240 and 242.
  • a provisioning MnS producer such as MnS-P 232 sends a notification to ASP 202 indicating the termination is in progress when a notification is received from NFVO 266 indicating the start of termination operation.
  • the provisioning MnS producer 232 next sends another notification to ASP 202 indicating the result of termination, such as success, failure or partial failure, when a notification is received from NFVO 266 indicating the result of termination operation.
  • REQ-EAS-TERM-FUN-1 provides that provisioning MnS producer 232 allows an authorized consumer such as MnS-C 204 to request the termination of the EAS VNF instance, such as 240 and 242.
  • REQ-EAS-TERM-FUN-2 provides that provisioning MnS producer 232 informs the authorized consumer such as MnS-C 204 about the progress of termination as a response to the termination request.
  • REQ-EAS-TERM-FUN-3 provides that provisioning MnS producer 232 notifies the authorized consumer such as MnS-C 204 the result, such as success, failure, partial failure, of termination operation.
  • one or more embodiments are directed to procedures for EAS lifecycle management that and more particularly how an ASP consumes provisioning, such as from MnS-P 232 to deploy the EAS, such as EAS VNF 240 or 242.
  • FIG. 3 shows timing diagram 300 and assumes ECSP consumers, such as ECSP 210 subscribe to an MnS-P producer, such as MnS-P 234, to receive notifications.
  • FIG. 3 shows ASP 302 as a consumer of a provisioning MnS, ECSP 304 as a consumer of provisioning MnS, ECSP 306 as a producer of provisioning MnS and ETSI NFV MANO NFVO 308 as a network function virtualization orchestrator.
  • provisioning begins with with createMOI operation 310 as provided in clause 11.1.1.1. in TS 28.532, for EASLcm Information Object Class (IOC) to request ECSP provisioning, and for an MnS producer to start the EAS VNF instantiation.
  • IOC EASLcm Information Object Class
  • MnS component type A provides services to manage the lifecycle of IOC instances which are also known as Managed Object Instances, (MOIs), or simply managed objects, and sets attributes of the MOI, as well as provide performance assurance and fault supervision for the MOI.
  • MOIs Managed Object Instances
  • the EASLcm IOC contains the deployment requirements, including at least the following attributes: the service areas (e.g., geographical, or topological) where the UEs can access the edge computing service in accordance with clause 7.3.3 in TS 28.558, Software image information, such as software image location, minimum RAM, disk requirements, QoS requirements such as bandwidth, end-to-end latency.
  • the service areas e.g., geographical, or topological
  • Software image information such as software image location, minimum RAM, disk requirements, QoS requirements such as bandwidth, end-to-end latency.
  • ECSP provisioning MnS producer 306 returns an output parameter to the ASP 302 an indication that the instantiation operation is in progress with createMOI output parameters 312.
  • ECSP 306 analyzes requirements to determine how many and where EAS VNFs should be instantiated.
  • ECSP provisioning MnS producer 306 analyzes the deployment requirements to determine which EDN and how many EAS instance(s) should be instantiated to satisfy the deployment requirements, and downloads the EAS VNF software image from the software image location.
  • a loop process begins with instantiating one or more EAS VNFs at step 316.
  • ECSP provisioning MnS producer 306 invokes the InstantiateNsRequest operation to request NFVO 308 via the Os-Ma-nfvo interface to instantiate EAS VNF instance.
  • InstantiateNsRequest to instantiate the EAS VNF.
  • N sLcmOperation OccurenceNotification is sent from NFVO 308 to ECSP 306 to indicate the start of the EAS instantiation at step 320.
  • NFVO 308 sends a NS lifecycle change notification to ECSP provisioning MnS producer 306 indicating the start of instantiation procedure.
  • NsLcmOperationOccurrenceNotification is sent to indicate the result of EAS instantiation at step 322.
  • NFVO 308 sends a NS Lifecycle Change notification to ECSP provisioning MnS producer 306 indicating the result of instantiation procedure If the VNF instantiation has been successful at 330, create the MOI for EASFunction IOC 332 occurs followed by notifyMOICreation to notify ASP EASFunction MOI has been created 334 which is sent from ECSP 306 to ASP 302.
  • ECSP producer 306 notifies ECSP consumer 304 that EASFunction has been created at step 338 via notifyMOICreation.
  • VNF Instantiation fails at 340, ECSP producer 306 notifies ASP302 that the creation of EASFunction MOI has failed at step 342.
  • the notification is that notifyMOICreation has not been created due to failure.
  • ECSP producer 306 then notifies ECSP consumer 304 that the creation of EASFunction MOI has failed at 344 via notifyMOICreation.
  • step 316 may then be repeated by instantiating another EAS VNF.
  • step 352 ECSP producer 306 creates an MOI for EASLCM IOC. ECSP producer 306 then notifies ASP 302 at 354 via notifyMOICreation to create the MOI for EASLcm IOC.
  • ECSP provisioning MnS producer 306 sends a notification notifyMOICreation to ECSP consumer 304 that the EASLcm MOI has been created.
  • ECSP provisioning MnS producer 306 sends a notification notifyMOICreation to ASP 302 to indicate that the EASLcm MOI has not been created due to failure at step 368.
  • ECSP provisioning MnS producer 306 notifies ASP 302 that no EASFunction MOI has been created at step 368 with notifyMOICreation.
  • ECSP provisioning MnS producer 306 sends a notification notifyMOICreation to ECSP consumer 304 to indicate that the EASLcm MOI has not been created due to failure.
  • a timing diagram 400 illustrates a procedure describing how an ASP can consume provisioning MnS to terminate the EAS VNF. It is assumed that both ASP and ECSP consumers have subscribed to the producer of provisioning MnS to receive notifications. As shown, the procedure includes interactions between ASP 402 consumer of provisioning MnS, ECSP 404 consumer of provisioning MnS, ECSP 406 producer of provisioning MnS, and NFVO 408 ETS NFV MANO orchestrator.
  • the termination begins with step 410 with deleteMOI of EASFunction wherein ASP 402 consumes the provisioning MnS with deleteMOI operation for EASFunction MOI to request ECSP provisioning MnS producer 406 to start the EAS VNF termination.
  • ECSP provisioning MnS producer 406 returns an output parameter to ASP 402 indicating the termination operation is in progress.
  • ECSP provisioning MnS producer 406 sends a TerminateNsRequest operation to NFVO 408 to request that NFVO via the Os-Ma-nfvo interface terminate an EAS VNF instance.
  • Os-Ma-nfvo interface 250 is coupled to NFVO 266 and to ECSP management system 230 to enable the termination request.
  • NFVO 408 sends at step 416, the NS lifecycle change notification to ECSP provisioning MnS producer 406 indicating the start of termination procedure using NsLcmOperation OccurrenceNotification to indicate the start of EAS termination as well as the result of the EAS termination at step 418.
  • ECSP provisioning MnS producer 406 deletes the MOI for EASLcm IOC.
  • ECSP provisioning MnS producer 406 sends a notification notifyMOIDeletion to notify ASP 402 that EASFunction MOI has been deleted.
  • ECSP provisioning MnS producer 406 notifies via notifyMOIDeletion to ECSP 404 consumer of provisioning MnS that indicate the EASFunction MOI has been deleted.
  • step 432 provides that ECSP provisioning MnS producer 406 sends a notification notifyMOIDeletion to ASP 402 to indicate the EASFunction MOI has not been deleted due to failure.
  • a flow diagram 500 illustrates an embodiment of a process for provisioning.
  • the ECSP may detect a request, received from an application service provider (ASP) consumer of provisioning managed services (MnS), for ECSP provisioning.
  • ASP application service provider
  • MnS provisioning managed services
  • FIG. 2 an ASP as a consumer of provisioning MnS with deployment requirements to request the deployment of EAS as the ECSP provisioning is shown in FIG. 2, ASP 202 requests provisioning from ECSP management system 230.
  • the request for ECSP provisioning includes a request to create a managed object instance (MOI) from an Application Service Provider (ASP) as a consumer of provisioning MnS with deployment requirements to request the deployment of EAS.
  • the request may include requirements for edge application server (EAS) virtualized network functions.
  • ECSP management system 230 receives the request and determines requirements.
  • the ECSP may encode a response to the request to indicate (e.g., to the requesting ASP) that the instantiation is in progress.
  • the ECSP may select an EDN and a number of EAS instances to be instantiated based on the deployment requirements.
  • the ECSP may detect an EAS VNF software image received based on the deployment requirements.
  • the ECSP may request an instantiation by a network function virtualization orchestrator (NFVO) based on the requirements of the EAS virtualized network functions.
  • NFVO network function virtualization orchestrator
  • ECSP management system 230 requests instantiation from NFVO 266 over the os-ma-nfvo interface 250.
  • an ECSP provisioning system may send output parameters indicating that deployment is in progress.
  • determining requirements may include analyzing the deployment requirements to determine a number of EAS instances that should be instantiated to satisfy the deployment requirements.
  • an embodiment includes downloading an EAS virtualized network function (VNF) software image from a software image location, and requesting instantiation of one or more EAS VNF instances from the downloaded software image by a network function virtualization orchestrator (NFVO), such as NFVO 266.
  • VNF EAS virtualized network function
  • the ECSP may detect a result of the instantiation, which may be a deployment or a failure.
  • a deployment may occur only when all requested instances have been instantiated.
  • a partial deployment may occur when a subset of requested instances have been instantiated while one or more other requested instances failed to instantiate.
  • FIGS 6-8 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
  • the network 600 may include a UE 602, which may include any mobile or non-mobile computing device designed to communicate with a RAN 604 via an over-the-air connection.
  • the UE 602 may be communicatively coupled with the RAN 604 by a Uu interface.
  • the UE 602 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 600 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 602 may additionally communicate with an AP 606 via an over-the-air connection.
  • the AP 606 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 604.
  • the connection between the UE 602 and the AP 606 may be consistent with any IEEE 802.11 protocol, wherein the AP 606 could be a wireless fidelity (Wi-Fi®) router.
  • the UE 602, RAN 604, and AP 606 may utilize cellular-WLAN aggregation (for example, LWA/LWIP).
  • Cellular- WLAN aggregation may involve the UE 602 being configured by the RAN 604 to utilize both cellular radio resources and WLAN resources.
  • the RAN 604 may include one or more access nodes, for example, AN 608.
  • AN 608 may terminate air-interface protocols for the UE 602 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 608 may enable data/voice connectivity between CN 620 and the UE 602.
  • the AN 608 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 608 be referred to as a BS, gNB, RAN node, eNB, ng- eNB, NodeB, RSU, TRxP, TRP, etc.
  • the AN 608 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 604 may be coupled with one another via an X2 interface (if the RAN 604 is an LTE RAN) or an Xn interface (if the RAN 604 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 604 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 602 with an air interface for network access.
  • the UE 602 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 604.
  • the UE 602 and RAN 604 may use carrier aggregation to allow the UE 602 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 604 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 602 or AN 608 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 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 604 may be an LTE RAN 610 with eNBs, for example, eNB 612.
  • the LTE RAN 610 may provide an LTE air interface with the following characteristics: SCS of 16 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 operate on sub-6 GHz bands.
  • the RAN 604 may be an NG-RAN 614 with gNBs, for example, gNB 616, or ng-eNBs, for example, ng-eNB 618.
  • the gNB 616 may connect with 5G-enabled UEs using a 5G NR interface.
  • the gNB 616 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface.
  • the ng-eNB 618 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface.
  • the gNB 616 and the ng-eNB 618 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 614 and a UPF 648 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN 614 and an AMF 4544 (e.g., N2 interface).
  • NG-U NG user plane
  • N3 interface e.g., N3 interface
  • N-C NG control plane
  • the NG-RAN 614 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 operate 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 602 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 602, 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 602 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 602 and in some cases at the gNB 616.
  • a BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.
  • the RAN 604 is communicatively coupled to CN 620 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 602).
  • the components of the CN 620 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 620 onto physical compute/storage resources in servers, switches, etc.
  • a logical instantiation of the CN 620 may be referred to as a network slice, and a logical instantiation of a portion of the CN 620 may be referred to as a network sub- slice.
  • the CN 620 may be an LTE CN 622, which may also be referred to as an EPC.
  • the LTE CN 622 may include MME 624, SGW 626, SGSN 628, HSS 630, PGW 632, and PCRF 634 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 622 may be briefly introduced as follows.
  • the MME 624 may implement mobility management functions to track a current location of the UE 602 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.
  • the SGW 626 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 622.
  • the SGW 626 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 628 may track a location of the UE 602 and perform security functions and access control. In addition, the SGSN 628 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 624; MME selection for handovers; etc.
  • the S3 reference point between the MME 624 and the SGSN 628 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle/active states.
  • the HSS 630 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions.
  • the HSS 630 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • An S6a reference point between the HSS 630 and the MME 4] 624 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 620.
  • the PGW 632 may terminate an SGi interface toward a data network (DN) 636 that may include an application/content server 638.
  • the PGW 632 may route data packets between the LTE CN 622 and the data network 636.
  • the PGW 632 may be coupled with the SGW 626 by an S5 reference point to facilitate user plane tunneling and tunnel management.
  • the PGW 632 may further include a node for policy enforcement and charging data collection (for example, PCEF).
  • the SGi reference point between the PGW 632 and the data network 636 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 632 may be coupled with a PCRF 634 via a Gx reference point.
  • the PCRF 634 is the policy and charging control element of the LTE CN 622.
  • the PCRF 634 may be communicatively coupled to the app/content server 638 to determine appropriate QoS and charging parameters for service flows.
  • the PCRF 632 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.
  • the CN 620 may be a 5GC 640.
  • the 5GC 640 may include an AUSF 642, AMF 644, SMF 646, UPF 648, NSSF 650, NEF 652, NRF 654, PCF 656, UDM 658, and AF 660 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 640 may be briefly introduced as follows.
  • the AUSF 642 may store data for authentication of UE 602 and handle authentication- related functionality.
  • the AUSF 642 may facilitate a common authentication framework for various access types.
  • the AUSF 642 may exhibit an Nausf service-based interface.
  • the AMF 644 may allow other functions of the 5GC 640 to communicate with the UE 602 and the RAN 604 and to subscribe to notifications about mobility events with respect to the UE 602.
  • the AMF 644 may be responsible for registration management (for example, for registering UE 602), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization.
  • the AMF 644 may provide transport for SM messages between the UE 602 and the SMF 646, and act as a transparent proxy for routing SM messages.
  • AMF 644 may also provide transport for SMS messages between UE 602 and an SMSF.
  • AMF 644 may interact with the AUSF 642 and the UE 602 to perform various security anchor and context management functions.
  • AMF 644 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 604 and the AMF 644; and the AMF 644 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection.
  • AMF 644 may also support NAS signaling with the UE 602 over an N3 IWF interface.
  • the SMF 646 may be responsible for SM (for example, session establishment, tunnel management between UPF 648 and AN 608); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 648 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 644 over N2 to AN 608; 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 602 and the data network 636.
  • the UPF 648 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 636, and a branching point to support multi-homed PDU session.
  • the UPF 648 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 648 may include an uplink classifier to support routing traffic flows to a data network.
  • the NSSF 650 may select a set of network slice instances serving the UE 602.
  • the NSSF 650 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed.
  • the NSSF 650 may also determine the AMF set to be used to serve the UE 602, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 654.
  • the selection of a set of network slice instances for the UE 602 may be triggered by the AMF 644 with which the UE 602 is registered by interacting with the NSSF 650, which may lead to a change of AMF.
  • the NSSF 650 may interact with the AMF 644 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 650 may exhibit an Nnssf service-based interface.
  • the NEF 652 may securely expose services and capabilities provided by 3 GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 660), edge computing or fog computing systems, etc.
  • the NEF 652 may authenticate, authorize, or throttle the AFs.
  • NEF 652 may also translate information exchanged with the AF 560 and information exchanged with internal network functions. For example, the NEF 652 may translate between an AF-Service-Identifier and an internal 5GC information.
  • NEF 652 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 652 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 652 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 652 may exhibit an Nnef service-based interface.
  • the NRF 654 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 654 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 554 may exhibit the Nnrf service-based interface.
  • the PCF 656 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior.
  • the PCF 656 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 658.
  • the PCF 656 exhibit an Npcf service-based interface.
  • the UDM 658 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 602. For example, subscription data may be communicated via an N8 reference point between the UDM 658 and the AMF 644.
  • the UDM 658 may include two parts, an application front end and a UDR.
  • the UDR may store subscription data and policy data for the UDM 658 and the PCF 656, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 602) for the NEF 652.
  • the Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 658, PCF 656, and NEF 652 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 658 may exhibit the Nudm service-based interface.
  • the AF 660 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.
  • the 5GC 640 may enable edge computing by selecting operator/3 rd party services to be geographically close to a point that the UE 602 is attached to the network. This may reduce latency and load on the network.
  • the 5GC 640 may select a UPF 648 close to the UE 602 and execute traffic steering from the UPF 648 to data network 636 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 660. In this way, the AF 660 may influence UPF (re)selection and traffic routing.
  • the network operator may permit AF 660 to interact directly with relevant NFs. Additionally, the AF 660 may exhibit an Naf service-based interface.
  • the data network 636 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 638.
  • the wireless network 700 may include a UE 702 in wireless communication with an AN 704.
  • the UE 702 and AN 704 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.
  • the UE 702 may be communicatively coupled with the AN 704 via connection 707.
  • the connection 706 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- 5 GHz frequencies.
  • the UE 702 may include a host platform 708 coupled with a modem platform 710.
  • the host platform 708 may include application processing circuitry 712, which may be coupled with protocol processing circuitry 714 of the modem platform 710.
  • the application processing circuitry 712 may run various applications for the UE 702 that source/sink application data.
  • the application processing circuitry 712 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 714 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 706.
  • the layer operations implemented by the protocol processing circuitry 714 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.
  • the modem platform 710 may further include digital baseband circuitry 716 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 714 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 710 may further include transmit circuitry 718, receive circuitry 720, RF circuitry 722, and RF front end (RFFE) 724, which may include or connect to one or more antenna panels 726.
  • the transmit circuitry 718 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.
  • the receive circuitry 720 may include an analog-to-digital converter, mixer, IF components, etc.
  • the RF circuitry 722 may include a low-noise amplifier, a power amplifier, power tracking components, etc.
  • RFFE 724 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- 5 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 714 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 726, RFFE 724, RF circuitry 722, receive circuitry 720, digital baseband circuitry 716, and protocol processing circuitry 714.
  • the antenna panels 726 may receive a transmission from the AN 704 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 726.
  • a UE transmission may be established by and via the protocol processing circuitry 714, digital baseband circuitry 716, transmit circuitry 718, RF circuitry 722, RFFE 724, and antenna panels 726.
  • the transmit components of the UE 704 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 726.
  • the AN 704 may include a host platform 728 coupled with a modem platform 730.
  • the host platform 728 may include application processing circuitry 732 coupled with protocol processing circuitry 734 of the modem platform 730.
  • the modem platform may further include digital baseband circuitry 736, transmit circuitry 738, receive circuitry 740, RF circuitry 742, RFFE circuitry 744, and antenna panels 746.
  • the components of the AN 704 may be similar to and substantially interchangeable with like-named components of the UE 702.
  • the components of the AN 708 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.
  • FIG. 8 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 8 shows a diagrammatic representation of hardware resources 800 including one or more processors (or processor cores) 810, one or more memory/storage devices 820, and one or more communication resources 830, each of which may be communicatively coupled via a bus 840 or other interface circuitry.
  • a hypervisor 802 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 800.
  • the processors 810 may include, for example, a processor 812 and a processor 814.
  • the processors 810 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 820 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 820 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 830 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 804 or one or more databases 806 or other network elements via a network 808.
  • the communication resources 830 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 850 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 810 to perform any one or more of the methodologies discussed herein.
  • the instructions 850 may reside, completely or partially, within at least one of the processors 810 (e.g., within the processor’s cache memory), the memory/storage devices 820, or any suitable combination thereof.
  • any portion of the instructions 850 may be transferred to the hardware resources 800 from any combination of the peripheral devices 804 or the databases 806. Accordingly, the memory of processors 810, the memory/storage devices 820, the peripheral devices 804, and the databases 806 are examples of computer-readable and machine -readable media.
  • Example 1 may be an apparatus of an Edge Computing Service Provider (ECSP) for provisioning a Management Service (MnS) producer at the ECSP in a wireless network, the apparatus comprising: a memory; processing circuitry coupled to the memory, the processing circuitry configured to: detect a request to create a managed object instance (MOI), the request received from an Application Service Provider (ASP), the request comprising deployment requirements; encode a response to the request for transmission to the ASP, the response indicating that instantiation is in progress; select an Edge Data Network (EDN) and a number of edge application servers (EAS) instances to be instantiated based on the deployment requirements; detect an EAS virtualized network function (VNF) software image received based on the deployment requirements; request instantiation, by a network function virtualization orchestrator (NFVO), of one or more EAS VNF instances of the software image; detect a result of the instantiation; and encode a notification for transmission to the ASP based on the instantiation, the notification comprising an indication of the result being
  • Example 2 may include the apparatus of example 1 and/or some other example herein, wherein the deployment requirements are included in an EAS lifecycle management information object class (EASLcm IOC) of the request, and wherein the deployment requirements comprise at least one of a service area where one or more user equipment (UE) can access the EDN, software image data, or quality of service (QoS) requirements.
  • EASLcm IOC EAS lifecycle management information object class
  • UE user equipment
  • QoS quality of service
  • Example 3 may include the apparatus of example 1 or example 2, and/or some other example herein, wherein the processing circuitry is further configured to: invoke an InstantiateNsRequest operation to request the instantiation via an Open Source Managed Orchestration network function virtualization orchestrator (Os-Ma-nfvo) interface; and detect a network service lifecycle change notification received from the NFVO indicating a status of the instantiation.
  • Os-Ma-nfvo Open Source Managed Orchestration network function virtualization orchestrator
  • Example 4 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry configured is further configured to: detect that all of the one or more EAS VNF instances were successfully instantiated, wherein the result is a deployment only when all of the one or more EAS VNF instances were successfully instantiated.
  • Example 5 may include the apparatus of example 4 and/or some other example herein, wherein the processing circuitry configured is further configured to: create the MOI for an EASFunction information object class (IOC) based on the result being a deployment.
  • IOC EASFunction information object class
  • Example 6 may include the apparatus of example 5 and/or some other example herein, wherein the notification further indicates that the MOI was created.
  • Example 7 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry is further configured to: detect that an EAS VNF instance of the one or more EAS VNF instances was not successfully instantiated.
  • Example 8 may include the apparatus of example 7 and/or some other example herein, wherein the notification indicates that the result was a failure based on the detection that the EAS VNF instance was not successfully instantiated.
  • Example 9 may include the apparatus of example 7 and/or some other example herein, wherein the processing circuitry is further configured to: detect that a second EAS VNF instance of the one or more EAS VNF instances was successfully instantiated, wherein the notification indicates that the result was a partial deployment.
  • Example 10 may include a computer-readable storage medium comprising instructions to cause processing circuitry of an application service provider (ASP), upon execution of the instructions by the processing circuitry, to encode, for transmission to an Edge Computing Service Provider (ECSP), a request to create a managed object instance (MOI), the request comprising deployment requirements associated with instantiating one or more virtual network function (VNF) instances of a software image of an edge application server; detect a response received from the ECSP, subsequent to the request, the response indicating that instantiation is in progress and that the ECSP will send a notification comprising an indication of an instantiation result being a deployment or a failure; and detect the notification received from the ECSP, subsequent to the response.
  • ASP application service provider
  • MOI managed object instance
  • VNF virtual network function
  • Example 11 may include the computer-readable medium of example 10 and/or some other example herein, wherein the deployment requirements are included in an EAS lifecycle management information object class (EASLcm IOC) of the request, and wherein the deployment requirements comprise at least one of a service area where one or more user equipment (UE) can access an Edge Data Network (EDN), software image data, or quality of service (QoS) requirements.
  • EAS lifecycle management information object class EASLcm IOC
  • EDN Edge Data Network
  • QoS quality of service
  • Example 12 may include the computer-readable medium of example 10 and/or some other example herein, wherein the request is further associated with invoking an InstantiateNsRequest operation to request the instantiation via an Open Source Managed Orchestration network function virtualization orchestrator (Os-Ma-nfvo) interface.
  • Os-Ma-nfvo Open Source Managed Orchestration network function virtualization orchestrator
  • Example 13 may include the computer-readable medium of example 10 and/or some other example herein, wherein the instantiation result is a deployment only when all of the one or more EAS VNF instances were successfully instantiated.
  • Example 14 may include the computer-readable medium of example 13 and/or some other example herein, wherein the request is further associated with creating the MOI for an EASFunction information object class (IOC) based on the instantiation result being a deployment.
  • Example 15 may include the non-transitory computer-readable medium of example 14 and/or some other example herein, wherein the notification further indicates that the MOI was created.
  • IOC EASFunction information object class
  • Example 16 may include the computer-readable medium of example 10 and/or some other example herein, the instantiation result indicates a failure when any of the one or more EAS VNF instances were not successfully instantiated.
  • Example 17 may include a method for provisioning a Management Service (MnS) producer at an Edge Computing Service Provider (ECSP) in a wireless network, the method comprising: detecting, by processing circuitry of the ECSP, a request to create a managed object instance (MOI), the request received from an Application Service Provider (ASP), the request comprising deployment requirements; encoding, by the processing circuitry, a response to the request for transmission to the ASP, the response indicating that instantiation is in progress; selecting, by the processing circuitry, an Edge Data Network (EDN) and a number of edge application servers (EAS) instances to be instantiated based on the deployment requirements; detecting, by the processing circuitry, an EAS virtualized network function (VNF) software image received based on the deployment requirements; request, by the processing circuitry, instantiation by a network function virtualization orchestrator (NFVO) of one or more EAS VNF instances of the software image; detecting, by the processing circuitry, a result of the instantiation; and en
  • Example 18 may include the method of example 17 and/or some other example herein, wherein the deployment requirements are included in an EAS lifecycle management information object class (EASLcm IOC) of the request, and wherein the deployment requirements comprise at least one of a service area where one or more user equipment (UE) can access the EDN, software image data, or quality of service (QoS) requirements.
  • EASLcm IOC EAS lifecycle management information object class
  • UE user equipment
  • QoS quality of service
  • Example 19 may include the method of example 17 and/or some other example herein, further comprising: invoking an InstantiateNsRequest operation to request the instantiation via an Open Source Managed Orchestration network function virtualization orchestrator (Os-Ma- nfvo) interface; and detecting a network service lifecycle change notification received from the NFVO indicating a status of the instantiation.
  • Os-Ma- nfvo Open Source Managed Orchestration network function virtualization orchestrator
  • Example 20 may include the method of example 17 and/or some other example herein, further comprising: detecting that all of the one or more EAS VNF instances were successfully instantiated, wherein the result is a deployment only when all of the one or more EAS VNF instances were successfully instantiated.
  • Example 21 may include the method of example 20 and/or some other example herein, further comprising: creating the MOI for an EASFunction information object class (IOC) based on the result being a deployment.
  • IOC EASFunction information object class
  • Example 22 may include the method of example 21 and/or some other example herein, wherein the notification further indicates that the MOI was created.
  • Example 23 may include the method of example 17 and/or some other example herein, further comprising detecting that an EAS VNF instance of the one or more EAS VNF instances was not successfully instantiated.
  • Example 24 may include an apparatus comprising means for: detecting, an ECSP, a request to create a managed object instance (MOI), the request received from an Application Service Provider (ASP), the request comprising deployment requirements; encoding a response to the request for transmission to the ASP, the response indicating that instantiation is in progress; selecting an Edge Data Network (EDN) and a number of edge application servers (EAS) instances to be instantiated based on the deployment requirements; detecting an EAS virtualized network function (VNF) software image received based on the deployment requirements; requesting instantiation by a network function virtualization orchestrator (NFVO) of one or more EAS VNF instances of the software image; detecting a result of the instantiation; and encoding a notification for transmission to the ASP based on the instantiation, the notification comprising an indication of the result being a deployment or a failure.
  • EDN Edge Data Network
  • EAS edge application servers
  • Example 25 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-24, or any other method or process described herein.
  • Example 26 may include one or more non-transitory computer-readable media comprising instructions to cause an ECSP and an ASP, 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-24, or any other method or process described herein.
  • Example 27 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in or related to any of examples 1-24, or any other method or process described herein.
  • Example 28 may include a method, technique, or process as described in or related to any of examples 1-24, or portions or parts thereof.
  • Example 29 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-24, or portions thereof.
  • 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.
  • Implementations of the systems, apparatuses, devices, and methods disclosed herein may comprise or utilize one or more devices that include hardware, such as, for example, one or more processors and system memory, as discussed herein.
  • An implementation of the devices, systems, and methods disclosed herein may communicate over a computer network.
  • a “network” is defined as one or more data links that enable the transport of electronic data between computer systems and/or modules and/or other electronic devices. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or any combination of hardwired or wireless) to a computer, the computer properly views the connection as a transmission medium.
  • Transmission media can include a network and/or data links, which can be used to carry desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. Combinations of the above should also be included within the scope of non-transitory computer-readable media.
  • Computer-executable instructions comprise, for example, instructions and data which, when executed at a processor, cause the processor to perform a certain function or group of functions.
  • the computer-executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code.
  • a memory device can include any one memory element or a combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)) and non-volatile memory elements (e.g., ROM, hard drive, tape, CDROM, etc.).
  • volatile memory elements e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)
  • non-volatile memory elements e.g., ROM, hard drive, tape, CDROM, etc.
  • the memory device may incorporate electronic, magnetic, optical, and/or other types of storage media.
  • a “non-transitory computer-readable medium” can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device.
  • the computer-readable medium would include the following: a portable computer diskette (magnetic), a random-access memory (RAM) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM, EEPROM, or Flash memory) (electronic), and a portable compact disc read-only memory (CD ROM) (optical).
  • a portable computer diskette magnetic
  • RAM random-access memory
  • ROM read-only memory
  • EPROM erasable programmable read-only memory
  • EPROM erasable programmable read-only memory
  • CD ROM portable compact disc read-only memory
  • the computer-readable medium could even be paper or another suitable medium upon which the program is printed, since the program can be electronically captured, for instance, via optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
  • the present disclosure may be practiced in network computing environments with many types of computer system configurations, including in-dash vehicle computers, personal computers, desktop computers, laptop computers, message processors, nomadic devices, multi-processor systems, microprocessorbased or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, tablets, pagers, routers, switches, various storage devices, and the like.
  • the disclosure may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by any combination of hardwired and wireless data links) through a network, both perform tasks.
  • program modules may be located in both the local and remote memory storage devices.
  • ASICs application specific integrated circuits
  • At least some embodiments of the present disclosure have been directed to computer program products comprising such logic (e.g., in the form of software) stored on any computer- usable medium.
  • Such software when executed in one or more data processing devices, causes a device to operate as described herein.
  • any or all of the aforementioned alternate implementations may be used in any combination desired to form additional hybrid implementations of the present disclosure.
  • any of the functionality described with respect to a particular device or component may be performed by another device or component.
  • embodiments of the disclosure may relate to numerous other device characteristics.
  • embodiments have been described in language specific to structural features and/or methodological acts, it is to be understood that the disclosure is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as illustrative forms of implementing the embodiments.
  • 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 refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network.
  • the term “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.
  • the term “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.
  • information element refers to a structural element containing one or more fields.
  • field refers to individual contents of an information element, or a data element that contains content.
  • SMTC refers to an SSB-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.
  • Server 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.
  • serving cell refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA/.
  • 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 Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des systèmes et des procédés permettant de fournir un producteur de service de gestion (PLMN) au niveau d'un système de gestion d'un fournisseur de services informatiques périphériques (ECSP) dans un réseau sans fil. Le ECSP peut détecter une demande de création d'une instance d'objet géré (MOI), la demande reçue d'un fournisseur de services d'application (ASP) comprenant des exigences de déploiement ; coder une réponse à la demande, la réponse indiquant qu'une instanciation est en cours ; sélectionner un réseau de données périphérique (EDN) et un certain nombre d'instances de serveurs d'application périphériques (EAS) à instancier d'après les exigences de déploiement ; détecter une image logicielle de fonction de réseau virtualisé (VNF) EAS reçue d'après les exigences de déploiement ; demander une instanciation, au moyen d'un orchestrateur de virtualisation de fonction de réseau (NFVO), d'une ou de plusieurs instances VNF EAS de l'image logicielle; détecter des résultats de l'instanciation ; et coder une notification basée sur l'instanciation, comprenant une indication du fait que les résultats sont un déploiement ou une défaillance.
EP22856512.3A 2021-08-11 2022-08-09 Procédés et appareil de gestion de cycle de vie améliorée dans des serveurs informatiques périphériques 5g Pending EP4385184A4 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163232066P 2021-08-11 2021-08-11
PCT/US2022/039847 WO2023018727A1 (fr) 2021-08-11 2022-08-09 Procédés et appareil de gestion de cycle de vie améliorée dans des serveurs informatiques périphériques 5g

Publications (2)

Publication Number Publication Date
EP4385184A1 true EP4385184A1 (fr) 2024-06-19
EP4385184A4 EP4385184A4 (fr) 2025-07-02

Family

ID=85200316

Family Applications (1)

Application Number Title Priority Date Filing Date
EP22856512.3A Pending EP4385184A4 (fr) 2021-08-11 2022-08-09 Procédés et appareil de gestion de cycle de vie améliorée dans des serveurs informatiques périphériques 5g

Country Status (3)

Country Link
EP (1) EP4385184A4 (fr)
CN (1) CN117426078A (fr)
WO (1) WO2023018727A1 (fr)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024196065A1 (fr) * 2023-03-19 2024-09-26 Samsung Electronics Co., Ltd. Procédés et appareil permettant de fournir une mobilité d'application dans des réseaux périphériques
CN118945733A (zh) * 2023-05-11 2024-11-12 华为技术有限公司 一种边缘应用方法及装置
KR20260040232A (ko) * 2023-07-13 2026-03-24 삼성전자주식회사 주도 사업자와 참여 사업자 사이의 공식화된 연합을 확립하기 위한 방법 및 시스템
WO2025121244A1 (fr) * 2023-12-07 2025-06-12 日本電気株式会社 Nœud de gestion de réseau de périphérie, dispositif d'application, système de communication, procédé de communication et programme
WO2025171788A1 (fr) * 2024-02-18 2025-08-21 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil de gestion de cycle de vie de service
CN120786637A (zh) * 2024-04-09 2025-10-14 华为技术有限公司 一种通信的方法和通信装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220295353A1 (en) * 2019-08-08 2022-09-15 Samsung Electronics Co., Ltd. Method and system for intent driven deployment and management of communication service in a wireless communication system

Also Published As

Publication number Publication date
WO2023018727A1 (fr) 2023-02-16
EP4385184A4 (fr) 2025-07-02
CN117426078A (zh) 2024-01-19

Similar Documents

Publication Publication Date Title
WO2022011527A1 (fr) Configuration et transmission de srs en multi-dci multi-trp et agrégation de porteuses
US12317126B2 (en) Apparatus and method for 5G quality of service indicator management
EP4406304A1 (fr) Procédés et appareil de configuration efficace de bande passante de services de synchronisation temporelle dans des systèmes 5g
US11871460B2 (en) Domain name system (DNS)-based discovery of regulatory requirements for non-3GPP inter-working function (N3IWF) selection
EP4385184A1 (fr) Procédés et appareil de gestion de cycle de vie améliorée dans des serveurs informatiques périphériques 5g
US20230141237A1 (en) Techniques for management data analytics (mda) process and service
WO2022235690A1 (fr) Chaînage de fonctions de service amélioré dans des réseaux cellulaires de prochaine génération
US20240129929A1 (en) Techniques for cancelation of one or more uplink transmissions from a user equipment
EP4320834A1 (fr) Procédés et appareil pour prendre en charge l'enregistrement d'applications de serveur d'application périphérique (eas) et d'applications d'informatique périphérique à accès multiple (mec) à des serveurs catalyseurs périphériques (ees) et à des platesformes mec
WO2023205381A1 (fr) Capacité de surveillance de canal physique de contrôle de descendante (pdcch) pour une planification multicellulaire
US20250184058A1 (en) Mechanisms for multi-carrier transmit switching for new radio systems in 5g ran1
WO2022251518A1 (fr) Classification de service améliorée pour chaînage de fonctions de service dans des réseaux cellulaires de nouvelle génération
WO2022155108A1 (fr) Saut de fréquence inter-intervalles amélioré permettant une couverture de liaison montante dans des systèmes 5g
WO2022154961A1 (fr) Support pour serveur activateur de périphérie et gestion de cycle de vie de serveur de configuration de périphérie
JP2025526551A (ja) ８ポートのサウンディング参照信号（ｓｒｓ）オペレーションのための技術
US11751228B2 (en) Methods and apparatuses for uplink spatial relation info switch
WO2022154962A1 (fr) Atténuation de chevauchements de domaine temporel impliquant un bloc de transport sur des transmissions à fentes multiples
EP4239479A1 (fr) Orchestration de services informatiques et de ressources pour des systèmes de prochaine génération
WO2022216859A1 (fr) Configuration d'avance temporelle pour mobilité inter-cellules
WO2022155505A1 (fr) Techniques de déclenchement d'un signal de référence de sondage (srs) apériodique et flexible
CN117099390A (zh) 针对5g系统中的网络切片实例支持无线电资源管理（rrm）优化的方法和装置
CN116783873A (zh) 下一代系统的数据管理和后台数据传送策略控制的性能测量
EP4278628B1 (fr) Mesures de performance pour fonction d'exposition de réseau sur la fourniture de paramètres de service, la négociation de politique et l'établissement de connexion
US20260006575A1 (en) Positioning enhancements for the next generation radio access network with service based interfaces
EP4207666A1 (fr) Configuration d'occasions de surveillance de pdcch pour capacité de surveillance de pdcch à intervalles multiples

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20231115

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20250603

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 67/289 20220101ALI20250527BHEP

Ipc: H04L 41/40 20220101ALI20250527BHEP

Ipc: H04L 41/5054 20220101ALI20250527BHEP

Ipc: H04L 41/0895 20220101AFI20250527BHEP