WO2022154961A1 - Support pour serveur activateur de périphérie et gestion de cycle de vie de serveur de configuration de périphérie - Google Patents

Support pour serveur activateur de périphérie et gestion de cycle de vie de serveur de configuration de périphérie Download PDF

Info

Publication number
WO2022154961A1
WO2022154961A1 PCT/US2021/065318 US2021065318W WO2022154961A1 WO 2022154961 A1 WO2022154961 A1 WO 2022154961A1 US 2021065318 W US2021065318 W US 2021065318W WO 2022154961 A1 WO2022154961 A1 WO 2022154961A1
Authority
WO
WIPO (PCT)
Prior art keywords
ecsp
management system
ees
consumer
ecs
Prior art date
Application number
PCT/US2021/065318
Other languages
English (en)
Inventor
Joey Chou
Yizhi Yao
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Priority to CN202180081836.7A priority Critical patent/CN116648900A/zh
Publication of WO2022154961A1 publication Critical patent/WO2022154961A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G06F8/63—Image based installation; Cloning; Build to order
    • 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/34—Signalling channels for network management communication
    • H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, 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/5051—Service on demand, e.g. definition and deployment of services in real time
    • 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

Definitions

  • Various embodiments generally may relate to the field of wireless communications.
  • some embodiments may relate to servers of edge computing networks.
  • Various embodiments generally may relate to the field of wireless communications.
  • FIG. 1 depicts an example edge computing network, in accordance with various embodiments.
  • FIG. 2 depicts an example of edge enabler server (EES) lifecycle management using a lifecycle management (LCM) management service (MnS), in accordance with various embodiments.
  • EES edge enabler server
  • LCM lifecycle management
  • Figure 3 depicts an example of EES lifecycle management using a provisioning MnS, in accordance with various embodiments.
  • FIG. 4 depicts an example of edge configuration server (ECS) lifecycle management using a LCM MnS, in accordance with various embodiments.
  • ECS edge configuration server
  • Figure 5 depicts an example of ECS lifecycle management using a provisioning MnS, in accordance with various embodiments.
  • FIG. 6 depicts an example technique for instantiating an EES, in accordance with various embodiments.
  • FIG. 7 depicts an example technique for instantiating an EES, in accordance with various embodiments.
  • FIG. 8 depicts an example technique for instantiating an ECS, in accordance with various embodiments.
  • Figure 9 depicts an example technique for instantiating an ECS, in accordance with various embodiments.
  • Figure 10 schematically illustrates a wireless network, in accordance with various embodiments.
  • FIG 11 schematically illustrates components of a wireless network, in accordance with various embodiments.
  • Figure 12 schematically illustrates components of a wireless network, in accordance with various embodiments.
  • Figure 1 depicts an example edge computing network 100, in accordance with various embodiments. Specifically, Figure 1 depicts a typical edge computing network 100, where the mobile network 105 is connected to 2 edge data networks (EDNs) 110a and 110b.
  • the EDNs 110a and 110b may each contains 1 edge application server (EAS) 115a and 115b.
  • EAS edge application server
  • EES edge enabler server
  • PCF policy control function
  • EAS 115b and EES 120b may be trusted to the mobile operator of the mobile network 105, so EAS 115b and EES 120b may be connected to the network exposure function (NEF) via Edge-7 interface and Edge-2 interface, respectively.
  • ECS 135 may be connected to the NEF 130 via Edge-8 interface.
  • embodiments of the present disclosure are directed to deploying EESs, ECSs, and the fifth generation (5G) mobile networks to support edge computing. Some embodiments are directed to Mobility Robustness Optimization (MRO). Some embodiments may be directed to the solutions and use cases as shown below: EES deployment
  • This subclause relates to potential solutions for use cases of the EES deployment. Embodiments may be described with respect to two LCM solutions based on LCM MnS and provisioning MnS, respectively.
  • Figure 2 depicts an example of EES lifecycle management using a LCM MnS, in accordance with various embodiments.
  • Figure 2 illustrates an example wherein the edge computing service provider (ECSP) consumer requests the ECSP management system to perform EES lifecycle management via the LCM MnS.
  • Figure 2 depicts the ECSP consumer 205 with an MnS Consumer (MnS-C) 210.
  • Figure 2 further depicts a LCM MnS 215.
  • Figure 2 further depicts an ECSP management system 220 with an MnS Provider (MnS-P) 225.
  • the ECSP management system 220 is coupled with an EES virtual network function (VNF) 230.
  • VNF EES virtual network function
  • the ECSP management system 220 is further coupled with a European telecommunications standards institute (ETSI) network function virtualization (NFV) management and orchestration (MANO) 235 that includes a NFV orchestrator (NFVO) 240 via an OS-Ma-nfvo interface.
  • ETSI telecommunications standards institute
  • NFV network function virtualization
  • MANO NFV orchestrator
  • the ECSP consumer 205 may consume the LCM MnS 215 with operation instantiateEesReq to request the ECSP management system 220 to instantiate the EES, with the EES LCM IE that includes (but not limited to) the following attributes:
  • - EES profile includes (but not limited to) information about the EES.
  • EES Topological Service Area The list of Cell IDs (or tracking area identities (TAIs)) serviced by this EES.
  • IE EES VNF information element
  • the ECSP management system 220 may send an instantiateEesResp to notify the ECSP consumer 205 that the EES instantiation is in progress.
  • the ECSP management system 220 may download the EES VNF 230 software image from the software image location, and requests the NFVO 240 via the Os-Ma-nfvo interface to instantiate EES VNF 230 instance.
  • the ECSP management system 220 may send instantiateEesResp to notify the ECSP consumer 205 that the EES VNF 230 instance has been instantiated.
  • the ECSP management system 220 may create the following managed object instances (MOIs):
  • EES LCM ID indicates the EES LCM IE associated with the EES instances.
  • ECSP management system 220 may send notify MOICreati on to notify the ECSP consumer 205 that EES VNF MOIs have been created.
  • the ECSP consumer 205 may consume the LCM MnS 215 with operation terminateEesReq to request the ECSP management system 220 to terminate the EES including (but not limited to) the following attributes:
  • EES instance identifiers the identifier of EES VNF 230 instance(s) to be terminated.
  • ECSP management system 220 may send a terminateEesResp to notify the ECSO consumer 205 that the EES termination is in progress.
  • ECSP management system 220 may perform the following operations to terminate EES instances;
  • notifyMOIDeletion to notify the consumer that EES' EVE MOI have been deleted.
  • Figure 3 depicts an example of EES lifecycle management using a provisioning MnS
  • Figure 3 shows that the ECSP consumer 305 requests the ECSP management system 320 to perform EES lifecycle management via the provisioning MnS 315.
  • Figure 3 depicts the ECSP consumer 305 with an MnS-C 310.
  • Figure 3 further depicts a Provisioning MnS 315.
  • Figure 3 further depicts an ECSP management system 320 with an MnS-P 325.
  • the ECSP management system 320 is coupled with an EES VNF 330.
  • the ECSP management system 320 is further coupled with an ETSI NFV MANO 335 that includes a NFVO 340 via an OS-Ma-nfvo interface.
  • IOCS information object classes
  • - EES profile includes (but not limited to) information about the EES.
  • EES Topological Service Area The list of Cell IDs (or TAIs) serviced by this EES.
  • EES VNF information The information needed to instantiate the EES VNF.
  • Virtual compute resources including virtual CPU, virtual memory and virtual disk
  • the ECSP consumer 305 may consume the provisioning MnS 320 with operation createMOI for EESLcm IOC to request the provisioning MnS-P 325 to instantiate the EES.
  • the ECSP management system 320 may download the EES VNF 330 software image from the software image location, and requests the NFVO 340 via the Os-Ma-nfvo interface to instantiate the EES VNF 330 instance.
  • the ECSP management system320 may create the following MOIs:
  • EES LCM ID indicates the EES LCM IE associated with the EES instances.
  • the ECSP management system 320 may send notifyMOICreation to notify the ECSP consumer 305 that EES EVA MOIs have been created.
  • ECSP consumer 305 may consume the provisioning MnS 315 with operation deleteMOI to request the Provisioning MnS-P 325 to terminate the EE instance(s), including (but not limited to) the following attributes:
  • EES VNF instance ID the identifier of MOIs for EESFunction IOC indicating the EES VNF 330 instance(s) to be terminated.
  • the ECSP management system 320 may perform the following;
  • notifyMOIDeletion to notify the consumer that MOI for EESFunction IOC has been deleted.
  • This subclause provides potential solutions for use cases of the ECS deployment. It includes 2 possible LCM solutions based on LCM MnS and provisioning MnS, respectively.
  • Figure 4 depicts an example of ECS lifecycle management using a LCM MnS, in accordance with various embodiments. Specifically, Figure 4 shows that the ECSP consumer 405 requests the ECSP management system 420 to perform ECS lifecycle management via the LCM MnS 415. Figure 4 depicts the ECSP consumer 405 with an MnS-C 410. Figure 4 further depicts a LCM MnS 415. Figure 4 further depicts an ECSP management system 420 with an MnS-P 425. The ECSP management system 420 is coupled with an ECS VNF 430. The ECSP management system 420 is further coupled with an ETSI NFV MANO 435 that includes a NFVO 440 via an OS-Ma-nfvo interface.
  • the ECSP consumer 405 may consume the LCM MnS 415 with operation instantiateEcsReq to request the ECSP management system 420 to instantiate the ECS VNF 430, with the ECS LCM IE that includes (but not limited to) the following attributes:
  • ECS VNF IE The information needed to instantiate the ECS VNF. - Software image information
  • the ECSP management system 420 may send an instantiateEcsResp to notify the ECSP consumer 405 that the ECS instantiation is in progress.
  • ECSP management system 420 may download the ECS VNF 430 software image from the software image location, and request the NFVO 440 via the Os-Ma-nfvo interface to perform the following operations:
  • ECSP management system 420 may send instantiateEcsResp to notify the ECSP consumer 405 that ECS VNF 430 instance has been instantiated.
  • the ECSP management system 420 may create the following MOIs:
  • ECS LCM ID indicates the ECS LCM IE associated with the ECS instances.
  • ECSP management system 420 may send notify MOICreati on to notify the ECSP consumer 405 that ECS VNF MOIs have been created.
  • ECSP consumer 405 may consume the LCM MnS 415 with operation terminateEcsReq to request the ECSP management system 420 to terminate the ECS including (but not limited to) the following attributes:
  • ECS instance identifiers the identifier of ECS VNF 430 instance(s) to be terminated.
  • ECSP management system 420 may send a terminateEcsResp to notify the ECSP consumer 405 that the ECS termination is in progress.
  • ECSP management system 420 may perform the following operations to terminate ECS instances; - requests NFVO 440 to terminate the VNF instances identified by the EAS instance ID, and disconnect the ECS VNF 430 instance from the EAS VNF instance(s).
  • notifyMOIDeletion to notify the consumer that ECS VNF MOI have been deleted.
  • Figure 5 depicts an example of ECS lifecycle management using a provisioning MnS, in accordance with various embodiments.
  • the ECSP consumer 505 may request the ECSP management system 520 to perform ECS lifecycle management via the provisioning MnS 515.
  • Figure 5 depicts the ECSP consumer 505 with an MnS-C 510.
  • Figure 5 further depicts a provisioning MnS 515.
  • Figure 5 further depicts an ECSP management system 520 with an MnS-P 525.
  • the ECSP management system 520 is coupled with an ECS VNF 530.
  • the ECSP management system 520 is further coupled with an ETSI NFV MANO 535 that includes a NFVO 540 via an OS-Ma-nfvo interface.
  • IOCS To support ECS deployment via provisioning MnS, the following IOCS should be defined:
  • ECS VNF information The information needed to instantiate the ECS VNF.
  • Virtual compute resources including virtual CPU, virtual memory and virtual disk
  • ECSP consumer 505 may consume the provisioning MnS 515 and invoke operation createMOI for ECSLcm IOC to request the provisioning MnS 515 to instantiate the ECS.
  • ECSP management system 520 may download the ECS VNF 530 software image from the software image location, and requests NFVO 540 via the Os-Ma-nfvo interface to perform the following operations: - Instantiate ECS VNF 530 instance.
  • the ECSP management system creates the following MOIs:
  • ECS LCM ID indicates the ECS LCM IE associated with the ECS instances.
  • ECSP management system 520 sends notifyMOICreation to notify the consumer that ECS ITVFMOIs have been created.
  • ECSP consumer 505 may consume the provisioning MnS 515with operation deleteMOI to request the Provisioning MnS 515 and/or the MnS-P 525 to terminate the EE instance(s), including (but not limited to) the following attributes:
  • ECS VNF instance ID the identifier of MOIs for ECSFunction IOC indicating the ECS VNF instance(s) to be terminated.
  • ECSP management system 520 will perform the following;
  • notifyMOIDeletion to notify the consumer that MOI for ECSFunction IOC has been deleted.
  • Figure 6 depicts an example technique for EES instantiation, in accordance with various embodiments.
  • the technique of Figure 6 may be performed by, for example, ECSP management system 220 of Figure 2.
  • the technique may include identifying, at 605 by the ECSP management system, that an ECSP consumer (e.g., ECSP consumer 205) has consumed a LCM MnS (e.g., LCM MnS 215) with operation instantiateEesReq with an EES LCM IE.
  • the technique may further include instantiating, at 610 by the ECSP management system based on the operation instantiateEesReq, the EES.
  • Figure 7 depicts an example technique for EES instantiation, in accordance with various embodiments.
  • the technique of Figure 7 may be performed by, for example, ECSP management system 320 of Figure 3.
  • the technique may include identifying, at 705 by the ECSP management system, that an ECSP consumer (e.g., ECSP consumer 305) has consumed a provisioning MnS (e.g., provisioning MnS 315) with operation createMOI for EESLcm IOC.
  • the technique may further include instantiating, at 710 by a MnS-P 325 of the ECSP management system based on the operation createMOI, an EES.
  • Figure 8 depicts an example technique for ECS instantiation, in accordance with various embodiments.
  • the technique of Figure 8 may be performed by, for example, ECSP management system 420 of Figure 4.
  • the technique may include identifying, at 805 by the ECSP management system, that an ECSP consumer (e.g., ECSP consumer 405) has consumed a LCM MnS (e.g., LCM MnS 415) with operation instantiateEcsReq with an ECS LCM IE.
  • the technique may further include instantiating, at 810 by the ECSP management system based on the operation instantiateEcsReq, the ECS.
  • Figure 9 depicts an example technique for ECS instantiation, in accordance with various embodiments.
  • the technique of Figure 9 may be performed by, for example, ECSP management system 520 of Figure 5.
  • the technique may include identifying, at 905 by the ECSP management system, that an ECSP consumer (e.g., ECSP consumer 505) has consumed a provisioning MnS (e.g., provisioning MnS 515) with operation createMOI for ECSLcm IOC.
  • the technique may further include instantiating, at 910 by a MnS-P 525 of the ECSP management system based on the operation createMOI, an ECS.
  • FIGS 10-12 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
  • FIG. 10 illustrates a network 1000 in accordance with various embodiments.
  • the network 1000 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems.
  • 3GPP technical specifications for LTE or 5G/NR systems 3GPP technical specifications for LTE or 5G/NR systems.
  • the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.
  • the network 1000 may include a UE 1002, which may include any mobile or non-mobile computing device designed to communicate with a RAN 1004 via an over-the-air connection.
  • the UE 1002 may be communicatively coupled with the RAN 1004 by a Uu interface.
  • the UE 1002 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 1000 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 1002 may additionally communicate with an AP 1006 via an over-the-air connection.
  • the AP 1006 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 1004.
  • the connection between the UE 1002 and the AP 1006 may be consistent with any IEEE 802.11 protocol, wherein the AP 1006 could be a wireless fidelity (Wi-Fi®) router.
  • the UE 1002, RAN 1004, and AP 1006 may utilize cellular- WLAN aggregation (for example, LWA/LWIP).
  • Cellular- WLAN aggregation may involve the UE 1002 being configured by the RAN 1004 to utilize both cellular radio resources and WLAN resources.
  • the RAN 1004 may include one or more access nodes, for example, AN 1008.
  • AN 1008 may terminate air-interface protocols for the UE 1002 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 1008 may enable data/voice connectivity between CN 1020 and the UE 1002.
  • the AN 1008 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 1008 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc.
  • the AN 1008 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 1004 may be coupled with one another via an X2 interface (if the RAN 1004 is an LTE RAN) or an Xn interface (if the RAN 1004 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 1004 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 1002 with an air interface for network access.
  • the UE 1002 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 1004.
  • the UE 1002 and RAN 1004 may use carrier aggregation to allow the UE 1002 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 1004 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 1002 or AN 1008 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications.
  • An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE.
  • An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like.
  • an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs.
  • the RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic.
  • the RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services.
  • the components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.
  • the RAN 1004 may be an LTE RAN 1010 with eNBs, for example, eNB 1012.
  • the LTE RAN 1010 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc.
  • the LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE.
  • the LTE air interface may operating on sub-6 GHz bands.
  • the RAN 1004 may be an NG-RAN 1014 with gNBs, for example, gNB 1016, or ng-eNBs, for example, ng-eNB 1018.
  • the gNB 1016 may connect with 5G-enabled UEs using a 5GNR interface.
  • the gNB 1016 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface.
  • the ng-eNB 1018 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface.
  • the gNB 1016 and the ng-eNB 1018 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 1014 and a UPF 1048 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN1014 and an AMF 1044 (e.g., N2 interface).
  • NG-U NG user plane
  • N3 interface e.g., N3 interface
  • N-C NG control plane
  • the NG-RAN 1014 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data.
  • the 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface.
  • the 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking.
  • the 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz.
  • the 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.
  • the 5G-NR air interface may utilize BWPs for various purposes.
  • BWP can be used for dynamic adaptation of the SCS.
  • the UE 1002 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 1002, 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 1002 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 1002 and in some cases at the gNB 1016.
  • a BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.
  • the RAN 1004 is communicatively coupled to CN 1020 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 1002).
  • the components of the CN 1020 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 1020 onto physical compute/storage resources in servers, switches, etc.
  • a logical instantiation of the CN 1020 may be referred to as a network slice, and a logical instantiation of a portion of the CN 1020 may be referred to as a network sub-slice.
  • the CN 1020 may be an LTE CN 1022, which may also be referred to as an EPC.
  • the LTE CN 1022 may include MME 1024, SGW 1026, SGSN 1028, HSS 1030, PGW 1032, and PCRF 1034 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 1022 may be briefly introduced as follows.
  • the MME 1024 may implement mobility management functions to track a current location of the UE 1002 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.
  • the SGW 1026 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 1022.
  • the SGW 1026 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the SGSN 1028 may track a location of the UE 1002 and perform security functions and access control. In addition, the SGSN 1028 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 1024; MME selection for handovers; etc.
  • the S3 reference point between the MME 1024 and the SGSN 1028 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle/active states.
  • the HSS 1030 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions.
  • the HSS 1030 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • An S6a reference point between the HSS 1030 and the MME 1024 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 1020.
  • the PGW 1032 may terminate an SGi interface toward a data network (DN) 1036 that may include an application/content server 1038.
  • the PGW 1032 may route data packets between the LTE CN 1022 and the data network 1036.
  • the PGW 1032 may be coupled with the SGW 1026 by an S5 reference point to facilitate user plane tunneling and tunnel management.
  • the PGW 1032 may further include a node for policy enforcement and charging data collection (for example, PCEF).
  • the SGi reference point between the PGW 1032 and the data network 10 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services.
  • the PGW 1032 may be coupled with a PCRF 1034 via a Gx reference point.
  • the PCRF 1034 is the policy and charging control element of the LTE CN 1022.
  • the PCRF 1034 may be communicatively coupled to the app/content server 1038 to determine appropriate QoS and charging parameters for service flows.
  • the PCRF 1032 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.
  • the CN 1020 may be a 5GC 1040.
  • the 5GC 1040 may include an AUSF 1042, AMF 1044, SMF 1046, UPF 1048, NSSF 1050, NEF 1052, NRF 1054, PCF 1056, UDM 1058, and AF 1060 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 1040 may be briefly introduced as follows.
  • the AUSF 1042 may store data for authentication of UE 1002 and handle authentication- related functionality.
  • the AUSF 1042 may facilitate a common authentication framework for various access types.
  • the AUSF 1042 may exhibit an Nausf service-based interface.
  • the AMF 1044 may allow other functions of the 5GC 1040 to communicate with the UE 1002 and the RAN 1004 and to subscribe to notifications about mobility events with respect to the UE 1002.
  • the AMF 1044 may be responsible for registration management (for example, for registering UE 1002), connection management, reachability management, mobility management, lawful interception of AMF -related events, and access authentication and authorization.
  • the AMF 1044 may provide transport for SM messages between the UE 1002 and the SMF 1046, and act as a transparent proxy for routing SM messages.
  • AMF 1044 may also provide transport for SMS messages between UE 1002 and an SMSF.
  • AMF 1044 may interact with the AUSF 1042 and the UE 1002 to perform various security anchor and context management functions.
  • AMF 1044 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 1004 and the AMF 1044; and the AMF 1044 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection.
  • AMF 1044 may also support NAS signaling with the UE 1002 over an N3 IWF interface.
  • the SMF 1046 may be responsible for SM (for example, session establishment, tunnel management between UPF 1048 and AN 1008); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 1048 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 1044 overN2 to AN 1008; 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 1002 and the data network 1036.
  • the UPF 1048 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 1036, and a branching point to support multi-homed PDU session.
  • the UPF 1048 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 1048 may include an uplink classifier to support routing traffic flows to a data network.
  • the NSSF 1050 may select a set of network slice instances serving the UE 1002.
  • the NSSF 1050 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed.
  • the NSSF 1050 may also determine the AMF set to be used to serve the UE 1002, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 1054.
  • the selection of a set of network slice instances for the UE 1002 may be triggered by the AMF 1044 with which the UE 1002 is registered by interacting with the NSSF 1050, which may lead to a change of AMF.
  • the NSSF 1050 may interact with the AMF 1044 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 1050 may exhibit an Nnssf service-based interface.
  • the NEF 1052 may securely expose services and capabilities provided by 3 GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 1060), edge computing or fog computing systems, etc.
  • the NEF 1052 may authenticate, authorize, or throttle the AFs.
  • NEF 1052 may also translate information exchanged with the AF 1060 and information exchanged with internal network functions. For example, the NEF 1052 may translate between an AF-Service-Identifier and an internal 5GC information.
  • NEF 1052 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 1052 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 1052 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 1052 may exhibit an Nnef servicebased interface.
  • the NRF 1054 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 1054 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 1054 may exhibit the Nnrf service-based interface.
  • the PCF 1056 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior.
  • the PCF 1056 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 1058.
  • the PCF 1056 exhibit an Npcf service-based interface.
  • the UDM 1058 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 1002. For example, subscription data may be communicated via an N8 reference point between the UDM 1058 and the AMF 1044.
  • the UDM 1058 may include two parts, an application front end and a UDR.
  • the UDR may store subscription data and policy data for the UDM 1058 and the PCF 1056, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 1002) for the NEF 1052.
  • the Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 1058, PCF 1056, and NEF 1052 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 1058 may exhibit the Nudm service-based interface.
  • the AF 1060 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.
  • the 5GC 1040 may enable edge computing by selecting operator/3 rd party services to be geographically close to a point that the UE 1002 is attached to the network. This may reduce latency and load on the network.
  • the 5GC 1040 may select a UPF 1048 close to the UE 1002 and execute traffic steering from the UPF 1048 to data network 1036 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 1060. In this way, the AF 1060 may influence UPF (re)selection and traffic routing.
  • the network operator may permit AF 1060 to interact directly with relevant NFs. Additionally, the AF 1060 may exhibit an Naf service-based interface.
  • the data network 1036 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 1038.
  • FIG 11 schematically illustrates a wireless network 1100 in accordance with various embodiments.
  • the wireless network 1100 may include a UE 1102 in wireless communication with an AN 1104.
  • the UE 1102 and AN 1104 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.
  • the UE 1102 may be communicatively coupled with the AN 1104 via connection 1106.
  • the connection 1106 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.
  • the UE 1102 may include a host platform 1108 coupled with a modem platform 1110.
  • the host platform 1108 may include application processing circuitry 1112, which may be coupled with protocol processing circuitry 1114 of the modem platform 1110.
  • the application processing circuitry 1112 may run various applications for the UE 1102 that source/sink application data.
  • the application processing circuitry 1112 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 1114 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 1106.
  • the layer operations implemented by the protocol processing circuitry 1114 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.
  • the modem platform 1110 may further include digital baseband circuitry 1116 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 1114 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 1110 may further include transmit circuitry 1118, receive circuitry 1120, RF circuitry 1122, and RF front end (RFFE) 1124, which may include or connect to one or more antenna panels 1126.
  • the transmit circuitry 1118 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.
  • the receive circuitry 1120 may include an analog-to-digital converter, mixer, IF components, etc.
  • the RF circuitry 1122 may include a low-noise amplifier, a power amplifier, power tracking components, etc.
  • RFFE 1124 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc.
  • transmit/receive components may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc.
  • the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.
  • the protocol processing circuitry 1114 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 1126, RFFE 1124, RF circuitry 1122, receive circuitry 1120, digital baseband circuitry 1116, and protocol processing circuitry 1114.
  • the antenna panels 1126 may receive a transmission from the AN 1104 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 1126.
  • a UE transmission may be established by and via the protocol processing circuitry 1114, digital baseband circuitry 1116, transmit circuitry 1118, RF circuitry 1122, RFFE 1124, and antenna panels 1126.
  • the transmit components of the UE 1104 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 1126.
  • the AN 1104 may include a host platform 1128 coupled with a modem platform 1130.
  • the host platform 1128 may include application processing circuitry 1132 coupled with protocol processing circuitry 1134 of the modem platform 1130.
  • the modem platform may further include digital baseband circuitry 1136, transmit circuitry 1138, receive circuitry 1140, RF circuitry 1142, RFFE circuitry 1144, and antenna panels 1146.
  • the components of the AN 1104 may be similar to and substantially interchangeable with like- named components of the UE 1102.
  • the components of the AN 1108 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.
  • Figure 12 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 12 shows a diagrammatic representation of hardware resources 1200 including one or more processors (or processor cores) 1210, one or more memory/storage devices 1220, and one or more communication resources 1230, each of which may be communicatively coupled via a bus 1240 or other interface circuitry.
  • a hypervisor 1202 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1200.
  • the processors 1210 may include, for example, a processor 1212 and a processor 1214.
  • the processors 1210 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 radiofrequency 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 radiofrequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • the memory/storage devices 1220 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 1220 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 1230 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1204 or one or more databases 1206 or other network elements via a network 1208.
  • the communication resources 1230 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 1250 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1210 to perform any one or more of the methodologies discussed herein.
  • the instructions 1250 may reside, completely or partially, within at least one of the processors 1210 (e.g., within the processor’s cache memory), the memory/storage devices 1220, or any suitable combination thereof.
  • any portion of the instructions 1250 may be transferred to the hardware resources 1200 from any combination of the peripheral devices 1204 or the databases 1206. Accordingly, the memory of processors 1210, the memory/storage devices 1220, the peripheral devices 1204, and the databases 1206 are examples of computer-readable and machine-readable media.
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • Example 1 may include a method of operating a wireless network wherein a consumer consumes the LCM Management Service (MnS) with operation instantiateEesReq with the EES LCM IE to request the ECSP management system to instantiate the EES (Edge Enabler Server).
  • MnS LCM Management Service
  • EES Edge Enabler Server
  • Example 2 may include the method according to example 1 or some other example herein, wherein the EES LCM IE includes: EES profile: includes EES Topological Service Area, EES Geographical Service Area; and EES VNF IE: includes Software image information, Software image location, Minimum RAM, Minimum disk; and Virtual compute resources; include Virtual CPU, Virtual memory, Virtual disk.
  • EES LCM IE includes: EES profile: includes EES Topological Service Area, EES Geographical Service Area; and EES VNF IE: includes Software image information, Software image location, Minimum RAM, Minimum disk; and Virtual compute resources; include Virtual CPU, Virtual memory, Virtual disk.
  • Example 3 may include the method according to examples 1 and 2 or some other example herein, wherein upon receiving a request to install an EES via operation instantiateEesReq, the ECSP management system is configured to: sends an instantiateEesResp to notify the consumer that the EES instantiation is in progress; and download the EES VNF software image from the software image location in the EES LCM IE; and request NFVO via the Os-Ma-nfvo interface to instantiate EES; and send an instantiateEesResp to notify the consumer that the EES has been instantiated; and create the EES VNF MOI from the EES VNF IOC; and send notifyMOICreation to notify the consumer that EES VNF MOIs have been created.
  • Example 4 may include an apparatus of a management system, comprising memory; and processing circuitry configured to operate as the consumer consumes the LCM MnS with operation terminateEesReq with the EES instance identifier to request the ECSP management system to terminate the EES.
  • Example 5 may include the method according to example 4 or some other example herein, wherein upon receiving a request to terminate an EES via operation terminateEesReq, the ECSP management system is configured to: sends a terminateEesResp to notify the consumer that the EES termination is in progress; and request NFVO via the Os-Ma-nfvo interface to terminate EES; and send a terminateEesResp to notify the consumer that the EES has been terminated; and delete the EES VNF MOI; and send notifyMOIDeletion to notify the consumer that EES VNF MOI have been deleted.
  • Example 6 may include the apparatus of a management system, comprising memory; and processing circuitry configured to operate as the consumer consumes the provisioning MnS with operation createMOI for EESLcm IOC to request the provisioning MnS Producer to instantiate the EES.
  • Example 7 may include the method according to example 6 or some other example herein, wherein the EESLcm IOC includes: EES profile: includes EES Topological Service Area, EES Geographical Service Area; and EES VNF IE: includes Software image information, Software image location, Minimum RAM, Minimum disk; and Virtual compute resources; include Virtual CPU, Virtual memory, Virtual disk.
  • EES profile includes EES Topological Service Area, EES Geographical Service Area
  • EES VNF IE includes Software image information, Software image location, Minimum RAM, Minimum disk
  • Virtual compute resources include Virtual CPU, Virtual memory, Virtual disk.
  • Example 8 may include the method according to examples 6 and 7 or some other example herein, wherein upon receiving a request to install an EES via operation createMOI, the ECSP management system is configured to: download the EES VNF software image from the software image location in the EESLcm IOC; and request NFVO via the Os-Ma-nfvo interface to instantiate EES; and create the EESLcm MOI; and send notifyMOICreation to notify the consumer that EESLcm MOI have been created.
  • Example 9 may include an apparatus of a management system, comprising memory; and processing circuitry configured to operate as the consumer consumes the provisioning MnS with operation deleteMOI with the EES instance identifier to request the ECSP management system to terminate the EES.
  • Example 10 may include the method according to example 9 or some other example herein, wherein upon receiving a request to terminate an EES via operation deleteMOI, the ECSP management system is configured to: request NFVO via the Os-Ma-nfvo interface to terminate EES; and delete the EESLcm MOI; and send notifyMOIDeletion to notify the consumer that EESLcm MOI have been deleted.
  • Example 11 may include an apparatus of a management system, comprising memory; and processing circuitry configured to operate as the consumer consumes the LCM Management Service (MnS) with operation instantiateEesReq with the ECS LCM IE to request the ECSP management system to instantiate the ECS (Edge Configuration Server).
  • MnS LCM Management Service
  • ECS Edge Configuration Server
  • Example 12 may include the method according to example 1 or some other example herein, wherein the ECS LCM IE includes: ECS VNF IE: includes Software image information, Software image location, Minimum RAM, Minimum disk; and Virtual compute resources; include Virtual CPU, Virtual memory, Virtual disk.
  • ECS LCM IE includes: ECS VNF IE: includes Software image information, Software image location, Minimum RAM, Minimum disk; and Virtual compute resources; include Virtual CPU, Virtual memory, Virtual disk.
  • Example 13 may include the method according to examples 1 and 2 or some other example herein, wherein upon receiving a request to install an ECS via operation instantiateEesReq, the ECSP management system is configured to: sends an instantiateEcsResp to notify the consumer that the ECS instantiation is in progress; and download the ECS VNF software image from the software image location in the ECS LCM IE; and request NFVO via the Os-Ma-nfvo interface to instantiate ECS; and send an instantiateEcsResp to notify the consumer that the ECS has been instantiated; and create the ECS VNF MOI from the ECS VNF IOC; and send notifyMOICreation to notify the consumer that ECS VNF MOIs have been created.
  • Example 14 may include an apparatus of a management system, comprising memory; and processing circuitry configured to operate as the consumer consumes the LCM MnS with operation terminateECSReq with the ECS instance identifier to request the ECSP management system to terminate the ECS.
  • Example 15 may include the method according to example 4 or some other example herein, wherein upon receiving a request to terminate an ECS via operation terminateEcsReq, the ECSP management system is configured to: sends a terminateEcsResp to notify the consumer that the ECS termination is in progress; and request NFVO via the Os-Ma-nfvo interface to terminate ECS; and send a terminateEcsResp to notify the consumer that the ECS has been terminated; and delete the ECS VNF MOI; and send notifyMOIDeletion to notify the consumer that ECS VNF MOI have been deleted.
  • Example 16 may include an apparatus of a management system, comprising memory; and processing circuitry configured to operate as the consumer consumes the provisioning MnS with operation createMOI for ECSLcm IOC to request the provisioning MnS Producer to instantiate the ECS.
  • Example 17 may include the method according to example 6 or some other example herein, wherein the ECSLcm IOC includes: ECS VNF IE: includes Software image information, Software image location, Minimum RAM, Minimum disk; and Virtual compute resources; include Virtual CPU, Virtual memory, Virtual disk.
  • ECS VNF IE includes Software image information, Software image location, Minimum RAM, Minimum disk; and Virtual compute resources; include Virtual CPU, Virtual memory, Virtual disk.
  • Example 18 may include the method according to examples 6 and 7 or some other example herein, wherein upon receiving a request to install an ECS via operation createMOI, the ECSP management system is configured to: download the ECS VNF software image from the software image location in the ECSLcm IOC; and request NFVO via the Os-Ma-nfvo interface to instantiate ECS; and create the ECSLcm MOI; and send notifyMOICreation to notify the consumer that ECSLcm MOI have been created.
  • Example 19 may include an apparatus of a management system, comprising memory; and processing circuitry configured to operate as the consumer consumes the provisioning MnS with operation deleteMOI with the ECS instance identifier to request the ECSP management system to terminate the ECS.
  • Example 20 may include the method according to example 9 or some other example herein, wherein upon receiving a request to terminate an ECS via operation deleteMOI, the ECSP management system is configured to: request NFVO via the Os-Ma-nfvo interface to terminate ECS; and delete the ECSLcm MOI; and send notifyMOIDeletion to notify the consumer that ECSLcm MOI have been deleted.
  • Example 21 includes a method comprising: receiving, by an edge computing service provider (ECSP), a request to instantiate an EES (Edge Enabler Server); and in response to receiving the a request to insstall the EES: sending an instantiateEesResp to notify a consumer that the EES instantiation is in progress; downloading an EES virtual network function (VNF) software image from a software image location indicated in an EES life cycle management (LCM) information element IE; requesting a network virtualization function orchestrator (NFVO) via an Os-Ma-nfvo interface to instantiate EES; sending an instantiateEesResp to notify the consumer that the EES has been instantiated; creating an EES VNF managed object instance (MOI) from an EES VNF information object class (IOC); and sending a notify MOICreati on to notify the consumer that EES VNF MOIs have been created.
  • ECSP edge computing service provider
  • EES Edge Enabler Server
  • Example 22 includes the method of example 21 or some other example herein, wherein the EES LCM IE includes: an EES profile that includes EES Topological Service Area, or EES Geographical Service Area.
  • Example 23 includes the method of example 21 or some other example herein, wherein the EES LCM IE includes: an EES VNF IE that includes Software image information, Software image location, Minimum RAM, or Minimum disk.
  • the EES LCM IE includes: an EES VNF IE that includes Software image information, Software image location, Minimum RAM, or Minimum disk.
  • Example 23 includes the method of example 21 or some other example herein, wherein the EES LCM IE includes: virtual compute resources that include Virtual CPU, Virtual memory, or Virtual disk.
  • Example 24 includes a method comprising: identifying, by an edge computing service provider (ECSP) management system, that an ECSP consumer has consumed a lifecycle management (LCM) management service (MnS) with operation instantiateEesReq with an edge enabler server (EES) LCM information element (IE); and instantiating, by the ECSP management system based on the operation instantiateEesReq, the EES.
  • ECSP edge computing service provider
  • MnS lifecycle management service
  • EES edge enabler server
  • IE edge enabler server
  • Example 25 includes the method of example 24, or some other example herein, wherein the EES LCM IE includes an EES profile, an EES virtual network function (VNF) IE, and an indication of one or more virtual compute resources.
  • the EES LCM IE includes an EES profile, an EES virtual network function (VNF) IE, and an indication of one or more virtual compute resources.
  • VNF virtual network function
  • Example 26 includes the method of examples 24 or 25, or some other example herein wherein instantiating the EES includes: transmitting, by the ECSP management system to the ECSP consumer, an instantiate EesResp notification; retrieving, by the ECSP management system from a software image location in the EES LCM IE, an EES virtual network function (VNF) software image; transmitting, by the ECSP management system to a network function virtualization orchestrator (NFVO) via a Os-Ma-nfvo interface, a request to instantiate the EES; transmitting, by the ECSP management system to the ECSP consumer, instantiateEesResp to notify the ECSP consumer that the EES has been instantiated; creating, by the ECSP management system, an EES VNF managed object instances (MOIs) from an EES VNF information object class (IOC); and transmitting, by the ECSP management system to the ECSP consumer, notifyMOICreation to notify the ECSP consumer that the E
  • Example 27 includes the method of example 26, or some other example herein, further comprising identifying, by the ECSP management system, that the ECSP consumer has consumed the LCM MnS with operation terminateEesReq with an EES instance identifier related to the EES; and terminating, by the ECSP management system based on operation terminateEesReq, the EES.
  • Example 28 includes the method of example 27, or some other example herein, wherein terminating the EES includes: transmitting, by the ECSP management system to the ECSP consumer, terminateEesResp; transmitting, by the ECSP management system to the NFVO via the Os-Ma-nfvo interface, a request to terminate the EES; transmitting, by the ECSP management system to the ECSP consumer, a notification that the EES has been terminated; deleting, by the ECSP management system, the EES VNF MOI; and transmitting, by the ECSP management system to the ECSP consumer, notifyMOIDeletion to notify the ECSP consumer that the EES VNF MOI has been deleted.
  • Example 29 includes a method comprising: identifying, by an edge computing service provider (ECSP) management system, that an ECSP consumer has consumed a provisioning management service (MnS) with operation createMOI for EESLcm information object class (IOC); and instantiating, by a MnS producer (MnS-P) of the ECSP management system based on the operation createMOI, an edge enabler server (EES).
  • ECSP edge computing service provider
  • MnS provisioning management service
  • IOC EESLcm information object class
  • EES edge enabler server
  • Example 30 includes the method of example 29, or some other example herein, wherein the EESlcm IOC includes an EES profile, an EES virtual network function (VNF) IE, and an indication of one or more virtual compute resources.
  • the EESlcm IOC includes an EES profile, an EES virtual network function (VNF) IE, and an indication of one or more virtual compute resources.
  • VNF virtual network function
  • Example 31 includes the method of examples 29 or 30, or some other example herein, wherein instantiating the EES includes: retrieving, by the ECSP management system from a software image location in the EESLcm IOC, an EES virtual network function (VNF) software image; transmitting, by the ECSP management system to a network function virtualization orchestrator (NFVO) via a Os-Ma-nfvo interface, a request to instantiate the EES; creating, by the ECSP management system, the EESLcm MOI; and transmitting, by the ECSP management system to the ECSP consumer, notify MO ICreati on to notify the ECSP consumer that the EESLcm MOI has been created.
  • VNF virtual network function
  • Example 32 includes the method of example 31, or some other example herein, further comprising identifying, by the ECSP management system, that the ECSP consumer has consumed the provisioning MnS with operation deleteMOI with an EES instance identifier related to the EES; and terminating, by the ECSP management system based on operation deleteMOI, the EES.
  • Example 33 includes the method of example 32, or some other example herein, wherein terminating the EES includes: transmitting, by the ECSP management system to the NFVO via the Os-Ma-nfvo interface, a request to terminate the EES; deleting, by the ECSP management system, the EESLcm MOI; and transmitting, by the ECSP management system to the ECSP consumer, notifyMOIDeletion to notify the ECSP consumer that the EESLcm MOI has been deleted.
  • Example 34 includes a method comprising: identifying, by an edge computing service provider (ECSP) management system, that an ECSP consumer has consumed a lifecycle management (LCM) management service (MnS) with operation instantiateEcsReq with an edge configuration server (ECS) LCM information element (IE); and instantiating, by the ECSP management system based on the operation instantiateEcsReq, the ECS.
  • ECSP edge computing service provider
  • MnS lifecycle management service
  • IE edge configuration server
  • Example 35 includes the method of example 34, or some other example herein, wherein the ECS LCM IE includes an ECS virtual network function (VNF) IE and an indication of one or more virtual compute resources.
  • VNF ECS virtual network function
  • Example 36 includes the method of examples 34 or 35, or some other example herein, wherein instantiating the ECS includes: transmitting, by the ECSP management system to the ECSP consumer, an instantiate EcsResp notification; retrieving, by the ECSP management system from a software image location in the ECS LCM IE, an ECS virtual network function (VNF) software image; transmitting, by the ECSP management system to a network function virtualization orchestrator (NFVO) via a Os-Ma-nfvo interface, a request to instantiate the ECS; transmitting, by the ECSP management system to the ECSP consumer, instantiateEcsResp to notify the ECSP consumer that the ECS has been instantiated; creating, by the ECSP management system, an ECS VNF managed object instances (MOIs) from an ECS VNF information object class (IOC); and transmitting, by the ECSP management system to the ECSP consumer, notifyMOICreation to notify the ECSP consumer that the
  • Example 37 includes the method of example 36, or some other example herein, further comprising identifying, by the ECSP management system, that the ECSP consumer has consumed the LCM MnS with operation terminateECSReq with an ECS instance identifier related to the EECSES; and terminating, by the ECSP management system based on operation terminateECSReq, the ECS.
  • Example 38 includes the method of example 37, or some other example herein, wherein terminating the ECS includes: transmitting, by the ECSP management system to the ECSP consumer, terminateEcsResp; transmitting, by the ECSP management system to the NFVO via the Os-Ma-nfvo interface, a request to terminate the ECS; transmitting, by the ECSP management system to the ECSP consumer, a notification that the ECS has been terminated; deleting, by the ECSP management system, the ECS VNF MOI; and transmitting, by the ECSP management system to the ECSP consumer, notifyMOIDeletion to notify the ECSP consumer that the ECS VNF MOI has been deleted.
  • Example 39 includes a method comprising: identifying, by an edge computing service provider (ECSP) management system, that an ECSP consumer has consumed a provisioning management service (MnS) with operation createMOI for ECSLcm information object class (IOC); and instantiating, by a MnS producer (MnS-P) of the ECSP management system based on the operation createMOI, an edge configuration server (ECS).
  • ECSP edge computing service provider
  • MnS provisioning management service
  • IOC ECSLcm information object class
  • ECS edge configuration server
  • Example 40 includes the method of example 39, or some other example herein, wherein the ECSlcm IOC includes an ECS virtual network function (VNF) IE and an indication of one or more virtual compute resources.
  • VNF ECS virtual network function
  • Example 41 includes the method of examples 39 or 40, or some other example herein, wherein instantiating the ECS includes: retrieving, by the ECSP management system from a software image location in the ECSLcm IOC, an ECS virtual network function (VNF) software image; transmitting, by the ECSP management system to a network function virtualization orchestrator (NFVO) via a Os-Ma-nfvo interface, a request to instantiate the ECS; creating, by the ECSP management system, the ECSLcm MOI; and transmitting, by the ECSP management system to the ECSP consumer, notifyMOICreation to notify the ECSP consumer that the ECSLcm MOI has been created.
  • VNF virtual network function
  • Example 42 includes the method of example 41, or some other example herein, further comprising identifying, by the ECSP management system, that the ECSP consumer has consumed the provisioning MnS with operation deleteMOI with an ECS instance identifier related to the ECS; and terminating, by the ECSP management system based on operation deleteMOI, the ECS.
  • Example 43 includes the method of example 42, or some other example herein, wherein terminating the ECS includes: transmitting, by the ECSP management system to the NFVO via the Os-Ma-nfvo interface, a request to terminate the ECS; deleting, by the ECSP management system, the ECSLcm MOI; and transmitting, by the ECSP management system to the ECSP consumer, notifyMOIDeletion to notify the ECSP consumer that the ECSLcm MOI has been deleted.
  • Example 44 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-43, or any other method or process described herein.
  • Example 45 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-43, or any other method or process described herein.
  • Example 46 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-43, or any other method or process described herein.
  • Example 47 may include a method, technique, or process as described in or related to any of examples 1-43, or portions or parts thereof.
  • Example 48 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-43, or portions thereof.
  • Example 49 may include a signal as described in or related to any of examples 1-43, or portions or parts thereof.
  • Example 50 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-43, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example 51 may include a signal encoded with data as described in or related to any of examples 1-43, or portions or parts thereof, or otherwise described in the present disclosure.
  • Example 52 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-43, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example 53 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-43, or portions thereof.
  • Example 54 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-43, or portions thereof.
  • Example 55 may include a signal in a wireless network as shown and described herein.
  • Example 56 may include a method of communicating in a wireless network as shown and described herein.
  • Example 57 may include a system for providing wireless communication as shown and described herein.
  • Example 58 may include a device for providing wireless communication as shown and described herein.
  • 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 computerexecutable 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 “instantiation,” and the like as used herein 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.
  • the term “Serving Cell” refers to the primary cell for a UE in RRC CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.
  • 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)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers modes de réalisation de la présente invention concernent des techniques associées à l'identification, par un système de gestion de fournisseur de service de calcul de périphérie (ECSP), qu'un consommateur d'ECSP a consommé un service de gestion (MnS) avec une opération pour instancier un serveur de périphérie. Le système de gestion d'ECSP peut ensuite activer le serveur de périphérie. Dans certains modes de réalisation, le MnS peut être un MnS d'approvisionnement ou un MnS de gestion de cycle de vie (LCM). Dans certains modes de réalisation, le serveur de périphérie peut être un serveur activateur de périphérie (EES) ou un serveur de configuration de périphérie (ECS). D'autres modes de réalisation peuvent être décrits ou revendiqués.
