Apparatus and method for providing access to a network

Abstract

A method and apparatus for data transfer over a communication network are disclosed. The method is implemented in a system including the following: • A first device including an interface configured to provide a wireless connection to a second communication device and a wireless access point for providing a wireless network. The second device includes a communication interface configured to provide a shared connection to the communication network to the first device. • A third communication device including a communication interface for connecting to the wireless network of the access point of the first device. The method allows a third device to access the shared connection via the first device, which is connected to the shared connection. Therefore, the third device does not need to obtain authentication credentials to connect directly to the shared connection. The method makes it possible for a person who owns a data plan to offer or sell data allowances anonymously.

Description

Technical Field

[0001] A method and apparatus for providing access to a network will be described. This apparatus and method can be used, in particular, in the context of providing network access to a user device through a shared connection with a mobile phone via an intermediate device functioning as a wireless access point. More specifically, this context can be anonymous peer-to-peer sharing of a cellular data plan.

Background Art

[0002] In the digital age, the use of mobile data has become an indispensable part of daily life. However, conventional data plans and contracts often impose restrictions, leading to inefficiencies and suboptimal resource utilization. Users frequently encounter situations where the purchased data plan is not fully utilized, resulting in waste of resources and unnecessary costs. At the same time, many users need additional data but lack flexible and cost-effective options to meet specific needs.

[0003] In the latter case, the user has the option to disable data access based on the mobile phone's data plan and limit the connection to a single connection provided by a wireless access point connected to the Internet, such as in a store or a public hot spot in a dedicated urban area. Such hot spots are not available everywhere, and the user needs to be within the limited range of the wireless access point creating the hot spot.

[0004] Users can also use their mobile phones to set up hotspots and borrow connections from phone owners who share their connections. Access to such hotspots requires the approval of the mobile phone owner. In these situations, users need to know the password to the personal hotspot and, in most cases, physically identify the person sharing the personal hotspot. This can lead to forced and unnecessary social connections, leaving little room for smartphone owners to refuse to share their identity.

[0005] These methods could compromise security, expose personal information, or involve rigid contractual agreements. In practice, today it is difficult to legally connect to a phone owner's personal hotspot without knowing the phone owner and without interacting with them to obtain the shared connection password. It is also impossible to measure the amount of data a user has used from a smartphone's shared connection without the phone owner checking it in real time on their smartphone.

[0006] Therefore, there is a need for a user-friendly, secure, and anonymous mobile data sharing system that leverages the global presence of mobile phones that are readily available and can function as internet access points, while maintaining transaction anonymity and ensuring the safety of the parties sharing the data. [Overview of the project]

[0007] The first aspect relates to a method for data transfer over a communication network, and the system includes the following: • A first communication device including a communication interface configured to provide the following: ○ Wireless connection to the second communication device ○ Wireless access point for providing a wireless network The second device includes a communication interface configured to provide a shared connection to the communication network to the first device, the shared connection being adapted to enable data transfer over the communication network. A third communication device including a communication interface for connecting to the wireless network of an access point of the first device. The method includes the following in the third device: • The third device obtains information representing at least one proposal for transferring data via the shared connection of the second device. In response to sending a message indicating acceptance of the received proposal, the third device receives access by the third device to a shared connection corresponding to the accepted proposal for transferring data in accordance with one or more conditions of the accepted proposal, wherein the communication of said data between the second device and the third device is performed only through the first device.

[0008] In practice, it is the first device that effectively connects to the shared connection, allowing the third device to retrieve and transmit data. Authentication information necessary to grant access to the shared connection, such as a password or the name of the second device providing the shared connection, does not need to be communicated to the third device, which can then connect to the first device for the purpose of benefiting from the shared connection. The anonymity of the person controlling the first device capable of providing the shared connection is maintained.

[0009] Users of a third device can benefit from the data plan without having their own subscription to such a plan. Furthermore, they can obtain only the amount of data they need, resulting in less waste.

[0010] According to one embodiment, the method further includes verifying the transaction that authorizes payment of the price associated with the accepted proposal before enabling access.

[0011] According to one embodiment, the wireless network has a network identifier that indicates to a third device that a first device is adapted to provide access to a shared connection.

[0012] Therefore, the third device can easily detect the wireless network provided by the first device, which is connected to a shared connection from which the third device may benefit.

[0013] According to one embodiment, the system includes a plurality of first devices connected to each second device, each first device providing a predetermined wireless network, all predetermined wireless networks using the same network identifier, and the network identifier is known to a third device.

[0014] According to one embodiment, the acquisition of information by a third communication device representing at least one proposal for data transfer via a shared connection of a second communication device includes the following in the third device: • Detect the wireless network of the first device using the network identifier of the first device. • A small amount of data transfer via a shared connection between the first device and the second communication device. At the very least, obtain information that represents one proposal.

[0015] According to one embodiment, the information representing the proposal is the amount of data to be transferred and the data Includes pricing to enable the transfer of quantities.

[0016] According to one embodiment, the information representing the proposal further includes the estimated time of the presence of the second device at the current geographical location.

[0017] According to one embodiment, the information representing the proposal does not include information regarding the identity of the user of the first device.

[0018] According to one embodiment, the communication network is a cellular network, and the second device is a mobile phone.

[0019] According to one embodiment, the verification of a transaction for approving payment of a price related to an accepted proposal is performed by a software application executed by a third device, and the method further includes the following. · Transmitting information indicating verification of the transaction from the third device to the first device · Transmitting information indicating verification of the transaction from the first device to the second device · Activating access to the shared connection by the second device in response to the information indicating verification of the transaction

[0020] According to one embodiment, the method further includes the following in the third device. · Detecting the wireless network of the first device using a pre-defined network identifier · Obtaining information representing at least one proposal for data transfer via the first device

[0021] According to one embodiment, the system further includes a cloud server, and the method further includes the following. · Obtaining, by the third device, from the cloud server, information representing at least one proposal for data transfer of the second device as a function of the geographical location of the second device and the geographical location of the third device [[ID=2二十二]]

[0022] According to one embodiment, the method further includes the following in the third device. · Transmitting information indicating the accepted proposal to the cloud server · Receiving, from the cloud server, information enabling connection of the third device to the wireless network of the first device connected to the second device for the purpose of transferring data via the shared connection · Connecting to the wireless network using the information enabling connection

[0023] According to one embodiment, the method further includes registering the third device with the cloud server, including setting up a wallet for transaction payments at the cloud server.

[0024] The second aspect relates to a third communication device including a processor and a memory containing software code, the third communication device being configured to execute one of the methods disclosed herein.

