WO2018095537A1 - Fourniture d'applications à un serveur périphérique mobile - Google Patents

Fourniture d'applications à un serveur périphérique mobile Download PDF

Info

Publication number
WO2018095537A1
WO2018095537A1 PCT/EP2016/078842 EP2016078842W WO2018095537A1 WO 2018095537 A1 WO2018095537 A1 WO 2018095537A1 EP 2016078842 W EP2016078842 W EP 2016078842W WO 2018095537 A1 WO2018095537 A1 WO 2018095537A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
server
mobile edge
edge computing
specific application
Prior art date
Application number
PCT/EP2016/078842
Other languages
English (en)
Inventor
Juha Antero Rasanen
Michael John Rooke
Original Assignee
Nokia Technologies Oy
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 Nokia Technologies Oy filed Critical Nokia Technologies Oy
Priority to PCT/EP2016/078842 priority Critical patent/WO2018095537A1/fr
Publication of WO2018095537A1 publication Critical patent/WO2018095537A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462—LAN interconnection over a bridge based backbone
    • H04L12/4625—Single bridge functionality, e.g. connection of two networks over a single bridge
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/176—Support for shared access to files; File sharing support
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • 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/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • 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
    • 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/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • 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/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1063—Application servers providing network services
    • 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/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network

Definitions

  • the present invention relates to apparatuses, methods, systems, computer programs, computer program products and computer-readable media regarding application provisioning to mobile edge.
  • eNB E-UTRAN Node B evolved Node B, (Base station)
  • ETSI ISG MEC European Telecommunications Standards Institute Industry Specification Group Mobile Edge Computing
  • edge cloud computing One of the areas of interest of edge cloud computing is application code provisioning from main cloud to edge cloud, i.e. moving server-side application code, which e.g. is usually hosted in a hyper-scale data centre, to an edge cloud infrastructure in close proximity to the user, in order to cut down on application-level latency.
  • moving server-side application code which e.g. is usually hosted in a hyper-scale data centre
  • an edge cloud infrastructure in close proximity to the user, in order to cut down on application-level latency.
  • ETSI ISG MEC has recently approved three new work items regarding the UE application interface (cf. document [4]), the management interface (cf. document [5]), and the deployment of mobile edge computing in an NFV environment (cf. document [6]).
  • This work item specifies the Mx2 reference point. This includes requesting application instantiation, discovering applications or application instances running in the mobile edge system, triggering the relocation of applications in and out of the mobile edge system, and exchanging information regarding an ongoing application, such as getting information on application IP address change. It will describe the information flows, required information, and as applicable, will specify the necessary data model and data format.
  • the document produced will be a Group Specification (GS) that contains normative parts.
  • This work item focuses on the management of the mobile edge system, mobile edge servers and mobile edge platforms. This includes platform configuration, performance and fault management, application monitoring, remote service configuration and service control, information gathering regarding the platform features, available services, and available virtualized resources. It will describe the information flows, required information and operation, and as when applicable, will specify the necessary opendata data model, and data format and operation format.
  • the document produced will be a Group Specification that contains normative parts. Deployment of Mobile Edge Computing in an NFV environment:
  • This work item focuses on defining solutions that allow deployment of MEC in an NFV environment.
  • the work will be a study with the intent to describe such solutions, document their architectural impacts, and conclude on the necessary normative work to enable one or more selected solutions, including potential changes to the MEC architecture. It will also decide where this normative work needs to be done, e.g. MEC Architecture GS, MEC interfaces GSs, in a new normative MEC GS or in specifications of other Standards Development Organizations (SDOs), as applicable. If applicable, ETSI ISG MEC will initiate collaboration with ETSI ISG NFV and potentially other SDOs, to perform the required modifications to their respective specifications. The document produced will be an informative GS.
  • ETSI ISG NFV is standardizing network acceleration resource management functions and related interfaces (refer e.g. to the ETSI ISG NFV meeting report IFA#28 F2F Espoo (March 15-18, 2016)).
  • Different HW and/or SW versions of platforms/gateways/servers may support different levels of HW and/or SW acceleration functions and facilities, or in general different capabilities to support a given application.
  • An application working smoothly on a server in a data centre may run into difficulties when moved onto a MEC server with lesser capabilities and/or accelerator support. This may cause quality of service or quality of experience problems, or even service unavailability at the mobile edge, and/or latency problems when the application shall run on a server in the data centre instead of the MEC server, etc.
  • a data centre and a MEC server requesting an application to be moved to it from the data centre may be operated by different operators and managed by different management systems in different realms. Consequently, from the data centre's point of view the problem is how to know what to move/download, e.g. what kinds of accelerator modules if any or which features of the application, to optimize the performance of the downloaded application on the MEC server.
  • the problem can be expressed as follows: When a user/UE requests an application to be made available at a MEC server (as per the draft ETSI MEC architecture specification), how is it guaranteed that the application downloaded e.g. from a data centre is able to run in an optimized way on the MEC server.
  • ETSI GS MEC 003 Mobile-Edge Computing; Framework and reference architecture
  • a mobile edge computing server comprising:
  • a method for use in a server entity comprising:
  • an apparatus for use in a mobile edge computing server comprising:
  • At least one memory for storing instructions to be executed by the processor, wherein the at least one memory and the instructions are configured to, with the at least one processor, cause the apparatus at least to perform:
  • an apparatus for use in a server entity comprising:
  • At least one memory for storing instructions to be executed by the processor, wherein the at least one memory and the instructions are configured to, with the at least one processor, cause the apparatus at least to perform: receiving, from a mobile edge computing server, a server request for an application including application parameters and capability parameters indicating the capability of the mobile edge computing server,
  • an apparatus for use in a mobile edge computing server comprising:
  • an apparatus for use in a server entity comprising:
  • a computer program product comprising code means adapted to produce steps of any of the methods as described above when loaded into the memory of a computer.
  • a computer program product as defined above, wherein the computer program product comprises a computer-readable medium on which the software code portions are stored.
  • Fig. 1 is a block diagram illustrating an example of an operating environment to which certain aspects of the present invention are applicable.
  • Fig. 2 is a signaling diagram illustrating an example of a case where a MEC server is triggered to start an application that is currently not installed.
  • Fig. 3 is a signaling diagram illustrating an example of a case where a MEC server is triggered to start an application that is currently installed/downloaded from a data centre.
  • Fig. 4 is a flowchart illustrating an example of a method according to certain aspects of the present invention.
  • Fig. 5 is a flowchart illustrating another example of a method according to certain aspects of the present invention.
  • Fig. 6 is block diagram illustrating an example of an apparatus according to certain aspects of the present invention.
  • the basic system architecture of a communication network may comprise a commonly known architecture of one or more communication systems comprising a wired or wireless access network subsystem and a core network.
  • Such an architecture may comprise one or more communication network control elements, access network elements, radio access network elements, access service network gateways or base transceiver stations, such as a base station (BS), an access point or an eNB, which control a respective coverage area or cell and with which one or more communication elements or terminal devices such as a UE or another device having a similar function, such as a modem chipset, a chip, a module etc., which can also be part of a UE or attached as a separate element to a UE, or the like, are capable to communicate via one or more channels for transmitting several types of data.
  • BS base station
  • eNB access point or an eNB
  • core network elements such as gateway network elements, policy and charging control network elements, mobility management entities, operation and maintenance elements, and the like may be comprised.
  • the general functions and interconnections of the described elements, which also depend on the actual network type, are known to those skilled in the art and described in corresponding specifications, so that a detailed description thereof is omitted herein.
  • additional network elements and signaling links may be employed for a communication to or from a communication element or terminal device like a UE and a communication network control element like a radio network controller, besides those described in detail herein below.
  • the communication network is also able to communicate with other networks, such as a public switched telephone network or the Internet.
  • the communication network may also be able to support the usage of cloud services.
  • BSs and/or eNBs or their functionalities may be implemented by using any node, host, server or access node etc. entity suitable for such a usage.
  • the described network elements and communication devices such as terminal devices or user devices like UEs, communication network control elements of a cell, like a BS or an eNB, access network elements like APs and the like, network access control elements like AAA servers and the like, as well as corresponding functions as described herein may be implemented by software, e.g. by a computer program product for a computer, and/or by hardware.
  • nodes or network elements may comprise several means, modules, units, components, etc. (not shown) which are required for control, processing and/or communication/signaling functionality.
  • Such means, modules, units and components may comprise, for example, one or more processors or processor units including one or more processing portions for executing instructions and/or programs and/or for processing data, storage or memory units or means for storing instructions, programs and/or data, for serving as a work area of the processor or processing portion and the like (e.g. ROM, RAM, EEPROM, and the like), input or interface means for inputting data and instructions by software (e.g. floppy disc, CD-ROM, EEPROM, and the like), a user interface for providing monitor and manipulation possibilities to a user (e.g. a screen, a keyboard and the like), other interface or means for establishing links and/or connections under the control of the processor unit or portion (e.g.
  • radio interface means comprising e.g. an antenna unit or the like, means for forming a radio communication part etc.) and the like, wherein respective means forming an interface, such as a radio communication part, can be also located on a remote site (e.g. a radio head or a radio station etc.).
  • a remote site e.g. a radio head or a radio station etc.
  • ETSI ISG MEC and NFV have several new work items related to moving/downloading applications from a server / data centre to a MEC server and to functions needed to support such downloading.
  • Some example versions of the present invention describe a set of measures for optimizing the to-be-downloaded content to match the operating environment available at the target server.
  • Fig. 1 is a diagram illustrating an example of an operating environment to which some example versions of the present invention are applicable.
  • Fig. 1 shows a simplified operating environment for moving/downloading applications from a data centre to MEC servers.
  • the environment comprises a UE 10 and one or several eNBs 1 1 , which are connected to one or several MEC servers 12, respectively. Further, the one or several MEC servers 1 1 are connected to a data centre 14 via a network 13.
  • a MEC server is triggered to activate an application, e.g. by a request from a UE.
  • the MEC server does not have the required application SW, but detects the application and its own capabilities to support the application, if the application SW is downloaded to the MEC server.
  • the MEC server searches for and finds a data centre that supports the application e.g. by an internal or external enquiry, e.g. a DNS enquiry, with an application identification as a parameter.
  • the application is known and addressed (by a UE, by the MEC server, or by any entity triggering the events) by an FQDN, and the enquiry resolves, as a minimum, the required address information of a data centre/server that supports the application and the required moving/downloading.
  • the result of the enquiry may refer to more than one data centres/servers that support the application, possibly with parameters like e.g. version information, requirements for acceleration support for optimal performance, etc.
  • the MEC server collects parameters, e.g. related to HW and/or SW accelerators, that characterize its capabilities to support the application, and sends a request with the parameters to the data centre that supports the application.
  • the MEC server If the MEC server already has the application SW, the MEC server still sends a request to a data centre that supports the application, e.g. if the capabilities of the MEC server to support the application have changed or to check whether an update is available.
  • the data centre identifies the requested application and/or its version and analyses the capabilities parameters of the MEC server to determine the optimal combination and/or versions of application and/or accelerator modules to be downloaded to the MEC server.
  • the data centre receives no current version related information from MEC, but merely a request to get the application, the data centre selects the application SW version / modules that are best optimized for the characteristics of the MEC server. If current version related information is received from MEC, the data centre checks whether there is a newer version, and anyway heeds the capabilities parameters of the MEC server to determine the optimal combination of application and/or accelerator modules to be downloaded to the MEC server.
  • MEC server installs the application and/or acceleration related modules and prepares to serve the entity that triggered the start of the application.
  • Fig. 2 is a signaling diagram illustrating an example of a case where a MEC server is triggered to start an application that is currently not installed.
  • the MEC server is for example triggered by a request from a UE or the like.
  • a step 1 the UE 10 sends a request including application parameters, like for example an application identification, to the MEC server 12.
  • application parameters like for example an application identification
  • the MEC server 12 is triggered to start an application that is currently not installed, but can be supported if installed.
  • the MEC server starts an internal or external enquiry to search for and find a server/data centre that supports the application, using the identification of the application as key.
  • the response to the enquiry contains an address or contact info to at least one data centre or server, and may contain other parameters, like e.g. version information or requirements for acceleration support.
  • the MEC server collects parameters, e.g. related to HW and/or SW accelerators, that characterize its capabilities to support the application, and prepares to send a request with the parameters to the data centre that supports the application (cf. step 2 in Fig. 2).
  • parameters e.g. related to HW and/or SW accelerators, that characterize its capabilities to support the application, and prepares to send a request with the parameters to the data centre that supports the application (cf. step 2 in Fig. 2).
  • the MEC server sends a request including the application parameters and the MEC parameters to the data centre that supports the application.
  • step 4 the data entre identifies the requested application and analyzes the MEC parameters to determine the optimal combination of application and/or accelerator modules to be downloaded to the MEC server.
  • the application related modules are downloaded to the MEC server in step 5 and in step 6 the MEC server installs the application and/or acceleration related modules and prepares to serve the entity that triggered the start of the application, e.g. the UE that sent the request in step 1 .
  • step 7 the MEC server sends a response to the UE and in step 8, application level actions are performed between the UE and the MEC server.
  • Fig. 3 is a signaling diagram illustrating an example of a case where a MEC server is triggered to start an application that is currently already installed/downloaded on the MEC server (from a data centre).
  • a step 1 the UE 10 sends a request including application parameters, like for example an application identification, to the MEC server 12.
  • application parameters like for example an application identification
  • the MEC server 12 is triggered to start an application that is currently installed/downloaded from a data centre 14.
  • the MEC server 12 either has already contact info to a data centre or server (as explained with respect to Fig. 2) or starts an internal or external enquiry to search for and find a server/data centre that supports the application, using the identification of the application as key.
  • the response to the enquiry contains an address or contact info to at least one data centre or server, and may contain other parameters, like e.g. version information or requirements for acceleration support.
  • the MEC server prepares to send a request to a data centre that supports the application, e.g. if the capabilities of the MEC server to support the application have changed or to check whether an update is available (cf. step 2 in Fig. 3).
  • the MEC server sends a request including the application version number / parameters and the MEC parameters to the data centre that supports the application.
  • step 4 the data centre identifies the requested application and its version and analyzes possible MEC parameters to determine the optimal combination of application and/or accelerator modules to be downloaded to the MEC server.
  • the application related modules are downloaded to the MEC server in step 5 and in step 6 the MEC server installs the application and/or acceleration related modules and prepares to serve the entity that triggered the start of the application, e.g. the UE that sent the request in step 1 .
  • step 7 the MEC server sends a response to the UE and in step 8, application level actions are performed between the UE and the MEC server.
  • a MEC server or a MEC server environment or realm subscribes to applications supported/managed by a data centre.
  • the activation of the subscription triggers the action of moving or downloading an application from the data centre to the subscribing MEC server.
  • the activation event of the subscription then contains the accelerator related capability information of the subscribing MEC server, and the data centre uses the capability information to determine the optimal combination and/or versions of application and/or accelerator modules to be downloaded to the MEC server.
  • the subscription of an application by a MEC server from a data centre is preceded by the data centre advertising available applications to the MEC server or MEC server environment or realm.
  • the advertising contains different flavours and/or features, e.g. related to accelerator functions and possibilities, of the advertised applications, or requirements that the applications have for the (MEC server) environment to run properly.
  • the MEC server uses the information for deciding which application(s) to subscribe to and which capabilities to indicate to the data centre upon the subscription.
  • the subscription of an application by a MEC server is updated e.g. when the accelerator related capabilities of the MEC server change.
  • the data centre uses the updated capability information to select and transmit/download a more optimal combination and/or versions of application and/or accelerator modules to the MEC server.
  • the MEC server then reconfigures the acceleration functions/modules accordingly.
  • the solution according to some example versions of the present invention relates to the MEC server and data centre.
  • the core of the suggested activities takes place between them.
  • the UE triggers the start of the activities and then uses the result, i.e. the application.
  • communication between the MEC server and data centre may then take place in different ways, for example via resource management entities or network management entities of each environment, or via a common resource/network management (in an integrated environment), or via control or signaling plane entities between the environments.
  • the solution according to some example versions of the present invention is particularly applicable to moving/downloading applications in a MEC environment, combined with the accelerator management functionalities (of NFV), to optimize the performance of applications in a MEC environment.
  • the activities as a whole respond to the requirements/scopes of those, for example: UE triggering t e relocation of applications in and out of the mobile edge system; the management of the mobile edge system, mobile edge servers and mobile edge platforms. This includes platform configuration, performance and fault management, application monitoring, remote service configuration and service control, information gathering regarding the platform features, available services, and available virtualised resources;
  • Fig. 4 is a flowchart illustrating an example of a method according to some example versions of the present invention.
  • the method may be implemented in or may be part of a mobile edge computing (MEC) server, or the like.
  • the method comprises determining capability parameters indicating capabilities of the mobile edge computing server regarding a specific application in a step S41 , sending a server request including application parameters and the capability parameters to a server entity in a step S42, and downloading data and/or modules related to the specific application from the server entity in a step S43.
  • MEC mobile edge computing
  • the method further comprises determining whether the specific application exists on the mobile edge computing server, and if it is determined that the specific application does not exist, downloading the data includes downloading the specific application from the server entity, and installing the specific application and/or the modules related to the specific application on the mobile edge computing server.
  • the method further comprises determining whether the specific application exists on the mobile edge computing server, and if it is determined that the specific application already exists, determining the capability parameters includes checking whether the capability parameters have changed and/or whether an update of the specific application is available.
  • downloading the data includes downloading an update of the specific application from the server entity, and the method further comprises installing t e update of the specific application and/or the modules related to the specific application on the mobile edge computing server.
  • the method further comprises receiving, from a user equipment, a user request for the specific application including application parameters, performing a search for the server entity that supports the specific application, and sending a server request to the server entity found in the search that supports the specific application.
  • the method further comprises subscribing to a server entity, wherein the subscription includes the server request, and wherein the subscription includes identification of at least one application.
  • the method further comprises receiving an advertisement for available applications from the server entity, the advertisement including information on features related to modules and requirements of the application, and deciding which application to subscribe to and which capability parameters are to be included in the server request based on the information included in the advertisement.
  • Fig. 5 is a flowchart illustrating another example of a method according to example versions of the present invention.
  • the method may be implemented in or may be part of a data centre or server entity or the like.
  • the method comprises receiving, from a mobile edge computing server, a server request for an application including application parameters and capability parameters indicating the capability of the mobile edge computing server in a step S51 , identifying the requested application based on the application parameters in a step S52, determining data regarding the requested application and/or modules related to the requested application suitable for the mobile edge computing server based on the capability parameters in a step S53, and transmitting the data regarding the requested application and/or the modules related to the requested application to the mobile edge computing server in a step S54.
  • the method further comprises determining a suitable combination of the data regarding the application and the modules related to t e requested application based on the application parameters and the capability parameters.
  • identifying the requested application includes identifying the version of the requested application, and transmitting the data includes transmitting an update of the requested application.
  • the method further comprises advertising available applications to the mobile edge computing server, and receiving a subscription from the mobile edge computing server based on the advertisement, the subscription including the server request.
  • the capability parameters include information regarding accelerator support of the mobile edge computing server, and the modules are accelerator modules.
  • Fig. 6 is a block diagram illustrating an example of an apparatus according to some example versions of the present invention.
  • a block circuit diagram illustrating a configuration of an apparatus 60 is shown, which is configured to implement the above described aspects of the invention.
  • the apparatus 60 shown in Fig. 6 may comprise several further elements or functions besides those described herein below, which are omitted herein for the sake of simplicity as they are not essential for understanding the invention.
  • the apparatus may be also another device having a similar function, such as a chipset, a chip, a module etc., which can also be part of an apparatus or attached as a separate element to the apparatus, or the like.
  • the I/O units 62 may be a combined unit comprising communication equipment towards several network elements, or may comprise a distributed structure with a plurality of different interfaces for different network elements.
  • the apparatus 60 further comprises at least one memory 63 usable, for example, for storing data and programs to be executed by the processor 61 and/or as a working storage of the processor 61 .
  • the processor 61 is configured to execute processing related to the above described aspects.
  • the apparatus 60 may be implemented in or may be part of a mobile edge computing (MEC) server or the like, and may be configured to perform a method as described in connection with Fig. 4.
  • the processor 61 is configured to perform determining capability parameters indicating capabilities of the mobile edge computing server regarding a specific application, sending a server request including application parameters and the capability parameters to a server entity, and downloading data and/or modules related to the specific application from the server entity.
  • the apparatus 60 may be implemented in or may be part of a data centre or server entity or the like, and may be configured to perform a method as described in connection with Fig. 5.
  • the processor 61 is configured to perform receiving, from a mobile edge computing server, a server request for an application including application parameters and capability parameters indicating the capability of the mobile edge computing server, identifying the requested application based on the application parameters, determining data regarding the requested application and/or modules related to the requested application suitable for the mobile edge computing server based on the capability parameters, and transmitting the data regarding the requested application and/or the modules related to the requested application to the mobile edge computing server.
  • the apparatus (or some other means) is configured to perform some function
  • this is to be construed to be equivalent to a description stating that a (i.e. at least one) processor or corresponding circuitry, potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function.
  • a (i.e. at least one) processor or corresponding circuitry potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function.
  • function is to be construed to be equivalently implementable by specifically configured circuitry or means for performing the respective function (i.e. the expression "unit configured to” is to be construed to be equivalent to an expression such as "means for").
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the aspects/embodiments and its modification in terms of the functionality implemented;
  • CMOS Complementary MOS
  • BiMOS Bipolar MOS
  • BiCMOS Bipolar CMOS
  • ECL emitter Coupled Logic
  • TTL Transistor-Transistor Logic
  • ASIC Application Specific IC
  • FPGA Field- programmable Gate Arrays
  • CPLD Complex Programmable Logic Device
  • APU Accelerated Processor Unit
  • GPU Graphics Processor Unit
  • DSP Digital Signal Processor
  • an apparatus may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of an apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a computer program product comprising executable software code portions for execution/being run on a processor;
  • a device may be regarded as an apparatus or as an assembly of more than one apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example.
  • respective functional blocks or elements according to above- described aspects can be implemented by any known means, either in hardware and/or software, respectively, if it is only adapted to perform the described functions of the respective parts.
  • the mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device.
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the present invention.
  • Devices and means can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to a skilled person.
  • Software in the sense of the present description comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means/portions or embodied in a signal or in a chip, potentially during processing thereof.
  • a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means/portions or embodied in a signal or in a chip, potentially during processing thereof.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Stored Programmes (AREA)

Abstract

L'invention concerne des appareils, des procédés, des programmes informatiques, des produits-programmes informatiques ainsi que des supports lisibles par ordinateur se rapportant à la fourniture d'applications à un serveur périphérique mobile. Sur un serveur informatique périphérique mobile, le procédé consiste à : déterminer les paramètres de capacité indiquant les capacités du serveur informatique périphérique mobile concernant une application spécifique; envoyer une demande de serveur comprenant les paramètres d'application et les paramètres de capacité à une entité de serveur; télécharger les données et/ou les modules associés à l'application spécifique à partir de l'entité de serveur.
PCT/EP2016/078842 2016-11-25 2016-11-25 Fourniture d'applications à un serveur périphérique mobile WO2018095537A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2016/078842 WO2018095537A1 (fr) 2016-11-25 2016-11-25 Fourniture d'applications à un serveur périphérique mobile

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2016/078842 WO2018095537A1 (fr) 2016-11-25 2016-11-25 Fourniture d'applications à un serveur périphérique mobile

Publications (1)

Publication Number Publication Date
WO2018095537A1 true WO2018095537A1 (fr) 2018-05-31

Family

ID=57406235

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2016/078842 WO2018095537A1 (fr) 2016-11-25 2016-11-25 Fourniture d'applications à un serveur périphérique mobile

Country Status (1)

Country Link
WO (1) WO2018095537A1 (fr)

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109617865A (zh) * 2018-11-29 2019-04-12 中国电子科技集团公司第三十研究所 一种基于移动边缘计算的网络安全监测与防御方法
CN110069341A (zh) * 2019-04-10 2019-07-30 中国科学技术大学 边缘计算中结合功能按需配置的有依赖关系任务的调度方法
CN110809167A (zh) * 2018-08-06 2020-02-18 中国移动通信有限公司研究院 一种视频播放方法、装置、电子设备及存储介质
CN111225016A (zh) * 2018-11-23 2020-06-02 财团法人工业技术研究院 网络服务系统及网络服务方法
CN111338807A (zh) * 2020-05-21 2020-06-26 中国人民解放军国防科技大学 一种面向边缘人工智能应用的QoE感知的服务增强方法
WO2020138605A1 (fr) * 2018-12-28 2020-07-02 연세대학교 산학협력단 Procédé d'attribution de ressources de fonction de réseau virtualisée basée grappe reflétant des caractéristiques d'utilisateur
US10990372B2 (en) 2018-09-20 2021-04-27 Microsoft Technology Licensing, Llc Updating an edge computing device
WO2021188628A1 (fr) * 2020-03-17 2021-09-23 Ofinno, Llc Gestion de session pour un délestage de traitement
CN113542330A (zh) * 2020-04-21 2021-10-22 中移(上海)信息通信科技有限公司 移动边缘计算数据获取方法及系统
CN113661479A (zh) * 2019-04-17 2021-11-16 索尼集团公司 移动边缘计算服务器的电力管理
FR3110805A1 (fr) * 2020-05-25 2021-11-26 Psa Automobiles Sa Procédé et système de communication dans un réseau cellulaire sans fil
CN113747436A (zh) * 2020-05-14 2021-12-03 华为技术有限公司 通信系统、服务器、通信方法和装置
US11405449B1 (en) 2021-10-01 2022-08-02 International Business Machines Corporation Optimizing response time by load sharing in edge computing

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2369796A1 (fr) * 2010-03-26 2011-09-28 France Telecom Procédé pour autoriser la messagerie avec une police personnalisée et dispositifs correspondants
US20140223423A1 (en) * 2013-02-05 2014-08-07 Apple Inc. Automatic Updating of Applications
CN104346192A (zh) * 2013-08-09 2015-02-11 聚游互动（北京）科技发展有限公司 一种移动应用的下载方法及系统
WO2016134772A1 (fr) * 2015-02-26 2016-09-01 Nokia Solutions And Networks Oy Facturation et commande de services périphériques

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2369796A1 (fr) * 2010-03-26 2011-09-28 France Telecom Procédé pour autoriser la messagerie avec une police personnalisée et dispositifs correspondants
US20140223423A1 (en) * 2013-02-05 2014-08-07 Apple Inc. Automatic Updating of Applications
CN104346192A (zh) * 2013-08-09 2015-02-11 聚游互动（北京）科技发展有限公司 一种移动应用的下载方法及系统
WO2016134772A1 (fr) * 2015-02-26 2016-09-01 Nokia Solutions And Networks Oy Facturation et commande de services périphériques

Cited By (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110809167B (zh) * 2018-08-06 2022-06-03 中国移动通信有限公司研究院 一种视频播放方法、装置、电子设备及存储介质
CN110809167A (zh) * 2018-08-06 2020-02-18 中国移动通信有限公司研究院 一种视频播放方法、装置、电子设备及存储介质
US10990372B2 (en) 2018-09-20 2021-04-27 Microsoft Technology Licensing, Llc Updating an edge computing device
CN111225016A (zh) * 2018-11-23 2020-06-02 财团法人工业技术研究院 网络服务系统及网络服务方法
CN111225016B (zh) * 2018-11-23 2022-05-03 财团法人工业技术研究院 网络服务系统及网络服务方法
CN109617865B (zh) * 2018-11-29 2021-04-13 中国电子科技集团公司第三十研究所 一种基于移动边缘计算的网络安全监测与防御方法
CN109617865A (zh) * 2018-11-29 2019-04-12 中国电子科技集团公司第三十研究所 一种基于移动边缘计算的网络安全监测与防御方法
WO2020138605A1 (fr) * 2018-12-28 2020-07-02 연세대학교 산학협력단 Procédé d'attribution de ressources de fonction de réseau virtualisée basée grappe reflétant des caractéristiques d'utilisateur
CN110069341A (zh) * 2019-04-10 2019-07-30 中国科学技术大学 边缘计算中结合功能按需配置的有依赖关系任务的调度方法
CN110069341B (zh) * 2019-04-10 2022-09-06 中国科学技术大学 边缘计算中结合功能按需配置的有依赖关系任务的调度方法
CN113661479A (zh) * 2019-04-17 2021-11-16 索尼集团公司 移动边缘计算服务器的电力管理
WO2021188628A1 (fr) * 2020-03-17 2021-09-23 Ofinno, Llc Gestion de session pour un délestage de traitement
CN113542330A (zh) * 2020-04-21 2021-10-22 中移(上海)信息通信科技有限公司 移动边缘计算数据获取方法及系统
CN113542330B (zh) * 2020-04-21 2023-10-27 中移(上海)信息通信科技有限公司 移动边缘计算数据获取方法及系统
CN113747436A (zh) * 2020-05-14 2021-12-03 华为技术有限公司 通信系统、服务器、通信方法和装置
CN113747436B (zh) * 2020-05-14 2022-09-23 华为技术有限公司 通信系统、服务器、通信方法和装置
CN111338807A (zh) * 2020-05-21 2020-06-26 中国人民解放军国防科技大学 一种面向边缘人工智能应用的QoE感知的服务增强方法
CN111338807B (zh) * 2020-05-21 2020-08-14 中国人民解放军国防科技大学 一种面向边缘人工智能应用的QoE感知的服务增强方法
WO2021240082A1 (fr) * 2020-05-25 2021-12-02 Psa Automobiles Sa Procédé et système de communication dans un réseau cellulaire sans fil
FR3110805A1 (fr) * 2020-05-25 2021-11-26 Psa Automobiles Sa Procédé et système de communication dans un réseau cellulaire sans fil
US11405449B1 (en) 2021-10-01 2022-08-02 International Business Machines Corporation Optimizing response time by load sharing in edge computing

Similar Documents

Publication Publication Date Title
WO2018095537A1 (fr) Fourniture d'applications à un serveur périphérique mobile
EP2955631B1 (fr) Commande de fonctions de réseau virtualisées à usage dans un réseau de communication
US20210377111A1 (en) Intent Processing Method, Apparatus, and System
US10230573B2 (en) Management of network entity selection
US20180191569A1 (en) Controlling of communication network comprising virtualized network functions
EP3592012B1 (fr) Procédé, dispositif et système de mise à jour d'abonnement
KR102626273B1 (ko) 네트워크 이상 검출
EP3520444B1 (fr) Amélioration de la détection et de l'acheminement du trafic dans un environnement virtualisé
US20170093749A1 (en) Controlling of communication network comprising virtualized network functions
US10846128B2 (en) Managing the graceful termination of a virtualized network function instance
US10674349B2 (en) Subscription update method, device, and system
US20240193021A1 (en) Platform independent application programming interface configuration
US20180234288A1 (en) Automatic symptom data collection in cloud deployment
EP3326406B1 (fr) Commande de fonction d'accélération dans un réseau
US20190116256A1 (en) Hybrid application launcher for mobile devices
WO2014202151A1 (fr) Sélection de machines virtuelles ou d'entités de réseau virtualisé
US11382150B2 (en) System and method of managing PNF connectivity in a network slice instance
US20220030508A1 (en) Apparatus, method, and computer program
EP3955542A1 (fr) Améliorations pour la mise à jour sécurisée dans des réseaux de communication
CN113824789B (zh) 一种通路描述符的配置方法、装置、设备及存储介质
EP4075762A1 (fr) Informatique périphérique
US20240147268A1 (en) "real feel" autonomous network test solution system, method, device, and program
CN115243291A (zh) 数据处理方法、装置、设备以及计算机存储介质
KR20230162805A (ko) 5g 미디어 스트리밍 아키텍처에서의 새로운 에지 서버들의 이벤트-중심 프로비저닝

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: 16801766

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16801766

Country of ref document: EP

Kind code of ref document: A1