CN112307734A

CN112307734A - XSLT template loading method and device and electronic equipment

Info

Publication number: CN112307734A
Application number: CN202011190335.6A
Authority: CN
Inventors: 杨毅; 宁娜; 杨成科; 柯锦
Original assignee: China Travelsky Holding Co
Current assignee: China Travelsky Holding Co
Priority date: 2020-10-30
Filing date: 2020-10-30
Publication date: 2021-02-02
Anticipated expiration: 2040-10-30
Also published as: CN112307734B

Abstract

The invention discloses a loading method, a device and a system of an XSLT template, wherein the loading method is applied to a system for NDC message conversion, and the system comprises an NDC message loader factory, an NDC message converter factory, an NDC version adapter, versions of navigation adapter and a message converter. Firstly, acquiring configuration information of a target template pool of each interface of a navigation department and a navigation department template loading path, and acquiring a message converter example corresponding to a target parameter of an NDC message loader from an NDC message converter factory based on the configuration information and the navigation department template loading path; initializing the message converter example based on an interface message translation mode and the size of a message translation pool; constructing an NDC message loader example based on the conversion mode configuration of each interface; and generating a target NDC version adapter based on the message converter example and the NDC message loader example. Therefore, the XSLT template loading method provided by the invention can improve the conversion efficiency of the XSLT template and has high flexibility.

Description

XSLT template loading method and device and electronic equipment

Technical Field

The invention relates to the technical field of information processing, in particular to a method and a device for loading an XSLT template and electronic equipment.

Background

NDC (New Distribution Capability) is a New Distribution industry standard that has been pursued by the International Air Transport Association (IATA) in recent years. The method mainly establishes a unified data transmission standard (message based on an XML format), and data interaction can be carried out between an airline company and its partners through the unified standard. The airline department can dynamically construct flight freight ticket products and auxiliary products in real time according to the request of the seller and the information of the seller and the passengers, and then the flight freight ticket products and the auxiliary products are provided for the seller through a unified standard, so that the situation that the products are mainly constructed by a Global Distribution System (GDS for short) in the traditional airline ticket field is changed, and the direct sale of the airline department is promoted.

However, there are multiple versions of NDC, there are large differences between versions, and the NDC version of each docking station may be different, so that the Aggregator (agglomerator) needs to process each NDC version of the navigation station, and perform XML transformation on the XSLT template of the multiple versions of the navigation station, so as to realize the transformation between the NDC version and the navigation NDC version. The existing XSLT template has low conversion efficiency and poor flexibility, and cannot meet the requirement of XML conversion in the current complex scene.

Disclosure of Invention

Aiming at the problems, the invention provides an XSLT template loading method, an XSLT template loading device and electronic equipment, which improve the conversion efficiency of the XSLT template and have high flexibility.

In order to achieve the purpose, the invention provides the following technical scheme:

a loading method of an XSLT template is applied to a system for NDC message conversion, the system comprises an NDC message loader factory, an NDC message converter factory, an NDC version adapter, versions of navigation adapters and a message converter, and the loading method comprises the following steps:

acquiring configuration information of a target template pool of each interface of a navigation department and a loading path of a navigation department template, wherein the configuration information of the target template at least comprises a maximum translation number, a minimum idle number, a maximum idle number and a maximum waiting time;

acquiring a message converter example corresponding to a target parameter of an NDC message loader from an NDC message converter factory based on the configuration information and the navigation department template loading path;

initializing the message converter example based on an interface message translation mode and the size of a message translation pool;

constructing an NDC message loader example based on the conversion mode configuration of each interface;

and generating a target NDC version adapter based on the message converter example and the NDC message loader example.

A loading device of XSLT template is applied to a system for NDC message conversion, the system comprises an NDC message loader factory, an NDC message converter factory, an NDC version adapter, versions of navigation adapter and a message converter, the loading device comprises:

the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring configuration information of a target template pool of each interface of a navigation department and a loading path of a template of the navigation department, and the configuration information of the target template at least comprises a maximum translation number, a minimum idle number, a maximum idle number and a maximum waiting time;

a second obtaining module, configured to obtain, from an NDC message converter factory, a message converter instance corresponding to a target parameter of an NDC message loader based on the configuration information and the navigation driver template loading path;

