WO2016197205A1 - Système de notification - Google Patents

Système de notification Download PDF

Info

Publication number
WO2016197205A1
WO2016197205A1 PCT/AU2016/050479 AU2016050479W WO2016197205A1 WO 2016197205 A1 WO2016197205 A1 WO 2016197205A1 AU 2016050479 W AU2016050479 W AU 2016050479W WO 2016197205 A1 WO2016197205 A1 WO 2016197205A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
token
authorisation
display
security
Prior art date
Application number
PCT/AU2016/050479
Other languages
English (en)
Inventor
Adrian MARAFIOTI
Original Assignee
Grity Pty Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority claimed from AU2015902350A external-priority patent/AU2015902350A0/en
Application filed by Grity Pty Ltd filed Critical Grity Pty Ltd
Priority to AU2016275575A priority Critical patent/AU2016275575A1/en
Publication of WO2016197205A1 publication Critical patent/WO2016197205A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • H04L63/0838—Network architectures or network communication protocols for network security for authentication of entities using passwords using one-time-passwords
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/101—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM] by binding digital rights to specific entities
    • G06F21/1011—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM] by binding digital rights to specific entities to devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/44—Program or device authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/50—Secure pairing of devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]

Definitions

  • the present invention relates to a notification system.
  • the Television is a big part of the average home with people watching up to 5 hours a day in some countries. Together with the increase in connected devices (an average of 8 devices within the household) and all of them becoming interoperable, the Television will also be the hub of the "connected home" before too long. Television viewing habits have changed though, with the introduction of social media and the proliferation of connected devices. Consumers now use second screens to deepen their engagement with what they are watching However, whilst the introduction of social media has allowed people to connect instantly with anyone in the world, some trends are actually causing social isolation within the home . Summary of the Invention
  • Embodiments of the present invention provide technology to push communications received on/or initiated from a mobile communications device to a television or other public display device automatically.
  • the invention provide a notification system comprising the steps of:
  • Embodiments include the step of identifying available devices and selecting a second device from the available devices .
  • Embodiments include transmission rules defining rules for transmission of messages wherein the step of transmitting the message and security token is performed in accordance with the transmission rules.
  • the security token is a one-time token. In embodiments the security token is generated from an application on the first device.
  • the security token is requested from a notification server.
  • Embodiments include the step of generating the message comprises the steps of:
  • step of generating the message is performed within an application. In embodiments the step of authorisation of the
  • authentication token is performed on the device.
  • the step of executing authorisation of the authentication token is performed by transmitting the token to security server, and receiving confirmation from the security server whether the security token is
  • Embodiments include the step of attaching a security identifier to the message, the security identifier identifying the first device.
  • Embodiments include the step of comprising the step of displaying the message on the display device.
  • the display device is a television.
  • the security token is associated with the first device.
  • the message comprises at least one of: text data, video data or audio data.
  • the invention provides a method for displaying a notification comprising the steps of:
  • executing authorisation of the security token and displaying the message on the device is dependence on successful authorisation of the security token.
  • step of authorisation of the security token is performed on the device.
  • the step of executing authorisation of the security token is performed by transmitting the token to a security server and receiving confirmation from the security server whether the security token is successfully authorised.
  • Embodiments include the step of applying at least one display rule to the message, the display rules comprising limitations on the display of the message, wherein the step of displaying is performed in accordance with the display rules.
  • the display device is a television.
  • the device displays content and the notification is displayed concurrently with content.
  • the invention provides a notification system comprising the steps of:
  • step of generating the message is performed on receipt of the message at the first device.
  • the display device is a television.
  • Embodiments comprise an application on the first device, the steps of generating the message and applying the security token are performed within the application. Embodiments comprise the step of identifying a second device before transmitting the message.
  • the invention provides notification application running on a processor of a video display device comprising the steps of:
  • the invention provides security server for a notification system comprising the steps of:
  • Embodiments comprise the further steps of generating a message ID associated with the authorisation token
  • Embodiments comprise the further step of receiving message ID associated with the authorisation token; comprising the step of matching the received message ID and authorisation token to a stored message ID and associated token
  • the authorisation token is authorised in dependence on the received message ID and authorisation token matching a stored message ID and authorisation token associated with the message ID.
  • FIG 1 shows architecture in an embodiment of the invention
  • FIG. 1 shows the messaging flow between components of the system
  • FIG. 3 shows messaging flow between components of the system
  • FIG. 4 shows messaging flow between components of the system.
  • Figure 5 illustrates the components of the ITNS server.
  • Figure 6 illustrates the components of messaging flow in a further embodiment.
  • FIG. 1 depicts an embodiment of a notification system 100.
  • the system is an Instant Television Notification System (ITNS) .
  • ITNS system 100 includes an embodiment of a notification server, ITNS server 110; an embodiment of a communication device, mobile telephone 120; and an embodiment of a display device, television 130.
  • ITNS system 100 allows notifications to be transmitted from communications device 120 for display on display device 130 by using ITNS applications installed on mobile telephone 120 and television 130.
  • the devices communicate across communications network 140.
  • the notifications may be received by communications device from a third party or created at communications device 120.
  • the notification system allows messages to be received or initiated at a communications device, for example a mobile phone, and transmitted to a paired device for display, for example a television.
  • ITNS Overview ITNS is a communication system which enables messages to be created and distributed for display on a display device.
  • Communications device 120 operates an ITNS mobile application.
  • the application is configured to act as a messaging gateway to send ITNS messages to an ITNS display application running on display device, for example a television. Messages can be created within the ITNS application for display on the television device and received from third party devices for onward transmission and display on the television device.
  • the ITNS is a communication system which enables messages to be created and distributed for display on a display device.
  • Communications device 120 operates an ITNS mobile application.
  • the application is configured to act as a messaging gateway to send ITNS messages to an ITNS display application running on display device, for example a television. Messages can be created within the ITNS application for display on the television device and received from third party devices for onward transmission and display on the television device.
  • the ITNS is a communication system which enables messages to be created and distributed for display on a display device.
  • Communications device 120 operates an ITNS mobile application
  • ITNS system 100 includes a network server to manage the security of the system.
  • the ITNS server allocates message ID to each created message. It also allocates an authorisation token to be transmitted between the devices to authorise the authenticity of the message.
  • the ITNS mobile application interacts with an ITNS network server to authorise messages before transfer and display.
  • the ITNS mobile application is loaded onto a mobile phone, but the application could be loaded onto other devices connected to a network including mobile tablets or personal computers.
  • the messaging application operating on the communications device identifies associated devices to which messages may be transmitted.
  • the associated devices may be public devices, for example a television.
  • the associated device also operates a notification system configured to receive and authorise notifications.
  • the ITNS display application is installed on television 130.
  • ITNS display application receives messages from mobile communications device 120 and processes the messages for display on the television.
  • ITNS display application communicates with network server to authorise incoming messages.
  • ITNS display application displays authorised messages on television display in accordance with any rules associated with the display of messages on the television.
  • Figure 1 shows an overview of the architecture and messaging procedure in an example of an ITNS messaging system. The message flows and interactions between the various components are also shown in Figure 2.
  • the ITNS message can originate from various sources depending on the specific use case. Messages may
  • Example 1 Message Generation a Service Provider via ITNS System
  • Communications device 160 is a mobile phone connected to a network. However, device 160 could be any communications device operating an ITNS application and connected to a communications network.
  • the user of device 160 holds an ITNS messaging account with the ITNS System.
  • the user is able to create a message within the ITNS application.
  • the user has a contact list within the ITNS application.
  • the contact list may be stored locally on the device. If stored on the device the contact list may be the user address list generally stored on the user's device or may be a specific ITNS contact list stored within the application.
  • the contact list may be stored locally on the device or stored against the user's account at ITNS server 110. Contacts may be identified by mobile phone number, email address or with a specific address associated with the ITNS
  • the user After creation of the message, the user selects recipients from the contact list. The message is then transmitted to ITNS network server 110 for registration at 210.
  • ITNS network server 110 The components of ITNS network server 110 are illustrated in Figure 5.
  • the network server 110 On receipt of the message at receiver 510, the network server 110 identifies the account holder making the request by retrieving account holder information from account holder database 580. The server registers the message. The message is allocated a message ID by message ID engine 530. The message ID is a unique identifier associated with the message. A copy of the message ID is stored in the database at the network server 110 at authorisation database 590. Identification of the user account is stored with the message ID at
  • authorisation database 590 The user may be identified by ITNS account number.
  • ITNS network server 110 then authorises the message using authorisation engine 540.
  • the ITNS server authorises the transmitting party.
  • the network server confirms that the transmitting party is a registered ITNS account holder.
  • the server may also perform additional checks on the content of the message, for example confirm the notification does not exceed a predefined character count. Such rules are stored in rule database 575.
  • the network server 110 allocates an
  • authorisation token to the message.
  • the authorisation token is associated with the message and the user account.
  • the authorisation token is stored in authorisation
  • the network server For each message the network server stores the account ID, message ID, authorisation token in authorisation database 590. Various other information relating to the message may also be stored, for example a time stamp, formatting, character count etc.
  • the authorisation token and message ID are attached to the message. In some systems they may be incorporated into the message header.
  • the message is then transmitted to the recipients across the communications network.
  • Users are able to configure their accounts with filters and preferences. For example, sending parties may configure the accounts such that messages for particular recipients are formatted in a particular manner. As a recipient, a user may be able to block messages from particular parties.
  • filters and preferences can be managed at the ITNS network server.
  • Embodiments of the ITNS system are configured to integrate with existing messaging systems, for example Apple APNS or Google GCM.
  • the ITNS applications on the devices and the network server are configured to send and receive messages over existing messaging platforms.
  • the messages along with the various message IDs and authorisation tokens are transmitted from the ITNS server to the recipients over the existing messaging platforms at 220.
  • Message is sent to recipient device 120 at 230.
  • the message is processed by the processor of the device 120 on receipt.
  • the message is identified as an ITNS message. If the ITNS application on the device is not activated, processor activates the ITNS application.
  • ITNS application executes authorisation procedures. Upon receipt of the message, the ITNS application retrieves the authorisation token from the message. The application then verifies the authorisation token by contacting ITNS server 110 at 250. The application may send confirmation of the recipients account ID or device ID with the authorisation token. The authorisation token is checked by ITNS server 110 using authentication engine 530. ITNS server matches the incoming authorisation token with the authorisation tokens stored in authorisation database 590. If the authorisation token matches that stored in the ITNS authorisation database 590 the ITNS server validates the token and confirms validation back to the notification application at 255.
  • the application may not require authorisation procedures before displaying the message.
  • the application approves the notification for display on the recipient device and for onward transmission for display at a second device.
  • the ITNS application and associated device are associated with compatible television devices. Once the notification is authorised by ITNS server the application identifies available devices to which to push the message.
  • the device is connected to a local WiFi network 190.
  • the application executes a WiFi discovery search for any devices on the same WiFi network as the mobile device .
  • the device executes a standard WiFi pairing process at 260. Televisions or other devices on the WiFi network may be required to accept pairing requests and may be prompted to accept the pairing request in line with normal WiFi pairing protocol. Any paired devices will be registered with the notification application. If there are multiple television devices paired with the mobile phone the user can be prompted to select a device to receive the message or could select a preference device. Pairing is complete with television 130 at 265.
  • Television 130 is installed with an ITNS application.
  • the ITNS application may be preinstalled or loaded onto the television via a network download or local download.
  • the mobile device transmits the ITNS message 270 to television 130.
  • Television application 135 receives the message from the mobile device 125 at 270.
  • the authorisation token is identified.
  • television 130 has a network connection and connects with the ITNS server 110 to validate the token at 280.
  • the token verification process is performed in the same way as that from the mobile device.
  • the television application 135 may send confirmation of the account holders ID or device ID with the authorisation token.
  • the authorisation token is checked by the ITNS server 110. If the authorisation token matches that stored in the network server ITNS server 110 validates the token and confirms validation back to the television notification application 135 at 285.
  • the television application determines whether to display the message.
  • the television application may have filter rules for whether the message can be displayed.
  • the television may include rules which block notifications between certain predefined time periods. The message is then displayed on the television at 135.
  • acknowledgement signal 290 is sent from the television to the network server.
  • the acknowledgement identifies the message ID for the displayed message.
  • the network server On receipt of the acknowledgement the network server logs that the message has been delivered and displayed. The authorisation token is released.
  • Example 2 Paired Networked Device
  • the IT application is not stored within a television but is stored within a device
  • the ITNS application may be stored within a satellite television box, for example a Sky or Foxtel box, alternatively the ITNS application may be installed within a gaming console, for example an Xbox console or a PlayStation console.
  • the ITNS application may be stored within a content delivery device for example Apple TV, or a content delivery device associated with the mobile phone for example a Google Chromecast.
  • the ITNS application may be installed on a specific ITNS device. In each case, the device is connected to the television and configured to provide content to the television, for example via an HDMI port or other
  • Figure 6 shows the steps taken to display an ITNS message on a television 640 via device 630.
  • Many of the message creation steps and steps taken by the mobile device in this example correspond to those of Figure 2 and the same reference numerals have been used. Reference should be made to the description of Figure 2 for steps 210 to 255.
  • Device 630 and ITNS application 635 loaded onto device 630 are associated with compatible television device 640.
  • the application on the mobile device 125 identifies available devices to which to push the message.
  • the device is connected to a local WiFi network, but the device could identify available devices over BlueTooth or other known communication networks .
  • the application executes a WiFi discovery search for any devices on the same WiFi network as the mobile device.
  • the device executes a standard WiFi pairing process at 660. Devices on the WiFi network may be required to accept pairing requests and may be prompted to accept the pairing request in line with normal WiFi pairing protocol. Any paired devices will be registered with the
  • Paired Device If there are multiple devices paired with the mobile phone the user can be prompted to select a device to receive the message or could select a preference device. Pairing is complete with device 630 at 665. Paired Device
  • Device 630 is installed with ITNS application 635.
  • the ITNS application may be preinstalled or loaded onto device 630 via a network download or local download.
  • the mobile device transmits ITNS message 670 to device 630.
  • Device application 635 receives the message from the mobile device 125 at 670. On receipt of the message the authorisation token is identified. Preferably device 130 has a network connection and connects with the ITNS server 110 to validate the token at 680.
  • the token verification process is performed in the same way as that from the mobile device.
  • the device
  • application 635 may send confirmation of the account holder's ID or device ID with the authorisation token.
  • the authorisation token is checked by the ITNS server 110.
  • the device application determines whether to display the message.
  • the device application may have filter rules for whether the message can be displayed.
  • the television may include rules which block notifications between certain predefined time periods. The message is then pushed to television 640 for display at 690.
  • ITNS device application 635 sends an acknowledgement signal 695 to ITNS messaging system 110.
  • acknowledgement identifies the message ID for the
  • the television transmits a message display confirmation signal to ITNS device application when the ITNS message has been
  • ITNS device application 630 transmits acknowledgement signal 695 to ITNS messaging system 110 on receipt of message display confirmation signal .
  • a message for display on television is created at the mobile device .
  • the ITNS application provides an option for messages to be displayed locally on the paired television.
  • the paired device may be identified as an address within the user's contact list (the fourth example described separately below describes the full message flow for a message for
  • the ITNS app is stored within the television, however, the ITNS application may be installed within a device
  • the message and signalling flows for a message displayed locally are described with reference to Figure 3. This is in contrast to the first and second examples in which an ITNS message is received at the mobile device.
  • the notification may be created by a user action within the application, for example a text notification for display on the television device.
  • the mobile device application can be configured to generate notifications at scheduled predefined time periods, for example reminder notifications or calendar events.
  • the messages originate directly from the application running on the device.
  • ITNS application 125 When a message is created the ITNS application 125 connects to the ITNS server 110. The application sends the message to the ITNS server 110 and requests a message ID and authorisation token at 125. As discussed above ITNS server identifies the account of the application, authorises the account holder and/or device, authorises the message and allocates a message ID and token to the message and sends these to the ITNS application at 315. A copy of the message ID and authorisation token are stored at the ITNS server 110. The message ID and token are transmitted back to the ITNS application 125 at 315.
  • the message ID and token are received at the mobile device they are attached to the message.
  • the message is transmitted to the paired television across the WiFi network at 320.
  • the receive steps, authorisation steps and display steps are executed by the television device in the same way as those discussed above with respect to the push message.
  • the ITNS TV application contacts the ITNS server at 325 for authorisation of the message.
  • ITNS server executes its authorisation checks and validates the message for display at 330.
  • the message is displayed on the television at 335.
  • ITNS TV application acknowledges display to ITNS server at 110 at 340.
  • Example 4 Message Received at Mobile Device with no Message ID
  • a message is received at mobile device 120 via a third party push service 170.
  • the message was not created within an ITNS application and was created without interaction with ITNS server 110. Since the message was not created within an ITNS application in collaboration with the ITNS server the message does not have an associated message ID or an authorisation token.
  • the application contacts ITNS server 110 to obtain an authorisation token and message ID.
  • the application then executes the same process as described above with respect to messages created within the
  • Example 5 Message Created within ITNS Application for Transmission to a third party ITNS Device and Paired Device
  • a subscriber creates a message for distribution to a second subscriber registered to a second communications device. The message is transmitted to the second communications device and is also transmitted to the device paired to the subscriber's device in which the ITNS app is installed. This example facilitates
  • FIG. 4 An ITNS message is created on Mobile Device 1 405 within ITNS Mobile Application 1 410. The subscriber selects contacts to which the message should be sent from within the contact list. Once the message is complete ITNS Mobile Application 1 transmits the ITNS message to ITNS network server 110 at 510. This step may be
  • the ITNS network server checks the subscriber account and creates a message ID and
  • the message ID and authorisation token are transmitted back to the ITNS mobile application 1 at 515.
  • message ID and authorisation token are transmitted into the messaging network 180 at 520.
  • the message is transmitted by the ITNS network server 110.
  • the message may be sent from the mobile device after receiving confirmation of the message ID and authorisation token.
  • the messaging network acknowledges receipt of the message at 520 and transmits the message to the recipient mobile device 2 420 at 530.
  • the message is processed internally within mobile device 2 and provided to the installed ITNS mobile application 2 at 540.
  • ITNS mobile application 2 authorises the message by validating the message ID and authorisation token with ITNS network server 110 at 550. If the token is authorised, confirmation of the validation is
  • Mobile device 2 is paired with television 2 having ITNS TV App 2 430 installed.
  • ITNS Mobile Application 2 sends the message, Message ID and authorisation token to television 2 at 570.
  • the message is forwarded to ITNS TV App 2.
  • ITNS TV Application 2 transmits the authorisation token and message ID to ITNS network server 110 to validate the message. If the message is validated, ITNS network server sends validation confirmation to ITNS TV App 2 at 585. The message is displayed at 590 in accordance with any display rules associated with television 2. ITNS TV App 2 acknowledges display of the message to ITNS Mobile App 2 at 620. The message and signalling flows 510 to 620 control the distribution of the message between ITNS Mobile App 1 and ITNS TV App 2. In addition to transmitting the message to Mobile Device 2 420, the message is transmitted to television 1 paired with Mobile device 1 405. The ITNS message, message ID and authorisation token are sent to television 1 at 700. On receipt of the ITNS message, ITNS IV application 1 validates the token, message ID and message with the ITNS network server 110 at 710. The message is validated at 715 and displayed at 720 in accordance with any display rules associated with
  • the subscriber's paired television displays outgoing messages as well as any incoming messages.
  • ITNS mobile applications can be configured to enable a subscriber to switch off the functionality of pushing outgoing messages to paired televisions. Additionally, specific rules may be loaded within ITNS mobile
  • ITNS applications can be configured to interoperate with third party messaging or content applications to push content to paired devices.
  • Content may be manually selected for movement into the ITNS application for distribution or the content may be automatically pushed into the ITNS application by the third party application.
  • Example third party applications include messaging
  • Content may also be provided from third party sources including internet sites as well as content applications. Content may also be incorporated into ITNS messages from storage devices attached to the device by fixed or
  • a user operating a device having a third party application running on the device or internet access or storage devices and the ITNS application running on the device is able to select content from within a third party application, internet source or storage source for delivery into the ITNS application.
  • the incoming content is treated in the same way as content generated within the ITNS application, described in Example 2 above.
  • the content can be identified as
  • third party applications originating from the third party application, for example including the name or logo of the application or content provider .
  • third party applications websites or storage devices can be configured to push content into ITNS. The content is received within ITNS application. Since the content did not originate from an ITNS
  • ITNS application it will not have a message ID or authorisation token.
  • ITNS application proceeds to obtain an ITNS message ID and authorisation token as discussed above.
  • a user is able to configure his third party account to set automatic filters on content being pushed into ITNS.
  • the ITNS television application operates independently of the input signals for display on the television.
  • the application runs in the background while input signals are displayed on the television display, for example broadcast television, DVD or Blue Ray or any other content stream.
  • the display settings for ITNS messages from the ITNS television application are configured within the display settings of the television.
  • the ITNS message is launched as an overlay over the current TV broadcast or other media input.
  • the application is configured as an overlay and does not impact other displayed media.
  • Display settings for the ITNS message can be configured to select the position that the message is displayed on the television screen. Certain applications may restrict positions for display, for example if certain areas of the screen would obscure service notifications.
  • the ITNS television application is configurable to allow a user to deactivate display.
  • the ITNS application can execute rules to select whether a message should be displayed based on the sending party.
  • the application is
  • the application may also execute rules to select whether to display a message based on timing. For example a user may configure the application not to display ITNS message between a particular time period or during a particular content stream, for example DVD input. Further rules and filters can be applied to determine whether or not to display a message.
  • the display format of the message can also be configured within the ITNS TV application. This may be configured as a user interface template. Different templates may be configured for different recipients or different content. For example, messages from third parties may display differently than messages generated by the paired device. Additionally, the message format can be specified by the sending party as part of the message contents. Again, the ITNS TV application can be configured with rules to manage display format.
  • the authorisation tokens and message IDs created within the ITNS system provide secure and authorised distribution and display procedure. Messages are authorised before display. Messages created within an ITNS application are authorised before transmission. All communications within the ITNS messaging system are sent via secure TLS connections. All ITNS clients will be issued with a unique client identifier that is required for all communication with the Messaging system and any messages sent will be recorded including sender and receiver information.
  • analytic information may also include additional metadata regarding current broadcast / input signal on the TV device on receipt of ITNS messages.
  • the ITNS network server can report on delivery rates and timings since it receives notification at the start of the messaging process and upon completion.
  • the ITNS messaging system to act as a Messaging Bridge to also forward messages to the Twitter network e.g. when containing @ username or # hashtag.
  • ITNS Message and Templates A template controls how the data from the ITNS message is displayed on screen.
  • the ITNS TV application will retrieve templates from the ITNS Message system based on the template id in the ITNS message. This provides users with options about how a message will be displayed on the display.
  • ITNS applications can be configured to predefine or control formatting of incoming messages .
  • a template will consist of HTML, CSS and template
  • the ITNS message format is a simple JSON object with a key of 'itns". Inside there are a few defined keys, i.e.
  • the value of the data key is an object containing keys and values as required by the UI message template.
  • the UI message template determines the schema of the data object; there is no requirement for this schema to be the same across multiple UI message templates.
  • ITNS TV Applications can be configured to display video and audio data in a similar way to text based content.
  • areas of the screen can be designated as video display areas and audio streams can be configured to overlay audio content streams currently being streamed on the television.
  • Television can be configured to display video and audio data in a similar way to text based content.
  • areas of the screen can be designated as video display areas and audio streams can be configured to overlay audio content streams currently being streamed on the television.
  • ITNS creates a new platform to receive notifications or messages, further enhancing the connected home. ITNS creates real time TV watching connectivity with family and friends and enhances your live TV experience while you are at home
  • Embodiments of the invention helps avoid social isolation within the home when using your personal connected device . It also deepens your TV room engagement by encouraging group interaction.
  • ITNS bridges the gap from inside and outside of the home between family, friends and like-minded people when watching your favourite shows / games by creating a real time group interaction / connection whether they are within your home or not.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Multimedia (AREA)
  • Technology Law (AREA)
  • Telephonic Communication Services (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un système de notification comprenant les étapes consistant à générer un message au niveau d'un premier dispositif, le message étant associé à une application fonctionnant sur le dispositif, le message étant destiné à l'affichage sur un second dispositif d'affichage ; à fixer un jeton de sécurité au message ; et à transmettre le message et le jeton de sécurité à un deuxième dispositif en vue de l'affichage sur le dispositif d'affichage.
PCT/AU2016/050479 2015-06-11 2016-06-10 Système de notification WO2016197205A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2016275575A AU2016275575A1 (en) 2015-06-11 2016-06-10 Notification system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
AU2015902350A AU2015902350A0 (en) 2015-06-11 Notification system
AU2015902350 2015-06-11

Publications (1)

Publication Number Publication Date
WO2016197205A1 true WO2016197205A1 (fr) 2016-12-15

Family

ID=57502871

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/AU2016/050479 WO2016197205A1 (fr) 2015-06-11 2016-06-10 Système de notification

Country Status (2)

Country Link
AU (1) AU2016275575A1 (fr)
WO (1) WO2016197205A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030204720A1 (en) * 2002-04-26 2003-10-30 Isadore Schoen Secure instant messaging system using instant messaging group policy certificates
US20070042757A1 (en) * 2005-08-17 2007-02-22 Bo-Sun Jung Apparatus and method for transmitting/receiving notification message in a broadcasting system, and system thereof
US20140195675A1 (en) * 2013-01-09 2014-07-10 Giga Entertainment Media Inc. Simultaneous Content Data Streaming And Interaction System

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030204720A1 (en) * 2002-04-26 2003-10-30 Isadore Schoen Secure instant messaging system using instant messaging group policy certificates
US20070042757A1 (en) * 2005-08-17 2007-02-22 Bo-Sun Jung Apparatus and method for transmitting/receiving notification message in a broadcasting system, and system thereof
US20140195675A1 (en) * 2013-01-09 2014-07-10 Giga Entertainment Media Inc. Simultaneous Content Data Streaming And Interaction System

Also Published As

Publication number Publication date
AU2016275575A1 (en) 2018-02-01

Similar Documents

Publication Publication Date Title
US11902606B2 (en) Methods, systems, and media for presenting notifications indicating recommended content
US11418836B2 (en) Integration of a mobile device into a local service domain
JP7050354B2 (ja) 非同期メッセージシステムにおける単一アカウントに対する複数プロファイルを管理する方法、システムおよびコンピュータ読み取り可能媒体
US20150095933A1 (en) Device Pairing
US9060198B2 (en) Home network component controlling data and function of another home network component
KR20220045962A (ko) 개인 오버레이 피어 투 피어 네트워크를 사용하여 통신하기 위한 인사말 프로토콜 시스템 및 방법
US7907213B1 (en) Wireless multimedia content at television host device
CN112217920A (zh) 通过主机使用客户端接听呼叫
CN101494550A (zh) 融合的多媒体环境中的资源仲裁
CN112738011B (zh) 投屏实现方法、装置及***
CN112738559A (zh) 投屏实现方法、装置及***
KR20190024798A (ko) 디지털 컨텐츠를 전달하기 위한 시스템 및 방법
CN105830391A (zh) 基于存在的内容共享
EP3170310B1 (fr) Système et procédé pour diffuser en continu une vidéo en temps réel d'un dispositif mobile à un boîtier décodeur connecté avec un serveur iptv
EP2770757A1 (fr) Procédé et terminal de traitement d'informations basé sur le système rcs-e
EP3078203B1 (fr) Module de pilotage d'un récepteur de contenus multimédias, serveur et procédés d'élaboration de contenus et de messages associés
WO2016197205A1 (fr) Système de notification
KR101041989B1 (ko) Ｉｐｔｖ에서의 채널 서비스 시스템 및 방법
US11259061B2 (en) Methods, systems, and media for presenting media content items using multiple devices
US10659590B2 (en) Electronic system for indirect intercommunication messaging between electronic terminals
JP2013152555A (ja) 映像表示システム、映像表示端末、サーバー
US20140082049A1 (en) Method for media-data broadcasting between communication network users
CA3008516A1 (fr) Systeme et methode d`envoi multimedia a un televiseur distant
KR20130132184A (ko) 멀티미디어 소비 권한 관리 시스템 및 장치
KR20160026416A (ko) 서비스 시스템 및 디스플레이 디바이스에서 서비스 처리 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16806448

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2016275575

Country of ref document: AU

Date of ref document: 20160610

Kind code of ref document: A

122 Ep: pct application non-entry in european phase

Ref document number: 16806448

Country of ref document: EP

Kind code of ref document: A1