WO2016154785A1 - 一种云平台、运行应用的方法及接入网单元 - Google Patents

一种云平台、运行应用的方法及接入网单元 Download PDF

Info

Publication number
WO2016154785A1
WO2016154785A1 PCT/CN2015/075200 CN2015075200W WO2016154785A1 WO 2016154785 A1 WO2016154785 A1 WO 2016154785A1 CN 2015075200 W CN2015075200 W CN 2015075200W WO 2016154785 A1 WO2016154785 A1 WO 2016154785A1
Authority
WO
WIPO (PCT)
Prior art keywords
network unit
capability
terminal
server
unit
Prior art date
Application number
PCT/CN2015/075200
Other languages
English (en)
French (fr)
Inventor
张晟
桂亦慧
饶超
田春长
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201580077704.1A priority Critical patent/CN107409436B/zh
Priority to PCT/CN2015/075200 priority patent/WO2016154785A1/zh
Publication of WO2016154785A1 publication Critical patent/WO2016154785A1/zh
Priority to US15/716,816 priority patent/US10481921B2/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
    • G06F9/4856—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
    • 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
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45562—Creating, deleting, cloning virtual machine instances
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45575—Starting, stopping, suspending or resuming virtual machine instances

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a cloud platform, a method for running an application, and an access network unit.
  • Cloud services can provide dynamic and easily expandable and virtualized resources to users through the Internet.
  • the core idea is to manage and schedule a large number of computing resources connected by network to form a computing resource pool to provide services to users on demand.
  • the network that provides the resources is called the "cloud.”
  • the resources in the "cloud” can be expanded infinitely by users, and can be obtained at any time, used as needed, expanded at any time, and paid for by usage.
  • At its core is virtualization technology.
  • SaaS Software-as-a-Service
  • PaaS Platform-as-a-Service
  • SaaS Infrastructure as a Service
  • SaaS is a model for providing software over a network. Instead of purchasing software, users rent Web-based software from providers to manage business operations. Many of the emerging Internet services represented by the Over The Top (OTT) service through the Internet serve the users through the SaaS model. At this time, the operators become pure transmission channels and cannot be profitable.
  • OTT Over The Top
  • PaaS actually refers to the platform for software development as a service, submitted to users in the SaaS model. Therefore, PaaS is also an application of the SaaS model.
  • the PaaS service model is the soul of today's cloud computing industry, delivered as a service with operating and platform capabilities.
  • the developer hosts the application on the platform, which in turn provides the service to the user.
  • This service model between users and developers is the most suitable for operators.
  • the IaaS service model encapsulates the underlying hardware resources and delivers them as services.
  • the service objects are application developers and a small number of advanced users. This service delivery model is highly versatile and flexible. However, the number of users is small and the unit price is relatively expensive. For operators, it is unattractive and has limited profit margins.
  • the technical problem to be solved by the embodiments of the present invention is to provide a cloud platform, a method for running an application, and an access network unit.
  • a cloud platform a method for running an application
  • an access network unit a method for running an application
  • the first aspect of the embodiments of the present invention provides a cloud platform, including:
  • the core network unit is configured to distribute the application and the lightweight server to the access network unit;
  • the access network unit is configured to virtualize the terminal, migrate the computing task of the terminal to a virtual user terminal in the virtual machine, and virtualize the lightweight server, and the lightweight The network service capability of the server is migrated to the access network unit such that the virtual user terminal runs an application distributed by the core network unit.
  • the Internet unit is further configured to send the capability requirement information of the developer to the core network unit;
  • the core network unit is further configured to perform capability extraction and encapsulation on the network element corresponding to the capability requirement information to provide a call.
  • the Internet unit is further configured to receive capability requirement information of the developer, develop its own capability, and store the new capability into the application program interface set of the Internet unit, The supply is called locally or remotely.
  • the core network unit is further configured to remotely control a capability engine in the access network unit according to an instruction of an administrator, and add or modify the access network.
  • the hardware and software capabilities of the unit and join the application interface of the access network unit for the virtual user terminal or the lightweight server to invoke.
  • the Internet unit is further configured to test and deploy the developed application and application server.
  • the Internet unit is further configured to distribute the developed application to the core network unit;
  • the core network unit is further configured to distribute a lightweight server corresponding to the application to the access network unit;
  • the access network unit is further configured to deploy the lightweight server in a local virtualization environment to provide services to the virtual user terminal.
  • the core network unit is further configured to receive a distribution instruction sent by an administrator, and distribute the installation package of the application to the In the virtualized environment of the access network unit;
  • the access network unit is further configured to install the application to the virtual user terminal.
  • the lightweight server located in the access network unit has the capability of serving the virtual user terminal
  • the access network unit is configured to connect the terminal with the virtualized user terminal, and send a request to the lightweight server according to the requirement of the terminal, and invoke the local application by using local capability.
  • the access network unit is configured to send, by the core network unit, a virtual machine server in the Internet unit And requesting, by the lightweight server, a service result returned after the virtual machine server invokes the capability application interface of the Internet unit to meet the requirement of the terminal.
  • the core network unit is further configured to virtualize the terminal and the lightweight server.
  • a second aspect of the embodiments of the present invention provides a method for running an application, including:
  • the application and the lightweight server are developed by the Internet unit and distributed to the core network unit;
  • Virtualize the terminal and migrate the computing tasks of the terminal to virtual users in the virtual machine The terminal executes, and virtualizes the lightweight server, and migrates the network service capability of the lightweight server to an access network unit, so that the virtual user terminal runs an application distributed by the core network unit.
  • the lightweight server located in the access network unit has the capability of serving the virtual user terminal, when the user uses the terminal, the terminal and the terminal are used. Virtualizing the user terminal connection, and sending a request to the lightweight server according to the requirement of the terminal, using a local capability to invoke a local application interface to provide a service, or communicating with the core network unit to invoke the core network unit capability
  • the capabilities in the pool serve the lightweight server to meet the needs of the terminal;
  • the lightweight server located in the access network unit does not have the capability to serve the virtual user terminal, send a request to the virtual machine server in the Internet unit through the core network unit, through the lightweight server Receiving a service result returned by the virtual machine server after calling the capability application interface of the Internet unit to satisfy the requirement of the terminal.
  • a third aspect of the embodiments of the present invention provides an access network unit, including:
  • a receiving module configured to receive an application distributed by the core network unit and a lightweight server, where the application and the lightweight server are developed by the Internet unit and distributed to the core network unit;
  • the terminal is virtualized, and the computing task of the terminal is migrated to a virtual user terminal in the virtual machine for execution, and the lightweight server is virtualized, and the network service capability of the lightweight server is Migrating to an access network unit for the virtual user terminal to run an application distributed by the core network unit.
  • the method includes:
  • the virtualization module is further configured to connect the terminal to the virtualized user terminal when the user uses the terminal. And sending a request to the lightweight server according to the requirement of the terminal, using a local capability to invoke a local application program interface to provide a service, or communicating with the core network unit, and calling the capability in the core network unit capability pool as a location Describe a lightweight server service to meet the needs of the terminal;
  • the virtualization module is further configured to use the core network unit to virtualize the Internet unit
  • the virtual machine sends a request, and the service result returned by the virtual machine server after calling the capability application interface of the Internet unit is received by the lightweight server to meet the requirement of the terminal.
  • a fourth aspect of the embodiments of the present invention provides an access network unit, including:
  • the application and the lightweight server are developed by the Internet unit and distributed to the core network unit;
  • the network unit causes the virtual user terminal to run an application distributed by the core network unit.
  • the processor further uses Connecting the terminal to the virtualized user terminal, and sending a request to the lightweight server according to the requirement of the terminal, using a local capability to invoke a local application program interface to provide a service, or communicating with the core network unit, Invoking an ability in the core network unit capability pool to serve the lightweight server to meet the requirements of the terminal;
  • the processor is further configured to send a request to the virtual machine server in the Internet unit by using the core network unit. Receiving, by the lightweight server, a service result returned by the virtual machine server after calling the capability application interface of the Internet unit to meet the requirement of the terminal.
  • the access network unit can provide VUE and Lite Server, maximally utilize the network capabilities of the operator, and enable ASP to provide better service to users while avoiding operators.
  • the network brings unnecessary burdens; at the same time, it can reduce the cost of the operator developing cloud products, improve the user experience, and improve the service promotion effect of the operators; the capability engine on the access network unit, the telecommunications of the access network unit Ability to deliver to applications on the platform while Utilize the location characteristics of the network edge to reduce round-trip delay and core network traffic, maximize the use of positioning capabilities, and increase profitability.
  • FIG. 1 is a schematic diagram of the composition of an embodiment of a cloud platform of the present invention.
  • FIG. 2 is a schematic diagram of a first specific architecture of the cloud platform shown in FIG. 1;
  • FIG. 3 is a schematic diagram of a specific architecture of an Internet unit in the cloud platform shown in FIG. 2;
  • FIG. 4 is a schematic diagram of a specific architecture of a core network unit in the cloud platform shown in FIG. 2;
  • FIG. 5 is a schematic diagram of a specific architecture of an access network unit in the cloud platform shown in FIG. 2;
  • FIG. 6 is a timing logic diagram of the cloud platform capability development phase shown in FIG. 2;
  • FIG. 7 is a timing logic diagram of cloud platform application development/deployment shown in FIG. 2;
  • FIG. 8 is a timing logic diagram when the cloud platform shown in FIG. 2 is used.
  • FIG. 9 is a schematic diagram of a second specific architecture of the cloud platform shown in FIG. 1;
  • FIG. 10 is a timing logic diagram of the cloud platform capability development phase shown in FIG. 9;
  • FIG. 11 is a timing logic diagram of cloud platform application development/deployment shown in FIG. 9;
  • FIG. 12 is a timing logic diagram when the cloud platform shown in FIG. 9 is used.
  • FIG. 13 is a schematic diagram of a third specific architecture of the cloud platform shown in FIG. 1;
  • FIG. 14 is a schematic diagram of a specific architecture of a core network unit in the cloud platform shown in FIG. 13;
  • FIG. 15 is a timing logic diagram of the cloud platform application development/deployment shown in FIG. 13;
  • FIG. 16 is a timing logic diagram when the cloud platform shown in FIG. 13 is used.
  • 17 is a schematic flow chart of a method for running an application according to an embodiment of the present invention.
  • FIG. 18 is a schematic diagram showing the composition of a first embodiment of an access network unit according to the present invention.
  • Figure 19 is a block diagram showing the composition of a second embodiment of the access network unit of the present invention.
  • the cloud platform includes:
  • the Internet unit 10 is configured to distribute an application developed by an application service provider and a lightweight server to the core network unit 20;
  • the core network unit 20 is configured to distribute the application and the lightweight server to the access network unit 30;
  • the access network unit 30 is configured to virtualize the terminal, migrate the computing task of the terminal to a virtual user terminal in the virtual machine, and virtualize the lightweight server, and the The network server capabilities of the volume server are migrated to the access network unit such that the virtual user terminal runs an application distributed by the core network unit.
  • the Internet unit 10 is further configured to send the developer's capability requirement information to the core network unit 20;
  • the core network unit 20 is further configured to perform capability extraction and encapsulation on the network element corresponding to the capability requirement information to supply a call.
  • the internet unit 10 is further configured to receive the developer's capability requirement information, develop its own capabilities, and store the new capabilities into the application interface set of the internet unit 10, the supply being invoked locally or remotely.
  • the core network unit 20 is further configured to remotely control the capability engine in the access network unit 30 according to an instruction of an administrator, add or modify the software and hardware capabilities of the access network unit 30, and join the The application interface of the access network unit 30 is invoked by the virtual user terminal or the lightweight server.
  • the Internet unit 10 is also used to test and deploy the developed application and application server during application development.
  • the internet unit 10 can distribute the application.
  • the Internet unit 10 is further configured to distribute the developed application to the core network unit 20;
  • the core network unit 20 is further configured to distribute the lightweight server corresponding to the application to the access network unit 30;
  • the access network unit 30 is further configured to deploy the lightweight server in a local virtualization environment to provide services to the virtual user terminal.
  • the core network unit 20 is further configured to receive a distribution instruction sent by an administrator, and distribute the installation package of the application to a virtualization environment of the access network unit 30;
  • the access network unit 30 is further configured to install the application to the virtual user terminal.
  • the terminal can be served according to the lightweight server capabilities on the access network unit 30.
  • the access network unit 30 is configured to use the terminal and the virtualized user when the user uses the terminal.
  • the terminal is connected, and sends a request to the lightweight server according to the requirement of the terminal, uses a local capability to invoke a local application program interface to provide a service, or communicates with the core network unit 20 to invoke the core network unit 20 in a capability pool.
  • the access network unit 30 is configured to use the core network unit to virtualize the Internet unit 10
  • the server sends a request, and the service result returned by the virtual machine server after calling the capability application interface of the Internet unit 10 is received by the lightweight server to satisfy the requirement of the terminal.
  • the capability of the virtualization environment may also be built in the core network unit 20, that is, the core network unit 20 is further configured to virtualize the terminal and the lightweight server.
  • the conventional platform is compared with the cloud platform of the embodiment of the present invention.
  • Hardware capabilities provided by servers in the Internet, including computing power, storage capabilities, etc.;
  • the APP itself obtains the rough location of the UE, and the power consumption is large for a long time;
  • Air interface capability the channel is only passively occupied
  • Hardware capability provided by the IaaS at the bottom of the access network unit, including computing power, storage capacity, etc., which are widely distributed from users;
  • the access network unit can accurately locate users, which is more practical and energy efficient;
  • Air interface capability Operators can provide better air interface services, such as dedicated push channels and fast transmission channels, and a large number of underlying capabilities to be developed.
  • the operator provides the user with information that does not involve personal privacy, such as monthly spending power, personalized features, etc., as an ability to be provided to the ASP for accurate delivery of advertisements;
  • the aggregation platform has a wealth of telecommunications capabilities, which can be deeply customized for different customer needs; install the APP in one-click to all users' terminals:
  • Advertising push Push the latest APP in the form of MMS, notification bar, banner, etc.
  • Contract machine The user provides a cheap terminal when purchasing the machine, and agrees to accept the APP push regularly;
  • Paid APP Redeem traffic, points, gifts, etc. by accepting the installation app.
  • APP trial Provide a public VUE pre-installed with the APP to be promoted, the user can switch to this VUE, and then choose to install after free trial, excluding the user from knowing enough about the APP or the trouble;
  • Operators occupy a more favorable position in the battle of mobile Internet, reducing the need to deal with OTT challenges The cost of getting out of the "pipeline" role.
  • operators can also use the cloud platform of this implementation to obtain a new profit model.
  • the cloud platform realizes true cloud storage, and different devices of the user share the same application data and personal data, and information security is guaranteed.
  • the localization service platform provides a basic platform for mobile Internet segmentation service innovation.
  • the cloud platform includes:
  • the Internet unit can be set in the base station.
  • the access network unit is the core unit that realizes many beneficial effects of the cloud platform.
  • the Internet unit is the entrance of the administrator and the ASP directly interacting with the platform.
  • the core network unit is located between the former two, playing the role of intermediary and more comprehensive function support.
  • the cloud platform described in this embodiment is described in detail below with reference to FIG. 3 to FIG. 8.
  • FIG. 3 is a schematic diagram of a specific architecture of an Internet unit in the cloud platform shown in FIG. 2 .
  • FIG. 3 is a schematic diagram of a specific architecture of an Internet unit in the cloud platform shown in FIG. 2 .
  • this embodiment
  • the cloud platform is a standard "cloud computing" application on the Internet side. From top to bottom, SaaS, PaaS and IaaS three-tier logical structure.
  • the top-level SaaS includes the platform's own support and management system, providing all the functions of the platform through the front-end administrator view and user view.
  • SaaS is built on top of PaaS. Whether it is a sub-application of the system itself or a user's web application, it is treated as a web application (Web APP).
  • the middle PaaS contains the complete development environment, test environment, network simulation environment, and required APIs. After development and testing, distribution is done through the App Distributor module, and a lightweight server (Lite Server) is published in the access network unit.
  • Lite Server lightweight server
  • the underlying IaaS serves the upper PaaS.
  • FIG. 4 is a schematic diagram of a specific architecture of a core network unit in the cloud platform shown in FIG. 2 .
  • FIG. 4 is a schematic diagram of a specific architecture of a core network unit in the cloud platform shown in FIG. 2 .
  • this embodiment
  • the core network unit is divided into three logical levels: the support layer, the capability abstraction layer and the service layer.
  • the top-level support layer consists of two parts: the management module in the first part is responsible for managing the unit, including the administrator to maintain the full functionality of the module; the capability module provides all the capability-related functions and interacts with the underlying capability engine; monitoring The module is used to monitor the operation of all modules at each layer in real time; the distribution module is responsible for distributing the Lite Server to the access network unit.
  • the second part provides a gateway and billing module that communicates with the access network unit at this level.
  • the middle capability layer contains the capability pool, the capability engine for adding, deleting, and modifying it, and the capability interface provided to the application call.
  • the underlying service layer abstracts multiple network elements, and uses the Service Master module to extract different services and capabilities, and encapsulates them into a capability pool. Data centers are externally represented as data-related capabilities.
  • FIG. 5 it is a schematic diagram of a specific architecture of an access network unit in the cloud platform shown in FIG. 2, in this embodiment,
  • the access network unit is divided into four logical levels: application layer, platform layer, infrastructure layer and hardware layer.
  • the top-level application layer contains two views. User view is presented directly to the end user, by mobile
  • the MaaIO service model in virtualization provides services.
  • the developer view is for APP developers, and the Lite Server is supported by the platform layer.
  • the platform layer includes a full set of PaaS platforms and sub-modules that support the platform.
  • the capability engine encapsulates different capabilities and services into APIs for upper layer calls according to requirements; the remote communication module interacts with the distribution module and the capability gateway in the core network unit, and completes the deployment task of the Lite Server together with the Lite Server Manager module, and provides the core The call of the network capability.
  • the infrastructure layer includes the IaaS platform that serves the PaaS platform and sub-modules that support the platform.
  • the Service Master module extracts and encapsulates the underlying hardware and network capabilities and provides them to the capability engine for management.
  • the underlying hardware layer contains the original network devices in the access network unit, as well as the newly added general server cluster and storage devices, providing comprehensive hardware support to the upper layer.
  • FIG. 6 is a timing logic diagram of the cloud platform capability development phase shown in FIG. 2 .
  • the application service uses the telecommunications network capability through an aggregated cloud platform across the telecommunication network and the Internet. Therefore, the development of capabilities is an important stage of the present invention.
  • the first is the development of capabilities initiated by developers.
  • Process 1 The developer initiates the process by operating on the PaaS portal of the Internet unit;
  • the administrator After the administrator receives the new requirements of the developer's ability on the PaaS portal, the administrator uses the administrator authority to operate the core module of the core network unit;
  • the capability module invokes the capability engine of the lower layer.
  • the capability engine extracts and encapsulates the network elements such as the Home Subscriber Server (HSS) into the capability pool for the upper application to invoke;
  • HSS Home Subscriber Server
  • the module is used to add new capabilities to the API collection of the Internet unit, and the application is called locally/remotely.
  • Process 2 A capability development process initiated by an administrator that applies to the capabilities of the access network unit Development and management.
  • the administrator utilizes the capability module in the core network unit to remotely control the capability engine of the access network unit;
  • VUE virtual user equipment
  • Lite Server Add or modify the underlying software and hardware capabilities of the access network unit, and then add the API set to the local virtual user terminal (virtual user equipment, VUE for short) or Lite Server.
  • VUE virtual user equipment
  • FIG. 7 is a timing logic diagram of the cloud platform application development/deployment shown in FIG. 2 .
  • the cloud platform essentially adopts the cloud computing service model of PaaS.
  • PaaS cloud computing service model
  • the first is the development and deployment of APP initiated by developers.
  • Process 1 The developer initiates the process by operating on the PaaS portal of the Internet;
  • the developer develops the app through the online development environment with the cooperation of the PaaS App Master module;
  • the simulation environment can be used in conjunction with the test environment or can be used separately.
  • the purpose is to provide developers with an online simulation environment with various hardware configurations and software environments, so that developers can deploy the APP or APP Server without formal deployment.
  • Local simulated deployment scenario
  • the development, test, and simulation environments all use virtual machines in the Internet unit with the PaaS App Master.
  • the administrator approves and deploys the APP Server and the Lite Server respectively;
  • the APP server is deployed in the virtual machine (Virtual Machine, VM for short) of the Internet unit to connect and provide services to the APP;
  • virtual machine Virtual Machine, VM for short
  • the distribution module establishes a connection with the remote communication module of the access network unit, and sends the Lite Server to one or more access network units;
  • the corresponding Lite Server is deployed in the virtualized environment of the access network unit to provide close-range services to the VUE.
  • Procedure 2 The APP deployment process initiated by the administrator is applicable to the scenario in which the operator promotes the APP.
  • the administrator uses the distribution module in the core network unit to directly distribute the installation package of the APP to a virtualized environment in some access network units;
  • the APP is installed by the access network unit into the designated VUE.
  • the distribution module can deploy Lite Server to the access network unit, or deploy the APP directly to the VUE, and distribute value-added content such as advertisements.
  • FIG. 8 is a timing logic diagram when the cloud platform shown in FIG. 2 is used; in this embodiment, there are two processes in the use phase.
  • the Lite Server local to the access network unit has the ability to provide services to the VUE.
  • the user uses the UE, and the UE establishes a connection with the VUE in the access network unit.
  • the VUE sends a request to the Lite Server according to the requirements.
  • the Lite Server has two possibilities at this time, namely calling the local API and using the capabilities in the core network.
  • the Lite Server needs to use local capabilities, such as dedicated channel, location and storage.
  • the unit After the unit performs billing, it calls the API to provide the service.
  • the access network unit communicates with the capability interface of the core network unit, and after the charging module takes effect, the capability in the local capability pool is invoked to provide services to the Lite Server.
  • Procedure 2 The local Lite Server cannot provide a complete service due to functional logic. In this case, a request needs to be sent to the server in the VM in the Internet unit. After the capability API in the Internet is called by the server, the service result is sent back to the Lite Server, and finally the VUE is served.
  • the three functional units of the cloud platform are respectively deployed in the base station, the core network, and the Internet, and can integrate various capabilities in the carrier telecommunication network, and have all the advantages of the existing PaaS platform. It can also provide operators with the advantage of one-click distribution of APP, turning existing network users into users of application services.
  • the cloud platform relies on the VUE and Lite Server provided by the mobile virtualization technology at the access network unit to maximize the utilization of the carrier's network capabilities, so that ASP can provide better services to users while avoiding operators.
  • the network brings unnecessary burdens.
  • the capability engine on the access network unit Provide the telecom capability of the access network unit to the application on the platform, and utilize the location characteristics of the network edge to reduce round-trip time (RTT) and core network traffic, and maximize the use of positioning capability. Increase profit margins.
  • the present invention provides a full set of development, testing, simulation and deployment environments, which greatly saves the cost of ASP development APP, improves development efficiency, and enriches the functions of the APP.
  • FIG. 9 is a schematic diagram of a second specific architecture of the cloud platform shown in FIG. 1 .
  • FIG. 9 is a schematic diagram of a second specific architecture of the cloud platform shown in FIG. 1 .
  • this embodiment
  • the cloud platform is divided into an Internet unit, a core network unit, and an access network unit, wherein the access network unit can be set in the base station.
  • the access network unit is the core unit that realizes many beneficial effects of the cloud platform of the present implementation.
  • the Internet unit is the entrance of the administrator and the ASP directly interacting with the platform, and the core network unit is located between the former two, playing the role of an intermediary and more comprehensive. Functional support, the Internet unit in this embodiment only retains two main functional modules of the PaaS portal and App Distributor, and an interactive interface with the external Internet application of the cloud platform, compared with the Internet unit shown in FIG. 4.
  • the entire Internet unit has become a cloud computing product with a SaaS service model. It does not provide a public development and operating environment and does not provide a unified platform.
  • ASP can distribute its own developed Lite Server to the access network unit through the App Distributor module through the core network unit and deploy it.
  • the virtualized environment for deploying the server is no longer provided in the Internet unit.
  • the communication between the Lite Server and the Server is provided by the capability interface.
  • the Internet capabilities required by the PaaS portal and supporting the management subsystem are also provided by the capability interface.
  • the remaining core network elements and access network elements are the same as the cloud platform shown in FIG. For the timing logic of the cloud platform in each stage in this embodiment, a detailed description will be given below with reference to FIGS. 13-15.
  • FIG. 10 is a timing logic diagram of the cloud platform capability development phase shown in FIG. 9; in this embodiment,
  • the capability development process initiated by the administrator is the same as the process 2 in the first embodiment.
  • FIG. 11 is a timing logic diagram of the cloud platform application development/deployment shown in FIG. 9 .
  • FIG. 11 is a timing logic diagram of the cloud platform application development/deployment shown in FIG. 9 .
  • FIG. 11 is a timing logic diagram of the cloud platform application development/deployment shown in FIG. 9 .
  • the first is the deployment of the Lite Server initiated by the developer.
  • the difference from the embodiment of FIG. 7 is that the embodiment of FIG. 7 has the entire process of developing an APP, an APP server, and a Lite Server, and the deployment process. In this embodiment, only the deployment and distribution process of the APP and the Lite Server are performed.
  • FIG. 12 is a timing logic diagram when the cloud platform shown in FIG. 9 is used; in this embodiment,
  • Process 1 is the same as Process 1 of Embodiment 1 shown in FIG.
  • Process 2 is that the local Lite Server cannot provide a complete service due to functional logic limitation. In this case, a request needs to be sent to the server. After the access network unit establishes a connection with the Internet unit, after accessing the server of the application through the capability interface, the service result is sent back to the Lite Server, and finally the VUE is served.
  • the three functional units of the cloud platform are respectively deployed in the base station, the core network, and the Internet, and can integrate various capabilities in the carrier telecommunication network, and have all the advantages of the existing PaaS platform. It can also provide operators with the advantage of one-click distribution of APP, turning existing network users into users of application services.
  • the cloud platform relies on the VUE and Lite Server provided by the mobile virtualization technology at the access network unit to maximize the utilization of the carrier's network capabilities, so that ASP can provide better services to users while avoiding operators.
  • the network brings unnecessary burdens.
  • the capability engine on the access network unit provides the telecommunications capability of the access network unit to the application on the platform, and utilizes the location characteristics of the network edge to reduce RTT and core network traffic, maximizing the use of positioning capability, and increasing Profitable space.
  • FIG. 13 is a schematic diagram of a third specific architecture of the cloud platform shown in FIG. 1 .
  • FIG. 13 is a schematic diagram of a third specific architecture of the cloud platform shown in FIG. 1 .
  • this embodiment
  • the cloud platform is divided into an Internet unit, a core network unit, and an access network unit, wherein the access network unit It can be set in the base station.
  • the access network unit is the core unit that realizes many beneficial effects of the cloud platform.
  • the Internet unit is the entrance of the administrator and the ASP directly interacting with the platform.
  • the core network unit is located between the former two, playing the role of intermediary and more comprehensive function support. A detailed description will be given below with reference to FIGS. 17 to 19.
  • FIG. 14 it is a schematic diagram of a specific architecture of a core network unit in the cloud platform shown in FIG. 13; in this embodiment,
  • the core network elements of the cloud platform are divided into five logical levels: application layer, platform layer, support layer, capability abstraction layer and service layer.
  • the top-level application layer and platform layer are to transplant the corresponding layer in the access network unit to the core network unit, which is applicable to the pre-deployment phase of the cloud platform.
  • the specific structure and function are related to the access network unit in the first embodiment. Description.
  • the number of users is small, and the demand for the downward movement of the Lite Server is not so strong.
  • the same virtualized environment as the access network unit is added to the core network unit, and the virtualized environment is The tools and environment for VUE and Lite Server deployment are set up, so that the core network unit can temporarily function as an access network unit and temporarily provide corresponding beneficial effects.
  • the support layer, the capability abstraction layer, and the base service layer are the same as those described in FIG.
  • FIG. 15 is a timing logic diagram of the cloud platform application development/deployment shown in FIG. 13; in this embodiment,
  • the APP can be deployed in the access network unit or the core network unit.
  • the timing logic is the same as the embodiment shown in FIG.
  • the thicker two arrows are respectively virtualized by the distribution module to the core network unit during the APP deployment process initiated by the developer and initiated by the administrator.
  • FIG. 16 is a timing logic diagram when the cloud platform shown in FIG. 13 is used.
  • FIG. 16 is a timing logic diagram when the cloud platform shown in FIG. 13 is used.
  • the VUE can accept from The service of the Lite Server in the access network unit or core network unit.
  • the former is the same as the embodiment shown in FIG.
  • the virtualization technology is added to the core network unit, which is specifically represented by the platform layer and the application layer on the unit, and the technical effect is to maximize the utilization of the network capability of the operator, so that the ASP provides the user with the network. At the same time of better service, avoid unnecessary burden on the operator's network.
  • FIG. 17 is a schematic flowchart of a method for running an application according to an embodiment of the present invention.
  • the method includes the following steps:
  • S101 Receive an application and a lightweight server distributed by the core network unit.
  • the terminal is virtualized, and the computing task of the terminal is migrated to a virtual user terminal in the virtual machine for execution, and the lightweight server is virtualized, and the network service capability of the lightweight server is migrated to Accessing the network unit such that the virtual user terminal runs an application distributed by the core network unit.
  • the access network unit includes:
  • the receiving module 100 is configured to receive an application distributed by the core network unit and a lightweight server, where the application and the lightweight server are developed by the Internet unit and distributed to the core network unit;
  • the virtualization module 200 virtualizes the terminal, migrates the computing task of the terminal to a virtual user terminal in the virtual machine, and virtualizes the lightweight server to perform network service of the lightweight server.
  • the capability is migrated to the access network unit such that the virtual user terminal runs the application distributed by the core network unit.
  • the virtualization module 200 is further configured to: when the user uses the terminal, the virtualization module 200 Virtualizing the user terminal connection, and sending a request to the lightweight server according to the requirement of the terminal, using a local capability to call a local application program interface to provide a service, or communicating with the core network unit, Invoking an ability in the core network unit capability pool to serve the lightweight server to meet the requirements of the terminal;
  • the virtualization module 200 is further configured to use the core network unit to the virtual machine server in the Internet unit. Sending a request, and receiving, by the lightweight server, a service result returned by the virtual machine server after calling the capability application interface of the Internet unit to meet the requirement of the terminal.
  • the access network unit includes:
  • the processor 140 is configured to invoke the program code stored in the memory 130 to perform the following operations:
  • the application and the lightweight server are developed by the Internet unit and distributed to the core network unit;
  • the network unit causes the virtual user terminal to run an application distributed by the core network unit.
  • the processor 140 is further configured to use the terminal and the virtual The user terminal is connected, and sends a request to the lightweight server according to the requirement of the terminal, uses a local capability to call a local application program interface to provide a service, or communicates with the core network unit, and invokes the core network unit capability pool.
  • the lightweight server located in the access network unit has the capability of serving the virtual user terminal
  • the processor 140 is further configured to use the terminal and the virtual The user terminal is connected, and sends a request to the lightweight server according to the requirement of the terminal, uses a local capability to call a local application program interface to provide a service, or communicates with the core network unit, and invokes the core network unit capability pool.
  • the processor 140 is further configured to send, by using the core network unit, a virtual machine server in the Internet unit. Requesting, by the lightweight server, receiving the virtual machine server to invoke the mutual The service results returned by the capabilities of the networking unit after the application interface meet the requirements of the terminal.
  • the present invention has the following advantages:
  • the access network unit can provide VUE and Lite Server, maximally utilize the network capabilities of the operator, and enable ASP to provide better service to users while avoiding operators.
  • the network brings unnecessary burdens; at the same time, it can reduce the cost of the operator developing cloud products, improve the user experience, and improve the service promotion effect of the operators; the capability engine on the access network unit, the telecommunications of the access network unit Capabilities are provided to applications on the platform, while taking advantage of the location characteristics of the network edge, reducing round-trip delay and core network traffic, maximizing the use of location capabilities and increasing profitability.
  • the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed.
  • the foregoing steps include the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Abstract

