KR101487192B1 - Server apparatus and method for providing service related to autosar - Google Patents

Abstract

Disclosed is a method for providing service relates to AUTOSAR of a server device. The present invention comprises the steps of supplying a first web page for file format conversion to a terminal device connected to the server device; receiving data in a first file format from the connected terminal device; converting the received data in the first file format into data in a second file format; and supplying a second web page for supplying the converted data in the second file format to the connected terminal device, wherein the first or second file format is ARXML, which is an AUTOSAR standard format.

Description

TECHNICAL FIELD [0001] The present invention relates to a server device and a method of providing a service related to the same,

The present invention relates to a server apparatus and a method of providing an autosource-related service, and more particularly, to a server apparatus that converts a file format into an ARXML standard file format or an ARXML standard file format And a method of providing an autosource related service.

Recently, the development of a variety of vehicle supplementary services focusing on stability and convenience has made vehicles that were merely a means of transportation in the past now recognized as the concept of a single space area of the individual driver.

Accordingly, automobile services that meet consumer needs and preferences are being developed everyday, from various automation services through automobile body control to various multimedia services based on GPS, mobile communication network, and Bluetooth.

These services are usually provided by electronic control units (ECUs) rather than mechanical devices, which has made it necessary to integrate software and IT technologies into the automotive industry.

However, the safety of the product, the problem of module reusability, and the elimination of hardware dependency are common tasks of all software products, and automobile electronic equipment services equipped with software-based services also can not avoid this problem.

In order to solve these problems, global automobile suppliers and parts companies such as BMW, Bosch, and Volkswagen are centering on the standardization of AUTOSAR (Automotive Open System Architecture).

AUTOSAR aims to standardize the SW architecture and development methodology that are embedded in the ECU. It is largely divided into the automotive SW architecture and application interface, the methodology for developing electronic equipment software using them, And compliance testing. AUTOSAR 4.1.1 has been released recently.

Accordingly, various development tools such as Vector, EB, KPIT, etc. have been proposed for developing vehicle software by the proposed model and methodology.

These development tools are written in ARXML, an Autosar standard format based on XML (eXtensible Markup Language).

However, since the created ARXML describes a lot of code in a complicated structure, it is difficult to confirm the result of creation through the ARXML created by the designer, and to modify the created ARXML.

This difficulty can also be greater for general users who lack ARXML knowledge.

SUMMARY OF THE INVENTION The present invention has been conceived to solve the above-described problems, and an object of the present invention is to provide a server for providing a service for converting a file format into an ARXML standard file format, or an ARXML standard file format, And to provide a method of providing services related to the autosource.

According to another aspect of the present invention, there is provided a method for providing an autosar related service in a server device, the method comprising: providing a first web page for file format conversion to a terminal device connected to the server device; Receiving data of a first file format from the connected terminal device, converting data of the received first file format into data of a second file format, and transmitting data of the second file format And providing the second web page to the connected terminal device, wherein the first or second file format may be ARXML, which is an auto standard format.

According to another aspect of the present invention, there is provided a server apparatus for providing an Autosar-related service, including: a web page generating unit for generating a web page; When a first file format is received from the connected terminal device via the first web page, a first web page for format conversion is provided to a terminal device connected to the server device, A file format conversion unit for converting data in a file format into data in a second file format and a web page generation unit for generating a second web page for providing data in the converted second file format, And a control unit for controlling the communication unit to provide the first web page and the second web page to the connected terminal apparatus, It can be formatted in ARXML.

According to various embodiments of the present invention, AUTOSAR-related services can be provided in real time even when the AUTOSAR-related tools are not installed in a terminal device such as a PC by providing AUTOSAR-related services on the web. That is, anyone with a terminal device such as a PC can receive AUTOSAR related services in real time regardless of location.

Further, according to various embodiments of the present invention, it is possible to easily confirm the creation result of the ARXML created by both the designer and the general user, by converting the data of the automobile standard format having a complicated structure into data of a format that can be easily understood by the user.

In addition, according to various embodiments of the present invention, parameters and the like can be easily corrected by checking data of a format that can be easily understood by a user, and the result can be converted into data in the standard format of Auto Corporation.

As a result, it is possible to easily perform difficult design work, which can drastically shorten the work hours of the designer in charge of the AUTO company and easily educate the general user about the AUTO company information.

