CN105608082A

CN105608082A - Data processing method, equipment and system

Info

Publication number: CN105608082A
Application number: CN201410629722.3A
Authority: CN
Inventors: 汤凯
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2014-11-10
Filing date: 2014-11-10
Publication date: 2016-05-25
Also published as: WO2016074477A1

Abstract

The embodiment of the invention discloses a data processing method, equipment and system. The method comprises the following steps: determining a service type which needs to be configured by an OID (Object Identifier) by a configuration side, and generating a resource record corresponding to the service type; storing the resource record into a corresponding DNS (Domain Name Server) database; obtaining a first service type request of an OID application by a client side, and generating a query domain name parameter according to a preset generation rule on the basis of the first service type of the OID application, wherein the query domain name parameter comprises the first service type; on the basis of the query domain name parameter, inquiring the corresponding DNS database, and obtaining service configuration information corresponding to the query domain name parameter; and sending the service configuration information to the OID application.

Description

Data processing method, equipment and system

Technical Field

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

Background

The Object Identifier (OID) is an identification mechanism jointly proposed by the international organization for standardization (ISO), International Electrotechnical Commission (IEC), and International Telecommunication Union (ITU), and globally unambiguous and uniquely names any type of object using a hierarchical tree structure. The OID has the advantages of flexible layering, strong expansibility, clear management mechanism and the like, can be compatible with the existing identification mechanism, is widely applied to the fields of information security, medical treatment and health, network management and the like, and has 891,938 top-level OID identifiers to complete registration in an international OID tree by 12 months in 2013. In recent years, with the development of technologies and industries such as the internet of things, there is an urgent need for identifier management and information management for a wide variety of objects, and the OID is receiving further attention. From aspects of management mechanism, technical superiority, technical maturity, application popularization, international and domestic standardization and the like, the OID is the most appropriate scheme for object identifier management.

The OID coding system is a hierarchical symbology, correspondingly, in order to solve the problem of unified query of information of objects corresponding to OIDs, a set of OID analysis systems (ORS) is defined by the international standard organization, a DNS technology is used, global OIDs are organized into a hierarchical database system through the Internet, and authorized connection is performed between an upper level DNS and a lower level DNS through NS type resource records. And each DNS stores the service configuration information of the corresponding OID object through the NAPTR type resource record.

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

1. because the DNS has cache, redundant service data is diffused, and the convergence speed is reduced when the configuration is modified;

2. with the expansion of the OID service types, the DNS query result is larger and larger, and the processing difficulty of the client is increased due to an overlarge response packet;

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

Disclosure of Invention

In order to solve the existing technical problem, embodiments of the present invention provide a data processing method, device, and system, which can reduce a query load of a DNS and reduce requirements for transport bearer, cache, and processing capability of an ORS client.

In order to achieve the above purpose, the technical solution of the embodiment of the present invention is realized as follows:

a method of data processing, comprising: a configuration end determines a service type to be configured by an object identifier OID, and generates a resource record corresponding to the service type; and storing the resource records into a corresponding Domain Name System (DNS) database.

Wherein the generating the resource record corresponding to the service type includes: generating a DNS service mapping name for the service type, wherein the DNS service mapping name at least comprises an OID service name identifier; acquiring service configuration information corresponding to the service type; and generating a resource record corresponding to the service type according to the DNS service mapping name and the service configuration information.

Further, before determining the service type that the OID needs to be configured, the method further includes: and configuring OID service name identification in advance, wherein the OID service name identification corresponds to the service type.

A method of data processing, comprising: the method comprises the steps that a client side obtains a first service type request of an OID application, and domain name inquiring parameters are generated according to a preset generation rule based on the first service type of the OID application; the query domain name parameter comprises the first service type; inquiring a corresponding DNS database based on the inquired domain name parameter to obtain service configuration information corresponding to the inquired domain name parameter; and sending the service configuration information to the OID application.

Generating a query domain name parameter according to a preset generation rule based on the first service type of the OID, wherein the generating comprises: and generating a query domain name parameter according to the first service type of the OID and a preset DNS service mapping name format.

