Methods, communication devices and network entities for aiding to provide communication-based services

Abstract

A method performed by a first communication device for aiding to provide a communication-based service to a second communication device is disclosed The method comprises receiving from the network entity, a request for availability to provide the communication-based service to the second communication device; and transmitting a first message, in response to confirming the availability to provide the communication-based service to the second communication device, to the network entity, the first message comprising a first token, wherein the first token is generated based on an anonymous identity of the first communication device, a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communication- based service.

Description

METHODS, COMMUNICATION DEVICES AND NETWORK ENTITIES FOR AIDING TO PROVIDE COMMUNICATION-BASED SERVICESTECHNICAL FIELD

[0001] The present disclosure relates generally to methods, communication devices and network entities for aiding to provide communication-based services. The present disclosure further relates to computer programs and carriers corresponding to the methods, communication devices and network entities.BACKGROUND

[0002] Communication devices, e.g., enterprise routers, supporting connectivity to multiple networks and having computational resources, can be used for local processing. These communication devices can be utilized to build a decentralized cloud communication network solution that allows individuals and organizations which owns the communication devices to contribute their idle computational resources, such as a spare server in a data center or a mobile computational device, to another communication device which needs computational resources or communication-based service, via the multiple networks, and receive rewards in return for their contribution. The communication devices can be connected to each other over the multiple networks via communication service providers (CSPs) or other 3rd party-vendors. These communication devices which provide computational resources can expose information about their communication and computational capabilities via Aggregator services, which provide Application Programming Interface (API) to the communication device which needs communication-based service. The exposed information about the communication and computation capabilities can be corroborated with information from the mobile network, so as to enhance device-to-device computational distribution services. This arrangement complements the current device-to-edge offloading and will enable the proliferation of network-based device-to-device computational service offloading. In other words, an idle communication device can provide a communication-based service to another communication device, via Aggregator and CSP.

[0003] Referring to fig. 1a, a communication device 106 needs a communicationbased service. An edge computational platform 112 provides its resource to thecommunication device 106, and requires communication-based service via a CSP 110 to ensure connectivity performance. This is a device-to-edge offloading scenario, as mentioned above.

[0004] Referring to fig. 1b, another communication device 102 provides its idle resource to the communication device 106 for the communication-based service, via the CSP 110. The communication device 102 differs from the edge computational platform 112, since it is similar in its capabilities and characteristics to the device 106. An Aggregator 104 can be connected between the communication device 102 and the CSP 110, enabling the communication device 106 to access information and / or communication-based services related to the communication device 102 in API form. The present invention discusses the device-to-device communication-based service scenario which is shown in fig. 1 b.

[0005] When implementing the scenario shown in fig. 1b, it relies on a unique identifier of the communication device 102. The identifier of the communication device 102 can be specified by one of the following: phone number, IPv4 or IPv6 address, or network access identifier corresponding to the 3rd Generation Partnership Project Generic Public Subscription Identifier (3GPP GPSI) formatted external identifier, i.e. , {Local Identifier} @ {Domain Identifier}.

[0006] However, when utilizing the identifier of the communication device 102 in the ways mentioned above, privacy of the communication parties cannot be preserved.

[0007] In an existing technology presented at https: / / developer.vonage.com / en / api / qod, a Mobile Station International Subscriber Directory Number (MSISDN), e.g., a telephone number and / or the IP address associated with the communication device needs to be provided in the communication-based service request towards the aggregator 104.SUMMARY

[0008] As discussed above, a technical problem of the prior art is lacking mechanism to protect the privacy of the communication parties when setting up thecommunication-based service. It is an object of the invention to provide security and / or privacy during the communication-based service set-up phase. It is possible to achieve the object and others by using the methods, the communication devices, the network entities, and computer programs described herein as defined in the attached claims.

[0009] According to one aspect, a method performed by a first communication device for aiding to provide a communication-based service to a second communication device is disclosed, the first communication device being communicatively connected to a network entity of a communication network and a communication service provider, CSP, the network entity being communicatively connected to the second communication device and the CSP, the method comprising: receiving from the network entity, a request for availability to provide the communication-based service to the second communication device; transmitting a first message, in response to confirming the availability to provide the communication-based service to the second communication device, to the network entity, the first message comprising a first token, wherein the first token is generated based on an anonymous identity of the first communication device, a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communicationbased service.

[0010] According to another aspect, a method performed by a network entity for aiding to provide a communication-based service to a second communication device is disclosed, the first communication device being communicatively connected to the network entity and a communication service provider, CSP, the network entity being communicatively connected to the second communication device and the CSP, the method comprising: sending, to the first communication device, a request for availability to provide the communication-based service to the second communication device; receiving, a first message from the first communication device, the first message comprising a first token, wherein the first token is generated based on an anonymous identity of the first communication device, a network address of the communication-based service, authorization information related to thecommunication-based service, validity information related to the communicationbased service; transmitting a second message to the second communication device, the second message comprising a second token, wherein the second token is generated based on the first message, an identity of the second communication device and a profile of the communication-based service.

[0011] According to another aspect, a method performed by a second communication device for requesting a communication-based service from a first communication device is disclosed, the first communication device being communicatively connected to a network entity and a communication-based service provider, CSP, the network entity being communicatively connected to the second communication device and the CSP, the method comprising: receiving a second message from the network entity, the second message comprising a second token, wherein the second token is generated based on a first message, an identity of the second communication device and a profile of the communication-based service, wherein the first message comprising a first token, the first token is generated based on an anonymous identity of the first communication device, a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communicationbased service; transmitting a first communication-based service request in response to the second message, to the network entity.

[0012] According to another aspect, a first communication device for aiding to provide a communication-based service to a second communication device is disclosed, the first communication device being communicatively connected to a network entity of a communication network and a communication service provider, CSP, the network entity being communicatively connected to the second communication device and the CSP, the first communication device comprising a communication unit, a processing circuitry and a memory, said memory containing instructions executable by said processing circuitry, whereby the first communication device is operative to: receive from the network entity, a request for availability to provide the communication-based service to the second communication device; transmit a first message, in response to confirming the availability to provide thecommunication-based service to the second communication device, to the network entity, the first message comprising a first token, wherein the first token is generated based on an anonymous identity of the first communication device, a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communicationbased service.

[0013] According to another aspect, a network entity for aiding to provide a communication-based service to a second communication device is disclosed, the first communication device being communicatively connected to the network entity and a communication service provider, CSP, the network entity being communicatively connected to the second communication device and the CSP, the network entity comprising a communication unit, a processing circuitry and a memory, said memory containing instructions executable by said processing circuitry, whereby the network entity is operative to: send, to the first communication device, a request for availability to provide the communication-based service to the second communication device; receive, a first message from the first communication device, the first message comprising a first token, wherein the first token is generated based on an anonymous identity of the first communication device, a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communicationbased service; transmitting a second message to the second communication device, the second message comprising a second token, wherein the second token is generated based on the first message, an identity of the second communication device and a profile of the communication-based service.

[0014] According to another aspect, a second communication device for requesting a communication-based service from a first communication device is disclosed, the first communication device being communicatively connected to a network entity and a communication-based service provider, CSP, the network entity being communicatively connected to the second communication device and the CSP, the second communication device comprising a communication unit, a processing circuitry and a memory, said memory containing instructions executable by saidprocessing circuitry, whereby the second communication device is operative to: receive a second message from the network entity, the second message comprising a second token, wherein the second token is generated based on a first message, an identity of the second communication device and a profile of the communicationbased service, wherein the first message comprising a first token, the first token is generated based on an anonymous identity of the first communication device, a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communication-based service; transmit a first communication-based service request in response to the second message, to the network entity.