the initialization module is used for initializing the message converter embodiment based on the interface message translation mode and the message translation pool size;

the building module is used for building an NDC message loader example based on the conversion mode configuration of each interface;

and the generating module is used for generating a target NDC version adapter based on the message converter example and the NDC message loader example.

A storage medium having stored thereon executable instructions which, when executed by a processor, implement a loading method as in any one of the above.

An electronic device, comprising:

a memory for storing a program;

a processor configured to execute the program, the program specifically configured to:

Compared with the prior art, the invention provides a loading method, a device and a system of an XSLT template, wherein the loading method is applied to a system for NDC message conversion, and the system comprises an NDC message loader factory, an NDC message converter factory, an NDC version adapter, versions of navigation adapters and a message converter. Firstly, acquiring configuration information of a target template pool of each interface of a navigation department and a navigation department template loading path, and acquiring a message converter example corresponding to a target parameter of an NDC message loader from an NDC message converter factory based on the configuration information and the navigation department template loading path; initializing the message converter example based on an interface message translation mode and the size of a message translation pool; constructing an NDC message loader example based on the conversion mode configuration of each interface; and generating a target NDC version adapter based on the message converter example and the NDC message loader example, so that the conversion efficiency of the extensive XSLT template oriented to the NDC aggregator and applicable to a wide scene is improved.

Drawings

The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers identify the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale.

FIG. 1 is a schematic structural diagram of a loading system of an XSLT template according to an embodiment of the invention;

FIG. 2 is a flowchart illustrating a method for loading an XSLT template according to an embodiment of the invention;

fig. 3 is a schematic diagram of an airline department adapter according to an embodiment of the present invention;

fig. 4 is a schematic diagram of initializing a message conversion pool according to an embodiment of the present invention;

FIG. 5 is a schematic illustration of an NDC adapter loading provided by an embodiment of the present invention;

fig. 6 is a schematic diagram of an NDC version adapter according to an embodiment of the present invention;

fig. 7 is a schematic structural diagram of a loading apparatus of an XSLT template according to an embodiment of the present invention.

Detailed Description

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.

The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.

It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units. The modifications referred to in this disclosure as "a", "an", and "the" are illustrative and not restrictive, and it will be understood by those skilled in the art that "one or more" may be used unless the context clearly dictates otherwise.

As described in the background art, with the establishment of new distribution capability of an airline company, airline company channel diversification is a trend, and more airlines release their NDC sales interfaces, but because the NDC interfaces are updated iteratively and quickly, different airlines select different versions of NDC interfaces, a plug-in platform is required to use an XSLT template to quickly implement XML transformation, load multiple-airline company version XSLT templates, and implement transformation between an NDC version and an airline company NDC version.

However, the inventors have found that under such circumstances, the loading and installation of the NDC aggregator XSLT template faces the following problems:

1. with the iterative upgrade of the NDC version, the platform needs to iterate continuously and provide NDC interfaces of different versions. Thus, the NDC aggregator needs to quickly implement XML transformation through XSLT templates and needs to handle different versions of NDC template loading.

2. As airline NDC versions iterate, the NDC aggregator needs to be continuously updated to access different versions of each airline. Thus, the NDC aggregator needs to handle different version NDC requests versus different version NDC template loading for the airline.

3. With iteration of the NDC versions of the airlines, the NDC aggregators are continuously integrated and unified, and for conversion of the NDC versions and the NDC versions of the airlines which are accessed to the airlines, different converters are used on the airlines or interface layers.

In response to these problems, according to conventional architectural design, the system requires the creation of a converter factory, then a converter from the converter factory, and finally the conversion is performed using a converter (SAXON, XALAN). The NDC aggregator is a conversion mode which needs multiple NDC versions and multiple navigation driver NDC versions, and supports customization among the NDC versions, the navigation driver NDC versions, interfaces and conversion implementation modes. Such conventional architecture designs cannot be flexibly and efficiently applied to NDC aggregators. Based on the method, the device and the electronic equipment for loading the XSLT template, the transformation efficiency of the XSLT template which is wide in application scene and faces to the NDC aggregator can be improved.

