WO2016074477A1 - Data processing method, device and system, and computer storage medium - Google Patents

Abstract

Disclosed are a data processing method, device and system, and a computer storage medium. The method comprises: a configuration end determines a service type to be configured for an OID, and generates a resource record corresponding to the service type; store the resource record into a corresponding DNS database; a client acquires a first service type request of an OID application, and generates a query domain name parameter according to a first service type of the OID application and a preset generating rule, the query domain name parameter comprising the first service type; query the corresponding DNS database according to the query domain name parameter, and obtain service configuration information corresponding to the query domain name parameter; and send the service configuration information to the OID application.

Description

Data processing method, device, system and computer storage medium Technical field

The present invention relates to data processing technologies, and in particular, to a data processing method, device, system, and computer storage medium.

Background technique

The object identifier (OID, Object Identifier) is an identification mechanism jointly proposed by the International Organization for Standardization (ISO), the International Electrotechnical Commission (IEC), and the International Telecommunication Union (ITU). Use a hierarchical tree structure to globally unambiguously and uniquely name any type of object. OID has the advantages of layered flexibility, strong scalability, clear management mechanism, and is compatible with existing identification mechanisms. It has been widely used in information security, medical and health, network management and other fields. As of December 2013, the international OID tree 891,938 top OID identifiers have been registered. In recent years, with the development of technologies and industries such as the Internet of Things, there is an urgent need for identity management and information management for a wide variety of objects, and OID has received further attention. Regardless of management mechanism, technical superiority, technology maturity, application promotion, international and domestic standardization, OID is the most suitable solution for object identification management.

The OID coding system is a hierarchical symbology. Correspondingly, in order to solve the unified query problem of the information corresponding to the OID, the International Standards Organization defines an OID Resolution System (ORS), which uses the DNS technology to pass the global OID through the Internet. Organized into a hierarchical database system, in which an upper-level DNS and a lower-level DNS perform an authorized connection through an NS-type resource record. Each DNS saves the service configuration information of the corresponding OID object through the resource record of the NAPTR type.

In the prior art, in the DNS corresponding to an OID object, the same DNS is usually used. The mapping name is used to configure all OID service types, which causes the DNS server to return all service configuration information related to the OID during the OID application parsing process, which causes the following problems:

1. Due to the cache of the DNS, the redundant service data is spread, which will cause the convergence speed to be reduced when the configuration is modified.

2. With the expansion of the OID service type, the DNS query result is also getting larger and larger, and the response package is too large, which makes the client processing more difficult;

3. The DNS system load corresponding to the OID increases.

Summary of the invention

In order to solve the existing technical problems, the embodiments of the present invention provide a data processing method, device, system, and computer storage medium, which can reduce the query load of the DNS and reduce the transmission bearer, cache, and processing capability requirements of the ORS client.

To achieve the above objective, the technical solution of the embodiment of the present invention is implemented as follows:

An embodiment of the present invention provides a data processing method, where the method includes:

The configuration end determines the service type that the object identifier OID needs to be configured, and generates a resource record corresponding to the service type;

The resource record is stored in the corresponding domain name system DNS database.

In another embodiment, the generating the resource record corresponding to the service type includes:

Generating a DNS service mapping name for the service type, where the DNS service mapping name includes at least an OID service name identifier;

Obtaining service configuration information corresponding to the service type;

And generating, according to the DNS service mapping name and the service configuration information, a resource record corresponding to the service type.

In another embodiment, before the determining the type of service that the OID needs to be configured, the method further includes:

Pre-configuring an OID service name identifier, where the OID service name identifier corresponds to the service class type.

The embodiment of the invention further provides a data processing method, the method comprising:

The client obtains the first service type request of the OID application, and generates a query domain name parameter according to the preset generation rule based on the first service type of the OID application; the query domain name parameter includes the first service type;

Querying a corresponding DNS database based on the query domain name parameter, and obtaining service configuration information corresponding to the query domain name parameter;

The service configuration information is sent to the OID application.

In another embodiment, the first service type based on the OID generates a query domain name parameter according to a preset generation rule, including:

The query domain name parameter is generated according to the format of the preset DNS service mapping name based on the first service type of the OID.

In another embodiment, the querying the corresponding DNS database based on the query domain name parameter to obtain the service configuration information corresponding to the query domain name parameter includes:

Determining the DNS corresponding to the query domain name parameter according to the query domain name parameter, and obtaining the resource record corresponding to the query domain name parameter by using the database of the DNS, where the resource record includes service configuration information;

Extracting service configuration information in the resource record.

The embodiment of the invention further provides a data processing method, the method comprising:

The configuration end determines the service type that the object identifier OID needs to be configured, and generates a resource record corresponding to the service type;

Depositing the resource record in a corresponding domain name system DNS database;

The client obtains the first service type request of the OID application, and generates a query domain name parameter according to the preset generation rule based on the first service type of the OID application; the query domain name parameter includes the first service type;

Querying a corresponding DNS database based on the query domain name parameter, and obtaining service configuration information corresponding to the query domain name parameter;

The service configuration information is sent to the OID application.

The embodiment of the present invention further provides a device, where the device is a configuration device, and the configuration device includes: a determining unit, a first generating unit, and a writing unit;

The determining unit is configured to determine a service type that the object identifier OID needs to be configured;

The first generating unit is configured to generate a resource record corresponding to the service type determined by the determining unit;

The writing unit is configured to store the resource record generated by the first generating unit in a corresponding domain name system DNS database.

