Embodiment
The following description and drawings illustrate specific embodiment of the invention scheme fully, to enable those skilled in the art to put into practice them.Other embodiments can comprise structure, logic, electric, process and other change.Embodiment only represents possible change.Unless explicitly requested, otherwise independent parts and function are optional, and the order of operation can change.The part of some embodiments and feature can be included in or replace part and the feature of other embodiments.The scope of embodiment of the present invention comprises the gamut of claims, and all obtainable equivalent of claims.In this article, these embodiments of the present invention can be represented with term " invention " individually or always, this is only used to conveniently, and if in fact disclose the invention more than, be not the scope that automatically will limit this application is any single invention or inventive concept.
Fig. 1 shows the schematic flow sheet of the method for a kind of aggregate response of the embodiment of the present invention,
As shown in Figure 1, in some illustrative embodiments, described method, can be applied to group controlling party, comprises following step:
Step S101, according to the mark of member whole in group resource, Requests routing initiator sent is to each described member;
Step S102, when arriving polymerization time or receive response that described whole member sends, the response polymerization described member received sent sends to described initiator;
Wherein, described group of controlling party refers to the node created for carrying out the described group of resource that batch controls to member, and described group of controlling party both can be application, also can be entity (such as unit, terminal etc.); Described initiator refers to node member in described group of resource being carried out to batch control, similar with described group of controlling party, and described initiator both can be application, also can be entity;
In described group of resource, store the mark of whole member, when initiator calls this group resource, the Requests routing that initiator sends by group controlling party, to each member, performs corresponding operation to make each member according to the content in described request;
In above process, specifically describe and trigger described group of controlling party and the response of polymerization sent to the process of initiator to be: when arrive store indicate corresponding polymerization time with the request of carrying in described request or receive the response that described whole member sends; Namely in this scheme, even if the response that the described group of whole member of controlling party unsuccessful reception in polymerization time sends, group controlling party also can when arriving polymerization time, trigger the operation that polymerization sends, the response that member in the group resource received sends condensed together, unification sends to described initiator; Described polymerization time can be that initiator carries according to demand in the request, also can be default default value, such as organize controlling party preset or user group controlling party arrange or group asset creation person arrange etc.;
Above-described embodiment avoids group controlling party and the response of polymerization cannot be sent to the situation of initiator occur; In addition by arranging polymerization time, can make initiator within the time of expection, receive the response of reply; Prevent because the unrestricted wait of group controlling party, increase the operating load of system, cause the wasting of resources.
In some illustrative embodiments, the request instruction of carrying in described request, it is a mark being specifically designed to this request of mark, when member after receiving the request, by carrying this request instruction in the response, to make group controlling party by identifying this request instruction, know that described response corresponds to described request;
In some illustrative embodiments, described polymerization time can be time period (as 3 minutes), also can be time point (as PM5:00); If polymerization time is time point, then, when the system time organizing controlling party arrives this time point, trigger the operation that polymerization sends;
If the restriction of described polymerization time is the time period, then, after by the described Requests routing that initiator is sent to each described member, also comprise:
After the response that the described member received first sends, if judge the described request instruction that described response is carried, triggered timer starts timing according to described polymerization time; Or,
To after each described member after receiving the request that described initiator sends or at the Requests routing described initiator sent, triggered timer starts timing according to described polymerization time;
Above embodiment described when triggered timer starts timing, such as, can be after first time receives the response of member's transmission, and according to the request instruction of carrying in response, triggered timer starts timing according to polymerization time; Or group controlling party is after the request receiving initiator's transmission, and just triggering timer starts timing; Or after Requests routing is given all members according to group resource by group controlling party, triggered timer starts timing;
When described timer then, the response polymerization described member received sent sends to described initiator;
In some illustrative embodiments, described request carries the request instruction for identifying this request; Before the described Requests routing that initiator is sent to each described member, also comprise: pairing is carried out in described request instruction and described polymerization time and stores; Namely can be understood as and request instruction and polymerization time are bound, a request instruction corresponds to a polymerization time, controls to find corresponding polymerization time according to request instruction to make group;
Further, described by described request instruction and described polymerization time carry out pairing storage after, also comprise:
According to the described request instruction of carrying in the response that the described member received sends, inquiry and described request indicate the described polymerization time matching and store;
Such as: after the response receiving described member transmission first, according to the described request instruction of carrying in described response, inquire described polymerization time, and then triggered timer starts timing according to this polymerization time;
In some illustrative embodiments, described request carries described polymerization time, then described by described request instruction and described polymerization time carry out pairing storage, comprising:
The described polymerization time extracted from described request and described request instruction are carried out pairing store; Or,
If do not carry described polymerization time in described request, and described request carries the mark of described initiator, then described by described request instruction and described polymerization time carry out pairing storage, comprising:
According to the mark of the described initiator that described request is carried, described request instruction is carried out pairing with the described polymerization time corresponding with the mark of described initiator found and stores; Namely stored the polymerization time corresponding with initiator described group of controlling party, this process can be realized by following method:
The group resource of described group of controlling party foundation comprises polymerization time attribute, and this is a newly-increased attribute, is specifically designed to and records different initiators and corresponding polymerization time, after the request receiving described initiator transmission, also comprises:
The mark of described initiator and described polymerization time are matched and is stored in described polymerization time attribute;
If described polymerization time is carried by described request, then the described mark of described initiator and described polymerization time pairings is stored in described polymerization time attribute, comprising:
The mark pairing of the described polymerization time extracted from described request and described initiator is stored in described polymerization time attribute; Or,
If described request does not carry described polymerization time, then the described mark of described initiator and described polymerization time pairings is stored in described polymerization time attribute, comprising:
Judge whether stored the described polymerization time corresponding with the mark of described initiator in described polymerization time attribute, if so, then undo; If not, then use default default value as described polymerization time, and described polymerization time and described request instruction pairing are stored in described polymerization time attribute;
In some illustrative embodiments, the described mark pairing by the described polymerization time extracted from described request and described initiator is stored in described polymerization time attribute, comprising:
Upgrade in described polymerization time attribute the polymerization time corresponding with the mark of described initiator stored; Namely, after receiving up-to-date polymerization time, the polymerization time stored is deleted, and up-to-date polymerization time is stored, be equivalent to the process that an information covers in original polymerization time attribute.
With three specific embodiments, this programme is described below, relates to Originator (initiator), GroupHostingCSE (group controlling party) and MemberHostingCSE (member) in this embodiment; Originator is by sending request to GroupHostingCSE, carry out batch to all MemberHostingCSE in GroupHostingCSE to control, GroupHostingCSE is after the response receiving MemberHostingCSE, and polymerization sends to Originator; As shown in Figure 2, in this process, GroupHostingCSE uses default default value as the value of polymerization time (groupaggregationtime, gat), and gat can be the time period or be time point; Detailed process is as follows:
Step S201, Originator send request to GroupHostingCSE;
Request instruction (Requestidentifier, ri) is carried in request;
Step S202, GroupHostingCSE by Requests routing to MemberHostingCSE;
GroupHostingCSE finds the mark of all MemberHostingCSE in group resource, then the request that Originator sends is sent to each MemberHostingCSE successively; In the process of distribution, need in request to carry ri;
Step S203, MemberHostingCSE send to GroupHostingCSE by the response of request;
Described response is carried at the ri carried in the request received in step S202;
When step S204, GroupHostingCSE receive first response corresponding with ri, according to the default value gat preset, start timing;
If gat is the time period, when GroupHostingCSE receives first response corresponding with ri, use default default value as gat, and start timing, lock this pairing, in order to avoid this timer of repeated priming (another, timer also can start timing before step S203) simultaneously; Step S204 is optional step, if gat is time point, does not then do any operation, because GroupHostingCSE can arrive rear triggered step S205 at time point automatically;
Step S205, trigger action;
GroupHostingCSE when following situation, triggered step S206:
A) gat is the time period: interior during timer, have received the response of all members;
B) gat is the time period: timer then;
C) gat is time point: at this moment before point, have received all members response;
D) gat is time point: arrive this time point;
The response of polymerization is sent to initiator by step S206, GroupHostingCSE.
Fig. 3 is the method flow schematic diagram of another embodiment of the present invention, and the difference of this embodiment and above-described embodiment is, gat is that the request sent to GroupHostingCSE by Originator is carried, and as shown in Figure 3, detailed process is as follows:
Step S301, Originator send request to GroupHostingCSE;
Polymerization time (groupaggregationtime, gat) and request instruction (Requestidentifier, ri) of the time responded for limit polymerization are carried in request; Gat can be the time period or be time point;
Step S302, ri and gat match storage;
GroupHostingCSE extracts ri and gat in request, and pairing stores;
Step S303, GroupHostingCSE by Requests routing to MemberHostingCSE;
GroupHostingCSE finds the mark of all MemberHostingCSE in group resource, then the request that Originator sends is sent to each MemberHostingCSE successively; In the process of distribution, need in request to carry ri;
Step S304, MemberHostingCSE send to GroupHostingCSE by the response of request;
Described response is carried at the ri carried in the request received in step S303;
Step S305, GroupHostingCSE, when receiving first response corresponding with ri, find corresponding gat by ri, and start timing;
If gat is the time period, when GroupHostingCSE receives first response corresponding with ri, find corresponding gat by ri, and start timing, lock this pairing, in order to avoid this timer of repeated priming (another, timer also can start timing before step S303) simultaneously; Step S305 is optional step, if be time point, does not then do any operation, because GroupHostingCSE can arrive rear triggered step S306 at time point automatically;
Step S306, trigger action;
GroupHostingCSE when following situation, triggered step S307, and the pairing of deleting ri and gat:
A) gat is the time period: interior during timer, have received the response of all members;
B) gat is the time period: timer then;
C) gat is time point: at this moment before point, have received all members response;
D) gat is time point: arrive this time point;
The response of polymerization is sent to initiator by step S307, GroupHostingCSE.
Fig. 4 is the method flow schematic diagram of another embodiment of the present invention, the difference of this embodiment and above-described embodiment is, add aggregationTime polymerization time attribute in the group resource that group controlling party creates, this attribute can comprise: a) the acquiescence polymerization time of GroupHostingCSE setting; B) polymerization time that the mark of initiator is corresponding with initiator; As shown in Figure 4, detailed process is as follows:
Step S401, Originator send request to GroupHostingCSE;
Request carry Originator mark ID, for limit polymerization response time polymerization time (groupaggregationtime, gat) and request indicate (Requestidentifier, ri), gat is the time period;
The pairing of step S402, ID and gat stores, ri and gat matches storage;
GroupHostingCSE extracts ID, ri and gat in request, if do not have the pairing of this ID and gat in aggregationTime attribute, then ID and gat pairing is stored in attribute aggregationTime, and ri and gat pairing is stored; If existing, then upgrade the gat of ID pairing therewith in aggregationTime attribute;
Step S403, GroupHostingCSE by Requests routing to MemberHostingCSE;
GroupHostingCSE finds the mark of all MemberHostingCSE in group resource, then the request that Originator sends is sent to each MemberHostingCSE successively; In the process of distribution, need in request to carry ri;
Step S404, MemberHostingCSE send to GroupHostingCSE by the response of request;
Described response is carried at the ri carried in the request received in step S403;
Step S405, finds corresponding gat by ri, and starts timing;
When GroupHostingCSE receives first response corresponding with ri, find corresponding gat by ri, and start timing, lock this pairing simultaneously, in order to avoid this timer of repeated priming (another, timer also can start timing before step S403);
Step S406, trigger action;
GroupHostingCSE when following situation, triggered step S407, and the pairing of deleting ri and gat:
A) interior during timer, have received the response of all members;
B) timer then;
The response of polymerization is sent to initiator by step S407, GroupHostingCSE;
In some illustrative embodiments, if do not carry gat in step S401, then in step S402, GroupHostingCSE extracts ID, the ri in request, the gat of ID pairing is therewith searched in aggregationTime, and gat and ri pairing is stored, if do not found, then Use Defaults and replace gat, and this default value is stored as gat and ri pairing.
Fig. 5 shows the structural representation of the device 500 of a kind of aggregate response of the embodiment of the present invention,
In some illustrative embodiments, device 500, comprising:
Transmitting element 501, for the mark according to member whole in group resource, the Requests routing that the initiator received by receiving element 502 sends is to each described member;
Feedback unit 503, for when arriving polymerization time or receive response that described whole member sends, the response polymerization described member received sent sends to described initiator;
Described polymerization time is the default value carrying in the described request sent by described initiator or preset;
In some illustrative embodiments, described request carries the request instruction for identifying this request; Device 500, also comprises:
Memory cell 504, before Requests routing initiator sent for described transmitting element 501 to each described member, carries out pairing storage by described request instruction and described polymerization time;
In some illustrative embodiments, device 500, also comprises:
Query unit 505, for described memory cell 504 by described request instruction and described polymerization time carry out pairing storage after, according to the described request instruction of carrying in the response that the described member received sends, inquiry and described request indicate the described polymerization time matching and store;
In some illustrative embodiments, device 500, also comprises:
First timing unit 506, the Requests routing described initiator sent after receiving for described receiving element 502 request that described initiator sends or for described transmitting element 501 is to each described member, and triggered timer starts timing according to described polymerization time; Or,
Second timing unit 507, for described transmitting element 501 by after described Requests routing initiator sent to each described member, after the response receiving described member transmission first, triggered timer starts timing according to described polymerization time;
In some illustrative embodiments, if described request carries described polymerization time, then described memory cell 504, comprising:
First storing sub-units 5041, stores for the described polymerization time extracted from described request and described request instruction are carried out pairing; Or,
If described request does not carry described polymerization time, and described request carries the mark of described initiator, then described memory cell 504, comprising:
Second storing sub-units 5042, for the mark of described initiator of carrying according to described request, carries out pairing by described request instruction with the described polymerization time corresponding with the mark of described initiator found and stores;
In some illustrative embodiments, described group of resource comprises polymerization time attribute, and device 500, also comprises:
Template(-let) 508, after receiving the request of described initiator transmission, matches the mark of described initiator and described polymerization time and is stored in described polymerization time attribute for described receiving element 502;
If described polymerization time is carried by described request, then described template(-let) 508, comprising:
First attribute subelement 5081, for being stored in described polymerization time attribute by the pairing of the mark of the described polymerization time extracted from described request and described initiator; Or,
If described request does not carry described polymerization time, then described template(-let) 508, comprising:
Second attribute subelement 5082, for judging whether stored the described polymerization time corresponding with the mark of described initiator in described polymerization time attribute, if so, then undo; If not, then use described default default value as described polymerization time, and described polymerization time and described request instruction pairing are stored in described polymerization time attribute;
In some illustrative embodiments, described first template(-let) 5081, comprising:
Updating block 50811, for upgrading in described polymerization time attribute the polymerization time corresponding with the mark of described initiator stored.
Adopt above-described embodiment, following effect can be reached:
Avoid because of many reasons causes organizing controlling party cannot by the responsive feedback of being polymerized to initiator;
In addition by arranging polymerization time, can make initiator within the time of expection, receive the response of reply;
Prevent because the unrestricted wait of group controlling party, increase the operating load of system, cause the wasting of resources.
Those skilled in the art it is also understood that various illustrative box, module, circuit and the algorithm steps combining embodiment herein and describe all can be embodied as electronic hardware, computer software or its combination.In order to the interchangeability between hardware and software is clearly described, all carry out usually describing around its function to various illustrative parts, frame, module, circuit and step above.Be embodied as hardware as this function or be embodied as software, the design constraint depending on specific application and whole system is applied.Those skilled in the art for each application-specific, can realize described function in the mode of accommodation, but, thisly realize decision-making and should not be construed as and deviate from protection range of the present disclosure.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.