CN100476739C - Method for managing group task - Google Patents

Method for managing group task Download PDF

Info

Publication number
CN100476739C
CN100476739C CNB2007101309084A CN200710130908A CN100476739C CN 100476739 C CN100476739 C CN 100476739C CN B2007101309084 A CNB2007101309084 A CN B2007101309084A CN 200710130908 A CN200710130908 A CN 200710130908A CN 100476739 C CN100476739 C CN 100476739C
Authority
CN
China
Prior art keywords
task
tasks
work
carry out
assembly
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CNB2007101309084A
Other languages
Chinese (zh)
Other versions
CN101110041A (en
Inventor
朱希
严克平
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Asialnfo Technology (Nanjing) Co., Ltd.
Original Assignee
LINKAGE SYSTEM INTEGRATION CO Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by LINKAGE SYSTEM INTEGRATION CO Ltd filed Critical LINKAGE SYSTEM INTEGRATION CO Ltd
Priority to CNB2007101309084A priority Critical patent/CN100476739C/en
Publication of CN101110041A publication Critical patent/CN101110041A/en
Application granted granted Critical
Publication of CN100476739C publication Critical patent/CN100476739C/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The method of group task management adopts the GTM module of group task management to defend the progress in the UNIX operating system, which can configure the information parameters form via the time scanning, so as to execute the qualified jobs. The job is composed of one or a plurality of tasks, but each task is an independent logical unit. When all the tasks are completed, the job is deemed to be done. The sequence of the tasks is pre-set by the module, which is strictly based on the task execution route. Each job is only provided with one task route, while each task route is composed of a plurality of task paths. The sequence of the tasks is in series or in the mix of series/parallel arrangement. The procedures of the tasks in series are explained as below: only when the task Ti is completed, the task Ti +1 can be executed; when the last Ti +1 is completed, the final procedure TE can be executed; when the TE is executed, the job is completed. i is a natural number.

Description

The method of managing group task
Technical field
The present invention relates to the method for computer operating system task management, the method for particularly a kind of managing group task (GTM) and according to this assembly of making.
Background technology
The managing group task assembly is the finger daemon that operates under the UNIX operating system environment.Be similar to crontab process under the unix, go to carry out the work of satisfying executive condition by timing scan configuration information operational factor table.Work is made up of one or more tasks, and each task all is an independently logical block, when all tasks all are finished, works and just finishes.Assembly is done in advance definition in proper order to task executions in the work; The assembly implementation will be carried out circuit (route) in strict accordance with task and carry out.Every work has only a task route, and each task route is to be made of many task paths.Under unix, can dispose a plurality of tasks, but these tasks are independent of each other all by crontab.
Summary of the invention
The present invention seeks to: at deficiency of the prior art, the present invention proposes the method and the assembly of a kind of managing group task (GTM), each task route is to be made of many task paths, under unix, can dispose a plurality of tasks by crontab, can serial, serial/parallel row mixes and execute the task.
Technical scheme of the present invention is: the method for managing group task, employing operates in the managing group task GTM assembly of the finger daemon under the UNIX operating system environment, go to carry out the work of satisfying executive condition by timing scan configuration information operational factor table, work is made up of one or more tasks, each task all is an independently logical block, when all tasks all are finished, work is just finished, and assembly is done in advance definition in proper order to task executions in working; The assembly implementation will be carried out route in strict accordance with task and carry out, and every work has only a task route, and each task route is to be made of many task paths, and task executions is that serial or serial/parallel row mix in proper order:
1) serial is carried out: dispose a plurality of tasks by crontab under unix, these tasks are independent of each other, the order that managing group task GTM assembly is carried out by configuration task is carried out a plurality of tasks with the mode serial of chained list, and a back task executions must be based upon on the basis that previous task runs succeeded; Have only as task T iCould carry out T after complete I+1As last T I+1Could carry out end step TE after complete; When TE was performed, this work is performed to be finished, and i is a natural number;
2) mix execution: under unix, dispose a plurality of tasks by crontab, these tasks are independent of each other, the order that managing group task GTM assembly is carried out by configuration task is carried out a plurality of tasks in the mode of string and mixing, i.e. a plurality of tasks of concurrent execution on the basis of the intact task of successful execution wait for that multitask finishes string and type multitask hybrid processing mechanism that the some independent tasks of execution are continued in the back. and a back task executions must be based upon on the basis that previous or a plurality of tasks run succeeded; Have only after all parallel tasks are complete and could carry out next task, by that analogy, after the front parallel task is complete, could carry out the task of back with serial mode, finish, carry out TE again up to all tasks, when TE was performed, this work is performed to be finished;
Configuration task: a job is needed 3 parameter lists at least by complete definition, is respectively: worksheet, routing table, task list; Described assembly is alarmed when the work of overrun or mistake takes place; The mode of alarm adopts note or mail; Described short message alarm is provided with and allows to alarm start and end time; The interval time that sends alarm message is controlled.
Effect of the present invention is: compared with prior art, the assembly of this method and formation can carry out serial, serial/parallel row mixing is executed the task.
Description of drawings
Fig. 1 is the work serial routing diagram of executing the task
Fig. 2 is that the serial/parallel row of work mixes the routing diagram of executing the task
Fig. 3 is the state conversion figure of task node
Fig. 4 is a managing group task GTM assembly assumption diagram
Embodiment
The invention will be further described below in conjunction with accompanying drawing and embodiment.
1, serial is carried out.Under unix, can dispose a plurality of tasks by crontab, but these tasks all are independent of each other, managing group task (GTM) assembly can be carried out a plurality of tasks by the order that configuration task is carried out with the mode serial of chained list, and a back task executions must be based upon on the basis that previous task runs succeeded.
2, mix execution.Under unix, can dispose a plurality of tasks by crontab, but these tasks all are independent of each other, managing group task (GTM) assembly can be carried out a plurality of tasks by the order that configuration task is carried out in the mode of string and mixing, promptly can be on the basis of the intact task of successful execution a plurality of tasks of concurrent execution, wait for that multitask finishes string and type multitask hybrid processing mechanism that the some independent tasks of execution are continued in the back. and a back task executions must be based upon on the basis that previous or a plurality of tasks run succeeded.
3, alarm.By alarm, the work that overrun or mistake take place is reminded to relevant responsible official, so that further find out alarm cause, deal with problems by the mode of manual intervention; Can be undertaken by the mode of note and mail.For short message alarm permission can be set and alarm start and end time,, can send note to the phone number of appointment only in this following period of time.Also can accomplish to control for the density of note, require in the time range that allows alarm, to send alarm message once, allow the people produce the detest sense in order to avoid note is too concentrated every how long.
Configuration instruction: a job is needed 3 parameter lists at least by complete definition, is respectively: worksheet, routing table, task list.
The work definition: the simple understanding of work is exactly the thing that will do.Usually the effective ways of handling complex thing are to divide and rule, and becoming huge, a numerous and diverse job analysis a plurality of tasks with clearly defined objective, easy realization to finish is the comparison appropriate methods.Little task after these decompose has been done, and this work also just has been done so.
Explanation of field: the ID of every work is the unique identification of a job of difference; Every work is all by work title, the subsystem under the work, the state of work, carry out type, execution time last time, this execution time, Time Of Next execution, in the time interval, whether alarm the priority of work, overtime switch setting, work comes into effect the time, and the end-of-job entry-into-force time, the work service marking is formed.Only support two kinds to carry out types in present managing group task assembly: a kind of be that regularly type is a kind of is to trigger type.For the timing type of work, when next time, the execution time arrived, assembly just automatically performed this work; For triggering type of work, when needing to carry out, need its execution of manual activation at every turn.When the execution type of this work is to trigger type, Time Of Next execution so, time interval field does not need definition.If the execution type of work is regularly a type, then need to dispose Time Of Next execution, the time interval.When Time Of Next execution is carried out for the first time, by manual configuration, later on by the configuration at interval of the automatic modification time of system.
Fixed time interval is represented: to the execution time between two tasks at interval can by, month, week, day, hour, minute.Example:
Carried out once in every month: add_months (next_date, 1)
Per three weeks carry out once: next_date+3*7
Carried out once in per two days: next_date+2
Carried out once in per three hours: next_date+3/24
Carried out once in per 40 minutes: next_date+40/ (24*60)
Overtime switch setting: when its value is 0, represent that it closes overtime setting; (promptly after this work surpasses timeout minute working time, the state of this work will change into the overrun state by normal operating condition otherwise for opening overtime switch.If alarm is masked as ' 1 ', then can alarm the work of overrun.This moment need be at an alarm of parameter list (td_s_alarm) configuration record.
The state of task node transforms, with reference to figure 3, and according to the assembly of Fig. 4.
Task definition: every task is the logic component units that constitutes a job.Every task all has own uniquely identified ID, task names, and package types, the plug-in unit name, channel number comes into effect the time, finishes the entry-into-force time, the sign that comes into force, whether card address encrypts link information, connects user name, connects password, connects compositions such as SID.Can be applied in the different work for same task, that is to say that it can be shared by one or more work.A typical example in the managing group task assembly, defines two system-level tasks; They are used to represent essential in an all working beginning task (ID is 0) and one end task (ID is-1).They exist as virtual node in the work route, and all routes all have from beginning task node and begin to carry out, and carry out from end node and finish whole work.The managing group task assembly is supported two kinds of package types at present: a kind of is background application or shell script under the UNIX; A kind of is storing process.In the plug-in unit name,, then can comprise the absolute path of appointment in the plugin name if package types is background application or shell script; Otherwise, search and carry out under the shell path of appointment in assembly.As: shell script l.sh, in the plug-in unit name, promptly can be configured to, also can be configured to l.sh.A kind of for the back, only under the work at present catalogue of managing group task or specific shell catalogue, search and carry out.
Channel number exists as task fixed delivery parameter.It goes to explain by managing group task assembly user of service configuration and by corresponding storing process or background application (comprising the shell script).
For example, in the application of BOSS1.0, when the data volume of a table is very big, usually these record data are carried out packet transaction; You can allow specific channel number task handle the particular group data, and (task of 10 passages [numbering from 0 to 9] goes to handle 0 to 9999 group data, and then 0 passage is handled 0-999 group data, and 1 passage is handled the 1000-1999 data, by that analogy).For another example, the storing process that arrearage is handled comprises defaulting subscriber, the pre-pin of arrearage number, arrearage pin function; These functions are combined in the storing process, at this moment can allow storing process explain and use different functions by be configured to different numerical value at channel number.
It is that storing process is provided with that card address is primarily aimed at task type.For non-storing process type, it must be configured to " LOCAL ", because at present performed shell script of managing group task assembly or background application prerequisite be they must with the assembly management assembly on same application server, can't support interdepartmental system to carry out.If task type is a storing process, can be by being configured to " REMOTE ", to reach function expansion: can move the storing process that belongs to different user under the same database instance; Can move the storing process under the disparate databases example.Otherwise, when the position is configured to " LOCAL ", can only moves with the core parameter table and belong to storing process under the same user.When task type is storing process and card address during for " REMOTE ", whether encrypts link information, connect user name, connect password, to connect SID just meaningful.When ISENCRYPT is " NO ", connect the user of database, password, SID are that the form with plain code is kept in the corresponding task; Otherwise, will preserve with the form of encrypting. and the definition of storing process must have fixing parameter to import, spread out of form into, the return code of v_resultcode storing process; The return message of v_resultinfo storing process.Please see Command Line Parsing in detail. do not need to do affairs control in storage, the control of affairs is that realize the outside of storing process.
Route: each work all corresponding a unique execution route.The master control process is carried out satisfying condition of task according to the task of showing in the route successively execution sequence.Last virtual ending task during node in carrying out route is indicating that whole work finishes, and the state of at this moment working is got back to ready state from running status, waits for the arrival of Time Of Next execution.The route classification, route is carried out simple classification:
I) serial route is with reference to figure 1:TB-〉T1-〉T2-〉T3-〉T4-〉T5-〉TE
In above-mentioned work routing diagram, have only after task Ti (i=1-4) is complete and could carry out Ti+1; After last Ti+1 (being T5) is complete, could carry out TE; When TE is performed, think just that this work is performed to finish.The task of composition work is held according to route serial sequentially
II) parallel route: task T1, T2, T3, T4, the concurrent execution of T5.After Ti (i=1-5) is complete, could carry out TE.When TE is performed, think just that this work is performed to finish.
III) mix route
In above-mentioned work routing diagram, task T1, T2, the concurrent execution of T4.Have only as task T1, could carry out T3 after T4 is complete; Have only the T2 of working as, could carry out T5 after T4 is complete; After T3 and T5 are complete, could carry out TE.When TE is performed, think just that this work is performed to finish.No matter (with reference to the configuration of arrearage data generation work in the ucr_yy01_kf.td_s_work table) is any work routing diagram, all has two virtual task nodes in the task of forming work.Any route all is to begin the summit from virtual beginning task node as route, with virtual end node as the route end vertex.Oriented line arrive another task node from a task node is called directed edge (directed edge).Each bar directed edge constitutes a record in the routing table in the work routing diagram.In the work routing diagram, many directed edges that point to same task node have identical control information (promptly being performed the control information of task).These control informations comprise: state, process ID, beginning execution time, finish the execution time, whether overtime, timeout interval is set, is converted into the time interval of status of fail, overtime action code, failure action code, failure retry control number of times, current failure retry control number of times, the last failure retry time, the failure retry time interval from timeout mode.In the managing group task assembly, the directed edge that points to same task node may be many, and control information is redundant in the configuration of work routing table on these directed edges, but necessary.
With reference to figure 3, the state of task node transforms figure, and state comprises: ready (S_PREPARED), normal operation (S_RUNNING), overrun (S_TORUNNING), retry operation (S_REDORUNNING), normal termination (S_END), jump out ends (S_SKIPEND), (S_FAULT) fails.
In the life cycle for some work, these states can all not occur; And the appearance of some state of task node be with directed edge on control information be provided with relation.As, in control information, be not provided with overtimely, then the S_TORUNNING state can not appear in the task node of this directed edge indication.Time institute takes alarm relevant with the failure strategy to carrying out this node with you in the appearance of some state of task node.Process ID is the subprocess ID when carrying out this task node.If this node is the virtual node that ends task, then this process ID is the master control Parent process ID.Beginning execution time and end execution time are write down this task node from beginning to carry out the time keeping that finishes.Whether be provided with overtime is to make restriction working time for this node.When overtime this restriction of task execution time (being timeout interval), then the state of this task will be transformed into the overrun state.If be not provided with, then do not have the overrun state.For the task of overrun state, you can determine to allow it always " overtime " go down, also can allow it arrive some threshold values (promptly being converted into the time interval of status of fail) and change into status of fail automatically from timeout mode.This " decision " depends on the overtime action code that you dispose.In overtime action code, TC_NOTRANSIT is can this node overtime always, up to its failure or finish; TC_TRANSIT can allow and " come to a halt " after this node overrun a period of time at this point.For the failure action code be to the failure processing policy: ignore (giving tacit consent to this task node runs succeeded); Retry (limited or unlimited trial).
When the failure action code was retry, the retry of then failing control number of times, current failure retry control number of times, the last failure retry time, the failure retry time interval worked.Failure retry control number of times then is the unlimited failure of attempting, till this task successful execution smaller or equal to 0.
Alarm: by alarm, the work that overrun or mistake take place is reminded to relevant responsible official,, dealt with problems by the mode of manual intervention so that further find out alarm cause; Can be undertaken by the mode of note and mail.For short message alarm permission can be set and alarm start and end time,, can send note to the phone number of appointment only in this following period of time.Also can accomplish to control for the density of note, require in the time range that allows alarm, to send alarm message once, allow the people produce the detest sense in order to avoid note is too concentrated every how long.Each bar alarm configuration parameter belongs to a certain specific work.When work is in overrun or error status, then can according to work whether the alarm sign determines whether sending alarm notification to the user.Give notice to the user and to depend on the alarm parameter table.It comprises work ID, Alarm ID, alarm mode, the last alarm time, alarm at interval, allow the alarm start time, allow alarm concluding time, Mobile Directory Number, e-mail address, the alarm compositions such as sign that whether come into force.The alarm mode of assembly support at present: a kind of is short message mode; Another kind is a lettergram mode.Assembly does not guarantee that the user who is alarmed necessarily receives alarm notification information; It only inserts relevant warning information in the corresponding alarm interface table, as the short message interface table, and is finished the processing of interface message by relevant interface handling procedure.Alarm interlude unit is minute.Allowing the alarm start time and allowing the form of alarm concluding time is the format string of hh24mi, as, allow from morning 08:00 to evening 9:00 during this period of time in
To user's alarm notification information of sending short messages, its time corresponding format string is respectively: " 0800 ", " 2100 ".The last alarm time is that assembly is safeguarded when alarm automatically, does not need manual intervention.When the user does not wish to receive alarm notification information, he can be set to the alarm sign that whether comes into force not come into force.

Claims (1)

1, the method for managing group task, employing operates in the managing group task GTM assembly of the finger daemon under the UNIX operating system environment, go to carry out the work of satisfying executive condition by timing scan configuration information operational factor table, work is made up of one or more tasks, each task all is an independently logical block, when all tasks all are finished, work is just finished, and assembly is done in advance definition in proper order to task executions in working; The assembly implementation will be carried out route in strict accordance with task and carry out, and every work has only a task route, and each task route is to be made of many task paths, it is characterized in that task executions is that serial or serial/parallel row mix in proper order:
1) serial is carried out: dispose a plurality of tasks by crontab under unix, these tasks are independent of each other, the order that managing group task GTM assembly is carried out by configuration task is carried out a plurality of tasks with the mode serial of chained list, and a back task executions must be based upon on the basis that previous task runs succeeded; Have only as task T iCould carry out T after complete I+1As last T I+1Could carry out end step TE after complete; When TE was performed, this work is performed to be finished, and i is a natural number;
2) mix execution: under unix, dispose a plurality of tasks by crontab, these tasks are independent of each other, the order that managing group task GTM assembly is carried out by configuration task is carried out a plurality of tasks in the mode of string and mixing, i.e. a plurality of tasks of concurrent execution on the basis of the intact task of successful execution, wait for that multitask finishes string and type multitask hybrid processing mechanism that the some independent tasks of execution are continued in the back, and a back task executions must be based upon on the basis that previous or a plurality of tasks run succeeded; Have only after all parallel tasks are complete and could carry out next task, by that analogy, after the front parallel task is complete, could carry out the task of back with serial mode, finish, carry out TE again up to all tasks, when TE was performed, this work is performed to be finished;
Configuration task: a job is needed 3 parameter lists at least by complete definition, is respectively: worksheet, routing table, task list;
Described assembly is alarmed when the work of overrun or mistake takes place; The mode of alarm adopts note or mail; Described short message alarm is provided with and allows to alarm start and end time; The interval time that sends alarm message is controlled.
CNB2007101309084A 2007-08-23 2007-08-23 Method for managing group task Active CN100476739C (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CNB2007101309084A CN100476739C (en) 2007-08-23 2007-08-23 Method for managing group task

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CNB2007101309084A CN100476739C (en) 2007-08-23 2007-08-23 Method for managing group task

Publications (2)

Publication Number Publication Date
CN101110041A CN101110041A (en) 2008-01-23
CN100476739C true CN100476739C (en) 2009-04-08

Family

ID=39042122

Family Applications (1)

Application Number Title Priority Date Filing Date
CNB2007101309084A Active CN100476739C (en) 2007-08-23 2007-08-23 Method for managing group task

Country Status (1)

Country Link
CN (1) CN100476739C (en)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102508716B (en) * 2011-09-29 2015-04-15 用友软件股份有限公司 Task control device and task control method
US20130085798A1 (en) * 2011-09-30 2013-04-04 Varian Medical Systems, Inc. Systems and methods for implementing medical workflow
CN106708481B (en) * 2015-07-30 2021-06-29 北京京东尚科信息技术有限公司 Method for controlling task execution
CN105446808B (en) * 2015-11-12 2019-05-21 国云科技股份有限公司 A kind of method that combined task completes complex task
CN106712924B (en) * 2015-11-16 2021-03-19 方正国际软件(北京)有限公司 Method and device for realizing universal time sequence communication
CN107241205A (en) * 2016-03-28 2017-10-10 阿里巴巴集团控股有限公司 abnormality monitoring method and device
CN106354370B (en) * 2016-08-31 2019-06-28 金现代信息产业股份有限公司 Emergency drilling system exchange method
CN110109740B (en) * 2019-05-08 2021-08-10 宜人恒业科技发展(北京)有限公司 Crontab command execution method and device
CN112069030A (en) * 2020-09-04 2020-12-11 苏州浪潮智能科技有限公司 Task monitoring method, system, equipment and medium
CN113694536A (en) * 2021-09-07 2021-11-26 北京蔚领时代科技有限公司 Scene management method, device, equipment and medium for cloud game

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
利用crontab命令实现计划任务. 栾宏宇,许海谦.中国金融电脑,第10期. 2001
利用crontab命令实现计划任务. 栾宏宇,许海谦.中国金融电脑,第10期. 2001 *

Also Published As

Publication number Publication date
CN101110041A (en) 2008-01-23

Similar Documents

Publication Publication Date Title
CN100476739C (en) Method for managing group task
CN105959151B (en) A kind of Stream Processing system and method for High Availabitity
CN109873873B (en) Flight data issuing system, flight changing method and message processing method
Mahajan et al. Consistency, availability, and convergence
US7707259B2 (en) Workflow systems and methods for project management and information management
US7421546B2 (en) Intelligent state engine system
JP3739108B2 (en) Event processing system
US7779298B2 (en) Distributed job manager recovery
CN101185076A (en) Computer network system and method for the synchronization of a second database with a first database
CN102521044A (en) Distributed task scheduling method and system based on messaging middleware
CN101185075A (en) Computer network system for the synchronization of a second database with a first database
Babaoğlu et al. System support for partition-aware network applications
CN101699799A (en) Method and network equipment for preventing network loop and spanning tree protocol network system
CN102387075A (en) Dynamic service routing method and device for enterprise service bus
JPWO2002054263A1 (en) Framework system
CN110138876A (en) Task deployment method, apparatus, equipment and platform
CN108829545B (en) Method for realizing distributed database backup
CN110569113A (en) Method and system for scheduling distributed tasks and computer readable storage medium
CN105260297A (en) Test data management system and method
Zezulka et al. Time-sensitive networking as the communication future of industry 4.0
EA006307B1 (en) System, method and devices for integration of distributed application
CN114513556B (en) Two-stage time triggering service scheduling method and system based on deterministic network
CA2465234A1 (en) Method for communication of a real-time data exchange in a collision-recognition based communication network, corresponding memory medium and communication network
CN102075315B (en) Data synchronization method and device among forwarding boards
CN115759955A (en) Business process execution engine based on block chain

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
ASS Succession or assignment of patent right

Owner name: LIANCHUANG SCIENCE ( NANJING ) CO., LTD.

Free format text: FORMER OWNER: NANJING LIANCHUANG SCIENCE CO., LTD.

Effective date: 20091113

C41 Transfer of patent application or patent right or utility model
TR01 Transfer of patent right

Effective date of registration: 20091113

Address after: Building 16, world window software park, No. 12 Huai gate, Jiangsu, Nanjing

Patentee after: LIAN Technology (Nanjing) Co., Ltd.

Address before: 16 floor, No. 12 Huai gate, Nanjing, Jiangsu

Patentee before: Linkage System Integration Co., Ltd.

EE01 Entry into force of recordation of patent licensing contract

Assignee: LIAN Technology (Nanjing) Co., Ltd.

Assignor: Linkage System Integration Co., Ltd.

Contract fulfillment period: 2009.6.23 to 2027.8.30 contract change

Contract record no.: 2009320001548

Denomination of invention: Method for managing group task

Granted publication date: 20090408

License type: exclusive license

Record date: 2009.8.17

LIC Patent licence contract for exploitation submitted for record

Free format text: EXCLUSIVE LICENSE; TIME LIMIT OF IMPLEMENTING CONTACT: 2009.6.23 TO 2027.8.30; CHANGE OF CONTRACT

Name of requester: LIANCHUANG SCIENCE ( NANJING ) CO., LTD.

Effective date: 20090817

C56 Change in the name or address of the patentee

Owner name: LINKAGE-ASIAINFO TECHNOLOGY (NANJING) CO., LTD.

Free format text: FORMER NAME: LINKAGE TECHNOLOGY (NANJING) CO., LTD.

CP01 Change in the name or title of a patent holder

Address after: 210013 No. 16 building, window of world window, No. 12 Huai gate, Jiangsu, Nanjing

Patentee after: LINKAGE-ASIAINFO TECHNOLOGIES (NANJING), INC.

Address before: 210013 No. 16 building, window of world window, No. 12 Huai gate, Jiangsu, Nanjing

Patentee before: Linkage System Integration Co., Ltd.

C56 Change in the name or address of the patentee

Owner name: ASIALNFO TECHNOLOGY (NANJING) CO., LTD.

Free format text: FORMER NAME: LINKAGE-ASIAINFO TECHNOLOGY (NANJING) CO., LTD.

CP01 Change in the name or title of a patent holder

Address after: 210013 No. 16 building, window of world window, No. 12 Huai gate, Jiangsu, Nanjing

Patentee after: Asialnfo Technology (Nanjing) Co., Ltd.

Address before: 210013 No. 16 building, window of world window, No. 12 Huai gate, Jiangsu, Nanjing

Patentee before: LINKAGE-ASIAINFO TECHNOLOGIES (NANJING), INC.