CN113821710A

CN113821710A - Global search method, device, electronic equipment and computer storage medium

Info

Publication number: CN113821710A
Application number: CN202111382972.8A
Authority: CN
Inventors: 韩天宇; 刘阳; 田娟; 池程; 朱斯语
Original assignee: China Academy of Information and Communications Technology CAICT
Current assignee: China Academy of Information and Communications Technology CAICT
Priority date: 2021-11-22
Filing date: 2021-11-22
Publication date: 2021-12-21
Anticipated expiration: 2041-11-22
Also published as: CN113821710B

Abstract

The embodiment of the application provides a global search method, a global search device, electronic equipment and a computer storage medium. The method comprises the following steps: receiving subscription data through a data interoperability protocol; performing access authority authentication on subscription data; and after the subscription data access authority passes the authentication, searching and inquiring according to the keywords or the time sequence carried in the subscription data to obtain the search data. Data can be shared in a wider range through a data interoperation protocol, so that an industrial internet identification analysis system can be effectively interconnected and associated.

Description

Global search method, device, electronic equipment and computer storage medium

Technical Field

The present application relates to the field of industrial internet technologies, and in particular, to a global search method, apparatus, electronic device, and computer storage medium.

Background

At present, secondary nodes only have the function of identification analysis, and although the secondary nodes can meet the requirements of data acquisition, data management and data discovery, search and utilization of data in enterprises, no effective interconnection and association are carried out through an industrial internet identification analysis system, and data are not shared in a wider range through a universal data interoperation protocol.

Disclosure of Invention

The embodiment of the application provides a global search method, a global search device, electronic equipment and a computer storage medium, so as to solve the problems in the prior art.

According to a first aspect of embodiments of the present application, there is provided a global search method, including:

receiving subscription data based on a data interoperability protocol;

performing access authority authentication on the subscription data;

and after the subscription data access authority passes the authentication, searching and inquiring according to the keywords or the time sequence carried in the subscription data to obtain search data.

According to a second aspect of embodiments of the present application, there is provided a global search apparatus, the apparatus including:

the receiving module is used for receiving subscription data based on a data interoperation protocol;

the authority control module is used for carrying out access authority authentication on the subscription data;

and the query searching module is used for searching and querying according to the keywords or the time sequence carried in the subscription data after the subscription data access authority passes the authentication so as to obtain search data.

According to a third aspect of embodiments of the present application, there is provided an electronic device comprising one or more processors, and memory for storing one or more programs; the one or more programs, when executed by the one or more processors, implement the steps of the population search method as described above.

According to a fourth aspect of embodiments of the present application, there is provided a computer storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the global search method as described above.

By adopting the universe searching method, the universe searching device, the electronic equipment and the computer storage medium, subscription data are received through a data interoperation protocol; performing access authority authentication on subscription data; and after the subscription data access authority passes the authentication, searching and inquiring according to the keywords or the time sequence carried in the subscription data to obtain the search data. Data can be shared in a wider range through a data interoperation protocol, so that an industrial internet identification analysis system can be effectively interconnected and associated.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is a schematic view of an application scenario of an electronic device according to an embodiment of the present application;

fig. 2 is a schematic diagram of a message structure of a data interoperability protocol according to an embodiment of the present application;

fig. 3 is a schematic format diagram of a data interoperability protocol according to an embodiment of the present application;

FIG. 4 is a schematic format diagram of another data interoperability protocol provided in an embodiment of the present application;

fig. 5 is a schematic diagram of a data format provided in an embodiment of the present application;

fig. 6 is a schematic diagram of another data format provided in the embodiment of the present application;

fig. 7 is a schematic flowchart of a global search method according to an embodiment of the present application;

fig. 8 is a schematic flowchart of another global search method according to an embodiment of the present application;

fig. 9 is a schematic diagram of inheritance of publishing data according to an embodiment of the present application;

fig. 10 is a schematic diagram of inheritance of another release data provided in this embodiment of the present application

Fig. 11 is a block diagram of a global search apparatus according to an embodiment of the present disclosure.

Icon:

100-an electronic device; 110-global search means; 111-a receiving module; 112-an authority control module; 113-a query search module; 114-standard recommendation module; 115-a cache module; 116-an upload module; 200-a subscriber; 300-the distribution end.

Detailed Description

In the process of implementing the present application, the inventor finds that an industrial internet identity resolution system is an important component of an industrial internet network architecture, is an important infrastructure and service for maintaining stable operation of the global industrial internet, and has a similar function to a domain name resolution system (DNS) in the internet field. The object of the industrial internet identification and analysis system is a machine, a product and other physical entities and an algorithm, a process and other virtual manufacturing resources, and the identification and analysis system inquires network positions according to the identification, so that communication addressing between people and objects, and between objects is realized, or related information of the objects is directly inquired. From the function perspective, compared with an internet domain name system, the industrial internet identification and analysis has the advantages of more abundant object range change, object granularity refinement and analysis functions.

In view of the foregoing problems, embodiments of the present application provide a global search method, an apparatus, an electronic device, and a computer storage medium, which receive subscription data through a data interoperability protocol; performing access authority authentication on subscription data; and after the subscription data access authority passes the authentication, searching and inquiring according to the keywords or the time sequence carried in the subscription data to obtain the search data. Data can be shared in a wider range through a data interoperation protocol, so that an industrial internet identification analysis system can be effectively interconnected and associated.

In order to make the technical solutions and advantages of the embodiments of the present application more apparent, the following further detailed description of the exemplary embodiments of the present application with reference to the accompanying drawings makes it clear that the described embodiments are only a part of the embodiments of the present application, and are not exhaustive of all embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.

Referring to fig. 1, which is a schematic view of an application scenario provided in the embodiment of the present application, an electronic device 100, a subscriber 200 and a publisher 300 perform data communication based on a data interoperability protocol.

The subscriber 200 is a party using data, and acquires data from the electronic device 100 in a subscription manner. The issuing end 300 is a party that generates data, and transmits the data to the electronic device 100 in an issuing manner. The subscribing end 200 and the publishing end 300 can be users, machines, sensors, software systems, and other industrial internet participants. The electronic device 100 is an agent for providing data distribution in the publish-subscribe mode, and is mainly responsible for functions of data storage, management, authority control, validity check, and the like. The electronic device 100 may be an existing system, such as an industrial software, an edge gateway, an industrial internet platform, etc.; the electronic device 100 may also be a subscriber 200 that subscribes to other information service data, or a publisher 300 that publishes data to other electronic devices 100, where the electronic devices 100 may be understood as secondary nodes in an industrial internet identity resolution system.

The data interoperation protocol mainly specifies the message format, the data format and the operation flow of data transmission and exchange in the industrial Internet. The message format defines a transmission mechanism, a control method and related safety verification information of data in the network; the data format provides a method for standardizing and organizing data assets generated by industrial manufacturing with an asset category system as a center; the operation flow explains how a user specifically shares and interoperates data based on a data interoperation protocol, and comprises system components, functions of each component and flow steps.

The data interoperability protocol communicates by exchanging predefined data interoperability protocol messages. The data interoperation protocol data packet mainly consists of five parts, as shown in fig. 2, which are respectively a basic header, a transport block, a control block, a data block, and a credential block. The basic header comprises basic information of the data packet, and the transmission block, the control block, the data block and the certificate block respectively carry information such as data packet transmission mode information, control information, data information, verification encryption and the like.

As shown in fig. 3, the format of the basic header includes a major version, a minor version, and a check code, the major version and the minor version each being set to 8 bits for representing a version of the data interoperability protocol, each field being defined by a 1-byte non-signed integer. The different major versions represent major changes in protocol format, and the party using the lower major version must upgrade the software to ensure the accuracy of the communication. The addition of the minor version means that additional functions are added to the protocol but does not affect the main information format of the protocol. The check code is set to 16 bits for checking the integrity of the transmitted data packet. The data interoperability protocol definition may be checked using the CRC-16 standard.

The formats of the transport block, the control block, the data block, and the credential block may all be set to be the same, as shown in fig. 4, and all include a block type, a header type, a flag, a block length, an option, a delimiter, and a payload. The block type is set to 2-bit unsigned integer, and the value range is 0-3, which is used to represent the type of the block, including a transmission block 00, a control block 01, a data block 10, and a credential block 11. The header type is set to 6-bit unsigned integer, with a range of values from 0 to 63, for the type of header in different blocks. The flag bit is set to 8 bits and set to 0 ignores this field. The block length is set to 16 bits, indicating the length of the block or the length of the fragmented packet (when the block type is a transport block), in bytes. The value of the data block length must be an integer multiple of 4 bytes, the block length not including the pad field length. The alternative is variable in length, carrying the necessary information about the block transfer. The payload can be made long, and in particular data, the data interoperability protocol states that if a block has a payload, the payload must be preceded by a delimiter of one byte (0 xFF), and if not, the recipient will process the error message. The sum of the length of the option and the payload must be a multiple of 4 bytes, if not, filled with 0 s.

The transmission block defines how the data packet is transmitted in the network, the header types of different transmission blocks define different transmission modes, each transmission mode has its own characteristics, and the user can select an appropriate transmission mode according to the network environment, service requirements, transmission equipment and other factors. Three transmission modes can be defined: retransmission mechanisms, multiple-issue mechanisms, and error correction mechanisms. The non-payload portion of the transport block is not protected by the signature or encryption information in the credential block, and the payload portion of the transport block is the aggregate of all other blocks.

In the retransmission mechanism, a sending end encodes a data sequence according to a certain rule, so that the data sequence becomes a data packet with strong error detection capability. And after receiving the data packet, the receiving end calculates a receiving check code according to the coding rule. If the check is correct, the packet is accepted. Meanwhile, the receiving end informs the transmitting end via the reverse channel feedback that the error-free code it transmitted has been successfully received. If the error is checked, the data packet is error. And informing the transmitting end to retransmit the same packet through a feedback channel. The sender retransmits the previously sent information once until the packet is successfully received. The sending end may be the issuing end 300 or the electronic device 100, and the receiving end may be the electronic device 100 or the subscribing end 200.

