Method for displaying streaming digital media on an internet-connectable remote device having a web-browser

The method and system address control and synchronization issues in digital media casting by enabling dynamic pairing and streaming of additional content between devices, enhancing user experience and usability.

GB2706016APending Publication Date: 2026-11-11GO SEE TV LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
GB2025019786
Authority / Receiving Office
GB · GB
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-04-10
Filing Date
2025-11-21
Publication Date
2026-11-11

AI Technical Summary

Technical Problem

Existing digital media casting solutions, such as Miracast, Google Cast, and Apple AirPlay, suffer from control limitations, usability issues, high latency, and poor audio/video synchronization, especially when casting or mirroring to multiple screens, disrupting the viewing experience.

Method used

A method and system for simultaneous digital media display on connected devices using an initiator device and a streaming device, facilitated by a remote server element that enables dynamic pairing and streaming of additional media content based on cue markers, allowing seamless interaction and control between devices.

Benefits of technology

Enhances user experience by providing seamless control, reduced latency, and synchronized audio/video playback across multiple screens, enabling interactive experiences and improved usability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

An initiator device 12 initiates a pairing with a streaming device 14 on an associated data network 22. A remote server element 16 separately streams to the paired streaming device 14 a first digital
Need to check novelty before this filing date? Find Prior Art

Description

The present invention relates to a method for simultaneously displaying associated first and second digital media on a combination of devices that share a connection to an associated data network. The invention also relates to a system which is specifically configured for the method. The proliferation of smartphones and smart televisions has led to a growing demand for seamless media casting solutions that allow users to stream digital content from mobile devices to larger screens. Technologies such as Miracast RTM, Google Cast RTM also called Chromecast RTM, Apple AirPlay RTM, and DLNA RTM have emerged to address this need. However, despite their widespread adoption, these casting solutions exhibit limitations which hinder the user experience, reliability, and interoperability. In particular, control limitations affect usability. In many cases, once casting begins, the smartphone either mirrors its screen entirely, which prevents multitasking, or relinquishes control entirely to the television. Additionally, to implement a casting or mirroring experience, a user typically has to undertake numerous clicks, taps and selections with their device in an effort to initiate the connection. Even then, the pairing can fail mid-process, thus requiring the user to start again from the beginning. Depending on the ecosystems being used across the platforms, the pairing or casting may fail completely. Furthermore, casting or mirroring often results in high latency connections as well as poor audio and video synchronisation, which disrupts the viewing experience. This becomes particularly pronounced when attempting to cast or mirror to several screens on the same local network, which is often preferred for a shared viewing experience. The present invention seeks to provide a solution to these problems. According to a first aspect of the invention, there is provided a method for simultaneously displaying associated first and second digital media on an internet-connectable initiator device having a first display and on an internet-connectable streaming device having a second display, the method comprising the steps of: a] the initiator device initiating a pairing with the streaming device on an associated data network; b] a remote server element separately of the initiator device streaming to the paired streaming device a first digital media, at one or more cue markers within the streaming first digital media the remote server element outputting a notifier element to the first display of the paired initiator device and / or the second display of the paired streaming device; and c] on activation of the notifier element, the remote server element dynamically sending to the paired initiator device for display on the said first display a second digital media, so that a user obtains associated second data of the second digital media on the first display of the initiator device in addition to first data of the first digital media on the paired streaming device. Preferably, during step a], said initiator device connects to an in-app browser for outputting an initiator-device identifier to a handshake server forming part of said remote server element on the associated data network. In this case, said initiator-device identifier may include one or more of a campaign identifier, a unique initiator-device hardware identifier, and an initiator-device public IP address. Furthermore, said remote server element preferably includes a communication server on the associated data network, said handshake server connecting with said communication server and outputting thereto at least one of the unique initiator-device hardware identifier and the initiator-device public IP address. Preferably, in step a], a streaming-device public IP address of the said streaming device matches the initiator-device public IP address of the initiator device enabling said streaming device to be discoverable by the communication server on the associated data network. Therefore, the communication server optionally outputs a unique code identifier to the discovered streaming device on the associated data network, and outputs said unique code identifier with a unique streaming-device hardware identifier of the said streaming device for storage as a unique ID pair at the handshake server. Additionally, the handshake server preferably outputs the unique code identifier associated with the discovered streaming device to the in-app browser, so that on selection of a said unique code identifier, the handshake server validates said discovered streaming device via the unique ID pair enabling pairing of the initiator device and the validated said streaming device, and instructs the communication server to initiate streaming of said first digital media to the said validated streaming device. As such it may be preferable that, when only one said streaming device is discovered on the associated data network, display of the unique code identifier of the discovered streaming device outputted by the handshake server to the in-app browser is omitted, the validation of the discovered streaming device by the handshake server being automatic. Additionally or alternatively, there may be two or more discovered streaming devices on the associated data network, the communication server outputting separate unique code identifiers to each said discovered streaming device for display on the respective second displays, and outputting the separate unique code identifiers associated with respective unique streaming-device hardware identifiers of the two or more streaming device for storage as separate unique ID pairs at the handshake server. Preferably, said remote server element includes a handshake server on the associated data network, and in step a], said streaming device outputs a unique code identifier with a unique streaming-device identifier and a streaming-device public IP address for storing at the said handshake server, and displays a connection identifier on the second display. In this case, during step a], preferably said initiator device uses said connection identifier to connect to an in-app browser, and outputs an initiator-device identifier for storage at the handshake server. Furthermore, said initiator-device identifier may therefore include one or more of a unique initiator-device hardware identifier and an initiator-device public IP address. Preferably, in step a], the streaming-device public IP address of said streaming device matches the initiator-device public IP address of the initiator device thereby enabling said streaming device to be discoverable by the initiator device via the handshake server on the associated data network. Additionally, the handshake server may therefore output a unique code identifier associated with the said discovered streaming device to the in-app browser of the initiator device, so that on selection of said unique code identifier, the handshake server validates said initiator device enabling pairing of the initiator device and the said streaming device. When only one said streaming device is discovered on the associated data network, it is preferable that display of the unique code identifier of the discovered streaming device outputted by the handshake server to the in-app browser is omitted, the validation of the discovered streaming device by the handshake server being automatic. Alternatively, when there are two or more discovered streaming devices on the associated data network, the handshake server preferably outputs separate unique code identifiers of each said discovered streaming device for display on the first display of the initiator device. Preferably, the cue marker associated with the streaming first digital media is at least one of a cue point, a hard-encoded element, or a VAST tag. In this case, preferably the streaming device outputs an event identifier and the or a unique streaming-device hardware identifier to the remote server element, the remote server element validating the or each paired initiator device and the or each paired streaming device. Subsequent to validation, the remote server element may dynamically send to the or each paired initiator device for display on the associated said first display the second digital media. In this case, the second digital media associated with the first digital media is preferably at least one of a catalogue of products, a survey, an advertisement, information associated with an advertisement, information specifically associated with the content of the first digital media, a quiz, a live event, or a VOD asset. Preferably, an input associated with the second digital media at the initiator device is transmitted for storage to the remote server element. In this case, a plurality of said inputs may be aggregated at the remote server element, the remote server element outputting a further digital media to at least the or each paired streaming device and / or at least the or each initiator device. Additionally or alternatively, the or each said paired initiator device dynamically may output to the or each said paired streaming device an additional digital media, so that the or each user obtains associated additional data of the additional digital media on the first display of the or each paired initiator device and / or on the second display of the or each paired streaming device. The output of the additional digital media to the paired streaming device may be via the remote server element which stores an association between the additional data and the said paired initiator device. Furthermore, the or each said paired initiator device may dynamically output to the or each said paired streaming device a control signal, so that a function of at least one said paired streaming device is controlled. Again, in this case, the output of the control signal to the paired streaming device may be via the remote server element which stores an association between the control signal and the said paired initiator device. The cue marker associated with the streaming first digital media is preferably at least a live-event trigger. As such, a third-party server may output a server identifier associated with the live-event trigger to the remote server element, the remote server element validating the server identifier, and the notifier element relating to the live-event trigger. Additionally, subsequent to validation and on activation of the notifier element, the remote server element may dynamically send to the respective paired initiator device for display on the associated said first display the second digital media. Therefore, the second digital media associated with the first digital media may be a survey. Preferably, an input associated with the survey of the second digital media at the initiator device is transmitted for storage to the remote server element. A plurality of said inputs is preferably aggregated at the remote server element, the remote server element outputting another further digital media to at least the or each paired streaming device and / or at least the or each initiator device. Additionally, the internet-connectable initiator device may be a mobile telecommunications device. Optionally, the mobile telecommunications device may be a smartphone. Preferably, the internet-connectable streaming device is a non-portable device supported by a surface and having a remote control. In this case, the non-portable device may be a television. Preferably, the internet-connectable streaming device includes a native web-browser application. Additionally or alternatively, the internet-connectable streaming device may comprise an integral broadcast and broadband IP delivery standard. In this case, the integral broadcast and broadband IP delivery standard preferably includes at least HbbTV. According to a second aspect of the invention, there is provided a system specifically configured for the method of the first aspect of the invention, the system comprising the initiator device having the first display and which is able to initiate the pairing with the streaming device having the second display on the associated data network; the remote server element which separately of the initiator device is able to stream to the paired streaming device the first digital media having one or more cue markers, the remote server element including a notifier element for output to the first display of the paired initiator device and / or the second display of the paired streaming device on an occurrence of the cue marker; and on activation of the notifier element, the remote server element is able to dynamically send to the paired initiator device for display on the said first display a second digital media, so that a user obtains associated second data of the second digital media on the first display of the initiator device in addition to first data of the first digital media on the paired streaming device. According to a third aspect of the invention, there is provided a method for simultaneously displaying associated first and second digital media on an internet-connectable initiator device having a first display and on an internet-connectable streaming device having a second display, the method comprising the steps of: a] the initiator device in relation to the first digital media initiating a handoff protocol of a device discovery module and pairing with the streaming device once discovered on an associated data network; b] separately of the initiator device, the handoff protocol causing streaming to the paired streaming device the first digital media; and c] a notifier element being outputted to the first display of the paired initiator device. According to a fourth aspect of the invention, there is provided a system specifically configured for the method of the third aspect of the invention, the system comprising the initiator device having the first display, the device discovery module having the handoff protocol, the streaming device having the second display, and the associated data network; the initiator device able to initiate the handoff protocol of the device discovery module and pair with the streaming device having the second display on the associated data network; the handoff protocol separately of the initiator device enabling streaming to the paired streaming device the first digital media; and means for enabling output of a notifier element to the first display of the paired initiator device. The invention will now be more particularly described, by way of example only, with reference to the accompanying drawings, in which: Figure 1 shows an embodiment of a system, in accordance with the second aspect of the invention, that enables simultaneous displaying of associated first and second digital media on paired internet-connectable initiator device and an internet-connectable streaming device; Figures 2a to 2e show a first embodiment of a pairing method, in accordance with the first aspect of the invention, by which the system of Figure 1 can implement a pairing between the internet-connectable initiator device and an internet-connectable streaming device, when initiated by a user’s mobile telecommunications device, such as a smartphone, using a social media advert and / or direct link and / or deep link delivered to the device itself; Figures 3a to 3c show a second embodiment of a pairing method, in accordance with the first aspect of the invention, by which the system of Figure 1 can implement a pairing between the internet-connectable initiator device and an internet-connectable streaming device, when initiated by a user’s mobile telecommunications device using a QR code or similar connection identifier on an associated smart television or similar internet-connectable streaming device; Figures 4a and 4b show an embodiment of a TV-to-Companion interaction method, in accordance with the first aspect of the invention, by which a user’s paired smartphone is dynamically and separately sent digital-media data associated with but different to the digital media being streamed to the paired smart television; Figure 5 shows a first embodiment of a Companion-to-TV interaction method, in accordance with the first aspect of the invention, by which a user’s paired smartphone dynamically and separately sends digital-media data associated with but different to the digital media being streamed to the paired smart television; Figure 6 shows a second embodiment of a Companion-to-TV interaction method, in accordance with the first aspect of the invention, by which a user’s paired smartphone dynamically and separately sends digital-media data associated with but different to the digital media being streamed to the paired smart television; Figures 7a to 7c show an embodiment of a TV-to-Companion-to-TV interaction method, in accordance with the first aspect of the invention, by which a user’s paired smartphone is dynamically and separately sent digital-media data associated with but different to the digital media being streamed to the paired smart television, followed by the user’s paired smartphone in response dynamically and separately sending further associated digital-media data back to the paired smart television; and Figures 8a to 8c show an embodiment of a Third-Party-to-Companion and / or TV interaction method, in accordance with the first aspect of the invention, by which a Third-Party Server dynamically and separately sends digital-media data associated with but different to the digital media being streamed to the paired smart television to a user’s paired smartphone, followed by the user’s paired smartphone in response dynamically and separately sending further associated digital-media data to the paired smart television. Referring firstly to Figure 1 of the drawings, there is provided a system 10 which comprises an internet-connectable initiator device 12, at least one internet-connectable streaming device 14, a remote server element 16, a broadcast server 18, in some cases a third-party server 20, and an associated data network 22, being for example, the internet. The initiator device 12 is preferably a or a part of a smartphone 24 or similar user device. Such user device 24 is preferably an electronic device, and in this case is a mobile telecommunications device. The user device 24 includes hardware, software, and / or embedded logic components or a combination of two or more such components. The user device 24 includes, either integrated, remote or semi-remote, a first display screen 26 to allow a user to interact with and use electronic functions of the user device 24. By way of examples, the user device in addition to the preferred option of a smartphone 24, may be or include a computer system, such as a desktop computer, notebook or laptop computer, netbook, a tablet computer, e-book reader, GPS device, camera, handheld electronic device, cellular or mobile telephone, smart television, or other suitable electronic device, or any other suitable device and / or combination thereof. The user device 24 includes standard known components and circuitry to allow a user of the user device 24 to access the associated data network 22, and once accessed to communicate with other devices on said data network 22. The user device 24 includes a web browser 28, also called herein and throughout a ‘web-app’. Said web browser 28 may be a native application provided as part of the operating system of the user device 24. Examples of operating systems are Google Android, Apple Safari, Linux Ubuntu; and examples of such native web browsers are Microsoft Edge, Google Chrome, Mozilla Firefox. Other, typically non-native web browsers, are available, such as Brave and Opera, and these may be preferred and installed by the user. Using said web browser 28 allows a user in a standard and known manner to connect to the internet via Uniform Resource locator, or URL, addresses; and to display or render desired webpages from HyperText Markup Language, also known as HTML, and other known coding languages. Such webpages may be or include digital media, and more particularly but not necessarily exclusively, streaming digital media, such as video and / or audio files. The said at least one streaming device 14, in this embodiment, is preferably a smart television 30 having a second display screen 32 and typically a separate user-operable remote control 34. It is envisaged that the streaming device 14, being the smart television 30, has a stand or is mounted on a wall of a room. As such, although the smart television 30 may be moved, it is considered to be a non-portable or non-mobile device due to its size and bulk. The second display 32 therefore is generally significantly larger than the first display 26 of the smartphone 24 or other user device, as described above. The smart television 30, as with the aforementioned user device 24, also includes standard known components and circuitry to allow a user of the streaming device 14 to access the associated data network 22, and once accessed to communicate with other devices on said data network 22. To enable this connectivity, the streaming device 14 includes standard known components and circuitry to allow a user of the streaming device 14 to access the associated data network 22, and once accessed to communicate with the said other devices on the data network 22. Similarly to the user device 24, the streaming device 14 includes a web browser 36, also called herein and throughout a ‘web-app’. Said web browser 36 may be a native application provided as part of the operating system of the streaming device 14 or embedded therein. Examples of operating systems for smart televisions are Google TV, Tizen, webOS, Roku OS, Fire TV, VIDAA and tvOS; and examples of such integrated, native or embedded web browsers are Google Chrome, Samsung Internet Browser, LG Web browser, Amazon Silk, Opera. A focus of the current invention is to enable a system that can be used without requiring additional software applications to be installed on the smart television 30 or other streaming device 14 by the user prior to use of the system. Preferably, the smart television 30 or other streaming device 14 is HbbTV RTM compliant. Other similar integral broadcast and broadband IP delivery standards or frameworks for hybrid TV interactivity may be considered. Such frameworks enable broadcasters, in relation to a single internet-connectable streaming device 14, to augment a linear television broadcast with one or more internet-enhanced features. Although herein and throughout whilst explaining the various embodiments of the invention, a single internet-connectable user device 24 and a single internet-connectable streaming device 14 will be referred to, the invention can be utilised with two or more said user devices 24 and / or two or more said streaming devices 14 to allow for multiuser experiences, such as watch-parties for internet-streaming live or replay events. The aforementioned remote server element16, which may be understood to be or include a device discovery module, may typically comprise a handshake server 38 and a communication server 40. The communication server 40 may be dispensed with in certain embodiments, as will be understood below. The handshake server 38 uses known server technology, and further detailed description is omitted for brevity. The handshake server 38 is a network-accessible computing system configured to facilitate secure session initiation between at least the user device 24 and the streaming device 14 by negotiating cryptographic parameters, protocol versions, and capability sets prior to establishing a persistent data channel, thereby enabling authenticated and encrypted exchange of data. In essence, the handshake server, which may be part of the device discovery module, preferably implements a handoff protocol to pair the initiator device with the one or more streaming devices. The communication server 40, in embodiments in which it is utilised, similarly uses known server technology, and further detailed description is omitted for brevity. The communication server 40 is preferably a network-based computer processing system that mediates bidirectional data exchange between the user device 24 and the streaming device 14 by routing, synchronizing, and transforming messages in accordance with defined application protocols. The broadcast server 18, as with the handshake server 38 and communication server 40, uses known server technology, and further detailed description is again omitted for brevity. The broadcast server 18 is a transmission system that multiplexes and distributes linear or streaming audiovisual content, along with associated signalling data such as cue markers via one-way digital broadcast streams, for example DVB-T / S / C, ATSC, ISDB, to a plurality of receiver or streaming devices simultaneously. The third-party server 20, again similarly to the above, uses known server technology and as such further detailed description is omitted. The third-party server 20 is preferably distinct, separate and independent of the handshake server 38, communication server 40, and / or broadcast server 18. However, it is feasible that the third-party server 20 may be operated or owned by the same entity or entities as the broadcast server 18, the handshake server 38, and / or the communication server 40. The associated data network 22 is envisaged in this invention to be an internet connected network of distributed computers and computer systems which allows, typically bidirectional, data communication between suitably connected devices. However, the associated data network may be one or more of the following an ad hoc network, an intranet, an extranet, a virtual private network also called a VPN, a local area network or LAN, a wireless LAN or WLAN, a wide area network or WAN, a wireless WAN or WWAN, a metropolitan area network or MAN, a portion of the Internet, a portion of a Public Switched Telephone Network or PSTN, and / or a cellular or mobile telephone network. Links 42 may connect the internet-connectable initiator device 12, the at least one internet-connectable streaming device 14, the remote server element 16, the broadcast server 18, and the third-party server 20 with the associated data network 22. The said links 42 are again well known standard technology, and maybe one, more or a combination of one or more of a wireline link, such as for example Digital Subscriber Line or DSL; Data Over Cable Service Interface Specification or DOCSIS; a wireless link, such as for example Wi-Fi or Worldwide Interoperability for Microwave Access or WiMAX; or an optical link such as for example Synchronous Optical Network also known as SONET, or Synchronous Digital Hierarchy also known as SDH. In particular embodiments, one or more said links 42 may each be, include or be part of an ad hoc network, an intranet, an extranet, a VPN, a LAN, a WLAN, a WAN, a WWAN, a MAN, a portion of the Internet, a portion of the PSTN, a cellular technology-based network, a satellite communications technology-based network, another like or similar link, or a combination of two or more such links. Referring now to Figures 2a to 2e, a first embodiment of a pairing method between the user device 24 and the streaming device 14 will now be described. At Step 210, the user uses their internet-connected initiator device 12, which in this case is the aforementioned smartphone user device 24, to interact with a campaign entry point, typically being an interactive advertisement or image on one or their social media accounts or feeds. Such social media accounts may be provided, for example, by Meta such as Facebook and / or Instagram, X, Truth Social, Rumble or the like. The said interaction involves clicking on the interactive advertisement, typically being a link-enabled rendered-image displayed on the first display 26 of the user device 24, and provided via the advertising engine of the social media account. The advertisement may be targeted to the user and may include an embedded call-to-action also called CTA. Additionally or alternatively, a direct link or deep link may be provided and displayed on the first display 26 of the user device 24. In this case, the user can click on the direct link. At Step 212, upon clicking the CTA of the advertisement, the user is redirected from the social media account to the web-app 28 of the user device 24. The web-app 28 launches, and may be a branded version associated with the campaign or a media channel. Furthermore, the web-app may include a User Engagement Module or element, offering reminders, loyalty rewards, personalized notifications and / or recommendations, retention mechanisms or similar. At Step 214, the user initiates a data connection to their smart television 30 or smart televisions 30 by pressing a typically link-enabled image-rendered connect button or similar. Other image-rendered buttons may be available to choose from, such as “Remind me Later” or similar. At Step 216, the web-app 28 encodes and transmits an initiator-device identifier, which includes one or more three identifier elements, to the remote handshake server 38. The three identifier element are preferably: a campaign identifier which identifies the specific interactive or advertising campaign that the user has interacted with; a unique initiatordevice hardware identifier which is generated based on the hardware of the user device 24, thus representing the specific smartphone 24 that the user is utilising; and an initiatordevice public IP address that is associated with the user’s current network environment and the connection of the user’s device to the associated data network 22. At Step 218, upon receiving the connection request, the handshake server 38: validates the request by validating the campaign identifier against registered campaigns to ensure the request is legitimate and active; validates that the user device 24 being or associated with the initiator device 12 satisfies any required constraints, such as location, device model, device brand, and the like; and associates the unique initiator-device hardware identifier along with the initiator-device public IP address with the current session, and temporarily stores them as an associated pair whilst the remainder of the pairing process is undertaken. At Step 220, prior, simultaneously or subsequently to the validation step, the handshake server 38 forwards via a secure API request the unique initiator-device hardware identifier and the initiator-device public IP address to the communication server 40. At Step 222, the communication server 40, using the initiator-device public IP address, locates any available devices, in this case being the or each smart television 30, on the associated data network 22 with matching streaming-device public IP addresses. At Step 224, the communication server 40 generates and outputs a first data message, for example as a first push notification, to the or each discovered or active streaming device 14 a unique code identifier, in this embodiment being a unique four digit pairing code. Although a four digit code is utilised, any suitable unique identifier code can be used. The unique four digit pairing code is displayed on the second display 32 of the or each discovered streaming device 14, in this case the or each smart television 30 on the network. At Step 226, additionally, the communication server 40 responds to the handshake server 38 via a secure API request with the or each discovered streaming-device hardware identifier along with the associated unique four digit pairing code. At Step 228, the handshake server 38 temporarily stores the available pairs of streamingdevice hardware identifiers and their corresponding unique four digit pairing codes as a unique ID pair. At Step 230, the handshake server 38 generates and outputs to the web-app 28 of the initiator device 12 a second data message, for example a second push notification. The second data message lists or is associated with the or each unique four digit pairing code of the available smart television 30s or other streaming devices 14 on the associated data network 22. At Step 232, if more than one smart television 30 or other streaming device 14 is available for pairing, the second data message displayed on the first display 26 of the initiator device 12 lists the separate and unique four digit pairing codes, allowing the user to select the or each preferred streaming device 14. However, if only one discovered and active streaming device 14 is present on the associated data network 22, the selection step required by the user may be omitted and selection may automatically occur within the system 10 without requiring user input or interaction. At Step 234, the web-app 28 initiates a secure API request to the handshake server 38 to validate the unique ID pair, being the unique streaming-device hardware identifier and the unique four digit pairing code, along with authentication token or tokens ensuring mutual verification of both the initiator device 12 and the handshake server 38. At Step 236, the handshake server 38 verifies that the selected unique four digit pairing code and the streaming-device hardware identifier match the stored data; validates the campaign association to ensure the smart television 30 or other selected streaming device 14 or devices is / are eligible for the same campaign identification; and finalises the pairing of the user device 24, which is or includes the initiator device 12, with the selected streaming device 14, thereby binding the session of the user device 24 to the or each specifically selected smart television 30. At Step 238, the handshake server 38 then sends a third data message, for example as a third push notification, indicating pairing success to the web-app 28 of the user device 24 and to the or each smart television 30 or other streaming device 14. Additionally, the communication server 40 is also informed of the pairing success. At Step 240, upon successful pairing, the communication server 40 automatically initiates and outputs a trigger message or trigger data to the paired smart television 30 or other streaming device 14. The trigger data includes a broadcast channel identifier such as a HbbTV identifier, and preferably a fallback URLorapp identifier if broadcast launching is unavailable. At Step 242, for broadcast-capable smart televisions 30 or other streaming devices 14, the trigger data automatically causes switching of the paired streaming device 14 to the specified channel and / or launches the corresponding HbbTV broadcast content, advert-supported video-on-demand, as called AVOD, channel or similar content from the broadcast server 18. In this way, the or each paired streaming device 14 receives, via its respective links 42 from the broadcast server 18, first digital media 44 containing first digital data. If the paired streaming device 14 lacks the required broadcast capabilities, it defaults to opening a web-based or app-based version of the broadcast content from the broadcast server 18. Furthermore, there may be a prompt to install the respective TV application, if it is not already installed on the streaming device. At Step 244, at the initiation of and / or during the broadcast, the paired streaming device 14 outputs data to the handshake server 38 regarding the success of the pairing; the streaming-device identifiers; campaign identifier; timestamps and outcomes; and heartbeat continuation for session persistence. The pairing between the user device 24 and the streaming device 14 preferably remains active only while the smart television 30 or other paired streaming device 14 continues sending heartbeat signals. When the heartbeat signals stop, either because the user changes the broadcast channel, powers off the paired user device 24 and / or the or each paired streaming device 14, or the conditions of the associated data network 22 change, the handshake server 38 then automatically invalidates the stored pairing resulting in disconnection. This ensures that pairings cannot persist unintentionally; subsequent campaigns cannot reuse expired sessions; and / or that privacy is maintained, as no permanent device mappings are retained. When re-pairing is required, the system 10 may enable an alias to be implemented by the user for the above-mentioned unique four digit pairing code associated with a specific streaming device 14 which has previously been connected to. For example, the alias ‘Kitchen TV’ may be applied by the user. Referring now to Figures 3a to 3c, a second embodiment of the pairing method between the user device 24 and the streaming device 14 will now be described. This pairing method enables broadcast entry and streaming-device side activation. At Step 310, the user uses their streaming device 14, which for example is the smart television 30 but could be the user’s smartphone 24 or other internet-connectable streaming device with a display, to navigate to a streaming broadcast channel or service provided by the broadcast server 18. This may be termed a One-Link RTM enabled channel or service. At Step 312, the smart television 30 sends for storing and registering a secure API request to the handshake server 38, which includes the streaming-device hardware identifier, the unique four digit code identifier, and the streaming-device public IP address. At Step 314, as part of the data of the streaming broadcast, a connection identifier, such as a QR code or similar, is displayed on the second display 32 of the smart television 30 or other streaming device 14. This may occur during an interactive segment of the streaming broadcast, for example, or due to the user pressing an associated button on the remote control 34 of the smart television 30 or other streaming device 14. The user scans the connection identifier displayed on the second display 32 of the smart television 30 using their smartphone 24 as the initiator device 12. The initiator device 12 thus connects to the associated web-app 28 corresponding to the active streaming broadcast. The initiator-device identifier is also outputted for storage as a secure API request at the handshake server 38. As above, the initiator-device identifier preferably includes one or more of the unique initiator-device hardware identifier and the initiator-device public IP address. At Step 316, upon receiving the API request from the initiator device 12, the handshake server 38 searches for all streaming devices 14 on the associated data network 22 that are currently active, registered under a matching streaming-device public IP address, and have a matching 4-digit pairing code with an expected streaming-device hardware identifier. If multiple streaming devices 14, such as smart televisions 30 which are HbbTV- or similarly enabled, are active within the associated data network 22, the handshake server 38 compiles a list of potential matches and sends this back to the web-app 28 of the user device 24. On the first display 26 of the user device 24, the web-app 28 then displays a list of unique four digit code identifiers or their aliases as explained above, one or more of which may be selected for pairing, or the system 10 automatically selects the streaming device 14 if only one unique four digit code identifier or associated alias is valid. At Step 318, once the user or system 10 confirms or selects the or each streaming device 14 to pair with, the web-app 28 of the user’s initiator device 12 issues a secure API request to the handshake server 38. The API request includes the unique initiator-device hardware identifier of the user device 24, in this example being the user’s smartphone 24, the selected unique four digit code identifier, and cryptographic authentication credentials for verification. At Step 320, the handshake server 38 then performs a mutual authentication sequence, verifying that the unique four digit code identifier along with initiator-device hardware identifier match an active streaming device session; that the initiator-device public IP address and the streaming-device public IP address match or correspond, ensuring the said devices are part of the same associated data network 22; and that the pairing request originated from a valid campaign and service environment. These elements are all logged by the handshake server 38, similarly to the first pairing method above. At Step 322, the handshake server 38 outputs a fourth message data, for example a fourth push notification, to the or each paired smart television 30 indicating that a companion initiator device 12, in this case being a companion smartphone 24 of the user, has successfully paired and is connected. Simultaneously, the handshake server 38 outputs a fifth message data to the web-app 28 of the initiator device 12 to confirm the successful pairing event to the user, transitioning the user interface on the display of the smartphone 24 to a branded experience. At Step 324 and similarly to the first pairing method above, the or each paired smart television 30 and the handshake server 38 then begin telemetry exchange: Heartbeats are monitored to confirm ongoing activity and session validity; and campaign engagement data may be captured for analytics. The pairing between the user device 24 and the streaming device 14 remains active only while the smart television 30 or other paired streaming device 14 continues sending heartbeat signals. When the heartbeat signals stop, either because the user changes the broadcast channel, powers off the paired user device 24 and / or the or each paired streaming device 14, or the conditions of the associated data network 22 change, the handshake server 38 then automatically invalidates the stored pairing resulting in disconnection. This ensures that pairings cannot persist unintentionally; subsequent campaigns cannot reuse expired sessions; and / or that privacy is maintained, as no permanent device mappings are retained. Referring now to Figures 4a and 4b, a TV-to-Companion interaction method follows the pairing described above of the user’s initiator device 12, typically but not necessarily exclusively being a smartphone 24, having the first display 26 with a smart television 30 or other similar streaming device 14 with the second display 32. It will be understood how the invention enables a paired streaming device 14, such as a HbbTV-enabled smart television 30, which is linked to the paired user device 24, also called a companion device and being or including the above-described initiator device 12, to cooperate to deliver synchronized interactive experiences triggered by a live or on-demand broadcast event to the streaming device 14 resulting in complementary associated but separate second data forming or forming part of a second digital media 46 stream being delivered to the user device 24. At Step 410, once pairing between the user device 24 and the streaming device 14 is complete, the or each smart television 30 or other streaming device 14 plays via the broadcast server 18 the first digital media 44 comprising the live broadcast or replay. The first digital media 44 is preferably an HLS or DASH live feed or Linear VOD Stream. The first digital media 44 includes one or more cue markers 46, for example cue points via a sidecar file, encoded data within the DASH or HLS stream, or Video Ad Serving Template metadata also called VAST tags embedded within incoming media data segments, such as advertisements. These cue markers 46 are used to signify, call or activate interactive moments, for example: product placement opportunities, live polls or surveys, extended content such as behind-the-scenes experiences or more detailed data regarding a specific item within the first digital media 44 such as educational insights, or calls-to-action for sponsorship or commerce. When a cue marker 46 is reached, the HbbTV application on the smart television 30 or other paired streaming device 14 interprets it as an interactive event trigger. At Step 412, upon detecting an interactive cue marker 46, the smart television 30 securely transmits event information data to the handshake server 38. The event information data includes: the interactive event identifier, such as a tag reference or metadata identification, and the or a unique streaming-device hardware identifier of the paired streaming device 14. The transmission is secured through mutual authentication with the smart television 30 and the handshake server 38 to ensure the event originates from a trusted and known source. At Step 414, the handshake server 38 validates: the authenticity of the request from the paired smart television 30; that the event metadata is valid for the given campaign; and that the paired companion device or companion devices, typically being the or each user device 24, but not necessarily excluding one or more said streaming devices 14, are currently connected and verified via ongoing heartbeat tracking. At Step 416, if the validation event is successful, the remote server element 16, in this case being the handshake server 38, retrieves the list of associated paired companion devices 24 for the smart television 30, and sends a secure notifier element, for example as a sixth push notification, of the event to the or each companion device 24 and / or to the or each paired streaming device 14. The notifier element also includes a unique reference identifier that can be used to fetch additional data to display the interactive event. At Step 418, upon receipt and activation of the notifier element, the web-app 28 of the paired companion device 24 issues a secure request via respective links 42 to the remote server element 16 to dynamically fetch the necessary metadata for second digital media 48 containing second data relating to the interactive experience and having the unique reference identifier. The web-app 28 triggers the final network requests to receive on the user device 24 for display on the first display 26 the full campaign information which includes but is not limited to images, content, text and the like and which forms part of the said second data of the second digital media 48. The user therefore dynamically obtains the associated second data of the second digital media 48 on the first display 26 of the user device 24 being or including the initiator device 12, in addition to the first data of the first digital media 44 on the paired streaming device 14. The aforementioned second data of the associated second digital media 48, once rendered on the or each companion device 24, may include: Product catalog rendering: Displays a list of products shown or promoted in the first digital media 44 being streamed to the paired streaming device 14, thus allowing the user to browse or purchase items without leaving the experience. For example, a viewer sees a commercial for a sports shoe and the companion app displays the same model with purchase options. Interactive survey or poll: Presents questions or opinion polls related to the content. For example, a talent show voting prompt or brand engagement survey. Extended content: Offers background information, behind-the-scenes videos, or video-on-demand also called VOD assets related to the advertisement or live event. Pull or push marketing experiences: Enables the advertiser or broadcaster to push personalized content to the companion device 24, or allows the viewer to pull more information voluntarily. Pull marketing refers to interactive experiences typically triggered during advertising breaks and are designed to enhance the advertising experience. For example, an advert for a new car may have an interactive experience that generates a unique QR code on the paired smart television 30 that can be scanned to let the viewer immediately book a test drive. Push marketing refers to interactive experiences which are designed to trigger a unique experience on the or each paired user device 24. For example, surveys, buy what you see, product catalogue. Push marketing specifically targets enhancing viewer engagement with the content, while pull marketing targets fulfilment of a call to action for an advert. Each interactive experience is contextually bound to the current or enabled broadcast segment and expires automatically once the TV stream moves beyond the relevant cue marker 46 or when the pairing session ends. At Step 420, when the user interacts with the experience, such as completing a survey, learning from an educational segment, and / or purchasing a product, the companion device 24 securely transmits the interaction results back to the handshake server 38. The handshake server 38 records these results and optionally notifies the smart television 30 for synchronized responses, such as acknowledging survey completion or displaying a confirmation animation. The handshake server 38 logs all interactions with one or more of the campaign identifier, streaming-device hardware identifier, initiator-device hardware identifier, and timestamps for analytic and attribution purposes, without retaining any personal identification data. As described above in relation to the two pairing methods, the interaction between the user device 24 and the streaming device 14 remains active only while the smart television 30 or other paired streaming device 14 continues sending heartbeat signals to the handshake server 38. When the heartbeat signals stop, either because the user changes the broadcast channel, powers off the paired user device 24 and / or the or each paired streaming device 14, or the conditions of the associated data network 22 change, the handshake server 38 then automatically invalidates the stored pairing resulting in disconnection. This ensures that interactive experiences using the or each paired companion device 24 only persist while the corresponding broadcast session is active and authenticated. Referring now to Figure 5, a first embodiment of a Companion-to-TV interaction method follows the pairing described above of the user’s initiator device 12, typically but not necessarily exclusively being or being part of the smartphone 24 and also now referred to as the companion device 24, having the first display 26 with a smart television 30 or other similar streaming device 14 with the second display 32. It will be understood how the invention enables a paired user device 24 to send commands, messages, and / or reactions back to the paired streaming device 14, typically being the smart television 30, dynamically and in real time. This capability enables a new class of interactive experiences, such as: viewers using their smartphone 24 as a second-screen remote control; live chat or reaction feeds displayed on the broadcast; and / or contextual real-time audience participation, such as during live shows, sports, concerts and other events. The embodiment of this method uses the same core infrastructure as the previously described methods to ensure that all events are securely validated, authenticated, and attributed to an active pairing session. At Step 510 and following either of the above-described two pairing methods, the broadcast server 18 outputs the first data as part of the streaming first digital media 44, such as a live stream of an event, to the second display 32 of the or each paired smart television 30 or other streaming device 14. At Step 512, the web-app 28 on the companion device 24 enables typing or entering input data, being additional digital data of additional digital media, to an input box or field. For example, a live or dynamic comment, message, reaction, and / or emoji or other image data during a broadcast can be sent in real time. The web-app 28 packages the input data with: the initiator-device hardware identifier; the campaign identifier; timestamp, reaction type if required, and a current pairing session token to verify active linkage. At Step 514, the input data is securely transmitted to the handshake server 38, which validates the payload and handles authentication and routing. The handshake server 38 then: verifies the source device is currently paired and authorized; tracks the event using the associated initiator-device hardware identifier for analytics and audit logging; and securely pushes the input data to the correct target, being the or each paired smart television 30 or other streaming device 14, such as during a shared and dynamic chat and / or reaction session between multiple viewers. At Step 516, once delivered, the or each smart television 30 or other streaming device 14 displays the received input data, being the additional data of the additional digital media, as messages and / or images in real time, for example as on-screen overlays and / or on-screen graphics. This creates a live or dynamic participatory environment, where companion interactions directly influence what is seen on television. Referring now to Figure 6, a second embodiment of the Companion-to-TV interaction method follows the pairing described above. This Companion-to-TV interaction method is similar to that of the first embodiment, and therefore similar or identical steps and parts will not be described again in detail for conciseness and brevity. It will be understood how the invention enables a paired user device 24 to be used as a remote control to control the paired streaming device 14, typically being the smart television 30, dynamically and in real time. At Step 610, the user uses built-in controls within the web-app 28 of the initiator device 12 to: navigate within a HbbTV or similar app, such as select sub-menus and trigger call-to-action buttons, or similar of the paired smart television 30; adjust playback or content options; and / or change a volume or other playback settings where permitted by campaign logic. If built-in controls within the web-app 28 are not provided, then a native HbbTV API or similar may be provided and utilized. Each remote interaction is encapsulated as a command event, in this case being the additional digital data, containing: the initiator-device hardware identifier; a command type such as “change channel”, “navigation,” “open menu”, and the like; and contextual metadata describing the user’s input action. At Step 612, the handshake server 38: authenticates the command to confirm it originated from a paired and active user device 24; tracks the event for telemetry purposes; and forwards the command securely to the paired streaming device 14, in this case being the paired smart television 30. At Step 614, the smart television 30 executes the command immediately, triggering the relevant action, such as moving a selection cursor, updating volume, or displaying feedback. In both of the above two described embodiments, every interaction, whether a message, reaction, or remote control command, is tracked at the remote server element 16. This includes: the or each initiator-device hardware identifier; the or each streaming-device hardware identifier; the or each target device; the event type such as the message, reaction, control; timestamp; and campaign identifier. This data enables aggregated audience analytics, content personalization, and feedback optimization without storing personally identifiable information. One of the benefits with the above-described embodiments is the communication channel supports bidirectional signalling. Both the or each paired smart television 30 can trigger interactive moments, along with the or each companion device 24 also being able to send events or commands simultaneously and dynamically to the or each paired smart television 30 or other streaming device 14. As with the above embodiments, the interaction between the or each user device 24 and the or each streaming device 14 remains active only while the smart television 30 or other paired streaming device 14 continues sending heartbeat signals to the handshake server 38. When the heartbeat signals stop, either because the user changes the broadcast channel, powers off the paired user device 24 and / or the or each paired streaming device 14, or the conditions of the associated data network 22 change, the handshake server 38 then automatically invalidates the stored pairing resulting in disconnection. This ensures that interactive experiences using the or each paired companion device 24 only persist while the corresponding broadcast session is active and authenticated. Referring now to Figures 7a to 7c, a TV-Companion-to-TV interaction method follows the pairing described above. This method extends the previously established pairing and communication framework to enable interactive, bidirectional broadcast experiences, specifically where a viewer uses their paired mobile device to respond to an interactive event, such as a quiz or poll, and the aggregated results are displayed back on the or each paired smart television 30 in real time. Similar or identical steps and parts will not be described again in detail for conciseness and brevity. At Step 710, the or each paired smart television 30 or other streaming device 14 continues to play a live, or VOD, HLS, or dash, stream from the broadcast server 18. As above, interactive segments are triggered by the cue markers 46, which may be a sidecar file containing cue points, or encoded messages in the HLS / DASH streams, or VAST tags. When an interactive segment is reached, for example, a live quiz or viewer poll begins, the HbbTV application of the paired smart television 30 interprets it as an interactive event trigger and notifies the handshake server 38. At Step 712, upon detecting the cue marker 46, the or each paired smart television 30 sends a securely signed event message to the handshake server 38. This message includes one or more of: an interactive event identifier which identifies the quiz or pol; and the streaming-device hardware identifier of the or each paired smart television 30 enabling look up of paired companions. At Step 714, the handshake server 38 authenticates and validates the message. Validation may include but is not limited to: the authenticity of the event trigger; the campaign identifier; and / or the presence of any actively paired companion devices 24 associated with the or each smart television 30 or other streaming device 14. At Step 716, once validation succeeds, the handshake server 38 retrieves and notifies via a seventh push notification, for example, all paired companion devices 24 of the new interactive event. The seventh push notification preferably includes the type of interactive experience, and a token for fetching full experience metadata. At Step 718, on activation of the seventh push notification, the web-app 28 securely fetches the said experience metadata from the remote server element 16, and in this case from the communication server 40, which includes the quiz questions, possible answers, and time limits. At Step 720, once the experience metadata is received, the web-app 28 renders an interactive quiz interface for the or each user to complete on the respective user device 24. For example, the experience metadata may include one or more of: multiple-choice questions; timed response segments; and / or predictive polls about the broadcast event of the first digital media 44. Preferably and regarding a live broadcast forming the first digital media 44, the quiz interface is active only for a limited duration, ensuring synchronization. At Step 722, once the user submits the or each answer, the companion device 24 sends securely authenticated response message data back to the handshake server 38. This payload may contain one or more: event metadata such as selected answers; the initiator-device hardware identifier; and any required timestamp or response token for ordering and integrity verification. At Step 724, the handshake server 38 validates and authenticates the securely authenticated response message data, and then: tracks each submission under the corresponding campaign identifier and the initiator-device hardware identifier; aggregates all received answers across participants, if the quiz is global or multi-user; and maintains timing data to ensure responses were submitted within a valid time window. At Step 726, once all answers are received or the time window for responses expires, the handshake server 38 aggregates the results. This includes: tallying correct answers; calculating audience-wide vote percentages; and compiling analytics summaries for the associated campaign. At Step 728, after aggregation, the handshake server 38 securely notifies the paired smart televisions 30 or other streaming devices 14. For example, these may be either a single paired smart television 30 for personal quizzes only, or all smart televisions 30 or other streaming devices 14 opted into the shared quiz experience for live events, multiviewer events, and the like. At Step 730, the handshake server 38 delivers the results payload to the HbbTV or other suitable environment of the or each paired smart television 30 or other streaming device 14, which then renders the aggregated results, being further digital media, on the associated second screen. For example, the aggregated results may comprise one or more of: showing the percentage of viewers selecting each answer; displaying “Correct Answer” highlights; or presenting live leaderboards or user-generated statistics. At Step 732, after the results are displayed, the or each smart television 30 and / or the or each companion device 24 may: reset to a default idle state awaiting the next cue marker 46; or continue interaction, for example, another round of the quiz or additional calls-to-action. Throughout this process, the handshake server 38 maintains heartbeat validation to ensure only active, authenticated participants contribute and receive updates. Once the first digital media 44 comprising the broadcast data moves past the cue marker 46 or a timeout occurs, the event session expires and the pairing preferably returns to a passive state. Referring now to Figures 8a to 8c, a Third-Party-to-Companion and / or TV interaction method follows the pairing described above. This method extends the previously established pairing and communication framework to again enable an interactive, bidirectional broadcast experience. More specifically in this case, a third-party provider or system, such as a third-party broadcaster, advertiser, analytics provider, or real-time engagement platform, can securely trigger interactive events across paired smart televisions 30 or other paired streaming devices 14 and companion devices 24 based on one or more cue markers 46 within the first digital media 44 being received from the broadcast server 18, thus enabling second digital media 48 to be dynamically and independently accessed by the paired companion device 24 and, where required, interaction back to the primary streaming device 14 or streaming devices 14. Similar or identical steps and parts will not be described again in detail for conciseness and brevity. At Step 810, the third-party server 20, which in this case may include an application or system, for example, a broadcaster’s live event control panel or an advertising campaign management API, sends a secure event request to an interactive API module 50 of the remote server element 16, preferably being the handshake server 38. Each request preferably includes one or more of: server identification credentials for authentication; a defined event type, such as live survey, product promotion, or QR overlay, for example; and optionally metadata payload, such as product details, survey questions, or donation URLs. As is well known, all API requests are encrypted and authenticated via a mutual TLS handshake or equivalent secure protocol to prevent spoofing. At Step 812, the interactive API module 50 forwards the API request to the handshake server 38 for validation. At Step 814, the handshake server 38: authenticates the request origin of the API request, verifying the identification credentials of the third-party server 20; registers and logs the event, associating it with the campaign identifier and event type; and identifies all active and opted-in devices, including the or each paired smart television 30 or other streaming device 14, and the or each companion device 24 currently participating in the campaign and therefore with the associated campaign identifier. Once validated, the handshake server 38 prepares to distribute the event data to said the or each paired smart television 30 or other streaming device 14, and said the or each companion device 24. At Step 816a, if the third-party server 20 dynamically outputs the secure event request in relation to a live interactive survey, then the or each paired companion device 24 receives the corresponding event data from the handshake server 38, and renders the survey interface on the first display 26. The user can therefore respond to the survey in real time, for example, ‘who will score the next goal?’. At Step 818a, the user responses are securely sent to the handshake server 38, and are aggregated thereon. At Step 820a, the aggregated result data is sent to the or each opted-in paired smart television 30 or other streaming device 14, and the result data is displayed on the second display 32 thereof. This example therefore allows mass, synchronized audience participation driven by a single external dynamically generated event. At Step 816b and by way of further example, a brand partner, via the third-party server 20 sending the secure API request, dynamically triggers a live QR code overlay, being in this case the event data, using a cue marker 46 in the first digital media 44. This may be, for example, a link to a donation page or special promotion. At Step 818b, the HbbTV application or similar of the or each paired smart television 30 or streaming device 14 renders the QR code overlay dynamically over the live stream forming the first digital media 44, without interrupting playback. At Step 820b, the or each paired user device 24 is able to scan the rendered QR code, linking to a donation webpage or similar. This example enables instant call-to-action overlays that can be externally triggered during a live event, and may include but not limited to one or more of a charity drive, ecommerce promotion, or second-screen registration. At Step 816c and by way of further in-use example, a retail partner, via the third-party server 20 sending the secure API request, dynamically triggers a live product promotion, tied to an ongoing advertisement or campaign, and which in this case is the event data. The event data contains, for example, name, price and purchase link. At Step 818c, the or each paired companion device 24 renders the product information instantly on the first display 26, complete with a Buy Now or Learn More button. This example turns passive broadcast advertising into transaction-enabled experiences, allowing immediate purchase or engagement from a paired user device 24, such as a smartphone 24. In this embodiment, the mutual authentication model of the system 10 ensures only authorized third-party servers can trigger live experiences. Each external event is preferably bound by: a campaign identifier; a session token tied to active heartbeats from participating devices; and user opt-in preferences, whereby the or each paired smart television 30 or other streaming device 14 along with the or each paired initiator device 12, typically being the user device 24 or companion device 24, must have explicitly joined the interactive experience. This ensures: no unapproved third-party events can appear on user screens; privacy is maintained, since no personal identifiers are shared with the third party; and synchronization is guaranteed, so all participating viewers see the same cue marker 46, such as a trigger, at the same broadcast timestamp during the streaming of the first digital media 44. It is therefore possible to provide a method that simultaneously and dynamically via cue markers displays second digital media associated with first digital media on a companion device paired with a streaming device. By delivering the first digital media to the streaming device via a remote server element, the paired companion device becomes available to receive associated second data, which may take the form of interactive or synchronized campaign experiences or other digital content. The process of pairing the companion device and the streaming device is simplified and seamless by utilising and authenticating via the remote server element. Latency issues are overcome or reduced by connecting the paired streaming device to the broadcast server instead of via the user initiator device, thereby leaving the user initiator device available for receiving and interacting with the associated second data. The words ‘comprises / comprising’ and the words ‘having / including’ when used herein with reference to the present invention are used to specify the presence of stated features, integers, steps or components, but do not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof. It is appreciated that certain features of the invention, which are, for clarity, described in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features of the invention which are, for brevity, described in the context of a single embodiment, may also be provided separately or in any suitable sub-combination. The embodiments described above are provided by way of example only, and various 5 changes and modifications will be apparent to persons skilled in the art without departing from the scope of the present invention as defined by the appended claims.

Claims

1. A method for simultaneously displaying associated first and second digital media on an internet-connectable initiator device having a first display and on an internet-connectable streaming device having a second display, the method comprising the steps of:a] the initiator device initiating a pairing with the streaming device on an associated data network;b] a remote server element separately of the initiator device streaming to the paired streaming device a first digital media, at one or more cue markers within the streaming first digital media the remote server element outputting a notifier element to the first display of the paired initiator device and / or the second display of the paired streaming device; andc] on activation of the notifier element, the remote server element dynamically sending to the paired initiator device for display on the said first display a second digital media, so that a user obtains associated second data of the second digital media on the first display of the initiator device in addition to first data of the first digital media on the paired streaming device.

2. A method as claimed in claim 1, wherein, during step a], said initiator device connects to an in-app browser for outputting an initiator-device identifier to a handshake server forming part of said remote server element on the associated data network.

3. A method as claimed in claim 2, wherein said initiator-device identifier includes one or more of a campaign identifier, a unique initiator-device hardware identifier, and an initiator-device public IP address.

4. A method as claimed in claim 3, wherein said remote server element includes a communication server on the associated data network, said handshake server connecting with said communication server and outputting thereto at least one of the unique initiator-device hardware identifier and the initiator-device public IP address.

5. A method as claimed in claim 4, wherein, in step a], a streaming-device public IP address of the said streaming device matches the initiator-device public IP address of the initiator device enabling said streaming device to be discoverable by the communication server on the associated data network.

