KR100942896B1 - Management system for development of terminal flatform dynamic system library and method thereof - Google Patents

Abstract

The present invention discloses a system and method for terminal platform DSL development management. Development management system according to the present invention, DSL registration system for DSL development and DSL profile, binary registration and approval request for registering the binary; A package registration device for registering package information that is a DSL set with an associated platform core for the DSL; A verification server for verifying, on the terminal, a DSL requested for approval from a DSL registration device and a package registration device, and a package associated with it; A platform management terminal for inputting a verification result of the verification server into the system and generating a final approval result for the verification based on output data corresponding to the input result; And a verification server for verification of the DSL and the package, and a package registration management server for providing the corresponding package profile, the DSL profile, and the DSL binary to the device management (DM) in response to the verification result. Therefore, the present invention provides a development environment for supporting DSL development of DSL developers, establishes a package-based verification procedure including DSL, and then transmits the corresponding package profile, DSL profile, and DSL binary to the DM for system development. It has the effect of shortening the efficiency and development time.

Terminal, platform, DSL, package, development, validation, approval, DM

Description

MANAGEMENT SYSTEM FOR DEVELOPMENT OF TERMINAL FLATFORM DYNAMIC SYSTEM LIBRARY AND METHOD THEREOF

The present invention relates to terminal platform development management of a mobile communication terminal, and more particularly, to establish a development support system for a dynamic platform (DSL) and a package, which is a terminal platform middleware component unit, to enable application and content activation based on a terminal platform. A terminal platform DL development management system and method for induction.

Recently, a system called 'third generation' (3G) has been developed as a cellular telecommunication system of the future. 3G systems will combine high-speed Internet access with traditional voice communications, allowing users to connect to Internet browsing, audio / video streaming, positioning, video conferencing, and many other functions in addition to voice communications. Will provide.

The Third Generation Partnership Project (3GPP) was established to determine compatibility between several 3G systems developed around the world. The Universal Mobile Telephone System (UMTS) is being developed by 3GPP to provide 3G systems including terrestrial and topological systems that can propagate voice, data and multimedia anywhere in the world.

The rapidly increasing functionality included in cellular telecommunication systems through 3GPP standardization is required for mobile terminal developers used in such systems. This demand is vulnerable in that the mobile terminal is in a 'lack of resources' environment, which is limited in size, memory and power.

Traditionally, mobile terminal manufacturers include virtually all the hardware and software necessary for basic terminal operation, as well as the hardware and software necessary to give a particular user the desired characteristics and functions based on the awareness of their manufacturer or their market demand. Designs, manufactures and sells complete mobile terminal systems. Such an approach does not provide the flexibility to quickly adapt to rapid changes in market demand or to meet the diverse needs of many users.

Recognizing the inadequacies of traditional methods in designing and manufacturing mobile terminals, mobile terminal platform assemblies have been developed to functionally include a plurality of software and hardware auxiliary units that can be sold as a unit to a plurality of users. This allows each user to load, install, and run their application in the assembly to provide a complete mobile terminal platform system that meets their specific needs.

The mobile terminal platform assembly software and the application software are separately developed and then combined by loading, installing, and executing the application software in the mobile terminal platform assembly, wherein the platform system as described above is provided between the platform assembly software and the application software. It requires a very well-defined interface.

Therefore, there is a need for an interface for a platform system for a mobile terminal of a wireless telecommunication system such that the software and application software of the mobile terminal platform assembly of the system are developed separately and then combined via an interface to complete the platform system. At present, the system structure for such a development environment is not established.

In response to the requirements of the environment, a platform development for a mobile terminal, for example, a development system for a dynamic system library (DSL) and a package, which is a platform middleware component unit, is not clearly linked to a platform manager and a device management (DM). There is an unnecessary waste of development. Therefore, the necessity of systematic management and system for terminal platform middleware development and verification as well as the development environment of system development is required.

