CN113037844A - Identification updating method and device - Google Patents

Identification updating method and device Download PDF

Info

Publication number
CN113037844A
CN113037844A CN202110270823.6A CN202110270823A CN113037844A CN 113037844 A CN113037844 A CN 113037844A CN 202110270823 A CN202110270823 A CN 202110270823A CN 113037844 A CN113037844 A CN 113037844A
Authority
CN
China
Prior art keywords
identifier
message
updating
updated
request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202110270823.6A
Other languages
Chinese (zh)
Other versions
CN113037844B (en
Inventor
张岩
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Jingdong Zhenshi Information Technology Co Ltd
Original Assignee
Beijing Jingdong Zhenshi Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Jingdong Zhenshi Information Technology Co Ltd filed Critical Beijing Jingdong Zhenshi Information Technology Co Ltd
Priority to CN202110270823.6A priority Critical patent/CN113037844B/en
Publication of CN113037844A publication Critical patent/CN113037844A/en
Application granted granted Critical
Publication of CN113037844B publication Critical patent/CN113037844B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/565Conversion or adaptation of application format or content
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23Updating
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/08Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/087Inventory or stock management, e.g. order filling, procurement or balancing against orders
    • G06Q10/0875Itemisation or classification of parts, supplies or services, e.g. bill of materials

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Economics (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Development Economics (AREA)
  • Operations Research (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • General Engineering & Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The application provides an identification updating method and device, wherein the method comprises the following steps: when a first message is sent to other systems, if a first identifier in the first message exists in a stored association relation, updating the first identifier in the first message by using an updated identifier associated with the first identifier, and sending the updated first message; when a second message sent by other systems is received, if a second identifier in the second message exists in the stored association relationship, updating the second identifier in the second message by using the identifier before updating associated with the second identifier, and processing the updated second message. The method can improve the updating efficiency of the identification on the premise of avoiding updating errors.

Description

Identification updating method and device
Technical Field
The present invention relates to the field of internet technologies, and in particular, to an identifier updating method and apparatus.
Background
In many application scenarios, for example, WMS system warehouse and the like implement isolation between data through corresponding identifiers of related organizations, warehouses, distribution centers and the like, in these application scenarios, a large amount of data tables and basic data tables are maintained by using the identifiers.
In the process of implementing the present application, the inventor finds that if the identifier in the identifier changes, a data table and a basic data table are needed to update, and such an identifier updating method is inefficient and prone to errors.
Disclosure of Invention
In view of this, the present application provides an identifier updating method and apparatus, which can improve identifier updating efficiency on the premise of avoiding updating errors.
In order to solve the technical problem, the technical scheme of the application is realized as follows:
in one embodiment, there is provided an identification update method, the method comprising:
when a first message is sent to other systems, if a first identifier in the first message exists in a stored association relation, updating the first identifier in the first message by using an updated identifier associated with the first identifier, and sending the updated first message;
when a second message sent by other systems is received, if a second identifier in the second message exists in the stored association relationship, updating the second identifier in the second message by using an identifier before updating associated with the second identifier, and processing the updated second message;
and the association relationship is the corresponding relationship between the identifier before updating and the identifier after updating.
In another embodiment, there is provided an identification update apparatus, the apparatus including: the device comprises a storage unit, a sending unit, a processing unit and a receiving unit;
the storage unit is used for storing the association relationship; wherein the correlation relationship is a corresponding relationship between the identifier before updating and the identifier after updating;
the processing unit is configured to, when the sending unit sends a first packet to another system, update a first identifier in the first packet by using an updated identifier associated with the first identifier if it is determined that the first identifier in the first packet exists in the association relationship stored in the storage unit; when the receiving unit receives a second message sent by other systems, if the second identifier in the second message is determined to exist in the association relationship stored in the storage unit, updating the second identifier in the second message by using the identifier before updating associated with the second identifier, and processing the updated second message;
the sending unit is used for sending the first message updated by the processing unit;
and the receiving unit is used for receiving second messages sent by other systems.
In another embodiment, an electronic device is provided, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the identification update method when executing the program.
In another embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when being executed by a processor, carries out the steps of the identification update method.
According to the technical scheme, the corresponding relation between the identifier before updating and the identifier after updating is maintained through the association relation, and when the message interaction is carried out with other systems, if the message carries the identifier in the association relation, the message is correspondingly processed after the identifier is updated. According to the scheme, when the identification is updated, the identification in the message is updated to replace the updating of the identification in the data table and the basic data table, so that the identification updating efficiency is improved on the premise of avoiding updating errors.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.
Fig. 1 is a schematic diagram illustrating an identifier update process according to a first embodiment of the present application;
fig. 2 is a schematic diagram illustrating an update process of the identifier according to a second embodiment of the present application;
fig. 3 is a schematic diagram illustrating an update process of the identifier according to a third embodiment of the present application;
FIG. 4 is a schematic diagram of a conventional warehouse management system login interface;
fig. 5 is a schematic diagram of a warehouse management system login interface according to an embodiment of the present application;
FIG. 6 is a schematic diagram of an apparatus for implementing the above technique in an embodiment of the present application;
fig. 7 is a schematic physical structure diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprising" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements explicitly listed, but may include other steps or elements not explicitly listed or inherent to such process, method, article, or apparatus.
The technical solution of the present invention will be described in detail with specific examples. Several of the following embodiments may be combined with each other and some details of the same or similar concepts or processes may not be repeated in some embodiments.
In a scene of data isolation by using an identifier, if the identifier needs to be changed, corresponding fields in a large number of tables related to the updated identifier need to be updated, efficiency is low, and errors easily occur.
Example one
Some identifiers need to be updated in the embodiment of the application, but the technical scheme provided in the embodiment of the application does not need to update the identifiers for the data table and the data table corresponding to each identifier, but maintains an association relationship, where the association relationship is a correspondence relationship between an identifier before update and an identifier after update. The specific implementation of the maintenance of the association is as follows:
when an identifier updating request is received, determining whether an identifier before updating carried in the request is stored in the association relationship, if so, replacing the identifier which is the same as the identifier before updating carried in the request in the association relationship with the updated identifier carried in the request by using the updated identifier carried in the request; otherwise, storing the incidence relation between the identifier before updating and the identifier after updating carried in the request.
Referring to fig. 1, fig. 1 is a schematic diagram illustrating an identifier updating process according to a first embodiment of the present application. The method comprises the following specific steps:
step 101, when a first message is sent to other systems, if a first identifier in the first message exists in a stored association relationship, updating the first identifier in the first message by using an updated identifier associated with the first identifier, and sending the updated first message.
The system for interacting data and instructions with the system for implementing the identification update (identification update system) by using the identification is called other system in the embodiment of the application.
When the identifier updating system sends a first message to other systems, whether a first identifier in the message exists needs to be searched in the association relationship, and if so, the first identifier in the first message is updated by using the updated identifier in the association relationship; otherwise, the first message is maintained unchanged.
If the first identifier exists in the association relationship, the first identifier is used in the identifier updating system, and the updated identifier corresponding to the first identifier in the association relationship is the identifier used in other systems;
if the first identifier does not exist in the association relationship, the first identifier is used for carrying out correlation processing in the identifier updating system and other systems, and the first identifier is not updated.
And 102, when a second message sent by other systems is received, if a second identifier in the second message exists in the stored association relationship, updating the second identifier in the second message by using the identifier before updating associated with the second identifier, and processing the updated second message.
When the identifier updating system receives a second message sent by other systems, whether a second identifier in the second message exists needs to be searched in the association relationship, and if so, the identifier before updating in the association relationship is used for updating the second identifier in the second message; otherwise, the second message is maintained unchanged.
If the incidence relation has a second identifier, the second identifier is used in other systems, and the identifier before updating corresponding to the second identifier in the incidence relation is the identifier used in the identifier updating system;
if the second identifier does not exist in the association relationship, the second identifier is used for carrying out correlation processing in the identifier updating system and other systems, and the second identifier is not updated.
When the identification updating system receives and transmits the message of other systems, if the incidence relation corresponding to the relevant identification exists, the identification updating is carried out only according to the identification corresponding relation in the incidence relation.
The step 101 and the step 102 are realized without distinguishing the sequence, the step 101 is executed when the message needs to be sent, and the step 102 is executed when the message is received.
In the embodiment of the application, the corresponding relation between the identifier before updating and the identifier after updating is maintained through the incidence relation, and when the message interaction is carried out with other systems, if the message carries the identifier in the incidence relation, the message is correspondingly processed after the identifier is updated. According to the scheme, when the identification is updated, the identification in the message is updated to replace the updating of the identification in the data table and the basic data table, so that the identification updating efficiency is improved on the premise of avoiding updating errors.
Example two
The identification updating method provided by the embodiment of the application can be applied to a warehouse management system.
Configuring relevant institution parameters through a centralized management platform in a warehouse management system, and recording basic information of a warehouse opening task when the warehouse is opened, wherein the basic information at least comprises the following steps: the mechanism identification is issued to each cluster, and each cluster receives and transmits the message and carries out related processing; multiple warehouses in each cluster.
Some mechanism identifications in the embodiment of the present application need to be updated, but the technical scheme provided in the embodiment of the present application does not need to update the mechanism identifications for the data table and the data table corresponding to each mechanism identification, but maintains an association relationship, where the association relationship is a correspondence relationship between a mechanism identification before updating and a mechanism identification after updating. The specific implementation of the maintenance of the association is as follows:
when an organization identifier updating request is received, determining whether an organization identifier before updating carried in the request is stored in the association relationship, if so, replacing the organization identifier which is the same as the organization identifier before updating carried in the request in the association relationship with the updated organization identifier carried in the request by using the updated organization identifier carried in the request; otherwise, storing the incidence relation between the mechanism identification before updating and the mechanism identification after updating carried in the request.
In specific implementation, in the embodiment of the present application, when a request carries multiple sets of identifiers before update and identifiers after update, batch processing may be performed, which may specifically be implemented in the following manner:
and when the request carries a plurality of groups of identifiers before updating and identifiers after updating, establishing the association relationship between each group of identifiers before updating and each group of identifiers after updating as a task to be executed until all tasks are executed successfully.
In the embodiment of the present application, in a specific implementation, the association relationship may be maintained and pushed to each cluster by the centralized management platform according to a request, or the association relationship may be maintained by each cluster.
Referring to fig. 2, fig. 2 is a schematic diagram illustrating an identifier updating process in a second embodiment of the present application. The method comprises the following specific steps:
step 201, when a first message is sent to other systems, if a first mechanism identifier in the first message exists in a stored association relationship, updating the first mechanism identifier in the first message by using an updated mechanism identifier associated with the first mechanism identifier, and sending the updated first message.
The system for interacting data and instructions with the system (warehouse management system) implementing the update of the organization identifier is called other system in the embodiment of the application.
When the warehousing management system sends a first message to other systems, whether a first mechanism identifier in the message exists needs to be searched in the association relation, and if so, the first mechanism identifier in the first message is updated by using the updated mechanism identifier in the association relation; otherwise, the first message is maintained unchanged.
If the incidence relation has the first mechanism identification, the first mechanism identification is used in the warehousing management system, and the updated mechanism identification corresponding to the first mechanism identification in the incidence relation is used in other systems;
if the first mechanism identification does not exist in the association relationship, the first mechanism identification is used in the warehousing management system and other systems for relevant processing, and the first mechanism identification is not updated.
Step 202, when a second message sent by another system is received, if a second mechanism identifier in the second message exists in the stored association relationship, updating the second mechanism identifier in the second message by using the mechanism identifier before updating associated with the second mechanism identifier, and processing the updated second message.
When the warehousing management system receives a second message sent by other systems, whether a second mechanism identifier in the second message exists needs to be searched in the association relationship, and if so, the mechanism identifier before updating in the association relationship is used for updating the second mechanism identifier in the second message; otherwise, the second message is maintained unchanged.
If the incidence relation has a second mechanism identification, the second mechanism identification is used in other systems, and the mechanism identification before updating corresponding to the second mechanism identification in the incidence relation is the mechanism identification used in the warehousing management system;
if the second mechanism identifier does not exist in the association relationship, the second mechanism identifier is used in the warehousing management system and other systems for relevant processing, and the second mechanism identifier is not updated.
When the mechanism warehousing management system receives and transmits the other system messages, if the incidence relation corresponding to the relevant mechanism identification exists, the mechanism identification is updated only according to the corresponding relation of the mechanism identification in the incidence relation.
The step 201 and the step 202 are realized without distinguishing the sequence, the step 201 is executed when the message needs to be sent, and the step 202 is executed when the message is received.
In the embodiment of the application, the corresponding relation between the mechanism identifier before updating and the mechanism identifier after updating is maintained through the incidence relation, and when the message is interacted with other systems, if the message carries the mechanism identifier in the incidence relation, the message is correspondingly processed after the mechanism identifier is updated. According to the scheme, when the mechanism identification is updated, the mechanism identification in the message is updated to replace the updating of the mechanism identification in the data table and the basic data table, so that the updating efficiency of the mechanism identification is improved on the premise of avoiding updating errors.
EXAMPLE III
The identification updating method provided by the embodiment of the application can be applied to a warehouse management system.
Configuring relevant institution parameters through a centralized management platform in a warehouse management system, and recording basic information of a warehouse opening task when the warehouse is opened, wherein the basic information at least comprises the following steps: the mechanism mark and the system mark are issued to each cluster, and each cluster is used for receiving and sending related processing of messages; multiple warehouses in each cluster. Wherein the organization identity is part of the system identity.
Some mechanism identifications need to be updated in the embodiment of the application, but the technical scheme provided in the embodiment of the application does not need to update the mechanism identifications for the data table and the data table corresponding to each mechanism identification, but maintains an association relationship, where the association relationship is a correspondence between the mechanism identifications before updating and the mechanism identifications after updating, and the system identifications before updating corresponding to the mechanism identifications before updating and the system identifications after updating corresponding to the mechanism identifications after updating. The specific implementation of the maintenance of the association is as follows:
when an organization identifier updating request is received, determining whether an organization identifier before updating carried in the request is stored in the association relationship, if so, replacing the organization identifier which is the same as the organization identifier before updating carried in the request in the association relationship with the updated organization identifier carried in the request by using the updated organization identifier carried in the request; otherwise, storing the incidence relation between the mechanism identification before updating and the mechanism identification after updating carried in the request.
The method further comprises:
and saving the system identifier before updating aiming at the mechanism identifier before updating, and saving the system identifier after updating aiming at the mechanism identifier after updating.
Specific content corresponding to the association relationship is given as a specific example below. Referring to table 1, table 1 shows the content corresponding to the association relationship in the embodiment of the present application. The content corresponding to the association relationship may be stored in a table form, which is referred to as a mapping table.
Figure BDA0002974317260000081
Figure BDA0002974317260000091
TABLE 1
The field wh _ no in table 1 is the system identification used inside the warehouse management system: the format is (4-4-2) (organization identifier-distribution center identifier-warehouse number), wh _ out _ no is the system identifier used by other systems, org _ no is the organization identifier used inside the warehouse management system, and org _ out _ no is the organization identifier used by other systems outside the warehouse management system.
The above four kinds of identifiers are indispensable contents in the association relationship, and other parameter information may be stored or not stored according to actual needs.
In the embodiment of the present application, in a specific implementation, the association relationship may be maintained and pushed to each cluster by the centralized management platform according to a request, or the association relationship may be maintained by each cluster.
Referring to fig. 3, fig. 3 is a schematic diagram illustrating an update process of the identifier in the third embodiment of the present application. The method comprises the following specific steps:
step 301, when a first message is sent to another system, if a first mechanism identifier in the first message exists in a stored association relationship, updating the first mechanism identifier in the first message by using an updated mechanism identifier associated with the first mechanism identifier, and if the first message carries a first system identifier, updating the first system identifier in the first message by using an updated system identifier associated with the first system identifier; and sending the updated first message.
The system for interacting data and instructions with the system (warehouse management system) implementing the update of the organization identifier is called other system in the embodiment of the application.
When the warehousing management system sends a first message to other systems, whether a first mechanism identifier in the message exists needs to be searched in the association relation, and if so, the first mechanism identifier in the first message is updated by using the updated mechanism identifier in the association relation; otherwise, the first message is maintained unchanged.
If the incidence relation has the first mechanism identification, the first mechanism identification is used in the warehousing management system, and the updated mechanism identification corresponding to the first mechanism identification in the incidence relation is used in other systems;
if the first mechanism identification does not exist in the association relationship, the first mechanism identification is used in the warehousing management system and other systems for relevant processing, and the first mechanism identification is not updated.
When the warehousing management system determines that the first mechanism identifier exists in the association relationship, the warehousing management system also determines whether the first message carries the first system identifier, and if so, the first system identifier is updated by using the updated system identifier in the association relationship; otherwise, no additional processing is performed.
Step 302, when a second message sent by another system is received, if a second mechanism identifier in the second message exists in the stored association relationship, updating the second mechanism identifier in the second message by using a mechanism identifier before update associated with the second mechanism identifier, and if the second message also carries a second system identifier, updating the second system identifier in the second message by using a system identifier before update associated with the second system identifier; and processing the updated second message.
When the warehousing management system receives a second message sent by other systems, whether a second mechanism identifier in the second message exists needs to be searched in the association relationship, and if so, the mechanism identifier before updating in the association relationship is used for updating the second mechanism identifier in the second message; otherwise, the second message is maintained unchanged.
If the incidence relation has a second mechanism identification, the second mechanism identification is used in other systems, and the mechanism identification before updating corresponding to the second mechanism identification in the incidence relation is the mechanism identification used in the warehousing management system;
if the second mechanism identifier does not exist in the association relationship, the second mechanism identifier is used in the warehousing management system and other systems for relevant processing, and the second mechanism identifier is not updated.
When the mechanism warehousing management system receives and transmits the other system messages, if the incidence relation corresponding to the relevant mechanism identification exists, the mechanism identification is updated only according to the corresponding relation of the mechanism identification in the incidence relation.
When the warehousing management system determines that the second mechanism identifier exists in the association relationship, the warehousing management system also determines whether the second message carries the second system identifier, and if so, the system identifier before updating in the association relationship is used for updating the second system identifier; otherwise, no additional processing is performed.
The step 301 and the step 302 are realized without distinguishing the sequence, the step 301 is executed when the message needs to be sent, and the step 302 is executed when the message is received.
In the embodiment of the application, the mechanism identifier before updating and the corresponding system identifier are maintained through the association relationship, and the corresponding relationship between the updated mechanism identifier and the corresponding system identifier is maintained, so that when the message interaction is performed with other systems, if the mechanism identifier and the system identifier in the association relationship are carried in the message, the mechanism identifier is updated, and then the message is correspondingly processed. According to the scheme, when the mechanism identification is updated, the mechanism identification and the system identification in the message are updated to replace the updating of the mechanism identification and the system identification in the data table and the basic data table, so that the updating efficiency of the mechanism identification is improved on the premise of avoiding updating errors.
Example four
In the embodiment of the application, the authority can be changed, the mechanism information is removed, the area information is added, and the mechanism identifier can be updated to the area identifier.
Because the attribute of the area field belonging to the position category is not changed generally, if the change is irrelevant, only one basic data table is added, the change only changes the relation between the area table and the distribution center table, and the service table does not retain the information of the field.
Therefore, the embodiment of the present application is directed to providing a login method, and specifically, the login method includes:
for the login information, replacing the organization information with the region information;
outputting a landing page including the region information.
Referring to fig. 4, fig. 4 is a schematic diagram of a conventional warehouse management system login interface.
Referring to fig. 5, fig. 5 is a schematic view of a warehouse management system login interface according to an embodiment of the present application.
In fig. 4, the conventional registration interface uses organization information to perform registration, and the organization information is selected as an organization name to perform registration of the warehouse management system.
In fig. 5, the login interface provided in the embodiment of the present application uses area information for login, where the area information may be south china, north china, and the like.
The realization can provide a convenient login mode for a user operating the warehouse management system, and improve the user experience.
Based on the same inventive concept, the embodiment of the application also provides an identification updating device. Referring to fig. 6, fig. 6 is a schematic structural diagram of an apparatus applied to the above technology in the embodiment of the present application. The device comprises: a storage unit 601, a transmission unit 602, a processing unit 603, and a reception unit 604;
a storage unit 601, configured to store an association relationship; wherein the correlation relationship is a corresponding relationship between the identifier before updating and the identifier after updating;
a sending unit 602, configured to send the first packet updated by the processing unit 603;
a processing unit 603, configured to, when the sending unit 602 sends a first packet to another system, if it is determined that a first identifier in the first packet exists in an association relationship stored in the storage unit 601, update the first identifier in the first packet by using an updated identifier associated with the first identifier; when the receiving unit 604 receives a second message sent by another system, if it is determined that a second identifier in the second message exists in the association relationship stored in the storage unit 601, updating the second identifier in the second message by using an identifier before update associated with the second identifier, and processing the updated second message;
the receiving unit 604 is configured to receive a second message sent by another system.
Preferably, the first and second electrodes are formed of a metal,
a receiving unit 604, further configured to receive an identifier update request;
a storing unit 601, configured to determine, when the receiving unit 604 receives an identifier update request, whether an identifier before update carried in the request is stored in the association relationship, and if so, replace, by using the updated identifier carried in the request, an identifier in the association relationship that is the same as the identifier before update carried in the request; otherwise, storing the incidence relation between the identifier before updating and the identifier after updating carried in the request.
Preferably, the first and second electrodes are formed of a metal,
when the method is applied to the warehouse management system, the mark is an organization mark.
Preferably, the association relationship further includes: and the mechanism identification corresponds to the system identification.
Preferably, the first and second electrodes are formed of a metal,
a processing unit 603, further configured to update a first system identifier in the first message by using an updated system identifier associated with the first system identifier if the first message also carries the first system identifier; and if the second message also carries a second system identifier, updating the second system identifier in the second message by using the system identifier before updating, which is associated with the second system identifier.
Preferably, the apparatus further comprises: an authority unit and an output unit;
the authority unit is used for replacing mechanism information with area information aiming at login information;
and the output unit is used for outputting the login page comprising the area information replaced by the authority unit.
The units of the above embodiments may be integrated into one body, or may be separately deployed; may be combined into one unit or further divided into a plurality of sub-units.
In another embodiment, an electronic device is also provided, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the identification update method when executing the program.
In another embodiment, a computer readable storage medium is also provided having stored thereon computer instructions which, when executed by a processor, may implement the steps in the identification update method.
Fig. 7 is a schematic physical structure diagram of an electronic device according to an embodiment of the present invention. As shown in fig. 7, the electronic device may include: a Processor (Processor)710, a communication Interface 720, a Memory (Memory)730 and a communication bus 740, wherein the Processor 710, the communication Interface 720 and the Memory 730 communicate with each other via the communication bus 740. Processor 710 may call logic instructions in memory 730 to perform the following method:
when a first message is sent to other systems, if a first identifier in the first message exists in a stored association relation, updating the first identifier in the first message by using an updated identifier associated with the first identifier, and sending the updated first message;
when a second message sent by other systems is received, if a second identifier in the second message exists in the stored association relationship, updating the second identifier in the second message by using an identifier before updating associated with the second identifier, and processing the updated second message;
and the association relationship is the corresponding relationship between the identifier before updating and the identifier after updating.
In addition, the logic instructions in the memory 730 can be implemented in the form of software functional units and stored in a computer readable storage medium when the software functional units are sold or used as independent products. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.

Claims (10)

1. An identity updating method, the method comprising:
when a first message is sent to other systems, if a first identifier in the first message exists in a stored association relation, updating the first identifier in the first message by using an updated identifier associated with the first identifier, and sending the updated first message;
when a second message sent by other systems is received, if a second identifier in the second message exists in the stored association relationship, updating the second identifier in the second message by using an identifier before updating associated with the second identifier, and processing the updated second message;
and the association relationship is the corresponding relationship between the identifier before updating and the identifier after updating.
2. The method of claim 1, further comprising:
when an identifier updating request is received, determining whether an identifier before updating carried in the request is stored in the association relationship, if so, replacing the identifier which is the same as the identifier before updating carried in the request in the association relationship with the updated identifier carried in the request by using the updated identifier carried in the request; otherwise, storing the incidence relation between the identifier before updating and the identifier after updating carried in the request.
3. The method of claim 1,
when the method is applied to the warehouse management system, the mark is an organization mark.
4. The method of claim 3, wherein the association further comprises:
the system identification corresponds to the mechanism identification; wherein the organization identifier is part of the system identifier.
5. The method of claim 4,
when sending the first message to other systems and before sending the updated first message, the method further includes:
if the first message also carries a first system identifier, updating the first system identifier in the first message by using the updated system identifier associated with the first system identifier;
when receiving a second message sent by another system and before processing the updated second message, the method further includes:
and if the second message also carries a second system identifier, updating the second system identifier in the second message by using the system identifier before updating, which is associated with the second system identifier.
6. The method according to any one of claims 3-5, wherein the method further comprises:
for the login information, replacing the organization information with the region information;
outputting a landing page including the region information.
7. An identity updating apparatus, the apparatus comprising: the device comprises a storage unit, a sending unit, a processing unit and a receiving unit;
the storage unit is used for storing the association relationship; wherein the correlation relationship is a corresponding relationship between the identifier before updating and the identifier after updating;
the processing unit is configured to, when the sending unit sends a first packet to another system, update a first identifier in the first packet by using an updated identifier associated with the first identifier if it is determined that the first identifier in the first packet exists in the association relationship stored in the storage unit; when the receiving unit receives a second message sent by other systems, if the second identifier in the second message is determined to exist in the association relationship stored in the storage unit, updating the second identifier in the second message by using the identifier before updating associated with the second identifier, and processing the updated second message;
the sending unit is used for sending the first message updated by the processing unit;
and the receiving unit is used for receiving second messages sent by other systems.
8. The apparatus of claim 7,
the receiving unit is further configured to receive an identifier update request;
the storage unit is further configured to determine, when the receiving unit receives an identifier update request, whether an identifier before update carried in the request is stored in the association relationship, and if so, replace, by using the updated identifier carried in the request, an identifier in the association relationship that is the same as the identifier before update carried in the request; otherwise, storing the incidence relation between the identifier before updating and the identifier after updating carried in the request.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1-6 when executing the program.
10. A computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, is adapted to carry out the method of any one of claims 1 to 6.
CN202110270823.6A 2021-03-12 2021-03-12 Identification updating method and device Active CN113037844B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110270823.6A CN113037844B (en) 2021-03-12 2021-03-12 Identification updating method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110270823.6A CN113037844B (en) 2021-03-12 2021-03-12 Identification updating method and device

Publications (2)

Publication Number Publication Date
CN113037844A true CN113037844A (en) 2021-06-25
CN113037844B CN113037844B (en) 2023-01-31

Family

ID=76470257

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110270823.6A Active CN113037844B (en) 2021-03-12 2021-03-12 Identification updating method and device

Country Status (1)

Country Link
CN (1) CN113037844B (en)

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101540726A (en) * 2009-04-27 2009-09-23 华为技术有限公司 Method, client, server and system of synchronous data
CN103500191A (en) * 2013-09-17 2014-01-08 华为技术有限公司 Flow table configuration, query and table item deleting method and device
CN106021594A (en) * 2016-06-06 2016-10-12 福建榕基软件股份有限公司 Database table and XML message mapping processing method and system
CN107862040A (en) * 2017-11-06 2018-03-30 中国银行股份有限公司 The update method of data, device and a kind of cluster in a kind of caching of application example
WO2018111412A1 (en) * 2016-12-16 2018-06-21 Mastercard International Incorporated Systems and methods for identifying updated unrequested on-file data
CN108959560A (en) * 2018-07-03 2018-12-07 泰康保险集团股份有限公司 Information processing method, device and electronic equipment based on tables of data
CN109002535A (en) * 2018-07-18 2018-12-14 腾讯科技(深圳)有限公司 A kind of data-updating method and device
CN109617647A (en) * 2018-10-22 2019-04-12 中国平安财产保险股份有限公司 Message forwarding method, device, computer equipment and computer readable storage medium
CN111262726A (en) * 2020-01-08 2020-06-09 Oppo广东移动通信有限公司 Configuration information updating method and device and computer readable storage medium
CN111415147A (en) * 2020-03-17 2020-07-14 深圳市炎华信息技术有限公司 Marketing account management method, marketing account management device, marketing account management equipment and computer storage medium

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101540726A (en) * 2009-04-27 2009-09-23 华为技术有限公司 Method, client, server and system of synchronous data
CN103500191A (en) * 2013-09-17 2014-01-08 华为技术有限公司 Flow table configuration, query and table item deleting method and device
CN106021594A (en) * 2016-06-06 2016-10-12 福建榕基软件股份有限公司 Database table and XML message mapping processing method and system
WO2018111412A1 (en) * 2016-12-16 2018-06-21 Mastercard International Incorporated Systems and methods for identifying updated unrequested on-file data
CN107862040A (en) * 2017-11-06 2018-03-30 中国银行股份有限公司 The update method of data, device and a kind of cluster in a kind of caching of application example
CN108959560A (en) * 2018-07-03 2018-12-07 泰康保险集团股份有限公司 Information processing method, device and electronic equipment based on tables of data
CN109002535A (en) * 2018-07-18 2018-12-14 腾讯科技(深圳)有限公司 A kind of data-updating method and device
CN109617647A (en) * 2018-10-22 2019-04-12 中国平安财产保险股份有限公司 Message forwarding method, device, computer equipment and computer readable storage medium
CN111262726A (en) * 2020-01-08 2020-06-09 Oppo广东移动通信有限公司 Configuration information updating method and device and computer readable storage medium
CN111415147A (en) * 2020-03-17 2020-07-14 深圳市炎华信息技术有限公司 Marketing account management method, marketing account management device, marketing account management equipment and computer storage medium

Also Published As

Publication number Publication date
CN113037844B (en) 2023-01-31

Similar Documents

Publication Publication Date Title
CN109474701B (en) Block chain prediction machine, internet of things equipment and information processing method
CN110119292B (en) System operation parameter query method, matching method, device and node equipment
CN107172169A (en) Method of data synchronization, device, server and storage medium
CN110677492B (en) Access request processing method and device, electronic equipment and storage medium
CN108958949B (en) Calling method and system of application program
CN110113247A (en) Rich media information receive-transmit system, transmission, methods of exhibiting and terminal device
CN112565334B (en) Access method and device of Internet of things equipment and MQTT gateway
CN103701653B (en) The processing method of a kind of interface hot plug configuration data and network configuration server
CN111901705A (en) OMCI function virtualization system of OLT equipment
CN108540408B (en) Openstack-based distributed virtual switch management method and system
CN109151025A (en) Load-balancing method, device, computer storage medium and equipment based on URL
CN107870982A (en) Data processing method, system and computer-readable recording medium
CN104796495A (en) Message pushing method and system
CN108076081A (en) Method, device and system for synchronizing service data
CN106878052B (en) User migration method and device
CN111726776A (en) Automatic network dialing parameter identification method of Internet of vehicles equipment
CN111008220A (en) Dynamic identification method and device of data source, storage medium and electronic device
CN113037844B (en) Identification updating method and device
CN109842482B (en) Information synchronization method, system and terminal equipment
CN115526586A (en) Business process processing method based on intelligent operation
CN107888677B (en) Communication implementation method, control terminal, intelligent device and system
WO2022183713A1 (en) Data storage method, apparatus, and device, and storage medium
CN115277707A (en) Service processing method, device, electronic equipment and storage medium
CN108574592A (en) A kind of method for managing resource and device based on telecom cloud
CN114866970A (en) Policy control method, system and related equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant