CN111984236B - Component standardization management method and device, computer equipment and readable storage medium - Google Patents
Component standardization management method and device, computer equipment and readable storage medium Download PDFInfo
- Publication number
- CN111984236B CN111984236B CN202010852276.8A CN202010852276A CN111984236B CN 111984236 B CN111984236 B CN 111984236B CN 202010852276 A CN202010852276 A CN 202010852276A CN 111984236 B CN111984236 B CN 111984236B
- Authority
- CN
- China
- Prior art keywords
- component
- standard
- processed
- calling
- thread
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/22—Procedural
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4482—Procedural
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention relates to artificial intelligence, and provides a component standardization management method, a device, a computer device and a readable storage medium, wherein the method comprises the following steps: receiving a to-be-processed component sent by a providing user side and executing a providing side process to construct an interface in the to-be-processed component to obtain a standard component; and receiving a call request sent by an access user terminal and executing an access terminal process, so as to obtain a standard component according to the call request sent by the access user terminal, or assembling the standard component to form a standard module, and establishing communication connection between the standard component or the standard module and the access user terminal. The present invention also relates to blockchain techniques in which information may be stored in blockchain nodes. The invention obtains the standard component for the component to be processed provided by the user side, and obtains the corresponding standard component or standard module according to the call request of the access user side, thereby avoiding the situation of repeated development of the computer system of the access user side.
Description
Technical Field
The present invention relates to the field of development and management technologies of artificial intelligence, and in particular, to a method and apparatus for standardized management of components, a computer device, and a readable storage medium.
Background
Because of the variety of business requirements of each organization, each organization's body typically creates a computer system for addressing its own business requirements to effect automatic execution of business operations in order to address its business requirements.
Generally, the general computer module is called when the business operation is executed, but each mechanism usually writes the respective computer system completely, so that the general module of each computer system is repeatedly developed, and resource waste is caused.
Disclosure of Invention
The invention aims to provide a standardized management method and device for components, computer equipment and a readable storage medium, relates to the field of module management of computer research and development management, and aims to solve the problem that in the prior art, common modules of all computer systems are repeatedly developed and resource waste is caused because all mechanisms usually write respective computer systems completely.
In order to achieve the above object, the present invention provides a component standardization management method, including:
Receiving a to-be-processed component sent by a providing user side and executing a providing side process to construct an interface in the to-be-processed component to obtain a standard component;
And receiving a call request sent by an access user terminal and executing an access terminal process, so as to obtain a standard component according to the call request sent by the access user terminal, or assembling the standard component to form a standard module, and establishing communication connection between the standard component or the standard module and the access user terminal.
In the above scheme, before receiving the to-be-processed component sent by the providing user side and executing the providing side process, the method includes:
Creating a component library, which is used for storing a database of components;
the component library stores the components in a key-value mode, wherein the ids of the components are keys, and the components are values.
In the above solution, the providing end process includes:
Executing a permission providing thread to judge whether the component to be processed is an acceptable component; if yes, calling a standardized thread; if not, returning refused information and ending;
Executing the standardized thread to construct a Restful interface in the component to be processed to obtain a standard component;
and sending the standard components to a preset component library.
In the above solution, the providing authority thread includes:
Extracting a component code of a component to be processed, and judging whether the component code belongs to a preset permission providing list or not; if yes, judging that the component to be processed is authorized; if not, returning refused information and ending; the component codes and records the ID information of the providing user terminal;
Detecting whether the authorized component to be processed can normally operate or not; if yes, judging the component to be processed as an acceptable component; if not, returning the refusal information and ending.
In the above scheme, the access terminal process includes:
executing an access authority thread to judge whether the call request has call authority; if yes, extracting a calling thread; if not, returning refusing calling information;
executing a calling thread to obtain standard components from a component library according to the calling request, and/or assembling the standard components to form a standard module;
Executing a communication thread to establish a communication connection between the obtained standard component or the standard module and the access client.
In the above scheme, the access permission thread includes:
Extracting a calling code of a calling request, and judging whether the calling code belongs to a preset access authority list or not; if yes, judging that the call request has the call authority; if not, returning refused information and ending; and the calling code records the ID information of the access user terminal.
In the above solution, the calling thread includes:
extracting a component ID in a call request, and acquiring a standard component corresponding to the component ID from a component library;
Judging whether the number of the obtained standard components is one; if yes, ending the calling thread; if not, extracting the association relation in the call request, and assembling the standard component according to the association relation to obtain a standard module.
In order to achieve the above object, the present invention also provides a component standardization management apparatus, including:
The providing end management module is used for receiving a to-be-processed component sent by a providing user end and executing a providing end process so as to construct an interface in the to-be-processed component to obtain a standard component;
the access terminal management module is used for receiving a call request sent by the access user terminal and executing an access terminal process so as to obtain a standard component according to the call request sent by the access user terminal or assemble the standard component to form a standard module, and the standard component or the standard module is connected with the access user terminal in a communication way.
To achieve the above object, the present invention also provides a computer device including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the steps of the above component standardization management method are implemented when the processor of the computer device executes the computer program.
To achieve the above object, the present invention also provides a computer-readable storage medium including a storage data area storing data created according to use of blockchain nodes and a storage program area storing a computer program, wherein the computer program stored in the storage medium implements the steps of the component standardization management method when executed by a processor.
The component standardization management method, the device, the computer equipment and the readable storage medium provided by the invention can obtain the standard component for the component to be processed provided by the user side, and obtain the corresponding standard component or standard module according to the call request of the access user side, so that the access user side can obtain the universal computer module, namely: the standard component or the standard module avoids the repeated development of the computer system accessed to the user side, thereby avoiding the waste of computer resources and development resources.
Drawings
FIG. 1 is a flowchart of a component standardization management method according to an embodiment of the present invention;
FIG. 2 schematically illustrates an environmental application diagram of a component standardization management method according to a second embodiment of the present application;
FIG. 3 is a flowchart illustrating a method for standardizing management of components according to a second embodiment of the present invention;
FIG. 4 is a flowchart of a providing end process of a second embodiment of the component standardization management method according to the present invention;
FIG. 5 is a flowchart of a method for providing a thread of rights in a second embodiment of a component standardization management method of the present invention;
FIG. 6 is a flowchart of an access end process according to a second embodiment of the component standardization management method of the present invention;
FIG. 7 is a flowchart of a method for managing access rights in a component standardization process according to a second embodiment of the present invention;
FIG. 8 is a flowchart of a call thread for a second embodiment of a component normalization management method according to the present invention;
FIG. 9 is a schematic diagram of a program module of a third embodiment of the component standardization management apparatus according to the present invention;
fig. 10 is a schematic diagram of a hardware structure of a computer device in a fourth embodiment of the computer device according to the present invention.
Reference numerals:
1. component standardization management device 2, server 3, providing user terminal 4, accessing user terminal
5. Computer device 11, creation module 12, provider management module
13. Access terminal management module 51, memory 52, and processor
Detailed Description
The present invention will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The component standardized management method, the device, the computer equipment and the readable storage medium are suitable for the module management field related to computer research and development management, and provide a component standardized management method based on a creation module, a provider management module and an access management module. The invention obtains a standard component by receiving a component to be processed sent by a providing user side and executing a providing side process so as to construct an interface in the component to be processed; and receiving a call request sent by an access user terminal and executing an access terminal process, so as to obtain a standard component according to the call request sent by the access user terminal, or assembling the standard component to form a standard module, and establishing communication connection between the standard component or the standard module and the access user terminal.
Embodiment one:
referring to fig. 1, a component standardization management method of the present embodiment includes:
s102: receiving a to-be-processed component sent by a providing user side and executing a providing side process to construct an interface in the to-be-processed component to obtain a standard component;
S103: and receiving a call request sent by an access user terminal and executing an access terminal process, so as to obtain a standard component according to the call request sent by the access user terminal, or assembling the standard component to form a standard module, and establishing communication connection between the standard component or the standard module and the access user terminal.
In order to enable the access user terminal to smoothly call the standard component, an interface is built in the component to be processed so that the access user terminal can call the standard component, and the complexity of calling the standard component is greatly reduced.
The standard component is called for ensuring the access user terminal with the calling authority, or the standard module formed by assembling a plurality of standard components is called, so that the access user terminal can obtain the reliable standard component or standard module.
Therefore, the application obtains the standard component for the component to be processed provided by the providing user terminal and obtains the corresponding standard component or standard module according to the call request of the accessing user terminal, so that the accessing user terminal can obtain the universal computer module, namely: the standard component or the standard module avoids the repeated development of the computer equipment accessed to the user side, thereby avoiding the waste of computer resources and development resources.
Embodiment two:
the present embodiment is a specific application scenario of the first embodiment, and by this embodiment, the method provided by the present invention can be more clearly and specifically described.
The method provided in this embodiment is specifically described below by taking a server running a component standardization management method as an example, where a standard component is obtained by constructing an interface in a component to be processed that is sent by a providing user, and the standard component is obtained according to a call request sent by an accessing user. It should be noted that the present embodiment is only exemplary, and does not limit the scope of protection of the embodiment of the present invention.
Fig. 2 schematically illustrates an environmental application diagram of a component standardization management method according to a second embodiment of the present application.
In an exemplary embodiment, the server 2 in which the component standardization management method is located provides the client 3 and the access client 4 through a network, respectively, and the server 2 may provide services through one or more networks, where the networks may include various network devices, such as routers, switches, multiplexers, hubs, modems, bridges, repeaters, firewalls, proxy devices, and/or the like. The network 3 may include physical links such as coaxial cable links, twisted pair cable links, fiber optic links, combinations thereof, and/or the like. The network may include wireless links, such as cellular links, satellite links, wi-Fi links, and/or the like; the providing client 3 and the accessing client 4 may be computer devices such as smart phones, tablet computers, notebook computers, desktop computers, and the like.
Fig. 3 is a flowchart of a specific method of component standardization management method according to an embodiment of the present invention, where the method specifically includes steps S201 to S203.
S201: a component library is created.
In this step, the component library is a database for storing components, and in this embodiment, the component library stores components in a key-value manner, where an id of the component is a key, and the component is a value.
S202: and receiving a to-be-processed component sent by the providing user side, and executing a providing side process to construct an interface in the to-be-processed component to obtain a standard component.
In order to enable the access user terminal to smoothly call the standard component, an interface is built in the component to be processed so that the access user terminal can call the standard component, and the complexity of calling the standard component is greatly reduced.
And the communication connection established with the providing user terminal through TCP or UDP receives the component to be processed.
It should be noted that TCP (Transmission Control Protocol transmission control protocol) is a connection-oriented, reliable, byte-stream-based transport layer communication protocol, defined by IETF RFC 793. In the simplified OSI model of computer networks, it performs the functions specified by the transport layer four, the User Datagram Protocol (UDP) being another important transport protocol within the same layer. In the internet protocol suite (Internet protocol suite), the TCP layer is an intermediate layer that sits above the IP layer and below the application layer. Reliable, pipe-like connections are often required between application layers of different hosts, but the IP layer does not provide such a streaming mechanism, but rather unreliable packet switching. UDP is a short term for User Datagram Protocol, chinese name is user datagram protocol, is a connectionless transport layer protocol in OSI (Open System Interconnection, open systems interconnection) reference model, provides a transaction-oriented simple unreliable information transfer service, and IETF RFC 768 is a formal specification for UDP.
In a preferred embodiment, referring to fig. 4, the provider process includes:
A1: executing a permission providing thread to judge whether the component to be processed is an acceptable component; if yes, calling a standardized thread; if not, returning the refusal information and ending.
To ensure that the received component to be processed belongs to an acceptable component which can be processed and operated, therefore, whether the component to be processed is an acceptable component is judged by providing a permission thread, namely: comparing the to-be-processed component with a preset provided authority list (which can be regarded as a white list) to judge whether the to-be-processed component is a processable component or not; and detecting whether the component to be processed can normally operate or not, judging whether the component to be processed is an operable component, and judging the component to be processed as an acceptable component if the component to be processed has the characteristics of being processed and operable at the same time.
Specifically, referring to fig. 5, the providing authority thread includes:
A11: extracting a component code of a component to be processed, and judging whether the component code belongs to a preset permission providing list or not; the component codes and records the ID information of the providing user terminal;
a12: if yes, judging that the component to be processed is authorized;
a13: if not, returning refused information and ending;
A14: detecting whether the authorized component to be processed can normally operate or not;
a15: if yes, judging the component to be processed as an acceptable component;
a16: if not, returning the refusal information and ending.
A2: and executing the standardized thread to construct a Restful interface in the component to be processed to obtain a standard component.
In this step, the restful interface (presentation layer state transition) is an API interface of a design style and development mode of a network application program, which may use XML format definition or JSON format definition based on HTTP, in this embodiment, a server application builds a restful interface based on an HTTP standard and the component to be processed in the specification, and the interface may be accessed by any user end, which is suitable for a scenario where a mobile internet manufacturer is used as a service enabling interface.
It should be noted that, since the restful interface architecture style specifies that the meta operations of the data, that is, the CRUD (create, read, update and delete), that is, the add-delete-modify operations of the data, correspond to the HTTP methods respectively: the GET is used for acquiring resources, the POST is used for newly building resources (also used for updating the resources), the PUT is used for updating the resources, and the DELETE is used for deleting the resources, so that the interface of data operation is unified, and the work of adding, deleting, checking, modifying and acquiring the resources of the data can be completed only by an HTTP method; therefore, the restful interface only defines resource operation and does not participate in business logic, so that any user side can directly use http to do not need any other message protocol (such as get/post/put/delete is CRUD operation), and the restful interface has self-interpretation property and simple data description (generally uses xml and json to make data exchange), so that context can be not considered when the restful interface is called (resource access and operation) and the current state is not considered, and the complexity is greatly reduced.
A3: and sending the standard components to a preset component library.
The standard components are stored in the component library, so that the access user side can quickly call the standard components.
S203: and receiving a call request sent by an access user terminal and executing an access terminal process, so as to obtain a standard component according to the call request sent by the access user terminal, or assembling the standard component to form a standard module, and establishing communication connection between the standard component or the standard module and the access user terminal.
The standard component is called for ensuring the access user terminal with the calling authority, or the standard module formed by assembling a plurality of standard components is called, so that the access user terminal can obtain the reliable standard component or standard module.
In a preferred embodiment, referring to fig. 6, the access terminal process includes:
b1: executing an access authority thread to judge whether the call request has call authority; if yes, extracting a calling thread; if not, returning refusing calling information.
In order to ensure that the received call request has the call authority, the user side without the call authority is prevented from calling the component, so that the safety of the component and the server where the component is located is ensured; the step judges whether the call request has authority or not through the access authority thread, namely: the call request is compared with a preset access permission list (which may be considered as a white list) to ensure that the call request for executing the call thread is authorized.
Specifically, referring to fig. 7, the access permission thread includes:
B11: extracting a calling code of a calling request, and judging whether the calling code belongs to a preset access authority list or not; the calling code records ID information of the access user terminal;
b12: if yes, judging that the call request has the call authority;
b13: if not, returning the refusal information and ending.
B2: executing a calling thread to obtain standard components from a component library according to the calling request, and/or assembling the standard components to form a standard module.
In order to avoid the access user side from reprocessing the obtained standard component and obtaining a module for completing complex tasks, the access user side is caused to use the standard component in a complicated and complex manner, the standard component can be directly called through a calling thread in the step, and/or the standard module capable of being directly called is formed through assembling the standard component, so that convenience is provided for the access user side to use the standard component.
Specifically, referring to fig. 8, the calling thread includes:
b21: extracting a component ID in a call request, and acquiring a standard component corresponding to the component ID from a component library;
b22: judging whether the number of the obtained standard components is one;
B23: if yes, ending the calling thread;
B24: if not, extracting the association relation in the call request, and assembling the standard component according to the association relation to obtain a standard module.
It should be noted that, the association relationship describes a call relationship between components corresponding to the component ID in the call request.
Illustratively, the component ID of the call request is extracted, such as: a005; and extracting the standard component corresponding to A005, and judging the component ID of the call request as one, so that the call thread is directly ended.
Illustratively, the component ID of the call request is extracted, such as: a005, a009, B010; extracting standard components corresponding to A005, A009 and B010, judging that the component ID of the call request is not one, and extracting the association relation in the call request;
The association relationship is assumed to be:
M1: calling A005 to operate the data to be processed to obtain first data;
m2: b010 operation is called to obtain first data and second data;
m3: and calling A009 to operate on the second data to obtain an operation result.
And then, assembling the standard components corresponding to the A005, the A009 and the B010 according to the association relation to obtain the standard modules of the standard components corresponding to the A005, the standard components corresponding to the B010 and the standard components corresponding to the A009 in the calling sequence.
B3: executing a communication thread to establish a communication connection between the obtained standard component or the standard module and the access client.
In this step, the standard component or the standard module is connected with the communication established by the access user terminal through TCP or UDP. The access user end only needs to send data to be processed to the server through the communication connection and call the standard component or the standard module to operate the data to obtain an operation result, so that the standard component and the standard module do not need to be sent to the access user end, the data transmission pressure of the communication connection is greatly reduced, and the safety of the standard component and the standard module is guaranteed.
It should be noted that TCP (Transmission Control Protocol transmission control protocol) is a connection-oriented, reliable, byte-stream-based transport layer communication protocol, defined by IETF RFC 793. In the simplified OSI model of computer networks, it performs the functions specified by the transport layer four, the User Datagram Protocol (UDP) being another important transport protocol within the same layer. In the internet protocol suite (Internet protocol suite), the TCP layer is an intermediate layer that sits above the IP layer and below the application layer. Reliable, pipe-like connections are often required between application layers of different hosts, but the IP layer does not provide such a streaming mechanism, but rather unreliable packet switching. UDP is a short term for User Datagram Protocol, chinese name is user datagram protocol, is a connectionless transport layer protocol in OSI (Open System Interconnection, open systems interconnection) reference model, provides a transaction-oriented simple unreliable information transfer service, and IETF RFC 768 is a formal specification for UDP.
Embodiment III:
referring to fig. 9, a device 1 for component standardization management of the present embodiment includes:
The provider management module 12 is configured to receive a component to be processed sent by a provider user and execute a provider process, so as to construct an interface in the component to be processed to obtain a standard component;
The access terminal management module 13 is configured to receive a call request sent by an access user terminal and execute an access terminal process, so as to obtain a standard component according to the call request sent by the access user terminal, or assemble the standard component to form a standard module, and establish a communication connection between the standard component or the standard module and the access user terminal.
Optionally, the component standardization management device 1 further includes:
the creation module 11 is configured to create a component library, where the component library is a database for storing components, and the component library stores the components in a key-value manner, where an id of the component is a key, and the component is a value.
The technical scheme is based on the development field of research and development management, and a standard component is obtained by constructing an interface in the component to be processed; and acquiring a standard component according to a call request sent by an access user terminal, or assembling the standard component to form a standard module, and establishing communication connection between the standard component or the standard module and the access user terminal to obtain a module management tool for assisting in developing components and modules.
Embodiment four:
In order to achieve the above objective, the present invention further provides a computer device 5, where the components of the component standardization management apparatus 1 of the third embodiment may be dispersed in different computer devices, and the computer device 5 may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack-mounted server, a blade server, a tower server, or a rack-mounted server (including a stand-alone server or a server cluster formed by multiple servers), etc. The computer device 5 of the present embodiment includes at least, but is not limited to: a memory 51, a processor 52, which may be communicatively coupled to each other via a system bus, as shown in fig. 10. It should be noted that fig. 10 only shows a computer device with components-but it should be understood that not all of the illustrated components are required to be implemented and that more or fewer components may be implemented instead.
In the present embodiment, the memory 51 (i.e., readable storage medium) includes a flash memory, a hard disk, a multimedia card, a card memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the memory 51 may be an internal storage unit of a computer device, such as a hard disk or memory of the computer device. In other embodiments, the memory 51 may also be an external storage device of a computer device, such as a plug-in hard disk, a smart memory card (SMART MEDIA CARD, SMC), a Secure Digital (SD) card, a flash memory card (FLASH CARD), etc. that are provided on the computer device. Of course, the memory 51 may also include both internal storage units of the computer device and external storage devices. In this embodiment, the memory 51 is typically used to store an operating system installed in a computer device and various types of application software, such as program codes of the component standardization management apparatus of the third embodiment. Further, the memory 51 may also be used to temporarily store various types of data that have been output or are to be output.
Processor 52 may be a central processing unit (Central Processing Unit, CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments. The processor 52 is typically used to control the overall operation of the computer device. In the present embodiment, the processor 52 is configured to execute the program code stored in the memory 51 or process data, for example, execute the component standardization management apparatus, to implement the component standardization management methods of the first and second embodiments.
Fifth embodiment:
To achieve the above object, the present invention also provides a computer-readable storage medium including a storage data area storing data created according to use of a blockchain node and a storage program area storing a computer program; the memory program area includes a storage medium such as a flash memory, a hard disk, a multimedia card, a card memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, a server, an App application store, etc., on which a computer program is stored that when executed by the processor 52 performs the corresponding functions. The computer-readable storage medium of the present embodiment is used for storing the component standardization management apparatus, and when executed by the processor 52, implements the component standardization management methods of the first and second embodiments.
Further, the computer-readable storage medium may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created from the use of blockchain nodes, and the like.
The blockchain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm and the like. The blockchain (Blockchain), essentially a de-centralized database, is a string of data blocks that are generated in association using cryptographic methods, each of which contains information from a batch of network transactions for verifying the validity (anti-counterfeit) of its information and generating the next block. The blockchain may include a blockchain underlying platform, a platform product services layer, an application services layer, and the like.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The application is operational with numerous general purpose or special purpose computer system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like. The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.
Claims (6)
1. A component standardization management method, characterized by comprising:
Receiving a to-be-processed component sent by a providing user side and executing a providing side process to construct an interface in the to-be-processed component to obtain a standard component; the communication connection established between the TCP or UDP and the providing user terminal receives a component to be processed;
Receiving a call request sent by an access user terminal and executing an access terminal process, so as to obtain a standard component according to the call request sent by the access user terminal, or assembling the standard component to form a standard module, and establishing communication connection between the standard component or the standard module and the access user terminal; the standard component or the standard module is connected with the communication established by the access user terminal through TCP or UDP;
The providing end process comprises the following steps:
Executing a permission providing thread to judge whether the component to be processed is an acceptable component; if yes, calling a standardized thread; if not, returning refused information and ending;
Executing the standardized thread to construct a Restful interface in the component to be processed to obtain a standard component;
the standard components are sent to a preset component library;
The providing authority thread comprises the following steps:
Extracting a component code of a component to be processed, and judging whether the component code belongs to a preset permission providing list or not; if yes, judging that the component to be processed is authorized; if not, returning refused information and ending; the component codes and records the ID information of the providing user terminal;
Detecting whether the authorized component to be processed can normally operate or not; if yes, judging the component to be processed as an acceptable component; if not, returning refused information and ending;
the access terminal process comprises the following steps:
executing an access authority thread to judge whether the call request has call authority; if yes, extracting a calling thread; if not, returning refusing calling information;
executing a calling thread to obtain standard components from a component library according to the calling request, and/or assembling the standard components to form a standard module;
executing a communication thread to establish communication connection between the obtained standard component or the standard module and the access user terminal;
The calling thread comprises:
extracting a component ID in a call request, and acquiring a standard component corresponding to the component ID from a component library;
Judging whether the number of the obtained standard components is one; if yes, ending the calling thread; if not, extracting the association relation in the call request, and assembling the standard component according to the association relation to obtain a standard module;
The association relation describes the calling relation between the components corresponding to the component ID in the calling request;
The TCP is a connection-oriented, reliable, byte stream based transport layer communication protocol; the UDP is a connectionless transport layer protocol and provides a simple unreliable information transmission service facing to the transaction; the Restful interface is an API interface of a design style and a development mode of a network application program, and is constructed by the components to be processed based on an http standard.
2. The component standardization management method according to claim 1, characterized by comprising, before receiving a component to be processed sent by a providing user side and executing a providing side process:
Creating a component library, which is used for storing a database of components;
the component library stores the components in a key-value mode, wherein the ids of the components are keys, and the components are values.
3. The component standardization management method of claim 1, characterized in that the access authority thread comprises:
Extracting a calling code of a calling request, and judging whether the calling code belongs to a preset access authority list or not; if yes, judging that the call request has the call authority; if not, returning refused information and ending; and the calling code records the ID information of the access user terminal.
4. A component standardization management apparatus, characterized by comprising:
The providing end management module is used for receiving a to-be-processed component sent by a providing user end and executing a providing end process so as to construct an interface in the to-be-processed component to obtain a standard component; the communication connection established between the TCP or UDP and the providing user terminal receives a component to be processed;
The access terminal management module is used for receiving a call request sent by an access user terminal and executing an access terminal process so as to obtain a standard component according to the call request sent by the access user terminal or assemble the standard component to form a standard module, and the standard component or the standard module is connected with the access user terminal in a communication way; the standard component or the standard module is connected with the communication established by the access user terminal through TCP or UDP;
The providing end process comprises the following steps: executing a permission providing thread to judge whether the component to be processed is an acceptable component; if yes, calling a standardized thread; if not, returning refused information and ending; executing the standardized thread to construct a Restful interface in the component to be processed to obtain a standard component; the standard components are sent to a preset component library; the providing authority thread comprises the following steps: extracting a component code of a component to be processed, and judging whether the component code belongs to a preset permission providing list or not; if yes, judging that the component to be processed is authorized; if not, returning refused information and ending; the component codes and records the ID information of the providing user terminal; detecting whether the authorized component to be processed can normally operate or not; if yes, judging the component to be processed as an acceptable component; if not, returning refused information and ending; the access terminal process comprises the following steps: executing an access authority thread to judge whether the call request has call authority; if yes, extracting a calling thread; if not, returning refusing calling information; executing a calling thread to obtain standard components from a component library according to the calling request, and/or assembling the standard components to form a standard module; executing a communication thread to establish communication connection between the obtained standard component or the standard module and the access user terminal; the calling thread comprises: extracting a component ID in a call request, and acquiring a standard component corresponding to the component ID from a component library; judging whether the number of the obtained standard components is one; if yes, ending the calling thread; if not, extracting the association relation in the call request, and assembling the standard component according to the association relation to obtain a standard module; the association relation describes the calling relation between the components corresponding to the component ID in the calling request; the TCP is a connection-oriented, reliable, byte stream based transport layer communication protocol; the UDP is a connectionless transport layer protocol and provides a simple unreliable information transmission service facing to the transaction; the Restful interface is an API interface of a design style and a development mode of a network application program, and is constructed by the components to be processed based on an http standard.
5. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the component standardization management method according to any one of claims 1 to 3 are implemented by the processor of the computer device when the computer program is executed.
6. A computer readable storage medium comprising a storage data area storing data created according to the use of blockchain nodes and a storage program area storing a computer program, characterized in that the computer program stored in the storage medium implements the steps of the component standardization management method of any one of claims 1 to 3 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010852276.8A CN111984236B (en) | 2020-08-21 | 2020-08-21 | Component standardization management method and device, computer equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010852276.8A CN111984236B (en) | 2020-08-21 | 2020-08-21 | Component standardization management method and device, computer equipment and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111984236A CN111984236A (en) | 2020-11-24 |
| CN111984236B true CN111984236B (en) | 2024-07-05 |
Family
ID=73442895
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010852276.8A Active CN111984236B (en) | 2020-08-21 | 2020-08-21 | Component standardization management method and device, computer equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111984236B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113934470A (en) * | 2021-10-19 | 2022-01-14 | 京东科技控股股份有限公司 | Method for constructing and using federated learning framework and related equipment |
| CN115826521B (en) * | 2022-11-22 | 2023-10-20 | 广州致远仪器有限公司 | Production process control method and device, electronic equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110324376A (en) * | 2018-03-30 | 2019-10-11 | 江苏融成嘉益信息科技有限公司 | A kind of business micro services Component Gallery |
| CN110995847A (en) * | 2019-12-10 | 2020-04-10 | 南京新贝金服科技有限公司 | Insurance service bus implementation method and system applied to multi-system communication |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7065549B2 (en) * | 2002-03-29 | 2006-06-20 | Illinois Institute Of Technology | Communication and process migration protocols for distributed heterogeneous computing |
| CN109710214A (en) * | 2018-08-17 | 2019-05-03 | 深圳壹账通智能科技有限公司 | Construction method, device, terminal device and the storage medium of electronic signature software |
| CN109408232B (en) * | 2018-10-17 | 2020-08-14 | 山东易通发展集团有限公司 | A Componentized Bus Call Execution System Based on Transaction Process |
| CN111324465A (en) * | 2020-02-19 | 2020-06-23 | 深圳壹账通智能科技有限公司 | Multi-thread calling method, device, computer system and storage medium |
| CN111142855B (en) * | 2020-04-03 | 2020-07-24 | 中邮消费金融有限公司 | Software development method and software development system |
-
2020
- 2020-08-21 CN CN202010852276.8A patent/CN111984236B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110324376A (en) * | 2018-03-30 | 2019-10-11 | 江苏融成嘉益信息科技有限公司 | A kind of business micro services Component Gallery |
| CN110995847A (en) * | 2019-12-10 | 2020-04-10 | 南京新贝金服科技有限公司 | Insurance service bus implementation method and system applied to multi-system communication |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111984236A (en) | 2020-11-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111343168B (en) | Identity authentication method and device, computer equipment and readable storage medium | |
| CN111294347B (en) | Safety management method and system for industrial control equipment | |
| CN111988337A (en) | Rights management method and system | |
| CN114124929A (en) | Cross-network data processing method and device | |
| CN114449047B (en) | File data processing method and device | |
| CN113190287B (en) | External device docking method, device, computer equipment and readable storage medium | |
| CN111831365A (en) | Interface route forwarding method, system, computer equipment and readable storage medium | |
| CN110213250B (en) | Data processing method and terminal equipment | |
| CN114153626A (en) | Method and device for abstracting service integration process and computer equipment | |
| CN111984236B (en) | Component standardization management method and device, computer equipment and readable storage medium | |
| CN111367923A (en) | Data processing method, data processing device, node equipment and storage medium | |
| CN115113898A (en) | Dynamic update method, device, computer equipment and storage medium of micro-application | |
| CN114238927A (en) | Business system login method, system, device, computer equipment and storage medium | |
| CN111314355B (en) | Authentication method, device, equipment and medium of VPN (virtual private network) server | |
| CN114567678A (en) | Resource calling method and device of cloud security service and electronic equipment | |
| CN110650014B (en) | Signature authentication method, system, equipment and storage medium based on hessian protocol | |
| US20250117315A1 (en) | Multicloud test automation framework | |
| CN112559027A (en) | Method, system, device and readable storage medium for creating and managing functional components | |
| CN111310141A (en) | Authentication management method, device, computer equipment and storage medium | |
| CN114745185B (en) | Cluster access method and device | |
| CN114640522A (en) | Processing method, device, equipment and storage medium of firewall security policy | |
| CN108718339A (en) | Data processing method, device and server | |
| CN117176708A (en) | Data processing method and related device | |
| CN114362960B (en) | Resource account data supervision method and device, computer equipment and medium | |
| CN117479172A (en) | Privacy number binding method, device, electronic equipment and storage 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |