EP4026346A1 - Aufbau einer verbindung zwischen einer ersten anwendung auf einem ersten gerät und einer zweiten anwendung auf einem zweiten gerät - Google Patents
Aufbau einer verbindung zwischen einer ersten anwendung auf einem ersten gerät und einer zweiten anwendung auf einem zweiten gerätInfo
- Publication number
- EP4026346A1 EP4026346A1 EP20740047.4A EP20740047A EP4026346A1 EP 4026346 A1 EP4026346 A1 EP 4026346A1 EP 20740047 A EP20740047 A EP 20740047A EP 4026346 A1 EP4026346 A1 EP 4026346A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- application
- identification
- service
- message
- executed
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000004891 communication Methods 0.000 claims abstract description 56
- 238000000034 method Methods 0.000 claims abstract description 34
- 230000004044 response Effects 0.000 claims description 6
- 238000012790 confirmation Methods 0.000 claims description 2
- 230000008569 process Effects 0.000 description 9
- 230000005540 biological transmission Effects 0.000 description 5
- 238000009434 installation Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000008901 benefit Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 235000014510 cooky Nutrition 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
- H04N21/43615—Interfacing a Home Network, e.g. for connecting the client to a plurality of peripherals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/41—Structure of client; Structure of client peripherals
- H04N21/4104—Peripherals receiving signals from specially adapted client devices
- H04N21/4126—The peripheral being portable, e.g. PDAs or mobile phones
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/434—Disassembling of a multiplex stream, e.g. demultiplexing audio and video streams, extraction of additional data from a video stream; Remultiplexing of multiplex streams; Extraction or processing of SI; Disassembling of packetised elementary stream
- H04N21/4345—Extraction or processing of SI, e.g. extracting service information from an MPEG stream
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
- H04N21/4363—Adapting the video stream to a specific local network, e.g. a Bluetooth® network
- H04N21/43632—Adapting the video stream to a specific local network, e.g. a Bluetooth® network involving a wired protocol, e.g. IEEE 1394
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
- H04N21/4363—Adapting the video stream to a specific local network, e.g. a Bluetooth® network
- H04N21/43637—Adapting the video stream to a specific local network, e.g. a Bluetooth® network involving a wireless protocol, e.g. Bluetooth, RF or wireless LAN [IEEE 802.11]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/45—Management operations performed by the client for facilitating the reception of or the interaction with the content or administrating data related to the end-user or to the client device itself, e.g. learning user preferences for recommending movies, resolving scheduling conflicts
- H04N21/462—Content or additional data management, e.g. creating a master electronic program guide from data received from the Internet and a Head-end, controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabilities
- H04N21/4622—Retrieving content or additional data from different sources, e.g. from a broadcast channel and the Internet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/47—End-user applications
- H04N21/472—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/47—End-user applications
- H04N21/478—Supplemental services, e.g. displaying phone caller identification, shopping application
- H04N21/4782—Web browsing, e.g. WebTV
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/81—Monomedia components thereof
- H04N21/8166—Monomedia components thereof involving executable data, e.g. software
- H04N21/8173—End-user applications, e.g. Web browser, game
Definitions
- the present invention relates to establishing a connection between applications on different devices.
- the present invention relates to the establishment of a connection between an HbbTV application on one HbbTV device and a second application on a mobile device.
- Version 2 of the HbbTV specification defines a mechanism with which an HbbTV application (“app") can find displayable devices (e.g. tablets, cell phones, etc.) in the local network and start applications on the devices found.
- HbbTV-2 only describes the interface via which an HbbTV application can trigger the search for devices (“Discovery”) and the start of applications (“Launch”). For this reason, manufacturer-specific protocols are typically used for communication between the display-capable device (“second screen”) and the HbbTV device.
- the HbbTV 2 standard provides that HbbTV device manufacturers provide applications that implement the endpoints of a manufacturer-specific protocol on the HbbTV device and the respective display-capable device.
- Such manufacturer-specific launcher applications according to the HbbTV standard have the following weaknesses:
- the present invention overcomes these and other problems associated with prior art methods of establishing a connection between applications on different devices.
- the present invention is not limited to HbbTV, but can be used quite generally to establish a connection between applications on different devices.
- a method comprises setting up a connection between a first application on a first device and a communication service on the first device using an identification that is assigned to a second application, setting up a connection between the second application running on a second device and the communication service using the identification, establishing a communication channel between the first application and the second application via the communication service and receiving, by the second application, a first message from the first application, the first message being a third on the second device to be executed application and / or a first service of the third application to be executed on the second device.
- the phrase “establishing a connection” as used in the context of the present description and the claims is to be understood in particular as the sending and receiving of messages by means of which user data is transferred from an application on one device to an application on another device can be transferred.
- the term “application” as used in the context of the present description and the claims is to be understood in particular as a software program that adds previously unavailable services to a device and thereby expands the possibility of using the device.
- the software program can, for example, be specially designed to run on the operating system of the terminal device (for example a “native” Android or iOS application).
- the software program can also be designed in such a way that it is interpreted and executed by other applications (e.g. a website that HTML, CSS and / or JavaScript code and executed by a web browser or an application that includes a web browser).
- device as used in the context of the present description and the claims is to be understood in this context in particular as an interconnection of electrical and electronic components in a functional unit, the electrical and electronic components being provided with a component-related software layer that allows the installation of an operating system on different devices.
- the term “communication service”, as used in the context of the present description and the claims, is to be understood in particular as a service provided by a software layer on the device that helps to transmit messages from one device to the other device enable.
- the term “communication channel” as used in the context of the present description and the claims is to be understood in particular as a transmission path via which messages can be transmitted from an application on one device to an application on another device.
- the term “identification”, as used in the context of the present description and the claims, is to be understood in particular as digitally reproducible information by means of which an unambiguous assignment of entities is possible (for example a type of an application or an instance of a Application).
- the first device is preferably designed to reproduce image and sound data.
- the first device can be designed as a television set.
- the first device is preferably designed as an HbbTV-capable receiver.
- the first device can be designed as an HbbTV-capable television set.
- the first application on the first device is preferably assigned to a first radio channel and is started automatically or can be started manually when the first device reproduces image and sound data from the first radio channel.
- the first application can be issued by a radio station and provide information and services relating to a radio channel of the radio station and / or interactive elements for the radio channel.
- the second application preferably checks whether the first application is authorized to initiate the execution of the third application and / or the first service and, if the first application is authorized, causes the execution of the third application and / or the first service third application and / or the first service.
- the method further comprises terminating the first application and executing a fourth application on the first device, setting up a communication channel between the fourth application and the second application via the communication service using the identification and receiving, by the second application, a second Message from the fourth application, the second message designating a fifth application to be executed on the second device and / or a second service of the fifth application to be executed on the second device.
- the termination of the first application and the execution of the fourth application on the first device can result, for example, from switching between a first and a second radio channel and can result in other applications and / or services being started on the second device in order to carry out the switching process and to take into account the associated shift in the user's attention to the second radio channel.
- the method may further include broadcasting a third message by the second application running on the second device and replying to the third message by the first device, the response comprising the address of the communication service on the first device.
- the second application can search for the first device in a network, the search being completed when the first device replies with the address of the communication service on the first device.
- the second application executed on the second device can be set up to repeat an attempt to establish the communication channel until the communication channel is established.
- the communication channel between the first and the second application can be set up with mutual use of an identification which identifies an instance of the second application on the second device.
- the identification can be stored persistently on the first device by the first application and access to the stored identification can be limited to applications that originate from the same source (for example the same web origin) as the first application.
- access to the stored identification can be limited to applications that are published by the same broadcaster or made available at the same Internet address.
- the second application can transmit the identification to the first application, which stores it persistently on the first device.
- the identification can be provided to a fifth application running on the first device, which comes from a different source than the first application, and can be stored persistently by the fifth application on the first device.
- identifications can, if desired, be passed on from applications to other applications, so that they do not have to go through the process of searching for and determining suitable devices / applications.
- the first application can be set up to forward the identification to the fifth application and the fifth application can be set up to store the second identification persistently on the first device.
- the second application can transmit the identification and sources of authorized applications to a sixth application on the first device which executes authorized applications and provides them with the identification, the authorized applications storing the identification on the first device and assigning it to their source.
- the identification can be derived from an application on the first device from a user input and stored persistently.
- the first application on the first device can be linked to the second application on the second device by means of the identification via an external communication service send a fourth message identifying the third application and / or the first service provided by the third application.
- the first application on the first device can send the second application on the second device a fifth message using the identification via an external communication service, which message prompts the second application to set up the connection between the second application and the communication service.
- the third application to be executed on the second device and / or the first service to be executed on the second device can be executed immediately or at a later point in time in response to the first message or in response to a confirmation input.
- the third application preferably provides a user interface coordinated with the playback on the first device, the coordination taking place by means of a communication channel established between the first application and the third application.
- Fig. La shows a first exemplary system with a first device and a second device
- FIG. 1b shows a second exemplary system with a first device and a second device
- Figure IC shows a third exemplary system having a first device and a second device
- Figure 1d shows a fourth exemplary system having a first device and a second device
- Fig. 1e shows a fifth exemplary system having a first device and a second device
- FIG. 2 shows a process for establishing a communication channel between a first application on the first device and a second application on the second device of the systems shown in FIGS. 1 a, 1 b, 1 c and 1 d;
- FIG. 3 shows a modification of the process shown in FIG. 2, in which, in addition to the second application on the second device, a further application on a third device signals its readiness for connection;
- FIG. 4 shows further steps of the process shown in FIG. 2, in which it is checked whether the first application is authorized to start the third application or the first service;
- FIG 5 shows further steps in the process shown in Figure 4 in which the second application seeks (and finds) the communication service
- Figure 6 shows a further modification of the process shown in Figure 2 in which the second application tries to establish a communication channel until the communication service responds.
- FIG. 3 a shows a first system 10, comprising a first device 12, which can exchange data with a second device 16 and a third device 18 via an internal or external radio unit 14a.
- the first device 12 can be set up to reproduce image and / or sound data.
- the first device 12 can be a television set (for example an HbbTV-compatible television set) that is set up to receive one or more radio channels via a radio or cable interface and the video and / or video content contained in a selected radio channel Play back audio data (on a screen or by means of one or more loudspeakers).
- the second device 16 and the third device 18 can be used as mobile devices (e.g.
- the devices 12, 16, 18 can be nodes of a network (for example a home network that is set up by a WLAN-capable router 14a) and can be addressed in the network via addresses.
- FIG. Lb shows a second system 10, which differs from the system 10 shown in Fig. La in that the second device 16 and the third device 18 are not via a radio link but via a wired transmission link (e.g. via a router 14b and an Ethernet connection) are connected to the first device 12.
- FIG. IC shows a third system 10 which differs from the system 10 shown in FIG. 3 a in that the second device 16 is not via a radio link but via a wired transmission link (e.g. via a router 14b and an Ethernet connection). is connected to the first device 12.
- Fig. 1d shows a fourth system 10, which differs from the system 10 shown in Fig. Ta in that the third device 18 is not via a radio link but via a wired transmission link (e.g. via a router 14b and an Ethernet connection). is connected to the first device 12.
- Fig. Le shows a fifth system 10, which differs from the in Fig. Lb-Fig. ld differs in that the first device 12 is wirelessly connected to the router 14b and the router 14b is also wirelessly connected to the second device 16 and the third device 18.
- the second device 16 and / or the third device 18 can of course also be connected to the router 14b via a wired transmission link.
- the session shown in FIG. 2 begins with the first application 20 (for example an HbbTV application) opening a connection to a communication service 22 (for example an APP2APP local endpoint) (for example sending it to the corresponding URL ID appends).
- a communication service 22 for example an APP2APP local endpoint
- the sequence shown in FIG. 2 may already have been preceded by attempts by the second application 24 to use the communication service 22 (or find the APP2 ⁇ PP remote endpoint) and connect to it.
- the second application 24 can carry out a communication service identification routine (for example using the “Discovery” routine described in HbbTV-2) through which it finds the communication service 22 (for example the APP2 ⁇ PP remote endpoint).
- the communication service 22 can always be available or only as long as the first application 20 keeps the connection to the communication service 22 open.
- an APP2APP remote URL of an APP2APP remote endpoint according to the HbbTV-2 specification can only be reached after opening by an HbbTV application and only until the HbbTV application closes the connection to the communication service 22. Attempts to connect can therefore fail because no application has connected to the corresponding remote station (or the APP2APP local endpoint). It is also possible that a previously existing connection was interrupted because an application that was connected to it was terminated.
- the second application 24 After the second application 24 has found the communication service 22 (or the APP2APP remote endpoint), it can establish a connection to it, as illustrated in FIG. 2, using the ID (which is assigned to the second application, for example ) appends to the APP2APP remote URL and sends a corresponding request 30 to the communication service 22. If the IDs specified by the first application 20 in the request 32 and the second application in the request 30 match, the communication service 22 on the first device 12 establishes a connection between the two applications 20, 24. The communication service 22 can inform the first application 20 and / or the second application 24 about the establishment of the connection by means of a message 34 (“pairing completed”). The first application 20 can now request the start of a third application 26 and / or a first service 28 on the second device 16 (for example a “second screen”) with a corresponding message 36 from the second application 24 via the communication service 22.
- the ID which is assigned to the second application, for example
- the second application 24 can be set up to enable applications 20 (for example different HbbTV applications) from different providers or applications 20 from different sources on the first device 12 to start applications / services on the second device 16.
- applications 20 for example different HbbTV applications
- the respective application 20 needs to know an ID which, for example, contains a type and / or instance Identifier of the second application 24 can be. It can be provided that the ID stored by a specific application 20 on the first device 12 can only be read by applications 20 that originate from the same source (or have been downloaded from the same source).
- a source can be defined, for example, by a communication protocol (e.g. http or https), a host (e.g. www.irt.de) and a port (e.g. 80) via which the Application can be downloaded, with applications 20 from different publishers typically being obtained from different sources.
- a publisher can also offer applications 20 through various sources.
- Applications 24 of the same type that are executed on different devices can, as illustrated in FIG ) transmit the ID with which the instances can be differentiated).
- the ID can be transmitted to one or more first applications 20 (from various sources) on the first device 12 as part of a setup routine.
- the one or more applications 20 can persistently store the ID on the first device 12.
- the setup routine can be designed so that the user can specify which applications 20 (or which applications 20 from which sources) are later allowed to connect to an application 24 of a particular type.
- the first application 20 can add information to the message 36 with regard to the third application 26 to be started or the first service 28 to be started (for example the application type of the first application 20) which the first Application 20 identified.
- the second application 24 can check whether the first application 20 is authorized in general to start any applications / services or specifically to start the third application 26 and / or the second service 28. For example, the second application 24 can compare the information with a “blacklist” (list of applications / services that are not allowed to start) or “whitelist” (list of applications / services that are allowed to start).
- the second application 24 can request the user to indicate whether he or she agrees to this (and future) application and / or service start by the first application 20. If the first application 20 is authorized to start the respective application and / or the respective service, the second application 24 can communicate this to the first application 20 and then attempt to start the requested application or the requested service. If the first application 20 is not authorized to do this, the second application 24 can also notify the first application 20 of this. The second application 24 can provide details on the justification, for example that the first application 20 is on a “blacklist”. This enables the first application 20 to display appropriate information to the user.
- the solution described offers an alternative to the manufacturer-specific “launcher” applications specified in HbbTV-2. It allows, across TV services, the “launch” of applications / services on “second screens” and manages without an additional web server. The latter has the advantage that the operating costs do not increase with the number of users.
- no data needs to be stored outside of the second application 24.
- a user profile that contains, for example, a history of started applications / services and a favorites list with applications / services maintained by the user can be stored in the second application 24 on the second device 16. In this way, the user has full and sole control over his data and is the only one who can read, delete and change it.
- a list of these applications 20 can be stored in the second application 24 and the second application 24 can be set up, to address the applications 20 on the first device 12 one after the other and thereby inform them of the ID.
- the discovery and launch protocols from HbbTV-2 can be used for this purpose.
- the second application 24 can transmit the ID via the communication service or already as a parameter in the start URL to the applications 20 on the first device 12, which can then persistently save it on the first device 12 (e.g. in a cookie) .
- the ID is then available for later connections.
- the list of applications 20 on the first device 12 that (possibly) require the ID can be updated when the second application 24 is “updated”. After the update, a new setup (with a sequential addressing of the applications 20 on the first device 12) can be carried out.
- the second application 24 can start an application 20 from a specific source on the first device 12 (in an HbbTV environment, for example via the DIAL protocol from the HbbTV specification) and thereby transmit the ID.
- the application 20 from the source can store the ID and forward it to an application 20 from a further source.
- the application 20 from the additional source can also save the ID and, in turn, forward it to an application 20 from another source, etc.
- an application 20 can be provided with a list of further applications 20 from a specific source, to which the ID is to be forwarded, and the list can be transferred together with the ID to the first application 20 on the list when forwarding.
- the first application 20 on the list can then be removed from the list and the list can be passed along with the ID to the next application 20 on the list, and so on.
- the first application 20 can establish a connection to the second application 24 and inform the second application 24 that it has saved the ID.
- the second application 24 can then send a command to the first application 20 to forward the ID to a further application 20 from another source, which then establishes a connection to the second application 24, and so on.
- the second application 24 (for example in an HbbTV environment using the DIAL protocol from the HbbTV-2 specification) can start all applications 20 of the authorized sources one after the other and transmit the ID in each case.
- the second application 24 can start an application on the first device 12 and thereby transmit the URLs of all applications 20 from authorized sources.
- the started application can then integrate the applications 20 of the authorized sources as inline frames and pass the ID to the applications 20 in the inline frames.
- the ID can be transferred, for example, via URL parameters to the addresses of the applications 20 from authorized sources.
- the ID can be transported by means of the W3C web messaging API between the started application and the authorized applications 20 by embedding in inline frames.
- a web service can also be used. If an application 20 on the first device 12 wants to connect to the second application 24 and does not have the ID, the application 20 can set up a forwarding to the application of the web service. If the ID is not available to the web service application, it can ask the user to enter the ID. Once the user has entered the ID, the web service application can save it on the first device 12. The web service application can then set up a redirection to the application 20 on the first device 12 and transmit the ID in the process. The application 20 on the first device 12 can store the ID on the first device 12. The ID can thus be made available to all applications 20 on the first device 12 via a forwarding to the application of the web service.
- the web service can also serve as a central gateway to Google's “Firebase cloud messaging” service (other platforms for second devices 16 offer equivalent services).
- Applications 24 which run in the background on a device 16 and do not have special privileges are typically cleaned up by the operating system after a certain time in order to free resources such as main memory and CPU. In this state, said applications 24 can no longer execute any code. In the tidy state, the second application 24 could therefore no longer search for the first device 12 or the communication service 22 in the network (home network) or react to messages from a first application 20.
- scheduled tasks e.g.
- FCMs are push messages that can be sent to an application on a device 16 via the Firebase cloud messaging service.
- the application 24 can display a notification to the user (for example a “notification” as an “icon” in the status bar, possibly supported by a vibration alarm and / or a beep), via which the user can then access the second application 24 can start again.
- a notification for example a “notification” as an “icon” in the status bar, possibly supported by a vibration alarm and / or a beep
- FCM FCM
- the web service offers the possibility of triggering actions in unreachable second applications 24 on a second device 16 that make them accessible again.
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Human Computer Interaction (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Stored Programmes (AREA)
- Mobile Radio Communication Systems (AREA)
- Computer And Data Communications (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP19194998.1A EP3787299A1 (de) | 2019-09-02 | 2019-09-02 | Aufbau einer verbindung zwischen einer ersten anwendung auf einem ersten gerät und einer zweiten anwendung auf einem zweiten gerät |
PCT/EP2020/070413 WO2021043490A1 (de) | 2019-09-02 | 2020-07-20 | Aufbau einer verbindung zwischen einer ersten anwendung auf einem ersten gerät und einer zweiten anwendung auf einem zweiten gerät |
Publications (1)
Publication Number | Publication Date |
---|---|
EP4026346A1 true EP4026346A1 (de) | 2022-07-13 |
Family
ID=67956445
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP19194998.1A Pending EP3787299A1 (de) | 2019-09-02 | 2019-09-02 | Aufbau einer verbindung zwischen einer ersten anwendung auf einem ersten gerät und einer zweiten anwendung auf einem zweiten gerät |
EP20740047.4A Pending EP4026346A1 (de) | 2019-09-02 | 2020-07-20 | Aufbau einer verbindung zwischen einer ersten anwendung auf einem ersten gerät und einer zweiten anwendung auf einem zweiten gerät |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP19194998.1A Pending EP3787299A1 (de) | 2019-09-02 | 2019-09-02 | Aufbau einer verbindung zwischen einer ersten anwendung auf einem ersten gerät und einer zweiten anwendung auf einem zweiten gerät |
Country Status (6)
Country | Link |
---|---|
US (1) | US20220303611A1 (de) |
EP (2) | EP3787299A1 (de) |
JP (1) | JP7416481B2 (de) |
KR (1) | KR20220053660A (de) |
CN (1) | CN114342412A (de) |
WO (1) | WO2021043490A1 (de) |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8839302B2 (en) * | 2011-07-14 | 2014-09-16 | Samsung Electronics Co., Ltd. | Launching an application from a broadcast receiving apparatus |
US8990913B2 (en) * | 2012-04-17 | 2015-03-24 | At&T Mobility Ii Llc | Peer applications trust center |
DE102013106005B4 (de) * | 2012-06-12 | 2018-12-06 | Lenovo (Beijing) Co., Ltd. | Informationssteuerverfahren für einen Würfel und elektronische Vorrichtung, die ein Würfel ist |
ITTO20120744A1 (it) * | 2012-08-29 | 2014-03-01 | Inst Rundfunktechnik Gmbh | Bereitstellung von applikationen auf mehreren elektronischen geraeten |
MX2016003821A (es) | 2013-09-23 | 2016-08-04 | Samsung Electronics Co Ltd | Metodo y aparato para ejecutar una aplicacion en un sistema de comunicacion inalambrico. |
JP6301464B2 (ja) | 2013-11-04 | 2018-03-28 | エルジー エレクトロニクス インコーポレイティド | 電子装置及び電子装置の制御方法 |
US10554745B2 (en) | 2014-01-14 | 2020-02-04 | Lg Electronics Inc. | Method and apparatus for managing connection between broadcasting reception device and another device which are connected through network |
CN104079987A (zh) * | 2014-06-25 | 2014-10-01 | 深圳市视维科技有限公司 | 基于数字电视机顶盒的hbbtv多屏互动系统及实现方法 |
CN108419132B (zh) * | 2018-04-16 | 2021-04-13 | 海信视像科技股份有限公司 | HbbTV应用控制方法及装置、HbbTV终端 |
-
2019
- 2019-09-02 EP EP19194998.1A patent/EP3787299A1/de active Pending
-
2020
- 2020-07-20 CN CN202080061867.1A patent/CN114342412A/zh active Pending
- 2020-07-20 EP EP20740047.4A patent/EP4026346A1/de active Pending
- 2020-07-20 WO PCT/EP2020/070413 patent/WO2021043490A1/de unknown
- 2020-07-20 US US17/639,437 patent/US20220303611A1/en active Pending
- 2020-07-20 KR KR1020227010821A patent/KR20220053660A/ko not_active Application Discontinuation
- 2020-07-20 JP JP2022513901A patent/JP7416481B2/ja active Active
Also Published As
Publication number | Publication date |
---|---|
KR20220053660A (ko) | 2022-04-29 |
CN114342412A (zh) | 2022-04-12 |
JP2022545971A (ja) | 2022-11-01 |
EP3787299A1 (de) | 2021-03-03 |
WO2021043490A1 (de) | 2021-03-11 |
US20220303611A1 (en) | 2022-09-22 |
JP7416481B2 (ja) | 2024-01-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE69832037T2 (de) | Dynamische Netzwerkkonfiguration für einen unidirektionalen Adapter | |
DE602004011579T2 (de) | Adress-Selbstkonfiguration in Ad-hoc Netzen | |
DE60132433T2 (de) | Sofortige nachrichtenübermittlung mit zusätzlicher sprachkommunikation | |
DE69838541T2 (de) | Verbindungsherstellung zwischen entfernten Einheiten mit Hypertext-Übertragungsprotokoll | |
DE69735009T2 (de) | Übertragungssystem | |
DE602005005131T2 (de) | Nutzungsberechtigung für Dienste in einem drahtlosen Kommunikationsnetzwerk | |
DE102006049131B4 (de) | Verfahren und System für Netzwerkdienste bei einem mobilen Fahrzeug | |
DE10148985A1 (de) | Verfahren zur Ausgabe von personalisierten Informationen auf einer Website | |
EP3162018B1 (de) | Verfahren zum aufbau einer für die übermittlung von medienströmen geeigneten kommunikationsverbindung von einem ersten rtc-client zu einem zweiten rtc-client | |
DE112006001712B4 (de) | Auf dem Address Resolution Protocol basierendes drahtloses Zugriffspunktverfahren und entsprechende Vorrichtung | |
DE60311113T2 (de) | Adressenerzeugungsverfharen in einer mit einem netzwerk verbundenen einrichtung und das verfahren verwendende einrichtung | |
DE60120437T2 (de) | Ein endgeräte-gestütztes Diensterkennungsverfahren | |
EP3488585B1 (de) | Vorrichtung und verfahren zur effizienten realisierung von online- und offline-telefonie in verbindung mit der übertragung und auswertung nutzerspezifischer daten | |
DE10316236B4 (de) | Verfahren und Anordnung zur Konfiguration einer Einrichtung in einem Datennetz | |
DE102013109884B3 (de) | Verfahren zum Herstellen der Verbindung von Netzwerk-Endgeräten | |
EP4026346A1 (de) | Aufbau einer verbindung zwischen einer ersten anwendung auf einem ersten gerät und einer zweiten anwendung auf einem zweiten gerät | |
DE10260926B4 (de) | Kommunikationsverfahren | |
EP2031831B1 (de) | Einrichtung zur umleitung in einem persönlichen netzwerk einer ims-domäne | |
EP2800342B1 (de) | Verfahren und system für ein zustandsabhängiges ip-adressmanagement | |
EP3537654B1 (de) | Verfahren und system zum ermitteln einer konfiguration einer schnittstelle | |
DE60126912T2 (de) | Aufbau eines steuerungskanals | |
DE102017205786B4 (de) | Verfahren zum Konfigurieren zumindest eines Geräts in einem Netzwerk, Computerprogramm und computerlesbares Speichermedium | |
WO2016075066A1 (de) | Verfahren zur übermittlung von daten zwischen zwei teilnehmern | |
DE602004005214T2 (de) | System und Verfahren zur drahtlosen Einrichtung eines mobilen Kommunikationsgeräts | |
CN105306238A (zh) | 终端接入方法、装置和系统 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: UNKNOWN |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20220310 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
DAV | Request for validation of the european patent (deleted) | ||
DAX | Request for extension of the european patent (deleted) | ||
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
17Q | First examination report despatched |
Effective date: 20240411 |