The present invention has been created to solve the above problems, and an object of the present invention is to provide a systematic management and system for terminal platform middleware development and verification, to build a stable platform for terminal platform development SL development management system and method to provide.

Another object of the present invention is to provide a systematic management and system for the development and verification of terminal platform middleware, to support the stable commercialization of the terminal platform and to provide a variety of DSL terminal platform DSL that can activate the application and content based on the platform To provide a development management system and method.

Another object of the present invention is to provide a development environment such as Emulator and SDK distribution, Q & A, and issue support on the system to support DSL development of DSL developers, and through the verification of the package unit including the DSL, It provides a terminal platform DS development management system and method that can reduce system development efficiency and development time through a series of prescribed procedures for sending DSL profiles and DSL binaries to DM.

Terminal platform DS development management system according to the first aspect of the present invention for achieving the above object, in the system for implementing the DSL and package registration and approval procedures, the system version information and DSL profile for the DSL development, A DSL registration device for registering and approving the binary; A package registration device for registering package information that is a DSL set with an associated platform core for the DSL; A verification server for verifying, on the terminal, a DSL and a package associated with the request for approval from the DSL registration device and the package registration device; A platform management terminal for inputting a verification result of the verification server into a system and generating a final approval result for verification based on output data corresponding to the input result; And receiving platform core and DSL package information provided from the DSL registration device and the package registration device, requesting the verification server to verify the DSL and the package, and receiving the verification result from the platform management terminal. In response to the result, the package profile, the DSL profile, and the package registration management server for providing the DSL binary to the DM (Device Management) is characterized in that it is configured.

Terminal platform DS development management method according to a second aspect of the present invention for achieving the above object, a) system version information and DSL profile according to the result of performing DSL development using the DSL registration device for the completed DSL, Registering a binary; b) identifying a package associated with the DSL profile and registering package information that is a DSL set with an associated platform core for the DSL using the package registration device; c) receiving, at the package registration management server, platform core and DSL package information provided from the DSL registration device and the package registration device, extracting package information associated with the DSL from the package registration management device, and requesting verification to the verification server; Making; d) determining, by the platform management terminal, whether or not to approve DSL based on a result of package verification of the platform and DSL; e) transmitting the DSL profile and the binary to the DM if the approval is made as a result of the determination of step d), and notifying the non-approved state by feeding back to the a) step if the approval is made as a result of the determination of step d). step; f) extracting package information associated with the DSL in response to the DSL approval of step e), and performing verification of a package unit including a DSL; And g) when the verification of the step d) fails, the verification of the DSL package information is fed back to the step b) to notify the unapproved status of the DSL package information, while the verification result of the step f), the DSL package When the verification approval for the information is made, it characterized in that the step of transmitting a profile for the package information to the DM.

The terminal platform DS development management system and method according to the present invention provides a development environment for supporting DSL development of the DSL developer, and after establishing a package-based verification procedure including the DSL, the corresponding package profile and DSL profile and By sending the DSL binary to the DM, the system development efficiency and development time can be shortened, and terminal platform-based applications and contents can be activated.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.

First, the platform DSL development management procedure according to the present invention is largely classified into a development support process, a package verification / approval process, and a DM system interworking process.

The development support process is for supporting DSL development of DSL developers, and includes emulator and SDK distribution, Q & A, and issue support. The package verification / approval process receives a package core and a DSL set package information from the platform developer, executes verification of the platform from a platform manager, and extracts package information associated with the requested DSL. And verify and approve the package unit including the newly requested DSL. In the DM system interworking process, a package profile, a DSL profile, and a DSL binary, on which a package has been approved, are transmitted to a device management (DM) to perform a procedure for commercializing a package.