本发明实施例公开了一种云平台，包括：互联网单元，用于将应用服务提供商开发的应用和轻量服务器分发至核心网单元；所述核心网单元，用于将所述应用和轻量服务器分发至接入网单元；所述接入网单元，用于将终端进行虚拟化，并将所述终端的计算任务迁移至虚拟机中的虚拟用户终端执行，以及将所述轻量服务器进行虚拟化，将所述轻量服务器的网络服务能力迁移至所述接入网单元以便所述虚拟用户终端运行所述核心网单元分发的应用。本发明实施例还公开了一种运行应用的方法及接入网单元。采用本发明，可降低运营商开发云产品的成本，提高用户体验，提升运营商的服务推广效果。

Description

一种云平台、运行应用的方法及接入网单元 技术领域
本发明涉及通信技术领域，尤其涉及一种云平台、运行应用的方法及接入网单元。
背景技术
随着通信技术及互联网技术的飞速发展，云服务正慢慢走入人们的生活和工作，云服务可通过互联网来提供动态易扩展且虚拟化的资源给用户使用。其核心思想是将大量用网络连接的计算资源统一管理和调度，构成一个计算资源池向用户按需服务。提供资源的网络被称为“云”。“云”中的资源在使用者看来是可以无限扩展的，并且可以随时获取，按需使用，随时扩展，按使用付费。其核心是虚拟化技术。根据虚拟化和提供服务的层次不同，主要分为软件即服务(Software-as-a-Service，简称IaaS)、平台即服务(Platform-as-a-Service，简称PaaS)和基础设施即服务(Infrastructure-as-a-Service，简称SaaS)。SaaS是一种通过网络提供软件的模式，用户无需购买软件，而是向提供商租用基于Web的软件，来管理企业经营活动。以通过互联网向用户提供应用服务(Over The Top，简称OTT)业务为代表的众多新兴互联网业务大多通过SaaS模型服务用户，而此时，运营商则变为单纯的传输管道，无法获利。PaaS实际上是指将软件研发的平台作为一种服务，以SaaS的模式提交给用户。因此，PaaS也是SaaS模式的一种应用。PaaS服务模型是当今云计算产业的灵魂，以运行环境和平台能力作为服务来交付。开发者将应用托管在平台上，平台再将服务提供给用户。这种位于用户和开发者之间的服务模型，是最适合运营商的。IaaS服务模型是将底层硬件资源包装后作为服务交付，其服务对象是应用开发者，以及少数高级用户。这种服务的交付模式，有很强的通用性和灵活性。但是用户数较少，单价较昂贵。对运营商来说，缺乏吸引力，盈利空间十分有限。
除了互联网应用服务提供商(Application Service Provider，简称ASP)在大力开发PaaS模型的云计算产品，几大运营商也很积极推出自己的“云”产品， 但功能较为初级，体验一般；这些云产品大多停留在SaaS模型阶段，少数进行了IaaS模型的尝试，但是从功能完备和使用人数上，都无法和ASP抗衡；且由于运营商开发云产品的基础薄弱，成本很高，提供的硬件配置较低，产品价格较高。
发明内容
本发明实施例所要解决的技术问题在于，提供一种云平台、运行应用的方法及接入网单元。以解决运营商现有云产品开发成本高，用户体验差，推广手段受限的问题。
为了解决上述技术问题，本发明实施例第一方面提供了一种云平台，包括：
互联网单元，用于将应用服务提供商开发的应用和轻量服务器分发至核心网单元；
所述核心网单元，用于将所述应用和轻量服务器分发至接入网单元；
所述接入网单元，用于将终端进行虚拟化，并将所述终端的计算任务迁移至虚拟机中的虚拟用户终端执行，以及将所述轻量服务器进行虚拟化，将所述轻量服务器的网络服务能力迁移至所述接入网单元以便所述虚拟用户终端运行所述核心网单元分发的应用。
在第一方面的第一种可能的实现方式中，所述互联网单元还用于将开发者的能力需求信息发送至所述核心网单元；
所述核心网单元还用于对所述能力需求信息对应的网元进行能力提取和封装以供应用调用。
在第一方面的第二种可能的实现方式中，所述互联网单元还用于接收开发者的能力需求信息，开发自身的能力并将新能力存储至所述互联网单元的应用程序接口集合中，供应用本地或远程调用。
在第一方面的第三种可能的实现方式中，所述核心网单元还用于根据管理员的指令，远程控制所述接入网单元中的能力引擎，新增或修改所述接入网单元的软硬件能力，并加入所述接入网单元的应用程序接口以供所述虚拟用户终端或所述轻量服务器调用。
在第一方面的第四种可能的实现方式中，所述互联网单元还用于测试并部署开发完成的应用和应用服务器。
结合第一方面的第四种可能的实现方式，在第五种可能的实现方式中，所述互联网单元还用于将开发完成的应用程序分发至所述核心网单元；
所述核心网单元还用于将与所述应用对应的轻量服务器分发至所述接入网单元；
所述接入网单元还用于在本地虚拟化环境中部署所述轻量服务器以便向所述虚拟用户终端提供服务。
结合第一方面的第四种可能的实现方式，在第六种可能的实现方式中，所述核心网单元还用于接收管理员发送的分发指令，将所述应用的安装包分发至所述接入网单元的虚拟化环境中；
所述接入网单元还用于将所述应用安装至所述虚拟用户终端。
结合第一方面的第五或第六种可能的实现方式，在第七种可能的实现方式中，若位于所述接入网单元的轻量服务器具备向所述虚拟用户终端服务的能力，则在用户使用终端时，所述接入网单元用于将所述终端与所述虚拟化用户终端连接，并根据所述终端的需求向所述轻量服务器发送请求，使用本地能力调用本地应用程序接口提供服务，或者与所述核心网单元通信，调用所述核心网单元能力池中的能力为所述轻量服务器服务以满足所述终端的需求；
若位于所述接入网单元的轻量服务器不具备向所述虚拟用户终端服务的能力，则所述接入网单元用于通过所述核心网单元向所述互联网单元中的虚拟机服务器发送请求，通过所述轻量服务器接收所述虚拟机服务器调用所述互联网单元的能力应用程序接口之后返回的服务结果以满足所述终端的需求。
在第一方面的第八种可能的实现方式中，所述核心网单元还用于对所述终端和所述轻量服务器进行虚拟化。
本发明实施例第二方面提供了一种运行应用的方法，包括：
接收核心网单元分发的应用及轻量服务器，所述应用及轻量服务器由互联网单元开发完成并分发至所述核心网单元；
将终端进行虚拟化，并将所述终端的计算任务迁移至虚拟机中的虚拟用户 终端执行，以及将所述轻量服务器进行虚拟化，将所述轻量服务器的网络服务能力迁移至接入网单元以便所述虚拟用户终端运行所述核心网单元分发的应用。
在第二方面的第一种可能的实现方式中，若位于所述接入网单元的轻量服务器具备向所述虚拟用户终端服务的能力，则在用户使用终端时，将所述终端与所述虚拟化用户终端连接，并根据所述终端的需求向所述轻量服务器发送请求，使用本地能力调用本地应用程序接口提供服务，或者与所述核心网单元通信，调用所述核心网单元能力池中的能力为所述轻量服务器服务以满足所述终端的需求；
若位于所述接入网单元的轻量服务器不具备向所述虚拟用户终端服务的能力，则通过所述核心网单元向所述互联网单元中的虚拟机服务器发送请求，通过所述轻量服务器接收所述虚拟机服务器调用所述互联网单元的能力应用程序接口之后返回的服务结果以满足所述终端的需求。
本发明实施例第三方面提供了一种接入网单元，包括：
接收模块，用于接收核心网单元分发的应用及轻量服务器，所述应用及轻量服务器由互联网单元开发完成并分发至所述核心网单元；
虚拟化模块，将终端进行虚拟化，并将所述终端的计算任务迁移至虚拟机中的虚拟用户终端执行，以及将所述轻量服务器进行虚拟化，将所述轻量服务器的网络服务能力迁移至接入网单元以便所述虚拟用户终端运行所述核心网单元分发的应用。
在第三方面的第一种可能的实现方式中，包括：
若位于所述接入网单元的轻量服务器具备向所述虚拟用户终端服务的能力，则在用户使用终端时，所述虚拟化模块还用于将所述终端与所述虚拟化用户终端连接，并根据所述终端的需求向所述轻量服务器发送请求，使用本地能力调用本地应用程序接口提供服务，或者与所述核心网单元通信，调用所述核心网单元能力池中的能力为所述轻量服务器服务以满足所述终端的需求；
若位于所述接入网单元的轻量服务器不具备向所述虚拟用户终端服务的能力，则所述虚拟化模块还用于通过所述核心网单元向所述互联网单元中的虚 拟机服务器发送请求，通过所述轻量服务器接收所述虚拟机服务器调用所述互联网单元的能力应用程序接口之后返回的服务结果以满足所述终端的需求。
本发明实施例第四方面提供了一种接入网单元，包括：
输入设备、输出设备、存储器和处理器，所述输入设备、输出设备、存储器和处理器与总线连接，其中，所述存储器中存储一组程序代码，所述处理器用于调用所述存储器中存储的程序代码，执行以下操作：
接收核心网单元分发的应用及轻量服务器，所述应用及轻量服务器由互联网单元开发完成并分发至所述核心网单元；
将终端进行虚拟化，并将所述终端的计算任务迁移至虚拟机中的虚拟用户终端执行，以及将所述轻量服务器进行虚拟化，将所述轻量服务器的网络服务能力迁移至接入网单元以便所述虚拟用户终端运行所述核心网单元分发的应用。
在第四方面的第一种可能的实现方式中，若位于所述接入网单元的轻量服务器具备向所述虚拟用户终端服务的能力，则在用户使用终端时，所述处理器还用于将所述终端与所述虚拟化用户终端连接，并根据所述终端的需求向所述轻量服务器发送请求，使用本地能力调用本地应用程序接口提供服务，或者与所述核心网单元通信，调用所述核心网单元能力池中的能力为所述轻量服务器服务以满足所述终端的需求；
若位于所述接入网单元的轻量服务器不具备向所述虚拟用户终端服务的能力，则所述处理器还用于通过所述核心网单元向所述互联网单元中的虚拟机服务器发送请求，通过所述轻量服务器接收所述虚拟机服务器调用所述互联网单元的能力应用程序接口之后返回的服务结果以满足所述终端的需求。
实施本发明实施例，具有如下有益效果：
通过在接入网单元处配置移动虚拟化技术，使得接入网单元可提供VUE和Lite Server，最大化地利用运营商的网络能力，让ASP向用户提供更加优质服务的同时，避免为运营商的网络带来不必要的负担；同时可降低运营商开发云产品的成本，提高用户体验，提升运营商的服务推广效果；接入网单元上的能力引擎，将接入网单元所具有的电信能力提供给平台之上的应用程序，同时 利用网络边缘的位置特点，减少往返时延和核心网流量，最大化利用定位能力，增加盈利空间。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明云平台实施例的组成示意图；
图2是图1所示云平台的第一种具体架构示意图；
图3是图2所示云平台中互联网单元的具体架构示意图；
图4是图2所示云平台中核心网单元的具体架构示意图；
图5是图2所示云平台中接入网单元的具体架构示意图；
图6是图2所示云平台能力开发阶段的时序逻辑图；
图7是图2所示云平台应用程序开发/部署的时序逻辑图；
图8是图2所示云平台使用时的时序逻辑图；
图9是图1所示云平台的第二种具体架构示意图；
图10是图9所示云平台能力开发阶段的时序逻辑图；
图11是图9所示云平台应用程序开发/部署的时序逻辑图；
图12是图9所示云平台使用时的时序逻辑图；
图13是图1所示云平台的第三种具体架构示意图；
图14是图13所示云平台中核心网单元的具体架构示意图；
图15是图13所示云平台应用程序开发/部署的时序逻辑图；
图16是图13所示云平台使用时的时序逻辑图。
图17是本发明实施例运行应用的方法的流程示意图；
图18是本发明接入网单元的第一实施例的组成示意图；
图19是本发明接入网单元的第二实施例的组成示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
请参照图1，为本发明实施例云平台的组成示意图，在本实施例中，所述云平台包括：
互联网单元10，用于将应用服务提供商开发的应用和轻量服务器分发至核心网单元20；
所述核心网单元20，用于将所述应用和轻量服务器分发至接入网单元30；
所述接入网单元30，用于将终端进行虚拟化，并将所述终端的计算任务迁移至虚拟机中的虚拟用户终端执行，以及将所述轻量服务器进行虚拟化，将所述轻量服务器的网络服务能力迁移至所述接入网单元以便所述虚拟用户终端运行所述核心网单元分发的应用。
在进行能力开发时，可选地，所述互联网单元10还用于将开发者的能力需求信息发送至所述核心网单元20；
所述核心网单元20还用于对所述能力需求信息对应的网元进行能力提取和封装以供应用调用。
或者，所述互联网单元10还用于接收开发者的能力需求信息，开发自身的能力并将新能力存储至所述互联网单元10的应用程序接口集合中，供应用本地或远程调用。
或者，所述核心网单元20还用于根据管理员的指令，远程控制所述接入网单元30中的能力引擎，新增或修改所述接入网单元30的软硬件能力，并加入所述接入网单元30的应用程序接口以供所述虚拟用户终端或所述轻量服务器调用。
在进行应用开发时，所述互联网单元10还用于测试并部署开发完成的应用和应用服务器。
当应用和应用服务器开发完成后，互联网单元10可以将应用进行分发。
可选地，所述互联网单元10还用于将开发完成的应用程序分发至所述核心网单元20；
所述核心网单元20还用于将与所述应用对应的轻量服务器分发至所述接入网单元30；
所述接入网单元30还用于在本地虚拟化环境中部署所述轻量服务器以便向所述虚拟用户终端提供服务。
或者，所述核心网单元20还用于接收管理员发送的分发指令，将所述应用的安装包分发至所述接入网单元30的虚拟化环境中；
所述接入网单元30还用于将所述应用安装至所述虚拟用户终端。
当用户使用终端时，可根据接入网单元30上的轻量服务器能力来服务终端。
若位于所述接入网单元30的轻量服务器具备向所述虚拟用户终端服务的能力，则在用户使用终端时，所述接入网单元30用于将所述终端与所述虚拟化用户终端连接，并根据所述终端的需求向所述轻量服务器发送请求，使用本地能力调用本地应用程序接口提供服务，或者与所述核心网单元20通信，调用所述核心网单元20能力池中的能力为所述轻量服务器服务以满足所述终端的需求；
若位于所述接入网单元30的轻量服务器不具备向所述虚拟用户终端服务的能力，则所述接入网单元30用于通过所述核心网单元向所述互联网单元10中的虚拟机服务器发送请求，通过所述轻量服务器接收所述虚拟机服务器调用所述互联网单元10的能力应用程序接口之后返回的服务结果以满足所述终端的需求。
可选地，还可以将虚拟化环境的能力内置于核心网单元20中，即所述核心网单元20还用于对所述终端和所述轻量服务器进行虚拟化。
下面将传统平台与本发明实施例的云平台进行对比。
传统开放平台能力：
硬件能力：由Internet中的服务器提供，包括计算能力、存储能力等；
位置能力：APP自己获取UE的粗略位置，长时间开启耗电量大；
空口能力：信道只是被动被占用；
用户信息能力：只能获取用户在该网站上的注册信息和操作日志；
能力可定制性：传统平台只拥有互联网能力，局限性大，可定制性差；
本申请云平台能力：
硬件能力：由接入网单元底层的IaaS提供，包括计算能力、存储能力等，分布广泛距离用户很近；
位置能力：接入网单元可以精准地定位用户，更加实用和节能；
空口能力：运营商有偿地提供更优质的空口服务，例如专用的推送通道和快速传输通道等，还有大量待开发的底层能力可利用；
用户信息能力：运营商将用户不涉及到个人隐私的信息，例如月消费能力，个性化特征等，作为能力提供给ASP，便于广告的精准投送；
能力可定制性：聚合平台拥有丰富的电信能力，可针对不同客户的需求，进行深度定制；向所有用户的终端中一键安装APP：
广告推送：通过彩信、通知栏、广告条等形式推送最新APP；
合约机：用户购机时提供廉价终端，以合约形式同意定期接受APP推送；
有偿APP：通过接受安装APP，兑换流量、积分、礼品等。
让用户最便捷地获得最需要的APP：个性化推荐：
利用聚合平台的全网数据收集能力，分析用户行为和习惯，提供最精准的APP个性化推荐；
APP试用：提供预装有待推广APP的公用VUE，用户可以切换至这个VUE，免费试用后再选择安装，免除了用户因为对APP了解不够或者嫌麻烦等问题；
因此，利用本发明实施例所述云平台，可以化现在的运营商、ASP、用户三方的诸多矛盾，变为共赢。
运营商在移动互联网的战局中占据更有利位置，减少了应对OTT挑战付 出的代价，彻底摆脱“管道”的角色。此外，运营商还可以利用本实施的云平台获得新的盈利模式。
云平台实现真正的云存储，用户的不同设备共享相同的应用数据和个人数据，信息安全得到了保障。
突破移动设备的能力限制，按需扩展硬件简单快捷，符合移动云计算思想，适应下一代网络的需求。本地化服务平台为移动互联网细分服务创新提供了基础平台。
综上所述，通过利用电信网络中非常广泛的网元设施，在现有硬件设备的基础上进行扩展，可降低平台的开发和维护成本，从而降低产品价格，提供优质服务；可提供ASP无法直接获取的电信能力，增加行业竞争力；可全面适应即将到来的物联网时代要求，在联网设备节能和降低成本上提供了新的思路；OTT开发者从运营商的竞争者，转化为运营商的客户，营造新的商业模式；可利用品牌效应，发挥运营商深受用户信赖的特点，提供更稳定和安全的服务。为解决APP推广过程中的“渠道”和“用户”两大问题提供完美解决方案。
请参照图2，为图1所示云平台的第一种具体架构示意图，在本实施例中，所述云平台包括：
互联网单元、核心网单元和接入网单元。其中，接入网单元可设置在基站中。
接入网单元是实现云平台诸多有益效果的核心单元，互联网单元是管理员和ASP直接与平台交互的入口，核心网单元位于前两者之间，起到中介的作用和更全面的功能支持，下文结合图3至图8对本实施例所述的云平台进行详细的说明。
请参照图3，为图2所示云平台中互联网单元的具体架构示意图，在本实施例中，
云平台在互联网侧是一个标准的“云计算”应用程序。自顶向下为SaaS、 PaaS和IaaS三层逻辑结构。
顶层的SaaS中包含平台本身的支撑和管理系统，通过前端的管理员视图和用户视图，提供平台全部的使用功能。
SaaS构建在PaaS之上，无论是系统本身的子应用还是用户的Web应用，都统一作为网络应用(Web APP)处理。
中间的PaaS中包含完整的开发环境、测试环境、网络仿真环境，以及所需API。当开发和测试结束后，通过应用程序分发(App Distributor)模块进行分发，将轻量服务器(Lite Server)发布在接入网单元中。
底层的IaaS为上层的PaaS提供服务。
请参照图4，为图2所示云平台中核心网单元的具体架构示意图，在本实施例中，
核心网单元自顶向下分为支撑层、能力抽象层和服务层三个逻辑层次。
顶层的支撑层中包含两个部分：第一部分中的管理模块负责管理该单元，包括管理员维护该模块的全部功能；能力模块提供所有与能力相关的功能，并与下层的能力引擎交互；监控模块用来实时监控各层所有模块的工作情况；分发模块负责向接入网单元分发Lite Server。
第二部分提供该层与接入网单元通信的网关和计费模块。
中间的能力层中包含能力池，以及对其进行增删改查的能力引擎，和提供给应用调用的能力接口。
底层的服务层对多个网元进行抽象，利用Service Master模块，提取出不同的服务和能力，封装后放入能力池中。数据中心对外表现为数据相关能力。
请参照图5，为图2所示云平台中接入网单元的具体架构示意图，在本实施例中，
接入网单元自顶向下分为应用层、平台层、基础设施层和硬件层四个逻辑层次。
顶层的应用层包含两个视图。用户视图是直接呈现给终端用户的，由移动 虚拟化中的MaaIO服务模型提供服务。开发者视图面向APP的开发者，其中的Lite Server由平台层提供支持。
平台层中包含全套的PaaS平台，以及向平台提供支持的子模块。能力引擎根据需求将不同的能力和服务封装成API供上层调用；远程通信模块与核心网单元中的分发模块和能力网关交互，与Lite Server Manager模块共同完成Lite Server的部署任务，同时提供对核心网能力的调用。
基础设施层中包含为PaaS平台提供服务的IaaS平台，以及向平台提供支持的子模块。Service Master模块对底层的各种硬件和网络能力进行提取和封装，向上提供给能力引擎进行管理。
底层的硬件层包含接入网单元中原有的网络设备，以及新加入的通用服务器集群和存储设备，向上层提供全面的硬件支持。
请参照图6，为图2所示云平台能力开发阶段的时序逻辑图，在本实施例中，通过一个跨电信网和互联网的聚合的云平台，实现应用服务对电信网络能力的使用。所以能力的开发是本发明的一个重要阶段。
能力开发阶段有2个过程。首先是由开发者主动发起的能力开发。
过程1：开发者在互联网单元的PaaS门户上操作发起该过程；
管理员在PaaS门户上收到开发者提出对能力的新需求后，利用管理员权限操作核心网单元的能力模块；
能力模块调用下层的能力引擎，能力引擎对归属签约用户服务器(Home Subscriber Server，简称HSS)等网元进行能力提取和封装后放入能力池中供上层应用调用；
开发者除了自己向管理员提出能力需求外，也可以自行开发互联网能力。在开发完成后利用IaaS App Master模块向管理员提出申请；
经过管理员审核通过后，利用该模块将新能力加入互联网单元的API集合中，供应用程序在本地/远程调用。
过程2：由管理员主动发起的能力开发过程，适用于对接入网单元中能力 的开发和管理。
管理员利用核心网单元中的能力模块，远程控制接入网单元的能力引擎；
新增或修改接入网单元处的底层软硬件能力后，加入API集合，供本地的虚拟用户终端，virtual User Equipment，简称VUE)或者Lite Server调用。
请参照图7，为图2所示云平台应用程序开发/部署的时序逻辑图，在本实施例中，云平台本质上还是采用了PaaS的云计算服务模型。作为一个优秀的PaaS平台，提供应用程序的开发和部署环境是必要的。
该阶段有2个过程。首先是由开发者主动发起的APP开发和部署。
过程1：开发者在互联网的PaaS门户上操作发起该过程；
开发者在PaaS App Master模块的配合下，通过在线开发环境来开发APP；
开发完成后使用测试环境，利用标准的沙盒进行完备的测试；
仿真环境可以与测试环境相配合，也可以单独使用，目的是向开发者提供各种不同硬件配置和软件环境的在线仿真环境，使开发者不需要将APP或者APP Server进行正式部署，就可以在本地模拟部署后的情景
开发、测试和仿真环境都在PaaS App Master的配合下使用互联网单元中的虚拟机。
在开发者完成了对APP和APP Server的最终开发后，经管理员审核通过，分别部署APP Server和Lite Server；
利用APP Router将APP Server部署在互联网单元的虚拟机(Virtual Machine，简称VM)中，以供APP进行连接并向其提供服务；
利用APP Distributor进行远程分发，将APP安装包发送至核心网单元的分发模块中；
分发模块与接入网单元的远程通信模块建立连接，将Lite Server发送至一个或多个接入网单元中；
在Lite Server Manager模块的配合下，在接入网单元本地的虚拟化环境中部署对应的Lite Server，向VUE提供近距离的服务。
过程2：由管理员主动发起的APP部署过程，适用于运营商推广APP的相关场景。
管理员利用核心网单元中的分发模块，将APP的安装包直接分发至处于某些接入网单元中的虚拟化环境中；
由接入网单元将APP安装至指定的VUE中。
分发模块可以向接入网单元中部署Lite Server，也可以直接向VUE中部署APP，以及分发广告等增值内容。
请参照图8，为图2所示云平台使用时的时序逻辑图；在本实施例中，使用阶段有2个过程。
过程1：接入网单元本地的Lite Server有能力向VUE提供服务。首先用户使用UE，UE与接入网单元中的VUE建立连接。VUE根据需求，向Lite Server发送请求，Lite Server此时有两种可能，分别是调用本地的API，和使用核心网中的能力。前者时，Lite Server需要使用本地能力，例如专用信道、定位和存储时，单元进行计费后，调用API提供服务。后者时，接入网单元与核心网单元的能力接口通信，在计费模块生效后，调用本地能力池中的能力向Lite Server提供服务。
过程2：本地的Lite Server由于功能逻辑所限，无法提供完整的服务，此时需要向互联网单元中VM中的Server发送请求。由Server调用了互联网中的能力API后，将服务结果发回Lite Server，最终服务VUE。
本实施例中云平台的三个功能单元，分别部署在基站、核心网和互联网中，能够整合运营商电信网络中的各种能力，同时具有现有PaaS平台的所有优点。更能够为运营商提供一键分发APP的优势，将现有网络用户转化为应用服务的用户。
从技术上，云平台依赖在接入网单元处的移动虚拟化技术提供的VUE和Lite Server，最大化地利用运营商的网络能力，让ASP向用户提供更加优质服务的同时，避免为运营商的网络带来不必要的负担。接入网单元上的能力引擎， 将接入网单元所具有的电信能力提供给平台之上的应用程序，同时利用网络边缘的位置特点，减少往返时延(Round-Trip Time，简称RTT)和核心网流量，最大化利用定位能力，增加盈利空间。
对ASP尤其是中小型ASP来说，本发明提供了全套的开发、测试、仿真和部署环境，大大节省了ASP开发APP的成本，提高了开发效率，丰富了APP的功能。
请参照图9，为图1所示云平台的第二种具体架构示意图；在本实施例中，
云平台共分为互联网单元、核心网单元和接入网单元，其中，接入网单元可设置在基站中。
接入网单元是实现本实施的云平台诸多有益效果的核心单元，互联网单元是管理员和ASP直接与平台交互的入口，核心网单元位于前两者之间，起到中介的作用和更全面的功能支持，本实施例中的互联网单元与图4所示互联网单元相比，只保留PaaS门户和App Distributor两个主要功能模块，和与云平台外部互联网应用程序的交互接口。
整个互联网单元对外表现成为一个SaaS服务模型的云计算产品，不提供公有的开发和运行环境，不提供统一的平台。
ASP可以将自己开发的Lite Server通过App Distributor模块经核心网单元分发至接入网单元中并部署，互联网单元中不再提供部署Server的虚拟化环境，Lite Server与Server的通信由能力接口提供。PaaS门户和支撑管理子系统所需的互联网能力也由能力接口来提供。其余的核心网单元和接入网单元与图4所示云平台相同。对于本实施例中云平台在各阶段的时序逻辑，下面结合图13-图15进行详细的说明。
请参照图10，为图9所示云平台能力开发阶段的时序逻辑图；在本实施例中，
能力开发阶段有2个过程。首先是由开发者主动发起的能力开发，该部分由于互联网单元的功能简化，所以只能先有开发者提出对新能力的需求后，由 管理员进行核心网能力的管理，详细同实施例图6中的:过程1。
由管理员主动发起的能力开发过程同实施例一中的过程2。
请参照图11，为图9所示云平台应用程序开发/部署的时序逻辑图。在本实施例中，
该阶段有2个过程。首先是开发者主动发起的Lite Server的部署。与图7实施例的区别在于，图7实施例有开发APP、APP Server、Lite Server的全过程及部署过程，而本实施例则只有APP和Lite Server的部署和分发过程。
详情可参照图7实施例过程2。
请参照图12，是图9所示云平台使用时的时序逻辑图；在本实施例中，
该阶段有2个过程。过程1同图8所示实施例一的过程1。
过程2是本地的Lite Server由于功能逻辑所限，无法提供完整的服务，此时需要向Server发送请求。接入网单元与互联网单元建立连接后，通过能力接口访问该应用程序的Server后，将服务结果发回Lite Server，最终服务VUE。
本实施例中云平台的三个功能单元，分别部署在基站、核心网和互联网中，能够整合运营商电信网络中的各种能力，同时具有现有PaaS平台的所有优点。更能够为运营商提供一键分发APP的优势，将现有网络用户转化为应用服务的用户。
从技术上，云平台依赖在接入网单元处的移动虚拟化技术提供的VUE和Lite Server，最大化地利用运营商的网络能力，让ASP向用户提供更加优质服务的同时，避免为运营商的网络带来不必要的负担。接入网单元上的能力引擎，将接入网单元所具有的电信能力提供给平台之上的应用程序，同时利用网络边缘的位置特点，减少RTT和核心网流量，最大化利用定位能力，增加盈利空间。
请参照图13，是图1所示云平台的第三种具体架构示意图；在本实施例中，
云平台共分为互联网单元、核心网单元和接入网单元，其中，接入网单元 可设置在基站中。
接入网单元是实现云平台诸多有益效果的核心单元，互联网单元是管理员和ASP直接与平台交互的入口，核心网单元位于前两者之间，起到中介的作用和更全面的功能支持，下面结合图17-图19进行详细的说明。
请参照图14，是图13所示云平台中核心网单元的具体架构示意图；在本实施例中，
云平台的核心网单元自顶向下分为应用层、平台层、支撑层、能力抽象层和服务层五个逻辑层次。
最顶层的应用层和平台层是将接入网单元中的对应层向核心网单元中进行移植，适用于云平台的前期部署阶段，具体结构和功能同实施例一中接入网单元的相关说明。
在云平台投入使用初期，用户数较少，同时对Lite Server下移的需求暂时没有那么强烈，此时在核心网单元中加入与接入网单元相同的虚拟化环境，在此虚拟化环境之上设置供VUE和Lite Server部署的工具和环境，使核心网单元可以暂时起到接入网单元的作用，并暂时提供相应的有益效果。
支撑层、能力抽象层和基础服务层同图4所述实施例。
请参照图15，是图13所示云平台应用程序开发/部署的时序逻辑图；在本实施例中，
由于本实施例在核心网单元中提供了虚拟化环境，故APP可以部署在接入网单元或者核心网单元中。当APP部署在接入网单元时，时序逻辑同图7所示实施例。
当APP部署在核心网单元时，如图18所示，较粗的两个箭头即分别是开发者主动发起和管理员主动发起的APP部署过程中，由分发模块地向核心网单元中的虚拟化环境中部署的流程。
请参照图16，是图13所示云平台使用时的时序逻辑图。在本实施例中，
由于本实施例在核心网单元中提供了虚拟化环境，故VUE可以接受来自 接入网单元或者核心网单元中Lite Server的服务。前者同图8所示实施例。
后者如图16所示，较粗的两组箭头分别是Lite Server和Server提供服务的过程中，由核心网单元中的虚拟机参与的流程。
本实施例在在核心网单元加入了虚拟化技术，具体表现为该单元上的平台层和应用层，由此带来的技术效果为最大化的利用运营商的网络能力，让ASP向用户提供更加优质服务的同时，避免为运营商的网络带来不必要的负担。
请参照图17，为本发明实施例运行应用的方法的流程示意图，在本实施例中，所述方法包括以下步骤：
S101，接收核心网单元分发的应用及轻量服务器。
其中，所述应用及轻量服务器由互联网单元开发完成并分发至所述核心网单元
S102，将终端进行虚拟化，并将所述终端的计算任务迁移至虚拟机中的虚拟用户终端执行，以及将所述轻量服务器进行虚拟化，将所述轻量服务器的网络服务能力迁移至接入网单元以便所述虚拟用户终端运行所述核心网单元分发的应用。
请参照图18，为本发明接入网单元的第一实施例的组成示意图，在本实施例中，所述接入网单元包括：
接收模块100，用于接收核心网单元分发的应用及轻量服务器，所述应用及轻量服务器由互联网单元开发完成并分发至所述核心网单元；
虚拟化模块200，将终端进行虚拟化，并将所述终端的计算任务迁移至虚拟机中的虚拟用户终端执行，以及将所述轻量服务器进行虚拟化，将所述轻量服务器的网络服务能力迁移至接入网单元以便所述虚拟用户终端运行所述核心网单元分发的应用。
可选地，若位于所述接入网单元的轻量服务器具备向所述虚拟用户终端服务的能力，则在用户使用终端时，所述虚拟化模块200还用于将所述终端与所述虚拟化用户终端连接，并根据所述终端的需求向所述轻量服务器发送请求，使用本地能力调用本地应用程序接口提供服务，或者与所述核心网单元通信， 调用所述核心网单元能力池中的能力为所述轻量服务器服务以满足所述终端的需求；
若位于所述接入网单元的轻量服务器不具备向所述虚拟用户终端服务的能力，则所述虚拟化模块200还用于通过所述核心网单元向所述互联网单元中的虚拟机服务器发送请求，通过所述轻量服务器接收所述虚拟机服务器调用所述互联网单元的能力应用程序接口之后返回的服务结果以满足所述终端的需求。
请参照图19，为本发明接入网单元的第二实施例的组成示意图，在本实施例中，所述接入网单元包括：
输入设备110、输出设备120、存储器130和处理器140，所述输入设备110、输出设备120、存储器130和处理器140与总线连接，其中，所述存储器130中存储一组程序代码，所述处理器140用于调用所述存储器130中存储的程序代码，执行以下操作：
接收核心网单元分发的应用及轻量服务器，所述应用及轻量服务器由互联网单元开发完成并分发至所述核心网单元；
将终端进行虚拟化，并将所述终端的计算任务迁移至虚拟机中的虚拟用户终端执行，以及将所述轻量服务器进行虚拟化，将所述轻量服务器的网络服务能力迁移至接入网单元以便所述虚拟用户终端运行所述核心网单元分发的应用。
可选地，若位于所述接入网单元的轻量服务器具备向所述虚拟用户终端服务的能力，则在用户使用终端时，所述处理器140还用于将所述终端与所述虚拟化用户终端连接，并根据所述终端的需求向所述轻量服务器发送请求，使用本地能力调用本地应用程序接口提供服务，或者与所述核心网单元通信，调用所述核心网单元能力池中的能力为所述轻量服务器服务以满足所述终端的需求；
若位于所述接入网单元的轻量服务器不具备向所述虚拟用户终端服务的能力，则所述处理器140还用于通过所述核心网单元向所述互联网单元中的虚拟机服务器发送请求，通过所述轻量服务器接收所述虚拟机服务器调用所述互 联网单元的能力应用程序接口之后返回的服务结果以满足所述终端的需求。
需要说明的是，本说明书中的各个实施例均采用递进的方式描述，每个实施例重点说明的都是与其它实施例的不同之处，各个实施例之间相同相似的部分互相参见即可。对于装置实施例而言，由于其与方法实施例基本相似，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
通过上述实施例的描述，本发明具有以下优点：
通过在接入网单元处配置移动虚拟化技术，使得接入网单元可提供VUE和Lite Server，最大化地利用运营商的网络能力，让ASP向用户提供更加优质服务的同时，避免为运营商的网络带来不必要的负担；同时可降低运营商开发云产品的成本，提高用户体验，提升运营商的服务推广效果；接入网单元上的能力引擎，将接入网单元所具有的电信能力提供给平台之上的应用程序，同时利用网络边缘的位置特点，减少往返时延和核心网流量，最大化利用定位能力，增加盈利空间。
本领域普通技术人员可以理解：实现上述方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成，前述的程序可以存储于一计算机可读取存储介质中，该程序在执行时，执行包括上述方法实施例的步骤；而前述的存储介质包括：ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上对本发明实施例所提供的一种云平台、运行应用的方法及接入网单元进行了详细介绍，本文中应用了具体个例对本发明的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本发明的方法及其核心思想；同时，对于本领域的一般技术人员，依据本发明的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本发明的限制。

