JP2019103111A - Caller information display device and program - Google Patents

Abstract

To make it possible to provide a caller information display device and program that present caller information to a user with high convenience and safely.SOLUTION: A caller information display device according to the present embodiment comprises: a processor for executing an application/program controlled by basic software and operates on the basic software; storage means including a secret area and an area storing the basic software and the application/program; and communication means for receiving call incoming from a call source telephone. The application/program makes the program function as means for storing data including a telephone number and name information corresponding to the telephone number in the secret area and means for registering a telephone number and name information included in the data with first caller data that is stored in the secret area and is capable of being retrieved by the basic software when the call incoming is received.SELECTED DRAWING: Figure 1

Description

  The present embodiment relates to a sender information display device and a program.

  2. Description of the Related Art In recent years, smartphones having both the function of a mobile phone and the function of a personal computer are rapidly spreading. By using the smartphone, for example, while going out, it is possible to browse e-mail, participate in an in-house meeting, etc. via the Internet. For this reason, in business applications, such mobile terminals are actively used to actively work to improve the business efficiency of business. For example, there may be mentioned BYOD (Bring Your Own Device) which uses a mobile terminal owned by an individual, and FMC (Fixed Mobile Convergence) which uses a mobile terminal as an extension telephone of a company.

JP, 2013-13019, A JP, 2015-198381, A

  As described above, when a personally-owned portable terminal is used in business, the management of the portable terminal is entrusted to the individual, and the terminal may be lost. In addition, if the terminal is lost even once, there is a risk that not only personal information but also information related to business leaks. Recently, in order to prevent such a risk, it is recommended that the business information not be registered in the telephone directory (address book) in the portable terminal.

  However, when the information is not registered in the phonebook of the portable terminal, it is impossible to know who is calling from when the call is received. In addition, even when registering information in the telephone directory, it is used in-house by FMC etc. In particular, when there are many employees, registering all extension numbers corresponding to each employee limits the number of registrable numbers of telephone directories. It is not realistic when considering etc. Therefore, even if it is a call from within the company, it may be difficult to know who the call is from.

  In Patent Documents 1 and 2 described above, there is disclosed a technology in which a portable terminal or the like inquires a telephone directory server or the like at the time of an incoming call, and the caller is specified and displayed. However, when the techniques of Patent Documents 1 and 2 are used, it may not be possible to display the caller in real time if the caller's search process takes time because the telephone directory is searched when an incoming call is received. Also, there may be cases where correct search results can not be obtained due to network communication failure or the like.

  The present invention has been made in view of the above situation, and provides a caller information display device and program for presenting caller information to a user conveniently and safely.

  The caller information display device according to the present embodiment is controlled by basic software, and a processor that executes an application program operating on the basic software, and an area for storing the basic software and the application program. , Storage means including a secret area, and communication means for receiving an incoming call from a source telephone. The application program includes means for storing data including a telephone number and name information corresponding to the telephone number in the secret area, the application program, a telephone number and name information included in the data, in the secret area. The basic software functions as a means for registering in the first caller data that can be searched when it is stored and the call is received.

  According to the present invention, it is possible to provide a caller information display apparatus and program for presenting caller information to a user conveniently and safely.