For convenience of explaining the message conversion method provided by the present invention, the related terms to which the present invention is applied will be explained.

IATA (International Air Transport Association), a large International organization composed of airlines of countries of the world, the predecessor of which is the International Air business Association established in 1919 in the time of two war and disassembled in the time of two war, headquarters is montreal in canada, and an execution agency is in japanese tile. Compared with the international civil aviation organization for supervising aviation safety and navigation rules, the international civil aviation organization is more like an international coordination organization consisting of carriers (airlines), manages problems such as ticket prices, dangerous goods transportation and the like in civil aviation transportation, and has the main functions of coordinating and communicating policies between governments through an aviation transportation enterprise and solving the problem of actual operation.

NDC (New Distribution Capability), a New Distribution industry standard that the international air transport association IATA has pursued in recent years. The new distribution capability mainly establishes a unified data transmission standard based on messages in an XML format, and data interaction can be carried out between an airline company and its partners through the unified standard. The airline department can dynamically construct a flight fare ticket product and an auxiliary operation product (a product quote which is constructed and returned to a partner by the airline department, namely Offer commonly spoken in NDC) in real time according to the request of the seller and the information of the seller and the passengers, and then the product quote is provided for the seller through a unified XML format standard message. The design changes the mode that the GDS mainly constructs Offer for distribution in the traditional air ticket field, and leads the airline company to return to the dominant position of transaction, thereby promoting the direct sale of the airline company.

GDS (Global Distribution System) is a large computer information service System applied to civil air transportation and the entire tourism industry. Through the GDS, travel sales organizations throughout the world can timely acquire a large amount of travel-related information from airlines, hotels, car rental companies, and travel companies, thereby providing customers with quick, convenient, and reliable services.

The OOMS (Offer and Order Management System) is a navigation sales System constructed based on the NDC standard. The system performs data interaction with a partner through a message of an NDC standard in an interface mode. The OOMS are carriers for the airline operators to implement NDC.

Offer, flight space, brand freight rate, additional services, usage rules, etc. returned by the flight department in a system built based on NDC (e.g., OOMS). There may be multiple OfferItems per Offer, one OfferItem for each passenger type, and one OfferItem for each additional service.

Order, which is various transaction data stored in a system built based on NDC (e.g., OOMS), or Order information based on NDC.

The NDC message mainly establishes a unified data transmission standard based on the message in the XML format, and data interaction can be performed between an airline company and a partner of the airline company through the unified standard. These unified messages are NDC messages. The NDC messages are all presented by XML format documents, and definition files of the XML format documents are corresponding XSD files. Both XSD and XML documents comply with their own specifications, such as: there are some "nodes", "attributes", etc., which are all the technical definitions of the standard.

The method includes that an NDC interface and an OOMS are carriers for realizing the NDC for an airline department, and due to the diversity of business links and flow scenes in a process of sales of the airline department, the OOMS must provide various different interfaces to meet the interaction requirement in the whole business process, for example, common NDC interfaces include: AirShopping (Offer query, providing a function for a user to query for a desired product), orderCreate (Order generation, providing a function for a user to place an Order to a navigation department OOMS), orderRetrieve (Order acquisition, providing a function for a user to request a navigation department to view a booked Order situation), and the like. Different interfaces use respective NDC messages.

The NDC version is a newer and continuously-developed project, and the international aviation protocol is continuously optimizing and perfecting the NDC. The NDC message is embodied on a specific delivery object, that is, two versions of update iteration are issued every year (for all NDC interfaces), and the version number is formed by adopting a "year". version number "writing method, for example: version number bit 17.2 of the second version released in 2017; the first version released in 2018 was 18.1, etc.

The Aggregator, a new role under the definition of NDC in the field of civil aviation distribution. Because the NDC versions of the OOMS of each navigation department are different, the service understanding is different, and the application modes are different, the NDC interfaces provided by the OOMS of the navigation department are different, and the cost and the difficulty of a downstream channel user for connecting the NDC interfaces of the OOMS of the navigation department are high. Therefore, an Aggregator role is born in the NDC, the NDC interfaces of all navigation departments are connected in an abutting mode, the NDC contents of different navigation departments are collected, analyzed, converted and fused to generate aggregated contents, then a unified interface is provided for downstream channel users according to the NDC standard, and the downstream channel users can quickly realize the abutting and selling of multiple navigation departments only by abutting the unified interface. May also be referred to as "Agg," "aggregator," "NDC aggregator," "content aggregator," etc.

