Equipment identification method and device, electronic equipment, medium and product

Abstract

The embodiment of the invention discloses an equipment identification method and device, electronic equipment, a storage medium and a product, and the method comprises the steps: responding to an equipment registration request of a client, and analyzing the equipment registration request to obtain target equipment feature information of equipment where the client is located; determining a target equipment identification rule matched with the target equipment characteristic information according to a mapping relation between the equipment characteristic information and a preset equipment identification rule; performing information processing on the target equipment feature information based on a target equipment identification rule, and determining an equipment identifier corresponding to the equipment registration request; the process of processing the target equipment identification information comprises the process of executing at least one of the implementation methods of the creating equipment, the updating equipment and the inquiring equipment according to the target equipment characteristic information. According to the technical scheme provided by the embodiment of the invention, the equipment registration request can be processed by uniformly configuring the management equipment rule to determine the equipment identifier, so that the function realization and maintenance of the equipment identification engine are facilitated.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and in particular to a device identification method, apparatus, electronic device, medium, and product. Background Technology

[0002] When a device connects to the business service system, the business system uses a rule-based device identification scheme through the device middleware to identify terminal devices such as mobile phones and personal computers (PCs), and then generates a unique ID (Identity document) for the corresponding terminal device.

[0003] However, during the code development and iteration process, as the types of terminal devices increase, the number of device identification rules also increases, and the rule implementation statements become complex and scattered. This makes it inconvenient for engineers to iterate and maintain the device identification rules, and the development and troubleshooting costs are often high. Summary of the Invention

[0004] This disclosure provides a device identification method, apparatus, electronic device, medium, and product, which can process device registration requests through unified configuration management of device rules to determine device identifiers, thereby facilitating the functional implementation and maintenance of the device identification engine.

[0005] In a first aspect, embodiments of this disclosure provide a device identification method, the method comprising:

[0006] In response to the client's device registration request, the device registration request is parsed to obtain the target device characteristic information of the client's device;

[0007] Based on the mapping relationship between device feature information and preset device identification rules, determine the target device identification rule that matches the target device feature information;

[0008] Based on the target device identification rules, the target device feature information is processed to determine the device identifier corresponding to the device registration request;

[0009] The preset device identification rules include a set of implementation methods for creating, updating, and querying devices based on a domain-specific language. The process of processing the target device identification information includes executing at least one of the implementation methods for creating, updating, and querying devices based on the target device feature information.

[0010] Secondly, embodiments of this disclosure also provide a device identification apparatus, the apparatus comprising:

[0011] The device information acquisition module is used to respond to the client's device registration request, parse the device registration request to obtain the target device characteristic information of the device where the client is located;

[0012] The device identification rule determination module is used to determine the target device identification rule that matches the target device feature information based on the mapping relationship between device feature information and preset device identification rules.

[0013] The device identifier determination module is used to process the feature information of the target device based on the target device identification rules and determine the device identifier corresponding to the device registration request.

[0014] The preset device identification rules include a set of implementation methods for creating, updating, and querying devices based on a domain-specific language. The process of processing the target device identification information includes executing at least one of the implementation methods for creating, updating, and querying devices based on the target device feature information.

[0015] Thirdly, embodiments of this disclosure also provide an electronic device, the electronic device comprising:

[0016] One or more processors;

[0017] Storage device for storing one or more programs.

[0018] When the one or more programs are executed by the one or more processors, the one or more processors implement the device identification method as described in any embodiment of this disclosure.

[0019] Fourthly, embodiments of this disclosure also provide a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform the device identification method as described in any of the embodiments of this disclosure.

[0020] Fifthly, embodiments of this disclosure also provide a computer program product, including a computer program that, when executed by a processor, implements the device identification method as described in any of the embodiments of the present invention.

[0021] In this embodiment, in response to a client's device registration request, the system parses the request to obtain the target device feature information of the client's device. Based on the mapping relationship between the device feature information and preset device identification rules, it determines the target device identification rule that matches the target device feature information. Based on the target device identification rule, it processes the target device feature information to determine the device identifier corresponding to the device registration request. The preset device identification rules include a set of implementation methods for creating, updating, and querying devices predefined in a domain-specific language. The process of processing the target device identification information includes executing at least one of the implementation methods for creating, updating, and querying devices based on the target device feature information. This embodiment solves the problem of complex, fragmented, and difficult-to-maintain device identification rules. It allows the device identification engine to determine the corresponding target device identification rule, and the unified configuration management of device rules to process the device registration request to determine the device identifier, thus facilitating the functional implementation and maintenance of the device identification engine. Attached Figure Description

