CN101155370B - Business serial processing method and system in multi-stream application of mobile communication system - Google Patents

Business serial processing method and system in multi-stream application of mobile communication system Download PDF

Info

Publication number
CN101155370B
CN101155370B CN2006101649683A CN200610164968A CN101155370B CN 101155370 B CN101155370 B CN 101155370B CN 2006101649683 A CN2006101649683 A CN 2006101649683A CN 200610164968 A CN200610164968 A CN 200610164968A CN 101155370 B CN101155370 B CN 101155370B
Authority
CN
China
Prior art keywords
affairs
management unit
flow management
task manager
correspondence
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.)
Expired - Fee Related
Application number
CN2006101649683A
Other languages
Chinese (zh)
Other versions
CN101155370A (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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to CN2006101649683A priority Critical patent/CN101155370B/en
Publication of CN101155370A publication Critical patent/CN101155370A/en
Application granted granted Critical
Publication of CN101155370B publication Critical patent/CN101155370B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Telephonic Communication Services (AREA)

Abstract

The present invention relates to a serial processing method for affair of the mobile communication system, comprising the following steps: step 1, an affair management device maps each service affair in the mobile communication system into affair corresponding to target flow management unit in turn, the affair contains affair identifier; step 2, to put the affairs into alignment buffer in turn; step 3, the affair management device schedules the affairs to the corresponding target flow management unit in turn to process, using for processing the affair serial process; in the step 3, both the sent requested message and received requested message of the corresponding target flow management unit schlep affair identifier for distinguishing message of each affair corresponding the target flow management unit. The present invention can ensure that the flow service process is able to execute orderly, avoid complication and can cause to severe consequence, realize the buffer and schedule to process the flow differently, ensure that various process of the flow can process harmonious orderly.

Description

The serial processing method and the system of affairs during a kind of mobile communcations system multithread is used
Technical field
The present invention relates to mobile communcations system, relate in particular to the serial processing method and the system of affairs in a kind of mobile communcations system multithread application.
Background technology
In order to satisfy the demand of user QoS, increased the multithread application in the HRPD RevA agreement, have the corresponding different upper layer application of stream of a plurality of radio link protocols (RLP) carrying for each user.Therefore, in the CDMA2000-EVDO mobile communication system, in one or more protocol hierarchies, can there be not homogeneous turbulence of a plurality of similar entities difference correspondences, finishes related service and handle.For convenience of description, (Flow Management Element, FME), a FME determines by flow management element identifier (element ID) FMEID is unique these logic entities to be referred to as the flow management unit.
In the CDMA2000-EVDO mobile communcations system, FME also will handle the characteristics of mobile system own and the dynamic miscellaneous service incident that causes except the transmission and reception of finishing media stream data, generally be divided into two big classes:
Category-A: at the Business Processing of a certain specific FME, opening, upgrade, closing etc. as stream;
Category-B: at the Business Processing of current all FME, as multicast, clean culture, switch, add " leg ", remove " leg " etc.
Category-A mainly is to cause that category-B then is along with AT moves, the variation of radio condition causes because the startup of different upper layer application is closed.After system caused business event, FME must finish relevant Business Processing, and for example, handover event is handled, and will make each FME change service " leg ".Because the dynamic of system, the generation that the business event meeting is concurrent if each FME also adopts concurrent mode to handle, may lead to a conflict, and cause that the FME state is inconsistent, for example, can not handle the clean culture incident simultaneously when we are opening to flow through in the journey.The conflict of relevant treatment finally may cause the failure of calling out, the serious consequences such as termination of Media Stream.For fear of the appearance of these situations, must be with a kind of effective mechanism, guarantee that the mode that these concurrent business event can harmonious orderly carries out.
Summary of the invention
In order to solve above-mentioned technical problem, provide a kind of mobile communcations system multithread use in the serial processing method and the system of affairs, its purpose is, realizes the buffer memory and the scheduling of convection current different disposal, guarantees the carrying out that every processing of stream can harmonious orderly.
The invention provides the serial processing method of affairs in a kind of mobile communcations system multithread application, may further comprise the steps:
Step 1, task manager is mapped to affairs corresponding to the flow management unit successively with each business event in the mobile communcations system, and wherein, described affairs are under the jurisdiction of well-determined flow management unit, and described affairs comprise transaction identifiers;
Step 2 is put into the formation buffer memory successively with described affairs;
Step 3, described task manager is handled by the sequential scheduling of first in first out described affairs successively to corresponding described flow management unit, be used for affairs are carried out serial process, and it comprises:
Step 61 is if the described flow management unit free of current affairs correspondence then starts these affairs;
Step 62, after described current affairs started, when being finished, described task manager was removed described current affairs from the formation buffer memory;
Step 63, described task manager is the next affairs of described flow management cell scheduling of described current affairs correspondence by the order of first in first out;
In the described step 3, the request message that the object flow administrative unit of described correspondence sends and the request message of reception all carry transaction identifiers, be used to distinguish the message of the described flow management unit of each affairs correspondence, described transaction identifiers comprises flow management unit marks and transaction number.
In the step 2, described affairs are put into successively the tail of the queue of formation buffer memory.
Described step 1 specifically comprises:
Step 41 according to the business event type, obtains corresponding described flow management unit;
Step 42 is created affairs.
The quantity of the described flow management unit of obtained correspondence is at least one in the described step 41.
Described step 3 may further comprise the steps:
Described step 63 may further comprise the steps:
Step 71, judging whether to arrive tail of the queue, is then to finish scheduling flow;
Step 72, obtain the next affairs in the formation;
Step 73, according to transaction identifiers, judge whether to belong to the described flow management unit of described current affairs correspondence, if, then start these affairs, finish scheduling flow;
Step 74, repeated execution of steps 71, step 72 and step 73.
The present invention also provides the serial processing system of affairs in a kind of mobile communcations system multithread application, it is characterized in that, comprising:
The affairs that comprise transaction identifiers are used for record traffic event handling information necessary, and the execution of control Business Processing on the flow management unit;
The flow management unit is used for being responsible for the maintenance of stream, finishes transaction;
Task manager is used for creating, dispatches and removes affairs; Wherein, task manager is used for each business event with mobile communcations system and is mapped to affairs corresponding to the flow management unit successively, and described affairs are put into the formation buffer memory successively, and described affairs are handled to corresponding described flow management unit by the sequential scheduling of first in first out successively, affairs are carried out serial process;
Wherein, described affairs are under the jurisdiction of well-determined flow management unit;
Wherein, described task manager with described affairs successively by the sequential scheduling of first in first out when corresponding described flow management unit is handled, if the described flow management unit free of current affairs correspondence, then start these affairs, after described current affairs start, when being finished, described task manager is removed described current affairs from the formation buffer memory, and described task manager is dispatched next affairs for the described object flow administrative unit of described current affairs correspondence in order;
Wherein, the request message that the described flow management unit of described correspondence sends and the request message of reception all carry transaction identifiers, be used to distinguish the message of the described flow management unit of each affairs correspondence, described transaction identifiers comprises flow management unit marks and transaction number.
Further, described task manager is put into described affairs the tail of the queue of formation buffer memory successively.
Further, described task manager is obtained corresponding described flow management unit according to the business event type, creates affairs.
Further, the quantity of the described flow management unit of the described correspondence that obtains is at least one.
Further, described task manager with described affairs successively by the sequential scheduling of first in first out when corresponding described flow management unit is handled, judging whether to arrive tail of the queue, is then to finish scheduling flow, otherwise obtains the next affairs in the formation, then according to transaction identifiers, judge whether to belong to the described flow management unit of described current affairs correspondence, if then start these affairs, finish scheduling flow, otherwise continue to judge whether to arrive tail of the queue.
The present invention can guarantee that the Business Processing of convection current can carry out in order, avoids concurrent and serious consequence that may cause, realizes the buffer memory and the scheduling of convection current different disposal, guarantees the carrying out that every processing of stream can harmonious orderly.
Description of drawings
Affairs were created and scheduling flow figure when Fig. 1 was business event arrival;
Fig. 2 is that task manager is concurrent business event establishment affairs and the schematic diagram that carries out queue scheduling;
Fig. 3 is the formation schematic diagram of transaction identifiers;
Fig. 4 is the sign of message and replys the route schematic diagram;
Fig. 5 is the flow chart of transaction scheduling after affairs are finished;
Fig. 6 is the part of Fig. 5, has described task manager belongs to the next affairs of this a certain flow management unit from the affairs queue search process circuit.
Embodiment
Among the present invention, each business event in the communication system is mapped to affairs at each stream, put into the formation buffer memory then, sequential scheduling by first in first out is handled to corresponding flow management unit (FME), dispatching algorithm guarantees that the affairs of same FME are by serial process, affairs between a plurality of FME are then concurrent carries out, and not only avoids conflict but also guarantee to carry out efficient.
The invention provides two kinds of software logic unit.Comprise: task manager (TransactionManager) is used for creating, dispatches and removes affairs; Affairs (Transaction) are used for record traffic event handling information necessary, and the execution of control Business Processing on FME.All FME share a task manager, and affairs are under the jurisdiction of well-determined FME, and task manager is safeguarded a transaction queues for all FME.
The invention provides the Transaction Identifier method, the affairs that belong to certain FME constitute transaction identifiers (TransactionId) jointly by flow management unit mark sign (FMEID) and transaction number (Transaction Number) and are identified.
The invention provides in the affairs implementation sign of interaction message and method for routing between logic entity.For the interference that prevents message between the different affairs (as last affairs in response to answering overtime the end, may receive after then affairs start this reply), must distinguish between different affairs FME and other logic entity interactive messages.Concrete grammar is that to replying that other logic entities transmissions are asked and returned, message body is all carried transaction identifiers (TransactionID) and identified.All are replied by task manager and receive, and distribute the affairs of correspondence according to transaction identifiers and handle.
The invention provides the establishment and the dispatching method of affairs, this method is at following two kinds of scenes:
When 1, business event arrives, mainly may further comprise the steps:
Step 1, according to event type, obtain relevant flow management unit (a certain specific flow management unit or all), carry out the processing of following steps 2,3 one by one;
Step 2, establishment affairs are put into tail of the queue;
Step 3, judge that corresponding flow management unit is whether idle, if then start these affairs at once;
When 2, the affairs of certain flow management unit are finished:
Step 1, task manager are removed these affairs from formation
Step 2, task manager are the next affairs of this flow management cell scheduling by the principle of first in first out
This step comprises the steps: again
21, judging whether to arrive tail of the queue, is then to finish scheduling flow
22, obtain next affairs in the formation;
23, according to transaction identifiers, judge whether to belong to the object flow administrative unit, belong to and then start this affairs, finish scheduling flow; Otherwise execution in step 21,22,23.
Below in conjunction with accompanying drawing, the present invention is described in further detail.
Fig. 1 to Fig. 6 has illustrated the affairs serial processing method in the CDMA2000-EVDO mobile communcations system multithread application, yet should be appreciated that the solution that the present invention also can be used for other mobile communication system and be distributed as.
Fig. 1 has illustrated that when Business Processing arrived, the flow process that affairs are created and dispatched is characterized in that, comprises following steps:
After step 101, business event arrive, obtain object flow administrative unit (a certain specific FME or whole FME), the object flow administrative unit of obtaining is carried out one by one the processing of following steps;
Step 102, task manager are created the affairs that belong to this FME, comprise that record traffic handles needed relevant information, put into the transaction queues afterbody that task manager is safeguarded after the establishment;
Whether idle condition of current FME is judged by step 103, system
If step 104 is idle, then start affairs at once
Step 105, all target FME dispose process ends
Fig. 2 is that task manager is that concurrent business event generates affairs, and carries out the schematic diagram of queue scheduling.After the business event 201 that system causes arrived, by task manager 202, the destination object of incident (a certain specific FME or all FME) was created affairs 203 for this reason, and puts into the transaction queues tail of the queue that task manager 202 is safeguarded.205 describe action is responsible for the transaction scheduling in the formation is started execution to corresponding FME 207 for task manager.FME 207 finished relevant Business Processing under the affairs 206 that start will be controlled it.
Fig. 3 has illustrated the formation of transaction identifiers (TransactionId), comprises two parts, the sign of flow management unit (FMEID) 301 and transaction number (TransactionNumber) 302.First, FMEID
301 take from the FME identifier FMEID that is subordinate to, and are to remain unchanged in the lifetime of FME; Second portion is taken from the sequence number variable TransactionNumber of each FME internal maintenance, and affairs of every establishment add 1.
Fig. 4 has illustrated FME and other entity interactions, the process of message identifier and route.For avoiding the interference of message between the affairs, request that FME sends and replying of returning, message body is all carried transaction identifiers T2k (T2k represents k affairs of flow management unit 2), and process is as follows.
Step 401, in the transaction process, FME sends request to other entities, carries transaction identifiers T2k in the message body;
Step 402, target entity are finished processing, echo reply, and message body is contained T2k equally, and message is at first received by task manager;
Step 403, distribute correspondent transaction according to transaction identifiers by task manager;
Step 404, under affairs control, flow management unit 2 receives to handle and replys.
After Fig. 5 had illustrated that affairs are finished, the flow process of transaction scheduling may further comprise the steps:
After step 501, the flow management unit current transaction of k finish, will notify task manager, task manager is removed this affairs;
Step 502, task manager are pressed the principle of first in first out, and retrieval belongs to next affairs of flow management unit k from transaction queues;
Step 503, judge whether that success retrieves;
Step 504, retrieve, then start these affairs at once
Fig. 6 has described task manager and has belonged to the process of the next affairs of flow management unit k from the affairs queue search, and the step 502 in the corresponding diagram 5 is characterized in that, comprise following step:
Step 601, judge whether to arrive tail of the queue, will finish scheduling flow if arrive tail of the queue;
Step 602, obtain the next affairs in the formation;
Step 603, judge whether to belong to the object flow administrative unit according to transaction identifiers; Transaction identifiers comprises the identifier of the flow management unit that is belonged to, and as shown in Figure 3, comprises flow management unit marks and transaction number;
If step 604 belongs to, then start and carry out, search otherwise can continue formation.
Those skilled in the art can also carry out various modifications to above content under the condition that does not break away from the definite the spirit and scope of the present invention of claims.Therefore scope of the present invention is not limited in above explanation, but determine by the scope of claims.

Claims (10)

1. the serial processing method of affairs is characterized in that during a mobile communcations system multithread was used, and may further comprise the steps:
Step 1, task manager is mapped to affairs corresponding to the flow management unit successively with each business event in the mobile communcations system, and wherein, described affairs are under the jurisdiction of well-determined flow management unit, and described affairs comprise transaction identifiers;
Step 2 is put into the formation buffer memory successively with described affairs;
Step 3, described task manager is handled by the sequential scheduling of first in first out described affairs successively to corresponding described flow management unit, be used for affairs are carried out serial process, and it comprises:
Step 61 is if the described flow management unit free of current affairs correspondence then starts these affairs;
Step 62, after described current affairs started, when being finished, described task manager was removed described current affairs from the formation buffer memory;
Step 63, described task manager is the next affairs of described flow management cell scheduling of described current affairs correspondence by the order of first in first out; In the described step 3, the request message that the described flow management unit of described correspondence sends and the request message of reception all carry transaction identifiers, be used to distinguish the message of the described flow management unit of each affairs correspondence, described transaction identifiers comprises flow management unit marks and transaction number.
2. the serial processing method of affairs is characterized in that during mobile communcations system multithread as claimed in claim 1 was used, and in the step 2, described affairs was put into successively the tail of the queue of formation buffer memory.
3. the serial processing method of affairs during mobile communcations system multithread as claimed in claim 1 is used is characterized in that described step 1 specifically comprises:
Step 41 according to the business event type, obtains corresponding described flow management unit;
Step 42 is created affairs.
4. the serial processing method of affairs is characterized in that the quantity of the described flow management unit of obtained correspondence is at least one in the described step 41 during mobile communcations system multithread as claimed in claim 3 was used.
5. the serial processing method of affairs during mobile communcations system multithread as claimed in claim 1 is used is characterized in that described step 63 may further comprise the steps:
Step 71, judging whether to arrive tail of the queue, is then to finish scheduling flow;
Step 72, obtain the next affairs in the formation;
Step 73, according to transaction identifiers, judge whether to belong to the described flow management unit of described current affairs correspondence, if, then start these affairs, finish scheduling flow;
Step 74, repeated execution of steps 71, step 72 and step 73.
6. the serial processing system of affairs is characterized in that during a mobile communcations system multithread was used, and comprising:
The affairs that comprise transaction identifiers are used for record traffic event handling information necessary, and the execution of control Business Processing on the flow management unit;
The flow management unit is used for being responsible for the maintenance of stream, finishes transaction;
Task manager is used for creating, dispatches and removes affairs; Wherein, task manager is used for each business event with mobile communcations system and is mapped to affairs corresponding to the flow management unit successively, and described affairs are put into the formation buffer memory successively, and described affairs are handled to corresponding described flow management unit by the sequential scheduling of first in first out successively, affairs are carried out serial process;
Wherein, described affairs are under the jurisdiction of well-determined flow management unit;
Wherein, described task manager with described affairs successively by the sequential scheduling of first in first out when corresponding described flow management unit is handled, if the described flow management unit free of current affairs correspondence, then start these affairs, after described current affairs start, when being finished, described task manager is removed described current affairs from the formation buffer memory, and described task manager is the next affairs of the described flow management cell scheduling of described current affairs correspondence in order;
Wherein, the request message that the described flow management unit of described correspondence sends and the request message of reception all carry transaction identifiers, be used to distinguish the message of the described flow management unit of each affairs correspondence, described transaction identifiers comprises flow management unit marks and transaction number.
7. the serial processing system of affairs is characterized in that described task manager is put into described affairs the tail of the queue of formation buffer memory successively during mobile communcations system multithread as claimed in claim 5 was used.
8. the serial processing system of affairs is characterized in that during mobile communcations system multithread as claimed in claim 5 was used, and described task manager is obtained corresponding described flow management unit according to the business event type, creates affairs.
9. the serial processing system of affairs is characterized in that the quantity of the described flow management unit of the described correspondence that obtains is at least one during mobile communcations system multithread as claimed in claim 8 was used.
10. the serial processing system of affairs during mobile communcations system multithread as claimed in claim 5 is used, it is characterized in that, described task manager with described affairs successively by the sequential scheduling of first in first out when corresponding described flow management unit is handled, judge whether to arrive tail of the queue, be then to finish scheduling flow, otherwise obtain the next affairs in the formation, then according to transaction identifiers, judge whether to belong to the described flow management unit of described current affairs correspondence, if, then start these affairs, finish scheduling flow, otherwise continue to judge whether to arrive tail of the queue.
CN2006101649683A 2006-12-08 2006-12-08 Business serial processing method and system in multi-stream application of mobile communication system Expired - Fee Related CN101155370B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN2006101649683A CN101155370B (en) 2006-12-08 2006-12-08 Business serial processing method and system in multi-stream application of mobile communication system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN2006101649683A CN101155370B (en) 2006-12-08 2006-12-08 Business serial processing method and system in multi-stream application of mobile communication system

Publications (2)

Publication Number Publication Date
CN101155370A CN101155370A (en) 2008-04-02
CN101155370B true CN101155370B (en) 2011-01-19

Family

ID=39256742

Family Applications (1)

Application Number Title Priority Date Filing Date
CN2006101649683A Expired - Fee Related CN101155370B (en) 2006-12-08 2006-12-08 Business serial processing method and system in multi-stream application of mobile communication system

Country Status (1)

Country Link
CN (1) CN101155370B (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104239145B (en) * 2014-09-28 2017-10-27 北京奇艺世纪科技有限公司 A kind of data consistency control method and device based on case mechanism
CN108984571B (en) * 2017-06-05 2023-08-29 金篆信科有限责任公司 Transaction identification operation method, system and computer readable storage medium
CN109753314B (en) * 2017-11-01 2021-08-27 南京南瑞继保电气有限公司 Configurable automatic flow execution method and system
CN113132121B (en) * 2019-12-30 2023-01-31 成都鼎桥通信技术有限公司 Broadcast message processing method and device and terminal equipment
CN114416183A (en) * 2020-10-28 2022-04-29 武汉软艺信息技术有限公司 Method and device for rapidly restoring App state based on iOS system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1642165A (en) * 2004-01-05 2005-07-20 华为技术有限公司 Dialogue processing method for business processing ability application part in distribution type system
EP1615394A1 (en) * 2004-07-06 2006-01-11 Motorola, Inc. Method and apparatus for managing packet data loss in a wireless network
CN1735065A (en) * 2004-08-10 2006-02-15 华为技术有限公司 Method for building bearing in multimedia broadcast/multicast service
CN1848739A (en) * 2005-11-03 2006-10-18 华为技术有限公司 Charging system and method

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1642165A (en) * 2004-01-05 2005-07-20 华为技术有限公司 Dialogue processing method for business processing ability application part in distribution type system
EP1615394A1 (en) * 2004-07-06 2006-01-11 Motorola, Inc. Method and apparatus for managing packet data loss in a wireless network
CN1735065A (en) * 2004-08-10 2006-02-15 华为技术有限公司 Method for building bearing in multimedia broadcast/multicast service
CN1848739A (en) * 2005-11-03 2006-10-18 华为技术有限公司 Charging system and method

Also Published As

Publication number Publication date
CN101155370A (en) 2008-04-02

Similar Documents

Publication Publication Date Title
CN102892089B (en) Message pushing method, device and system
CN101155370B (en) Business serial processing method and system in multi-stream application of mobile communication system
CN101222374B (en) System, device and method for implementing service upgrade
CN102523179B (en) Topic group service realization method based on instant messaging
US20140337435A1 (en) Device and Method for the Dynamic Load Management of Cloud Services
CN110324238A (en) Online customer service method, apparatus and equipment
CN101207924B (en) Method for processing multi-user connections in high speed grouped data terminal
CN101998227B (en) Service routing method, device and system
CN101442667A (en) Interworking system for operation class video monitoring system
CN102571920A (en) Online customer service implementation method and online customer service system
CN101854703B (en) Method, server and system for acquiring status information
CN103516579A (en) Service system providing offline message and corresponding service method
CN110740161A (en) system and method for adapting converged communication
CN106330683A (en) Multimedia seating system
CN107870982A (en) Data processing method, system and computer-readable recording medium
CN100527883C (en) Method and system for insuring service chain service quality
CN109446204A (en) A kind of date storage method of instant messaging, device, electronic equipment and medium
CN109325068A (en) A kind of method for interchanging data and device
CN101247370B (en) Method and system for implementing message presentation service
KR100687719B1 (en) System form providing electronic businesscard service using open service interface
CN100544465C (en) Realize system, platform and the method for SMS value-added service
GB2366160A (en) Information routing in an integrated data network
CN103312623B (en) Task cooperation device and method
CN102523236A (en) Method and equipment for establishing dynamic connection
CN101489102A (en) Method and system for setting and executing network television content publishing policy

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
CF01 Termination of patent right due to non-payment of annual fee
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20110119