Claims (15)

  1. 一种云平台，其特征在于，包括：
    互联网单元，用于将应用服务提供商开发的应用和轻量服务器分发至核心网单元；
    所述核心网单元，用于将所述应用和轻量服务器分发至接入网单元；
    所述接入网单元，用于将终端进行虚拟化，并将所述终端的计算任务迁移至虚拟机中的虚拟用户终端执行，以及将所述轻量服务器进行虚拟化，将所述轻量服务器的网络服务能力迁移至所述接入网单元以便所述虚拟用户终端运行所述核心网单元分发的应用。
  2. 如权利要求1所述的云平台，其特征在于，所述互联网单元还用于将开发者的能力需求信息发送至所述核心网单元；
    所述核心网单元还用于对所述能力需求信息对应的网元进行能力提取和封装以供应用调用。
  3. 如权利要求1所述的云平台，其特征在于，所述互联网单元还用于接收开发者的能力需求信息，开发自身的能力并将新能力存储至所述互联网单元的应用程序接口集合中，供应用本地或远程调用。
  4. 如权利要求1所述的云平台，其特征在于，所述核心网单元还用于根据管理员的指令，远程控制所述接入网单元中的能力引擎，新增或修改所述接入网单元的软硬件能力，并加入所述接入网单元的应用程序接口以供所述虚拟用户终端或所述轻量服务器调用。
  5. 如权利要求1所述的云平台，其特征在于，所述互联网单元还用于测试并部署开发完成的应用和应用服务器。
  6. 如权利要求5所述的云平台，其特征在于，所述互联网单元还用于将开发完成的应用程序分发至所述核心网单元；
    所述核心网单元还用于将与所述应用对应的轻量服务器分发至所述接入网单元；
    所述接入网单元还用于在本地虚拟化环境中部署所述轻量服务器以便向所述虚拟用户终端提供服务。
  7. 如权利要求5所述的云平台，其特征在于，所述核心网单元还用于接收管理员发送的分发指令，将所述应用的安装包分发至所述接入网单元的虚拟化环境中；
    所述接入网单元还用于将所述应用安装至所述虚拟用户终端。
  8. 如权利要求6或7所述的云平台，其特征在于，若位于所述接入网单元的轻量服务器具备向所述虚拟用户终端服务的能力，则在用户使用终端时，所述接入网单元用于将所述终端与所述虚拟化用户终端连接，并根据所述终端的需求向所述轻量服务器发送请求，使用本地能力调用本地应用程序接口提供服务，或者与所述核心网单元通信，调用所述核心网单元能力池中的能力为所述轻量服务器服务以满足所述终端的需求；
    若位于所述接入网单元的轻量服务器不具备向所述虚拟用户终端服务的能力，则所述接入网单元用于通过所述核心网单元向所述互联网单元中的虚拟机服务器发送请求，通过所述轻量服务器接收所述虚拟机服务器调用所述互联网单元的能力应用程序接口之后返回的服务结果以满足所述终端的需求。
  9. 如权利要求1所述的云平台，其特征在于，所述核心网单元还用于对所述终端和所述轻量服务器进行虚拟化。
  10. 一种运行应用的方法，其特征在于，包括：
    接收核心网单元分发的应用及轻量服务器，所述应用及轻量服务器由互联网单元开发完成并分发至所述核心网单元；
    将终端进行虚拟化，并将所述终端的计算任务迁移至虚拟机中的虚拟用户终端执行，以及将所述轻量服务器进行虚拟化，将所述轻量服务器的网络服务能力迁移至接入网单元以便所述虚拟用户终端运行所述核心网单元分发的应用。
  11. 如权利要求10所述的方法，其特征在于，若位于所述接入网单元的轻量服务器具备向所述虚拟用户终端服务的能力，则在用户使用终端时，将所述终端与所述虚拟化用户终端连接，并根据所述终端的需求向所述轻量服务器发送请求，使用本地能力调用本地应用程序接口提供服务，或者与所述核心网单元通信，调用所述核心网单元能力池中的能力为所述轻量服务器服务以满足所述终端的需求；
    若位于所述接入网单元的轻量服务器不具备向所述虚拟用户终端服务的能力，则通过所述核心网单元向所述互联网单元中的虚拟机服务器发送请求，通过所述轻量服务器接收所述虚拟机服务器调用所述互联网单元的能力应用程序接口之后返回的服务结果以满足所述终端的需求。
  12. 一种接入网单元，其特征在于，包括：
    接收模块，用于接收核心网单元分发的应用及轻量服务器，所述应用及轻量服务器由互联网单元开发完成并分发至所述核心网单元；
    虚拟化模块，将终端进行虚拟化，并将所述终端的计算任务迁移至虚拟机中的虚拟用户终端执行，以及将所述轻量服务器进行虚拟化，将所述轻量服务器的网络服务能力迁移至接入网单元以便所述虚拟用户终端运行所述核心网单元分发的应用。
  13. 如权利要求12所述的接入网单元，其特征在于，包括：
    若位于所述接入网单元的轻量服务器具备向所述虚拟用户终端服务的能力，则在用户使用终端时，所述虚拟化模块还用于将所述终端与所述虚拟化用户终端连接，并根据所述终端的需求向所述轻量服务器发送请求，使用本地能力调用本地应用程序接口提供服务，或者与所述核心网单元通信，调用所述核 心网单元能力池中的能力为所述轻量服务器服务以满足所述终端的需求；
    若位于所述接入网单元的轻量服务器不具备向所述虚拟用户终端服务的能力，则所述虚拟化模块还用于通过所述核心网单元向所述互联网单元中的虚拟机服务器发送请求，通过所述轻量服务器接收所述虚拟机服务器调用所述互联网单元的能力应用程序接口之后返回的服务结果以满足所述终端的需求。
  14. 一种接入网单元，其特征在于，包括：
    输入设备、输出设备、存储器和处理器，所述输入设备、输出设备、存储器和处理器与总线连接，其中，所述存储器中存储一组程序代码，所述处理器用于调用所述存储器中存储的程序代码，执行以下操作：
    接收核心网单元分发的应用及轻量服务器，所述应用及轻量服务器由互联网单元开发完成并分发至所述核心网单元；
    将终端进行虚拟化，并将所述终端的计算任务迁移至虚拟机中的虚拟用户终端执行，以及将所述轻量服务器进行虚拟化，将所述轻量服务器的网络服务能力迁移至接入网单元以便所述虚拟用户终端运行所述核心网单元分发的应用。
  15. 如权利要求14所述的接入网单元，其特征在于，若位于所述接入网单元的轻量服务器具备向所述虚拟用户终端服务的能力，则在用户使用终端时，所述处理器还用于将所述终端与所述虚拟化用户终端连接，并根据所述终端的需求向所述轻量服务器发送请求，使用本地能力调用本地应用程序接口提供服务，或者与所述核心网单元通信，调用所述核心网单元能力池中的能力为所述轻量服务器服务以满足所述终端的需求；
    若位于所述接入网单元的轻量服务器不具备向所述虚拟用户终端服务的能力，则所述处理器还用于通过所述核心网单元向所述互联网单元中的虚拟机服务器发送请求，通过所述轻量服务器接收所述虚拟机服务器调用所述互联网单元的能力应用程序接口之后返回的服务结果以满足所述终端的需求。
