KR100845234B1 - Apparatus and method for parsing domain profile in software communication architecture - Google Patents

Abstract

1. TECHNICAL FIELD OF THE INVENTION

The present invention relates to an apparatus and method for parsing domain profiles in a communication software architecture.

2. The technical problem to be solved by the invention

The present invention stores all information contained in the DOM (Document Object Model) tree when parsing a system domain profile describing a hardware device and software component information as a series of files in a mobile terminal based on a communication software structure. An advanced XML parsing interface that includes paths, selections, qualifiers, and reference functions for direct access to information in domain profiles with self-describe characteristics, eliminating the creation of additional storage structures, and DOM generated from them. Apparatus and method for domain profile parsing in communication software architecture to provide parsing time efficiency without providing frequent redundant parsing and hard coding process and additional storage structure by providing management functions such as tree maintenance, removal, and sharing The purpose is to provide

3. Summary of Solution to Invention

The present invention relates to a domain profile parsing apparatus in a communication software structure, which transmits a domain profile name from a framework to parsing means, and generates a query for extracting corresponding data in response to a data request from the framework. Interface processing means for directly extracting the corresponding data from the document object model (hereinafter referred to as DOM) tree and providing it to the framework; And the parsing means for generating a DOM tree of the domain profile in response to receiving a domain profile name from the interface processing means.

4. Important uses of the invention

The present invention is used in a mobile terminal.

Open Platform, Software Communication Architecture, Domain Profile Parser, Query

Description

Apparatus and method for parsing domain profile in software communication architecture

1 is an illustration of a typical communications software architecture (SCA),

2 is a diagram illustrating an embodiment of a general domain profile;

3 is an example diagram of a domain profile parsing platform in an open communication software architecture in accordance with the present invention;

4 is an exemplary diagram illustrating a class structure of an open profile interface according to the present invention;

5 is an exemplary view of a query statement according to the present invention,

6 is an exemplary diagram illustrating a DOM tree interface structure according to the present invention;

7 is a configuration diagram of an embodiment of a domain profile parsing apparatus in a communication software structure according to the present invention;

8 is a flowchart of an embodiment of a method for parsing a domain profile in a communication software architecture according to the present invention.

* Explanation of symbols for the main parts of the drawings

71: open profile interface processing unit 72: XML parser

711: Parser Interface Handler

712: DOM interface handler

713: Sparring Interface Handler

The present invention relates to an apparatus and method for parsing a domain profile in a communication software structure, and more particularly, to a document object model (DOM) which is a result of parsing a SCA-based domain profile. Maintain and manage the tree, and directly extract and provide the corresponding information from the DOM tree that is not dependent on a specific XML (eXtensible Markup Language) parser to avoid wasting memory due to redundant parsing and hard coding of profiles. A domain profile parsing apparatus in a communication software architecture and a method thereof are provided.

The Communication Software Architecture (SCA) was developed to provide interoperability between communication systems in the Joint Tactical Radio System (JTRS) and Joint Program Executive Office (JPEO), providing portability of software and hardware. Ensure the composition ability.

SCA also provides an integrated environment of heterogeneous hardware and software based on the Common Object Request Broker Architecture (CORBA) middleware, the industry standard for distributed object models.

In addition, SCA's core framework consists of interface processors and core services that provide software application designers with access to and operation of the software and hardware layers.

In addition, the domain profile of the SCA is divided into a hardware (device) profile and a software profile, and the interface, logical location, interdependencies and unique parameters between the software or hardware components are described using XML. In this case, the core framework allocates / maintains / manages target resources, devices, and applications based on the domain profile.

In other words, the domain profile is written in XML, an informal and self-describing recording method, and the core framework obtains information by individually accessing the domain profile, which is an XML document.

Hereinafter, the communication software structure (SCA) will be described in more detail with reference to FIG. 1.

As shown in FIG. 1, the communication software architecture uses a real-time embedded operating system 11 that supports multithreading, uses CORBA 12 as a message delivery technology for distributed processing environments, and uses a framework 15. It provides interfaces and core services to embedded software and hardware layers.

