WO2016072895A1

WO2016072895A1 - Wireless communications network, user equipment and methods for handling a cloud

Info

Publication number: WO2016072895A1
Application number: PCT/SE2014/051316
Authority: WO
Inventors: Lars Westberg
Original assignee: Telefonaktiebolaget L M Ericsson (Publ)
Priority date: 2014-11-06
Filing date: 2014-11-06
Publication date: 2016-05-12

Abstract

A method performed by an end-user policy server for handling a cloud service in a cloud is provided. The user equipment operates in a wireless communications network. The user equipment sends (201) a request for the cloud service to an end-user policy server. When the user equipment fulfilsan end-user policy according to the end-user policy server, the end-user policy server sends (203) an instruction to a charging system, to activate a charging of the cloud service. The charging is related to the user equipment.

Description

WIRELESS COMMUNICATIONS NETWORK, USER EQUIPMENT AND METHODS FOR

HANDLING A CLOUD SERVICE

TECHNICAL FIELD

Embodiments herein relate to a wireless communications network, an end-user policy server and methods therein. In particular, it relates to handling a cloud service in a cloud in the wireless communications network.

BACKGROUND

Wireless communications networks

Wireless devices for communication such as terminals are also known as e.g. User Equipments (UE), mobile terminals, wireless terminals and/or mobile stations. Wireless devices are enabled to communicate wirelessly in a cellular communications network or wireless communication system, sometimes also referred to as a cellular radio system or cellular networks. The communication may be performed e.g. between two wireless devices, between a wireless device and a regular telephone and/or between a wireless device and a server, such as server providing video streaming service, via a Radio Access Network (RAN) and possibly one or more core networks, comprised within the cellular communications network.

Wireless devices may further be referred to as mobile telephones, cellular telephones, computers, or surf plates with wireless capability, just to mention some further examples. The wireless devices in the present context may be, for example, portable, pocket-storable, hand-held, computer-comprised, or vehicle-mounted mobile devices, enabled to communicate voice and/or data, via the RAN, with another entity, such as another wireless device or a server.

A cellular communications network covers a geographical area which is divided into cell areas, wherein each cell area being served by a base station, e.g. a Radio Base Station (RBS), which sometimes may be referred to as e.g. eNodeB (eNB), NodeB, B node, Base Transceiver Station (BTS), or AP (Access Point), depending on the technology and terminology used. The base stations may be of different classes such as e.g. macro eNodeB, home eNodeB or pico base station, based on transmission power and thereby also cell size. A cell is the geographical area where radio coverage is provided by the base station at a base station site. One base station, situated on the base station site, may serve one or several cells. Further, each base station may support one or several communication technologies. The base stations communicate over the air interface operating on radio frequencies with the wireless devices within range of the base stations also referred to as transmitter-receiver pairs. In the context of this disclosure, the expression Downlink (DL) is used for the transmission path from the base station to a wireless device. The expression Uplink (UL) is used for the transmission path in the opposite direction i.e. from the wireless device to the base station.

In 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE), base stations, which may be referred to as eNodeBs or even eNBs, may be directly connected to one or more core networks.

Universal Mobile Telecommunications System (UMTS) is a third generation mobile communication system, which evolved from the GSM, and is intended to provide improved mobile communication services based on Wideband Code Division Multiple Access (WCDMA) access technology. UMTS Terrestrial Radio Access Network (UTRAN) is essentially a radio access network using wideband code division multiple access for terminals. The 3GPP has undertaken to evolve further the UTRAN and GSM based radio access network technologies.

3GPP LTE radio access standard has been written in order to support high bitrates and low latency both for uplink and downlink traffic. All data transmission is in LTE is controlled by the radio base station.

Cloud

Cloud computing in general may be portrayed as a synonym for distributed computing over a network, with the ability to run a program or application on many connected computers at the same time. It specifically refers to a Computing hardware machine or group of computing hardware machines commonly referred as a server connected through a communication network such as Internet, intranet, local area network (LAN) or Wide area network (WAN) and Individual user or users who have permission to access the server can use the server's processing power for their individual computing needs like to run an application, store data or any other computing need alike. Therefore, instead of using a personal computer every-time to run the application, individual can now run the application from anywhere in the world, as the server provides the processing power to the application and the server is also connected to a network via Internet or other connection platforms to be accessed from anywhere. All this has become possible due to increasing computer processing power available to humankind with decrease in cost.

In common usage, the term "the cloud" is essentially a metaphor for the Internet. The Cloud has two drivers, cloud in Internet or for optimization of enterprises mainly driven for a hosting service for enterprises. The driver means that they can lower the cost of operation of the back-end infrastructures. The major business case is that multiprocessor capability allows the cloud provider to offer a cost efficient Infrastructure as a service (laaS) to enterprises. It lower the cost for the enterprise instead of having their own hardware.

Marketers have further popularized the phrase "in the cloud" to refer to software, platforms and infrastructure that are sold "as a service", i.e. remotely through the Internet. Typically, the seller has actual energy-consuming servers which host products and services from a remote location, so end-users don't have to; they can simply log on to the network without installing anything. The major models of cloud computing service are known as software as a service, platform as a service, and infrastructure as a service. These cloud services may be offered in a public, private or hybrid network.

Network-based services, which appear to be provided by real server hardware and are in fact served up by virtual hardware simulated by software running on one or more real machines, are often called cloud computing. Such virtual servers do not physically exist and can therefore be moved around and scaled up or down on the fly without affecting the end user, somewhat like a cloud becoming larger or smaller without being a physical object.

The term "cloud computing" is mostly used to sell hosted services in the sense of application service provisioning that run client server software at a remote location. End users access cloud-based applications through a web browser, thin client or mobile app while the business software and user's data are stored on servers at a remote location.

Cloud computing providers offer their services according to numerous of fundamental models.

Infrastructure as a service

An example of such model is Infrastructure as a service (laaS).

In a cloud-service model according to the Internet Engineering Task Force (IETF), providers of laaS offer computers such as physical or virtual machines, and other resources. laaS-cloud providers supply resources on-demand from their large pools installed in data centers. For wide area connectivity, customers may use either the Internet or carrier clouds such as dedicated virtual private networks.

To deploy their applications, cloud users install operating-system images and their application software on the cloud infrastructure. In this model, the cloud user patches and maintains the operating systems and the application software. Cloud providers typically charge laaS services on a utility computing basis: cost reflects the amount of resources allocated and consumed. Platform as a service

Another example of model is Platform as a service (PaaS). In the PaaS models, cloud providers deliver a computing platform, e.g. including operating system,

programming language execution environment, database, and web server. Application developers can develop and run their software solutions on a cloud platform without the cost and complexity of buying and managing the underlying hardware and software layers. With some PaaS offers, the underlying computer and storage resources scale automatically to match application demand so that the cloud user does not have to allocate resources manually. The automatic scaling function could be one of the functionality provided by the PaaS. There are also other possibilities as well

Cloud clients

Users access cloud computing using networked client devices, such as desktop computers, laptops, tablets and smartphones. Some of these devices also referred to as cloud clients, rely on cloud computing for all or a majority of their applications so as to be essentially useless without it. Examples are thin clients and browser-based Chromebook. Many cloud applications do not require specific software on the client and instead use a web browser to interact with the cloud application.

Thus, the emerging technology of today is Cloud as an infrastructure component that can be used for end-user services.

On the Internet , any end-user and/or enterprise may rent computer capacity from Amazon through ECE-interfaces. Similar offering are made by operators as well.

Therefore renting of cloud is one of the major technical trends within Internet . In all cases, the charging of the renting cost is provided by the Cloud provider. Currently, there are some suggestions for split-browser architecture, also referred to as silk browser, when the Browser in the clients is divided into two different parts: A first part relating to thin-client browser that views the streaming video from a central server. A second part is related to the server that fetching all objects and rendering the WEB-page. In this case, the charging is made by split-browser provider.

A virtual desktops may further be used as model for centralized processing for clients. A server is running an entire PC-environment and the server is generating a video-stream to clients. In this case, any application may be used. It is a demand for utilizing Cloud technology as a service for any client. There may two types of scenarios:

The first type comprises exposure of a number of Cloud interface to client's ecosystem such that the application can reach the cloud applications and resources. In this case the charging is paid by person that rents the cloud service.

The second type comprises a scenario when the application is a part of the ecosystem such as an Android and/or Apple eco-system. But in this case, the development of the application should be done by the application-developer. This comprises both parts: the App in the Client part and the App in the server part, that will run within the network. In this case there are no prior knowledge in the cloud about the application.

The first type of scenario of cloud-service is today provided by Google and Amazon.

The second type of scenario of cloud-service is usually not used because, the solution today is to have two different developments: client application development and a separate server development platform. The allocation is made when cloud service resources are requested by an software developer that design the server. The cloud service resources are typically larger databases or virtual PC with a set of memory assigned to it. The end-user in this case is typically an IT-manager on a small enterprise and it would like to use the cloud to boost a back-end server farm. The executable of the server is uploaded to a cloud and the communication is then made over Internet.

The integration of cloud services in a cellular networks is not sufficient for providing cloud services in an optimal way.

SUMMARY It is therefore an object of embodiments herein to provide an improved way of handling cloud services in a wireless communications network using service clouds. According to a first aspect of embodiments herein, the object is achieved by a method performed by an end-user policy server for handling a cloud service in a cloud. The end-user policy server operates in a wireless communications network. The end-user policy server receives a request for the cloud service from a user equipment. When the user equipment fulfils an end-user policy according to the end-user policy server, the end- user policy server sends an instruction to a charging system, to activate a charging of the cloud service. The charging is related to the user equipment.

According to a second aspect of embodiments herein, the object is achieved by a method performed in a wireless communications network for handling a cloud service in a cloud. The cloud service is to be provided to a user equipment operating in a wireless communications network.

The user equipment sends a request for the cloud service to an end-user policy server.

The end-user policy server checks whether the user equipment fulfils an end-user policy.

When the user equipment fulfils an end-user policy according to the end-user policy server, a cloud application is downloaded into the cloud 105, and the fulfils sends an instruction to a charging system to activate a charging of the cloud service. The charging is related to the user equipment.

According to a third aspect of embodiments herein, the object is achieved by an end-user policy server for handling a cloud service in a cloud. The end-user policy server is arranged to operate in a wireless communications network. The end-user policy server is configured to send a request for the cloud service to an end-user policy server, and to send an instruction to a charging system to activate a charging of the cloud service when the user equipment fulfils an end-user policy according to the end-user policy server. The charging is related to the user equipment.

According to a forth aspect of embodiments herein, the object is achieved by a wireless communications network 100 for handling a cloud service in a cloud 105. The cloud service is to be provided to a user equipment operating in a wireless

communications network. The cloud is arranged to be comprised in the wireless communications network. In the wireless communications network 100:

The user equipment is configured to send a request for the cloud service to an end- user policy server.

The end-user policy server is configured to check whether the user equipment fulfils an end-user policy.

Any one out of a node in the cloud and the user equipment is configured to download a cloud application into the cloud, when the user equipment fulfils an end-user policy according to the end-user policy server.

The end-user policy server is further configured to send an instruction to a charging system to activate a charging of the cloud service when the user equipment fulfils an end- user policy according to the end-user policy server 145. The charging is related to the user equipment.

An advantage with embodiments herein is that the mobile system can provide cloud services to an end-user such as user equipment and that the end-user can submit their own server.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of embodiments herein are described in more detail with reference to attached drawings in which: Figure 1 is a schematic block diagram illustrating a wireless communications network.

Figure 2 is a flowchart depicting embodiments of a method in a network node.

Figure 3a and b are a sequence diagrams illustrating a embodiments of a method.

Figure 4 is a schematic block diagram illustrating embodiments of a user equipment.

Figure 5 is a schematic block diagram illustrating embodiments of an end-user policy server. Figure 6 is a schematic block diagram illustrating embodiments of a node in a cloud.

Figure 7 is a schematic block diagram illustrating embodiments of a cloud resource manager.

DETAILED DESCRIPTION

As part of developing embodiments herein, a problem will first be identified and shortly discussed.

The existing mobile core network is designed for on-demand establishment of policy control and charging, but does not cover the support for on-demand cloud based service. Current solutions for network operators are designed for provisioned service. This means that the system needs configuration-scripts to the orchestration function. The lack of on- demand requires new functionality in the telecom operator network.

So, an integration of on-demand usage of Cloud services puts new requirements on the network.

Further, currently, there is no functionality where an end-user can request and be charged for cloud resources. There are two different aspects:

• The Charging system do not have any charging for cloud resources.