[0015] According to other aspects, computer programs and carriers are also provided, the details of which will be described in the claims and the detailed description.

[0016] With the solutions in the application, an improved security and privacy are provided to both parties when constructing a communication-based service between two communication devices. Further possible features and benefits of this solution will become apparent from the detailed description below.BRIEF DESCRIPTION OF DRAWINGS

[0017] The solution will now be described in more detail by means of exemplary embodiments and with reference to the accompanying drawings, in which:

[0018] Fig. 1a and 1 b are schematic block diagrams of device-to-edge offloading and device-to-device offloading.

[0019] Fig. 2 is a flow chart illustrating a method performed by a first communication device, according to exemplary embodiments.

[0020] Fig. 3 is a flow chart illustrating a method performed by a network entity, according to exemplary embodiments.

[0021] Fig. 4 is a flow chart illustrating a method performed by second communication device, according to exemplary embodiments.

[0022] Fig. 5 is a sequence diagram according to exemplary embodiments.

[0023] Figs. 6-8 are block diagrams illustrating the first communication device, the network entity and the second communication device in more detail, according to exemplary embodiments.DETAILED DESCRIPTION

[0024] As mentioned in the Background, fig. 1a shows a device-to-edge offloading scenario and fig. 1b shows a device-to-device offloading scenario. In fig. 1b, the communication device 102 can be any kind of device which has connectivity and computational capability to provide the computations to others in the network. For example, the communication device 102 may be a User Equipment (UE), a machine type UE or a UE capable of machine to machine (M2M) communication, a router, a sensor, a tablet, a mobile terminal, a smart phone, a laptop embedded equipped (LEE), a laptop mounted equipment (LME), a USB dongle, a Customer Premises Equipment (CPE) etc.

[0025] The communication device 102 can also be a connected vehicle belonging to the same vehicle original equipment manufacturer (OEM) when the communication device 106 is also a connected vehicle. The OEM can also manufacture the control units for handling the vehicle operations that are used in multiple models serving safety and other important features. There are examples of OEMs using this unit for helping other models of the same OEM regarding for example, the possibility of accidents and sharing the information. This feature can further be used for ordering or provisioning extra compute in case of autonomous driving, automated valet parking etc. that requires compute either on-device, edge or cloud.

[0026] The communication device 102 can also be a drone, or an unmanned aerial vehicle. Drones can share computational resources with trusted drones, which could also belong to other vendors. Therefore, this solution could also be applied when a drone or a bunch of drones are resource or compute hungry to carry out their operations. It should be possible for many drones belonging to different vendors to share compute amongst them without having to resort to actually having an exclusive subscription from an aggregator or third-party vendors.

[0027] The communication device 102 is also called the first communication device in this disclosure and corresponding to the first communication device 502 in fig. 5.

[0028] Similarly, the communication device 106 be any kind of device which has connectivity and computational capability to request for and get the computations done by others in the network. For example, the communication device 102 may be a User Equipment (UE), a machine type UE or a UE capable of machine to machine (M2M) communication, a router, a sensor, a tablet, a mobile terminal, a smart phone, a laptop embedded equipped (LEE), a laptop mounted equipment (LME), a USB dongle, a Customer Premises Equipment (CPE), a connected vehicle, a drone, etc.

[0029] The communication device 106 is also called the second communication device in this disclosure and corresponding to the second communication device 506 in fig. 5.

[0030] The CSP 110 is a network operator which provides network connection service to communication devices. Atypical CSP is e.g., Verizon, Vodafone. The CSP 110 is corresponding to the CSP 510 in fig. 5.

[0031] As mentioned in Background, by explicitly using a unique identifier of the communication device 102 when constructing a communication-based service for the communication device 106, the privacy of the parties cannot be preserved. To be specific, the solution in prior art requires that, for ordering / requesting a communication-based service from the communication device 106, the identity, e.g., MSISDN or source IP address, of the requestor communication device 106 and the IP address of the destination, i.e., the communication device 102, are known to each other, which does not preserve the privacy of the parties involved.

[0032] Furthermore, since the requirement of the communication-based service from the communication device 106 and the capability of the communication device 102 for providing the communication-based service are dynamic, it is challenging to set up the communication-based service between the two parties, as the communication device 102 needs to be pre-authorized, e.g., with an Aggregator 104, to provide the communication-based service. An Aggregator 104 is a platform / entitywhich enables integrating Network APIs from individual CSPs and exposing them to a broad ecosystem of developer platforms, including hyperscalers (HCPs), Communications Platform as a Service (CPaaS) providers, System Integrators (Sis) and Independent Software Vendors (ISVs).

[0033] The Aggregator 104 is also called a network entity in this disclosure and corresponding to for example the network entity 504 in fig. 5.

[0034] In addition, Application Programming Interface, API, provided by an Aggregator are available as application server-initiated procedures that offer the possibilities for application developers on the communication device 106 side to, for example, request a prioritized traffic for the communication-based service. From UE-initiated procedures, User equipment Route Selection Policy (URSP) is a mechanism that allowed the UE, i.e., the communication device 106, to determine the best / dedicate route for data transmission. These two different approaches, i.e., API and UE-initiated procedures, do not enable any UE-to-UE prioritized data flows, i.e., device-to-device data flow shown in fig. 5. Current solution focus only on UE to User Plane Function (UPF).

[0035] Therefore, it is required to provide a solution to construct a communicationbased service between two communication devices, while preserving privacy for the parties, in a pre-authorized way, and provide prioritized traffic for the service requestor.

[0036] The core idea of the present invention is to enable the communicationbased service provider, i.e., the communication device 102, to generate a first token which comprises an anonymous identifier of the communication device 102 and the communication-based service related information. The first token is sent to an Aggregator with which the communication device 102 has already registered and authorized. The Aggregator generates a second token which comprises the first token and additional information, then transmits the second token to the communication-based service requestor, i.e., the communication device 106. A communication-based service is provided by the communication device 102 to the communication device 106 based on the second token.

[0037] Therefore, the requestor communication device 106 cannot obtain the exact identity of the provider communication device 102, but only obtains the limited information, for example, that the communication device 102 has specific properties, e.g., capabilities to provide the communication-based service to it.

[0038] Referring to fig. 2 and fig. 5, a method performed by a first communication device 502 is disclosed. The first communication device 502 in fig. 5 is corresponding to 102 in fig. 1b. The network entity 504 comprises an Aggregator, which is a network platform providing services via network APIs from multiple network operators, i.e., multiple CSPs, and can be used by application developers on the second communication device 106 side. Network APIs allow developers to easily access advanced network capabilities from multiple CSPs, such as differentiated connectivity, location, security / authentication and network insights to enhance existing applications and develop new ones. The second communication device 506 is corresponding to 106 in fig. 1b and the CSP 510 is corresponding to 110 in fig. 1 b.

[0039] According to an embodiment, a method performed by a first communication device 502 for aiding to provide a communication-based service to a second communication device 506 is disclosed. The first communication device 502 is communicatively connected to a network entity 504 of a communication network via a communication service provider, CSP 510, the network entity 504 being communicatively connected to the second communication device 506 via the CSP 510. The method comprises: receiving 202 from the network entity 504, a request for availability to provide the communication-based service to the second communication device 506; transmitting 204 a first message, in response to confirming the availability to provide the communication-based service to the second communication device 506, to the network entity 504, the first message comprising a first token, wherein the first token is generated based on an anonymous identity of the first communication device 502, a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communication-based service.