1 is a system configuration diagram for implementing the above-described DSL and package registration procedure. As shown, the DSL registration device 101 for registering and approving the system version information, DSL profile, binary for the DSL development, and the package information for registering the DSL set and the associated platform Core and DSL set for the DSL A verification server 111 for verifying, on the terminal, a DSL registered in the package registration device 103, the DSL registration device 101 and the package registration device 103 and its associated package, and the verification server 111; And a platform management terminal 107 for inputting the verification result of the verification to the system and generating a final approval result for verification based on the output data corresponding to the input result, from the DSL registration device 101 and the package registration device 103. Receiving platform core and DSL package information, requesting verification of the DSL and package to the verification server 111, and verifying the verification result from the platform management terminal 107. And a package registration management server 105 for providing the package profile, the DSL profile, and the DSL binary to the DM (109: Device Management) in response to the reception result.

The DM 109 is a management system for providing a commercialization procedure for a binary whose final package verification is completed, and information such as a package profile, a DSL profile, a DSL binary, and the like are stored and managed in a database of the DM 109.

2 is a diagram illustrating a package registration procedure according to the present invention. As shown, in step S201 to provide a DSL development environment for the terminal platform DSL development, DSL development is made based on this development environment. The DSL development environment includes development environments such as emulator and SDK distribution, Q & A, and issue support.

In step S203, the DSL developer registers the system version information, DSL profile, and binary according to the result of the DSL development by using the DSL registration apparatus 101. The DSL registration device 101 is equipped with a browser provided from the package registration management server 105, the DSL registration device 101 requests the approval along with the registration of the file developed by the DSL developer through the browser.

Meanwhile, the platform developer receives the mounted DSL profile from the DSL registration device 101 through the package registration device 103 and checks and recognizes the package associated with the DSL profile in step S205. In operation S207, the platform developer registers package information corresponding to the platform core and DSL set associated with the DSL using the package registration apparatus 103. Accordingly, the package registration management server 105 receives platform core and DSL package information provided from the DSL registration device 101 and the package registration device 103.

The package registration management server 105 extracts package information associated with the DSL and provides the package information to the verification server 111. The verification server 111 downloads a binary for verification among package information and transmits the binary to the terminal through serial communication. This is for execution verification of the binary mounted as a terminal, and the verification result of the verification server 111 is provided to the platform management terminal 107.

In step S209, the platform management terminal 107 determines whether to approve the DSL based on the verification result of the DSL, and if the approval is determined, the approval information is provided to the package registration management server 105 as in step S211. . The package registration management server 105 transmits a DSL profile and a binary to the DM 109 in response to the approval information of the platform management terminal 107.

On the other hand, if the above-mentioned DSL is not approved in step S209, a return to the factor that is not approved is executed. That is, feedback to the DSL registration step for non-DSL approval is instructed to resolve the disapproval factor. However, when the approval for the DSL verification result is determined, the verification server 111 extracts package information associated with the DSL and performs verification of a package unit including the DSL. The verification of the package unit verifies mutual compatibility between the platform core and the DSL package information, and the verification server 111 determines whether the verification criteria are passed in step S213.

As a result of the determination in step S213, if the verification of the DSL package information fails, the feedback is fed back to the package registration step, while if the verification of the DSL package information is made, the process proceeds to step S215. That is, the platform management terminal 107 completes the package verification and provides the package registration management server 105 with approval information about the package as in step S217. In step S219, the package registration management server 105 transmits a profile for the package information to the DM 109 in response to the package approval of the platform management terminal 107. Therefore, the DM 109 performs the commercialization of the package through the package secondary network interworking test in step S221.

Meanwhile, the DSL registration procedure and the package registration procedure shown in FIG. 2 will be described in more detail with reference to FIGS. 3 to 9. 3 is a diagram for explaining a DSL registration procedure. As shown, the DSL registration procedure holds a terminal in progress of the procedure for configuring the DSL registration device 101 described above. That is, the DSL developed by the DSL developer analyzes the DSL registration terminal 301 performing the registration process by the DSL registrant, the DSL registration management terminal 303 in charge of DSL registration management, and the XML file for the DSL. An XML parsing terminal 305, a DLS storage terminal 307 for storing a DSL, and a DSL file storage terminal 309 for storing a file for the DSL.

