KR102173840B1 - Method and device for excuting native features of a mobile device by using a broker - Google Patents

Abstract

A method for executing a native function of a mobile device using a broker is disclosed. The method for executing a native function of a mobile device using the broker is the step of transmitting a message including command data consisting of only special characters and words to the broker in response to a request for executing the native function, a native component ) Receiving the message including the command data from the broker, and the native component interprets the command data included in the received message to execute the native function, and according to the interpreted command data And executing a native code, and the operation of interpreting the command data includes executing an extraction operation of extracting the word between the special characters, and a word written by the developer using a part of the extracted word. And performing a speculative operation that infers the intention.

Description

Method and device for excuting native features of a mobile device by using a broker}

An embodiment according to the concept of the present invention relates to a method and apparatus for executing a native function of a mobile device using a broker, and in particular, for easily implementing a native function using a broker in a hybrid mobile application. It relates to a method and apparatus.

The mobile app refers to a computer program used in a mobile device such as a smart phone or a tablet PC. Mobile apps may be classified into native applications, web applications, and hybrid mobile applications. Native applications are generally developed in computer code and executed directly by a processor embodied in a mobile device. A web application is an application that accesses a network such as the Internet through a web browser. A web application is a mobile-optimized web page that looks like an app. Hybrid mobile applications are applications written using web technologies such as HTML5, CSS, and JavaScript.

Web applications and hybrid mobile applications are developed using web-based languages such as JavaScript and HTML. Web-based languages such as JavaScript and HTML are high level languages, and unlike native applications, the high-level languages cannot directly control the hardware of a mobile device. That is, web applications and hybrid mobile applications cannot directly utilize specific functions of mobile devices such as cameras, accelerometers, or GPS.

Development tools such as PhoneGap, Native Script, and React Native were provided to developers to fill the gap between the web application programming environment and the native platform programming environment. However, in order to use the development tool, developers had to learn the specialized functions of the development tool, and spent a lot of time learning the specialized functions of the development tool. In addition, in the process of converting the development tool into a native code, there is a problem in that an interface is deformed or a design cannot be freely applied. In addition, utilizing the specific function of the mobile device using the development tool is slower than using a specific function of the mobile device directly using native code.

Also, in the related art, native functions were called from the JavaScript API in the web view. As in the prior art, in order to call a native function, a developer must write a JavaScript API. However, when a designer who is not a professional developer develops a hybrid mobile application, the designer must learn the JavaScript API by spending a lot of time to write the JavaScript API. In addition, there is a problem that the designer must remember the JavaScript API, and it is not easy to accurately use the complex JavaScript API.

The technical problem to be achieved by the present invention is to provide a method and apparatus for easily implementing native functions in a hybrid mobile application using a broker.

In the method for executing a native function of a mobile device using a broker according to an embodiment of the present invention, in response to a request for executing the native function, the web application transmits a message including command data composed of only special characters and words to the broker. , A native component receiving the message including the command data from the broker, and the native component interpreting the command data included in the received message to execute the native function, And executing the native code according to the interpreted instruction data.

The mobile device according to an embodiment of the present invention includes a web application that transmits a message including command data composed of only special characters and words to a broker in response to a request for execution of a native function, and the message including the command data from the broker. And a native component receiving, wherein the native component interprets the command data included in the received message to execute the native function, and executes a native code according to the interpreted command data.

A method and apparatus for executing a native function of a mobile device according to an embodiment of the present invention provides a broker for a message including command data consisting of only special characters and words or only special characters, images, and words in order to execute the native function. By transferring to, the developer can develop a hybrid mobile application by using the existing web page development language as it is, without spending time learning the specialized functions of the development tool.

In addition, a method and apparatus for executing a native function of a mobile device according to an embodiment of the present invention is a message including command data consisting of only special characters and words or only special characters, images, and words in order to execute the native function. By transmitting the data to the broker, even a person who is not a professional developer can easily develop a hybrid mobile application.

A detailed description of each drawing is provided in order to more fully understand the drawings cited in the detailed description of the present invention.
1 is a block diagram of a system for executing a native function of a mobile device according to an embodiment of the present invention.
2 shows embodiments of an interface shown in the web view shown in FIG. 1.
3 is a block diagram of a system for executing a camera function of a mobile device according to an embodiment of the present invention.
4 is a block diagram of a system for executing a GPS function of a mobile device according to an embodiment of the present invention.
5 is a flowchart illustrating a method for executing a native function of a mobile device according to an embodiment of the present invention.
6 is a flowchart illustrating a method for executing a native function of a mobile device according to another embodiment of the present invention.

Specific structural or functional descriptions of the embodiments according to the concept of the present invention disclosed in the present specification are exemplified only for the purpose of describing the embodiments according to the concept of the present invention, and the embodiments according to the concept of the present invention are It may be implemented in various forms and is not limited to the embodiments described herein.

Since the embodiments according to the concept of the present invention can apply various changes and have various forms, the embodiments will be illustrated in the drawings and described in detail in the present specification. However, this is not intended to limit the embodiments according to the concept of the present invention to specific disclosed forms, and includes all changes, equivalents, or substitutes included in the spirit and scope of the present invention.

Terms such as first or second may be used to describe various elements, but the elements should not be limited by the terms. The terms are only for the purpose of distinguishing one component from other components, for example, without departing from the scope of the rights according to the concept of the present invention, the first component may be referred to as the second component, and similarly The second component may also be referred to as a first component.

When a component is referred to as being "connected" or "connected" to another component, it is understood that it may be directly connected or connected to the other component, but other components may exist in the middle. Should be. On the other hand, when a component is referred to as being "directly connected" or "directly connected" to another component, it should be understood that there is no other component in the middle. Other expressions describing the relationship between components, such as "between" and "just between" or "adjacent to" and "directly adjacent to" should be interpreted as well.

The terms used in the present specification are only used to describe specific embodiments, and are not intended to limit the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In the present specification, terms such as "comprise" or "have" are intended to designate the presence of a set feature, number, step, action, component, part, or combination thereof, but one or more other features or numbers It is to be understood that the possibility of addition or presence of, steps, actions, components, parts, or combinations thereof is not preliminarily excluded.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which the present invention belongs. Terms as defined in a commonly used dictionary should be interpreted as having a meaning consistent with the meaning in the context of the related technology, and should not be interpreted as an ideal or excessively formal meaning unless explicitly defined in this specification. Does not.

Hereinafter, the present invention will be described in detail by describing a preferred embodiment of the present invention with reference to the accompanying drawings.

1 is a block diagram of a system for executing a native function of a mobile device according to an embodiment of the present invention.

Referring to FIG. 1, the system 100 includes a mobile device 10, a web server 30, and a broker 40. The mobile device 10 refers to a smart phone, a tablet PC, or a mobile electronic product. The mobile device 10 includes a camera 11, a Global Positioning System (GPS) 13, and Near Field Communication (NFC) 15. In the present invention, the mobile device 10 includes the camera 11, the GPS 13, and the NFC 15, but is not limited thereto. Depending on the embodiment, the mobile device 10 may include other external hardware.

The camera 11 is implemented in the mobile device 10 and refers to a component including hardware capable of implementing a function to take a picture. The GPS 13 is implemented in the mobile device 10 and refers to a component including hardware capable of implementing a function capable of notifying the current location of the mobile device 10. NFC 15 refers to a component including hardware capable of performing short-range wireless communication.

It is assumed that the mobile app installed on the mobile device 10 is implemented as a hybrid mobile application. In this specification, a web application (21) means a mobile app. Therefore, the term web application will be used instead of the term mobile app.

When the web application 21 installed in the mobile device 10 is implemented as a hybrid mobile application, the mobile device 10 includes a native component 17 and a web view 19.

The native component 17 includes native code for executing the functions of the hardware of the mobile device 10. Depending on the embodiment, the native component 17 may be called differently (eg, native).

In this specification, the native function refers to a function of the hardware (eg, camera 11, GPS 13, or NFC 15) of the mobile device 10 (eg, an operation of taking a picture using the camera 11, GPS (13) is used to determine the current location, and NFC (15) is used to perform short-range wireless communication). Detailed operations of the native component 17 will be described in detail later.

The web view 19 refers to a browser implemented in the web application 21 implemented as a hybrid mobile application.

The web application 21 may be generated using web technologies (eg, HTML, JavaScript, CSS, etc.).

The web application 21 may transmit a message including command data composed of only special characters and words to the broker 40 in response to a request for execution of a native function. The native function execution request means a web view in order for the user of the mobile device 10 to execute a function of hardware (eg, camera 11, GPS 13, or NFC 15) implemented in the mobile device 10 In (19), it refers to the act of clicking on a specific word, a specific icon, or a combination thereof. For example, the user may perform an operation requesting execution of a native function by clicking the word “camera” implemented in the web view 19 to take a picture using the camera 11 of the mobile device 10.

Since the web application 21 cannot directly cause the hardware of the mobile device 10 to perform a native function, it transmits a message including command data to perform the native function to the broker 40. The command data may be implemented only with special characters and words. Special characters may be "!, @, #, $, %, ^, &, *, or {{, }}". The word can be freely decided by the developer. For example, when the native function is an operation of turning on the camera 11, the command data may be implemented as "{{camera}}". Alternatively, the command data may be "{{taking a picture}}" or "{{Camera}}". That is, words in the command data can be arbitrarily written by the developer, so that the developer can easily implement a native function without learning the JavaScript API.

Although defined herein as command data, command data may be referred to as other terms according to embodiments. The web view 19 cannot directly execute the native function.

The broker 40 is used for MQTT (Message Queuing Telemetry Transport), which is a publish-subscribe-based message protocol, and is a separate device distinguished from the mobile device 10 and the web server 30 to be.

The native component 17 receives the message including the command data from the broker 40. Native component 17 interprets the command data contained in the received message to execute the native function. In other words, the native component 17 interprets the instruction data to be an instruction to execute what operation. Specifically, the native component 17 performs an extraction operation for extracting words between special characters, and a determination operation for determining whether the extracted word is related to a word stored in a database (not shown). The operation of interpreting the command data includes the extraction operation and the determination operation. The native component 17 executes a native code corresponding to a word in the database related to the extracted word. For example, when the command data is "{{take a picture}}", the native component 17 extracts the "take a picture" between special characters, and the extracted "take a picture" is a word stored in the database, "Camera. It is determined whether it is related to "On", and executes the native code corresponding to the word "Camera On" in the database related to the extracted word "taking a picture". The database stores native codes and words corresponding to the native codes in the form of a table. In addition, words corresponding to the native codes stored in the database are related to words extracted from the native component 17. The relationship means that the extracted word and the word stored in the database correspond to each other. For example, when a word corresponding to the native codes stored in the database is "Camera On", "Camera On" is a word that can be extracted from the native component 17, "Camera", "Taking a picture", or " It is assumed that they are related by appointment in advance, such as "taking a picture", or they correspond to each other. That is, words that can be extracted from the native component 17, native codes, and words corresponding to the native codes are stored in the form of a table.

Words that can be extracted from the native component 17, "camera", "take a picture", or "take a picture" are words that can be arbitrarily written by a developer.

According to an embodiment, the native component 17 may perform an extraction operation for extracting words between special characters, and may perform an inference operation for inferring an intention of a word written by a developer using a part of the extracted words. The operation of interpreting the command data includes the extraction operation and the inference operation. For example, when the command data is "{{landscape shooting}}", the native component 17 extracts the word "landscape shooting" between special characters, and uses the extracted word to extract a word stored in the database. As it relates to "Camera On", the intention of the word "landscape photography" can be deduced. Both the word stored in the database (eg, “Camera On”) and the word to be written by the developer (eg, “Landscape”) cannot be associated by appointment in advance. That is, all of the words to be written by the developer cannot be stored in the form of words and tables stored in the database. This is because the words to be written by the developer can vary. In this case, it is difficult to determine whether the word written by the developer is related to the word stored in the database. There is no word stored in the database associated with the extracted word “landscape shooting”, but the intention of the word can be inferred by using a part of the word “shooting” from the extracted word “landscape shooting.” , Words corresponding to the native codes are stored in the form of a table In addition, some of the words extracted from the native component 17 are related to words corresponding to the native codes stored in the database. Some of the words extracted from the component 17 correspond to words corresponding to the native codes stored in the database.

