WO2006003239A1 - Data processing in a mediation or service provisioning system - Google Patents
Data processing in a mediation or service provisioning system Download PDFInfo
- Publication number
- WO2006003239A1 WO2006003239A1 PCT/FI2005/000287 FI2005000287W WO2006003239A1 WO 2006003239 A1 WO2006003239 A1 WO 2006003239A1 FI 2005000287 W FI2005000287 W FI 2005000287W WO 2006003239 A1 WO2006003239 A1 WO 2006003239A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- logic
- function
- processing
- parameters
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4482—Procedural
- G06F9/4484—Executing subprograms
Definitions
- the present invention relates to data processing.
- the present invention relates to processing structured data records, containing data fields and data in the data fields.
- a data record is an event record containing data on usage of a communications network.
- an embodiment of the present invention relates to mediation methods and systems.
- Mediation is a process wherein usage data is collected from communication network and delivered to operator's Operation and Business Support System(s)
- OSS/BSS Mediation software collects usage data from network by interfacing various different network elements. The mediation layer then aggregates, correlates, enriches, validates, formats, and/or rates the data so that it is readable by the target OSS/BSS system(s) and it contains all the required information.
- Continuous streaming mediation which is also called real-time mediation, has been developed to fulfil these requirements. Especially in continuous streaming mediation, quality, reliability and effectiveness of data processing is very important.
- Service provisioning and service activation is a process wherein any types of services in all types of networks are provisioned and activated to network elements. These can be for instance activating all consumer and corporate services, such as voice, ADSL, WLAN access and VPN with the same provisioning system helps the operator to remove lots of costly, unnecessary and overlapping processes.
- Patent publication US 6,449,618 discloses one real-time event processing system.
- the system presented in the publication has a poor flexibility.
- Patent publication US 6,366,657 discloses a system of supporting and managing telecommunications services.
- the principle idea of US 6,366,657 is that the system comprises a Service Creation Environment (SCE), which environment enables to create, provide and manage new services for subscribers easily. This is done by toolkits for specifying object definitions in an object-oriented framework.
- SCE Service Creation Environment
- the system presented in the publication is aimed to telecommunication operators for making services easier.
- the first alternative would be to generate some scripting language from the predefined processing logic.
- One suitable scripting language is Perl.
- Advantage of this approach is that the resulting code can be viewed and is human readable. Hence, the code is easy to debug.
- the scripting language approach there are several disadvantages in the scripting language approach. For example, the performance is relatively low as the scripting languages (even Perl) are slower than native code. It is also difficult to generate valid code and to ensure that the variable names etc. do not cause any conflicts in the system.
- the second alternative would be to generate C or Java source code and compile it before the execution.
- This solution produces the fastest code, if C is used, because no interpreting is needed.
- the problem is to compile the source code and ensure that the system really works correctly.
- the logics created in this way could not be tested before taking into use, if really fast changes to the logic are needed. This makes the system unreliable and risky. Compilation is also very difficult if not impossible because it has to be performed in customer environment and on different platforms. Hence, this approach involves serious risks and is extremely difficult.
- the problems involved in this solution could be solved, the solution would offer a very high performance.
- the object of the invention is achieved by forming a special logic definition structure based on the processing logic.
- the logic definition structure is designed so that it is easy to execute efficiently.
- the logic definition structure is also designed such that making modifications to the processing logic requires relatively limited and straightforward alterations in the logic definition structure. This is made possible by defining the processing logic in the form of a series of byte code instructions, wherein each instruction contains a pointer to a piece of program code performing a function and a pointer to parameters to be used in performing the function.
- the instructions, the program codes performing the functions, the pointers and the data under processing are preferably stored in arrays thus allowing the use of efficient pointer mechanisms together with flexibility and ease of modification.
- the logic definition structure comprises a parameter array containing pointers to the values of the parameters needed in the processing logic, a function code set containing program codes for performing the functions needed in the processing logic, and a series of byte code instructions, each of the instructions pointing to pointers in the parameter array and a function code that are needed in the execution of the instruction.
- the present invention makes it possible to construct a reliable data processing system and method that both provide a relatively high performance and are relatively easy to adapt to new processing logics.
- inventive concept allows also several useful and advantageous embodiments, which provide further advantages.
- adaptation of provisioning logic can be implemented and visualised through graphical user interface. New services and service packages - regardless of their complexity - can be rapidly introduced without having to make timely and costly changes to OSS/BSS system of an operator.
- Invention offers also embodiments of a mediation system, which can be operated continuously once started, because all of the configurations can be made while the system is in production.
- the present invention can be applied in a great variety of applications requiring fast and reliable processing of event records.
- Figure 1 presents a block diagram of a system according to an embodiment of the invention.
- Figure 2 presents a block diagram of an example of functioning according to an embodiment of the invention.
- Figure 3 a presents a block diagram of an example of processing logic function execution according to an embodiment of the invention.
- Figure 3b presents a block diagram of another example of processing logic function execution according to an embodiment of the invention.
- Figure 4 presents a block diagram of an example of a byte code execution according to an embodiment of the invention.
- Figure 5 presents a flow diagram of an example of mediation process according to an embodiment of the invention.
- a data record is a record containing data on e.g. a service usage or provisioning request.
- Data Record typically contains several data fields and may be structured (records contain other records).
- examples of data records include such as CDR, Call Detail Record; ER, Event Record; UDR, Usage Data Record; and IPDR, Internet Protocol Detail Record.
- Field is a single unit of a data record. Normally field contains a value that can be any data (date, integer, string, etc).
- Event is a transaction occurring in a telecommunications network. Events are typically caused by actions taken by a subscriber while using telecommunication services. Events may also be based on actions taken by the telecommunication network or an apparatus connected to it, e.g. while executing telecommunications services. Some events may be even generated automatically while executing service programs and performing other functions for providing services to the customers.
- Event Record is a data record that indicates that an event has occurred. That is, an even record provides information that a subscriber has used a telecommunications service. Event record contains also detailed information about the event. Hence, an event record may contain information on the usage, e.g. if the used telecommunication service is a phone call, the event record may indicate how long the call lasted, or if the service is downloading a file from an FTP server, the event record may contain information about the size of the transferred data block.
- Real time processing refers to passing event record through mediation system in streaming format. That is, as soon as a certain node in mediation stream has processed (e.g. enriched) the record, it is passed to the next node.
- a great number of event records are first collected in an intermediate storage and then the lot of event records is processed from the intermediate storage.
- processing delays experienced by the event records are typically long and vary between the event records.
- processing delays experienced by the event records are typically short and substantially the same in magnitude between the event records.
- Pass-through time in a real-time system may be, e.g. from about 1 millisecond to 10 seconds, hi some embodiments, events may pass through the system even faster. Sometimes, depending on the embodiment and application, the term real-time may also comprise pass-through times longer that stated above.
- a real-time service is a service that does not include considerable delays such that a user of the service considers acts being taken and services provided essentially at the moment the services are ordered (i.e. events supplied to the mediation system).
- Data record that is read by a processing node.
- the format and structure of the input record is preferably predefined and known by the node.
- Processing Logic Executor is a node application in a mediation system. Processing Logic Executor manages predefined processing logic in a processing stream. It executes the user defined rule-set using existing prototype functions for rules.
- Arrow or actually a group of arrows pointing to a single field represent a function.
- Function is a prototype of one processing rule, e.g. field validation, value matching or conversion.
- Function code is a program code for performing a function needed in the predefined logic.
- function code is a binary code directly executable by an operating system. Code uses function parameters for decisions that need to be made during function execution.
- Instruction is a single unit of Processing Logic Byte Code.
- an instruction contains a pointer to the function code, pointer to the function parameters and the number of parameters. Instructions are created during compilation process.
- Byte Code Executor is the component that takes care of instruction fetching, decoding and execution. Thus, the Byte Code Executor takes the next instruction from array and calls the function of the instruction using the parameters of the instruction.
- Shared library files contain function code for both core and custom functions.
- the code is produced by C compiler and is fast to execute. Functions are loaded into memory from the files when the Processing Logic Executor node is started.
- Figure 1 shows one example of using an embodiment of the invention.
- the system of Figure 1 comprises a graphical user interface 1 (GUI) for defining the predefined processing logic according to which the user desires the system to process data records, such as event records of a communications network.
- GUI 1 produces a Predefined processing logic file 2 containing the Predefined processing logic, and takes care of saving the data into a persistent storage, e.g. database 3.
- Predefined processing logic file 2 contains an XML representation of the logic built with the GUI 1.
- the system comprises a Compiler 4 that uses the Predefined processing logic file 2 as a source code and builds a Processing Logic byte code 5 on the basis of the Predefined processing logic.
- the compilation is performed every time the logic is tested or saved into the persistent storage 3.
- the persistent storage 3 holds all Processing Logic configurations and the compiled byte codes for them.
- Processing Logic byte code 5 is a plain text file that describes how the predefined processing logic should be executed. It has a sequential set of instructions and their parameters. All instructions are saved using the original function names.
- the system also comprises a Processing Logic Executor 6, which may be a node application that can be executed using Node Base.
- Processing Logic Executor 6 itself comprises a function library 7, byte code parser 8 and a Byte Code Executor 9.
- Function library 7 holds all functions of the Processing Logic. In the figure, the function library 7 is divided into core functions 10 and custom functions 11.
- Byte code parser 8 parses the plain text byte code 5 and produces a more efficient form of the code.
- the complete byte code does not have any function names but direct pointers to them.
- Byte Code Executor 9 executes the parsed byte code. Hence, the Byte Code Executor 9 acts as the logic execution means for executing the predefined processing logic. The code is executed "blindly" without knowing what the functions do.
- a graphical user interface can be used to set up the system to process data records according to a desired processing logic. After defining the processing logic, Compiler analyses the processing logic and compiles it into a format
- Compilation means reading the processing logic XML file, creating a data structure of it and producing byte code file using the data structure.
- Compiler removes all "useless" information that is not needed in execution from the processing logic and flattens the structure of the logic.
- Compiler also reserves a field array to which all the fields are placed. After this fields are no longer referenced by their names but the index of the array. Byte code parser changes the index to direct memory location.
- Required instructions are added into the byte code when compiler either encounters a function in processing logic definition or needs to add a function for e.g. jumping from one place to another in the code.
- the compiler adds an instruction, it also adds the parameters of the function as a list of indexes of the fields. Byte code parser builds the parameter array using this information. After the compilation is ready, the compiler calculates the values for byte code header fields.
- a user can also define and add custom functions via the graphical user interface. When adding a custom function, the system adds a new plug-in screen for defining the function parameters in the graphical user interface. The system also adds a corresponding function code in the function code array of the Processing Logic Executor 6.
- the compiler includes a custom function extension for modifying the logic definition structure to include the custom function and parameters of the custom function in the field arrays of the system.
- FIG 2 shows one example of the functioning of the Processing Logic Executor 6.
- each arrow 10, 11 (or a group of arrows pointing to the same field) represent a Processing Logic function.
- the Processing Logic Executor executes, in specified order, the Byte Code the Compiler has generated.
- Each arrow in the figure represents a Processing Logic function that executes the action depending on function parameters (fields).
- fields 22, 32 in input 20 and output 30 records are the fields read by the node base 130.
- the node base 130 reads the fields 22 from an input file 20 and creates a data structure 40 for the record. Each field can be fetched or written using the field name.
- the Processing Logic Executor 6 does not have to read all fields from the input record.
- internal fields 42 in the Processing Logic Executor 6 are temporary fields that the Processing Logic Executor has produced. Internal fields 42 may hold the original data read from the node base 130 or data generated by the functions 10, 11. Internal fields 42 can also be constants inside the Processing Logic Executor 6.
- Processing Logic Executor 6 allocates memory for all temporary fields 42 in initialisation phase to make the execution more efficient. Fields are grown automatically during the execution if needed. The fields read from node base do not need any space (node base takes care of that) and they cannot be modified inside Processing Logic Executor.
- the fields can be mapped directly from the input record 20 into the output record 30 without modifying the field or using it for any other fields.
- each arrow 10, 11 (or a group of arrows pointing to same field) represent a function in Processing Logic Executor 6.
- Function may be e.g. string concatenation, which takes two input fields and produces an output field.
- Processing Logic byte code 5 consists of pointers to these functions 10, 11 and their parameters.
- Figure 3 shows two examples of Processing Logic function executions in an embodiment of the invention.
- Figure 3 a is an example of basic function that takes four input fields 22, 42 and produces two output fields 32, 42.
- Figure 3b an example has a function that takes three input fields 22, 42 and doesn't produce any output fields but modifies the program counter 17 according to the field values.
- instructions 62 in both examples in the figure 3 are pointers to function codes 12.
- Function code 12 exists in memory only once even if there are many instructions 62 using it.
- Byte Code Executor 9 always executes the instruction 62 to which its program counter 17 points.
- Byte Code Executor 9 increases the program counter 17 by one after each function call.
- Processing Logic Executor 6 gets its entire configuration in node application parameters and in byte code file 5.
- Node application parameters include all predefined processing logic specific parameters and the settings of Processing Logic Executor. Break points in the byte code and other debugging parameters are set with using node parameters if needed any. These parameters are used e.g. in debug mode.
- Figure 4 shows one example of a Byte Code Executor 9 according to an embodiment of the invention.
- the Byte Code Executor 9 fetches one instruction 62 at a time.
- a single instruction 62 contains three parts: function pointer 70, number of parameters 80 and pointer-to-parameters 90 of the instruction 62.
- FIG 4 describes how a single instruction 62 is handled in the Byte Code Executor 9.
- Each instruction 62 consists of following parts:
- Function pointer 70 - Function pointer points to the actual function code 12 that is used in the execution of this instruction 62.
- Number of parameters 80 - Function can use different number of parameters 52 depending on the use of the function.
- value match function may get 3 -N parameters depending on the number of values for matches.
- Pointer to parameters 90 Pointer to parameters points to the parameter array 50, which contains all parameters 52 needed in entire predefined processing logic. All parameters 52 of this instruction 62 are in the array 50 one after another.
- the pointer 90 refers to the first parameter 54 and the number of parameters 80 tells how many of them should be used. Parameter list can contain both input and output parameters.
- function gets both number of parameters and the pointer to parameter list as function arguments.
- Byte Code Executor 6 handles the execution of the byte code 5. The execution is performed blindly, not caring about the functions that are executed.
- the byte code 5 is divided in three different parts: initialisation, processing and shutdown parts. Byte code execution is a straightforward task:
- Processing Logic Executor of the above-described embodiment is a very flexible component. User can program new custom functions into the system without modifying the existing implementation. This makes it possible to create even very complicated logic using Processing Logic and make customer specific modifications to the system if needed without affecting the performance.
- Processing Logic Executor of the above-described embodiment also provides high performance. Interpretation overhead is minimal in this implementation meaning that running logic with Processing Logic Executor is almost like running a native code program specifically programmed for the customer's logic.
- Processing Logic Executor of the above-described embodiment is also very modular and thus easy to test. Each function is an independent software component that can be tested with an automated tool. This will save costs in porting of the product and makes it easier to implement new functionality to the system.
- Processing Logic byte code 5 is stored in plain text format to avoid problems with porting from one platform to another.
- Byte code contains following components:
- Header - Header contains detailed information about the predefined processing logic.
- byte code parser 8 takes care of reading the byte code file 5, parsing it to internal structures and pre-formatting fields. Internal structures include following components:
- Data field arrays 40 - Fields are stored into two arrays: one containing all integers and another containing all strings. Fields are read and initialised. Initialisation contains memory allocation and setting value, if needed.
- Instruction array 60 Instructions are stored into one long array. They are stored there as described in Processing Logic Byte Code Executor design.
- Processing Logic functions 10, 11 are tested with an automated test tool.
- the main idea is that the function developer creates some test data into a text file in defined format and executes the test cases.
- the automated test tool uses Processing Logic function library 7 for loading the functions 10, 11 defined in test case file. No coding is needed for tests.
- An embodiment of the invention belongs to processing data records in mediation systems with communications networks. Sophisticated mediation solutions have several beneficial features, which of the most important are told below.
- each node 120 includes a node base 130 and a node application 140.
- Node base 130 provides the basic standard functionality for the node 120. It handles the internal usage data transmission mechanism between the nodes 120 and encodes the internal usage data.
- Node base 130 provides an interface to the node application 140 for accessing the usage data and collecting customised audit information.
- a node base 130 may include several components, for example a node input 131, a node output 132, a node API 133, a node configuration 134 and a node audit 135.
- Node Input 131 is responsible for reading the data, input records 20, from the internal input data sources, parsing it and passing the data to Node Application interface.
- Node Input uses Data Transmission Interface that defines the internal data format and data transmission mechanism.
- Node Output 132 is responsible for reading the data, output records 30, from the Node Application Interface and encoding and writing it to Data Transmission Interface.
- Node Output uses Data Transmission Interface that defines the internal data format and data transmission mechanism.
- Node API 133 provides the Node Application the access to the usage data. It 'hides' to internal data transmission interface from the Node Application 140.
- Node API includes functionality for providing the usage data to and receiving it from the Node Application 140. It is also used for retrieving customised audit information from the Node Application 140 and for providing configuration parameters to it.
- Node Configuration 134 is responsible for reading the configuration data from the Configuration Interface and for initialising the Node according to given configuration parameters.
- Node Configuration also passes Node Application specific parameters to the Node API.
- Node Configuration uses Configuration Interface that defines the configuration data format and transmission mechanism.
- Node Audit 135 is responsible for writing various audit data to the Audit Interface.
- Node Audit defines content for audit interface.
- Node Audit uses Audit Interface that defines the default audit data format and transmission mechanism.
- Node Audit uses also Management Interface that defines monitored data format and transmission mechanism. This is used for example for indicating the status of the Node.
- Data Transmission Interface and/or buffering 145 define the usage data format and data transmission mechanism between the Nodes.
- Mediation consists of different processes like collection, validation, enrichment, aggregation, correlation, rating, conversion and delivery.
- the varied functionality allows OSS/BSS systems to receive usage data just as they want it.
- the keywords of the mediation solution architecture are simplicity and straightforwardness.
- the modular design of the solution according to an embodiment of the invention enables real-time and distributable processes, reliable operation and high performance.
- Nodes 120 are functional components specialised in different mediation processes, such as collection, aggregation, validation, correlation and formatting, or a combination of these. Nodes are linked together to form processing streams for event record handling.
- Each Node 120 has standard functionality that provides automated data transmission mechanism between the Nodes and processing information logging mechanism between the Node and the Node Manager (not shown in figure).
- the actual usage data processing logic is implemented by different applications 140 that reside in the Nodes. These applications 140 are isolated from internal data transmission mechanism and internal data formats enabling easier application development. Applications 140 are drawn as ovals in the figure 5 presented. The system provides a standard interface through which the applications communicate with the processing framework.
- Nodes 120 can be further categorised according to their functionality. The functionality depends on the Node Application 140 and the Node's position in the Processing Chain 200. The first Node 120 in a Processing Chain can be called a Collector Node and the last Node a Distribution Node. In these cases the data parsing and formatting functionality needs to be performed by the application 140 itself and the standard functionality provided by the Node Base 130 is not used. The flow of usage data and the standard components that become obsolete are shown in the Figure 5. In this picture it is assumed that the data source 210 and destination 220 both operate with some real-time protocol, i.e. they are using a socket connection for sending and receiving data.
- the applications take care of formatting and writing the data in the output files. In case like this, it might be necessary to separate the output file generation and the delivery of the output files to separate Nodes 120.
- Processing Logic Executor 6 represents an example of a node application 140 used in mediation systems.
Abstract
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2005259108A AU2005259108B2 (en) | 2004-07-06 | 2005-06-16 | Data processing in a mediation or service provisioning system |
BRPI0513004-2A BRPI0513004B1 (en) | 2004-07-06 | 2005-06-16 | "SYSTEM AND METHOD FOR PROCESSING DATA RECORDS, MEDIATION SYSTEM FOR HANDLING EVENT RECORDS, SERVICE SUPPLY SYSTEM, AND SYSTEM AND METHOD FOR PROCESSING EVENT RECORDS" |
US11/571,700 US8042106B2 (en) | 2004-07-06 | 2005-06-16 | Data processing in a mediation or service provisioning system |
CA2572668A CA2572668C (en) | 2004-07-06 | 2005-06-16 | Data processing in a mediation or service provisioning system |
NO20070481A NO338023B1 (en) | 2004-07-06 | 2007-01-25 | Data processing in a mediation or service supply system. |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US58552704P | 2004-07-06 | 2004-07-06 | |
EP04396044.2 | 2004-07-06 | ||
EP20040396044 EP1615127B1 (en) | 2004-07-06 | 2004-07-06 | Data processing in a mediation or service provisioning system |
US60/585,527 | 2004-07-06 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2006003239A1 true WO2006003239A1 (en) | 2006-01-12 |
Family
ID=34971665
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/FI2005/000287 WO2006003239A1 (en) | 2004-07-06 | 2005-06-16 | Data processing in a mediation or service provisioning system |
Country Status (5)
Country | Link |
---|---|
AU (1) | AU2005259108B2 (en) |
BR (1) | BRPI0513004B1 (en) |
CA (1) | CA2572668C (en) |
NO (1) | NO338023B1 (en) |
WO (1) | WO2006003239A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101394451B (en) * | 2008-11-06 | 2012-09-05 | 北京中创信测科技股份有限公司 | Storage method for call detailed recorded data, indication method and system |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6591416B1 (en) * | 1997-06-30 | 2003-07-08 | Sun Microsystems, Inc. | Interpreting functions utilizing a hybrid of virtual and native machine instructions |
-
2005
- 2005-06-16 AU AU2005259108A patent/AU2005259108B2/en not_active Ceased
- 2005-06-16 WO PCT/FI2005/000287 patent/WO2006003239A1/en active Application Filing
- 2005-06-16 CA CA2572668A patent/CA2572668C/en not_active Expired - Fee Related
- 2005-06-16 BR BRPI0513004-2A patent/BRPI0513004B1/en not_active IP Right Cessation
-
2007
- 2007-01-25 NO NO20070481A patent/NO338023B1/en not_active IP Right Cessation
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6591416B1 (en) * | 1997-06-30 | 2003-07-08 | Sun Microsystems, Inc. | Interpreting functions utilizing a hybrid of virtual and native machine instructions |
Non-Patent Citations (4)
Title |
---|
BEDICHEK R C: "Talisman: fast and accurate multicomputer simulation", 1995 ACM SIGMETRICS JOINT INTERNATIONAL CONFERENCE ON MEASUREMENT AND MODELING OF COMPUTER SYSTEMS. OTTAWA, MAY 15 - 19, 1995, ACM SIGMETRICS JOINT INTERNATIONAL CONFERENCE ON MEASUREMENT AND MODELING OF COMPUTER SYSTEMS, NEW YORK, ACM, US, vol. 23 1, 1 May 1995 (1995-05-01), pages 14 - 24, XP000537012, ISBN: 0-89791-695-6 * |
BELL J R: "Threaded code", COMMUNICATIONS OF THE ASSOCIATION FOR COMPUTING MACHINERY, ASSOCIATION FOR COMPUTING MACHINERY. NEW YORK, US, vol. 16, no. 6, 1973, pages 370 - 372, XP000996587, ISSN: 0001-0782 * |
CHANDRA S, MOONA R: "Retargetable functional simulator using high level processor models", VLSI DESIGN, 2000. THIRTEENTH INTERNATIONAL CONFERENCE ON VLSI DESIGN, CALCUTTA, INDIA 3-7 JAN. 2000, LOS ALAMITOS, CA, USA,IEEE COMPUT. SOC, US, 7 January 2000 (2000-01-07), pages 424 - 429, XP010365894, ISBN: 0-7695-0487-6 * |
CLICK C, PALECZNY M: "A simple graph-based intermediate representation", ACM SIGPLAN NOTICES, ASSOCIATION FOR COMPUTING MACHINERY, NEW YORK, US, vol. 30, no. 3, 1 March 1995 (1995-03-01), pages 35 - 49, XP000501653, ISSN: 0362-1340 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101394451B (en) * | 2008-11-06 | 2012-09-05 | 北京中创信测科技股份有限公司 | Storage method for call detailed recorded data, indication method and system |
Also Published As
Publication number | Publication date |
---|---|
CA2572668A1 (en) | 2006-01-12 |
CA2572668C (en) | 2014-10-14 |
BRPI0513004B1 (en) | 2017-12-05 |
AU2005259108A1 (en) | 2006-01-12 |
NO338023B1 (en) | 2016-07-18 |
AU2005259108B2 (en) | 2011-08-04 |
BRPI0513004A (en) | 2008-04-22 |
NO20070481L (en) | 2007-01-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8042106B2 (en) | Data processing in a mediation or service provisioning system | |
US8769485B2 (en) | Data parallelism and parallel operations in stream processing | |
US7124145B2 (en) | System and method for dynamic business logic rule integration | |
US7356806B2 (en) | Method and system for processing records of events during use of a communications system | |
US7810082B2 (en) | System and method for transforming generic software code into operator specific code | |
US20080134158A1 (en) | Stream processor with compiled programs | |
KR101310506B1 (en) | Virtual machine and programming language for event processing | |
US20040268301A1 (en) | Adding new compiler methods to an integrated development environment | |
WO2007115031A2 (en) | Method and system for processing xml-type telecommunications documents | |
US20080127128A1 (en) | Type Validation for Applications Incorporating A Weakly-Typed Language | |
AU2005259108B2 (en) | Data processing in a mediation or service provisioning system | |
CN111259042B (en) | Dynamic query method and system | |
Nottegar et al. | Performance evaluation of mobile processes via abstract machines | |
Südholt | A model of components with non-regular protocols | |
US20030217190A1 (en) | Service description and development processes | |
Antoniol et al. | Library miniaturization using static and dynamic information | |
EP1196846A1 (en) | Meta-language for c++ business applications | |
CN116032809B (en) | Network protocol analysis method and system using Wasm | |
CN116594681B (en) | Scaffold design method and system based on specific scene modularization | |
CA2566025C (en) | Type validation for applications incorporating a weakly-typed language | |
Hasselmeyer | A methodology for formalizing GDMO behavior descriptions | |
Glitho et al. | Handling subscription in a mobile agent based service environment for Internet Telephony: Swapping agents | |
Falcarin | A CPL to Java compiler for dynamic service personalization in JAIN-SIP server | |
GB2388214A (en) | Updating a monitoring agent using a structured document | |
Conti | The development and analysis of a Bourne shell compiler |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2005259108 Country of ref document: AU |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2572668 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: 11571700 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: DE |
|
ENP | Entry into the national phase |
Ref document number: 2005259108 Country of ref document: AU Date of ref document: 20050616 Kind code of ref document: A |
|
WWP | Wipo information: published in national office |
Ref document number: 2005259108 Country of ref document: AU |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
122 | Ep: pct application non-entry in european phase | ||
ENP | Entry into the national phase |
Ref document number: PI0513004 Country of ref document: BR |