JP2007306300A - Mobile communication terminal device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a mobile communication terminal device that reports a plurality of states of the device by a small number of reporting means according to the necessity of the state reporting. <P>SOLUTION: When a request to turn on an LED in a predetermined illumination pattern is received, the request and illumination pattern are stored (step S21b) and when a plurality of requests including the request meet predetermined conditions ("matching" at a step S21f), the LED is turned on in an illumination pattern different from illumination patterns of the plurality of requests (step S21g). <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a mobile communication terminal device, and more particularly to control of display of the state of each part of the device.

  In order to notify each unit of the mobile communication terminal device of the state of the unit, a technique for displaying a display unit such as an LED (Light Emitting Diode) with a lighting pattern depending on the state is known. Here, the state is, for example, that charging is being performed in a unit that manages charging. Further, in the part that controls the call, there is a missed call. The lighting pattern includes continuous lighting, and repeats lighting for a predetermined time and extinguishing for a predetermined time. Further, it includes turning off after lighting for a predetermined time, and turning off after repeating lighting and turning off a predetermined number of times.

  By displaying on the LED, compared with the case of displaying on an LCD (Liquid Crystal Display), the area occupied by the display unit on the outside of the housing of the device is reduced, which is advantageous for downsizing of the device. Further, power consumption is reduced, and the device can be operated for a long time by the power stored in the storage battery.

  Here, in order to display a plurality of states of one part or a plurality of parts with one LED, it is known that the LED is displayed with a different lighting pattern for each state. In addition, when a plurality of states occur simultaneously, it is known to give priority to the states and display with a lighting pattern in a high priority state. However, this method has a problem that even if it is necessary to simultaneously notify that there are two states, it is only possible to notify that one state is present.

  Therefore, when each of the two states (shake correction is properly performed in the camera and the in-focus state is completed) is in one of the two states, 2 It is known that the lighting pattern is changed and displayed in both cases (see, for example, Patent Document 1).