In the sending process of the multi-sending mechanism, for the same transmission identifier, each data packet has a unique transmission sequence number. For the same transmission sequence number, the transmitting end continuously transmits data for a plurality of times, but the transmission sequence number does not increase, and the number of transmissions is defined in the count (2 or more). The interval of the consecutive transmission is not limited. In the receiving process, the received data is subjected to transmission sequence number judgment, if the received data is greater than the sequence number of the last data packet, the data is considered to be an effective packet, and the data is immediately processed; if the transmission sequence number is the same as that of the previous packet, the redundant transmission of the previous data packet is considered, and the invalid data is discarded.

The error correction mechanism adopts a forward error correction method to increase the reliability of data communication, and once an error is found in a unidirectional communication channel, a receiving end of the unidirectional communication channel does not have the right to request transmission again. The forward error correction coding technology adds redundant error correction codes into a transmission code sequence, and can automatically correct transmission error codes through decoding under a certain condition, so that the error code rate of received signals is reduced. Forward error correction coding is a method for transmitting redundant information by using data, and when errors occur in transmission, a receiving end can reconstruct the data. During transmission, data to be transmitted is divided into a plurality of groups for transmission, and each group is composed of a certain proportion of data packets and redundant packets (redundancy). In one group, redundant packets are generated from data packets and corresponding error correction codes. The groups are independent from each other, the size and redundancy of the groups can be different, and the sending end can be dynamically adjusted according to the network receiving condition of the receiving end so as to achieve the optimal service quality. For example, when the channel condition is poor and the packet loss rate of the receiver is increased, the redundancy can be improved by the transmitting end to enhance the packet loss resistance; on the contrary, if the packet loss rate is very low, the redundancy can be properly reduced at the transmitting end, so as to save the network bandwidth. In the receiving process, if the receiving end receives the packet according to the group sequence number, the packet is not lost, and is directly uploaded to the upper application; if the packet is not received according to the group sequence number, the packet loss situation is indicated, and the receiving end needs to recover according to the error correction code and other packets in the group. If the recovery can not be carried out, the received packets are uploaded in sequence, and the rest are abandoned.

The control block is mainly responsible for relevant information of message operation and does not contain load. The control block has an object issuing function, which means that a message is transmitted from a transmitting end to a receiving end. The control block also has a release object update function, which refers to an operation of updating a registered object. The control block also has an issued object deleting function, which means an operation of deleting an issued object. The control block also has an issue object return function, which refers to the return of an object issue operation response. The control block also has a subscribe object function, which refers to operations to subscribe to a specified object. The control block also has an unsubscribe object function, which means an operation of unsubscribing a specified object. The control block also has a subscription object return function, which refers to a response message at the receiving end of the subscription operation.

In the stage of issuing the asset object, the block type of the control block is set to be 2 bits, and the block type value is set to be 1; the head type is set to be 6 bits, the head type value is set to be 0, namely the function type representing the control block is the function of issuing the asset object; the flag Bit is set to 8 bits, 6 flag bits can be predefined, Bit0 is a uf (user flag) flag Bit, which is set to 0, the option cannot contain the username field, and is set to 1, and the option must contain the username field; bit1 is a pf (password flag) flag Bit, which is set to 0, and optionally cannot contain a password field; set to 0, must contain a password field; bit2 is the TK (token) flag, set to 0, cannot contain tokens (tokens) in the alternative, set to 1, and must contain tokens in the alternative; bit3 is a tp (type) flag Bit, which is set to 0, and represents that the published data is a category object, and is set to 1, and represents that the published data is an ontology object; bit4 is an RP (repeat) flag Bit that is set to 0, indicating that the data identifier was first issued, set to 1, indicating that the data identifier was previously issued but was not successful; bit5 is a CT (verified) flag Bit, when the CT Bit of the sending end is set to 1, the receiving end needs to encrypt the return by using a private key, when the CT Bit of the returning party is set to 1, it represents that the data has been signed, and if the receiving end does not provide a valid signature in the return, the sending end discards the returned data; the block length is set to 16 bits, indicating the length of the control block, in bytes, excluding the pad field length. An alternative contains one or more fields prefixed by length, and the flag bit determines whether or not to contain these fields, and if so, must appear in this order: data identifier, username, password, token.

Where if the UF flag bit is set to 1, the next field of the option must be the username. The username must be the UTF-8 encoded string. The receiver can use it for authentication and authorization of data access. If the PF flag is set to 1, the next field of the option must be the password. If the TK flag bit is set to 1, the next field of the selectable item must be the token. The user is allowed to provide a token, rather than a username and password, to access data for a particular data server.

