EP3332535A1 - Procédé et système de fourniture de données d'informations - Google Patents

Procédé et système de fourniture de données d'informations

Info

Publication number
EP3332535A1
EP3332535A1 EP16742209.6A EP16742209A EP3332535A1 EP 3332535 A1 EP3332535 A1 EP 3332535A1 EP 16742209 A EP16742209 A EP 16742209A EP 3332535 A1 EP3332535 A1 EP 3332535A1
Authority
EP
European Patent Office
Prior art keywords
notification
terminal
adr
address
gwk
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP16742209.6A
Other languages
German (de)
English (en)
Inventor
Andreas Ziller
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Siemens AG
Original Assignee
Siemens AG
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
Application filed by Siemens AG filed Critical Siemens AG
Publication of EP3332535A1 publication Critical patent/EP3332535A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
    • H04L51/18—Commands or executable codes
    • 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
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • H04W4/21—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel for social networking applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/12—Application layer protocols, e.g. WAP [Wireless Application Protocol]

Definitions

  • the invention relates to a method and a system for providing information data by a notification system for an application of a terminal.
  • Fig. 1 shows a conventional asynchronous notification system which notifies a terminal.
  • At least one application APP is executed on the terminal, for example a portable terminal.
  • the terminal EG transmits via a network a notification registration BREG, with which the terminal EG logs on to the notification system B for receiving notifications B.
  • This notification subscription usually contains a notification address or URL (Uniform Resource Locator) to which the notifications B are to be sent by the notification system BSYS.
  • the notification registration usually contains a notification rule which triggers the sending of a notification B with information data ID in the notification system BSYS when it is fulfilled.
  • a conventional asynchronous notification system BSYS as shown schematically in FIG. 1, is implemented, for example, according to the Sensor Event Service (SES) specification of the Open Geospatial Consortium (OGC).
  • SES Sensor Event Service
  • OAC Open Geospatial Consortium
  • Such asynchronous messaging systems use a web service call to notify the receivers or terminals. This requires a server process can receive connections on a TCP port or receive data on a UDP port.
  • terminals EG which are behind NATs or in mobile networks, can not accept such connections. Even if the network does not object to the provision of a web service, they are not suitable for an asynchronous messaging system because of their operating system.
  • Such terminals EG are, for example, terminals equipped with the operating system IOS. Neither iPhones nor iPads of all generations are able to accept incoming TCP or UDP connections. This is prevented by the implemented on the terminal EG IOS operating system.
  • Apple Push Notification Service is offered by the device manufacturer Apple.
  • This service forwards messages or notifications and third-party applications to Apple terminals.
  • the APNS service may be used by applications APPs operating on an Apple terminal EG equipped with the IOS operating system to enable specific applications that require it make the IOS terminal receive unsolicited notification or informational data. In this manner, the application of the IOS terminal can receive corresponding information data without being requested when a corresponding event occurs.
  • APNS as shown schematically in FIG.
  • the terminal EG initially logs on when it is delivered or forwarding system APNS and receives a notification token BT at system startup.
  • This notification token BT can use the IOS terminal EG when registering with a service provider SP.
  • the web service WS sends a notification B to the proprietary delivery system APNS, as shown in FIG. provides.
  • the notification B contains as notification content information data ID and the notification token BT of the terminal EG, which has received the service provider at registration.
  • the proprietary delivery system APNS compares the notification token BT assigned at system start with the notification token received in the notification B to identify the corresponding terminal EG. Subsequently, the delivery system APNS delivers the notification content or the information data ID to the identified terminal, as shown in FIG.
  • the delivery system APNS as shown in FIG. 2, is proprietary and can not be used by a conventional notification system BSYS, as shown schematically in FIG.
  • This object is achieved by a method having the features specified in claim 1.
  • the invention provides a method for providing information data by a notification system for an application of a terminal, comprising the steps:
  • the received notification registration comprises a notification address for addressing a web service provided by a gateway component and a notification call parameter, which depends on a notification token of the terminal,
  • the derived notification token is transmitted to a delivery system together with the information data or an access address for accessing the information data
  • the method according to the invention offers the advantage that the information data can be reliably provided to the terminal without having to change a conventional notification system or a proprietary delivery system.
  • the method according to the invention can be used by applications or application programs (APPs) on a terminal which requires information data from an asynchronous notification system.
  • APPs application programs
  • the terminal receives a unique notification token from the delivery system after the terminal has registered with the delivery system.
  • the terminal generates the call parameter by applying a predetermined generator function to the received notification token.
  • the notification address is formed by concatenation of an address of the gateway component, a port number of the web service, an address path for calling the web service and the call parameter.
  • the notification sent by the notification system which contains the information data as the notification content, is triggered by an event.
  • the web service of the gateway component addressed by the notification address derives the notification token from the received call parameter by applying an inverse function of the predetermined generator function to the call parameter.
  • the gateway component generates an associated key for a received notification if the data volume of the notification received from the notification system exceeds a permissible maximum data volume, and sets the notification content of the received notification together with the associated notification
  • the gateway component for the notification received from the notification system generates an access address for accessing the information data contained in the notification as notification content if the data extent of the notification received from the notification system exceeds a maximum allowable data size.
  • the gateway component transmits the generated access address for accessing the information data obtained in the received notification, which has the generated key, together with the notification token derived from the notification address to the delivery system, which is based on the notification. the terminal identified and the access address including the key to the application of the identified terminal forwards.
  • the access address for accessing the information data is transmitted through the gateway component
  • Port number of the web service an address path for calling the web service and the key generated for the notification generated.
  • the application of the identified terminal invokes the web service of the gateway component addressed in the access address, which uses the key contained in the access address for referencing to the associated notification content of the notification stored in the local memory of the gateway component.
  • the notification content of the notification referenced by the key is read out from the local memory of the gateway component by the web service and transmitted to the application of the terminal for evaluating the information data which forms the notification content.
  • the gateway component generates the key by means of a cryptographic hash function.
  • the invention further provides, according to a further aspect, an information system having the features specified in claim 14.
  • the invention accordingly provides an information system for the provision of information data by a notification system for at least one application of a communication-limited terminal,
  • notification system is adapted to a
  • Notification which contains as notification content information data to automatically send to a notification address, which comes from a notification registration registration of the terminal at the notification system, which has the notification address for addressing a web service provided by a gateway component and a call parameter, which from a notification token of the terminal depends
  • the web service of the gateway component addressed by the notification address derives the notification token from the received invocation parameter and transmits, together with the information data or an access address for accessing the information data, to a delivery system adapted to identify the terminal based on the received notification token and to forward the information data or the access address for accessing the information data to the application of the identified terminal.
  • the notification system and the gateway component are integrated in a server of a service provider.
  • the delivery system is a proprietary delivery system, in particular an APNS system.
  • the terminal is a communication device with respect to push-limited terminal, in particular an IOS device.
  • the information system provides as information data traffic-related and / or environmental data of a navigation application executed on the communication-limited terminal for route calculation by push operation.
  • the invention provides according to a further aspect
  • Gateway component with the features specified in claim 19.
  • the invention accordingly provides a gateway component for an information system according to the second aspect of the invention, wherein the gateway component receives notification from a notification system of a notification address for addressing a web service provided by the gateway component having a polling parameter that depends on a notification token of a terminal.
  • the addressed web service derives the notification token of the terminal from the invocation parameter and transmits the derived notification token together with the notification content of the received notification or access address for accessing the notification content of the received notification to a delivery system of the terminal.
  • Fig. 1 is a schematic representation of a conventional asynchronous messaging system
  • Fig. 2 is a schematic representation of a conventional
  • FIG. 3 shows a flow chart for illustrating an embodiment of the method according to the invention for providing information data
  • FIG. a schematic representation of a first exemplary embodiment of the method and the information system according to the invention for providing information data
  • a notification system BSYS receives from a terminal EG a notification registration BREG during the registration of the terminal with the notification system BSYS.
  • This notification register BREG has a notification address B-ADR for addressing a web service WS provided by a gateway component and a call parameter AP.
  • the call parameter AP preferably depends on a notification token BT of the terminal EG.
  • the terminal EG receives a unique notification token BT from the relevant delivery system ASYS.
  • An application APP of the terminal EG can then generate from the received notification token BT the call parameter AP and transmit this together with a notification address B-ADR in the notification registration BREG to the notification system BSYS.
  • the notification system BSYS receives the notification registration B-REG from the terminal EG in step S1.
  • the notification registration BREG essentially comprises a specific notification address B-ADR and the call parameter AP.
  • the notification address B-ADR is preferably a network-compliant URL (Uniform Resource Locator).
  • the notification address B-ADR is preferably formed by concatination of an address of the gateway component, a port number of the web services WS, an address path for calling the respective web service WS and the call parameter AP.
  • the address of the gateway component GWK is a host name or an IP address of the gateway component GWK.
  • the port number PN specifies the port on which the relevant web service WS can be reached.
  • the address path for calling the web service WS preferably specifies a path to the respective resources in which the relevant web service WS is mounted.
  • the call parameter AP is preferably generated by the terminal EG by applying a predetermined generator function F to the received notification token BT.
  • the call parameter AP is formed, for example, by a string or a character string, which is generated by the generator function F on the part of the terminal EG.
  • the notification system BSYS sends a notification B to the notification address B-ADR contained in the notification registration BREG.
  • This notification B contains as notification content BI information data ID.
  • the sending of the notification B is preferably triggered by an event.
  • the notification system BSYS receives a value, for example a signal value, which can trigger the transmission of the notification B.
  • the obtained signal value is evaluated according to an evaluation rule AR to check whether the event has occurred.
  • a signal value can be compared with a signal threshold value TH in accordance with a predetermined evaluation rule AR. As soon as the received signal value exceeds the threshold value, the relevant event has occurred and the transmission of the notification B by the notification system BSYS is triggered.
  • the corresponding evaluation rules AR can be stored in a local memory of the notification system BSYS.
  • the evaluation rules AR are configurable.
  • the notification system BSYS receives one or more evaluation rules AR from the application APP of a terminal EG, for example when registering the terminal EG in the respective notification system BSYS.
  • the evaluation rules AR can be changed dynamically or over time by an application APP of a terminal EG.
  • the values or data which are evaluated by the evaluation rules AR can be received by the notification system BSYS from various data sources, in particular sensors.
  • the notification system BSYS uses the notification address used in the notification registration BREG to transmit the notification B. For example, an HTTP POST can be made to this notification address or URL.
  • the gateway component GWK As soon as the gateway component GWK has received the notification B, in step S3 the web service WS of the gateway component GWK addressed in the notification address B-ADR derives the original notification token BT from the call parameter AP contained therein. This is done in one possible embodiment, in that the addressed web service of the gateway component GWK applies an inverse function F "1 to the given generator function F to the received invocation parameter AP.
  • the gateway component GWK is a component or unit which integrates the received notification B into As soon as the notification token BT has been derived from the received call parameter AP by the addressed web service WS, the gateway component transmits the derived notification token BT in step S3 together with the received notification message Information data ID or an access address for accessing this information data to an ASYS delivery system.
  • step S4 of the exemplary embodiment of the method illustrated in FIG. 3 this identifies
  • Delivery system ASYS based on the received from the gateway component GWK notification token UE the relevant terminal EG and forwards the received information ID or the obtained access address Z-ADR to access the information data ID to the application APP of the identified terminal EG on.
  • the application or the application program which is executed on the terminal EG thus receives information data ID from the notification System BSYS via its proprietary delivery system ASYS.
  • This is made possible by the provision of the gateway component GWK between the notification system BSYS and the proprietary delivery system ASYS by implementing a notification format conversion in the gateway component GWK.
  • the gateway component GWK provides an addressable web service WS, which is called by a URL that has previously used the terminal EG in its notification registration BREG.
  • the URL scheme contains a variable part affected by the token or notification token BT. However, this is not required for the call of the web service concerned. Instead, exactly this variable part is passed to the web service WS as the call parameter AP. This is for example through a
  • the length of the notification B or the amount of information data ID contained therein is limited for efficiency reasons to a maximum data size of, for example, a few hundred bytes.
  • notifications B of a conventional notification system BSYS can be significantly longer, in particular if XML is used as the data format.
  • the gateway component GWK for the terminal EG may occur as a cache and provide the actual notification B to a URL address or callback address, as shown schematically in Fig. 5.
  • FIG. 4 schematically shows a first embodiment of the method and system according to the invention for providing information data by a notification system BSYS, in particular by a conventional notification system BSYS, as shown in Fig. 1.
  • the terminal EG registers with a proprietary delivery system or forwarding system ASYS (1) and receives (2) from the delivery system ASYS a token or a notification token BT.
  • This notification token BT is unique and requires identification of the relevant terminal EG.
  • the ASYS delivery system may be a proprietary delivery system, such as an Apple Push Notification Service System, APNS.
  • the terminal EG generates (3) in the illustrated embodiment, a call parameter AP by a predetermined generator function F is applied to the received notification token BT.
  • the terminal EG subsequently registers (4) with a notification system BSYS in its registration process for the future receipt of notifications (B), for example, when certain events occur.
  • the terminal EG transmits a notification registration BREG having a notification address B-ADR and the generated invocation parameter AP.
  • the notification address B-ADR is for addressing a web service WS provided by the gateway component GWK.
  • the notification system BSYS receives the notification registration BREG and stores the received call parameter AP and the notification address B-ADR in a local memory.
  • the notification system BSYS can receive one or more evaluation rules AR from the terminal EG in a possible embodiment variant.
  • the notification system BSYS can check whether received data or values satisfy these rules AR and thus an event EG has occurred which makes it necessary to provide a notification or information data for the relevant terminal EG.
  • the evaluation rules AR can also be preconfigured in the notification system. Once the event has occurred, the notification system BSYS sends (5) at least one notification B to the one stored in the local memory Notification address B-ADR which the notification system has received from the terminal EG during the notification registration BREG. This notification B contains information data ID provided by the notification system BSYS.
  • the gateway component GWK provides a web service WS, which is addressed by the notification address B-ADR and derives from the transferred call parameter AP a notification token BT (6).
  • the gateway component GWK then transmits (7) the derived notification token BT along with the information data ID to the proprietary delivery system ASYS, as shown in FIG.
  • the proprietary delivery system ASYS identifies the terminal EG on the basis of the notification token BT received from the gateway component GWK and forwards (8) the likewise received information data ID to the application APP of the identified terminal EG.
  • the information data ID includes, for example, traffic-related and / or environment-related data for one on the communication-restricted
  • Terminal EG executed navigation application for route calculation via push operation.
  • the delivery system ASYS is, for example, an APNS system. 5 shows a further embodiment of the method according to the invention and of the system according to the invention for providing information data.
  • the terminal EG receives an application (1) in the proprietary delivery system
  • ASYS also a notification token BT (2), from which a call parameter AP is derived (3).
  • the terminal EG registers (4) during a notification registration with a notification system BSYS and transfers a notification address B-ADR and the generated call parameter AP.
  • the notification system BSYS sends a notification B, which includes BI information data ID as the notification content.
  • the notification B also contains the transferred call parameter AP.
  • the notification B is transmitted to the notification address B-ADR as in the embodiment variant shown in FIG. 4, wherein the web service WS addressed in the gateway component GWK derives the original notification token BT from the received call parameter AP (6).
  • the web service WS addressed in the gateway component GWK derives the original notification token BT from the received call parameter AP (6).
  • the gateway component GWK does not forward the information data ID to the proprietary delivery system ASYS in the embodiment variant shown in FIG. 5, but rather an access address or callback address Z-ADR. Furthermore, the gateway component GWK generates a corresponding key for the received notification B, in particular a cryptographic key K, if the data volume of the notification B received from the notification system BSYS exceeds a permissible maximum data volume. Furthermore, the gateway component GWK deposits the notification content BI of the received notification B, ie the information data ID, together with the associated key K for referencing the respective notification content BI in a local memory of the gateway component GWK.
  • the gateway component GWK generates, for the notification B received from the notification system BSYS, an access or callback address Z-ADR for accessing the information data ID contained in the notification B as notification content BI, if the data volume of the information received from the notification system BSYS Notification B exceeds a permitted maximum data volume.
  • the gateway component GWK recognizes on the basis of the transmitted notification content BI or the information data ID that it exceeds a permissible maximum size. In this case, the gateway component GWK now generates a random cryptographic key K, for example by a cryptographic hash function H.
  • This cryptographic key K is used exactly once and is not easily decipherable.
  • the notification B is then sent with the key K was stored as a reference in a local memory of the gateway component GWK.
  • the gateway component GWK can now generate a URL which comprises in the address of the gateway component GWK a port number PN of the relevant web service WS, an address path for calling the web service WS and a character representation of the key K.
  • This character representation can only use characters that can be used in a URL as a string.
  • the gateway component GWK sends (7) instead of the original message, a new message containing this URL together with the notification token BT to the delivery system ASYS of the terminal EG.
  • the gateway component generates, for the notification B received from the notification system BSYS, an access address or call address Z-ADR for accessing the information data ID contained in the notification B as notification content.
  • the gateway component GWK transmits (7) the generated access address Z-ADR for accessing the information data ID obtained in the received notification B including the generated key K to the delivery system together with the notification token BT derived from the notification address B-ADR ASYS.
  • the delivery system ASYS identifies the relevant terminal EG and forwards (8) the obtained access address Z-ADR or callback address including the key K to the application APP of the identified terminal EG, as in FIG. 5 shown.
  • the application APP of the identified terminal EG calls the web service WS of the gateway component GWK addressed in the access address Z-ADR (9).
  • the terminal EG uses the web service URL for a web service call on the gateway component GWK, wherein the web service call contains the cryptographic key K.
  • the gateway component GWK uses the cryptographic key K taken from the web service call for referencing to the corresponding notification content BI stored in the local memory of the gateway component GWK of the original notification B provided by the notification system BSYS.
  • the notification content BI referenced by the key K which comprises the information data ID, is retrieved from the local memory by the called web service WS
  • Gateway component GWK read and transmitted to the application APP of the terminal EG for the evaluation of the information data ID (10), as shown in Fig. 5.
  • the gateway component GWK illustrated in FIGS. 4, 5, which converts the notification B into a suitable notification format, may in one possible embodiment be integrated together with the notification system BSYS in a server of a service provider.
  • the information system according to the invention is integrated in a sensor web system which provides intelligent traffic services.
  • a notification system or a data platform offers traffic and / or environment-related information data ID, wherein drivers using an application APP, in particular a navigation application, this information ID on an IOS device, in particular an iPad or iPhone, use.
  • a navigation application implemented in an IOS terminal may register for obtaining specific information data ID relevant to a current route of a vehicle.
  • the navigation application then receives a notification B or information data ID for certain events in the relevant area and can then change the route guidance.
  • the notification system BSYS of the sensor web system can also send information data ID in push mode to an IOS terminal EG and thus make the route calculation possible.
  • the method according to the invention and the system according to the invention can be used for processes controlled for any event.
  • BSYS such as, for example, OGC SES
  • OGC SES OGC SES
  • ADPS information data ID which is based on IOS terminals EG are running.
  • APNS uses message formats that provide for the use of certificates for identification and authorization.
  • an IOS terminal must provide a secret token to the notifying entity to use for addressing. This is also not provided in the OGC SES specification.
  • the method according to the invention introduces a mechanism which allows forwarding of a token, in particular notification token, by a conventional system, in particular OGC SES system, to a gateway component GWK, so that the actual notification recipient can be addressed.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un procédé et un système de fourniture de données d'informations (ID) par un système de notification (BSYS) à une application (APP) d'un appareil terminal (EG). Ledit procédé comprend les étapes suivantes : la réception (S1), par l'appareil terminal (EG), d'un enregistrement de notification (BREG) par le système de notification (BSYS) lors de l'enregistrement de l'appareil terminal (EG) auprès du système de notification (BSYS), l'enregistrement de notification (BREG) reçu comprenant une adresse de notification (B-ADR) pour l'adressage d'un service Web (WS) fourni par un composant de passerelle (GWK) et un paramètre d'appel (AP) qui dépend d'un jeton de notification (BT) de l'appareil terminal (EG) ; l'émission (S2) d'une notification (B), qui contient en tant que contenu de notification (BI) des données d'informations (ID), par le système de notification (BSYS) à l'adresse de notification (B-ADR) contenue dans l'enregistrement de notification (BREG) ; la déduction (S3) du jeton de notification (BT) par le service Web (WS), du composant de passerelle (GWK), adressé par l'adresse de notification (B-ADR) à partir du paramètre d'appel obtenu (AP), le jeton de notification (BT) déduit étant transmis conjointement avec les données d'informations (ID) ou avec une adresse d'accès (Z-ADR) pour accéder aux données d'informations (ID) à un système de livraison (ASYS) ; l'identification (S4) de l'appareil terminal (EG) par le système de livraison (ASYS) à l'aide du jeton de notification obtenu (BT) et le transfert des données d'informations (ID) ou de l'adresse d'accès (Z-ADR) pour accéder aux données d'informations (ID) par le système de livraison (ASYS) à l'application (APP) de l'appareil terminal identifié (EG).