In addition, the said description is not restricted to LED, It is applied also to all alerting | reporting means. For example, an electric lamp may be used as long as the display unit performs either lighting or extinguishing. Furthermore, it is not restricted to a light emitting element, A vibrator and a speaker may be sufficient. In the case of a vibrator, the vibration operation corresponds to the lighting of the LED, and the vibration pattern corresponds to the lighting pattern. In the case of a speaker, the sound generation operation corresponds to the lighting of the LED, or the generated music corresponds to the lighting pattern.
JP-A-10-232421 (pages 12-13, FIG. 10)

  However, in the method disclosed in Patent Document 1 described above, when the states of three or more processing units occur in an arbitrary order, the number of state combinations becomes enormous and how the lighting pattern is changed. There is a problem that it is not clear whether this is appropriate for status notification. Furthermore, there is a problem that it is not clear how it is appropriate to change the lighting pattern when the generated state ends.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to provide a mobile communication terminal device that notifies a plurality of states of the device by a small number of notification means according to the necessity of the state notification. To do.

  In order to achieve the above object, a mobile communication terminal apparatus according to the present invention receives notification means for informing a state of a mobile communication terminal apparatus, a request for operating the notification means, and identification information of an operation pattern of the operation. And a notification control unit that operates the notification unit with an operation pattern identified by the received identification information, the notification control unit includes a first request to operate with the first operation pattern, When the second request for operating with the second operation pattern is received, the notification means is operated with an operation pattern different from the first operation pattern and different from the second operation pattern. .

  Further, the mobile communication terminal apparatus of the present invention receives and receives notification means for notifying the state of the mobile communication terminal apparatus, a request for operating the notification means, and identification information of an operation pattern of the operation. A notification control unit that operates the notification unit with an operation pattern identified by the identification information, and the notification control unit receives a first request to operate with the first operation pattern, and the first operation When a second request for operating with the second operation pattern is received after operating the notification means with a pattern, the operation pattern is different from the first operation pattern and different from the second operation pattern. After the second request for operating the notification means and operating with the second operation pattern is received, and operating the notification means with the second operation pattern, the first operation pattern If the first request to create has been received, and wherein the operating the informing means in the second operation pattern.

  ADVANTAGE OF THE INVENTION According to this invention, the mobile communication terminal device which alert | reports the several state of an apparatus with a small number of alerting | reporting means according to the necessity for the alerting | reporting of the state can be provided.

  Hereinafter, an embodiment of a mobile communication terminal device according to the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing a configuration of a mobile communication terminal apparatus according to an embodiment of the present invention. The mobile communication terminal device includes a control unit 11 that controls the entire device, an antenna 12a that transmits and receives radio waves to and from a base station (not shown), a communication unit 12b, a transmission and reception unit 13, and a communication unit. Speaker 14a, call microphone 14b, call unit 14c, display unit 15, input device 16, LED management unit 21, LED 22, LED management information storage unit 23, power supply unit 31, and charging control Part 32.

  The LED management information storage unit 23 stores information used when the LED management unit 21 controls the lighting of the LEDs 22. FIG. 2 shows information stored in the LED management information storage unit 23. The LED management information storage unit 23 includes a logical-physical correspondence table 24, a physical LED management table 25, a request list table 26, a lighting pattern change table 27, an LED lighting request management table 28, and a logical LED management table 29. Is memorized.

  The operation of each unit of the mobile communication terminal device configured as described above according to the embodiment of the present invention will be described.

  The communication unit 12b outputs the high-frequency signal received by the antenna 12a to the transmission / reception unit 13, and transmits the high-frequency signal output from the transmission / reception unit 13 from the antenna 12a.

  The transmission / reception unit 13 amplifies, frequency-converts and demodulates the high-frequency signal from the communication unit 12b, and sends a digital voice signal obtained thereby to the call unit 14c and a control signal including an incoming signal to the control unit 11. Further, the control signal including the digital voice signal output from the communication unit 14c and the call signal output from the control unit 11 is modulated, frequency-converted and amplified to obtain a high-frequency signal, which is transmitted to the communication unit 12b. send.

  The call unit 14c converts the digital audio signal output from the transmission / reception unit 13 into an analog audio signal, amplifies it, and sends it to the speaker 14a. The analog audio signal output from the microphone 14 b is amplified, converted into a digital audio signal, and transmitted to the transmission / reception unit 13.

  The display unit 15 is controlled by the control unit 11 to display characters / numbers and image data including a cursor, and the displayed data is controlled in response to an input operation from the input device 16. Switching is performed upon receiving an instruction from the unit 11.

  The input device 16 designates a telephone number of a communication partner, and a plurality of keys including a numeric key for inputting hiragana characters, alphabetic characters and symbol characters by a toggle type input method, a cursor movement key, and a scroll key. It consists of keys including function keys. When a key of the input device 16 is pressed, the identifier of the key is notified to the control unit 11 and displayed as a character on the display unit 15 by the control unit 11 and notified to each unit or controlled. .

  The LED management unit 21 receives a request for lighting the LED 22 transmitted from each unit of the apparatus with a predetermined lighting pattern, and lights the LED 22 with the requested lighting pattern. Further, when a plurality of lighting requests are overlapped, the LED 22 is lit with a lighting pattern of one request among the plurality of requests, the LED 22 is lit with a lighting pattern different from any request, or the LED 22 is not lit.

  The power supply unit 31 is a rechargeable battery, and stores the power supplied from the charge control unit 32. Moreover, the stored electric power is supplied to each part of the apparatus.

  The charge control unit 32 measures the amount of power stored in the power supply unit 31. When the measured amount of power is less than a predetermined value and the charging control unit 32 is connected to a power source (not shown), the power supplied from the power source is supplied to the power source unit 31. Let it charge.

  Hereinafter, the operation | movement regarding control of the lighting pattern of LED22 of the mobile communication terminal device which concerns on this embodiment is demonstrated.

  FIG. 3 shows an example of the configuration of the logical-physical correspondence table 24. The logical-physical correspondence table 24 includes information in which the LED logical identifier 24a and the LED physical identifier 24b are associated with each other. The LED logical identifier 24a is a logical identifier for identifying the LED. The LED physical identifier 24 b is a physical identifier that identifies the LED 22.

  According to the logical-physical correspondence table 24 shown in FIG. 3, the LED physical identifiers 24b are all “PH-A” for the three LED logical identifiers 24a “LO-A”, “LO-B”, and “LO-C”. ”, Which shows the LED 22. In this embodiment, there is no LED other than the LED 22, and any LED logical identifier 24 a is associated with the LED physical identifier 24 b “PH-A”, that is, the LED 22. Therefore, in the following description, the description of the correspondence between the LED logical identifier 24a and the LED 22 is omitted.

  FIG. 4 shows an example of the configuration of the physical LED management table 25. The physical LED management table 25 includes information in which an LED physical identifier 25a, a pointer 25b to the LED lighting request management table, and a pointer 25c to the logical LED management table are associated with each other. The LED physical identifier 25a is a value equal to the LED physical identifier 24b. In this embodiment, since it is one of the LED physical identifiers 24b “PH-A”, the physical LED management table 25 stores a set of information.

  The pointer 25b to the LED lighting request management table is a pointer indicating the position where the LED lighting request management table 28 is stored. The pointer 25c to the logical LED management table is a pointer indicating the position where the logical LED management table 29 is stored.

  As will be described later, in the LED lighting request management table 28 and the logical LED management table 29, information is added or removed in accordance with a request to turn on the LED 22 from each unit, so that the pointers to these two tables are stored here. However, in the following description, since the position where these tables are stored is known with reference to the physical LED management table 25, the description of the operation of knowing the position is omitted. In addition to these two tables, the position to be stored is determined according to the determination of the hardware configuration and software configuration of the apparatus, and the position is not changed by the operation of the apparatus. The description of is omitted.

  FIG. 5 shows an example of the configuration of the request list table 26. The request list table 26 includes information in which a priority 26a, an LED logical identifier 26b, a lighting pattern 26c, and a service identifier 26d are associated with each other. The LED logical identifier 26b, the lighting pattern 26c, and the service identifier 26d indicate a list of requests for lighting the LEDs 22 from the respective units of the device to the LED management unit 21, and the priority 26a indicates the priority of the request.

  The priority 26a is a positive integer, and the smaller the number, the higher the priority. The LED logical identifier 26b is an identifier equal to the LED logical identifier 24a. The lighting pattern 26c is constantly turned on, repeatedly turned on for a predetermined time and turned off for a predetermined time, turned off after turning on for a predetermined time, turned off after a predetermined number of turns on and off, etc. Is an identifier. The service identifier 26d is an identifier indicating what the request is intended to be notified by turning on the LED 22, and as will be described later, the processing unit that made the request to turn on the LED 22 with the service identifier 26d Is identified.

  In the present embodiment, as shown in FIG. 5, the LED logical identifier 26b, the lighting pattern 26c, and the service identifier 26d of information indicating different requests are all different information. Therefore, the following description will be continued assuming that the request can be uniquely identified by at least one piece of information of the LED logical identifier 26b, the lighting pattern 26c, and the service identifier 26d, but the present invention is not limited to this. The present invention can be applied if a request can be uniquely identified by a plurality of pieces of information, or by setting information for uniquely identifying a request.

  FIG. 6 shows an example of the configuration of the lighting pattern change table 27. The lighting pattern change table 27 includes a first LED logic identifier 27a, a first lighting pattern 27b, a second LED logic identifier 27c, a second lighting pattern 27d, and a third lighting pattern 27e. Consists of associated information. The first LED logical identifier 27a and the first lighting pattern 27b are information equivalent to the LED logical identifier 26b of one request stored in the request list table 26 and the lighting pattern 26c.

  On the other hand, the second LED logic identifier 27c and the second lighting pattern 27d are the LED logic identifier 26b and the lighting pattern 26c of one request stored in the request list table 26, and are the first LED logic. The identifier 27a and the first lighting pattern 27b are different request information. The third lighting pattern 27e is an identifier that identifies a lighting pattern that is different from at least the first lighting pattern 27b and different from the second lighting pattern 27d.

  When the LED 22 is controlled to be lighted according to the request indicated by the first LED logical identifier 27a and the first lighting pattern 27b, the second LED logical identifier 27c and the second lighting pattern 27d When requested, the LED 22 is turned on with the lighting pattern identified by the third lighting pattern 27e, but the present invention is not limited to this.

  When a request indicated by the second LED logical identifier 27c and the second lighting pattern 27d is made after a request indicated by the first LED logical identifier 27a and the first lighting pattern 27b, It may be indicated that the LED 22 is lit with the lighting pattern identified by the third lighting pattern 27e.

  The request indicated by the first LED logical identifier 27a and the first lighting pattern 27b, the request indicated by the second LED logical identifier 27c and the second lighting pattern 27d are in the order requested. It may be indicated that the LED 22 is lit in the lighting pattern identified by the third lighting pattern 27e when they are overlapped without depending on each other. Moreover, it is preferable that the 3rd lighting pattern 27e is an identifier of the lighting pattern different from any of the lighting patterns 26c.

  Here, the first LED logical identifier 27 a and the second LED logical identifier 27 c are associated with the same LED physical identifier 24 b by the logical-physical correspondence table 24.

  FIG. 7 shows an example of the configuration of the LED lighting request management table 28. The LED lighting request management table 28 includes information in which a request identifier 28a, an LED logical identifier 28b, a lighting pattern 28c, and a service identifier 28d are associated with each other. This associated information indicates a request for turning on the LED 22 that is currently requested. That is, the request identifier 28a is information that uniquely identifies the lighting request that is currently generated, and is an integer that is assigned in ascending order each time the request is generated. That is, the order in which the requests are made is indicated by the request identifier 28a.

  The LED logical identifier 28b, the lighting pattern 28c, and the service identifier 28d are the LED logical identifier 26b, the lighting pattern 26c, and the service identifier 26d of the request list table 26, respectively. In the request list table 26, the requests stored in the LED lighting request management table 28 are sorted and stored according to the priority 26a associated with the LED logical identifier 26b, the lighting pattern 26c, and the service identifier 26d. ing.

  FIG. 8 shows an example of the configuration of the logical LED management table 29. The logical LED management table 29 is made up of a number of pieces of information corresponding to the information stored in the logical-physical correspondence table 24, in which the LED logical identifier 29a and the lighting pattern 29b are associated with each other. The LED logical identifier 29a is equal to the LED logical identifier 24a, and the lighting pattern 29b is obtained by searching the LED lighting request management table 28 using a search key that the LED logical identifier 29a is equal to the LED logical identifier 28b. The same information as 28c is stored.

  In other words, the logical LED management table 29 stores an LED logical identifier 29a of a request for lighting the generated LED 22 and a lighting pattern 29b. No information is stored in the lighting pattern 29b corresponding to the LED logical identifier 29a for which the request has not occurred. In FIG. 8, “−” indicates that no information is stored.

  In the present embodiment, as already described, a plurality of lighting patterns 28c are not obtained by the search. However, when a plurality of lighting patterns 28c are obtained, the identifier of the lighting pattern performed by the LED 22 when the request is generated is stored. As will be described later, this identifier is one of the searched lighting patterns 28c and has the highest priority 26a associated with the request list table 26, or the third lighting pattern 27e. It is. In addition, the number of obtained lighting patterns 28c, that at least a plurality of lighting patterns 28c are obtained, is also stored.

  The control unit 11 stores the presence / absence of a missed call (the incoming signal is received and the incoming signal is no longer received without the incoming call process being performed). Then, an address book (not shown) is searched using the identification information of the communication terminal device that has made the incoming missed call, for example, a telephone number as a search key. When the search result is obtained, the LED logical identifier 26b is “LO-A”, the lighting pattern 26c is “lighting pattern X”, and the service identifier 26d is a request to turn on the LED 22 with “important missed call”. Transmit to the management unit 21. The priority 26a of this request is “1” and should be given the highest priority.

  If the search result is not obtained, the control unit 11 causes the LED management unit 21 to indicate that the LED logical identifier 26b is “LO-C”, the lighting pattern 26c is “lighting pattern Z”, and the service identifier 26d is “missed call”. ”Is sent to turn on the LED 22. The priority 26a of this request is “3”, which is the lowest priority. Note that the selection method of these two types of requests is not limited to the above. For example, when it is obtained by the search that the telephone number is important in the address book, a request with a priority 26a of “1” may be transmitted.

  When the control unit 11 determines that the presence of the missed call has been recognized by the user by a predetermined key operation of the input device 16, the control unit 11 issues a request to cancel the request to turn on the LED 22 transmitted due to the missed call. Transmit to the management unit 21.

  When the charging control unit 32 starts charging the power supply unit 31, the LED logical identifier 26 b is “LO-B”, the lighting pattern 26 c is “lighting pattern Y”, and the service identifier 26 d is “charging”. The request is transmitted to the LED management unit 21. The priority 26a of this request is “2”, which is a medium priority.

  When the charging of the power supply unit 31 is completed and when no power is supplied to the charging control unit 32, the charging control unit 32 transmits a request to cancel the request for turning on the LED 22 to the LED management unit 21.

  FIG. 9 shows a flowchart of the control operation when the LED management unit 21 receives a request to turn on the LED 22. The LED management unit 21 receives the request to turn on the LED 22 transmitted from each unit of the apparatus and starts the operation (step S21a). This request includes an LED logical identifier 26b, a lighting pattern 26c, and a service identifier 26d.

  Next, the LED management unit 21 stores the received request in the LED lighting request management table 28 and the logical LED management table 29 (step S21b). When storing in the LED lighting request management table 28, the received LED logical identifier 26b, lighting pattern 26c, and service identifier 26d are set to the LED logical identifier 28b, the lighting pattern 28c, and the service identifier 28d, respectively. An integer exceeding the integer already stored in the request identifier 28a is set in the request identifier 28a, and the set information is stored in the position sorted by the priority 26a as described above.

  Further, when storing in the logical LED management table 29, the received LED logical identifier 26b is searched for information having the same LED logical identifier 29a, and the received lighting pattern 26c is set in the lighting pattern 29b of the searched information. And remember.

  Then, the LED management unit 21 checks how many requests to turn on the LEDs 22 are stored according to how many pieces of information are stored in the lighting pattern 29b of the logical LED management table 29 (step S21c). If there is one stored request, the request is the request received in step S21a, the LED 22 is turned on with the lighting pattern 29b (step S21d), and the control operation is terminated (step S21e). .

  On the other hand, if a plurality of requests are stored in step S21c, the LED management unit 21 checks whether two of the plurality of requests match the lighting pattern change table 27 (step S21f). .

  That is, a set of first LED logic identifier 27a, first lighting pattern 27b, second LED logic identifier 27c, and second lighting pattern 27d stored in association with the lighting pattern change table 27. On the other hand, when the following three conditions are satisfied, it is determined that the two conditions are met.

  First, associated information consisting of an LED logical identifier 29a equal to the first LED logical identifier 27a and a lighting pattern 29b equal to the first lighting pattern 27b is stored in the logical LED management table 29, and That is, the associated information consisting of the LED logical identifier 29a equal to the second LED logical identifier 27c and the lighting pattern 29b equal to the second lighting pattern 27d is stored in the logical LED management table 29.

  Second, before the request is received in step S21a, the LED 22 is controlled to be lit with the first lighting pattern 27b, which is stored in the lighting pattern 29b, as will be described later. For the above information (excluding the lighting pattern 26c received in step S21a), a request for which the lighting pattern 26c of the request list table 26 is equal to the information is searched, and the obtained priority 26a is the highest. That is, the lighting pattern 26c and the first lighting pattern 27b are equal.

  Third, the LED logic identifier 26b and the lighting pattern 26c of the request received in step S21a are equal to the second LED logic identifier 27c and the second lighting pattern 27d, respectively. Alternatively, after the request identified by the first LED logical identifier 27a and the first lighting pattern 27b is received, the second LED logical identifier 27c and the second lighting pattern 27d are identified. The request has been received. The order in which the requests are received is determined by retrieving each request from the LED lighting request management table 28 and using the request identifier 28a corresponding to each obtained request.

  Of these three conditions, the first condition is essential, but the second condition and / or the third condition may not be determined.

  If it is determined that they match, the LED management unit 21 causes the LED 22 to light up with the third lighting pattern 27e stored in the lighting pattern change table 27 in association with the one set of information (step S21g). ), The control operation is terminated (step S21e).

  On the other hand, if it is determined that they do not match, the LED management unit 21 turns on the LED 22 with the lighting pattern 28c having the highest priority 26a among the requests stored in the LED lighting request management table 28 ( In step S21h, the control operation is terminated (step S21e). Here, since the requests are sorted and stored according to the priority 26a in the LED lighting request management table 28, a request with the highest priority 26a can be easily obtained.

  In step S21h, the LED 22 is turned on with the requested lighting pattern 28c having the highest priority 26a. However, the present invention is not limited to this. For example, the LED 22 may be turned on with the lighting pattern 28c of the newest request. Furthermore, a high priority 26a may be combined with a new one. For example, among the requests stored in the same LED lighting request management table 28, first, a new request is selected from requests having the same LED logical identifier 28b, and then the highest priority is selected from the selected requests. A request with high 26a may be selected.

  In the above description, when the above condition is satisfied with respect to a certain set of information stored in association with the lighting pattern change table 27 in step S21f, it is determined that they are matched. When there is a possibility that the above condition is satisfied in any of a plurality of sets of information, the information stored in association with the lighting pattern change table 27 is stored with priority, and the above condition is satisfied. Among the information, the LED 22 is turned on by the third lighting pattern 27e of information having a high priority, but this is not restrictive.

  For example, the third LED lighting pattern of the information set in which the LED logical identifier 26b and the lighting pattern 26c of the request received in step S21a are equal to the second LED logical identifier 27c and the second lighting pattern 27d, respectively. The LED 22 may be turned on at 27e.

  Further, among the requests identified by the first LED logical identifier 27a and the second LED logical identifier 27c of all the sets in which the above conditions are satisfied, the request with the highest priority 26a is retrieved from the request list table 26. The LED 22 may be turned on with the third lighting pattern 27e of the set in which the LED logical identifier 26b of the searched request is equal to the first LED logical identifier 27a or the second LED logical identifier 27c. .

  FIG. 10 shows a flowchart of the control operation when the LED management unit 21 receives a request to cancel the request to turn on the LED 22. The LED management unit 21 receives a request to cancel the request to turn on the LED 22 transmitted from each unit of the apparatus, and starts operation. In addition, when the request for turning on the LED 22 is a request for turning on only for a predetermined time or a request for turning on for a predetermined number of times, when the predetermined time has passed or for the predetermined number of times When the lighting is finished, the control unit 11 that is instructed to start by the LED management unit 21 when the request is received is started and the operation is started. (Step S21j).

  This cancel request includes the LED logical identifier 26b, the lighting pattern 26c, and the service identifier 26d, but is not limited thereto. Any information may be used as long as the request stored in the LED lighting request management table 28 can be identified and the lighting pattern 29b stored in the logical LED management table 29 can be identified. For this identification, the request list table 26 may be referred to.

  Next, the LED management unit 21 deletes the received cancel request from the LED lighting request management table 28 and deletes it from the logical LED management table 29 (step S21k). When deleting from the LED lighting request management table 28, a set of information corresponding to the received cancel request is deleted. Further, when deleting from the logical LED management table 29, the information stored in the lighting pattern 29b of the request to cancel is deleted.

  Then, the LED management unit 21 checks how many requests to turn on the LEDs 22 are stored according to how many pieces of information are stored in the lighting pattern 29b of the logical LED management table 29 (step S21m). If no request is stored (0 is stored), the LED 22 is turned off (step S21n), and the control operation is terminated (step S21o).

  On the other hand, if one request is stored, the LED management unit 21 turns on the LED 22 with the lighting pattern 29b of the request (step S21p), and ends the control operation (step S21o).

  Further, when a plurality of requests are stored, the LED management unit 21 checks whether two of the plurality of requests match the set of information stored in the lighting pattern change table 27 (step S21q). ). This operation is the same as the operation in step S21f already described, and a description thereof will be omitted.

  If the information matches the information stored in the lighting pattern change table 27, the LED management unit 21 turns on the LED 22 with the third lighting pattern 27e (step S21r), and ends the control operation (step S21o). . The operation in step S21r is the same as the operation in step S21g already described, and a description thereof will be omitted.

  On the other hand, if the information does not match the information stored in the lighting pattern change table 27, the LED management unit 21 turns on the LED 22 with the requested lighting pattern 26c having a high priority 26a (step S21s), and ends the control operation. (Step S21o). The operation in step S21s is the same as the operation in step S21h already described, and a description thereof will be omitted.

  As described below with reference to the request list table 26 and the lighting pattern change table 27, the state of each part of the apparatus is appropriately notified by the operation of the LED management unit 21 described above.

  That is, when the charging control unit 32 is charging the power source unit 31 and the LED 22 is lit with the lighting pattern 26c “lighting pattern Y” to notify that the charging is being performed, it is stored in the address book. If a missed call from the telephone number occurs, the lighting pattern of the LED 22 is changed to the third lighting pattern 27e, which is “lighting pattern P”, so that in addition to notifying that charging is in progress, an immediate response is possible. It is informed that it is not responding to the incoming call estimated to be necessary.

  On the other hand, if a missed call from a telephone number not stored in the address book occurs while the charging control unit 32 is charging the power supply unit 31, the lighting pattern of the LED 22 does not change and the service identifier 26d “Missed call” does not change, and It is not notified that it is not responding to an incoming call that is estimated to be unnecessary. By this operation, the user can avoid annoyance.

  Further, when a missed call from the telephone number stored in the address book has occurred and the LED 22 is lit with the lighting pattern 26c of “lighting pattern X” to notify that there is a missed call, charging is performed. When the control unit 32 starts charging the power supply unit 31, the lighting pattern of the LED 22 is changed to the lighting pattern 26 c that is “lighting pattern Y”, thereby informing that charging is being performed.

  In this case, the start of charging is performed by the user's intention, and the user recognizes that there is a missed call at that time. Therefore, the user can avoid annoyance by not changing the lighting pattern of the LED 22 to the third lighting pattern 27e which is “lighting pattern P”.

  Further, when a missed call from a telephone number not stored in the address book has occurred and the LED 22 is lit with the lighting pattern 26c, which is “lighting pattern Z”, to notify that there is a missed call, the address book If the missed call from the phone number stored in the message is generated and / or charging of the power supply unit 31 is started, it is treated that the LED 22 is not lit with the “lighting pattern Z” having a low priority 26a, The LED 22 is turned on in the “lighting pattern X”, “lighting pattern Y”, or “lighting pattern P”, and the user can avoid confusion in many lighting patterns.

  In the above description, the third lighting pattern 27e stored in the lighting pattern change table 27 is an identifier of a predetermined lighting pattern, but is not limited thereto. For example, logical operators (AND), logical sums (OR), exclusive logical sums (EX-OR, exclusive OR), negation (NOT), and combinations of these operators may be used.

  When a logical operator is stored in the third lighting pattern 27e, the LED management unit 21 assigns a logical value to each of the first LED logical identifier 27a and the second LED logical identifier 27c. Then, the logical operation indicated by the logical operator is performed on the two logical values. If the obtained logical value is true, the LED 22 is turned on. If the logical value is false, the LED 22 is turned off.

  The logical value assignment must be true if a request identified by these identifiers has occurred for each of the first LED logical identifier 27a and the second LED logical identifier 27c. It may be false. Moreover, according to each of the 1st lighting pattern 27b and the 2nd lighting pattern 27d, it is good also as false when the light is extinguished when LED22 is lighting.

  In the above description, the LED 22 is used for notification that there is a missed call and notification that charging is being performed. However, the present invention is not limited to this. It may be used for notifying that an incoming call is being received or notifying that the amount of power stored in the power supply unit 31 has become a predetermined value or less. Furthermore, the apparatus may have an e-mail transmission / reception unit (not shown), and may be used for notification of incoming e-mails.

  In the above description, the apparatus has one LED 22, but the present invention is not limited to this. The present invention can be applied to each of a plurality of LEDs or to lighting control in which they are combined. The present invention is not limited to the above configuration, and various modifications are possible.