1 is a block diagram illustrating a server apparatus according to an embodiment of the present invention.
2 is a diagram illustrating conversion of an ARXML format to an image format according to an embodiment of the present invention.
3 is a diagram illustrating conversion of an ARXML format to an Excel format according to an embodiment of the present invention.
FIG. 4 illustrates conversion of an Excel format to an ARXML format according to an embodiment of the present invention.
5 to 6 are views showing an example of converting an ARXML format into an Excel format according to an embodiment of the present invention.
7 is a diagram illustrating conversion of a legacy code into an ARXML format or an Excel format according to an embodiment of the present invention.
8 is a diagram illustrating a web page according to an embodiment of the present invention.
9 is a flowchart illustrating a method of providing an autosource-related service according to an embodiment of the present invention.
10 to 13 are flowcharts specifically illustrating an auto company related service providing method according to an embodiment of the present invention.

The following merely illustrates the principles of the invention. Thus, those skilled in the art will be able to devise various apparatuses which, although not explicitly described or shown herein, embody the principles of the invention and are included in the concept and scope of the invention. Furthermore, all of the conditional terms and embodiments listed herein are, in principle, intended only for the purpose of enabling understanding of the concepts of the present invention, and are not intended to be limiting in any way to the specifically listed embodiments and conditions .

It is also to be understood that the detailed description, as well as the principles, aspects and embodiments of the invention, as well as specific embodiments thereof, are intended to cover structural and functional equivalents thereof. It is also to be understood that such equivalents include all elements contemplated to perform the same function irrespective of the currently known equivalents as well as the equivalents to be developed in the future, i.e., the structure.

Thus, for example, it should be understood that the block diagrams herein represent conceptual views of exemplary circuits embodying the principles of the invention. Similarly, all flowcharts, state transition diagrams, pseudo code, and the like are representative of various processes that may be substantially represented on a computer-readable medium and executed by a computer or processor, whether or not the computer or processor is explicitly shown .

The functions of the various elements shown in the figures, including the functional blocks depicted in the processor or similar concept, may be provided by use of dedicated hardware as well as hardware capable of executing software in connection with appropriate software. When provided by a processor, the functions may be provided by a single dedicated processor, a single shared processor, or a plurality of individual processors, some of which may be shared.

Also, the explicit use of terms such as processor, control, or similar concepts should not be interpreted exclusively as hardware capable of running software, and may be used without limitation as a digital signal processor (DSP) (ROM), random access memory (RAM), and non-volatile memory. Other hardware may also be included.

In the claims hereof, the elements represented as means for performing the functions described in the detailed description include all types of software including, for example, a combination of circuit elements performing the function or firmware / microcode etc. , And is coupled with appropriate circuitry to execute the software to perform the function. It is to be understood that the invention defined by the appended claims is not to be construed as encompassing any means capable of providing such functionality, as the functions provided by the various listed means are combined and combined with the manner in which the claims require .

BRIEF DESCRIPTION OF THE DRAWINGS The above and other objects, features and advantages of the present invention will become more apparent from the following detailed description of the present invention when taken in conjunction with the accompanying drawings, in which: There will be. In the following description, well-known functions or constructions are not described in detail since they would obscure the invention in unnecessary detail.

The software architecture of AUTOSAR according to an embodiment of the present invention is composed of three layers of application software, RTE (Run Time Environment) and BSW (Basic Software).

The basic concept of the present invention is to introduce RTE to develop application software independent of hardware by separating application software and hardware related software BSW. This helps to reduce development costs by increasing application reusability and maintainability.

The application software is located at the top of the RTE and consists of software components (SWCs) that are placed in specific ECUs (Electronic Control Units), which include software that performs various functions.

Software components communicate with other software components, services, atomic software components such as ECU Abstraction, Complex Device Driver through RTE, and exchange information between other software components via RTE using the interface. Each software component implements a part of the application software function and is a basic unit that is mapped to the ECU, and exchange data with each other through a port and an interface. Sensor / Actuator A software component is a kind of software component and is a software component for the implementation of ECU sensors and actuators.

Communication of these software components can be defined by port and interface. Each software component can have multiple ports for communication, and the communication pattern is determined through the interface. Ports are called PPort (Provide Port) when providing data or service and RPort (Require port) when requesting.

The communication interface is divided into Server-client and Sender-receiver depending on the pattern.

