Enterprise information technology consulting service system based on internet of things technology

Abstract

The present application relates to the technical field of information technology consulting service, in particular to an enterprise information technology consulting service system based on Internet of Things technology, which comprises a benchmark unit, a collection unit, a continuity unit, a determination unit and a recording unit, receives enterprise identification, equipment identification, operation boundary and communication boundary, collects operation value and link value when consulting is submitted, generates sequential message, checks continuity, forms deviation level and blocking level according to boundary, generates cause attribution and verification instruction in combination with matter category, corrects and writes database when verification is inconsistent, in the present application, through benchmark constraint, sequential collection, continuous verification, level determination, terminal verification and recording write-back closed loop, the device out-of-bound and access blocking are associated with analysis in the same consulting link, the breakpoint data is blocked from entering the judgment process, the attribution deviation caused by single comparison is reduced, the consulting response accuracy is enhanced, the processing direction stability is handled, the verification basis integrity and the subsequent traceability reliability are enhanced.

Description

Technical Field

[0001] This invention relates to the field of information technology consulting services, and in particular to an enterprise information technology consulting service system based on Internet of Things (IoT) technology. Background Technology

[0002] The field of information technology consulting services involves information technology services that collect, store, and present enterprise information needs, equipment access information, and service records based on computer systems, enterprise terminals, network communication links, and databases. Traditional enterprise information technology consulting service systems based on Internet of Things (IoT) technology involve enterprise terminals sending IoT device identifiers, operating parameters, network connection status, and consulting matters to a server. The server then writes the received data into a consulting service database, and consultants use client applications to access enterprise files, equipment records, and consulting history to create service records.

[0003] Existing enterprise IT consulting services rely heavily on manual reporting of equipment and network status. Equipment operation data and communication link data are stored in a scattered manner, making it difficult to confirm the order of data collection after a consulting matter is triggered. Anomaly judgment often relies on comparison of a single indicator. There is a lack of linkage analysis between operational overruns and access blockages. Terminal verification results fail to correct the cause attribution in a timely manner. Service records lack support from overrun items and verification values, which can easily lead to biased processing and affect the accuracy of consulting responses, the efficiency of subsequent traceability, and the stability of responsibility determination. Summary of the Invention

[0004] The purpose of this invention is to address the shortcomings of existing technologies by proposing an enterprise information technology consulting service system based on Internet of Things (IoT) technology.

[0005] To achieve the above objectives, the present invention adopts the following technical solution: an enterprise information technology consulting service system based on Internet of Things (IoT) technology, the system comprising:

[0006] The reference unit is used to receive enterprise identification information, IoT device identification information, device rated operating boundary and communication access boundary, and write them into the enterprise access reference record;

[0007] The data acquisition unit, connected to the reference unit, is used to read the current current value, current temperature value, and current start / stop status of the equipment controller when an inquiry is submitted, read the current received signal strength, current number of data packet retransmissions, current number of connection interruptions, and service confirmation waiting time of the communication module, and generate a reporting message with a data acquisition sequence number.

[0008] The continuous unit, connected to the acquisition unit, is used to compare the acquisition sequence number in the reported message with the previous acquisition sequence number, output a continuous message when the sequence is continuous, and generate a supplementary acquisition instruction when the sequence is discontinuous.

[0009] The determination unit, connected to the continuous unit and the reference unit, is used to compare the device operation values ​​in the continuous messages with the device's rated operation boundary to generate an operation deviation level, compare the communication link values ​​with the communication access boundary to generate an access blockage level, and generate a cause attribution result and a terminal verification instruction based on the operation deviation level, the access blockage level, and the consultation item category information.

[0010] The recording unit, connected to the judgment unit, is used to receive verification messages, regenerate the cause attribution result when the out-of-bounds items are inconsistent, and write the cause attribution result, the out-of-bounds item that triggered the branch, the verification value, and the service processing pointer into the consulting service database.

[0011] As a further embodiment of the present invention, the reference unit includes an identification access submodule, a boundary registration submodule, and a reference writing submodule:

[0012] The identification access submodule receives enterprise identification information and IoT device identification information, performs a unique match between the enterprise identification information and the IoT device identification information, and outputs the identification verification result when the match fails.

[0013] The boundary registration submodule receives the device's rated operating boundary and communication access boundary, associates the device's rated operating boundary with the IoT device identification information, and associates the communication access boundary with the enterprise identification information;

[0014] The baseline writing submodule writes the identifier matching results, device rated operating boundaries, and communication access boundaries into the enterprise access baseline record, generating baseline registration results.

[0015] As a further embodiment of the present invention, the acquisition unit includes a control reading submodule, a link reading submodule, and a message generation submodule:

[0016] After the consultation is submitted, the control reading submodule sends a read request to the device controller based on the IoT device identification information, receives the current current value, current temperature value and current start / stop status, and generates the operation acquisition results.

[0017] The link reading submodule sends a link reading request to the communication module based on the enterprise identification information, receives the current received signal strength, the current number of data packet retransmissions, the current number of connection interruptions, and the service confirmation waiting time, and generates link acquisition results;

[0018] The message generation submodule encapsulates the running collection results and the link collection results according to the same collection sequence number to generate a reporting message.

[0019] As a further aspect of the present invention, the process of generating the collection sequence number specifically includes:

[0020] Obtain the submission time of the consultation matter, enterprise identification information and IoT device identification information, read the previous collection sequence number corresponding to the enterprise identification information and IoT device identification information in the enterprise access benchmark record, and update the previous collection sequence number to the current collection sequence number in ascending order;

[0021] If the previous collection sequence number is not found, the first collection marker corresponding to the submission time of the consultation matter is written into the sequence number field, and the sequence number field is associated with the running collection result and the link collection result to generate the sequence association result.

[0022] As a further aspect of the present invention, the continuous unit includes a sequential reading submodule, a continuous comparison submodule, and a supplementary sampling generation submodule:

[0023] The sequential reading submodule extracts the collection sequence number from the reported message and reads the previous collection sequence number corresponding to the enterprise identification information and IoT device identification information from the sequential cache record to generate a sequence comparison result.

[0024] The continuous comparison submodule compares the collection sequence number with the previous collection sequence number to determine the adjacent increasing relationship. When the collection sequence number satisfies the adjacent increasing relationship, the reported message is marked as a continuous message.

[0025] When the acquisition sequence number does not satisfy the adjacent incremental relationship, the supplementary acquisition generation submodule determines the missing sequence range based on the sequence comparison results and generates a supplementary acquisition instruction.

[0026] As a further aspect of the present invention, the process for determining the range of missing sequences specifically includes:

[0027] Obtain the collection sequence number and the previous collection sequence number from the sequence comparison results. Determine the sequence position after the previous collection sequence number and before the current collection sequence number as the sequence position to be supplemented. Associate the sequence position to be supplemented with the enterprise identification information and the IoT device identification information to generate a sequence record to be supplemented.

[0028] Accordingly, the supplementary sampling generation submodule writes the sequence record to be supplemented into the supplementary sampling instruction and sends the supplementary sampling instruction to the acquisition unit to generate the supplementary sampling trigger result.

[0029] As a further aspect of the present invention, the determination unit includes a running determination submodule, an access determination submodule, and an attribution generation submodule:

[0030] The operation judgment submodule reads the current current value, current temperature value, and current start / stop status from the continuous message, and reads the rated operating boundary of the equipment from the enterprise access benchmark record. It then compares the current current value, current temperature value, and current start / stop status with the rated operating boundary of the equipment to generate the operation deviation level.

[0031] The access determination submodule reads the current received signal strength, current data packet retransmission count, current connection interruption count, and service confirmation waiting time from the continuous messages, and reads the communication admission boundary from the enterprise access baseline record. It then compares the communication link values ​​with the communication admission boundary to generate the access obstruction level.

[0032] The attribution generation submodule reads the operational deviation level, access obstruction level, and consultation item category information, generates the cause attribution result according to the level priority relationship, and generates the terminal verification instruction based on the cause attribution result.

[0033] As a further aspect of the present invention, the process of generating deviation levels specifically includes:

[0034] Calculate the current deviation ratio of the current value relative to the upper limit of the rated current, calculate the temperature deviation ratio of the current value relative to the upper limit of the rated temperature, and generate a start / stop deviation flag based on the consistency relationship between the current start / stop state and the allowed start / stop state.

[0035] The current deviation ratio, temperature deviation ratio, and start / stop deviation marker are compared with the operating level range to determine the operating candidate level. When at least two operating candidate levels are inconsistent, the higher level is selected as the operating deviation level, and the operating level judgment result is generated.

[0036] As a further aspect of the present invention, the process of generating the access blockage level specifically includes:

[0037] Calculate the degree of signal insufficiency of the current received signal strength relative to the lower limit of the received signal strength, calculate the degree of retransmission exceeding the current number of data packet retransmissions relative to the upper limit of the number of data packet retransmissions, calculate the degree of interruption exceeding the current number of connection interruptions relative to the upper limit of the number of connection interruptions, and calculate the degree of waiting exceeding the service confirmation waiting time relative to the upper limit of the service confirmation waiting time.

[0038] The signal insufficiency, retransmission overrun, interruption overrun, and waiting overrun are compared with the access level range to determine the access candidate level, and an access blocking level is generated based on the higher access candidate level.

[0039] As a further aspect of the present invention, the recording unit includes a verification and parsing submodule, an attribution verification submodule, and a record writing submodule:

[0040] The verification parsing submodule receives the verification message, extracts the verification value, verification field name and terminal confirmation identifier from the verification message, and matches the verification field name with the out-of-bounds item that triggered the branch to generate the verification matching result;

[0041] When the verification and matching results show inconsistencies in out-of-bounds items, the attribution verification submodule re-compares the equipment's rated operating boundary or communication access boundary based on the verification values ​​and generates a corrected attribution result.

[0042] The record writing submodule writes the cause attribution result or the corrected attribution result, the out-of-bounds project that triggered the branch, the verification value and the service processing to the consulting service database, generating service record results.

[0043] The working principle and advantages of this invention are as follows:

[0044] In this invention, by uniformly writing enterprise identifiers, equipment identifiers, rated operating boundaries, and communication access boundaries into the access benchmark, the operating values ​​of the equipment controller and communication link are collected simultaneously when an inquiry is submitted. The continuity of the message is constrained by the collection sequence number, and missing collection triggers supplementary collection to prevent breakpoint data from entering the judgment link. Continuous data is then compared with the corresponding boundary to form the operating deviation level and access obstruction level. Combined with the inquiry category, the cause attribution and terminal verification requirements are generated. The verification message is reverse-corrected for inconsistent out-of-bounds items. The service database stores the cause, out-of-bounds items, verification values, and processing directions, thereby improving the consistency of inquiry judgment, the accuracy of response, and the completeness of traceability. Attached Figure Description

[0045] Figure 1 This is a flowchart illustrating the enterprise information technology consulting service process of this invention.

[0046] Figure 2 This is a schematic diagram illustrating the collaborative effect of the system modules of the present invention;

[0047] Figure 3 This is a schematic diagram illustrating the sequential continuous verification and supplementary sampling effect of the present invention;

[0048] Figure 4 This is a schematic diagram illustrating the effects of operational deviation and communication obstruction on the attribution of the present invention.

[0049] Figure 5 This is a schematic diagram illustrating the terminal verification and service record traceability effect of the present invention. Detailed Implementation

[0050] The technical solution of the present invention will now be described with reference to the accompanying drawings.