[0022] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0023] Figure 1 This is a schematic flowchart of a device identification method provided in an embodiment of this disclosure;

[0024] Figure 2 This is a schematic diagram illustrating the determination of target device identification rules provided in an embodiment of this disclosure;

[0025] Figure 3 This is a schematic flowchart of a device identification method provided in an embodiment of this disclosure;

[0026] Figure 4 This is a schematic flowchart of a device identification method provided in an embodiment of this disclosure;

[0027] Figure 5 This is a schematic diagram of a device feature information structure conversion process provided in an embodiment of this disclosure;

[0028] Figure 6 This is a schematic flowchart of a device identification method provided in an embodiment of this disclosure;

[0029] Figure 7 This is a schematic diagram of the structure of a device identification device provided in an embodiment of this disclosure;

[0030] Figure 8This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Detailed Implementation

[0031] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0032] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0033] The term "comprising" and its variations as used herein are open-ended inclusion, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0034] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0035] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0036] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0037] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0038] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose whether to "agree" or "disagree" to provide personal information to the electronic device.

[0039] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0040] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0041] Figure 1 This is a flowchart illustrating a device identification method provided in an embodiment of the present disclosure. This embodiment is applicable to scenarios that respond to device registration requests from application clients. The method can be executed by a device identification device, which can be implemented in software and / or hardware. Optionally, the device identification device can be implemented by an electronic device, such as a mobile terminal, a PC, or a server.

[0042] like Figure 1 As shown, the device identification method includes:

[0043] S110. In response to the client's device registration request, parse the device registration request to obtain the target device characteristic information of the device where the client is located.

[0044] A device registration request is a request initiated by an application client to the corresponding server (device engine) before obtaining application services. Device registration is the process of recording specific device information of the terminal device where the application client resides into the corresponding application service system or platform. Its main purpose is to enable the corresponding terminal device to be identified, managed, and interact with other systems or services during the use of the services provided by the application, so as to realize the corresponding application service content. The device engine is a server equipped with a device identification device. After receiving the client's device registration request, it parses the device request content to obtain the target device characteristic information of the client's device.

[0045] The target device feature information can be at least one of the following device-related features: device serial number, model, brand, system type, system version number, and advertising identifier. The target device feature information can be used to represent the identifiable characteristics of the terminal device, and to generate a corresponding device identifier or to perform device queries. A single target device feature information, or a combination of one or more target device feature information, can uniquely identify a terminal device.

[0046] S120. Based on the mapping relationship between device feature information and preset device identification rules, determine the target device identification rule that matches the target device feature information.

[0047] The mapping relationship between device feature information and preset device identification rules can be pre-configured to determine the target device identification rules that match the target device feature information.

[0048] Specifically, the corresponding target device identification rule can be determined based on one or more device feature information. For example, the target device identification rule matching the target device feature information can be determined based on the mapping relationship between at least one of the terminal device's brand, system type, and system version information and the preset device identification rule.

[0049] For example, such as Figure 2 As shown, three preset device identification rules (DeviceCase) are provided: DeviceCase for iOS operating system, DeviceCase for lower versions of Android system, and DeviceCase for higher versions of Android system. The target DeviceCase can be determined by combining the operating system type and system version number.

[0050] S130. Based on the target device identification rules, process the target device feature information to determine the device identifier corresponding to the device registration request.

[0051] The preset device identification rules include a set of implementation methods for creating, updating, and querying devices, predefined based on a domain-specific language. The process of processing target device feature information based on these rules can include executing at least one of the implementation methods for creating, updating, and querying devices based on the target device feature information. Each preset device identification rule can be independently configured, corresponding to a configuration file. The configuration file structures for different preset device identification rules are identical, including a configuration layer, a data access layer, and a rule layer (business logic layer). These layers can interact through pre-configured functional interfaces. The configuration layer manages the metadata during the application of the device identification rules; the data access layer manages the corresponding device identifier and device feature information database through preset data read / write interfaces; and the rule layer specifies the concrete logical processes for implementing the methods for creating, updating, and querying devices. In application, the preset device identification rules implement the overall functional logic of device identification through the configuration layer, data access layer, and rule layer.