In another embodiment, the first generating unit is configured to generate a DNS service mapping name for the service type, where the DNS service mapping name includes at least an OID service name identifier, and obtain service configuration information corresponding to the service type. And generating, according to the DNS service mapping name and the service configuration information, a resource record corresponding to the service type.

In another embodiment, the device further includes a configuration unit configured to pre-configure an OID service name identifier, the OID service name identifier corresponding to the service type.

The embodiment of the present invention further provides a device, where the device is a client device, where the client device includes: an acquiring unit, a second generating unit, a querying unit, and a sending unit;

The obtaining unit is configured to obtain a first service type request of the OID application;

The second generating unit is configured to generate a query domain name parameter according to a preset generation rule according to the first service type of the OID application acquired by the acquiring unit, where the query domain name parameter includes the first service type;

The querying unit is configured to query the corresponding DNS database based on the query domain name parameter generated by the second generating unit, and obtain service configuration information corresponding to the query domain name parameter;

The sending unit is configured to send the service configuration information obtained by the query unit To the OID application.

In another embodiment, the second generating unit is configured to generate a query domain name parameter in a format of a preset DNS service mapping name based on the first service type of the OID.

In another embodiment, the querying unit is configured to determine a DNS corresponding to the query domain name parameter according to the query domain name parameter, and obtain a resource record corresponding to the query domain name parameter by using the database of the DNS, where the resource is The record includes service configuration information; and the service configuration information in the resource record is extracted.

The embodiment of the present invention further provides a data processing system, where the system includes: a configuration end device and a client device;

The configuration end device is configured to determine a service type that needs to be configured by the object identifier OID, and generate a resource record corresponding to the service type; and store the resource record in a corresponding domain name system DNS database;

The client device is configured to obtain a first service type request to the OID application, and generate a query domain name parameter according to a preset generation rule according to the first service type of the OID application; the query domain name parameter includes the first service Querying the corresponding DNS database based on the query domain name parameter, and obtaining the service configuration information corresponding to the query domain name parameter; and sending the service configuration information to the OID application.

The embodiment of the invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the data processing method applied to the configuration end according to the embodiment of the invention.

The embodiment of the invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the data processing method applied to the client according to the embodiment of the invention.

The data processing method, the device, the system, and the computer storage medium provided by the embodiment of the present invention determine the service type that the OID needs to be configured by the configuration end, and generate the resource corresponding to the service type. Recording; storing the resource record in the corresponding DNS database; the client obtains the first service type request of the OID application, and generates a query domain name parameter according to the preset generation rule based on the first service type of the OID application; Querying the domain name parameter includes the first service type; querying the corresponding DNS database based on the query domain name parameter, obtaining service configuration information corresponding to the query domain name parameter; and sending the service configuration information to the OID application. According to the technical solution of the embodiment of the present invention, different DNS service mapping names are generated by using different service types of the OID, and the DNS server does not need to return all the service configuration information related to the OID. On the one hand, the query load of the DNS is greatly reduced, and the query load is improved. On the other hand, because the query result is relatively small, the transmission and processing are convenient, which greatly reduces the transmission bearer, cache, and processing capability requirements of the ORS client. The applicability and scalability are stronger. faster.

DRAWINGS

1 is a schematic flowchart of a data processing method according to Embodiment 1 of the present invention;

2 is a schematic flowchart of a data processing method according to Embodiment 2 of the present invention;

3 is a schematic flowchart of a data processing method according to Embodiment 3 of the present invention;

4 is a schematic structural diagram of a data processing system according to Embodiment 4 of the present invention;

5 is a schematic structural diagram of a device according to Embodiment 5 of the present invention;

6 is a schematic structural diagram of a device according to Embodiment 6 of the present invention;

FIG. 7 is a schematic flowchart diagram of a data processing method according to Embodiment 7 of the present invention.

detailed description

The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

Embodiment 1

The embodiment of the invention provides a data processing method, and the data processing method is applied to the configuration end side. 1 is a schematic flowchart of a data processing method according to Embodiment 1 of the present invention; as shown in FIG. 1, the data processing method includes:

Step 101: The configuration end determines an object identifier (OID) that needs to be configured, and generates a resource record corresponding to the service type.

Here, before the determining the type of service that the OID needs to be configured, the method further includes:

The OID service name identifier is pre-configured, and the OID service name identifier corresponds to the service type.

In this embodiment, the configuration end determines N service types that need to be configured for the OID, where N is a positive integer. Correspondingly, the configuration end pre-configures N OID service name identifiers, and the N OID service name identifiers correspond to the N service types.

Specifically, in an actual application, the OID service name identifier and the corresponding service type may be as shown in Table 1, and are of course not limited to the service type and the corresponding service name identifier shown in Table 1. The configured OID service name identifier is different from other configuration identifiers in the DNS, that is, the OID service name identifier and other configuration identifiers in the DNS are not duplicated to avoid conflicts.

Service type	OID service name identifier
		Formal OID service	COID
Registration information service	RINF
		Object information service	OINF
Sub OID list service	CINF
		Child node allocation scheme service	COAS
Module information service	MINF
		......	......

Table 1

In the actual application, the configurator does not need to configure the OID service name identifier corresponding to all service types as shown in Table 1 for each OID. The service type of the OID needs to be configured according to the OID requirements, and is configured according to different OIDs. The service type generates a resource record corresponding to the service type.

In this step, the generating the resource record corresponding to the service type includes:

Generating a DNS service mapping name for the service type, where the DNS service mapping name includes at least an OID service name identifier;

Obtaining service configuration information corresponding to the service type;

