Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/2866—Architectures; Arrangements
  • H04L67/30—Profiles
  • H04L67/306—User profiles
• • 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/50—Address allocation
  • H04L61/5007—Internet protocol [IP] addresses
  • H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]

Definitions

• the invention relates to a method for obtaining configuration data for a terminal by using the DHCP protocol. More specifically, the subject of the invention is a method for obtaining configuration data of a terminal as well as a method for processing by a server one or more DHCP requests issued by a DHCP client module of a terminal for obtaining configuration data from said terminal.
• Dynamic Host Configuration Protocol DHCP
• IP Internet Protocol
• This protocol defines a set of requests for establishing a dialogue between, on the one hand, a client module implemented in the terminal and, on the other hand, a server module implemented in the server. These requests are sent either directly from the client module to the server module and vice versa, or through a DHCP relay.
• the DHCP protocol can be used for different types of terminals: PC, router, IP phones, SetTopBox, videophones, video camera, etc., as such a terminal includes a DHCP client module able to communicate with a DHCP server module.
• Such terminals are hereinafter referred to simply as IP terminals.
• DHCP specifies that DHCP requests issued from a given terminal must contain the MAC address of the terminal. This MAC address uniquely identifies the network interface of the terminal, but it is insufficient to determine the nature of the terminal.
• the DHCP protocol furthermore provides that the DHCP requests may contain optional data making it possible to manage the diversity of the terminals or the diversity of the needs of the users of these terminals.
• These optional data are inserted into an option field of the query and include for example:
• Some users may therefore need a static IP address - not a dynamic IP address - that allows them to access a particular service, for example a database that performs user identification. from its IP address and determines the access rights to the database data accordingly.
• a known solution to this type of problem is to manually assign a static IP address to the terminal.
• the disadvantage is that this solution involves the intervention of computer maintenance personnel for each case. In addition, it only works if the need is for a static IP address.
• One of the aims of the invention is to provide a method for obtaining configuration data of a terminal by means of DHCP requests as well as a method for processing such requests, which do not have the drawbacks mentioned above for the previous solutions, which are compatible with the DHCP protocol and allow in particular a configuration data management of different terminals of a network that is fully automated and adaptable to the specific needs of certain users.
• the subject of the invention is a method for obtaining configuration data of a terminal, the terminal comprising a DHCP client module able to communicate via a network with at least one DHCP server module according to the DHCP protocol, the method comprising the following steps:
• DHCP client module generating by said DHCP client module one or more DHCP requests for obtaining configuration data from said terminal, transmission of said one or more DHCP requests via said network by said DHCP client module to said at least one DHCP server module,
• the method further comprising a step of inserting into a predefined option field at least one of the requests DHCP, optional data comprising an associated identifier, directly or indirectly, to a single user of said terminal, the received configuration data being customized for said user.
• the insertion in one of the requests of an identifier, associated with one and only one user of the terminal allows the generation of a response to this request which is personalized for a given user, identified, indirectly or indirectly by the identifier inserted. . In this way, the configuration data can be generated to meet the specific needs of a given user.
• the method makes it possible to envisage a control over the generation of configuration data, and in particular to carry out an identification of the user as soon as he is connected to the network, or even to refuse the assignment of configuration data so as to prevent a user from accessing the network. Securing access to the network therefore occurs at the request of configuration, and is thus reinforced.
• the method additionally provides a practical answer to situations of nomadism in which the same user can connect to a network using each time a different terminal, for example by using a terminal among a plurality of terminals accessible self-service.
• the method is further compatible with DHCP and does not require modification of the basic principles of this protocol.
• the method comprises a step of reading all or part of the optional data in a personal recording medium accessible from the terminal.
• a recording medium is typically a smart card.
• the personal recording medium is a medium whose access is secured by an identification code. This makes it possible to secure access to this identifier and its introduction in the request and reduces the chances of successful fraudulent use of personal recording media.
• the personal recording medium is of the removable media type.
• a user in a situation of mobility can thus bring his removable support to find a suitable and personalized configuration whatever the terminal he uses.
• the personal recording medium is integrated in a mobile terminal and is accessible from said terminal by a local communication link established between said terminal and said mobile terminal.
• This variant avoids the user of a mobile terminal, for example a mobile phone, to provide additional support for the storage of the identifier.
• the identifier can be for example:
• a user profile identifier associated with said user Any type of identifier can thus be used to implement the method according to the invention, it is not necessary to have an identifier of the user himself.
• a registration identifier of a personal recording medium as identifier facilitates the implementation of the method, since such an identifier is pre-existing and databases are available. known mechanisms for processing such identifiers, and if necessary, to determine the identity of the user from such identifiers.
• all or part of the optional data are inserted into the request in encrypted form. This increases the confidentiality of exchanges and limits the chances of successful fraudulent login attempts.
• the invention also relates to a terminal comprising a DHCP client module, suitable for implementing the method according to the invention and comprising
• the subject of the invention is also a method of processing by a server one or more DHCP requests issued by a DHCP client module of a terminal for obtaining configuration data of said terminal, the server comprising a DHCP server module capable of communicating with the DHCP client module via a network according to the DHCP protocol, at least one of said one or more received DHCP requests comprising, in a predefined option field, optional data including an associated identifier, directly or indirectly to a single user of said terminal, the method comprising the steps of
• the configuration data being personalized for said user
• the generated configuration data comprise an IP address whose static or dynamic type is a function of said identifier.
• the method comprises a step of recording for each request comprising said predefined option field tracking data including date and / or time of receipt of said request.
• said predefined option field tracking data including date and / or time of receipt of said request.
• the method comprises steps of determining the identity of said user from said identifier, generating the requested configuration data according to the identity of said user in case of identification of the user, to refuse the generation of the requested configuration data in the case where said user is not identified.
• the invention also relates to a server comprising a DHCP server module, suitable for implementing the processing method according to the invention, and comprising a module for generating said requested configuration data according to said identifier.
• the server comprises a database comprising a list of identifiers, and for each identifier of the data corresponding to a description of the configuration requirements of the user associated with this identifier.
• FIG. 1 is a simplified representation of the invention. architecture of a system for implementing the invention
• FIG. 2 schematically illustrates different phases of the method according to the invention as well as data exchanges between the entities concerned by these different phases.
• the invention is described in the context of its application to a situation in which a customer of a service provider wishes to access services made available through terminals accessing a network.
• the terminals are, in this example, self-service terminals.
• the customer begins by registering with the service provider for certain predefined services.
• the service provider gives him a smart card.
• This smart card contains information about the customer himself (ID
• This terminal has a standard configuration, which is for example a configuration allowing only local use, without a network connection, of this terminal. To allow access to the services subscribed by a given user, it must be configured appropriately, and in particular have a DHCP address to access the services implemented via the network. Thanks to the invention, this terminal can be configured each time according to the identity of the user who connects to the network via this terminal, and this as soon as the connection to the network of the terminal is restored.
• Figure 1 shows in a simplified manner the main elements cooperating in a system of such a terminal.
• the terminal 100 is in communicating via a communication network 50 with a data processing server 200 accessing a database 300.
• the terminal 100 is a microcomputer.
• this terminal can be any type of terminal including a DHCP client module allowing access to the network 50.
• the terminal 100 comprises a network card 1 15 compatible with the communication network 50. It also includes a 125 smart card reader. As a variant, the smart card reader 125 can be, not integrated in the terminal
• the terminal 100 includes various software modules:
• a DHCP client module 1 a driver 140 adapted to the smart card reader, a read module 150 accessing via the driver 140 to the data of the smart card, a data insertion module 170 used in combination with the DHCP client module 1 10,
• the DHCP client module 1 10 of the terminal is adapted to interface with the data insertion module 170.
• Either the DHCP client module 1 10 includes a software interface for communicating or interfacing with the insertion module 170, or it fully integrates the data insertion module 170.
• the smart card acts as a personal recording medium.
• Any other form of personal recording medium capable of storing data can also be envisaged: a USB electronic key connected via a USB port, a SIM card of a mobile phone accessible via a Bluetooth link between the terminal and the telephone, etc.
• the means of access to the recording medium are each adapted to the recording medium used.
• the access to the recording medium is secure so as to prevent fraudulent access to the data it contains or identity theft. This access security usually consists in allowing access to the data of the smart card only after provision of a confidential code.
• the recording medium is a removable chip card type medium so that a given user can easily, even when is in frequent motion, connect from any terminal while finding a configuration appropriate to its needs.
• the data processing server 200 comprises a network interface card 215 compatible with the communication network 50. It also includes a software module called DHCP 210 server module.
• the DHCP client module and the DHCP server module are designed to interact with each other according to the DHCP protocol as defined by the IETF ("Internet Engineering Task Force") in the RFC 2131 standard.
• This protocol defines in particular how a client terminal comprising a DHCP client module obtains its network configuration (its IP address, in general) from a DHCP server including a DHCP server module.
• the requests sent by the client module to the server module are for example:
• DHCP DISCOVER a "DHCP DISCOVER" request by which the client module tests the presence of one or more DHCP servers on the network and requests the establishment of a dialogue with one of these servers;
• DHCP REQUEST a "DHCP REQUEST” request by which the client module requests configuration data from the server that has responded to its previous "DHCP DISCOVER” request; a "DHCP REQUEST RENEWAL” request by which the client module renews its previous “DHCP REQUEST” request.
• DHCP requests issued by a DHCP client module may contain optional data. This data is identified in a DHCP request by an option code. For example, an option code 60 indicates the presence of data identifying the type of terminal.
• an option field provided in the DHCP protocol is used to insert, in the DHCP request sent by the DHCP client module, an option code and data associated with this option code.
• the inserted DHCP option complies with RFC 2489 standard. It is defined by: - an option code, for example code 180,
• a parameter indicating the quantity of data associated with the option for example in the form of a number of characters.
• an option will be named "option 180" or "user option”.
• This predefined option code identifies the option field in which the identifier is inserted and is indicative that the configuration data requested by the client module is to be generated according to said identifier, and more specifically, that they are to be personalized. for the user associated with this identifier.
• the data associated with the option code 180 includes an identifier associated, directly or indirectly, with one and only one user of the terminal 1, 10. Such an identifier makes it possible to determine without ambiguity the identity of the associated user. to this identifier.
• Such an identifier can be, at choice: - an identifier of the user himself, for example his surname, first name;
• an identifier of the user himself in coded form which is attributed to this user and makes it possible to identify him among other users within a given organization; it may be for example an employee identifier assigned to the user in the company for which he works or a customer identifier assigned to the user by a service provider organization of which this user is a customer;
• a smart card registration identifier from which the identity of the user can be determined, the user associated with this identifier being in this case the owner of the smart card; an identifier of the type of telephone number from which the identity of the user can be determined, the user associated with this identifier being in this case the subscriber to the telephone line identified by this number,
• an identifier of an abstract entity associated with a single user for example a user profile identifier associated with this user, etc.
• a predefined option code identifying said option field is preferably used to indicate the presence of such an identifier and to indicate to the request processing module that the requested configuration data are to be customized for the user associated with the request. this identifier.
• Other data can also be inserted into the query. These may or may not be extracted from the smart card. In particular, it may be useful to insert data identifying or describing a user profile. It can indeed be envisaged that a user needs to connect with different types of profiles to the terminal. For example, a user profile includes identification information of the services accessible from the terminal to which this user has subscribed. A User profile can also include information on the conditions of access to these services: time slot, number of access, etc.
• the profile identifier may be the only data item integrated into the option field 180 because it can be used to identify the terminal user if this profile identifier is associated with a user. and only one.
• the database preferably comprises a list of identifiers, and for each identifier of the corresponding data, either information relating to the services subscribed by the user associated with this identifier, or to a description of the configuration requirements of the the user associated with this identifier (type of address, access rights, etc.), or the configuration data themselves (in the case of a static address, it is necessary to memorize it). In this way, the server is thus able, without even knowing the identity of the user, to generate custom configuration data.
• the data inserted in the request and associated with the option code 180 are preferably extracted from the smart card.
• data from different sources for example non-confidential data, can also be inserted into the request.
• Some or all of the data associated with option 180 may be encrypted.
• the encryption of these data can be done, either before insertion of the data in the request, or before recording of the data on the smart card.
• the risks of identity theft are very low, especially if access to the information medium is moreover secure.
• FIG. 2 illustrates the different phases of the method according to the invention as well as the data exchanges carried out during these different phases between the terminal
• this data notably comprises an identifier associated with a user of the terminal 100;
• the reader 120 reads the data requested in the smart card 130 and sends them back to the terminal;
• the server 200 processes the request "DHCP DISCOVER" by accessing S75 if necessary to the database 300; this processing is carried out taking into account all or part of the data read in the card and inserted in the request; the server 200 generates a response that preferably depends on the identifier inserted in the request;
• the terminal 100 generates a request "DHCP REQUEST" and insert all or part of the previously read data in the card;
• the server 200 processes the request "DHCP REQUEST" by accessing S135 if necessary to the database 300;
• the server 200 sends a response to the request "DHCP REQUEST" in the form of a "DHCP ACK" request including an IP address intended for the configuration of the terminal 100;
• the terminal 100 receives the response "DHCP ACK";
• the terminal 100 proceeds to its IP configuration from the IP address returned by the server 200.
• the constitution of a DHCP request by the terminal 100 itself comprises the following steps:
• the DHCP client module 1 10 creates a DHCP request; the DHCP client module 1 10 transfers this request to the insertion module 170;
• the insertion module 170 sends a request to the reading module 150 via the middleware 160 for the extraction of the data from the smart card; the reading module 150 obtains the requested data from the driver 140 of the card reader 120; the reading module 150 sends the requested data to the insertion module 170 via the middleware 160; the insertion module 170 inserts the data in the created DHCP request and the transfer to the DHCP client module 1; the DHCP client module sends the DHCP request to the DHCP server module 210 and waits for its response.
• each generated DHCP request may include an option 180 and associated data.
• the "DHCP DISCOVER” and “DHCP REQUEST” requests contain information on the identity of the user of the terminal. All requests issued by the DHCP client module ("DHCP REQUEST RENEWAL”, “DHCP INFORM” and “DHCP RELEASE”) may contain this information as needed.
• DHCP REQUEST RENEWAL "DHCP INFORM”
• DHCP RELEASE DHCP RELEASE
• step S100 of generating a "DHCP REQUEST” request may require substeps S102 and S103 for access to the smart card and for reading data in the smart card.
• the DHCP server is configured to use the information set in the chosen DHCP option in different ways:
• the service provider can implement billing by user, for example depending on the number of connections or the duration of each connection, the tracking data being crossed with the information linking a customer to a smart card ; - to emit a response that is personalized according to the identity of the user or according to the services this user has subscribed to; for example by generating configuration data according to the identifier and / or the identity of the user.
• the operation considered is a simple record of tracking data, it can optionally be executed after sending the response to the client request.
• the processing by the server 200 of the DHCP request sent by the terminal 100 is performed according to the data of the optional data field. These data comprise an identifier, uniquely associated with the user of the terminal 100. This is in particular an identifier for a unique identification of the user of the terminal 100.
• the DHCP server determines, prior to the processing of the DHCP request, the identity of the user of the terminal 100 and processes the request according to the identity of the user.
• operations such as the recording of tracking data, the processing of the data associated with the request, the access control from the data associated with the request or the generation of the response to the request, can be performed according to the identity of the current user of the terminal 100.
• the step of determining the identity of the user of the terminal can be avoided, if the server is designed to respond to the request solely on the basis of the identifier, especially if the server comprises a database registering the user configuration requirements in association with the identifier.
• the DHCP server identifies from the identifier associated with the user the services subscribed by this user and returns a response (configuration data) that is adapted to the services subscribed.
• the DHCP configuration returned by the server in response to a request "DHCP REQUEST" may be a function of the identifier, and therefore of the identity of this user. It is thus possible to ensure that the type, static or dynamic, of the returned address is also a function of the identity of this user. In the case of example where the user needs a static address, the server will always return a predefined static address tailored to that user's needs.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Small-Scale Networks (AREA)
• Communication Control (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=35825368

Family Applications (1)

Country Status (4)

Families Citing this family (8)

Family Cites Families (5)

• 2005
  • 2005-06-28 FR FR0506572A patent/FR2887723A1/fr active Pending
• 2006
  • 2006-06-22 EP EP06778966A patent/EP1900179A2/de not_active Ceased
  • 2006-06-22 US US11/994,036 patent/US20080279116A1/en not_active Abandoned
  • 2006-06-22 WO PCT/FR2006/050621 patent/WO2007000552A2/fr active Application Filing

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events