The querying a corresponding DNS database based on the queried domain name parameter to obtain service configuration information corresponding to the queried domain name parameter includes: determining a DNS corresponding to the query domain name parameter according to the query domain name parameter, and obtaining a resource record corresponding to the query domain name parameter through a database of the DNS, wherein the resource record comprises service configuration information; and extracting service configuration information in the resource record.

A method of data processing, comprising: a configuration end determines a service type to be configured by an object identifier OID, and generates a resource record corresponding to the service type; storing the resource records into a corresponding Domain Name System (DNS) database; the method comprises the steps that a client side obtains a first service type request of an OID application, and domain name inquiring parameters are generated according to a preset generation rule based on the first service type of the OID application; the query domain name parameter comprises the first service type; inquiring a corresponding DNS database based on the inquired domain name parameter to obtain service configuration information corresponding to the inquired domain name parameter; and sending the service configuration information to the OID application.

An apparatus, the apparatus being a provisioning end apparatus, comprising: a determination unit, a first generation unit, and a writing unit; wherein,

the determining unit is configured to determine a service type to be configured by the object identifier OID;

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.

The first generating unit is configured to generate a DNS service mapping name for the service type, where the DNS service mapping name at least includes an OID service name identifier; acquiring service configuration information corresponding to the service type; and generating a resource record corresponding to the service type according to the DNS service mapping name and the service configuration information.

Further, the device further includes a configuration unit, configured to pre-configure an OID service name identifier, where the OID service name identifier corresponds to the service type.

An apparatus, the apparatus being a client device, comprising: the device comprises an acquisition unit, a second generation unit, a query unit and a sending unit; wherein,

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 generating rule based on the first service type of the OID application acquired by the acquiring unit; the query domain name parameter comprises the first service type;

the query unit is configured to query a corresponding DNS database based on the query domain name parameter generated by the second generation 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 querying unit to the OID application.

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

The query unit is configured to determine, according to the query domain name parameter, a DNS corresponding to the query domain name parameter, and obtain, through a database of the DNS, a resource record corresponding to the query domain name parameter, where the resource record includes service configuration information; and extracting service configuration information in the resource record.

A data processing system comprising: configuring end equipment and client equipment; wherein,

the configuration end device is used for determining the service type to be configured by the object identifier OID and generating a resource record corresponding to the service type; storing the resource records into a corresponding Domain Name System (DNS) database;

the client device is used for acquiring a first service type request of the OID application and generating a query domain name parameter according to a preset generation rule based on the first service type of the OID application; the query domain name parameter comprises the first service type; inquiring a corresponding DNS database based on the inquired domain name parameter to obtain service configuration information corresponding to the inquired domain name parameter; and sending the service configuration information to the OID application.

According to the data processing method, the data processing equipment and the data processing system, the service type needing to be configured of the OID is determined through the configuration end, and the resource record corresponding to the service type is generated; storing the resource records into a corresponding DNS database; the method comprises the steps that a client side obtains a first service type request of an OID application, and domain name inquiring parameters are generated according to a preset generation rule based on the first service type of the OID application; the query domain name parameter comprises the first service type; inquiring a corresponding DNS database based on the inquired domain name parameter to obtain service configuration information corresponding to the inquired domain name parameter; and sending the service configuration information to the OID application. By adopting the technical scheme of the embodiment of the invention, different DNS service mapping names are generated through different service types of the OID, and a DNS server does not need to return all service configuration information related to the OID, so that on one hand, the query load of the DNS is greatly reduced, and the configuration convergence speed is improved; on the other hand, the query result is small, the transmission and processing processes are convenient, the requirements on transmission bearing, cache and processing capacity of the ORS client are greatly reduced, the applicability and expansibility are strong, and the convergence speed is high after the configuration is modified.

Drawings

Fig. 1 is a schematic flow chart of a data processing method according to a first embodiment of the present invention;