And generating, according to the DNS service mapping name and the service configuration information, a resource record corresponding to the service type.

Specifically, in this embodiment, each DNS service mapping name represents a service type; each service type may correspond to at least one resource record, that is, the DNS service mapping name corresponding to the service type and And the service configuration information, the resource record corresponding to the service type is generated, and at least one resource record corresponding to the service type is generated according to the DNS service mapping name and the service configuration information corresponding to the service type.

The DNS service mapping name is represented by the owner name field in the resource record, and is configured to distinguish different service types of the OID in the DNS. Specifically, the DNS service mapping name may be in the following format:

DNS service mapping name = OID service name identifier. + dot-notation OID. + OID resolution system DNS root.

The OID service name identifier may be a host identifier or a sub-domain identifier, and the OID service name identifier is different from other configuration identifiers in the DNS, that is, the OID service name identifier and other configurations in the DNS. The logo is not duplicated.

Specifically, the OID service name identifier is specifically an OID service name identifier, such as COID, RINF, OINF, and the like, as shown in Table 1. The domain name is determined by taking an OID of 1.2.156.102.8 as an example. The reverse order is 8.102.156.2.1; the OID resolution system DNS root can be represented by "oid-res.org.", which represents the root position of the ORS system in the DNS. Of course, the OID resolution system DNS root can also be configured as Other values.

Specifically, the service configuration information in the resource record may be through an IN NAPTR type resource. Source record representation. The IN NAPTR represents a service record information of a resource record storing an OID object using Class=IN, Type=NAPTR in the DNS, and the service configuration information may be embodied by an RDATA field in the resource record.

The RDATA field includes at least a regular expression field, where the regular expression field is configured to store specific service configuration information of the OID object, and the service configuration information may be a uniform resource locator (URL, Uniform Resource Locator). ) Address and so on.

Step 102: Store the resource record in a corresponding domain name system DNS database.

Specifically, the OID is set to 1.2.156.102.8, the service type to be configured is COID, and the corresponding DNS is 202.202.1.102. The COID service is configured for the OID and stored in the DNS. In the database, the resource records of the data entry of the DNS are as follows:

coid.8.102.156.2.1.oid-res.org.IN NAPTR 0 100"u""ORS+OINF""!^.*$!/1/2/156/102/8!".

The owner name field in the resource record is “coid.8.102.156.2.1.oid-res.org.”, the owner name field is a DNS service mapping name, and “IN NAPTR” indicates a resource record storage OID. The service configuration information of the object; the specific service configuration information may be embodied by the RDATA field in the resource record, and the RDATA field is specifically “0 100"u""ORS+OINF""! ^.*$! /1/2/156/102/8! ".".

The fields included in the RDATA field and the corresponding field assignments are as shown in Table 2:

Table 2

The regular expression field is configured to store specific service configuration information of the OID object, and the service configuration information may specifically be a URL address or the like.

An embodiment of the present invention further provides a computer storage medium, where the computer storage medium The computer executable instructions are stored for executing the data processing method applied to the configuration end according to the embodiment of the present invention.

The technical solution provided in this embodiment generates different DNS service mapping names by using different service types of the OID, so that when querying the specific service of the OID application, the DNS server does not need to return all the service configuration information related to the OID, on the one hand, The query load of the DNS is reduced, and the configuration convergence speed is improved. On the other hand, since the query result is relatively small, the transmission and processing processes are relatively convenient, and the transmission bearer, cache, and processing capability requirements of the ORS client are greatly reduced, and the applicability and More extensibility, faster convergence after modifying the configuration.

Embodiment 2

The embodiment of the invention further provides a data processing method, and the data processing method is applied to a client side. 2 is a schematic flowchart of a data processing method according to Embodiment 2 of the present invention; as shown in FIG. 2, the data processing method includes:

Step 201: The client obtains the first service type request of the OID application, and generates a query domain name parameter according to the preset generation rule based on the first service type of the OID application; the query domain name parameter includes the first service type.

In this embodiment, the client knows all the service types and the corresponding OID service name identifiers in advance. The service type and the corresponding OID service name identifiers are as shown in Table 1, and are not described here.

The first service type request is a service type request corresponding to any one of the service types that are known in advance.

In this embodiment, the client has pre-configured a DNS service mapping name generation rule; the query domain name parameter in the embodiment is the DNS service mapping name. Correspondingly, the first service type based on the OID in the step is configured to generate a query domain name parameter according to a preset generation rule, including:

Generating a check based on a format of a preset DNS service map name based on the first service type of the OID Ask for domain name parameters.

The DNS service mapping name may be in the following format:

DNS service mapping name = OID service name identifier. + dot-notation OID. + OID resolution system DNS root.

Specifically, the OID is 1.2.156.102.8, and the first service type is the COID. The query domain name parameter can be generated as: coid.8.102.156.2.1. Oid-res.org.

Step 202: Query the corresponding DNS database based on the query domain name parameter, and obtain service configuration information corresponding to the query domain name parameter.

Here, the querying the corresponding DNS database based on the query domain name parameter, and obtaining the service configuration information corresponding to the query domain name parameter, includes:

Determining, according to the query domain name parameter, the DNS corresponding to the query domain name parameter, obtaining a resource record corresponding to the query domain name parameter by using the database of the DNS, where the resource record includes service configuration information; and extracting the resource record Service configuration information.