In the updating stage of issuing the asset object, the block type of the control block is set to be 2 bits, and the block type value is set to be 1, namely the type representing the block is the control block; the head type is set to 6 bits, the head type value is set to 1, namely the function type representing the control block is an asset object issuing updating function; the flag Bit is set to 8 bits, 7 flag bits can be predefined, Bit0 is a uf (user flag) flag Bit, which is set to 0, the option cannot contain the username field, and is set to 1, and the option must contain the username field; bit1 is a pf (password flag) flag Bit, which is set to 0, and optionally cannot contain a password field; set to 0, must contain a password field; bit2 is the TK (token) flag, set to 0, cannot contain tokens (tokens) in the alternative, set to 1, and must contain tokens in the alternative; bit3 is a tp (type) flag Bit, which is set to 0, and represents that the published data is a category object, and is set to 1, and represents that the published data is an ontology object; bit4 is an nf (notification) flag Bit, which is set to 0, representing that it is not necessary to send a reminder message to a user party referring to the same identifier, and is set to 1, representing that it is necessary to send a reminder message; bit5 is an RP (repeat) flag Bit that is set to 0, indicating that the data identifier was first issued, set to 1, indicating that the data identifier was previously issued but was not successful; bit6 is a CT (verified) flag Bit, when the CT Bit of the sending end is set to 1, the receiving end needs to encrypt the return by using a private key, when the CT Bit of the returning party is set to 1, it represents that the data has been signed, and if the receiving end does not provide a valid signature in the return, the sending end discards the returned data; the block length is set to 16 bits, indicating the length of the control block, in bytes, excluding the pad field length. An alternative contains one or more fields prefixed by length, and the flag bit determines whether or not to contain these fields, and if so, must appear in this order: data identifier, username, password, token, prompt message.

Where the last field of the option must be a hint message if the hint message flag NF is set to 1. The prompt message defines the message sent by the end using the asset object after the asset object is updated, which may be but is not limited to comparison before and after updating, update reason, author, etc., and the specific format is defined by the user, or defined by using an asset category system.

In the deletion stage of the published asset object, the block type of the control block is set to be 2 bits, and the block type value is set to be 1, namely the type representing the block is the control block; the head type is set to 6 bits, the head type value is set to 2, namely the function type representing the control block is the function of deleting the published asset object; the flag Bit is set to 8 bits, 6 flag bits can be predefined, Bit0 is a uf (user flag) flag Bit, which is set to 0, the option cannot contain the username field, and is set to 1, and the option must contain the username field; bit1 is a pf (password flag) flag Bit, which is set to 0, and optionally cannot contain a password field; set to 0, must contain a password field; bit2 is the TK (token) flag, set to 0, cannot contain tokens (tokens) in the alternative, set to 1, and must contain tokens in the alternative; bit3 is a tp (type) flag Bit, which is set to 0, and represents that the published data is a category object, and is set to 1, and represents that the published data is an ontology object; bit4 is an RP (repeat) flag Bit that is set to 0, indicating that the data identifier was first issued, set to 1, indicating that the data identifier was previously issued but was not successful; bit5 is a CT (verified) flag Bit, when the CT Bit of the sending end is set to 1, the receiving end needs to encrypt the return by using a private key, when the CT Bit of the returning party is set to 1, it represents that the data has been signed, and if the receiving end does not provide a valid signature in the return, the sending end discards the returned data; the block length is set to 16 bits, indicating the length of the control block, in bytes, excluding the pad field length. An alternative contains one or more fields prefixed by length, and the flag bit determines whether or not to contain these fields, and if so, must appear in this order: data identifier, username, password, token.

In the return stage of issuing the asset object, the block type of the control block is set to be 2 bits, and the block type value is set to be 1, namely the type representing the block is the control block; the head type is set to 6 bits, the head type value is set to 3, namely the function type representing the control block is an asset object issuing return function; the flag Bit is set to 8 bits, 6 flag bits can be predefined, Bit0 is a uf (user flag) flag Bit, which is set to 0, the option cannot contain the username field, and is set to 1, and the option must contain the username field; bit1 is a pf (password flag) flag Bit, which is set to 0, and optionally cannot contain a password field; set to 0, must contain a password field; bit2 is the TK (token) flag, set to 0, cannot contain tokens (tokens) in the alternative, set to 1, and must contain tokens in the alternative; bit3 is a CT (verified) flag Bit, when the CT Bit of the sending end is set to 1, the receiving end needs to encrypt the return by using a private key, when the CT Bit of the returning party is set to 1, it represents that the data has been signed, and if the receiving end does not provide a valid signature in the return, the sending end discards the returned data; bit4-6 is the number of status codes representing the number of status codes contained in the published asset object return type control block; the block length is set to 16 bits, indicating the length of the control block, in bytes, excluding the pad field length.

In the stage of subscribing the asset object, the block type of the control block is set to be 2 bits, and the block type value is set to be 1, namely the type representing the block is the control block; the head type is set to 6 bits, and the head type value is set to 4, namely, the function type representing the control block is the function of subscribing the asset object; the flag Bit is set to 8 bits, 7 flag bits can be predefined, Bit0 is a uf (user flag) flag Bit, which is set to 0, the option cannot contain the username field, and is set to 1, and the option must contain the username field; bit1 is a pf (password flag) flag Bit, which is set to 0, and optionally cannot contain a password field; set to 0, must contain a password field; bit2 is the TK (token) flag, set to 0, cannot contain tokens (tokens) in the alternative, set to 1, and must contain tokens in the alternative; bit3 is an RP (repeat) flag Bit that is set to 0, indicating that the data identifier was first issued, set to 1, indicating that the data identifier was previously issued but was not successful; bit4 is a tp (type) flag Bit, which is set to 0, and represents that the published data is a category object, and is set to 1, and represents that the published data is an ontology object; bit5 is the LT (List) flag; bit6 is a CT (verified) flag Bit, when the CT Bit of the sending end is set to 1, the receiving end needs to encrypt the return by using a private key, when the CT Bit of the returning party is set to 1, it represents that the data has been signed, and if the receiving end does not provide a valid signature in the return, the sending end discards the returned data; the block length is set to 16 bits, indicating the length of the control block, in bytes, excluding the pad field length. An alternative contains one or more fields prefixed by length, and the flag bit determines whether or not to contain these fields, and if so, must appear in this order: data identifier, username, password, token. Category object identifier, ontology object identifier, username, password, token, parameter fields.