Here, the domain profile 14 refers to a file that records the interface, logical location, interdependencies, and unique parameter characteristics between the software and hardware device components in XML. These multiple domain profiles 14 are parsed by the domain profile parser 13 and divided into individual information provided to the framework 15.

In addition, the application 16 performs user communication functions including digital signal processing, protocol processing, external input / output connections, and the like. In this case, the application 16 uses interfaces and services provided by the framework 15.

Hereinafter, the type of the domain profile will be described with reference to FIG. 2.

As shown in FIG. 2, the domain profile described in the file of hardware devices and software components constituting the SCA system domain includes a software package description (SPD) 21 and a software component (SCD) containing information on individual components. Descriptor (22), Software Assembly Descriptor (SAD) (23), Properties Descriptor (PD) (24), Device Package Descriptor (DPD) (25), Device Configuration Descriptor (DCD) (26), Profile Descriptor (PD) And (27).

Here, the software package description (SPD) 21 includes information for identifying an object of implementation of the unit software component.

In addition, the Software Component Descriptor (SCD) 22 includes information on the interface provided and used by the component.

In addition, the SAD (Software Assembly Descriptor) 23 includes information on the components constituting the application.

In addition, the property descriptor (PD) 24 includes unique characteristic information to be applied to the package.

In addition, the device package descriptor (DPD) 25 includes information used to identify a device to be installed.

In addition, the device configuration descriptor (DDC) 26 includes devices and device configuration information.

In addition, the PD (Profile Descriptor) 27 includes the domain profiles used.

In this communication software structure, the domain profile parser 13 generates a DOM tree by parsing a domain profile, extracts all information included in the DOM tree, and regenerates (reparses) the data depending on the framework. After storing, the data is retrieved and provided to the framework 15 according to a request from the framework 15. At the time of reparsing, the DOM tree is hard-coded directly to an unstructured low level and regenerated into framework-dependent data.

Therefore, the conventional domain profile parser 13 extracts all information included in the DOM tree (XML parser-dependent hard coding) and stores it as data dependent on the framework. Inefficiencies in parsing time, and increased memory size of the parser due to hard coding, dependencies on specific XML parsers, and lack of adaptability to specialized parsing applications (APIs) for mobile terminals.

Therefore, there is a demand for a method of directly extracting and providing request information from a framework from a DOM tree.

The present invention has been proposed to solve the above problems, and in parsing a system domain profile describing a hardware device and software component information as a series of files in a mobile terminal based on a communication software structure, a Document Object Model (DOM) Advanced, including path, selection, qualification, and reference functions for direct access to information in domain profiles with self-describe characteristics, eliminating the creation of additional storage structures that store all the information contained in the tree. Communication software architecture to provide parsing time efficiency without frequent redundant parsing and hard coding process and additional storage structure by providing management functions such as maintenance, removal, and sharing of XML parsing interface and DOM tree created through it. To provide a domain profile parsing apparatus and method thereof in The purpose is.

Other objects and advantages of the present invention can be understood by the following description, and will be more clearly understood by the embodiments of the present invention. Also, it will be readily appreciated that the objects and advantages of the present invention may be realized by the means and combinations thereof indicated in the claims.

An apparatus of the present invention for achieving the above object is a domain profile parsing apparatus in a communication software structure, which transmits a domain profile name from a framework to parsing means, and in accordance with a request for data from the framework, Interface processing means for generating a query for extraction and directly extracting corresponding data from a document object model (hereinafter referred to as DOM) tree to provide the framework; And the parsing means for generating a DOM tree of the corresponding domain profile as the domain profile name is received from the interface processing means.

On the other hand, the method of the present invention includes a method of parsing a domain profile in a communication software structure, the open profile interface passing a domain profile name from the framework to a parser; Generating a document object model (hereinafter referred to as DOM) tree for the domain profile received by the parser; A query generation step of generating, by the open profile interface, a query for extracting corresponding data in response to a data request from the framework; And directly extracting the corresponding data from the DOM tree using the query statement generated by the open profile interface and providing the data to the framework.

The above objects, features and advantages will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, whereby those skilled in the art may easily implement the technical idea of the present invention. There will be. In addition, in describing the present invention, when it is determined that the detailed description of the known technology related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