Specifically, after obtaining the query domain name parameter, the client initiates a DNS query by using CLASS=IN, TYPE=NAPTR as a query condition, that is, sending a DNS NAPTR query request, where the DNS NAPTR query request includes the query domain name. parameter. In this embodiment, the DNS NAPTR query request is sent to the DNS; the DNS obtains the DNS service mapping name of the first service type of the OID in the corresponding DNS database according to the query domain name, named owner name. The resource record of the field, and the service configuration information is extracted from the resource record.

Step 203: Send the service configuration information to the OID application.

Here, the service configuration information may specifically be a URL address or the like. After the OID application obtains the service configuration information, the OID service may be accessed according to the service configuration information (specifically, a URL address).

The embodiment of the invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the data processing method applied to the client according to the embodiment of the invention.

In the technical solution provided by the embodiment, different DNS service mapping names are generated in advance by using different service types of the OID, so that when the specific service of the OID application is queried, the DNS server does not need to return all service configuration information related to the OID. The query load of the DNS is greatly reduced, and the configuration convergence speed is improved. On the other hand, since the query result is relatively small, the transmission and processing processes are relatively convenient, and the transmission bearer, cache, and processing capability requirements of the ORS client are greatly reduced, and the applicability is adopted. It is more scalable and converges faster after modifying the configuration.

Embodiment 3

The embodiment of the invention also provides a data processing method. 3 is a schematic flowchart of a data processing method according to Embodiment 3 of the present invention; as shown in FIG. 3, the data processing method includes:

Step 301: The configuration end determines the service type that the OID needs to be configured, and generates a resource record corresponding to the service type.

Here, before the determining the object identifier OID needs to be configured, the method further includes:

The OID service name identifier is pre-configured, and the OID service name identifier corresponds to the service type.

In this embodiment, the configuration end determines N service types that need to be configured for the OID, where N is a positive integer. Correspondingly, the configuration end pre-configures N OID service name identifiers, and the N OID service name identifiers correspond to the N service types.

Specifically, in the actual application, the OID service name identifier and the corresponding service type may be as shown in Table 1, and are not limited to the service type and the corresponding service name identifier shown in Table 1, and details are not described herein again. The configured OID service name identifier is different from other configuration identifiers in the DNS, that is, the OID service name identifier and other configuration identifiers in the DNS are not duplicated. In order to avoid conflicts.

In the actual application, the configurator does not need to configure the OID service name identifier corresponding to all service types as shown in Table 1 for each OID. The service type of the OID needs to be configured according to the OID requirements, and is configured according to different OIDs. The service type generates a resource record corresponding to the service type.

In this step, the generating the resource record corresponding to the service type includes:

Generating a DNS service mapping name for the service type, where the DNS service mapping name includes at least an OID service name identifier;

Obtaining service configuration information corresponding to the service type;

And generating, according to the DNS service mapping name and the service configuration information, a resource record corresponding to the service type.

Specifically, in this embodiment, each DNS service mapping name represents a service type; each service type may correspond to at least one resource record, that is, the DNS service mapping name corresponding to the service type and And the service configuration information, the resource record corresponding to the service type is generated, and at least one resource record corresponding to the service type is generated according to the DNS service mapping name and the service configuration information corresponding to the service type.

The DNS service mapping name is represented by the owner name field in the resource record, and is configured to distinguish different service types of the OID in the DNS. Specifically, the DNS service mapping name may be in the following format:

DNS service mapping name = OID service name identifier. + dot-notation OID. + OID resolution system DNS root.

The OID service name identifier may be a host identifier or a sub-domain identifier, and the OID service name identifier is different from other configuration identifiers in the DNS, that is, the OID service name identifier and other configurations in the DNS. The logo is not duplicated.

Specifically, the OID service name identifier is specifically an OID service name label shown in Table 1. For example, COID, RINF, OINF, etc.; taking the OID to be configured as 1.2.156.102.8 as an example, the domain name is reversed to 8.102.156.2.1. The DNS root of the OID resolution system can be represented by "oid-res.org.", which represents the root position of the ORS system in the DNS. Of course, the DNS root of the OID resolution system can also be configured to other values.

Specifically, the service configuration information in the resource record may be represented by a resource record of an IN NAPTR type. The IN NAPTR represents a service record information of a resource record storing an OID object using Class=IN, Type=NAPTR in the DNS, and the service configuration information may be embodied by an RDATA field in the resource record.

The RDATA field further includes a regular expression field, where the regular expression field is configured to store specific service configuration information of the OID object, and the service configuration information may specifically be a URL address or the like.

Step 302: Store the resource record in a corresponding DNS database.

Specifically, the OID is set to 1.2.156.102.8, the service type to be configured is COID, and the corresponding DNS is 202.202.1.102. The COID service is configured for the OID and stored in the DNS. In the database, the resource records of the data entry of the DNS are as follows:

coid.8.102.156.2.1.oid-res.org.IN NAPTR 0 100"u""ORS+OINF""!^.*$!/1/2/156/102/8!".

The owner name field in the resource record is “coid.8.102.156.2.1.oid-res.org.”, the owner name field is a DNS service mapping name, and “IN NAPTR” indicates a resource record storage OID. The service configuration information of the object; the specific service configuration information may be embodied by the RDATA field in the resource record, and the RDATA field is specifically “0 100"u""ORS+OINF""! ^.*$! /1/2/156/102/8! ".".

The fields included in the RDATA field and the corresponding field assignments are as shown in Table 2, and are not described here.

Step 303: The client obtains the first service type request of the OID application, and generates a query domain name parameter according to the preset generation rule according to the first service type of the OID application; The number includes the first service type.

