Method and system for verifying the authenticity of a first communication participants in a communications network
Claim Score by NHIP
Abstract
In the method and the arrangement for checking the authenticity of a first communication subscriber in a communications network, a first fault information item is formed in the first communication subscriber using a fault detection data item of the first communication subscriber and an information item relating to a random data item. In a second communication subscriber in the communications network, a second fault information item is formed using a fault detection data item of the second communication subscriber and the information relating to the random data item. The authenticity of the first communication subscriber is checked using the first fault information and the second fault information.

Term
Term ended
Expired 31 May 2020, 6.3 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
20 claims: 3 independent, 17 dependent
- 1A method for checking the authenticity of a first communication subscriber in a communications network, comprising:forming a first fault information item in the first communication subscriber using a fault detection data item of the first communication subscriber and an information item relating to a random data item which has been transmitted to the first communication subscriber by a second communication subscriber in the communications network;transmitting the first fault information to the second communication subscriber by the first communication subscriber, forming a second fault information item in the second communication subscriber using a fault detection data item of the second communication subscriber and the information item relating to the random data item;checking the authenticity of the first communication subscriber in the second communication subscriber using the first fault information item and the second fault information item.
- 7Broadest claimClaim Score 59, broad(NHIP)A system for checking authenticity in a communications network, comprising:a first communication subscriber to form a first fault information using a fault detection data item of the first communication subscriber and an information item relating to a random data item which has been transmitted to the first communication subscriber, and to transmit the first fault information;a second communication subscriber to transmit the information relating to the random data item to the first communication subscriber, to receive the first fault information from the first communication subscriber, to form a second fault information using a fault detection data item of the second communication subscriber and the information relating to the random data item, and to check the authenticity of the first communication subscriber using the first fault information and the second fault information.
- 20A method for a second communication subscriber to confirm the authenticity of a first communication subscriber in a communications network, comprising:transmitting an information item relating to a random data item to the first communication subscriber;receiving a first fault information item from the first communication subscriber, the first fault information item being formed using a fault detection data item of the first communication subscriber and the information item relating to the random data item;forming a second fault information item in the second communication subscriber using a fault detection data item of the second communication subscriber and the information item relating to the random data item;and checking the authenticity of the first communication subscriber in the second communication subscriber using the first fault information item and the second fault information item.
Independent claims3
77 paragraphs in 5 sections, as filed
CROSS REFERENCE TO RELATED APPLICATIONS
This application is based on and hereby claims priority to German Application No. 19927 271.9 filed on Jun. 15, 1999 in Germany, and PCT Application No. PCT/DE00/01788 filed on May 31, 2000, the contents of which are hereby incorporated by reference. This application is a reissue of 10/009/975, patent 6,980,796.
BACKGROUND OF THE INVENTION
The invention relates to a method and an arrangement for checking the authenticity of a first communication subscriber in a communications network.
In a communications network, data is generally transmitted between communication subscribers, for example a service provider and a service user. In order to protect a communications network against penetration of an unauthorized communication subscriber into the communications network, the authenticity of each communication subscriber is generally checked.
3G TS 33.102 Version 3.0.0 Draft Standard, 3<sup>rd </sup>Generation Partnership Project, Technical Specification Group Services and System Aspects, 3G Security, Security Architecture, 05/1999 (“the 3G reference”) discloses a method and an arrangement for checking the authenticity of a communication subscriber, in particular of a service provider or of a service user in a communications network.
The method known from the 3G reference and the corresponding arrangement are based on what is referred to as 3G TS 33.102 Version 3.0.0 Draft Standard, which describes a security architecture of a mobile phone system.
In <figref idref="DRAWINGS">FIG. 4</figref>, the procedure during the checking of the authenticity of a communication subscriber, such as is known from the 3G reference is illustrated symbolically and parts thereof will be explained below briefly.
A transmission of data is illustrated in <figref idref="DRAWINGS">FIG. 4</figref> by an arrow in each case. A direction of an arrow characterizes a transmission direction during a data transmission.
<figref idref="DRAWINGS">FIG. 4</figref> shows a mobile phone system <b>400</b>, comprising a user <b>401</b> of a communication service, for example a mobile phone, and a provider <b>402</b> of a communication service. The provider <b>402</b> comprises a dial-in network <b>403</b> with a dial-in network operator from which the user <b>401</b> locally requests a communication service, and a home network <b>404</b> with a home network operator with which the user <b>401</b> is signed on and registered.
In addition, the user <b>401</b>, the dial-in network <b>403</b> and the home network <b>404</b> each have a central processing unit with a memory, for example a server (central computing unit), with which processing unit the procedure described below is monitored and controlled and on which memory data is stored.
The dial-in network <b>403</b> and the home network <b>404</b> are connected to one another via a data line over which digital data can be transmitted. The user <b>401</b> and the dial-in network <b>403</b> are connected to one another via any desired transmission medium for the transmission of digital data.
During a communication, the user <b>401</b> dials <b>410</b> into the dial-in network <b>403</b>. At the start of the communication, checking of both the authenticity of the user <b>401</b> and the authenticity of the provider <b>402</b> is carried out.
To do this, the dial-in network <b>403</b> requests <b>411</b> what is referred to as authentication data from the home network <b>404</b>, with which data the authenticity of the user <b>401</b> and of the provider <b>402</b> can be checked.
The authentication data which is obtained from the home network <b>404</b> comprises a random number and a sequential number of the provider <b>402</b>. The sequential number of the provider <b>402</b> is obtained in such a way that a counter of the provider <b>402</b> increases the sequential number of the provider <b>402</b> by the value 1 at each attempt at communication between the user <b>401</b> and the provider <b>402</b>.
It is to be noted that the random number and the sequential number of the provider <b>402</b> only constitute part of the authentication data and are not to be understood as comprehensive. Further authentication data is known from the 3G reference.
The home network <b>404</b> transmits <b>412</b> the requested authentication data to the dial-in network <b>403</b>. The dial-in network <b>403</b> processes the received authentication data in a suitable way <b>413</b>, and transmits the processed authentication data to the user <b>401</b>.
The user <b>401</b> checks <b>415</b> the authenticity of the provider <b>402</b> using a dedicated sequential number, which is handled in a way corresponding to the sequential number of the provider <b>402</b>, and using the sequential number of the provider <b>402</b>.
The procedure during the checking of the authenticity of the provider <b>402</b> is described in the 3G reference.
A result of the checking of the authenticity of provider <b>402</b>, “authenticity of provider satisfactory” <b>416</b>, “authenticity of provider satisfactory but sequential fault has occurred” <b>417</b> or “authenticity of provider not satisfactory” <b>418</b>, is transmitted <b>419</b> from the user <b>401</b> to the provider <b>402</b>.
In the case of the result “authenticity of provider satisfactory” <b>416</b>, the dial-in network <b>403</b> checks <b>420</b> the authenticity of the user <b>401</b> as described in the 3G reference.
In the case of the result “authenticity of provider not satisfactory” <b>418</b>, the communication is interrupted and/or restarted <b>421</b>.
In the case of the result “authenticity of provider satisfactory but a sequential fault has occurred” <b>417</b>, resynchronization takes place in such a way that the home network <b>404</b> transmits <b>422</b> a resynchronization request to the user <b>401</b>. The user responds with a resynchronization response in which resynchronization data is transmitted <b>423</b> to the home network <b>404</b>. The sequential number of the provider <b>402</b> is changed <b>424</b> as a function of the resynchronization response. The authenticity of the user <b>401</b> is then checked, as is known from the 3G reference.
The procedure described has the disadvantage that during checking of the authenticity of a communication subscriber, in particular during the checking of the authenticity of a service provider, a large amount of data has to be transmitted between the communication subscribers.
SUMMARY OF THE INVENTION
One aspect of the invention is thus based on simplifying and improving the known method and the known arrangement, to yield a simplified and improved arrangement for checking the authenticity of a communication subscriber in a communications network.
In the method for checking the authenticity of a first communication subscriber in a communications network, a first fault information item is formed in the first communication subscriber using a fault detection data item of the first communication subscriber and an information item relating to a random data item. In a second communication subscriber in the communications network, a second fault information item is formed using a fault detection data item of the first communications subscriber and the information relating to the random data item.
The authenticity of the first communication subscriber is checked using the first fault information item and the second fault information item.
In the arrangement for checking the authenticity of a first communication subscriber in a communications network, the first communication subscriber is set up in such a way that a first fault information item can be formed using a fault detection data item of the first communication subscriber and an information item relating to a random data item. In addition, the arrangement has a second communication subscriber in the communications network which is set up in such a way that a second fault information item can be formed using a fault detection data item of the second communication subscriber and the information relating to the random data item. The authenticity of the first communication subscriber can be checked using the first fault information item and the second fault information item.
The checking of the authenticity of a communication subscriber in a communications network is to be understood as meaning method steps which are carried out in the wider sense with checking of the authorization of a communication subscriber for access to a communications network or participation in communication in a communication network.
This thus encompasses both method steps which are carried out within the scope of the checking of the authorization of a communication subscriber for access to a communications network and such method steps which are carried out within the scope of the processing or the administration of data which is used in the checking.
The developments described below relate to the method and to the arrangement.
The development described below can be implemented either using software or hardware, for example using a specific electrical circuit.
In one refinement, the first communication subscriber is a service provider and/or the second communication subscriber is a service user in the communications network.
A sequential number is preferably used as the fault detection data item.
In one refinement, the information relating to the random data item is a random number.
In one development, the checking of the authenticity is simplified by determining a difference between the fault detection data item of the first communication subscriber and the fault detection data item of the second communication subscriber.
In one refinement, the checking of the authenticity is further improved with respect to the security of the communications network by limiting the difference.
One development is preferably used within the scope of a mobile phone system. In the mobile phone system, the service user is implemented as a mobile phone and/or the service provider is implemented as a mobile phone network operator.
BRIEF DESCRIPTION OF THE DRAWINGS
These and other objects and advantages of the present invention will become more apparent and more readily appreciated from the following description of the preferred embodiments, taken in conjunction with the accompanying drawings of which:
<figref idref="DRAWINGS">FIG. 1</figref> shows a mobile phone system;
<figref idref="DRAWINGS">FIG. 2</figref> shows an outline in which checking of the authenticity of a communication subscriber is illustrated symbolically;
<figref idref="DRAWINGS">FIG. 3</figref> shows a flowchart in which individual method steps are illustrated during checking of the authenticity of a service provider in a communications network; and
<figref idref="DRAWINGS">FIG. 4</figref> shows an outline in which checking of the authenticity of a communication subscriber in accordance with the 3G TS 33.102 Version 3.0.0 Standard is illustrated symbolically.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to like elements throughout.
Exemplary Embodiment: Mobile Phone System
A mobile phone system <b>100</b> is illustrated in FIG. <b>1</b>. The mobile phone system <b>100</b> comprises a mobile phone <b>101</b>, a local dial-in network <b>102</b> with a dial-in network operator <b>103</b> and a home network <b>104</b> with a home network operator <b>105</b>.
The mobile phone <b>101</b> is signed on and registered in the home network <b>104</b>.
In addition, the mobile phone <b>101</b>, the dial-in network <b>102</b> and the home network <b>104</b> each have a central processing unit <b>106</b>, <b>107</b>, <b>108</b> with a memory <b>109</b>, <b>110</b>, <b>111</b>, with which processing units <b>106</b>, <b>107</b>, <b>108</b> the procedure described below is monitored and controlled, and on which memories <b>109</b>, <b>110</b>, <b>111</b> data is stored.
The dial-in network <b>102</b> and the home network <b>104</b> are connected to one another via a data line <b>112</b> via which digital data can be transmitted. The mobile phone <b>101</b> and the dial-in network <b>102</b> are connected to one another via any desired transmission medium <b>113</b> for transmitting digital data.
The procedure during the checking of the authenticity of the mobile phone <b>101</b> and the procedure during the checking of the authenticity of the home network <b>104</b> and/or of the home network operator <b>105</b> are illustrated symbolically in <figref idref="DRAWINGS">FIG. 2</figref>, and parts thereof will be explained below briefly.
The transmission of data in <figref idref="DRAWINGS">FIG. 2</figref> is illustrated in each case by an arrow. A direction of an arrow characterizes a transmission direction during a data transmission.
The procedure which is described below and illustrated symbolically in <figref idref="DRAWINGS">FIG. 2</figref> is based on what is referred to as a 3G TS 33.102 Version 3.0.0 Standard, which describes a security architecture of a mobile phone system and is described in the 3G reference.
During a communication, the mobile phone <b>201</b> dials <b>210</b> into the dial-in network <b>203</b>. At the start of the communication, checking both of the authenticity of the mobile phone <b>201</b> and of the authenticity of the home network <b>204</b> and/or of the home network operator takes place.
To do this, the dial-in network <b>203</b> requests <b>211</b> authentication data from the home network <b>204</b>, with which authentication data the authenticity of the user <b>201</b> and of the home network <b>204</b> and/or of the home network operator can be checked.
The authentication data which is determined by the home network <b>204</b> comprises a random number and a sequential number of the home network <b>204</b> (cf. <figref idref="DRAWINGS">FIG. 3</figref> step <b>310</b>). The sequential number of the home network <b>204</b> is determined in such a way that a counter of the home network <b>204</b> increases the sequential number of the home network <b>204</b> by the value 1 at each attempt at communication between the mobile phone <b>201</b> and the home network <b>204</b>.
It is to be noted that the random number and the sequential number of the home network <b>204</b> only constitute part of the authentication data and are not to be understood as comprehensive. Further authentication data is specified in the 3G reference.
The home network <b>204</b> transmits <b>212</b> the requested authentication data to the dial-in network <b>203</b>. The dial-in network <b>203</b> processes the received authentication data in a suitable way <b>213</b> and transmits the processed authentication data to the mobile phone <b>201</b>.
The mobile phone <b>201</b> checks <b>215</b> the authenticity of the home network <b>204</b> using a dedicated sequential number which is handled in a way corresponding to the sequential number of the home network <b>204</b>, and using the sequential number of the home network <b>204</b>. In a way corresponding to the home network <b>204</b>, the mobile phone <b>201</b> also has a counter.
The procedure during the checking of the authenticity of the home network <b>204</b> is described in the 3G reference. Method steps which differ therefrom are described below.
What is referred to as overflow checking of the counter of the mobile phone <b>201</b> is carried out within the scope of the checking of the authenticity of the home network <b>203</b>. This overflow checking prevents overflowing of an acceptable numerical range of the counter of the mobile phone <b>201</b>.
In the overflow checking, the following conditions are tested: <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0059">1) sequential number of the home network <b>204</b>>sequential number of the mobile phone <b>201</b>;</li><li id="ul0002-0002" num="0060">2) sequential number of the home network <b>204</b>−sequential number of the mobile phone <b>201</b><−predefinable deviation (1,000,000);</li><li id="ul0002-0003" num="0061">the following applying for the predefined deviation: <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0062">predefinable deviation is sufficiently large in order to ensure, during normal or fault-free communications operation:</li><li id="ul0003-0002" num="0063">that the sequential number of the home network <b>204</b>—sequential number of the mobile phone <b>201</b> is not>predefinable deviation; <ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0064">the maximum permissible sequential number of the mobile phone <b>201</b>/predefinable deviation is sufficiently large in order to ensure that the maximum permissible sequential number of the mobile phone <b>201</b> is not reached during operation.</li></ul></li></ul></li></ul></li></ul>
The result of the checking of the authenticity of the home network <b>204</b>, “authenticity satisfactory” <b>216</b>, “authenticity satisfactory but a sequential fault has occurred” <b>217</b> or “authenticity not satisfactory” <b>218</b> is transmitted <b>219</b> to the home network <b>204</b> from the mobile phone <b>201</b>.
In the case of the result “authenticity satisfactory” <b>216</b>, the dial-in network <b>203</b> checks <b>220</b> the authenticity of the mobile phone <b>201</b>, as described in 3G reference.
In the case of the result “authenticity not satisfactory” <b>218</b>, the communication is interrupted or restarted <b>221</b>.
In the case of the result “authenticity satisfactory but a sequential fault has occurred” <b>217</b>, resynchronization <b>222</b> takes place. Resynchronization is to be understood as a change of the sequential number of the home network <b>204</b>.
For this purpose, the mobile phone <b>201</b> transmits <b>222</b> resynchronization data to the dial-in network <b>203</b>.
The resynchronization data comprises the same random number which was transmitted within the scope of the authentication data, and the sequential number of the mobile phone <b>201</b> (cf. <figref idref="DRAWINGS">FIG. 3</figref> step <b>320</b>).
The dial-in network <b>203</b> processes the resynchronization data in a suitable way and transmits the processed resynchronization data to the home network <b>204</b>.
The home network <b>204</b> checks the sequential number of the mobile phone <b>201</b> and the sequential number of the home network <b>204</b> using the processed resynchronization data, and if appropriate changes <b>223</b> the sequential number of the home network <b>204</b> (cf. <figref idref="DRAWINGS">FIG. 3</figref> step <b>330</b>).
The home network <b>204</b> sequentially transmits new authentication data, which if appropriate comprises the changed sequential number of the home network <b>204</b>, to the dial-in network <b>203</b>.
In order to illustrate the described procedure, important steps <b>300</b> of the procedure are illustrated in FIG. <b>3</b>.
<figref idref="DRAWINGS">FIG. 3</figref> shows a first step <b>310</b> within the scope of which the authentication data (first fault information) is determined.
The resynchronization data (second fault information) is determined within the scope of a second step <b>320</b>.
The sequential number of the mobile phone and the sequential number of the home network are checked within the scope of a third step <b>330</b>, using the resynchronization data.
An alternative of the first exemplary embodiment is described below.
In the alternative exemplary embodiment, a method is implemented in which the home network is made more reliable with respect to a data in the event of a system crash.
For this purpose, the current sequential number of the home network is stored in the memory of the home network, in each case at a predefinable time interval. A sequential number of the home network which has been lost during a system crash of the home network is restored in such a way that a predefinable additional value is added to the value of the stored sequential number. The predefinable additional value is dimensional in such a way that exceeding of the sum of the sequential number of the mobile phone and the predefinable deviation is not exceeded.
In the alternative exemplary embodiment, the predefinable additional value is determined in such a way that an average number of authentication attempts on one day by the home network, which number is determined during operation of the communications network, is multiplied by a factor with the value 10.
The invention has been described in detail with particular reference to preferred embodiments thereof and examples, but it will be understood that variations and modifications can be effected within the spirit and scope of the invention.
Contents5
5 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5
Every citation, both waysCites: the store holds 36 of 37
| Document | Relation | Office | Cited during |
|---|---|---|---|
| DE19524021A1 | Cites | Germany | Search report |
| US4519068A | Cites | United States of America | Applicant |
| US5239294A | Cites | United States of America | Search report |
| US5241598A | Cites | United States of America | Search report |
| US5282250A | Cites | United States of America | Search report |
| US5557654A | Cites | United States of America | Search report |
| US5572193A | Cites | United States of America | Search report |
| US5642401A | Cites | United States of America | Search report |
| US5689563A | Cites | United States of America | Search report |
| US5794139A | Cites | United States of America | Search report |
| US5799084A | Cites | United States of America | Search report |
| US5953652A | Cites | United States of America | Search report |
| US5991623A | Cites | United States of America | Applicant |
| US6016349A | Cites | United States of America | Search report |
| US6035039A | Cites | United States of America | Search report |
| US6078807A | Cites | United States of America | Search report |
| US6091945A | Cites | United States of America | Search report |
| US6108424A | Cites | United States of America | Search report |
| US6118993A | Cites | United States of America | Search report |
| US6466780B1 | Cites | United States of America | Applicant |
| US6618584B1 | Cites | United States of America | Search report |
| US6665530B1 | Cites | United States of America | Search report |
| US6741852B1 | Cites | United States of America | Search report |
| US6839553B2 | Cites | United States of America | Search report |
| US6980796B1 | Cites | United States of America | Applicant |
| WO9101067A2 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO9202103A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| JPH05508274A | Cites | Japan | Applicant |
| JPH08242488A | Cites | Japan | Applicant |
| JPH0984124A | Cites | Japan | Applicant |
| DE19524021 | Cites | Germany | Search report |
| JP5508274 | Cites | Japan | Third party observation |
| JP8242488 | Cites | Japan | Third party observation |
| JP984124 | Cites | Japan | Third party observation |
| WO9101067 | Cites | World Intellectual Property Organization (WIPO) | Third party observation |
| WO9202103 | Cites | World Intellectual Property Organization (WIPO) | Third party observation |
| 3G TS 33.102 version 3.0.0-Draft Standard, 3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, 3G Security Architecture (May 1999). | Non-patent | – | Search report |
| Patent Abstract of Germany-DE 197 18 827 A1-Mohrs, Nov. 19, 1998. | Non-patent | – | Search report |
| 3G TS 33.102 version 3.9.0-Draft Standard, 3rdGeneration Partnership Project, Technical Specification Group Services and System Aspects, 3G Security Architecture (Jun. 2001) (Release 1999). | Non-patent | – | Search report |
| 3G TS 33.102 version 3.4.2-Draft Standard 3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, 3G Security Architecture (Sep. 2001) (Release 4). | Non-patent | – | Search report |
| The GSM System, Mobility and Security Management, pp. 433-498 XP-000860007. | Non-patent | – | Search report |
| Patent Abstract of Japanese Publication No. JP-5-503816 published Jun. 17, 1993. | Non-patent | – | Applicant |
| Patent Abstract of Japanese Publication No. JP-4-24954 published Sep. 4, 1992. | Non-patent | – | Applicant |
| 3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, 3G Security, Security Architecture, Release 4, 3GPP TS 33.102 V4.4.0 (Jun. 2002). | Non-patent | – | Applicant |
| Patent Abstract of Japanese Publication No. JP-5-503816 published Jun. 17, 1993. | Non-patent | – | Third party observation |
| Patent Abstract of Japanese Publication No. JP-4-24954 published Sep. 4, 1992. | Non-patent | – | Third party observation |
| 3<sup>rd </sup>Generation Partnership Project, Technical Specification Group Services and System Aspects, 3G Security, Security Architecture, Release 4, 3GPP TS 33.102 V4.4.0 (Jun. 2002). | Non-patent | – | Third party observation |
| 3G TS 33.102 version 3.0.0—Draft Standard, 3<sup>rd </sup>Generation Partnership Project, Technical Specification Group Services and System Aspects, 3G Security Architecture (May 1999). | Non-patent | – | Search report |
| Patent Abstract of Germany-DE 197 18 827 A1—Mohrs, Nov. 19, 1998. | Non-patent | – | Search report |
| 3G TS 33.102 version 3.9.0-Draft Standard, 3<sup>rd</sup>Generation Partnership Project, Technical Specification Group Services and System Aspects, 3G Security Architecture (Jun. 2001) (Release 1999). | Non-patent | – | Search report |
| 3G TS 33.102 version 3.4.2-Draft Standard 3<sup>rd </sup>Generation Partnership Project, Technical Specification Group Services and System Aspects, 3G Security Architecture (Sep. 2001) (Release 4). | Non-patent | – | Search report |
| The GSM System, Mobility and Security Management, pp. 433-498 XP-000860007. | Non-patent | – | Search report |
50 members in 10 offices
Priority claims10
| Document | Office | Kind | Date |
|---|---|---|---|
| 19927271 | Germany | – | |
| 19927271 | Germany | A | |
| 19927271 | Germany | A | |
| 0001788 | Germany | W | |
| 0001788 | Germany | W | |
| 10009975 | – | – | – |
| 19927271 | – | – | – |
| DE1999127271 | – | – | – |
| PCTDE0001788 | – | – | – |
| WO2000DE01788 | – | – | – |
Members50
| Document | Office | Kind | |
|---|---|---|---|
| WO0078078A1 | World Intellectual Property Organization (WIPO) | A1 | |
| AU5805100A | Australia | A | |
| KR20020019087A | Republic of Korea | A | |
| EP1186193A1 | European Patent Office (EPO) | A1 | |
| BR0011703A | Brazil | A | |
| CN1369183A | China | A | |
| JP2003501979A | Japan | A | |
| AU760714B2 | Australia | B2 | |
| EP1326469A2 | European Patent Office (EPO) | A2 | |
| EP1326470A2 | European Patent Office (EPO) | A2 | |
| KR20030059824A | Republic of Korea | A | |
| KR20030062415A | Republic of Korea | A | |
| CN1130099C | China | C | |
| US2003229784A1 | United States of America | A1 | |
| EP1326469A3 | European Patent Office (EPO) | A3 | |
| EP1326470A3 | European Patent Office (EPO) | A3 | |
| JP2004007690A | Japan | A | |
| US2004006714A1 | United States of America | A1 | |
| JP2004032730A | Japan | A | |
| CN1516494A | China | A | |
| CN1516495A | China | A | |
| EP1186193B1 | European Patent Office (EPO) | B1 | |
| EP1326470B1 | European Patent Office (EPO) | B1 | |
| DE50010928D1 | Germany | D1 | |
| DE50010940D1 | Germany | D1 | |
| ES2244451T3 | Spain | T3 | |
| ES2244843T3 | Spain | T3 | |
| US6980796B1 | United States of America | B1 | |
| KR100576956B1 | Republic of Korea | B1 | |
| KR100576957B1 | Republic of Korea | B1 | |
| KR100578685B1 | Republic of Korea | B1 | |
| EP1326469B1 | European Patent Office (EPO) | B1 | |
| DE50013577D1 | Germany | D1 | |
| US7139550B2 | United States of America | B2 | |
| ES2272824T3 | Spain | T3 | |
| CN1314277C | China | C | |
| CN1316834C | China | C | |
| JP3924465B2 | Japan | B2 | |
| JP4272920B2 | Japan | B2 | |
| USRE40791EThis record | United States of America | E | |
| JP4650994B2 | Japan | B2 | |
| US8565429B2 | United States of America | B2 | |
| BR0017414B1 | Brazil | B1 | |
| BRPI0017414B1 | Brazil | B1 | |
| BR0017415B1 | Brazil | B1 | |
| BRPI0017415B1 | Brazil | B1 | |
| BR0011703B1 | Brazil | B1 | |
| BRPI0011703B1 | Brazil | B1 | |
| BRPI0017415B8 | Brazil | B8 | |
| BRPI0017414B8 | Brazil | B8 |
27 transactions on the USPTO file
Allowed without a rejection on record.
- Non-final rejections
- 0
- Final rejections
- 0
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Expire PatentEXP. | EXP. | |
| Post Issue Communication - Certificate of CorrectionN423 | N423 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Receipt into PubsR1021 | R1021 | |
| Dispatch to FDCD1935 | D1935 | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Filing Receipt - ReplacementFLRCPT.R | FLRCPT.R | |
| Notice of Reissue Published in Official GazetteNRE. | NRE. | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Application Is Now CompleteCOMP | COMP | |
| Cleared by L&R (LARS)L128 | L128 | |
| Referred to Level 2 (LARS) by OIPE CSRL198 | L198 | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Initial Exam Team nnIEXX | IEXX |
8 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.)LAPS | LAPS | |
| Maintenance fee reminder mailedREMI | REMI | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Fee paymentFPAY | FPAY | |
| Certificate of correctionCC | CC |
Numbers
- Publication
- RE040791
- Publication, DOCDB
- RE40791
- Publication, EPODOC
- USRE40791E
- Application
- 12004440
- Application, DOCDB
- 444000
- Application, EPODOC
- US20000004440
Titles
- English
- Method and system for verifying the authenticity of a first communication participants in a communications network
Classification
- CPC, 4
- H04L63/126
- H04W12/06
- H04L69/40
- H04W12/108
- IPC, 8
- H04M1 66
- G06F11 30
- G09C1 00
- H04L9 00
- H04L9 32
- H04L12 28
- H04W12 06
- H04W12 10
- USPC, 6
- 455410000
- 380247000
- 380270000
- 380271000
- 455411000
- 713182000