[0025] The third aspect relates to a method for data transfer on a communication network, the system comprising the following. · A first communication device including a communication interface configured to provide the following: ○ A wireless connection to a second communication device ○ A wireless access point for providing a wireless network The second device includes a communication interface configured to provide a shared connection to a communication network to the first device, the shared connection being adapted to enable data transfer on the communication network · A third communication device including a communication interface for connecting to the wireless network of the access point of the first device The method includes the following in the second device. · Enabling the shared connection · Configuring the first device so that the first device can connect to the shared connection · Providing information representing at least one proposal for transferring data via the shared connection for acquisition by the third device, wherein communication between the second device and the third device of the data upon acceptance of the proposal is performed only via the first device

[0026] According to one embodiment, the system further includes a cloud server, and providing information representing at least one proposal includes the following. · Transmitting the information to the cloud server by the second device, wherein the proposed information includes the amount of data to be transferred and the price for enabling the transfer of the amount of data

[0027] According to one embodiment, the information includes the current geographical location of the second device.

[0028] According to one embodiment, the information includes an estimated time of the presence of the second device at the current geographical location.

[0029] A fourth aspect relates to a second communication device including a processor and a memory containing software code, wherein the third communication device is configured to perform one of the methods disclosed herein.

[0030] The fifth aspect relates to a method for data transfer over a communication network, and the system includes the following: • A first communication device including a communication interface configured to provide the following: ○ Wireless connection to the second communication device ○ Wireless access point for providing a wireless network The second device includes a communication interface configured to provide a shared connection to the communication network to the first device, the shared connection being adapted to enable data transfer over the communication network. A third communication device, including a communication interface for connecting to the wireless network of an access point of the first device, is a method that includes the following in the first device: • Connect to the shared connection of the second device. • To provide the wireless network for connection by a third device. - Transferring the data between the second device and the third device in response to information indicating acceptance by the third device of a proposal to transfer the data via a shared connection of the second device.

[0031] A sixth aspect relates to a communication device including a processor and memory containing software code, wherein the third communication device is configured to perform one of the methods disclosed herein.

[0032] A non-temporary computer-readable storage medium that, when executed, includes instructions causing a processor of a computing device to perform steps in accordance with one of the methods disclosed herein. [Brief explanation of the drawing]

[0033] Exemplary embodiments will be better understood from the detailed description and accompanying drawings provided for illustrative purposes only. [Figure 1] This is a schematic diagram of a system according to a non-limiting embodiment. [Figure 2] This is a schematic diagram of one of the devices in the system shown in Figure 1. [Figure 3] This is a screen copy of an application run by one of the devices in Figure 1 to provide a data volume for use according to a non-limiting embodiment. [Figure 4] This is a screen copy of an application run by another device in Figure 1 to request a data volume for use according to a non-limiting embodiment. [Figure 5] This is a flowchart of how the application is implemented according to a non-limiting embodiment. [Figure 6] This diagram schematically illustrates the use of a cloud server within the system described above, according to one embodiment. [Figure 7] This diagram schematically illustrates the use of a cloud server within the system described above, according to another embodiment. [Figure 8] This diagram schematically illustrates the use of a cloud server within the system described above, according to yet another embodiment, including the use of an electronic wallet on a user device. [Figure 9] This figure schematically illustrates the use of a cloud server within the system described above, according to yet another embodiment, including the use of an electronic wallet on the server. Detailed description of the invention

[0034] Various exemplary embodiments will be described more fully with reference to the accompanying drawings. However, certain structural and functional details disclosed herein are representative only for the purpose of illustrating the exemplary embodiments. Exemplary embodiments may be embodied in many alternative forms and should not be construed as being limited to the embodiments described herein.

[0035] Those skilled in the art will understand that any function, engine, block diagram, flow diagram, state transition diagram, message sequence chart, and / or flowchart described herein represent a conceptual diagram of an exemplary circuit embodying a principle. The functions, actions, or steps described herein can be implemented in hardware, software, or any combination thereof, and the order of these functions, actions, or steps may differ from those presented. When implemented in software, the functions and blocks in the block diagrams and / or flowcharts can be implemented, for example, using software code executed by a processor or processing unit.

[0036] In this description, a functional block referred to as "means configured to perform..." should be understood as a functional block containing circuitry adapted to or configured to perform a particular function. Furthermore, any entity referred to as "means" in this specification may be implemented as one or more separate entities or within entities that provide additional functions. Where provided by a processor, a function may be provided by a single processor or multiple processors. Furthermore, the term "processor" includes one or more of the following: digital signal processors, remote processors, graphical processing units ("GPUs"), dedicated or general-purpose circuitry, read-only memory for storing software, random-access memory, and non-volatile storage.

[0037] The present invention addresses the above technical challenges by introducing a novel peer-to-peer mobile data sharing and trading system that utilizes a small electronic device (named "#dot") that is different from the device providing network access via a shared connection (e.g., a mobile phone) and different from the user device seeking to obtain a connection. The intermediate device (i.e., the "#dot" device) connects to a device that can provide a shared connection via a wireless connection such as WiFi (IEEE 802.11) or Bluetooth®. The intermediate device functions as a mobile access point, creating an independent wireless network that user devices seeking a connection can access.

[0038] In practice, it is the intermediate device that effectively utilizes the shared connection. For this purpose, the intermediate device and the device capable of providing the shared connection on the cellular network are configured ("paired") to allow the intermediate device to use the shared connection under the control of the person controlling the device capable of providing the shared connection. Authentication information necessary to allow access to the shared connection, such as a password and the name of the device providing the shared connection, is used only during the pairing phase between the intermediate device and the device capable of providing the shared connection and is not communicated to any user device requesting a connection. The person controlling the device capable of providing the shared connection ("seller") determines one or more conditions regarding the use of the shared connection for data transfer by user devices via the intermediate device (e.g., data volume limits, data volume pricing, current geographical location or time spent near it). The intermediate device creates a wireless network and allows user devices to connect in a simple manner. For example, a user device can easily find the intermediate device's wireless network based on the characteristics of the network identifier, for example, this identifier is known to the user device in advance. The user of the user device ("purchaser") can review and accept the terms of use (e.g., the purchaser can accept paying a specific price for a certain amount of data). In this case, the intermediate device can be used for data transfer under accepted conditions.

[0039] In this way, authentication information for devices that can share connections is not communicated to user devices, and the anonymity of the person controlling the devices that can share connections is maintained.

[0040] Figure 1 is a block diagram of a system showing a wireless hotspot device 101 (also called a seller user device), an intermediate device 102, and a buyer user device 103 according to one or more embodiments. The wireless hotspot device 101 provides internet connectivity. The wireless hotspot device 101 and the intermediate device 102 can communicate using wireless connectivity. For example, the wireless station interface of the intermediate device 102 can connect to the access point of the hotspot device 101. The intermediate device 102 and the buyer user device 103 communicate over a specific wireless network created by the intermediate device 102, as disclosed herein. The user device 103 may be any device configured to utilize internet connectivity, including but not limited to smartphones, personal computers, tablets, and wearable devices.