In case of server-client interface, client starts communication by sending configuration parameter when server is needed, and server waits for communication request from client in RTE form. That is, the client provides the server side operation and the client calls the operation function of the server.

The sender-receiver interface is divided into a sender and a receiver in such a way that the sender sends various data to the receiver.

BSW (Basic Software) is a standardized software layer that is located under the RTE and provides the services that a software component needs to run an application. The standard layer of the BSW is composed of a service layer, an ECU abstraction layer (EAL), a microcontroller abstraction layer (MCAL), and a complex device driver (CDD). The service layer performs service functions such as operating system (OS), network, memory, verification, and ECU status management. The EAL provides an interface to the ECU's internal units and provides an upper layer design independent of the ECU. MCAL avoids direct manipulation of registers from higher layers to microcontrols and consists of digital input / output, analog to digital conversion, waveform conversion, and serial to parallel conversion.

The RTE serves as a communication center for exchanging data between ECUs or exchanging data between ECUs. Regardless of whether communication occurs within an ECU or between ECUs using protocols such as CAN, LIN, FlexRay, and MOST, the RTE provides the same interface and services to communicate abstracted communications . The RTE plays a central role in the exchange of information between software components and between software components and the BSW, and plays a key role in separating software and hardware.

Here, CAN, LIN, FlexRay, and the like are typical serial communications that are mainly used for control between in-vehicle ECUs.

On the other hand, automobiles targeted by AUTOSAR are made up of complex mechanical structures and electrical and electronic devices. Among them, the electric / electronic device is constituted by a complex system of electric field systems including sensors, actuators, controllers, and the like in various networks.

The vehicle electric field system configured in this manner is largely composed of a body, a chassis, a power train, a safety, and a multimedia. The body electric field system is a system mainly for providing the convenience of the driver, and carries out various commands of the driver and carries information of the vehicle. Typically, it controls windows, an outside mirror, a seat, a dashboard, a burglar alarm, a headlight, an interior light, a wiper, and the like. The ECUs constituting these body electric system are connected to the vehicle network CAN, LIN, FlexRay, and the like.

Accordingly, various development tools such as Vector, EB, KPIT, etc. have been proposed for developing vehicle software by the proposed model and methodology.

Meanwhile, according to the vehicle software development methodology proposed by AUTOSAR, it can be divided into a system design step, an ECU setting step, and a BSW (Basic SoftWare) generator step.

The system design phase carries out system design for several ECUs. The system design stage includes the network design and the software component design. In the software component design, the file name, the function name, the variable name, and the RTE-API to be used are designed. Here, the system design phase is written in ARXML, an Autosar standard format based on XML (eXtensible Markup Language) using various development tools. Hereinafter, ARXML created at the system design stage will be referred to as 'system ARXML'.

The ECU setup step sets the AUTOSAR BSW (Basic SoftWare) selection and function for one ECU. Here, the ECU setting step is written in ARXML, which is an Autosar standard format based on XML (eXtensible Markup Language) using various development tools. Hereinafter, the ARXML created in the ECU setting step will be referred to as an 'ECU parameter ARXML'.

The BSW Generator step performs the integration and C coding tasks using the codes generated in the system design phase and the ECU setting phase. Here, the BSW Generator step performs BSW source generation, SWC coding, and service SWC generation.

Hereinafter, various embodiments of the present invention will be described in detail based on the basic concept of the above-mentioned Autosar.

1 is a block diagram illustrating a server apparatus according to an embodiment of the present invention. 1, the server apparatus 100 includes a communication unit 110, a storage unit 120, a file format conversion unit 130, a web page generation unit 140, , And a control unit 150, as shown in FIG.

Here, the user terminal device may be a smart phone, a tablet computer, a notebook computer, a personal digital assistant (PDA), a portable multimedia player (PMP), or the like, which can display a web page screen provided in the server device 100, player), a personal computer (PC), and the like. In this case, the connection can be performed by the user inputting the URL address corresponding to the server device 100 to the user's terminal device.

Meanwhile, the communication unit 110 enables communication between the server apparatus 100 and an external apparatus. In particular, the communication unit 110 enables communication between the server apparatus 100 and a terminal apparatus of a user.