[0051] In embodiments of the present invention, words such as "exemplarily," "for example," etc., are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" in the present invention should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word "exemplary" is intended to present the concept in a concrete manner. Furthermore, in embodiments of the present invention, the meaning expressed by "and / or" can be both, or either one.

[0052] Example

[0053] Please see Figures 1 to 5 This embodiment provides an enterprise information technology consulting service system based on Internet of Things (IoT) technology. In practical applications, for example, during the continuous operation of enterprise field IoT devices, device controllers, communication modules, and consulting service terminals on the enterprise information technology consulting platform, consulting matters are submitted by the enterprise service terminal. The operating data and communication link data of the enterprise field IoT devices are synchronously entered into the consulting service platform. The platform completes benchmark registration, field collection, sequential continuous verification, cause attribution, terminal verification, and service record writing within the same business system boundary, including a benchmark unit, a collection unit, a continuous unit, a judgment unit, and a recording unit.

[0054] The baseline unit serves as the baseline data carrier structure before enterprise access. It receives enterprise identification information, IoT device identification information, device rated operating boundaries, and communication access boundaries, and writes them into the enterprise access baseline record. Enterprise identification information is the enterprise's access identity field in the consulting service platform, carrying the enterprise account, access permissions, and communication affiliation. IoT device identification information is the device identity field of the enterprise's on-site IoT devices within the platform, carrying the device controller address, device type, and device affiliation. Device rated operating boundaries are a set of configuration fields bound to IoT device identification information, including operating judgment boundaries such as rated current upper limit, rated temperature upper limit, and allowed start / stop states. These boundaries originate from device access registration data, device controller configuration items, or device operation rules imported by the enterprise. Communication access boundaries are a set of configuration fields bound to enterprise identification information, including link judgment boundaries such as received signal strength lower limit, data packet retransmission count upper limit, connection interruption count upper limit, and service confirmation waiting time upper limit. These boundaries originate from the enterprise's communication access policy, communication module configuration items, or the consulting service platform's access rule table.

[0055] The enterprise access baseline record is a persistent record generated by the baseline unit and invoked by subsequent units. It carries enterprise identification information, IoT device identification information, identification matching status, device rated operating boundaries, communication access boundaries, a sequence number field, baseline registration status, and access permission identifiers. The sequence number field is used to verify the collection order of subsequent reported messages. It retains its initial state when the device first accesses the consultation matter processing link, and when there are already consecutive collection records, it is written back from the sequence cache record to form the previous collection sequence number. The baseline unit does not perform on-site data collection or generate cause attribution results; its output serves only as the baseline input for the collection unit, judgment unit, and recording unit.

[0056] The identification access submodule receives enterprise identification information and IoT device identification information, and performs a unique match between the enterprise identification information and the IoT device identification information. Unique matching means confirming, in the enterprise access baseline record and device registration index, that the IoT device identification information corresponding to the same enterprise identification information does not conflict with other enterprise access relationships, and confirming that the device controller address and enterprise access permissions are within the same authorization boundary. During matching, the enterprise account status, device registration status, and controller access status are read, and cases with incomplete field formats, inconsistent enterprise permissions, conflicting device ownership, or mismatched controller addresses are marked as identification verification results.

[0057] The identifier verification result is a status record output by the identifier access submodule, including the enterprise identifier field to be verified, the IoT device identifier field to be verified, the verification trigger reason, and the return path. This result is sent to the access verification interface of the consulting service platform and simultaneously written to the baseline registration log. When a match fails, the identifier access submodule does not output a valid identifier matching result to subsequent submodules to prevent unconfirmed devices from entering the data acquisition link; when a match succeeds, it outputs the identifier matching result, which serves as input for the boundary registration submodule to establish boundary association relationships.

[0058] The boundary registration submodule receives the device's rated operating boundary and communication access boundary, associating the device's rated operating boundary with IoT device identification information and the communication access boundary with enterprise identification information. The upper limit of rated current, the upper limit of rated temperature, and the permissible start / stop status in the device's rated operating boundary serve as the baseline boundaries for the current field, temperature field, and start / stop field, respectively. These field values ​​are not disclosed in the form of example data but rather form engineering boundaries based on device configuration sources, enterprise authorization sources, and platform rule sources. The lower limit of received signal strength, the upper limit of data packet retransmission count, the upper limit of connection interruption count, and the upper limit of service acknowledgment waiting time in the communication access boundary serve as the access boundaries for the link signal field, retransmission count field, interruption count field, and acknowledgment waiting field, respectively. The source of these field boundaries is consistent with the enterprise's communication access strategy.

[0059] The boundary registration submodule performs integrity, field name, and source verification on the received boundary fields. Integrity verification confirms that both the operational and communication boundaries contain the necessary fields for subsequent determination; field name verification confirms that the fields submitted by the enterprise match the platform's preset field names; and source verification confirms that the boundary fields originate from device configuration, enterprise authorization configuration, or platform access rules. Upon successful verification, the device's rated operational boundary is written to the device boundary slot corresponding to the IoT device identification information, and the communication access boundary is written to the communication boundary slot corresponding to the enterprise identification information, forming a boundary association result. If verification fails, a boundary registration exception status is generated and returned to the baseline writing submodule, which then blocks the baseline registration completion status.

[0060] The benchmark writing submodule writes the identifier matching results, device rated operating boundaries, and communication access boundaries into the enterprise access benchmark record, generating the benchmark registration result. During writing, the identifier matching result serves as the record's primary index, the device rated operating boundary as the device operating determination field group, the communication access boundary as the communication link determination field group, and the sequence number field as the initialization field for continuous data collection verification. The benchmark writing submodule also writes the record source, writing status, access permission identifier, and log index, ensuring that subsequent data collection units only read enterprise access benchmark records within their own permission scope.

[0061] The benchmark registration result is a status object output by the benchmark writing submodule to the acquisition unit and the judgment unit, including the registration completion status, the range of readable fields, and the exception return status. The registration completion status allows the acquisition unit to read the device controller and communication module when the consultation item is submitted; the range of readable fields limits the call boundaries of the acquisition unit, continuous unit, judgment unit, and recording unit to the enterprise access benchmark record; the exception return status keeps the consultation item in a pending review state when the boundary is missing, the identifier conflicts, or the write fails, and retains the source of the exception in the log to prevent subsequent modules from using incomplete benchmark data by default.

[0062] The data acquisition unit connects to the baseline unit. Upon submission of an inquiry, it reads the current current value, current temperature value, and current start / stop status of the device controller, as well as the current received signal strength, current data packet retransmission count, current connection interruption count, and service confirmation waiting time of the communication module. It then generates a reporting message with a data acquisition sequence number. Inquiry submission is a business trigger signal issued by the enterprise service terminal, carrying enterprise identification information, IoT device identification information, and inquiry category information. The inquiry category information is a classification field submitted by the terminal, indicating whether the inquiry request involves categories such as device operation, communication access, service confirmation, or comprehensive inquiry. This field serves as a branching auxiliary basis when the determination unit generates the cause attribution result.

[0063] The reported message is a data object generated by the acquisition unit and sent to the continuous unit. It includes enterprise identification information, IoT device identification information, current current value, current temperature value, current start / stop status, current received signal strength, current data packet retransmission count, current connection interruption count, service confirmation waiting time, inquiry category information, acquisition sequence number, and message integrity status. The acquisition unit does not determine the operational deviation level or access obstruction level. Its responsibilities are limited to reading field fields, encapsulating operational acquisition results and link acquisition results under the same acquisition sequence number, and outputting the reported message.

[0064] After an inquiry is submitted, the control reading submodule sends a read request to the device controller based on the IoT device identification information. It receives the current current value, current temperature value, and current start / stop status, and generates the operational data acquisition results. The device controller is the control interface node for the enterprise's field IoT devices, providing the capability to read the device's operational status. The read request includes the IoT device identification information, the enterprise access permission identifier, and the data acquisition trigger identifier. Before sending the request, the control reading submodule reads the readable fields in the baseline registration results to confirm that the inquiry has the necessary permissions to access the device controller.

[0065] The current current value is the current status field returned by the device controller, the current temperature value is the temperature status field returned by the device controller, and the current start / stop status is the operating switch status field returned by the device controller. After receiving the fields, the control reading submodule performs field name verification, source verification, and message parsing verification. If a field is missing, the field source does not match, the controller does not respond, or parsing fails, an abnormal operation status is written to the operation acquisition result, and the abnormal field name and abnormal return path are retained. When the fields are complete, the operation acquisition result, carrying the current current value, current temperature value, current start / stop status, and operation field integrity identifier, is output to the message generation submodule.

[0066] The link reading submodule sends a link reading request to the communication module based on the enterprise identification information, receives the current received signal strength, the current number of data packet retransmissions, the current number of connection interruptions, and the service confirmation waiting time, and generates link acquisition results. The communication module is the access link node between the enterprise's on-site IoT devices and the consulting service platform, and is responsible for signal reception, data retransmission, interruption recording, and service confirmation waiting status. The link reading request includes enterprise identification information, communication access permission identifier, and consulting matter trigger identifier. Before sending, the link reading submodule reads the enterprise access relationship corresponding to the communication access boundary to confirm that the link reading object is consistent with the current enterprise access relationship.

[0067] The current received signal strength is the signal reception status field returned by the communication module; the current number of data packet retransmissions is the data retransmission count field returned by the communication module; the current number of connection interruptions is the connection interruption count field returned by the communication module; and the service confirmation wait time is the service confirmation wait status field returned by the communication module. The link reading submodule performs field name verification, link source verification, and parsing verification on the link fields. If the communication module does not respond, the field format is inconsistent, the link source is inconsistent with the enterprise identification information, or field parsing fails, the link acquisition result is written to the link acquisition abnormal status, and the abnormal status is returned to the message generation submodule. When the fields are complete, the link acquisition result carries the link fields and the link field integrity identifier, and is output to the message generation submodule.

[0068] The message generation submodule encapsulates the runtime collection results and the link collection results according to the same collection sequence number to generate a reporting message. The collection sequence number is a sequence identifier field in the consultation item processing link, used to mark the sequential relationship of collection messages under the same enterprise identification information and the same IoT device identification information. The message generation submodule obtains the consultation item submission time, enterprise identification information, and IoT device identification information, reads the previous collection sequence number corresponding to the enterprise identification information and IoT device identification information in the enterprise access benchmark record, and updates the previous collection sequence number to the current collection sequence number in ascending order. The ascending order is a platform-preset order rule, which expresses the collection order through the adjacency relationship of the sequence field, and is not disclosed as a numerical example in the embodiment.

[0069] When the previous collection sequence number is not found, the message generation submodule writes the first collection marker corresponding to the submission time of the consultation matter into the sequence number field, and associates the sequence number field with the running collection result and the link collection result to generate a sequence association result. The first collection marker is the sequence field in the initial state, used to indicate that the current message belongs to the starting collection record of the consultation matter processing link under the enterprise's device access relationship. When the running collection result or the link collection result has an abnormal state, the message generation submodule still writes the abnormal state into the reported message, but marks the message integrity status as pending review, so that the continuous unit can identify the sequence relationship and the judgment unit can distinguish between data missing and boundary out-of-bounds.

[0070] The continuous unit connects to the acquisition unit, compares the acquisition sequence number in the reported message with the previous acquisition sequence number, outputs a continuous message when the data is continuous, and generates a supplementary acquisition instruction when it is discontinuous. The continuous message is a data object formed after the reported message has undergone sequence verification, carrying the operation field, link field, consultation item category information, and continuous status identifier from the reported message. The supplementary acquisition instruction is a control command generated by the continuous unit and sent to the acquisition unit, carrying the missing sequence range, enterprise identification information, IoT device identification information, and the range of fields to be supplemented, used to trigger the acquisition unit to reread the field data corresponding to the missing sequence position.