[0041] Intermediate device 102 knows, or is provided with, the information necessary to connect to hotspot device 101. The connection between the two devices 101 and 102 is also referred to as the two devices being "paired".

[0042] According to one non-limiting embodiment, the intermediate device connects to only one hotspot device at a time.

[0043] A typical use case is a hotspot device (a mobile phone as described in this embodiment). This includes the fact that the intermediate device is controlled by the same person. This person uses the intermediate device to create a specific wireless network that is easily accessible, providing that person a certain degree of anonymity compared to providing direct access to the shared connection provided by the hotspot device.

[0044] According to one non-limiting embodiment, an unpaired intermediate device performs the following: • Creates a wireless network that can provide a shared connection and is visible and identifiable by compatible devices that request pairing with it. • When a request is received from a hotspot device running a software application that can perform pairing over a wireless network, it provides the pairing password. Any compatible hotspot-enabled device can be paired with the intermediate device. Once this is complete, the seller user device enables connection sharing, allowing the intermediate device to connect as a hotspot. The seller user device may need to disable WiFi in order to function as a hotspot. According to a modified embodiment, the pairing password is well known and identical across all intermediate devices; that is, it is known in advance to the device that you wish to pair with the intermediate device.

[0045] According to one or more embodiments, a wireless network created by the intermediate device 102 for access by the user device 103 has a predetermined identifier that allows the user device to identify the wireless network as providing connectivity as described. For example, the wireless network has a predetermined SSID, e.g., "#dot:dot". The predetermined name is known to the user device and allows it to discover the wireless network provided by the intermediate device.

[0046] According to one embodiment, several pairs of intermediate devices and hotspot devices may be within the wireless range of the purchaser user device. In such a case, since the different wireless networks created by the intermediate devices have the same SSID, two such networks created by intermediate devices paired with different hotspot devices are not distinguishable by their SSID. However, they are distinguished within a software application running on the purchaser user device. Through this application, the purchaser user device can see the surrounding intermediate devices and select the one it wishes to connect to.

[0047] Figure 2 is a schematic block diagram of an intermediate device 102 according to one or more non-limiting embodiments. The intermediate device includes a processor 201. The intermediate device also includes a wireless radio 203 that provides wireless network access point functionality. For example, the radio 203 is an IEEE 802.11 compliant radio. The intermediate device 102 also includes a wireless station interface 204 for connecting to a wireless hotspot 101. Although the processor 201 and radio 203 are shown separately, in practice they may be integrated into a single component or shared among two or more components. The processor may be a microcontroller. For example, the processor may be Espressif's ESP32 or ESP8266, Nordic's nRF7002, or Texas Instruments' CC32x0 or CC3235. These processors integrate some of the wireless radio functionality. In one embodiment, the radio 203 is compatible with the wireless radio frequencies of a smartphone, i.e., currently 2.4 GHz or 5 GHz. The intermediate device also includes memory 202 for holding software code. When the processor 201 executes the code, it causes the device 102 to perform the method described herein.

[0048] According to one or more embodiments, the intermediate device 102 is configured to relay any compatible wireless hotspot, such as a hotspot arising from a shared mobile phone connection. As described above, the wireless hotspot device 101 has an internet connection. The wireless station (STA) of the intermediate device 102 can connect to the access point of the hotspot device 101, and the access point (AP) 203 of the intermediate device creates a wireless network with a predetermined SSID, for example, "#dot:dot", that is visible to other devices.

[0049] Devices 101 and 103 each include a communication interface for performing the disclosed types of communication (e.g., cellular and wireless LAN), as well as memory containing a processor and software code.

[0050] Any purchaser user device requesting a connection, such as a mobile phone, can connect to an intermediate device or a wireless network created by the device, either without a password or with a publicly known password. However, the purchaser user device does not know the password to the shared connection.

[0051] In the following embodiments, the hotspot device and the intermediate device are described as being controlled by the same person. However, this is merely an illustrative use case, and the teachings derived from the embodiments are extended to use cases where the hotspot device and the intermediate device are controlled by different people.

[0052] The person controlling the hotspot device paired with the intermediate device creates an account in a software application, such as an application running on the controller's hotspot device or another device. This person is also referred to as the "seller."

[0053] According to one or more embodiments, the seller's account information includes information that allows a third party (e.g., a buyer using the buyer user device 103) to make payments to that person's bank account, PayPal or Stripe account, or other type of financial account. This information may be, for example, a tag. The tag identifies the account but does not allow the buyer to directly identify the seller.

[0054] According to one or more embodiments, when pairing an intermediate device with a hotspot device, the application of the hotspot device shares the amount of data provided by the seller (e.g., gigabytes) and the aforementioned financial tags.

[0055] Depending on the optional features, hotspot devices may also share the price of data usage. The price may be zero (if the seller wants to provide data capacity for free) or not.

[0056] Optionally, the hotspot device application also shares an estimate of the seller's presence time at the geographical location where the seller is sharing the connection.

[0057] The information described in the previous two paragraphs, as well as the identifier of the intermediate device (e.g., MAC ID number), can be obtained from the intermediate device by a third-party device (such as a purchaser user device requesting a connection).

[0058] Figure 3 shows an exemplary screen displayed by the application to a specific seller offering a particular amount of data, according to a non-limiting embodiment. For example, the amount of data may correspond to the sum of uploaded and downloaded data. In Figure 3, the hotspot device 101 is a mobile phone. The application requests input for the amount of data and the price the specific seller is offering.

[0059] Optionally, the application displays offers from other sellers. This provides a benchmark for comparing prices offered by other sellers, and if this option is implemented, it helps a particular seller determine their own price.

[0060] According to one non-limiting embodiment, a buyer user who wishes to purchase data capacity creates an account. Account creation can be performed using the same application used by the seller (i.e., the application provides both an interface for the seller to provide data capacity and an interface for the buyer seeking a connection via the intermediate device to obtain data capacity). The buyer connects to the wireless network created by the intermediate device using their device, for example, their mobile phone.

[0061] Optionally, the buyer can locate the presence of several intermediaries on a map within the application that propose data amounts for mobile internet access, and can see the amount of data available at each. Optionally, the buyer can also obtain and verify the estimated presence time of sellers. For example, they can verify that the seller's presence sufficiently overlaps with the buyer's own neighborhood so that the purchased data amount can be used. This information may also influence the amount of data the buyer decides to obtain from a particular seller user. Once a proposal is selected, the buyer user accesses a transaction platform where the buyer user enters their credit card or online payment account credentials and authorizes future payments. Optionally, the application includes a "wallet," where the buyer user prepays data amounts, such as gigabytes of data, which are stored in the wallet and can be used as currency tokens to pay for desired data amounts when connecting. Using the wallet has certain advantages, including: (i) the wallet enables a single payment for multiple connections, reducing transaction fees; and (ii) the wallet can be replenished through direct money transfers using credit cards and appropriate digital money transfer protocols, or through the sale of data amounts as described above.