BRIEF DESCRIPTION OF THE DRAWINGS The block diagram which shows an example of the sender | caller information display system which concerns on embodiment. The block diagram showing an example of the user terminal concerning an embodiment. The block diagram showing an example of the server apparatus concerning an embodiment. The flowchart which shows an example of the address data acquisition process of the user terminal which concerns on embodiment. The figure which shows an example of the in-house address book which concerns on embodiment. The figure which shows an example of the personal address book which concerns on embodiment. The figure which shows an example of the share address book which concerns on embodiment. 6 is a flowchart showing an example of address book merge processing according to the embodiment. The figure which shows an example of the address list data which concern on embodiment. The flowchart which shows an example of the sender | caller information display process which concerns on embodiment.

  Hereinafter, each embodiment will be described with reference to the drawings. In the following description, the same or substantially the same functions and components as those described above will be denoted by the same reference numerals, and the description thereof will be omitted or will be described as needed.

  FIG. 1 is a block diagram showing an example of the configuration of a sender information display system 1 according to the present embodiment. Hereinafter, the outline of the configuration and process of the caller information display system 1 will be described using FIG. 1.

  The caller information display system 1 includes a user terminal 2 and a server device 3. The user terminal 2 and the server device 3 are communicably connected via the network N.

  The network N may be, for example, a wide area communication network including the Internet, an intranet, or the like, or may be a short distance wireless communication conforming to Bluetooth (registered trademark), a wireless LAN (Local Area Network), or other standards.

  The user terminal 2 is an information processing apparatus including, for example, a smart device, a personal computer (PC), a tablet terminal, and the like. The user terminal 2 has a function of communicating with an external device such as the server device 3 via the network N, for example.

  The user terminal 2 includes a telephone set that can be connected to a public network. That is, the user terminal 2 may be a smartphone, a mobile phone, or a PDA (Personal Data Assistance) having a call function. The user terminal 2 may be available as a telephone under a PBX (Private Branch exchange), that is, an extension telephone. The user terminal 2 is operated by the user U.

  The user terminal 2 requests acquisition (downloading) of list data of address data to the server device 3 at any timing manually or in a cycle of a predetermined time, and conceals the user terminal 2 by using the acquired address data as a temporary file Save in the area (application area). Also, when given authority is given, the user terminal 2 registers the extracted address data from the saved temporary file to the sender information data in the secret area.

  Also, the user terminal 2 receives an incoming call from the source telephone T0. The source telephone T0 is a telephone or a device having a call function. The source telephone T0 may be an external telephone connected to the public network or an extension telephone connected to the subordinate of the PBX.

  The user terminal 2 searches the internal telephone directory using the incoming call number as a key when an incoming call from the calling telephone T0 is made, and when the corresponding caller is not found, the user information is further transmitted by further searching the caller information data. The telephone number of the original telephone set T0 is specified.

  The server device 3 is, for example, an information processing device that manages address data of a user.

  The server device 3 can identify the user U. For example, the server device 3 uniquely identifies the user U by authenticating the user U using identification data such as a user ID and a password. Further, the server device 3 may be able to identify the user terminal 2 tied to the user U.

  In response to the address data acquisition request from the user terminal 2, the server device 3 generates address list data in which an address book which can be browsed by the authenticated user U is merged, and transmits it to the user terminal 2.

  In the caller information display system 1 according to the present embodiment, for example, even when the user U who uses the user terminal 2 having a call function does not register information in the telephone directory of the user terminal 2, the user U has already been authenticated. The address data stored in the server device 3 is displayed on the user terminal 2 without the user U being aware. More specifically, the server device 3 generates address list data by merging a plurality of address books held by the server device 3 based on the rank information of the user U. The user terminal 2 acquires the address list data in advance from the server device 3 and registers it as the sender information data in the secret area of the user terminal 2 when the predetermined authority is given. In addition to the internal telephone directory, the user terminal 2 searches the caller information data in addition to the internal telephone directory and displays the caller information obtained by the search on the display of the user terminal 2 when an incoming call from the caller telephone T0 is received.

  Below, the more detailed structure of the user terminal 2 and the server apparatus 3, and the detail of the process which the sender | caller information display system 1 perform are demonstrated.

  FIG. 2 is a block diagram showing an example of the user terminal 2 according to the present embodiment.

  The user terminal 2 includes a first non-volatile memory 2 a, a processor 2 b, a first volatile memory 2 c, a communication device 2 d, a display device 2 e, an input device 2 f, and a call device 2 g. These respective devices are connected to one another by a bus.

  The first non-volatile memory 2 a is constituted by, for example, a hard disk, a solid state drive (SSD), a flash memory, etc., and constitutes a storage area together with the first volatile memory 2 c.

  The first non-volatile memory 2 a includes a secret area X and a user area Y. The secret area X is an area which the user U can not access. The secret area X is, for example, an application area. On the other hand, the user area Y is a public area accessible to the user U.

  The secret area X stores various software, such as an operating system (OS), a browser, a mailer, and various application programs. In the secret area X, a program P1 for realizing the caller information display system 1 according to the present embodiment is stored.

  In the secret area X, user data X1, temporary file X2, and sender information data X3 are stored.

  The user data X1 includes, for example, identification data such as a user ID and a password. The user data X1 may further include data capable of identifying the user U.

  The temporary file X2 is a file received (downloaded) from the server device 3. The temporary file X2 includes the address data generated by the server device 3 but is treated as a mere downloaded file on the user terminal 2. The temporary file X2 may be encrypted.

  The temporary file X2 is data described in text format, for example. The temporary file X2 may be described in a special format such as JSON format or XML format. The temporary file X2 may be binary format data. The file format of the temporary file X2 is not limited to that described above.

  The sender information data X3 is address data including the display name of the sender and the telephone number. Since the caller information data X3 is stored in the secret area X, the user U can not access the caller information data X3 such as registration, deletion, viewing and editing. In other words, the caller information data X3 is a telephone directory hidden from the user U. In the sender information data X3, for example, the display name and the telephone number of the sender based on the address data included in the temporary file X2 are registered.

  The user area Y includes an internal telephone directory Y1. The internal telephone directory Y1 is a standard telephone directory that the user terminal 2 has as an existing function, and includes, for example, data related to caller information. The internal telephone directory Y1 is disclosed to the user U, and the user U registers desired address data including, for example, a telephone number and a display name with the internal telephone directory Y1 via the input device 2f or the like. It is editable. In addition, the user U can browse the address data included in the internal telephone directory Y1 by the display device 2e.

  The processor 2 b executes various software (programs) to control the entire user terminal 2. The processor 2 b is, for example, a central processing unit (CPU), a microprocessor unit (MPU), a digital signal processing (DSP), or the like.

  The processor 2 b includes, for example, an OS 21 and an application 22. The application 22 is installed on the OS 21. In other words, the OS 21 is basic software capable of installing a plurality of applications.

  The processor 2b executes, for example, the OS 21 and the application 22 by executing the program P1 stored in the first non-volatile memory 2a or expanded from the first non-volatile memory 2a to the first volatile memory 2c. Act as.

  The OS 21 includes an incoming call processing unit 210 and an authorization unit 211.

  The incoming call processing unit 210 performs necessary processing when there is an incoming call from the source telephone T0. For example, the incoming call processing unit 210 displays a screen indicating that an incoming call is in progress on the display device 2e. Further, the incoming call processing unit 210 searches for information related to the caller from the internal telephone directory Y1 and the caller information data, and executes a caller information display process for displaying the information. Details of the caller information display process will be described later with reference to FIG.

  The authorization unit 211 gives or deletes (removes) a predetermined authorization for the application 22 to operate on the user terminal 2 with respect to the application 22. The predetermined authority indicates, for example, permitting an operation related to an incoming call.

  Note that the authorization unit 211 may execute authorization to the application 22 by the operation of the user U (that is, by manual operation), or may automatically execute the authorization. When the authorization is executed by the manual operation of the user U, the user U may be able to execute the authorization via the screen of the application 22 or the operation of the authorization via the setting screen of the OS 21 It may be feasible.

  The application 22 includes, for example, an authentication unit 220, an acquisition unit 221, and a registration unit 222.

  The authentication unit 220 manages user data X1. The authentication unit 220 causes the user U to input user data X1 including a user ID, a password, and the like, and stores the user data X1 in the secret area X. The authentication unit 220 also transmits user data X1 to the server device 3. Thus, the server device 3 can authenticate the user U. Further, the authentication unit 220 acquires an authentication result from the server device 3. The authentication unit 220 may encrypt the user data X1 and send it to the server device 3.

  The acquisition unit 221 transmits a download request for address data to the server device 3 that has authenticated the user U. The acquisition unit 221 receives address data from the server device 3.

  The registration unit 222 analyzes the address data included in the temporary file X2 and registers the information in the caller information data X3 when the predetermined right is given to the application 22 by the authority giving unit 211. The registration unit 222 registers, in the caller information data X3, data (record) in which a display name indicating at least the caller and a telephone number of the caller among the address data are combined. The display name is, for example, name information such as a name. At the time of the registration process, the registration unit 222 may use, for example, a predetermined API (Application Program Interface) provided by the OS 21. In addition, the registration unit 222 may be able to register additional data such as a company name and a department name in the sender information data X3 among the address data included in the temporary file X2.

  When the authentication unit 220 fails to authenticate the user U, the registration unit 222 deletes (uninstalls) the application 22 or the user U requests deletion of the caller information data X3. In some cases, the caller information data X3 may be deleted. Thereby, the secrecy and security of the sender information data X3 can be enhanced.

  The application 22 and / or the OS 21 execute processing for transmitting and receiving commands and the like to and from the server device 3 via the communication device 2d. Further, the application 22 and / or the OS 21 generates a user interface using the display device 2e, the input device 2f, and the like, and executes a process for controlling the user interface.

The first volatile memory 2c as the main memory is, for example, RAM (Random Access Mem)
ory) and is used as a work area or the like. The work area is used when the processor 2b executes various software.

  The communication device 2 d controls communication with the server device 3 via the network N. The communication device 2d may have a wireless communication function such as a wireless LAN, or a short distance wireless communication function such as Bluetooth (registered trademark).

  The display device 2 e displays the OS 21 that the processor 2 b executes, the application 22, and user interfaces of various application programs.

  The input device 2 f includes, for example, a screen keyboard or a touch sensor. Also, the input device 2 f may include a keyboard or a mouse.

  The communication device 2g is a device for making a call by the user terminal 2, and includes a microphone and a speaker (not shown).

  FIG. 3 is a block diagram showing an example of the server device 3 according to the present embodiment.

  The server device 3 includes a second non-volatile memory 3 a, a processor 3 b, a second volatile memory 3 c, and a communication device 3 d. These devices are interconnected by a bus.

  Similar to the first non-volatile memory 2a, the second non-volatile memory 3a includes, for example, a hard disk, an SSD, and a flash memory, and stores various software, data, and the like. Various software includes an OS, a data management program, various application programs, and the like. The second non-volatile memory 3a stores, for example, a program P2, user data D1, address data D2, and the like.

  The user data D1 includes, for example, information on the user U who uses the server device 3. The user data D1 includes the user ID and password of the user U. Further, rank information R is associated with the user data D1 for each user U. The rank information R is, for example, attribute information such as a position in an organization. More specifically, the rank information R is, for example, a number indicating the rank, "1: director" "2: general manager" "3: department manager" "4: section manager" "5: general employee" "6: temporary employee It is expressed like ". In the present embodiment, it is assumed that the position becomes higher as the number indicating the rank is smaller.

  The address data D2 includes various address books that can be browsed by the user U. For example, the address data D2 includes an in-house address book AD1, a personal address book AD2, and a shared address book AD3.

  The in-house address book AD1 is, for example, an address book classified according to the rank of the organization (for example, the above-mentioned rank information R). For example, the user U can browse to the address of a position one rank higher than the position indicated by his rank information R. More specifically, for example, when the position of user U is “4: section manager”, an address book corresponding to rank information of “3” or higher (ie, an address book of positions lower than “3: manager”) Can be browsed, and "1: Director" and "2: General manager" address book can not be browsed. Details of the in-house address book AD1 will be described later with reference to FIG.

  The personal address book AD2 is an address book that the user U can use and other users can not browse. Details of the personal address book AD2 will be described later with reference to FIG.

  The shared address book AD3 is, for example, an address book shared by a group consisting of only a specific user U or a plurality of specific users U. The shared address book AD3 can be viewed only by users authorized for the group unit or individual unit. Details of the shared address book AD3 will be described later with reference to FIG.

  The address data D2 may include at least one or more address books among the in-house address book AD1, the personal address book AD2, and the shared address book AD3.

  The processor 3 b executes various software (programs) to control the entire server device 3. The processor 3 b is, for example, a CPU, an MPU, or a DSP.

  The processor 3 b may execute, for example, a user by executing the program P2 stored in the second nonvolatile memory 3 a or expanded from the second nonvolatile memory 3 a to the second volatile memory 3 c. It functions as an identification unit 31, an address data management unit 32, and an address list data generation unit 33.

  The user identification unit 31 authenticates the user U by, for example, collating the user data X1 received from the user terminal 2 with the user data D1 read from the second non-volatile memory 3a. . The user identification unit 31 permits access from the user terminal 2 to the server device 3 when the authentication is successful, and disallows the access when the authentication is unsuccessful.

  The address data management unit 32 manages each address book included in the address data D2. The address data management unit 32 receives, for example, a request for registration, deletion, browsing, editing, acquisition, etc. of an address for each address book from the user terminal 2, and transmits / receives address data according to the request, and registers the address. And execute deletion processing and the like.

  When receiving the address data download request from the user terminal 2, the address list data generation unit 33 merges each address book included in the address data D2 based on the rank information R of the authenticated user U and the like, Generate address list data. The address list data is preferably, for example, one file. The address list data is transmitted to the user terminal 2 and stored in the first non-volatile memory 2 a of the user terminal 2 as a temporary file X2. Preferably, the address list data includes at least a telephone number and a display name among data (records) included in each address book. Details of the address book merging process will be described later with reference to FIG.

  Similar to the first volatile memory 2c, the second volatile memory 3c is used as a work area or the like of the processor 3b.

  The communication device 3 d controls communication with the user terminal 2 via the network N, similarly to the communication device 2 d.

  In addition, the server device 3 may include a display device, an input device, and the like.

  FIG. 4 is a flowchart showing an example of address data acquisition processing of the user terminal 2 according to the present embodiment. In the example of FIG. 4, it is assumed that the authority giving unit 211 of the user terminal 2 has given in advance the right to permit the operation at the time of call reception to the application 22 (hereinafter referred to as a predetermined right). Do.

  In step S101, the authentication unit 220 of the user terminal 2 transmits the user data X1 manually by the operation of the user U or automatically at predetermined intervals. The predetermined interval is, for example, 24 hours.

  In step S102, the server device 3 receives the user data X1 and performs user authentication processing. More specifically, the user identification unit 31 reads out the user data D1 stored in advance in the second non-volatile memory 3a, and uses the user ID and password included in the received user data X1, and The user U is authenticated by collating the user ID and the password stored in the person data D1.

  The user data X1 may not be stored in the user terminal 2 in advance. In this case, when the user identification unit 31 accesses the server device 3 from the user terminal 2 via the network N, the user identification unit 31 directly prompts the user U to input a user ID and a password. It is also possible to acquire the person data X1.

  In step S103, the acquisition unit 221 of the user terminal 2 transmits a download request for address data to the server device 3. The transmission of the download request may be performed manually by the operation of the user U, or may be automatically performed at predetermined intervals.

  In step S104, the server device 3 receives the download request. The address list data generation unit 33 of the server device 3 reads out the rank information R corresponding to the user U and the address data D2 that the user U can view from the second non-volatile memory 3a, and generates address list data. .

  In step S105, the address data management unit 32 transmits the address list data generated in step S104 to the user terminal 2. At this time, the address data management unit 32 may encrypt the address list data.

  In step S106, the acquisition unit 221 of the user terminal 2 receives the address list data, and stores it as the temporary file X2 in the secret area X of the first non-volatile memory 2a. The acquisition unit 221 may encrypt the received temporary file X2. The temporary file X2 may be encrypted on the side of the server device 3 after being generated on the server device 3 in step S105.

  In addition, it is preferable that the temporary file X2 be always kept updated. Therefore, the acquisition unit 221 replaces the old temporary file X2 downloaded before with the latest temporary file X2.

  In step S <b> 107, the registration unit 222 of the user terminal 2 checks whether or not the application 22 has been given predetermined authorization. If the predetermined authority has not been granted, the process ends. If the predetermined right has been granted, the process proceeds to step S108.

  In step S108, the registration unit 222 confirms whether or not the temporary file X2 is encrypted. When the temporary file X2 is encrypted, the registration unit 222 performs decryption processing on the encryption in step S109. On the other hand, when the temporary file X2 is not encrypted, the process proceeds to step S110.

  In step S110, the registration unit 222 registers the address data included in the temporary file X2 in the caller information data X3. When, for example, address data having a duplicate telephone number exists in the address data, the registration unit 222 selects and registers only the address data having a higher priority (sort order information) described later, for example. . That is, in the caller information data X3, one display name is associated with one telephone number. Thus, when the caller information X3 is searched using the telephone number as a key, the display name to be displayed for the telephone number can be uniquely identified.

  Note that even if the predetermined authority is not granted in step S107 and the process ends, if the predetermined authority is granted later, the address data acquisition process is performed from step S108 using the acquired temporary file X2 Can be resumed.

  The authentication of the user U in step S102 may be performed when a download request for address data is received from the user terminal 2 in step S103.

  FIG. 5 is a view showing an example of the in-house address book AD1 according to the present embodiment. In FIG. 5, for example, it is assumed that data (records) of six in-house address data L11 to L16 are input. Although the in-house address book AD1 is described as being sorted by job position and in descending order of sort order information iA, it may be sorted according to other rules.

  In the in-house address book AD1, for example, a job position i11, a department name i12, a display name (employee name) i13, a telephone number i14, etc. in the organization are stored as personal information. These pieces of personal information are associated with management information such as sort order information iA and display flag iB.

  The job position i11 corresponds to the rank information R of the user data D1 stored in the server device 3 as described above.

  The sort order information iA indicates the display priority in the address data D2. When merging the plurality of address books included in the address data D2, the address list data generation unit 33 arranges the address data using the sorting order information iA as a key. In the present embodiment, it is assumed that the values of the sort order information iA are sorted in descending order.

  The display flag iB is flag information indicating whether or not to display the address data for each user. The display flag iB is set for each user U. For example, when the display flag iB of the address data is set to off (for example, “0”), the address data is not disclosed to the user U. That is, based on the rank information R of the user U, the display flag iB of the browsable address data is set to ON (for example, "1"), and the display flag iB of the browsable address data is set to OFF. In other words, the display flag iB is information indicating the browsing authority of the user U.

  Of the personal information included in the in-house address book AD1, it is preferable that the job title i11, the display name i13 and the telephone number i14 have already been entered as essential items. Further, in FIG. 5, the department name i12 is illustrated as an optional item, but another optional item may be input to the personal information.

  FIG. 6 is a view showing an example of the personal address book AD2 according to the present embodiment. In FIG. 6, for example, it is assumed that data (record) of four personal address data L21 to L24 is input.

  In the personal address book AD2, for example, a department name i21, a display name (employee name) i22, a telephone number i23, etc. are stored as personal information, and such personal information is management information such as sort order information iA, display flag iB, etc. Associated with The personal information is the same as the department name i12, the display name (employee name) i13, and the telephone number i14 in the in-house address book AD1.

  Since the personal address book AD2 is created for each user U, the display flag iB is normally turned on. However, for example, in the case where the user U wants to conceal by his / her intention, the user U can turn it off.

  Further, in the personal address book AD2 of FIG. 6, as in the in-house address book AD1 of FIG. 5, other arbitrary items other than the department name i12 may be input.

  FIG. 7 is a diagram showing an example of the shared address book AD3 according to the present embodiment. In FIG. 7, for example, it is assumed that data (record) of four shared address data L31 to L34 is input.

  In the shared address book AD3, for example, a display name (group name) i31, a telephone number i32 and the like are stored as personal information, and these personal information are associated with management information such as sort order information iA and display flag iB. The personal information is the same as the display name (employee name) i13 and the telephone number i14 in the in-house address book AD1.

  Further, the display flag iB of the address data to which the user U is given the browsing authority is set to ON, and the display flag iB of the address data to which the browsing authority is not authorized is set to OFF.

  Also in the personal address book AD2 of FIG. 7, a department name, a job title, or any other optional item may be input.

  FIG. 8 is a flowchart showing an example of address book merge processing according to the present embodiment. The process shown in FIG. 8 corresponds to the process of step S104 in FIG.

  In step S301, the address list data generation unit 33 of the server device 3 selects (extracts) address data for which the display flag iB is on among the address data D2 stored in the second non-volatile memory 3a.

  In step S302, the address list data generation unit 33 merges the address data selected in step S301 and further generates address list data by sorting based on the sort order information iA of each address data.

  Further, in the sorting process, for example, in the case where sorting order information iA, display name or telephone number overlap among a plurality of address books or within the same address book, the following steps S303 to S306 are executed. Ru.

  The address list data generation unit 33 checks whether there is address data having the same sort order information iA (step S303). If there is no address data having the same sort order information iA, the address list data generation unit 33 does nothing. On the other hand, when there is address data having the same sort order information iA, the address list data generation unit 33 sorts the address data based on the priority determined among the address books (step S304). . At this time, the address list data generation unit 33 confirms whether the priority order of the address book is the same among the address data (step S305). If the priorities of the address book are the same, the address data is sorted based on the other priorities (step S306). The other priority order is, for example, the reading order of display names (Kana order), the telephone number order, and the like.

  The priority of each address book may be determined in advance, and may be stored, for example, in the non-volatile memory 3a.

  A plurality of address data selected from the plurality of address books are merged by the process shown in steps S303 to S306 described above, and are uniquely sorted by the preset sort order information iA. Further, according to the process of step S110 of FIG. 4, the address data with high sort order information iA is preferentially registered in the sender information data X3. That is, even if, for example, the administrator of the user U or each address book registers a plurality of address data having overlapping telephone numbers in the address data D2, desired address data can be obtained by arbitrarily setting the sort order information iA. Can be registered in the sender information data X3.

  FIG. 9 is a view showing an example of the address list data according to the present embodiment. More specifically, FIG. 9 shows the address list data generation unit 33 of the server device 3 when the user U is in the position “5: general employee”, the in-house address book AD1 shown in FIGS. FIG. 9 shows address list data generated when the address book merge process shown in FIG. 8 is performed on the personal address book AD2 and the shared address book AD3.

  The address list data includes at least a name i1 and a telephone number i2 as required items. The address list data may include information other than the personal information included in each address book.

  Since the rank information R of the user U is “5: general employee” as described above, the user U can browse the address data of the positions below “4: section manager” in the in-house address book AD1. That is, as shown in FIG. 5, the display flag iB corresponding to the user U is turned off in the positions of “3: section manager” or higher and turned on in the positions of “4: section manager” or lower.

  The address list data generation unit 33 selects (extracts) the in-house address data L14 to L16, the personal address data L21 to L24, and the shared address data L31, L32, and L34 in which the display flag iB is on (see step S301).

  Then, the address list data generation unit 33 generates the address list data shown in FIG. 9 by rearranging the selected address data in the order of the sort order information iA (see step S302).

  Here, since the sort order information iA of the in-house address data L14, the shared address data L31, and the shared address data L34 is the same, these are sorted based on the process shown in steps S303 to S306 in FIG. .

  For example, assuming that the priority order of each address book is, for example, the order of the in-house address book AD1, the personal address book AD2, and the shared address book AD3, the in-house address data L14 is the fastest in order (step S304). Since the priority order of the address book of shared address data L31 and shared address data L34 is the same, according to the kana order of both display names, the arrangement order of both becomes shared address data L31 and shared address data L34 (step S306) . Therefore, the arrangement order of the three parties is the order of the in-house address data L14, the shared address data L31, and the shared address data L34.

  Among the address data having the same telephone number, the registration unit 222 of the user terminal 2 registers, for example, the personal address data L22 lined up most in the address list data in the caller information data X3, and the in-house address data Registration of L14 and shared address data L31 is skipped.

  FIG. 10 is a flowchart showing an example of the sender information display process according to the present embodiment. More specifically, FIG. 10 shows a process for displaying caller data by using the caller information data X3 registered by the process of FIG. 9 by the OS 21 of the user terminal 2.

  In step S501, the caller telephone set T0 dials the user terminal 2. The call origination is not limited to origination using a public line, for example, but may be extension origination using FMC or the like, telephone origination using an internet line such as VoIP (Voice over Internet Protocol), or the like.

  In step S502, the OS 21 of the user terminal 2 searches the internal telephone directory Y1 using the telephone number of the call received by the user terminal 2 as a key on the basis of the call origination in step S501.

  In step S503, the OS 21 checks whether address data including a telephone number matching the telephone number is found in the internal telephone directory Y1. If the address data is found, the OS 21 displays the display name included in the address data as the sender information in step S506. On the other hand, when the address data is not found, the OS 21 searches for the sender information data X3 in step S504.

  In step S505, the OS 21 determines whether address data including a telephone number matching the telephone number is found in the caller information data X3. If the address data is found, the process proceeds to step S506, and the display name included in the address data is displayed as the sender information. On the other hand, if no address data is found, the caller information is not displayed.

  In the present embodiment, the OS 21 has been described as performing the incoming call control of the telephone, but the application 22 may perform it.

  In the embodiment described above, the application 22 of the user terminal 2 transmits an acquisition request for address data to the server device 3, and the received address list data is regarded as a temporary file X2 in the first non-volatile memory 2a. It is stored in the secret area X which the user U can not access. In addition, when the application 22 is given predetermined authority by the OS 21, the application 22 registers address data from the temporary file X2 to the caller information data X3 present in the secret area X as well.

  As a result, even when the user U loses the user terminal 2, another person can not know the existence of the temporary file X2 and the sender information data X3, and therefore the risk of leakage of personal information can be reduced. Furthermore, the temporary file X2 can be encrypted to further reduce the risk of leakage of personal information.

  Further, the temporary file X2 is acquired regardless of whether or not the OS 21 has given the right. That is, the user terminal 2 can hold the latest address list data in the user terminal 2 even when the application 22 is not granted the right, and when the user 2 is further granted, the latest. Can be immediately registered in the sender information data X3. Thereby, the convenience of the user U is improved.

  Furthermore, the acquisition unit 221 can execute encryption processing on the temporary file X2. In this case, when registering the temporary file X2 in the sender information data X3, the registration unit 222 executes the decryption process of the encrypted temporary file X2. As a result, even when the application 22 has not been granted the right, the temporary file X2 can be held safely.

  When the user terminal 2 receives a call, the OS 21 searches the internal telephone directory Y1 stored in the user area Y and the caller information data X3 stored in the secret area X using the incoming call number as a key. That is, the OS 21 can acquire the sender data by searching only the inside of the user terminal 2 without communicating with the external device. Thus, the convenience of the user is improved because the caller information can be displayed on the user terminal 2 quickly when a call is received because the search process is excellent in real time.

  Furthermore, the OS 21 searches the internal telephone directory Y1 first when an incoming call is received. As a result, even when there is overlapping address data in the internal telephone directory Y1 and the caller information data X3, the caller information based on the internal telephone directory Y1 normally used by the user U is preferentially displayed. The convenience of the person is not impaired.

  Also, the caller information data X3 may have a larger capacity than the internal telephone directory Y1 and be able to store more address data. In this case, in the caller information display system 1, by storing a large number of address data in the caller information data X3, it is possible to provide the user U with an advanced service which can not be realized only by the internal telephone directory Y1. .

  In the present embodiment, the server device 3 sorts the address data selected from the address data D2 according to the browsing authority of the user U for each user U based on the sort order information iA. User U or the administrator of the address book, by arbitrarily setting sort order information iA, address data to be used preferentially even when a plurality of address data having overlapping telephone numbers are registered in the address data D2. Can be specified. Thereby, the convenience of the user U is improved.

  In the present embodiment, the OS 21 or the application 22 of the user terminal 2 may have a call history display function. In this case, as in the case of the caller information display process described in FIG. 10, the OS 21 or the application 22 refers to the caller information data X3 when there is no corresponding address data in the internal telephone directory Y1. You may get data about

  The present invention is not limited to the above embodiment as it is, and at the implementation stage, the constituent elements can be modified and embodied without departing from the scope of the invention. Further, various inventions can be formed by appropriate combinations of a plurality of constituent elements disclosed in the above embodiment. For example, some components may be reduced from all the components shown in the embodiment. Furthermore, components in different embodiments may be combined as appropriate.

  DESCRIPTION OF SYMBOLS 1 ... sender information display system, 2 ... user terminal, 2a ... 1st non-volatile memory, 2b, 3b ... processor, 2c ... 1st volatile memory, 2d, 3d ... communication apparatus, 2e ... display apparatus, 2f ... Input device, 2g ... Communication device, 3 ... Server device, 3a ... Second non-volatile memory, 3c ... Second volatile memory, 21 ... OS, 22 ... Application, 31 ... User identification unit, 32 ... Address Data management unit 33 Address list data generation unit 210 Incoming processing unit 211 Authorization unit 220 Authentication unit 221 Acquisition unit 222 Registration unit AD1 In-house address book AD2 Personal address AD, shared address book, D1: user data, D2: address data, N: network, P1, P2: program, R: rank information, T0: source telephone, U: interest Person, X ... secret area, X1 ... user data, X2 ... temporary file, X3 ... caller information data, Y ... user area, Y1 ... internal phone book.