[0071] The responsibility of the continuous unit is limited to sequence verification and supplementary sampling triggering. It does not change the rated operating boundaries of the equipment, nor does it generate operating deviation levels or access obstruction levels. The sequence cache record is a cache object maintained by the continuous unit, which stores the previously confirmed continuous sampling sequence number, enterprise identification information, IoT device identification information, and cache status. When the cache status expires, the cache is missing, or the cache is inconsistent with the enterprise access baseline record, the continuous unit reads the sequence number field in the enterprise access baseline record as an alternative verification source and writes the alternative source into the continuous processing log.

[0072] The sequential reading submodule extracts the collection sequence number from the reported message and reads the previous collection sequence number corresponding to the enterprise identification information and IoT device identification information from the sequential cache record, generating a sequence comparison result. The sequence comparison result is an intermediate object output by the sequential reading submodule, containing the current collection sequence number, the previous collection sequence number, the enterprise identification information, the IoT device identification information, the cache source status, and a read error status. The read error status indicates situations such as cache missing, cache expired, inconsistent identification, or the reported message lacking a sequence field.

[0073] When a reported message lacks enterprise identification information or IoT device identification information, the sequential reading submodule does not proceed to the continuous comparison submodule. Instead, it marks the message as missing identification and returns it to the acquisition unit. If the current acquisition sequence number is missing, the format is inconsistent with the platform's sequence rules, or the message arrives repeatedly, the sequential reading submodule generates a sequence anomaly record and writes it to the continuous processing log. When the current acquisition sequence number and the previous acquisition sequence number can be read, the sequence comparison result is sent to the continuous comparison submodule.

[0074] The continuous comparison submodule compares the collection sequence number with the previous collection sequence number based on their adjacent increasing relationship. When the collection sequence numbers satisfy the adjacent increasing relationship, the reported message is marked as a continuous message. The adjacent increasing relationship is a close-proximity relationship formed by the sequence fields under the same enterprise identification information and the same IoT device identification information according to the platform's order rules. This is used to confirm that there are no missing sequence positions between consecutive collection records. The continuous comparison submodule only compares the sequence fields under the same enterprise and the same device, and does not merge sequence caches across enterprises or devices.

[0075] When the current collection sequence number satisfies an adjacent increasing relationship, the continuous comparison submodule retains the running field, link field, consultation item category information, and message integrity status from the reported message, adds a continuous status identifier, and outputs a continuous message to the judgment unit. When there is a missing sequence position between the current collection sequence number and the previous collection sequence number, the continuous comparison submodule does not output a continuous message to the judgment unit, but instead sends the sequence comparison result to the supplementary collection generation submodule. When the current collection sequence number is the same as or regresses from the previous collection sequence number, the continuous comparison submodule marks the message as a duplicate sequence status or a regressed sequence status, and hands it over to the supplementary collection generation submodule to generate a supplementary collection instruction with a verification identifier.

[0076] When the acquisition sequence numbers do not satisfy the adjacent incremental relationship, the supplementary acquisition generation submodule determines the missing sequence range based on the sequence comparison results and generates a supplementary acquisition instruction. The missing sequence range is the set of sequence positions that have not been confirmed by consecutive units after the previous acquisition sequence number and before the current acquisition sequence number. This set is only used as a description of the sequence positions and is not disclosed as a numerical example. The supplementary acquisition generation submodule associates the sequence positions to be supplemented with enterprise identification information and IoT device identification information to generate a sequence record to be supplemented.

[0077] The sequence record to be supplemented is written into a supplementary sampling instruction, which is then sent to the acquisition unit to generate a supplementary sampling trigger result. The supplementary sampling trigger result is a status object after the acquisition unit receives the supplementary sampling instruction, including the supplementary sampling reception status, the range of fields to be supplemented, and the supplementary sampling return path. The acquisition unit rereads the device controller and communication module according to the supplementary sampling instruction, and the reported message generated by the supplementary sampling still enters the continuous unit for sequence verification. If the supplementary sampling instruction is not confirmed, the acquisition unit returns a failure, or the sequence record to be supplemented cannot correspond to the enterprise access baseline record, the supplementary sampling generation submodule writes to the supplementary sampling exception log and outputs exception trace information to the recording unit to prevent missing sequences from being skipped due to lack of records.

[0078] The judgment unit is connected to the continuous unit and the reference unit. It compares the equipment operating values ​​in the continuous message with the equipment's rated operating boundary to generate an operating deviation level, and compares the communication link values ​​with the communication access boundary to generate an access blockage level. Based on the operating deviation level, access blockage level, and inquiry category information, it generates a cause attribution result and a terminal verification instruction. The equipment operating values ​​are the current current value, current temperature value, and current start / stop status in the continuous message. The communication link values ​​are the current received signal strength, current data packet retransmission count, current connection interruption count, and service confirmation waiting time in the continuous message.

[0079] The "Operational Deviation Level" is an operational status level field generated by the judgment unit, indicating the deviation of the device's operational field from its rated operational boundary. The "Access Impedance Level" is a link status level field generated by the judgment unit, indicating the impedance status of the communication link field relative to the communication access boundary. The "Cause Attribution Result" is a structured result output by the judgment unit to the recording unit and the consulting service terminal, carrying the attribution branch, the boundary-crossing items triggering the branch, the field names involved in the judgment, and the service processing pointer candidates. The "Terminal Verification Instruction" is a confirmation instruction sent by the judgment unit to the enterprise service terminal, containing the field names requiring terminal verification, verification source requirements, and the return message path.