[0062] After this transaction is verified, the intermediate device receives an encrypted verification code from the buyer user's device application, which includes the buyer user's payment details and confirmation that the payment has been approved. The intermediate device then forwards this verification to the application running on the mobile phone 101, which enables internet access to the mobile phone 101's shared connection. After the transaction is verified, a unique password or code is generated for the buyer user, and the buyer user's device 103 is granted access to the intermediate device's wireless network. The intermediate device 102 acts as a root node and accesses the internet via the seller's mobile phone 101, which acts as a router.

[0063] According to one or more embodiments, the password is unique to the purchaser user and is valid only for the duration of the transaction. This differs from direct access of the purchaser user's device to a shared connection, which does not allow dynamic assignment of passwords to individual users based on the transaction.

[0064] At this point, the buyer user device 103 can access the internet via the shared connection of the mobile phone 101.

[0065] According to the modified embodiment, payment is made locally using the respective electronic wallets of the buyer and seller.

[0066] This internet link can be interrupted in various ways. • If the amount of data purchased by the buyer user is equal to the amount of data consumed as measured by #dot: In this case, #dot sends a termination message to the #dot:dot server, the server sends a notification to the buyer user's application, which is displayed on the buyer user's device screen. #dot terminates the connection, the server executes a financial transaction for the amount corresponding to the amount of data initially reserved by the buyer user, and invalidates the financial tag used to initially open the connection. • The seller or buyer, along with their respective devices, leaves their previous geographical location, and the distance to the intermediate device exceeds the intermediate device's wireless network range. This range is typically on the order of 30-50 meters, depending on the environment and the presence of obstacles. In this case, the connection is interrupted by the intermediate device, and a financial transaction is executed by the server for an amount proportional to the amount of data actually used relative to the amount of data initially reserved by the buyer. The financial tag used to initially open the connection is permanently invalidated.

[0067] According to one or more embodiments, multiple intermediate devices providing data capacity are available within the scope of the user device. Software applications running on the user device can be configured to collect relevant information and facilitate the buyer user selecting one from several suggestions. Each intermediate device creates a wireless network with the same SSID and is therefore indistinguishable by network name alone. However, each intermediate device collects and shares with the buyer user device the amount of data it shares from the paired seller user device, the expected duration of use, and its own identifier (such as MAC ID).

[0068] By sharing this information within an application running on the buyer user's device, the intermediary device allows the application to display each offer from all specific nearby sellers on the buyer user's device screen, enabling the buyer user to select the most suitable option. The application presents a comprehensive list of sellers and their specific offers, allowing the buyer user to make informed decisions based on their requirements. Once the buyer selects a specific seller and completes the financial transaction, the buyer effectively selects a specific MAC ID number associated with the appropriate intermediary device, and bank authorization and activation proceed as described above.

[0069] Figure 4 shows an exemplary screen displayed to a buyer attempting to reserve a specific amount of data by an application running on the buyer user device 103. The screen displays a field for the buyer to enter the desired amount of data. Further on the screen, a list of seller aliases, prices per amount of data, and the amount of data each seller has made available is displayed. In the example shown, the list is the result of filtering all offers based on the desired amount of data.

[0070] Figure 5 is a flowchart showing an overall method 500 performed by an application according to one or more embodiments. The illustrated method assumes that a single application is used by both sellers and buyers. Of course, the functions related to buyers and sellers can also be implemented in separate applications.

[0071] The flowchart in Figure 5 is broadly divided into four sections: section 501 for account creation, section 502 for intermediate device pairing, and sections 503 and 504 for data purchase and sale. Interconnections exist between the different sections, but not all of them are detailed here. The application presents the user with three consecutive options: whether to connect for the first time, acquire or pair an intermediate device, or the user wants to purchase or sell data, each option leading to one of the above sections.

[0072] In Section 501, the application asks the user in 501.1 whether it is their first time connecting or if they want to pair a new intermediate device with the hotspot. If yes, the user can watch a video in 501.2 explaining the principles of using the intermediate device. Account creation is suggested in 501.3 and can be done in 501.4 if the user decides to do so, where the user enters authentication information, including bank account information.

[0073] Section 502 states that the application provides pairing and / or acquisition of an intermediate device in 502.1. If the user does not have an intermediate device and / or wishes to acquire a new intermediate device, they are directed to a corresponding website (502.2, 502.3). If the user wishes to pair an intermediate device, pairing and connection with the cellular shared connection is performed in 502.4 and requires various user inputs. The application prompts the user to confirm that the connection was successful, i.e., confirm that the intermediate device is displaying the appropriate signal (e.g., a white LED is lit) in 502.5. Pairing can be performed via a wireless connection, e.g., a WiFi connection between a hotspot-enabled device and an intermediate device. Once the devices are paired, the hotspot mode of the hotspot-enabled device is activated, and the intermediate device can access the shared connection on the cellular network.

[0074] Section 503 states that the application provides the option to purchase or sell data volumes in 503.1. Note that prior pairing is not required when purchasing data.

[0075] If a user wants to purchase a volume of data, they are asked in 503.2 whether they are connected to the intermediate device's wireless network. If not, the user is asked in 503.3 to connect to at least one such wireless network. If the user is already connected to the intermediate device's wireless network, they are asked in 503.4 to select the volume of data they wish to purchase. Next, a price list of one or more corresponding offers from one or more sellers / owners is displayed. The user is asked in 503.5 to select an offer with a specific price, or in 503.6 to reject the offer and indicate that the price is unacceptable. In this case, the user is asked to check if they can connect to other intermediate devices elsewhere to obtain other offers. If an offer is selected, the application checks in 503.7 whether the user has an account. If not, the user is asked if they wish to create an account (in 501.3). However, in this case, the application requests verification of the price of the selected offer in 503.8. Then, transaction verification is performed as described above, and the application initiates a message to the intermediate device, allowing the user device to receive or send data via the shared connection through the intermediate device. If the data capacity is fully utilized (tested in 503.10), the session ends in 503.12 and full payment to the owner account begins. Otherwise, if the session is simply interrupted, a proportional price is calculated in 503.11 and partial payment begins in 503.13. The session can be continued at another time (e.g., using the code shown in Figure 3). If requested by the user, the trade dashboard (report) may be displayed in 503.14. Otherwise, the method returns to the buy and sell selection suggestions in 503.1. Similarly, a dashboard of all past trades can be displayed on request in 504.9, or a global trade dashboard can be displayed in 504.10.