The aggregator is a vendor or technology provider that provides the aggregator. Also known as "content aggregators", and the like.

The Airline Profile is a component in the Aggregator defined by NDC, which functions to store configuration details during the interaction of the Aggregator with the navigation server, for example: and saving the airline information supported by the airline operator (but not limited to the above). That is, if a record "the canadian Airline does not support the beijing-helsinki flight" is stored in the Airline Profile, "when the downstream channel user wishes to query the flight of" beijing-helsinki "through the Aggregator, the Aggregator will first read the configuration in the Airline Profile and find that the canadian Airline does not support the information, the Aggregator will not request the interface of the canadian Airline, so that the system pressure of the interface of the canadian Airline and the Aggregator itself can be simultaneously relieved.

XSL, refers to the EXtensible Stylesheet Language (EXtensible Styleshet Language).

XSLT, refers to XSL transformation.

XSLT transformation processors, including SAXON and XALAN, where Xalan is a specification for transforming extensible markup language (XML) into hypertext markup language (HTML) or other types of XML documents. Xalan-Java 1.2 was built for extensible stylesheet language transformation (XSLT) and XML Path Language (XPL) based on the Internet alliance (W3C). While Xalan typically uses Xerces XML lexical parser, it may also use other parsers to convert to Document Object Model (DOM)2 or Simple API for XML (SAX) 1. Through a large number of tests, when the small messages are converted by using the xalan template, the speed is high, and the system overhead is low.

Saxon is an XSLT processor, which is a program that uses XML documents and stylesheets as inputs, and then generates a result document as an output. It can be used with other parsers that implement the Java SAX interface. Saxon also includes a serializer for converting result trees into XML, HTML, or plain text. The good performance is certainly one reason for selecting Saxon, and the Saxon has obvious speed advantage in analyzing large messages through a large number of tests. When the AirShopping message is analyzed, a Saxon template is used.

Referring to fig. 1, in the embodiment of the present invention, a system for performing NDC message conversion through an XSLT template is first established, where the system includes an NDC message loader factory, an NDC message converter factory, an NDC version adapter, each version of navigation adapter, and a message converter. The system is used for preloading the template, so that the NDC polymerization product can be used for rapidly and flexibly configuring different interface message conversion modes of multiple versions of multiple navigation systems.

Wherein, the NDC message loader factory: and the system is responsible for providing four types of NDC message loading POOLs, namely XALAN, SAXON, XALAN _ POOL and SAXON _ POOL. And the method supports the initialization of the template pool for the maximum idle quantity and the minimum idle quantity loaded by different interfaces, navigation departments and templates. Acquiring template configuration of a navigation department for initialization, and merging template pools of all initialized interfaces of the navigation department for subsequent use, wherein the template configuration at least comprises an NDC version number, a navigation department interface, an NDC message converter unique identifier and an NDC message loading type. Schematically, the following table lists specific implementations configured according to the process steps herein.

The template configuration of the navigation department interface is as the above table, and after the successful loading by the NDC message loader and the NDC message converter, two template pools as shown in the following table are obtained:

NDC message converter factory: and the system is responsible for providing four types of NDC message conversion POOLs, namely XALAN, SAXON, XALAN _ POOL and SAXON _ POOL. And then acquiring the NDC message loader, and acquiring a template pool according to the NDC version number, the navigation department version number and the navigation department interface.

NDC version adapter: the NDC version of the adapter supports the loading types (XALAN and SAXON) that configure the templates separately by the driver and by the interface. And the conversion between different interface messages under the same NDC version is also supported.

Each version of navigation department adapter: the target navigation version and the output NDC version obtain the message converter from the message converter factory.

The message converter: and analyzing according to the strategy according to the message request content to obtain a message conversion mode and execute conversion. The conversion modes supported by the message converter are as follows: current thread conversion, large task fragmentation conversion and parallel stream conversion.