3 is an illustration of a domain profile parsing platform in an open communication software architecture in accordance with the present invention.

As shown in FIG. 3, the framework 15 requests parsing results via the open profile interface 32 instead of a direct call to the standard XML parser 31 (301). At this time, since the open profile interface 32 is defined as 'CORBA IDL', its implementation 33 is a CORBA servant.

In addition, the open profile interface 32 is an XML parsing operator, a standardized XML parser 31 or a specific XML parser 34, which is an improved XML parsing operator to record XML parsing results in a framework view rather than a general XML data extraction view. DOM interface 323, which provides operators that can flexibly utilize the DOM tree parsed by H.sub.), And a parser interface 322 to selectively add complex data structures from a framework perspective.

This allows the framework vendor for SCA to achieve the profile parsing request 301 through the implementation case 33 for the open profile interface 32.

Here, the implementation 33 of the open profile interface is more flexible, by selecting an interface with the standard XML parser 31 or with an implementation 34 optimized by a particular XML parser vendor (or memory limited terminal parser). Optimization is possible. These interfaces ultimately request parsing 302 of the domain profile 14 written in XML form, resulting in a DOM tree 35 (303).

The data request 301 of the framework is also mapped to a data extraction interface to the DOM tree 35 via an implementation interface. Through this, the framework 15 may obtain flexible parsing efficiency while providing independence to the XML parsing process.

Hereinafter, the open profile interface 32 will be described in more detail with reference to FIGS. 4 and 5.

As shown in FIG. 4, the open profile interface 32 consists of a scraping interface 321, a DOM interface 323, and a parser interface 322. The individual parsers 41 for the domain profile 14 are created by the parser factory 42, and the actual parser implementation 43 for them is achieved by inheriting and redefining the parser 41.

Here, an example in which the scraping interface 321 uses the advanced data extraction operator required by the framework 15 in order to exclude unnecessary memory allocation / release processes and redundant parsing in the framework will be described with reference to FIG. 5.

As shown in Fig. 5, the scraping interface 321 is configured in the form of a path record, a selection condition, a limit condition, and a reference structure.

For example, the scraping interface command for the physical location extraction request of the profile for the three resources may be defined as "dom.componentfile []. Localfile.name" 51.

In this command, dom (511) refers to the top node of the DOM tree 35, and if there is a path from the 'componentfile' node 512 to the 'localfile' node 513 below it in the hierarchy, the 'localfile' element Extract the 'name' attribute of 514. The value is returned in the form of the first set by the finite operator '[]' 515.

In other words, the framework 15 is a result of the physical location extraction request of the profile for the three resources, the string data set of String []: {'/ xml / Controller.spd.xml', '/ xml / 3ge_resource. spd.xml ',' /xml/wlan_resource.spd.xml '}. At this time, up to two restriction operators may be used, and the extraction may be performed by specifying an order number as shown in [1, 2, 5].

As another example, a request to obtain the value of the 'refid' attribute of an 'Assemblycontroller' is defined as "dom.assemblycontroller.refid" (52) to obtain a single string data String: 'Controller' as the value of the 'refid' attribute. Can be. In this case, since the 'assemblycontroller' element is uniquely defined in the SAD file, such an abbreviated expression is possible.

As another example, a request to extract the CORBA naming context of a resource that provides a port for a CORBA connection identified by 'Controller2wlan_resource' would be: 'dom.connectinterface (id =' Controller2wlan_resource '). Providesport.namingservice.name' (53 ), You get String: 'domain_a / wlan_resource'.

The request 53 may specify a conditional expression using id 532, which is an attribute node of the 'connectioninterface' node 531, to specify a selection condition among two 'connectioninterface' elements 534. Separated by the selection operator '()' 533.

Also, to get the connection name of the target resource, use String: 'wlan_resource', the value of the 'providesidentifier' element 535, via 'dom.connectinterface (id =' Controller2wlan_resource '). Providesidentifier.value' instead of the 'name' attribute. Reference may be made.

6 is an exemplary view illustrating a DOM tree interface structure according to the present invention.

As shown in FIG. 6, the DOM tree interface structure according to the present invention includes a DOM tree list 61, a pointer 62, and a reference count 63.