FIG. 2 is a flowchart illustrating a data processing method according to a second embodiment of the present invention;

FIG. 3 is a flowchart illustrating a data processing method according to a third embodiment of the present invention;

FIG. 4 is a block diagram of a data processing system according to a fourth embodiment of the present invention;

FIG. 5 is a schematic structural diagram of an apparatus according to a fifth embodiment of the present invention;

FIG. 6 is a schematic structural diagram of an apparatus according to a sixth embodiment of the present invention;

fig. 7 is a flowchart illustrating a data processing method according to a seventh embodiment of the present invention.

Detailed Description

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

Example one

The embodiment of the invention provides a data processing method, which is applied to a configuration end side. Fig. 1 is a schematic flow chart of a data processing method according to a first embodiment of the present invention; as shown in fig. 1, the data processing method includes:

step 101: and the configuration end determines the service type needing to be configured by the object identifier OID and generates a resource record corresponding to the service type.

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

and configuring OID service name identification in advance, wherein the OID service name identification corresponds to the service type.

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

Specifically, in practical applications, the OID service name identifier and the corresponding service type may be as shown in table 1, but 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 is not duplicated with other configuration identifiers in the DNS, so as to avoid collision.

Type of service	OID service name identification
		Regular OID service	COID
Registration information service	RINF
		Object information service	OINF
Sub OID list service	CINF
		Child node distribution scheme service	COAS
Modular information service	MINF
		……	……

TABLE 1

In practical application, a configurator does not need to configure OID service name identifiers corresponding to all service types as shown in table 1 for each OID, and can determine the service types required to be configured by the OID according to the needs of the OID, and generate resource records corresponding to the service types according to the service types required to be configured by different OIDs.

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

generating a DNS service mapping name for the service type, wherein the DNS service mapping name at least comprises an OID service name identifier;

acquiring service configuration information corresponding to the service type;

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

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

Wherein the DNS service mapping name is represented in the resource record by an ownername field, and is used for distinguishing different service types of the OID in the DNS. Specifically, the DNS service mapping name may adopt the following format:

the DNS service mapping name ═ OID service name identification, + reverse-naming 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 is not duplicated with other configuration identifiers in the DNS.

Specifically, the OID service name identifier is specifically an OID service name identifier shown in table 1, such as a COID, a RINF, an OINF, and the like; taking the OID to be configured as 1.2.156.102.8 as an example, the domain name reverse order is 8.102.156.2.1; the OID resolution system DNS root may be denoted by "OID-res.

Specifically, the service configuration information in the resource record may be represented by an inantr type resource record. The INNAPTR represents that the resource record with Class IN and Type NAPTR IN DNS stores the service configuration information of OID object, and the service configuration information can be embodied by RDATA field IN the resource record.

Wherein, the RDATA field at least comprises a Regularrection field; the Regularexpression field is used to store specific service configuration information of the OID object, where the service configuration information may specifically be a Uniform Resource Locator (URL) address and the like.

Step 102: and storing the resource records into a corresponding Domain Name System (DNS) database.

Specifically, for example, an OID to be configured is 1.2.156.102.8, a service type to be configured is a COID, and a corresponding DNS is 202.202.1.102, the OID is configured with the COID service and stored in a database of the DNS, where resource records stored in the database of the DNS are as follows:

coid.8.102.156.2.1.oid-res.org.INNAPTR0100"u""ORS+OINF""！^.*$！/1/2/156/102/8！".。

wherein, an owernenamee field in the resource record is "id.8.102.156.2.1. oid-res.org", and the owernenamee field is a DNS service mapping name; "inantr" indicates service configuration information of the resource record storage OID object; the specific service configuration information may be embodied by the RDATA field in the resource record, which is specifically "0100" u "," ORS + OINF "," |! ^. $! /1/2/156/102/8! ".".

Wherein, the fields included in the RDATA field and the corresponding field assignments are shown in table 2:

TABLE 2

The Regularexpression field is used to store specific service configuration information of the OID object, where the service configuration information may specifically be a URL address and the like.