· The charging is related to for each end-user. It is not developed for charging for hosting of a server. The interaction of the core is designed for "per end-user" charging.

Thus an object of embodiments herein is to enable end-user charging for Cloud and then allow the end-user to upload the server to the Cloud such that each server is uniquely associated with each end-user.

According to embodiments herein, an extension for the current core-network is provided to enable policy control and charging for a cloud-service which is directed toward a mobile client.

A step of introducing the cloud in the telecom operator domain is to Virtualizes the Network Functions (VNF), as can be seen in European Telecommunications Standards Institute (ETSI) http://www.etsi.org/technologies-clusters/technologies/nfv. These functions are deployed in a cloud environment. Orchestration is the tool to make deployment.

According to embodiments herein, an on-demand architecture is assumed when the end-user makes an on-demand resource request and upload the server executable to the cloud. The server executable may be based of cava, complied C.C++ code. The core- network is extended to provide end-user with cloud service execution and the cloud infrastructure is 0065ended with functionality for deployment of the server executables. Thus, embodiments herein may e.g. relate to Cloud service support in Mobile Core Network and cloud infrastructure.

Figure 1 depicts a wireless communications network 100 in which embodiments herein may be implemented. The wireless communications network 100 is a radio network such as an GSM, LTE, a WCDMA, Fifth Generation (5G), a Wimax, or any cellular network or system. The a wireless communications network 100 e.g. comprises a core network and a radio access network.

A cloud 105 is used in the wireless communications network 100 for cloud services.

The cloud 105 comprises a cloud architecture 110 comprising one or more operating systems (OS) such as a laaS OS and a Guest OS. The cloud architecture 1 10 may supports laaS and/or PaaS services. The cloud 105 may support execution of the C- Apps which are uploaded to the cloud 105 based on an App in the clients requests.

Needed function and Application Programming Interface (API) is developed to support the execution. Many API:s already exists for Cloud-execution see e.g.

http://cloudfoundry.org/index.html. The main difference is that the code is delivered by the App in the Client to the Cloud. Usually, the executable or program code is installed separately by provisioning. Cloud foundry is mainly a PaaS architecture where the GuestOs is used as a platform for the PaaS-service. The proposed laaS architecture let's the C-App to have API:s directly into the operating system. The App may be designed in C++ and utilize operating system calls. In both of the example cloud platform, these cloud resources are exposed to a client to run C-app application. In some embodiments, the cloud 102 further comprises a cloud resource manager

115 for booking and admittance of Cloud resources. The a cloud resource manager 1 15 may be a part of a cloud orchestration function of the cloud. Cloud orchestration describes the automated arrangement, coordination, and management of clouds. A number of user equipments operate in the wireless communications network 100. In the example scenario of Figure 1 , only one user equipment is shown for simplicity, a user equipment 120 which is located in the cell 1 15 served by the network node 110. The user equipment 120, may e.g. be a mobile wireless terminal, a mobile phone, a 5 computer such as e.g. a laptop, or tablet computer, sometimes referred to as a surf plate, with wireless capabilities, or any other radio network unit capable to communicate over a radio link in a wireless communications network. Please note the term user equipment used in this document also covers other wireless terminals such as Machine to Machine (M2M) devices. The user equipment 120 may also be referred to as a host or a client and

10 comprises an OS and a number of applications denoted App. The user equipment 120 is a user device where one or more Applications denoted App. In the figure such as e.g. IOS or Android Apps are executing. The App in the user equipment 120 may also store an embedded Cloud Application (C-App).

A C-App is a piece of software that can be executed into the cloud 105. It is either a

15 software designed for PaaS-environment or an laaS-application composed of a set of images executing as one or more Virtual Machines (VM)s. The C-App may e.g. be stored as a part of the Client Application such as the user equipment 120 or into a separate cloud application server 130.

20 An example of such cloud application server 130 for storing C-Apps is a an app- repository server. The A separate server for C-Apps that may e.g. be located within the Internet 135 or be part of an operator infrastructure. In Figure 1 showing a location within the Internet 135.

Further, the wireless communications network 100 comprises a charging system 25 140. To be able to provide a valuable cloud service end-user service, a charging must be performed. Both on-line, i.e. pre-paid and off-line, i.e. post-paid charging may be supported.

Further, and end-user policy server 145 is used in the wireless communications network 100. The end-user policy server 145 may be an end-user policy, Policy and 30 Charging Rules Function (PCRF). If an end-user such as user of the user equipment 120 pays for a cloud service, he should be able to use it. The end-user policy server 145 e.g. checks if the end-user such as the user equipment 120 has any one out of:

Access right to Cloud resources in the cloud 105.

Cloud Quota limits for C-Apps. Cloud Quota limits refer to that the cloud resource 35 may be limited for the end-user C-apps. Resources for Java-VM, PaaS or laaS. E.g. checks if the service is Java code, PaaS or laaS code.

According to embodiments herein a cloud service is provided that lets cloud applications (apps) run into a cloud of an operator. These apps may e.g. be based on laaS or PaaS. In the PaaS-case, the software may be JAVA-code executed in a JAVA- Virtual Machine (JVM) environment.

Due to the fact that the cloud applications are "unknown" to the operators, these cloud applications are referred to as basic resource requirements such as e.g. storage, memory and CPU requirements. These resources must then be admitted by a charging system and supported by the Cloud of the operator.

A general architecture of the cloud 105 is either when the C-App resides in the user equipment 120 such as a part of the Client of the user equipment 120, or when the source code of the C-App resides within a C-App storage 130 in the Internet 135.

The main part of a Mobile Core Network has to act both with the policy server, charging and cloud.

The major important components of the architecture will be described below. Embodiments herein will first be described in a general way in a flow chart of Figure

2 as seen from a view of the user equipment 120. After, a general description related to a sequence diagram in Figure 3 seen from an overview of the wireless communication system 100 will follow. Further, after the general description a more detailed description will follow.

Example embodiments of a method performed by the end-user policy server 145 for handling a cloud service in a cloud 105 will now be described with reference to a flowchart depicted in Figure 2. As mentioned above the end-user policy server 145 operates in the wireless communications network 100.

The method comprises the following actions, which actions may be taken in any suitable order. Dashed lines of some boxes in Figure 2 indicate that this action is not mandatory. In an example scenario, the user equipment 120 requires to use a cloud service in the cloud 105. The service may e.g. be a temporary storage of database object, rendering for complex object from a browser or augmented reality Action 201

The end-user policy server 145 receives a request for the cloud service from the user equipment 120.

As mentioned above, in some embodiments the cloud resource manager 1 15 operates in the cloud 105. In these embodiments, the request for the cloud service further is sent to the cloud resource manager 115 via the end-user policy server 145. Thus there are some other embodiments where no cloud resource manager is present in the cloud 105.

The request for the cloud service may be represented by any one out of:

A DNS-request, an explicit activation message, and an implicit request for the cloud service when the user equipment 120 is attached to the wireless communications network 100. Action 202

In some embodiments the cloud application is stored in the user equipment 120. In these embodiments, the user equipment 120 downloads the cloud application into the cloud 105, when the user equipment 120 fulfils the end-user policy according to the end- user policy server 145 and the resources for the cloud service are available.

Action 203

When the user equipment 120 fulfils an end-user policy according to the end-user policy server 145, the end-user policy server 145 sends an instruction to the charging system 140, to activate a charging of the cloud service. Since embodiments herein relates to specifically charging per end-user, the charging is related to the user equipment 120. The charging may be performed by the core network. In some embodiments wherein the C-App is free of charge, the activation of the charging is set to zero.

In some embodiments wherein the cloud resource manager 115 operates in the cloud 105, the end-user policy server 145 may performed the sending of the instruction to the charging system 140 to activate a charging of the cloud service, when further, resources for the cloud service are available in the cloud according to the cloud resource manager 1 15.

The user equipment 120 fulfils the end-user policy may comprise when any one or more out of:

- the user equipment 120 has access right to cloud resources, - the user equipment 120 is associated with a cloud resource limitation for the cloud,

- the user equipment 120 has associated resources for Java Virtual Machine, JVM, or Infrastructure as a Service, laaS, PaaS, when the cloud service is related to Java code or laaS code respectively.

5 The charging of the cloud service may be time based charging for pre-paid

charging, also referred to as on-line charging or post-paid charging , also referred to as offline charging. The charging of the cloud service may be based on any one or more out of: resource categories, type of cloud, time used, and standby charge.

10 Action 204

The user equipment 120 then executes the cloud service in the cloud 105.

Action 205

The executing cloud service in the cloud 105 may then be suspended. In that case, 15 the end-user policy server 145 receives from the user equipment 120, a suspend request for the cloud service to the end-user policy server 145.

Action 206

The end-user policy server 145 then sends an instruction to the charging system 20 140, to de-activate the charging of the cloud service.

Example embodiments of a method performed in the wireless communications network 100 for handling a cloud service in a cloud 105, will now be described with 25 reference to a sequence diagram depicted in Figure 3a and 3b. Actions 301-306 is

depicted in Figure 3a and Actions 307-311 is depicted in Figure 3b. As mentioned above, the cloud service is to be provided to the user equipment 120 operating in the wireless communications network 100.

The method comprises the following actions, which actions may be taken in any 30 suitable order. In an example scenario, the user equipment 120 wishes to use a cloud service in the cloud 105.

Action 301 The user equipment 120 sends 301 a request for the cloud service to the end-user policy server 145. For example the C App is requesting a cloud service memory, Central Processing Unit (CPU), and storage, to be used for the cloud service.

This action relates to Action 201 above.

Action 302

Upon receiving the request for the cloud service, the end-user policy server 145 checks whether the user equipment 120 fulfils an end-user policy.

The checking whether the user equipment 120 fulfils an end-user policy comprises any one or more out of: checking whether the user equipment 120 has access right to cloud resources, checking whether the user equipment 120 is associated with a cloud resource limitation for the cloud, checking whether the user equipment 120 has resources for Java Virtual Machine, JVM, or Infrastructure as a Service, laaS, when the cloud service is related to Java code or laaS code respectively.

This means that the end-user policy server 145 may admit or deny the user equipment 120 to use the cloud resources based on the policies. If ok, go to the next

Action.

Action 303

In some embodiments, the cloud resource manager 1 15 operates in the cloud 105.

In these embodiments the end-user policy server 145 may checks with the cloud resource manager 115 whether resources for the cloud service is available in the cloud 105.

The required resources are checked with the Cloud resource manager 1 15 such that these are available for the user equipment 120. If ok, go to the next action.

Action 304

When the user equipment 120 fulfils the end-user policy according to the end-user policy server 145, the cloud application is downloaded into the cloud 105. The C-Apps may e.g. be Java-VM or an laaS image. The C-App may be downloaded from a C-App repository or be a part of the App of the user equipment.

Thus, the cloud application may be stored in the user equipment 120, in that case the downloading of the cloud application into the cloud 105 is performed by the user equipment 120. As an alternative, the cloud application is stored in a cloud application server 130 at the Internet 135. The downloading of the cloud application into the cloud 105 may then be performed by a node in the cloud 105.

This action relates to Action 202 above.

Action 305

The end-user policy server 145 then sends an instruction to a charging system 140 to activate a charging of the cloud service, which charging is related to the user equipment 120. This means that the charging system140 is activated during the execution into the cloud 105. A combination of costs for Cloud resources memory, processing, network and time-duration and bucket is done for the results into the charging fee.

In the embodiments wherein the cloud resource manager 1 15 operates in the cloud 105, end-user policy server 145 may perform the sending of the instruction to the charging system 140 to activate a charging of the cloud service when further, resources for the cloud service are available in the cloud according to the cloud resource manager 115.

In some embodiments wherein the C App is free of charge, the activation of the charging is set to zero.

This action relates to Action 203 above. Action 306

The user equipment 120 downloads executable of the cloud service into the cloud

105.

This action relates to Action 204 above. Action 307

The executing cloud service in the cloud 105 may then be suspended. In that case the user equipment 120 sends a suspend request for the cloud service to the end-user policy server 145.

This action relates to Action 205 above.

Action 308

Upon receiving the suspend request for the cloud service, the end-user policy server 145 sends an instruction to the cloud resource manager 1 15. The instruction instructs the cloud resource manager 1 15 to suspend the executing cloud service in the cloud 105. Action 309

The end-user policy server 145 sends an instruction to the charging system 140, to de-activate the charging of the cloud service.

This action relates to Action 206 above.

Action 310

In some embodiments wherein the executing cloud service in the cloud 105 is to be suspended, the cloud resource manager 115 may store in a cloud application storage, any image or java code together with session parameters related to the cloud service in the cloud 105.

Action 311

The cloud resources related to the cloud service is then released. This may be performed by the resource manager 1 15.

Embodiment's herein will now be described and explained more in detail. The text below is applicable to and may be combined with any suitable embodiment described above.

Operation of the method

Detailed sequence diagram for the different step is depicted in Figure 3a and b above. The details are described sequence is the details of different steps. Note that any of these step may be merged together or taken in a different order.

Request for cloud, related to Action 201 and 301.

The request for cloud service to the end-user policy server 145 may be sent in many ways, whereof some examples are described here.

One example is to send a Domain Name Server (DNS)-request. The application or the C-App in the user equipment 120 accesses a certain server on internet or in the operator network i.e. web-server. The C-App is an internally stored server application in the user equipment 120. The DNS-request is checked by the core network e.g. a Packet Data Network Gateway (PDN-GW) and the DNS-request may be identified as a request for a cloud service and thus implicitly have generated a request for Cloud Service. Another example is to send an explicit activation message of Cloud Service. A client such as the user equipment 120 may use a default DNS-name e.g. a Fully Qualified Domain Name (FQDN) to find the appropriate cloud policy server such as the end-user Policy server 145. In this case the client such as the user equipment 120, uses a two-step 5 approach, wherein the first step is to generate a DNS-request and get an IP-address to the cloud policy server such as the End-user Policy server 145, and wherein the second step is to generate a request to the cloud policy server such as the End-user Policy server 145.

A further example is to implicitly request for cloud service to the end-user policy 10 server 145 at attach. The activation may be made when the user equipment 120 is

attached to wireless access to the communications network 100. This may be performed by a set of default applications that are established at the attach.

A yet further example is to use Deep Packet Inspection DPI. The activation may be made upon DPI-detection on a specific Uniform Resource Locator (URL) for the client 15 such as the user equipment 120. In this case, the binding between applications and the Cloud request must be made on the detected DPI-information.

End-user Policy PCRF, related to Action 302

The End-user Policy server 145 checks if the end-user such as the user equipment 20 120 fulfils an end-user policy by checking if the user equipment 120 has e.g.:

-Access to the cloud 105. The End-user Policy server 145 checks whether the end- user such as the user equipment 120 have access right to cloud resources?

-Cloud Quota limits for C-Apps. The cloud resource may e.g. be limited for C-apps of the user equipment 120.

25 -Resources for Java-VM or laaS. The End-user Policy server 145 checks if the

service is Java coded or laaS coded.

End-user Policy PCRF, related to Action 303

The End-user Policy server 145 further checks whether any resources for the 30 requested cloud service are available. This may be performed by checking the allocation of CU resource in the Cloud and/or allocation of a share of resources in the Cloud.

Download of C-apps, related to Action 202 and 304 The C-App may e.g. be downloaded from a selected C-App server such as a C-App server of the operator, a C-app server from Internet 135 such as the C-App storage 130 or from a client such as the user equipment 120.

Security i.e. DRM-protection of the C-App may be performed if the C-App is stored within Internet 135. In some embodiments, the C-App server is found by means of DNS, by assigning a specific FQDN for the C-App server. A DNS-request (FQDN) is sent and the replied IP-addresses pointing at the C-app server.

Activation of charging, related to Action 203 and 305

The charging for charging of cloud service may be time-based charging both for prepaid also referred to as on-line charging, and post-paid charging also referred to as offline charging. The cloud service may e.g. be based on:

- Resource categories such as e.g. storage, process, and CPU. The resource may be quantified in resource classes where the max limits are related to the cost such as e.g.

laaS: 10Gbyte storage, One CPU-core, 1GB memory=> XX cost laaS: 1 Gbyte storage, One CPU-core, 0.5GB memory=> YY cost PaaS: One Java VM, 10M memory...=> ZZ

- laaS or PaaS. In this case the charging may be dependent on type of cloud.

- Time used, i.e. charging for the time using the cloud. This implies that the end-user such as the user equipment 120 may activate the cloud and then suspend the usage for a time period. This is an advantage for pre-paid services.

- Standby charge. If the user equipment 120 is using the cloud service sporadically, the user equipment 120 may activate and re-establish its C-App. For this case a standby charge may be applied.

Cloud service execution, related to Action 204 and 306

The main part of the start-up of the execution of the cloud service may be to let the C-App execute and at the same time enabling the time-based charging. De-activation of processing i.e. De-attach of connectivity

In this example above the suspending the execution may be made due to the user equipment 120 has lost the connectivity to the wireless communications network 100.

However, it may also be other reasons for stop execution such as e.g.:

- C-Apps have not been used by the user equipment 120 for a while and an automatic time-out has been activated. - The pre-paid quota has become out-of-quota. Quota here means allocated resources. The processing may be suspended due to "out-of-quota".

- End-user manual de-activation of the execution.

- An application in the client makes an explicit request for de-activation.

Suspend execution, related to Action 205, 307 and 308

An explicit suspend request for deactivating the execution of the C-App may be sent to the cloud 105 via the End-user Policy server 145, which End-user Policy server 145 in turn instructs cloud resource manager 1 15 to suspend cloud service.

This means that the processing of the cloud service stops and the session variables may be captured and stored together with the java-code image in the C-app storage.

De-activation of Charging for the cloud service, related to Action 206 and 309

The current charging may be de-activated when the C-App execution is suspended and a charging for standby operation may be needed e.g. when the execution has been suspended,.

Storage of C-app, related to Action 310

The java code image together with session parameters may be stored in the C-App storage.

Release of cloud resources, related to Action 311

Allocated and used cloud resources are de-allocated and e.g. assigned to an unused pool of resources.

To perform the method actions for handling a cloud service in the cloud 105 described above in relation to Figure 2 and 3, the end-user policy server 145 may comprise the following arrangement depicted in Figure 5. As mentioned above. The end- user policy server 145 is arranged to operate in the wireless communications network 100.

The end-user policy server 145 is configured to, e.g. by means of a receiving module 500 configured to, receive a request for the cloud service from the user equipment 120. The request for the cloud service may be represented by any one out of: a DNS- request, an explicit activation message, and an implicit request for the cloud service when the user equipment 120 is attached to the wireless communications network 100. The end-user policy server 145 is further configured to, e.g. by means of a sending module 520 configured to, send an instruction to a charging system 140 to activate a charging of the cloud service, when the user equipment 120 fulfils an end-user policy according to the end-user policy server 145. The charging is related specifically to the user equipment 120.