Here, the DOM tree list 61 is configured in an index structure for quick access, and each item includes a pointer 62 that points to the actual DOM tree and a reference count 63 that refers to the actual DOM tree.

At this time, the reference count 63 is initialized to 1 at the time of registration in the DOM tree list 61 and has a reference count for the target tree. This is used to determine the actual removal point when removing the DOM tree. Based on this, the DOM interface 323 parses the DOM tree generation operator through parsing, the operator for specifying the release / maintenance of the DOM tree in the unit component in the framework 15, and whether the DOM tree exists for the required domain profile. Includes a validation operator, a split operator that moves only the recursive parts of the DOM tree to a new virtual DOM tree, and a remove operator of the part trees that are no longer needed in the DOM tree.

7 is a block diagram of an embodiment of a domain profile parsing apparatus in a communication software architecture according to the present invention.

As shown in FIG. 7, the domain profile parsing apparatus in the communication software structure according to the present invention delivers the domain profile name received together with the XML parser 72 according to the DOM tree generation request from the framework 15. An open profile interface processor 71 for generating a query statement corresponding to the information request in the DOM tree for the domain profile, directly extracting the corresponding information from the DOM tree, and providing the information to the framework 15; And an XML parser 72 for generating a DOM tree of the corresponding domain profile as the domain profile name is received from the open profile interface processor 71.

Here, the open profile interface processor 71 calls the DOM interface processor 712 using the domain profile name received from the framework 15, and requests the information in the DOM tree for the domain profile from the DOM interface processor. A parser interface processor 711 for transferring the information extracted by the scraping interface processor 713 to the framework 15, and a domain profile name received from the parser interface processor 711. And a DOM interface processor 712 for generating a query statement corresponding to the information request in the DOM tree for the domain profile and passing it to the scraping interface processor 713, and the DOM interface. Using the query received from the processor 712, the corresponding information in the DOM tree The scraping interface processor 713 for extracting the beam directly.

At this point, the parser interface handler 711 forwards the DOM tree removal request from the framework to the DOM interface handler 712.

In addition, the parser interface processor 711 may convert and extract the information extracted by the scraping interface processor 713 into a data format corresponding to the framework 15.

In addition, the parser interface processor 711 may additionally determine whether the DOM tree is a copy, a double reference, or the like, and may transmit a management command for the DOM tree to the DOM interface processor 712.

In addition, the parser interface processor 711 may notify the framework 15 as the DOM interface processor 712 completes the generation of the DOM tree.

In addition, the DOM interface handler 712 removes all or part of the DOM tree in response to a DOM tree removal request from the parser interface handler 711.

In addition, the DOM interface processor 712 generates a respective query statement for extracting all of the request information from the framework 15 in the DOM tree, and delivers it to the scraping interface processor 713. Then, the parser interface processor 711 collects the corresponding information extracted by the scraping interface processor 713 and delivers the information to the framework 15.

8 is a flowchart of an embodiment of a method for parsing a domain profile in a communication software architecture according to the present invention.

First, the user initializes the domain profile parsing device to perform a response to the request from the framework 15.

Subsequently, the domain profile name received together with the DOM tree generation request from the framework 15 is transferred to the XML parser 72 (801). Then, the XML parser 72 generates a DOM tree for the received domain profile (802).

Thereafter, a corresponding query is generated according to the information request in the DOM tree for the domain profile (803). Examples of queries for this are as shown in Fig. 5, "51", "52", and "53".

Thereafter, the information is directly extracted from the DOM tree and then provided to the framework 15 (804).

Herein, the process of "804" will be described in more detail. The scraping interface processor 713 extracts a node name from the query path of the query received from the DOM interface processor 712.

Then, after extracting the same element as the node name from the DOM tree, the value or attribute value of the element is extracted. At this time, if a conditional expression (selection operator, qualification operator, reference operator) using an operator exists in the query statement, the result according to the conditional expression is extracted.

As described above, the method of the present invention may be implemented as a program and stored in a recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto-optical disk, etc.) in a computer-readable form. Since this process can be easily implemented by those skilled in the art will not be described in more detail.