Inference means that the word "shooting", which is a word extracted from the word "landscape shooting", is determined to be related (or correspond to each other) with the word "Camera On" stored in the database corresponding to the native code. Means to do. After inferring the intention of the word to be related to “Camera On”, the native component 17 executes the native code corresponding to “Camera On”. When the native code is executed, the native function of turning on the camera 11 is executed.

According to another embodiment, the native component 17 may perform an extraction operation for extracting words between special characters, analyze phrases displayed on the web view 19, and execute an inference operation for inferring the intention of the word written by the developer. have. Inference means determining that the word extracted by the extraction operation is related to the word stored in the database. That is, the reasoning operation means determining whether a word extracted by the extraction operation corresponds to a word stored in the database.

For example, when the command data is “{{photo}}”, the native component 17 extracts the word “photo” between special characters, and the phrase displayed on the web view 19 is “take a photo with a camera and take a photo. When there is a phrase "make your photos beautiful", the native component 17 can infer the intention of the word "photo" as being related to the word "Camera On" stored in the database for the extracted word "photo". I can. That is, when a specific word (eg, camera) is searched for more than a certain word in the web view 19, the native component 17 is related to the word “Camera On” stored in the database for the extracted word “photo”. You can deduce the intention of the word “photo” from (or correspond to each other).

On the other hand, when the phrase displayed on the web view 19 is “Please decorate your photos beautifully using photos stored in the photo album”, a specific word (eg, a photo book or gallery) in the web view 19 is more than a certain word. Count whether it is searched. When the counted specific word is searched for more than a certain word, the native component 17 refers to the extracted word “photo” as “Pickup Photo”, which is a word stored in the database (or corresponds to each other). The intention of the word “photo” can be deduced. After inferring the intention of the word as something related to (or corresponding to each other) “Pickup Photo”, the native component 17 Run the code. When the native code is executed, a native function for loading an image stored in a storage space (not shown) of the mobile device 10 is executed.

According to an embodiment, when a specific word (eg, a camera) is searched for less than a certain word in the web view 19, the native component 17 is a word stored in the database for the extracted word “photo”, “Pickup Photo”. The intention of the word “photo” can be deduced from things that are related to (or correspond to each other).

According to another embodiment, the native component 17 performs an extraction operation for extracting words between special characters, and an inference operation for inferring the intention of the word written by the developer by analyzing the extracted word order. Can run. Inference means determining that the word extracted by the extraction operation is related to the word stored in the database. That is, the reasoning operation means determining whether a word extracted by the extraction operation corresponds to a word stored in the database.

For example, when the word written by the developer is "taking a picture or a picture taken", the intention of the extracted word may be inferred based on the word "photo" based on whether there is a word in front or a word in the back. When another word exists in front of the word “photo”, the native component 17 may infer the intention of the word as something related (or corresponding to each other) with “Pickup Photo”, which is a word stored in the database. When another word exists after the word “photo”, the native component 17 may infer the intention of the word “photo” as something related to (or correspond to each other) “Camera On”. After inferring the intention of the word as something related to (or corresponding to) "Camera On", the native component 17 executes the native code corresponding to "Camera On".

According to an embodiment, the command data may be implemented only with special characters, images, and words. For example, the command data may be "{{ <img src='/native/camera/image.a.jpeg'> take a picture}}".

2 shows embodiments of an interface shown in the web view shown in FIG. 1.

Referring to FIGS. 1 and 2, various words and images (or icons) may be used in the web view 19 as in FIG. 2 to execute a native function. That is, even if the word "photo" is used in the web view 19, whether the intention is to turn on the camera or to load a picture stored in the mobile device 10 depends on the image used. When the command data is implemented only with special characters, images, and words, the native component 17 performs an extraction operation of extracting words and images between special characters, a read operation of reading the extracted image, and the extraction An inference operation for inferring the intention of the word may be performed by analyzing the resultant word and the read image. The operation of interpreting the command data includes the extraction operation, the read operation, and the inference operation. Inference means determining that the word extracted by the extraction operation is related to the word stored in the database. That is, the reasoning operation means determining whether a word extracted by the extraction operation corresponds to a word stored in the database.