According to the technical scheme provided by the embodiment, different DNS service mapping names are generated through different service types of the OID, so that when a specific service applied by the OID is queried, a DNS server does not need to return all service configuration information related to the OID, on one hand, the query load of the DNS is greatly reduced, and the configuration convergence speed is improved; on the other hand, the query result is small, the transmission and processing processes are convenient, the requirements on transmission bearing, cache and processing capacity of the ORS client are greatly reduced, the applicability and expansibility are strong, and the convergence speed is high after the configuration is modified.

Example two

The embodiment of the invention also provides a data processing method, which is applied to the client side. FIG. 2 is a flowchart illustrating a data processing method according to a second embodiment of the present invention; as shown in fig. 2, the data processing method includes:

step 201: the method comprises the steps that a client side obtains a first service type request of an OID application, and domain name inquiring parameters are generated according to a preset generation rule based on the first service type of the OID application; the query domain name parameter comprises the first service type.

In this embodiment, the client learns all the service types and the corresponding OID service name identifiers in advance, where the service types and the corresponding OID service name identifiers may be as shown in table 1, and are not described herein again.

The first service type request is a service type request corresponding to any one of the pre-known service types.

In this embodiment, the client has configured a generation rule of a DNS service mapping name in advance; the domain name querying parameter in this embodiment is the DNS service mapping name. Correspondingly, the step of generating a query domain name parameter according to a preset generation rule based on the first service type of the OID includes:

and generating a query domain name parameter according to the first service type of the OID and a preset DNS service mapping name format.

Wherein, the DNS service mapping name may adopt the following format:

Specifically, taking an OID as 1.2.156.102.8 and the first service type as a COID as an example, based on the above format of the DNS service mapping name, the query domain name parameter may be generated as: id.8.102.156.2.1. oil-res.

Step 202: and querying a corresponding DNS database based on the queried domain name parameter to obtain service configuration information corresponding to the queried domain name parameter.

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

determining a DNS corresponding to the query domain name parameter according to the query domain name parameter, and obtaining a resource record corresponding to the query domain name parameter through a database of the DNS, wherein the resource record comprises service configuration information; and extracting service configuration information in the resource record.

Specifically, after obtaining the domain name querying parameter, the client initiates DNS query by using CLASS ═ IN and TYPE ═ NAPTR as query conditions, that is, sends a DNSNAPTR query request, where the DNSNAPTR query request includes the domain name querying parameter. In this embodiment, the DNSNAPTR query request is sent to the DNS; and the DNS acquires a resource record which takes the DNS service mapping name of the first service type of the OID as an owernenamee field in a corresponding DNS database according to the query domain name parameter, and extracts service configuration information from the resource record.

Step 203: and sending the service configuration information to the OID application.

Here, the service configuration information may specifically be a URL address or the like. The OID application may access the corresponding OID service according to the service configuration information (specifically, the URL address) after obtaining the service configuration information.

According to the technical scheme provided by the embodiment, different DNS service mapping names are generated in advance through different service types of the OID, so that when a specific service applied by the OID is queried, a DNS server does not need to return all service configuration information related to the OID, on one hand, the query load of the DNS is greatly reduced, and the configuration convergence speed is improved; on the other hand, the query result is small, the transmission and processing processes are convenient, the requirements on transmission bearing, cache and processing capacity of the ORS client are greatly reduced, the applicability and expansibility are strong, and the convergence speed is high after the configuration is modified.

EXAMPLE III

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

step 301: and the configuration end determines the service type required to be configured by the OID and generates a resource record corresponding to the service type.

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

Specifically, in practical applications, the OID service name identifier and the corresponding service type may be as shown in table 1, but are not limited to the service type and the corresponding service name identifier shown in table 1, and 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 is not duplicated with other configuration identifiers in the DNS, so as to avoid collision.

acquiring service configuration information corresponding to the service type;