Wherein, the TP flag bit and the LT flag bit are both set to 0, which represents that the subscribed category object is the category object itself; TP mark position 0, LT mark position 1, representing the display fields listing all the body objects under the appointed category object; TP mark position 1 and LT mark position 0, representing that the subscription is an ontology object, and the parameter condition of the subscription needs to be defined in the optional block, and the data format is defined by an asset category system provided by a service party; TP flag position 1 and LT flag position 1 represent all the parameters and descriptions listed for the operation of the ontology object.

In the stage of unsubscribing the asset object, the block type of the control block is set to be 2 bits, and the block type value is set to be 1, namely the type representing the block is the control block; the head type is set to 6 bits, and the head type value is set to 5, namely the function type representing the control block is the function of canceling the subscription asset object; the flag Bit is set to 8 bits, 8 flag bits can be predefined, Bit0 is a uf (user flag) flag Bit, which is set to 0, the option cannot contain the username field, and is set to 1, and the option must contain the username field; bit1 is a pf (password flag) flag Bit, which is set to 0, and optionally cannot contain a password field; set to 0, must contain a password field; bit2 is the TK (token) flag, set to 0, cannot contain tokens (tokens) in the alternative, set to 1, and must contain tokens in the alternative; bit3 is an RP (repeat) flag Bit that is set to 0, indicating that the data identifier was first issued, set to 1, indicating that the data identifier was previously issued but was not successful; bit4 is a CT (verified) flag Bit, when the CT Bit of the sending end is set to 1, the receiving end needs to encrypt the return by using a private key, when the CT Bit of the returning party is set to 1, it represents that the data has been signed, and if the receiving end does not provide a valid signature in the return, the sending end discards the returned data; bit5-7 is a number flag representing the number of unsubscribed asset objects contained; the block length is set to 16 bits, indicating the length of the control block, in bytes, excluding the pad field length. An alternative contains one or more fields prefixed by length, that is, the object identifier to unsubscribe. The number of identifiers of the object to be revoked must be the same as the number in the flag bit.

In the return stage of issuing the asset object, the block type of the control block is set to be 2 bits, and the block type value is set to be 1, namely the type representing the block is the control block; the head type is set to 6 bits, and the head type value is set to 6, namely, the function type representing the control block is the return function of the subscription asset object; the flag Bit is set to 8 bits, 7 flag bits can be predefined, Bit0 is a uf (user flag) flag Bit, which is set to 0, the option cannot contain the username field, and is set to 1, and the option must contain the username field; bit1 is a pf (password flag) flag Bit, which is set to 0, and optionally cannot contain a password field; set to 0, must contain a password field; bit2 is the TK (token) flag, set to 0, cannot contain tokens (tokens) in the alternative, set to 1, and must contain tokens in the alternative; bit3 is a CT (verified) flag Bit, when the CT Bit of the sending end is set to 1, the receiving end needs to encrypt the return by using a private key, when the CT Bit of the returning party is set to 1, it represents that the data has been signed, and if the receiving end does not provide a valid signature in the return, the sending end discards the returned data; bit4-6 is a status code number flag Bit representing the number of status codes contained in the return type control block of the subscribed asset object; the block length is set to 16 bits, indicating the length of the control block, in bytes, excluding the pad field length.

The data block is used for carrying specific data to be transmitted, and the data format is defined by an asset category system. The data transmitted in the data interoperability protocol are Asset Objects (AO), and the Asset objects are effectively organized through an Asset class system. The asset objects can be classified into category objects (Class AO) and Ontology objects (Ontology AO), the category objects represent the affiliation among data assets, category description information, meta-attribute information, and the like, and the Ontology objects are specific examples of the category objects and need to be consistent with the definitions and descriptions in the corresponding category objects. Ontology objects are further divided into data objects, which describe definitions and refer to data, and operation objects, which are operations on specified data.

And the asset category system divides the related people, objects and processes into objects according to the business requirements. After the original data is integrated according to the asset category system, the data is stably and invariably transmitted to the asset category system no matter how the front-end service changes the acquisition form, period, transmission mode and the like of the data. The asset category system can not be changed with the change of the upper layer morphology such as a business form operation activity scheme and the like to generate the bottom layer structure.

The category object is a concrete representation of an asset category system, and the category object comprises basic information for object creation, inheritance reference information and meta-attribute information. Fig. 5 is a schematic structural diagram of an object of a category. Object ID in FIG. 5 represents an Object identifier, a number unique to an asset Object; registry Time represents the registration Time, i.e., the Time when the asset object was created; the Expiration Time indicates the Expiration Time, i.e., the Time when the asset object is spent; the Modified Time represents the modification Time, namely the Time when the asset object was Modified last Time; the Father representation points to the higher level category object represented by the category object, represented by a set containing identifiers of inherited higher level category objects, such as: { Object ID1, Object ID2, … }; the attribute of Child representation attribute becomes a meta attribute; meta Attribute (Meta Attribute) is an Attribute description of a category object intended to use business-oriented terminology to help people and machines better understand, identify tags; the meta-attributes may mainly include category standards to which the attributes belong, attribute names, attribute descriptions, attribute processing types, value dictionaries, value types, examples, update cycles, security levels, object relationships, and the like; the attribute belongs to the category standard: i.e., the specification standard to which the attribute conforms, such as Eclass; attribute name: attribute naming should follow three major principles: privacy violation is avoided, the same attribute uses the same attribute name, and the same attribute uses the same statement structure; and attribute description: the attribute names are explained by one or two sentences, so that the problems of ambiguity, polysemy and the like of the attribute names caused by too short words are avoided; and (3) attribute processing type: the method comprises the following steps of dividing the processing types into original attribute, statistical attribute and algorithm attribute according to different processing types, wherein fields existing in an original data table of the original attribute become attributes after simple and regular adjustment, and the attributes can be used by service personnel, such as age, mobile phone number and the like; the statistical attribute represents that the original data becomes attribute-attributed service personnel, such as total number of commodities browsed in 7 days and the like, through processing, such as simple mathematical function operations of summation, averaging, regular expression and the like; the algorithm type attribute is a label of the deep processing type of the original data calculated by the model algorithm, such as 'labor waste' and the like; value dictionary: i.e. an enumeration of various possible values of an attribute, such as: the value dictionary of the "gender" attribute is [ male, female ]; the value type is as follows: data types of attribute values, such as numeric type, character type, date type, and the like; example (c): specific examples of attribute values; and (3) updating period: the update period of the attribute data is referred to; and (4) safety level: data security risks exist in the processes of acquiring data from source data, processing the data, enabling the data to be online and using the data, so that security levels are formulated for the attributes, and attribute use specifications of different levels are generated according to the security levels of the attributes; object relationship: the native attribute tags of category objects for fast and child can be further explained by the object relationship.

An ontology object is an asset instance created from a category object, which in turn may be divided into data objects and operation objects. Fig. 6 is a schematic structural diagram of an ontology object. In fig. 6, Class Object indicates an Object type, and represents that the type of the Object is a category Object; Data/Opera represents the object type, the Data representation is the Data object, and the Opera representation is the operation object; data ontology: the data format, semantics, period, security level and the like need to be consistent with those defined in the object of the category.

The credential block is used primarily to carry any digital signature signed by the message issuer, and to protect the control block and the contents of the data block from tampering during transmission, the data source being authentic.

Next, on the basis of the electronic device 100 shown in fig. 1, an embodiment of the present invention provides a global search method, please refer to fig. 7, where fig. 7 is a global search method provided in an embodiment of the present invention, and the global search method may include the following steps:

s401, subscription data is received based on a data interoperation protocol.

S402, performing access authority authentication on the subscription data.

And S403, after the authentication of the access authority of the subscription data is passed, searching and querying are carried out according to the keywords or the time sequence carried in the subscription data, and searching data are obtained.

It should be understood that the subscription data is an asset object, and the subscription terminal 200 packages the asset object into a message based on the control block, the data block and the certificate block of the data interoperability protocol, and sends the message to the electronic device 100 according to the transmission block of the data interoperability protocol.

The subscription data includes first operation type information and first identity information, and the electronic device 100 determines whether the first identity information is correct; if the first operation type information is correct, determining the access control condition of the subscription data according to the first operation type information; and authenticating the subscription data according to the access control condition.

It should be understood that, after receiving the subscription data, the electronic device 100 performs parsing to obtain first operation type information and first identity information, where the first operation type information is used to characterize a data transmission manner of the subscriber 200, and the first identity information may be obtained from a flag bit of the control block.

Specifically, the electronic device 100 is preset with access control conditions, that is, different subscription data have different operation types, different access control conditions are correspondingly set for different operation types, for example, an operation subscribing to a specified object is set with a corresponding access control condition, an operation canceling subscribing to the specified object is set with a corresponding access control condition, and a response operation at a receiving end of the subscription operation is set with a corresponding access control condition. The access control condition may be similar to a white list, the access control condition being stored in an access control policy database of the electronic device 100.

After receiving the subscription data, the electronic device 100 determines whether the identity is correct according to the first identity information, and the identity may be determined in a user name mode, a password mode, or a token mode. And after the identity is confirmed to be correct, determining whether a corresponding access control condition exists according to the first operation type, if so, performing authorization verification, and if the verification passes, opening a corresponding right. Electronic device 100 may also query or supplement other authorization mechanisms or modes through authorization management, system internal implementation, or other assistant agents.

In this embodiment, the electronic device 100 may further obtain data type information of the subscription data according to the flag bit of the control block, where the data type information represents whether the subscription data is a category object or an ontology object, and if the subscription data is the category object, the electronic device 100 determines whether there is an authority for operating the corresponding category object; if the body object is the corresponding body object, whether the corresponding body object has the operation authority is judged.

As shown in fig. 8, another global search method provided in the embodiment of the present application further includes, on the basis of fig. 7, the following steps:

s404, receiving the publishing data based on the data interoperation protocol.

S405, the write authority authentication is carried out on the issued data.

It should be understood that the publishing data is an asset object, and the publishing terminal 300 packages the asset object into a message based on the control block, the data block and the certificate block of the data interoperability protocol, and sends the message to the electronic device 100 according to the transmission block of the data interoperability protocol.

The release data includes the second operation type information and the second identity information, and the electronic device 100 determines whether the second identity information is correct; if the operation is correct, determining the write-in control condition of the release data according to the second operation type information; and authenticating the issued data according to the writing control condition.

It should be understood that the electronic device 100 receives the release data and then parses the release data to obtain second operation type information and second identity information, where the second operation type information is used to represent a manner of transmitting data to the release terminal 300, and the second identity information may be obtained from a flag bit of the control block.

Specifically, the electronic device 100 is preset with write control conditions, that is, different release data have different operation types, different write control conditions are correspondingly set for different operation types, for example, an operation of releasing a specified object is set with a corresponding write control condition, an operation of releasing an object update is set with a corresponding write control condition, an operation of releasing an object delete is set with a corresponding write control condition, and an operation of responding to an release is set with a corresponding write control condition. The write control conditions may be similar to a white list, the write control conditions being stored in an access control policy database of the electronic device 100.

After receiving the release data, the electronic device 100 determines whether the identity is correct according to the second identity information, and the identity determination mode may be a user name mode, a password mode, or a token mode. And after the identity is confirmed to be correct, determining whether a corresponding write-in control condition exists according to the second operation type, if so, performing authorization verification, and if the verification passes, opening a corresponding right.

In this embodiment, the electronic device 100 may further obtain data type information of the release data according to the flag bit of the control block, where the data type information represents whether the release data is a category object or an ontology object, and if the release data is the category object, the electronic device 100 determines whether there is an authority for operating the corresponding category object; if the body object is the corresponding body object, whether the corresponding body object has the operation authority is judged.

Referring to fig. 8, the global search method further includes the following steps:

s406, if the issued data is determined to be the category object data according to the data type information.

And S407, comparing the category object data with the existing category object data after the issued data write permission passes the authentication.

And S408, if the data are not similar, comparing the category object data with the metadata standard recommended by the top-level node.

And S409, replacing the category object data with standard metadata if the similarity is smaller than a preset value.

And S410, if the similarity is greater than a preset value, creating a temporary standard database.

It should be understood that, for the published data, if the published data is the category object data, after the authority verification is passed, the published category object data is improved and recommended, so that the meaning of the uniformly consensus metadata is maximized, and a uniform standard is formed.

The electronic device 100 compares the published category object data with the existing category object data, and if the registration is similar, the publishing terminal 300 returns the existing category object data to recommend the user to use the registered category object data. If the similarity does not exist, comparing the published category object data with the metadata standard recommended by the top level node; and judging the similarity between each field of the issued category object data and metadata defined in the metadata standard, wherein the similarity can be judged by adopting a space vector distance method. If the similarity is smaller than a preset value, replacing the issued category object data with standard metadata; and if the similarity is greater than a preset value, creating a temporary standard database. At the same time, the improved category object data is returned to the publishing terminal 300.

If the release data is not released for the first time, has been released before but has not been successfully released, determining whether the release data is the same as the data recommended last time, and if so, returning the improved category object data to the release end 300; if the difference is not the same, the judgment is carried out by special personnel through the category object registration bureau, the uploaded category object data are unified, and the unified category object data are returned to the issuing end 300.

s411, if the issued data is determined to be the body object data according to the data type information.

And S412, after the issued data write authority passes the authentication, performing conformity judgment on the body object data.

It is to be understood that the conformity criterion may be whether the ontology object data conforms to the value dictionary and the value type in the category object, and conforms to the definition for the value, etc.

and S413, verifying the legality, the compliance, the relevance and the inheritance of the published data.

It is understood that the validity and compliance checks of the published data may be: and the digital asset object registration administration and the object examiner carry out validity and compliance check on the uploaded release data, wherein the validity and compliance check comprises whether the content is compliant or not, whether false or unreal conditions exist or not and the like.

The relevance and inheritance detection of the release data can be as follows: whether inheritance and relevance conflicts exist among the issued data or not is detected, and the conflict type comprises the problem of inconsistent front and back of the category relation. And traversing all objects below the asset category system in the published data, and checking whether the relationship between the objects is legal or not and whether the relationship accords with logic or not.

As shown in fig. 9, in one case of error, when traversing the published data object, it is found that the parent node of the next-level object does not match with the child node of the present-level object, child lacks the next level or the parent class lacks the previous level, or does not match.

As shown in FIG. 10, in another case of an error, a child object that is not recognized by the previous level is found to be present in the next level category when traversing the published data object.

In this embodiment, the electronic device 100 may determine whether to store the data in the cache according to the frequency and frequency of the accesses, so as to improve the access efficiency. And determining the effective time of the cache according to the frequency and the frequency of the access, and associating the related management content.