[0080] The operation judgment submodule reads the current current value, current temperature value, and current start / stop status from continuous messages, and reads the equipment's rated operating boundary from the enterprise access benchmark record. It then compares the current current value, current temperature value, and current start / stop status with the equipment's rated operating boundary to generate an operation deviation level. When comparing the current current value with the rated current upper limit, the operation judgment submodule generates a current deviation degree field, indicating whether the current current field is approaching or exceeding the rated current upper limit. When comparing the current temperature value with the rated temperature upper limit, the operation judgment submodule generates a temperature deviation degree field, indicating whether the current temperature field is approaching or exceeding the rated temperature upper limit. When comparing the current start / stop status with the permissible start / stop status, the operation judgment submodule generates a start / stop deviation flag, indicating whether the on-site start / stop status is consistent with or inconsistent with the benchmark permissible status.

[0081] The operating level range is a lookup rule field in the enterprise access baseline record that corresponds to the rated operating boundary of the equipment. It originates from equipment configuration rules, enterprise authorization policies, and platform operating judgment rules. The operating judgment submodule maps the current deviation field, temperature deviation field, and start / stop deviation flag to the operating candidate levels. When there is inconsistency between operating candidate levels, the operating judgment submodule selects the level with the stricter constraints as the operating deviation level using a preset level priority relationship. This level priority relationship is written into the operating judgment rule field in the enterprise access baseline record and subsequently called by the attribution generation submodule. When consecutive packets show abnormal operating acquisition states, the operating judgment submodule does not directly judge the abnormal field as out of bounds. Instead, it generates an operating verification pending state and writes the abnormal field name into the terminal verification instruction candidate content.

[0082] The access determination submodule reads the current received signal strength, current packet retransmission count, current connection interruption count, and service acknowledgment waiting time from continuous packets. It also reads the communication admission boundary from the enterprise access baseline record and compares the communication link values ​​with the communication admission boundary to generate an access obstruction level. When comparing the current received signal strength with the lower limit of received signal strength, the access determination submodule generates a signal insufficiency field, indicating the insufficient state of the link reception relative to the admission boundary. When comparing the current packet retransmission count with the upper limit of packet retransmission count, a retransmission exceedance field is generated, indicating the exceeding state of packet retransmission relative to the admission boundary. When comparing the current connection interruption count with the upper limit of connection interruption count, an interruption exceedance field is generated. When comparing the service acknowledgment waiting time with the upper limit of service acknowledgment waiting time, a waiting exceedance field is generated.

[0083] The access level range is a lookup rule field in the enterprise access baseline record that corresponds to the communication access boundary, derived from communication access rules, enterprise service rules, and platform link determination rules. The access determination submodule maps the signal insufficiency level, retransmission exceedance level, interruption exceedance level, and waiting exceedance level fields to access candidate levels, and generates access obstruction levels based on a preset access level priority relationship. When candidate levels conflict, the access determination submodule uses the candidate level with the stricter constraints as the output level. When a link field has acquisition anomalies, parsing failures, or incomplete communication module return status, the access determination submodule generates an access pending verification status and writes the corresponding field name into the terminal verification instruction candidate content.

[0084] The attribution generation submodule reads the operational deviation level, access obstruction level, and consultation item category information, generates a cause attribution result according to the level priority relationship, and generates a terminal verification instruction based on the cause attribution result. The level priority relationship is the attribution judgment rule field stored by the platform in the enterprise access baseline record, which carries the branch priority rule between the operational deviation level and the access obstruction level. When the constraint status corresponding to the operational deviation level is higher than that of the access obstruction level, the cause attribution result is assigned to the device operation branch. When the constraint status corresponding to the access obstruction level is higher than that of the operational deviation level, the cause attribution result is assigned to the communication access branch. When the operational deviation level and the access obstruction level are in the same constraint status or both are in the pending verification status, the attribution generation submodule reads the consultation item category information to perform branch correction.

[0085] When the consultation item category information points to operational issues such as equipment inability to start or stop, abnormal equipment operation, or abnormal equipment control response, the attribution generation submodule prioritizes writing operational-side out-of-bounds items into the cause attribution result. When the consultation item category information points to communication issues such as connection abnormalities, service confirmation waiting, or data synchronization delays, the communication-side out-of-bounds items are prioritized into the cause attribution result. When the consultation item category information is associated with both branches, the attribution generation submodule writes the trigger fields from both the operational and communication sides into the terminal verification instruction, but the cause attribution result still retains one main attribution branch and one branch to be verified, to avoid the recording unit receiving conflicting attribution fields. After the terminal verification instruction is sent to the enterprise service terminal, the terminal reads the on-site verification value according to the field names listed in the instruction and returns a verification message.

[0086] The recording unit connects to the judgment unit, receives verification messages, and regenerates the cause attribution result when there is inconsistency in out-of-bounds items. It then writes the cause attribution result, the out-of-bounds item triggering the branch, the verification value, and the service processing pointer into the consulting service database. The verification message is a data object returned by the enterprise service terminal based on the terminal verification command, carrying the verification field name, verification value, terminal confirmation identifier, verification source identifier, and message parsing status. The service processing pointer is the processing route field written by the recording unit to the consulting service database, indicating the service processing direction of the consulting matter, such as equipment control verification, communication access verification, service confirmation review, or manual review. The service processing pointer only serves as an internal service route within the platform and does not change the baseline boundary of the equipment controller or communication module.

[0087] The consulting service database serves as a persistent storage object for the recording unit, storing the cause attribution result, corrected attribution results, out-of-bounds items that triggered branches, verification field names, verification values, service processing directions, associated enterprise identification information, IoT device identification information, collection sequence number, and audit trail status. Database writes employ field validation, permission validation, and log recording. If a write fails, permission validation fails, or the database returns an exception, the recording unit generates a write exception status and returns this status to the consulting service platform's service processing interface, keeping the verification message and cause attribution result in a pending write state.