First, the DSL developed by the DSL developer performs a registration request to the DSL registration terminal 301 in step S301. In step S303, the DSL registration terminal 301 transmits an XML file and a binary file for the DSL developed by the DSL developer to the DSL registration management terminal 303. The DSL registration management terminal 303 enters the step S305 to instruct the XML analysis terminal 305 to register the XML file.

In step S307, the XML parsing terminal 305 checks an error for the XML file for the currently received DSL, and if an error occurs as a result of the check, the XML parsing terminal 305 notifies the fact that the registration failed with the DSL registration terminal 301 as in step S309. Notify me. On the other hand, if an error is not found as a result of the error check on the XML file for the currently received DSL, the process proceeds to step S311 and instructs the DSL storage terminal 307 to store the corresponding DSL information.

In addition, the XML analysis terminal 305 notifies the DSL registration management terminal 303 of the analysis result of the XML file in step S313, and the DSL registration management terminal 303 in step S315, the binary for the DSL file. The file is transmitted to the DSL file storage terminal 309, and the DSL registration management terminal 303 requests registration of the current DSL file to the DSL registration terminal 301 in step S317.

4 is a flowchart illustrating a DSL approval procedure according to the present invention. First, look at the terminal for the DSL approval prior to the approval process, the DSL approval terminal 401 for DSL approval, the DSL approval management terminal 403 for storing and managing DSL approval information, and the inspection of the approved DSL information DSL checking means 405 for performing the operation, DSL file checking means for performing file inspection on the approved DSL information 407, and DSL for transmitting the final approved and verified DSL file to the DM 109. It is composed of an interface terminal 409.

As shown, the DSL provided by the DSL registration device 101 in step S401 requests the DSL approval terminal 401 for approval. The DSL approval terminal 401 transmits a DSL file to the DSL approval management terminal 403 in step S403, and the DSL approval management terminal 403 inspects a DSL check means 405 and a DSL file in steps S405 and S407. The terminal 407 requests the DSL and the DSL file to be inspected, and receives a result thereof.

If it is determined that the inspection result received from the DSL approval management terminal 403 is inappropriate, the DSL approval management terminal 403 notifies the DSL approval terminal 401 of the rejection of approval in step S409. However, if it is determined that the inspection result received from the DSL approval management terminal 403 is appropriate, the DSL approval management terminal 403 transmits a DSL to the DSL interface terminal 409 in step S411, and Request transmission to DM 109.

The DSL interface terminal 409 provides the approval request information for the corresponding DSL to the DM 109 in step S413, and provides a result of the approval request to the DSL approval management terminal 403 in step S415. In operation S417, the DSL approval management terminal 403 provides a response signal for the approval result to the DSL approval terminal 401.

5 is a flowchart illustrating a DSL deletion procedure according to the present invention. Each terminal required for the DSL deletion procedure, first, a DSL deletion terminal 401 for executing DSL development or returned DSL, a DSL deletion management terminal 503 for registering and managing DSL deletion, and DSL deletion A DSL storage terminal 505 for storing information and a DSL file storage terminal 507 for storing and managing a DSL file approved for deletion are configured.

The operation of the terminal for deleting the DSL configured as described above, the DSL developer first requests the file deletion to the DSL deletion terminal 501 in step S501. The DSL deletion terminal 501 instructs the DSL deletion management terminal 503 to search for and delete the corresponding DSL deletion in step S503. In step S505, the DSL deletion management terminal 503 determines whether or not to delete by checking whether the DSL is not approved.

As a result of the determination by the DSL deletion management terminal 503, if the corresponding DSL is an approved file, that is, when it is not the target of deletion, the DSL deletion management terminal 503 cancels the approval of the DSL at step S507. (501). However, when the DSL deletion management terminal 503 determines that the DSL is an unapproved file, that is, the deletion target, the DSL deletion management terminal 503 in step S509, the DSL storage terminal 505 to the DSL Instruct to delete.

