CN117596141A - Message assembling method, device, equipment and storage medium - Google Patents
Message assembling method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN117596141A CN117596141A CN202311655853.4A CN202311655853A CN117596141A CN 117596141 A CN117596141 A CN 117596141A CN 202311655853 A CN202311655853 A CN 202311655853A CN 117596141 A CN117596141 A CN 117596141A
- Authority
- CN
- China
- Prior art keywords
- message
- domain
- initial
- transaction
- interface
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 56
- 238000004590 computer program Methods 0.000 claims description 16
- 238000012217 deletion Methods 0.000 claims description 9
- 230000037430 deletion Effects 0.000 claims description 9
- 238000012545 processing Methods 0.000 description 14
- 238000004891 communication Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000012360 testing method Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000005034 decoration Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 125000004122 cyclic group Chemical group 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Marketing (AREA)
- Signal Processing (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the invention discloses a message assembling method, a device, equipment and a storage medium, wherein the method comprises the following steps: acquiring a transaction type and an initial transaction message domain, and updating the initial transaction message domain according to the transaction type to obtain an updated transaction message domain; wherein, the initial transaction message field contains a plurality of initial configuration elements; when the newly added configuration element exists in the updated transaction message domain, acquiring an initial transaction interface domain, and newly adding an additional message domain in the initial transaction interface domain according to the newly added configuration element to acquire the updated transaction interface domain; the initial transaction interface domain comprises an initial message domain corresponding to each initial configuration element; and respectively inputting the initial message domain value and the additional message domain value into each initial message domain and the additional message domain, and assembling each message domain value to obtain the transaction message. The technical scheme of the invention can realize dynamic updating of the transaction interface domain, and improves the flexibility of determining the transaction message.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a storage medium for packet assembly.
Background
The capital transaction message standard is upgraded and optimized every year, for example, the SWIFT message standard is upgraded every year, so that the corresponding system message is also upgraded and reformed. In addition, each fund product transaction has different requirements for the same type of message, and each branch has different requirements for the message.
In the prior art, a background configuration and a general page dynamic generation technology are generally adopted to generate and update a transaction interface domain, and a transaction message is generated according to the updated transaction interface domain. Specifically, the transaction interface field may be updated by modifying the transaction interface field corresponding code in the background.
However, in the prior art, the code needs to be modified in the background, so that a tester is required to test the system every time the transaction interface domain is updated, and thus the transaction message cannot be flexibly generated according to the user requirement.
Disclosure of Invention
The invention provides a message assembling method, a device, equipment and a storage medium, which can realize dynamic updating of a transaction interface domain and improve the flexibility of determining transaction messages.
In a first aspect, a method for assembling a message is provided, the method comprising:
acquiring a transaction type and an initial transaction message domain, and updating the initial transaction message domain according to the transaction type to obtain an updated transaction message domain;
wherein, the initial transaction message field contains a plurality of initial configuration elements;
when the newly added configuration element exists in the updated transaction message domain, acquiring an initial transaction interface domain, and newly adding an additional message domain in the initial transaction interface domain according to the newly added configuration element to acquire the updated transaction interface domain;
the initial transaction interface domain comprises an initial message domain corresponding to each initial configuration element;
and respectively inputting the initial message domain value and the additional message domain value into each initial message domain and the additional message domain, and assembling each message domain value to obtain the transaction message.
Optionally, updating the initial transaction message field according to the transaction type includes: according to the transaction type, adding and/or deleting initial configuration elements in an initial transaction message domain;
the method further comprises the following steps:
when the initial configuration element is deleted, the deletion configuration element is obtained, and the initial transaction interface domain is updated according to the deletion configuration element.
Optionally, the initial transaction message field includes an interface name, an interface control type, an interface value range and an initial message field;
acquiring an initial transaction interface field, comprising:
determining a target transaction interface corresponding to the initial transaction message domain according to the interface name, the interface control type and the interface value range;
and generating an initial transaction interface domain corresponding to the target transaction interface according to the initial message domain.
Optionally, after inputting the initial message domain value and the additional message domain value into each of the initial message domain and the additional message domain, the method further includes:
acquiring a preset message domain value table, and adding each additional message domain to a message adding sequence in the initial transaction message domain;
and storing the additional message domain and the additional message domain value into a preset message domain value table according to the new message adding sequence.
Optionally, assembling each message domain value to obtain a transaction message, including:
acquiring a preset message type, and assembling each initial message threshold according to the preset message type to obtain an initial message assembling result;
and assembling the additional message domain value and the initial message assembling result according to the new message adding sequence to obtain the transaction message.
Optionally, inputting additional message domain values into each additional message domain includes:
judging whether an additional message domain exists in the updated transaction interface domain;
if yes, inputting an additional message domain value in an additional message tab corresponding to the additional message domain.
In a second aspect, there is provided a message assembling apparatus, the apparatus comprising:
the transaction message domain updating module is used for acquiring the transaction type and the initial transaction message domain, and updating the initial transaction message domain according to the transaction type to obtain an updated transaction message domain; wherein, the initial transaction message field contains a plurality of initial configuration elements;
the transaction interface domain updating module is used for acquiring an initial transaction interface domain when the newly added configuration element exists in the updated transaction message domain, and newly adding an additional message domain in the initial transaction interface domain according to the newly added configuration element to acquire the updated transaction interface domain; the initial transaction interface domain comprises an initial message domain corresponding to each initial configuration element;
and the transaction message generation module is used for respectively inputting the initial message domain value and the additional message domain value into each initial message domain and the additional message domain, and assembling each message domain value to obtain the transaction message.
Optionally, the transaction message generating module includes:
the initial message assembly unit is used for acquiring a preset message type, and assembling each initial message domain value according to the preset message type to obtain an initial message assembly result;
and the transaction message generating unit is used for assembling the additional message threshold value and the initial message assembling result according to the message newly-added sequence to obtain the transaction message.
In a third aspect, there is provided an electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the message assembly method of any one of the embodiments of the present invention.
In a fourth aspect, a computer readable storage medium is provided, where the computer readable storage medium stores computer instructions for causing a processor to implement a message assembly method according to any of the embodiments of the present invention when executed.
According to the technical scheme, the transaction type and the initial transaction message domain are obtained, and the initial transaction message domain is updated according to the transaction type to obtain an updated transaction message domain; wherein, the initial transaction message field contains a plurality of initial configuration elements; when the newly added configuration element exists in the updated transaction message domain, acquiring an initial transaction interface domain, and newly adding an additional message domain in the initial transaction interface domain according to the newly added configuration element to acquire the updated transaction interface domain; the initial transaction interface domain comprises an initial message domain corresponding to each initial configuration element; the method comprises the steps of respectively inputting an initial message domain value and an additional message domain value into each initial message domain and each additional message domain, and assembling each message domain value to obtain a transaction message.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the invention or to delineate the scope of the invention. Other features of the present invention will become apparent from the description that follows.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flowchart of a message assembly method according to a first embodiment of the present invention;
FIG. 2 is a flowchart of another message assembly method according to a second embodiment of the present invention;
fig. 3 is a schematic structural diagram of a message assembling apparatus according to a third embodiment of the present invention;
fig. 4 is a schematic structural diagram of an electronic device implementing a message assembly method according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Example 1
Fig. 1 is a flowchart of a message assembly method according to a first embodiment of the present invention, where the method may be performed by a message assembly device, and the message assembly device may be implemented in hardware and/or software, and the message assembly device may be configured in an electronic device, such as a computer. As shown in fig. 1, the method includes:
s110, acquiring a transaction type and an initial transaction message domain, and updating the initial transaction message domain according to the transaction type to obtain an updated transaction message domain.
Wherein the initial transaction message field contains a plurality of initial configuration elements.
In this embodiment, the transaction type may be the type of transaction product. The transaction products may include bonds, derivatives, money markets, foreign exchange, and the like. The initial transaction message field may include initial configuration elements such as transaction name, message type, and initial message field.
In this step, specifically, the initial configuration element may be added, deleted or modified according to the transaction type, to obtain an updated transaction message field.
S120, when the newly added configuration element exists in the updated transaction message domain, acquiring an initial transaction interface domain, and newly adding an additional message domain in the initial transaction interface domain according to the newly added configuration element to acquire the updated transaction interface domain.
The initial transaction interface field contains initial message fields corresponding to the initial configuration elements.
In this embodiment, the initial transaction interface field may be used to generate a target transaction interface corresponding thereto.
In this step, specifically, before the initial transaction interface domain is acquired, a centralized interception technology may be used to intercept the update transaction message domain, and determine whether a new configuration element exists in the update transaction message domain, and if the new configuration element exists in the update transaction message domain, then an additional message domain may be newly added in the initial transaction interface domain. Then, additional message tabs can be added in the initial transaction interface field according to the additional message fields. The additional message tabs are in one-to-one correspondence with the additional message fields, that is, the number of the additional message tabs can be determined according to the number of the additional message fields.
S130, respectively inputting an initial message domain value and an additional message domain value into each initial message domain and the additional message domain, and assembling each message domain value to obtain a transaction message.
In this embodiment, the initial message threshold and the additional message threshold may be determined according to the transaction content and the user requirement.
In this step, specifically, an initial message tab corresponding to an initial message domain and an additional message tab corresponding to an additional message domain may be obtained in the transaction interface, and a corresponding message domain value may be input into each tab. And then, assembling the message domain values based on the decorator mode to obtain the transaction message. The decorator schema may be a design schema that allows new functionality to be added to an existing object without changing its structure.
The advantage of this arrangement is that compared with the prior art of newly adding and rewriting different message processing classes, the technical solution of this embodiment dynamically updates the transaction interface fields of different message types through the decorator mode, thereby implementing the dynamic update of the transaction interface fields, reducing the addition and expansion of the message processing classes, and improving the flexibility of determining the transaction messages.
According to the technical scheme, the transaction type and the initial transaction message domain are obtained, and the initial transaction message domain is updated according to the transaction type to obtain an updated transaction message domain; when the newly added configuration element exists in the updated transaction message domain, acquiring an initial transaction interface domain, and newly adding an additional message domain in the initial transaction interface domain according to the newly added configuration element to acquire the updated transaction interface domain; the method comprises the steps of respectively inputting an initial message domain value and an additional message domain value into each initial message domain and each additional message domain, and assembling each message domain value to obtain a transaction message.
Example two
Fig. 2 is a flowchart of another message assembly method according to a second embodiment of the present invention, where the technical solution in this embodiment is further refined, and the technical solution in this embodiment may be combined with each of the alternatives in one or more embodiments.
As shown in fig. 2, this embodiment discloses a message assembling method, which includes:
s210, acquiring a transaction type and an initial transaction message domain, and performing addition and/or deletion operation on initial configuration elements in the initial transaction message domain according to the transaction type to obtain an updated transaction message domain.
In this embodiment, the initial transaction message field includes a transaction name, a message type, an interface name, an interface control type, an interface value range, an initial message field, and the like. Interface control types may include file transfer, calendar management, grid controls, menu management, buttons, and window controls, among others. The initial message field may be used to reflect the transaction content.
Specifically, the initial transaction message field may be updated by the following procedure: an initial transaction message field may be acquired first and initial configuration elements in the transaction message field queried. Then, the new button can be clicked on the configuration page of the transaction message domain, and the configuration element can be newly added on the popped configuration page. Alternatively, an initial configuration element may be selected in the transaction message domain configuration page and a modify button may be clicked to modify the initial configuration element.
Optionally, when the initial configuration element is deleted, a deletion configuration element is obtained, and the initial transaction interface field is updated according to the deletion configuration element. For example, an initial configuration element may be selected in the transaction message domain configuration page and a delete button may be clicked to delete the corresponding initial configuration element (i.e., delete the configuration element).
The setting has the advantages that the interface message domain can be flexibly expanded, deleted or modified, and the change of the message demand can be dynamically adapted.
S220, when the newly added configuration element exists in the updated transaction message domain, determining a target transaction interface corresponding to the initial transaction message domain according to the interface name, the interface control type and the interface value range.
S230, generating an initial transaction interface domain corresponding to the target transaction interface according to the initial message domain.
S240, adding additional message fields in the initial transaction interface fields according to the newly added configuration elements to obtain updated transaction interface fields.
In this embodiment, optionally, the target transaction interface may be updated according to the update transaction interface field, to obtain an update transaction interface. The update transaction interface may include an initial message tab corresponding to the initial configuration element and an additional message tab corresponding to the newly added configuration element.
By way of example, the update transaction interface may be generated by: first, a funds transaction code may be entered, and the funds transaction opened. The updated transaction message fields may then be intercepted prior to transaction loading and checked for the presence of additional message fields in the updated transaction message fields. If there is an additional message domain in the update transaction message domain, an update transaction interface domain may be generated according to the additional message domain. At this point, the funds transaction may be loaded normally and the update transaction interface generated from the update transaction interface field.
S250, inputting the initial message domain value and the additional message domain value into each initial message domain and the additional message domain respectively.
In this embodiment, optionally, a product transaction table may be obtained, and transaction product information stored in the product transaction table is used as an initial message domain value or an additional message domain value, and is automatically input to the initial message tab and the additional message tab.
In an optional implementation manner of the embodiment of the present invention, inputting an additional message domain value into each additional message domain includes: judging whether an additional message domain exists in the updated transaction interface domain; if yes, inputting an additional message domain value in an additional message tab corresponding to the additional message domain.
S260, acquiring a preset message domain value table, and newly adding each additional message domain to the message newly-added sequence in the initial transaction message domain.
In this embodiment, the preset message domain value table may be used to store a plurality of additional message domains and the corresponding additional message domain values thereof. Alternatively, the preset message threshold table may be a vertical table. The order of message addition may be determined based on the order in which each additional message field is added to the initial transaction message field.
S270, storing the additional message domain and the additional message domain value into a preset message domain value table according to the new message adding sequence.
In this step, specifically, a key value pair formed by an additional message field and an additional message field value may be obtained, and the key value pair is used as a hash table parameter. Then, according to the new sequence of the messages, each hash table parameter can be stored into a preset message threshold table. Alternatively, the transaction state of each additional message threshold may be checked periodically at night in batches, and the additional message Wen Yuzhi of the expired transaction is moved into the preset historical message threshold table, so that excessive data in the preset message threshold table is avoided.
For example, it may be checked whether an additional message field is included in an extensible markup language (Extensible Markup Language, XML) page when transaction processing is performed. If the additional message domain exists in the XML page, the additional message domain value in the transaction interface can be extracted and analyzed and updated. And then, carrying out cyclic processing on the domain values of each additional message to generate a domain value record list, and storing the domain value record list into a preset message domain value table.
The method has the advantages that the extra message threshold value is stored in the preset message threshold value table, the original product transaction table and the original message table are not required to be modified, the change of the table structure is reduced, and the influence on a downstream system is reduced. The message table may store transaction messages.
S280, acquiring a preset message type, and assembling each initial message threshold according to the preset message type to obtain an initial message assembly result.
S290, according to the new message adding sequence, the additional message threshold value and the initial message assembling result are assembled to obtain the transaction message.
In this embodiment, multiple additional message threshold values may be assembled to the initial message assembly result according to the message addition sequence, so as to obtain the transaction message.
Specifically, message assembly can be performed through a preset fund module and a preset message module. The preset fund module can comprise product sub-modules such as bonds, derivatives, foreign exchange buying and selling, money market and the like. The preset fund module can be used for updating the transaction interface field and sending each message threshold value to the preset message module. The preset message module may be configured to correspond each message domain value to an actual message domain according to a message type, so as to generate a transaction message.
By way of example, message assembly may be performed by the following procedure: and generating different message processing objects according to different message types through a preset fund module, and transmitting the hash table parameters into a decoration type method of the preset message module. Then, the original message class assembly method can be called through the decoration class method to generate the transaction message. The original message assembly method can be used for generating an initial message assembly result. Different message types may correspond to different message assembly classes.
Alternatively, after the additional message domain value is input to the additional message tab, the additional message domain processing interface in the preset message module may be called by the preset fund module. Then, the message processing object can be decorated based on the decorator mode through the preset message module, namely, a plurality of additional message domain values are assembled to an initial message assembling result, and the transaction message is obtained. Finally, the transaction message may be transmitted back to the default funds module for previewing.
According to the technical scheme of the embodiment, the transaction type and the initial transaction message domain are obtained, and according to the transaction type, the initial configuration elements in the initial transaction message domain are added and/or deleted to obtain an updated transaction message domain; when the newly added configuration elements exist in the updated transaction message domain, determining a target transaction interface corresponding to the initial transaction message domain according to the interface name, the interface control type and the interface value range; generating an initial transaction interface domain corresponding to the target transaction interface according to the initial message domain; adding additional message fields in the initial transaction interface fields according to the newly added configuration elements to obtain updated transaction interface fields; inputting an initial message domain value and an additional message domain value into each initial message domain and additional message domain respectively; acquiring a preset message domain value table, and adding each additional message domain to a message adding sequence in the initial transaction message domain; storing the additional message domain and the additional message domain value into a preset message domain value table according to the new message adding sequence; acquiring a preset message type, and assembling each initial message threshold according to the preset message type to obtain an initial message assembling result; according to the new message adding sequence, the additional message domain value and the initial message assembling result are assembled to obtain the technical means of the transaction message, so that the problem that a tester is required to test a system and the flexibility is insufficient when the transaction interface domain is updated every time because the code is required to be modified in the background in the prior art is solved, the dynamic updating of the transaction interface domain can be realized, and the flexibility of determining the transaction message is improved. And secondly, the additional message threshold value of the expired transaction is shifted into a preset historical message threshold value table at regular intervals, so that the message assembly efficiency is improved.
In the technical scheme of the disclosure, the related processes of collecting, storing, using, processing, transmitting, providing, disclosing and the like of the personal information of the user accord with the regulations of related laws and regulations, and the public order colloquial is not violated.
Example III
Fig. 3 is a schematic structural diagram of a message assembling apparatus according to a third embodiment of the present invention.
As shown in fig. 3, the apparatus includes:
a transaction message domain updating module 31, a transaction interface domain updating module 32 and a transaction message generating module 33.
The transaction message domain updating module 31 is configured to obtain a transaction type and an initial transaction message domain, and update the initial transaction message domain according to the transaction type to obtain an updated transaction message domain; wherein, the initial transaction message field contains a plurality of initial configuration elements;
the transaction interface domain updating module 32 is configured to obtain an initial transaction interface domain when a new configuration element exists in the updated transaction message domain, and to add an additional message domain in the initial transaction interface domain according to the new configuration element, so as to obtain an updated transaction interface domain; the initial transaction interface domain comprises an initial message domain corresponding to each initial configuration element;
the transaction message generating module 33 is configured to input an initial message domain value and an additional message domain value into each of the initial message domain and the additional message domain respectively, and assemble each of the message domain values to obtain a transaction message.
According to the technical scheme provided by the embodiment of the invention, the transaction message domain updating module, the transaction interface domain updating module and the transaction message generating module are mutually matched, so that the problem that a tester is required to test a system when the transaction interface domain is updated every time in the prior art due to the fact that codes are required to be modified in the background is solved, the problem of insufficient flexibility is solved, dynamic updating of the transaction interface domain can be realized, the flexibility of determining the transaction message is improved, and the follow-up maintenance is facilitated.
Optionally, the transaction message domain updating module 31 includes:
and the configuration element modification unit is used for carrying out addition and/or deletion operation on the initial configuration elements in the initial transaction message domain according to the transaction type.
Optionally, the apparatus further includes a configuration element deletion module, which includes:
and the configuration element deleting unit is used for acquiring the deleted configuration element when the initial configuration element is deleted, and updating the initial transaction interface domain according to the deleted configuration element.
Optionally, the initial transaction message field includes an interface name, an interface control type, an interface value range and an initial message field; the transaction interface field update module 32 includes:
the target interface determining unit is used for determining a target transaction interface corresponding to the initial transaction message domain according to the interface name, the interface control type and the interface value range;
and the initial interface domain generating unit is used for generating an initial transaction interface domain corresponding to the target transaction interface according to the initial message domain.
Optionally, the device further comprises a threshold storage module, the module comprising
The new adding sequence obtaining unit is used for obtaining a preset message domain value table and a message adding sequence of each additional message domain newly added to the initial transaction message domain;
and the domain value storage unit is used for storing the additional message domain and the additional message domain value into a preset message domain value table according to the new message adding sequence.
Optionally, the transaction message generating module 33 includes:
the initial result obtaining unit is used for obtaining a preset message type, and assembling each initial message domain value according to the preset message type to obtain an initial message assembling result;
the transaction message generating unit is used for assembling the additional message threshold value and the initial message assembling result according to the message newly-added sequence to obtain a transaction message;
the extra message domain judging unit is used for judging whether the extra message domain exists in the updated transaction interface domain;
and the extra domain value input unit is used for inputting extra message domain values in extra message tabs corresponding to the extra message domains if the extra message domains exist in the updated transaction interface domains.
The message assembling device provided by the embodiment of the invention can execute the message assembling method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the executing method.
Example IV
Fig. 4 shows a schematic diagram of the structure of an electronic device 10 that may be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic equipment may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.
As shown in fig. 4, the electronic device 10 includes at least one processor 11, and a memory, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, etc., communicatively connected to the at least one processor 11, in which the memory stores a computer program executable by the at least one processor, and the processor 11 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from the storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 may also be stored. The processor 11, the ROM 12 and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.
Various components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, etc.; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.
The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 11 performs the various methods and processes described above, such as message assembly methods.
In some embodiments, the message assembly method may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as the storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the message assembly method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the message assembly method in any other suitable way (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
A computer program for carrying out methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.
The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present invention may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solution of the present invention are achieved, and the present invention is not limited herein.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.
Claims (10)
1. A method of message assembly, comprising:
acquiring a transaction type and an initial transaction message domain, and updating the initial transaction message domain according to the transaction type to obtain an updated transaction message domain;
wherein the initial transaction message field contains a plurality of initial configuration elements;
when a new configuration element exists in the updated transaction message domain, acquiring an initial transaction interface domain, and adding an additional message domain in the initial transaction interface domain according to the new configuration element to acquire the updated transaction interface domain;
wherein the initial transaction interface domain comprises an initial message domain corresponding to each initial configuration element;
and respectively inputting an initial message domain value and an additional message domain value into each initial message domain and the additional message domain, and assembling each message domain value to obtain a transaction message.
2. The method of claim 1, wherein updating the initial transaction message field according to the transaction type comprises:
according to the transaction type, adding and/or deleting initial configuration elements in the initial transaction message domain;
the method further comprises the steps of:
when the initial configuration element is deleted, acquiring a deletion configuration element, and updating the initial transaction interface domain according to the deletion configuration element.
3. The method of claim 1, wherein the initial transaction message field comprises an interface name, an interface control type, an interface value range, and an initial message field;
the acquiring the initial transaction interface field comprises the following steps:
determining a target transaction interface corresponding to the initial transaction message domain according to the interface name, the interface control type and the interface value range;
and generating an initial transaction interface domain corresponding to the target transaction interface according to the initial message domain.
4. The method of claim 1, further comprising, after entering the initial and additional message fields into each of the initial and additional message fields, respectively:
acquiring a preset message domain value table and a message adding sequence of each additional message domain newly added to the initial transaction message domain;
and storing the additional message domain and the additional message domain value into the preset message domain value table according to the new message adding sequence.
5. The method of claim 4, wherein assembling each of the message threshold values to obtain a transaction message comprises:
acquiring a preset message type, and assembling each initial message threshold according to the preset message type to obtain an initial message assembling result;
and assembling the additional message threshold and the initial message assembly result according to the message newly-added sequence to obtain a transaction message.
6. The method of claim 1, wherein inputting additional message fields into each of the additional message fields comprises:
judging whether an additional message domain exists in the updated transaction interface domain;
if yes, inputting an additional message domain value in an additional message tab corresponding to the additional message domain.
7. A message assembling apparatus, comprising:
the transaction message domain updating module is used for acquiring a transaction type and an initial transaction message domain, and updating the initial transaction message domain according to the transaction type to obtain an updated transaction message domain; wherein the initial transaction message field contains a plurality of initial configuration elements;
the transaction interface domain updating module is used for acquiring an initial transaction interface domain when a new configuration element exists in the updated transaction message domain, and adding an additional message domain in the initial transaction interface domain according to the new configuration element to acquire the updated transaction interface domain; wherein the initial transaction interface domain comprises an initial message domain corresponding to each initial configuration element;
and the transaction message generation module is used for respectively inputting the initial message domain value and the additional message domain value into each of the initial message domain and the additional message domain, and assembling each of the message domain values to obtain the transaction message.
8. The apparatus of claim 7, wherein the transaction message generation module comprises:
the initial message assembling unit is used for obtaining preset message types, and assembling the initial message domain values according to the preset message types to obtain initial message assembling results;
and the transaction message generating unit is used for assembling the additional message domain value and the initial message assembling result according to the message newly-added sequence to obtain the transaction message.
9. An electronic device, the electronic device comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the message assembly method of any one of claims 1-6.
10. A computer readable storage medium storing computer instructions for causing a processor to perform the method of message assembly of any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311655853.4A CN117596141A (en) | 2023-12-05 | 2023-12-05 | Message assembling method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311655853.4A CN117596141A (en) | 2023-12-05 | 2023-12-05 | Message assembling method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117596141A true CN117596141A (en) | 2024-02-23 |
Family
ID=89914962
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311655853.4A Pending CN117596141A (en) | 2023-12-05 | 2023-12-05 | Message assembling method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117596141A (en) |
-
2023
- 2023-12-05 CN CN202311655853.4A patent/CN117596141A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114816393B (en) | Information generation method, device, equipment and storage medium | |
| CN116611411A (en) | Business system report generation method, device, equipment and storage medium | |
| CN114389969A (en) | Client test method and device, electronic equipment and storage medium | |
| CN116089739A (en) | Message pushing method, device, electronic equipment and storage medium | |
| CN116185389A (en) | Code generation method and device, electronic equipment and medium | |
| CN115543423A (en) | Method, device and equipment for generating benchmarks and storage medium | |
| CN117596141A (en) | Message assembling method, device, equipment and storage medium | |
| CN114138358A (en) | Application program starting optimization method, device, equipment and storage medium | |
| CN113691403A (en) | Topological node configuration method, related device and computer program product | |
| CN115840604B (en) | Data processing method, device, electronic equipment and computer readable storage medium | |
| CN115951921A (en) | Service processing method, device and storage medium | |
| CN118051670A (en) | Service recommendation method, device, equipment and medium | |
| CN117493214A (en) | Interface message generation method and device, electronic equipment and storage medium | |
| CN116894048A (en) | Data query method, device, equipment and storage medium based on artificial intelligence | |
| CN115098520A (en) | Device data updating method and device, electronic device and storage medium | |
| CN117668114A (en) | Data synchronization method, device, equipment and medium | |
| CN117574477A (en) | Distribution box drawing output method and device, electronic equipment and storage medium | |
| CN116069319A (en) | Form rendering method and device, electronic equipment and storage medium | |
| CN117608944A (en) | Method and device for calculating weight migration volume ratio, electronic equipment and storage medium | |
| CN116303071A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN117032712A (en) | Pipeline compiling and constructing method and device, electronic equipment and storage medium | |
| CN117640752A (en) | SWIFT standard-based message matching method, device and equipment | |
| CN117278648A (en) | Protocol dynamic adaptation method, device, electronic equipment and storage medium | |
| CN114564133A (en) | Application program display method, device, equipment and medium | |
| CN114896322A (en) | JSON (Java Server object notation) -based configuration data conversion method, device, equipment and medium |
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 |