Specifically, based on the structure of the system for performing NDC message conversion through an XSLT template shown in fig. 1, as shown in fig. 2, fig. 2 shows a flowchart of a loading method of an XSLT template provided in an embodiment of the present invention, where the loading method may include the following steps:

s101, constructing a navigation driver adapter: and acquiring configuration information of a target template pool of each interface of the navigation department and a loading path of the navigation department template.

Specifically, with reference to fig. 3, first, the message conversion configuration of each interface of different versions and different navigation systems is initialized, including a message translation loading mode and a message conversion mode. Each airline department has one adapter per NDC version.

Then, the SAXON or XALAN conversion mode configuration of each interface of each version of each navigation department is read, and an NDC message loader example is constructed. And after the specific implementation of the binding of all the components is finished, scanning the converter configuration of each interface below each navigation department component to obtain a corresponding interface converter set. And acquiring a navigation department template loading path from a configuration file below the navigation department component, wherein the template pool configuration information of each interface of the navigation department can comprise a maximum translation number, a minimum idle number, a maximum waiting time and the like.

S102, initializing a message conversion pool: and acquiring a message converter example corresponding to the target parameter of the NDC message loader from the NDC message converter factory based on the configuration information and the navigation department template loading path.

Specifically, in conjunction with fig. 4, the message conversion pool of each navigation department for different interfaces is initialized. Loading a template pool according to the read configuration and template paths, acquiring all converted XSLT template paths of all interfaces of all navigation departments according to a template suffix determined by a platform for initialization, acquiring an NDC message converter example correspondingly realized from an NDC message converter factory according to the configuration of each NDC version of each interface of each navigation department in a construction stage, and loading a plurality of template examples in the template pool for subsequent conversion under the condition of judging whether the template loading mode of each interface of each navigation department is pooling or non-pooling, and then putting the template examples into the pool for waiting after use; whereas non-pooling is only loaded into one incoming pool. If the NDC message is in the pooling loading mode, the configuration information obtained in the step is loaded into a template configuration adapter pool, and the template is translated by the NDC message converter example obtained above; and then obtaining the corresponding realized NDC message loader example loading template pooling from the NDC message loader factory, and putting the NDC message loader example loading template pooling into a template pool.

S103, initializing a message conversion example: initializing the message converter instance based on the interface message translation mode and the message translation pool size.

And initializing the converter according to the interface message translation mode and the message translation pool size in the starting process of the driver adapter.

S104, constructing an NDC adapter: and constructing an NDC message loader example based on the conversion mode configuration of each interface.

In particular, in connection with fig. 5, the NDC aggregator supports various NDC version adapters. And reading SAXON or XALAN conversion mode configuration of each interface, and constructing an NDC message loader example. Acquiring an NDC version template loading path from a configuration file of an NDC adapter, wherein the template pool configuration information of each interface is as follows: maximum translation number, minimum idle number, maximum wait duration, etc. Loading a template pool according to the read configuration and template paths, acquiring all converted XSLT template paths of an NDC version interface according to a template suffix determined by a platform for initialization, then loading the obtained configuration information into a template configuration adapter pool, and translating a template by using the obtained NDC message converter example; and then obtaining the corresponding realized NDC message loader example loading template pooling from the NDC message loader factory, and putting the NDC message loader example loading template pooling into a template pool.

S105, assembling an NDC version adapter: and generating a target NDC version adapter based on the message converter example and the NDC message loader example.

Specifically, with reference to fig. 6, the navigation adapter and the NDC version adapter obtained through the above steps are assembled. The adaptation of the multi-navigation multi-version adapter and the multi-version NDC aggregator can be realized.

Schematically, in order to better understand the technical solution of the present application, the embodiment of the present invention will be described by taking the NDC182 as an example to aggregate two different NDC versions.