The user equipment 120 may further be configured to fulfil the end-user policy comprises when any one or more out of:

- the user equipment 120 has access right to cloud resources,

- the user equipment 120 is associated with a cloud resource limitation for the cloud,

- the user equipment 120 has associated resources for Java Virtual Machine, JVM, or Infrastructure as a Service, laaS, when the cloud service is related to Java code or laaS code respectively.

In some embodiments, a cloud resource manager 115 is arranged to operate in the cloud 105. In these embodiments, the request for the cloud service may further be sent to the cloud resource manager 115 via the end-user policy server 145.

The end-user policy server 145 may further be configured to e.g. by means of the sending module 520 configured to, send an instruction to a charging system 140, to activate a charging of the cloud service, which is performed when further, resources for the cloud service are available in the cloud according to the cloud resource manager 115.

The charging of the cloud service may be arranged to be time based charging for pre-paid charging or post-paid charging.

The charging of the cloud service may be arranged to be based on any one or more out of: resource categories, type of cloud, time used, and standby charge.

The executing cloud service in the cloud 105 may be to be suspended. The end- user policy server 145 may further be configured to e.g. by means of the receiving module 500 configured to send a suspend request for the cloud service to the user equipment 120, and to send an instruction, e.g. through module 520, to the charging system 140, to de-activate the charging of the cloud service. The receiving module 500 and the sending module 520 may be comprised in a wireless transceiver of the end-user policy server 145.

The user equipment 120 may be configured to, e.g. by means of a executing

5 module 420 depicted in Figure 4 configured to, execute the cloud service in the cloud.

In some embodiments, a cloud application is configured to be stored in the user equipment 120. In these embodiments, the user equipment 120 may further be configured to, e.g. by means of a downloading module 430 depicted in Figure 4 configured to, 10 download the cloud application into the cloud 105 when the user equipment 120 fulfils the end-user policy according to the end-user policy server 145 and the resources for the cloud service are available.

15 The embodiments herein comprising the process of handling a cloud service in the cloud 105 may be implemented through one or more processors, such as a processor 530 in end-user policy server 145 depicted in Figure 4, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance

20 in the form of a data carrier carrying computer program code for performing the

embodiments herein when being loaded into the end-user policy server 145. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the end-user policy server

25 145.

The end-user policy server 145 may further comprise a memory 540 comprising one or more memory units. The memory 450 comprises instructions executable by the processor 440.

30 The memory 450 is arranged to be used to store e.g. applications, the C-App,

information about local service clouds, data, configurations, and applications to perform the methods herein when being executed in the user equipment 120.

Those skilled in the art will also appreciate that the an sending module 410, 35 executing module 420, and downloading module 430, described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in the memory 450, that when executed by the one or more processors such as the processor 440 as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application- Specific Integrated Circuitry (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).

To perform the method actions for handling a cloud service in a cloud 105 in relation to Figure 1 , 3a, 3b, the wireless communications network 100 may comprise the following arrangement as depicted in Figure 4, Figure 5 Figure 6 and Figure 7. As mentioned above, the cloud service is to be provided to the user equipment 120 operating in a wireless communications network 100, and the cloud 105 is arranged to be comprised in the wireless communications network 100.

In the wireless communications network 100, the following is arranged:

The user equipment 120 is configured to send a request for the cloud service to an end-user policy server 145.

The end-user policy server 145 is configured to send to the user equipment 120, an instruction to a charging system 140 to activate a charging of the cloud service when the user equipment 120 fulfils an end-user policy according to the end-user policy server 145. The charging is related to the user equipment 120.

The end-user policy server 145 may further be configured to send the instruction to the charging system 140, to activate a charging of the cloud service when further, resources for the cloud service are available in the cloud according to the cloud resource manager 1 15.

The user equipment 120 may further be configured to download the cloud service into the cloud 105.

In some embodiments, the cloud application is arranged to be stored in the user equipment 120. In these embodiments, the user equipment 120 is further configured to download the cloud application into the cloud 105.

The executing cloud service in the cloud 105 may be suspended. The user equipment 120 may further be configured to send a suspend request for the cloud service to the end-user policy server 145. The end-user policy server 145 is configured to send an instruction to the charging system 140, to de-activate the charging of the cloud service.

The end-user policy server 145 is configured to, e.g. by means of an checking 5 module 510 configured to, check whether the user equipment 120 fulfils an end-user policy.

In some embodiments, the cloud resource manager 115 is arranged to operate in the cloud 105. In these embodiments, the end-user policy server 145 further is configured to, e.g. by means of the checking module 510 configured to, check with the cloud

10 resource manager 115 whether resources for the cloud service is available in the cloud 105. The checking module 510 in the end-user policy server 145 is depicted in Figure 5.

The end-user policy server 145 is configured to, e.g. by means of the checking module 510 configured to, check whether the user equipment 120 fulfils an end-user policy according to any one or more out of: checking whether the user equipment 120 has

15 access right to cloud resources, checking whether the user equipment 120 is associated with a cloud resource limitation for the cloud, checking whether the user equipment 120 has resources for Java Virtual Machine, JVM, or Infrastructure as a Service, laaS, when the cloud service is related to Java code or laaS code respectively. The checking module 510 in the end-user policy server 145 is depicted in Figure 5.

20 The end-user policy server 145 may further be configured to, e.g. by means of an sending module 520 configured to, send an instruction to the cloud resource manager 1 15. The instruction instructs the cloud resource manager 1 15 to suspend the executing cloud service in the cloud 105. The sending module 520 in the end-user policy server 145 is depicted in Figure 5.

25

Any one out of a node in the cloud 105 and the user equipment 120 is configured to e.g. by means of an downloading module 610 configured to or the by means of the downloading module 430 configured to, download a cloud application into the cloud 105, when the user equipment 120 fulfils an end-user policy according to the end-user policy 30 server 145. The downloading module 610 in the node in the cloud 105 is depicted in

Figure 6 and the downloading module 430 in the user equipment 120 is depicted in Figure 4.

In some embodiments, the cloud application is arranged to be stored in the cloud application server 130 at the Internet 135. In these embodiments, the node in the cloud 35 105 may be configured to e.g. by means of the downloading module 610 configured to, download the cloud application into the cloud 105 is performed by a node in the cloud 105. The downloading module 610 in the node in the cloud 105 is depicted in Figure 6.