Here, the communication unit 110 may be connected in a wireless or wired manner via a local area network (LAN) and an Internet network, a form connected through a USB (Universal Serial Bus) port, a mobile communication network Or a short-range wireless communication method such as NFC (Near Field Communication), Radio Frequency Identification (RFID), Wi-Fi, or the like.

The storage unit 120 stores various data and applications necessary for the operation. In particular, the storage unit 120 may store various tools for file format conversion. Also, the storage unit 120 may store data of various file formats received from the user's terminal device.

Here, the storage unit 120 may be implemented as a storage medium provided in the server apparatus 100, or may be implemented as a separate DB (Data Base) connected externally so as to be able to communicate with the server apparatus 100.

When the data of the first file format is received from the terminal device connected to the server apparatus 100, the file format conversion unit 130 converts the received first file format Can be converted into data of the second file format. This will be described later with reference to Figs. 2 to 7.

The web page generation unit 140 may generate a web page to be provided to the user terminal device connected to the server device 100. [

In particular, the web page generator 140 may generate a first web page for file format conversion and a second web page for providing data of the converted second file format.

Here, the first web page for file format conversion includes a UI (User Interface) area for selecting a first file format, a UI area for selecting a second file format, a file for inputting data for data of a first file format And a UI area for inputting data of the first file format.

For example, a UI (User Interface) area for selecting a first file format is a UI area for selecting a file format before the file format is converted, and can select an Excel format, an image format, an ARXML format, a C format, have.

The UI (User Interface) area for selecting the second file format is a UI area for selecting a file format after converting the file format, and can select an Excel format, an image format, an ARXML format, a C format, and the like .

The UI area for inputting the file of the first file format is an area for uploading the file before the file format conversion to the server device 100. The UI area is a file of an Excel format, a file of an image format, a file of an ARXML format, Formatted file or the like can be uploaded to the server apparatus 100.

The UI area for inputting the data of the first file format is an area for inputting the source code before file format conversion, and can input the ARXML source code, C source code, Excel data, and the like.

On the other hand, the second web page for providing the data of the second file format may include at least one of a UI area for downloading the file of the second file format and a UI area for displaying the data of the second file format.

Here, the UI area for downloading the file of the second file format is an area for downloading the file after the file format conversion from the server apparatus 100, and includes a file of an Excel format, a file of an image format, a file of an ARXML format, Format file or the like can be downloaded from the server apparatus 100.

The UI area displaying the data of the second file format is an area for displaying the source code after the file format conversion, and can display the ARXML source code, C source code, Excel data, image diagram data and the like.

The control unit 150 controls the overall operation of the server device 100. More specifically, the control unit 150 may control all or a part of the communication unit 110, the storage unit 120, the file format conversion unit 130, and the web page generation unit 140.

In particular, when the terminal device is connected to the server device 100, the control unit 150 controls the communication unit 110 to provide the first web page for file format conversion, which is generated by the web page generation unit 140, Can be controlled.

In this case, the terminal device can display the first web page provided from the server device 100, and the user can select the UI area for inputting the file of the first file format in the first web page displayed on the terminal device, The data of the first file format can be transmitted to the server device 100 through the UI area for inputting the formatted data.

In addition, the user can select the file format before the file format is converted through the UI area for selecting the first file format in the first web page displayed on the terminal device.

Also, the user can select a file format to be converted through the UI area for selecting the second file format in the first web page displayed on the terminal device.

On the other hand, when the data of the first file format is received from the terminal device connected to the server device 100, the control unit 150 transmits the data of the received first file format to the second file corresponding to the second file format selected by the user The file format conversion unit 130 can be controlled so as to be converted into data of the format.

If the data of the first file format is converted into the data of the second file format in accordance with the file format conversion, the control unit 150 controls the second file format for providing data of the second file format, It is possible to control the communication unit 110 to provide the web page to the connected terminal device.

In this case, the terminal device can display the second web page provided from the server device 100, and the user can download the file via the UI area for downloading the file of the second file format in the second web page displayed on the terminal device, The file of the second file format according to the format conversion can be downloaded.

Further, the user can confirm the source code of the second file format according to the file format conversion through the UI area displaying the data of the second file format in the second web page displayed on the terminal device.

2 is a diagram illustrating conversion of an ARXML format to an image format according to an embodiment of the present invention. 2, the file format conversion unit 130 of the server apparatus 100 converts data 201 of the received system ARXML format into image data of at least one software component constituting the system in an image format The data 202 of FIG.

Here, the system ARXML format 201 may be an ARXML format created through a system design step of the development methodology proposed in the AUTO standard.

Specifically, the file format conversion unit 130 of the server apparatus 100 may analyze the data in the system ARXML format to obtain data on at least one software component constituting the system. The data for the software component may include at least one of name data of the software component, connection relationship data of the software component, executable object (runnable) data included in the software component, port data of the software component, Connection relationship data between the ports, and the like.

The file format conversion unit 130 of the server device 100 uses the data of the acquired at least one software component to diagram the connection relation, port, and name of at least one software component constituting the system It is possible to generate data 202 of a schematized image format.

The file format conversion unit 130 of the server apparatus 100 converts the received data 201 in the system ARXML format into data of at least one software component constituting the system in an image format 202).

