JP3863122B2 - Wireless terminal, communication control program, and communication control method - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a wireless terminal, a communication control program, and a communication control method including a proximity communication unit that performs communication in a relatively narrow range such as Bluetooth (registered trademark), and in particular, performs communication with a proximity communication unit according to an application program. Regarding technology.
[0002]
[Prior art]
Recently, short-range wireless communication with a transmission distance of about 10 m has attracted attention. While the effective transmission distance range of the conventional wireless LAN is 100 m or more, the short-range wireless communication uses a small amount of power because the transmission range is narrow, so a portable information processing device such as a mobile phone or a PDA ( This is suitable for a communication device having a limited battery such as a portable terminal hereinafter.
[0003]
Bluetooth is one of this kind of short-range wireless communication, and in recent years, mobile terminals equipped with this Bluetooth communication means have begun to spread (see Non-Patent Documents 1 to 4).
[0004]
Since Bluetooth has a low device unit price and can be miniaturized, it is expected that devices with Bluetooth communication functions will be widely used in the future. As Bluetooth spreads, it will be possible to receive services and information according to each location at any location.
[0005]
For example, in convenience stores, supermarkets, retail stores, etc., it is possible to provide services for buyers such as electronic coupon service, electronic point service, electronic payment, receipt and receipt issuance. Applications are also expected for gate opening and closing control using electronic tickets, payment and discount services at vending machines, payment of charges at parking lots, gas stations and drive-throughs. In addition, access to the Internet, information distribution depending on a specific location, provision of user location information, and the like are also possible.
[0006]
In addition, recent mobile phones are equipped with operating systems (OS) such as ITRON (registered trademark), Symbian (registered trademark), and Linux (registered trademark), and operate virtual machines on these OSs. There is an environment in which the same application can be executed on the terminal.
[0007]
A JAVA (registered trademark) virtual machine is one implementation. A JAVA application operating on JAVA is downloaded from a specific server on the Internet using a data communication function of the mobile phone and stored in a storage device inside the mobile phone. At that time, a JAD (Java Application Descriptor) file describing information attached to the JAVA application is also downloaded and stored in the storage device.
[0008]
When the user instructs the mobile phone to start the application, the OS starts up the JAVA virtual machine and operates the specified application on the JAVA virtual machine. Also, when starting a virtual machine, the resources that can be used by the virtual machine are set or restricted based on the information in the JAD file associated with the application.
[0009]
In this type of virtual machine standard, there is a core standard called CLDC and a standard called MIDP that defines communication and user interfaces. MIDP verifies the Ver2 standard, and when downloading a JAVA application, verifies the digital signature attached to the application, determines whether the application is reliable, and uses the hardware resources that the application can use And class constraints can be set.
[0010]
In addition, the establishment of the standard JSR82 that enables the use of Bluetooth functions from JAVA virtual machines has made it possible for JAVA applications to partially use Bluetooth communication functions through Bluetooth class methods. The JAVA virtual machine security policy prohibits or restricts JAVA applications from directly controlling mobile phone hardware, which limits the available Bluetooth functions.
[0011]
JSR82 partially relaxes the above functional restrictions by defining settings related to hardware through an entity called BCC (Bluetooth Control Center) that is different from the JAVA application. The specification describes a form that an OS native application plays as one of the implementation forms of BCC.
[0012]
[Non-Patent Document 1]
J2METM Connected, Limited Device Configuration
http://jcp.org/en/jsr/detail?id=30
[Non-Patent Document 2]
Mobile Information Device Profile for the J2METM Platform
http://jcp.org/en/jsr/detail?id=37
[Non-Patent Document 3]
JavaTM APIs for Bluetooth
http://jcp.org/en/jsr/detail?id=82
[Non-Patent Document 4]
Mobile Information Device Profile 2.0
(http://jcp.org/en/jsr/detail?id=118)
[0013]
[Problems to be solved by the invention]
Settings made through BCC are stored in a non-volatile memory or the like. When a JAVA virtual machine calls a Bluetooth method from a JAVA application, the JAVA virtual machine determines whether or not the process can be executed by looking at a set value. For example, when the Bluetooth communication function is turned off in BCC and the JAVA application is started and the JAVA application tries to execute the terminal discovery command, the BCC setting is set to OFF for the Bluetooth function. The return value of the command is an error.
[0014]
Also, if the JAVA application tries to execute an authentication command in the situation where the security function is turned off in BCC, the return value of this command will similarly become an error.
[0015]
In this case, the user terminates the JAVA application, starts BCC, changes the setting value, and starts the JAVA application again. Alternatively, as another implementation, when a command is requested, the JAVA virtual machine or the OS automatically starts BCC, or presents a dialog for changing the setting to change the setting managed by BCC. There may be a way to explicitly encourage users to change.
[0016]
Further, when the authentication mode is set in the BCC, the authentication procedure is executed when a connection request is made to the counterpart device or when the connection request is accepted. The authentication request event is received as a normal HCI event by the HCI task, and a JAVA virtual machine task or a dialog prompting the OS to input the authentication key is displayed on the screen, and the user's explicit key input (usually PIN code) Request data input to create a key for authentication).
[0017]
However, it has been pointed out that short PIN codes have security problems, and an ideal PIN code length of 128 bits is required. However, 128-bit code length requires input of 32 alphanumeric characters. The burden required for user input is very large. If an input mistake is made at this time, both terminal authentications fail and connection cannot be made, and it is necessary to execute the connection procedure again and enter the PIN code correctly.
[0018]
In addition, when a specific service is provided to another device, or when a specific service is received from another device, the Bluetooth device setting appropriate to the situation in which the service is used is set to the processing time. It is necessary from the viewpoint of usability.
[0019]
For example, when a mobile phone owned by a customer and a cash register are connected via Bluetooth to make a financial settlement, it is desirable to set a narrow communication range for security.
[0020]
However, in the current JSR82 specification, such a change of communication range cannot be set. Although a method of setting through BCC is also conceivable, it is very troublesome for the user to explicitly start the BCC before starting the application and to make settings appropriate for the application to be used. In addition, if you forget to return to the original setting after the application ends, there is a possibility that problems such as poor connection will occur when you receive a different service next time.
[0021]
When performing Bluetooth processing from a JAVA application, in addition to the Bluetooth processing time, overhead such as the startup of the JAVA virtual machine and the startup time of the JAVA application occurs, so the processing wait time of the user becomes long.
[0022]
The present invention has been made in view of such a point, and an object of the present invention is to permit the communication of the proximity communication means only when the application receiving the service is reliable, and to reduce the troublesome communication setting of the proximity communication means. An object of the present invention is to provide a wireless terminal, a communication control program, and a communication control method that can reduce the processing time until receiving a service.
[0023]
[Means for Solving the Problems]
According to one aspect of the present invention, first communication means capable of receiving an application program including attached information;
Trust verification means for verifying whether or not the application program is reliable based on the attached information;
A second communication unit that is used by the application program and that is provided separately from the first communication unit and has a narrower communication range than the first communication unit;
Communication for performing communication setting of the second communication unit according to information necessary for communication by the second communication unit included in the attached information when executing the application program verified to be reliable by the trust verification unit Setting means;
After the communication setting unit performs communication setting on the second communication unit, a start start unit that starts the application program, and
Information necessary for communication by the second communication means includes start-up search of communication partner, authentication mode, link key, PIN code, transmission power, page timeout, supervision timeout, page scan interval, inquiry scan interval, etc. There is provided a wireless terminal characterized by including at least one of application exclusion, effective communication distance, packet type, class of device, inquiry access code, and channel number.
[0024]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, a wireless terminal according to the present invention will be specifically described with reference to the drawings. Hereinafter, a wireless terminal having a Bluetooth communication function will be described as an example of the wireless terminal according to the present invention. The wireless terminal according to the present embodiment establishes a connection with a service providing apparatus having a Bluetooth function, which is a communication partner, using a method conforming to the specification of Bluetooth. Can be provided.
[0025]
The wireless terminal of this embodiment is, for example, a mobile phone or a PDA, and the service providing device is, for example, a cash register, an automatic ticket gate, a vending machine, an information providing device, or the like. A case where a cash register is used as a service providing apparatus will be described.
[0026]
(First embodiment)
FIG. 1 is a block diagram showing an example of the internal configuration of a mobile phone which is an embodiment of a wireless terminal according to the present invention. The mobile phone shown in FIG. 1 stores a CPU 2 connected to the internal bus 1 for executing a predetermined program, a mobile phone control program, a ROM 3 for storing originally built-in programs and dictionary data, and temporary variables and data. Memory 4, EEPROM 5 for storing personal registration information, electronic coupons, downloaded programs, program management data, etc., A / D 7 for converting audio signals to digital signals with microphone 6, and converting digital signals to audio signals D / A 9 output to the speaker 8, the eccentric motor 10 that vibrates the housing, the communication unit 12 that communicates with the base station 11, the display unit 13 that displays various information, and the telephone number and characters are input. A key input unit 14 for selecting, a selection instruction unit 15 for selecting a menu, and the like, and a Bluetooth module 16 (hereinafter referred to as a BT module).
[0027]
For example, the BT module 16 has a function of establishing a wireless communication path with a cash register and receiving a service provided from the cash register. The operation of the BT module 16 conforms to the Bluetooth specification.
[0028]
An interface unit 17 compliant with the UART interface for connecting the BT module 16 to the internal bus 1 is provided between the BT module 16 and the internal bus 1. The interface unit 17 communicates with the BT module 16 using a UART communication method.
[0029]
Alternatively, the format of the external interface of the BT module 16 may be matched with the signal format of the internal bus 1. Alternatively, instead of the BT module 16, a Bluetooth RF module (not shown) is connected to the internal bus 1, and the CPU 2 executes the function provided by the baseband module for link management as a program. It is also conceivable to provide a configuration.
[0030]
A method of giving a command to the BT module 16 and a method of receiving an event from the BT module 16 are realized in a form according to an HCI (Host Controller Interface) described in the Bluetooth specification. Alternatively, there may be a method using a communication protocol unique to the baseband.
[0031]
The configuration related to the voice call is the same as that of a conventional mobile phone. For example, the communication unit 12 performs position registration with the base station 11 and performs call control at the time of outgoing / incoming calls to transmit / receive data, When communication is completed, disconnect call control is performed, and during communication, handover or the like is performed.
[0032]
When the communication unit 12 receives a connection request from the base station 11, the communication unit 12 outputs a ringing tone from the speaker 8 or drives the eccentric motor to vibrate the casing of the mobile phone. Call the attention of the user who is the owner of After the user responds with an acknowledgment of connection, the line connection is established between the mobile phone and the cash register to start communication.
[0033]
At the time of communication, the mobile phone converts the sound input from the microphone 6 from an analog signal to a digital signal by the A / D 7, compresses the digital data under the control of the CPU 2, and closes the base station through the communication unit 12. Transmit to station 11. The signal received by the communication unit 12 is decompressed and returned to the original signal under the control of the CPU 2 and then converted from a digital signal to an analog signal by the D / A 9 to be output from the speaker 8. Is output from.
[0034]
The function in which the mobile phone of FIG. 1 receives service provision from the cash register 1 is usually realized by an application program. In recent years, a technology has been widely used in which a JAVA virtual machine is executed in a mobile phone, a JAVA application acquired through a public network is stored in a storage device of the mobile phone, and the JAVA application is executed on the JAVA virtual machine. This embodiment will be described using this technique. JAM (Java Application Manager) downloads JAD (JAVA Application Descriptor) files that describe application attributes, downloads JAVA applications, records downloaded programs to EEPROM 5, and records program management data as shown in Fig. 8 Management of starting up and deleting recorded applications. JAM is an OS-native application and assigns OS resources according to the contents described in the program management data at startup.
[0035]
The memory space called the scratchpad that stores the JAVA application of the mobile phone and the data of the JAVA application is managed differently from the normal memory space and cannot be accessed from other applications. . This protects data from unauthorized applications and ensures security.
[0036]
Also, the API (Application Program Interface) for controlling Bluetooth from the JAVA virtual machine is defined as JSR-82, and the JAVA application sends a command to the BT module 16 through the API provided by the JAVA virtual machine. Events are received through the JAVA virtual machine and called back to the registered function.
[0037]
FIG. 2 is a block diagram of modules necessary for the JAVA application to use the Bluetooth function. In this embodiment, an example in which ITRON is used as an OS of a mobile phone will be described. Each block in FIG. 2 is managed as a task, activated as a task when the mobile phone is turned on, and waits until called from the OS. Each task is processed by exchanging messages via the OS. The HCI task 21 sets a value instructed by a higher-level protocol or BCC in the BT module 16, or reads a value currently set in the BT module 16 of a specified item and controls a link. Request execution of the command.
[0038]
A command from the JAVA application 22 is called from a method of an instance of a Bluetooth class or an OBEX class 23 specified in JSR82, and a core of a KVM 24 that extends a virtual machine task 24 called KVM compliant with CLDC for Bluetooth. There are two cases: when called from an instance of a class. The former is used to establish an ACL link and instructs the inquiry command to start discovery of surrounding communicable terminals, the latter is a protocol specified as an argument, and sets up a connection with a device having a specific Bluetooth address. Used when sending and receiving data through the set connection.
[0039]
As described above, the BT module 16 performs near field communication by a method according to the Bluetooth specification. The portable BT module 16 uses CLASS3 with a communication distance of about 10 m in consideration of power consumption. The HCI task 21 communicates with the BT module 16 across a hardware abstraction layer (HAL) that absorbs the difference in OS, but the description thereof is omitted in this embodiment.
[0040]
The HCI task 21 converts commands and data from the L2CAP task 25, the Bluetooh / OBEX task 23, the BCC task 26, etc. into HCI commands and transmits them to the BT module 16. Also, the event and data received from the BT module 16 are passed to the L2CAP task 25, the Bluetooh / OBEX task 23, and the BCC task 26. Further, the data is divided in consideration of the buffer size of the BT module 16, and the process of combining the divided data is performed according to the capacity of the reception buffer of the HCI task 21.
[0041]
The L2CAP task 25, the RFCOM task 27, and the GOE task P28 are called stacks and provide functions in accordance with Bluetooth specifications. The Bluetooh / OBEX task 23 provides an API so that the JAVA application 22 can use the function defined in JSR82, and changes the command instructed to the API into a form suitable for the API provided by the Bluetooth stack.
[0042]
In addition, since the API of Bluetooh / OBEX task 23 is more abstract than the functions provided by the Bluetooth stack, it is necessary to control the functions provided by the stack in Bluetooh / OBEX task 23. Perform proper processing.
[0043]
For example, in the OBEX specification stipulated by JSR82, 4M size data can be sent and received, but the transferable data amount determined by the OBEX specification is 32K bytes, so the data in the Bluetooh / OBEX task 23 Is divided into 32K size and the OBEX PUT command is repeated as many times as necessary. Alternatively, when data is received, it has a function of concatenating a plurality of packets into a form that can be accessed by the JAVA application 22 as one data.
[0044]
The communication unit 12 in FIG. 1 not only performs a voice call with the base station 11, but also realizes data communication. As shown in FIG. 3, the communication unit 12 in the mobile phone 20 sets up a dedicated communication link with the base station 11, and exchanges IP packet data or a subset thereof using the link. The base station 11 is connected to a device having the function of the gateway 41 and transmits the received IP packet to the Internet network 42, and the communication unit 12 of the mobile phone 20 transmits it from the Web server 43 through the Internet 42. The incoming packet is received via the base station 11.
[0045]
With the above method, it is possible to exchange IP packets between the mobile phone 20 and the server 43 on the Internet 42. Further, by mounting the TCP protocol on the IP packet and the HTTP protocol on the IP packet, the application of the mobile phone 20 can transmit and receive data to and from a specific server 43 on the Internet 42.
[0046]
Since the MIDP 2.0 specification supports SSL (Secure Sockets Layer), the communication function of the mobile phone 20 can authenticate the identity of the server and can trust the server to which data is downloaded. Further, by verifying the electronic signature attached to the downloaded JAVA application 22, it can be confirmed that the application is created by a specific company that manages the server. Alternatively, it can be verified whether the application has been tampered with.
[0047]
FIG. 4 is a flowchart showing an application authentication procedure performed by the mobile phone 20. It is assumed that the public key of the root certificate authority is stored in the ROM 3 of the mobile phone 20. Prior to downloading the JAVA application 22, JAM downloads a JAD file in advance (step S1).
[0048]
FIG. 5 is a diagram showing an example of the structure of a JAD (JAVA Application Descriptor) file. As illustrated, the JAD file includes attribute data 44 of the JAVA application 22, an electronic certificate 45 of the company that created the JAVA application 22, and an electronic signature 46 of the JAVA application 22. More specifically, the attribute data 44 includes an application URL (Uniform Resource Locator), an application name, an application size, a configuration version to be used, a profile version to be used, a scratch pad size, as shown in FIG. It includes information such as whether the communication unit 12 is used, whether the BT module 16 is used, attribute data 44 of the BT module 16, a device management flag, and a startup search flag.
[0049]
Among these, the attribute data 44 of the BT module 16 is more specifically, as shown in FIG. 7, transmission power control, packet type, authentication mode, link key, PIN code, page timeout, supervision timeout, inquiry scan. It includes information such as interval, page scan interval, channel number, other application exclusion, effective communication distance, and anonymity mode.
[0050]
First, JAM determines whether it can be executed on its own terminal or stored based on attribute data 44 such as version information and program size (step S2 in FIG. 4). If execution is not possible, error processing is performed. If execution and storage are possible, JAM (Java Application Manager) obtains the root certificate authority identification number from JAD and obtains the public key of the root certificate authority from ROM 3 (step S3).
[0051]
Next, JAM creates a hash value of the company certificate 45 using a hash function such as MD5. Also, the electronic signature 46 of the JAVA application 22 is decrypted with the obtained public key of the root certificate authority. Then, the hash value created earlier and the combined value are compared (steps S4 and S5). If they do not match, error processing is performed, and if they match, it is determined that the electronic certificate 45 of the company in the JAD is correct, and the public key of the company that created the JAVA application 22 is acquired from the electronic certificate 45 of the company ( Step S6). Using the acquired public key, the electronic signature 46 of the JAVA application 22 included in the JAD file is acquired and decrypted (steps S7 and S8). Next, the JAVA application 22 is downloaded (step S9), and its hash value is created (step S10).
[0052]
Next, JAM downloads the JAVA application 22 and the JAR file including the resource data from the URL described in the attribute data 44 in the JAD file. During downloading, a hash value of the JAR file is created using a hash function such as MD5, and compared with the hash value decrypted earlier (steps S11 and S12). If the hash values match, the downloaded JAVA application 22 can definitely determine the application created by the company.
[0053]
If it is determined to be correct, a trust flag is set (step S13), management data including attribute data 44 as shown in FIG. 8 is created, saved in the JAVA application 22 EEPROM 5 (step S14), and saved successfully. It is confirmed whether or not (step S15). As shown in FIG. 8, the management data includes an application identifier, an application name, an application creation company name, application attribute data 44, a flag indicating trust, an attribute change flag, a device status change flag, an authentication status flag, and the like. . Management data is created for each application and stored in the EEPROM 5.
[0054]
Next, when the attribute of the downloaded application is checked and the BT module 16 is used, the application name and the created company name are presented to the user at the time of saving (step S16), and the BT module 16 is activated when the application is activated. Whether or not the setting is automatically changed is confirmed with the user (step S17), and if the user instructs to change the setting, a setting valid flag of the management data is set (step S18).
[0055]
On the other hand, if it is determined in step S12 that the JAVA application 22 is not reliable, it is confirmed whether or not the JAVA application 22 is stored in the EEPROM 5 (step S19). If not desired, the downloaded JAVA application 22 and management data are discarded.
[0056]
FIG. 9 is a diagram showing a sequence up to the start of data exchange by an application that receives a service that conforms to the specification of JSR82. When the JAVA application 22 receives a service reception instruction from the user, the JAVA application 22 calls an inquiry method to discover a device that provides the service (step S21). In the argument, an identifier called IAC (Inquiry Access code) for filtering the terminal is set. The Bluetooh / OBEX task 23 requests the HCI task 21 to start inquiry (step S22). The HCI task 21 instructs the BT module 16 to start inquiry (step S23). Thereby, the BT module 16 transmits an IQ packet in order to perform inquiry (step S24).
[0057]
When the BT module 16 discovers a new terminal by inquiry (receives an FHS packet) (step S25), the BT module 16 notifies the event to the HCI task 21 (step S26), and the HCI task 21 is a Bluetooh / OBEX task. A message is transmitted to 23 (step S27). The Bluetooh / OBEX task 23 transmits a message to the KVM task 24 (step S28), and the virtual machine task calls back a method registered by the application. The argument at the time of callback includes the BT module identifier of the discovered device and the COD (class of device) indicating the type of the discovered terminal.
[0058]
The application checks the acquired COD, and if it matches the desired COD, calls an inquiry cancel function (steps S29 to S33), and then acquires a remote name that is an easy-to-understand identification name for the user. A method is called (steps S34 to S41).
[0059]
Alternatively, in order to set up the upper protocol connection without obtaining the remote name, create an instance of the connector class and set up the connection by calling the OPEN method. The JAVA virtual machine blocks this function until a connection is established. In the specification of JSR82, L2CAP, RFCOM, SDP, and OBEX are supported as upper protocols.
[0060]
The JAVA application 22 creates an OBEX connector object in order to use the OBEX protocol. When this connector object OPEN request is made (step S42), the KVM 24 requests the HCI task 21 to connect the ACL link in order to create an ACL link (step S43). The HCI task 21 transmits a CreateConnection command to the BT module 16 (step S44).
[0061]
When the BT module 16 issues a link key request to the HCI stack (step S45), the HCI task 21 transmits a link key to the BT module 16 (step S46).
[0062]
When the connection of the connection is completed, the BT module 16 notifies the HCI task 21 of a ConnectionComplete event (step S47). The HCI task 21 notifies the KVM task 24 of an ACL creation event (step S48). The KVM 24 requests the L2CAP 25 task to create an L2CAP connection, and the L2CAP 25 task requests the HCI task 21 to transmit data (step S48). Thereafter, an RFCOM connection is created through the created L2CAP connection, and an OBEX connection is set through the RFCOM connection.
[0063]
Until the OBEX connection is made, the KVM 24 blocks the connector OPEN function, and the success or failure is set as the return value of the OBEX connection request.
[0064]
With the above procedure, preparation for starting data communication is completed. Next, a procedure until the user receives a service using this embodiment will be described with reference to the flowchart of FIG.
[0065]
When the user receives service provision from the Bluetooth device, the user activates the JAVA application 22 corresponding to the service (step S51). At this time, the Java Application Manager (JAM) checks the identifier of the designated JAVA application 22, checks the contents of the attribute data 44 of the application from the management data (step S52), and the OS resources such as the memory 4 and the communication function. Is assigned (step S53). Next, a message is sent to the JAVA virtual machine task to request that the designated JAVA application 22 be activated.
[0066]
At this time, JAM checks whether or not to use the BT module 16 based on the attribute data 44 in the management data (step S54). If the application to be started uses the BT module 16, the JAM next The application trust flag is checked to determine whether or not the application can be trusted (step S55).
[0067]
If the application is reliable, the proximity communication means attribute data in the attribute data 44 in the management data is read, and the value is set in the BT module 16 through the HCI task 21 (step S56). For example, when “2 s” is described in the page timeout item, the HCI task 21 requests to change the page timeout setting to “2 s”. The HCI task 21 instructs to change the setting of the BT module 16 using the WritePageTimeout command.
[0068]
In addition, even in an untrusted application, a dialog for confirming the setting change is presented to the user (step S57), and the setting change of the BT module 16 is permitted or activated even in the case of the trusted application like the temporarily trustworthy application. There may be implementations such as checking each.
[0069]
Next, the JAVA virtual machine is activated (step S58), and the JAVA application 22 is activated on the JAVA virtual machine (step S59). Next, a Bluetooth function is called (step S60), and it is determined whether or not it matches the BCC 26 setting (step S61). If they match, a Bluetooth command is transmitted (step S62). Is notified (step S63).
[0070]
As described above, according to the first embodiment, when a user requests activation of the JAVA application 22, it is automatically verified whether or not the application is reliable, and is necessary for Bluetooth communication only when the application is reliable. Because it automatically reads and sets the necessary information from the information file, the user does not need to make the settings themselves, saving the user's trouble and optimizing the settings for Bluetooth communication regardless of the JAVA virtual machine specifications. It can be performed. Further, when the application is not reliable, Bluetooth communication is not performed, so that security can be improved.
[0071]
In addition, by verifying the electronic signature 46 attached to the JAVA application 22, the company that created the application can be confirmed, and the identity of the server to be provided can be confirmed by using SSL at the time of download. It is possible to identify whether or not the server is operated by a person who owns it and whether or not it is a modified application.
[0072]
(Second Embodiment)
In the second embodiment, the setting information of the BT module 16 is temporarily saved in the memory 4 before the JAVA application 22 is activated, and is restored after the activation is completed.
[0073]
11 and 12 are flowcharts showing the processing procedure of the mobile phone 20 according to the second embodiment. Below, it demonstrates centering on the process different from 1st Embodiment. After the user gives an instruction to start the JAVA application 22, the application trust flag is inspected (step S75). If the application is reliable, only the item for which the attribute value of the BT module 16 is set, the current setting value of the item is set. A message is transmitted to the HCI task 21 for reading (step S76). The HCI task 21 acquires a value from the BT module 16 and returns it to JAM. The JAM associates the item with the read value and records it in the memory 4 as attribute value data of the BT module 16 (step S77). Thereafter, a message is transmitted to the HCI task 21 so as to set the value of the set item.
[0074]
For example, when “2 s” is described in the page timeout item, the current setting value of the BT module 16 is obtained through the HCI task 21, for example, the value “5 s” is obtained when the default value is maintained. The item is recorded in the memory 4 in a pair with the page timeout, and then the HCI task 21 is requested to change the page timeout setting to “2s”. The HCI task 21 uses the WritePageTimeout command to instruct to change the setting of the BT module 16 (step S78).
[0075]
When the user gives an instruction to end the JAVA application 22 after starting the JAVA application 22 (step S91 in FIG. 12), the JAVA virtual machine notifies the end event to the JAVA application 22 (step S92). As a result, the JAVA application 22 executes an end process, and then the JAVA virtual machine releases the application program from the storage area of the memory 4 (step S93).
[0076]
Thereafter, JAM examines the attribute value data of the BT module 16 (step S94), checks whether there is a value to be restored (step S95), and if there is an item to restore, the HCI task A message is sent to set the value to 21. In the above case, a message is transmitted to the HCI task 21 so as to change the page timeout to 5 s, and the HCI task 21 changes the value of the BT module 16 by the WritePegetimeout command to the BT module 16 (steps S96 and S97).
[0077]
As described above, in the second embodiment, the value of the BT module 16 is temporarily stored before the JAVA application 22 is activated, and is restored to the original value at the end of the application, whereby another application that uses the BT module 16 is used. When starting up, there is no contradiction in the setting value.
[0078]
(Third embodiment)
In the third embodiment, the power consumption of the mobile phone 20 is reduced.
[0079]
FIG. 13 is a flowchart showing the processing procedure of the mobile phone 20 according to the third embodiment. Below, it demonstrates centering on the process different from 1st Embodiment. If the JAVA application 22 is reliable, the device management flag of the attribute data 44 is checked (step S106).
[0080]
When the application to be used performs device management, the state of power supply to the BT module 16 is inspected (step S107). If the power is currently supplied to the BT module 16, the attribute data 44 of the BT module 16 in the attribute data 44 is read and the value is set in the BT module 16 through the HCI task 21 (step S108).
[0081]
If the power is not supplied, the API of the OS that enables the power supply to the BT module 16 is called to change the BT module 16 to a usable state (step S109). Next, a device status change flag (a flag indicating whether or not power has been supplied) in the management data is set (step S110), and then the attribute data 44 of the BT module 16 is read out and is sent to the BT module 16 through the HCI task 21. A value is set (step S108).
[0082]
On the other hand, when device management is not performed, the state of power supply to the BT module 16 is inspected (step S111). If the power is currently supplied to the BT module 16, the attribute data 44 of the BT module 16 in the attribute data 44 is read and the value is set in the BT module 16 through the HCI task 21 (step S108).
[0083]
If power is not supplied, a dialog is presented to the user to confirm whether or not to supply power to the BT module 16 (step S112). When the user instructs to supply power, the API of the OS that enables power supply to the BT module 16 is called, and the attribute data 44 of the BT module 16 in the attribute data 44 is read (step S113). ), The value is set in the BT module 16 through the HCI task 21 (step S108). If the user instructs not to supply power, the JAVA virtual machine is started as it is (step S114). In this case, even though the user desires to use the Bluetooth communication function, since the power is not supplied, the command requested in the application results in an error.
[0084]
On the other hand, when the user gives an instruction to end the JAVA application 22 after starting the JAVA application 22, the JAVA virtual machine notifies the JAVA application 22 of an end event. The JAVA application 22 executes termination processing necessary for its own termination such as data storage, and then the JAVA virtual machine releases the application program from the memory area. JAM then checks whether there is a value to be restored with the set value to the BT module 16, and if there is an item to be restored, a message is sent to the HCI task 21 to set that value. Send. Next, the device status change flag of the management data is checked, and when the power status is changed, the API of the OS that stops the power supply to the BT module 16 is called.
[0085]
As described above, in the third embodiment, even if the user does not explicitly instruct power supply to the BT module 16, JAM automatically turns on the power according to the attribute of the application, and ends. Sometimes it is possible to automatically turn off the power. That is, since power is supplied only during a period in which Bluetooth is used, the mobile phone 20 can be driven to save power.
[0086]
(Fourth embodiment)
The fourth embodiment is intended to shorten the time required from receiving an application to receiving a service.
[0087]
FIG. 14 is a flowchart showing the processing procedure of the mobile phone 20 according to the fourth embodiment. Below, it demonstrates centering on the process different from 1st Embodiment. If the application is reliable, the automatic search attribute flag of the attribute data 44 of the BT module 16 is checked (step S127). If the attribute is set, the BT module 16 is instructed to start inquiry through the HCI task 21 (step S128). At this time, an inquiry start instruction is made using the Class of Device and Inquiry Access Code attributes of the BT module 16.
[0088]
Thereafter, the JAVA virtual machine is activated (step S129), and the JAVA application 22 is activated (step S130). After the start of the JAVA application 22, the HCI task 21 checks the state of the BT module 16, checks whether a communicable terminal has been found, and if found, temporarily puts the event in a queue and sends an initialization event first. To the JAVA application 22. Thereafter, the discovery event is notified to the JAVA application 22 (step S131).
[0089]
As described above, in the fourth embodiment, by simultaneously performing discovery processing of a communicable terminal together with an application activation instruction, it is possible to reduce the processing time required from the activation of an application until a service is received.
[0090]
(Fifth embodiment)
In the first to fourth embodiments described above, when one or more settings of the BT module 16 are changed, the JAM notifies the user of the change using a notification device designated in advance. As a notification device, reproduction of an audio file or the like, vibration of a vibrator, blinking of an LED or the like can be considered. In particular, the user can check the state of the BT module 16 by turning on a specific color until the LED returns to the original setting.
[0091]
(Sixth embodiment)
FIG. 15 is a flowchart showing a processing procedure of the mobile phone 20 according to the sixth embodiment. Below, it demonstrates centering on the process different from 1st Embodiment.
[0092]
When the JAVA application 22 makes a connection request, the Bluetooth / OBEX task 23 makes a connection request to the HCI task, and the HCI task 21 makes a connection request to the BT module 16. If the setting of the BCC 26 is set to no authentication at this time (step S141) and the authentication mode of the attribute data 44 of the BT module 16 is authentication (step S142), the authentication change flag of the management data is set. In step S146, the BT module 16 is instructed to change to the authentication mode through the HCI task 21, and when the mode change is successful, a connection request is sent to the BT module 16 (step S147).
[0093]
When the BT module 16 performs connection processing with the counterpart device, the HCI task 21 receives a link key request event from the BT module 16. The HCI task 21 requests a link key from the JAM (step S150). If the JAM checks the attribute data 44 of the BT module 16 and has link key data, the value is used as the link key (step S151). ) To the BT module 16 through the HCI task 21.
[0094]
If it does not have a link key, a link key rejection is returned to the BT module 16 through the HCI task 21 (step S152). In the case of refusal, the HCI task 21 similarly receives a PIN code input event (step S153). The JAM that has received the PIN code request checks the PIN code of the attribute data 44 of the BT module 16 (step S154), and if it has the PIN code, returns the PIN code to the BT module 16 through the HCI task 21. (Step S155).
[0095]
If the user does not have a PIN code, a PIN code input dialog is presented to the user to prompt input (step S156). If there is a PIN code input, the PIN code is returned and the connection process is continued (step S157).
[0096]
When the JAVA application 22 is terminated, the authentication change flag of the management data is checked, and if the authentication mode is changed, the BT module 16 is requested through the HCI task 21 to change to the no authentication mode.
As described above, in the sixth embodiment, the user can authenticate the partner apparatus by using the authentication function of the BT module 16 without having to input an application-specific authentication key. .
[0097]
(Other embodiments)
The effects related to the attributes of the BT module 16 used in this embodiment will be described below.
[0098]
Since the following parameters cannot be directly controlled by the Bluetooth / OBEX task 23, settings suitable for the application can be performed by changing the parameters according to the method described in the present embodiment.
[0099]
In the transmission power control, the communication distance of a Bluetooth device is normally 10 m. However, by reducing the transmission power of the RF modem using a vendor extension command, the communication distance can be reduced, and communication suitable for the application. Can provide areas and improve security.
[0100]
A plurality of packet types are prepared as packets for Bluetooth data communication. Since the DM packet with an error correction function has a simple error correction capability, the packet transfer rate is lowered in an environment where other communication devices exist. However, since retransmission of packets does not occur, it is possible to prevent a decrease in the actual transfer rate even in a noisy environment. On the other hand, the DH packet does not have error correction capability, but the transfer rate can be increased accordingly. If an environment in which an application is used is predicted in advance and the environment is constant, it is advantageous to select a packet type corresponding to the environment.
[0101]
The authentication mode, PIN code, and link key are as described in the sixth embodiment. The page timeout is a parameter that determines the timeout of the connection request. Increasing this value increases the time required for connection, but increases the probability of being able to connect to the other party. On the other hand, when high-speed connection is possible, the reaction can be improved by reducing this value.
[0102]
The supervision timeout is a parameter for determining disconnection of a connection. When this value is increased, disconnection is difficult, but conversely, disconnection detection takes time and reaction becomes worse.
[0103]
The inquiry scan interval and page scan interval are used when the portable device becomes a slave. Decreasing this value can shorten the time required for connection, but on the other hand, the power consumed by the Bluetooth device increases.
[0104]
The channel number is an identification number used for OBEX connection, and is usually obtained using SDP. However, if there are no other applications, the processing time for SDP can be eliminated by fixing this value.
[0105]
Other application exclusion indicates that execution of another application is rejected. It is conceivable that Bluetooth is used not only by the JAVA application 22 but also by an OS native application. That is, when the native application using Bluetooth tries to send a command to the task of the Bluetooth stack while executing the JAVA application 22 corresponding to Bluetooth, this attribute is checked, and if it is exclusive, the native request is rejected. . Thereby, a certain Bluetooth JAVA application 22 can exclusively use resources.
[0106]
The effective communication distance requests RSSI measurement from the HCI task 21 when an ACL link is established, and if the obtained value does not satisfy the condition described in the attribute, the link is forcibly disconnected. . For example, when a distance of several tens of centimeters to 1 m is sufficient for a cash register, or when an erroneous connection is made with a device several meters away, the RSSI value is smaller than the expected RSSI value. Thereby, it can be determined whether or not communication is performed with a device existing in a desired area, and security can be enhanced. In this case, use RSSI that conforms to the use of Ver1.2.
[0107]
Anonymity mode uses Ver1.2, and if this function is used, it is possible to periodically change one's BT address, thereby ensuring privacy.
[0108]
In addition, this invention is not limited to said embodiment, In the implementation stage, it can change variously in the range which does not deviate from the summary. Furthermore, the above embodiments include inventions at various stages, and various inventions can be extracted by appropriately combining a plurality of disclosed constituent elements. For example, even if some constituent elements are deleted from all the constituent elements shown in the embodiment, the problem (at least one of them) described in the column of the problem to be solved by the invention can be solved, and the column of the effect of the invention If at least one of the effects described in (1) is obtained, a configuration from which this configuration requirement is deleted can be extracted as an invention.
[0109]
The functions of the wireless terminal described in the above-described embodiment may be configured by hardware or software. When configured by software, a program for realizing at least a part of the functions of the wireless terminal may be stored in a recording medium such as a floppy disk or a CD-ROM, and read and executed by a computer. The recording medium is not limited to a portable medium such as a magnetic disk or an optical disk, but may be a fixed recording medium such as a hard disk device or a memory.
[0110]
Further, a program for realizing at least a part of the functions of the wireless terminal may be distributed via a communication line (including wireless communication) such as the Internet. Furthermore, the program may be distributed through being stored in a recording medium via a wired line or a wireless line such as the Internet in a state where the program is encrypted, modulated, or compressed.
[0111]
【The invention's effect】
As described above in detail, according to the present invention, when there is a request for starting an application program, it is automatically verified whether or not the application program is reliable. Since the setting is automatically performed, it is not necessary for the user himself to perform the communication setting of the near field communication means, the user's trouble is saved, and the optimum communication setting can be performed when the application program is reliable. Further, there is no possibility of performing communication according to an unreliable application program, and security is improved.
[Brief description of the drawings]
FIG. 1 is a block diagram showing an example of the internal configuration of a mobile phone which is an embodiment of a wireless terminal according to the present invention.
FIG. 2 is a block diagram of modules necessary for the JAVA application to use the Bluetooth function.
FIG. 3 is a diagram showing a connection relationship between a mobile phone, a base station, and a Web server.
FIG. 4 is a flowchart showing an authentication procedure of an application performed by the mobile phone.
FIG. 5 is a diagram showing the structure of a JAD (JAVA Application Descriptor) file.
FIG. 6 is a diagram showing detailed contents of attribute data in a JAD file.
FIG. 7 is a diagram showing detailed contents of attribute data of a BT module.
FIG. 8 is a diagram showing detailed contents of management data.
FIG. 9 is a diagram showing a sequence until an application that receives a service according to the specification of JSR82 starts data exchange.
FIG. 10 is a flowchart showing a procedure until a user receives a service using the embodiment.
FIG. 11 is a flowchart illustrating a processing procedure according to the second embodiment when an application is activated.
FIG. 12 is a flowchart illustrating a processing procedure according to the second embodiment when an application ends.
FIG. 13 is a flowchart showing a processing procedure of the third embodiment of the mobile phone;
FIG. 14 is a flowchart showing a processing procedure of the fourth embodiment of the mobile phone;
FIG. 15 is a flowchart showing a processing procedure of the sixth embodiment of the mobile phone;
[Explanation of symbols]
1 Internal bus
2 CPU
3 ROM
4 memory
5 EEPROM
6 Microphone
7 A / D
8 Speaker
9 D / A
10 Eccentric motor
11 Base station
12 Communication Department
13 Display section
14 Key input section
15 Selection instruction part
16 BT module
17 Interface

Claims (11)

First communication means capable of receiving an application program including attached information;
Trust verification means for verifying whether or not the application program is reliable based on the attached information;
A second communication unit that is used by the application program and that is provided separately from the first communication unit and has a narrower communication range than the first communication unit;
Communication for performing communication setting of the second communication unit according to information necessary for communication by the second communication unit included in the attached information when executing the application program verified to be reliable by the trust verification unit Setting means;
After the communication setting unit performs communication setting on the second communication unit, a start start unit that starts the application program, and
Information necessary for communication by the second communication means includes communication partner activation search, authentication mode, link key, PIN code, transmission power, page timeout, supervision timeout, page scan interval, inquiry scan interval, etc. A wireless terminal comprising at least one of application exclusion, effective communication distance, packet type, class of device, inquiry access code, and channel number. The trust verification means includes
When the electronic certificate of the creator or administrator of the application program included in the attached information is verified, and the electronic certificate is trusted, the application program included in the attached information The wireless terminal according to claim 1, further comprising signature verification means for verifying whether the electronic signature is reliable. A storage unit that stores the application program after being verified by the signature verification unit as being reliable;
The said trust verification means further has a flag setting means which sets the flag information which shows that the said application program can be trusted after the said storage means has preserve | saved the said application program, The claim setting means characterized by the above-mentioned. Wireless terminal.   The attached information includes attribute information of the application program, information necessary for communication by the second communication means, an electronic certificate of the creator or administrator of the application program, and an electronic signature of the application program. The wireless terminal according to claim 1, wherein the wireless terminal is included. An information saving unit that temporarily saves information that needs to be changed among the communication setting information of the second communication unit before executing the application program verified to be reliable by the trust verification unit;
And a resetting unit configured to reset the information saved in the information saving unit in the second communication unit after the application program executed after the setting by the communication setting unit is completed. Item 5. The wireless terminal according to any one of Items 1 to 4. Communication permission determining means for determining whether or not the second communication means is set in a communication permission state;
When it is determined that the second communication means is not set in a communication allowable state when it is verified by the trust verification means that the second communication means is set in a communication allowable state, a communication allowable setting for setting the second communication means in a communication allowable state. The wireless terminal according to any one of claims 1 to 5, further comprising: means. A search request means for requesting the second communication means to start searching for a communicable communication device after the communication setting to the second communication means is completed by the communication setting means;
The wireless start according to any one of claims 1 to 6, wherein the activation start unit starts the application program after the search request unit requests the second communication unit to start a search. Terminal.   The wireless terminal according to any one of claims 1 to 7, further comprising a notification unit configured to notify that when the communication setting unit changes communication setting information of the second communication unit.   The wireless terminal according to claim 1, wherein the second communication unit performs communication using Bluetooth. Receiving an application program including attached information at the first communication means of the wireless terminal ;
Verifying whether the application program can be trusted based on the attached information by the trust verification means of the wireless terminal ;
When executing the application program verified to be reliable, the first wireless communication device is provided in the wireless terminal separately from the first communication means according to information necessary for communication by the application program included in the attached information. Performing communication setting of the second communication means having a communication range narrower than the communication means of the communication setting means of the wireless terminal ;
After performing the communication setting, the step of starting the application program in the start start unit of the wireless terminal ,
Information necessary for communication by the second communication means includes communication partner activation search, authentication mode, link key, PIN code, transmission power, page timeout, supervision timeout, page scan interval, inquiry scan interval, etc. A communication control program comprising at least one of application exclusion, effective communication distance, packet type, class of device, inquiry access code, and channel number. The application program including the attached information is received by the first communication means of the wireless terminal ,
Based on the attached information, whether or not the application program is reliable is verified by the trust verification means of the wireless terminal ,
When executing the application program verified to be reliable, the first communication unit is provided in the wireless terminal separately from the first communication unit according to information necessary for communication by the application program included in the attached information. The communication setting of the second communication means having a communication range narrower than that of the communication means is performed by the communication setting means of the wireless terminal ,
After performing the communication setting, the application program is activated by the activation start unit of the wireless terminal ,
Information necessary for communication by the second communication means includes communication partner activation search, authentication mode, link key, PIN code, transmission power, page timeout, supervision timeout, page scan interval, inquiry scan interval, etc. A communication control method comprising at least one of application exclusion, effective communication distance, packet type, class of device, inquiry access code, and channel number.

Images