For example, when the command data is "{{<img src='/native/camera/image.a.jpeg'> photo}}", the native component 17 includes words between special characters ("photo") and An extraction operation to extract an image (<img src='/native/camera/image.a.jpeg'>") is executed. The native component 17 is the extracted image ("<img src='/native/camera). /image.a.jpeg'>") is read. For example, as shown in Fig. 2, the extracted word is "photo", and the extracted image may be various. The native component 17 is described above. By analyzing the extracted word ("photo") and the read image ("<img src='/native/camera/image.a.jpeg'>"), it is possible to perform an inference operation to infer the intention of the word. 2A or 2B, when the word is "photo", the image contains a square or heptagon, and contains a circle, or an ellipse within the square, or heptagon, the native component 17 is stored in the database. The intention of the word “photo” can be deduced from something related to (or corresponding to) the word “Camera On.” After inferring the intention of the word to be related to “Camera On,” the native component ( 17) executes the native code corresponding to "Camera On".

On the other hand, as in FIG. 2C or 2D, when the word is “photo”, the image includes a rectangle, and does not include a circle or an ellipse in the rectangle, or includes a shape other than a circle or an ellipse, the native The component 17 may infer the intention of the word as being related to (or corresponding to each other) "Pickup Photo". After inferring the intention of the word as being related to "Pickup Photo", the native component 17 ) Executes the native code corresponding to "Pickup Photo".

The native component 17 executes native code according to the interpreted instruction data, and executes the native function according to the executed native code.

By implementing command data only with special characters and words, or only special characters, images, and words, the developer of the web application 21 does not need to spend time learning the specialized functions of the development tool, (Eg, HTML, JavaScript, CSS, etc.) can be used as it is to develop the web application 21.

The web server 30 is a computer system that processes requests through HTTP. The web server 30 receives output information obtained according to the execution of the native function. For example, the web server 30 receives photo information obtained by the operation of the camera 11 or receives information on the current location of the mobile device 10 obtained by the operation of the GPS 13.

3 is a block diagram of a system for executing a camera function of a mobile device according to an embodiment of the present invention.

Referring to FIG. 3, ① the user clicks the word "camera" implemented in the web view 19 to take a picture using the camera 11 of the mobile device 10 to perform an execution request operation of the native function. The web application 21 may promise in advance to transmit a message including command data composed of only special characters and words to the broker 40 in response to a request for execution of a native function. For example, when the command data is "{{camera}}", the web application 21 transmits a message including the command data to the broker 40.

The web application 21 calls and operates a PHP program through asynchronous communication, and the PHP program delivers a message including command data to the broker 40 through socket communication.

② The broker 40 transmits the message including the command data to the native component 17.

(3) The native component 17 interprets the received instruction data to execute the native function, and executes the native code according to the interpreted instruction data. A photo file is generated by the camera 11 according to the executed native code.

④ The native component 17 may transmit the photo file to the web server 30.

⑤ The native component 17 may call back the information of the photo file to the web application 21 through the web view 19. The information of the photo file includes the format, size, resolution, and creation date of the photo file.

⑥ The web application 21 may transmit the information of the photo file to the web server 30 for storage in the web server 30.

4 is a block diagram of a system for executing a GPS function of a mobile device according to an embodiment of the present invention.

Referring to FIG. 4, ① a user clicks the word GPS implemented in the web application 21 to know the current location of the mobile device 10 using the GPS 13 of the mobile device 10 to execute the native function. Perform the requested action. The web application 21 may transmit a message including command data composed of only special characters and words to the broker 40 in response to a request for execution of a native function. For example, the command data may be "{{GPS}}".

② The broker 40 transmits the message including the command data to the native component 17.

(3) The native component 17 interprets the instruction data to execute the native function, and executes the native code according to the interpreted instruction data. Information of the current location is generated by the GPS 13 according to the executed native code.