[0040] Referring to fig. 5, the first communication device 502 is capable of providing a communication-based service to a second communication device 506. The method needs to be performed for aiding to provide the communication-based service. The first communication device 502 is communicatively connected to the network entity 504 comprising, e.g., an Aggregator, via the CSP 510. The second communication device 506 is also communicatively connected to the network entity 504 via the CSP 510. In other words, the first communication device 502 provisions the communication-based service to the second communication device 506 through the CSP 510 and the network entity 504. The first communication device 502 will initiate an API call to the CSP 510 on behalf of the second communication device 506. The communication-based service can be any service which is based on a communication function. Some examples of the communication-based service will be discussed in the text below.

[0041] Fig.2 shows a flow chart of the method performed by the first communication device 502. In the step 202, the first communication device 502 receives a request for availability to provide the communication-based service to the second communication device 506, from the network entity 504. In other words, the network entity 504 sends a request to the first communication device 502, checking if the first communication device 502 has the availability to provide the communicationbased service to the second communication device 506. The request for availability can be contained in a machine-readable message format, e.g. JavaScript Object Notation (JSON), Extensible Markup Language (XML), Yet Another Markup Language (YAML). Furthermore, depending on the communication-based service requested, might contain, among others, information on the hardware resources required, e.g., CPU, GPU, memory, storage, software libraries required, task execution constraints, i.e., a time window when the communication-based service should be executed, results required by a specific time.

[0042] In the step 204, in response to confirming the availability requested in the step 202, the first communication device 502 transmits a first message to the network entity 504. The first message comprises a first token, wherein the first token is generated based on an anonymous identity of the first communication device 502, anetwork address of the communication-based service, authorization information related to the communication-based service, validity information related to the communication-based service. The format of the first message can be in JSON format, XML format or similar.

[0043] In this step, when the first communication device 502 is able to support the communication-based service to the second communication device 506, it will generate a first token. This first token is generated based on an anonymous identity of the first communication device 502, which can be translated at the network entity 504 to a real identity. The real identity of the first communication device 502 can also be used to identify the connection tuple at the first communication device 502 level. The first token is also generated based on a network address of the communicationbased service, authorization information related to the communication-based service which can be used for safely accessing the communication-based service, and validity information related to the communication-based service. The network address of the communication-based service can be a Uniform Resource Locator (URL). Alternatively, the first token is integrity protected and also signed by the first communication device 502.

[0044] When the first token is generated, the first communication device 502 transmits a first message to the network entity 504, the first message comprises the first token.

[0045] By such an embodiment, the network entity 504 is able to identify the first communication device 502 based on the anonymous identity of the first communication device 502 and information related to the communication-based service. Therefore, first communication device 502 aids to provide the communication-based service in an anonymous and secured way while keeping privacy without revealing its real identity.

[0046] According to another embodiment, the first token is generated further based on information related to the CSP 510.

[0047] Referring to fig. 5, besides the network entity 504, another network entity 508 is shown, and the network entity 508 is another network entity which has a potential to aid to provide a communication-based service to the second communication device 506, via communication devices which are connected to the network entity 508. The network entity 508 can also be connected with its corresponding CSP. When the first token is generated based on CSP related information and when the second communication device 506 receives multiple first tokens from multiple CSPs, i.e. , CSPs respectively related to the network entity 504 and network entity 508, the second communication 506 can select a CSP based on the CSP information in the multiple first tokens. This will be explained in detail in the text below.

[0048] According to another embodiment, the anonymous identity of the first communication device 502 is converted into a non-anonymous identity of the first communication device 502 by the network entity 504.

[0049] In this embodiment, the anonymous identity of the first communication device 502 contained in the first message is converted into a non-anonymous identity by the network entity 504, so that the network entity 504 is aware of the real identity of the first communication device 502, or is able to identify the first communication device 502. This will be explained in detail in the text below.

[0050] According to another embodiment, the communication-based service comprises one or more of the following: Quality on Demand, QoD service, service with Quality of Service, QoS requirement, or computational service.

[0051] This embodiment lists several examples of the communication-based service: QoD service, service with QoS requirement, or computational service. QoD service refers to a service demanding network performance optimization to enhance the experience of the service. Service with QoS requirement refers to a service has a specific requirement on overall performance of the service. The requirement can be requirement on e.g., packet loss, bit rate, throughput, transmission delay, availability, jitter, traffic prioritization, resource reservation. Computational service refers to the use of computers to perform complex calculations, simulations, data analysis, etc.These tasks often require a higher level of computational power and specialized software or algorithms.

[0052] According to another embodiment, the anonymous identity comprises a verifiable anonymous identity or a pseudonym associated with the anonymous identity.

[0053] In this embodiment, the real identity of the first communication device 502 could be exchanged for an anonymous one either by the first communication device 502, or by the network entity 504 at an earlier stage, that the network entity 504 is aware of the real-anonymous allocation and / or mappings. The anonymous identity can be based on Subscription Concealed Identifier (SUCI -5G) method, IP address anonymization methods - e.g. prefix preserving anonymization method or any anonymization method that can be applied to the identifier. The anonymization methods can replace the identity with a pseudonym, cryptographic based methods, etc.

[0054] According to another embodiment, the authorization information comprises a temporary Application Programming Interface, API key or an authorization token.

[0055] The temporary API key and authorization token can be used as authorization information to access the communication-based service in an authorized way.

[0056] According to another embodiment, the validity information comprises a creation time and / or an expiration time of the communication-based service.

[0057] In this embodiment, the creation time can be a timestamp when the communication-based service is created, the expiration time can be a date or other specific time points.

[0058] According to another embodiment, the method further comprises providing 206 the communication-based service to the second communication device 506.

[0059] In this embodiment, the first communication device 502 provides the communication-based service to the second communication device 506, with the helpof the previous steps. A communication between the first communication device 502 and the second communication device 506 is established.

[0060] According to another embodiment, a method performed by the network entity 504 for aiding to provide a communication-based service to a second communication device 506 is disclosed. The first communication device 502 is communicatively connected to the network entity 504 via the CSP 510, the network entity 504 is communicatively connected to the second communication device 506 via the CSP 510. The method comprises sending 302, to the first communication device 502, a request for availability to provide the communication-based service to the second communication device 506; receiving 304, a first message from the first communication device 502, the first message comprising a first token, wherein the first token is generated based on an anonymous identity of the first communication device 502, a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communication-based service; transmitting 306 a second message to the second communication device 506, the second message comprising a second token, wherein the second token is generated based on the first message, an identity of the second communication device 506 and a profile of the communication-based service.

[0061] Fig.3 shows a flow chart of the method performed by the network entity 504. In the step 302, the network entity 504 sends a request to the first communication device 502, checking availability of the first communication device 502 to provide the communication-based service to the second communication device 506. The format of the request can be JSON format, XML format, YAML format or similar.

[0062] In the step 304, the network entity 504 receives a first message from the first communication device 502, in response to the request sent in the step 302. The first message comprises a first token, the first token is generated based on an anonymous identity of the first communication device 502, a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communication-based service. The first token is already discussed in the embodiments of the methods performed by the first communication device 502.