[0076] If a user wants to sell a volume of data, the application checks in 504.1 whether the intermediate device is connected to the hotspot device, i.e., the seller's mobile phone in this example. If not, the user is asked if they want to view the transaction dashboard (504.9). In this case, the application displays fields for the user to enter the volume of data to sell and the corresponding price (504.2 and 504.3). Next, the application checks if the user has an account (504.4). If not, the user is asked if they want to create an account (returning to 501.3). If the user has an account, information about the offer is sent to the intermediate device, and the application waits in 504.5 for the offer to be accepted. Once the offer is accepted, a session password or code is created by the seller's application in 504.6 and sent to the buyer user device and the hotspot device.

[0077] To maintain anonymity, it is preferable that the seller's real name is not displayed by the application. Rather, an alias chosen by the seller may be displayed, or even the alias may not be displayed at all. The #dot controllers and their offering characteristics (GB amount, length of stay in the vicinity) are displayed in real time on a small map, and people can select the #dot they want to connect to by examining this map.

[0078] In this variant, only the proposal is listed. The seller's name, whether real or alias, is not displayed in this variant.

[0079] Optionally, at the end of a data sharing session, both the buyer and seller can rate each other and assess the quality of service through a common five-star rating scheme, for example: the buyer can rate the reliability of the seller's initial statements regarding the seller's presence at the initial location, pricing, and the bitrate experienced. The embodiments shown in Figures 6 to 9 illustrate the use of a server for centralized account creation and proposal collection, and unless otherwise specified, the aforementioned principles are valid.

[0080] Figure 6 is a schematic diagram illustrating the use of a cloud server within the system described above according to one embodiment. The seller user device is paired with the intermediate device as previously described. According to Figure 6, seller information is first sent to the cloud server by the seller user device at 601. The information includes information indicating the geographic location of the seller user device. Next, seller information (such as the amount of data offered, price, and time of existence) is retrieved by the buyer user device from the server 600 at 602 based on the proximity of the seller user device's location to the buyer user device's location. At 603, the buyer user device sends a message to the cloud server indicating the buyer's selection regarding the offer and information identifying how to make the payment later. The cloud server verifies the payment information and approves the transaction. At 604, the buyer user device obtains wireless network authentication information corresponding to the selected seller intermediate device, and at 605, uses these authentication information to connect to the wireless network and benefit from the shared connection of the seller user device. In step 606, the cloud server obtains the amount of data consumed by the purchaser user's device through communication with the application running on the purchaser user's device. In step 607, the cloud server checks whether the amount of data consumed by the purchaser user's device has reached a threshold, i.e., the amount obtained. If so, the transaction is terminated and payment is initiated in step 608. As mentioned above, proportional payment can also be performed in case of interruption.

[0081] Figure 7 schematically illustrates the use of a cloud server within the system described above according to another embodiment. The method is similar to that in Figure 6, with corresponding steps (e.g., 701 corresponding to 601), and the seller information is centralized on server 700. The difference is that in 702, information describing the seller user device and available offers as a function of the geographical location of the buyer user device is obtained from the cloud server not via a direct connection to the cloud server, but via a wireless network of intermediate devices to which the buyer user device can connect. Otherwise, the method proceeds as described above.

[0082] Figure 8 schematically illustrates the use of a cloud server within the system described above according to yet another embodiment. In this embodiment, payment involves electronic wallets on the seller's device and the buyer's device. The seller user device is paired with the intermediate device as described above. After the device is registered with the server and the server verifies the payment information of the buyer and seller user devices, the payment is processed locally between the wallets of the buyer and seller user devices, and no interaction with the server is required during the payment itself.

[0083] Steps 801 through 816 are as follows: (a) Initial registration phase 801. Create a seller account on the seller device, including: bank authentication, seller wallet information 802. Registration on the server and creation of a seller user ID on the server (the user ID can be used for both selling and buying data capacity, but for clarity purposes, the user ID as herein is shown as buyer (user) ID and seller (user) ID). 803. The seller user ID is transmitted to the seller user device by the cloud server 804. The seller's payment information (bank authentication, seller wallet information) is verified (only once) by the cloud server. 805. The buyer account is created on the buyer user device, including: bank authentication, seller wallet information. 806. The buyer is registered on the server and a buyer user ID is created. 807. The buyer user ID is sent to the buyer user device by the cloud server. 808. The buyer's payment information (bank authentication, seller wallet information) is verified (only once) by the cloud server. (a) Buyer's Device Connection Phase 809. The Buyer's User Device connects to the wireless network of nearby intermediate devices and obtains available seller offer information (data volume, selling price, and optionally, existence time) from sellers near the Buyer's User Device. 810. The Buyer selects an offer using the Buyer's User Device. 811. Local verification of payment from the Buyer's wallet using the Buyer's User Device. 812. The Buyer's User Device verifies the Buyer's User ID and wallet information and approves the transaction. 813. Data transfer over the shared connection is authorized as specified in the accepted offer. 814. If the connection is interrupted, the Buyer's wallet is updated (e.g., the amount is withdrawn), and the Seller's wallet is updated (e.g., the amount is credited). (b) Bank Transfer The following steps can be implemented at a later stage, for example, periodically: 815. The seller device updates the online wallet / information on the server. 816. The cloud server initiates payment to the seller's bank account based on the (updated) seller wallet information.

[0084] According to the modified embodiment, an optional registration check is implemented. However, this security check can be used in combination with any of the above embodiments in which the user device registers with the server. The method according to this embodiment includes the following: • The buyer's device detects the wireless network of intermediate devices connected to the seller's device. • The buyer's device connects to the intermediate device's wireless network. Next, the intermediate device checks whether the buyer is registered with the server. If not, the intermediate device disconnects the buyer's device.

[0085] Registration verification reduces the number of devices connecting to the wireless network that are not registered with the server and do not use software applications. Therefore, the server verifies the connection of purchaser devices and limits intrusions.

[0086] The check can be performed as follows: • The buyer's device knows an identifier ("ID key") that proves the buyer's registration with the server. This identifier may also be useful for other purposes (e.g., identifying the buyer within the system). • When the buyer's device connects to the wireless network, it transmits its ID key to the intermediate device. The intermediate device sends the ID key to the server, and the server responds by indicating whether the ID key corresponds to a registered purchaser. • The ID key is provided to the purchaser's device by the server during the registration process, Conversely, or generated and communicated using any appropriate process

