Data updating method and device, and electronic device

Abstract

The application provides a data updating method and device and electronic equipment, wherein the method comprises the following steps: receiving an input request of a target wiring component, the input request comprising a target serial number corresponding to the target wiring component and a near-end service port; performing port conflict detection in the case that the target serial number belongs to a planned serial number set and the near-end service port is inconsistent with a near-end planned port corresponding to the target serial number in planned link data; the planned link data comprising a near-end planned port corresponding to each planned serial number in the planned serial number set; updating service link data in the case that there is no port conflict; the updated service link data comprising a near-end service port corresponding to the target serial number. The technical scheme provided by the application can avoid the case that the port is distorted, the port occupation relationship is inconsistent with the serial number binding relationship, thereby improving the data consistency and the comprehensive wiring management efficiency.

Description

Technical Field

[0001] This application relates to the field of data verification technology, and in particular to a data update method, apparatus and electronic device. Background Technology

[0002] The structured cabling of data centers / enterprise server rooms typically involves planning, procurement, construction, archiving, and operation and maintenance. Taking cabling components as cables as an example, the port connection relationships and serial numbers (SN) established during the planning phase often deviate from the actual business situation on the construction site due to reasons such as port adjustment for proximity, misplugging, temporary detours, equipment relocation, or phased construction.

[0003] In existing technologies, dealing with such discrepancies between specifications and actual conditions mainly relies on manual on-site verification and manual modification of database records, resulting in low efficiency in structured cabling management. Summary of the Invention

[0004] In view of this, embodiments of this application provide a data update method, apparatus, and electronic device for improving the efficiency of structured cabling management.

[0005] To achieve the above objectives, in a first aspect, embodiments of this application provide a data updating method, the method comprising: Receive a target cabling component entry request, the entry request including the target serial number and near-end service port corresponding to the target cabling component; If the target sequence number belongs to the planned sequence number set, and the near-end service port is inconsistent with the near-end planned port corresponding to the target sequence number in the planned link data, port conflict detection is performed; the planned link data includes the near-end planned ports corresponding to each planned sequence number in the planned sequence number set. If there is no port conflict, update the service link data; the updated service link data includes the near-end service port corresponding to the target sequence number.

[0006] In one possible implementation of the first aspect, the planned link data further includes remote planned ports corresponding to each of the planned sequence numbers, and the updated service link data includes link port pairs corresponding to the target sequence number, wherein the link port pairs include near-end service ports and remote service ports. The updated business link data includes: If there are multiple remote service ports corresponding to the target sequence number recorded in the service link data before the update, select one target remote service port from the multiple remote service ports corresponding to the target sequence number as the remote service port in the link port pair corresponding to the target sequence number.

[0007] In one possible implementation of the first aspect, the target remote service port is the remote service port with the highest priority among the plurality of remote service ports; Remote service ports with different data entry sources have different priorities; for remote service ports with the same data entry source, the earlier the data entry time, the higher the priority; the data entry source includes multiple of the following: data entry through data synchronization, data entry through QR code scanning, data entry through import, and manual entry.

[0008] In one possible implementation of the first aspect, the method further includes: Generate a transaction log corresponding to the input request. The transaction log includes at least one of the following: timestamp, port information corresponding to the target sequence number in the business link data before the update, port information corresponding to the target sequence number in the business link data after the update, and port conflict information.

[0009] In one possible implementation of the first aspect, if a port conflict exists, the entry is rejected and the reason for the conflict is recorded.

[0010] In one possible implementation of the first aspect, the method further includes: If the target sequence number does not belong to the planned sequence number set, the target sequence number is added to the planned sequence number set, and the business link data is updated.

[0011] In one possible implementation of the first aspect, a prompt message is issued before port conflict detection is performed; the prompt message is used to prompt the user whether to continue entering data. Upon receiving a request from the user to continue entering data, the port conflict detection is performed. If the user cancels the data entry request, the data entry will be cancelled.

[0012] Secondly, embodiments of this application provide a data updating apparatus, the apparatus comprising: A receiving module is used to receive an entry request for a target cabling component, the entry request including the target serial number and near-end service port corresponding to the target cabling component; The detection module is used to perform port conflict detection when the target sequence number belongs to the planned sequence number set and the near-end service port is inconsistent with the near-end planned port corresponding to the target sequence number in the planned link data; the planned link data includes the near-end planned ports corresponding to each planned sequence number in the planned sequence number set; The update module is used to update the service link data when there is no port conflict; the updated service link data includes the near-end service port corresponding to the target sequence number.