EP16742209.6A 2015-08-03 2016-07-14 Procédé et système de fourniture de données d'informations Withdrawn EP3332535A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102015214740.1A DE102015214740A1 (de) 2015-08-03 2015-08-03 Verfahren und System zum Bereitstellen von Informationsdaten
PCT/EP2016/066759 WO2017021123A1 (fr) 2015-08-03 2016-07-14 Procédé et système de fourniture de données d'informations

Publications (1)

Publication Number Publication Date
EP3332535A1 true EP3332535A1 (fr) 2018-06-13

Family

ID=56550200

Family Applications (1)

Application Number Title Priority Date Filing Date
EP16742209.6A Withdrawn EP3332535A1 (fr) 2015-08-03 2016-07-14 Procédé et système de fourniture de données d'informations

Country Status (5)

Country Link
US (1) US20180227720A1 (fr)
EP (1) EP3332535A1 (fr)
CN (1) CN107925672A (fr)
DE (1) DE102015214740A1 (fr)
WO (1) WO2017021123A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10693680B2 (en) * 2017-05-17 2020-06-23 Hand Held Products, Inc. Methods and apparatuses for enabling secure communication between mobile devices and a network
CN107222543B (zh) * 2017-06-14 2020-06-05 北京掌上时惠科技有限公司 一种移动APP与Web页面通讯方法及系统

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1278112B1 (fr) * 2001-07-12 2003-05-28 Castify Networks SA Procédé permettant au client d'accéder au serveur fournisseur de contenus sous contrôle d'un serveur localisateur de ressources
US20150088982A1 (en) * 2006-09-25 2015-03-26 Weaved, Inc. Load balanced inter-device messaging
US9137191B2 (en) * 2011-03-17 2015-09-15 Microsoft Technology Licensing, Llc Messaging for notification-based clients
US20130014497A1 (en) * 2011-07-15 2013-01-17 Gm Global Technology Operations Llc. Housing for an internal combustion engine
US20130073607A1 (en) * 2011-09-16 2013-03-21 Andrey Smirnov Registered Users Of An Application
WO2013082501A1 (fr) * 2011-12-02 2013-06-06 Notice Software, Llc Systèmes et procédés pour faciliter une notification de poussée
US9674123B2 (en) * 2012-03-13 2017-06-06 Semotus Inc. System and method for message dispatching and communication
JP6444020B2 (ja) * 2013-08-09 2018-12-26 キヤノン株式会社 情報処理システム、情報処理方法、及びプログラム