PCT/US2021/065318 2021-01-12 2021-12-28 Support pour serveur activateur de périphérie et gestion de cycle de vie de serveur de configuration de périphérie WO2022154961A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202180081836.7A CN116648900A (zh) 2021-01-12 2021-12-28 对边缘启用服务器和边缘配置服务器生命周期管理的支持

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163136541P 2021-01-12 2021-01-12
US63/136,541 2021-01-12

Publications (1)

Publication Number Publication Date
WO2022154961A1 true WO2022154961A1 (fr) 2022-07-21

Family

ID=82448521

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2021/065318 WO2022154961A1 (fr) 2021-01-12 2021-12-28 Support pour serveur activateur de périphérie et gestion de cycle de vie de serveur de configuration de périphérie

Country Status (2)

Country Link
CN (1) CN116648900A (fr)
WO (1) WO2022154961A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024027398A1 (fr) * 2022-08-05 2024-02-08 华为技术有限公司 Procédé et appareil de communication

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190327621A1 (en) * 2017-01-05 2019-10-24 Intel IP Corporation Instantiation and management of physical and virtualized network functions of a radio access network node
US20200021487A1 (en) * 2018-03-12 2020-01-16 Yizhi Yao Management services for 5g networks and network functions

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190327621A1 (en) * 2017-01-05 2019-10-24 Intel IP Corporation Instantiation and management of physical and virtualized network functions of a radio access network node
US20200021487A1 (en) * 2018-03-12 2020-01-16 Yizhi Yao Management services for 5g networks and network functions

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3 Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture for enabling Edge Applications; (Release 17)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.558, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V1.2.0, 7 December 2020 (2020-12-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 131, XP051961777 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects Management and orchestration; Study on enhancements of edge computing management (Release 17)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 28.814, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V0.2.0, 2 November 2020 (2020-11-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 22, XP051961639 *
SAMSUNG: "pCR Edge Deployment", 3GPP DRAFT; S5-204130, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG5, no. Online; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051916670 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024027398A1 (fr) * 2022-08-05 2024-02-08 华为技术有限公司 Procédé et appareil de communication

Also Published As

Publication number Publication date
CN116648900A (zh) 2023-08-25

Similar Documents

Publication Publication Date Title
US11871436B2 (en) Apparatus for UE measurement delay and granularity for new radio positioning measurement
US11968559B2 (en) Apparatus and method for 5G quality of service indicator management
US11871460B2 (en) Domain name system (DNS)-based discovery of regulatory requirements for non-3GPP inter-working function (N3IWF) selection
US20230141237A1 (en) Techniques for management data analytics (mda) process and service
US11792814B2 (en) Techniques for cancelation of one or more uplink transmissions from a user equipment
WO2022159400A1 (fr) Surveillance de qualité de service dans un réseau ponté sensible au temps cellulaire intégré
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
US11979894B2 (en) Soft resource availability indication for integrated access and backhaul (IAB) operation in paired spectrum
WO2022011527A1 (fr) Configuration et transmission de srs en multi-dci multi-trp et agrégation de porteuses
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
US11751228B2 (en) Methods and apparatuses for uplink spatial relation info switch
EP4207666A1 (fr) Configuration d'occasions de surveillance de pdcch pour capacité de surveillance de pdcch à intervalles multiples
US20240187172A1 (en) Single trp and multiple trp dynamic switching for single dci based pusch transmissions
EP4240050A1 (fr) Fonctions et services associés à des informations d'enrichissement a1 dans un contrôleur intelligent ran en temps non réel
WO2022155098A1 (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
WO2023018727A1 (fr) Procédés et appareil de gestion de cycle de vie améliorée dans des serveurs informatiques périphériques 5g
WO2023033813A1 (fr) Transmission de csi-rs (signal de référence d'informations d'état de canal) basée sur un groupe
WO2022217083A1 (fr) Procédés et appareil pour prendre en charge une optimisation de gestion de ressources radio (rrm) pour des instances de tranches de réseau dans des systèmes 5g
WO2022155505A1 (fr) Techniques de déclenchement d'un signal de référence de sondage (srs) apériodique et flexible
WO2022216859A1 (fr) Configuration d'avance temporelle pour mobilité inter-cellules
WO2023212049A1 (fr) Mécanismes de commutation d'émission à porteuses multiples pour des systèmes de nouvelle radio dans un ran1 5g
WO2022240614A1 (fr) Commutation dynamique trp unique et mult-trp pour des transmissions pusch à base de dci unique
WO2022177822A1 (fr) Actualisation de clés d'ancrage dérivées à long terme et gestion d'identité fédérée

Legal Events

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

Ref document number: 21920076

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180081836.7

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21920076

Country of ref document: EP

Kind code of ref document: A1