EP1529370B1 - Procede et dispositif pour authentifier un produit de valeur fourni sous forme de message numerique - Google Patents

Procede et dispositif pour authentifier un produit de valeur fourni sous forme de message numerique Download PDF

Info

Publication number
EP1529370B1
EP1529370B1 EP03784222A EP03784222A EP1529370B1 EP 1529370 B1 EP1529370 B1 EP 1529370B1 EP 03784222 A EP03784222 A EP 03784222A EP 03784222 A EP03784222 A EP 03784222A EP 1529370 B1 EP1529370 B1 EP 1529370B1
Authority
EP
European Patent Office
Prior art keywords
message
field
value
digital message
identifier
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.)
Expired - Lifetime
Application number
EP03784222A
Other languages
German (de)
English (en)
Other versions
EP1529370A1 (fr
Inventor
Ari Pakarinen
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.)
Plusdial Oy AB
Original Assignee
Plusdial Oy AB
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
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=8564428&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=EP1529370(B1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Plusdial Oy AB filed Critical Plusdial Oy AB
Publication of EP1529370A1 publication Critical patent/EP1529370A1/fr
Application granted granted Critical
Publication of EP1529370B1 publication Critical patent/EP1529370B1/fr
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07B—TICKET-ISSUING APPARATUS; FARE-REGISTERING APPARATUS; FRANKING APPARATUS
    • G07B15/00—Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points
    • G07B15/02—Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points taking into account a variable factor such as distance or time, e.g. for passenger transport, parking systems or car rental systems

Definitions

  • the invention concerns generally the technology of electronically delivering relatively short and compact messages that represent a commodity of value. Especially the invention concerns the problem of how to ensure that such a message, when presented for inspection, is an authentic one and not an illegal copy.
  • SMS messages Short Message Service
  • MMS messages Multimedia Message Service
  • similar compact, well-defined messaging formats is rapidly gaining popularity.
  • SMSC Short Message Service Center
  • a ticket application server 105 is arranged to have a communication connection with the SMSC.
  • Conveying an order message from the mobile telephone 101 through the base transceiver station 102 and the SMSC 104 to the ticket application server 105 is schematically represented in fig. 1 as a series of steps 1, 2 and 3. After having received the order message the ticket application server 105 generates an electronic ticket and sends it back to the mobile telephone that ordered it. Conveying a ticket back to the mobile telephone 101 is shown as steps 4, 5 and 6.
  • Charging for the electronically delivered ticket is most straightforwardly accomplished by adding a certain fixed price to the telephone bill of the user of the mobile telephone 101.
  • the price for just sending another SMS message is typically considerably lower than the ticket price that was charged of the original recipient of the ticket message.
  • a temptation quickly arises to cheat the system by ordering a single ticket for one of a group of persons and distributing copies of the original ticket as ordinary SMS messages to the other members of the group.
  • the reliability of checking the sender is undermined by certain mobile telephone models having a feature that was originally introduced in good faith in order to enhance user-friendliness.
  • the user of the mobile telephone can use a freely selectable alphanumeric string as the identifier of an entry in the directory of stored names and numbers.
  • said certain mobile telephone models check the sender's number from a received SMS message, and if the number matches that of a named entry in the directory, they only display the "name" or identifier of that entry as the sender of the message.
  • a reference publication GB 2 361 570 is known to describe a general-purpose electronic ticket delivery system, in which the ticket is delivered as an SMS message or in a browser-readable format.
  • the SMS solution discussed in said publication is especially prone to the fraud scheme described earlier.
  • WO 96/06508 presents a general-purpose method for reliably identifying the originator of an SMS message.
  • the drawback of this scheme is that it requires modifications to the standardised basic operation of conveying SMS messages, because it involves using at least two different addresses in calling a Short Message Services Centre.
  • the objectives of the invention are achieved by adding a time-dependent extension to the telephone number that the message transmission system includes into the message as the number of the sender.
  • a method according to the invention has the characteristic features that are recited in the independent patent claim directed to a method.
  • the invention is based on the insight that cheating in the way described above is only possible if the telephone number of the ticket application server is constant, so that the potential cheater can store it beforehand into his mobile telephone (or corresponding mobile telecommunication device) as an identifier of his accomplice. Every time when the telephone number of the ticket application server changes, the cheater must reprogram his mobile telephone. By making the telephone number of the ticket application server to change very often it is possible to make it difficult or impossible for the cheater to follow. Depending on the number and nature of possible other network-generated field values in a message it may be possible to apply a similar authentication strategy also to other field values than just the sender's telephone number.
  • the scheme utilizes certain spare character locations that have been defined to constitute a part of a field in a transmitted message but are not necessarily needed for the transmission of information when the invention is not applied.
  • the changing values are somehow related to another network-generated value in a well-defined field of the message, so that the message becomes self-sustaining regarding verification: for someone who knows the rules according to which the changing values behave, it suffices to compare the contents of the changing-value field to some other field in the message to see whether the message has been appropriately generated and delivered.
  • the most straightforward candidate for the changing-value field is the field for the sender's telephone number. Typically it comprises relatively many character locations, to reckon with exceptionally long telephone numbers used in certain systems. If the telephone number assigned to a ticket application server is not as long as the maximum length of the sender's number field, the spare character locations can be used to insert a repeatedly changing extension.
  • a simple and workable rule for generating repeatedly changing extensions, that also correlate with the value of another field in the same message, is to utilize as an extension a part of or a derivative from the time value that is inserted into the message as transmission time.
  • Fig. 2 illustrates schematically a message 201, which we may designate as a multimedia message for the sake of generality.
  • a message 201 which we may designate as a multimedia message for the sake of generality.
  • a further feature of the message 201, which is also important to the present invention, is that its standardized composition defines a network-generated part 202 in addition to a user-defined part 203.
  • the network-defined part 202 consists of the parameter values that a network (typically an SMSC) adds to the message, while the user-defined part 203 consists of the (originally maximum of 160) payload characters that a user or a message-generating computer program at a content provider's server puts in.
  • a network typically an SMSC
  • the user-defined part 203 consists of the (originally maximum of 160) payload characters that a user or a message-generating computer program at a content provider's server puts in.
  • the network-generated part 202 typically comprises fields, of which fields 204 and 205 are shown in fig. 2 , into which the network inserts certain values.
  • fields 204 and 205 are shown in fig. 2 , into which the network inserts certain values.
  • At least one of these fields has a certain maximum length that has been selected to accommodate the longest possible values that can be inserted into that field, with some marginal so that typically the whole length of the field is not needed.
  • field 204 is a field for the sender's telephone number. Telephone numbers of various lengths appear in different telephone systems around the world, so the length of the sender's number field 204 must have been selected to accommodate also relatively long telephone numbers.
  • a telephone number that identifies a ticket application server (or other instance that is to generate messages that represent a commodity of value) is shorter than the maximum length of the field 204, so after said telephone number has been inserted as a field value 206, spare space 207 remains in the field 204.
  • spare space 207 corresponds to three alphanumeric characters.
  • field 205 also appears in the network-generated part 202 of the message 201.
  • field 205 is the transmission time field, into which the SMSC should insert a value 208 that represents the moment of time at which the message was originally sent by its sender.
  • the spare space 207 of the sender number field 204 is used to carry a code, the value of which has a certain relationship to the transmission time value 208 in the appropriate field 205.
  • a code the value of which has a certain relationship to the transmission time value 208 in the appropriate field 205.
  • an easy option would be to insert a certain fixed character into the spare space 207, followed (or preceded) by a two-digit number that matches the minute count, i.e. the two-digit number that represents minutes, in the transmission time value 208.
  • Another option would be to select said two digits to match the second count in the transmission time value 208.
  • a third option would be to use two digits of the spare space 207 to match the minute count and a third digit to match the number that represents tens of seconds in the transmission time value 208. It is not important to the invention, what is the exact way of mapping the transmission time value into a code value in the spare space 207; the following considerations should anyway be taken into account:
  • the message may naturally include also other parts and other fields than just those shown in fig. 2 . If there is not enough spare space in one previously determined field and/or if it is considered advantageous for increasing security, code values can also be distributed into more than one field. It is likewise possible to make a single code value depend on more than one other value in more than one other field. In the process of defining a completely new message format it would naturally be possible to define a dedicated code value field for the insertion of a code value; however it is a major advantage of the present invention that the code value is "smuggled" in a previously defined field, moreover so that every ordinary mobile terminal will handle and display the code value in an exactly similar way with absolutely no additional definitions for message handling. The mobile terminals are not even aware of there being any code values involved: they will just handle and display the code value of the present invention as a part of the value that belongs to the appropriate field, which is field 204 in fig. 2 .
  • Fig. 3a illustrates a process of exchanging messages in a system that comprises a mobile terminal, an SMSC that implements the so-called CIMD protocol (Computer Interface to Message Distribution), a messaging gateway and a ticket application.
  • the terminal At step 301 the terminal generates a ticket ordering message as a response of a user telling the terminal to do so.
  • the terminal transmits the message, and at step 303 the SMSC receives it. Forwarding the message further towards the ticket application may involve certain processing 304 at the SMSC, after which a further transmit/receive step 305 and 306 takes place between the SMSC and the messaging gateway.
  • CIMD protocol Computer Interface to Message Distribution
  • the latter inspects the incoming message at step 307 enough to find out that it is a ticket ordering message, and passes it further to the ticket application in steps 308 and 309.
  • the ticket application generates the ordered ticket message at step 310. Up to this point the operation proceeds exactly like in known prior art electronic ticketing applications.
  • the ticket application At step 311 the ticket application generates an authentication code that is to be added to the ticket message generated at the previous step. Certain more detailed ways of generating the code will be described later.
  • the ticket application transmits the completed ticket message to the messaging gateway, which receives it at step 313 and selects, by using appropriate known methods, the SMSC through which the ticket message should be delivered to the terminal that ordered it.
  • a feature of the CIMD protocol is that the SMSC does not need to receive a sender's telephone number from the application that generated a message or the gateway that forwarded it to the SMSC: the SMSC has been configured to otherwise know a sender's telephone number that it adds to the message as a part of the process of sending the message towards the terminal. It is possible to provide a sender's telephone number to the SMSC according to CIMD, but the SMSC will still use the configured number and only add the number that came from the application server into the sender's number field after the configured number.
  • the messaging gateway - In order not to have the same sender's number repeated twice in the message, the messaging gateway - after having recognized the appropriate SMSC as one that implements CIMD - strips off the actual telephone number value from the message at step 315 before sending the message to the SMSC at step 316.
  • the SMSC receives the message at step 317 and executes its conventional processing at step 318: as a part of the last-mentioned it takes the code value that remained in the sender's number field after step 315 and appends it to the end of the sender's number field of the final message.
  • Steps 319 and 320 represent transmitting the ticket message from the SMSC to the mobile terminal in a known way.
  • Fig. 3b is otherwise the same as fig. 3a , but now we assume that the SMSC implements the so-called Content Gateway interface towards message-generating applications in the network.
  • An important difference to CIMD arrangements is that according to the Content Gateway specifications, the SMSC will not use any configured numbers but will accept and use any sender's number that came with the messsage from an application server. Steps 301 to 314 take place exactly in the same way as in fig. 3a . However, after noticing now at step 314 that the SMSC implements Content Gateway rather than CIMD, the messaging gateway now preserves at step 315' the contents of the sender's number field as they were in the message that came from the ticket application.
  • Step 318' proceeds in the SMSC according to the Content Gateway specifications, so the SMSC reads the whole contents of the sender's number from the message it received from the messaging gateway at step 317 and reuses it as such in the message it transmits to the mobile terminal at step 319.
  • Fig. 4 illustrates the operation of a ticket-generating application according to an embodiment of the invention.
  • the application receives a ticket order message from an SMSC, typically through a messaging gateway.
  • the application extracts the sender's telephone number or corresponding sender identification from the order message and stores it for later use as an identifier of the intended recipient of a generated ticket message.
  • the application generates the actual ticket message according to some preprogrammed instructions that describe how a ticket message should look like and what should it contain.
  • the application inserts the sender identification extracted at step 402 into the message as an identifier of the intended recipient.
  • the application takes its own telephone number or corresponding identifier and inserts it into an appropriate sender identification field in the ticket message as a prefix of a complete identifier value.
  • the process has executed itself similarly as in prior art electronic ticketing applications.
  • the application reads a code value and inserts it into the sender identification field in the ticket message as a suffix that complements the prefix inserted at step 405 to constitute a complete identifier value.
  • the code value is simply some part of the number string that indicates current time, possibly altered with a fixed offset
  • an advantageous way of executing step 406 is to read current time from a local clock, extract the appropriate numbers from the time value read, refer to a database for finding the currently valid offset value, perform the summing (or other calculational) operation between the extracted numbers and the offset, and write the result into the ticket message under construction.
  • the database may also include a look-up table prepared beforehand, from which the application finds directly a modified code value by using the local time reading as a key.
  • step 407 the application reads once more (if necessary) the local time value and inserts it into an appropriate field in the ticket message as an indicator of original message transmission time.
  • step 408 the application transmits the completed ticket message towards an SMSC, typically through a message gateway. Steps 407 and 408 are again similar to corresponding steps known from prior art.
  • Fig. 5 illustrates the operation of a message gateway functionality according to an embodiment of the invention when it conveys a completed ticket message from a ticket-generating application towards an SMSC.
  • the message gateway receives a ticket message from the application, and at step 502 it selects the appropriate SMSC according to certain rules.
  • the identity of the SMSC can be derived from the subscribers IMSI (International Mobile Subscription Identifier), fo typically the message gateway reads the recipient identifier at step 502 and uses some simple logic to select the appropriate SMSC.
  • Steps 501 and 502 take place according to practices known from prior art.
  • the message gateway checks, whether the selected SMSC runs CIMD or not. To be more general, we may say that at step 503 message gateway checks, whether the selected SMSC runs a messaging protocol that will only use a possibly transmitted sender's telephone number as a suffix to a preconfigured sender identifier (as in CIMD) or whether the selected SMSC runs a messaging protocol under which it is possible to send a complete sender identifier to the SMSC together with the message.
  • a positive finding at step 503, which means that CIMD or a corresponding protocol is in use, causes a transition to step 504 at which the message gateway deletes the prefix part from the sender identifier that the application has inserted.
  • the message gateway need certain unambiguous preprogrammed instructions of how to decide the number of characters to be deleted; assuming our example of always having three characters in the suffix an unambiguous instruction may be as simple as to delete all but the three last characters in a sender identifier string.
  • Step 505 is a straightforward transmitting step at which the ticket message is transmitted towards the appropriately selected SMSC.
  • Fig. 6 is a general block diagram of a system 601 according to an embodiment of the invention, in which the message gateway functionality 602 has been integrated into a single system with the ticket-generating application 603.
  • a database 604 which can be used for various purposes. Closest of these to the present invention is the use of the database 604 as a storage of the currently valid code value.
  • the system includes a web interface 605 through which it is possible to examine and change certain configuration information stored in the database 604. There may also be direct connections for exchanging information between the web interface 605 on one hand and the message gateway functionality 602 and the ticket-generating application 603 on the other hand.
  • the database 604 there is a collection of scripts 606, some of which may have been configured to execute automatically at the fulfilment of certain criteria while others must be manually triggered through the web interface 605.
  • Illustrating all functionalities of fig. 6 in an exemplary way as existing within a single system 601 does not exclude other possible implementations. Parts of the system may be implemented even very far from each other, physically in clearly separate systems, as long as the communication connections between the different functionalities are realised appropriately. For example, it is relatively common that a message gateway functionality exists as a standalone system that serves to selectively connect a number of SMSCs with a number of application servers that run a wide variation of different service applications that utilize messaging.
  • tickets in the sense of admission tickets or travel tickets.
  • the concept of a "ticket” must be understood widely to cover all such instants where a user must or may have at his possession some commodity of value, which ultimately is just a piece of information that proves that the user has committed a certain transaction in a prescribed manner.
  • the code value is derived from the transmission time of the ticket message and inserted into the sender identification (sender's telephone number) field, while the transmission time is inserted into the well-defined transmission time field of the same message.

Landscapes

  • Business, Economics & Management (AREA)
  • Finance (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Storage Device Security (AREA)
  • Debugging And Monitoring (AREA)
  • Communication Control (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Circuits Of Receivers In General (AREA)

Claims (11)

  1. Procédé d'authentification d'un produit de valeur délivré à partir d'un réseau fermé sous la forme d'un message numérique (201) vers un terminal mobile, lequel message numérique (201) a un format prédéfini qui comprend des champs (204, 205) pour des valeurs générées par le réseau (206, 208), caractérisé en ce que le procédé comprend des étapes consistant à :
    - générer (311, 406) une combinaison de code selon une règle de dépendance au temps, de telle sorte que la combinaison de code générée dépend du moment où le message numérique sera transmis,
    - insérer (311, 406) la combinaison de code générée dans un certain premier champ (204) dans le message numérique, lequel premier champ a un rôle prédéfini qui est autre que le transport des combinaisons de code, et
    - insérer (407) une valeur qui représente une heure de transmission du message dans un second champ (205) dans le message numérique.
  2. Procédé selon la revendication 1, caractérisé en ce que l'étape d'insertion (311, 406) de la combinaison de code générée dans un certain premier champ (204) dans le message numérique comprend les étapes auxiliaires consistant à :
    - insérer (405) dans ledit premier champ (204) un identifiant (206) d'un service permettant de générer et de délivrer des produits de valeur, lequel identifiant (206) est plus petit en taille qu'un espace total disponible dans ledit premier champ (204), et
    - insérer en plus (311, 406) la combinaison de code générée dans ledit premier champ (204) sous la forme d'un suffixe audit identifiant (206).
  3. Procédé selon la revendication 2, caractérisé en ce qu'il comprend en plus les étapes consistant à :
    a) trouver (502, 503) si le message numérique doit être acheminé selon un premier protocole de communication qui impliquera l'utilisation d'un identifiant par défaut préconfiguré dans un champ d'identifiant du message numérique et ajouter des identifiants existant potentiellement contenus dans le message après ledit identifiant par défaut préconfiguré et
    b) dans le cas d'une découverte positive pendant l'étape a), suppression (504), dans ledit message numérique, dudit identifiant d'un service permettant de générer et de délivrer des produits de valeur, avant d'acheminer ledit message numérique selon ledit premier protocole.
  4. Procédé selon la revendication 1, caractérisé en ce que l'étape de génération (311, 406) d'une combinaison de code selon une règle de dépendance au temps comprend les étapes auxiliaires consistant à :
    - obtenir une chaîne de chiffres qui représente une heure de transmission du message numérique et
    - prendre un sous-ensemble de chiffres dans ladite chaîne de chiffres comme combinaison de code.
  5. Procédé selon la revendication 4, caractérisé en ce que l'étape consistant à prendre un sous-ensemble de chiffres dans ladite chaîne de chiffres comme combinaison de code implique la prise d'une paire de chiffres qui représentent un compte de minute.
  6. Procédé selon la revendication 4, caractérisé en ce que l'étape consistant à prendre un sous-ensemble de chiffres dans ladite chaîne de chiffres comme combinaison de code implique la prise d'une paire de chiffres qui représentent un compte de seconde.
  7. Procédé selon la revendication 1, caractérisé en ce que l'étape de génération (311, 406) d'une combinaison de code selon une règle de dépendance au temps comprend les étapes auxiliaires consistant à :
    - obtenir une chaîne de chiffres qui représente une heure de transmission du message numérique,
    - la prise d'un sous-ensemble de chiffres dans ladite chaîne de chiffres et
    - l'addition d'une valeur décalée prédéfinie par rapport au nombre représenté par ledit sous-ensemble de chiffres pour obtenir la combinaison de code.
  8. Agencement (601) destiné à générer et à délivrer des produits de valeur authentifiés qui doivent être délivrés à partir d'un réseau fermé sous la forme de messages numériques vers des terminaux mobiles, lesquels messages numériques ont un format prédéfini (201) qui comprend des champs (204, 205) pour des valeurs générées par le réseau (206, 208), caractérisé en ce que l'agencement comprend :
    - les moyens (603, 604) destinés à générer une combinaison de code selon une règle de dépendance au temps, de telle sorte qu'une combinaison de code générée est agencée pour dépendre du moment où un message numérique doit être transmis,
    - un moyen (603) pour insérer une combinaison de code générée dans un certain premier champ dans un message numérique qui sera transmis, lequel premier champ a un rôle prédéfini qui est autre que de transporter des combinaisons de code, et
    - un moyen (603) destiné à insérer une valeur qui représente une heure de transmission de message dans un second champ dans un message numérique qui sera transmis.
  9. Agencement selon la revendication 8, caractérisé en ce qu'il comprend :
    - une application génératrice de produits (603) destinée à générer des produits de valeur et
    - couplée à ladite application génératrice du produit (603), une fonctionnalité de passerelle de message (602) permettant de délivrer des produits de valeur générés sous la forme de messages numériques à des centres de messagerie pour une délivrance ultérieure.
  10. Agencement selon la revendication 9, caractérisé en ce que ladite application génératrice du produit (603) est agencée pour insérer dans un premier champ dans les messages numériques générés un identifiant d'un service permettant de générer et de délivrer des produits de valeur, lequel identifiant est plus petit en taille qu'un espace total disponible dans ledit premier champ, et pour insérer de plus une combinaison de code générée par ledit premier champ sous la forme d'un suffixe audit identifiant.
  11. Agencement selon la revendication 10, caractérisé en ce que ladite fonctionnalité de passerelle de message (602) est agencée afin de :
    - trouver si un message numérique qui doit être délivré à un certain centre de messagerie doit être acheminé selon un premier protocole de communication qui impliquera l'utilisation d'un identifiant par défaut préconfiguré dans un champ d'identifiant du message numérique et ajouter des identifiants existant potentiellement contenus dans le message après ledit identifiant par défaut préconfiguré, et
    - supprimer une partie du contenu d'un champ d'identifiant dans les messages numériques qui seront acheminés selon ledit premier protocole avant de délivrer ces messages numériques aux centres de messagerie.
EP03784222A 2002-08-12 2003-08-11 Procede et dispositif pour authentifier un produit de valeur fourni sous forme de message numerique Expired - Lifetime EP1529370B1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
FI20021467 2002-08-12
FI20021467A FI114425B (fi) 2002-08-12 2002-08-12 Menetelmä ja järjestely digitaalisena viestinä jaettavan rahanarvoisen hyödykkeen aitouden todentamiseksi
PCT/FI2003/000597 WO2004015917A1 (fr) 2002-08-12 2003-08-11 Procede et dispositif pour authentifier un produit de valeur fourni sous forme de message numerique

Publications (2)

Publication Number Publication Date
EP1529370A1 EP1529370A1 (fr) 2005-05-11
EP1529370B1 true EP1529370B1 (fr) 2009-01-07

Family

ID=8564428

Family Applications (1)

Application Number Title Priority Date Filing Date
EP03784222A Expired - Lifetime EP1529370B1 (fr) 2002-08-12 2003-08-11 Procede et dispositif pour authentifier un produit de valeur fourni sous forme de message numerique

Country Status (12)

Country Link
EP (1) EP1529370B1 (fr)
CN (1) CN100542087C (fr)
AT (1) ATE420503T1 (fr)
AU (1) AU2003249134B2 (fr)
CA (1) CA2495515C (fr)
DE (1) DE60325735D1 (fr)
DK (1) DK1529370T3 (fr)
EA (1) EA200500975A1 (fr)
ES (1) ES2320877T3 (fr)
FI (1) FI114425B (fr)
PT (1) PT1529370E (fr)
WO (1) WO2004015917A1 (fr)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20040090620A (ko) * 2003-04-18 2004-10-26 삼성전자주식회사 무선 이동 통신망을 이용한 경주 계좌투표 구매 시스템 및그 방법
US8111694B2 (en) 2005-03-23 2012-02-07 Nokia Corporation Implicit signaling for split-toi for service guide
US8520703B2 (en) 2005-04-05 2013-08-27 Nokia Corporation Enhanced electronic service guide container
US8607271B2 (en) 2005-08-26 2013-12-10 Nokia Corporation Method to deliver messaging templates in digital broadcast service guide
US8316132B2 (en) 2005-09-08 2012-11-20 Nokia Corporation Method to determine the completeness of a service guide
US8320819B2 (en) 2005-11-01 2012-11-27 Nokia Corporation Mobile TV channel and service access filtering
US8763036B2 (en) 2005-11-04 2014-06-24 Nokia Corporation Method for indicating service types in the service guide
CN100411456C (zh) * 2006-04-12 2008-08-13 华为技术有限公司 预定义短消息业务的实现方法
CN102164037B (zh) * 2011-03-31 2014-04-30 飞天诚信科技股份有限公司 一种数字签章系统和方法
US9881260B2 (en) 2012-10-03 2018-01-30 Moovel North America, Llc Mobile ticketing
CN103994810B (zh) * 2014-05-29 2016-05-25 广州市中兴电子衡器厂 一种防作弊电子秤及防作弊方法
US9792604B2 (en) 2014-12-19 2017-10-17 moovel North Americ, LLC Method and system for dynamically interactive visually validated mobile ticketing

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI96374C (fi) * 1994-08-10 1996-06-10 Radiolinja Ab Menetelmä lyhytsanoman lähettäjäluokan määrittämiseksi digitaalisessa matkapuhelinverkossa
GB0009599D0 (en) * 2000-04-18 2000-06-07 British Airways Plc A method of operating a ticketing system
NL1016853C2 (nl) * 2000-12-12 2002-06-13 Koninkl Kpn Nv Methode voor de afname van diensten en de controle daarop, gebruikmakend van een mobiele terminal.

Also Published As

Publication number Publication date
DE60325735D1 (de) 2009-02-26
FI20021467A (fi) 2004-02-13
EA200500975A1 (ru) 2005-12-29
PT1529370E (pt) 2009-04-09
FI20021467A0 (fi) 2002-08-12
ATE420503T1 (de) 2009-01-15
ES2320877T3 (es) 2009-05-29
CN1689270A (zh) 2005-10-26
FI114425B (fi) 2004-10-15
WO2004015917A1 (fr) 2004-02-19
CA2495515C (fr) 2010-06-08
CA2495515A1 (fr) 2004-02-19
EP1529370A1 (fr) 2005-05-11
CN100542087C (zh) 2009-09-16
DK1529370T3 (da) 2009-03-09
AU2003249134A1 (en) 2004-02-25
AU2003249134B2 (en) 2008-04-17

Similar Documents

Publication Publication Date Title
US7240199B2 (en) System and method for verifying delivery and integrity of electronic messages
US7886008B2 (en) System and method for verifying delivery and integrity of electronic messages
US7865557B2 (en) System and method for verifying delivery and integrity of electronic messages
US7707624B2 (en) System for, and method of, proving the transmission, receipt and content of a reply to an electronic message
US8549301B2 (en) Method and computer system for ensuring authenticity of an electronic transaction
US8050694B2 (en) Method and system for extending the use and/or application of messaging systems
US20070168432A1 (en) Use of service identifiers to authenticate the originator of an electronic message
US20120278417A1 (en) System and method for verifying delivery and integrity of electronic messages
US20050021963A1 (en) System for, and method of, proving the transmission, receipt and content of a reply to an electronic message
EP1529370B1 (fr) Procede et dispositif pour authentifier un produit de valeur fourni sous forme de message numerique
US7917943B1 (en) E-mail Stamping with accredited entity name
EP2461297B1 (fr) Dispositif et procédé de distribution de numéros d'identification personnels
CA2547480C (fr) Systeme et procede permettant de verifier le bon acheminement et l'integrite de messages electroniques
CN106331354B (zh) 一种短信信息提取与分析方法
CN104160664A (zh) 用于发送至移动终端的数据消息传输的验证的方法
GB2380897A (en) Sending email to mobile phone as text message
US20040001455A1 (en) Method and system for identification of digitally signed messages in a telecommunication system
CN109670763B (zh) 一种数据处理方法及系统、终端和服务器
KR20190009239A (ko) 쌍방 인증을 통한 배달 증명 서비스를 제공하는 전자문서 전송 시스템
JP2005537572A (ja) 検証可能な配送支払コーディングの提供

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: 20050225

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL LT LV MK

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

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: CH

Ref legal event code: NV

Representative=s name: HEPP WENGER RYFFEL AG

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 60325735

Country of ref document: DE

Date of ref document: 20090226

Kind code of ref document: P

REG Reference to a national code

Ref country code: DK

Ref legal event code: T3

REG Reference to a national code

Ref country code: SE

Ref legal event code: TRGR

REG Reference to a national code

Ref country code: PT

Ref legal event code: SC4A

Free format text: AVAILABILITY OF NATIONAL TRANSLATION

Effective date: 20090331

REG Reference to a national code

Ref country code: GR

Ref legal event code: EP

Ref document number: 20090400701

Country of ref document: GR

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090107

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2320877

Country of ref document: ES

Kind code of ref document: T3

REG Reference to a national code

Ref country code: HU

Ref legal event code: AG4A

Ref document number: E005424

Country of ref document: HU

PLBI Opposition filed

Free format text: ORIGINAL CODE: 0009260

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090107

PLAX Notice of opposition and request to file observation + time limit sent

Free format text: ORIGINAL CODE: EPIDOSNOBS2

26 Opposition filed

Opponent name: INA FINLAND OY

Effective date: 20091006

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090107

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090107

NLR1 Nl: opposition has been filed with the epo

Opponent name: INA FINLAND OY

PLBB Reply of patent proprietor to notice(s) of opposition received

Free format text: ORIGINAL CODE: EPIDOSNOBS3

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20090831

PLCK Communication despatched that opposition was rejected

Free format text: ORIGINAL CODE: EPIDOSNREJ1

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20090811

APAH Appeal reference modified

Free format text: ORIGINAL CODE: EPIDOSCREFNO

APBM Appeal reference recorded

Free format text: ORIGINAL CODE: EPIDOSNREFNO

APBP Date of receipt of notice of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA2O

APBQ Date of receipt of statement of grounds of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA3O

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090107

PLAB Opposition data, opponent's data or that of the opponent's representative modified

Free format text: ORIGINAL CODE: 0009299OPPO

R26 Opposition filed (corrected)

Opponent name: INA FINLAND OY

Effective date: 20091006

PLAB Opposition data, opponent's data or that of the opponent's representative modified

Free format text: ORIGINAL CODE: 0009299OPPO

R26 Opposition filed (corrected)

Opponent name: INA FINLAND OY

Effective date: 20091006

APBU Appeal procedure closed

Free format text: ORIGINAL CODE: EPIDOSNNOA9O

PLBN Opposition rejected

Free format text: ORIGINAL CODE: 0009273

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

Free format text: STATUS: OPPOSITION REJECTED

27O Opposition rejected

Effective date: 20140409

REG Reference to a national code

Ref country code: DE

Ref legal event code: R100

Ref document number: 60325735

Country of ref document: DE

Effective date: 20140409

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 14

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 15

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 16

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: TR

Payment date: 20190724

Year of fee payment: 17

Ref country code: DK

Payment date: 20190725

Year of fee payment: 17

Ref country code: CZ

Payment date: 20190718

Year of fee payment: 17

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: HU

Payment date: 20190717

Year of fee payment: 17

Ref country code: GR

Payment date: 20190716

Year of fee payment: 17

Ref country code: BG

Payment date: 20190716

Year of fee payment: 17

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: AT

Payment date: 20190722

Year of fee payment: 17

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: CH

Payment date: 20190821

Year of fee payment: 17

REG Reference to a national code

Ref country code: DK

Ref legal event code: EBP

Effective date: 20200831

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: AT

Ref legal event code: MM01

Ref document number: 420503

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200811

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200831

Ref country code: CZ

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200811

Ref country code: GR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210304

Ref country code: HU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200812

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200811

Ref country code: BG

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210228

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200831

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20210715

Year of fee payment: 19

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FI

Payment date: 20210721

Year of fee payment: 19

Ref country code: FR

Payment date: 20210831

Year of fee payment: 19

Ref country code: IE

Payment date: 20210719

Year of fee payment: 19

Ref country code: IT

Payment date: 20210816

Year of fee payment: 19

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: SE

Payment date: 20210817

Year of fee payment: 19

Ref country code: BE

Payment date: 20210824

Year of fee payment: 19

Ref country code: DE

Payment date: 20210811

Year of fee payment: 19

Ref country code: ES

Payment date: 20210903

Year of fee payment: 19

Ref country code: GB

Payment date: 20210819

Year of fee payment: 19

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: PT

Payment date: 20210716

Year of fee payment: 19

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200811

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 60325735

Country of ref document: DE

REG Reference to a national code

Ref country code: SE

Ref legal event code: EUG

REG Reference to a national code

Ref country code: NL

Ref legal event code: MM

Effective date: 20220901

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20220811

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220812

Ref country code: PT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230213

Ref country code: FI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220811

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20220831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220901

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220811

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220811

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220831

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230301

REG Reference to a national code

Ref country code: ES

Ref legal event code: FD2A

Effective date: 20230928

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF EXPIRATION OF PROTECTION

Effective date: 20230823

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220811

Ref country code: ES

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220812