Also Published As

Publication number Publication date
US20180227720A1 (en) 2018-08-09
DE102015214740A1 (de) 2017-02-09
CN107925672A (zh) 2018-04-17
WO2017021123A1 (fr) 2017-02-09

Similar Documents

Publication Publication Date Title
DE60026373T2 (de) Vermeidung der identitätsverfälschung in fernmeldesystemen
DE69931344T2 (de) Nachrichtenverarbeitungsverfahren und system in einem telekommunikationssystem
DE102004016580B4 (de) Verfahren zur Übertragung von Daten in einem Ad Hoc Netzwerk oder einem Sensornetzwerk
EP3718265A1 (fr) Dispositif de raccordement pour un échange de données entre un réseau de bus de terrain et un nuage
WO2018077528A1 (fr) Détection de manipulations dans un réseau can par vérification d'identifiants can
WO2004088942A1 (fr) Procede de transmission immediate de messages electroniques a des terminaux de telecommunication
EP3332535A1 (fr) Procédé et système de fourniture de données d'informations
DE10351961A1 (de) Verfahren zum Übertragen von verschlüsselten Nutzdatenobjekten
DE102014000763B4 (de) Kommunikationssystem und Kommunikationsverfahren
EP3304957A1 (fr) Procédé permettant de transmettre des paramètres entre un réseau de télécommunication et un terminal de télécommunication et permettant d'activer et/ou de modifier et/ou de désactiver un profil de communication défini ou désigné par des paramètres sur le terminal de télécommunication, système permettant de transmettre des paramètres, terminal permettant de transmettre des paramètres, programme informatique et produit-programme informatique
EP2030348B1 (fr) Procede de signalisation d'une invitation a etablir une liaison
DE102014206545A1 (de) Verfahren, Kommunikationssystem und Daten-Zugangsknoten zur Übermittlung von Daten
EP2804407B1 (fr) Procédé et système de transfert d'un message d'appel d'urgence textuel au moyen d'un appareil émetteur de télécommunication et un réseau de radiocommunication mobile, système, programme informatique et produit de programme informatique
DE102016215612A1 (de) Verfahren zur Assoziation von Clients
EP3788807B1 (fr) Procédé pour établir un canal de communication entre un dispositif de données et un terminal d'un utilisateur
EP2685682A2 (fr) Procédé et système de messagerie sécurisée
WO2004021663A1 (fr) Procede et dispositif pour identifier des donnees utiles push de façon specifique aux sources de donnees
DE10215567A1 (de) Verfahren zur Übertragung von Daten, insbesondere mit multimedialen Inhalten, in einem Mobilfunknetz
WO2013120569A1 (fr) Transmission de flux de données entre un appareil terminal et un module de sécurité
EP1832132B1 (fr) Systeme et procede permettant la delivrance de donnees entre un fournisseur de donnees et un terminal mobile
EP1901527B1 (fr) Procédé d'exécution d'une communication entre véhicules
EP3005645B1 (fr) Procede pour securiser les donnees de circulation en telecommunication
EP3066812B1 (fr) Procédé de sécurisation de données de trafic de télécommunication
EP1265408A1 (fr) Système et procédé pour la distribution de messages
DE102011116251B4 (de) Nachrichtenübermittlungssystem und Verfahren zum Übertragen einer Nachricht von einem Server zu einem Fahrzeug

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20180124

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 12/06 20090101ALI20190621BHEP

Ipc: H04W 4/60 20180101ALI20190621BHEP

Ipc: H04L 29/06 20060101ALI20190621BHEP

Ipc: H04W 4/20 20180101ALI20190621BHEP

Ipc: H04L 12/58 20060101ALI20190621BHEP

Ipc: H04L 29/08 20060101AFI20190621BHEP

INTG Intention to grant announced

Effective date: 20190723

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20191203