In operation S511, the DSL file storage terminal 507 instructs the DSL binary file to be deleted. In step S513, the DSL deletion management terminal 503 notifies the DSL deletion terminal 501 of the result of the deletion processing by the DSL storage terminal 505 and the DSL file storage terminal 507. The DSL deletion terminal 501 registers information on deleting the corresponding DSL.

6 is a flowchart for explaining a platform registration procedure according to the present invention. This process consists of a platform registration terminal 601, a platform registration management terminal 603, an XML analysis management terminal 605 for analyzing the XML for the platform file and a platform storage terminal 607 for storing platform information. do.

Looking at the platform registration process configured as described above, first, in step S601 platform developers request the platform in accordance with the platform registration procedure to the platform registration terminal (601). In step S603, the platform registration terminal 601 requests the platform registration for the platform to the platform registration management terminal 603, and in step S605 the platform registration management terminal 603 reads the XML file for the platform Send to the XML analysis management terminal 605.

In step S607, the XML analysis management terminal 605 determines whether to approve the platform. In addition, as a result of the approval decision, if the platform is not approved as in step S609, the XML analysis management terminal 605 notifies the platform registration terminal 601 of the registration failure. On the contrary, when the XML analysis management terminal 605 determines that the XML file for the platform is approved, the XML analysis management terminal 605 instructs the platform storage terminal 607 to store the approved platform.

In step S613, the XML analysis management terminal 605 notifies the platform registration management terminal 603 of the XML analysis result, and the platform registration management terminal 603 registers a decision state of the corresponding platform in step S615. To the platform registration terminal (601).

7 is a flowchart illustrating a platform approval procedure according to the present invention. The terminal applied in the illustrated process is composed of a platform approval terminal 701, a platform approval management terminal 703, a platform inspection means 705, and a platform interface 707 for transmitting the completed inspection platform to the DM 109. do.

In the platform approval procedure of the terminal system configured as described above, the platform manager first presents platform information to the platform approval terminal 701 in step S701. The platform approval terminal 701 requests the approval of the platform to the platform approval management terminal 703 in step S703.

In step S705, the platform approval management terminal 703 requests the platform inspection means 705 to inspect the platform. Then, the platform approval management terminal 703 receives the inspection result from the platform inspection means end 705. The platform approval management terminal 703 receives the inspection result provided from the platform inspection means 705, but if the inspection result rejects the platform approval, the platform approval management terminal 703 is the platform approval terminal in step S707 701 notifies the approval denial for the platform.

On the other hand, if the inspection result received by the platform approval management terminal 703 approves the platform, the platform approval management terminal 703 enters platform information to the platform interface 707 and enters step S709. Request transmission to the DM 109. The platform interface 707 provides the platform to the DM 109 in step S711, and the DM 109 transmits the reception result of the platform received in step S713 to the platform approval management terminal 703. . In operation S715, the platform approval management terminal 703 notifies the platform approval terminal 701 of the platform approval terminal 701 by notifying the final result of the platform approval.

8 is a flowchart illustrating a platform inspection procedure according to the present invention. Prior to the description of this process, the terminal applied to the first is composed of the platform check terminal 801, the platform inspection management terminal 803, the platform inspection means 805 and the DSL file storage terminal 807.

Looking at the platform inspection procedure based on such a configuration, in step S801, the platform verifier requests the platform inspection terminal to the platform check terminal 801, and enters the step S803, the platform inspection management terminal 803 is the platform In response to the request of the check terminal 801, it has an execution procedure for the platform inspection. That is, in step S805, the platform inspection management terminal 803 provides the platform associated with the DSL to the platform inspection means 805, and requests the inspection thereof.

In addition, the platform inspection management terminal 803 enters the step S807 and downloads the corresponding DSL file to the DSL file storage terminal 807. In addition, the platform inspection management terminal 803 performs an offline test on the platform in step S809, and provides the result to the platform check terminal 801 as in step S811, thereby completing the platform inspection.