1. And constructing the navigation department adapter. In the AA navigation driver NDC172 version, the air mapping interface is implemented by using SAXON (the navigation driver has a large data volume of query messages, and the logic for implementing the aggregation service is complex, so that the VTD fast conversion is implemented by using SAXON), and the offsprine interface is implemented by using XALAN (the price verification interface has a small data volume of messages, the aggregation service is simple, and time consumption such as performance is not considered); the AY navigation driver NDC181 version, all interfaces are realized using SAXON; two adapters were constructed, AA172 and AY181 respectively. Reading the version number of the navigation department and the SAXON or XALAN conversion mode configuration of the interface, constructing an NDC message loader example, after the components are bound, scanning the converter configuration of each interface of the AA navigation department and the AY navigation department, such as V172To182OfferPriceRSTranslator, and acquiring a corresponding interface converter set. Acquiring a navigation department template loading path/opt/app/agg/tpls/aa 172/, template pool configuration information of each interface of the navigation department from a configuration file below the navigation department component: the maximum translation number of the AirShoppinging interface is 50, the minimum idle number is 20, the maximum idle number is 40, the maximum waiting time is 10000 and the like, the default maximum translation number of other interfaces is 25, the minimum idle number is 10, the maximum idle number is 20, the maximum waiting time is 10000 and the like.

2. And initializing a message conversion pool. Loading a template pool according to the read configuration and template paths, acquiring all converted XSLT template paths of all interfaces of all navigation departments according to a template suffix _ NDC _ tpl.xsl determined by a platform, initializing, acquiring an NDC message converter example correspondingly realized from an NDC message converter factory according to the configuration of each NDC version of each interface of each navigation department in a construction stage, loading the AA navigation department and the AY navigation department templates into a template configuration adapter pool, and translating the templates by using the NDC message converter example acquired above; and then obtaining the corresponding realized NDC message loader example loading template pooling from the NDC message loader factory, and putting the NDC message loader example loading template pooling into a template pool.

3. Initializing a message conversion instance. And initializing the converter according to the interface message translation mode and the message translation pool size in the starting process of the driver adapter.

4. And constructing the NDC adapter. The NDC aggregator is used as version 182. Reading each interface and using XALAN conversion mode configuration to construct NDC message loader example. Acquiring an NDC version template loading path from a configuration file of an NDC adapter, wherein the template pool configuration information of each interface is as follows: and if OrderReshoppTOAirShoping realizes the label change query of the AY navigation department, the maximum translation number is 20, the minimum idle number is 10, the maximum idle number is 20, the maximum waiting time is 10000 and the like, the maximum translation number is 10, the minimum idle number is 5, the maximum waiting time is 10000 and the like are defaulted by other interfaces. Loading a template pool according to the read configuration and template paths, acquiring all converted XSLT template paths of an NDC version interface according to a template suffix _ NDC _ tpl.xsl determined by a platform for initialization, loading the obtained configuration information into a template configuration adapter pool, and translating a template by using the obtained NDC message converter example; and then obtaining the corresponding realized NDC message loader example loading template pooling from the NDC message loader factory, and putting the NDC message loader example loading template pooling into a template pool.

5. Assembling the NDC version adapter. Assembling the AA172 adapter, the AY181 adapter and the NDC182 adapter obtained in the above steps. The NDC aggregator is used for aggregating all the interfaces of different versions of AA172 and AY 181.

In summary, the loading method provided by the embodiment of the invention improves the conversion efficiency of the extensive XSLT template oriented to the NDC aggregator and applicable to a wide range of scenes.

Referring to fig. 7, in an embodiment of the present invention, there is further provided an XSLT template loading apparatus, including:

a first obtaining module 71, configured to obtain configuration information of a target template pool of each interface of a navigation department and a loading path of a template of the navigation department, where the configuration information of the target template at least includes a maximum translation number, a minimum idle number, a maximum idle number, and a maximum waiting time;

a second obtaining module 72, configured to obtain, from an NDC message converter factory, a message converter instance corresponding to a target parameter of an NDC message loader based on the configuration information and the navigation driver template loading path;

an initialization module 73, configured to initialize the message converter instance based on an interface message translation mode and a message translation pool size;

a building module 74, configured to build an NDC message loader instance based on a conversion mode configuration of each interface;

a generating module 75, configured to generate a target NDC version adapter based on the packet converter instance and the NDC packet loader instance.

On the basis of the above embodiment, the apparatus further includes:

the third acquisition module is used for acquiring the converter configuration of each interface of the navigation department, and the converter configuration at least comprises an NDC version number, a navigation department interface, an NDC message converter unique identifier and an NDC message loading type;

a first determining module for determining at least one template pool based on the converter configuration;