The node in the cloud 105 may be configured to, e.g. by means of a releasing module 620 configured to, release the cloud resources related to the cloud service. The 5 releasing module 620 in the node in the cloud 105 is depicted in Figure 6.

The cloud resource manager 115 may further be configured to, e.g. by means of an storing module 710 configured to, store in a cloud application storage any image or java code together with session parameters related to the cloud service in the cloud 105, when 10 the executing cloud service in the cloud 105 is to be suspended. The storing module 710 in the cloud resource manager 115 is depicted in Figure 7.

The embodiments herein comprising the process of for handling a cloud service in a cloud 105, may be implemented through one or more processors, such as the processor

15 440 in the user equipment 120 depicted in Figure 4, a processor 530 in the end-user policy server 145 depicted in Figure 5, a processor 630 in the node in the cloud 105 depicted in Figure 6, and as the processor 720 in the cloud resource manager 115 depicted in Figure 7, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be

20 provided as a computer program product, for instance in the form of a data carrier

carrying computer program code for performing the embodiments herein when being loaded into the user equipment 120, the end-user policy server 145, the node in the cloud 105 and/or the cloud resource manager 115. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The

25 computer program code may furthermore be provided as pure program code on a server and downloaded to the user equipment 120, the end-user policy server 145, the node in the cloud 105 and/or the cloud resource manager 1 15.

The the user equipment 120, the end-user policy server 145, the node in the cloud 30 105 and/or the cloud resource manager 115 may further comprise a respective memory comprising one or more memory units, such as such as the memory 450 in the user equipment 120 depicted in Figure 4, a memory 540 in the end-user policy server 145 depicted in Figure 5, a memory 640 in the node in the cloud 105 depicted in Figure 6, and a memory 730 in the cloud resource manager 1 15 depicted in Figure 7. The the memory 35 450 comprises instructions executable by the processor 440, the memory 540 comprises instructions executable by the processor 530, the memory 640 comprises instructions executable by the processor 630 and the memory 730 comprises instructions executable by the processor 720. Those skilled in the art will also appreciate that the modules in the the user equipment 120, the end-user policy server 145, the node in the cloud 105 and/or the cloud resource manager 1 15 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in the the memory 450 in the user equipment 120, the memory 540 in the end- user policy server 145, the memory 640 in the node in the cloud 105, and/or the memory 730 in the cloud resource manager 1 15, that when executed by the one or more processors such as the processors 440, 530, 630 and/or 720 as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).

Claims

A method performed by an end-user policy server (145), for handling a cloud service in a cloud (105), which end-user policy server (145), operates in a wireless communications network (100), the method comprising:

receiving (201) a request for the cloud service from a user equipment (120), when the user equipment (120) fulfils an end-user policy according to the end-user policy server (145), sending (203) an instruction to a charging system (140), to activate a charging of the cloud service, which charging is related to the user equipment (120).

The method according to claim 1 , wherein a cloud resource manager (115) operates in the cloud (105), wherein the request for the cloud service further is sent to the cloud resource manager (115) via the end-user policy server (145), and

wherein sending (203) an instruction to a charging system (140), to activate a charging of the cloud service, is performed when further, resources for the cloud service are available in the cloud according to the cloud resource manager (1 15).

The method according to any of the claims 1-2, wherein the user equipment (120) fulfils the end-user policy comprises when any one or more out of:

- the user equipment (120) has access right to cloud resources,

- the user equipment (120) is associated with a cloud resource limitation for the cloud,

- the user equipment (120) has associated resources for Java Virtual Machine, JVM, or Infrastructure as a Service, laaS, when the cloud service is related to Java code or laaS code respectively.

The method according to any of the claims 1-3, wherein the request for the cloud service is represented by any one out of:

a DNS-request, an explicit activation message, and an implicit request for the cloud service when the user equipment (120) is attached to the wireless communications network (100).

5. The method according to any of the claims 1-4, wherein charging of the cloud service is time based charging for pre-paid charging or post-paid charging.

The method according to any of the claims 1-5,

wherein charging of the cloud service is based on any one or more out of: resource categories, type of cloud, time used, and standby charge.

The method according to any of the claims 2-6, wherein the executing cloud service in the cloud (105) is to be suspended, the method further comprising

receiving (205) a suspend request for the cloud service from a user equipment (120) and

sending (206) an instruction to the charging system (140), to de-activate the charging of the cloud service.

A method performed in a wireless communications network (100) for handling a cloud service in a cloud (105), which cloud service is to be provided to a user equipment (120) operating in a wireless communications network (100), the method comprising:

sending (301) by the user equipment (120), a request for the cloud service to an end-user policy server (145),

checking (302) by the end-user policy server (145), whether the user equipment (120) fulfils an end-user policy,

when the user equipment (120) fulfils an end-user policy according to the end-user policy server (145), the method further comprising:

downloading (304) a cloud application into the cloud (105),

sending (305) by the end-user policy server (145), an instruction to a charging system (140) to activate a charging of the cloud service, which charging is related to the user equipment (120).

The method according to claim 8, wherein a cloud resource manager (115) operates in the cloud (105), the method further comprising:

checking (303) by the end-user policy server (145) with the cloud resource manager (115) whether resources for the cloud service is available in the cloud

(105), and wherein sending (305) by the end-user policy server (145), the instruction to the charging system (140), to activate a charging of the cloud service, is performed when further, resources for the cloud service are available in the cloud according to the cloud resource manager (1 15).

10. The method according to any of the claims 10-11 , further comprising:

downloading (306) by the user equipment (120) executable of the cloud service into the cloud (105).

1 1. The method according to any of the claims 8-9, wherein the cloud application is stored in the user equipment (120), and wherein the downloading (304) the cloud application into the cloud (105) is performed by the user equipment (120).

12. The method according to any of the claims 8-10, wherein the cloud application i stored in a cloud application server (130) at the Internet (135), and wherein downloading (304) the cloud application into the cloud (105) is performed by a node in the cloud (105).

13. The method according to any of the claims 8-1 1 , wherein checking (302) whether the user equipment (120) fulfils an end-user policy comprises any one or more out of: checking whether the user equipment (120) has access right to cloud resources, checking whether the user equipment (120) is associated with a cloud resource limitation for the cloud, checking whether the user equipment (120) has resources for Java Virtual Machine, JVM, or Infrastructure as a Service, laaS, when the cloud service is related to Java code or laaS code respectively.