9 is a flowchart illustrating a platform deletion procedure according to the present invention. In this process, the platform deletion terminal 901, the platform deletion management terminal 903 and the platform deletion information registration terminal 905. Based on this, the platform deletion procedure is described as follows.

First, in step S901, the platform developer requests the platform deletion terminal 901 to delete a platform in which a development error or development fails. The platform deletion terminal 901 instructs the platform deletion management terminal 903 to delete the platform in step S903. In step S905, the platform deletion management terminal 903 determines whether the platform is currently unapproved for the platform requested to be deleted.

As a result of the determination in step S905, when the platform currently requested to be deleted is an approved platform, that is, a platform that is not a target of deletion, as in step S907, the platform deletion management terminal 903 cannot be deleted by the platform deletion terminal 901. Notify. On the other hand, as a result of the determination in step S905, if the platform currently requested to be deleted is an unapproved platform, the platform is provided to the platform deletion information registration terminal 905, as in step S909. In operation S911, the platform deletion management terminal 903 notifies the platform deletion terminal 901 of the deletion status of the corresponding platform.

As described above, the present invention provides a development support system for a DSL and a package, which is a terminal platform middleware component unit, and builds an infrastructure that can contribute to stable commercialization support and application and content activation of a terminal platform, thereby speeding up platform development. Accelerate to increase the value of industrial use.

1 is a block diagram showing a terminal platform DS development management system according to the present invention.

FIG. 2 is a flowchart for explaining the main functions of FIG. 1.

FIG. 3 is a flowchart for explaining the DSL registration procedure of FIG. 1.

FIG. 4 is a flowchart for explaining a DSL approval procedure of FIG. 1.

FIG. 5 is a flowchart for explaining a DSL deletion procedure of FIG. 1.

FIG. 6 is a flowchart for describing a platform registration procedure of FIG. 1.

FIG. 7 is a flowchart for explaining a platform approval procedure of FIG. 1.

FIG. 8 is a flowchart for explaining a platform inspection procedure of FIG. 1.

9 is a flowchart for explaining a platform deletion procedure of FIG. 1.

<Explanation of symbols for main drawings>

101: DSL registration device 103: package registration device

105: package registration management server 107: platform management terminal

109: DM 111: Verification Server

Claims (11)