[0088] The verification parsing submodule receives the verification message, extracts the verification value, verification field name, and terminal confirmation identifier from the message, and matches the verification field name with the out-of-bounds item that triggered the branch, generating a verification matching result. The verification value is the field value after the terminal rereads or confirms the fields specified in the terminal verification command. The verification field name is the field identifier corresponding to the verification value, and the terminal confirmation identifier is the status identifier indicating the verification source and return path of the enterprise service terminal. The verification parsing submodule performs source verification, field verification, and parsing verification on the verification message, confirming that the verification message and the original terminal verification command belong to the same enterprise identification information, the same IoT device identification information, and the same collection sequence number.

[0089] When the verification field name matches the out-of-bounds item in the triggering branch, the verification parsing submodule generates a matching status. When the verification field name does not match the out-of-bounds item in the triggering branch, an inconsistent status is generated, and the verification field name, the original triggering field name, and the terminal confirmation identifier are retained. When the verification message lacks a verification value, the terminal confirmation identifier is invalid, the verification source is inconsistent with the instruction source, or the message parsing fails, the verification parsing submodule outputs a verification exception status. The recording unit writes this status into the pending verification field of the consulting service database, without directly overwriting the cause attribution result already generated by the judgment unit.

[0090] When the verification matching results show inconsistencies in out-of-bounds items, the attribution verification submodule re-compares the equipment's rated operating boundary or communication access boundary based on the verification values ​​to generate a corrected attribution result. If the verification field name belongs to the operating field, the attribution verification submodule reads the equipment's rated operating boundary from the enterprise access baseline record and compares the verification value with the corresponding operating boundary using text rules to obtain the operating-side verification status. If the verification field name belongs to the communication field, the attribution verification submodule reads the communication access boundary from the enterprise access baseline record and compares the verification value with the corresponding communication boundary using text rules to obtain the communication-side verification status.

[0091] The corrected attribution result is a structured output from the attribution review submodule to the record writing submodule. It carries the corrected attribution branch, the corrected trigger field, the original cause attribution result reference relationship, and the verification basis. If the verification value still points to the original trigger branch after comparison with the baseline boundary, the attribution review submodule retains the cause attribution result and writes a verification consistency flag. If the verification value points to a different branch or the original trigger field no longer meets the out-of-bounds item rules, the attribution review submodule generates a corrected attribution result and uses the corrected out-of-bounds item as input to the record writing submodule. If the verification value cannot correspond to the equipment's rated operating boundary or communication access boundary, the attribution review submodule generates a boundary mismatch status and sends this status to the record writing submodule for manual review service processing.

[0092] The record writing submodule writes the cause attribution result or corrected attribution result, the out-of-bounds item triggering the branch, the verification value, and the service processing pointer to the consultation service database, generating service record results. The cause attribution result comes from the judgment unit, the corrected attribution result comes from the attribution review submodule, the out-of-bounds item triggering the branch comes from the attribution generation submodule or the attribution review submodule, the verification value comes from the verification parsing submodule, and the service processing pointer is written by the record writing submodule to the corresponding service routing field based on the attribution branch, verification status, and consultation item category information.

[0093] The service record result is the output status after the consulting service database has been written, including the record completion status, record index, attribution field status, and subsequent service processing entry point. Before writing, the record writing submodule performs field integrity checks to confirm that the enterprise identification information, IoT device identification information, collection sequence number, attribution branch, out-of-bounds project, verification fields, and service processing pointers all have sources. If a field is missing, a record status of "to be completed" is generated; if the database write fails, a write exception status is generated; and if the service processing pointer cannot correspond to the platform service route, a service route "to be reviewed" status is generated. After recording, the consulting service database retains the entire link relationship from the enterprise access baseline record, reporting message, continuous message, cause attribution result, terminal verification command, verification message to the service record result, enabling enterprise IT consulting services to trace the source, judgment process, verification status, and service processing direction of each field within the same business system.

[0094] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. An enterprise information technology consulting service system based on Internet of Things (IoT) technology, characterized in that, include: The reference unit is used to receive enterprise identification information, IoT device identification information, device rated operating boundary and communication access boundary, and write them into the enterprise access reference record; The data acquisition unit, connected to the reference unit, is used to read the current current value, current temperature value, and current start / stop status of the equipment controller when an inquiry is submitted, read the current received signal strength, current number of data packet retransmissions, current number of connection interruptions, and service confirmation waiting time of the communication module, and generate a reporting message with a data acquisition sequence number. The continuous unit, connected to the acquisition unit, is used to compare the acquisition sequence number in the reported message with the previous acquisition sequence number, output a continuous message when the sequence is continuous, and generate a supplementary acquisition instruction when the sequence is discontinuous. The determination unit, connected to the continuous unit and the reference unit, is used to compare the device operation values ​​in the continuous messages with the device's rated operation boundary to generate an operation deviation level, compare the communication link values ​​with the communication access boundary to generate an access blockage level, and generate a cause attribution result and a terminal verification instruction based on the operation deviation level, the access blockage level, and the consultation item category information. The recording unit, connected to the judgment unit, is used to receive verification messages, regenerate the cause attribution result when the out-of-bounds items are inconsistent, and write the cause attribution result, the out-of-bounds item that triggered the branch, the verification value, and the service processing pointer into the consulting service database.

2. The enterprise information technology consulting service system based on Internet of Things technology according to claim 1, characterized in that, The reference unit includes an identification access submodule, a boundary registration submodule, and a reference writing submodule: The identification access submodule receives enterprise identification information and IoT device identification information, performs a unique match between the enterprise identification information and the IoT device identification information, and outputs the identification verification result when the match fails. The boundary registration submodule receives the device's rated operating boundary and communication access boundary, associates the device's rated operating boundary with the IoT device identification information, and associates the communication access boundary with the enterprise identification information; The baseline writing submodule writes the identifier matching results, device rated operating boundaries, and communication access boundaries into the enterprise access baseline record, generating baseline registration results.