In this embodiment, the client knows all the service types and the corresponding OID service name identifiers in advance. The service type and the corresponding OID service name identifiers are as shown in Table 1, and are not described here.

In this embodiment, the client has pre-configured a DNS service mapping name generation rule; the query domain name parameter in the embodiment is the DNS service mapping name. Correspondingly, the first service type based on the OID in the step is configured to generate a query domain name parameter according to a preset generation rule, including:

The query domain name parameter is generated according to the format of the preset DNS service mapping name based on the first service type of the OID.

The DNS service mapping name may be in the following format:

DNS service mapping name = OID service name identifier. + dot-notation OID. + OID resolution system DNS root.

Specifically, the OID is 1.2.156.102.8, and the first service type is the COID. The query domain name parameter can be generated as: coid.8.102.156.2.1. Oid-res.org.

Step 304: Query the corresponding DNS database based on the query domain name parameter, and obtain service configuration information corresponding to the query domain name parameter.

Here, the querying the corresponding DNS database based on the query domain name parameter to obtain the service configuration information corresponding to the query domain name includes:

Determining, according to the query domain name parameter, the DNS corresponding to the query domain name parameter, obtaining a resource record corresponding to the query domain name parameter by using the database of the DNS, where the resource record includes service configuration information; and extracting the resource record Service configuration information.

Specifically, after obtaining the query domain name parameter, the client uses CLASS=IN, TYPE=NAPTR as a query condition, and initiates a DNS query, that is, sends a DNS NAPTR query. The request includes the query domain name parameter in the DNS NAPTR query request. In this embodiment, the DNS NAPTR query request is sent to the DNS, and the DNS obtains the DNS service mapping name of the first service type of the OID in the corresponding DNS database according to the query domain name. The resource record of the field, and the service configuration information is extracted from the resource record.

Step 305: Send the service configuration information to the OID application.

Here, the service configuration information may specifically be a URL address or the like. After the OID application obtains the service configuration information, the OID service may be accessed according to the service configuration information (specifically, a URL address).

The technical solution provided by the embodiment of the present invention generates different DNS service mapping names by using different service types of the OID, and does not need to cause the DNS server to return all service configuration information related to the OID. On the one hand, the query load of the DNS is greatly reduced, and the query is improved. On the other hand, because the query result is relatively small, the transmission and processing are convenient, which greatly reduces the transmission bearer, cache, and processing capability requirements of the ORS client. The applicability and scalability are stronger. faster.

Embodiment 4

The embodiment of the invention also provides a data processing system. 4 is a schematic structural diagram of a data processing system according to Embodiment 4 of the present invention; as shown in FIG. 4, the system includes: a configuration end device 41 and a client device 42;

The configuration end device 41 is configured to determine a service type that the OID needs to be configured, and generate a resource record corresponding to the service type; and store the resource record in the corresponding DNS database 43;

The client device 42 is configured to obtain a first service type request of the OID application, and generate a query domain name parameter according to a preset generation rule according to the first service type of the OID application; the query domain name parameter includes the first Querying the corresponding DNS database 43 based on the query domain name parameter, and obtaining service configuration information corresponding to the query domain name parameter; Configuration information is sent to the OID application.

Here, the service type of the OID includes N, and N is a positive integer. In the actual application, the configurator does not need to configure the OID service name identifier corresponding to all service types as shown in Table 1 for each OID. The service type of the OID needs to be configured according to the OID requirements, and is configured according to different OIDs. The service type generates a resource record corresponding to the service type.

In another embodiment, the configuration end device 41 is configured to generate a DNS service mapping name for the service type, where the DNS service mapping name includes at least an OID service name identifier, and obtain service configuration information corresponding to the service type. And generating, according to the DNS service mapping name and the service configuration information, a resource record corresponding to the service type.

In this embodiment, each DNS service mapping name represents a service type; each service type may correspond to at least one resource record, that is, the DNS service mapping name and the service corresponding to the service type. The configuration information is generated, and the resource record corresponding to the service type is generated, and at least one resource record corresponding to the service type is generated according to the DNS service mapping name and the service configuration information corresponding to the service type.

The DNS service mapping name is represented by the owner name field in the resource record, and is configured to distinguish different service types of the OID in the DNS. Specifically, the DNS service mapping name may be in the following format:

DNS service mapping name = OID service name identifier. + dot-notation OID. + OID resolution system DNS root.

The OID service name identifier may be a host identifier or a sub-domain identifier, and the OID service name identifier is different from other configuration identifiers in the DNS, that is, the OID service name identifier and other configurations in the DNS. The logo is not duplicated.

Specifically, the OID service name identifier is specifically an OID service name identifier, such as COID, RINF, OINF, and the like, as shown in Table 1. The domain name is determined by taking an OID of 1.2.156.102.8 as an example. The reverse order is 8.102.156.2.1; the OID resolution system DNS root can be used "oid-res.org." indicates that it represents the root position of the ORS system in the DNS. Of course, the OID resolution system DNS root can also be configured to other values.

Specifically, the service configuration information in the resource record may be represented by a resource record of an IN NAPTR type. The IN NAPTR represents a service record information of a resource record storing an OID object using Class=IN, Type=NAPTR in the DNS, and the service configuration information may be embodied by an RDATA field in the resource record.

The RDATA field further includes a regular expression field, where the regular expression field is configured to store specific service configuration information of the OID object, and the service configuration information may specifically be a URL address or the like.

In this embodiment, the client device 42 knows all the service types and the corresponding OID service name identifiers in advance. The service type and the corresponding OID service name identifiers are as shown in Table 1, and are not described here.