[0052] In determining a device identifier, the process begins by querying the database to see if the target device, as indicated by the target device characteristic information, already exists. This checks whether the device identifier corresponding to the target device characteristic information already exists, i.e., whether the device of the client issuing the device registration request has already been registered. If so, the retrieved device identifier is used as the device identifier corresponding to the device registration request. Otherwise, a new device identifier is generated based on the target device characteristic information to complete the device registration and respond to the device registration request. Furthermore, if the device of the client issuing the device registration request has already been registered and a corresponding device identifier exists, but the device characteristic information corresponding to that device identifier has been updated, a device update operation can be performed to update the current target device characteristic information in the corresponding database.

[0053] In this embodiment, in response to a client's device registration request, the system parses the request to obtain the target device feature information of the client's device. Based on the mapping relationship between the device feature information and preset device identification rules, a target device identification rule matching the target device feature information is determined. Information processing is performed on the target device feature information based on the target device identification rule to determine the device identifier corresponding to the device registration request. The preset device identification rules include a set of implementation methods for creating, updating, and querying devices predefined in a domain-specific language. The process of processing the target device identification information includes executing at least one of the implementation methods for creating, updating, and querying devices based on the target device feature information. This embodiment solves the problem of complex, fragmented, and difficult-to-maintain device identification rules. It allows the device identification engine to determine the corresponding target device identification rule, and the unified configuration management of device rules to process the device registration request to determine the device identifier, thus facilitating the functional implementation and maintenance of the device identification engine.

[0054] Figure 3 This is a flowchart illustrating a device identification method provided in an embodiment of the present disclosure. Based on the above embodiment, it further explains the process of querying a device and generating a new device identifier in response to a device registration request. This method can be executed by a device identification device, which can be implemented in software and / or hardware, optionally through an electronic device, such as a mobile terminal, PC, or server.

[0055] like Figure 3 As shown, the device identification method includes:

[0056] S210. In response to the client's device registration request, parse the device registration request to obtain the target device characteristic information of the device where the client is located.

[0057] S220. Based on the mapping relationship between device feature information and preset device identification rules, determine the target device identification rule that matches the target device feature information.

[0058] S230. Based on the index relationship between at least one feature information in the target device feature information and the device identifier, query the device identifier that matches the target device feature information.

[0059] The index relationship is a predefined mapping relationship between at least one feature information and a device identifier.

[0060] In existing technologies, a complete set of logic for creating, querying, and updating devices is usually built based on device type. This means that each additional device type will require an additional set of such logic, resulting in an O(N) complexity increase in the number of lines of code and making maintenance inconvenient.

[0061] This embodiment focuses on the logic of querying and updating devices based on the index. This reduces the complexity of the configuration file for pre-defined device identification rules.

[0062] In one optional implementation, one or more features can be randomly selected from the target device feature information to query a device identifier that matches the target device feature information. If no device identifier matching the target device feature information is found during a single device identifier query, other device features can be selected from the target device feature information to perform the device identifier query.

[0063] In an optional implementation, the information query priority of the feature information or combination of feature information in the target device feature information can be pre-configured. According to the information query priority of the feature information in the target device feature information, at least one feature information is selected from the target device feature information in descending order of priority. Then, according to the index relationship between the selected at least one feature information and the device identifier, the device identifier that matches the target device feature information can be queried until the corresponding device identifier is found or the target device feature information is traversed.

[0064] S240. Use the queried device identifier as the device identifier corresponding to the device registration request.

[0065] Using the queried device identifier as the device identifier corresponding to the device registration request can prevent duplicate registration of devices.

[0066] S250. If no device identifier is found, generate a new device identifier according to the preset identifier generation rules.

[0067] If no device identifier is found, it indicates that the terminal device of the client that issued the device registration request had not registered before issuing the request. In this case, a new device identifier can be generated using preset identifier generation rules.

[0068] S260. Use the new device identifier as the device identifier corresponding to the device registration request, establish a mapping relationship between the new device identifier and at least one feature information, and store the target device feature information.

[0069] Establish a mapping relationship between the new device identifier and at least one feature information, and establish an index relationship between the new device identifier and at least one feature information in the target device feature information, so as to serve as the query basis for the subsequent device query process.

[0070] The technical solution of this disclosure, in response to a client's device registration request, parses the device registration request to obtain the target device feature information of the client's device; determines the target device identification rule matching the target device feature information based on the mapping relationship between the device feature information and preset device identification rules; queries the device identifier matching the target device feature information based on the index relationship between at least one feature information in the target device feature information and the device identifier; uses the queried device identifier as the device identifier corresponding to the device registration request; if no device identifier is found, generates a new device identifier according to preset identifier generation rules; uses the new device identifier as the device identifier corresponding to the device registration request, establishes a mapping relationship between the new device identifier and at least one feature information, and stores the target device feature information. The technical solution of this disclosure solves the problem of complex, fragmented, and difficult-to-maintain device identification rules. It allows the device identification engine to determine the corresponding target device identification rule, and the unified configuration management of device rules processes the device registration request to determine the device identifier, facilitating the functional implementation and maintenance of the device identification engine. Furthermore, the index-oriented query in device queries significantly reduces the complexity of the device identification rule algorithm.

[0071] Figure 4 This is a flowchart illustrating a device identification method provided in an embodiment of the present disclosure. Based on the above embodiment, the process of updating device feature information is further explained. This method can be executed by a device identification device, which can be implemented in software and / or hardware, optionally through an electronic device, such as a mobile terminal, PC, or server.

[0072] like Figure 4 As shown, the device identification method includes:

[0073] S310. In response to the client's device registration request, parse the device registration request to obtain the target device characteristic information of the device where the client is located.

[0074] In one implementation, after receiving a device registration request, a locking operation can be performed on the request to ensure that the device identifier corresponding to certain key device characteristics remains consistent within a certain period after device creation. This way, even if a write operation fails during creation, the same device identifier will be retrieved from the corresponding database based on the key device characteristics when the device registration request re-enters, preventing the creation of unnecessary device identifiers in the backend. Furthermore, it functions as a distributed lock, because device creation involves writes to multiple storage layers, and allowing concurrent requests might lead to data write discrepancies. The locking operation function implements this process by constructing "lock" and "unlock" interfaces, which users can choose to implement according to their actual needs.

[0075] S320. Determine whether the information structure of the target device feature information is the target information structure; if the information structure of the target device feature information is not the target information structure, perform information structure transformation on the target device feature information to obtain the target device feature information represented by the target information structure.

[0076] The device information structure used within the device engine equipped with a device identification device is defined using a domain-specific language. It can represent complete device information or a portion of a field to be updated in a device update request. This structure may differ from the information structure of systems or platforms that do not employ the device identification method of this embodiment. For example, if the device engine obtains a device registration request via a remote procedure call, and the information structure of the request content differs from the information structure that the engine can recognize and process, then information structure conversion is required so that the device engine can further respond to the device registration request.

[0077] For example, such as Figure 5 As shown, a code generation tool can be used to convert between different information structures according to a preset configuration. Information structure conversion can be performed between the first information structure corresponding to the external request of the device engine and the target information structure of the device engine itself. Alternatively, information structure conversion can be performed between the target information structure and the second information structure of the data access layer storing device identification rules (e.g., the old information structure before adopting the scheme of this embodiment).

[0078] S330. Based on the mapping relationship between device feature information and preset device identification rules, determine the target device identification rule that matches the target device feature information.

[0079] S340. Based on the information query priority of the feature information in the target device feature information, select at least one feature information in the target device feature information in turn.

[0080] The index relationship is a predefined mapping between at least one feature and a device identifier. An index relationship can be a key-value pair mapping, where the key is at least one selected feature from the target device's feature information, and the corresponding value is the device identifier.

[0081] S350. Based on the index relationship between at least one selected feature information and the device identifier, query the device identifier that matches the target device feature information until the corresponding device identifier is found or the target device feature information is traversed.

[0082] Specifically, when performing a device query, based on the index relationship between at least one selected feature and the device identifier, an index query interface matching the index type of the index relationship can be used to query the device identifier that matches the target device feature. The index type can be based on the index update method or the result categorized by key-value mapping method. The update method can be an overwrite update or a non-overwrite update. In some scenarios, devices may appear in pairs or groups, resulting in a one-to-many relationship rather than a traditional one-to-one mapping. Therefore, during the device query process, different index interfaces can be called according to the corresponding index type to query the device identifier.

[0083] S360. Use the queried device identifier as the device identifier corresponding to the device registration request.

[0084] S370. When the target device feature information is not completely identical to the device feature information associated with the queried device identifier, update the target device feature information to the target device information data table.

[0085] In some cases, a device identifier can be retrieved based on the target device's characteristic information. However, the device characteristic information associated with the retrieved device identifier is not entirely the same as the target device's characteristic information, indicating that the device characteristic information may have been updated, such as the device's corresponding advertising identification code. In this situation, the target device characteristic information can be used as the latest device characteristic information to update the corresponding device information storage space. The new device information does not need to overwrite the old device information during storage; both old and new information are retained.

[0086] The technical solution of this disclosure embodiment, in response to a client's device registration request, parses the device registration request to obtain the target device feature information of the device where the client is located; determines whether the information structure of the target device feature information is the target information structure; if the information structure of the target device feature information is not the target information structure, performs information structure transformation on the target device feature information to obtain the target device feature information represented by the target information structure; determines the target device identification rule matching the target device feature information according to the mapping relationship between the device feature information and the preset device identification rule; selects at least one feature information in the target device feature information in sequence according to the information query priority of the feature information in the target device feature information; queries the device identifier matching the target device feature information according to the index relationship between the selected at least one feature information and the device identifier, until the corresponding device identifier is found or the target device feature information is traversed; uses the queried device identifier as the device identifier corresponding to the device registration request; when the target device feature information and the device feature information associated with the queried device identifier are not completely the same, updates the target device feature information to the target device information data table. The technical solution of this disclosure solves the problem that current device identification rules are complex, fragmented, and difficult to maintain. The device identification engine can determine the corresponding target device identification rule, and the unified configuration management of device rules can process the device registration request to determine the device identifier. This facilitates the functional implementation and maintenance of the device identification engine and allows for the updating of device information.

[0087] Figure 6 This is a flowchart illustrating a device identification method provided in an embodiment of this disclosure. Based on the above embodiment, the process of configuring device identification rules is further explained. This method can be executed by a device identification device, which can be implemented in software and / or hardware, optionally through an electronic device, such as a mobile terminal, PC, or server.

[0088] like Figure 6 As shown, the device identification method includes:

[0089] S410. In the device identification rule configuration interface, in response to the creation operation of the data field associated with the device identifier, determine the metadata fields required during the application of the target device identification rule.

[0090] The device identification rule configuration interface provides the function of defining device identification rules. Users can use the functions of the device identification rule configuration interface to configure selection controls or input controls, create the metadata fields required in the application of the target device identification rule, and the business logic of device identification based on the metadata fields.

[0091] Determine the metadata fields required during the application of target device identification rules. This may include creating metadata field content, such as device type, brand, operating system type, operating system version, and advertising identification code, as well as information structure of device information, field update methods, and field data acquisition methods.

[0092] S420. In response to the configuration operation of the mapping relationship between metadata fields and device identifiers, determine the index relationship between metadata fields and device identifiers.

[0093] This involves determining the index relationship between metadata fields and device identifiers, and then determining which fields' corresponding device feature information to use for querying when querying a device.

[0094] The mapping relationship between metadata fields and device identifiers can be one metadata field corresponding to one device identifier, or multiple metadata fields corresponding to one device identifier.

[0095] S430, In response to the priority configuration operation of the index relationship, determine the query strategy in the process of querying the device identifier based on the index relationship.

[0096] This can also be understood as the logic and strategy for retrieving device identifiers based on device characteristic information. For example, the device identifier is first queried based on the highest priority index relationship. If it is not found, the query can then be performed based on the highest priority index relationship among the unused index relationships.

[0097] S440, in response to the configuration operation of the rule triggering conditions, determine the application conditions of the target device identification rule.

[0098] The rule triggering condition is the judgment condition that the device engine uses to determine the target device identification rule based on the target device's characteristic information. This condition can be expressed using a Boolean logic expression structure. For example, it can determine the corresponding target device identification rule based on device characteristic information such as device system type.

[0099] S450. The configuration file obtained through the above steps is used as a target device identification rule.

[0100] Users can configure different device recognition rules based on their specific device identification scenarios, using general configuration functions, for the device engine to invoke when responding to device registration requests. Alternatively, existing device recognition rules can be configured and modified to update business logic.

[0101] In addition, the device engine can provide additional function settings interfaces, allowing users to configure some custom function components to meet business implementation needs.