[0063] In the step 306, the network entity 504 transmits a second message to the second communication device 506. The second message comprises a second token, and the second token is generated by the network entity 504, based on the first token, an identity of the second communication device 506, and a profile of the communication-based device. The second token comprises the information comprised in the first token, i.e., the anonymous identity of the first communication device 502, a network address of the communication-based service, authorization information related to the communication-based service and validity information related to the communication-based service. Besides, the second token also comprises the identity of the second communication device 506, which is used as a receiver identity of the second message, and a profile of the communication-based device. The profile indicates one or more attribute of the communication-based service and will be discussed in the text below. The format of the second message can be JSON format, XML format, YAML format or similar.

[0064] In this embodiment, the network entity 504 receives the first token which comprises an anonymous identity of the first communication device, then adds additional information to become a second token, further sends the second token to the second communication device 506. In this way, the service requestor, i.e., the second communication device 506 is aware of that a service provider will provide a communication-based service to it, and the second communication device 506 is also aware of some properties of the service or the service provider, e.g., address of the service, validity of the service. However, the second communication device 506 is not aware of the real identity of the service provider, i.e., the first communication device 502. Therefore, privacy is kept between the two parties of the communication-based service.

[0065] According to another embodiment, the request for availability to provide the communication-based service to the second communication device 506 comprisesan identity of the second communication device 506, and the identity of the second communication device 506 can be anonymous.

[0066] In this embodiment, it is ensured that the first communication device 502 which receives the request may not be able to obtain the real identity of the requestor, i.e., second communication device 506 when the request for availability comes from the network entity 504. This provides privacy preservation of identities of the two participants, neither the requester nor the provider reveals their identities to each other before the communication-based service is established or during the establishment. For anonymous identity of the second communication device 506, verifiable anonymous identity or a pseudonym associated with the anonymous identity can be used. Similar anonymization methods can be used as the anonymization methods of the anonymous identity of the first communication device 502. The anonymous identity of the second communication device 506 can be added to the request for availability by the network entity 504.

[0067] According to another embodiment, the method further comprises receiving 308, from the second communication device 506, a request for the communicationbased service, prior to sending the request for availability to the first communication device 502. The format of the request can be JSON format, XML format, YAML format or similar.

[0068] In this embodiment, the requestor, i.e., the second communication device 506 sends a request for communication-based service to the network entity 504, so as to request the network entity 504 to check if there is available resource for the service, via the CSP 510. If there are multiple network entities which are connected to the second communication device 506, e.g., both network entity 504 and network entity 508 are connected to the second communication device 506, the second communication device 506 can send the request for communication-based service to each of the network entities 504 and 508 respectively, and select one network entity to proceed. In the example shown in fig. 5, the network entity 504 is selected.

[0069] In a more specific example, the request for communication-based service requests matching profile for a computational service, which is one type ofcommunication-based service. In other words, the second communication device 506 requests to offload to another communication device in an area, the selection of the area is either specific geospatial area based, or latency based.

[0070] The second communication device 506 sends a request to the network entities related to its mobile subscriptions: network entity 508 and network entity 504. This request can contain information related to the communication-based service, e.g., computational service for which QoD is requested. The communication-based service can be described via port, service name, other semantic metadata, QoS requirements and / or profile, etc.

[0071] Depending on the privacy preferences of the second communication device 506, a privacy-preserving but verifiable identity can be used for the second communication device 506 in the description of communication-based device contained in the request for communication-based service. For example, an anonymous identity of the second communication device is used. This anonymous identity can be included directly from the second communication device 506 when sending the request for communication-based service.

[0072] According to another embodiment, the method further comprises receiving 314, from the first communication device 502, a registration information for providing a communication-based service, prior to receiving the request for the communicationbased service from the second communication device 506. The format of the registration information can be in JSON format, XML format, YMAL format or similar, and it might contain information on the identity of the first communication device 502 and an indicator that the communication device 502 should be registered at the network entity 504 as authorized to generate the first token.

[0073] In this embodiment, the first communication device 502 sends a registration information to the network entity 504, prior to any other step for providing the communication-based service. The registration information indicates to the network entity 504 that the first communication device 502 has the potential to provide a communication-based service, and the first communication device 502 is authorizedto generate the first token. The network entity 504 is aware of the identity of the first communication device 502 with the registration information.

[0074] In other words, the first communication device 502 which is allowed to generate the first token is preferred to be registered / authorized beforehand with the network entity 504. This ensures that the network entity 504 can verify the authenticity of the received first token and reject the ones coming from unauthorized / not-registered communication device.

[0075] According to another embodiment, the profile of the communication-based service comprises one or more requirements associated with the communicationbased service, or an identifier of a previous communication-based service.

[0076] For example, the profile can be one or more requirements on specific geospatial area or latency. For another example, an identifier of a communication is used as a pointer to the profile of a previous communication-based service.

[0077] According to another embodiment, the first token is generated further based on information related to the CSP 510.

[0078] According to another embodiment, the method further comprises converting 310 the anonymous identity of the first communication device 502 into a non-anonymous identity of the first communication device 502, after transmitting the second message. The converting is feasible since the network entity 504 is aware of the real identity of the first communication device 502 beforehand.

[0079] According to another embodiment, the method further comprises: receiving 312 a first communication-based service request from the second communication device 506, wherein the first communication-based service request is generated based on the second message; transmitting 316 a second communication-based service request to the CSP 510, wherein the second communication-based service request is generated for the first communication device 506, based on the first communication-based service request.

[0080] In the step 312, the second communication device 506 uses the information extracted from the first token included in the second token, second message. The extracted information comprises the anonymous identity of the first communication device 502, the network address of the communication-based service and the authorization information related to the communication-based service. The second communication device 506 constructs a first communication-based service request, based on extracted information. The first communication-based service request can also contain updated information for the tuple describing the endpoint at the second communication device 506. The format of the first communication-based service request can be JSON format, XML format, YAML format or similar.

[0081] In the step 316, the network entity 504 constructs a second communicationbased service request for the first communication device 502 towards the CSP 510, based on the received first communication-based service request from the second communication device 506, e.g., based on the identities / network addresses of the first and the second communication devices 502, 506. The second communicationbased request can contain information on endpoints of the communication-based service channel, duration and profile. The network entity 504 sends the second communication-based service request to the CSP 510. The format of the second communication-based service request can be JSON format, XML format, YAML format or similar.

[0082] According to another embodiment, the method comprises: transmitting 318 a charging information to the CSP 510, the charging information relates to the communication-based service. The format of the charging information can be in JSON format, XML format, YAML format or similar, and it might contain information on the identity of the first communication device 502, the identity of the second communication device 506 and information extracted from the second token.

[0083] According to another embodiment, the method comprises: receiving 320 a communication-based service provisioning information from the CSP 510.

[0084] The communication-based service provisioning information is a message from the CSP 510 which indicates that communication-based service and charginghave been setup correctly. Optionally, some parameters of the communication-based service can be contained in this information. The format of the communication-based service provisioning information can be JSON format, XML format, YAML format or similar.

[0085] According to another embodiment, the method comprises: transmitting 322 the communication-based service provisioning information and information on communication-based service endpoints to the first communication device 502 and transmitting 324 the communication-based service provisioning information and information on communication-based service endpoints to the second communication device 506.

[0086] In this embodiment, the communication-based service provisioning information and information on communication-based service endpoints are sent to both the first and second communication devices 502 and 506. The first and second communication devices 502 and 506 are aware of the two endpoints of the communication-based service explicitly until these two steps.

