CN104506371A - Method and device for management of application programming interface (API) call records - Google Patents
Method and device for management of application programming interface (API) call records Download PDFInfo
- Publication number
- CN104506371A CN104506371A CN201510003882.1A CN201510003882A CN104506371A CN 104506371 A CN104506371 A CN 104506371A CN 201510003882 A CN201510003882 A CN 201510003882A CN 104506371 A CN104506371 A CN 104506371A
- Authority
- CN
- China
- Prior art keywords
- api calls
- api
- charging
- record
- records
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Meter Arrangements (AREA)
Abstract
The invention relates to the technical field of flow calculation and provides a method for management of application programming interface (API) call records; the method comprises the steps: acquiring a plurality of API call records; determining the respective affiliated charging period of each call record in the plurality of the API call records according to the Called time of each call record in the plurality of the API call records; superposing the resource usage amount of each of more than two API call records, which are located in the same charging period, have the same caller mark and have the same charging unit price, in the plurality of the API call records according to the preset charging unit price, and obtaining one API call record subjected to superposition. With adoption of the technical scheme, the quantity of the API call records to be processed by an API charging gateway can be reduced and partial processing resources can be released.
Description
Technical field
The present invention relates to field of computer technology, particularly relate to a kind of management method and device of application programming interface API Calls record.
Background technology
API (Application Programming Interface, application programming interface), for the service ability of capable server being opened to the outside world, during use, calls API to realize the access to capable server by API gateway usually.Often call an API, API gateway can produce an API Calls record, then this API Calls record can be transferred to API charging gateway by API gateway, and API charging gateway, according to preset charging regulation, calculates this according to API Calls record and calls the expense that API produces.
The major defect of this technology is: API charging gateway needs API Calls record quantity to be processed too large, occupies more process resource.
Summary of the invention
The object of this invention is to provide a kind of management method and device of application programming interface API Calls record, for reducing the quantity of the API Calls record that API gateway produces to a certain extent, and then reduce the quantity that API charging gateway needs API Calls record to be processed, discharge part process resource.
First aspect, the embodiment of the present invention provides a kind of management method of application programming interface API Calls record, and the method comprises:
Obtain many API Calls records, each API Calls record in described many API Calls records all at least comprises following attribute information: caller identifies, calls moment Called time and resource use amount, wherein, the caller of described caller mark for representing described API, described Called time is for representing the invoked time information of described API;
According to the Called time of bar API Calls record every in described many API Calls records, determine the metering period that in described many API Calls records, every bar API Calls record is affiliated separately;
According to the charging unit price preset, by being arranged in same metering period in described many API Calls records, there is identical caller mark and the resource use amount with more than two each API Calls record of API Calls record of identical charging unit price carries out overlap-add procedure, and obtain an API Calls record after overlap-add procedure.
In conjunction with first aspect, under the first execution mode of first aspect, according to described charging unit price, the charging result that charging obtains is carried out to a described API Calls record after overlap-add procedure, with, according to described charging unit price, to being positioned at same metering period in described many API Calls records, having identical caller mark and more than two the API Calls records with identical charging unit price carry out the charging result that charging obtains, is identical.
In conjunction with the first execution mode of first aspect or first aspect, under the second execution mode of first aspect,
Each API Calls record in described many API Calls records all also comprises following attribute information: API identifies, and described API mark is for representing invoked API;
The charging unit price that described basis is preset, by being arranged in same metering period in described many API Calls records, there is identical caller mark and the resource use amount with more than two each API Calls record of API Calls record of identical charging unit price carries out overlap-add procedure, and obtain an API Calls record after overlap-add procedure, specifically comprise:
By being arranged in same metering period in described many API Calls records, there is identical caller mark and the resource use amount with more than two each API Calls record of API Calls record that identical API identifies carries out overlap-add procedure, and obtain an API Calls record after overlap-add procedure.
In conjunction with the second execution mode of first aspect, under the third execution mode of first aspect,
According to described charging unit price, the charging result that charging obtains is carried out to a described API Calls record after overlap-add procedure, with, according to described charging unit price, to being positioned at same metering period in described many API Calls records, having identical caller mark and have more than two API Calls records that identical API identifies and carry out the charging result that charging obtains, is identical.
In conjunction with the first execution mode of first aspect or first aspect to any one execution mode in the third execution mode of first aspect, under the 4th kind of execution mode of first aspect,
Carry out filtration treatment to described many API Calls records, filtering is arranged in the API Calls record that described many API Calls record charging unit prices are zero.
In conjunction with the first execution mode of first aspect or first aspect to any one execution mode in the 4th kind of execution mode of first aspect, under the 5th kind of execution mode of first aspect,
Described charging unit price be call described API unit duration price, call described API unit number of times price, call the unit data flow that described API obtains price or call the price of unit memory space that described API obtains.
In conjunction with the first execution mode of first aspect or first aspect to any one execution mode in the 5th kind of execution mode of first aspect, under the 6th kind of execution mode of first aspect,
Described metering period is one month.
Second aspect, the embodiment of the present invention provides a kind of management devices of application programming interface API Calls record, comprising:
Acquiring unit, for obtaining many API Calls records, each API Calls record in described many API Calls records all at least comprises following attribute information: caller identifies, calls moment Called time and resource use amount, wherein, the caller of described caller mark for representing described API, described Called time is for representing the invoked time information of described API;
Determining unit, for the Calledtime according to bar API Calls record every in described many API Calls records, determines the metering period that in described many API Calls records, every bar API Calls record is affiliated separately;
Administrative unit, for the charging unit price that basis is preset, by being arranged in same metering period in described many API Calls records, there is identical caller mark and the resource use amount with more than two each API Calls record of API Calls record of identical charging unit price carries out overlap-add procedure, and obtain an API Calls record after overlap-add procedure.
In conjunction with second aspect, under the first execution mode of second aspect,
According to described charging unit price, the charging result that charging obtains is carried out to a described API Calls record after overlap-add procedure, with, according to described charging unit price, to being positioned at same metering period in described many API Calls records, having identical caller mark and more than two the API Calls records with identical charging unit price carry out the charging result that charging obtains, is identical.
In conjunction with the first execution mode of second aspect or second aspect, under the second execution mode of second aspect,
Each API Calls record in described many API Calls records all also comprises following attribute information: API identifies, and described API mark is for representing invoked API;
Described administrative unit specifically for by being arranged in same metering period in described many API Calls records, there is identical caller mark and the resource use amount with more than two each API Calls record of API Calls record that identical API identifies carries out overlap-add procedure, and obtain an API Calls record after overlap-add procedure.
In conjunction with the second execution mode of second aspect, under the third execution mode of second aspect,
According to described charging unit price, the charging result that charging obtains is carried out to a described API Calls record after overlap-add procedure, with, according to described charging unit price, to being positioned at same metering period in described many API Calls records, having identical caller mark and have more than two API Calls records that identical API identifies and carry out the charging result that charging obtains, is identical.
In conjunction with the first execution mode of second aspect or second aspect to any one execution mode in the third execution mode of second aspect, under the 4th kind of execution mode of second aspect,
Described administrative unit is also for carrying out filtration treatment to described many API Calls records, and filtering is arranged in the API Calls record that described many API Calls record charging unit prices are zero.
In conjunction with the first execution mode of second aspect or second aspect to any one execution mode in the 4th kind of execution mode of second aspect, under the 5th kind of execution mode of second aspect,
Described charging unit price be call described API unit duration price, call described API unit number of times price, call the unit data flow that described API obtains price or call the price of unit memory space that described API obtains.
In conjunction with the first execution mode of second aspect or second aspect to any one execution mode in the 5th kind of execution mode of second aspect, under the 6th kind of execution mode of second aspect,
Described metering period is one month.
The third aspect, the embodiment of the present invention provides a kind of management system of application programming interface API Calls record, comprises API gateway, API charging gateway and if the first execution mode of second aspect or second aspect is to the management devices of the API Calls record as described in any one execution mode in the 6th kind of execution mode of second aspect:
Described many API Calls records that described API gateway obtains for generation of the management devices of described API Calls record;
Described API charging gateway is used for an API Calls record after the management devices overlap-add procedure of described API Calls record, carries out charging according to described default charging unit price.
In conjunction with the third aspect, under the first execution mode of the third aspect,
The management devices of described API Calls record is integrated in described API gateway, or the management devices of described API Calls record is integrated in described API charging gateway.
Known, the embodiment of the present invention provides a kind of management method of API Calls record, specifically comprise: according to the charging unit price preset, by being positioned at same metering period in many API Calls records, there is identical caller mark and the resource use amount with more than two API Calls records of identical charging unit price carries out overlap-add procedure, obtain an API Calls record through overlap-add procedure.Adopt this technical scheme, under the prerequisite not affecting charging result correctness, the number that API charging gateway needs to carry out the API Calls record of charging process can be decreased, discharged part and processed resource.
Accompanying drawing explanation
In order to be illustrated more clearly in the technical scheme of the embodiment of the present invention, be briefly described to the accompanying drawing used required in embodiment or description of the prior art below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.
Fig. 1 is the application scenarios schematic diagram of the management method of the API Calls record that the embodiment of the present invention provides;
The schematic flow sheet of the management method of a kind of API Calls record that Fig. 2 a provides for the embodiment of the present invention;
The schematic flow sheet of the management method of the another kind of API Calls record that Fig. 2 b provides for the embodiment of the present invention;
The schematic diagram of the API Calls record before the merging that Fig. 3 a provides for the embodiment of the present invention;
The schematic diagram of the API Calls record after the merging that Fig. 3 b provides for the embodiment of the present invention;
The structural representation of the management devices of the API Calls record that Fig. 4 provides for the embodiment of the present invention;
The structural representation of the gateway that Fig. 5 provides for the embodiment of the present invention;
The structural representation of the management system of the API Calls record that Fig. 6 provides for the embodiment of the present invention.
Embodiment
For making the object of the embodiment of the present invention, technical scheme and advantage clearly, below in conjunction with the accompanying drawing in the embodiment of the present invention, technical scheme in the embodiment of the present invention is clearly and completely described, obviously, described embodiment is the present invention's part embodiment, instead of whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtained under creative work prerequisite, belong to the scope of protection of the invention.
Gateway (Gateway) is also known as gateway, protocol converter.Gateway realizes network interconnection more than network layer, is the most complicated network interconnection apparatus, network interconnection, only for network interconnection that two upper-layer protocols are different.Gateway both may be used for wide area network interconnection, also may be used for local area network interconnection.Gateway is a kind of computer system or equipment of serving as conversion important task.Using different communication protocol, data format or language, even between the diverse two kinds of systems of architecture, gateway is a translater.What commonly use in the function of gateway is protocol conversion, but also forwards block for security protection, statistics charging, message.Technical scheme provided by the invention for be the statistics billing function of gateway.
Application programming interface (API described in the embodiment of the present invention, Application ProgrammingInterface) for the disposal ability of capable server is opened to the outside world, specifically see accompanying drawing 1, the ability that caller provides for using capable server, by the API of API gateway call capability server, to realize the access to capable server; In addition, the ability that capable server provides normally paid service, an API Calls record will be produced so usually often call API, an API gateway and this API Calls record is transferred to API charging gateway, carrying out charging by API charging gateway according to this API Calls record.It should be noted that, the API gateway described in the embodiment of the present invention refers to Web WPI gateway, also i.e. API gateway shown in Fig. 1 and being connected by network service between capable server.
In the prior art, after API gateway produces a collection of API Calls record, this collection of API Calls record can be transferred to API charging gateway, carry out unified charging process by API charging gateway.Usually, this collection of API Calls record is the whole API Calls records produced in a metering period.The technical scheme that the embodiment of the present invention provides manages this collection of API Calls record exactly, to reduce the number of the pending API Calls record of API charging gateway, thus discharges the process resource of API charging gateway to a certain extent.
Embodiment one
Accompanying drawings 2a, the schematic flow sheet of the management method of a kind of API Calls record provided for the embodiment of the present invention, should be understood that, the method can be used in the application scenarios shown in Fig. 1.Concrete, as shown in Figure 2 a, the management method of the API Calls record that the embodiment of the present invention provides comprises the steps:
S201, obtain many API Calls records, each API Calls record in described many API Calls records all at least comprises following attribute information: caller identifies, calls moment Called time and resource use amount, wherein, the caller of described caller mark for representing described API, described Called time is for representing the invoked time information of described API;
It should be noted that, described many API Calls records are produced by API gateway.
It should be noted that the caller of described caller mark for identifying described API, from the angle of charging, described caller mark is for identifying charge to whom likes.As a specific embodiment, namely described caller is designated APP Key (also App mark), also namely by APP key can be unique the caller that identifies whom is, the APP of such as enterprise's customization, by this APP key, caller just can be identified for this enterprise.See accompanying drawing 3a, be and use APP Key to determine caller, should be understood that, the caller that same APP Key is corresponding is unique, there is not the situation of the corresponding two or more caller of same APP key.
It should be noted that, described resource use amount specifically refers to the data traffic that the duration (or calling the duration of API) of access ability server, the number of times (or calling the number of times of API) of access ability server, acquisition capability server provide or the space size etc. that acquisition capability server provides.For a concrete capable server, the charging way that operator is arranged determines the particular content of described resource use amount.If the charging way that operator is arranged is pay-per-use, then described resource use amount refers to the number of times (or calling the number of times of API) of access ability server; If the charging way that operator is arranged is by calling duration based accounting, then described resource use amount refers to the duration (or calling the duration of API) of access ability server; If the charging way that operator is arranged is the data traffic charging provided by capable server, then described resource use amount refers to the data traffic that acquisition capability server provides; If the charging way that operator is arranged is the space size charging provided by capable server, then described resource use amount refers to space size that acquisition capability server provides etc.Will not enumerate herein, but it is understood that, the particular content of described resource use amount is relevant with the charging way that operator is arranged for a certain concrete capable server.
S203, Called time according to bar API Calls record every in described many API Calls records, to determine in described many API Calls records the metering period belonging to every bar API Calls record separately;
Usually, metering period is one month.See accompanying drawing 3a, easily learn, according to called time, can determine that call action specifically occurs in certain year in such a month, and on such a day at a moment in time, so according to calledtime, certainly can determine and call as being specifically positioned at which metering period.
The charging unit price that S205, basis are preset, by being arranged in same metering period in described many API Calls records, there is identical caller mark and the resource use amount with more than two each API Calls record of API Calls record of identical charging unit price carries out overlap-add procedure, and obtain an API Calls record after overlap-add procedure.
It should be noted that, according to described charging unit price, the charging result that charging obtains is carried out to a described API Calls record after overlap-add procedure, with, according to described charging unit price, to being positioned at same metering period in described many API Calls records, having identical caller mark and more than two the API Calls records with identical charging unit price carry out the charging result that charging obtains, is identical.Also namely, the method that the embodiment of the present invention provides needs the primary condition followed to be the correctness not affecting charging result.
It should be noted that, the charging unit price preset is usually located in API charging gateway, is preset by operator.
See accompanying drawing 3a and 3b, it should be noted that, in the embodiment shown in Fig. 3 a and 3b, caller is designated APP Key, also namely can determine whom caller is by APP Key.So, step 205 is in the embodiment shown in Fig. 3 a and 3b, should be specially: according to the charging unit price preset, by being arranged in same metering period in described many API Calls records, there is identical APP Key and the resource use amount with more than two each API Calls record of API Calls record of identical charging unit price carries out overlap-add procedure, and obtain an API Calls record after overlap-add procedure.With further reference to accompanying drawing 3a and 3b, known, the APPKey of front 4 API Calls records is APP_Key1; And according to the Called Time of front 4 API Calls records, known, these front 4 API Calls records are all positioned at 2014-10, and this calls the cycle, and the cycle of also namely calling is identical; Further, these front 4 API Calls records are all according to call number charging, and the identical (not shown) of charging unit price preset in API gateway, so overlap-add procedure can be carried out to the resource use amount of these front 4 API Calls records, namely call number superposes, and obtains calling record as shown in Article 1 in Fig. 3 b.The 5th article in Fig. 3 a is the same with the merging method of the 6th article of API Calls record with the merging method of above-mentioned front 4 articles of API Calls records, repeats no more herein.
It should be noted that, described charging unit price be call described API unit duration price, call described API unit number of times price, call the unit data flow that described API obtains price or call the price of unit memory space that described API obtains.Described charging unit price is pre-set by the operator of capable server, and described charging unit price be not arranged just unalterable, such as common telephone expenses appreciate, or, various telephone expenses set meals etc., operator normally, after a metering period terminates, changes charging unit price.
Further, the method described in the embodiment of the present invention can also comprise the steps: to carry out filtration treatment to described many API Calls records, and filtering is arranged in the API Calls record that described many API Calls record charging unit prices are zero.
See accompanying drawing 3a, last two the API Calls records in this table are free, in other words, the charging unit price that API charging gateway is preset is zero, so do not need API charging gateway to carry out charging process, so these last two API Calls records of filtering, can not have an impact to charging result.
It should be noted that, after this filtering step occurs in step S201, concrete, after can step S201 being occurred in, before step S203, also after can occurring in step S203, before S205, but or after occurring in step S205. preferred, after this filtering step occurs in step S201, before step S203, this is owing to just having carried out filtering process before superposition, data volume to be processed is needed to decrease when making to carry out overlap-add procedure, thus ensureing the quantity of the API Calls record reducing the process of API charging gateway, on the basis of the process resource of release API charging gateway, improve the execution efficiency of the management method of the API Calls record that the embodiment of the present invention provides.
As from the foregoing, the embodiment of the present invention provides a kind of management method of API Calls record, specifically comprise: according to the charging unit price preset, by being positioned at same metering period in many API Calls records, there is identical caller mark and the resource use amount with more than two API Calls records of identical charging unit price carries out overlap-add procedure, obtain an API Calls record through overlap-add procedure.Adopt this technical scheme, under the prerequisite not affecting charging result correctness, the number that API charging gateway needs to carry out the API Calls record of charging process can be decreased, discharged part and processed resource.
See accompanying drawing 2b, the schematic flow sheet of the management method of the another kind of API Calls record provided for the embodiment of the present invention, should be understood that, the method can be used in the application scenarios shown in Fig. 1.Concrete, as shown in Figure 2 b, the management method of the API Calls record that the embodiment of the present invention provides comprises the steps:
S211, obtain many API Calls records, each API Calls record in described many API Calls records all at least comprises following attribute information: caller identifies, call moment Called time, API mark and resource use amount, wherein, the caller of described caller mark for representing described API, described Called time is for representing the invoked time information of described API, and described API mark is for representing invoked API;
S213, Called time according to bar API Calls record every in described many API Calls records, to determine in described many API Calls records the metering period belonging to every bar API Calls record separately;
S215, by being arranged in same metering period in described many API Calls records, there is identical caller mark and the resource use amount with more than two each API Calls record of API Calls record that identical API identifies carries out overlap-add procedure, and obtain an API Calls record after overlap-add procedure.
The difference of the embodiment shown in the present embodiment and Fig. 2 a is, the combining objects that the embodiment of the present invention limits is different with the combining objects that the embodiment shown in Fig. 2 a limits, in the embodiment shown in Fig. 2 a, " be positioned at same metering period by described many API Calls records, there is identical caller mark and the resource use amount with each API Calls record in more than two API Calls records of identical charging unit price carries out overlap-add procedure ", but in the embodiment shown in Fig. 2 b, " be positioned at same metering period by described many API Calls records, there is identical caller mark and there is the resource use amount of each API Calls record in more than two the API Calls records that identical API identifies and carry out overlap-add procedure ".
It should be noted that, " having identical API to identify " described in embodiment shown in Fig. 2 b and " the having identical charging unit price " described in the embodiment shown in Fig. 2 a are different, there is following relation between them: be positioned at same metering period, have identical caller mark and have identical API identify more than two API Calls records must have identical charging unit price, but, be positioned at same metering period, there is identical caller mark and more than two the API Calls records with identical charging unit price might not have identical API mark.
Further, owing to being positioned at same metering period, there is identical caller mark and there are more than two the API Calls records that identical API identifies and must have identical charging unit price, so, in the embodiment shown in Fig. 2 b, the resource use amount of more than two the API Calls records meeting this condition can be superposed, and charging unit price default in API charging gateway need not be considered.
Should be understood that, in the embodiment shown in accompanying drawing 2b, according to described charging unit price, the charging result that charging obtains is carried out to a described API Calls record after overlap-add procedure, with, according to described charging unit price, to being positioned at same metering period in described many API Calls records, having identical caller mark and have more than two API Calls records that identical API identifies and carry out the charging result that charging obtains, is identical.
It should be noted that, embodiment shown in embodiment shown in accompanying drawing 2b and accompanying drawing 2a only has above-mentioned distinctive points, other every explanation explanations being applicable to the embodiment shown in accompanying drawing 2a, be applicable to the embodiment shown in accompanying drawing 2b too, also be, these two embodiments can be quoted mutually, repeat no more herein.
As from the foregoing, the embodiment of the present invention provides a kind of management method of API Calls record, specifically comprise: by being arranged in same metering period in described many API Calls records, there is identical caller mark and the resource use amount with more than two each API Calls record of API Calls record that identical API identifies carries out overlap-add procedure, and obtain an API Calls record after overlap-add procedure.Adopt the program, under the prerequisite not affecting charging result correctness, the number that API charging gateway needs to carry out the API Calls record of charging process can be decreased, discharged part and processed resource.Further, the management method of the API Calls record that the embodiment of the present invention provides, does not rely on charging unit price, and relative to the embodiment corresponded to described in Fig. 2 a, the technical scheme that the present embodiment provides more simply, easily realizes.
Embodiment two
See accompanying drawing 4, the structural representation of the management devices 40 of a kind of API Calls record provided for the embodiment of the present invention, it should be noted that, the management devices 40 of this API Calls record can be used in the application scenarios figure described in Fig. 1, preferably, the management devices 40 of this API Calls record is integrated in API gateway described in Fig. 1 or API charging gateway.Concrete, as shown in Figure 4, the management devices 40 of API Calls record is made up of following parts:
Acquiring unit 41, for obtaining many API Calls records, each API Calls record in described many API Calls records all at least comprises following attribute information: caller identifies, calls moment Called time and resource use amount, wherein, the caller of described caller mark for representing described API, described Calledtime is for representing the invoked time information of described API;
It should be noted that the caller of described caller mark for identifying described API, from the angle of charging, described caller mark is for identifying charge to whom likes.As a specific embodiment, namely described caller is designated APP Key (also App mark), also namely by APP key can be unique the caller that identifies whom is, the APP of such as enterprise's customization, by this APP key, caller just can be identified for this enterprise.See accompanying drawing 3a, be and use APP Key to determine caller, should be understood that, the caller that same APP Key is corresponding is unique, there is not the situation of the corresponding two or more caller of same APP key.
It should be noted that, for a concrete capable server, the charging way that operator is arranged determines the particular content of described resource use amount.If the charging way that operator is arranged is pay-per-use, then described resource use amount refers to the number of times (or calling the number of times of API) of access ability server; If the charging way that operator is arranged is by calling duration based accounting, then described resource use amount refers to the duration (or calling the duration of API) of access ability server; If the charging way that operator is arranged is the data traffic charging provided by capable server, then described resource use amount refers to the data traffic that acquisition capability server provides; If the charging way that operator is arranged is the space size charging provided by capable server, then described resource use amount refers to space size that acquisition capability server provides etc.Will not enumerate herein, but it is understood that, the particular content of described resource use amount is relevant with the charging way that operator is arranged for a certain concrete capable server.
Determining unit 43, for the Calledtime according to bar API Calls record every in described many API Calls records, determines the metering period that in described many API Calls records, every bar API Calls record is affiliated separately;
See accompanying drawing 3a, easily learn, according to called time, can determine that call action specifically occurs in certain year in such a month, and on such a day at a moment in time, so according to called time, certainly can determine and call as being specifically positioned at which metering period.It should be noted that, usually, metering period is one month.
Administrative unit 45, for the charging unit price that basis is preset, by being arranged in same metering period in described many API Calls records, there is identical caller mark and the resource use amount with more than two each API Calls record of API Calls record of identical charging unit price carries out overlap-add procedure, and obtain an API Calls record after overlap-add procedure.
It should be noted that, according to described charging unit price, the charging result that charging obtains is carried out to a described API Calls record after overlap-add procedure, with, according to described charging unit price, to being positioned at same metering period in described many API Calls records, having identical caller mark and more than two the API Calls records with identical charging unit price carry out the charging result that charging obtains, is identical.
It should be noted that described charging unit price be call described API unit duration price, call described API unit number of times price, call the unit data flow that described API obtains price or call the price of unit memory space that described API obtains.Described charging unit price is pre-set by the operator of capable server, and described charging unit price be not arranged just unalterable, such as common telephone expenses appreciate, or, various telephone expenses set meals etc., operator normally, after a metering period terminates, changes charging unit price.
See accompanying drawing 3a and 3b, it should be noted that, in the embodiment shown in Fig. 3 a and 3b, caller is designated APP Key, also namely can determine whom caller is by APP Key.So, step 205 is in the embodiment shown in Fig. 3 a and 3b, should be specially: according to the charging unit price preset, by being arranged in same metering period in described many API Calls records, there is identical APP Key and the resource use amount with more than two each API Calls record of API Calls record of identical charging unit price carries out overlap-add procedure, and obtain an API Calls record after overlap-add procedure.With further reference to accompanying drawing 3a and 3b, known, the APPKey of front 4 API Calls records is APP_Key1; And according to the Called Time of front 4 API Calls records, known, these front 4 API Calls records are all positioned at 2014-10, and this calls the cycle, and the cycle of also namely calling is identical; Further, these front 4 API Calls records are all according to call number charging, and the identical (not shown) of charging unit price preset in API gateway, so overlap-add procedure can be carried out to the resource use amount of these front 4 API Calls records, namely call number superposes, and obtains calling record as shown in Article 1 in Fig. 3 b.The 5th article in Fig. 3 a is the same with the merging method of the 6th article of API Calls record with the merging method of above-mentioned front 4 articles of API Calls records, repeats no more herein.
Further, administrative unit 45 is also for carrying out filtration treatment to described many API Calls records, and filtering is arranged in the API Calls record that described many API Calls record charging unit prices are zero.
See accompanying drawing 3a, last two the API Calls records in this table are free, in other words, the charging unit price that API charging gateway is preset is zero, so do not need API charging gateway to carry out charging process, so these last two API Calls records of filtering, can not have an impact to charging result.
As from the foregoing, there is provided in a kind of management devices of API Calls record in the embodiment of the present invention, the charging unit price that administrative unit 45 is preset for basis, by being positioned at same metering period in many API Calls records, there is identical caller mark and the resource use amount with more than two API Calls records of identical charging unit price carries out overlap-add procedure, obtain an API Calls record through overlap-add procedure.Adopt this device, under the prerequisite not affecting charging result correctness, the number that API charging gateway needs to carry out the API Calls record of charging process can be decreased, discharged part and processed resource.
As an alternative embodiment of the invention, each the API Calls record in described many API Calls records all also comprises following attribute information: API identifies, and described API mark is for representing invoked API;
Administrative unit 45 specifically for by being arranged in same metering period in described many API Calls records, there is identical caller mark and the resource use amount with more than two each API Calls record of API Calls record that identical API identifies carries out overlap-add procedure, and obtain an API Calls record after overlap-add procedure.
It should be noted that, " there is identical API identify " and " having identical charging unit price " is different, there is following relation between them: be positioned at same metering period, have identical caller mark and have identical API identify more than two API Calls records must have identical charging unit price, but, be positioned at same metering period, there is identical caller mark and more than two the API Calls records with identical charging unit price might not have identical API mark.
Further, owing to being positioned at same metering period, there is identical caller mark and there are more than two the API Calls records that identical API identifies and must have identical charging unit price, the resource use amount of more than two the API Calls records meeting this condition superposes by institute's business administrative unit 45, and need not consider charging unit price default in API charging gateway.
It should be noted that, according to described charging unit price, the charging result that charging obtains is carried out to a described API Calls record after overlap-add procedure, with, according to described charging unit price, to being positioned at same metering period in described many API Calls records, having identical caller mark and have more than two API Calls records that identical API identifies and carry out the charging result that charging obtains, is identical.
As from the foregoing, the embodiment of the present invention provides a kind of management devices of API Calls record, relative to the management devices that previous embodiment provides, administrative unit 45 specifically for by being arranged in same metering period in described many API Calls records, there is identical caller mark and the resource use amount with more than two each API Calls record of API Calls record that identical API identifies carries out overlap-add procedure, and obtain an API Calls record after overlap-add procedure.Adopt the program, under the prerequisite not affecting charging result correctness, the number that API charging gateway needs to carry out the API Calls record of charging process can be decreased, discharged part and processed resource.Further, the management devices of the API Calls record that the embodiment of the present invention provides, does not rely on charging unit price, so more simply, easily realize.
Embodiment three
See accompanying drawing 5, for the structural representation of a kind of gateway 500 that the embodiment of the present invention provides, this gateway 500 is operation carriers of the management devices of API Calls record described in embodiment two, and should be understood that, this gateway 500 can be used in the application scenarios figure shown in Fig. 1.It should be noted that, when the operation carrier that API gateway is the management devices of the API Calls record described in embodiment two, namely gateway 500 refers to API gateway; When the operation carrier that API charging gateway is the management devices of the API Calls record described in embodiment two, namely gateway 500 refers to API charging gateway; Certainly, gateway 500 may also be other gateways outside API gateway and API charging gateway.
Concrete, as shown in Figure 5, gateway 500 can comprise at least one processor 501, such as CPU, at least one network interface 504, such as physical network card, or other user interface 503, and memory 505 and at least one communication bus 502.
Wherein, communication bus 502 is for realizing the connection communication between these assemblies.
Network interface 504 is for realizing the connection communication between this gateway 500 and network, and such as described control appliance 500 connects the equipment such as physical network card and/or physical switches by described network interface 504, so that receive the data of other network equipments transmission.Optionally, user interface 503, can comprise display, keyboard or other pointing devices, such as, and mouse, trace ball (trackball), touch-sensitive plate or touch sensitive display screen etc.
Memory 605 may comprise high random access memory body (RAM, Random Access Memory), still may comprise non-labile memory (non-volatile memory), such as at least one magnetic disc store.Optionally, this memory 605 can also comprise at least one and is positioned at storage device away from aforementioned processor 501.In some embodiments, memory 505 stores following element, executable module or data structure, or their subset, or their superset: operating system 5051, comprises various system program, for realizing various basic business and processing hardware based task; Application module 5052, comprises various application program, for realizing various applied business.In gateway 500, in application module 5052, include but not limited to acquiring unit, determining unit and administrative unit that the management devices of the API Calls record described in embodiment two comprises.
It should be noted that, processor 501, for realizing all functions of the management devices of the API Calls record described in embodiment two, repeats no more herein, and particular content is see embodiment two.
Known, the embodiment of the present invention provides a kind of gateway, this gateway is the operation carrier of the management devices of the API Calls record described in embodiment, based on this gateway, can according to the charging unit price preset, by being positioned at same metering period in many API Calls records, there is identical caller mark and the resource use amount with more than two API Calls records of identical charging unit price carries out overlap-add procedure, obtain an API Calls record through overlap-add procedure.Thus under the prerequisite not affecting charging result correctness, decrease the number that API charging gateway needs to carry out the API Calls record of charging process, discharge part and process resource.
Embodiment four
See accompanying drawing 6, the structural representation of the management system of a kind of API Calls record provided for the embodiment of the present invention, the management system of this API Calls record can be used in the application scenarios shown in Fig. 1.And the concrete function of the management devices of API Calls record in the management system of this API Calls record is see embodiment two, repeats no more herein.
Concrete volume, in the management system of API Calls record as shown in Figure 6, described many API Calls records that described API gateway obtains for generation of the management devices of described API Calls record; Described API charging gateway is used for an API Calls record after the management devices overlap-add procedure of described API Calls record, carries out charging according to described default charging unit price.
Preferably, the management devices of described API Calls record is integrated in described API gateway, or the management devices of described API Calls record is integrated in described API charging gateway.
The embodiment of the present invention provides a kind of management system of API Calls record, based on the management system of this API Calls record, can according to the charging unit price preset, by being positioned at same metering period in many API Calls records, there is identical caller mark and the resource use amount with more than two API Calls records of identical charging unit price carries out overlap-add procedure, obtain an API Calls record through overlap-add procedure.Thus under the prerequisite not affecting charging result correctness, decrease the number that API charging gateway needs to carry out the API Calls record of charging process, discharge part and process resource.
Those skilled in the art can be well understood to, and for convenience and simplicity of description, the specific works process of the system of foregoing description, device and unit, with reference to the corresponding process in preceding method embodiment, can not repeat them here.
In several embodiments that the application provides, should be understood that disclosed system, apparatus and method can realize by another way.Such as, device embodiment described above is only schematic, such as, the division of described unit, be only a kind of logic function to divide, actual can have other dividing mode when realizing, such as multiple unit or assembly can in conjunction with or another system can be integrated into, or some features can be ignored, or do not perform.Another point, shown or discussed coupling each other or direct-coupling or communication connection can be by some interfaces, and the indirect coupling of device or unit or communication connection can be electrical, machinery or other form.
The described unit illustrated as separating component or can may not be and physically separates, and the parts as unit display can be or may not be physical location, namely can be positioned at a place, or also can be distributed in multiple network element.Some or all of unit wherein can be selected according to the actual needs to realize the object of the present embodiment scheme.
In addition, each functional unit in each embodiment of the present invention can be integrated in a processing unit, also can be that the independent physics of unit exists, also can two or more unit in a unit integrated.
If described function using the form of SFU software functional unit realize and as independently production marketing or use time, can be stored in a computer read/write memory medium.Based on such understanding, the part of the part that technical scheme of the present invention contributes to prior art in essence in other words or this technical scheme can embody with the form of software product, this computer software product is stored in a storage medium, comprising some instructions in order to make a computer equipment (can be personal computer, server, or the network equipment etc.) or processor perform all or part of step of method described in each embodiment of the present invention.And aforesaid storage medium comprises: USB flash disk, portable hard drive, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disc or CD etc. various can be program code stored medium.
The above; be only the specific embodiment of the present invention, but protection scope of the present invention is not limited thereto, is anyly familiar with those skilled in the art in the technical scope that the present invention discloses; change can be expected easily or replace, all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should described be as the criterion with the protection range of claim.
Claims (14)
1. a management method for application programming interface API Calls record, is characterized in that, comprising:
Obtain many API Calls records, each API Calls record in described many API Calls records all at least comprises following attribute information: caller identifies, calls moment Called time and resource use amount, wherein, the caller of described caller mark for representing described API, described Called time is for representing the invoked time information of described API;
According to the Called time of bar API Calls record every in described many API Calls records, determine the metering period that in described many API Calls records, every bar API Calls record is affiliated separately;
According to the charging unit price preset, by being arranged in same metering period in described many API Calls records, there is identical caller mark and the resource use amount with more than two each API Calls record of API Calls record of identical charging unit price carries out overlap-add procedure, and obtain an API Calls record after overlap-add procedure.
2. method according to claim 1, is characterized in that:
According to described charging unit price, the charging result that charging obtains is carried out to a described API Calls record after overlap-add procedure, with, according to described charging unit price, to being positioned at same metering period in described many API Calls records, having identical caller mark and more than two the API Calls records with identical charging unit price carry out the charging result that charging obtains, is identical.
3. method according to claim 1 and 2, is characterized in that,
Each API Calls record in described many API Calls records all also comprises following attribute information: API identifies, and described API mark is for representing invoked API;
The charging unit price that described basis is preset, by being arranged in same metering period in described many API Calls records, there is identical caller mark and the resource use amount with more than two each API Calls record of API Calls record of identical charging unit price carries out overlap-add procedure, and obtain an API Calls record after overlap-add procedure, specifically comprise:
By being arranged in same metering period in described many API Calls records, there is identical caller mark and the resource use amount with more than two each API Calls record of API Calls record that identical API identifies carries out overlap-add procedure, and obtain an API Calls record after overlap-add procedure.
4. method according to claim 3, is characterized in that:
According to described charging unit price, the charging result that charging obtains is carried out to a described API Calls record after overlap-add procedure, with, according to described charging unit price, to being positioned at same metering period in described many API Calls records, having identical caller mark and have more than two API Calls records that identical API identifies and carry out the charging result that charging obtains, is identical.
5. the method according to any one of Claims 1-4, is characterized in that, described method also comprises:
Carry out filtration treatment to described many API Calls records, filtering is arranged in the API Calls record that described many API Calls record charging unit prices are zero.
6., according to the method described in claim 1 to 5, it is characterized in that:
Described charging unit price be call described API unit duration price, call described API unit number of times price, call the unit data flow that described API obtains price or call the price of unit memory space that described API obtains.
7. a management devices for application programming interface API Calls record, is characterized in that, comprising:
Acquiring unit, for obtaining many API Calls records, each API Calls record in described many API Calls records all at least comprises following attribute information: caller identifies, calls moment Called time and resource use amount, wherein, the caller of described caller mark for representing described API, described Called time is for representing the invoked time information of described API;
Determining unit, for the Called time according to bar API Calls record every in described many API Calls records, determines the metering period that in described many API Calls records, every bar API Calls record is affiliated separately;
Administrative unit, for the charging unit price that basis is preset, by being arranged in same metering period in described many API Calls records, there is identical caller mark and the resource use amount with more than two each API Calls record of API Calls record of identical charging unit price carries out overlap-add procedure, and obtain an API Calls record after overlap-add procedure.
8. device according to claim 7, is characterized in that:
According to described charging unit price, the charging result that charging obtains is carried out to a described API Calls record after overlap-add procedure, with, according to described charging unit price, to being positioned at same metering period in described many API Calls records, having identical caller mark and more than two the API Calls records with identical charging unit price carry out the charging result that charging obtains, is identical.
9. the device according to claim 7 or 8, is characterized in that:
Each API Calls record in described many API Calls records all also comprises following attribute information: API identifies, and described API mark is for representing invoked API;
Described administrative unit specifically for by being arranged in same metering period in described many API Calls records, there is identical caller mark and the resource use amount with more than two each API Calls record of API Calls record that identical API identifies carries out overlap-add procedure, and obtain an API Calls record after overlap-add procedure.
10. device according to claim 9, is characterized in that:
According to described charging unit price, the charging result that charging obtains is carried out to a described API Calls record after overlap-add procedure, with, according to described charging unit price, to being positioned at same metering period in described many API Calls records, having identical caller mark and have more than two API Calls records that identical API identifies and carry out the charging result that charging obtains, is identical.
11. devices according to any one of claim 7 to 10, is characterized in that:
Described administrative unit is also for carrying out filtration treatment to described many API Calls records, and filtering is arranged in the API Calls record that described many API Calls record charging unit prices are zero.
12. devices according to any one of claim 7 to 11, is characterized in that:
Described charging unit price be call described API unit duration price, call described API unit number of times price, call the unit data flow that described API obtains price or call the price of unit memory space that described API obtains.
The management system of 13. 1 kinds of application programming interface API Calls records, is characterized in that, comprises the management devices of API gateway, API charging gateway and the API Calls record as described in any one of claim 7 to 12:
Described many API Calls records that described API gateway obtains for generation of the management devices of described API Calls record;
Described API charging gateway is used for an API Calls record after the management devices overlap-add procedure of described API Calls record, carries out charging according to described default charging unit price.
14. management systems according to claim 13, is characterized in that:
The management devices of described API Calls record is integrated in described API gateway, or the management devices of described API Calls record is integrated in described API charging gateway.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510003882.1A CN104506371A (en) | 2015-01-04 | 2015-01-04 | Method and device for management of application programming interface (API) call records |
| PCT/CN2015/099160 WO2016107510A1 (en) | 2015-01-04 | 2015-12-28 | Management method and apparatus for application programming interface (api) calling record |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510003882.1A CN104506371A (en) | 2015-01-04 | 2015-01-04 | Method and device for management of application programming interface (API) call records |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104506371A true CN104506371A (en) | 2015-04-08 |
Family
ID=52948086
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510003882.1A Pending CN104506371A (en) | 2015-01-04 | 2015-01-04 | Method and device for management of application programming interface (API) call records |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN104506371A (en) |
| WO (1) | WO2016107510A1 (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016107510A1 (en) * | 2015-01-04 | 2016-07-07 | 华为技术有限公司 | Management method and apparatus for application programming interface (api) calling record |
| CN108469956A (en) * | 2017-02-23 | 2018-08-31 | 京瓷办公信息系统株式会社 | Image forming apparatus, management server and information processing method |
| CN109428753A (en) * | 2017-08-29 | 2019-03-05 | 西门子公司 | Measuring index acquisition methods, service call record acquisition methods and device |
| CN109787780A (en) * | 2017-11-10 | 2019-05-21 | 华为技术有限公司 | The open functional entity of charging method and ability based on API content |
| CN109949064A (en) * | 2017-12-20 | 2019-06-28 | 北京京东尚科信息技术有限公司 | A kind of open interface calls charging method and device |
| CN111274248A (en) * | 2020-01-19 | 2020-06-12 | 北京金堤科技有限公司 | Charging data generation method and device |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10756911B2 (en) | 2018-05-10 | 2020-08-25 | International Business Machines Corporation | Cost estimation on a cloud-computing platform |
| JP2021099584A (en) | 2019-12-20 | 2021-07-01 | 富士通株式会社 | Service cost calculation device, service cost calculation system, and service cost calculation method |
| CN114679459B (en) * | 2022-05-07 | 2024-03-12 | 阿里巴巴（中国）有限公司 | Cloud function calling method and device |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101401408A (en) * | 2006-03-06 | 2009-04-01 | 思科技术公司 | System and method for generating a unified accounting record for a communication session |
| CN102065057A (en) * | 2009-11-18 | 2011-05-18 | 华为技术有限公司 | Method and server applied to agency service of Widget |
| CN102202281A (en) * | 2010-03-24 | 2011-09-28 | 中兴通讯股份有限公司 | Ticket processing method and system |
| CN102387486A (en) * | 2010-09-06 | 2012-03-21 | 中国移动通信集团河北有限公司 | Method and device for charging general packet radio service (GPRS) partition bill |
| CN102573112A (en) * | 2010-12-07 | 2012-07-11 | 中国电信股份有限公司 | Telecommunication network capability opening method, system and alliance support platform |
| US20120179587A1 (en) * | 2011-01-07 | 2012-07-12 | Gregg Alan Hill | Premium access to open application programming interface systems and methods |
| CN103269479A (en) * | 2013-05-07 | 2013-08-28 | 华为技术有限公司 | Call ticket processing method, device and system |
| CN104144069A (en) * | 2013-05-10 | 2014-11-12 | 中国电信股份有限公司 | Method and device for correlating wireless side call data records and user service behaviors |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101667920B (en) * | 2008-09-03 | 2012-07-25 | 中国移动通信集团上海有限公司 | Charging method and system and ticket generating device |
| CN102779255B (en) * | 2012-07-16 | 2014-11-12 | 腾讯科技（深圳）有限公司 | Method and device for judging malicious program |
| CN104506371A (en) * | 2015-01-04 | 2015-04-08 | 华为技术有限公司 | Method and device for management of application programming interface (API) call records |
-
2015
- 2015-01-04 CN CN201510003882.1A patent/CN104506371A/en active Pending
- 2015-12-28 WO PCT/CN2015/099160 patent/WO2016107510A1/en active Application Filing
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101401408A (en) * | 2006-03-06 | 2009-04-01 | 思科技术公司 | System and method for generating a unified accounting record for a communication session |
| CN102065057A (en) * | 2009-11-18 | 2011-05-18 | 华为技术有限公司 | Method and server applied to agency service of Widget |
| CN102202281A (en) * | 2010-03-24 | 2011-09-28 | 中兴通讯股份有限公司 | Ticket processing method and system |
| CN102387486A (en) * | 2010-09-06 | 2012-03-21 | 中国移动通信集团河北有限公司 | Method and device for charging general packet radio service (GPRS) partition bill |
| CN102573112A (en) * | 2010-12-07 | 2012-07-11 | 中国电信股份有限公司 | Telecommunication network capability opening method, system and alliance support platform |
| US20120179587A1 (en) * | 2011-01-07 | 2012-07-12 | Gregg Alan Hill | Premium access to open application programming interface systems and methods |
| CN103269479A (en) * | 2013-05-07 | 2013-08-28 | 华为技术有限公司 | Call ticket processing method, device and system |
| CN104144069A (en) * | 2013-05-10 | 2014-11-12 | 中国电信股份有限公司 | Method and device for correlating wireless side call data records and user service behaviors |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016107510A1 (en) * | 2015-01-04 | 2016-07-07 | 华为技术有限公司 | Management method and apparatus for application programming interface (api) calling record |
| CN108469956A (en) * | 2017-02-23 | 2018-08-31 | 京瓷办公信息系统株式会社 | Image forming apparatus, management server and information processing method |
| CN108469956B (en) * | 2017-02-23 | 2022-01-11 | 京瓷办公信息系统株式会社 | Image forming apparatus, management server, and information processing method |
| CN109428753A (en) * | 2017-08-29 | 2019-03-05 | 西门子公司 | Measuring index acquisition methods, service call record acquisition methods and device |
| CN109787780A (en) * | 2017-11-10 | 2019-05-21 | 华为技术有限公司 | The open functional entity of charging method and ability based on API content |
| CN109787780B (en) * | 2017-11-10 | 2021-08-31 | 华为技术有限公司 | Charging method based on API content and capability open function entity |
| CN109949064A (en) * | 2017-12-20 | 2019-06-28 | 北京京东尚科信息技术有限公司 | A kind of open interface calls charging method and device |
| CN109949064B (en) * | 2017-12-20 | 2021-09-03 | 北京京东尚科信息技术有限公司 | Open interface call charging method and device |
| CN111274248A (en) * | 2020-01-19 | 2020-06-12 | 北京金堤科技有限公司 | Charging data generation method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2016107510A1 (en) | 2016-07-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104506371A (en) | Method and device for management of application programming interface (API) call records | |
| CN112182655A (en) | Data interaction method among multiple devices and related devices | |
| US7765460B2 (en) | Out-of-band change detection | |
| CN108881495A (en) | Resource allocation methods, device, computer equipment and storage medium | |
| CN110321226A (en) | Automatic scalable appearance method, apparatus, host and the storage medium of host | |
| CN104115447A (en) | Allowing destroy scheme configuration method and device under cloud computing architecture | |
| US9652812B2 (en) | Obtaining software asset insight by analyzing collected metrics using analytic services | |
| CN110008021A (en) | EMS memory management process, device, electronic equipment and computer readable storage medium | |
| CN104699363A (en) | Window interface display method and system | |
| CN104424015A (en) | Virtual machine management method and virtual machine management device | |
| CN109002281A (en) | Project development method, apparatus and user terminal based on platform assembly | |
| CN110708369A (en) | File deployment method and device for equipment nodes, scheduling server and storage medium | |
| CN104216902A (en) | Paging data loading method, device and system based on server paging | |
| CN101388036A (en) | Data table summarizing method and device | |
| CN109582439A (en) | DCN dispositions method, device, equipment and computer readable storage medium | |
| CN103150159A (en) | Identifier generation using named objects | |
| CN104657216B (en) | The resource allocation methods and device of a kind of resource pool | |
| CN108491294A (en) | A kind of database backup method, apparatus and system | |
| CN102591714B (en) | Process calling method, system and application server | |
| WO2016013020A1 (en) | Event processing systems and methods | |
| CN114675931A (en) | Resource monitoring method and monitoring device for integrated platform instance | |
| CN105787791A (en) | Service request processing method and apparatus | |
| CN114911479A (en) | Interface generation method, device, equipment and storage medium based on configuration | |
| CN104424594A (en) | Data checking method and system | |
| CN107741887A (en) | A kind of communication interaction method and apparatus of inter-module |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20150408 |