CN106488055A - Calling list rearrangement method, back end equipment and routing node device - Google Patents

Calling list rearrangement method, back end equipment and routing node device Download PDF

Info

Publication number
CN106488055A
CN106488055A CN201510541617.9A CN201510541617A CN106488055A CN 106488055 A CN106488055 A CN 106488055A CN 201510541617 A CN201510541617 A CN 201510541617A CN 106488055 A CN106488055 A CN 106488055A
Authority
CN
China
Prior art keywords
ticket
pending ticket
pending
described pending
business
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.)
Granted
Application number
CN201510541617.9A
Other languages
Chinese (zh)
Other versions
CN106488055B (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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies 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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201510541617.9A priority Critical patent/CN106488055B/en
Publication of CN106488055A publication Critical patent/CN106488055A/en
Application granted granted Critical
Publication of CN106488055B publication Critical patent/CN106488055B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Landscapes

  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

The embodiment of the present invention provides a kind of calling list rearrangement method, back end equipment and routing node device.The calling list rearrangement method of the present invention, including the re-scheduling factor obtaining pending ticket；The re-scheduling factor includes the multiple parameters determining according to pending ticket；Determine pending ticket corresponding business partition directory according to the partial parameters in the re-scheduling factor；Judge according to the other specification outside partial parameters in the re-scheduling factor whether the processed ticket in pending ticket corresponding business partition directory has and pending ticket identical ticket；If having in processed ticket with pending ticket identical ticket it is determined that pending ticket is to repeat ticket.The embodiment of the present invention can improve ticket re-scheduling efficiency.

Description

Calling list rearrangement method, back end equipment and routing node device
Technical field
The present embodiments relate to communication technology, more particularly, to a kind of calling list rearrangement method, back end set Standby and routing node device.
Background technology
Operator is providing a user with business service, during speech business and/or data service, needs Want the information of the business that accurate recording user used, these information are generally embodied with ticket form, as Operation analyses and/or the foundation of charging.The accuracy of ticket, can directly affect the operation carrying out according to ticket Analysis result and/or the accuracy of charging.
Ticket repeats to be the inaccurate key factor of ticket.Therefore, for avoiding ticket to repeat to bring Ticket inaccurate, re-scheduling can be carried out to current ticket, that is, determine that whether current ticket is to repeat ticket. Re-scheduling is carried out to current ticket, can be generally according to the corresponding parameter of the re-scheduling factor default in current ticket Judged with this corresponding parameter of re-scheduling factor in each ticket in all of processed ticket, judging should Whether each ticket identical with this current ticket, so that it is determined that whether include in this all processed ticket with This current ticket identical ticket, if it is determined that this current ticket is to repeat ticket.This re-scheduling factor The parameter of at least one type of ticket can be included.
The development of cordless communication network technology and Internet technology, so that business data flow is increasing, is transported Battalion business is increasing in the face of the quantity of ticket.For ensureing the accuracy of ticket, the re-scheduling gesture of mass tickets exists Must go.However, during mass tickets re-scheduling, ticket quantity is larger, the quantity of processed ticket Also larger, therefore the less efficient of re-scheduling is carried out according to all of processed ticket of re-scheduling factor pair.
Content of the invention
The embodiment of the present invention provides a kind of calling list rearrangement method, back end equipment and routing node device, With ticket re-scheduling efficiency.
In a first aspect, the embodiment of the present invention provides a kind of calling list rearrangement method, including：
Obtain the re-scheduling factor of pending ticket；The described re-scheduling factor includes：According to described pending ticket The multiple parameters determining；
Determine described pending ticket corresponding business subregion mesh according to the partial parameters in the described re-scheduling factor Record；
Other specification outside partial parameters according to the described re-scheduling factor judges described pending ticket pair Whether the processed ticket in the business partition directory answered has and described pending ticket identical ticket；
If having in described processed ticket with described pending ticket identical ticket it is determined that described treat Processing ticket is to repeat ticket.
According in a first aspect, in the first mode in the cards of first aspect, described acquisition waits to locate The re-scheduling factor of reason ticket, including：
Receive the re-scheduling request message that routing node device sends；Described re-scheduling request message includes：Described The re-scheduling factor；The described re-scheduling factor includes what described routing node device determined according to described pending ticket Multiple parameters.
According to the first mode in the cards of first aspect or first aspect, can enable in second Mode in, described partial parameters include：The type of service of described pending ticket and described pending words Single time started；
Described determine that the corresponding business of described pending ticket is divided according to the partial parameters in the described re-scheduling factor Area's catalogue, including：
The corresponding operation list of described pending ticket is determined according to the type of service of described pending ticket；
Time started according to described pending ticket in the corresponding operation list of described pending ticket really Determine the corresponding business partition directory of described pending ticket.
According to the second mode in the cards of first aspect, in the third mode in the cards, The described time started according to described pending ticket in the corresponding operation list of described pending ticket really Determine the corresponding business partition directory of described pending ticket to include：
Determine the mapping table of ticket time started section and business partition directory；
Time started according to described pending ticket and described mapping table are in described pending ticket pair In the operation list answered, determine that the time started section at the time started place of described pending ticket is corresponding Business partition directory is the corresponding business partition directory of described pending ticket.
According to the third mode in the cards of first aspect, in the 4th kind of mode in the cards, Described determination ticket time started section is included with the mapping table of business partition directory：
It is described right to be determined according to the business subregion mapped file in the corresponding operation list of described pending ticket Answer relation table.
Second according to first aspect to the 4th kind of mode in the cards any one, at the 5th kind In mode in the cards, the other specification outside described partial parameters according to the described re-scheduling factor is sentenced Whether the processed ticket in the corresponding business partition directory of described pending ticket that breaks has is waited to locate with described Reason ticket identical ticket, including：
Time started according to described pending ticket apart from the absolute time of Preset Time, treats described in determination Process the filename of ticket；
Judge that whether having described pending ticket in internal memory corresponds to according to the filename of described pending ticket Fileinfo；
If having the corresponding fileinfo of described pending ticket in described internal memory, judge described fileinfo In whether there is the corresponding key value of described other specification；
If there is the corresponding key value of described other specification in the corresponding fileinfo of described pending ticket, Determine and have in described processed ticket and described pending ticket identical ticket.
According to the 5th kind of mode in the cards of first aspect, in the 6th kind of mode in the cards, The described filename according to described pending ticket judges that whether having described pending ticket in internal memory corresponds to Fileinfo include：
Filename according to described pending ticket and the mapping relations of default filename and memory address Table, determines the corresponding memory address of described pending ticket；
Using the fileinfo preserving in corresponding for described pending ticket memory address as described pending words Single corresponding fileinfo.
The 5th kind according to first aspect or the 6th kind of mode in the cards, in the cards at the 7th kind In mode, whether the described filename according to described pending ticket judges to have in internal memory described pending Before the corresponding fileinfo of ticket, methods described also includes：
Judge the place whether having in the corresponding business partition directory of described pending ticket in described internal memory The reason corresponding fileinfo of ticket；
The described filename according to described pending ticket judges whether there is described pending ticket in internal memory Corresponding fileinfo, including：
If having the processed ticket in the corresponding business partition directory of described pending ticket in described internal memory Corresponding fileinfo, judges whether to have institute in described internal memory according to the filename of described pending ticket State the corresponding fileinfo of pending ticket.
Second according to first aspect to the 7th kind of mode in the cards any one, at the 8th kind In mode in the cards, if the type of service of described pending ticket includes：Short message service, described its He includes parameter：The other party number of described pending ticket, in the end time of described pending ticket extremely Few one.
Second according to first aspect to the 7th kind of mode in the cards any one, at the 9th kind In mode in the cards, if the type of service of described pending ticket includes：Talk business, described its He includes parameter：The end time of described pending ticket, the type of call of described pending ticket, institute State at least one in the other party number of pending ticket.
Second according to first aspect to the 7th kind of mode in the cards any one, at the tenth kind In mode in the cards, if the type of service of described pending ticket includes：Data service, described its He includes parameter：In the network type of described pending ticket, the flow information of described pending ticket extremely Few one.
Second aspect, the embodiment of the present invention provides a kind of calling list rearrangement method, including：
Determine the re-scheduling factor of described pending ticket according to pending ticket；The described re-scheduling factor includes many Individual parameter；
Send re-scheduling request message to the corresponding back end equipment of described pending ticket, described re-scheduling please Message is asked to include the described re-scheduling factor；Described re-scheduling request message be used for making described back end equipment according to Partial parameters in the described re-scheduling factor determine the corresponding business partition directory of described pending ticket, according to Other specification outside partial parameters described in the described re-scheduling factor judges the corresponding business of described pending ticket Whether the processed ticket in partition directory has and described pending ticket identical ticket.
According to second aspect, in the first mode in the cards of second aspect, described partial parameters Including：The type of service of described pending ticket and the time started of described pending ticket.
According to the first mode in the cards of second aspect or second aspect, can enable in second Mode in, described to the corresponding back end equipment of described pending ticket send re-scheduling request message it Before, methods described also includes：
The corresponding data of described pending ticket is determined according to the corresponding service access code of described pending ticket Node device.
According to the second mode in the cards of second aspect, in the third mode in the cards, Described the corresponding data of described pending ticket is determined according to the corresponding service access code of described pending ticket Node device includes：
According to default integer value, the standard code for information interchange of the preset characters in described service access code is entered Row delivery, obtains modulus value；
According to described modulus value and modulus value and the mapping table of back end equipment, determine described modulus value pair The back end equipment answered is the corresponding back end equipment of described pending ticket.
Second according to second aspect or the third mode in the cards, in the cards at the 4th kind In mode, described service access code includes the corresponding traffic identification code of described pending ticket；Described business Identification code includes：Business account information.
According to second aspect the first to the 4th kind of mode in the cards any one, at the 5th kind In mode in the cards, if the type of service of this pending ticket includes：Short message service, described other Parameter includes：The other party number of described pending ticket, in the end time of described pending ticket at least One.
According to second aspect the first to the 4th kind of mode in the cards any one, at the 6th kind In mode in the cards, if the type of service of described pending ticket includes：Talk business, described its He includes parameter：The end time of described pending ticket, the type of call of described pending ticket, institute State at least one in the other party number of pending ticket.
According to second aspect the first to the 4th kind of mode in the cards any one, at the 7th kind In mode in the cards, if the type of service of described pending ticket includes：Data service, described its He includes parameter：In the network type of described pending ticket, the flow information of described pending ticket extremely Few one.
The third aspect, the embodiment of the present invention provides a kind of back end equipment, including：
Acquisition module, for obtaining the re-scheduling factor of pending ticket；The described re-scheduling factor includes：According to The multiple parameters that described pending ticket determines；
Determining module, for determining described pending ticket pair according to the partial parameters in the described re-scheduling factor The business partition directory answered；
Judge module, for partial parameters according to the described re-scheduling factor outside other specification judge institute State whether the processed ticket in pending ticket corresponding business partition directory has and described pending words Single-phase same ticket；
Described determining module, if be additionally operable in described processed ticket to have identical with described pending ticket Ticket it is determined that described pending ticket be repeat ticket.
According to the third aspect, in the first mode in the cards of the third aspect, described back end Equipment also includes：
Receiver module, for receiving the re-scheduling request message of routing node device transmission；Described re-scheduling request Message includes：The described re-scheduling factor；The described re-scheduling factor includes described routing node device and is treated according to described Process the multiple parameters that ticket determines.
Existed according to the first mode in the cards of the third aspect or the third aspect, may be real in second In existing mode, described partial parameters include：The type of service of described pending ticket and described pending The time started of ticket；
Described determining module, is additionally operable to be determined according to the type of service of described pending ticket described pending The corresponding operation list of ticket, the time started according to described pending ticket is in described pending ticket pair The corresponding business partition directory of described pending ticket is determined in the operation list answered.
According to the second mode in the cards of the third aspect, in the third mode in the cards, Described determining module, is additionally operable to determine the mapping table of ticket time started section and business partition directory, Time started according to described pending ticket and described mapping table are corresponding in described pending ticket In operation list, determine the corresponding business of time started section at the time started place of described pending ticket Partition directory is the corresponding business partition directory of described pending ticket.
According to the third mode in the cards of the third aspect, in the 4th kind of mode in the cards, Described determining module, is additionally operable to be reflected according to the business subregion in the corresponding operation list of described pending ticket Penetrate file and determine described mapping table.
Second according to the third aspect to the 4th kind of mode in the cards any one, at the 5th kind In mode in the cards, described determining module, it is additionally operable to the time started according to described pending ticket Apart from the absolute time of Preset Time, determine the filename of described pending ticket；
Described judge module, is additionally operable to judge whether have in internal memory according to the filename of described pending ticket There is the corresponding fileinfo of described pending ticket, if there is in described internal memory described pending ticket corresponding to Fileinfo, judge whether there is in described fileinfo the corresponding key value of described other specification；
Described determining module, if be additionally operable in the corresponding fileinfo of described pending ticket to have described its The corresponding key value of his parameter, determines and has in described processed ticket and described pending ticket identical Ticket.
According to the 5th kind of mode in the cards of the third aspect, in the 6th kind of mode in the cards, Described determining module, be additionally operable to filename according to described pending ticket and default filename with interior Deposit the mapping table of address, determine the corresponding memory address of described pending ticket, will be described pending The fileinfo preserving in the corresponding memory address of ticket is defined as described pending ticket corresponding file letter Breath.
The 5th kind according to the third aspect or the 6th kind of mode in the cards, in the cards at the 7th kind In mode, described judge module, it is additionally operable to judge whether there is in described internal memory described pending ticket pair The corresponding fileinfo of processed ticket in the business partition directory answered；If having described in described internal memory The corresponding fileinfo of processed ticket in the corresponding business partition directory of pending ticket, according to described The filename of pending ticket judges whether there is described pending ticket corresponding file letter in described internal memory Breath.
Second according to the third aspect to the 7th kind of mode in the cards any one, at the 8th kind In mode in the cards, if the type of service of described pending ticket includes：Short message service, described its He includes parameter：The other party number of described pending ticket, in the end time of described pending ticket extremely Few one.
Second according to the third aspect to the 7th kind of mode in the cards any one, at the 9th kind In mode in the cards, if the type of service of described pending ticket includes：Talk business, described its He includes parameter：The end time of described pending ticket, the type of call of described pending ticket, institute State at least one in the other party number of pending ticket.
Second according to the third aspect to the 7th kind of mode in the cards any one, at the tenth kind In mode in the cards, if the type of service of described pending ticket includes：Data service, described its He includes parameter：In the network type of described pending ticket, the flow information of described pending ticket extremely Few one.
Fourth aspect, the embodiment of the present invention provides a kind of routing node device, including：
Determining module, for determining the re-scheduling factor of described pending ticket according to pending ticket；Described The re-scheduling factor includes multiple parameters；
Sending module, is additionally operable to the corresponding back end equipment transmission re-scheduling request of described pending ticket Message, described re-scheduling request message includes the described re-scheduling factor；Described re-scheduling request message is used for making described Back end equipment determines the corresponding industry of described pending ticket according to the partial parameters in the described re-scheduling factor Business partition directory, other specification outside partial parameters according to the described re-scheduling factor judge described in wait to locate It is identical with described pending ticket whether the processed ticket in reason ticket corresponding business partition directory has Ticket.
According to fourth aspect, in the first mode in the cards of fourth aspect, described partial parameters Including：The type of service of described pending ticket and the time started of described pending ticket.
According to the first mode in the cards of fourth aspect or fourth aspect, can enable in second Mode in, described determining module, be additionally operable to true according to the corresponding service access code of described pending ticket Determine the corresponding back end equipment of described pending ticket.
According to the second mode in the cards of fourth aspect, in the third mode in the cards, Described determining module, is additionally operable to according to default integer value to the preset characters in described service access code Standard code for information interchange carries out delivery, obtains modulus value；Set with back end according to described modulus value and modulus value Standby mapping table, determines that described modulus value corresponding back end equipment is that described pending ticket corresponds to Back end equipment.
Second according to fourth aspect or the third mode in the cards, in the cards at the 4th kind In mode, described service access code includes the corresponding traffic identification code of described pending ticket；Described business Identification code includes：Business account information.
According to fourth aspect the first to the 4th kind of mode in the cards any one, at the 5th kind In mode in the cards, if the type of service of this pending ticket includes：Short message service, described other Parameter includes：The other party number of described pending ticket, in the end time of described pending ticket at least One.
According to fourth aspect the first to the 4th kind of mode in the cards any one, at the 6th kind In mode in the cards, if the type of service of described pending ticket includes：Talk business, described its He includes parameter：The end time of described pending ticket, the type of call of described pending ticket, institute State at least one in the other party number of pending ticket.
According to fourth aspect the first to the 4th kind of mode in the cards any one, at the 7th kind In mode in the cards, if the type of service of described pending ticket includes：Data service, described its He includes parameter：In the network type of described pending ticket, the flow information of described pending ticket extremely Few one.
Calling list rearrangement method provided in an embodiment of the present invention, back end equipment and routing node device, lead to Cross the acquisition re-scheduling factor, determine the corresponding business of pending ticket according to the partial parameters in this re-scheduling factor Partition directory, judges the corresponding business subregion of this pending ticket according to the other specification in this re-scheduling factor Whether the processed ticket in catalogue has and this pending ticket identical ticket, if this processed ticket In have with this pending ticket identical ticket it is determined that this pending ticket be repeat ticket.Due to Carry out ticket re-scheduling only for the processed ticket in the corresponding business partition directory of this pending ticket, and It is not directed to all of processed ticket and carries out ticket re-scheduling, thus reduce the processed ticket of ticket re-scheduling Quantity less, improve ticket re-scheduling efficiency.
Brief description
In order to be illustrated more clearly that the embodiment of the present invention or technical scheme of the prior art, below will be to reality Apply required use in example or description of the prior art accompanying drawing do one simply introduce it should be apparent that, under Accompanying drawing in the description of face is some embodiments of the present invention, for those of ordinary skill in the art, On the premise of not paying creative labor, other accompanying drawings can also be obtained according to these accompanying drawings.
The structural representation of the network system that Fig. 1 is suitable for for various embodiments of the present invention；
The flow chart of the calling list rearrangement method that Fig. 2 provides for the embodiment of the present invention one；
The flow chart of the calling list rearrangement method that Fig. 3 provides for the embodiment of the present invention two；
Fig. 4 is that the structure of the corresponding fileinfo of this pending ticket in internal memory in the embodiment of the present invention two is shown It is intended to；
A kind of flow chart of calling list rearrangement method that Fig. 5 provides for the embodiment of the present invention three；
The structure of the applicable network system of the calling list rearrangement method that Fig. 6 provides for the embodiment of the present invention four is shown It is intended to；
The ticket storage organization that Fig. 7 is suitable for for the calling list rearrangement method that the embodiment of the present invention four provides is illustrated Figure；
A kind of flow chart of calling list rearrangement method that Fig. 8 provides for the embodiment of the present invention four；
A kind of structural representation of back end equipment that Fig. 9 provides for the embodiment of the present invention five；
A kind of structural representation of routing node device that Figure 10 provides for the embodiment of the present invention six.
Specific embodiment
Purpose, technical scheme and advantage for making the embodiment of the present invention are clearer, below in conjunction with this Accompanying drawing in bright embodiment, is clearly and completely described to the technical scheme in the embodiment of the present invention, Obviously, described embodiment is a part of embodiment of the present invention, rather than whole embodiments.It is based on Embodiment in the present invention, those of ordinary skill in the art are obtained under the premise of not making creative work The every other embodiment obtaining, broadly falls into the scope of protection of the invention.
The calling list rearrangement method that various embodiments of the present invention provide is applicable to the Internet protocol clothes in operator Business (Operator`s Internet Protocol Services) corresponding business operation support system of network Carry out in (Business＆Operation Support System, abbreviation BOSS).Fig. 1 is that the present invention is each The structural representation of the network system that embodiment is suitable for.As shown in figure 1, the net that the embodiment of the present invention is suitable for Network system, that is, this BOSS may include：List system 101, adaptation (Mediation) system 102, meter Charge system 103 and through subsystem 104.Wherein, this is also called operation analysis system etc. through subsystem 104. As shown in figure 1, this adaption system 102 is located between list system 101 and charge system 103, this is fitted Match system 102 be also located at list system 101 and through subsystem 104 between.Wherein, this list system 101 Including Record Bill Server 105.Record Bill Server 105 can be service server, can gather acquisition user Equipment (User Equipment, abbreviation UE) obtain operator IP service network in business service and The ticket producing.This business service can be internet protocol multi-media sub-system (Internet Protocol Multimedia Subsystem, abbreviation IMS) packet switched streaming (Packet Switching Streaming, Abbreviation PSS) service, such as short message service, talk business and/or data service etc..This adaption system 102 Set including routing node device 106 and the corresponding back end of at least one of this routing node device 106 Standby 107.This routing node device 106 can processed to this ticket with reference to data node device 107 Afterwards, by this ticket send accounting server 108 to this charge system 103 and/or this through subsystem In 104 through sub-server 109.This accounting server 108 adopts default according to the ticket after this process Charging regulation carries out charging, or, this is carried on the work according to the ticket after this process through sub-server 109 The analysis of decision-making.Equipment in this adaption system 102 is processed to ticket, arranges including to ticket Process it is ensured that the accuracy of ticket again, so that the charging of this accounting server 108 is more accurate, And/or this analysis result through sub-server 109 is more accurate.
The embodiment of the present invention one provides a kind of calling list rearrangement method.Fig. 2 provides for the embodiment of the present invention one The flow chart of calling list rearrangement method.The method of this embodiment of the invention can be by back end equipment execution. This back end equipment can set for the corresponding back end of ticket pending determined by routing node device Standby.As shown in Fig. 2 the method may include：
S201, the re-scheduling factor of the pending ticket of acquisition；This re-scheduling factor is included according to this pending ticket The multiple parameters determining.
Specifically, this re-scheduling factor can be that this back end equipment determines according to this pending ticket, Other equipment, such as this corresponding routing node of back end equipment can also be received for this back end equipment Equipment, this other equipment of transmission is according to this pending ticket determination.This re-scheduling factor may include：Should The type of service of pending ticket, the initial time of this pending ticket.The service class of this pending ticket Type can include：Arbitrary type of service in short message service, talk business data business.Wherein, this leads to Call business includes local call business and strange land talk business；This data service may include：Application program visitor Family end data business and browser data business.The initial time of this pending ticket may include：This waits to locate The time started of reason ticket and end time.
For example, if the type of service of this pending ticket is short message service, this re-scheduling factor also includes： The other party number of this pending ticket.If the type of service of this pending ticket includes：Talk business, should The re-scheduling factor also includes：The type of call of this pending ticket, the call type of this pending ticket, should In the other party number of pending ticket, the duration of call of this pending ticket at least one.Wherein, this is exhaled Type is made to include caller call or incoming call；Call type includes local call type or strange land conversational class Type；When other party number can be this talk business of UE execution corresponding with this pending ticket, opposite end Operator's signing number of UE；The duration of call includes the duration of the corresponding talk business of this pending ticket, should The duration of call can be time started rising apart from this pending ticket in the initial time of this pending ticket The duration of end time in time beginning.If the type of service of this pending ticket includes：Data service, should The re-scheduling factor also include the network type of this pending ticket, in the flow information of this pending ticket at least One.This network type can for 2nd generation (second Generation, abbreviation 2G) network type, 3rd generation (3rd-Generation, abbreviation 3G) network type or the 4th generation (Fourth-Generation, Abbreviation 4G) arbitrary in network type；This flow information can be this pending ticket this data industry corresponding The uninterrupted that business produces, this flow information may include transmission byte-sized and receives byte-sized.
S202, determine the corresponding business subregion of this pending ticket according to the partial parameters in this re-scheduling factor Catalogue.
Specifically, the processed ticket in the corresponding business partition directory of this pending ticket may include at least One ticket.In processed ticket in the corresponding business partition directory of this pending ticket, each ticket should The corresponding parameter of partial parameters, this partial parameters all same with this pending ticket.This pending ticket The not all of processed ticket of processed ticket of corresponding business partition directory, but pending with this Ticket has the processed ticket of part identical parameters.Thus the corresponding business subregion mesh of this pending ticket The processed ticket of record could also say that the ticket partly similar with this pending ticket.This pending ticket Each ticket in processed ticket in corresponding business partition directory, can be to be stored in this after treatment to treat Process in ticket corresponding business partition directory.
Wherein, in this re-scheduling factor, this partial parameters includes at least one parameter.If this partial parameters bag Include at least two parameters, then this pending ticket pair determining according to this partial parameters in this re-scheduling factor The business partition directory answered, can be that this waits to locate according to this at least two parameter determination in this partial parameters Reason ticket corresponding business partition directory, processed in the corresponding business partition directory of this pending ticket Change the corresponding parameter of this partial parameters of each ticket in list, all identical with this partial parameters.
S203, this pending ticket pair is judged according to the other specification outside this partial parameters in this re-scheduling factor Whether the processed ticket in the business partition directory answered has and this pending ticket identical ticket.
Specifically, the corresponding business of this pending ticket is judged according to this other specification in this re-scheduling factor Whether have in processed ticket in partition directory and this pending ticket identical ticket, can be to sentence The corresponding parameter of this other specification of each ticket in this processed ticket disconnected, if identical with this other specification. If identical, can determine that in the processed ticket in the corresponding business partition directory of this pending ticket and have With this process ticket identical ticket, then can determine that this pending ticket is to repeat ticket.This S203 according to Other specification in this re-scheduling factor judges processed in the corresponding business partition directory of this pending ticket Whether ticket has and this pending ticket identical ticket, is to say, according to other in this re-scheduling factor Parameter is carried out only for the processed ticket in the corresponding business partition directory of this pending ticket, i.e. only pin Processed ticket in the corresponding business partition directory to this pending ticket carries out ticket re-scheduling, and not Carry out ticket re-scheduling for all of processed ticket, thus reduce the number of the processed ticket of ticket re-scheduling Amount is less, improves the efficiency of ticket re-scheduling.Because the corresponding business partition directory of this pending ticket is root Determine according to the partial parameters in this re-scheduling factor, therefore the corresponding business partition directory of this pending ticket Outside other business partition directory in processed ticket in this partial parameters corresponding at least one ginseng Number, different from this partial parameters of this pending ticket that is to say, that in this other business partition directory The ticket of processed ticket all different from this pending ticket, place in this other business partition directory The ticket of reason ticket does not include this pending ticket.Thus divide only for the corresponding business of this pending ticket Processed ticket in area's catalogue carries out ticket re-scheduling, can be in the number of the processed ticket reducing ticket re-scheduling Amount is less, improves on the basis of the efficiency of ticket re-scheduling it is ensured that the accuracy of ticket re-scheduling.
If there is this pending ticket it is determined that this pending ticket is attached most importance in this processed ticket of S204 Multiple ticket.
Calling list rearrangement method provided in an embodiment of the present invention, by obtain the re-scheduling factor, according to this re-scheduling because Partial parameters in son determine pending ticket corresponding business partition directory, according in this re-scheduling factor Other specification judge the processed ticket in the corresponding business partition directory of this pending ticket whether have with This pending ticket identical ticket, if having in this processed ticket identical with this pending ticket if List is it is determined that this pending ticket is to repeat ticket.Due to only for the corresponding business of this pending ticket Processed ticket in partition directory carries out ticket re-scheduling, and is not directed to all of processed ticket and carries out Ticket re-scheduling, thus the quantity reducing the processed ticket of ticket re-scheduling is less, improves the effect of ticket re-scheduling Rate.
Simultaneously as the corresponding business partition directory of this pending ticket is according to the portion in this re-scheduling factor Point parameter determination, according to the other specification in this re-scheduling factor only for the corresponding industry of this pending ticket Processed ticket in business partition directory carries out ticket re-scheduling, can be in the processed ticket reducing ticket re-scheduling The less efficiency improving ticket re-scheduling of quantity on the basis of it is ensured that the accuracy of ticket re-scheduling.
On the basis of the calling list rearrangement method of above-described embodiment, the embodiment of the present invention two also provides a kind of words Single weighing method.The flow chart of the calling list rearrangement method that Fig. 3 provides for the embodiment of the present invention two.As Fig. 3 Shown, the re-scheduling factor that the method obtains pending ticket in the S201 of above-described embodiment may include：
The re-scheduling request message that S301, reception routing node send, this re-scheduling request message includes：This row Repeated factor；This re-scheduling factor includes the multiple parameters that this routing node determines according to this pending ticket.
Optionally, the corresponding business partition directory of this pending ticket is the corresponding business of this pending ticket Business partition directory in catalogue；This partial parameters includes：The type of service of this pending ticket is treated with this Process the time started of ticket.
Optionally, in above-mentioned S202, this determines this pending ticket according to the partial parameters in this re-scheduling factor Corresponding business partition directory, can include：
S302, determine the corresponding operation list of this pending ticket according to the type of service of this pending ticket.
Specifically, the corresponding business mesh of this pending ticket is determined according to the type of service of this pending ticket Record, can be that to be defined as this pending ticket corresponding for the operation list of ticket by storing this type of service Operation list.Processed ticket in all business partition directory in the corresponding operation list of this pending ticket Type of service all identical with the type of service of this pending ticket.
The corresponding operation list of this pending ticket, can be the corresponding operation list literary composition of this pending ticket Part presss from both sides.For example, the entitled service100 of the corresponding operation list of this pending ticket, then this is treated Processing ticket corresponding operation list file can be entitled service100 file.
S303, according to time started of this pending ticket in the corresponding operation list of described pending ticket Middle determine the corresponding business partition directory of this pending ticket.
Specifically, the time started according to this pending ticket is in the corresponding operation list of this pending ticket Middle determine the corresponding business partition directory of this pending ticket, can be by corresponding for this pending ticket industry In business catalogue, the memory ticket time started business identical or close with the time started of this pending ticket Partition directory is defined as the corresponding business partition directory of this pending ticket.This ticket time started is treated with this The time started processing ticket is close, during the beginning that can be this ticket time started with this pending ticket Between be located the time period identical.The corresponding business partition directory of this pending ticket can be pending according to this The business partition directory that the time started of ticket determines in the corresponding operation list of this pending ticket, because The processed ticket that this is directed in the corresponding business partition directory of this pending ticket carries out ticket re-scheduling, can Reduce the quantity of the processed ticket of ticket re-scheduling, improve the efficiency of ticket re-scheduling.
For example, if this corresponding operation list of process ticket is the file of entitled service100, Then the corresponding business partition directory of this pending ticket is the business partition directory in service100 file. Determine in the corresponding operation list of this pending ticket if being determined according to time started of this pending ticket The corresponding business partition directory of this pending ticket be part0 file, then this pending ticket is corresponding Business partition directory can be the part0 file in service file.
Optionally, in above-mentioned S303, the time started according to this pending ticket corresponds in this pending ticket Operation list in determine that the corresponding business partition directory of this pending ticket may include：
Determine the mapping table of ticket time started section and business partition directory；
Time started according to this pending ticket and this mapping table are in the corresponding industry of this pending ticket In business catalogue, determine the time started section corresponding business subregion at the time started place of this pending ticket Catalogue is the corresponding business partition directory of this pending ticket.
Specifically, the mapping table of this ticket time started section and business partition directory, it may include：Extremely The corresponding relation of each ticket time started section and business partition directory in a few ticket time started section, Wherein, different ticket time started section corresponding business subregion mesh in this at least one ticket time started section Record can be different.That is, business partition directory is the time started institute in operation list according to ticket Time period divide, the time started section of ticket in different business partition directory in same operation list Different.Ticket in a ticket time started section for the time started, for this ticket time started For the corresponding business partition directory of section, it is properly termed as effective ticket.That is, the ticket time started Section with the mapping table of business partition directory in, ticket time started section is represented by effective ticket and starts Time period.Meanwhile, in the mapping table of this ticket time started section and business partition directory, this business Partition directory can be represented by the mark of business partition directory.
In the mapping table of this ticket time started section and business partition directory, each ticket time started Section also refers to opening of processed ticket in this each corresponding business partition directory of ticket time started section Begin the time period.For example, the mapping table of this ticket time started section and business partition directory, example As being as shown in table 1 below.
Ticket time started section Business partition directory
Data1-Data2 N1
Data2-Data3 N2
Data3-Data4 N3
Data4-Data5 N4
Table 1
In table 1, N1-N4 represents the mark of four business partition directory respectively.As shown in table 1, if should The time started of pending ticket, more than Data2, less than between Data3, i.e. the opening of this pending ticket The time started section that time beginning is located is Data2-Data3, the therefore time started according to this pending ticket Can determine that this pending ticket is corresponding in the corresponding operation list of this pending ticket with this mapping table Business partition directory be N2 corresponding business subregion mesh in the corresponding operation list of this pending ticket Record.
In the mapping table of this ticket time started section and business partition directory, each ticket time started section The corresponding relation of business partition directory corresponding with this each ticket time started section, can be respectively to should correspond to The different editions of relation table.Therefore, also include in this mapping table：This each ticket time started section is right The version number answered.This ticket time started section and the mapping table of business partition directory, can be also as follows Shown in table 2.
Ticket time started section Business partition directory Version number
Data1-Data2 N1 Ver1
Data2-Data3 N2 Ver2
Data3-Data4 N3 Ver3
Data4-Data5 N4 Ver4
Table 2
In table 2, Ver1-Ver4 is respectively four different version numbers.Wherein, this correspondence of Ver2 version In relation table, ticket time started section Data2-Data3 and the corresponding relation of business partition directory N2 can be Pass through what division obtained on the basis of this mapping table of Ver1 version.For example, this Ver1 This mapping table of version may include ticket time started section Data1-Data2 and business partition directory N1 Corresponding relation, and, the corresponding pass of ticket time started section Data2-DataN and business partition directory N2 System.Wherein, the time difference of DataN and Data2, can be more than, the time difference of Data2 and Data1.Should The time difference of Data2 and Data1 can be default time difference.If ticket starts in this mapping table Between section unit be year, DataN for example can be 9999.If the time started Data3 of current ticket, It is less than DataN more than Data2, and the time difference of Data3 and Data2 is this default time difference, then will The corresponding relation of this ticket time started section Data2-DataN and business partition directory N2 is split into, ticket Time started section Data2-Data3 and the corresponding relation of business partition directory N2, and ticket time started section Data3-DataN and the corresponding relation of business partition directory N3, obtain Ver2 this corresponding relation corresponding Table.In table 2, Ver3 with Ver4 this mapping table corresponding can be obtained using method similar as follows , will not be described here.
Optionally, above-mentioned steps determine that the mapping table of ticket time started section and business partition directory can To include：
Determine that this correspondence is closed according to the business subregion mapped file in the corresponding operation list of this pending ticket It is table.
Specifically, the business subregion mapped file in the corresponding operation list of this pending ticket can be for should Business root (Root) file in the corresponding operation list of pending ticket, this business root file can represent For 0.dat file.This mapping table can be saved in this business subregion mapped file.
Optionally, the fileinfo of this business subregion mapped file can be in memory-resident that is to say, that Therefore determine that this correspondence is closed according to the business subregion mapped file in the corresponding operation list of this pending ticket It is table, can be the fileinfo according to this business subregion mapped file in internal memory, determine that this correspondence is closed It is table.
This correspondence is being determined according to the business subregion mapped file in the corresponding operation list of this pending ticket Before relation table, the method may also include：
Judge the fileinfo whether in this internal memory with this business subregion mapped file；
If it is not, then the fileinfo of this business subregion mapped file is preserved to this internal memory；
If it is determined that the fileinfo of this business subregion mapped file in this internal memory.
Specifically, judge the fileinfo whether in this internal memory with this business subregion mapped file, permissible It is to judge whether this business subregion mapped file is loaded into internal memory, if so, then there is in this internal memory this business and divide The fileinfo of area's mapped file.
Optionally, according to other ginsengs outside this partial parameters in this re-scheduling factor in S203 in above-described embodiment Number judges whether the processed ticket in the corresponding business partition directory of this pending ticket has to be waited to locate with this Reason ticket identical ticket may include：
S304, according to time started of this pending ticket apart from Preset Time absolute time, determining should The filename of pending ticket.
Specifically, this Preset Time can be with 0 second 0 point of on January 1st, 1970.The opening of this pending ticket The absolute time of beginning time gap Preset Time, can be that the time started distance of this pending ticket is default The absolute number of seconds of time.In this S304 can be by the time started of this pending ticket apart from this default when Between absolute time, such as distance 0 point of absolute number of seconds of 0 second of on January 1st, 1970, pending as this The system timestamp (TimeStamp, abbreviation TS) of ticket, and the system time by this pending ticket Stamp is defined as the filename of this pending ticket.
S305, judge whether there is in internal memory this pending ticket pair according to the filename of this pending ticket The fileinfo answered.
Specifically, for ensureing to judge whether to have in internal memory the standard of the corresponding fileinfo of this pending ticket Really property, at least needs to ensure to have in this internal memory the business subregion in the corresponding operation list of this pending ticket The fileinfo of the processed ticket in catalogue.
Therefore, judge that whether having this in internal memory treats according to the filename of this pending ticket in this S305 Before processing the corresponding fileinfo of ticket, the method may also include：
Judge whether to have the processed ticket of the corresponding business partition directory of this pending ticket in this internal memory Fileinfo；
If it is not, the fileinfo by the processed ticket in corresponding for this pending ticket business partition directory It is stored in this internal memory；
If so, then execute this S305, judge whether have in internal memory according to the filename of this pending ticket There is the corresponding fileinfo of this pending ticket.
Specifically, judge whether to have the corresponding business partition directory of this pending ticket in this internal memory Process the fileinfo of ticket, can be the place judging the corresponding business partition directory of this pending ticket Whether the fileinfo of reason ticket is loaded into internal memory.
Therefore, whether have in judging this internal memory in the corresponding business partition directory of this pending ticket Before the fileinfo of processed ticket, also can determine whether that the corresponding business partition directory of this pending ticket is No have processed ticket.If the corresponding business partition directory of this pending ticket does not have processed ticket, Then can directly determine this pending ticket non-duplicate ticket, the fileinfo of this pending ticket is protected then Deposit the fileinfo creating this pending ticket to this internal memory in this internal memory；If this pending word Single corresponding business partition directory has processed ticket, then judge whether to have this in this internal memory pending The fileinfo of the processed ticket of ticket corresponding business partition directory.
In the case of the memory capacity of this internal memory is conditional, for ensureing the accuracy of ticket re-scheduling, can be by In this internal memory, untapped fileinfo is eliminated at most, such as deletes, or preserves to other storage media In.
If having the corresponding fileinfo of this pending ticket in this internal memory of S306, judge this document information In whether there is the corresponding key value of this other specification.
Specifically, judge whether there is in this document information the corresponding key value of this other specification, Ke Yishi, Judge the modulus value of the corresponding default integer of each parameter in this other specification, with file header in this document information (FileHead) key value of the corresponding data offset (DataOffSet) of this default integer in (KeyValue) whether identical.If identical, there is in this document information the corresponding pass of this other specification Key assignments, determines and has in this processed ticket and this pending ticket identical ticket；If it is different, then should There is no in fileinfo the corresponding key value of this other specification, determine do not have in this processed ticket with This pending ticket identical ticket, then can determine that in this processed ticket and do not have and this pending ticket Identical ticket.
If this default integer is 1,000,000, the modulus value of the corresponding default integer of each parameter in this other specification, Can be according to this 1,000,000 modulus value that each parameter in this other specification is carried out with delivery acquisition.This document is believed In file header in breath, this default integer can pass through this default integer corresponding Hash codes (HashCode) table Show.
Fig. 4 is that the structure of the corresponding fileinfo of this pending ticket in internal memory in the embodiment of the present invention two is shown It is intended to.As shown in figure 4, the corresponding fileinfo of this pending ticket may include Part I and second Point, wherein, Part I can be file header, and file header includes the corresponding data-bias of multiple Hash codes Amount, Part II may include the corresponding key value of each data offset in this document head.For example, if This default integer is 1, the Hash codes of this default integer 1, i.e. Hash codes 1 in file header in this document information In corresponding data offset 1, key value 1 can be value 0.Judge whether there is this in this document information The corresponding key value of other specification, can be to judge the corresponding default integer 1 of each parameter in this other specification Modulus value, if identical with 0, if so, then there is in this document information the corresponding key of this other specification Value, if it is not, then do not have the corresponding key value of this other specification in this document information.
If there is no the corresponding Hash codes of this default integer in the file header of this document information, can directly determine There is no in this document information the corresponding key value of this other specification, therefore, can be the of this document information Increase Hash codes and the corresponding data offset of this Hash codes of this default integer in the file header of a part, Increase the key value of the corresponding data offset of this Hash codes in the second portion.
If there is the corresponding keyword of this other specification in the corresponding fileinfo of this pending ticket of S307 Value, determine and have in this processed ticket and this pending ticket identical ticket.
Optionally, whether judge in internal memory according to the filename of this pending ticket in S305 as above There is the corresponding fileinfo of this pending ticket may include：
Filename according to this pending ticket and the mapping table of default filename and memory address, Determine the corresponding memory address of this pending ticket；
Using the fileinfo preserving in corresponding for this pending ticket memory address as this pending ticket pair The fileinfo answered.
Optionally, if the type of service of this pending ticket includes：Short message service, this other specification can be wrapped Include this pending ticket other party number, in the end time of this pending ticket at least one.
Alternately, if the type of service of this pending ticket includes talk business, this other specification can be wrapped Include end time of this pending ticket, the type of call of this pending ticket, this pending ticket right In square number at least one.
Alternately, if the type of service of this pending ticket includes data service, this other specification can be wrapped Include：In the network type of this pending ticket, the flow information of this pending ticket at least one.
The calling list rearrangement method that the embodiment of the present invention two provides, also can be according to the service class of this pending ticket Type, determines the corresponding file directory of this pending ticket, the time started according to this pending ticket then The corresponding business partition directory of this pending ticket is determined in the corresponding file directory of this pending ticket, Then the processed ticket being directed in the corresponding business partition directory of this pending ticket carries out ticket re-scheduling, The quantity of the processed ticket of ticket re-scheduling can be reduced, improve the efficiency of ticket re-scheduling.Meanwhile, by sentencing Whether there is in disconnected internal memory the corresponding fileinfo of this pending ticket, this being then directed in this internal memory is treated Process the corresponding fileinfo of ticket, determine in the corresponding business partition directory of this pending ticket whether have Have single-phase with this pending good word with ticket, due to only storing the corresponding industry of this pending ticket in internal memory The fileinfo of processed ticket in business partition directory, and not processed ticket, can improve re-scheduling effect Rate, while preserving re-scheduling accuracy, reduces the memory capacity shared by processed ticket needed for ticket re-scheduling.
The embodiment of the present invention three may also provide a kind of calling list rearrangement method.Fig. 5 carries for the embodiment of the present invention three For a kind of calling list rearrangement method flow chart.The calling list rearrangement method that this embodiment three provides can be by routeing Node device executes.As shown in figure 5, the method may include：
S501, determine the re-scheduling factor of this pending ticket according to pending ticket；This re-scheduling factor includes Multiple parameters.
S502, send re-scheduling request message, this re-scheduling to the corresponding back end equipment of this pending ticket Request message includes this re-scheduling factor；This re-scheduling request message is used for making this back end equipment according to this row Partial parameters in repeated factor determine the corresponding business partition directory of this pending ticket, according to this re-scheduling because In son, the other specification outside this partial parameters judges in the corresponding business partition directory of this pending ticket Process whether ticket has and this pending ticket identical ticket.
The calling list rearrangement method that the embodiment of the present invention three provides, is the corresponding route of above-described embodiment one or two The calling list rearrangement method of node device execution, its advantage and realize process and can refer to above-described embodiment, Will not be described here.
Optionally, this partial parameters includes：The type of service of this pending ticket and this pending ticket Time started.
Optionally, to the corresponding back end equipment transmission re-scheduling request of this pending ticket in above-mentioned S502 Before message, the method also includes：
The corresponding back end of this pending ticket is determined according to the corresponding service access code of this pending ticket Equipment.
Optionally, according to the corresponding service access code of this pending ticket, step determines that this waits to locate as mentioned Reason ticket corresponding back end equipment includes：
According to default integer value, the standard information permuted code of the preset characters in this service access code is carried out Delivery, obtains modulus value；
According to this modulus value and modulus value and the mapping table of back end equipment, determine that this modulus value is corresponding Back end equipment is the corresponding back end equipment of this pending ticket.
Specifically, this standard information permuted code can be ASCII (American Standard Code for Information Interchange, abbreviation ASCII).
This service access code can include the corresponding traffic identification code of this pending ticket；This traffic identification code Including：Business account information.This business account information can be the telex network number of this process ticket, As telephone number.This business account information can also be User logs in account, such as the use of broadband data service Family login account.If this service access code is telephone number, such as 185xxxxxx78.If this is default whole Numerical value is 3, and the preset characters in this service access code are the last character 8 of this service access code.That According to default integer value, the standard information permuted code of the preset characters in this service access code is taken Mould, can be according to default integer value 3, carry out delivery to the ASCII of character 8, then arrive modulus value 2.
If this corresponding back end equipment of modulus value 2, such as the 2nd back end equipment, then this pending word Single corresponding back end equipment can be the 2nd back end equipment.
Optional, if the type of service of this pending ticket includes：Short message service, this other specification can be wrapped Include：The other party number of this pending ticket, in the end time of this pending ticket at least one.
Optionally, if the type of service of this pending ticket includes：Talk business, this other specification can be wrapped Include：The end time of this pending ticket, the type of call of this pending ticket, this pending ticket In other party number at least one.
Optionally, if the type of service of this pending ticket includes：Data service, this other specification can be wrapped Include：In the network type of this pending ticket, the flow information of this pending ticket at least one.
The calling list rearrangement method that the embodiment of the present invention three provides, is the corresponding route of above-described embodiment one or two The calling list rearrangement method of node device execution, its advantage and realize process and can refer to above-described embodiment, Will not be described here.
The embodiment of the present invention four also provides a kind of calling list rearrangement method.Fig. 6 provides for the embodiment of the present invention four The applicable network system of calling list rearrangement method structural representation.As shown in fig. 6, this example IV Calling list rearrangement method be suitable for network system can include routing node device 601 and the first back end Equipment 602 and the second back end equipment 603.The calling list rearrangement method of this example IV can be by this Fig. 6 In routing node device 601 back end equipment corresponding with pending ticket interaction execution.
The ticket storage organization that Fig. 7 is suitable for for the calling list rearrangement method that the embodiment of the present invention four provides is illustrated Figure.As shown in fig. 7, in this calling list rearrangement method, the logical structure that ticket storage organization stores for ticket Figure.In this Fig. 7, re-scheduling master catalogue may include multiple back end partition directory, such as data0, data1, Tri- data partition of nodes catalogues of data2.Each back end subregion in the plurality of back end partition directory Catalogue can be the corresponding storage catalogue of data node device.Each back end partition directory May include multiple operation lists, such as two operation lists of service100 and service103.Each business mesh Record may include business root file, multiple business partition directory, and the plurality of business partition directory is corresponding many Individual business partitioned file.Business root file can be 0.dat, the plurality of business partition directory may include as Multiple business partition directory shown in part0 and part1, the plurality of business partitioned file can include as Multiple business partitioned files of part0.dat and part1.dat.Each business partition directory may include at least one Individual data file, the data file as shown in 337231098.dat and 337892722.dat.This every number Can be the corresponding data file of ticket according to file.The title of this each data file can be that this is every The time started of the corresponding ticket of individual data file apart from Preset Time, 0 point 0 of on January 1st, 1 Second, absolute number of seconds.
A kind of flow chart of calling list rearrangement method that Fig. 8 provides for the embodiment of the present invention four.As shown in figure 8, The method may include：
S801, routing node device determine the re-scheduling factor of this pending ticket according to pending ticket.
This re-scheduling factor include the type of service of this pending ticket, the time started of this pending ticket, The end time of this pending ticket and the numbers of calling and called parties of this pending ticket.
This routing node device can be by being decoded to this pending ticket, and according to this decoding after This pending ticket determine this repetition factor.This routing node device is decoded to this pending ticket, For example this pending ticket can be converted to this routing node device pair by the corresponding form of Record Bill Server The form answered.For ensureing the information integrity of this pending ticket that this routing node device receives, should Routing node device, after this pending ticket is decoded, also can enter row information to this pending ticket Verification.
S802, routing node device according to the first default integer to this pending ticket corresponding service access The preset characters of code carry out delivery and obtain the first modulus value and determine that this pending ticket corresponds to according to the first modulus value Back end equipment.
The corresponding service access code of this pending ticket for example can be for the corresponding user's of this pending ticket Communicating number, such as telephone number, or, user carries out the login account of broadband data service.
If the service access code of this pending ticket is the corresponding subscriber directory number of this pending ticket, such as 185xxxxxx78.This preset characters can be for example last of the service access code of this pending ticket Character.Therefore, this routing node device root can correspond to this pending ticket according to the first default integer 3 The last character 8 of service access code carry out delivery, obtain the first modulus value 2.This routing node sets Standby can be according to this first modulus value, and the mapping table of modulus value and back end equipment determine this first Modulus value corresponding data node device is the corresponding back end of this pending ticket.This pending ticket corresponds to Back end equipment can be for example the second back end equipment.
Alternately, this routing node device can also be and determines this re-scheduling factor according to this pending ticket In the corresponding back end equipment of this pending ticket of parameter determination.For example, this routing node sets Standby can be to determine corresponding for the time period residing for the time started of this pending ticket back end equipment For the corresponding back end equipment of this pending ticket.Change single time started if this is pending in 2014 Before December 31, then the corresponding back end equipment of this pending ticket can be for example the first data section Point device.Change single time started if this is pending after 1 day January in 2015, this pending ticket Corresponding back end equipment can be for example the second back end equipment.
S803, routing node device send re-scheduling request to pending ticket corresponding back end equipment and disappear Breath, this re-scheduling request message includes this re-scheduling factor.
S804, back end equipment judge in back end equipment according to the type of service of this pending ticket Whether there is the corresponding operation list of this pending ticket.
This back end equipment is the corresponding back end equipment of this pending ticket.
If it is not, then executing S805, if so, then execute S806.
S805, back end equipment determine that this pending ticket is not to repeat ticket.
S806, back end equipment are according to business subregion mapping in the corresponding operation list of this pending ticket File determines the mapping table of ticket time period and business partition directory.
S807, back end equipment are according to time started of this pending ticket and this mapping table at this Determine in the corresponding operation list of pending ticket that the time period that the time started is located of this pending ticket corresponds to Business partition directory be the corresponding business partition directory of this pending ticket.
S808, back end equipment are absolute apart from Preset Time according to the time started of this pending ticket Number of seconds determines the filename of this pending ticket.
This Preset Time can be 0 second 0 point of on January 1st, 1970.
S809, back end equipment judge the business subregion mesh in the corresponding operation list of this pending ticket Whether record has processed ticket.
If it is not, execution S810.If so, execute S811.
S810, back end equipment determine that this pending ticket is not to repeat ticket, preserve and treat in internal memory Process the corresponding fileinfo of ticket.
S811, back end equipment judge whether to have the corresponding business subregion of this pending ticket in internal memory The fileinfo of the processed ticket of catalogue.
Execute S812 and S813 if not；If so, execute S813.
S812, back end equipment are by the processed ticket of corresponding for this pending ticket business partition directory File information storage to this internal memory.
S813, back end equipment are according to the filename of this pending ticket and default filename and internal memory The mapping table of address determines the corresponding memory address of this pending ticket and corresponds to this pending ticket Memory address in the fileinfo that preserves as the corresponding fileinfo of this pending ticket.
S814, back end equipment are according to the second default integer to this pending ticket in this re-scheduling factor In other specification outside the time started of type of service and this pending ticket, each parameter carries out delivery and obtains the Two modulus value.
It is second default whole that S815, back end equipment judge whether to have this in file header in this document information The key value of the corresponding data offset of number.
If it is not, then executing S816；If so, then execute S817.
S816, back end equipment determine that this pending ticket is not to repeat ticket this is second default whole The key value of the corresponding data offset of number is stored in this document information.
S817, back end equipment judge that in file header in this second modulus value and this document information, this is default whole Whether the key value of the corresponding data offset of number is identical.
If it is not, then executing S818, if so, then executing S819.
S818, back end equipment determine do not there is the corresponding key value of this other specification in this document information, This pending ticket is not to repeat ticket.
In above steps, if this pending ticket is not to repeat ticket, this back end equipment can Insert re-scheduling record in internal memory.
S819, back end equipment determine there is the corresponding key value of this other specification in this document information, This pending ticket is to repeat ticket.
If this pending ticket is to repeat ticket, this back end equipment can send to this routing node device Re-scheduling confirms message, to indicate that this pending equipment of this routing node device is to repeat ticket.This route section Point device also can generate that this pending ticket is corresponding wrong single to indicate message, to represent that this pending ticket is Repeat ticket.This routing node device also can to this pending ticket and repeat ticket carry out ticket merge or Telephone bill association etc. processes operation, and exports the ticket after process, and the ticket after this process is converted to down The trip corresponding form of system equipment.This down-stream system equipment, can be the accounting server in charge system Or through in subsystem through sub-server.
The embodiment of the present invention four is by specific example to arbitrary described in above-described embodiment one to embodiment three Calling list rearrangement method illustrate, its advantage is similar to the above embodiments, will not be described here.
The embodiment of the present invention five also provides a kind of back end equipment.Fig. 9 provides for the embodiment of the present invention five A kind of back end equipment structural representation.As shown in figure 9, back end equipment 900 includes：
Acquisition module 901, for obtaining the re-scheduling factor of pending ticket；This re-scheduling factor includes：Root The multiple parameters determining according to this pending ticket.
Determining module 902, for determining this pending ticket pair according to the partial parameters in this re-scheduling factor The business partition directory answered.
Judge module 903, for judging to be somebody's turn to do according to the other specification outside this partial parameters in this re-scheduling factor Whether the processed ticket in the corresponding business partition directory of pending ticket has and this pending ticket phase Same ticket.
Determining module 902, if be additionally operable in this processed ticket to have identical with this pending ticket if List is it is determined that this pending ticket is to repeat ticket.
Optionally, back end equipment 900 also includes：
Receiver module, for receiving the re-scheduling request message of routing node device transmission；The request of this re-scheduling disappears Breath includes：This re-scheduling factor；It is true according to this pending ticket that this re-scheduling factor includes this routing node device Fixed multiple parameters.
Optionally, this partial parameters includes：The type of service of this pending ticket and this pending ticket Time started.
Determining module 902, is additionally operable to determine this pending ticket according to the type of service of this pending ticket Corresponding operation list, the time started according to this pending ticket is in the corresponding business of this pending ticket The corresponding business partition directory of this pending ticket is determined in catalogue.
Optionally, determining module 902, are additionally operable to determine ticket time started section and business partition directory Mapping table, the time started according to this pending ticket and this mapping table are in this pending ticket In corresponding operation list, determine that the time started section at the time started place of this pending ticket is corresponding Business partition directory is the corresponding business partition directory of this pending ticket.
Optionally, determining module 902, are additionally operable to according in the corresponding operation list of this pending ticket Business subregion mapped file determines this mapping table.
Optionally, determining module 902, the time started distance being additionally operable to according to this pending ticket is default The absolute time of time, determines the filename of this pending ticket.
Judge module 903, is additionally operable to judge whether have in internal memory according to the filename of this pending ticket The corresponding fileinfo of this pending ticket, if having the corresponding file letter of this pending ticket in this internal memory Breath, judges whether there is the corresponding key value of this other specification in this document information.
Determining module 902, if be additionally operable in the corresponding fileinfo of this pending ticket have this other ginseng The corresponding key value of number, determines and has in this processed ticket and this pending ticket identical ticket.
Optionally, determining module 902, are additionally operable to filename according to this pending ticket and default The mapping table of filename and memory address, determines the corresponding memory address of this pending ticket, should The fileinfo preserving in the corresponding memory address of pending ticket is defined as the corresponding literary composition of this pending ticket Part information.
Optionally, judge module 903, are additionally operable to judge whether there is this pending ticket pair in this internal memory The corresponding fileinfo of processed ticket in the business partition directory answered；If there is in this internal memory this wait to locate The corresponding fileinfo of processed ticket in reason ticket corresponding business partition directory, pending according to this The filename of ticket judges whether to have the corresponding fileinfo of this pending ticket in this internal memory.
Optionally, if the type of service of this pending ticket includes：Short message service, this other specification includes： The other party number of this pending ticket, in the end time of this pending ticket at least one.
Optionally, if the type of service of this pending ticket includes：Talk business, this other specification includes： The end time of this pending ticket, the type of call of this pending ticket, the other side of this pending ticket In number at least one.
Optionally, if the type of service of this pending ticket includes：Data service, this other specification includes： In the network type of this pending ticket, the flow information of described pending ticket at least one.
The back end equipment that the embodiment of the present invention five provides, can be used for executing above-described embodiment one or implements The calling list rearrangement method that example two provides, its advantage is similar to the above embodiments, will not be described here.
The embodiment of the present invention six also provides a kind of routing node device.Figure 10 provides for the embodiment of the present invention six A kind of routing node device structural representation.As shown in Figure 10, routing node device 1000 can wrap Include：
Determining module 1001, for determining the re-scheduling factor of this pending ticket according to pending ticket；Should The re-scheduling factor includes multiple parameters.
Sending module 1002, being additionally operable to send re-scheduling to the corresponding back end equipment of this pending ticket please Seek message, this re-scheduling request message includes this re-scheduling factor；This re-scheduling request message is used for making this data section Point device determines the corresponding business subregion mesh of this pending ticket according to the partial parameters in this re-scheduling factor Record, judges the corresponding industry of this pending ticket according to the other specification outside this partial parameters in this re-scheduling factor Whether the processed ticket in business partition directory has and this pending ticket identical ticket.
Optionally, this partial parameters includes：The type of service of this pending ticket and this pending ticket Time started.
Optionally, determining module 1001, are additionally operable to true according to the corresponding service access code of this pending ticket The corresponding back end equipment of fixed this pending ticket.
Optionally, determining module 1001, are additionally operable to according to default integer value in this service access code The standard code for information interchange of preset characters carries out delivery, obtains modulus value；According to this modulus value and modulus value and number According to the mapping table of node device, determine that this modulus value corresponding back end equipment is this pending ticket Corresponding back end equipment.
Optionally, this service access code includes the corresponding traffic identification code of this pending ticket；This business is known Other code includes：Business account information.
Optionally, if the type of service of this pending ticket includes：Short message service, this other specification includes： The other party number of this pending ticket, in the end time of this pending ticket at least one.
Optionally, if the type of service of this pending ticket includes：Talk business, this other specification includes： The end time of this pending ticket, the type of call of this pending ticket, the other side of this pending ticket In number at least one.
Optionally, if the type of service of this pending ticket includes：Data service, this other specification includes： In the network type of this pending ticket, the flow information of this pending ticket at least one.
The routing node device that the embodiment of the present invention six provides, can be used for executing what above-described embodiment three provided Calling list rearrangement method, its advantage is similar to the above embodiments, will not be described here.
One of ordinary skill in the art will appreciate that：Realize all or part step of above-mentioned each method embodiment Suddenly can be completed by the related hardware of programmed instruction.Aforesaid program can be stored in a computer can Read in storage medium.This program upon execution, executes the step including above-mentioned each method embodiment；And Aforesaid storage medium includes：ROM, RAM, magnetic disc or CD etc. are various can be with store program codes Medium.
Finally it should be noted that：Various embodiments above is only in order to illustrating technical scheme rather than right It limits；Although being described in detail to the present invention with reference to foregoing embodiments, this area common Technical staff should be understood：It still can be modified to the technical scheme described in foregoing embodiments, Or equivalent is carried out to wherein some or all of technical characteristic；And these modifications or replacement, and Do not make the scope of the essence disengaging various embodiments of the present invention technical scheme of appropriate technical solution.

Claims (38)

1. a kind of calling list rearrangement method is it is characterised in that include：
Obtain the re-scheduling factor of pending ticket；The described re-scheduling factor includes：According to described pending ticket The multiple parameters determining；
Determine described pending ticket corresponding business subregion mesh according to the partial parameters in the described re-scheduling factor Record；
Other specification outside partial parameters according to the described re-scheduling factor judges described pending ticket pair Whether the processed ticket in the business partition directory answered has and described pending ticket identical ticket；
If having in described processed ticket with described pending ticket identical ticket it is determined that described treat Processing ticket is to repeat ticket.
2. method according to claim 1 is it is characterised in that the row of the pending ticket of described acquisition Repeated factor, including：
Receive the re-scheduling request message that routing node device sends；Described re-scheduling request message includes：Described The re-scheduling factor；The described re-scheduling factor includes what described routing node device determined according to described pending ticket Multiple parameters.
3. method according to claim 1 and 2 is it is characterised in that described partial parameters include： The type of service of described pending ticket and the time started of described pending ticket；
Described determine that the corresponding business of described pending ticket is divided according to the partial parameters in the described re-scheduling factor Area's catalogue, including：
The corresponding operation list of described pending ticket is determined according to the type of service of described pending ticket；
Time started according to described pending ticket in the corresponding operation list of described pending ticket really Determine the corresponding business partition directory of described pending ticket.
4. method according to claim 3 it is characterised in that described according to described pending ticket Time started determine that described pending ticket is corresponding in the corresponding operation list of described pending ticket Business partition directory includes：
Determine the mapping table of ticket time started section and business partition directory；
Time started according to described pending ticket and described mapping table are in described pending ticket pair In the operation list answered, determine that the time started section at the time started place of described pending ticket is corresponding Business partition directory is the corresponding business partition directory of described pending ticket.
5. method according to claim 4 is it is characterised in that described determination ticket time started section Include with the mapping table of business partition directory：
It is described right to be determined according to the business subregion mapped file in the corresponding operation list of described pending ticket Answer relation table.
6. the method according to any one of claim 3-5 is it is characterised in that described in described basis Other specification outside partial parameters described in the re-scheduling factor judges the corresponding business subregion of described pending ticket Whether the processed ticket in catalogue has and described pending ticket identical ticket, including：
Time started according to described pending ticket apart from the absolute time of Preset Time, treats described in determination Process the filename of ticket；
Judge that whether having described pending ticket in internal memory corresponds to according to the filename of described pending ticket Fileinfo；
If having the corresponding fileinfo of described pending ticket in described internal memory, judge described fileinfo In whether there is the corresponding key value of described other specification；
If there is the corresponding key value of described other specification in the corresponding fileinfo of described pending ticket, Determine and have in described processed ticket and described pending ticket identical ticket.
7. method according to claim 6 it is characterised in that described according to described pending ticket Filename judge that whether having the corresponding fileinfo of described pending ticket in internal memory includes：
Filename according to described pending ticket and the mapping relations of default filename and memory address Table, determines the corresponding memory address of described pending ticket；
Using the fileinfo preserving in corresponding for described pending ticket memory address as described pending words Single corresponding fileinfo.
8. the method according to claim 6 or 7 it is characterised in that described according to described pending Before the filename of ticket judges whether to have the corresponding fileinfo of described pending ticket in internal memory, institute Method of stating also includes：
Judge the place whether having in the corresponding business partition directory of described pending ticket in described internal memory The reason corresponding fileinfo of ticket；
The described filename according to described pending ticket judges whether there is described pending ticket in internal memory Corresponding fileinfo, including：
If having the processed ticket in the corresponding business partition directory of described pending ticket in described internal memory Corresponding fileinfo, judges whether to have institute in described internal memory according to the filename of described pending ticket State the corresponding fileinfo of pending ticket.
9. if the method according to any one of claim 3-8 is it is characterised in that described pending The type of service of ticket includes：Short message service, described other specification includes：Described pending ticket right Square number, in the end time of described pending ticket at least one.
If the method 10. according to any one of claim 3-8 is it is characterised in that described wait to locate The type of service of reason ticket includes：Talk business, described other specification includes：Described pending ticket End time, the type of call of described pending ticket, in the other party number of described pending ticket at least One.
If 11. methods according to any one of claim 3-8 are it is characterised in that described wait to locate The type of service of reason ticket includes：Data service, described other specification includes：Described pending ticket In network type, the flow information of described pending ticket at least one.
A kind of 12. calling list rearrangement methods are it is characterised in that include：
Determine the re-scheduling factor of described pending ticket according to pending ticket；The described re-scheduling factor includes many Individual parameter；
Send re-scheduling request message to the corresponding back end equipment of described pending ticket, described re-scheduling please Message is asked to include the described re-scheduling factor；Described re-scheduling request message be used for making described back end equipment according to Partial parameters in the described re-scheduling factor determine the corresponding business partition directory of described pending ticket, according to Other specification outside partial parameters described in the described re-scheduling factor judges the corresponding business of described pending ticket Whether the processed ticket in partition directory has and described pending ticket identical ticket.
13. methods according to claim 12 are it is characterised in that described partial parameters include：Institute State the type of service of pending ticket and the time started of described pending ticket.
14. methods according to claim 12 or 13 are it is characterised in that described wait to locate to described Before reason ticket corresponding back end equipment sends re-scheduling request message, methods described also includes：
The corresponding data of described pending ticket is determined according to the corresponding service access code of described pending ticket Node device.
15. methods according to claim 14 it is characterised in that described according to described pending words Single corresponding service access code determines that the corresponding back end equipment of described pending ticket includes：
According to default integer value, the standard code for information interchange of the preset characters in described service access code is entered Row delivery, obtains modulus value；
According to described modulus value and modulus value and the mapping table of back end equipment, determine described modulus value pair The back end equipment answered is the corresponding back end equipment of described pending ticket.
16. according to claims 14 or 15 methods described it is characterised in that described service access code bag Include：The corresponding traffic identification code of described pending ticket；Described traffic identification code includes：Business account is believed Breath.
If 17. methods according to any one of claim 13-16 are it is characterised in that this waits to locate The type of service of reason ticket includes：Short message service, described other specification includes：Described pending ticket Other party number, in the end time of described pending ticket at least one.
If 18. methods according to any one of claim 13-16 are it is characterised in that described treat The type of service processing ticket includes：Talk business, described other specification includes：Described pending ticket End time, the type of call of described pending ticket, in the other party number of described pending ticket extremely Few one.
If 19. methods according to any one of claim 13-16 are it is characterised in that described treat The type of service processing ticket includes：Data service, described other specification includes：Described pending ticket Network type, in the flow information of described pending ticket at least one.
A kind of 20. back end equipment are it is characterised in that include：
Acquisition module, for obtaining the re-scheduling factor of pending ticket；The described re-scheduling factor includes：According to The multiple parameters that described pending ticket determines；
Determining module, for determining described pending ticket pair according to the partial parameters in the described re-scheduling factor The business partition directory answered；
Judge module, for partial parameters according to the described re-scheduling factor outside other specification judge institute State whether the processed ticket in pending ticket corresponding business partition directory has and described pending words Single-phase same ticket；
Described determining module, if be additionally operable in described processed ticket to have identical with described pending ticket Ticket it is determined that described pending ticket be repeat ticket.
21. back end equipment according to claim 20 are it is characterised in that described back end Equipment also includes：
Receiver module, for receiving the re-scheduling request message of routing node device transmission；Described re-scheduling request Message includes：The described re-scheduling factor；The described re-scheduling factor includes described routing node device and is treated according to described Process the multiple parameters that ticket determines.
22. back end equipment according to claim 20 or 21 are it is characterised in that described portion Point parameter includes：The type of service of described pending ticket and the time started of described pending ticket；
Described determining module, is additionally operable to be determined according to the type of service of described pending ticket described pending The corresponding operation list of ticket, the time started according to described pending ticket is in described pending ticket pair The corresponding business partition directory of described pending ticket is determined in the operation list answered.
23. back end equipment according to claim 22 it is characterised in that
Described determining module, is additionally operable to determine the corresponding relation of ticket time started section and business partition directory Table, the time started according to described pending ticket and described mapping table are in described pending ticket pair In the operation list answered, determine that the time started section at the time started place of described pending ticket is corresponding Business partition directory is the corresponding business partition directory of described pending ticket.
24. back end equipment according to claim 23 it is characterised in that
Described determining module, is additionally operable to be divided according to the business in the corresponding operation list of described pending ticket Area's mapped file determines described mapping table.
25. back end equipment according to any one of claim 22-24 it is characterised in that
Described determining module, is additionally operable to time started according to described pending ticket apart from Preset Time Absolute time, determines the filename of described pending ticket；
Described judge module, is additionally operable to judge whether have in internal memory according to the filename of described pending ticket There is the corresponding fileinfo of described pending ticket, if there is in described internal memory described pending ticket corresponding to Fileinfo, judge whether there is in described fileinfo the corresponding key value of described other specification；
Described determining module, if be additionally operable in the corresponding fileinfo of described pending ticket to have described its The corresponding key value of his parameter, determines and has in described processed ticket and described pending ticket identical Ticket.
26. back end equipment according to claim 25 it is characterised in that
Described determining module, is additionally operable to the filename according to described pending ticket and default filename With the mapping table of memory address, determine the corresponding memory address of described pending ticket, treat described Process the fileinfo preserving in the corresponding memory address of ticket and be defined as the corresponding literary composition of described pending ticket Part information.
27. back end equipment according to claim 25 or 26 it is characterised in that
Described judge module, is additionally operable to judge whether to have described pending ticket in described internal memory corresponding The corresponding fileinfo of processed ticket in business partition directory；If waiting to locate described in having in described internal memory The corresponding fileinfo of processed ticket in reason ticket corresponding business partition directory, waits to locate according to described The filename of reason ticket judges whether there is the corresponding fileinfo of described pending ticket in described internal memory.
28. back end equipment according to any one of claim 22-27 it is characterised in that If the type of service of described pending ticket includes：Short message service, described other specification includes：Described treat Process ticket other party number, in the end time of described pending ticket at least one.
29. back end equipment according to any one of claim 22-27 it is characterised in that If the type of service of described pending ticket includes：Talk business, described other specification includes：Described treat The end time of process ticket, the type of call of described pending ticket, the other side of described pending ticket In number at least one.
30. back end equipment according to any one of claim 22-27 it is characterised in that If the type of service of described pending ticket includes：Data service, described other specification includes：Described treat Process the network type of ticket, in the flow information of described pending ticket at least one.
A kind of 31. routing node devices are it is characterised in that include：
Determining module, for determining the re-scheduling factor of described pending ticket according to pending ticket；Described The re-scheduling factor includes multiple parameters；
Sending module, is additionally operable to the corresponding back end equipment transmission re-scheduling request of described pending ticket Message, described re-scheduling request message includes the described re-scheduling factor；Described re-scheduling request message is used for making described Back end equipment determines the corresponding industry of described pending ticket according to the partial parameters in the described re-scheduling factor Business partition directory, other specification outside partial parameters according to the described re-scheduling factor judge described in wait to locate It is identical with described pending ticket whether the processed ticket in reason ticket corresponding business partition directory has Ticket.
32. routing node devices according to claim 31 are it is characterised in that described partial parameters Including：The type of service of described pending ticket and the time started of described pending ticket.
33. routing node devices according to claim 31 or 32 it is characterised in that
Described determining module, is additionally operable to according to the corresponding service access code of described pending ticket determines The corresponding back end equipment of pending ticket.
34. routing node devices according to claim 33 it is characterised in that
Described determining module, is additionally operable to according to default integer value to the predetermined word in described service access code The standard code for information interchange of symbol carries out delivery, obtains modulus value；According to described modulus value and modulus value and data section The mapping table of point device, determines that described modulus value corresponding back end equipment is described pending ticket Corresponding back end equipment.
35. routing node devices according to claim 33 or 34 are it is characterised in that described industry Business access code includes the corresponding traffic identification code of described pending ticket；Described traffic identification code includes：Industry Business account information.
36. routing node devices according to any one of claim 32-35 it is characterised in that If the type of service of this pending ticket includes：Short message service, described other specification includes：Described wait to locate Reason ticket other party number, in the end time of described pending ticket at least one.
37. routing node devices according to any one of claim 32-35 it is characterised in that If the type of service of described pending ticket includes：Talk business, described other specification includes：Described treat The end time of process ticket, the type of call of described pending ticket, the other side of described pending ticket In number at least one.
38. routing node devices according to any one of claim 32-35 it is characterised in that If the type of service of described pending ticket includes：Data service, described other specification includes：Described treat Process the network type of ticket, in the flow information of described pending ticket at least one.
CN201510541617.9A 2015-08-28 2015-08-28 Calling list rearrangement method, back end equipment and routing node device Active CN106488055B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201510541617.9A CN106488055B (en) 2015-08-28 2015-08-28 Calling list rearrangement method, back end equipment and routing node device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201510541617.9A CN106488055B (en) 2015-08-28 2015-08-28 Calling list rearrangement method, back end equipment and routing node device

Publications (2)

Publication Number Publication Date
CN106488055A true CN106488055A (en) 2017-03-08
CN106488055B CN106488055B (en) 2019-10-22

Family

ID=58235999

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201510541617.9A Active CN106488055B (en) 2015-08-28 2015-08-28 Calling list rearrangement method, back end equipment and routing node device

Country Status (1)

Country Link
CN (1) CN106488055B (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108990001A (en) * 2017-06-05 2018-12-11 中兴通讯股份有限公司 Calling list rearrangement method, device, storage medium and computer equipment
CN109976896A (en) * 2019-04-09 2019-07-05 中国联合网络通信集团有限公司 Business re-scheduling treating method and apparatus
CN111209272A (en) * 2019-12-26 2020-05-29 杭州亚信云信息科技有限公司 Ticket repetition checking method, device and system
CN111694693A (en) * 2019-03-12 2020-09-22 上海晶赞融宣科技有限公司 Data stream storage method and device and computer storage medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1567821A (en) * 2003-06-24 2005-01-19 华为技术有限公司 Call ticket repetition removing method
KR100802092B1 (en) * 2006-09-14 2008-02-11 주식회사 케이티프리텔 Method and system for billing based on the client-server
CN101159795A (en) * 2007-10-25 2008-04-09 中兴通讯股份有限公司 Calling list rearrangement method and device
CN102169499A (en) * 2011-04-18 2011-08-31 北京神州数码思特奇信息技术股份有限公司 Repeated ticket removing method
CN103037344A (en) * 2012-12-06 2013-04-10 亚信联创科技（中国）有限公司 Call bill repetition removing method and call bill repetition removing device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1567821A (en) * 2003-06-24 2005-01-19 华为技术有限公司 Call ticket repetition removing method
KR100802092B1 (en) * 2006-09-14 2008-02-11 주식회사 케이티프리텔 Method and system for billing based on the client-server
CN101159795A (en) * 2007-10-25 2008-04-09 中兴通讯股份有限公司 Calling list rearrangement method and device
CN102169499A (en) * 2011-04-18 2011-08-31 北京神州数码思特奇信息技术股份有限公司 Repeated ticket removing method
CN103037344A (en) * 2012-12-06 2013-04-10 亚信联创科技（中国）有限公司 Call bill repetition removing method and call bill repetition removing device

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108990001A (en) * 2017-06-05 2018-12-11 中兴通讯股份有限公司 Calling list rearrangement method, device, storage medium and computer equipment
CN108990001B (en) * 2017-06-05 2021-04-20 中兴通讯股份有限公司 Ticket repetition eliminating method, device, storage medium and computer equipment
CN111694693A (en) * 2019-03-12 2020-09-22 上海晶赞融宣科技有限公司 Data stream storage method and device and computer storage medium
CN109976896A (en) * 2019-04-09 2019-07-05 中国联合网络通信集团有限公司 Business re-scheduling treating method and apparatus
CN109976896B (en) * 2019-04-09 2021-06-29 中国联合网络通信集团有限公司 Service re-ranking processing method and device
CN111209272A (en) * 2019-12-26 2020-05-29 杭州亚信云信息科技有限公司 Ticket repetition checking method, device and system
CN111209272B (en) * 2019-12-26 2023-04-18 杭州亚信云信息科技有限公司 Method, device and system for checking call ticket

Also Published As

Publication number Publication date
CN106488055B (en) 2019-10-22

Similar Documents

Publication Publication Date Title
CN104468592B (en) Login method and login system
WO2017091401A1 (en) Identity authentication method, system, business server and authentication server
EP2698967A1 (en) Social network data mining method for terminal user, and relevant method, device and system
CN108259425A (en) The determining method, apparatus and server of query-attack
CN110430288A (en) Node visit method, apparatus, computer equipment and storage medium
US20130311283A1 (en) Data mining method for social network of terminal user and related methods, apparatuses and systems
CN106488055A (en) Calling list rearrangement method, back end equipment and routing node device
CN102868670A (en) Unified registration and logon system as well as registration and logon method for mobile user
CN107241344A (en) Intercept method, apparatus and system of the client to the access of hostile network server
CN106775486A (en) Data access system, method and routing server, configuration center server
CN101674318A (en) Method for pushing data to mobile equipment at regular time
CN105812482B (en) The sharing method and server platform of communication information
CN110198265A (en) Information processing method, system, device, equipment and medium
CN104580310A (en) Log processing method and server
CN108076017A (en) The protocol analysis method and device of a kind of data packet
CN110232633A (en) A kind of electronic signature method, apparatus, storage medium and server
CN105528352B (en) The method for establishing mobile communication subscriber and the corresponding relationship of its network account information
CN109522501A (en) Content of pages management method and its device
CN104426834B (en) A kind of web-page requests method, client, server and system
CN108055653A (en) cloud broadcasting method and system
KR100752351B1 (en) System and method realtime question and answers by communication media which can transfer interactively data or voice
CN108696864A (en) Virtual-number is asked and sending method, device and storage medium
CN108173909A (en) Method of data synchronization, mobile terminal and computer readable storage medium
US20210359938A1 (en) A method and program product for electronic communication based on user action
CN107885734A (en) Interaction language translating method and device

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20200217

Address after: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen

Patentee after: HUAWEI TECHNOLOGIES Co.,Ltd.

Address before: 210012 Ande Gate No. 94, Yuhuatai District, Jiangsu, Nanjing

Patentee before: Huawei Technologies Co.,Ltd.