[0102] S460: In response to the client's device registration request, parse the device registration request to obtain the target device characteristic information of the device where the client is located.

[0103] S470. Based on the mapping relationship between device feature information and preset device identification rules, determine the target device identification rule that matches the target device feature information.

[0104] S480. Based on the target device identification rules, process the target device feature information to determine the device identifier corresponding to the device registration request.

[0105] The preset device identification rules include a set of implementation methods for creating, updating, and querying devices based on a domain-specific language. The process of processing the target device identification information includes executing at least one of the implementation methods for creating, updating, and querying devices based on the target device feature information.

[0106] The technical solution of this embodiment, in the device identification rule configuration interface, in response to the creation operation of the data field associated with the device identifier, determines the metadata fields required in the application process of the target device identification rule; in response to the mapping relationship configuration operation between the metadata fields and the device identifier, determines the index relationship between the metadata fields and the device identifier; in response to the priority configuration operation of the index relationship, determines the query strategy in the process of querying the device identifier according to the index relationship; in response to the rule triggering condition configuration operation, determines the application conditions of the target device identification rule; the configuration file obtained after the above steps is used as a target device identification rule; in response to the device registration request of the client, the device registration request is parsed to obtain the target device feature information of the device where the client is located; according to the mapping relationship between the device feature information and the preset device identification rule, the target device identification rule matching the target device feature information is determined; based on the target device identification rule, the target device feature information is processed to determine the device identifier corresponding to the device registration request. The technical solution of this disclosure solves the problem that current device identification rules are complex, fragmented, and difficult to maintain. It can provide a universal device rule configuration interface to uniformly configure device identification rules and uniformly manage device rules to process device registration requests to determine device identifiers. This can avoid omissions or errors that are very easy to occur during the iteration of device identification rules, and is conducive to the functional implementation and maintenance of the device identification engine.

[0107] Figure 7 This disclosure provides a device identification device suitable for scenarios where a device registration request is sent in response to an application client. The device identification device can be implemented in software and / or hardware and can be configured on an electronic device, such as a mobile terminal, a PC, or a server.

[0108] like Figure 7 As shown, the device identification device includes: a device information acquisition module 510, a device identification rule determination module 520, and a device identifier determination module 530.

[0109] The device information acquisition module 510 is used to respond to the device registration request from the client and parse the device registration request to obtain the target device feature information of the device where the client is located; the device identification rule determination module 520 is used to determine the target device identification rule that matches the target device feature information according to the mapping relationship between the device feature information and the preset device identification rule; the device identifier determination module 530 is used to process the target device feature information based on the target device identification rule to determine the device identifier corresponding to the device registration request; wherein, the preset device identification rule includes a set of implementation methods for creating, updating, and querying devices predefined based on a domain-specific language, and the process of processing the target device identification information includes the process of executing at least one of the implementation methods for creating, updating, and querying devices for the target device feature information.

[0110] The technical solution of this disclosure, in response to a client's device registration request, parses the device registration request to obtain the target device feature information of the client's device; determines the target device identification rule matching the target device feature information based on the mapping relationship between the device feature information and preset device identification rules; and processes the target device feature information based on the target device identification rule to determine the device identifier corresponding to the device registration request. The preset device identification rules include a set of implementation methods for creating, updating, and querying devices predefined based on a domain-specific language. The process of processing the target device identification information includes executing at least one of the implementation methods for creating, updating, and querying devices based on the target device feature information. This technical solution solves the problem of complex, fragmented, and difficult-to-maintain device identification rules. It allows the device identification engine to determine the corresponding target device identification rule, and the unified configuration management of device rules to process the device registration request to determine the device identifier, thus facilitating the functional implementation and maintenance of the device identification engine.

[0111] In one optional implementation, the device identification determination module 530 is specifically used for:

[0112] Based on the index relationship between at least one feature in the target device feature information and the device identifier, query the device identifier that matches the target device feature information; wherein, the index relationship is a predefined mapping relationship between at least one feature and the device identifier;

[0113] The queried device identifier will be used as the device identifier corresponding to the device registration request.

[0114] In an optional implementation, the device identification determination module 530 may be further used to:

[0115] Based on the information query priority of the feature information in the target device feature information, at least one feature information is selected sequentially from the target device feature information;

[0116] Based on the index relationship between at least one selected feature and the device identifier, query the device identifier that matches the target device feature until the corresponding device identifier is found or the target device feature is traversed.