The caller information display device according to the present embodiment is controlled by basic software, and a processor that executes an application program operating on the basic software, and an area for storing the basic software and the application program. And storage means including a hidden area to which the user can not access, and communication means for receiving an incoming call from a caller telephone. The application program includes means for storing data including a telephone number and name information corresponding to the telephone number in the secret area, the application program, a telephone number and name information included in the data, in the secret area. It functions as a means for registering the first caller data that is stored and can be retrieved by the basic software when the call is received and that the user can not access .

Claims (4)

A processor that is controlled by the basic software and executes an application program operating on the basic software;
An area for storing the basic software and the application program, and storage means including a hidden area;
A communication means for receiving an incoming call from the source telephone;
Equipped with
Means for storing, in the hidden area, data including the telephone number and name information corresponding to the telephone number in the application program;
A means for registering the telephone number and name information included in the data in the first caller data which is stored in the secret area and which can be searched by the basic software when the incoming call is received;
An originator information display device characterized in that it functions. The storage means further includes an open area accessible to the user, and the open area stores second caller data in which a telephone number and name information are registered according to a registration instruction of the user,
When the call is received from the caller telephone, the second caller data is searched based on the caller telephone number of the caller telephone, and the second caller data is searched for the caller telephone number Search means for searching the first caller data if the first caller data is not included;
Display means for displaying information on a caller when receiving the incoming call, and displaying name information corresponding to the caller telephone number when the first caller data includes the caller telephone number When,
The caller information display apparatus according to claim 1, further comprising: A program that is controlled by basic software of a computer and operates on the basic software,
The computer,
Storage means for storing data including a telephone number and name information corresponding to the telephone number in a secret area of the storage means provided in the computer;
A program for causing a telephone number and name information included in the data to be stored in the secret area and functioning as a registration means for registering the caller data that can be searched by the basic software when receiving an incoming call. The storage means encrypts the data;
The program according to claim 3, wherein the registration unit decrypts the encrypted data.

Images