[0013] In one possible implementation of the second aspect, the planned link data further includes remote planned ports corresponding to each of the planned sequence numbers, and the updated service link data includes link port pairs corresponding to the target sequence numbers, the link port pairs including near-end service ports and remote service ports; The update module is also used for: If there are multiple remote service ports corresponding to the target sequence number recorded in the service link data before the update, select one target remote service port from the multiple remote service ports corresponding to the target sequence number as the remote service port in the link port pair corresponding to the target sequence number.

[0014] In one possible implementation of the second aspect, the target remote service port is the remote service port with the highest priority among the plurality of remote service ports; Remote service ports with different data entry sources have different priorities; for remote service ports with the same data entry source, the earlier the data entry time, the higher the priority; the data entry source includes multiple of the following: data entry through data synchronization, data entry through QR code scanning, data entry through import, and manual entry.

[0015] In one possible implementation of the second aspect, the apparatus further includes a generation module, the generation module further including: Generate a transaction log corresponding to the input request. The transaction log includes at least one of the following: timestamp, port information corresponding to the target sequence number in the business link data before the update, port information corresponding to the target sequence number in the business link data after the update, and port conflict information.

[0016] In one possible implementation of the second aspect, if a port conflict exists, the entry is rejected and the reason for the conflict is recorded.

[0017] In one possible implementation of the second aspect, the apparatus further includes a processing module, the processing module being configured to: If the target sequence number does not belong to the planned sequence number set, the target sequence number is added to the planned sequence number set, and the business link data is updated.

[0018] In one possible implementation of the second aspect, the device further includes a prompting module, which is used to: issue a prompting message before performing port conflict detection; the prompting message is used to prompt the user whether to continue entering data. The detection module is also used to: perform port conflict detection when a user's request to continue input is received; and cancel input when a user's request to cancel input is received.

[0019] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor, wherein the memory is used to store a computer program; and the processor is used to execute the method described in the first aspect or any embodiment of the first aspect when the computer program is invoked.

[0020] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in the first aspect or any embodiment of the first aspect.

[0021] Fifthly, embodiments of this application provide a computer program product that, when run on an electronic device, causes the electronic device to execute the data update method described in any one of the first aspects.

[0022] The technical solution provided in this application embodiment, upon receiving a request to input a target cabling component, can perform port conflict detection if the input target sequence number belongs to the planned sequence number set and the input near-end service port is inconsistent with the near-end planned port corresponding to the target sequence number in the planned link data; then, if there is no port conflict, the service link data is updated; the updated service link data includes the near-end service port corresponding to the input target sequence number. This enables automatic data detection and updating, reduces the error rate of manual verification and recording, and thus improves the management efficiency and reliability of structured cabling. Attached Figure Description

[0023] Figure 1 A flowchart illustrating the data update method provided in this application embodiment; Figure 2 This is a schematic diagram of a prompt window provided in an embodiment of this application; Figure 3 This is a schematic diagram of the structure of the data update device provided in the embodiments of this application; Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0024] To facilitate understanding of the technical solutions in the embodiments of this application, some terms involved in the embodiments of this application will be explained below: Serial Number Binding: Records the binding relationship between service SN and port ID using the service SN as the key or a combination of service SN and port identification (Port ID) as the key, and includes one or more of the following: binding version number, binding source (scanning / manual input / import / one-click synchronization) and binding timestamp.

[0025] PlanSN: Belongs to the planning domain and is used to indicate the sequence number / tag number assigned during the planning phase.

[0026] Business SN (BizSN): Belongs to the field domain and is used to indicate the serial number entered on-site during actual business operations.

[0027] Port: Includes fields such as port ID, device ID, rack ID, U-coordinates, port location (left / right) on the device, and port number.

[0028] Link: Records the link port pair between the near-end service port and the far-end service port, and can be associated with cabling component identifiers, path information and version numbers.