A system for implementing DSL and package registration and approval procedures, A DSL registration device for registering and approving a DSL profile and binary for the DSL development; A package registration device for registering DSL package information that is a DSL set with an associated platform core for the DSL; A verification server for verifying, on the terminal, a DSL requesting approval from the DSL registration device and a package registration device and a package related thereto; A platform management terminal for inputting a verification result of the verification server into a system and generating a final approval result for verification based on output data corresponding to the input result; And Receives the DSL profile for the DSL development, the binary and the DSL package information provided from the package registration device according to the registration and approval request provided from the DSL registration device, and verifies the DSL and the package to the verification server based on this. And a package registration management server for receiving the approval result from the platform management terminal, and providing a corresponding package profile, a DSL profile, and a DSL binary to the device management (DM) in response to the received result. Terminal platform DS development management system, characterized in that. The method of claim 1, Terminal package DS development management system, characterized in that the information of the package profile, DSL profile, DSL binary stored in the DM database. The method of claim 1, The verification server downloads the binary for verification of the DSL package information, and transmits to the terminal via serial communication to manage the procedure for performing the execution verification for the binary loaded on the terminal SL Development Management System. A method for implementing DSL and package registration and approval procedures, a) registering a DSL profile and binary for the DSL development in a DSL registration device; b) identifying a package associated with the DSL profile in a package registration device, and registering DSL package information that is a DSL set with an associated platform core for the DSL; c) a package registration management server receives a DSL profile for the DSL development provided from the DSL registration device, a binary, and DSL package information provided from the package registration device, and extracts package information associated with the DSL therefrom; Requesting verification by the verification server; d) determining whether to approve in a platform management terminal based on a package verification result associated with a platform and the DSL at the verification server according to the verification request; e) As a result of the determination of step d), if the approval is made, the package registration management server transmits a DSL profile and binaries to the device management (DM), and if the result of the determination of step d) is not approved, go to step a). Feeding back a notification of unauthorized status; f) extracting package information associated with the DSL from the verification server in response to the DSL approval of step e), and performing verification of a package unit including a DSL; And g) If the verification approval of the DSL package information is verified in step f), the package registration management server transmits a profile for the DSL package information to the DM, while the verification result DSL in step f) is performed. And if the verification of the package information fails, feeding back to step b), notifying of the disapproved status of the DSL package information. The method of claim 4, wherein And the DM executes a package secondary network interworking test based on a DSL profile and binary information as well as a profile for the DSL package information. The method of claim 4, wherein step a) comprises: a-1) transmitting an XML file and a binary file for the DSL; a-2) checking an error on the XML file, if an error occurs as a result of the check, notifying that the registration failed, and if the error is not found as a result of error checking on the XML file for the DSL, storing the corresponding DSL information ; And A-3) Terminal platform DS development management method comprising the step of registering the system version information, DSL profile, binary for the stored DSL information. 7. The method of claim 6, further comprising a procedure for deleting corresponding DSL information for the DSL registration failure of step a-2); The procedure for deleting the corresponding DSL information, a-2-1) requesting deletion of failed registration DSL information; a-2-2) checking whether the information is already approved or unapproved for the DSL requested to be deleted; a-2-3) canceling the deletion approval for the DSL and notifying the DSL when the DSL is the approved file as determined in step a-2-2); And a-2-4) Terminal platform DS development management method comprising the step of instructing the deletion of the DSL information when the DSL is not approved as a result determined in step a-2-2) . The verification approval step for the DSL package information of the step g), g-1) requesting approval for the DSL; g-2) requesting inspection of the DSL and DSL file by transmitting a DSL file; And g-3) If the result of the inspection performed based on the inspection rule previously stored according to the inspection request of step g-2) determines that the corresponding DSL and DSL file are inappropriate, a notification of rejection of the DSL is notified, and g And, if it is determined that the corresponding DSL and DSL files are suitable, as a result of the inspection performed based on the pre-stored inspection rule according to the inspection request of step -2), requesting the transmission of the DSL and DSL files to the DM. Terminal platform DS development management method. The platform registration step of claim 4, wherein b-1) receiving a platform registration request for the platform; b-2) requesting an analysis of the XML file for the platform; b-3) determining whether to approve the platform according to the analysis result of step b-2); And b-4) As a result of the decision of step b-3), if the platform is not approved, the feedback is returned to step b-1) to notify the registration failure, and when the XML file for the platform is approved, the approved platform Terminal platform DL development management method comprising the step of storing and notifying. The method of claim 4, wherein the approval procedure for the platform of step d), d-1) presenting platform information requiring approval, requesting approval, and receiving a result according to the approval request; d-2) if the result received in step d-1) is a denial of approval for the platform, feeding back to step b) to notify the denial of approval for the registered platform; And d-3) if the result received in step d-1) is approved for the platform, the terminal platform DL development management method comprising the step of requesting the platform transmission to the DM. 11. The method of claim 10, further comprising the step of deleting the platform for the platform approval denial of step d-2); Deleting the platform, d-2-1) requesting to delete the platform for development errors; d-2-2) determining whether the platform is currently unapproved for the platform requested to be deleted; And d-2-3) If it is determined in step d-2-2) that the platform currently requested to be deleted is a platform that has already been approved, it is notified that the platform cannot be deleted, and in step d-2-2) And determining that the currently requested platform to be deleted is an unapproved platform, deleting the platform and registering the deletion information.

Images