[0117] In an optional implementation, the device identification determination module 530 may be further used to:

[0118] Based on the index relationship between at least one selected feature information and the device identifier, the device identifier that matches the target device feature information is queried through an index query interface that matches the index type of the index relationship.

[0119] In an optional implementation, the device identification determination module 530 can also be used for:

[0120] If no device identifier is found, a new device identifier is generated according to the preset identifier generation rules.

[0121] The new device identifier is used as the device identifier corresponding to the device registration request, and a mapping relationship is established between the new device identifier and at least one feature information, and the target device feature information is stored.

[0122] In an optional implementation, the device identification determination module 530 can also be used for:

[0123] If the target device feature information is not exactly the same as the device feature information associated with the queried device identifier, the target device feature information will be updated in the target device information data table.

[0124] In an optional implementation, the device information acquisition module 510 can also be used for:

[0125] After obtaining the target device feature information, determine whether the information structure of the target device feature information is the target information structure;

[0126] When the information structure of the target device feature information is not the target information structure, the target device feature information is transformed to obtain the target device feature information represented by the target information structure.

[0127] In one optional implementation, the device identification device further includes a rule configuration module for:

[0128] In the device identification rule configuration interface, in response to the creation operation of data fields associated with the device identifier, the metadata fields required for the application of the target device identification rule are determined; and / or,

[0129] In response to a configuration operation that establishes a mapping between metadata fields and device identifiers, the index relationship between metadata fields and device identifiers is determined; and / or,

[0130] In response to a priority configuration operation for index relationships, determine the query strategy during the process of querying device identifiers based on index relationships; and / or,

[0131] In response to the configuration operation of the rule triggering conditions, the application conditions of the target device identification rule are determined. The device identification device provided in the embodiments of this disclosure can execute the device identification method provided in any embodiment of this disclosure, and has the corresponding functional modules and beneficial effects of the method execution.

[0132] It is worth noting that the various units and modules included in the above-mentioned device are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the protection scope of the embodiments of this disclosure.

[0133] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Reference is made below. Figure 8 It illustrates an electronic device suitable for implementing embodiments of the present disclosure (e.g., Figure 8 The diagram below shows the structure of the terminal device or server 600. The terminal device in this embodiment may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), and vehicle terminals (e.g., vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. Figure 8 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0134] like Figure 8As shown, electronic device 600 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 602 or a program loaded from storage device 608 into random access memory (RAM) 603. The RAM 603 also stores various programs and data required for the operation of electronic device 600. The processing unit 601, ROM 602, and RAM 603 are interconnected via bus 604. An edit / output (I / O) interface 605 is also connected to bus 604.

[0135] Typically, the following devices can be connected to I / O interface 605: input devices 606 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 607 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 608 including, for example, magnetic tapes, hard disks, etc.; and communication devices 609. Communication device 609 allows electronic device 600 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 8 An electronic device 600 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0136] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 609, or installed from a storage device 608, or installed from a ROM 602. When the computer program is executed by the processing device 601, it performs the functions defined in the methods of embodiments of this disclosure.

[0137] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0138] The electronic device provided in this embodiment and the device identification method provided in the above embodiments belong to the same inventive concept. Technical details not described in detail in this embodiment can be found in the above embodiments, and this embodiment has the same beneficial effects as the above embodiments.

[0139] This disclosure also provides a computer storage medium storing a computer program that, when executed by a processor, implements the device identification method provided in the above embodiments.

[0140] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0141] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and end-to-end networks (e.g., ad hoc end-to-end networks), as well as any currently known or future-developed networks.

[0142] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0143] The aforementioned computer-readable medium carries one or more programs that, when executed by the electronic device, cause the electronic device to:

[0144] In response to the client's device registration request, the device registration request is parsed to obtain the target device characteristic information of the client's device;

[0145] Based on the mapping relationship between device feature information and preset device identification rules, determine the target device identification rule that matches the target device feature information;

[0146] Based on the target device identification rules, the target device feature information is processed to determine the device identifier corresponding to the device registration request;

[0147] The preset device identification rules include a set of implementation methods for creating, updating, and querying devices based on a domain-specific language. The process of processing the target device identification information includes executing at least one of the implementation methods for creating, updating, and querying devices based on the target device feature information.

[0148] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0149] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0150] The units described in the embodiments of this disclosure can be implemented in software or in hardware. The name of a unit does not necessarily limit the unit itself; for example, the first acquisition unit can also be described as "a unit that acquires at least two Internet Protocol addresses".

[0151] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0152] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0153] This disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the device identification method provided in any embodiment of this disclosure.

[0154] In implementing a computer program product, computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0155] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

[0156] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0157] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

Claims

1. A device identification method, characterized in that, include: In response to a client's device registration request, the device registration request is parsed to obtain the target device characteristic information of the device where the client is located; Based on the mapping relationship between device feature information and preset device identification rules, determine the target device identification rule that matches the target device feature information; Based on the target device identification rules, the target device feature information is processed to determine the device identifier corresponding to the device registration request; The preset device identification rules include a set of implementation methods for creating, updating, and querying devices predefined based on a domain-specific language. The process of processing the target device identification information includes executing at least one of the implementation methods for creating, updating, and querying devices on the target device feature information.

2. The method according to claim 1, characterized in that, The step of processing the target device feature information based on the target device identification rule to determine the device identifier corresponding to the device registration request includes: Based on the index relationship between at least one feature in the target device feature information and the device identifier, query the device identifier that matches the target device feature information; wherein, the index relationship is a predefined mapping relationship between the at least one feature and the device identifier; The queried device identifier is used as the device identifier corresponding to the device registration request.

3. The method according to claim 2, characterized in that, The step of querying the device identifier that matches the target device feature information based on the index relationship between at least one feature information in the target device feature information and the device identifier includes: Based on the information query priority of the feature information in the target device feature information, at least one feature information is selected sequentially from the target device feature information; Based on the index relationship between at least one selected feature information and the device identifier, query the device identifier that matches the target device feature information until a corresponding device identifier is found or the target device feature information is traversed.

4. The method according to claim 3, characterized in that, The step of querying the device identifier that matches the target device feature information based on the index relationship between at least one selected feature information and the device identifier includes: Based on the index relationship between at least one selected feature information and the device identifier, the device identifier that matches the target device feature information is queried through an index query interface that matches the index type of the index relationship.

5. The method according to claim 2, characterized in that, The step of processing the target device feature information based on the target device identification rule to determine the device identifier corresponding to the device registration request further includes: If no device identifier is found, a new device identifier is generated according to the preset identifier generation rules. The new device identifier is used as the device identifier corresponding to the device registration request, and a mapping relationship is established between the new device identifier and the at least one feature information, and the target device feature information is stored.

6. The method according to claim 2, characterized in that, The method further includes: If the target device feature information is not completely identical to the device feature information associated with the queried device identifier, the target device feature information will be updated in the target device information data table.

7. The method according to claim 1, characterized in that, After obtaining the target device feature information, the method further includes: Determine whether the information structure of the target device feature information is the target information structure; If the information structure of the target device feature information is not the target information structure, the target device feature information is transformed to obtain the target device feature information represented by the target information structure.

8. The method according to any one of claims 1-7, characterized in that, The configuration process for the target device identification rules includes: In the device identification rule configuration interface, in response to the creation operation of data fields associated with the device identifier, the metadata fields required for the application of the target device identification rule are determined; and / or, In response to a configuration operation on the mapping relationship between the metadata fields and the device identifier, the index relationship between the metadata fields and the device identifier is determined; and / or, In response to a priority configuration operation for the index relationship, a query strategy is determined during the process of querying a device identifier based on the index relationship; and / or, In response to the configuration operation of the rule triggering conditions, the application conditions of the target device identification rule are determined.

9. A device identification device, characterized in that, include: The device information acquisition module is used to respond to the device registration request from the client, parse the device registration request to obtain the target device feature information of the device where the client is located; The device identification rule determination module is used to determine the target device identification rule that matches the target device feature information based on the mapping relationship between device feature information and preset device identification rules; The device identifier determination module is used to process the feature information of the target device based on the target device identification rules, and determine the device identifier corresponding to the device registration request. The preset device identification rules include a set of implementation methods for creating, updating, and querying devices predefined based on a domain-specific language. The process of processing the target device identification information includes executing at least one of the implementation methods for creating, updating, and querying devices on the target device feature information.

10. An electronic device, characterized in that, The electronic device includes: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the device identification method as described in any one of claims 1-8.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the device identification method as described in any one of claims 1-8.

12. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the device identification method as described in any one of claims 1-8.

Images