[0029] In existing technologies, the common practice for addressing issues such as "inconsistency between planning and actual business, distortion of link endpoints, port occupation conflicts, mismatched SN bindings, and untraceable changes" is "scanning / entering → writing to the ledger." The key drawbacks are: on-site entry has the characteristics of uncertain endpoint order, concurrent writing, and cross-table updates, which can easily lead to a semi-updated or contradictory state of the link table, port occupation table, and SN binding table; when deviations are detected, the system lacks calculable branch decision rules to determine which endpoints should be kept and which should be rewritten, often relying on manual judgment and manual database modification, which is inefficient and introduces the risk of secondary errors.

[0030] In view of this, this application provides a feasible consistency control chain solution for engineering projects. This technical solution uses the set of planning sequence numbers and planning link data formed during the planning phase as authoritative data sources, and only submits input requests during construction / maintenance at the business site. When it is detected that the target sequence number (service SN) deviates from the set of planning sequence numbers, and the near-end service port is inconsistent with the near-end planning port corresponding to the target sequence number in the planning link data, the service link data can be updated based on the input status of the far-end service port, thereby reducing manual operations and improving the management efficiency of structured cabling.

[0031] The embodiments of this application are described below with reference to the accompanying drawings. The terminology used in the implementation section of this application is only for explaining specific embodiments and is not intended to limit the application. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0032] Figure 1 This is a flowchart illustrating the data update method provided in an embodiment of this application, as shown below. Figure 1 As shown, the method may include the following steps: Step S110: Receive the input request for the target wiring component.

[0033] Cabling components can be cables, patch panels, or other components with serial numbers that can be used to connect to network devices. For ease of understanding, the following description uses cables as an example of cabling components.

[0034] The target cable (i.e., the target cabling assembly) can be any cable selected by the current construction personnel (or user) during the business phase (construction / maintenance) for tasks such as testing, connection, and maintenance. The electronic device can be a network terminal; for example, a mobile terminal can receive input requests, which may include the target cable's serial number (i.e., the target serial number) and the near-end service port.

[0035] For example, a target serial number can be set on the target cable. Construction personnel can use a scanning device (such as a barcode scanner) to obtain the target serial number of the target cable by scanning the code. They can also obtain the near-end service port of the network device connected to the target cable by scanning the code and send an input request to the mobile terminal.

[0036] In some embodiments, the data entry request may also include a timestamp and the identity information of the construction personnel to facilitate subsequent review and other processes.

[0037] Step S120: If the target sequence number belongs to the planned sequence number set, and the near-end service port is inconsistent with the near-end planned port corresponding to the target sequence number in the planned link data, perform port conflict detection.

[0038] During the planning phase, managers, planners, and collaborators can configure starting and ending devices, as well as cable trays, during scenario creation. Then, the ports of the starting and ending devices can be connected via cables to form a link. The connecting cable refers to a physical cable, and the SN corresponding to the cable is denoted as the planning SN. The port connected by the connecting cable is called the planning port. The planning sequence number set can include all planning SNs in the planning scenario. The planning link data can include the near-end planning port and the far-end planning port corresponding to each planning SN in the planning sequence number set. Planners can export the planning sequence number set to Excel as label data and a printing source. Pre-assigning serial numbers during the planning phase and having the manufacturer directly embed them onto the cables ensures that the serial numbers match the data from the planning phase when the cables leave the factory. This avoids errors such as incorrect labeling or misplacement by on-site construction workers in busy environments, effectively improving the uniqueness and accuracy of the target serial numbers. Furthermore, this allows construction workers to immediately identify the planned location of the target cabling component after scanning the target serial number, eliminating the need for complex configuration or record entry, reducing subsequent rectification and rework, and thus shortening the construction cycle.

[0039] In some embodiments, during the planning phase, a port set and port range including all ports in each computer room in the scenario can also be established to facilitate determining the port's location coordinates (rack → device → unit → surface → row and column) based on the port.

[0040] After obtaining the target serial number, the mobile terminal can match the target serial number with a planned serial number set to determine whether there is a serial number in the planned serial number set that is the same as the target serial number. The planned serial number set can be stored in the mobile terminal for local matching; however, in other embodiments, the planned serial number set can also be stored in other network devices.

[0041] If a matching serial number exists, the target cable is confirmed to meet the planning requirements. If no matching serial number exists, the target cable does not meet the planning requirements. By determining whether the target cable's serial number belongs to the planned serial number set, the use of incorrect cables (such as those with incorrect specifications) or unplanned cables can be prevented.