In order to implement the global search method corresponding to the above-mentioned S401 to S413 and possible sub-steps thereof, an embodiment of the present invention provides a global search apparatus, please refer to fig. 11, where fig. 11 is a block diagram of a global search apparatus 110 provided by an embodiment of the present invention, the global search apparatus 110 includes: a receiving module 111, an authority control module 112, a query search module 113, a standard recommendation module 114, a caching module 115, and an uploading module 116.

The receiving module 111 is configured to receive subscription data based on a data interoperability protocol.

The receiving module 111 is further configured to receive the publishing data based on the data interoperability protocol.

It should be understood that the receiving module 111 is configured to perform the above-described contents of S401 and S404.

The right control module 112 is used for performing access right authentication on the subscription data.

The authority control module 112 is also used for performing write authority authentication on the issue data.

The entitlement control module 112 is also used to perform legitimacy, compliance, association and inheritance checks on the published data.

The authority control module 112 is further configured to prevent the electronic device 100 from receiving a malicious attack, so that the electronic device 100 has a security protection function; periodic inspection can also be carried out, and the uploaded data can be required to be aged for a period of time or cannot be updated for a period of time; and whether the same data uploaded or queried is frequent or not can be determined, if so, the same data is stored in the cache module 115, otherwise, the same data is stored in the main database, and the data access efficiency can be improved.

It should be understood that the rights control module 112 is used to execute the above-described contents of S402, S405 and S413.

The query search module 113 is configured to perform search query according to the keywords or the time sequence carried in the subscription data after the subscription data access right authentication is passed, so as to obtain search data.

It should be understood that the query search module 113 is configured to execute the above-mentioned contents of S403.

The standard recommending module 114 is configured to determine that the release data is category object data according to the data type information; after the issued data write-in authority passes the authentication, comparing the category object data with the existing category object data; if not, comparing the category object data with the metadata standard recommended by the top-level node; if the similarity is smaller than a preset value, replacing the category object data with standard metadata; and if the similarity is greater than a preset value, creating a temporary standard database.

The standard recommending module 114 is further configured to determine that the release data is ontology object data according to the data type information; and after the issued data write-in authority passes the authentication, carrying out conformity judgment on the body object data.

It should be appreciated that the standard recommendation module 114 is configured to perform the above-described contents of S406-S412.

The uploading module 116 is used for uploading a certain category object to the national top level node and the universe search engine according to the frequency of use, the service requirement of the user and other factors, so that the asset object can be more easily searched and discovered, and a wider data service is provided for the user.

It should be understood that the receiving module 111, the authority control module 112, the query search module 113, the standard recommendation module 114, the caching module 115 and the uploading module 116 may cooperatively implement the above-mentioned S401 to S413 and possible sub-steps thereof.

In summary, the present application provides a global search method, apparatus, electronic device and computer storage medium, which receive subscription data through a data interoperability protocol; performing access authority authentication on subscription data; and after the subscription data access authority passes the authentication, searching and inquiring according to the keywords or the time sequence carried in the subscription data to obtain the search data. Data can be shared in a wider range through a data interoperation protocol, so that an industrial internet identification analysis system can be effectively interconnected and associated.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application 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, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. 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.

While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method for global search, the method comprising:

receiving subscription data based on a data interoperability protocol;

performing access authority authentication on the subscription data;

2. The method of claim 1, wherein the subscription data comprises first operation type information and first identity information, and wherein the step of authenticating the access right of the subscription data comprises:

judging whether the first identity information is correct or not;

if the first operation type information is correct, determining the access control condition of the subscription data according to the first operation type information;

and authenticating the subscription data according to the access control condition.

3. The method of claim 1, further comprising:

receiving release data based on a data interoperability protocol;

and performing write permission authentication on the release data.

4. The method according to claim 3, wherein the issue data includes second operation type information and second identity information, and the step of performing write right authentication on the issue data includes:

judging whether the second identity information is correct or not;

if the operation is correct, determining the write-in control condition of the release data according to the second operation type information;

and authenticating the release data according to the write-in control condition.

5. The method of claim 3, wherein the release data further includes data type information, and wherein after the step of performing write authorization authentication on the release data, the method further comprises:

if the issued data is determined to be category object data according to the data type information;

after the issued data write-in authority passes the authentication, comparing the category object data with the existing category object data;

if not, comparing the category object data with the metadata standard recommended by the top-level node;

if the similarity is smaller than a preset value, replacing the category object data with standard metadata;

and if the similarity is greater than the preset value, creating a temporary standard database.

6. The method of claim 3, wherein the release data further includes data type information, and wherein after the step of performing write authorization authentication on the release data, the method further comprises:

if the issued data is determined to be the body object data according to the data type information;

and after the issued data write-in authority passes the authentication, performing conformity judgment on the body object data.

7. The method of claim 3, further comprising:

and carrying out validity, compliance, relevance and inheritance tests on the release data.

8. A global search apparatus, comprising:

9. An electronic device comprising one or more processors, and memory for storing one or more programs; the one or more programs, when executed by the one or more processors, implement the method of any of claims 1-7.

10. A computer storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.