6. A method as claimed in claim 5, wherein the communication server outputs a unique code identifier to the discovered streaming device on the associated data network, and outputs said unique code identifier with a unique streaming-device hardware identifier of the said streaming device for storage as a unique ID pair at the handshake server.

7. A method as claimed in claim 6, wherein the handshake server outputs the unique code identifier associated with the discovered streaming device to the in-app browser, so that on selection of a said unique code identifier, the handshake server validates said discovered streaming device via the unique ID pair enabling pairing of the initiator device and the validated said streaming device, and instructs the communication server to initiate streaming of said first digital media to the said validated streaming device.

8. A method as claimed in claim 7, wherein, when only one said streaming device is discovered on the associated data network, display of the unique code identifier of the discovered streaming device outputted by the handshake server to the in-app browser is omitted, the validation of the discovered streaming device by the handshake server being automatic.

9. A method as claimed in claim 6 or claim 7, wherein there are two or more discovered streaming devices on the associated data network, the communication server outputting separate unique code identifiers to each said discovered streaming device for display on the respective second displays, and outputting the separate unique code identifiers associated with respective unique streaming-device hardware identifiers of the two or more streaming device for storage as separate unique ID pairs at the handshake server.

10. A method as claimed in claim 1, wherein said remote server element includes a handshake server on the associated data network, and in step a], said streaming device outputs a unique code identifier with a unique streaming-device identifier and a streaming-device public IPaddress for storing at the said handshake server, and displays a connection identifier on the second display.

