Enabling communication between a first user device of a first user and a second user device of a second user
A support server enables seamless communication across diverse applications by providing format conversion and communication details, addressing interoperability issues and simplifying user interactions.
Patent Information
- Application Number
- PCT/EP2025/062421
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-06
- Publication Date
- 2026-11-12
AI Technical Summary
Interoperability between different communication applications is patchy, requiring users to have multiple applications across platforms to communicate with various contacts, complicating the process and necessitating awareness of the correct platform and media type for each contact.
A support server facilitates communication by storing and providing communication details, including data format conversions, between user devices, enabling seamless interaction regardless of application discrepancies.
Enhances interoperability by allowing users to communicate across different applications without needing to know the specific platform or media type, simplifying the communication process and ensuring format compatibility.
Smart Images

Figure EP2025062421_12112026_PF_FP_ABST
Abstract
Description
ENABLING COMMUNICATION BETWEEN A FIRST USER DEVICE OF A FIRST USER AND A SECOND USER DEVICE OF A SECOND USERTECHNICAL FIELD
[0001] The present disclosure relates to the field of communication and in particular to enabling communication between a first user device of a first user and a second user device of a second user.BACKGROUND
[0002] Users today communicate with their user devices using many different communication applications such as WhatsApp, Snapchat, Facebook Messenger, Android messages, iPhone messages, Signal, Snapchat, etc. The applications use different media types, such as video, audio, text, as well as media formats within the media types. Furthermore, communication protocols vary between applications.
[0003] Interoperability between different communication applications is extremely patchy in the few instances that it is even possible. For instance, it is possible to message between Android messages and iPhone messages based on phone numbers, but the interoperability has limits in terms of media size, read receipts, encryption, etc. It is thus difficult to get interoperability between different users and their different applications. This leads to users having to get multiple communication applications across several platforms to be able to keep in touch with all personal contacts and knowing the communication application to use for each personal contact.
[0004] Hence, it is complicated for a first user to communicate with a second user. The first user needs to be aware which platform and with what media type to contact the second user.SUMMARY
[0005] One object is to improve interoperability between communication applications.
[0006] According to a first aspect, it is provided a method for enabling communication between a first user device of a first user and a second user device of asecond user. The method is performed by a support server. The method comprises: receiving, from the second user device, communication details for communicating with the second user device, the communication details comprising an indication of a second data format for communicating with the second user device receiving, from second user device, a message indicating that the second user device is associated with the second user; storing, in a database, the communication details in association with the second user device; receiving, from the first user device, a request for communication details for the second user device, the request comprising an identifier associated with the second user, and an identifier associated with the first user; determining that the second user device is associated with the second user based on the received message indicating that the second user device is associated with the second user; retrieving, from the database, the communication details being associated with the second user device; and sending a response to the first user device, the response comprising the communication details for communicating with the second user device.
[0007] The message may be cryptographically signed by a credential associated with the second user.
[0008] The method may further comprise: sending an approval request to the second user device, requesting approval that the first user is allowed to initiate contact with the second user; receiving an approval response from the second user device, confirming that the first user is allowed to initiate contact with the second user. In this case, the sending a response to the first user device is performed in response to receiving the approval response.
[0009] The communication details may comprise a plurality of indications of respective data formats for communicating with the second user device.
[0010] The request may be cryptographically signed by a credential associated with the first user. In this case, the method further comprises: verifying that the request is validly signed and the sending a response to the first user device is conditional to the verification being positive.[oon] The method may further comprise: providing at least one of code and data to provide conversion functionality to the first user device for converting communication between a first data format used by a first application in the first user device to the second data format.
[0012] The indication of data format may comprise an indication of a second application used for communication with the second user device.
[0013] The indication of data format may comprise an end point identifier of the second user device used by the second application.
[0014] According to a second aspect, it is provided a support server for enabling communication between a first user device of a first user and a second user device of a second user. The support server comprises: processing circuitry; and memory circuitry storing instructions that, when executed by the processing circuitry, cause the support server to: receive, from the second user device, communication details for communicating with the second user device, the communication details comprising an indication of a second data format for communicating with the second user device; receive, from second user device, a message indicating that the second user device is associated with the second user; store, in a database, the communication details in association with the second user device; receive, from the first user device, a request for communication details for the second user device, the request comprising an identifier associated with the second user, and an identifier associated with the first user; determine that the second user device is associated with the second user based on the received message indicating that the second user device is associated with the second user; retrieve, from the database, the communication details being associated with the second user device; and send a response to the first user device, the response comprising the communication details for communicating with the second user device.
[0015] The message may be cryptographically signed by a credential associated with the second user.
[0016] The support server may further comprise instructions that, when executed by the processing circuitry, cause the support server to: send an approval request to thesecond user device, requesting approval that the first user is allowed to initiate contact with the second user; receive an approval response from the second user device, confirming that the first user is allowed to initiate contact with the second user. In this case, the instructions to send a response to the first user device are executed in response to receiving the approval response.
[0017] The communication details may comprise a plurality of indications of respective data formats for communicating with the second user device.
[0018] The request may be cryptographically signed by a credential associated with the first user. In this case, the support server further comprises instructions that, when executed by the processing circuitry, cause the support server to: verify that the request is validly signed. Furthermore, the instructions to send a response to the first user device are executed conditional to the verification being positive.
[0019] The support server may further comprise instructions that, when executed by the processing circuitry, cause the support server to: provide at least one of code and data to provide conversion functionality to the first user device for converting communication between a first data format used by a first application in the first user device to the second data format.
[0020] The indication of data format may comprise an indication of a second application used for communication with the second user device.
[0021] The indication of data format may comprise an end point identifier of the second user device used by the second application.
[0022] According to a third aspect, it is provided a computer program for enabling communication between a first user device of a first user and a second user device of a second user. The computer program comprise computer program code which, when executed on a support server causes the support server to: receive, from the second user device, communication details for communicating with the second user device, the communication details comprising an indication of a second data format for communicating with the second user device; receive, from second user device, a message indicating that the second user device is associated with the second user; store,in a database, the communication details in association with the second user device; receive, from the first user device, a request for communication details for the second user device, the request comprising an identifier associated with the second user, and an identifier associated with the first user; determine that the second user device is associated with the second user based on the received message indicating that the second user device is associated with the second user; retrieve, from the database, the communication details being associated with the second user device; and send a response to the first user device, the response comprising the communication details for communicating with the second user device.
[0023] According to a fourth aspect, it is provided a computer program product comprising a computer program according to the third aspect and a computer readable means comprising non-transitory memory in which the computer program is stored.
[0024] According to a fifth aspect, it is provided a method for enabling communication between a first user device of a first user and a second user device of a second user. The method is performed by the first user device. The method comprises: sending, to a support server, a request for communication details for the second user device, the request comprising an identifier associated with the second user, and an identifier associated with the first user; receiving a response from the support server, the response comprising communication details for communicating with the second user device, the communication details comprising an indication of a second data format for communicating with the second user device; and communicating with the second user device, which includes converting communication between a first data format used by a first application in the first user device to the second data format.
[0025] The communicating may comprise converting the communication by intercepting communication to and from the first application, such that the first application is relieved from performing the conversion between the first data format and the second data format.
[0026] The request may be cryptographically signed by a credential associated with the first user.
[0027] The communication details may comprise a plurality of indications of respective data formats for communicating with the second user device. In this case, the method further comprises: selecting one of the plurality of indications of respective data formats, based on its compatibility with the first application or based on a user context of the second user device.
[0028] The method may further comprise: querying an application server, using the identifier associated with the second user being associated with a second application in the second user device, for an end point identifier of the second user device used by the second application in the second user device.
[0029] The method may further comprise: receiving and installing at least one of code and data for performing the conversion between the first data format and the second data format. In this case, in the communicating with the second user device, the converting is performed using the installed conversion functionality.
[0030] The indication data format may comprise an indication of a second application used for communication with the second user device.
[0031] The indication of data format may comprise an end point identifier of the second user device used by the second application.
[0032] According to a sixth aspect, it is provided a user device for enabling communication between the user device, denoted a first user device of a first user and a second user device of a second user. The user device comprises: processing circuitry; and memory circuitry storing instructions that, when executed by the processing circuitry, cause the user device to: send, to a support server, a request for communication details for the second user device, the request comprising an identifier associated with the second user, and an identifier associated with the first user; receive a response from the support server, the response comprising communication details for communicating with the second user device, the communication details comprising an indication of a second data format for communicating with the second user device; and communicate with the second user device, which includes converting communicationbetween a first data format used by a first application in the first user device to the second data format.
[0033] The instructions to communicate may comprise instructions that, when executed by the processing circuitry, cause the user device to convert the communication by intercepting communication to and from the first application, such that the first application is relieved from performing the conversion between the first data format and the second data format.
[0034] The request may be cryptographically signed by a credential associated with the first user.
[0035] The communication details may comprise a plurality of indications of respective data formats for communicating with the second user device. In this case, the user device further comprises instructions that, when executed by the processing circuitry, cause the user device to: select one of the plurality of indications of respective data formats, based on its compatibility with the first application or based on a user context of the second user device.
[0036] The user device may further comprise instructions that, when executed by the processing circuitry, cause the user device to: query an application server, using the identifier associated with the second user being associated with a second application in the second user device, for an end point identifier of the second user device used by the second application in the second user device.
[0037] The user device may further comprise instructions that, when executed by the processing circuitry, cause the user device to: receive and install at least one of code and data for performing the conversion between the first data format and the second data format. In this case, the instructions to communicate with the second user device comprise instructions that, when executed by the processing circuitry, cause the user device to convert using the installed conversion functionality.
[0038] The indication data format may comprise an indication of a second application used for communication with the second user device.
[0039] The indication of data format may comprise an end point identifier of the second user device used by the second application.
[0040] According to a seventh aspect, it is provided a computer program for enabling communication between the user device, denoted a first user device of a first user and a second user device of a second user. The computer program comprises computer program code which, when executed on a user device being the first user device causes the user device to: send, to a support server, a request for communication details for the second user device, the request comprising an identifier associated with the second user, and an identifier associated with the first user; receive a response from the support server, the response comprising communication details for communicating with the second user device, the communication details comprising an indication of a second data format for communicating with the second user device; and communicate with the second user device, which includes converting communication between a first data format used by a first application in the first user device to the second data format.
[0041] According to an eighth aspect, it is provided a computer program product comprising a computer program according to the seventh aspect and a computer readable means comprising non-transitory memory in which the computer program is stored.
[0042] Generally, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein. All references to "a / an / the element, apparatus, component, means, step, etc." are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated.BRIEF DESCRIPTION OF THE DRAWINGS
[0043] Aspects and embodiments are now described, by way of example, with reference to the accompanying drawings, in which:
[0044] Fig 1 is a schematic diagram illustrating an environment in which embodiments presented herein can be applied;
[0045] Fig 2 is a schematic diagram illustrating a system for enabling communication between the first user device and the second user device of Fig 1;
[0046] Figs 3A-B are swimlane diagrams illustrating embodiments of methods for enabling communication between a first user device (of a first user) and a second user device (of a second user), such as those illustrated in Fig 1;
[0047] Fig 4 is a schematic diagram illustrating components of the user device (either one of the first user device or the second user device) and the support server of Fig 1;
[0048] Fig 5 is a schematic diagram showing functional modules of the support server of Fig 1 according to one embodiment;
[0049] Fig 6 is a schematic diagram showing functional modules of the user device; and
[0050] Fig 7 shows one example of a computer program product comprising computer readable means.DETAILED DESCRIPTION
[0051] The aspects of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which certain embodiments of the invention are shown. These aspects may, however, be embodied in many different forms and should not be construed as limiting; rather, these embodiments are provided by way of example so that this disclosure will be thorough and complete, and to fully convey the scope of all aspects of invention to those skilled in the art. Like numbers refer to like elements throughout the description.
[0052] According to embodiments presented herein, it is provided a way for a first user with a first user device to communicate with a second user with a second user device. This is enabled by a support server that stores communication details of how toreach the second user, where the support server provides these communication details to the first user device. The first user device then connects to the second user device based on the communication details from the support server, including, when needed, converting to a data format that is used by the application in the second user device. In this way, the first user does not need to keep track of how to reach the second user, e.g. in terms of which application to use, etc.
[0053] Fig 1 is a schematic diagram illustrating an environment in which embodiments presented herein can be applied.
[0054] A first user 5a carries a first user device 2a, executing a first application 6a. Furthermore, a second user 5b carries a second user device 2b, executing a second application 6b. The term app is sometimes used instead of application. Each application 6a, 6b is a communication application, in the form of software executable by the user device in question, that is capable of communicating with a corresponding communication application on another user device.
[0055] Each one of the first user device 2a and the second user device 2b can be any suitable electronic device that is capable of communication and executing a communication application. For instance, the user devices 2a, 2b can be in the form of smart phones, wearable devices, tablet computers, laptop, computer, computers, etc. Optionally, one or both of the user devices 2a-b are each made up of two coupled devices, e.g. a smart watch that is coupled to a smartphone.
[0056] A communication network 7 can be a wide area network, such as the Internet, to which the user devices 2a, 2b can connect via Wi-Fi (e.g. any of the IEEE 802. nx standards) or a cellular network, such as LTE (Long Term Evolution), next generation mobile networks (fifth generation, 5G), sixth generation (6G) mobile network, etc.
[0057] A first application server 4a is provided in contact with the communication network 7. The first application server 4a serves the first application 6a, allowing the first application 6a to communicate with other corresponding applications on other user devices. Analogously, a second application server 4b is provided in contact with the communication network 7. The second application server 4b serves the secondapplication 6b, allowing the second application 6b to communicate with other corresponding applications on other user devices. Each one of the application servers 4a, 4b can be implemented on a single physical server or over multiple physical servers, potentially over large geographic areas, also known as in the cloud.
[0058] In the prior art, the first application 6a and the second application 6b cannot readily communicate with each other, unless they are instances of the same application.
[0059] As presented in more detail below, according to embodiments presented herein a support server 3 is provided for supporting communication setup between the first application 6a of the first user device 2a and the second application 6b of the second user device 2b. The support server 3 is also connected to the communication network 7, e.g. via Ethernet, using an optical fibre and / or Wi-Fi. The support server 3 can be implemented on a single physical server or over multiple physical servers, potentially over large geographic areas, also known as in the cloud.
[0060] Fig 2 is a schematic diagram illustrating a system for enabling communication between the first user device 2a and the second user device 2b of Fig 1. The system 1 comprises first user device 2a and the support server 3.
[0061] Figs 3A-B are swimlane diagrams illustrating embodiments of methods for enabling communication between a first user device 2a (of a first user) and a second user device 2b (of a second user), such as those illustrated in Fig 1. The swimlane diagrams can be considered to comprise a flow chart for methods in the first user device 2a in the two leftmost swimlanes and a flow chart for methods in the support server 3 in the penultimate swimlane to the right. Communication between the various entities is also shown.
[0062] Both the first application 6a and a converter 8 form part of the first user device 2a.
[0063] In a send details (det.) step 240, the second application 6b of the second user device 2b sends communication details 20 to the support server 3. The communication details comprise an indication of a second data format for communicating with the second user device 2b. The data format can include modality (text, audio, video, etc.) ofthe second user device 2b and different formats within each modality. Moreover, the communication details comprise control signal details to enable transmission of data to arrive at the second user device 2b. The control signal details can comprise information related to the second application 6b, e.g. the type of application, and how to communicate with the server associated with the second application 6b.
[0064] Optionally, the indication of data format comprises an indication of a second application 6b, e.g. WhatsApp, Snapchat, Signal, etc., which can be used when communicating with the second user device 2b.
[0065] Optionally, the communication details comprise a plurality of indications of respective data formats which can be used when communicating with the second user device 2b. In other words, the second user device 2b may comprise multiple instances of second applications 6b, e.g. WhatsApp, Snapchat, Signal, etc.
[0066] Optionally, the indication of data format comprises an end point identifier of the second user device 2b used by the second application 6b. The end point identifier can e.g. be a handle of the user of the second user device used in the second application 6b, or an address to the second user device 2b.
[0067] In a receive (recv.) details step 40, the support server 3 receives, from the second user device 2b, the communication details 20 for communicating with the second user device 2b. The communication details 20 comprise an indication of one or more second data formats for communicating with the second user device 2b as described above for the send details step 240.
[0068] In an send association step 242, the second application 6b of the second user device 2b sends a message 22 indicating that the second user device 2b is associated with the second user 5b. It is to be noted that the send association step 242 can be performed before or after the send details step 240.
[0069] In an receive association step 42, the support server 3 receives, from the second user device 2b, the message 22 indicating that the second user device 2b is associated with the second user. In this case, this association is stored, and the determining that the second user device 2b is associated with the second user (in thedetermine association step 48) is based on the received message 22 indicating that the second user device 2b is associated with the second user.
[0070] Optionally, the message 22 is cryptographically signed by a credential associated with the second user. The credential associated with the second user can be associated with an identifier of the second user. The identifier and the cryptographic signature can be in accordance with the public identification framework.
[0071] It is to be noted that the receive association step 42 can be performed before or after the receive details step 40.
[0072] In a store details step 44, the support server 3 stores, in a database, the communication details in association with the second user device 2b.
[0073] In a send request (req.) step 140, the first application 6a of the first user device 2a sends, to the support server 3, a request 24 for communication details for the second user device 2b. The sending of the request can be initiated based on the first application 6a of the first user device 2a wanting to communicate with the second user of the second communication device 2b. The request 24 comprises an identifier associated with the second user, and an identifier associated with the first user.
[0074] Optionally, the request is cryptographically signed by a credential associated with the first user. The credential can be associated with a public identification framework. For instance, EU (European Union) Digital Identity (EUDI) wallet is a public identification framework that has recently been defined. Every EU Member State will offer its own wallet application, built to the same specifications, to all citizens, residents and businesses. EUDI enables signatures to be associated with public identifiers that are widely accessible.
[0075] The credential can be associated with an identifier of the first user, in accordance with a public identification framework such as EUDI. In this case, the cryptographic signature proves that the first user device 2a is in possession of the identifier, e.g. of a wallet application that could comply with EUDI or a similar framework.
[0076] The identifier associated with the second user can also be an identifier of the public identification framework. The identifier associated with the second user can be any suitable identifier, including username / handle, phone number, e-mail address or public key of a certificate in a public identification framework. The identifier of the first user can be of the same or different type compared to the identifier of the second user.
[0077] The identifier of the second user can be obtained prior to the method starting from a public directory (e.g. part of the public identification network) or from prior communication from the first user to the second user, such as in an e-mail, or other text-based or binary communication.
[0078] In a receive request step 46, the support server 3 receives, from the first user device 2a, the request 24 for communication details for the second user device 2b. As detailed above, the request comprising an identifier associated with the second user, and an identifier associated with the first user.
[0079] In a determine (det.) association (association) step 48, the support server 3 determines that the second user device 2b is associated with the second user based on the received message indicating that the second user device 2b is associated with the second user. This association between user and user device can be stored in a database that is accessible to the support server 3.
[0080] In a retrieve (retr.) details step 54, the support server 3 retrieves, from the database, the communication details being associated with the second user device 2b. These are the communication details that were received in the receive details step 40.
[0081] In a send response (resp.) step 56, the support server 3 sends a response 28 to the first user device 2a. The response 28 comprises the communication details for communicating with the second user device 2b.
[0082] In a receive response step 142, the first application 6a of the first user device 2a receives the response 28 from the support server 3. The response comprises communication details for communicating with the second user device 2b. As detailed above, the communication details comprise an indication of the second data format for communicating with the second user device 2b.
[0083] In a communicate step 150, the first application 6a of the first user device 2a communicates with the second application 6b. The communication is enabled based on the communication details. The second application 6b performs its own communicate step 250. More specifically, the first user device 2a communicates with the second user device 2b, which includes converting communication between a first data format used by a first application 6a in the first user device 2a to the second data format in a converter 8.
[0084] The conversion can include converting media of a first format to a format specified in the second data format, e.g. converting video from HVEC (High Efficiency Video Coding) to MP4 (Moving Picture Experts Group 4), and / or converting control and / or user signalling to comply with the application server that is associated with the second application 6b, as stipulated by the communication details. The conversion may occur in both directions, but is performed by the converter 8 of first user device 2a. The second application 6b, the second user device 2b and the second application server 4b communicate transparently with the converter 8 of the first user device 2a, without needing to know that conversion occurs on the side of the first user device 2a.Optionally, the conversion includes converting between modalities, e.g. from text to audio, or vice versa.
[0085] The communicating may comprise converting the communication by intercepting communication to and from the first application 6a, such that the first application 6a is relieved from performing or knowing of the conversion between the first data format and the second data format. This can be based on setting up a hook for the interception in the first user device 2a. In this way, also the first application 6a can operate transparently, without knowledge of the conversion that occurs for the communication with the second application 6b.
[0086] In one embodiment, the conversion occurs by a local application in the first user device 2a corresponding to the second application 6b of the second user device 2b.
[0087] Looking now to Fig 3B, only new or modified steps compared to those of Fig 3A will be described.
[0088] In an optional conditional verify signature (sign.) step 47, the support server 3 evaluates whether the request 24 from the first user device 2a is validly signed. If the signature is verified, i.e. the request 24 is validly signed, the method proceeds to the determine association step 48. Otherwise, the method ends.
[0089] In an optional send an approval (appr.) request step 50, the support server 3 sends an approval request 26 to the second user device 2b, requesting approval that the first user is allowed to initiate contact with the second user. This step can be performed based on a configuration that the second user should be queried whether to allow incoming communication. Such configuration can be applied for all incoming communication or for incoming communication from users that are not pre-approved, e.g. by forming part of a contact list of the second user.
[0090] In an optional receive approval request step 250, the second application 6b of the second user device 2b receives the approval request 26 from the support server 3. The second user device 2b then queries the second user whether the first user is allowed to initiate contact. If the second user denies the contact request, the method ends (not shown), otherwise the method continues.
[0091] In an optional send approval response step 252, the second application 6b of the second user device 2b sends an approval response 27 to the support server 3, which includes an indication that the second user approves the contact request if that is the case.
[0092] In an optional receive approval response step 52, the support server 3 receives the approval response 27 from the second user device 2b, confirming that the first user is allowed to initiate contact with the second user.
[0093] In an optional select indication (indie.) step 144, when the communication details comprise a plurality of indications of respective data formats for communicating with the second user device 2b, the first application 6a of the first user device 2a selects one of the plurality of indications of respective data formats. This selection can be based on its compatibility with the first application 6a. Alternatively or additionally, the selection can be based on a user context of the second user device 2b. The user contextof the second user device 2b can be reported to the support server 3, which can provide this information to the first user device 2a. For instance, if the user context indicates that the second user device 2b is driving or running, video communication and / or certain applications might be excluded. Alternatively or additionally, the selection can be based on that certain applications might be temporarily unavailable on the second user device 2b. This could be the case if the second user device 2b is a smart watch that is coupled with a smartphone, that is temporarily not in contact with the smart watch, and only the smartphone supports certain applications.
[0094] It is to be noted that the coupled devices, e.g. smartwatch and smartphone, can be used for all cryptographic operations mentioned herein. In this case, most operations can be performed by the smartphone, while the cryptographic operations (such as signing) can be performed by the smartwatch that is coupled to the smartphone.
[0095] In an optional provide converter (conv.) step 58, the support server 3 provides at least one of code and data to provide conversion functionality to the first user device 2a, for converting communication between a first data format used by a first application 6a in the first user device 2a to the second data format.
[0096] The at least one of code and data can comprise source code, bytecode or compiled code that can be executed by the first user device 2a, directly or after local compilation. Alternatively or additionally, the at least one of code and data can comprise an FPGA bitstream or an ASIC configuration for implementing the conversion functionality on the first user device 2a.
[0097] Optionally, this step is preceded by a request (not shown) for conversion functionality from the first user device 2a, indicating the first application 6a and the second application 6b.
[0098] In an optional install converter step 146, the first application 6a of the first user device 2a receives and installs a converter 8 in accordance with the at least one of code and data for performing the conversion between the first data format and the second data format. In this case, in the communicating 150 with the second user device2b, the converting is performed using the installed conversion functionality of the converter 8.
[0099] In an optional query end point ID step 148, the first application 6a of the first user device 2a queries the second application server 4b, using the identifier associated with the second user of the second application 6b in the second user device 2b, for an end point identifier of the second user device 2b used by the second application 6b in the second user device 2b. The second application server 4b, in a provide user ID step 248 responds with the end point identifier.
[0100] Using embodiment presented herein, interoperability between different communication applications is greatly improved. Only one side of the communication (the first user device 2a in the nomenclature used herein) needs to be aware of the discrepancy in how communication occurs. Using the conversion in the first user device 2a, the format is ensured to be correct for both the second application 6b and the first application 6a. The converter in the first user device 2a is transparent for the second user device 2b, whereby the second user device 2b can communicate without being aware of any conversion occurring. Optionally, the identification of users is based on a public identification framework to simplify user lookup and improve trust.
[0101] Fig 4 is a schematic diagram illustrating components of the user device 2 (either one of the first user device or the second user device) and the support server 3 of Fig 1. Processing circuitry 60 is provided using any combination of one or more of a suitable central processing unit (CPU), graphics processing unit (GPU), multiprocessor, neural processing unit (NPU), microcontroller, digital signal processor (DSP), etc., capable of executing software instructions 67 stored in memory circuitry 64, which can thus be a computer program product. The processing circuitry 60 could alternatively be implemented using an application specific integrated circuit (ASIC), field programmable gate array (FPGA), etc. The processing circuitry 60 can be configured to execute the methods for the first user device and the support server 3 described with reference to Figs 3A-B above.
[0102] The memory circuitry 64 can be any combination of random-access memory (RAM) and / or read-only memory (ROM). The memory circuitry 64 also comprises non-transitory persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid-state memory or even remotely mounted memory.
[0103] A data memory 66 is also provided for reading and / or storing data during execution of software instructions in the processing circuitry 60. The data memory 66 can be any combination of transitory and non-transitory persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid-state memory or even remotely mounted memory. The data memory 66, for the support server 3, comprises a database for storing communication details in association with instances of the second user device.
[0104] An I / O interface 62 is provided for communicating with external and / or internal entities. Optionally, the I / O interface 62 also includes a user interface, especially for the user device 2.
[0105] Other components are omitted in order not to obscure the concepts presented herein.
[0106] Fig 5 is a schematic diagram showing functional modules of the support server 3 of Fig 1 according to one embodiment. The modules are implemented using software instructions such as a computer program executing in the support server 3. Alternatively or additionally, the modules are implemented using hardware, such as any one or more of an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or discrete logical circuits. The modules correspond to the steps in the methods for the support server 3 illustrated in Figs 3A-B.
[0107] A details receiver 70 corresponds to step 40. An association receiver 72 corresponds to step 42. A details storer 74 corresponds to step 44. A request receiver 76 corresponds to step 46. A signature verifier corresponds to step 47. An association determiner 78 corresponds to step 48. An approval request sender 80 corresponds to step 50. An approval response receiver 82 corresponds to step 52. A details retriever 84 corresponds to step 54. A response sender 86 corresponds to step 56. A converter provider 88 corresponds to step 58.
[0108] Fig 6 is a schematic diagram showing functional modules of the user device 2, e.g. the first user device of Fig 1 according to one embodiment. The modules are implemented using software instructions such as a computer program executing in the user device 2. Alternatively or additionally, the modules are implemented using hardware, such as any one or more of an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or discrete logical circuits. The modules correspond to the steps in the methods for the first user device illustrated in Figs 3A-B.
[0109] A request sender 170 corresponds to step 140. A response receiver 172 corresponds to step 142. An indication selector 174 corresponds to step 144. A converter installer 176 corresponds to step 146. A user ID 178 corresponds to step 148. A communicator 180 corresponds to step 150.
[0110] Fig 7 shows one example of a computer program product 90 comprising computer readable means. On this computer readable means, a computer program 91 can be stored in a non-transitory memory. The computer program can cause processing circuitry to execute a method according to embodiments described herein. In this example, the computer program product 90 is in the form of a removable solid-state memory, e.g. a Universal Serial Bus (USB) drive. As explained above, the computer program product could also be embodied in a memory of a device, such as the computer program product 64 of Fig 4. While the computer program 91 is here schematically shown as a section of the removable solid-state memory, the computer program can be stored in any way which is suitable for the computer program product, such as another type of removable solid-state memory, or an optical disc, such as a CD (compact disc), a DVD (digital versatile disc) or a Blu-Ray disc.
[0111] The aspects of the present disclosure have mainly been described above with reference to a few embodiments. However, as is readily appreciated by a person skilled in the art, other embodiments than the ones disclosed above are equally possible within the scope of the invention, as defined by the appended patent claims. Thus, while various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope being indicated by the following claims.
Claims
CLAIMS1. A method for enabling communication between a first user device (2a) of a first user (5a) and a second user device (2b) of a second user (5b), the method being performed by a support server (3), the method comprising:receiving (40), from the second user device (2b), communication details for communicating with the second user device (2b), the communication details comprising an indication of a second data format for communicating with the second user device (2b);receiving (42), from second user device (2b), a message indicating that the second user device (2b) is associated with the second user (5b);storing (44), in a database (66), the communication details in association with the second user device (2b);receiving (46), from the first user device (2a), a request (24) for communication details for the second user device (2b), the request (24) comprising an identifier associated with the second user (5b), and an identifier associated with the first user (5a);determining (48) that the second user device (2b) is associated with the second user (5b) based on the received message indicating that the second user device (2b) is associated with the second user (5b);retrieving (54), from the database (66), the communication details being associated with the second user device (2b); andsending (56) a response (28) to the first user device (2a), the response (28) comprising the communication details for communicating with the second user device (2b).
2. The method according to claim 1, wherein the message is cryptographically signed by a credential associated with the second user (5b).
3. The method according to any one of the preceding claims, further comprising: sending (50) an approval request to the second user device (2b), requesting approval that the first user (5a) is allowed to initiate contact with the second user (5b);receiving (52) an approval response from the second user device (2b), confirming that the first user (5a) is allowed to initiate contact with the second user (5b); andwherein the sending (56) a response (28) to the first user device (2a) is performed in response to receiving the approval response.
4. The method according to any one of the preceding claims, wherein the communication details comprise a plurality of indications of respective data formats for communicating with the second user device (2b).
5. The method according to any one of the preceding claims, wherein the request (24) is cryptographically signed by a credential associated with the first user (5a);wherein the method further comprises:verifying (47) that the request (24) is validly signed; andwherein the sending (56) a response (28) to the first user device (2a) is conditional to the verification being positive.
6. The method according to any one of the preceding claims, further comprising: providing (58) at least one of code and data to provide conversion functionality to the first user device (2a) for converting communication between a first data format used by a first application (6a) in the first user device (2a) to the second data format.
7. The method according to any one of the preceding claims, wherein the indication of data format comprises an indication of a second application (6b) used for communication with the second user device (2b).
8. The method according to claim 7, wherein the indication of data format comprises an end point identifier of the second user device (2b) used by the second application (6b).
9. A support server (3) for enabling communication between a first user device (2a) of a first user (5a) and a second user device (2b) of a second user (5b), the support server (3) comprising:processing circuitry (60); andmemory circuitry (64) storing instructions (67) that, when executed by the processing circuitry, cause the support server (3) to:receive, from the second user device (2b), communication details for communicating with the second user device (2b), the communication details comprisingan indication of a second data format for communicating with the second user device (2b);receive, from second user device (2b), a message indicating that the second user device (2b) is associated with the second user (5b);store, in a database (66), the communication details in association with the second user device (2b);receive, from the first user device (2a), a request (24) for communication details for the second user device (2b), the request (24) comprising an identifier associated with the second user (5b), and an identifier associated with the first user (5a);determine that the second user device (2b) is associated with the second user (5b) based on the received message indicating that the second user device (2b) is associated with the second user (5b);retrieve, from the database (66), the communication details being associated with the second user device (2b); andsend a response (28) to the first user device (2a), the response (28) comprising the communication details for communicating with the second user device (2b).
10. The support server (3) according to claim 9, wherein the message is cryptographically signed by a credential associated with the second user (5b).
11. The support server (3) according to claim 9 or 10, further comprising instructions (67) that, when executed by the processing circuitry, cause the support server (3) to: send an approval request to the second user device (2b), requesting approval that the first user (5a) is allowed to initiate contact with the second user (5b);receive an approval response from the second user device (2b), confirming that the first user (5a) is allowed to initiate contact with the second user (5b); andwherein the instructions to send a response (28) to the first user device (2a) are executed in response to receiving the approval response.
12. The support server (3) according to any one of claims 9 to 11, wherein the communication details comprise a plurality of indications of respective data formats for communicating with the second user device (2b).13- The support server (3) according to any one of claims 9 to 12, wherein the request (24) is cryptographically signed by a credential associated with the first user (5a);wherein the support server (3) further comprises instructions (67) that, when executed by the processing circuitry, cause the support server (3) to:verify that the request (24) is validly signed; andwherein the instructions to send a response (28) to the first user device (2a) are executed conditional to the verification being positive.
14. The support server (3) according to any one of claims 9 to 13, further comprising instructions (67) that, when executed by the processing circuitry, cause the support server (3) to:provide at least one of code and data to provide conversion functionality to the first user device (2a) for converting communication between a first data format used by a first application (6a) in the first user device (2a) to the second data format.
15. The support server (3) according to any one of claims 9 to 14, wherein the indication of data format comprises an indication of a second application (6b) used for communication with the second user device (2b).
16. The support server (3) according to claim 15, wherein the indication of data format comprises an end point identifier of the second user device (2b) used by the second application (6b).
17. A computer program (67, 91) for enabling communication between a first user device (2a) of a first user (5a) and a second user device (2b) of a second user (5b), the computer program comprising computer program code which, when executed on a support server (3) causes the support server (3) to:receive, from the second user device (2b), communication details for communicating with the second user device (2b), the communication details comprising an indication of a second data format for communicating with the second user device (2b);receive, from second user device (2b), a message indicating that the second user device (2b) is associated with the second user (5b);store, in a database (66), the communication details in association with the seconduser device (2b);receive, from the first user device (2a), a request (24) for communication details for the second user device (2b), the request (24) comprising an identifier associated with the second user (5b), and an identifier associated with the first user (5a);determine that the second user device (2b) is associated with the second user (5b) based on the received message indicating that the second user device (2b) is associated with the second user (5b);retrieve, from the database (66), the communication details being associated with the second user device (2b); andsend a response (28) to the first user device (2a), the response (28) comprising the communication details for communicating with the second user device (2b).
18. A computer program product (64, 90) comprising a computer program according to claim 17 and a computer readable means comprising non-transitory memory in which the computer program is stored.
19. A method for enabling communication between a first user device (2a) of a first user (5a) and a second user device (2b) of a second user (5b), the method being performed by the first user device (2a), the method comprising:sending (140), to a support server (3), a request (24) for communication details for the second user device (2b), the request (24) comprising an identifier associated with the second user (5b), and an identifier associated with the first user (5a);receiving (142) a response (28) from the support server (3), the response (28) comprising communication details for communicating with the second user device (2b), the communication details comprising an indication of a second data format for communicating with the second user device (2b); andcommunicating (150) with the second user device (2b), which includes converting communication between a first data format used by a first application (6a) in the first user device (2a) to the second data format.
20. The method according to claim 19, wherein the communicating (150) comprises converting the communication by intercepting communication to and from the first application (6a), such that the first application (6a) is relieved from performing the conversion between the first data format and the second data format.
21. The method according to claim 19 or 20, wherein the request (24) is cryptographically signed by a credential associated with the first user (5a).
22. The method according to any one of claims 19 to 21, wherein the communication details comprise a plurality of indications of respective data formats for communicating with the second user device (2b);and wherein the method further comprises:selecting (144) one of the plurality of indications of respective data formats, based on its compatibility with the first application (6a) or based on a user context of the second user device (2b).
23. The method according to any one of claims 19 to 22, further comprising:querying (148) an application server (4), using the identifier associated with the second user (5b, the application server (4) being associated with a second application (6b) in the second user device (2b), for an end point identifier of the second user device (2b) used by the second application (6b) in the second user device (2b).
24. The method according to any one of claims 19 to 23, further comprising:receiving (146) and installing at least one of code and data for performing the conversion between the first data format and the second data format;and wherein, in the communicating (150) with the second user device (2b), the converting is performed using the installed conversion functionality.
25. The method according to any one of claims 19 to 24, wherein the indication data format comprises an indication of a second application (6b) used for communication with the second user device (2b).
26. The method according to claim 25, wherein the indication of data format comprises an end point identifier of the second user device (2b) used by the second application (6b).
27. A user device (2) for enabling communication between the user device (2), denoted a first user device (2a) of a first user (5a) and a second user device (2b) of a second user (5b), the user device (2) comprising:processing circuitry (60); andmemory circuitry (64) storing instructions (67) that, when executed by the processing circuitry, cause the user device (2) to:send, to a support server (3), a request (24) for communication details for the second user device (2b), the request (24) comprising an identifier associated with the second user (5b), and an identifier associated with the first user (5a);receive a response (28) from the support server (3), the response (28) comprising communication details for communicating with the second user device (2b), the communication details comprising an indication of a second data format for communicating with the second user device (2b); andcommunicate with the second user device (2b), which includes converting communication between a first data format used by a first application (6a) in the first user device (2a) to the second data format.
28. The user device (2) according to claim 27, wherein the instructions to communicate comprise instructions (67) that, when executed by the processing circuitry, cause the user device (2) to convert the communication by intercepting communication to and from the first application (6a), such that the first application (6a) is relieved from performing the conversion between the first data format and the second data format.
29. The user device (2) according to claim 27 or 28, wherein the request (24) is cryptographically signed by a credential associated with the first user (5a).
30. The user device (2) according to any one of claims 27 to 29, wherein the communication details comprise a plurality of indications of respective data formats for communicating with the second user device (2b);and wherein the user device (2) further comprises instructions (67) that, when executed by the processing circuitry, cause the user device (2) to:select one of the plurality of indications of respective data formats, based on its compatibility with the first application (6a) or based on a user context of the second user device (2b).
31. The user device (2) according to any one of claims 27 to 30, further comprising instructions (67) that, when executed by the processing circuitry, cause the user device(2) to:query an application server (4), using the identifier associated with the second user (5b, the application server (4) being associated with a second application (6b) in the second user device (2b), for an end point identifier of the second user device (2b) used by the second application (6b) in the second user device (2b).
32. The user device (2) according to any one of claims 27 to 31, further comprising instructions (67) that, when executed by the processing circuitry, cause the user device (2) to:receive and install at least one of code and data for performing the conversion between the first data format and the second data format;and wherein, the instructions to communicate with the second user device (2b) comprise instructions (67) that, when executed by the processing circuitry, cause the user device (2) to convert using the installed conversion functionality.
33. The user device (2) according to any one of claims 27 to 32, wherein the indication data format comprises an indication of a second application (6b) used for communication with the second user device (2b).
34. The user device (2) according to claim 33, wherein the indication of data format comprises an end point identifier of the second user device (2b) used by the second application (6b).
35. A computer program (67, 91) for enabling communication between the user device (2), denoted a first user device (2a) of a first user (5a) and a second user device (2b) of a second user (5b), the computer program comprising computer program code which, when executed on a user device (2) being the first user device (2a) causes the user device (2) to:send, to a support server (3), a request (24) for communication details for the second user device (2b), the request (24) comprising an identifier associated with the second user (5b), and an identifier associated with the first user (5a);receive a response (28) from the support server (3), the response (28) comprising communication details for communicating with the second user device (2b), the communication details comprising an indication of a second data format forcommunicating with the second user device (2b); andcommunicate with the second user device (2b), which includes converting communication between a first data format used by a first application (6a) in the first user device (2a) to the second data format.
36. A computer program product (64, 90) comprising a computer program according to claim 35 and a computer readable means comprising non-transitory memory in which the computer program is stored.
