Element processing method and device based on business system, equipment and storage medium
By generating and distributing unified feature format standards and open interfaces, the problem of inconsistent data feature formats between different business systems is solved, the feature format and label unity of the global system is realized, and the interoperability between business systems is improved.
Patent Information
- Application Number
- CN202310545141.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-15
- Publication Date
- 2024-11-15
AI Technical Summary
The format and identification of data elements between different business systems are not uniform, resulting in the problem of unrecognition of breakpoints and associated elements between data elements.
By obtaining the business attributes in the global system, generating and distributing unified feature format standards, ensuring that different business systems adopt the same feature format, and achieving balanced routing processing of service requests through open interfaces.
It realizes the unity of feature formats and labels in the global system, avoids breakpoints and related factor identification problems between data elements, and improves interoperability between business systems.
Smart Images

Figure CN118966988A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of artificial intelligence technology, and specifically relates to a method, device, equipment and storage medium for element processing based on a business system. Background Art
[0002] With the development of society, there are more and more service interactions and data interactions between business systems.
[0003] In the past, the group generally had multiple businesses running at the same time, each with its own independent self-operating system, but there were also cases where multiple businesses were based on the same common technology platform. If the format and identification of elements in the global system are not unified, there will be breakpoints between data elements of different businesses and business scenarios, and related elements cannot be well identified. Summary of the invention
[0004] In order to solve the above-mentioned problems in the prior art, the present application provides an element processing method, device, equipment and storage medium based on a business system.
[0005] In a first aspect, the present application provides a method for processing elements based on a business system, the method comprising:
[0006] Acquire business attributes of a business system in a global system, wherein the global system includes a plurality of business systems having business interactions;
[0007] Generate a globally unified element format standard according to the business attributes of the business system;
[0008] The element format standard is distributed to the multiple business systems so that different business systems use the same element format.
[0009] In a possible implementation, generating a globally unified element format standard according to the business attributes of the business system includes:
[0010] According to the business attribute, obtaining the target element unified rule corresponding to the business attribute; wherein the business attribute is used to indicate the business processing type, and different business attributes correspond to different element unified rules;
[0011] According to the target element unification rule, a globally unified element format standard is generated.
[0012] In a possible implementation, generating a globally unified element format standard according to the target element unified rule includes:
[0013] According to the unified rule of the target element, the header element format standard is obtained, the header element format standard includes the preset code digits of each element and the code generation rule of each element, and the header element format standard is used to generate the eco-party code, business code, business code and execution code; wherein each element corresponds to its own preset code digits;
[0014] A globally unified element format standard is generated according to the header element format standard.
[0015] In a possible implementation manner, generating a globally unified element format standard according to the header element format standard includes:
[0016] According to the target element unified rule, a rear element format standard is obtained, wherein the rear element format standard includes a preset code digit number of each rear element and a code generation rule of the rear element, and the rear element format standard is used to generate an identification extension code, a reserved code and a custom code;
[0017] A globally unified element format standard is generated according to the header element format standard and the rear element format standard.
[0018] In a possible implementation, the method further includes:
[0019] Obtain an open interface that matches each element format standard;
[0020] The open interface is distributed to the plurality of business systems, so that different business systems use the element format standard through the open interface.
[0021] In a possible implementation, the method further includes:
[0022] Receiving a service request sent by the first business system, wherein the service request is used to request a service from the second business system;
[0023] According to the load of the second business system, route balancing processing is performed, and the service request is forwarded to the second business system, so that the service request arrives at the second business system in a balanced manner.
[0024] In a possible implementation manner, after receiving the service request sent by the first business system, the method further includes:
[0025] Determine whether the first business system is in a whitelist, where the whitelist includes multiple business systems included in the global system;
[0026] If it is in the whitelist, and obtains access rights to the first business system;
[0027] It is determined according to the access permission that the first business system can access the second business system.
[0028] In a second aspect, the present application provides an element processing control device based on a business system, comprising: an acquisition module, a generation module and a distribution module, wherein:
[0029] The acquisition module is used to acquire the business attributes of the business system in the global system, wherein the global system includes a plurality of business systems with business interactions;
[0030] The generating module is used to generate a globally unified element format standard according to the business attributes of the business system;
[0031] The distribution module is used to distribute the element format standard to the multiple business systems so that different business systems use the same element format.
[0032] In a possible implementation manner, the generating module is further used for:
[0033] According to the business attribute, obtaining the target element unified rule corresponding to the business attribute; wherein the business attribute is used to indicate the business processing type, and different business attributes correspond to different element unified rules;
[0034] According to the target element unification rule, a globally unified element format standard is generated.
[0035] In a possible implementation manner, the generating module is further used for:
[0036] According to the unified rule of the target element, the header element format standard is obtained, the header element format standard includes the preset code digits of each element and the code generation rule of each element, and the header element format standard is used to generate the eco-party code, business code, business code and execution code; wherein each element corresponds to its own preset code digits;
[0037] A globally unified element format standard is generated according to the header element format standard.
[0038] In a possible implementation manner, the generating module is further used for:
[0039] According to the target element unified rule, a rear element format standard is obtained, wherein the rear element format standard includes a preset code digit number of each rear element and a code generation rule of the rear element, and the rear element format standard is used to generate an identification extension code, a reserved code and a custom code;
[0040] A globally unified element format standard is generated according to the header element format standard and the rear element format standard.
[0041] In a possible implementation manner, the distribution module is further used for:
[0042] Obtain an open interface that matches each element format standard;
[0043] The open interface is distributed to the plurality of business systems, so that different business systems use the element format standard through the open interface.
[0044] In a possible implementation manner, the distribution module is further used for:
[0045] Receiving a service request sent by the first business system, wherein the service request is used to request a service from the second business system;
[0046] According to the load of the second business system, route balancing processing is performed, and the service request is forwarded to the second business system, so that the service request arrives at the second business system in a balanced manner.
[0047] In a possible implementation manner, the distribution module is further used for:
[0048] Determine whether the first business system is in a whitelist, where the whitelist includes multiple business systems included in the global system;
[0049] If it is in the whitelist, and obtains access rights to the first business system;
[0050] It is determined according to the access permission that the first business system can access the second business system.
[0051] In a third aspect, the present application provides an electronic device, including: at least one processor and a memory, wherein:
[0052] The memory is used to store computer-executable instructions;
[0053] The at least one processor is used to execute the computer-executable instructions stored in the memory, so that the at least one processor executes the element processing method based on the business system as described in any one of the first aspects.
[0054] In a fourth aspect, the present application provides a computer storage medium, in which computer execution instructions are stored. When the computer execution instructions are executed by a processor, they are used to implement the element processing method based on the business system as described in any of the above items.
[0055] In a fifth aspect, the present application also provides a computer program product, including a computer program, which, when executed by a processor, can implement the steps of the element processing method based on the business system as described in any of the above items.
[0056] The present application provides a method, device, equipment and storage medium for element processing based on a business system, which sets corresponding element format annotations according to the business system in the global system, issues the element format standard to the global system, and elementizes the services / data of each business based on the element format standard. Through the above method, the element format and label of the global system are unified, avoiding problems such as breakpoints between data elements of different businesses and different scenarios, different identities of unified elements, and poor identification between related elements. BRIEF DESCRIPTION OF THE DRAWINGS
[0057] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0058] Figure 1 A schematic diagram of a globally unified element format standard;
[0059] Figure 2 A schematic diagram of a process for processing elements based on a business system provided in an embodiment of the present application Figure 1 ;
[0060] Figure 3 A schematic diagram of a process for processing elements based on a business system provided in an embodiment of the present application Figure 2 ;
[0061] Figure 4 A schematic diagram of a process for processing elements based on a business system provided in an embodiment of the present application Figure 3 ;
[0062] Figure 5 A schematic diagram of the structure of an element processing control device based on a business system provided in an embodiment of the present application;
[0063] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.
[0064] Through the above-mentioned drawings, clear embodiments of the present application have been shown, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the concept of the present application in any way, but to illustrate the concept of the present application for those skilled in the art by reference to specific embodiments. Through the above-mentioned method, the service / data elements are standardized, so that the breakpoints between the data elements of different services and different scenarios of services are connected in series, and the intercommunication between related business systems in the global system is improved. DETAILED DESCRIPTION
[0065] In order to make the purpose, technical solutions and advantages of this application clearer, the technical solutions in this application will be clearly and completely described below in conjunction with the drawings in this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0066] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in sequences other than those illustrated or described herein, for example.
[0067] In the embodiments of the present application, the words "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.
[0068] With the development of society, there are more and more service interactions and data interactions between business systems. At present, most groups generally carry out multiple businesses at the same time. Each independent business has its own independent self-operating system, but there is also intercommunication between different businesses. Those intercommunication businesses are based on the same public technology platform. In this way, when supporting internal and external unified ecological businesses, there will be breakpoints between data elements of different businesses and different scenarios, different identities of unified elements, and poor identification between related elements.
[0069] Therefore, this application provides an element processing method based on the business system, which sets the corresponding element format annotation according to the business system in the global system, issues the element format standard to the global system, and elementizes the services / data of each business based on the element format standard. Through the above method, the element format and label of the global system are unified, avoiding the problems of breakpoints between data elements of different businesses and different scenarios, different identities of unified elements, and poor identification between related elements.
[0070] Next, the technical solution shown in the present application is described in detail through specific embodiments. It should be noted that the following embodiments can exist independently or in combination with each other, and the same or similar contents will not be described repeatedly in different embodiments.
[0071] Figure 1Schematic diagram of a globally unified element format standard. The globally unified element format standard provided in this embodiment includes:
[0072] The preset code digits of each element and the code generation rules of each element. Among them, the elements include: ecological party elements, business elements, business elements, execution elements, identification extension elements, reserved elements and custom elements. Then, based on the element format standard, the ecological party code, business code, execution code, identification extension code, reserved code and custom code are generated.
[0073] Furthermore, the preset code number of the eco-party code is 16 bits, the preset code number of the business code is 8 bits, the preset code number of the service code is 8 bits, the preset code number of the execution code is 4 bits, the preset code number of the identification extension code is 64 bits, the preset code number of the reserved code is 8 bits, and the number of bits of the custom code is the remaining number of codes.
[0074] Among them, the eco-party is the organization to which the business belongs, that is, the eco-party code is the code of the organization to which the business to be synchronized belongs; the identification extension code is the screening condition of the elements to be synchronized; the reserved code is the reserved extension code of the elements to be synchronized; the custom code is the code of a specific element. For example, when the service request is to query Zhang San's order data yesterday, the corresponding eco-party is the dealer, the corresponding eco-party code is the dealer's code, and the identification extension code is the screening condition, that is, the date. The custom code is the user code corresponding to Zhang San.
[0075] For example, when the service request is: synchronize the order data of Zhang San yesterday. The element code obtained according to the element format standard can be:
[0076] Eco-party code: 0000000000000011, the corresponding business owner is the dealer;
[0077] Business format code: 00000011, corresponding to the laundry business format of Eco-Fang;
[0078] Business code: 00000001, corresponding to men's clothing;
[0079] Execution code: 0022, corresponding to synchronous execution operation;
[0080] Identification extension code: 2023051020230511, corresponding to the date filter condition, the identification extension code is 64 bits, and the 0 in front of 2023051020230511 is omitted here;
[0081] The reserved code is the reserved extension code of the element to be synchronized, and if there is none, it is 000000000.
[0082] Custom code: 00034, corresponds to Zhang San’s user code.
[0083] Therefore, the code of the service request "Synchronize yesterday's Zhang San's order data" after elementization according to the element format standard is: a code composed of the ecosystem code, business code, business code, execution code, identification extension code, reserved code and custom code in sequence.
[0084] Figure 2 A schematic diagram of a process for processing elements based on a business system provided in an embodiment of the present application Figure 1 This embodiment describes in detail the operation process of obtaining a globally unified element format standard. Figure 2 As shown, the method includes:
[0085] S201. Acquire business attributes of a business system in a global system, wherein the global system includes a plurality of business systems having business interactions, and the business attributes are used to indicate a business processing type.
[0086] In this step, the multiple business systems with business interactions refer to business systems corresponding to businesses with shared services or data. For example, in a clothing enterprise, the multiple business systems with business interactions include: clothing manufacturing system, sales system, and warehousing system.
[0087] Furthermore, the business attributes of the business system may be divided according to coarse granularity or fine granularity. For example, when divided in coarse granularity, the business attributes may be sales, reserves, and manpower.
[0088] S202. Generate a globally unified element format standard according to the business attributes of the business system, wherein the element format standard includes: generation rules of ecosystem code, business code, business code and execution code.
[0089] In this step, businesses with different attributes all include: the business owner, i.e., the eco-party, eco-party business, business, and business operation, i.e., the four characteristics of execution. The element format standard used to unify the element format and identification needs to include the code generation rules of the above four characteristics, i.e., the generation rules of the eco-party code, business format code, business code, and execution code. According to the generation rules of the eco-party code, business format code, business code, and execution code.
[0090] Furthermore, due to the wide variety of business types of enterprises, it is impossible for business systems with different attributes to use a unified code generation rule to cover all businesses. Therefore, this embodiment generates corresponding code generation rules according to the attributes of the business system, that is, different global unified element format standards correspond to the attributes of the business system.
[0091] S203: Distribute the element format standard to the multiple business systems so that different business systems use the same element format.
[0092] In this step, the generated element format standard is sent to multiple business systems in the global system, so that when the business system receives a service request, it elementizes the service based on the sent element format standard and generates the actual element code corresponding to the service request. At the same time, the identification and format of the element are unified with other element format identifications of the global system, making interaction between business systems more convenient.
[0093] Among them, this embodiment realizes the allocation of services and elements through open interfaces, and its specific operations are: obtaining an open interface matching each element format standard, distributing the open interface to the multiple business systems, so that different business systems can use the element format standard through the open interface.
[0094] The present application provides a method for processing elements based on a business system, which sets the corresponding element format annotation according to the business system in the global system, issues the element format standard to the global system, and elementizes the services / data of each business based on the element format standard. Through the above method, the element format and label of the global system are unified, avoiding the problems of breakpoints between data elements of different businesses and different scenarios, different identities of unified elements, and poor identification between related elements.
[0095] Figure 3 A schematic diagram of a process for processing elements based on a business system provided in an embodiment of the present application Figure 2 This embodiment describes in detail the operation flow of generating a globally unified element format standard according to the unified rules of target elements. Figure 3 As shown, the method includes:
[0096] S301. According to the business attributes, obtain a unified rule of target elements corresponding to the business attributes; different business attributes correspond to different unified rules of elements.
[0097] In this step, after obtaining the target element unified rules corresponding to the business attributes according to the business attributes, the element format standard is obtained according to the target element unified rules. Different attributes of the business system correspond to different target element unified rules, so the element format standard obtained based on the target element unified rules is also different.
[0098] S302. According to the unified rule of the target element, obtain the header element format standard, the header element format standard includes the preset code bit number of each element and the code generation rule of each element, the header element format standard is used to generate the ecosystem party code, business code, business code and execution code; wherein each element corresponds to its own preset code bit number.
[0099] In this step, the element code corresponding to the service includes two parts: the header element code and the rear element code. It is necessary to obtain the header element format standard and the rear element format standard according to the unified rules of the target element.
[0100] Furthermore, the header element code is generated based on the header element format standard, namely: eco-party code, business code, business code and execution code. The header element format standard includes: the preset code digits of each element and the code generation rules of each element. The preset code digits of the element are determined by the element type, for example: the business code is 8 digits and the eco-party code is 16 digits.
[0101] Specifically, the preset code digits of each element in the element format standards corresponding to different business attributes are the same, which means that different business attributes affect the code generation rules of each element of the element format standards. In other words, in business systems with different business attributes, each element code is the same, but its actual meaning may not be the same. For example: in a business system with sales attributes, its business code 00000011 is men's clothing. In a business system with human resources attributes, the meaning of business code 00000011 can be leave.
[0102] S303. According to the unified rule of the target element, the format standard of the rear element is obtained, and the format standard of the rear element includes the preset code bit number of each rear element and the code generation rule of the rear element. The format standard of the rear element is used to generate an identification extension code, a reserved code and a custom code. According to the header element format standard and the rear element format standard, a global unified element format standard is generated.
[0103] In this step, the rear element code is generated based on the rear element format standard, namely: identification extension code, reserved code and custom code. Among them, the rear element format standard includes: the preset code digits of the identification extension code, reserved code and custom code, and the code generation rules of the identification extension code, reserved code and custom code. The code generation rules are consistent with the above description and will not be described in detail here.
[0104] The present application provides an element processing method based on a business system, which obtains unified rules for target elements according to the business attributes of the business system, and obtains the header element format standard and the rear element format standard based on the unified rules, wherein the element format standard includes: the preset number of code bits for each element and the code generation rule for each element. And based on the header element format standard and the rear element format standard, a globally unified element format standard is generated. Through the above method, the element format and label of the global system are unified, avoiding problems such as breakpoints between data elements of different businesses and different scenarios, different identities of unified elements, and poor identification between related elements.
[0105] Figure 4 A schematic diagram of a process for processing elements based on a business system provided in an embodiment of the present application Figure 3 This embodiment describes in detail the operation flow when the second service system providing the service receives a service request. Figure 4 As shown, the method includes:
[0106] S401. Receive a service request sent by a first business system, where the service request is used to request a service from a second business system, so that the service request arrives at the second business system in a balanced manner.
[0107] In this step, the first business system is the service demander, and the second business system is the service provider. When receiving a service request sent by the first business system, in order to ensure that the service request can reach the second business system in a balanced manner, an additional management and control configuration center is required to implement the operation of ensuring that the service request can reach the second business system in a balanced manner.
[0108] S402. Determine whether the first business system is in a whitelist, where the whitelist includes multiple business systems included in the global system. If the first business system is in the whitelist, and obtain access rights to the first business system, determine whether the first business system can access the second business system based on the access rights.
[0109] In this step, in terms of service access to the first business system, suspicious access and abnormal interaction may occur. To avoid the above problems, after receiving the service request from the first business system, it is determined whether the first business system is in the access whitelist, which includes multiple business systems in the global system. If the first business system is in the access whitelist, the access rights of the first business system are obtained, and the access rights are used to indicate the second business system that the first business system can access. The service request is sent to the second business system that the first business system can access.
[0110] S403: Perform route balancing processing according to the load of the second business system, and forward the service request to the second business system, so that the service request arrives at the second business system in a balanced manner.
[0111] In this step, if the service access of the first business system has a high burst volume, it is necessary to maintain the high-availability load balancing capability of the service provider, that is, the high-availability load balancing capability of the second business system, through the management and control configuration center.
[0112] Among them, load balancing refers to balancing the load and distributing it to multiple operation units for operation. The load in this embodiment refers to the service request of the first business system. The specific operation can be: obtaining the load of the second business system, and adjusting the process of the service request according to the load of the second business system, so that the service request reaches the second business system in a balanced manner.
[0113] In a possible implementation, the access frequency of the first business system is obtained, and access restrictions are imposed on the first property system according to the access frequency of the first business system. That is, when the access frequency of the first business system exceeds the access threshold, the number of accesses to the first business system is restricted; when the access frequency of the first business system is less than the access threshold, normal access is allowed, and only routing balancing is performed on the service requests of the first business system.
[0114] Optionally, load balancing includes software load balancing and hardware load balancing. The hardware load balancing solution is to install a load balancing device directly between the server and the external network. This device is usually called a load balancer. Since the dedicated device completes a dedicated task and is independent of the operating system, the overall performance is greatly improved. In addition, with a variety of load balancing strategies and intelligent traffic management, the best load balancing requirements can be achieved.
[0115] Furthermore, in addition to the deployment of routing load balancing, load balancing can also be deployed in bridging mode and service direct return mode. Among them, the deployment of routing load balancing is to set the server's gateway to the LAN port address of the load balancing and to deploy a different logical network from the WAN port.
[0116] The present application provides a method for processing elements based on business systems. When a service request is received from a first business system, if the first business system is on the whitelist, the second business system corresponding to the first business system is obtained, and routing balancing is performed according to the load of the second business system, and the request is forwarded to the second business system at the same time. Through the above method, it is ensured that the second business system providing the service capability has balanced service access, balanced traffic distribution, and stable service guarantee capabilities.
[0117] Figure 5This is a schematic diagram of the structure of a business system-based element processing control device provided in an embodiment of the present application. Figure 5 As shown, it includes: an acquisition module 501, a generation module 502 and a distribution module 503, wherein:
[0118] The acquisition module 501 is used to acquire the business attributes of a business system in a global system, wherein the global system includes a plurality of business systems having business interactions;
[0119] The generating module 502 is used to generate a globally unified element format standard according to the business attributes of the business system;
[0120] The distribution module 503 is used to distribute the element format standard to the multiple business systems so that different business systems use the same element format.
[0121] In a possible implementation manner, the generating module 502 is further configured to:
[0122] According to the business attribute, obtaining the target element unified rule corresponding to the business attribute; wherein the business attribute is used to indicate the business processing type, and different business attributes correspond to different element unified rules;
[0123] According to the target element unification rule, a globally unified element format standard is generated.
[0124] In a possible implementation manner, the generating module 502 is further configured to:
[0125] According to the unified rule of the target element, the header element format standard is obtained, the header element format standard includes the preset code digits of each element and the code generation rule of each element, and the header element format standard is used to generate the eco-party code, business code, business code and execution code; wherein each element corresponds to its own preset code digits;
[0126] A globally unified element format standard is generated according to the header element format standard.
[0127] In a possible implementation manner, the generating module 502 is further configured to:
[0128] According to the target element unified rule, a rear element format standard is obtained, wherein the rear element format standard includes a preset code digit number of each rear element and a code generation rule of the rear element, and the rear element format standard is used to generate an identification extension code, a reserved code and a custom code;
[0129] A globally unified element format standard is generated according to the header element format standard and the rear element format standard.
[0130] In a possible implementation manner, the distribution module 503 is further configured to:
[0131] Obtain an open interface that matches each element format standard;
[0132] The open interface is distributed to the plurality of business systems, so that different business systems use the element format standard through the open interface.
[0133] In a possible implementation manner, the distribution module 503 is further configured to:
[0134] Receiving a service request sent by the first business system, wherein the service request is used to request a service from the second business system;
[0135] According to the load of the second business system, route balancing processing is performed, and the service request is forwarded to the second business system, so that the service request arrives at the second business system in a balanced manner.
[0136] In a possible implementation manner, the distribution module 503 is further configured to:
[0137] Determine whether the first business system is in a whitelist, where the whitelist includes multiple business systems included in the global system;
[0138] If it is in the whitelist, and obtains access rights to the first business system;
[0139] It is determined according to the access permission that the first business system can access the second business system.
[0140] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 6 As shown, it includes: at least one processor 601 and a memory 602, wherein:
[0141] The memory 602 is used to store computer-executable instructions;
[0142] The at least one processor 601 is used to execute the computer execution instructions stored in the memory 602, so that the at least one processor 601 executes the technical solution of the aforementioned element processing method based on the business system.
[0143] Among them, at least one processor 601 may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.
[0144] Optionally, in a specific implementation, the processor 601 and the memory 602 are implemented independently, and the processor 601 and the memory 602 can be connected to each other through a bus and communicate with each other. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, etc., but it does not mean that there is only one bus or one type of bus.
[0145] Optionally, in a specific implementation, if the processor 601 and the memory 602 are integrated on a chip, the processor 601 and the memory 602 can communicate through an internal interface.
[0146] The present application also provides a computer storage medium, in which computer execution instructions are stored. When a processor executes the computer execution instructions, the technical solution of the aforementioned element processing method based on the business system is implemented.
[0147] The computer-readable storage medium may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The computer-readable storage medium may be any available medium that can be accessed by a general or special purpose computer.
[0148] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (Application Specific Integrated Circuits, referred to as: ASIC). Of course, the processor and the readable storage medium can also exist as discrete components in the control device of the clothing processing device.
[0149] The division of the units is only a logical function division, and there may be other divisions in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, which may be electrical, mechanical or other forms.
[0150] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0151] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0152] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc., which can store program codes.
[0153] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.
[0154] So far, the technical solution of the present application has been described in conjunction with the preferred embodiments shown in the accompanying drawings. However, it is easy for those skilled in the art to understand that the protection scope of the present application is obviously not limited to these specific embodiments, and the above embodiments are only used to illustrate the technical solution of the present application rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein by equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.
Claims
1. A method for processing elements based on a business system, characterized in that: The method comprises: Acquire business attributes of a business system in a global system, wherein the global system includes a plurality of business systems having business interactions; Generate a globally unified element format standard according to the business attributes of the business system; The element format standard is distributed to the multiple business systems so that different business systems use the same element format.
2. The method according to claim 1, characterized in that Generating a globally unified element format standard according to the business attributes of the business system includes: According to the business attribute, obtaining the target element unified rule corresponding to the business attribute; wherein the business attribute is used to indicate the business processing type, and different business attributes correspond to different element unified rules; According to the target element unification rule, a globally unified element format standard is generated.
3. The method according to claim 2, characterized in that The step of generating a globally unified element format standard according to the target element unified rule includes: According to the unified rule of the target element, the header element format standard is obtained, the header element format standard includes the preset code digits of each element and the code generation rule of each element, and the header element format standard is used to generate the eco-party code, business code, business code and execution code; wherein each element corresponds to its own preset code digits; A globally unified element format standard is generated according to the header element format standard.
4. The method according to claim 3, characterized in that Generating a globally unified element format standard according to the header element format standard includes: According to the target element unified rule, a rear element format standard is obtained, wherein the rear element format standard includes a preset code digit number of each rear element and a code generation rule of the rear element, and the rear element format standard is used to generate an identification extension code, a reserved code and a custom code; A globally unified element format standard is generated according to the header element format standard and the rear element format standard.
5. The method according to claim 1, characterized in that The method further comprises: Obtain an open interface that matches each element format standard; The open interface is distributed to the plurality of business systems, so that different business systems use the element format standard through the open interface.
6. The method according to claim 1, characterized in that The method further comprises: Receiving a service request sent by the first business system, wherein the service request is used to request a service from the second business system; According to the load of the second business system, route balancing processing is performed, and the service request is forwarded to the second business system, so that the service request arrives at the second business system in a balanced manner.
7. The method according to claim 6, characterized in that After receiving the service request sent by the first business system, the method further includes: Determine whether the first business system is in a whitelist, where the whitelist includes multiple business systems included in the global system; If it is in the whitelist, and obtains access rights to the first business system; It is determined according to the access permission that the first business system can access the second business system.
8. A factor processing control device based on a business system, characterized in that: include: Get module, generate module and distribute module, where: The acquisition module is used to acquire the business attributes of the business system in the global system, wherein the global system includes a plurality of business systems with business interactions; The generating module is used to generate a globally unified element format standard according to the business attributes of the business system; The distribution module is used to distribute the element format standard to the multiple business systems so that different business systems use the same element format.
9. An electronic device, characterized in that: include: at least one processor and memory, wherein: The memory is used to store computer-executable instructions; The at least one processor is configured to execute the computer-executable instructions stored in the memory, so that the at least one processor performs the method according to any one of claims 1 to 7.
10. A computer storage medium, characterized in that: The computer storage medium stores computer executable instructions, which are used to implement the method according to any one of claims 1 to 7 when executed by a processor.