11. A method as claimed in claim 10, wherein, during step a], said initiator device uses said connection identifier to connect to an in-app browser, and outputs an initiator-device identifier for storage at the handshake server.

12. A method as claimed in claim 11, wherein said initiator-device identifier includes one or more of a unique initiator-device hardware identifier and an initiator-device public IP address.

13. A method as claimed in claim 12, wherein, in step a], the streaming-device public IP address of said streaming device matches the initiator-device public IP address of the initiator device thereby enabling said streaming device to be discoverable by the initiator device via the handshake server on the associated data network.

14. A method as claimed in claim 13, wherein the handshake server outputs a unique code identifier associated with the said discovered streaming device to the in-app browser of the initiator device, so that on selection of said unique code identifier, the handshake server validates said initiator device enabling pairing of the initiator device and the said streaming device.

15. A method as claimed in claim 14, wherein, when only one said streaming device is discovered on the associated data network, display of the unique code identifier of the discovered streaming device outputted by the handshake server to the in-app browser is omitted, the validation of the discovered streaming device by the handshake server being automatic.

16. A method as claimed in claim 14, wherein there are two or more discovered streaming devices on the associated data network, the handshake server outputting separate unique code identifiers of each said discovered streaming device for display on the first display of the initiator device.

17. A method as claimed in any one of the preceding claims, wherein the streaming device outputs an event identifier and the or a unique streaming-device hardware identifier to the remote server element, the remote server element validating the or each paired initiator device and the or each paired streaming device.

18. A method as claimed in claim 17, wherein, subsequent to validation, the remote server element dynamically sends to the or each paired initiator device for display on the associated said first display the second digital media.

19. A method as claimed in any one of the preceding claims, wherein the or each said paired initiator device dynamically outputting to the or each said paired streaming device an additional digital media, so that the or each user obtains associated additional data of the additional digital media on the first display of the or each paired initiator device and / or on the second display of the or each paired streaming device.

20. A method as claimed in any one of the preceding claims, wherein the cue marker associated with the streaming first digital media is at least a live-event trigger, a third-party server outputting a server identifier associated with the live-event trigger to the remote server element, the remote server element validating the server identifier, the notifier element relating to the live-event trigger and, subsequent to validation and on activation of the notifier element, the remote server element dynamically sending to the respective paired initiator device for display on the associated said first display the second digital media.

21. A method as claimed in any one of the preceding claims, wherein the internet-connectable initiator device is a mobile telecommunications device.

22. A method as claimed in claim 21, wherein the mobile telecommunications device is a smartphone.

23. A method as claimed in any one of the preceding claims, wherein the internet-connectable streaming device is a non-portable device supported by a surface and having a remote control.

24. A method as claimed in claim 23, wherein the non-portable device is a television.

25. A system specifically configured for the method of any one of the preceding claims, the system comprising the initiator device having the first display and which is able to initiate the pairing with the streaming device having the second display on the associated data network; the remote server element which separately of the initiator device is able to stream to the paired streaming device the first digital media having one or more cue markers, the remote server element including a notifier element for output to the first display of the paired initiator device and / or the second display of the paired streaming device on an occurrence of the cue marker; and on activation of the notifier element, the remote server element is able to dynamically send to the paired initiator device for display on the said first display a second digital media, so that a user obtains associated second data of the second digital media on the first display of the initiator device in addition to first data of the first digital media on the paired streaming device.A

Citation Information

Patent Citations

  • ViewUS2014/282677A1onEspacenetopensinnewtab

  • ViewUS2023/009446A1onEspacenetopensinnewtab

  • ViewUS2021/136129A1onEspacenetopensinnewtab