[0042] In some scenarios, considering that the customer's existing cables need to be added for later maintenance, in some embodiments, if the target sequence number does not belong to the planned sequence number set, the target sequence number can be added to the planned sequence number set and the business link data can be updated to facilitate subsequent maintenance.

[0043] After determining that the target sequence number belongs to the set of planned sequence numbers, it can be judged whether the near-end service port is consistent with the near-end planned port corresponding to the target sequence number in the planned link data. If it is determined that the near-end service port is consistent with the near-end planned port, it can be determined that the near-end service port connected to the target cable is the near-end planned port planned in the planning stage, and the near-end service port satisfies the planned port position constraint.

[0044] In this embodiment, the service link data may include SN binding data, port occupancy data, and link port pair data. The SN binding data indicates the binding relationship between the service SN and the port, the port occupancy data indicates the port occupancy status, and the link port pair data indicates the port information of the link. In some embodiments, if the near-end service port is inconsistent with the near-end planned port corresponding to the target sequence number in the planned link data, the update of the link service data may include the following three cases: Scenario 1: The remote service port corresponding to the target sequence number is not recorded in the service link data. Specifically, taking the near-end device as 01 and the remote-end device as 02 as an example, if the near-end planned port is A and the remote-end planned port is C, then the planned port pair is A-C. However, the near-end service port corresponding to the current target sequence number is B. In this case, the processing strategy can be: keep the remote-end planned port C unchanged, write the near-end service port B into the service link data, thereby updating the link port pair (including the near-end service port and the remote service port) in the service link data to B-C, and updating the SN binding data and port occupancy data.

[0045] Scenario 2: The remote service port corresponding to the target sequence number has already been entered in the service link data, and the remote service port is the same as the remote planned port. In this case, the near-end service port can be written into the service link data. Specifically, taking the near-end device 01 and the remote device 02 as an example, if the near-end planned port is A and the remote planned port is C, then the planned port pair is A-C. The near-end service port corresponding to the current target sequence number is B, and the remote service port is C. At this time, the processing strategy can be: write the near-end service port B corresponding to the current target sequence number into the service link data, thereby updating the link port pair in the service link data to B-C, and updating the SN binding data and port occupancy data.

[0046] Scenario 3: The remote service port corresponding to the target serial number has been entered in the service link data, but the remote service port is inconsistent with the planned remote port, i.e., a two-way deviation has occurred. In this case, both the near-end service port and the remote service port can be written into the service link data. Specifically, taking the near-end device 01 and the remote device 02 as an example, if the near-end planned port is A and the remote planned port is C, the planned port pair is A-C. However, the near-end service port corresponding to the current target serial number is B, and the actual remote connected service port is D (inconsistent with the planned remote port C), then the processing strategy can be: write the near-end service port B and the remote service port D corresponding to the current target cable into the service link data, thereby forming a link port pair B-D in the service link data, and update the SN binding data and port occupancy data.

[0047] As can be seen from the above, when it is determined that the target sequence number belongs to the planned sequence number set, and the near-end service port is inconsistent with the near-end planned port corresponding to the target sequence number in the planned link data, the near-end service port in the link port pair in the service link data can be updated to the near-end service port corresponding to the current target cable, regardless of the status of the opposite end of the target cabling component.

[0048] In some scenarios, if there are multiple remote service ports corresponding to the target sequence number entered in the business link data before the update, one target remote service port can be selected from the multiple remote service ports corresponding to the target sequence number as the remote service port in the link port pair corresponding to the target sequence number.

[0049] In some embodiments, a target remote service port can be randomly selected as the remote service port in the link port pair corresponding to the target sequence number. After determining the remote service port in the link port pair corresponding to the target sequence number, other remote service ports recorded in the service link data can be deleted to achieve the uniqueness of the remote service port, or a remote service port corresponding to the target sequence number can be added to the data link data to improve traceability.

[0050] In other embodiments, different priorities can be set for remote service ports with different input sources, and the target remote service port can be selected from multiple remote service ports according to the priority. For example, the input source can include multiple of the following: input via data synchronization, input via QR code scanning, input via import, and manual input, wherein the priority of input via data synchronization, input via QR code scanning, input via import, and manual input can decrease in that order. For remote service ports with the same input source, the earlier the input time, the higher the priority.

[0051] In some embodiments, considering that the data entry source and entry time may be the same, if the business link data has not been updated, the remote planning port in the planning link data can be used as the remote business port. If the business link data has been updated, the remote business port in the current business link data can be used as the remote business port in the link port pair corresponding to the target sequence number.