PCT/CN2015/075200 2015-03-27 2015-03-27 一种云平台、运行应用的方法及接入网单元 WO2016154785A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN201580077704.1A CN107409436B (zh) 2015-03-27 2015-03-27 一种云平台、运行应用的方法及接入网单元
PCT/CN2015/075200 WO2016154785A1 (zh) 2015-03-27 2015-03-27 一种云平台、运行应用的方法及接入网单元
US15/716,816 US10481921B2 (en) 2015-03-27 2017-09-27 Cloud platform, application running method, and access network unit

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/075200 WO2016154785A1 (zh) 2015-03-27 2015-03-27 一种云平台、运行应用的方法及接入网单元

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/716,816 Continuation US10481921B2 (en) 2015-03-27 2017-09-27 Cloud platform, application running method, and access network unit

Publications (1)

Publication Number Publication Date
WO2016154785A1 true WO2016154785A1 (zh) 2016-10-06

Family

ID=57003713

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/075200 WO2016154785A1 (zh) 2015-03-27 2015-03-27 一种云平台、运行应用的方法及接入网单元

Country Status (3)

Country Link
US (1) US10481921B2 (zh)
CN (1) CN107409436B (zh)
WO (1) WO2016154785A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10193762B2 (en) 2016-08-11 2019-01-29 Rescale, Inc. Dynamic optimization of simulation resources
US10387198B2 (en) 2016-08-11 2019-08-20 Rescale, Inc. Integrated multi-provider compute platform
EP3528458B1 (en) * 2018-02-20 2020-09-23 Darktrace Limited A cyber security appliance for a cloud infrastructure
CN110933623B (zh) * 2018-09-17 2021-08-31 华为技术有限公司 一种通信方法和装置
EP3816800A1 (en) * 2019-10-31 2021-05-05 ABB Schweiz AG Assignment of tasks between a plurality of devices
CN113691533B (zh) * 2021-08-24 2023-02-14 武汉光影智能技术有限公司 一种路由器能力接口的聚合方法及系统
CN115102952B (zh) * 2022-06-22 2023-04-07 睿云联(厦门)网络通讯技术有限公司 终端产品通过本地服务器连接云平台的方法、设备及介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101969391A (zh) * 2010-10-27 2011-02-09 北京邮电大学 一种支持融合网络业务的云平台及其工作方法
US20130117769A1 (en) * 2011-11-09 2013-05-09 Qualcomm Incorporated Sensor api framework for cloud based applications
CN103365702A (zh) * 2013-07-11 2013-10-23 中国科学院合肥物质科学研究院 IaaS云环境下轻量级虚拟机进程追踪系统和方法

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7577730B2 (en) * 2002-11-27 2009-08-18 International Business Machines Corporation Semi-hierarchical system and method for administration of clusters of computer resources
US8630192B2 (en) * 2009-01-28 2014-01-14 Headwater Partners I Llc Verifiable and accurate service usage monitoring for intermediate networking devices
US8261295B1 (en) * 2011-03-16 2012-09-04 Google Inc. High-level language for specifying configurations of cloud-based deployments
CN102968860B (zh) * 2012-12-20 2014-11-19 广东御和电子科技有限公司 云atm系统
US9870268B2 (en) * 2013-08-05 2018-01-16 Amazon Technologies, Inc. Virtual computing instance migration
CN103746886B (zh) * 2013-12-13 2017-06-30 北京邮电大学 一种FiWi节点和一种FiWi融合组网方法
CN103746925B (zh) * 2013-12-13 2017-06-30 北京邮电大学 一种FiWi融合网络以及基于FiWi融合网络的通信方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101969391A (zh) * 2010-10-27 2011-02-09 北京邮电大学 一种支持融合网络业务的云平台及其工作方法
US20130117769A1 (en) * 2011-11-09 2013-05-09 Qualcomm Incorporated Sensor api framework for cloud based applications
CN103365702A (zh) * 2013-07-11 2013-10-23 中国科学院合肥物质科学研究院 IaaS云环境下轻量级虚拟机进程追踪系统和方法