[0087] In another embodiment, as shown in the schematic diagram of Figure 9, the buyer's and seller's wallets are located on a cloud server rather than on the buyer's and seller's user devices. Then, the device, typically an intermediate device 102, can verify the credit level of the buyer's wallet on the server.

[0088] Both the seller device 101 and the buyer device 103 register with the server 900. In Figure 9, this stage is shown by each device user (seller, buyer) creating an account on the server (see 901, 903 respectively) to enable the sale and / or purchase of data capacity, and the account information is maintained by the server (see 902, 904 respectively). The account information includes the information necessary to implement the electronic wallet and bank information for crediting to the wallet, or conversely, information for performing transfers from the wallet to the user's bank account. For example, a buyer user can credit to the wallet if the buyer user device has a connection to the server (including cases where this connection is achieved via an intermediate device and a seller user device).

[0089] The seller user device is paired with the intermediate device 102 as described above and communicates its proposal along with its geographical location to the server. To provide a diagram of the registration check of the above option, Figure 9 shows an implementation of such a check. At 905, the buyer user device receives an "ID key," i.e., proof of registration, and identifies the buyer within the system. The buyer can transfer money tokens to an electronic wallet on the server, for example at 906 or at another stage. The buyer can then connect to the intermediate device's wireless network using a software application (907) and request a proposal. For example, if the wireless networks of different intermediate devices use the same identifier, the buyer device 103 can use a predefined network identifier to discover the wireless network of the intermediate device 102 and connect to this wireless network.

[0090] When connected to a wireless network, the purchaser user device transmits the following: • Request for proposals for intermediate devices • ID key to prove registration • Its geographical location (which can also be derived from the intermediate device's own location)

[0091] The embodiment in Figure 9 also shows an additional option for implementing a so-called application key ("app key"). The application key is a code that allows the device to determine whether the software application of another device communicating for the purpose of purchasing and / or selling data capacity is a genuine application. The application identifier is unique to the application of, for example, the purchaser device. This application identifier is also transmitted from the purchaser user device to the intermediate device.

[0092] Using the received information, the intermediate device performs the following using the shared connection of the seller user device (on 908): If the option is implemented, the server will use the ID key to verify that the buyer is registered, and if the check result is negative, the buyer user device will be disconnected. • If the option is implemented, the server verifies that the application used by the purchaser user device is authentic as a function of the application identifier. • As a function of geographical location, retrieve a list of proposals from seller user devices within the area from the server (note that this step does not need to be performed if any of the optional checks are negative).

[0093] The intermediate device returns a list of proposals to the buyer user device. The buyer then submits the proposals ( The intermediate device validates the data in block x for the value of y, and this information is returned to the intermediate device. Using the ID key that identifies the buyer, the intermediate device checks on the server whether the credit level in the buyer's wallet is sufficient to pay for the requested amount of data. If so, the intermediate device also validates the proposal (909) and opens access to the shared connection (910). Otherwise, the intermediate device may ask the buyer user device to reduce the amount of data to retrieve or to credit it to their wallet.

[0094] The intermediate device periodically retrieves a counter value from the buyer user device representing the amount of data actually transferred via the shared connection. The server is updated with this amount. The intermediate device also checks whether the amount specified in the validated proposal has been reached. If the specified amount has not been reached, the intermediate device repeats the check of the counter value (911, 912). The intermediate device may also send information to the buyer user device representing the amount of unused data in the validated proposal (912). The buyer user device may display the amount through a software application.

[0095] Once the data capacity of the validated proposal is fully utilized, the intermediate device will perform the following: cormorant. • Send a message to the buyer's user device indicating that the amount of data used for the verified proposal has been utilized. • Disconnect from the shared connection. • Update the server based on the amount of data used.

[0096] Next, payment is made by properly updating the wallets of both the buyer and the seller.

[0097] According to another option that may be used in any of the embodiments described above, the buyer user device obtains limited access to the seller device's shared connection when connected to the intermediate device's wireless network, but also before accepting the proposal for the purpose of facilitating the acquisition, review, and acceptance of the proposal. For example, the buyer user device may be permitted to connect to a specific URL, such as the URL of a cloud server if such a cloud server is used, or may be permitted to access a URL of a website from which a software application or its updates can be acquired.

[0098] According to a modified embodiment, each intermediate device's wireless network is assigned a different network identifier. These identifiers are broadcast by the intermediate device and have a format that can be recognized as corresponding to the intermediate device's wireless network from which a buyer user device may obtain a connection via a shared connection. Advantageously, the identifier format includes a predefined code, e.g., a six-character code, indicating that the identifier corresponds to the intermediate device's wireless network proposing the functionality described herein. Advantageously, the identifier may include additional data characterizing the proposal made by the seller user device paired with the intermediate device using this identifier for its wireless network. The additional data may include time intervals in which the seller user is present within a specific range. The format could be, for example, of the following type: #dot.dot_Price=0.1_20min_ABCDEF, where "20min" corresponds to the time the seller user is present.

[0099] According to the embodiments described below, no session password or code is used. Instead, a token verified by the cloud server is used. In this embodiment, both the seller user device and the buyer user device are mobile phones.

[0100] 1. The server obtains (or already owns) a list of approved intermediate devices. The list may include, for example, the identifier of the intermediate device and the MAC ID of the intermediate device. The list of MAC IDs can be provided to the server, for example, by the manufacturer of the intermediate device.

[0101] 2. The seller must obtain verification from the server that they are a legitimate seller, meaning their phone number has been verified and they are using an approved intermediate device. (i) The seller provides the seller user device's phone number through a software application running on the seller user device. The seller user device sends the phone number to the server. The server sends a one-time code to the seller user device via the cellular network, and the seller enters the one-time code into the software application for transmission to the server: If a valid code is received by the server, the server returns a token called a “valid seller token” to the seller user device. If an invalid code is returned, the server returns nothing. (i) The seller pairs the intermediate device with the user device using a software application. Once complete, the intermediate device sends its MAC ID to the server via the shared connection of the seller's user device. If the MAC ID is approved, i.e., it is on the list of approved intermediate devices, the server returns a token called an "approved intermediate device token" to the seller's user device. If the MAC ID is unknown to the server, the server returns nothing.

[0102] 3. The seller sends a proposal to the server using a software application running on the seller's user device. This proposal is accompanied by a valid seller token and an authorized intermediate device token. The server checks the tokens and authorizes the seller's proposal to be displayed in the software applications of potential buyers within the seller's scope.

[0103] 4. The buyer must obtain verification from the server that they are a valid buyer, meaning their phone number is verified and they have sufficient credit in their wallet, thus enabling them to perform financial transactions related to the use of data volume from the seller via the service.

[0104] The buyer's user device connects to the seller's paired intermediate device. The buyer provides the buyer's user device's phone number through a software application running on the buyer's user device (for example, via a shared network connection established during the pairing process, which may be used exclusively for this purpose). The buyer's user device sends the phone number to the server.

[0105] The server sends a one-time code to the buyer's user device via the cellular network, and the buyer enters the one-time code into a software application. The code is sent to the server, which checks the amount of data or currency in the wallet. If a valid code is received by the server and the amount in the wallet is higher than a minimum threshold amount (e.g., €0.20), the server returns a token called a "valid buyer token" to the buyer's user device. If an invalid code is returned, the server returns nothing. Optionally, if the code is valid but the amount in the wallet is lower than the threshold amount, the server returns a temporary token and redirects the buyer to a page in the software application to allow them to credit their account to exceed the threshold.

[0106] 5. Next, the buyer user device sends a valid buyer token to the intermediate device along with the relevant requested GB amount (i.e., the proposal is accepted as described above) in order to request the use of the shared connection.

[0107] 6. The intermediary device sends the following to the server: the request, a valid seller token, an authorized intermediary device token, and a valid buyer token.

[0108] 7. The server verifies the validity of the token. If all checks are positive and the buyer's wallet balance is sufficient compared to the accepted proposal, the server allows the intermediate device to use the shared connection. Otherwise, if the server shows or does not verify at least one negative check result, the intermediate device disconnects the buyer user device.

[0109] If a buyer user device connects to the same intermediate device or other intermediate devices multiple times, a new buyer authorization token must be obtained each time so that the wallet balance is checked each time.

[0110] The various embodiments described offer some or all of the following advantages:

[0111] By utilizing intermediary devices and applications, sellers can seamlessly share surplus mobile data plans, and buyers can easily find and purchase data that precisely matches their requirements. This revolutionizes how users share and acquire mobile data, providing a flexible, cost-effective, and anonymous solution to problems associated with wasted data and inflexible data plans.

[0112] Furthermore, the limitations of existing methods are overcome by eliminating the need for sellers to share passwords for shared connections or reveal their identities. Seller anonymity is maintained, and privacy and security are ensured throughout the entire transaction process.

[0113] Furthermore, by applying proportional payment calculations, fair compensation for shared mobile data can be ensured, providing a fair solution for both buyers and sellers.

[0114] A rating system may be incorporated, which helps address concerns about the reliability of seller information and the quality of service. This promotes transparency and trust within the community of intermediate device owners, improving the overall user experience.

[0115] In conclusion, a comprehensive solution is provided to address technical issues associated with wasted mobile data, inflexible data plans, and a lack of anonymity in data sharing. By leveraging intermediaries, applications, secure transactions, and evaluation mechanisms, users can efficiently share and purchase mobile data, ensuring optimal resource utilization and improving the overall connectivity experience.

[0116] This description discloses a peer-to-peer mobile data sharing system that includes an intermediate device, a dedicated application, and a secure transaction mechanism. A seller equipped with the intermediate device establishes a wireless network with a predetermined name to advertise data available for sale. The application allows sellers to specify the amount of data, set a selling price, and enable buyers to identify suitable sellers.

[0117] The buyer can connect to the application, browse a list of sellers, and view their respective selling prices (if available) and / or the number of GBs available for sale and / or the duration of their stay (e.g., within 100 meters of the initial point where the seller began sharing the GBs). Once a seller is selected, a secure transaction begins, and future payment authorizations are processed. Upon completion of the transaction, a unique session password or code may be generated, granting the buyer access to the shared connection via a wireless network created by the intermediate device. The intermediate device acts as a root node, accessing the internet via the seller's smartphone, which acts as a router. The session password or code can be generated by the cloud server as a function of, for example, the identifier of the buyer user device, the identifier of the seller user device proposing the buyer's selected offer, and the identifier of the intermediate device paired with the seller user device. These identifiers could be the MAC ID of each device. The session password is sent from the server to the seller user device, which then sends it to the paired intermediate device, which then communicates the session password to the buyer user device. The buyer user device uses this session password to obtain unrestricted access to the intermediate device's wireless network (i.e., granting access to the shared connection).

[0118] The amount of data traded is determined based on the buyer's connection within the scope of the seller's intermediary equipment. Payment is calculated proportionally, considering the amount of data consumed versus the initial amount of data pre-booked by the user, ensuring fair compensation for shared mobile data. To facilitate buyer selection, sellers are asked to declare their expected availability upfront, although this commitment is not binding. Buyers can consider this information when selecting a seller based on their expected usage period.

[0119] Furthermore, an evaluation system has been proposed to assess the quality of service and the reliability of seller information. This would allow both buyers and sellers to provide feedback, increasing transparency and fostering trust within the dot-dot community.

[0120] In conclusion, a system and methods for efficient and anonymous peer-to-peer mobile data sharing will be introduced. By utilizing an intermediary device, sellers can offer unused data volumes for sale, and buyers can easily purchase data tailored to their needs. A secure transaction mechanism, rating system, and proportional payment calculation will revolutionize how users share and acquire mobile data, promoting flexibility, cost-effectiveness, and anonymity within the dot-to-dot community. Examples Example 1 - A method performed by a first communication device (102), wherein the communication device includes a processor (201), a memory (202) containing software code, and wireless communication interfaces (203, 204) for communicating with at least one second device (101), the second device The first device is a mobile phone, and the communication interface is further configured to provide a wireless network for access by at least one third device (103), and the processor causes the first device to perform a method when executing the software code, the method including: - Establish a connection with a predetermined second device in the shared connection mode of the second device. • Receiving a message from a predetermined second device, including the amount of data to be made available by the second device and the price of the said data, where the said data represents data passing through the cellular network to which the second device is connected. • Creating a wireless network - In response to a request message received from a designated third device via a wireless network, transmit a message to the designated third device that includes at least the amount of data and the price. - In response to information indicating price verification by a predetermined third device, provide the predetermined third device with access to a shared connection via a wireless network for data volume. The first communication device acts as an intermediary between a mobile phone and a third device that requires a connection via a shared connection provided by the mobile phone. The second and third devices do not communicate directly. The user of the third device does not need to know the actual identity of the user or owner of the second device. In other words, the user of the second device can remain completely anonymous. Example 2 - The method of Example 1, wherein a message from a predetermined second device (101) further includes an estimated time of presence at the current location of the owner of the second device. Example 3 - The method of Example 1, wherein the wireless network uses a predetermined SSID that identifies the wireless network as providing connectivity via a cellular network. Example 4 - The method of Example 2, wherein a predetermined SSID is common to multiple first communication devices. This predetermined SSID can therefore be known by a third device, for example, a third device running a software application adapted to enable the use of the first device as described. Example 5 - The method of Example 2, wherein a predetermined SSID is unique to the first communication device. Example 6 - A method according to any of Examples 1 to 4, wherein the wireless network is an IEEE 802.11 type network. Example 7 - A method according to any of Examples 1 to 5, wherein the first device provides the third device with either an alias representing the user of the second device, or no information regarding the identity of the user. Example 8 - A method according to any of Examples 1 to 6, wherein providing access to a shared network connection includes transmitting verification information to a second device, forwarding data requests from a predetermined third device to the second device, and forwarding responses from the second device to the predetermined third device. Example 9 - A communication device comprising a processor (201), a memory (202) containing software code, and a wireless communication interface (203) for communicating with at least one second device, wherein the second device is a mobile phone (101), and the communication interface is further configured to provide a wireless network for access by at least one third device (103), and the processor causes the first device to perform a method according to any of Examples 1 to 8 when executing the software code.

Claims

1. A method for data transfer over a communication network, wherein the system includes the following: - A first communication device (102) including communication interfaces (203, 204) configured to provide the following: ○ Wireless connection to the second communication device ○ Wireless access point for providing a wireless network The second device (101) includes a communication interface configured to provide a shared connection to the communication network to the first device, the shared connection being adapted to enable data transfer over the communication network. - A third communication device (103) including a communication interface for connecting to the wireless network of the access point of the first device. The method includes the following in the third apparatus: - The third device obtains information representing at least one proposal for transferring data via the shared connection of the second device. - In response to sending a message indicating acceptance of the received proposal, the third device receives access to a shared connection corresponding to the accepted proposal for transferring data according to one or more conditions of the accepted proposal, wherein the communication of the data between the second device and the third device is performed only through the first device.

2. The method according to claim 1, wherein, before enabling access, the accepted proposal A method that further includes verifying a transaction that authorizes payment of the price related to the proposal.

3. A method according to claim 1 or 2, wherein the wireless network has a network identifier that indicates to a third device that the first device is adapted to provide access to a shared connection.

4. A method according to claim 3, wherein the system comprises a plurality of first devices connected to each second device, each first device providing a predetermined wireless network, all predetermined wireless networks using the same network identifier, and the network identifier is known to a third device.

5. The method according to claim 4, wherein the acquisition of information by a third communication device representing at least one proposal for data transfer via a shared connection of a second communication device includes in the third device the following: - Detect the wireless network of the first device using the network identifier of the first device. A method for obtaining information representing at least one proposal for data transfer via a shared connection of a second communication device through a first device.

6. A method according to any one of claims 2 to 5, wherein information representing the proposal is A method including the amount of data to be transferred and the price for enabling the transfer of that amount of data.

7. A method according to any one of the prior claims, wherein the information representing the proposal further includes an estimated time of the presence of a second device at the current geographical location.

8. A method according to any one of the preceding claims, wherein the information representing the proposal does not include information relating to the identity of the user of the first apparatus.

9. A method according to any one of the prior claims, wherein the communication network is a cellular network and the second device is a mobile phone.

10. A method of any one of the preceding claims, combined with claim 2, wherein the verification of a transaction authorizing payment of a price related to an accepted proposal is performed by a software application executed by a third device, and the method further includes: - Transmission of information from the third device to the first device indicating transaction verification. - Transmission of information from the first device to the second device indicating transaction verification. - A method for enabling access to the shared connection by a second device in response to information indicating transaction verification.

11. A method according to any one of the preceding claims, further comprising, in a third apparatus: - Detection of the wireless network of the first device using a predefined network identifier. A method for obtaining information representing at least one proposal for data transfer via a first device.

12. A method according to any one of claims 1 to 9, wherein the system is cloud The methods further include servers (600, 700, 800, 900) and the following: A method comprising obtaining information from a cloud server by a third device, representing at least one proposal for data transfer of the second device as a function of the geographical location of the second device and the geographical location of the third device (602).

13. The method according to claim 12, further comprising the following in a third apparatus: - Sending information to the cloud server indicating that the proposal has been accepted (603) - Receiving information from a cloud server that enables a third device to connect to the wireless network of a first device connected to a second device for the purpose of transferring data via a shared connection (604) - Connecting to a wireless network using information that enables connection (605), method.

14. A method according to claim 12 or 13, further comprising: - A method for registering a third device with a cloud server (902, 904), including setting up a wallet for transaction payments on the cloud server.

15. A third communication device (103) comprising a processor and memory containing software code, wherein the third communication device is configured to perform a method according to any one of claims 1 to 14.

16. A method for data transfer over a communication network, wherein the system includes the following: - A first communication device (102) including communication interfaces (203, 204) configured to provide the following: ○ Wireless connection to the second communication device ○ Wireless access point for providing a wireless network The second device (101) includes a communication interface configured to provide a shared connection to the communication network to the first device, the shared connection being adapted to enable data transfer over the communication network. A third communication device (103) including a communication interface for connecting to the wireless network of the access point of the first device. The method includes the following in the second device: Enable shared connection. - Configure the first device so that it can connect to the shared connection. A method comprising: providing information representing at least one proposal for transferring data via a shared connection for acquisition by a third device, wherein communication of the data between the second and third devices upon acceptance of the proposal is performed only through the first device.

17. A method according to claim 16, wherein the system further includes cloud servers (600, 700, 800, 900) that provide information representing at least one proposal, the following: - A method for transmitting the information to a cloud server by a second device (601, 701), wherein the proposed information includes the amount of data to be transferred and the price for enabling the transfer of the amount of data.

18. A method according to claim 16 or 17, wherein the information includes the current geographical location of the second device.

19. The method according to claim 18, wherein the information is the current geographical location A method including the estimated time of the existence of two devices.

20. A second communication device (103) comprising a processor and memory containing software code, wherein a third communication device is configured to perform a method according to any one of claims 16 to 19.

21. A method for data transfer over a communication network, wherein the system includes the following: - A first communication device (102) including communication interfaces (203, 204) configured to provide the following: ○ Wireless connection to the second communication device ○ Wireless access point for providing a wireless network The second device (101) includes a communication interface configured to provide a shared connection to the communication network to the first device, the shared connection being adapted to enable data transfer over the communication network. A third communication device (103) including a communication interface for connecting to the wireless network of the access point of the first device. The method includes the following in the first device: - Connect to the shared connection of the second device. - To provide the wireless network for connection by the third device. A method for transferring data between a second device and a third device in response to information indicating acceptance by the third device of a proposal to transfer data via a shared connection of the second device.

22. A first communication device (103) including a processor and memory containing software code, wherein a third communication device is configured to perform the method according to claim 21.

23. A non-temporary computer-readable storage medium (202) comprising, when executed, an instruction causing a processor of a computing device to perform a step of any one of claims 1 to 14, 16 to 19, and 21.

Images