14. The method according to any of the claims 8-12, wherein the executing cloud

service in the cloud (105) is to be suspended, the method further comprising

sending (307) by the user equipment (120), a suspend request for the cloud service to the end-user policy server (145),

sending (309) by the end-user policy server (145)_an instruction to a charging system (140), to de-activate the charging of the cloud service, and

releasing (311) the cloud resources related to the cloud service.

15. The method according to any of the claims 8-14, further comprising: sending (308) by the end-user policy server (145), an instruction to the cloud resource manager (1 15), which instruction instructs the cloud resource manager (115) to suspend the executing cloud service in the cloud (105).

16. The method according to any of the claims 8-15, wherein the executing cloud

service in the cloud (105) is to be suspended, the method further comprising

storing (310) in a cloud application storage by the cloud resource manager (115), any image or java code together with session parameters related to the cloud service in the cloud (105).

17. A end-user policy server (145), for handling a cloud service in a cloud (105), which user equipment (120) is arranged to operate in a wireless communications network (100), the user equipment (120) being configured to:

receive a request for the cloud service from a user equipment (120), and send an instruction to a charging system (140) to activate a charging of the cloud service when the user equipment (120) fulfils an end-user policy according to the end-user policy server (145), which charging is related to the user equipment (120).

18. The end-user policy server (145), according to claim 17, wherein a cloud resource manager (1 15) is arranged to operate in the cloud (105), wherein the request for the cloud service further is to be sent to the cloud resource manager (115) via the end-user policy server (145), and

wherein the end-user policy server (145) is configured to send an instruction to a charging system (140), to activate a charging of the cloud service, is performed when further, resources for the cloud service are available in the cloud according to the cloud resource manager (115).

19. The end-user policy server (145), according to any of the claims 17-18, wherein the user equipment (120) is configured to fulfil the end-user policy comprises when any one or more out of:

- the user equipment (120) has access right to cloud resources,

- the user equipment (120) is associated with a cloud resource limitation for the cloud, - the user equipment (120) has associated resources for Java Virtual Machine, JVM, or Infrastructure as a Service, laaS, when the cloud service is related to Java code or laaS code respectively.

20. The end-user policy server (145), according to any of the claims 17-19, wherein the request for the cloud service is represented by any one out of:

21. The end-user policy server (145), according to any of the claims 17-20,

wherein charging of the cloud service is arranged to be time based charging for pre-paid charging or post-paid charging.

22. The end-user policy server (145), according to any of the claims 17-21 ,

wherein charging of the cloud service is arranged to be based on any one or more out of: resource categories, type of cloud, time used, and standby charge.

23. The end-user policy server (145), according to any of the claims 17-22, wherein the executing cloud service in the cloud (105) is to be suspended, and wherein the user equipment (120) further is configured to:

receive (205) a suspend request for the cloud service from a user equipment (120), and

send an instruction to the charging system (140), to de-activate the charging of the cloud service.

24. A wireless communications network (100) for handling a cloud service in a cloud (105), which cloud service is to be provided to a user equipment (120) operating in a wireless communications network (100), and which cloud (105) is arranged to be comprised in the wireless communications network (100), in which wireless communications network (100):

the user equipment (120) is configured to send a request for the cloud service to an end-user policy server (145),

the end-user policy server (145) is configured to check whether the user equipment (120) fulfils an end-user policy, wherein any one out of: a node in the cloud (105) and the user equipment (120) is configured to download a cloud application into the cloud (105), when the user equipment (120) fulfils an end-user policy according to the end-user policy server (145), and

wherein end-user policy server (145), is further configured to send by the user equipment (120), an instruction to a charging system (140) to activate a charging of the cloud service when the user equipment (120) fulfils an end-user policy according to the end-user policy server (145), which charging is related to the user equipment (120).

25. The wireless communications network (100) according to claim 24, wherein a cloud resource manager (1 15) is arranged to operate in the cloud (105), wherein:

the end-user policy server (145) further is configured to check with the cloud resource manager whether resources for the cloud service is available in the cloud (105), and

wherein the end-user policy server (145), is further configured to send, the instruction to the charging system (140), to activate a charging of the cloud service when further, resources for the cloud service are available in the cloud according to the cloud resource manager (1 15).

26. The wireless communications network (100) according to any of the claims 24-25, wherein the user equipment (120) is further configured to download executable into the cloud service in the cloud (105).

27. The wireless communications network (100) according to any of the claims 24-26, wherein the cloud application is arranged to be stored in the user equipment (120), and wherein the user equipment (120) is further configured to download the cloud application into the cloud (105).

28. The wireless communications network (100) according to any of the claims 24-27, wherein the cloud application is arranged to be stored in a cloud application server (130) at the Internet (135), and wherein a node in the cloud is configured to download the cloud application into the cloud (105) is performed by a node in the cloud (105).

29. The wireless communications network (100) according to any of the claims 24-28, wherein the end-user policy server (145) is configured to check whether the user equipment (120) fulfils an end-user policy according to any one or more out of: checking whether the user equipment (120) has access right to cloud resources, checking whether the user equipment (120) is associated with a cloud resource limitation for the cloud, checking whether the user equipment (120) has resources for Java Virtual Machine, JVM, or Infrastructure as a Service, laaS, when the cloud service is related to Java code or laaS code respectively.

30. The wireless communications network (100) according to any of the claims 24-29, wherein the executing cloud service in the cloud (105) is to be suspended, and wherein the user equipment (120) is further configured to send a suspend request for the cloud service to the end-user policy server (145), and

the end-user policy server (145), is further configured to send an instruction to a charging system (140), to de-activate the charging of the cloud service, and wherein a node in the cloud (105) is configured to release the cloud resources related to the cloud service.

31. The wireless communications network (100) according to any of the claims 24-30, wherein:

the end-user policy server (145) further is configured to send an instruction to the cloud resource manager (1 15), which instruction instructs the cloud resource manager (1 15) to suspend the executing cloud service in the cloud (105).

32. The wireless communications network (100) according to any of the claims 24-31 , wherein the executing cloud service in the cloud (105) is to be suspended, and wherein the cloud resource manager (115) further is configured to

store in a cloud application storage (130) any image or java code