[0087] According to another embodiment, a method performed by a second communication device 506 for requesting a communication-based service from a first communication device 502 is disclosed. The first communication device 502 is communicatively connected to a network entity 504 via a communication-based service provider, CSP 510, the network entity 504 is communicatively connected to the second communication device 506 via the CSP 510. The method comprises: receiving 402 a second message from the network entity 504, the second message comprising a second token, wherein the second token is generated based on a first message, an identity of the second communication device 506 and a profile of the communication-based service, wherein the first message comprising a first token, the first token is generated based on an anonymous identity of the first communication device 502, a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communication-based service; transmitting 404 a first communication-based service request in response to the second message, to the network entity 504.

[0088] Fig. 4 shows a flow chart of the method performed by the second communication device 506. In the step 402, the second communication device 506 receives a second message from the network entity 504. The second message comprises a second token, the second token is generated based on the first token and additional information added by the network entity 504, which is discussed in the embodiments of the methods performed by the network entity 504.

[0089] In the step 404, the second communication device 506 generates a first communication-based service request based on the second message, i.e. , the second token, and transmits first communication-based service request to the network entity 504, indicating that the second communication device 506 requests to obtain the communication-based service.

[0090] In a specific example, the second communication device 506 uses the information extracted from the first token, i.e., the network address of the communication-based service, the authorization information which can be used for accessing the communication-based service, and constructs the first communicationbased service request for the first communication device 502, based on the anonymous identity in the first token. The first communication-service request can also comprise updated information for the tuple describing the endpoint at the second communication device 506.

[0091] According to another embodiment, the method further comprises transmitting 406 a request for the communication-based service to the network entity 504, prior to receiving the second message.

[0092] In this embodiment, the second communication device 506 as the requestor sends a request for communication-based service to the network entity 504, so as to request the network entity 504 to check if there is available resource for the service, via the CSP 510. If there are multiple network entities which are connected to the second communication device 506, e.g., both network entity 504 and network entity 508 are connected to the second communication device 506, the second communication device 506 can send the request for communication-based service toeach of the network entities 504 and 508 respectively, and select one network entity to proceed. In the example shown in fig. 5, the network entity 504 is selected.

[0093] In a more specific example, the request for communication-based service requests matching profile for a computational service, which is one type of communication-based service. In other words, the second communication device 506 requests to offload to another communication device in an area, the selection of the area is either specific geospatial area based, or latency based.

[0094] The second communication device 506 sends a request to the network entities related to its mobile subscriptions: network entity 508 and network entity 504. This request can contain information related to the communication-based service, e.g., computational service for which QoD is requested. The communication-based service can be described via port, service name, other semantic metadata, QoS requirements and / or profile, etc.

[0095] Depending on the privacy preferences of the second communication device 506, a privacy-preserving but verifiable identity can be used for the second communication device 506 in the description of communication-based device contained in the request for communication-based service. For example, an anonymous identity of the second communication device is used. This anonymous identity can be included directly from the second communication device 506 when sending the request for communication-based service.

[0096] According to another embodiment, the method further comprises obtaining 408 the communication-based service provided by the first communication device 502, based on the first communication-based service request.

[0097] According to another embodiment, the first token is generated further based on information related to the CSP 510. As discussed above, the second communication device 506 may send the request for communication-based service to each of the multiple network entities 504 and 508 respectively. When receiving the second message, the second communication device 506 receives multiple second messages from each of the network entities 504 and 508, whereas each of thesecond token comprises respective CSP information. Therefore, the second communication device 506 can select one CSP based on the CSP information, thereby select one network entity. The second tokens which relate to unselected CSP(s) can be discarded.

[0098] Referring to fig. 5, interactions between the first communication device 502, the second communication device 506, the network entity 504, the CSP 510 and another network entity 508 are shown in the sequence diagram.