the fourth acquisition module is used for acquiring target parameters of the NDC message loader, wherein the target parameters at least comprise one or more of an NDC version number, a navigation driver version number and a navigation driver interface;

a second determining module, configured to determine a target template pool from the at least one template pool based on the target parameter.

On the basis of the above embodiment, the building module further includes:

the device comprises a first acquisition unit, a second acquisition unit and a third acquisition unit, wherein the first acquisition unit is used for acquiring an NDC version template loading path from a configuration file of an NDC adapter;

the loading unit is used for loading the template pool according to the configuration file and the template loading path;

the initialization unit is used for acquiring all converted XSLT template paths of the NDC version interface according to the template suffix determined by the platform and initializing;

the configuration unit is used for loading the acquired configuration information into the template configuration adapter pool;

a translation unit, configured to translate the NDC version template by using the NDC packet converter instance;

a second obtaining unit, configured to obtain a corresponding NDC messenger instance from an NDC messenger factory.

On the basis of the above embodiment, the generating module includes:

an assembling unit for assembling the message converter instance and the NDC message loader instance.

It is to be noted that the flowcharts and block diagrams in the figures referred to in the embodiments illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information. Although the operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.

The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of an element does not in some cases constitute a limitation on the element itself.

The embodiment of the present invention further provides a storage medium, where the storage medium stores executable instructions, and the instructions, when executed by a processor, implement the message conversion method according to any one of the above.

An embodiment of the present invention further provides an electronic device, including:

a memory for storing a program;

Further, the method further comprises: determining the target template pool, comprising:

acquiring converter configuration of each interface of a navigation department, wherein the converter configuration at least comprises an NDC version number, a navigation department interface, an NDC message converter unique identifier and an NDC message loading type;

determining at least one template pool based on the converter configuration;

acquiring target parameters of an NDC message loader, wherein the target parameters at least comprise one or more of an NDC version number, a navigation driver version number and a navigation driver interface;

and determining a target template pool from the at least one template pool based on the target parameters.

Further, the method further comprises: the method for constructing the NDC message loader example based on the conversion mode configuration of each interface comprises the following steps:

acquiring an NDC version template loading path from a configuration file of an NDC adapter;

loading a template pool according to the configuration file and the template loading path;

acquiring all converted XSLT template paths of the NDC version interface according to the template suffix determined by the platform, and initializing;

loading the acquired configuration information into a template configuration adapter pool;

translating the NDC version template by the NDC message converter example;

a corresponding NDC message loader instance is obtained from the NDC message loader factory.

Further, the method further comprises: generating a target NDC version adapter based on the message converter instance and the NDC message loader instance, comprising:

assembling the message translator instance and the NDC message loader instance.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

According to one or more embodiments of the disclosure, a method, a system, a storage medium and an electronic device for loading an XSLT template are provided.

An electronic device, comprising:

a memory for storing a program;

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

While several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.

Claims

1. A loading method of an XSLT template is applied to a system for NDC message conversion, the system comprises an NDC message loader factory, an NDC message converter factory, an NDC version adapter, versions of navigation driver adapters and a message converter, and the loading method comprises the following steps:

2. The method of claim 1, wherein determining the pool of target templates comprises:

determining at least one template pool based on the converter configuration;

3. The method of claim 1, wherein constructing an NDC message loader instance based on the translation mode configuration of each interface comprises:

compiling the NDC version template by the NDC message converter example;

4. The method of claim 1, wherein generating a target NDC version adapter based on the packet converter instance and the NDC packet loader instance comprises:

assembling the message translator instance and the NDC message loader instance.

5. A loading device of an XSLT template is applied to a system for NDC message conversion, the system comprises an NDC message loader factory, an NDC message converter factory, an NDC version adapter, versions of navigation adapters and a message converter, and the loading device comprises:

6. The apparatus of claim 5, further comprising:

7. The apparatus of claim 5, wherein the building module comprises:

a translation unit, configured to compile the NDC version template with the NDC packet converter instance;

8. The apparatus of claim 5, wherein the generating module comprises:

9. A storage medium having stored thereon executable instructions which, when executed by a processor, implement the loading method of any one of claims 1 to 4.

10. An electronic device, comprising:

a memory for storing a program;