The present invention described above is capable of various substitutions, modifications, and changes without departing from the technical spirit of the present invention for those skilled in the art to which the present invention pertains. It is not limited by the drawings.

The present invention as described above, in parsing the system domain profile that describes the hardware device and software component information as a series of files in the mobile terminal based on the communication software structure, all contained in the DOM (Document Object Model) tree An advanced XML parsing interface that includes paths, selections, constraints, and referencing features for direct access to information in domain profiles with self-describe characteristics, eliminating the creation of additional storage structures for storing information, and By providing management functions such as maintaining, removing, and sharing the created DOM tree, it is possible to provide efficiency of parsing time without frequent redundant parsing and hard coding process and additional storage structure.

In addition, in parsing a domain profile for SCA, the present invention provides a system that can use an advanced interface including qualified, conditional, and reference operations that are adapted for parsing domain profiles without using a low-level DOM API. By providing an effect, the size of the code added to parsing can be minimized.

In addition, the present invention maintains and manages the parsing result of the profile in the SCA structure, and a flexible domain profile management scheme for preventing repetitive parsing of the profile and improving memory efficiency and processing performance through a partial DOM tree reconstruction interface. There is an effect that can provide.

In addition, the present invention is to minimize the frequent interworking of the framework and the parser, there is an effect that can provide a system for generating an ordered or structured data structure from the domain profile perspective.

Claims (11)

A domain profile parsing device in a communication software architecture, comprising: Pass the domain profile name from the framework to the parsing means, generate a query to extract the data according to the data request from the framework, and then extract the data directly from the document object model (hereafter DOM) tree. Interface processing means for providing to the framework; And The parsing means for generating a DOM tree of the domain profile in response to receiving a domain profile name from the interface processing means; Domain profile parsing device comprising a. The method of claim 1, The interface processing means, A parser interface processor for passing a domain profile name from the framework to a DOM interface processor, a data request from the framework to the DOM interface processor, and delivering data extracted from a scraping interface processor to the framework; The DOM interface processor for transferring the domain profile name from the parser interface processor to the parsing means, generating a query for extracting the data according to the data request received from the parser interface processor, and delivering the query to the scraping interface processor. ; And The scraping interface processor for directly extracting the corresponding data from the DOM tree using a query received from the DOM interface processor Domain profile parsing device comprising a. The method of claim 2, The DOM interface handler is And when there are a plurality of request data from the framework in the DOM tree, generating a respective query statement for extracting all of them and transferring the generated query statements to the scraping interface processor. The method of claim 2, The DOM interface handler is And splitting / removing the corresponding DOM tree according to a request for splitting / removing a DOM tree from the framework received through the parser interface processor. The method of claim 2, The scraping interface processor, And extracting a node name from a query path of a query received from the DOM interface processor, and extracting an element identical to the node name from a DOM tree to return a value or attribute value of the corresponding element. The method of claim 2, The scraping interface processor, And extracting a result according to the conditional expression if a conditional expression (selection operator, qualification operator, reference operator) using an operator exists in the query statement. In the domain profile parsing method in a communication software structure, The open profile interface passing the domain profile name from the framework to the parser; Generating a document object model (hereinafter referred to as DOM) tree for the domain profile received by the parser; A query generation step of generating, by the open profile interface, a query for extracting corresponding data in response to a data request from the framework; And Directly extracting corresponding data from the DOM tree using a query generated by the open profile interface and providing the framework to the framework Domain profile parsing method comprising a. The method of claim 7, wherein The query generation step, If there are a plurality of request data from the framework in the DOM tree, domain profile parsing method, characterized in that for generating each query to extract all of them. The method of claim 7, wherein Extracting the data directly from the DOM tree, And extracting a node name from the query path of the query statement and extracting an element identical to the node name from a DOM tree to return a value or attribute value of the corresponding element. The method of claim 7, wherein Extracting the data directly from the DOM tree, And if a conditional expression (selection operator, qualifier operator, reference operator) using an operator exists in the query statement, extracting a result matching the conditional expression. The method of claim 7, wherein Removing the DOM tree according to the DOM tree removal request from the framework Domain profile parsing method further comprising.

Images