3 is a diagram illustrating conversion of an ARXML format to an Excel format according to an embodiment of the present invention. 3, the file format conversion unit 130 of the server apparatus 100 may convert the received data 301 in the system ARXML format or the ECU parameter ARXML 301 into data in the Excel format 302 .

<Example of converting system ARXML format to Excel format>

Specifically, the file format conversion unit 130 of the server apparatus 100 may analyze the data 301 in the system ARXML format to obtain data on at least one software component constituting the system.

The file format conversion unit 130 of the server apparatus 100 uses the data of the acquired at least one software component to determine a connection relationship, a port, a name, a runabilty, etc. for at least one software component constituting the system Data in the Excel format in which the data is classified by each element can be generated.

Accordingly, the file format conversion unit 130 of the server apparatus 100 can convert the received system ARXML formatted data 301 into the excel formatted data 302.

<Example of converting the ECU parameter ARXML format to Excel format>

Specifically, the file format conversion unit 130 of the server apparatus 100 can obtain the ECU setting parameter data by analyzing the data 301 in the ECU parameter ARXML format.

Here, the ECU parameter ARXML may be an ARXML format created through the ECU setting step of the development methodology proposed by the automobile standard.

The file format conversion unit 130 of the server apparatus 100 writes the ECU setting parameter data into the corresponding element by using the obtained ECU setting parameter data and stores the ECU setting parameter data in an Excel format 302 Can be generated.

Accordingly, the file format conversion unit 130 of the server apparatus 100 can convert the received data 301 of the ECU parameter ARXML format into the data 302 of the Excel format.

FIG. 4 illustrates conversion of an Excel format to an ARXML format according to an embodiment of the present invention. 4, the file format conversion unit 130 of the server device 100 converts the received data 401 of the Excel format into the data 402 of the system ARXML format or the data 402 of the ECU parameter ARXML .

Specifically, the file format conversion unit 130 of the server apparatus 100 can analyze the data 401 in the Excel format and obtain data for each element.

The file format conversion unit 130 of the server device 100 applies the acquired element-by-element data to the autosampler standard format and converts it into data 402 in the system ARXML format or data 402 in the ECU parameter ARXML format .

Accordingly, the file format conversion unit 130 of the server device 100 can convert the received data 401 of the Excel format into the data 402 of the ARXML format.

Conversely, the conversion from the Excel format to the ARXML format and the conversion from the ARXML format to the Excel format will be described in detail with reference to FIGS. 5 to 6. FIG.

5 to 6 are views showing an example of converting an ECU parameter ARXML format according to an embodiment of the present invention into an Excel format.

5 shows a part of the source code of the ECU parameter ARXML format. In this case, the file format conversion unit 130 of the server apparatus 100 can analyze the data in the ECU parameter ARXML format to obtain the ECU setting parameter data. For example, ECU configuration parameter data such as a description, parameters, and the like for 'OsAlarmAutostart' in the source code 501 shown in FIG. 5 can be obtained.

The file format conversion unit 130 of the server apparatus 100 writes the acquired ECU setting parameter data to a corresponding one of a plurality of elements 601 and 602 such as Module, Container, SubContainer, parameter / reference, , Thereby generating the Excel format 602 as shown in FIG. 6 in which the ECU setting parameter data is classified by each element.

5 to 6 illustrate the conversion of the ECU parameter ARXML format into the Excel format. However, this is also applicable to the case where the system ARXML format is converted into the Excel format. In addition, the conversion of the Excel format to the ARXML format, which is the standard format of the Auto Corporation, can be performed in the reverse process of the above-described operation.

7 is a diagram illustrating conversion of a legacy code into an ARXML format or an Excel format according to an embodiment of the present invention. 7, the file format conversion unit 130 of the server device 100 converts the C format data 701 corresponding to the received legacy code into the ARXML format data 702 or the Excel format (702).

Here, the legacy code may be a C format corresponding to the software for vehicle control before the AutoShape standard.

<Example of converting C format data into Excel format data>

Specifically, the file format conversion unit 130 of the server device 100 may analyze the C format data 701 corresponding to the legacy code to obtain the C code configuration data. Here, the C code configuration data may include file name data, RETURN data, function name data, function input data, function output data, and the like.

The file format conversion unit 130 of the server apparatus 100 can write the obtained C code configuration data into the corresponding element and generate the Excel format 702 in which the C code configuration data is classified according to each element.

Accordingly, the file format conversion unit 130 of the server device 100 can convert the data 701 of the C format corresponding to the received legacy code into the data 702 of the Excel format.

&Lt; Example of converting data of C format into data of ARXML format >

Specifically, the file format conversion unit 130 of the server device 100 may analyze the C format data 701 corresponding to the legacy code to obtain the C code configuration data. Here, the C code configuration data may include file name data, RETURN data, function name data, function input data, function output data, and the like.

The file format conversion unit 130 of the server apparatus 100 can generate the data 702 in the ARXML format by converting the obtained C code configuration data to match the auto signature standard format. For example, the file format conversion unit 130 can perform an operation such as converting a function name used in a legacy code into a function name corresponding to an auto company standard format. In addition, the file format conversion unit 130 can convert the data type used in the legacy code to the data type corresponding to the auto company standard format. You can also create a sender-receiver interface when passing arguments to another file in your legacy code. You can also create a client-server interface when calling other file functions from legacy code.

Accordingly, the file format conversion unit 130 of the server apparatus 100 can convert the data 701 of the C format corresponding to the received legacy code into the data 702 of the ARXML format.

8 is a diagram illustrating a web page according to an embodiment of the present invention. 8, the first web page for file format conversion includes a UI area 801 for selecting a first file format, a UI area 802 for selecting a second file format, A UI area 804 for inputting a file for data, a UI area 803 for inputting data of the first file format, and a UI area 805 for inputting a file format conversion command have.

Here, the UI area 801 for selecting the first file format is a UI area for selecting a file format (input file format) before the file format is converted. The UI area 801 includes an Excel format, an image format, an ARXML format, Can be selected.

The UI area 802 for selecting the second file format is a UI area for selecting a file format (output file format) after the file format has been converted. The UI area 802 is an Excel format, an image format, an ARXML format, Can be selected.