Specifically, the OID service name identifier is specifically an OID service name identifier shown in table 1, such as a COID, a RINF, an OINF, and the like; taking the OID to be configured as 1.2.156.102.8 as an example, the domain naming reverse order is 8.102.156.2.1. The OID resolution system DNS root may be denoted by "OID-res.

Wherein, the RDATA field at least comprises a Regularrection field; the Regularexpression field is used to store specific service configuration information of the OID object, where the service configuration information may specifically be a URL address and the like.

Step 302: and storing the resource records into a corresponding DNS database.

The fields included in the RDATA field and the corresponding field assignments are shown in table 2, and are not described herein again.

Step 303: the method comprises the steps that a client side obtains a first service type request of an OID application, and domain name inquiring parameters are generated according to a preset generation rule based on the first service type of the OID application; the query domain name parameter comprises the first service type.

Wherein, the DNS service mapping name may adopt the following format:

Step 304: and querying a corresponding DNS database based on the queried domain name parameter to obtain service configuration information corresponding to the queried domain name parameter.

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

Specifically, after obtaining the domain name querying parameter, the client initiates DNS query by using CLASS ═ IN and TYPE ═ NAPTR as query conditions, that is, sends a DNSNAPTR query request, where the DNSNAPTR query request includes the domain name querying parameter. In this embodiment, the DNS snaptr query request is sent to a DNS, the DNS acquires, according to the query domain name parameter, a resource record in a corresponding DNS database with a DNS service mapping name of the first service type of the OID as an owernenamee field, and extracts service configuration information from the resource record.

Step 305: and sending the service configuration information to the OID application.

According to the technical scheme provided by the embodiment of the invention, different DNS service mapping names are generated through different service types of the OID, and a DNS server does not need to return all service configuration information related to the OID, so that on one hand, the query load of the DNS is greatly reduced, and the configuration convergence speed is improved; on the other hand, the query result is small, the transmission and processing processes are convenient, the requirements on transmission bearing, cache and processing capacity of the ORS client are greatly reduced, the applicability and expansibility are strong, and the convergence speed is high after the configuration is modified.

Example four

The embodiment of the invention also provides a data processing system. FIG. 4 is a block diagram of a data processing system according to a fourth embodiment of the present invention; as shown in fig. 4, the system includes: a configuration side device 41 and a client side device 42; wherein,

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; storing the resource records in a 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 based on the first service type of the OID application; the query domain name parameter comprises the first service type; querying a corresponding DNS database 43 based on the queried domain name parameter to obtain service configuration information corresponding to the queried domain name parameter; and sending the service configuration information to the OID application.

Here, the service types of the OIDs include N, where N is a positive integer. In practical application, a configurator does not need to configure OID service name identifiers corresponding to all service types as shown in table 1 for each OID, and can determine the service types required to be configured by the OID according to the needs of the OID, and generate resource records corresponding to the service types according to the service types required to be configured by different OIDs.

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

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

In this embodiment, the client device 42 obtains all the service types and the corresponding OID service name identifiers in advance, where the service types and the corresponding OID service name identifiers may be as shown in table 1, and are not described herein again.

In this embodiment, the client device 42 has configured a generation rule of a DNS service mapping name in advance; the domain name querying parameter in this embodiment is the DNS service mapping name.

In another embodiment, the configuration end device 41 is further configured to, before determining the service type that the object identifier OID needs to be configured, configure an OID service name identifier in advance, where the OID service name identifier corresponds to the service type.

The OID service name identifier is preconfigured in the configuration end device 41, where the OID service name identifier corresponds to the service type, and the OID service name identifier and the corresponding service type may be shown in table 1, which is 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 is not duplicated with other configuration identifiers in the DNS, so as to avoid collision.

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

Wherein, the DNS service mapping name may adopt the following format:

The client device 42 is specifically configured to determine, according to the query domain name parameter, a DNS44 corresponding to the query domain name parameter, and obtain, through the database 43 of the DNS44, a resource record corresponding to the query domain name parameter, where the resource record includes service configuration information; and extracting service configuration information in the resource record.