3. The enterprise information technology consulting service system based on Internet of Things technology according to claim 1, characterized in that, The acquisition unit includes a control reading submodule, a link reading submodule, and a message generation submodule: After the consultation is submitted, the control reading submodule sends a read request to the device controller based on the IoT device identification information, receives the current current value, current temperature value and current start / stop status, and generates the operation acquisition results. The link reading submodule sends a link reading request to the communication module based on the enterprise identification information, receives the current received signal strength, the current number of data packet retransmissions, the current number of connection interruptions, and the service confirmation waiting time, and generates link acquisition results; The message generation submodule encapsulates the running collection results and the link collection results according to the same collection sequence number to generate a reporting message.

4. The enterprise information technology consulting service system based on Internet of Things technology according to claim 3, characterized in that, The process of generating the collection sequence number specifically includes: Obtain the submission time of the consultation matter, enterprise identification information and IoT device identification information, read the previous collection sequence number corresponding to the enterprise identification information and IoT device identification information in the enterprise access benchmark record, and update the previous collection sequence number to the current collection sequence number in ascending order; If the previous collection sequence number is not found, the first collection marker corresponding to the submission time of the consultation matter is written into the sequence number field, and the sequence number field is associated with the running collection result and the link collection result to generate the sequence association result.

5. The enterprise information technology consulting service system based on Internet of Things technology according to claim 1, characterized in that, The continuous unit includes a sequential reading submodule, a continuous comparison submodule, and a supplementary sampling generation submodule: The sequential reading submodule extracts the collection sequence number from the reported message and reads the previous collection sequence number corresponding to the enterprise identification information and IoT device identification information from the sequential cache record to generate a sequence comparison result. The continuous comparison submodule compares the collection sequence number with the previous collection sequence number to determine the adjacent increasing relationship. When the collection sequence number satisfies the adjacent increasing relationship, the reported message is marked as a continuous message. When the acquisition sequence number does not satisfy the adjacent incremental relationship, the supplementary acquisition generation submodule determines the missing sequence range based on the sequence comparison results and generates a supplementary acquisition instruction.

6. The enterprise information technology consulting service system based on Internet of Things technology according to claim 5, characterized in that, The process of determining the missing order range specifically includes: Obtain the collection sequence number and the previous collection sequence number from the sequence comparison results. Determine the sequence position after the previous collection sequence number and before the current collection sequence number as the sequence position to be supplemented. Associate the sequence position to be supplemented with the enterprise identification information and the IoT device identification information to generate a sequence record to be supplemented. Accordingly, the supplementary sampling generation submodule writes the sequence record to be supplemented into the supplementary sampling instruction and sends the supplementary sampling instruction to the acquisition unit to generate the supplementary sampling trigger result.

7. The enterprise information technology consulting service system based on Internet of Things technology according to claim 1, characterized in that, The determination unit includes a running determination submodule, an access determination submodule, and an attribution generation submodule: The operation judgment submodule reads the current current value, current temperature value, and current start / stop status from the continuous message, and reads the rated operating boundary of the equipment from the enterprise access benchmark record. It then compares the current current value, current temperature value, and current start / stop status with the rated operating boundary of the equipment to generate the operation deviation level. The access determination submodule reads the current received signal strength, current data packet retransmission count, current connection interruption count, and service confirmation waiting time from the continuous messages, and reads the communication admission boundary from the enterprise access baseline record. It then compares the communication link values ​​with the communication admission boundary to generate the access obstruction level. The attribution generation submodule reads the operational deviation level, access obstruction level, and consultation item category information, generates the cause attribution result according to the level priority relationship, and generates the terminal verification instruction based on the cause attribution result.

8. The enterprise information technology consulting service system based on Internet of Things technology according to claim 7, characterized in that, The process of generating deviation levels specifically includes: Calculate the current deviation ratio of the current value relative to the upper limit of the rated current, calculate the temperature deviation ratio of the current value relative to the upper limit of the rated temperature, and generate a start / stop deviation flag based on the consistency relationship between the current start / stop state and the allowed start / stop state. The current deviation ratio, temperature deviation ratio, and start / stop deviation marker are compared with the operating level range to determine the operating candidate level. When at least two operating candidate levels are inconsistent, the higher level is selected as the operating deviation level, and the operating level judgment result is generated.

9. The enterprise information technology consulting service system based on Internet of Things technology according to claim 7, characterized in that, The process of generating the access blockage level specifically includes: Calculate the degree of signal insufficiency of the current received signal strength relative to the lower limit of the received signal strength, calculate the degree of retransmission exceeding the current number of data packet retransmissions relative to the upper limit of the number of data packet retransmissions, calculate the degree of interruption exceeding the current number of connection interruptions relative to the upper limit of the number of connection interruptions, and calculate the degree of waiting exceeding the service confirmation waiting time relative to the upper limit of the service confirmation waiting time. The signal insufficiency, retransmission overrun, interruption overrun, and waiting overrun are compared with the access level range to determine the access candidate level, and an access blocking level is generated based on the higher access candidate level.

10. The enterprise information technology consulting service system based on Internet of Things technology according to claim 1, characterized in that, The recording unit includes a verification and parsing submodule, an attribution verification submodule, and a record writing submodule: The verification parsing submodule receives the verification message, extracts the verification value, verification field name and terminal confirmation identifier from the verification message, and matches the verification field name with the out-of-bounds item that triggered the branch to generate the verification matching result; When the verification and matching results show inconsistencies in out-of-bounds items, the attribution verification submodule re-compares the equipment's rated operating boundary or communication access boundary based on the verification values ​​and generates a corrected attribution result. The record writing submodule writes the cause attribution result or the corrected attribution result, the out-of-bounds project that triggered the branch, the verification value and the service processing to the consulting service database, generating service record results.

Images