Also Published As

Publication number Publication date
US20180018204A1 (en) 2018-01-18
CN107409436B (zh) 2020-02-21
US10481921B2 (en) 2019-11-19
CN107409436A (zh) 2017-11-28

Similar Documents

Publication Publication Date Title
WO2016154785A1 (zh) 一种云平台、运行应用的方法及接入网单元
US11297601B2 (en) Resource allocation method and orchestrator for network slicing in the wireless access network
CN105207798B (zh) 软件定义网络中的业务编排方法及装置
KR101507919B1 (ko) 가상 데스크탑 서비스를 위한 방법 및 장치
US9450783B2 (en) Abstracting cloud management
US8271653B2 (en) Methods and systems for cloud management using multiple cloud management schemes to allow communication between independently controlled clouds
US11928522B2 (en) Containerized VNF deployment method and related device
KR102140636B1 (ko) Nfv를 통한 풀 기반 m2m 서비스 계층 구축
WO2017080391A1 (zh) 一种网络服务部署方法和装置
CN110908658A (zh) 一种“微服务+微应用”系统、数据处理方法及装置
US20130325433A1 (en) Model for Simulation Within Infrastructure Management Software
US10855757B2 (en) High availability and high utilization cloud data center architecture for supporting telecommunications services
Zou et al. Design and implementation of hybrid cloud computing architecture based on cloud bus
CN103885833A (zh) 一种资源管理方法和系统
Yasrab Platform-as-a-service (paas): the next hype of cloud computing
WO2018032884A1 (zh) 一种计费方法、装置及系统
CN109428764A (zh) 虚拟网络功能的实例化方法
Roda-Sanchez et al. Cloud–edge microservices architecture and service orchestration: An integral solution for a real-world deployment experience
CN103618758B (zh) Web服务器及其系统资源访问控制方法
Garcia-Aviles et al. ACHO: A framework for flexible re-orchestration of virtual network functions
CN109347661A (zh) 消费者vnf的实例化方法及装置
CN116800616A (zh) 虚拟化网络设备的管理方法及相关装置
Houacine et al. Service architecture for multi-environment mobile cloud services
Premsankar et al. Advances in cloud computing, wireless communications and the internet of things
Mwangama et al. Towards mobile federated network operators

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

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

Country of ref document: EP

Kind code of ref document: A1