[0099] In the step 5.5, the first communication device 502 transmits a registration information to the network entity 504, registering itself as a communication device which is authorized to provide communication-based service and generating the first token. In the steps 5.4, the second communication device 506 as a requestor transmits requests to each of the network entities 504, 508, requesting a communication-based service. The network entity 504 is selected for subsequent procedure.[000100] In the step 5.14, upon receiving the request for communication-based service, the network entity 504 can translate this request into a series of requests towards a list of connected communication devices having potential to provide service in a specific area and the service profiles supported by them. Based on this information the network entity 504 can select a subset of the connected communication devices which potentially can support the communication-based service request initiated by second communication device 506. The first communication device 502 is one of the selected communication devices which potentially can support the communication-based service. In the step 5.1, the network entity 504 transmits a request to the first communication device 502, checking the availability / possibility of the first communication device 502 to support the communication-based service.[000101] In the step 5.2, in response to the request received in the step 5.1, the first communication device 502 generates a first token, based on an anonymous identity of the first communication device 502, a network address of the communicationbased service, authorization information related to the communication-based service,validity information related to the communication-based service and optionally the information related to CSP 510. The first token is transmitted from the first communication device 502 to the network entity 504, in a first message.[000102] In the step 5.3, the network entity 504 generates a second token, based on the first token, an identity of the second communication device 506 and a profile of the communication-based service. The second token is transmitted from the network entity 504 to the second communication device 506, in a second message. In the step 5.6, the network entity 504 converts the anonymous identity in the first token into a non-anonymous identity.[000103] In the step 5.7, upon receiving the second token, the second communication device 506 generates a first communication-based service request based on the second token, and transmits the request to the network entity 504. In the step 508, the network entity 504 generates a second communication-based service request based on the first communication-based service request and transmits the second communication-service request to the CSP 510. In the step 5.9, the network entity 504 transmits charging information to the CSP 510 and the CSP 5.11 transmits communication-based service provisioning information to the network entity 504.[000104] In the step 5.11 and step 5.12, the network entity 504 propagates the provisioning information to the first and second communication devices 502 and 506, and the second communication device 506 obtains the communication-based service from the first communication device 502 in the step 5.13.[000105] According to another embodiment, a first communication device 502 for aiding to provide a communication-based service to a second communication device 506 is disclosed. The first communication device 502 is communicatively connected to a network entity 504 of a communication network and a communication service provider, CSP 510, the network entity 504 is communicatively connected to the second communication device 506 and the CSP 510, the first communication device 502 comprising a communication unit 602, a processing circuitry 603 and a memory 604, said memory 604 containing instructions executable by said processing circuitry603, whereby the first communication device 502 is operative to: receive from the network entity 504, a request for availability to provide the communication-based service to the second communication device 506; transmit a first message, in response to confirming the availability to provide the communication-based service to the second communication device 506, to the network entity 504, the first message comprising a first token, wherein the first token is generated based on an anonymous identity of the first communication device 502, a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communicationbased service.[000106] According to another embodiment, the first token is generated further based on information related to the CSP 510.[000107] According to another embodiment, the anonymous identity of the first communication device 502 is converted into a non-anonymous identity of the first communication device 502 by the network entity 504.[000108] According to another embodiment, the communication-based service comprises one or more of the following: Quality on Demand, QoD service, service with Quality of Service, QoS requirement, or computational service.[000109] According to another embodiment, the anonymous identity comprises a verifiable anonymous identity or a pseudonym associated with the anonymous identity.[000110] According to another embodiment, the authorization information comprises a temporary Application Programming Interface, API key or an authorization token.[000111] According to another embodiment, the validity information comprises a creation time and / or an expiration time of the communication-based service.[000112] According to another embodiment, the first communication device 502 is further operative to: provide the communication-based service to the second communication device 506.[000113] According to another embodiment, a network entity 504 for aiding to provide a communication-based service to a second communication device 506 is disclosed. The first communication device 502 is communicatively connected to the network entity 504 and a communication service provider, CSP 510, the network entity 504 is communicatively connected to the second communication device 506 and the CSP 510, the network entity 504 comprising a communication unit 702, a processing circuitry 703 and a memory 704, said memory 704 containing instructions executable by said processing circuitry 703, whereby the network entity 504 is operative to: send, to the first communication device 502, a request for availability to provide the communication-based service to the second communication device 506; receive, a first message from the first communication device 502, the first message comprising a first token, wherein the first token is generated based on an anonymous identity of the first communication device 502, a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communication-based service; transmitting 306 a second message to the second communication device 506, the second message comprising a second token, wherein the second token is generated based on the first message, an identity of the second communication device 506 and a profile of the communication-based service.[000114] According to another embodiment, the request for availability to provide the communication-based service to the second communication device 506 comprises an anonymous identity of the second communication device 506.[000115] According to another embodiment, the network entity 504 is further operative to receive, from the second communication device 506, a request for the communication-based service, prior to sending the request for availability to the first communication device 502.[000116] According to another embodiment, the network entity 504 is further operative to receive, from the first communication device 502, a registration information for providing a communication-based service, prior to receiving therequest for the communication-based service from the second communication device 506.[000117] According to another embodiment, the profile of the communication-based service comprises one or more requirements associated with the communicationbased service, or an identifier of a previous communication-based service.[000118] According to another embodiment, the first token is generated further based on information related to the CSP 510.[000119] According to another embodiment, the network entity 504 is further operative to convert the anonymous identity of the first communication device 502 into a non-anonymous identity of the first communication device 502, after transmitting the second message.[000120] According to another embodiment, the network entity 504 is further operative to: receive a first communication-based service request from the second communication device 506, wherein the first communication-based service request is generated based on the second message; transmit a second communication-based service request to the CSP 510, wherein the second communication-based service request is generated for the first communication device 506, based on the first communication-based service request.[000121] According to another embodiment, the network entity 504 is further operative to: transmit a charging information to the CSP 510, the charging information relates to the communication-based service.[000122] According to another embodiment, the network entity 504 is further operative to: receive a communication-based service provisioning information from the CSP 510.[000123] According to another embodiment, the network entity 504 is further operative to: transmit the communication-based service provisioning information and information on communication-based service endpoints to the first communication device 502 and transmit the communication-based service provisioning informationand information on communication-based service endpoints to the second communication device 506.[000124] According to another embodiment, a second communication device 506 for requesting a communication-based service from a first communication device 502 is disclosed. The first communication device 502 is communicatively connected to a network entity 504 and a communication-based service provider, CSP 510, the network entity 504 is communicatively connected to the second communication device 506 and the CSP 510, the second communication device 506 comprising a communication unit 802, a processing circuitry 803 and a memory 804, said memory 804 containing instructions executable by said processing circuitry 803, whereby the second communication device 506 is operative to: receive a second message from the network entity 504, the second message comprising a second token, wherein the second token is generated based on a first message, an identity of the second communication device 506 and a profile of the communication-based service, wherein the first message comprising a first token, the first token is generated based on an anonymous identity of the first communication device 502, a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communicationbased service; transmit a first communication-based service request in response to the second message, to the network entity 504.[000125] According to another embodiment, the second communication device 506 is further operative to transmit a request for the communication-based service to the network entity 504, prior to receiving the second message.[000126] According to another embodiment, the second communication device 506 is further operative to obtain the communication-based service provided by the first communication device 502, based on the first communication-based service request.[000127] According to another embodiment, the first token is generated further based on information related to the CSP 510.[000128] According to another embodiment in fig. 6, the first communication device 502 may further comprise a communication unit 602, which may be considered to comprise conventional means for communication with the network entity 504 and the CSP 510, such as a transceiver for transmission and reception of signals. The instructions executable by said processing circuitry 603 may be arranged as a computer program 605 stored e.g., in said memory 604. The processing circuitry 603 and the memory 604 may be arranged in a sub-arrangement 601. The subarrangement 601 may be a micro-processor and adequate software and storage therefore, a Programmable Logic Device, PLD, or other electronic component(s) / processing circuit(s) configured to perform the method mentioned above. The processing circuitry 603 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these adapted to execute instructions.[000129] The computer program 605 may be arranged such that when its instructions are run in the processing circuitry, they cause the first communication device 502 to perform the steps described in any of the described exemplary embodiments of the first communication device 502 and its method. The computer program 605 may be carried by a computer program product connectable to the processing circuitry 603. The computer program product may be the memory 604, or at least arranged in the memory. The memory 604 may be realized as for example a RAM (Random-access memory), ROM (Read-Only Memory) or an EEPROM (Electrical Erasable Programmable ROM). In some embodiments, a carrier may contain the computer program 605. The carrier may be one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or computer readable storage medium. The computer-readable storage medium may be e.g., a CD, DVD or flash memory, from which the program could be downloaded into the memory 604. Alternatively, the computer program may be stored on a server or any other entity to which the first communication device 502 has access via the communication unit 602. The computer program 605 may then be downloaded from the server into the memory 604.[000130] According to another embodiment in fig. 7, the network entity 504 may further comprise a communication unit 702, which may be considered to comprise conventional means for communication with the communication devices and the CSP 510, such as a transceiver for transmission and reception of signals. The instructions executable by said processing circuitry 703 may be arranged as a computer program 705 stored e.g., in said memory 704. The processing circuitry 703 and the memory 704 may be arranged in a sub-arrangement 701. The sub-arrangement 701 may be a micro-processor and adequate software and storage therefore, a Programmable Logic Device, PLD, or other electronic component(s) / processing circuit(s) configured to perform the method mentioned above. The processing circuitry 703 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these adapted to execute instructions.[000131] The computer program 705 may be arranged such that when its instructions are run in the processing circuitry, they cause the network entity 504 to perform the steps described in any of the described exemplary embodiments of the network entity 504 and its method. The computer program 705 may be carried by a computer program product connectable to the processing circuitry 703. The computer program product may be the memory 704, or at least arranged in the memory. The memory 704 may be realized as for example a RAM (Random-access memory), ROM (Read-Only Memory) or an EEPROM (Electrical Erasable Programmable ROM). In some embodiments, a carrier may contain the computer program 705. The carrier may be one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or computer readable storage medium. The computer-readable storage medium may be e.g., a CD, DVD or flash memory, from which the program could be downloaded into the memory 704. Alternatively, the computer program may be stored on a server or any other entity to which the network entity 504 has access via the communication unit 702. The computer program 705 may then be downloaded from the server into the memory 704.[000132] According to another embodiment in fig. 8, the second communication device 506 may further comprise a communication unit 802, which may beconsidered to comprise conventional means for communication with the network entity 504 and the CSP 510, such as a transceiver for transmission and reception of signals. The instructions executable by said processing circuitry 803 may be arranged as a computer program 805 stored e.g., in said memory 804. The processing circuitry 803 and the memory 804 may be arranged in a sub-arrangement 801. The sub-arrangement 801 may be a micro-processor and adequate software and storage therefore, a Programmable Logic Device, PLD, or other electronic component(s) / processing circuit(s) configured to perform the method mentioned above. The processing circuitry 803 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these adapted to execute instructions.[000133] The computer program 805 may be arranged such that when its instructions are run in the processing circuitry, they cause the second communication device 506 to perform the steps described in any of the described exemplary embodiments of the second communication device 506 and its method. The computer program 805 may be carried by a computer program product connectable to the processing circuitry 803. The computer program product may be the memory 804, or at least arranged in the memory. The memory 804 may be realized as for example a RAM (Randomaccess memory), ROM (Read-Only Memory) or an EEPROM (Electrical Erasable Programmable ROM). In some embodiments, a carrier may contain the computer program 805. The carrier may be one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or computer readable storage medium. The computer-readable storage medium may be e.g., a CD, DVD or flash memory, from which the program could be downloaded into the memory 804. Alternatively, the computer program may be stored on a server or any other entity to which the second communication device 506 has access via the communication unit 802. The computer program 805 may then be downloaded from the server into the memory 804.[000134] Although the description above contains a plurality of specificities, these should not be construed as limiting the scope of the concept described herein but as merely providing illustrations of some exemplifying embodiments of the describedconcept. It will be appreciated that the scope of the presently described concept fully encompasses other embodiments which may become obvious to those skilled in the art, and that the scope of the presently described concept is accordingly not to be limited. Reference to an element in the singular is not intended to mean "one and only one" unless explicitly so stated, but rather "one or more." Further, the term “a number of”, such as in “a number of wireless devices” signifies one or more devices. All structural and functional equivalents to the elements of the above-described embodiments that are known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed hereby. Moreover, it is not necessary for an apparatus or method to address each and every problem sought to be solved by the presently described concept, for it to be encompassed hereby. In the exemplary figures, a broken line generally signifies that the feature within the broken line is optional.

