CN112596932A - Service registration and interception method and device, electronic equipment and readable storage medium - Google Patents

Abstract

The invention relates to data processing, and discloses a service registration and interception method, comprising: obtaining an annotation definition code; The list of method names to be intercepted generates the service definition code, and the service definition code includes the annotation identifier; fill the annotation definition code and service definition code into the main program code corresponding to the target application, scan the annotation identifier in the main program code, and treat the registration service. Perform registration operations and binding operations with the interceptor to be registered; perform interception processing on the invocation request based on the name of one or more services to be invoked and the name of the method to be invoked carried in the invocation request. The present invention also provides a service registration and interception device, an electronic device and a readable storage medium. The invention improves the expansibility and maintainability of the code, and realizes fine-grained interception.

Description

Service registration and interception method, apparatus, electronic device and readable storage medium

technical field

The present invention relates to the field of data processing, and in particular, to a service registration and interception method, device, electronic device and readable storage medium.

Background technique

With the development of science and technology, communication is more and more widely used in people's life. The gRPC (Google RemoteProcedure Call, Google Remote Procedure Call) framework is a basic network communication component. The communication process involves service registration, interceptor registration, and binding of services and interceptors. The existing gRPC framework requires Write the corresponding registration code and binding code one by one, which is difficult to expand. If there are many services to be registered, the code will be too bloated and difficult to maintain, and the existing gRPC framework will intercept all methods under the service and cannot intercept the specified ones. method, which cannot achieve fine-grained interception. Therefore, there is an urgent need for a service registration and interception method to improve the scalability and maintainability of the code, and to achieve fine-grained interception.

SUMMARY OF THE INVENTION

In view of the above, it is necessary to provide a service registration and interception method, which aims to improve the scalability and maintainability of the code, and realize fine-grained interception.

The service registration and interception method provided by the present invention includes:

Parse the service registration request for the target application sent by the user based on the client, and obtain the name of the service to be registered carried in the service registration request, the name of the interceptor to be registered, the binding relationship between the service to be registered and the interceptor to be registered, and A list of method names to be intercepted of the to-be-registered service;

Obtain a predetermined annotation definition code from the database, based on the name of the service to be registered, the name of the interceptor to be registered, the binding relationship between the service to be registered and the interceptor to be registered, and the name of the method to be intercepted of the service to be registered The list generates service definition code, the service definition code includes an annotation identifier;

Fill in the main program code corresponding to the target application program with the annotation definition code and the service definition code, scan the annotation identifier in the main program code, and perform a registration operation on the to-be-registered service and the to-be-registered interceptor. bind operation;

Monitor the call request for the target application in real time, obtain one or more service names to be called and the name of the method to be called carried in the call request, and based on the name of the service to be called and the name of the method to be called Call request to perform interception processing.

Optionally, the service registration request further includes a transaction to be intercepted, the name of the service to be registered, the name of the interceptor to be registered, the binding relationship between the service to be registered and the interceptor to be registered, and the to-be-registered interceptor. The service definition code for generating a list of method names to be intercepted for a service includes:

generating a first definition code based on the name of the interceptor to be registered and the transaction to be intercepted;

Generate a second definition code based on the name of the service to be registered, the binding relationship between the service to be registered and the interceptor to be registered, and the list of method names to be intercepted of the service to be registered;

The first definition code and the second definition code are combined to obtain the service definition code.

Optionally, performing a registration operation and a binding operation on the to-be-registered service and the to-be-registered interceptor by scanning the annotation identifier in the main program code, including:

Scan the program segment carrying the annotation identifier in the main program code, and perform a correctness check on the program segment;

When the verification is passed, interception data is generated based on the program segment, and a registration operation and a binding operation are performed on the service to be registered and the interceptor to be registered based on the interception data.

Optionally, after performing the correctness check on the program segment, the method further includes:

If the verification fails, the program segment is identified, and early warning information is sent to the client.

Optionally, performing interception processing on the invocation request based on the name of the service to be invoked and the name of the method to be invoked includes:

Determine whether each service to be called is bound with an interceptor;

When judging that a specified service to be called is bound with an interceptor, it is judged whether the method to be called of the specified service to be called exists in the list of method names to be intercepted of the specified service to be called;

When it is determined that it exists in the list of method names to be intercepted for the designated service to be invoked, an interception process is performed on the invocation request.

Optionally, after judging whether each service to be called is bound with an interceptor, the method further includes:

If it is determined that each service to be called is not bound with an interceptor or the method to be called of the specified service to be called does not exist in the list of method names to be intercepted for the specified service to be called, execute the call corresponding to the call request operate.

In order to solve the above problems, the present invention also provides a service registration and interception device, the device includes:

The parsing module is used to parse the service registration request for the target application sent by the user based on the client, and obtain the name of the service to be registered, the name of the interceptor to be registered, the service to be registered and the interceptor to be registered carried in the service registration request. The binding relationship and the list of method names to be intercepted for the service to be registered;

The generation module is used to obtain the predetermined annotation definition code from the database, based on the name of the service to be registered, the name of the interceptor to be registered, the binding relationship between the service to be registered and the interceptor to be registered, and the service to be registered. The list of method names to be intercepted generates a service definition code, and the service definition code includes an annotation identifier;

A scanning module is used to fill the annotation definition code and service definition code into the main program code corresponding to the target application, scan the annotation identifier in the main program code, and intercept the service to be registered and the service to be registered. The device performs registration and binding operations;

The interception module is used to monitor the call request for the target application in real time, obtain one or more service names to be called and the name of the method to be called carried in the call request, and based on the name of the service to be called and the name of the method to be called The method name performs interception processing on the invocation request.

Optionally, performing a registration operation and a binding operation on the to-be-registered service and the to-be-registered interceptor by scanning the annotation identifier in the main program code, including:

Scan the program segment carrying the annotation identifier in the main program code, and perform a correctness check on the program segment;

When the verification is passed, interception data is generated based on the program segment, and a registration operation and a binding operation are performed on the service to be registered and the interceptor to be registered based on the interception data.

In order to solve the above problems, the present invention also provides an electronic device, the electronic device includes:

at least one processor; and,

a memory communicatively coupled to the at least one processor; wherein,

The memory stores a service registration and interception program executable by the at least one processor, and the service registration and interception program is executed by the at least one processor to enable the at least one processor to perform the above-mentioned service registration and interception method.

In order to solve the above problems, the present invention also provides a computer-readable storage medium, where a service registration and interception program is stored on the computer-readable storage medium, and the service registration and interception program can be executed by one or more processors, In order to realize the above service registration and interception methods.

Compared with the prior art, the present invention first obtains the annotation definition code, and generates a service based on the name of the service to be registered, the name of the interceptor to be registered, the binding relationship between the service to be registered and the interceptor to be registered, and the name list of the method to be intercepted of the service to be registered. Definition code, the service definition code includes the annotation identifier; then, fill in the annotation definition code and the service definition code into the main program code corresponding to the target application, scan the annotation identifier in the main program code, and execute the service to be registered and the interceptor to be registered. Registration operation and binding operation; finally, intercept the call request based on the name of the service to be called and the name of the method to be called carried in the call request. This solution only needs to mark the service definition code corresponding to the service to be registered to realize the registration of the service, the registration of the interceptor, and the binding of the service and the interceptor, which improves the scalability and maintainability of the code; By adding a list of method names to be intercepted for a service in the service definition code, the technical problem that the existing gRPC can only intercept all methods under the service but not the specified methods under the service is solved, and refined interception is realized. Therefore, the present invention improves the expansibility and maintainability of the code, and realizes fine-grained interception.

Description of drawings

1 is a schematic flowchart of a service registration and interception method provided by an embodiment of the present invention;

2 is a schematic block diagram of a service registration and interception apparatus provided by an embodiment of the present invention;

3 is a schematic structural diagram of an electronic device implementing a service registration and interception method according to an embodiment of the present invention;

The realization, functional characteristics and advantages of the present invention will be further described with reference to the accompanying drawings in conjunction with the embodiments.

Detailed ways

In order to make the objectives, technical solutions and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention, but not to limit the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

It should be noted that the descriptions involving "first", "second", etc. in the present invention are only for the purpose of description, and should not be construed as indicating or implying their relative importance or implying the number of indicated technical features . Thus, a feature delimited with "first", "second" may expressly or implicitly include at least one of that feature. In addition, the technical solutions between the various embodiments can be combined with each other, but must be based on the realization by those of ordinary skill in the art. When the combination of technical solutions is contradictory or cannot be realized, it should be considered that the combination of such technical solutions does not exist. , is not within the scope of protection required by the present invention.

The present invention provides a service registration and interception method. Referring to FIG. 1 , it is a schematic flowchart of a service registration and interception method provided by an embodiment of the present invention. The method may be performed by an electronic device, which may be implemented by software and/or hardware.

In this embodiment, the service registration and interception methods include:

S1. Analyze the service registration request for the target application sent by the user based on the client, and obtain the service registration request to be registered, the name of the interceptor to be registered, the binding of the service to be registered and the interceptor to be registered. Relationship and a list of method names to be intercepted for the service to be registered.

The target application may be a communication APP, and the target application uses the gRPC framework for communication. gRPC is a general-purpose RPC framework, designed for mobile and HTTP/2, supports C, Java and Go language versions, the framework uses protobuf (protobuf is a platform-independent, language-independent, extensible, lightweight and efficient serialization data structure protocol, the protocol is stored in a file with a .proto suffix) serialization and deserialization structure of binary messages.

Service (ie service class) is defined by the service keyword in the .proto file, and the JAVA version generated by the .proto file is a class that inherits the io.grpc.BindableService interface; service can be simply understood as the system provided externally interface to access.

Interceptor (ie, interceptor class). In the gRPC framework, the interceptor includes a client-side interceptor and a server-side interceptor. The interceptor in this embodiment is a server-side interceptor, and the class that implements the io.grpc.ServerInterceptor interface is Server-side interceptor. The interceptor can be understood as doing pre-check work before calling the service (the pre-check work that the interceptor needs to do after intercepting the call request can be set according to the business scenario), for example 1. The caller can only access after logging in. If the caller is not logged in, it is not allowed to access the corresponding service; for example, 2. The system requires the caller's IP address to be in the system's IP whitelist Only allow access to the service within the system, you can use the interceptor to intercept the caller's request first, and then determine whether the caller's IP is in the system's whitelist, if not, deny access to the service, otherwise allow access.

A method is used to complete something or implement a function (for example, control input or calculate a value), and usually has a return value used as a processing result or calculation result.

S2. Obtain a predetermined annotation definition code from the database, based on the name of the service to be registered, the name of the interceptor to be registered, the binding relationship between the service to be registered and the interceptor to be registered, and the interception of the service to be registered. The list of method names generates service definition code that includes annotation identifiers.

The annotation definition code is a self-defined gRPC service annotation code. In this embodiment, the annotation is @GrpcServer, and the attributes of the @GrpcServer annotation include value (service name, type is String), interceptor (interceptor class Class, must be Implement the io.grpc.ServerInterceptor interface. If this property is not set, it means that the service has no interceptor binding, otherwise it means that the service is bound with an interceptor), interceptMethods (a list of method names to be intercepted, if this property is not set, Then intercept all methods of the service class, otherwise intercept the methods in the list of method names to be intercepted in the service class; this attribute must be set when the interceptor attribute is set).

In this embodiment, the service registration request further includes the transaction to be intercepted (for example, judging whether the caller IP is in the system whitelist), and the request is based on the name of the service to be registered, the name of the interceptor to be registered, the name of the to be registered The binding relationship between the service and the interceptor to be registered and the method name list to be intercepted of the to-be-registered service to generate the service definition code include:

A11. Generate a first definition code based on the name of the interceptor to be registered and the transaction to be intercepted;

In this embodiment, the interceptor class name xxxServerInterceptor can be determined according to the name of the interceptor to be registered. The xxxServerInterceptor interceptor class needs to inherit the io.grpc.ServerInterceptor interface class, and the corresponding interception business code can be generated according to the transaction to be intercepted. Define code.

A12. Generate a second definition code based on the name of the service to be registered, the binding relationship between the service to be registered and the interceptor to be registered, and a list of method names to be intercepted of the service to be registered;

The service class name xxxServer can be determined according to the name of the service to be registered. The xxxServer service class needs to inherit the io.grpc.BindableService interface class, add the annotation @GrpcServer to the xxxServer service class, and according to the binding relationship between the service to be registered and the interceptor to be registered and the to-be-intercepted method name list of the service to be registered to set the relevant attributes, and the second definition code is obtained after summarizing.

A13. Merge the first definition code and the second definition code to obtain a service definition code.

S3. Fill the annotation definition code and service definition code into the main program code corresponding to the target application, scan the annotation identifier in the main program code, and perform registration on the to-be-registered service and the to-be-registered interceptor operations and binding operations.

In this embodiment, the scanning of the annotation identifier in the main program code, and performing the registration operation and the binding operation on the to-be-registered service and the to-be-registered interceptor, include:

B11. Scan the program segment carrying the annotation mark in the main program code, and perform correctness check on the program segment;

The correctness check includes checking whether the service class in the program segment inherits the io.grpc.BindableService interface class, checking whether the interceptor class inherits the io.grpc.ServerInterceptor interface class, and checking the syntax correctness.

B12. When the verification is passed, generate interception data based on the program segment, and perform a registration operation and a binding operation on the to-be-registered service and the to-be-registered interceptor based on the interception data.

In this embodiment, the intercepted data samples are as follows:

//The structure definition of intercepting data

struct GrpcServer {

serverClass,//Service class

interceptorClass,//Interceptor class

interceptMethods//List of method names under the service class to be intercepted

}

In this embodiment, by calling the serverBuilder.addService method provided by the gRPC framework, the services and interceptors in the intercepted data are registered and bound to the system in a loop.

When the existing gRPC framework needs to add registration services and binding interceptors, it is necessary to gradually add the registration code and binding code of each service and interceptor. When more services are added, the amount of code is relatively large, and this embodiment There is only one line of code corresponding to registration and binding operations. When you need to add service registration and binding interceptors, you only need to add annotations and set relevant properties before the corresponding service definition code. When deleting services or unbinding interceptors It is only necessary to delete the annotation identifier or delete the attribute in the annotation. This embodiment makes the code more maintainable and easier to expand.

In this embodiment, after the correctness check is performed on the program segment, the method further includes:

If the verification fails, the program segment is identified, and early warning information is sent to the client.

S4. Monitor the call request for the target application in real time, obtain one or more service names to be called and the names of the methods to be called carried in the call request, and compare the names of the services to be called and the names of the methods to be called based on the names of the services to be called and the names of the methods to be called. The invocation request performs interception processing.

The performing interception processing on the invocation request based on the name of the service to be invoked and the name of the method to be invoked includes:

C11. Determine whether each service to be called is bound with an interceptor;

In this embodiment, it can be determined whether the service to be called is bound with an interceptor according to the interception data generated by the program segment.

C12. When judging that a specified service to be called is bound with an interceptor, judge whether the method to be called of the specified service to be called exists in the list of method names to be intercepted of the specified service to be called;

C13. When it is determined that the method name list to be intercepted of the designated service to be invoked exists, perform interception processing on the invocation request.

After the call request is intercepted, corresponding business processing can be performed according to the intercepted business code corresponding to the transaction to be intercepted. Different from the existing gRPC framework, which can only intercept the granularity of the service (only all methods under the service can be intercepted), this step implements refined interception, which can intercept any specified method in the list of method names to be intercepted by the service.

In this embodiment, after judging whether each service to be called is bound with an interceptor, the method further includes:

If it is determined that each service to be called is not bound with an interceptor or the method to be called of the specified service to be called does not exist in the list of method names to be intercepted for the specified service to be called, execute the call corresponding to the call request operate.

As can be seen from the above embodiments, the service registration and interception method proposed by the present invention firstly obtains the annotation definition code, based on the name of the service to be registered, the name of the interceptor to be registered, the binding relationship between the service to be registered and the interceptor to be registered, and the to-be-registered interceptor. The list of method names to be intercepted of the service generates the service definition code, and the service definition code includes the annotation identifier; then, fill in the annotation definition code and the service definition code into the main program code corresponding to the target application, and scan the annotation identifier in the main program code, The registration operation and the binding operation are performed on the service to be registered and the interceptor to be registered; finally, the interception processing is performed on the call request based on the name of the service to be called and the name of the method to be called carried in the call request. This solution only needs to mark the service definition code corresponding to the service to be registered to realize the registration of the service, the registration of the interceptor, and the binding of the service and the interceptor, which improves the scalability and maintainability of the code; By adding a list of method names to be intercepted for a service in the service definition code, the technical problem that the existing gRPC can only intercept all methods under the service but not the specified methods under the service is solved, and refined interception is realized. Therefore, the present invention improves the expansibility and maintainability of the code, and realizes fine-grained interception.

As shown in FIG. 2 , it is a schematic block diagram of a service registration and interception apparatus provided by an embodiment of the present invention.

The service registration and interception apparatus 100 of the present invention can be installed in an electronic device. According to the implemented functions, the service registration and interception apparatus 100 may include a parsing module 110 , a generating module 120 , a scanning module 130 and an intercepting module 140 . The modules in the present invention can also be called units, which refer to a series of computer program segments that can be executed by the electronic device processor and can perform fixed functions, and are stored in the memory of the electronic device.

In this embodiment, the functions of each module/unit are as follows:

The parsing module 110 is configured to parse the service registration request for the target application sent by the user based on the client, and obtain the name of the service to be registered, the name of the interceptor to be registered, the service to be registered and the interception to be registered carried in the service registration request. The binding relationship of the server and the list of method names to be intercepted of the to-be-registered service.

The target application may be a communication APP, and the target application uses the gRPC framework for communication. gRPC is a general-purpose RPC framework, designed for mobile and HTTP/2, supports C, Java and Go language versions, the framework uses protobuf (protobuf is a platform-independent, language-independent, extensible, lightweight and efficient serialization data structure Protocol, the protocol is stored in a file with a .proto suffix) serialization and deserialization structure of binary messages.

Service (ie service class) is defined by the service keyword in the .proto file, and the JAVA version generated by the .proto file is a class that inherits the io.grpc.BindableService interface; service can be simply understood as the system provided externally interface to access.

Interceptor (ie, interceptor class). In the gRPC framework, the interceptor includes a client-side interceptor and a server-side interceptor. The interceptor in this embodiment is a server-side interceptor, and the class that implements the io.grpc.ServerInterceptor interface is Server-side interceptor. The interceptor can be understood as doing pre-check work before calling the service (the pre-check work that the interceptor needs to do after intercepting the call request can be set according to the business scenario), for example 1. The caller can only access after logging in. If the caller is not logged in, it is not allowed to access the corresponding service; for example, 2. The system requires the caller's IP address to be in the system's IP whitelist Only allow access to the service within the system, you can use the interceptor to intercept the caller's request first, and then determine whether the caller's IP is in the system's whitelist, if not, deny access to the service, otherwise allow access.

A method is used to complete something or implement a function (for example, control input or calculate a value), and usually has a return value used as a processing result or calculation result.

The generating module 120 is used to obtain a predetermined annotation definition code from the database, based on the name of the service to be registered, the name of the interceptor to be registered, the binding relationship between the service to be registered and the interceptor to be registered, and the to-be-registered interceptor The service definition code is generated from the list of method names to be intercepted for the service, and the service definition code includes the annotation identifier.

The annotation definition code is a self-defined gRPC service annotation code. In this embodiment, the annotation is @GrpcServer, and the attributes of the @GrpcServer annotation include value (service name, type is String), interceptor (interceptor class Class, must be Implement the io.grpc.ServerInterceptor interface. If this property is not set, it means that the service has no interceptor binding, otherwise it means that the service is bound with an interceptor), interceptMethods (a list of method names to be intercepted, if this property is not set, Then intercept all methods of the service class, otherwise intercept the methods in the list of method names to be intercepted in the service class; this attribute must be set when the interceptor attribute is set).

In this embodiment, the service registration request further includes the transaction to be intercepted (for example, judging whether the caller IP is in the system whitelist), and the request is based on the name of the service to be registered, the name of the interceptor to be registered, the name of the to be registered The binding relationship between the service and the interceptor to be registered and the method name list to be intercepted of the to-be-registered service to generate the service definition code include:

A21. Generate a first definition code based on the name of the interceptor to be registered and the transaction to be intercepted;

In this embodiment, the interceptor class name xxxServerInterceptor can be determined according to the name of the interceptor to be registered. The xxxServerInterceptor interceptor class needs to inherit the io.grpc.ServerInterceptor interface class, and the corresponding interception business code can be generated according to the transaction to be intercepted. Define code.

A22. Generate a second definition code based on the name of the service to be registered, the binding relationship between the service to be registered and the interceptor to be registered, and a list of method names to be intercepted of the service to be registered;

The service class name xxxServer can be determined according to the name of the service to be registered. The xxxServer service class needs to inherit the io.grpc.BindableService interface class, add the annotation @GrpcServer to the xxxServer service class, and according to the binding relationship between the service to be registered and the interceptor to be registered and the to-be-intercepted method name list of the service to be registered to set the relevant attributes, and the second definition code is obtained after summarizing.

A23. Merge the first definition code and the second definition code to obtain a service definition code.

The scanning module 130 is used to fill the annotation definition code and service definition code into the main program code corresponding to the target application, scan the annotation identifier in the main program code, and scan the to-be-registered service and to-be-registered service. Interceptors perform registration and binding operations.

In this embodiment, the scanning of the annotation identifier in the main program code, and performing the registration operation and the binding operation on the to-be-registered service and the to-be-registered interceptor, include:

B21. Scan the program segment carrying the annotation identifier in the main program code, and perform a correctness check on the program segment;

The correctness check includes checking whether the service class in the program segment inherits the io.grpc.BindableService interface class, checking whether the interceptor class inherits the io.grpc.ServerInterceptor interface class, and checking the syntax correctness.

B22. When the verification is passed, generate interception data based on the program segment, and perform a registration operation and a binding operation on the to-be-registered service and the to-be-registered interceptor based on the interception data.

In this embodiment, the intercepted data samples are as follows:

//The structure definition of intercepting data

struct GrpcServer {

serverClass,//Service class

interceptorClass,//Interceptor class

interceptMethods//List of method names under the service class to be intercepted

}

In this embodiment, by calling the serverBuilder.addService method provided by the gRPC framework, the services and interceptors in the intercepted data are registered and bound to the system in a loop.

When the existing gRPC framework needs to add registration services and binding interceptors, it is necessary to gradually add the registration code and binding code of each service and interceptor. When more services are added, the amount of code is relatively large, and this embodiment There is only one line of code corresponding to registration and binding operations. When you need to add service registration and binding interceptors, you only need to add annotations and set relevant properties before the corresponding service definition code. When deleting services or unbinding interceptors It is only necessary to delete the annotation identifier or delete the attribute in the annotation. This embodiment makes the code more maintainable and easier to expand.

In this embodiment, after the correctness check is performed on the program segment, the scanning module 130 is further configured to:

If the verification fails, the program segment is identified, and early warning information is sent to the client.

The interception module 140 is configured to monitor the call request for the target application in real time, obtain one or more service names to be called and the names of the methods to be called carried in the call request, and based on the name of the service to be called and the names of the methods to be called. The calling method name performs interception processing on the calling request.

The performing interception processing on the invocation request based on the name of the service to be invoked and the name of the method to be invoked includes:

C21. Determine whether each service to be called is bound with an interceptor;

In this embodiment, it can be determined whether the service to be called is bound with an interceptor according to the interception data generated by the program segment.

C22. When judging that a specified service to be called is bound with an interceptor, judge whether the method to be called of the specified service to be called exists in the list of method names to be intercepted of the specified service to be called;

C23. When it is determined that the method name list to be intercepted of the designated service to be invoked exists, perform interception processing on the invocation request.

After the call request is intercepted, corresponding business processing can be performed according to the intercepted business code corresponding to the transaction to be intercepted. Different from the existing gRPC framework, which can only intercept the granularity of the service (only all methods under the service can be intercepted), this step implements refined interception, which can intercept any specified method in the list of method names to be intercepted by the service.

In this embodiment, after judging whether each service to be called is bound with an interceptor, the interception module 140 is further configured to:

If it is determined that each service to be called is not bound with an interceptor or the method to be called of the specified service to be called does not exist in the list of method names to be intercepted for the specified service to be called, execute the call corresponding to the call request operate.

As shown in FIG. 3 , it is a schematic structural diagram of an electronic device implementing a service registration and interception method according to an embodiment of the present invention.

The electronic device 1 is a device that can automatically perform numerical calculation and/or information processing according to pre-set or stored instructions. The electronic device 1 may be a computer, a single network server, a server group composed of multiple network servers, or a cloud composed of a large number of hosts or network servers based on cloud computing, where cloud computing is a type of distributed computing, A super virtual computer consisting of a collection of loosely coupled computers.

In this embodiment, the electronic device 1 includes, but is not limited to, a memory 11, a processor 12, and a network interface 13 that can be communicatively connected to each other through a system bus. The memory 11 stores a service registration and interception program 10, the service The registration and interception procedure 10 may be executed by the processor 12 . FIG. 3 only shows the electronic device 1 with components 11-13 and the service registration and interception program 10. Those skilled in the art can understand that the structure shown in FIG. 3 does not constitute a limitation on the electronic device 1, and may include Fewer or more components than shown, or some components are combined, or a different arrangement of components.

The memory 11 includes a memory and at least one type of readable storage medium. The memory provides a cache for the operation of the electronic device 1; the readable storage medium can be, for example, flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM) ), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), programmable read only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. non-volatile storage media. In some embodiments, the readable storage medium may be an internal storage unit of the electronic device 1, such as a hard disk of the electronic device 1; in other embodiments, the non-volatile storage medium may also be an external storage unit of the electronic device 1 A storage device, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash memory card (Flash Card), etc. equipped on the electronic device 1 . In this embodiment, the readable storage medium of the memory 11 is generally used to store the operating system and various application software installed in the electronic device 1 , for example, to store the code of the service registration and interception program 10 in an embodiment of the present invention. In addition, the memory 11 can also be used to temporarily store various types of data that have been output or will be output.

In some embodiments, the processor 12 may be a central processing unit (Central Processing Unit, CPU), a controller, a microcontroller, a microprocessor, or other data processing chips. The processor 12 is generally used to control the overall operation of the electronic device 1, such as performing control and processing related to data interaction or communication with other devices. In this embodiment, the processor 12 is used for running the program code or processing data stored in the memory 11, for example, running the service registration and interception program 10 and the like.

The network interface 13 may include a wireless network interface or a wired network interface, and the network interface 13 is used to establish a communication connection between the electronic device 1 and a client (not shown in the figure).

Optionally, the electronic device 1 may further include a user interface, and the user interface may include a display (Display), an input unit such as a keyboard (Keyboard), and an optional user interface may also include a standard wired interface and a wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode, organic light-emitting diode) touch device, and the like. The display may also be appropriately called a display screen or a display unit, which is used for displaying information processed in the electronic device 1 and for displaying a visualized user interface.

It should be understood that the embodiments are only used for illustration, and are not limited by this structure in the scope of the patent application.

The service registration and interception program 10 stored in the memory 11 in the electronic device 1 is a combination of multiple instructions, and when running in the processor 12, can realize:

Parse the service registration request for the target application sent by the user based on the client, and obtain the name of the service to be registered carried in the service registration request, the name of the interceptor to be registered, the binding relationship between the service to be registered and the interceptor to be registered, and A list of method names to be intercepted of the to-be-registered service;

Obtain a predetermined annotation definition code from the database, based on the name of the service to be registered, the name of the interceptor to be registered, the binding relationship between the service to be registered and the interceptor to be registered, and the name of the method to be intercepted of the service to be registered The list generates service definition code, the service definition code includes an annotation identifier;

Fill in the main program code corresponding to the target application program with the annotation definition code and the service definition code, scan the annotation identifier in the main program code, and perform a registration operation on the to-be-registered service and the to-be-registered interceptor. bind operation;

Monitor the call request for the target application in real time, obtain one or more service names to be called and the name of the method to be called carried in the call request, and based on the name of the service to be called and the name of the method to be called Call request to perform interception processing.

Specifically, for the specific implementation method of the above-mentioned service registration and interception program 10 by the processor 12, reference may be made to the description of the relevant steps in the corresponding embodiment of FIG. 1, and details are not described herein.

Further, if the modules/units integrated in the electronic device 1 are implemented in the form of software functional units and sold or used as independent products, they may be stored in a computer-readable storage medium. The computer-readable medium may be non-volatile or non-volatile. The computer-readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM, Read-Only Memory) .

The computer-readable storage medium stores a service registration and interception program 10, and the service registration and interception program 10 can be executed by one or more processors. Each embodiment of the interception method is basically the same, and will not be repeated here.

In the several embodiments provided by the present invention, it should be understood that the disclosed apparatus, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the modules is only a logical function division, and there may be other division manners in actual implementation.

The modules described as separate components may or may not be physically separated, and components shown as modules may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional module in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware, or can be implemented in the form of hardware plus software function modules.

It will be apparent to those skilled in the art that the present invention is not limited to the details of the above-described exemplary embodiments, but that the present invention may be embodied in other specific forms without departing from the spirit or essential characteristics of the invention.

Therefore, the embodiments are to be regarded in all respects as illustrative and not restrictive, and the scope of the invention is to be defined by the appended claims rather than the foregoing description, which are therefore intended to fall within the scope of the claims. All changes within the meaning and range of the equivalents of , are included in the present invention. Any reference signs in the claims shall not be construed as limiting the involved claim.

Furthermore, it is clear that the word "comprising" does not exclude other units or steps and the singular does not exclude the plural. Several units or means recited in the system claims can also be realized by one unit or means by means of software or hardware. Second-class terms are used to denote names and do not denote any particular order.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit them. Although the present invention has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that the technical solutions of the present invention can be Modifications or equivalent substitutions can be made without departing from the spirit and scope of the technical solutions of the present invention.

Claims (10)

1. a service registration and interception method, is characterized in that, described method comprises: Parse the service registration request for the target application sent by the user based on the client, and obtain the name of the service to be registered carried in the service registration request, the name of the interceptor to be registered, the binding relationship between the service to be registered and the interceptor to be registered, and A list of method names to be intercepted of the to-be-registered service; Obtain a predetermined annotation definition code from the database, based on the name of the service to be registered, the name of the interceptor to be registered, the binding relationship between the service to be registered and the interceptor to be registered, and the name of the method to be intercepted of the service to be registered The list generates service definition code, the service definition code includes an annotation identifier; Fill in the main program code corresponding to the target application program with the annotation definition code and the service definition code, scan the annotation identifier in the main program code, and perform a registration operation on the to-be-registered service and the to-be-registered interceptor. bind operation; Monitor the call request for the target application in real time, obtain one or more service names to be called and the name of the method to be called carried in the call request, and based on the name of the service to be called and the name of the method to be called Call request to perform interception processing. 2. The service registration and interception method according to claim 1, wherein the service registration request further comprises a transaction to be intercepted, the service name to be registered, the name of the interceptor to be registered, the The binding relationship between the service and the interceptor to be registered and the method name list to be intercepted of the to-be-registered service to generate the service definition code include: generating a first definition code based on the name of the interceptor to be registered and the transaction to be intercepted; Generate a second definition code based on the name of the service to be registered, the binding relationship between the service to be registered and the interceptor to be registered, and the list of method names to be intercepted of the service to be registered; The first definition code and the second definition code are combined to obtain the service definition code. 3. service registration and interception method as claimed in claim 1, is characterized in that, described scanning the annotation mark in described main program code, to described service to be registered and to be registered interceptor to carry out registration operation and binding operation ,include: Scan the program segment carrying the annotation identifier in the main program code, and perform a correctness check on the program segment; When the verification is passed, interception data is generated based on the program segment, and a registration operation and a binding operation are performed on the service to be registered and the interceptor to be registered based on the interception data. 4. The service registration and interception method according to claim 3, characterized in that, after the correctness check is performed on the program segment, the method further comprises: If the verification fails, the program segment is identified, and early warning information is sent to the client. 5. The service registration and interception method according to claim 1, wherein the performing interception processing on the invocation request based on the name of the service to be invoked and the name of the method to be invoked comprises: Determine whether each service to be called is bound with an interceptor; When judging that a specified service to be called is bound with an interceptor, it is judged whether the method to be called of the specified service to be called exists in the list of method names to be intercepted of the specified service to be called; When it is determined that it exists in the list of method names to be intercepted for the designated service to be invoked, an interception process is performed on the invocation request. 6. The service registration and interception method according to claim 5, wherein after judging whether each service to be called is bound with an interceptor, the method further comprises: If it is determined that each service to be called is not bound with an interceptor or the method to be called of the specified service to be called does not exist in the list of method names to be intercepted for the specified service to be called, execute the call corresponding to the call request operate. 7. A service registration and interception device, wherein the device comprises: The parsing module is used to parse the service registration request for the target application sent by the user based on the client, and obtain the name of the service to be registered, the name of the interceptor to be registered, the service to be registered and the interceptor to be registered carried in the service registration request. The binding relationship and the list of method names to be intercepted for the service to be registered; The generation module is used to obtain the predetermined annotation definition code from the database, based on the name of the service to be registered, the name of the interceptor to be registered, the binding relationship between the service to be registered and the interceptor to be registered, and the service to be registered. The list of method names to be intercepted generates a service definition code, and the service definition code includes an annotation identifier; A scanning module is used to fill the annotation definition code and service definition code into the main program code corresponding to the target application, scan the annotation identifier in the main program code, and intercept the service to be registered and the service to be registered. The device performs registration and binding operations; The interception module is used to monitor the call request for the target application in real time, obtain one or more service names to be called and the name of the method to be called carried in the call request, and based on the name of the service to be called and the name of the method to be called The method name performs interception processing on the invocation request. 8. The service registration and interception device according to claim 7, characterized in that, by scanning the annotation identifier in the main program code, a registration operation and a binding operation are performed on the to-be-registered service and the to-be-registered interceptor ,include: Scan the program segment carrying the annotation identifier in the main program code, and perform a correctness check on the program segment; When the verification is passed, interception data is generated based on the program segment, and a registration operation and a binding operation are performed on the service to be registered and the interceptor to be registered based on the interception data. 9. An electronic device, characterized in that the electronic device comprises: at least one processor; and, a memory communicatively coupled to the at least one processor; wherein, The memory stores a service registration and interception program executable by the at least one processor, the service registration and interception program being executed by the at least one processor to enable the at least one processor to execute the claims The service registration and interception method described in any one of 1 to 6. 10. A computer-readable storage medium, characterized in that, a service registration and interception program is stored on the computer-readable storage medium, and the service registration and interception program can be executed by one or more processors to achieve the following: The service registration and interception method according to any one of claims 1 to 6.

Images