④ The native component 17 may transmit the information of the current location to the web server 30 for storage in the web server 30.

5 is a flowchart illustrating a method for executing a native function of a mobile device according to an embodiment of the present invention.

1 and 5, in response to a request for executing a native function, the web application 19 sends a message including command data consisting of only special characters and words, or only special characters, images, and words, to the broker 40 It is transmitted to (S100).

The native component 17 receives the message including the command data from the broker 40 (S200).

The native component 17 interprets the command data included in the received message to execute the native function, and executes a native code according to the interpreted command data (S300).

6 is a flowchart illustrating a method for executing a native function of a mobile device according to another embodiment of the present invention.

Referring to FIGS. 1 to 3 and 6, according to an embodiment, the web application 21 may be implemented to display content of other web sites such as advertisements on the web view 19. That is, the web view 19 may display not only the content of the web application 21 but also the content of other web sites such as advertisements. The other website refers to a website implemented by a third party, not a developer implementing the web application 21.

The other websites may also be implemented to execute native functions. That is, the user of the mobile device 10 clicks a specific word, a specific icon, or a combination of the other website displayed on the web view 19, and the camera 11, the GPS 13, and the mobile device 10 Alternatively, an operation requesting execution of the function of the NFC 15 may be performed.

At this time, since the other website is not a developer who implemented the web application 21, it is difficult to trust. For example, by clicking on a specific word, a specific icon, or a combination thereof displayed on the other website, a contact information implemented in the mobile device 10 may be hacked.

In order to prevent hacking of the mobile device 10 due to the execution of the native function of the other website, the following method may be proposed.

When there is a request to execute a native function implemented on a website of a third party other than the developer rather than a native function implemented by the developer of the web application 21, the web application 21 first sets an arbitrary value to the flag value. It checks whether it is set (S10000). The website of the third party is a website implemented by a third party, not the developer who implemented the web application 21, so that the contents of the website of the third party are displayed in the web view 19 by the web application 21. It means the implemented site.

When an arbitrary value is set for the flag value, the web application 21 may allow the native component 17 to execute a native function implemented in the third party's website. The native component 17 executes a native function implemented in the third party's website (S50000).

According to an embodiment, when there is a request to execute a native function implemented on a website of a third party other than the developer, not a native function implemented by the developer of the web application 21, the web application 21 You can count the average number of visits to your website. In addition, according to an embodiment, when an arbitrary value is not set for the flag value, the web application 21 may count the average number of visits to the website of the third party (S20000). The average number of visits may be an average number of visits per day, an average number of visits per week, an average number of visits per month, or an average number of visits per year. The content of the third party's website may be an advertisement displayed on the web view 19.

The web application 21 compares whether the counted average number of visits exceeds a predetermined value (S30000). The predetermined value may be arbitrarily set. When the counted average number of visits exceeds the predetermined value, the third party's website can be trusted as a site visited by many people.

In addition, when the counted average number of visits exceeds the predetermined value, the web application 21 may allow the native component 17 to execute a native function implemented in the third party's website. The native component 17 executes a native function implemented in the third party's website (S50000).

According to an embodiment, the web application 21 allows the native component 17 to execute a native function on the third party's website, then sets an arbitrary value as a flag value, and the flag value set as the arbitrary value. Can be saved. According to an embodiment, the flag value set to the arbitrary value is copied to the native component 17 and the native component 17 may also store the flag value.

After executing the native function implemented on the third party's website, when the user of the mobile device 10 requests again to execute the native function implemented on the third party's website, the web application 21 displays the flag Without counting the average number of visits to the website of the third party according to the arbitrary value set in the value, the native component 17 may immediately allow the native component 17 to execute a native function implemented in the website of the third party. This is because the web application 21 has already determined that the web site of the third party is trusted. Due to the setting of the flag value, the operation of counting the average number of visits to the website of the third party can be omitted, thereby improving the speed of the native function.

According to an embodiment, after executing the native function implemented on the third party's website, when the user of the mobile device 10 requests again to execute the native function implemented on the third party's website, the web application 21 ) Compares the flag value set as the arbitrary value stored in the web application 21 with the flag value set as the arbitrary value stored in the native component 17, and only when both values match, the native component 17 You can allow third-party websites to run native functions implemented. This is because the arbitrary value stored in the web application 21 may be changed by hacking.

When the counted average number of visits does not exceed a predetermined value, the web application 21 includes a first register value corresponding to the website stored in the web application 21 and the website stored in the native component 17 The corresponding second register values are compared with each other (S40000).

The web application 21 receives a list of trusted sites, sets a random number as the first register value for the trusted sites, and transmits the first register value to the native component 17. The native component 17 stores the first register value as the second register value. The list of trusted sites may be updated periodically.

When the first register value and the second register value coincide with each other, the web application 21 may allow the native component 17 to execute a native function implemented in the third party's website. The native component 17 executes a native function implemented in the third party's website (S50000). The first register value may be hacked, but the second register value cannot be hacked as a value stored in the native component 17. For example, a hacker may change the value of the first register to make it appear as a trusted site, but the hacking can be prevented by comparing the value of the first register and the value of the second register.

According to an embodiment, when the first register value and the second register value coincide with each other, the web application 21 allows the native component 17 to execute the native function implemented in the third party's website. , The web application 21 may set an arbitrary value as the flag value, and a flag value in which an arbitrary value is set may be stored. According to an exemplary embodiment, the flag value in which the arbitrary value is set is copied to the native component 17 so that the native component 17 may also store the flag value.

After executing the native function implemented on the third party's website, when the user of the mobile device 10 requests again to execute the native function implemented on the third party's website, the web application 21 displays the flag The first register value and the second register value are not compared with each other according to the arbitrary value set in the value, and the native component 17 immediately allows the native component 17 to execute the native function implemented in the third party's website.

This is because the web application 21 has already determined that the website of the third party is trusted by comparing the first register value with the second register value. Due to the setting of the flag value, the operation of counting the average number of visits to the website of the third party and the comparison operation of the first register value and the second register value for the website of the third party can be omitted. There is an effect that can improve the speed of native functions.

According to an embodiment, after executing the native function implemented on the third party's website, when the user of the mobile device 10 requests again to execute the native function implemented on the third party's website, the web application 21 ) Compares the flag value set as the arbitrary value stored in the web application 21 with the flag value set as the arbitrary value stored in the native component 17, and only when both values match, the native component 17 You can allow third-party websites to run native functions implemented. This is because the arbitrary value stored in the web application 21 may be changed by hacking.

When the first register value and the second register value do not match each other, the web application 21 prevents the native component 17 from executing the native function implemented in the third party's website (S60000). Therefore, security can be enhanced by allowing native functions to be performed only for websites of trusted third parties.

Although the present invention has been described with reference to the exemplary embodiment shown in the drawings, this is only exemplary, and those of ordinary skill in the art will appreciate that various modifications and other equivalent embodiments are possible therefrom. Therefore, the true technical protection scope of the present invention should be determined by the technical idea of the attached registration claims.

100: system; 17: native components;
10: moving device; 19; Web view;
11: camera; 21; Web application;
13; GPS; 30: web server;
15: NFC; 40: broker;

Claims (2)

In response to a request for executing a native function, the web application transmits a message including command data composed of only special characters and words to the broker;
Receiving, by a native component, the message including the command data from the broker; And
The native component includes the step of interpreting the command data included in the received message to execute the native function, and executing a native code according to the interpreted command data,
The operation of interpreting the command data,
Performing an extraction operation of extracting the word between the special characters; And
A method for executing a native function of a mobile device using a broker, comprising the step of executing an inference operation for inferring an intention of a word written by a developer using a part of the extracted word. A web application that transmits a message including command data composed of only special characters and words to a broker in response to a request for execution of a native function; And
Including a native component that receives the message including the command data from the broker,
The native component,
Interpret the command data included in the received message to execute the native function, execute a native code according to the interpreted command data,
The operation of interpreting the command data,
An extraction operation for extracting the word between the special characters is performed,
A mobile device indicating that a developer infers an intention of a written word by using a part of the extracted word.

Images