The block diagram which shows the structure of the mobile communication terminal device which concerns on embodiment of this invention. The block diagram which shows the structure of the LED management information storage part which concerns on embodiment of this invention. The figure which shows an example of a structure of the logical-physical information correspondence table which concerns on embodiment of this invention. The figure which shows an example of a structure of the physical LED management table which concerns on embodiment of this invention. The figure which shows an example of a structure of the request | requirement list table which concerns on embodiment of this invention. The figure which shows an example of a structure of the lighting pattern change table which concerns on embodiment of this invention. The figure which shows an example of a structure of the LED lighting request management table which concerns on embodiment of this invention. The figure which shows an example of a structure of the logic LED management table which concerns on embodiment of this invention. The flowchart which shows operation | movement of the LED management part which concerns on embodiment of this invention (the 1 and operation | movement when the LED lighting request | requirement is received). The flowchart which shows operation | movement of the LED management part which concerns on embodiment of this invention (the 2 and operation | movement at the time of receiving the request | requirement to cancel LED lighting).

Explanation of symbols

11 Control unit 21 LED management unit 22 LED
23 LED management information storage unit 24 Logical-physical correspondence table 24a, 26b, 28b, 29a LED logical identifier 24b, 25a LED physical identifier 25 Physical LED management table 25b Pointer to LED lighting request management table 25c Pointer to logical LED management table 26 request list table 26a priority 26c, 28c, 29b lighting pattern 26d, 28d service identifier 27 lighting pattern change table 27a first LED logic identifier 27b first lighting pattern 27c second LED logic identifier 27d second lighting pattern 27e Third lighting pattern 28 LED lighting request management table 28a Request identifier 29 Logical LED management table 32 Charging control unit

Claims (5)

Informing means for informing the state of the mobile communication terminal device;
A notification control means for receiving a request for operating the notification means and identification information of an operation pattern of the operation, and operating the notification means with an operation pattern identified by the received identification information;
The notification control means is different from the first operation pattern when the first request to operate in the first operation pattern and the second request to operate in the second operation pattern are received, and A mobile communication terminal apparatus, wherein the notification means is operated with an operation pattern different from the second operation pattern. The notification control means stores the priority of the request, and when the first request to operate in the first operation pattern and the third request to operate in the third operation pattern are received, If the priority of the first request is higher than the priority of the third request, the notification means is operated in the first operation pattern, and the priority of the first request is the priority of the third request. 2. The mobile communication terminal device according to claim 1, wherein the notification unit is operated according to the third operation pattern if it is lower than the degree. Informing means for informing the state of the mobile communication terminal device;
A notification control means for receiving a request for operating the notification means and identification information of an operation pattern of the operation, and operating the notification means with an operation pattern identified by the received identification information;
The notification control means receives a first request to operate in the first operation pattern, operates the notification means in the first operation pattern, and then operates the second request to operate in the second operation pattern. Is received, a second request for operating the notification means with an operation pattern different from the first operation pattern and different from the second operation pattern and operating with the second operation pattern is received. When the first request for operating with the first operation pattern is received after operating the notification unit with the second operation pattern, the notification unit is operated with the second operation pattern. A mobile communication terminal device. The notification control means receives a first request for operating in the first operation pattern, operates the notification means in the first operation pattern, and then operates in a third operation pattern. The mobile communication terminal apparatus according to claim 3, wherein when the request is received, the notification unit is operated according to the first operation pattern or the third operation pattern. A rechargeable battery;
Charging control means for controlling charging to the rechargeable battery;
Call means,
Call control means for controlling the call means;
The first request is a request transmitted when the charge control unit charges the rechargeable battery,
The mobile communication terminal apparatus according to claim 1 or 3, wherein the second request is a request transmitted when the call control unit stores that there is a missed call.

Images