Specifically, after obtaining the domain name querying parameter, the client device 42 initiates DNS query by using CLASS ═ IN and TYPE ═ NAPTR as query conditions, that is, sends a DNSNAPTR query request, where the DNSNAPTR query request includes the domain name querying parameter. In this embodiment, the DNS snaptr query request is sent to a DNS, the DNS acquires, according to the query domain name parameter, a resource record in the DNS database 43 corresponding to the DNS44, in which a DNS service mapping name of the first service type of the OID is an owernenamee field, and then extracts service configuration information from the resource record.

EXAMPLE five

The embodiment of the invention also provides equipment, which is the configuration end equipment. FIG. 5 is a schematic structural diagram of an apparatus according to a fifth embodiment of the present invention; as shown in fig. 5, the configuration end device includes: a determination unit 411, a first generation unit 412, and a writing unit 413; wherein,

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; acquiring service configuration information corresponding to the service type; and generating a resource record corresponding to the service type according to the DNS service mapping name and the service configuration information.

In another embodiment, the apparatus further includes a configuring unit 414, configured to pre-configure an OID service name identifier, where the OID service name identifier corresponds to the service type.

In this embodiment, the determining unit 411, the first generating unit 412 and the configuring unit 414 in the configuring end device may be implemented by a Central Processing Unit (CPU), a Digital Signal Processor (DSP), or a programmable gate array (FPGA) in the device in an actual application; the writing unit 413 may be implemented by a transmitter or a transmitter in the device in practical applications.

EXAMPLE six

The embodiment of the invention also provides equipment, which is client equipment. FIG. 6 is a schematic structural diagram of an apparatus according to a sixth embodiment of the present invention; as shown in fig. 6, the configuration end device includes: an acquisition unit 421, a second generation unit 422, an inquiry unit 423, and a transmission unit 424; wherein,

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

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

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

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

In another embodiment, the second generating unit 422 is configured to generate the 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 423 is configured to determine, according to the query domain name parameter, a DNS corresponding to the query domain name parameter, and obtain a resource record corresponding to the query domain name parameter through a database of the DNS, where the resource record includes service configuration information; and extracting service configuration information in the resource record.

In this 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 actual application; the querying unit 423 and the sending unit 424 may be implemented by a transmitter or a transmitter in the device in practical applications; the obtaining unit 421 may be implemented by a receiver or a receiver in the device in practical applications.

EXAMPLE seven

The present embodiment further describes the present invention in detail with reference to specific embodiments in specific application scenarios. The specific application scenario of this embodiment is that an authority is a winery, and the OID node is: 1.2.156.102, the corresponding DNS is: 202.202.1.102, the OID to be configured is: 1.2.156.102.8, the service types to be configured are: COID, RINF, OINF; in the above application scenario, fig. 7 is a schematic flow chart of a data processing method according to a seventh embodiment of the present invention, and as shown in fig. 7, the data processing method includes:

step 701: and the configuration end reserves N OID service name identifiers, wherein 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 services of three service types for the OID to be configured, generates three resource records corresponding to the three service types, and writes the three resource records into a corresponding DNS database.

In this embodiment, the configuration end configures services of three service types 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; in other embodiments, each service type is not limited to corresponding to one resource record, and each service type may correspond to M resource records, where M is a positive integer.

The OID resolution system DNS root may be denoted by "OID-res.

The service configuration information in the resource record may be represented by an inantr type resource record. The INNAPTR represents that the resource record with Class IN and Type NAPTR IN DNS stores the service configuration information of OID object, and the service configuration information can be embodied by RDATA field IN the resource record.

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

coid.8.102.156.2.1.oid-res.org.INNAPTR0100"u""ORS+OINF""！^.*$！/1/2/156/102/8！".；

rinf.8.102.156.2.1.oid-res.org.INNAPTR0100"u""ORS+RINF""！^.*$！http://www.maotai.com/oid/rinf-1.2.156.102.8.xml！".；

