EP2014057A2 - Identification de noeuds dans un reseau - Google Patents
Identification de noeuds dans un reseauInfo
- Publication number
- EP2014057A2 EP2014057A2 EP07788935A EP07788935A EP2014057A2 EP 2014057 A2 EP2014057 A2 EP 2014057A2 EP 07788935 A EP07788935 A EP 07788935A EP 07788935 A EP07788935 A EP 07788935A EP 2014057 A2 EP2014057 A2 EP 2014057A2
- Authority
- EP
- European Patent Office
- Prior art keywords
- node
- parameter
- identifier
- file
- cryptographic
- 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
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
- H04L63/126—Applying verification of the received information the source of the received data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
Definitions
- the present invention relates to an identification of nodes in a network. More particularly, it relates to secure identification of heterogeneous nodes in a network without an infrastructure, for example an ad-hoc type network.
- the identification according to the invention is defined in accordance with the domain name system according to the DNS / DNSSEC specification ("Domain Name System / Domain Name System Security") in order to facilitate its subsequent integration.
- a DNS naming system is designed specifically for a communications network comprising an infrastructure like that of I 1 internet or intranet network connecting nodes such as terminals or servers.
- This naming system matches for each of these nodes one or more understandable names, called domain names, for example "mydomain.com", to network information relating to the node, such as textual fields, cryptographic identifiers, parameters security, a mail server, or more particularly IP type addresses ("Internet Protocol" in English).
- domain names for example "mydomain.com”
- IP type addresses Internet Protocol" in English.
- networks including networks without infrastructure such as ad-hoc networks, use the nodes to establish connectivity between users of said nodes.
- These nodes are very heterogeneous and can be simple entities such as servers or terminals, or complex entities such as networks. Referring to the last case, the DNS naming system does not apply to complex entities.
- the DNS naming system does not apply to nodes connected in a network without an infrastructure such as an ad-hoc network, where communications are established spontaneously between two nodes without the intermediary of a network. central entity.
- the nodes of an ad-hoc network are ignored a priori and are not referenced in DNS servers.
- the invention fills this gap by identifying heterogeneous nodes as simple nodes and complex nodes present in a network without infrastructure.
- the invention relates to a method for identifying a node with other nodes in a communication network, characterized in that it comprises the following steps: storing in each node a file containing descriptive parameters of the node, each parameter being indexed by a cryptographic identifier of the node and a parameter identifier, broadcast from a first node connecting to the network, from the cryptographic identifier of said first node to the other nodes of the network, transmitting the cryptographic identifier of the first node and the identifier of a parameter of the first node required by another node from said other node of the network to the first node, searching for a portion of the required parameter in the file of the first node node according to the cryptographic identifier and the identifier of the required parameter, and transmitting the found portion of the required parameter from the first node to said other node.
- the invention advantageously identifies any type of node, both simple nodes such as a server, a mobile terminal or a computer, as complex nodes such as a network, such a node being unknown in the domain name system according to the DNS specification.
- the identification based on a cryptographic identifier is universal for all the nodes, since the cryptographic identifier of each node is relative to a public key of a public key / private key pair assigned to the node.
- the identifier of a descriptive parameter is a name dedicated to the parameter which makes it possible to distinguish the descriptive parameters from each other and thus allows the file to contain a large number of descriptive parameters.
- the identifier of a descriptive parameter is a type characterizing the parameter which facilitates a subsequent integration of the invention with the DNS system.
- the invention also relates to a node of a communication network, characterized in that it comprises: a memory for a file containing descriptive parameters of the node, each parameter being indexed by a cryptographic identifier of the node and a parameter identifier, a means for distributing the cryptographic identifier of said node to the other nodes of the network, a means for transmitting the cryptographic identifier of a first other node and the identifier of a parameter of said first other node required by said node, means for searching in the file for a part of a parameter required by a second other node according to the cryptographic identifier of said node and parameter identifier transmitted by the second other node, and means for transmitting the found portion of the requested parameter to said second other node.
- the invention relates to a computer program comprising instructions for implementing the method according to the invention when said instructions are implemented by a processor in a node according to the invention.
- FIG. 1 is a schematic block diagram of an identification system in a network without infrastructure according to the invention
- FIG. 2 is a schematic block diagram of a node according to the invention
- FIG. 3 is a representative diagram of a node descriptive file according to the invention
- FIG. 4 is an algorithm of a node identification method according to the invention
- Figures 5 and 6 are respectively representative diagrams of an identification request and an identification response according to a first embodiment of the invention.
- FIGS. 7 and 8 are respectively representative diagrams of an identification request and an identification response according to a second embodiment of the invention.
- an identification system comprises a set of heterogeneous nodes Ni to Nj present in a communication network without infrastructure.
- the network is considered an ad-hoc network RA and is thus called in the following description.
- the ad-hoc network RA the communications between two nodes are established spontaneously and the nodes have no prior knowledge of the other nodes present in the network.
- the identification between two nodes is effected by an exchange of identification request RQI and identification response RPI.
- the nodes are heterogeneous and may be simple entities such as a server Ni, a mobile terminal N3, Nj + i, or a personal computer Nj, Nj and / or complex entities such as a network R forming the node N2 and associated with a terminal T.
- the network R is different from an ad-hoc network and can be a. an infrastructure network such as the Internet or an Intranet, to which client terminals are wired or wirelessly connected, or a GSM (Global System for Mobile Communications) or UMTS (Universal Mobile Telecommunications System) radio network.
- GSM Global System for Mobile Communications
- UMTS Universal Mobile Telecommunications System
- a descriptive file F j comprising descriptive information specific to the node, such as information relating to the identity of the node, for example : if it is a router or a terminal, information relating to the location of the node, for example an IP address, and accessible to other nodes.
- the terminal T associated with the network R comprises the descriptive file F2 identifying the network R.
- the descriptive information specific to the node Nj is called in the following description "descriptive parameters" P mj , with 1 ⁇ m ⁇ M, the integer M may be different from one node to another.
- the file Fj of the node N j is described in more detail with reference to FIG.
- the nodes N 1 to N 1 of the ad-hoc network RA comprise similar entities in order to implement the identification method of the invention described with reference to FIG.
- IR network interface which is a radio interface when the node is a mobile terminal for example, a communication unit UC, a descriptive file management unit UF, and two memories M1 and M2.
- a specific unit US characterizes the node N j , for example the processing unit of a PC, the processing unit of a server or the processing unit of a terminal mobile. All the entities of the node are connected by a bidirectional communication bus B.
- the node Nj communicates with the other nodes of the ad-hoc network RA via the IR network interface to transmit requests and receive responses to said requests.
- the RQI identification requests transmitted from the network interface of the node N j are established by the communication unit UC.
- the identification responses received by the IR network interface are processed by the communication unit UC.
- the UF descriptive file management unit manages the information relating to the node N j , included in a descriptive file F j .
- the management unit UF responds to the identification requests RQI relating to the identification of the node N j transmitted by other nodes in the ad hoc network.
- the functionalities of the UC, UF and US units can be realized in the form of software modules implemented in the node Nj and executed by a central processing unit of the node N j .
- the memory Ml contains, among other things, the descriptive file F j of the node N j , a public key KPUj of a public key cryptographic pair KPU j / private key KPVj assigned to the node Nj and a one-way hash function H.
- memory M2 is a security memory including the private key KPVj of the cryptographic pair.
- the file F j of the node Nj is specified by a cryptographic identifier ICj dedicated to the node to establish a link to a more complete description of the node relating to the descriptive parameters Pi j to P m ⁇ of the node.
- the cryptographic identifier ICj depends on the public key KPUj of the public key cryptographic pair KPU j / private key KPV j assigned to the node.
- the cryptographic identifier ICj is the public key KPU ⁇ , or a hash of the public key H (KPU j ) determined by applying the hash function H to the public key KPUj, the minced public key H (KPU j ) being generally fixed size and smaller than that of the public key KPU- ⁇ .
- the public key-based node identification has the advantage of being universal, with each node of the RA network having its own cryptographic pair.
- the cryptographic pair of the node participates in security functions when sending data to a destination node.
- the signature of the data using the private key of the node guarantees the integrity of the data for the destination node which verifies the signature using the public key of the node that sent the data.
- the encryption of the data using the public key of the destination node guarantees the confidentiality of the exchange between the node and the destination node, which is the only one able to decrypt the data using its private key.
- the file F j comprises one or more descriptive parameters related to the nature of the node M j .
- a descriptive parameter of a personal computer (PC) Nj or Nj is the IP address of the personal computer.
- descriptive parameters of the network R are the address of a DHCP server ("Dynamic Host Configuration Protocol" in English) or the address of a network gateway such as a HTTP proxy ("HyperText Transfer Protocol" in English) .
- a descriptive parameter of the terminal mobile N3 or N-JJ-I is for example the international telephone number MSISDN ("Mobile Station ISDN Number" and "Integrated Digital Services Network” in English) of the mobile terminal.
- the public key KPU j and the hashed public key H (KPU j ) of a node are also descriptive parameters contained in the file of each node. All the parameters contained in the file are parameters that are accessible by the other nodes.
- Each descriptive parameter P n J in the file Fj contains an identifier of the parameter, such as a name NP mj and / or a type TP m ⁇ , and a parameter value VP mj .
- the name NP n -J is a sub-identifier of the node Nj.
- the type TP m j characterizes the parameter P mj by indicating for example that the parameter is an IPv4 address "A", an e-mail server name "MX" or a text "TXT”.
- the parameter value VP m j is required by another node of the network and is for example of the form "2001: 2: 56" for a parameter of type address, or of the form "server name mail.com" for a parameter e-mail server type.
- Information other than the descriptive parameters in the file F j are related to the descriptive parameter (s) of the file and / or their name and each include a type and a value. This information corresponds to the detection of errors and the integrity of the information to be transmitted from the node Np.
- the error value VE m j of the error information contains a list of types linked to a parameter name NPj n - ,, such as TP 1n J, TA, and the name of the next parameter NP ⁇ i.
- a RQI Identification request transmitted by another node concerning a name parameter NP mj existing in the file F j whose type TP mj contained in the request is invalid, a response to the error value VE m -.
- the response indicates that the type contained in the request for this required parameter name does not exist in the F j file, which is justified by the list of types associated with the NP mj name of the required parameter.
- Authentication information characterized by a type TA and relating to a respective value VP mj i v E mj to be transmitted to another node which has requested it, authenticates the origin and guarantees the integrity of said respective value relative to the node N j , the authentication value VAP nj , VAE mj associated with the authentication information corresponds to a signature determined according to the respective value VP m j, VE m j to be transmitted and the private key KPV j assigned at node N j .
- the value VAP mj , VAE m j is determined by applying the hash function H to the value VP mj , VE mj and by asymmetric encryption of the hash value as a function of the private key KPV j assigned to the node.
- the value VAP 111 -; transmitted in an RPI response at the same time as the respective value VP m j of the parameter P mj required ensures that said respective value comes from the node N mj .
- the value VAE mj transmitted in an RPI response at the same time as the error value VE m j relative to the name NP m j of the required parameter P m j ensures the integrity of the error value VE m j.
- the value VAP mj , VAE mj is transmitted encrypted by the public key of the other node, thereby guaranteeing the confidentiality of the information exchange in the RPI response.
- the other node receiving an identification response containing the value VP T g has also required, or previously, the public key KPU ⁇ associated with the private key KPV- cryptographic pair assigns node N- ] to decrypt the authentication value V ⁇ P mi .
- the other node applies to the value VP m - j received the one-way hash function H to obtain a hash value, and compares the obtained hash value and the decrypted value which must be identical.
- the descriptive parameters in the file F j are indexed according to two indexing embodiments.
- the first embodiment of indexing relates to a parameter indexing associating the identifier IC- of the node N- ] and the name NP mj of the parameter in order to obtain the associated value VP m .
- the types TPI ⁇ to ⁇ Pm j characterizing the parameters Pi j to P m - j of the node are identical and do not differentiate a parameter of the node from another parameter of the node.
- Parameters Pi, at P mj of the node are differentiated by their names NPi ⁇ to
- the second indexing embodiment relates to a parameter indexation associating the identifier IC 1 of the node B j and the type TP mj of the parameter in order to obtain the associated value VP ⁇ .
- the types TP ⁇ j to TP 1n - ] characterizing the parameters P i to P n .- of the node are distinct from each other, the parameters having no name NPi ] to NPr n -J .
- the F-F then contains error information containing all types of parameters and information of the descriptive file of the node N j , which reduces the size of the file.
- Each descriptive parameter or information in the descriptive file is defined by an identical class for all the information, for example the class "IN” relative to the Internet.
- the descriptive file includes file management information characterized by the type "SOA" ("Start Of Authority” in English) whose value includes, inter alia, the identity and address of the administrator of the file and data. describing how the file is managed.
- the descriptive file may further comprise cryptographic information characterized by the "Domain Name System KEY" (DNSKEY) type relating to the public key of the cryptographic pair assigned to the node.
- DNSKEY Domain Name System KEY
- the values of this additional information are respectively authenticated by authentication information characterized by the TA type.
- step E1 node N1 is connected for the first time to the ad-hoc RA network.
- the IR network interface of the node N1 broadcasts to the other nodes an MS message established by the CPU unit of the node N1 and containing the cryptographic identifier ICi of the node N1 and an address of source ADNi assigned to the Node Node so that the other nodes identify the Node and send it messages or queries.
- the ADNI address is for example the MAC ("Medium Access Control") address of the node including identifiers and a serial number, or alternatively an address formed from the cryptographic identifier IC 1.
- the IR network interface of another node N2 intercepts the message MS.
- the communication unit OC of the node N2 establishes a request for identification RQI intended for the node N1 to read one or more descriptive parameters required such as at least the public key assigned to the node N, in order to check the integrity of the parameters coming from of the node Ni.
- the request RQI contains at least the identifier ICi of the node N extracted from the message MS, the name NP m ⁇ of the required parameter, as identifier of the parameter, and a source address ADN2 relating to the node N2 for the node Ni to transmit a response from the request RQI to the node N2 -
- the node N2 can require all the parameters of the node N1 by the transmission of a specific identification request.
- the IR network interface of the node N1 receives the request RQI which is processed by the communication unit UC of the node N1.
- the descriptive file management unit UF of the node NN looks for the value VP n . and the VAP m i authentication value associated with the NP n i parameter name in the Fi file.
- step E4 the values VP n -I and VAP m i are included in the file Fi
- the communication unit of the node N1 establishes an identification response RPI including the identifier ICi ⁇ u node Ni, the name NP m i and the values VP m i and VAP m ⁇ of the required parameter found in the file Fi of the first node Ni.
- the RPI response is transmitted to node N2 in step E5.
- the node N2 receives the response RPI and the communication unit of the node N2 checks the integrity of the parameter value VP m i required.
- the communication unit of the node N2 decrypts the authentication value VAP m i according to the public key KPUi assigned to the node N1 and transmitted in the response RPI or in a previous response and produces a decrypted value. Then the communication unit applies the one-way hash function H to the value VP m i extracted from the transmitted response RPI and compares the hash value with the decrypted value, which must be identical.
- the communication unit UC of the node N 1 establishes an identification response RPI containing the identifier IC 1 of the node Ni, the NP m i name of the parameter, the error value VE m i corresponding to the parameter P n i and the associated authentication value VAE m i.
- the response RPI is transmitted by the IR interface of the node N1 to the node N2 in the step E1, which verifies the integrity of the error value VAE m i in the step E8 similarly to the step E6.
- the identification requests RQI and the identification responses RPI do not contain the name NP m i of the parameter, but contain the type TP m i characterizing the parameter P rc i, as identifier of the parameter.
- steps E3 and E4 The search for the values VP m i and VAP i i of the required parameter P m i in the file Fi is performed according to the identifier IC i and the type of parameter TP i i included in the request RQI transmitted in step E 2.
- step E4 If in step E4, the values VP m i and VAP m i are not included in the file Fi, an error information containing all the types of parameters and information of the descriptive file Fi and accompanied by the value d associated authentication is transmitted to node N2.
- RQI identification request frames and RPI identification response frames have identical field structures and conform to the frames of the DNS / DNSSEC specification.
- a frame has at least four fields.
- a first C_ET header field indicates whether the frame is relative to an RQI request or an RPI response
- a second C_RQ field comprises the request
- a third C__RP field comprises the response
- a fourth field C__AD may include additional information .
- the field C_RQ of the request RQI and of the response RPI includes the name NP m j of the required parameter associated with the identifier IC j of the node N j to which the Query is intended.
- the TP mj type of the parameter is included in the request to conform to the DNS / DMSSEC specification, but does not distinguish one parameter from another parameter.
- the C_RP field of the RPI response also has the NP name n -, - of the required parameter associated with the identifier IC j and the type TP- of the parameter, and furthermore comprises the value VP m ⁇ of the parameter and the value d 1 authentxfication VAP 1n -, associated.
- the field C_RQ of the request RQI and the response RPI include the identifier IC j of the node INh for which the request is intended and the type TP m - characterizing the required parameter.
- the C_RP field of the RPI response also comprises the identifier IC 1 and the TP m - type of the parameter, and furthermore comprises the value VP n - J of the parameter and the value d 1 authentication VAP T0 associated.
- the additional field C_AD of the RPI identification response of a node N j may contain parameters useful for a first exchange with another node, such as the public key KPU j or the IP address of the node N j .
- the invention is not limited to networks without ad-hoc type infrastructure, it can also be implemented in a network with infrastructure such as the internet in which the nodes have access to the DNS system. In this case, the identification system of the invention easily integrates into the DNS without ambiguity.
- the DNS / DNSS ⁇ C databases relating to the invention associate a domain name of an N- j node with an IP address j and a cryptographic identifier IC j .
- a client node can obtain the cryptographic identifier IC 3 of the N- node, other than by receiving said identifier broadcast by the N- node.
- the client node To obtain the cryptographic identifier of a node N j , the client node requires the identifier ICi associated with the domain name of the node Kj from one of the DNS servers linked to a database that transmits it to him.
- the client node obtains a more detailed description of the node Nj after the steps E2 to E8 of FIG.
- a client node which requires the IP address of the node Nj to a DNS server, also obtains in response the cryptographic identifier IC j of the node N j included in the additional field C_AD.
- the invention described herein relates to a method and a node among heterogeneous nodes.
- the steps of the method of the invention are determined by the instructions of a computer program incorporated in the node.
- the program comprises program instructions which, when said program is executed in a processor of the node whose operation is then controlled by the execution of the program, carry out the steps of the method according to the invention.
- the invention also applies to a computer program, including a computer program on or in an information carrier, adapted to implement the invention.
- This program can use any programming language, and be in the form of source code, object code, or intermediate code between source code and object code such as in a partially compiled form, or in any other form desirable to implement the method according to the invention.
- the information carrier may be any entity or device capable of storing the program.
- the medium may comprise storage means or recording medium on which is recorded the computer program according to the invention, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or a USB key, or a magnetic recording means, for example a floppy disk (fioppy dise) or a hard disk.
- the information medium may be a transmissible medium such as an electrical or optical signal, which may be conveyed via an electrical or optical cable, by radio or by other means.
- the program according to the invention can in particular be downloaded to an Internet type network.
- the information carrier may be an integrated circuit in which the program is incorporated, the circuit being adapted to execute or to be used in carrying out the method according to the invention.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
FR0651527A FR2900523A1 (fr) | 2006-04-28 | 2006-04-28 | Identification de noeuds dans un reseau |
PCT/FR2007/051097 WO2007125235A2 (fr) | 2006-04-28 | 2007-04-12 | Identification de noeuds dans un reseau |
Publications (1)
Publication Number | Publication Date |
---|---|
EP2014057A2 true EP2014057A2 (fr) | 2009-01-14 |
Family
ID=37597722
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP07788935A Withdrawn EP2014057A2 (fr) | 2006-04-28 | 2007-04-12 | Identification de noeuds dans un reseau |
Country Status (5)
Country | Link |
---|---|
US (1) | US20090109874A1 (fr) |
EP (1) | EP2014057A2 (fr) |
JP (1) | JP2009535875A (fr) |
FR (1) | FR2900523A1 (fr) |
WO (1) | WO2007125235A2 (fr) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120094600A1 (en) * | 2010-10-19 | 2012-04-19 | Welch Allyn, Inc. | Platform for patient monitoring |
WO2018002111A1 (fr) * | 2016-06-28 | 2018-01-04 | Robert Bosch Gmbh | Procédé et dispositif pour déléguer une authentification de ticket à un réseau en étoile dans l'internet des objets et services |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6496704B2 (en) * | 1997-01-07 | 2002-12-17 | Verizon Laboratories Inc. | Systems and methods for internetworking data networks having mobility management functions |
CZ20014168A3 (cs) * | 1999-05-21 | 2002-05-15 | International Business Machines Corporation | Způsob a zařízení pro inicializaci zabezpečné komunikace a pro vytvoření výhradních dvojic bezdrátových přístrojů |
EP1102430A1 (fr) * | 1999-10-27 | 2001-05-23 | Telefonaktiebolaget Lm Ericsson | Procédé et agencement dans un réseau ad hoc |
US20040025018A1 (en) * | 2002-01-23 | 2004-02-05 | Haas Zygmunt J. | Secure end-to-end communication in mobile ad hoc networks |
JP4554968B2 (ja) * | 2004-03-26 | 2010-09-29 | 株式会社日立製作所 | アドホックネットワークにおける無線通信端末装置 |
US7461253B2 (en) * | 2005-11-22 | 2008-12-02 | Motorola, Inc. | Method and apparatus for providing a key for secure communications |
-
2006
- 2006-04-28 FR FR0651527A patent/FR2900523A1/fr active Pending
-
2007
- 2007-04-12 WO PCT/FR2007/051097 patent/WO2007125235A2/fr active Application Filing
- 2007-04-12 JP JP2009507124A patent/JP2009535875A/ja active Pending
- 2007-04-12 EP EP07788935A patent/EP2014057A2/fr not_active Withdrawn
- 2007-04-12 US US12/298,791 patent/US20090109874A1/en not_active Abandoned
Non-Patent Citations (1)
Title |
---|
See references of WO2007125235A2 * |
Also Published As
Publication number | Publication date |
---|---|
JP2009535875A (ja) | 2009-10-01 |
US20090109874A1 (en) | 2009-04-30 |
FR2900523A1 (fr) | 2007-11-02 |
WO2007125235A3 (fr) | 2007-12-21 |
WO2007125235A2 (fr) | 2007-11-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
RU2444054C2 (ru) | Одноранговый обмен контактной информацией | |
US7546454B2 (en) | Automated digital certificate discovery and management | |
FR2847752A1 (fr) | Methode et systeme pour gerer l'echange de fichiers joints a des courriers electroniques | |
EP2092703A1 (fr) | Contrôle de message a transmettre depuis un domaine d'émetteur vers un domaine de destinataire | |
EP3568966B1 (fr) | Procédés et dispositifs de délégation de diffusion de contenus chiffrés | |
EP3854021A1 (fr) | Méthode de traitement confidentiel de logs d'un système d'information | |
WO2018130796A1 (fr) | Procédés et dispositifs de vérification de la validité d'une délégation de diffusion de contenus chiffrés | |
WO2015097357A1 (fr) | Obtention de donnees de connexion a un equipement via un reseau | |
EP2014057A2 (fr) | Identification de noeuds dans un reseau | |
EP3900305A1 (fr) | Procédé d'acquisition d'une chaîne de délégation relative à la résolution d'un identifiant de nom de domaine dans un réseau de communication | |
WO2020128239A1 (fr) | Procédé de détermination d'une chaîne de délégation associée à une résolution d'un nom de domaine dans un réseau de communication | |
FR3015839A1 (fr) | Procede de ralentissement d'une communication dans un reseau | |
EP3149902B1 (fr) | Technique d'obtention d'une politique de routage de requêtes émises par un module logiciel s'exécutant sur un dispositif client | |
US7412599B1 (en) | Administrative remote notification system and method | |
Godra et al. | Practical Approach to Design and Implement a P2P and E2EE Instant Messaging System | |
EP4222632B1 (fr) | Procédé de synchronisation d'une pluralité de serveurs de communications, dispositifs et programmes d'ordinateurs correspondants | |
EP4158872A1 (fr) | Procede de delegation de la livraison de contenus a un serveur cache | |
FR3116921A1 (fr) | Périphérique connecté à un terminal, terminal et serveur configurés pour gérer une preuve de propriété, par le terminal, d’une donnée générée par le périphérique | |
EP4128717A1 (fr) | Délégation d'une fonction de résolution d'identifiants de nommage | |
WO2024047128A1 (fr) | Procédé, dispositif et système de contrôle de la validité d'un message | |
FR2902260A1 (fr) | Verification et correction d'erreurs de donnees d'enregistrement dans un systeme de nommage | |
FR3141020A1 (fr) | Procédé de mise en œuvre d’un service d’une chaîne de services et dispositif électronique associé | |
FR3141021A1 (fr) | Procédé de mise en œuvre d’un service d’une chaîne de services et dispositif électronique associé | |
CN118353685A (zh) | 一种匿名访问控制方法及系统 | |
Trabelsi | Services spontanés sécurisés pour l'informatique diffuse |
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: 20081014 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC MT NL PL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL BA HR MK RS |
|
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 84/18 20090101ALN20090422BHEP Ipc: H04L 29/12 20060101ALN20090422BHEP Ipc: H04L 29/06 20060101ALN20090422BHEP Ipc: H04W 12/10 20090101AFI20090422BHEP |
|
DAX | Request for extension of the european patent (deleted) | ||
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: 20090926 |