Claims

CLAIMS1. A method performed by a first communication device (502) for aiding to provide a communication-based service to a second communication device (506), the first communication device (502) being communicatively connected to a network entity (504) of a communication network and a communication service provider, CSP (510), the network entity (504) being communicatively connected to the second communication device (506) and the CSP (510), the method comprising:receiving (202) from the network entity (504), a request for availability to provide the communication-based service to the second communication device (506);transmitting (204) a first message, in response to confirming the availability to provide the communication-based service to the second communication device (506), to the network entity (504), the first message comprising a first token, wherein the first token is generated based on an anonymous identity of the first communication device (502), a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communication-based service.

2. The method as claimed in claim 1 , wherein the first token is generated further based on information related to the CSP (510).

3. The method as claimed in claim 1 or 2, wherein the anonymous identity of the first communication device (502) is converted into a non-anonymous identity of the first communication device (502) by the network entity (504).

4. The method as claimed in any one of the claims 1-3, wherein the communication-based service comprises one or more of the following: Quality on Demand, QoD service, service with Quality of Service, QoS requirement, or computational service.

5. The method as claimed in any one of the claims 1-4, wherein the anonymous identity comprises a verifiable anonymous identity or a pseudonym associated with the anonymous identity.

6. The method as claimed in any one of the claims 1-5, wherein the authorization information comprises a temporary Application Programming Interface, API key or an authorization token.

7. The method as claimed in any one of the claims 1-6, wherein the validity information comprises a creation time and / or an expiration time of the communication-based service.

8. The method as claimed in any one of claims 1-7, the method further comprises:providing (206) the communication-based service to the second communication device (506).

9. A method performed by a network entity (504) for aiding to provide a communication-based service to a second communication device (506), the first communication device (502) being communicatively connected to the network entity (504) and a communication service provider, CSP (510), the network entity (504) being communicatively connected to the second communication device (506) and the CSP (510), the method comprising:sending (302), to the first communication device (502), a request for availability to provide the communication-based service to the second communication device (506);receiving (304), a first message from the first communication device (502), the first message comprising a first token, wherein the first token is generated based on an anonymous identity of the first communication device (502), a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communicationbased service;transmitting (306) a second message to the second communication device (506), the second message comprising a second token, wherein the secondtoken is generated based on the first message, an identity of the second communication device (506) and a profile of the communication-based service.

10. The method as claimed in claim 9, wherein the request for availability to provide the communication-based service to the second communication device (506) comprises an anonymous identity of the second communication device (506).

11. The method as claimed in claim 9 or 10, the method further comprises receiving (308), from the second communication device (506), a request for the communication-based service, prior to sending the request for availability to the first communication device (502).

12. The method as claimed in any one of the claims 9-11 , the method further comprises receiving (314), from the first communication device (502), a registration information for providing a communication-based service, prior to receiving the request for the communication-based service from the second communication device (506).

13. The method as claimed in any one of the claims 9-12, wherein the profile of the communication-based service comprises one or more requirements associated with the communication-based service, or an identifier of a previous communicationbased service.

14. The method as claimed in any one of the claims 9 -13, wherein the first token is generated further based on information related to the CSP (510).

15. The method as claimed in any one of the claims 9-14, the method further comprisesconverting (310) the anonymous identity of the first communication device (502) into a non-anonymous identity of the first communication device (502), after transmitting the second message.

16. The method as claimed in any one of the claims 9-15, the method further comprises:receiving (312) a first communication-based service request from the second communication device (506), wherein the first communication-based service request is generated based on the second message;transmitting (316) a second communication-based service request to the CSP (510), wherein the second communication-based service request is generated for the first communication device (506), based on the first communication-based service request.

17. The method as claimed in any one of the claims 9-16, the method comprises:transmitting (318) a charging information to the CSP (510), the charging information relates to the communication-based service.

18. The method as claimed in any one of the claims 9-17, the method comprises:receiving (320) a communication-based service provisioning information from the CSP (510).

19. The method as claimed in claim 18, the method comprises:transmitting (322) the communication-based service provisioning information and information on communication-based service endpoints to the first communication device (502) andtransmitting (324) the communication-based service provisioning information and information on communication-based service endpoints to the second communication device (506).

20. A method performed by a second communication device (506) for requesting a communication-based service from a first communication device (502), the first communication device (502) being communicatively connected to a network entity (504) and a communication-based service provider, CSP (510), the networkentity (504) being communicatively connected to the second communication device (506) and the CSP (510), the method comprising:receiving (402) a second message from the network entity (504), the second message comprising a second token, wherein the second token is generated based on a first message, an identity of the second communication device (506) and a profile of the communication-based service, wherein the first message comprising a first token, the first token is generated based on an anonymous identity of the first communication device (502), a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communication-based service;transmitting (404) a first communication-based service request in response to the second message, to the network entity (504).

21. The method as claimed in claim 20, the method further comprises transmitting (406) a request for the communication-based service to the network entity (504), prior to receiving the second message.

22. The method as claimed in claim 20 or 21 , the method further comprises obtaining (408) the communication-based service provided by the first communication device (502), based on the first communication-based service request.

23. The method as claimed in any one of the claims 20-22, wherein the first token is generated further based on information related to the CSP (510).

24. A first communication device (502) for aiding to provide a communication-based service to a second communication device (506), the first communication device (502) being communicatively connected to a network entity (504) of a communication network and a communication service provider, CSP (510), the network entity (504) being communicatively connected to the second communication device (506) and the CSP (510), the first communication device (502) comprising a communication unit (602), a processing circuitry (603) and a memory(604), said memory (604) containing instructions executable by said processing circuitry (603), whereby the first communication device (502) is operative to:receive from the network entity (504), a request for availability to provide the communication-based service to the second communication device (506);transmit a first message, in response to confirming the availability to provide the communication-based service to the second communication device (506), to the network entity (504), the first message comprising a first token, wherein the first token is generated based on an anonymous identity of the first communication device (502), a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communication-based service.

25. The first communication device (502) as claimed in claim 24, wherein the first token is generated further based on information related to the CSP (510).

26. The first communication device (502) as claimed in claim 24 or 25, wherein the anonymous identity of the first communication device (502) is converted into a non-anonymous identity of the first communication device (502) by the network entity (504).