oinf.8.102.156.2.1.oid-res.org.INNAPTR0100"u""ORS+OINF""！^.*$！http://www.maotai.com/oid/oinf-1.2.156.102.8.xml！".；

taking the COID service type as an example for explanation, an owernenamefield in a resource record of the COID service type is "id.8.102.156.2.1.oid-res.org", and the owernenamefield is a DNS service mapping name; "inantr" indicates service configuration information of the resource record storage OID object; the specific service configuration information may be embodied by the RDATA field in the resource record, which is specifically "0100" u "," ORS + OINF "," |! ^. $! /1/2/156/102/8! ".".

Step 703: and the client receives an instruction for inquiring the OINF information of the OID and generates an inquiry domain name parameter.

In this embodiment, the client has configured a generation rule of a DNS service mapping name in advance; the domain name querying parameter in this embodiment is the DNS service mapping name.

Wherein, the DNS service mapping name may adopt the following format:

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

Step 704: and the client directs 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 through the database corresponding to the DNS.

Step 705: and 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 domain name querying parameter, the client initiates DNS query by using CLASS ═ IN and TYPE ═ NAPTR as query conditions, that is, sends a DNSNAPTR query request, where the DNSNAPTR query request includes the domain name querying parameter. In this embodiment, the DNS snaptr query request is sent to a DNS, the DNS acquires, according to the query domain name parameter, a resource record with a DNS service mapping name of the first service type of the OID as an owernenamee field, and extracts service configuration information from the resource record.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims

1. A method of data processing, the method comprising:

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

and storing the resource records into a corresponding Domain Name System (DNS) database.

2. The method of claim 1, wherein the generating the resource record corresponding to the service type comprises:

acquiring service configuration information corresponding to the service type;

3. The method of claim 2, wherein prior to determining the type of service that the OID needs to be configured for, the method further comprises:

4. A method of data processing, the method comprising:

the method comprises the steps that a client side obtains a first service type request of an OID application, and domain name inquiring parameters are generated according to a preset generation rule based on the first service type of the OID application; the query domain name parameter comprises the first service type;

inquiring a corresponding DNS database based on the inquired domain name parameter to obtain service configuration information corresponding to the inquired domain name parameter;

and sending the service configuration information to the OID application.

5. The method of claim 4, wherein the generating, according to a preset generation rule, a query domain name parameter based on the first service type of the OID comprises:

6. The method according to claim 4, wherein the querying a corresponding DNS database based on the queried domain name parameter to obtain the service configuration information corresponding to the queried domain name parameter includes:

determining a DNS corresponding to the query domain name parameter according to the query domain name parameter, and obtaining a resource record corresponding to the query domain name parameter through a database of the DNS, wherein the resource record comprises service configuration information;

and extracting service configuration information in the resource record.

7. A method of data processing, the method comprising:

storing the resource records into a corresponding Domain Name System (DNS) database;

and sending the service configuration information to the OID application.

8. An apparatus, the apparatus being a configuration end apparatus, the configuration end apparatus comprising: a determination unit, a first generation unit, and a writing unit; wherein,

9. The apparatus according to claim 8, wherein 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; acquiring service configuration information corresponding to the service type; and generating a resource record corresponding to the service type according to the DNS service mapping name and the service configuration information.

10. The apparatus according to claim 9, wherein the apparatus further comprises a configuration unit configured to pre-configure an OID service name identifier, where the OID service name identifier corresponds to the service type.

11. An apparatus, the apparatus being a client device, the client device comprising: the device comprises an acquisition unit, a second generation unit, a query unit and a sending unit; wherein,

12. The apparatus according to claim 11, wherein the second generating unit is configured to generate the 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 querying unit is configured to determine, according to the queried domain name parameter, a DNS corresponding to the queried domain name parameter, and obtain, through a database of the DNS, a resource record corresponding to the queried domain name parameter, where the resource record includes service configuration information; and extracting service configuration information in the resource record.

14. A data processing system, characterized in that the system comprises: configuring end equipment and client equipment; wherein,