In this embodiment, the client device 42 has pre-configured a DNS service mapping name generation rule; the query domain name parameter described in this embodiment is the DNS service mapping name.

In another embodiment, the configuration end device 41 is further configured to pre-configure an OID service name identifier before the object identifier OID needs to be configured, and the OID service name identifier corresponds to the service type.

In this embodiment, the configuration end determines N service types that need to be configured for the OID, where N is a positive integer. Correspondingly, the configuration end pre-configures N OID service name identifiers, and the N OID service name identifiers correspond to the N service types.

The OID service name identifier is pre-configured in the configuration end device 41, and the OID service name identifier is corresponding to the service type. The OID service name identifier and the corresponding service type may be as shown in Table 1, and details are not described herein again. Of course, the OID service name identifier and the corresponding service type are not limited to the service type and the corresponding service name identifier shown in Table 1. The configured OID service name identifier is different from other configuration identifiers in the DNS, that is, the OID service name identifier and Other configuration identifiers in the DNS are not duplicated to avoid conflicts.

The client device 42 is configured to generate a query domain name parameter according to a format of a preset DNS service mapping name based on the first service type of the OID.

The DNS service mapping name may be in the following format:

DNS service mapping name = OID service name identifier. + dot-notation OID. + OID resolution system DNS root.

Specifically, the OID is 1.2.156.102.8, and the first service type is the COID. The query domain name parameter can be generated as: coid.8.102.156.2.1. Oid-res.org.

The client device 42 is configured to determine, according to the query domain name parameter, the DNS 44 corresponding to the query domain name parameter, and obtain the resource record corresponding to the query domain name parameter by using the database 43 of the DNS 44, where the resource record is Include service configuration information; extract service configuration information in the resource record.

Specifically, after obtaining the query domain name parameter, the client device 42 initiates a DNS query by using CLASS=IN, TYPE=NAPTR as a query condition, that is, sending a DNS NAPTR query request, where the DNS NAPTR query request includes the Query the domain name parameters. In this embodiment, the DNS NAPTR query request is sent to the DNS, and the DNS obtains the DNS of the first service type of the OID in the DNS database 43 corresponding to the DNS 44 according to the query domain name parameter. The service maps a resource record named owner name field, and extracts service configuration information from the resource record.

Embodiment 5

An embodiment of the present invention further provides a device, where the device is a configuration end device. 5 is a schematic structural diagram of a device according to Embodiment 5 of the present invention; as shown in FIG. 5, the configuration end device includes: a determining unit 411, a first generating unit 412, and a writing unit 413;

The determining unit 411 is configured to determine a service type that the object identifier OID needs to be configured;

The first generating unit 412 is configured to generate a resource record corresponding to the service type determined by the determining unit 411;

The writing unit 413 is configured to store the resource record generated by the first generating unit 412 in a corresponding DNS database.

In another embodiment, the first generating unit 412 is configured to generate a DNS service mapping name for the service type, where the DNS service mapping name includes at least an OID service name identifier, and obtain a service configuration corresponding to the service type. And generating, according to the DNS service mapping name and the service configuration information, a resource record corresponding to the service type.

In another embodiment, the device further includes a configuration unit 414 configured to pre-configure an OID service name identifier, the OID service name identifier corresponding to the service type.

In this embodiment, the determining unit 411, the first generating unit 412, and the configuring unit 414 in the configuration end device may be processed by a central processing unit (CPU, Central Processing Unit) and digital signal in the device in an actual application. The DSP (Digital Signal Processor) or the Field-Programmable Gate Array (FPGA) is implemented; the writing unit 413 can be implemented by a transmitter or a transmitter in the device in practical applications.

Embodiment 6

The embodiment of the invention further provides a device, which is a client device. FIG. 6 is a schematic structural diagram of a device according to Embodiment 6 of the present invention; as shown in FIG. 6, the configuration end device includes: an obtaining unit 421, a second generating unit 422, a query unit 423, and a sending unit 424;

The obtaining unit 421 is configured to obtain a first service type request of the OID application;

The second generating unit 422 is configured to generate a query domain name parameter according to a preset generation rule according to the first service type of the OID application acquired by the acquiring unit 421; the query domain name parameter includes the first service type;

The query unit 423 is configured to be based on the query generated by the second generating unit 422 The domain name parameter queries the corresponding DNS database, and obtains service configuration information corresponding to the query domain name;

The sending unit 424 is configured to send the service configuration information obtained by the query unit 423 to the OID application.

In another embodiment, the second generating unit 422 is configured to generate a query domain name parameter in a format of a preset DNS service mapping name based on the first service type of the OID.

In another embodiment, the query unit 423 is configured to determine a DNS corresponding to the query domain name parameter according to the query domain name parameter, and obtain a resource record corresponding to the query domain name parameter by using the database of the DNS, The resource record includes service configuration information; and the service configuration information in the resource record is extracted.

In the embodiment, the second generating unit 422 in the client device may be implemented by a CPU, a DSP or an FPGA in the device in an actual application; the query unit 423 and the sending unit 424 may be used in an actual application. The transmitter or transmitter in the device is implemented; in an actual application, the acquisition unit 421 can be implemented by a receiver or receiver in the device.

Example 7

This embodiment describes the present invention in further detail in conjunction with specific embodiments in a specific application scenario. The specific application scenario of the embodiment is that the authorized institution is a winery, the OID node is: 1.2.156.102, the corresponding DNS is 202.202.1.102, and the to-be-configured OID is 1.2.156.102.8. The service type to be configured is: COID, RINF, OINF; in the above application scenario, FIG. 7 is a schematic flowchart of a data processing method according to Embodiment 7 of the present invention. As shown in FIG. 7, the data processing method includes:

Step 701: The configuration end reserves N OID service name identifiers, where N is a positive integer.

Here, the N OID service name identifiers may be specifically shown in Table 1, and are not described herein again.

Step 702: The configuration end configures three service types of services for the OID to be configured, generates three resource records corresponding to the three service types, and writes the three resource records into the corresponding DNS database.

In this embodiment, the configuration end configures three service types of services for the OID to be configured, and generates three resource records corresponding to the three service types, that is, each service type corresponds to one resource record; Each service type is not limited to one resource record, and each service type may correspond to M resource records, and M is a positive integer.

The DNS service mapping name is represented by the owner name field in the resource record, and is configured to distinguish different service types of the OID in the DNS. Specifically, the DNS service mapping name may be in the following format:

DNS service mapping name = OID service name identifier. + dot-notation OID. + OID resolution system DNS root.

The OID service name identifier may be a host identifier or a sub-domain identifier, and the OID service name identifier is different from other configuration identifiers in the DNS, that is, the OID service name identifier and other configurations in the DNS. The logo is not duplicated.

The DNS root of the OID resolution system can be represented by "oid-res.org.", which represents the root position of the ORS system in the DNS. Of course, the DNS root of the OID resolution system can also be configured to other values.

The service configuration information in the resource record may be represented by a resource record of the IN NAPTR type. The IN NAPTR represents a service record information of a resource record storing an OID object using Class=IN, Type=NAPTR in the DNS, and the service configuration information may be embodied by an RDATA field in the resource record.

The RDATA field further includes a regular expression field, where the regular expression field is configured to store specific service configuration information of the OID object, and the service configuration information may specifically be a URL address or the like.

Specifically, the to-be-configured OID is 1.2.156.102.8, and the service type to be configured is: COID, RINF, OINF, and the corresponding DNS is 202.202.1.102, and the resource records in the DNS database are as follows:

coid.8.102.156.2.1.oid-res.org.IN NAPTR 0 100"u""ORS+OINF" "!^.*$!/1/2/156/102/8!".;

rinf.8.102.156.2.1.oid-res.org.IN NAPTR 0 100"u""ORS+RINF""!^.*$!http://www.maotai.com/oid/rinf-1.2.156.102 .8.xml!".;

oinf.8.102.156.2.1.oid-res.org.IN NAPTR 0 100"u""ORS+OINF""!^.*$!http://www.maotai.com/oid/oinf-1.2.156.102 .8.xml!".;

Taking the COID service type as an example, the owner name field in the resource record of the COID service type is "coid.8.102.156.2.1.oid-res.org.", and the owner name field is the DNS service. The name of the mapping; "IN NAPTR" indicates that the resource record stores the service configuration information of the OID object; the specific service configuration information may be represented by the RDATA field in the resource record, and the RDATA field is specifically "0 100"u""ORS+ OINF""! ^.*$! /1/2/156/102/8! ".".

Step 703: The client receives an instruction to query the OINF information of the OID, and generates a query domain name parameter.

In this embodiment, the client knows all the service types and the corresponding OID service name identifiers in advance. The service type and the corresponding OID service name identifiers are as shown in Table 1, and are not described here.

In this embodiment, the client has pre-configured a DNS service mapping name generation rule; the query domain name parameter in the embodiment is the DNS service mapping name.

The DNS service mapping name may be in the following format:

DNS service mapping name = OID service name identifier. + dot-notation OID. + OID resolution system DNS root.

Based on the application scenario described in this embodiment, the query domain name parameter corresponding to the COID service type is generated as: coid.8.102.156.2.1.oid-res.org.

Step 704: The client is directed to the DNS corresponding to the query domain name parameter according to the query domain name parameter, and obtains the resource record corresponding to the query domain name parameter by using the database corresponding to the DNS.

Step 705: The client extracts the service configuration information in the resource record, and sends the service configuration information to the OID application, so that the OID application can perform subsequent processing according to the service configuration information.

Specifically, after obtaining the query domain name parameter, the client initiates a DNS query by using CLASS=IN, TYPE=NAPTR as a query condition, that is, sending a DNS NAPTR query request, where the DNS NAPTR query request includes the query domain name. parameter. In this embodiment, the DNS NAPTR query request is sent to the DNS, and the DNS obtains the resource record named the owner name field of the first service type of the OID according to the query domain name parameter. The service configuration information is extracted from the resource record.

The technical solution provided by the embodiment of the present invention generates different DNS service mapping names by using different service types of the OID, and does not need to cause the DNS server to return all service configuration information related to the OID. On the one hand, the query load of the DNS is greatly reduced, and the query is improved. On the other hand, because the query result is relatively small, the transmission and processing are convenient, which greatly reduces the transmission bearer, cache, and processing capability requirements of the ORS client. The applicability and scalability are stronger. faster.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, such as: multiple units or components may be combined, or Can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, or direct coupling, or communication connection of the components shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical, mechanical or other forms. of.

The units described above as separate components may or may not be physically separated, and the components displayed as the unit may or may not be physical units, that is, may be located in one place or distributed to multiple network units; You can choose some of them according to your actual needs. Or all of the units to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing module, or each unit may be separately used as one unit, or two or more units may be integrated into one unit; the above integration The unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to the program instructions. The foregoing program may be stored in a computer readable storage medium, and the program is executed when executed. The foregoing storage medium includes: a mobile storage device, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. A medium that can store program code.

The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the appended claims.

Industrial applicability

The embodiment of the present invention generates different DNS service mapping names by using different service types of the OID, and does not need to cause the DNS server to return all service configuration information related to the OID. On the one hand, the query load of the DNS is greatly reduced, and the configuration convergence speed is improved; On the one hand, because the query result is relatively small, the transmission and processing are more convenient, which greatly reduces the transmission bearer, cache and processing capability requirements of the ORS client, and the applicability and scalability are stronger, and the convergence speed is faster after the configuration is modified.

Claims (16)

1. A data processing method, the method comprising:

   The configuration end determines the service type that the object identifier OID needs to be configured, and generates a resource record corresponding to the service type;

   The resource record is stored in the corresponding domain name system DNS database.
2. The method of claim 1, wherein the generating the resource record corresponding to the service type comprises:

   Generating a DNS service mapping name for the service type, where the DNS service mapping name includes at least an OID service name identifier;

   Obtaining service configuration information corresponding to the service type;

   And generating, according to the DNS service mapping name and the service configuration information, a resource record corresponding to the service type.
3. The method of claim 2, wherein before the determining the type of service that the OID needs to be configured, the method further comprises:

   The OID service name identifier is pre-configured, and the OID service name identifier corresponds to the service type.
4. A data processing method, the method comprising:

   The client obtains the first service type request of the OID application, and generates a query domain name parameter according to the preset generation rule based on the first service type of the OID application; the query domain name parameter includes the first service type;

   Querying a corresponding DNS database based on the query domain name parameter, and obtaining service configuration information corresponding to the query domain name parameter;

   The service configuration information is sent to the OID application.
5. The method according to claim 4, wherein the generating the query domain name parameter according to the preset generation rule by using the first service type of the OID comprises:

   The query domain name parameter is generated according to the format of the preset DNS service mapping name based on the first service type of the OID.
6. The method according to claim 4, wherein the querying the corresponding DNS database based on the query domain name parameter to obtain the service configuration information corresponding to the query domain name parameter includes:

   Determining the DNS corresponding to the query domain name parameter according to the query domain name parameter, and obtaining the resource record corresponding to the query domain name parameter by using the database of the DNS, where the resource record includes service configuration information;

   Extracting service configuration information in the resource record.
7. A data processing method, the method comprising:

   The configuration end determines the service type that the object identifier OID needs to be configured, and generates a resource record corresponding to the service type;

   Depositing the resource record in a corresponding domain name system DNS database;

   The client obtains the first service type request of the OID application, and generates a query domain name parameter according to the preset generation rule based on the first service type of the OID application; the query domain name parameter includes the first service type;

   Querying a corresponding DNS database based on the query domain name parameter, and obtaining service configuration information corresponding to the query domain name parameter;

   The service configuration information is sent to the OID application.
8. An apparatus, the device is a configuration end device, and the configuration end device includes: a determining unit, a first generating unit, and a writing unit; wherein

   The determining unit is configured to determine a service type that the object identifier OID needs to be configured;

   The first generating unit is configured to generate a resource record corresponding to the service type determined by the determining unit;

   The writing unit is configured to store the resource record generated by the first generating unit in a corresponding domain name system DNS database.
9. The device according to claim 8, wherein the first generating unit is configured to generate a DNS service mapping name for the service type, the DNS service mapping name includes at least an OID service name identifier, and obtain the service type corresponding to The service configuration information is generated, and the resource record corresponding to the service type is generated according to the DNS service mapping name and the service configuration information.
10. The device according to claim 9, wherein the device further comprises a configuration unit configured to pre-configure an OID service name identifier, the OID service name identifier corresponding to the service type.
11. A device, the device is a client device, and the client device includes: an obtaining unit, a second generating unit, a query unit, and a sending unit;

    The obtaining unit is configured to obtain a first service type request of the OID application;

    The second generating unit is configured to generate a query domain name parameter according to a preset generation rule according to the first service type of the OID application acquired by the acquiring unit, where the query domain name parameter includes the first service type;

    The querying unit is configured to query the corresponding DNS database based on the query domain name parameter generated by the second generating unit, and obtain service configuration information corresponding to the query domain name parameter;

    The sending unit is configured to send the service configuration information obtained by the query unit to the OID application.
12. The device according to claim 11, wherein the second generating unit is configured to generate a query domain name parameter in a format of a preset DNS service mapping name based on the first service type of the OID.
13. The device according to claim 11, wherein the query unit is configured to determine a DNS corresponding to the query domain name parameter according to the query domain name parameter, and obtain a resource record corresponding to the query domain name parameter by using the database of the DNS And the resource record includes service configuration information; and the service configuration information in the resource record is extracted.
14. A data processing system, the system comprising: a configuration end device and a client device; among them,

    The configuration end device is configured to determine a service type that needs to be configured by the object identifier OID, and generate a resource record corresponding to the service type; and store the resource record in a corresponding domain name system DNS database;

    The client device is configured to obtain a first service type request to the OID application, and generate a query domain name parameter according to a preset generation rule according to the first service type of the OID application; the query domain name parameter includes the first service Querying the corresponding DNS database based on the query domain name parameter, and obtaining the service configuration information corresponding to the query domain name parameter; and sending the service configuration information to the OID application.
15. A computer storage medium having stored therein computer executable instructions for performing the data processing method of any one of claims 1 to 3.
16. A computer storage medium having stored therein computer executable instructions for performing the data processing method of any one of claims 4 to 6.

Images