27. The first communication device (502) as claimed in any one of the claims 24-26, wherein the communication-based service comprises one or more of the following: Quality on Demand, QoD service, service with Quality of Service, QoS requirement, or computational service.

28. The first communication device (502) as claimed in any one of the claims 24-27, wherein the anonymous identity comprises a verifiable anonymous identity or a pseudonym associated with the anonymous identity.

29. The first communication device (502) as claimed in any one of the claims 24-28, wherein the authorization information comprises a temporary Application Programming Interface, API key or an authorization token.

30. The first communication device (502) as claimed in any one of the claims 24-29, wherein the validity information comprises a creation time and / or an expiration time of the communication-based service.

31. The first communication device (502) as claimed in any one of claims 24-30, the first communication device (502) is further operative to:provide the communication-based service to the second communication device (506).

32. A network entity (504) for aiding to provide a communication-based service to a second communication device (506), the first communication device (502) being communicatively connected to the network entity (504) and a communication service provider, CSP (510), the network entity (504) being communicatively connected to the second communication device (506) and the CSP (510), the network entity (504) comprising a communication unit (702), a processing circuitry (703) and a memory (704), said memory (704) containing instructions executable by said processing circuitry (703), whereby the network entity (504) is operative to:send, to the first communication device (502), a request for availability to provide the communication-based service to the second communication device (506);receive, a first message from the first communication device (502), the first message comprising a first token, wherein the first token is generated based on an anonymous identity of the first communication device (502), a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communicationbased service;transmit a second message to the second communication device (506), the second message comprising a second token, wherein the second token is generated based on the first message, an identity of the second communication device (506) and a profile of the communication-based service.

33. The network entity (504) as claimed in claim 32, wherein the request for availability to provide the communication-based service to the second communicationdevice (506) comprises an anonymous identity of the second communication device (506).

34. The network entity (504) as claimed in claim 32 or 33, the network entity (504) is further operative toreceive, from the second communication device (506), a request for the communication-based service, prior to sending the request for availability to the first communication device (502).

35. The network entity (504) as claimed in any one of the claims 32-34, the network entity (504) is further operative toreceive, from the first communication device (502), a registration information for providing a communication-based service, prior to receiving the request for the communication-based service from the second communication device (506).

36. The network entity (504) as claimed in any one of the claims 32-35, wherein the profile of the communication-based service comprises one or more requirements associated with the communication-based service, or an identifier of a previous communication-based service.

37. The network entity (504) as claimed in any one of the claims 32-36, wherein the first token is generated further based on information related to the CSP (510).

38. The network entity (504) as claimed in any one of the claims 32-37, the network entity (504) is further operative toconvert the anonymous identity of the first communication device (502) into a non-anonymous identity of the first communication device (502), after transmitting the second message.

39. The network entity (504) as claimed in any one of the claims 32-38, the network entity (504) is further operative to:receive a first communication-based service request from the second communication device (506), wherein the first communication-based service request is generated based on the second message;transmit a second communication-based service request to the CSP (510), wherein the second communication-based service request is generated for the first communication device (506), based on the first communication-based service request.

40. The network entity (504) as claimed in any one of the claims 32-39, the network entity (504) is further operative to:transmit a charging information to the CSP (510), the charging information relates to the communication-based service.

41. The network entity (504) as claimed in any one of the claims 32-40, the network entity (504) is further operative to:receive a communication-based service provisioning information from the CSP (510).

42. The network entity (504) as claimed in claim 41 , the network entity (504) is further operative to:transmit the communication-based service provisioning information and information on communication-based service endpoints to the first communication device (502) andtransmit the communication-based service provisioning information and information on communication-based service endpoints to the second communication device (506).

43. A second communication device (506) for requesting a communicationbased service from a first communication device (502), the first communication device (502) being communicatively connected to a network entity (504) and a communication-based service provider, CSP (510), the network entity (504) beingcommunicatively connected to the second communication device (506) and the CSP (510), the second communication device (506) comprising a communication unit (802), a processing circuitry (803) and a memory (804), said memory (804) containing instructions executable by said processing circuitry (803), whereby the second communication device (506) is operative to:receive a second message from the network entity (504), the second message comprising a second token, wherein the second token is generated based on a first message, an identity of the second communication device (506) and a profile of the communication-based service, wherein the first message comprising a first token, the first token is generated based on an anonymous identity of the first communication device (502), a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communication-based service;transmit a first communication-based service request in response to the second message, to the network entity (504).

44. The second communication device (506) as claimed in claim 43, the second communication device (506) is further operative totransmit a request for the communication-based service to the network entity (504), prior to receiving the second message.

45. The second communication device (506) as claimed in claim 43 or 44, the second communication device (506) is further operative toobtain the communication-based service provided by the first communication device (502), based on the first communication-based service request.

46. The second communication device (506) as claimed in any one of the claims 43-45, wherein the first token is generated further based on information related to the CSP (510).

47. A computer program (605) comprising instructions, which, when executed by at least one processing circuitry (603) of a first communication device(502), the first communication device (502) being communicatively connected to a network entity (504) of a communication network and a communication service provider, CSP (510), the network entity (504) being communicatively connected to the second communication device (506) and the CSP (510), causes the first communication device (502) to perform the following steps:receiving (202) from the network entity (504), a request for availability to provide the communication-based service to the second communication device (506);transmitting (204) a first message, in response to confirming the availability to provide the communication-based service to the second communication device (506), to the network entity (504), the first message comprising a first token, wherein the first token is generated based on an anonymous identity of the first communication device (502), a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communication-based service.

48. A carrier containing the computer program (605) according to claim 47, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, an electric signal, or a computer readable storage medium.

49. A computer program (705) comprising instructions, which, when executed by at least one processing circuitry (703) of a network entity (504), the first communication device (502) being communicatively connected to the network entity (504) and a communication service provider, CSP (510), the network entity (504) being communicatively connected to the second communication device (506) and the CSP (510), causes the network entity (504) to perform the following steps:sending (302), to the first communication device (502), a request for availability to provide the communication-based service to the second communication device (506);receiving (304), a first message from the first communication device (502), the first message comprising a first token, wherein the first token is generated based on an anonymous identity of the first communication device (502), a network address of the communication-based service, authorization information related to thecommunication-based service, validity information related to the communicationbased service;transmitting (306) a second message to the second communication device (506), the second message comprising a second token, wherein the second token is generated based on the first message, an identity of the second communication device (506) and a profile of the communication-based service.

50. A carrier containing the computer program (705) according to claim 49, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, an electric signal, or a computer readable storage medium.

51. A computer program (805) comprising instructions, which, when executed by at least one processing circuitry (803) of a second communication device (506), a first communication device (502) being communicatively connected to a network entity (504) and a communication-based service provider, CSP (510), the network entity (504) being communicatively connected to the second communication device (506) and the CSP (510), causes the second communication device (506) to perform the following steps:receiving (402) a second message from the network entity (504), the second message comprising a second token, wherein the second token is generated based on a first message, an identity of the second communication device (506) and a profile of the communication-based service, wherein the first message comprising a first token, the first token is generated based on an anonymous identity of the first communication device (502), a network address of the communication-based service, authorization information related to the communication-based service, validity information related to the communication-based service;transmitting (404) a first communication-based service request in response to the second message, to the network entity (504).

52. A carrier containing the computer program (805) according to claim 51 , wherein the carrier is one of an electronic signal, an optical signal, a radio signal, an electric signal, or a computer readable storage medium.

Images