[0052] The above implementation method can replace the traditional method of relying on manual judgment and manual database modification, significantly reducing the operation and maintenance threshold and the risk of secondary errors, and greatly improving the efficiency of cabling management.

[0053] In one alternative implementation, for any of cases one, two, and three, refer to [reference needed]. Figure 2 It can send prompts to the user. These prompts can be used to ask the user whether to continue entering data. In some embodiments, the prompts may also include a processing strategy (or a preview result) for each situation.

[0054] Upon receiving a user's request to continue entering data, the corresponding processing strategy is executed, and port conflict detection is performed. For example, port conflict detection can determine whether a port conflict exists by checking whether a port in the business link data is occupied by another business link.

[0055] In some embodiments, it can be determined whether the near-end service port is occupied. If it is detected that the near-end service port is occupied, a port conflict can be determined. Based on the port conflict, a consistent transaction can be initiated to ensure that the consistency of SN binding data, port occupancy data, and link port pair data in the service link data is not compromised, and a security check (lock / version verification and unique constraint) is performed. After the security check passes, the SN binding data, port occupancy data, and link port pair data can be updated according to the pre-rehearsal results. If any of the three types of data fails during the update process, an atomic rollback is triggered, and the service link data is restored to the state before the user clicked "Continue" to prevent data from being entered into the service link data. This can solve the difficulty of error correction decision-making and the risk of accidental database modification caused by the "uncertainty" of the on-site entry port.

[0056] If it is detected that the near-end service port is not occupied, it is determined that no port conflict has occurred. Under the premise that no port conflict has occurred, the link port pair data and port occupancy status in the service link data can be updated.

[0057] It is understandable that the above method determines whether a port conflict exists by checking whether the near-end service port is occupied. In other embodiments, other methods can be used to determine whether a port conflict exists, such as determining whether a port conflict exists based on the SN binding relationship.

[0058] This application's embodiments introduce a database consistency transaction mechanism, encapsulating SN binding, link port pair updates, and port occupancy status updates into atomic operations. Combined with lock / version verification and unique constraints, this resolves the "half-update" or data contradiction issues caused by concurrent writes or cross-table updates in existing technologies, ensuring strict synchronization of data states across multiple tables. Furthermore, through pre-drill result confirmation and automatic conflict detection mechanisms, it also achieves a shift from "manual database modification" to "automatic data updates." While ensuring strong data consistency, it significantly shortens the entry time for construction and changes, substantially improving the management efficiency of structured cabling during the business phase.

[0059] In some embodiments, when a port conflict is determined to occur, a failure message can be sent to the user, and the reason for the port conflict can be displayed. In other embodiments, when a port conflict exists, the reason for the conflict can be recorded, such as the port being occupied or the version being inconsistent, to facilitate the association of work orders, task acceptance, feedback and rollback, and data verification and archiving.

[0060] If a user cancels an input request, the input is cancelled, and the business process data is not updated.

[0061] Step S130: Update the business link data if there is no port conflict.

[0062] If no port conflict is determined, the service link data can be updated according to the above-mentioned pre-simulation results so that the updated service link data includes the near-end service port corresponding to the target sequence number.

[0063] Optionally, after the business link data is updated, a transaction log (or evidence log) corresponding to the entry request can also be generated. The transaction log may include at least one of the following information: operator, scenario, event type, timestamp, port information corresponding to the target sequence number in the business link data before the update, port information corresponding to the target sequence number in the updated business link data, and port conflict information.

[0064] In some embodiments, the above method can also be associated with work orders. Upon receiving a work order, construction personnel can begin performing scanning and other construction operations. Work orders can be created by planners using Gantt chart time logic to establish task time bars, containing multiple fields such as work order ID, work order status, creator / recipient, expected start / expected completion, actual completion, and priority associated objects (scene, device, link). By constructing work orders, an association with construction tasks can be established. Construction personnel can view construction tasks based on work orders. Construction tasks can include multiple fields such as task ID, planning SN, task type, port pair before change, port pair after change, remarks, and associated work order ID. Fields can be set according to actual needs. For example, corresponding fields can be set in each step of the data update method to facilitate construction personnel in executing corresponding tasks. This allows planners to intuitively and efficiently conduct acceptance and review based on work order status, rejecting work orders requiring rectification (e.g., construction tasks not meeting requirements), withdrawing tasks that need to be withdrawn, and accepting and archiving work orders that conform to the construction plan.