The UI area 804 for inputting the file of the first file format is an area for uploading the file (input file) before file format conversion to the server device 100, A file in the ARXML format, a file in the C format, and the like can be uploaded to the server apparatus 100. [

The UI area 803 for inputting data of the first file format is an area for inputting the source code before file format conversion, and can input the ARXML source code, the C source code, and the like.

The first web page as shown in FIG. 8 can be provided to the connected terminal apparatus when the terminal apparatus first accesses the server apparatus 100. FIG.

On the other hand, when data of the first file format is received through the first web page as shown in FIG. 8 and the file format conversion conversion 805 is selected, the server apparatus 100 transmits the data of the received first file format to the user To the second file format corresponding to the second file format selected from the second file format.

When data of the first file format is converted into data of the second file format according to the file format conversion, the server device 100 provides the second web page for providing data of the second file format to the connected terminal device can do.

In this case, the terminal device can display the second web page provided from the server device 100, and the user can select the UI area for downloading the file of the second file format in the second web page displayed on the terminal device, The file of the second file format according to the file format conversion can be downloaded. Further, the user can confirm the source code of the second file format according to the file format conversion by checking the UI area displaying the data of the second file format in the second web page displayed on the terminal device.

9 is a flowchart illustrating a method of providing an autosource-related service according to an embodiment of the present invention. Referring to FIG. 9, a first web page for file format conversion may be provided to a terminal device connected to the server device 100 (S901). Here, the first web page includes a UI (User Interface) area for selecting a first file format, a UI area for selecting a second file format, a UI area for inputting a file for data of the first file format, And a UI area for inputting data in one file format.

When the terminal device connected to the server device 100 transmits the data of the first file format via the first web page, the data of the first file format can be received from the terminal device (S902).

When the user inputs a file format conversion command using the terminal device, the server device 100 can convert the received data of the first file format into data of the second file format (S903).

Then, the second Web page for providing data of the converted second file format may be provided to the connected terminal device (S904).

Here, the second web page may include at least one of a UI area for downloading files for data of the second file format, and a UI area for displaying data of the second file format.

Here, the first or second file format may be ARXML, which is the standard format of AUTOSAT.

10 is a flowchart illustrating a method for converting a system ARXML format to an image format or an Excel format according to an embodiment of the present invention. Referring to FIG. 10, a first web page for file format conversion may be provided to a terminal device connected to the server device 100 (S1001).

When the terminal device connected to the server device 100 transmits the data in the system ARXML format through the first web page, the data in the system ARXML format can be received from the terminal device (S1002).

When the user inputs a file format conversion command using the terminal device, the server device 100 analyzes data of the system ARXML and obtains data of at least one software component constituting the system (S1003) .

The data for the software component may be transformed into an Excel format that is classified into image formats or elements that are represented by diagrams using data of at least one acquired software component (S1004).

Then, the second web page for providing data of the converted file format can be provided to the connected terminal device (S1005).

11 is a flowchart illustrating a method of converting an ECU parameter ARXML format according to an embodiment of the present invention into an Excel format. Referring to FIG. 11, a first web page for file format conversion may be provided to a terminal device connected to the server device 100 (S1101).

Then, when the terminal device connected to the server device 100 transmits data in the ECU parameter ARXML format through the first web page, the server device 100 can receive data on the ECU parameter ARXML format (S1102) .

Then, when the user inputs a file format conversion command using the terminal device, the ECU parameter data can be obtained by analyzing the data on the ECU parameter ARXML format (S1103).

Then, by using the acquired data, the ECU setting parameter data can be converted into an Excel format that is classified by elements (S1104).

Then, the second web page for providing data in the converted format can be provided to the connected terminal device (S1105).

12 is a flowchart illustrating a method of converting an Excel format to an ARXML format according to an embodiment of the present invention. Referring to FIG. 12, a first web page for file format conversion may be provided to a terminal device connected to the server device 100 (S1201).

When the terminal device connected to the server device 100 transmits the data in the Excel format via the first web page, the server device 100 can receive the data for the Excel format from the connected terminal device (S1202 ).

Then, the data for the Excel format can be analyzed to acquire the data for each element (S1203).

If the user inputs a file format conversion command using the terminal device, the acquired data for each element can be converted into the system ARXML format or the ECU parameter ARXML format by applying the data according to the standard format (S 1204).

Then, the second web page for providing data in the converted format can be provided to the connected terminal device (S1205).

FIG. 13 is a flowchart illustrating a method of converting a format of a distance code according to an embodiment of the present invention into an ARXML format. Referring to FIG. 13, a first web page for file format conversion may be provided to a terminal device connected to the server device 100 (S1301).

When the terminal apparatus connected to the server apparatus 100 transmits the data in the Excel format via the first web page, the server apparatus 100 can receive the data on the run length code format from the connected terminal apparatus (S1302).

When the user inputs a file format conversion command using the terminal device, the format corresponding to the run length code can be converted to match the auto signature standard format (S1303).

Then, the second Web page for providing data in the converted format may be provided to the connected terminal device (S1304).

Meanwhile, the method of providing an autosource-related service according to various embodiments of the present invention may be implemented in the form of installation data for execution in a server device, and may be stored in various non-transitory computer readable media. Server or devices.

A non-transitory readable medium is a medium that stores data for a short period of time, such as a register, cache, memory, etc., but semi-permanently stores data and is readable by the apparatus. In particular, the various applications or programs described above may be stored on non-volatile readable media such as CD, DVD, hard disk, Blu-ray disk, USB, memory card, ROM,

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, but, on the contrary, It will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the present invention.

100: server device 110:
120: Storage unit 130: File format conversion unit
140: Web page generator 150:

Claims (15)

A method of providing an autosar related service of a server apparatus,
Providing a first web page for file format conversion to a terminal device connected to the server device;
Receiving data of a first file format from the connected terminal device;
Converting the data of the received first file format into data of a second file format; And
And providing a second web page for providing data of the converted second file format to the connected terminal device,
Wherein the first or second file format is an ARXML standard format of Autosar. The method according to claim 1,
Wherein the first web page for file format conversion comprises:
A user interface (UI) area for selecting the first file format, a UI area for selecting the second file format, a UI area for inputting a file for data of the first file format, And a UI area for inputting the data of the service provider. The method according to claim 1,
The first file format is a system ARXML created through a system design step of the development methodology proposed in the AUTO standard,
Wherein the second file format is an Excel format in which data for at least one software component constituting the system is categorized by image formats or elements represented by diagrams,
Wherein the converting comprises:
Related system, the method comprising: analyzing the system ARXML to obtain data for the at least one software component, and performing the conversion using data for the at least one software component; Way. The method according to claim 1,
The first file format is the ECU parameter ARXML created through the ECU setting step of the development methodology proposed in the AUTOSAR standard,
Wherein the second file format is an Excel format for classifying the ECU setting parameter data by elements,
Wherein the converting comprises:
Wherein the ECU parameter analysis unit analyzes the ECU parameter ARXML to obtain the ECU setting parameter data, and performs the conversion using the obtained ECU setting parameter data. The method according to claim 1,
Wherein the first file format is an Excel format,
The second file format is ARXML created through the system designing step or the ECU setting step among the development methodologies proposed by the AUTOSAR standard,
Wherein the converting comprises:
The method comprising: acquiring element-by-element data in the Excel format; and applying the obtained element-by-element data to an autosampler standard format to perform the conversion. The method according to claim 1,
The first file format is a format corresponding to a legacy code created before Autosam standard,
The second file format is ARXML, which is an autosampler standard format,
Wherein the converting comprises:
And converting the legacy code to match an autosource standard format. The method according to claim 1,
A second web page for providing data of the second file format,
A UI area for downloading a file for the data of the second file format, and a UI area for displaying data of the second file format. 1. A server apparatus for providing an Autosar-related service,
A web page generator for generating a web page;
A communication unit for providing a first web page for file format conversion generated by the web page generation unit to a terminal device connected to the server apparatus;
A file format conversion unit for converting the data of the first file format into data of the second file format when the data of the first file format is received from the connected terminal apparatus through the first web page; And
A control unit for controlling the web page generator to generate a second web page for providing the converted data of the second file format and controlling the communication unit to provide the generated second web page to the connected terminal apparatus; Lt; / RTI &gt;
Wherein the first or second file format is ARXML, which is an autosampler standard format. 9. The method of claim 8,
A user interface (UI) area for selecting the first file format, a UI area for selecting the second file format, a UI area for inputting a file for data of the first file format, And a UI area for inputting data of the server device. 9. The method of claim 8,
The first file format is a system ARXML created through a system design step of the development methodology proposed in the AUTO standard,
Wherein the second file format is an Excel format in which data for at least one software component constituting the system is categorized by image formats or elements represented by diagrams,
Wherein the file format conversion unit comprises:
Analyzing the system ARXML to obtain data for the at least one software component, and performing the conversion using data for the at least one software component. 9. The method of claim 8,
The first file format is the ECU parameter ARXML created through the ECU setting step of the development methodology proposed in the AUTOSAR standard,
Wherein the second file format is an Excel format for classifying the ECU setting parameter data by elements,
Wherein the file format conversion unit comprises:
Analyzes the ECU parameter ARXML to obtain the ECU setting parameter data, and performs the conversion using the obtained ECU setting parameter data. 9. The method of claim 8,
Wherein the first file format is an Excel format,
The second file format is ARXML created through the system designing step or the ECU setting step among the development methodologies proposed by the AUTOSAR standard,
Wherein the file format conversion unit comprises:
Acquiring element-by-element data in the Excel format, and applying the obtained element-by-element data to an autosampler standard format to perform the conversion. 9. The method of claim 8,
Wherein the first file format is a format corresponding to a legacy code created before Autosam standard,
The second file format is ARXML, which is an autosampler standard format,
Wherein the file format conversion unit comprises:
And converts the legacy code to match the auto company standard format. 9. The method of claim 8,
A second web page for providing data of the second file format,
A UI area for downloading a file of data of the second file format, and a UI area for displaying data of the second file format. A computer-readable recording medium having recorded thereon a program code for performing the method according to any one of claims 1 to 7.

Images