[0065] The technical solution provided in this application embodiment can receive an input request for a target cabling component. The input request includes the target sequence number and near-end service port corresponding to the target cabling component. Then, if the target sequence number belongs to the planned sequence number set and the near-end service port is inconsistent with the near-end planned port corresponding to the target sequence number in the planned link data, port conflict detection can be performed. The planned link data includes the near-end planned ports corresponding to each planned sequence number in the planned sequence number set. Then, if there is no port conflict, the service link data can be updated. The updated service link data includes the near-end service port corresponding to the target sequence number. Through the above implementation, the problem of link data distortion caused by cabling components failing to connect to planned ports between the planning and service stages can be solved. Furthermore, the risk of accidental database modifications due to manual data changes can be reduced, improving the work efficiency of staff and thus enhancing the efficiency of structured cabling management.

[0066] Those skilled in the art will understand that the above embodiments are exemplary and not intended to limit this application. Where possible, the execution order of one or more of the above steps can be adjusted, or they can be selectively combined to obtain one or more other embodiments. Those skilled in the art can arbitrarily select and combine the above steps as needed, and all those that do not depart from the essence of this application fall within the protection scope of this application.

[0067] Based on the same inventive concept, as an implementation of the above method, this application provides a data update device. This device embodiment corresponds to the aforementioned method embodiment. For ease of reading, this device embodiment will not repeat the details of the aforementioned method embodiment one by one, but it should be clear that the device in this embodiment can correspondingly implement all the contents of the aforementioned method embodiment.

[0068] Figure 3 This is a schematic diagram of the structure of the data update device provided in the embodiments of this application, such as... Figure 3 As shown, the apparatus provided in this embodiment includes: The receiving module 110 is used to receive an entry request for a target cabling component, the entry request including the target serial number and near-end service port corresponding to the target cabling component; The detection module 120 is used to perform port conflict detection when the target sequence number belongs to the planned sequence number set and the near-end service port is inconsistent with the near-end planned port corresponding to the target sequence number in the planned link data; the planned link data includes the near-end planned ports corresponding to each planned sequence number in the planned sequence number set; The update module 130 is used to update the service link data when there is no port conflict; the updated service link data includes the near-end service port corresponding to the target sequence number.

[0069] In one possible implementation of the second aspect, the planned link data further includes remote planned ports corresponding to each of the planned sequence numbers, and the updated service link data includes link port pairs corresponding to the target sequence numbers, the link port pairs including near-end service ports and remote service ports; The update module 130 is also used for: If there are multiple remote service ports corresponding to the target sequence number recorded in the service link data before the update, select one target remote service port from the multiple remote service ports corresponding to the target sequence number as the remote service port in the link port pair corresponding to the target sequence number.

[0070] In one possible implementation of the second aspect, the target remote service port is the remote service port with the highest priority among the plurality of remote service ports; Remote service ports with different data entry sources have different priorities; for remote service ports with the same data entry source, the earlier the data entry time, the higher the priority; the data entry source includes multiple of the following: data entry through data synchronization, data entry through QR code scanning, data entry through import, and manual entry.

[0071] In one possible implementation of the second aspect, the apparatus further includes a generation module 140, the generation module 140 further including: Generate a transaction log corresponding to the input request. The transaction log includes at least one of the following: timestamp, port information corresponding to the target sequence number in the business link data before the update, port information corresponding to the target sequence number in the business link data after the update, and port conflict information.

[0072] In one possible implementation of the second aspect, if a port conflict exists, the entry is rejected and the reason for the conflict is recorded.

[0073] In one possible implementation of the second aspect, the apparatus further includes a processing module 150, the processing module 150 being configured to: If the target sequence number does not belong to the planned sequence number set, the target sequence number is added to the planned sequence number set, and the business link data is updated.

[0074] In one possible implementation of the second aspect, the device further includes a prompting module 160, which is used to: issue a prompting message before performing port conflict detection; the prompting message is used to prompt the user whether to continue inputting data. The detection module 120 is further configured to: perform port conflict detection upon receiving a user's request to continue inputting data; and cancel inputting data upon receiving a user's request to cancel inputting data.

[0075] The data update device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

[0076] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0077] Based on the same inventive concept, embodiments of this application also provide an electronic device. Figure 4 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application, such as... Figure 4 As shown, the electronic device provided in this embodiment includes: a memory 210 and a processor 220. The memory 210 is used to store computer programs; the processor 220 is used to execute the method described in the above method embodiment when the computer program is invoked.

[0078] The electronic device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so they will not be described again here.

[0079] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the methods described in the above-described method embodiments.

[0080] This application also provides a computer program product that, when run on an electronic device, causes the electronic device to implement the method described in the above-described method embodiments.

[0081] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, or magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

[0082] Those skilled in the art will understand that implementing all or part of the processes in the above embodiments can be accomplished by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium can include various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

[0083] The naming or numbering of steps in this application does not mean that the steps in the method flow must be executed in the time / logical order indicated by the naming or numbering. The execution order of the named or numbered process steps can be changed according to the technical purpose to be achieved, as long as the same or similar technical effect can be achieved.

[0084] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0085] In the embodiments provided in this application, it should be understood that the disclosed apparatus / devices and methods can be implemented in other ways. For example, the apparatus / device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0086] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0087] In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0088] Furthermore, in the description of this application, unless otherwise stated, "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0089] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0090] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein.

[0091] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized.

[0092] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A data update method, characterized in that, Applied to electronic devices, including: Receive a target cabling component entry request, the entry request including the target serial number and near-end service port corresponding to the target cabling component; If the target sequence number belongs to the planned sequence number set, and the near-end service port is inconsistent with the near-end planned port corresponding to the target sequence number in the planned link data, port conflict detection is performed; the planned link data includes the near-end planned ports corresponding to each planned sequence number in the planned sequence number set. If there is no port conflict, update the service link data; the updated service link data includes the near-end service port corresponding to the target sequence number.

2. The method according to claim 1, characterized in that, The planned link data also includes the remote planned port corresponding to each planned sequence number, and the updated business link data includes the link port pair corresponding to the target sequence number, the link port pair including the near-end business port and the remote business port; The updated business link data includes: If there are multiple remote service ports corresponding to the target sequence number recorded in the service link data before the update, select one target remote service port from the multiple remote service ports corresponding to the target sequence number as the remote service port in the link port pair corresponding to the target sequence number.

3. The method according to claim 2, characterized in that, The target remote service port is the remote service port with the highest priority among the plurality of remote service ports; Remote service ports with different data entry sources have different priorities; for remote service ports with the same data entry source, the earlier the data entry time, the higher the priority; the data entry source includes multiple of the following: data entry through data synchronization, data entry through QR code scanning, data entry through import, and manual entry.

4. The method according to claim 1, characterized in that, The method further includes: Generate a transaction log corresponding to the input request. The transaction log includes at least one of the following: timestamp, port information corresponding to the target sequence number in the business link data before the update, port information corresponding to the target sequence number in the business link data after the update, and port conflict information.

5. The method according to claim 1, characterized in that, If a port conflict exists, refuse to enter the data and record the reason for the conflict.

6. The method according to claim 1, characterized in that, The method further includes: If the target sequence number of the target cabling component does not belong to the planned sequence number set, the target sequence number is added to the planned sequence number set.

7. The method according to any one of claims 1-6, characterized in that, Before performing port conflict detection, a prompt message is issued; the prompt message is used to ask the user whether to continue entering data. Upon receiving a request from the user to continue entering data, the port conflict detection is performed. If the user cancels the data entry request, the data entry will be cancelled.

8. A data update device, characterized in that, include: A receiving module is used to receive an entry request for a target cabling component, the entry request including the target serial number and near-end service port corresponding to the target cabling component; The detection module is used to perform port conflict detection when the target sequence number belongs to the planned sequence number set and the near-end service port is inconsistent with the near-end planned port corresponding to the target sequence number in the planned link data; the planned link data includes the near-end planned ports corresponding to each planned sequence number in the planned sequence number set; The update module is used to update business link data when there are no port conflicts. The updated service link data includes the near-end service port corresponding to the target sequence number.

9. An electronic device, characterized in that, include: A memory and a processor, the memory being used to store a computer program; the processor being used to execute the method as described in any one of claims 1-7 when the computer program is invoked.

10. A computer program product, characterized in that, When the computer program product is run on an electronic device, it causes the electronic device to perform the method as described in any one of claims 1-7.

Images