Patent Description:
A nurse call system which enables telephone conversations between a nurse call extension unit and a portable terminal device carried by a medical worker such as a doctor and a nurse is known. The nurse call system includes a nurse call extension unit (call button), a nurse call base unit, a private branch exchange (PBX), and a Personal Handy-Phone System (PHS) terminal under control of the PBX. A nurse carries a PHS terminal and responds to a nurse call of a patient. When there is a nurse call, the PHS terminal displays a patient name and an extension number. In this case, the nurse can recognize where the call was made from and respond to it.

With the improvement of the radio wave environment of Wi-Fi, the linkage with electronic medical records, and the downsizing of the PHS business, there is an increasing demand for replacing PHS terminals, which are terminals carried by nurses, with smartphones and enabling nurses to respond to a nurse call using the smartphones. Further, there is a need for a medical worker to display an incoming call screen including patient information related to symptoms of a patient on a portable terminal device when an incoming call is received on the portable terminal device side. In this connection, Patent Literature <NUM> discloses a nurse call system in which a portable terminal device such as a smartphone is used.

In Patent Literature <NUM>, a patient calls a medical worker by pressing a call button provided on a nurse call extension unit. The nurse call extension unit outputs a call signal when a patient presses a call button. The nurse call controller identifies the nurse call extension unit in which the call button is depressed, and refers to the patient information table to acquire the patient name. The nurse call controller transmits the call signal and the patient name to the portable terminal device. The portable terminal device displays an incoming call screen including the extension number of the nurse call extension unit and the patient name on a display screen.

In Patent Literature <NUM>, an incoming call screen is generated by using a telephone directory server. The telephone directory server receives patient information of the patient who presses the call button. The telephone directory server associates the received patient information with an extension number and records it in a telephone directory table. The telephone directory server generates an incoming call screen on the basis of patient information recorded in a telephone directory table and records the incoming call screen. The incoming call screen includes a patient name, an extension number, a medical treatment subject, and a rescue category. The telephone directory server transmits URL (uniform resource locator) information accessible to the recorded incoming call screen to the portable terminal device. The mobile terminal device acquires the incoming call screen from the telephone directory server on the basis of the URL information, and displays the incoming call screen and the call screen in combination on a display screen.

In a normal environment, each extension number is often used fixedly by each user. Therefore, in the management of user information (name, e-mail address, etc.) in association with an extension number, there are few use cases in which the user information corresponding to each extension number is frequently changed. However, in the medical field, hospitalization, discharge from hospital, transfer to hospital room, etc. occur according to the situation of the patient. For this reason, the extension number cannot be used in a fixed manner.

In a nurse call system, if the combination of the caller's extension number and patient information is managed for each terminal and the information in the terminal is updated every time the combination is updated, it is necessary to update the information frequently in each terminal. Therefore, when a smartphone terminal is used as a nurse call receiving terminal, it is required, for the nurse call system, that the combination of the caller's extension number and patient information be changed irregularly and the patient information be updated and reflected immediately, as a system requirement. A system that satisfies this requirement can be realized by linking the nurse call terminal with the shared telephone directory linked with the nurse call base unit and the PBX.

Further, the nurse call receiving terminal is desired to have a function of displaying the patient information of the calling patient in response to the received nurse call. For example, when the patient information is displayed on the nurse call receiving terminal, the medical worker can recognize from which patient the nurse call is received and respond to it. In Patent Literature <NUM>, an incoming call screen is generated using a telephone directory server, and the portable terminal device acquires the incoming call screen from the telephone directory server at the time of an incoming call and displays it on a display unit. Thus, the work efficiency of the medical worker can be improved.

By the way, smartphones are divided into two main categories: the iPhone (registered trademark) sold by Apple and the Android (registered trademark) sold by various companies, which is compatible with OS (Operating System), the basic outline of which is regulated by Google. Of these two devices, iPhone devices are particularly in demand in the medical field.

When the iPhone device is used as a nurse call receiving terminal, a VoIP (Voice over Internet Protocol) application for making nurse call telephone conversations can be operated on the iPhone device. However, when the inventors examined the use of an iPhone device as a terminal for receiving a nurse call, the present inventors found that patient information cannot be freely displayed on the receiving screen due to restrictions of the OS.

In the iPhone device, a telephone function application is already installed in the OS, and incoming and outgoing calls of that application are controlled by "CallKit". A VoIP application (also referred to as a dedicated VoIP application) for making nurse call telephone conversations can use CallKit to control incoming and outgoing calls. However, when CallKit is used, the incoming call screen will be the CallKit call screen. CallKit has a restriction that the character information which can be displayed on the incoming call screen is limited. CallKit also has a restriction that the background color on the incoming call screen cannot be changed.

When a dedicated VoIP application does not use CallKit, an incoming call screen can be freely generated and patient information can be displayed on the incoming call screen when a nurse call arrives. However, without CallKit, if an incoming call occurs in the OS's phone function application during telephone conversations of a dedicated VoIP application, the OS's phone function application takes precedence and the telephone conversation are cut off. Further, when an incoming call is received during the security locking of the terminal, the user must first release the security lock, whereby usability is significantly reduced. Thus, the use of CallKit is essential for the operation of a dedicated VoIP application in order to manage conflicting operations with other telephone conversation applications and to respond to incoming calls when the terminal security is locked.

In Patent Literature <NUM>, a dedicated incoming call screen is displayed on a display unit, and thus a function (framework), such as CallKit, for managing conflicting operations with other telephone conversation application and receiving an incoming call during a terminal security lock cannot be used for receiving a nurse call. Therefore, there is a need for a mechanism that enables the display of patient information or the like while utilizing such a framework when receiving a nurse call.

In one aspect, the present disclosure aims to provide a portable terminal device, an incoming call screen display method, and a program capable of displaying information of a caller or the like when receiving a call even in a situation where a combination of a caller number and a caller can be changed.

In another aspect, the present disclosure aims to provide a portable terminal device, an incoming call history display method, and a program capable of correctly displaying information of a caller at the time of receiving a call in an incoming call history while information of a caller or the like can be displayed when receiving a call.

The present disclosure is defined by the independent claims. Dependent claims refer to preferred embodiments.

The present disclosure provides an incoming call screen display method carried out by a portable terminal device (<NUM>) configured to receive a telephone call and manage a telephone dictionary therein, and comprising a display, comprising the steps of:.

The present disclosure further provides a program causing a processor in a portable terminal device configured to receive a telephone call and manage a telephone dictionary (<NUM>, <NUM>, <NUM>) therein, and comprising a display, to execute:.

An incoming call screen display method, and a program according to the present disclosure can display information of a caller or the like when receiving a call even in a situation where a combination of a caller number and a caller can be changed.

Prior to escribing embodiments of the present disclosure, an outline of the present disclosure will be described. <FIG> shows a schematic configuration of a portable terminal device according to the present disclosure in one aspect. A portable terminal device <NUM> includes an incoming call signal reception means <NUM>, an image generation means <NUM>, a telephone directory registering means <NUM>, and an incoming call screen display means <NUM>. The incoming call signal reception means <NUM> receives an incoming call signal when there is a telephone incoming call. The incoming call signal includes a caller number, caller information, and ring type information.

The image generation means <NUM> generates a caller information image based on the incoming call signal received by the incoming call signal reception means <NUM>. The caller information image is an image including at least a portion of the caller information included in the incoming call signal as character information. The telephone directory registering means <NUM> generates caller text information based on at least one of the caller information and the ring type information included in the incoming call signal. The telephone directory registering means <NUM> registers the caller number included in the incoming call signal, the caller text information and the caller information image in a telephone directory <NUM> managed in the portable terminal device <NUM>.

The incoming call screen display means <NUM> receives a caller number, and acquires caller text information and a caller information image registered corresponding to the received caller number from the telephone directory <NUM>. The incoming call screen display means <NUM> displays an incoming call screen including the caller text information and the caller information image on the display screen of the portable terminal device to inform the user of the incoming call.

According to the present disclosure, the image generation means <NUM> generates the caller information image based on the incoming call signal. The telephone directory registering means <NUM> registers the caller text information and the caller information image in the telephone directory <NUM>. The incoming call screen display means <NUM> displays the caller text information and the caller information image on an incoming call screen. In the present disclosure, the information of the caller is displayed on the incoming call screen as image information. For example, when the portable terminal device <NUM> is used as a nurse call receiving terminal in a nurse call system, the combination of the caller number and the caller can be frequently changed. According to the present disclosure, even in such a situation, the information of the caller and the like can be displayed as image information when an incoming call is received, and the user who receives the incoming call can easily know who the incoming call is from.

Specifically, a case is considered in which the portable terminal device <NUM> is used as a nurse call receiving terminal, and iPhone manufactured by Apple is used for the portable terminal device <NUM>. When the nurse call terminal is not used for telephone conversations or the like, the nurse call terminal is applied to a security lock so that others cannot use it without permission. When the incoming nurse call is received during the security lock, nurse call applications must use CallKit to respond to incoming nurse calls without unlocking the security lock. In <FIG>, functions of the incoming call screen display means <NUM> corresponds to, for example, a portion of the functions provided by CallKit.

CallKit retrieves information stored in the telephone dictionary and displays the incoming call screen. Accordingly, in order to display information such as the name of the patient who made the nurse call on the nurse call receiving terminal, it is necessary to register the "caller number" and the "patient name" of the nurse call extension unit in the telephone directory application (Contacts) under the OS. "Contacts" correspond to the telephone directory <NUM> shown in <FIG>. However, the patient's room (bed) may be change frequently. In order to display the patient name on the nurse call receiving terminal, it is necessary to update the "caller number" and "patient name" registered in the "Contacts" of all nurse call receiving terminals carried by the medical workers each time the name is changed. In the present disclosure, the caller information image is generated using the caller information included in the incoming call signal, and is registered in the telephone directory <NUM>. Thus, information such as a patient name can be displayed on the nurse call receiving terminal without updating the "caller number" and "patient name" registered in the "Contacts" of all nurse call receiving terminals carried by the medical workers.

<FIG> shows a schematic configuration of a portable terminal device according to the present disclosure in another aspect. A portable terminal device <NUM> includes an incoming call signal reception means <NUM>, a telephone directory registering means <NUM>, an incoming call screen displaying means <NUM>, an incoming call history recording means <NUM>, and an incoming call history displaying means <NUM>. The incoming call signal reception means <NUM> receives an incoming call signal when there is a telephone incoming call. The incoming call signal includes a caller number, caller information, and ring type information.

The telephone directory registering means <NUM> generates caller text information based on at least one of the caller information and the ring type information included in the incoming call signal. The telephone directory registering means <NUM> registers the caller number included in the incoming call signal and the generated caller text information in a telephone directory <NUM> managed in the portable terminal device <NUM>.

The incoming call screen display means <NUM> receives a caller number and acquires caller text information registered corresponding to the received caller number from the telephone directory <NUM>. The incoming call screen display means <NUM> displays an incoming call screen including the caller text information on the display screen of the portable terminal device to inform the user of the incoming call.

The incoming call history recording means <NUM> associates the caller number which is a source of a call with the caller text information and records them in incoming call history information. The telephone directory registering means <NUM> deletes the registered caller number from the telephone directory after the incoming telephone call ends. The incoming call history display means <NUM> displays an incoming call history including a number of the incoming telephone call and a name of the caller. The incoming call history display means <NUM> acquires caller text information from the incoming call history information, and displays the acquired caller text information as a name of the caller when displaying the incoming call history.

According to the present disclosure, the telephone directory registering means <NUM> generates caller text information based on at least one of the caller information and the ring type information included in the incoming call signal, and registers the caller text information in the telephone directory <NUM>. The incoming call screen display means <NUM> displays caller text information on an incoming call screen. For example, when the portable terminal device <NUM> is used as a nurse call receiving terminal in a nurse call system, the combination of the caller number and the caller can be frequently changed. According to the present disclosure, even in such a situation, the information of the caller and the like can be displayed when an incoming call is received, and the user who receives the incoming call can easily know who the incoming call is from.

Further, according to the present disclosure, the telephone directory registering unit <NUM> deletes the registered caller number from the telephone directory <NUM> after the incoming telephone call ends. When the incoming call history is displayed, the incoming call history display means <NUM> acquires, from the incoming call history information, the caller text information registered by the incoming call history registering means <NUM>. The incoming call history display means <NUM> displays the acquired caller text information as the name of the caller. In this way, in the present disclosure, when the incoming call history is displayed, the information of the caller is acquired from the incoming call history information, not the information registered in the telephone directory. Thus, even in a situation where the combination of the caller number and the caller can be changed, information of the caller at the time of the incoming call can be correctly displayed in the incoming call history, while enabling information of the caller and the like to be displayed when an incoming call is received.

Specifically, a case is considered in which the portable terminal device <NUM> is used as a nurse call receiving terminal, and iPhone manufactured by Apple is used for the portable terminal device <NUM>. When the nurse call terminal is not used for telephone conversations or the like, the nurse call terminal is applied to a security lock so that others cannot use it without permission. When an incoming nurse call is received during the security lock, the nurse call application must use CallKit to respond to the incoming nurse call without unlocking the security lock. In <FIG>, functions of the incoming call screen display means <NUM> corresponds to, for example, a portion of the functions provided by CallKit.

CallKit retrieves information stored in the telephone dictionary and displays the incoming call screen. Accordingly, in order to display information such as the name of the patient who made the nurse call on the nurse call receiving terminal, it is necessary to register the "caller number" and the "patient name" of the nurse call extension unit in the telephone directory application (Contacts) under the OS. "Contacts" corresponds to the telephone directory <NUM> shown in <FIG>. However, the patient's room (bed) may be changed frequently. In order to display the patient name on the nurse call receiving terminal, it is necessary to update the "caller number" and "patient name" registered in the "Contacts" of all nurse call receiving terminals carried by the medical workers each time the name is changed. In the present disclosure, the caller text information is generated using the caller information included in the incoming call signal, and is registered in the telephone directory <NUM>. Thus, information such as a patient name can be displayed on the nurse call receiving terminal without updating the "caller number" and "patient name" registered in the "Contacts" of all nurse call receiving terminals carried by the medical workers.

The incoming call history (call history) information of the OS of iPhone has a restriction that, when the registered name registered in the telephone directory is changed, the display name of the past incoming call history stored in the history is also changed. For example, it is assumed that the called number "<NUM>" corresponds to the patient name "Tanaka" at a certain time point in the past. Thereafter, it is assumed that the patient name corresponding to the caller number "<NUM>" is changed to "Suzuki" due to the change of the hospital room, etc. When Mr. Suzuki calls the nurse call, a telephone directory registering means <NUM> registers the caller number "<NUM>" and the patient name "Suzuki" in a telephone directory <NUM> in association with each other. In this case, when the incoming call history is displayed, the display name of the incoming call history of the nurse call made by Mr. Tanaka in the past changes to "Suzuki". In this way, when the name (registered name) registered in the telephone directory is changed in iPhone, the display name of the past incoming call history stored in the history is also changed in association with the change. In that case, it would look as if the nurse call was made by Mr. Suzuki, even though it was Mr. Tanaka who made the nurse call in the past.

For the above problem, in the present disclosure, the telephone directory registering unit <NUM> deletes the registered caller number from the telephone directory <NUM> after a call ends. By doing so, in the telephone directory <NUM>, the correspondence between the caller number and the registered name (caller text information) is canceled. As for storing the incoming call history information, the incoming call history recording means <NUM> registers the caller text information in the incoming call history information using, for example, 'LocalizeCallerName'. The incoming call history display means <NUM> displays the caller text information registered in 'LocalizeCallerName' in the incoming call history information. Thus, even if the name registered for the same number in the telephone directory <NUM> is changed, the name of the caller at the time of the incoming call can be displayed in the incoming call history.

<FIG> shows a telephone system according to a first embodiment of the present disclosure. In the present embodiment, the telephone system is configured as a Nurse Call (NC) system. The NC system <NUM> includes NC extension units <NUM>, an NC base unit <NUM>, an NC controller <NUM>, a private branch exchange <NUM>, an access point <NUM>, and a portable terminal device <NUM>.

The NC extension unit <NUM> is a device used when a patient calls a medical worker. The NC extension unit <NUM> includes a call button, a speaker, a microphone, and the like. The NC extension unit <NUM> is arranged, for example, in a hospital room, each bed in the hospital room, a bathroom, a toilet, or the like. The NC extension unit <NUM> transmits a call signal to the nurse call controller <NUM> when the patient presses the call button. It should be noted that, although three NC extension units <NUM> are shown in <FIG>, the present disclosure is not limited thereto. The NC system <NUM> may include any number of NC extension units <NUM>.

The NC base unit <NUM> is installed at a nurse station or the like, and is configured to respond to a call from the NC extension unit <NUM>. The nurse call base unit <NUM> includes, for example, a handset for responding to a call, a small monitor for displaying patient information, and a large monitor for displaying detailed information about each patient as list. The NC extension unit <NUM> and the NC base unit <NUM> may be the same as the NC extension unit and the NC base unit used in a common NC system.

The private branch exchange <NUM> is a device for managing the call connection between the NC extension unit <NUM> and the portable terminal device <NUM> and the call connection between the NC base unit <NUM> and the portable terminal device <NUM>. The private branch exchange <NUM> is installed, for example, in a hospital. The access point <NUM> is connected to the private branch exchange <NUM> by wired communication and is connected to the portable terminal device <NUM> by wireless communication. The access point <NUM> includes a wireless transceiver, an antenna, and the like. The access point <NUM> are arranged, for example, at various places in the hospital. The portable terminal device <NUM> is registered in the private branch exchange <NUM>, and can transmit and receive a signal to and from the private branch exchange <NUM> through the access point <NUM>.

The NC controller <NUM> controls communication between the NC extension unit <NUM> and each device. For example, when a nurse call is transmitted from the NC extension unit <NUM>, the NC controller <NUM> controls communication between the NC extension unit <NUM> and the NC base unit <NUM>. Further, the NC controller <NUM> controls communication between the NC extension unit <NUM> and the portable terminal device <NUM>. The NC controller <NUM> may be integrated with the NC base unit <NUM>.

The NC controller <NUM> manages places where the NC extension units <NUM> are arranged. When the NC extension unit <NUM> is arranged at the bedside, the NC controller <NUM> manages which patient uses the NC extension unit <NUM>. When a nurse call is made from an NC extension unit <NUM>, the NC controller <NUM> identifies which NC extension unit <NUM> has made the call. Further, the NC controller <NUM> identifies the name of the patient (caller name) who made the nurse call and where the nurse call was made from.

When a nurse call is made, the NC controller <NUM> transmits an incoming call signal including a caller number (extension number), patient information (caller information), and ring type information to the portable terminal device <NUM>. The portable terminal device <NUM> receives the incoming call signal through the private branch exchange <NUM> and the access point <NUM>.

The patient information includes, for example, at least one of a patient name and information indicating the location where the nurse call is made from. The patient information may alternatively or additionally include information indicating a medical specialty of a patient. The ring type information includes information indicating that the call is for a nurse call (incoming nurse call). The NC controller <NUM> may change the ring type information according to the urgency of the nurse call. The NC controller <NUM> may determine the urgency of the nurse call based on, for example, the medical specialty of a patient and/or the location of the NC extension unit <NUM>.

<FIG> shows a logical configuration of the portable terminal device <NUM>. It is assumed that the portable terminal device <NUM> is an iPhone device manufactured by Apple. A VoIP application (hereinafter also referred to as a dedicated application) <NUM> supporting an incoming nurse call is installed in the portable terminal device <NUM>. In the portable terminal device <NUM>, the dedicated application <NUM>, CallKit <NUM> and the telephone directory <NUM> operate on an OS <NUM>. The portable terminal device <NUM> corresponds to the portable terminal device <NUM> shown in <FIG>.

The dedicated application <NUM> includes an NC incoming call processing unit <NUM>. The NC incoming call processing unit <NUM> includes an incoming call signal reception unit <NUM>, a registration data generation unit <NUM>, a telephone directory operating unit <NUM>, and a CallKit operating unit <NUM>. It should be noted that the dedicated application <NUM> also includes other functions (processing unit) such as a function for calling the NC extension unit <NUM> and the NC base unit <NUM>, although they are not shown in the drawing.

The incoming call signal reception unit <NUM> receives the incoming call signal transmitted from the NC controller <NUM> via the network interface (NW I/F) <NUM>. When the incoming call signal is the incoming call signal of the nurse call, the incoming call signal reception unit <NUM> sends, to the registration data generation unit <NUM>, the caller number, the patient information, and the ring type information included in the incoming call signal. The incoming call signal reception unit <NUM> corresponds to the incoming call signal reception means <NUM> shown <FIG>.

The registration data generation unit <NUM> generates registration data to be registered in the telephone directory <NUM> based on the information received from the incoming call signal reception unit <NUM>. Generating the registration data includes generating a patient information image (caller information image). The registration data generation unit <NUM> generates an image, as the patient information image, including at least a portion of patient information included in the incoming call signal as character information. The registration data generation unit <NUM> includes means corresponding to the image generation means <NUM> shown in <FIG>.

The registration data generation unit <NUM> may change the feature of the patient information image, for example, in accordance with the ring type information included in the incoming call signal. For example, the registration data generation unit <NUM> may generate a patient information image in a display color in accordance with the ring type information. For example, when the ring type information indicates that the urgency is low, the registration data generation unit <NUM> generates a patient information image, the background color of which is black. When the ring type information indicates that the urgency is high, the registration data generation unit <NUM> generates a patient information image, the background color of which is red. By doing so, the user who receives the nurse call can determine the degree of urgency based on the color of the image.

The telephone directory operating unit <NUM> operates registration data of the telephone directory (Contacts) <NUM>. In the telephone dictionary <NUM>, a set of a number, a name and an image can be registered. Further, in the telephone directory <NUM>, a ringtone can be individually set to each telephone directory data. The telephone directory operating unit <NUM> generates a text (caller text information) representing a name to be registered in the telephone directory based on at least one of the patient information and the ring type information. The telephone directory operating unit <NUM> refers to, for example, the patient information, and generates text information representing at least one of the patient name and the place where the nurse call made from as the caller text information. Alternatively, the telephone directory operating unit <NUM> may generate text information indicating the degree of urgency as the caller information with reference to the ring type information. The telephone directory operating unit <NUM> may generate text information in which the text information representing a patient name or the like and the text information representing urgency are combined as the caller text information.

The telephone directory operating unit <NUM> registers a caller number included in the incoming call signal in "number" of the telephone directory data. The telephone directory operating unit <NUM> registers the caller text information (string) generated based on at least one of the patient information and the ring type information in "name" of the telephone directory data. The telephone directory operating unit <NUM> registers the patient information image generated by the registration data generation unit <NUM> in "image" of the telephone directory data. The telephone directory operating unit <NUM> corresponds to the telephone directory registration means <NUM> shown in <FIG>.

The telephone directory operating unit <NUM> registers a plurality of templates of telephone directory data in the telephone directory <NUM>, for example, when the dedicated application <NUM> is started up for the first time. At this time, the telephone directory operating unit <NUM> registers a plurality of templates corresponding to each ring type information in the telephone directory <NUM>. The user sets the ringtone for each template by using a telephone dictionary application. The user can specify a sound source implemented in the portable terminal device <NUM> when setting the ringtone. "Sound source implemented in the portable terminal device <NUM>" refers to, for example, a sound source selectable as "ringtone" on an iPhone device. The user sets a ringtone for each template, whereby a ringtone is individually set to each template.

<FIG> shows an example of the ringtone setting. In this example, it is assumed that a template registered in the telephone dictionary <NUM> as telephone dictionary data of No. <NUM> corresponds to a template corresponding to ring type information "<NUM>". It is assumed that a template registered as telephone dictionary data of No. <NUM> corresponds to a template corresponding to ring type information "<NUM>". It is assumed that a template registered as telephone dictionary data of No. <NUM> corresponds to a template corresponding to ring type information "<NUM>". For example, the user sets "ringtone A" as the ringtone of the template corresponding to the ring type information "<NUM>". The user sets "ringtone B" as the ringtone of the template corresponding to the ring type information "<NUM>", and sets "ringtone C" as the ringtone of the template corresponding to the ring type information "<NUM>". It should be noted that the setting of the ringtone includes setting of the incoming call notification using a vibrator which does not actually sound.

The telephone directory operating unit <NUM> selects a template corresponding to the ring type information included in the incoming call signal from a plurality of templates, and registers the caller number, the caller text information and the patient information image in the selected template. For example, when the ring type information is "<NUM>", the telephone directory operating unit <NUM> selects the template registered as the telephone dictionary data of No. <NUM>. The telephone dictionary operating unit <NUM> registers the caller number, the caller text information and the patient information image in the telephone directory data of No. <NUM>. When the ring type information is "<NUM>", the telephone directory operating unit <NUM> selects the template registered as the telephone dictionary data of No. <NUM>. In this case, the telephone directory operating unit <NUM> registers the caller number, the caller text information and the patient information image in the telephone directory data of No. <NUM>. After the incoming nurse call ends, the telephone directory operating unit <NUM> may delete the registered information from the template in the telephone directory <NUM>. In this case, the template is initialized after the call ends.

The CallKit operating unit <NUM> notifies the CallKit <NUM> of the caller number and an incoming call after the telephone dictionary operating unit <NUM> registers information in the telephone dictionary <NUM>. The CallKit <NUM> is a framework that provides, in the OS <NUM>, a function for managing conflict between applications using the call function, a function for enabling an incoming call during a security lock, and a function for displaying an incoming screen. When an incoming call is notified, the CallKit <NUM> acquires the caller text information registered corresponding to the caller number and the caller image (patient information image) from the telephone directory <NUM>. Further, a ringtone set for the caller number is acquired. The CallKit <NUM> displays an incoming call screen including the acquired caller text information and the patient information image on the display screen through an external interface (external I/F) <NUM>. The CallKit <NUM> outputs the acquired ringtone from a speaker through an external I/F <NUM>.

<FIG> shows a display example of the incoming call screen. In an incoming call screen <NUM>, an area <NUM> is an area in which information (string) registered in "name" in the telephone directory <NUM> is displayed. The telephone directory operating unit <NUM> generates a character string in which, for example, a character string "nurse call", a bed number where a nurse call has been made from, a patient name, and the like are combined as the caller text information. The telephone directory operating unit <NUM> registers the generated caller text information in the "name" of the telephone directory <NUM>. If the number of characters of the caller text information exceeds the number of characters that can be displayed in the area <NUM>, the caller text information is scrolled and displayed in the area <NUM>.

In the incoming call screen <NUM>, an area <NUM> is an area in which an image registered as the caller image in the telephone directory <NUM> is displayed. The registration data generation unit <NUM> generates an image including a character string obtained by combining a character string "nurse call", a bed number where a nurse call has been made from, a patient name, and an extension number as the patient information image. The registration data generation unit <NUM> changes the background color in accordance with the ring type information in the generation of the patient information image. For example, the registration data generation unit <NUM> sets the background color of the patient information image to red when the ring type information indicates "high" urgency. The registration data generation unit <NUM> sets the background color of the patient information image to black when the ring type information indicates "low" urgency. The telephone directory operating unit <NUM> registers the patient information image generated by the registration data generation unit <NUM> in "image" of the telephone directory <NUM>.

Next, an operation procedure will be described. <FIG> shows an operation procedure (incoming call screen display method) in the portable terminal device <NUM> when a nurse call is received. When the call button of the NC extension unit <NUM> is operated, the NC controller <NUM> identifies the caller number, the patient information, and the ring type information, and transmits the information on them to the private branch exchange <NUM>. The private branch exchange <NUM> transmits an incoming call signal including the caller number, the patient information, and the ring type information as accompanying data to the portable terminal device <NUM> via the access point <NUM>.

The dedicated application <NUM> in the portable terminal device <NUM> receives an incoming call signal. The incoming call signal reception unit <NUM> of the NC incoming call processing unit <NUM> in the dedicated application <NUM> determines whether or not the incoming call signal indicates an incoming nurse call (Step S1). In step S1, the incoming call signal reception unit <NUM> determines whether or not the incoming call signal indicates an incoming nurse call based on the ring type information included in the incoming call signal. When the incoming call signal reception unit <NUM> determines that the incoming call signal does not indicate the incoming nurse call, the processing ends.

When the incoming call signal reception unit <NUM> determines in step S1 that the incoming call signal indicates the incoming nurse call, the incoming call signal reception unit <NUM> sends the caller number, the patient information, and the ring type information to the registration data generation unit <NUM>. The registration data generation unit <NUM> generates a patient information image based on the caller number, the patient information, and the ring type information (Step S2). In step S2, the registration data generation unit <NUM> generates, for example, an image in which the caller number and the patient information to be displayed are embedded as the patient information image. In the generation of the patient information image, the registration data generation unit <NUM> may change the characteristics of the image, such as the display color, according to the ring type information. In this case, the user can easily distinguish the ringing type visually.

The telephone directory operating unit <NUM> generates caller text information based on at least one of the patient information and the ring type information (Step S3). In step S3, the telephone directory operating unit <NUM> generates, for example, data (string) obtained by combining the patient name and the urgency level as the caller text information. The telephone directory operating unit <NUM> may include the caller number in the caller text information.

The telephone directory operating unit <NUM> associates the patient information image generated in step S2 and the caller text information generated in step S3 with the caller number and registered them in the telephone directory <NUM> (Step S4). In step S4, the telephone directory operating unit <NUM> selects a template corresponding to the ring type information included in the incoming call signal from among the plurality of templates. The telephone directory operating unit <NUM> registers the caller text information in "name" of the selected template, and registers the patient information image in "image".

The CallKit operating unit <NUM> notifies the CallKit <NUM> of the caller number after the registration in the telephone dictionary <NUM> is completed (Step S5). The CallKit <NUM> acquires data of "name" and "image" corresponding to the notified incoming call number from the telephone directory <NUM>, and displays an incoming call screen (Step S6). In step S6, the CallKit <NUM> acquires the caller text information and the patient information image registered in step S4 from the telephone directory <NUM>, and displays them on the incoming call screen (See <FIG>). Further, the CallKit <NUM> acquires a ringtone setting corresponding to the telephone dictionary data (See also <FIG>). The CallKit <NUM> sounds a ringtone for the incoming calls set in the ringtone settings.

According to the present embodiment, the registration data generation unit <NUM> generates a patient information image to be registered in the telephone directory <NUM> based on the patient information included in the incoming call signal. The telephone directory operating unit <NUM> generates caller text information and registers the caller text information and the patient information image in the telephone directory <NUM>. The CallKit <NUM> acquires the caller text information and the patient information image from the telephone directory <NUM>, and displays the caller text information and the patient information image on an incoming call screen. In this way, patient information can be displayed on the incoming call screen for the nurse call while using the CallKit <NUM>. In the present embodiment, even in a system in which a combination of information such as a caller number and a patient name is frequently changed, the information displayed on the incoming call screen can be dynamically changed without updating the registration information in all terminals.

In the incoming call screen <NUM> (See <FIG>), although the caller text information is displayed in the area <NUM>, characters that can be displayed in the area <NUM> are limited. In present embodiment, the patient information is displayed as image information in the area <NUM> on the incoming call screen <NUM>. Thus, more information can be presented to the user. For example, in the present embodiment, even when the amount of information in the patient information image is large, the information can be displayed on the incoming call screen without scrolling. Therefore, the user can obtain the desired information without waiting for the end of the scroll. Further, in the present embodiment, the display color of the patient information image displayed in the area <NUM> can be changed according to the ring type information. In this case, the user can recognize, by the display color, which ring type information the incoming nurse call corresponds to.

In the present embodiment, templates each corresponding to the ring type information are prepared in the telephone directory <NUM>. In the telephone directory <NUM>, a ringtone can be individually set to each template. The telephone directory operating unit <NUM> registers the caller text information and the patient information image in a template corresponding to the ring type information included in the incoming call signal. The CallKit <NUM> has a restriction that when the system ringtone of an iPhone device is used as a VoIP ringtone, only the ringtone set in the telephone dictionary data in association with the caller number can be sounded. In the present embodiment, as described above, receiving incoming calls using the CallKit <NUM> can be realized, and switching ringtones according to the ring type information can be realized.

Next, a second embodiment of the present disclosure will be described. <FIG> shows a logical configuration of a portable terminal device according to a second embodiment of the present disclosure. In the present embodiment, it is assumed that the portable terminal device <NUM> is an iPhone device manufactured by Apple. The portable terminal device <NUM> includes an incoming call history recording unit <NUM>, incoming call history information <NUM>, and an incoming call history display unit <NUM> in addition to the logical configuration of the portable terminal device <NUM> in the first embodiment shown in <FIG>. The incoming call history recording unit <NUM> is included in the NC incoming call processing unit <NUM> included in the dedicated application <NUM>. The incoming call history information <NUM> and the incoming call history display unit <NUM> operate on the OS <NUM>.

In the present embodiment, the portable terminal device <NUM> corresponds to the portable terminal device <NUM> shown in <FIG>. The incoming call signal reception unit <NUM> corresponds to the incoming call signal reception means <NUM> shown in <FIG>. The telephone directory operating unit <NUM> corresponds to the telephone directory registration means <NUM> shown in <FIG>. The telephone directory <NUM> corresponds to the telephone directory <NUM> shown in <FIG>. The incoming call history recording unit <NUM> corresponds to the incoming call history recording means <NUM> shown in <FIG>. The incoming call history display unit <NUM> corresponds to the incoming call history display means <NUM> shown in <FIG>. Some of the functions provided by the CallKit <NUM> include the functions of the incoming screen display means <NUM> shown in <FIG>. The operations of the incoming call signal reception unit <NUM>, the registration data generation unit <NUM>, the CallKit operating unit <NUM>, and the CallKit <NUM> may be the same as those described in the first embodiment.

In addition to the operation described in the first embodiment, the telephone directory operating unit <NUM> deletes the registered caller number from the telephone directory <NUM> after the call ends. The telephone directory operating unit <NUM> deletes, for example, a record (e.g., a set of a number, a names, and an image) corresponding to the registered caller number from the telephone directory <NUM>, thereby deleting the caller number from the telephone directory <NUM>. Alternatively, the telephone directory operating unit <NUM> may delete the caller number from the telephone directory <NUM> by initializing the telephone directory <NUM>.

The incoming call history recording unit <NUM> associates the caller number with the caller text information generated by the telephone dictionary operating unit <NUM> and stores them in the incoming call history information <NUM>. The incoming call history information <NUM> includes, for example, an incoming call number (number of the source of the call), LocalizeCallerName, and an incoming call date and time. The incoming call history recording unit <NUM> records the caller number in the incoming call number and records the caller text information in LocalizeCallerName. The incoming call history recording unit <NUM> records the date and time of the incoming call in the incoming call date and time. For example, the incoming call history recording unit <NUM> records the caller number and the caller text information in the incoming call history information <NUM> each time the incoming call signal reception unit <NUM> receives an incoming call signal. The incoming call history information <NUM> may include not only the incoming call history of the dedicated application <NUM> but also the incoming call history of other applications in the mobile terminal device <NUM> such as a telephone application.

The incoming call history display unit <NUM> displays the incoming call history when the user performs an operation for displaying the incoming call history. The incoming call history display unit <NUM> displays the incoming call history on a display screen through an external I/F <NUM>. In the present embodiment, it is assumed that the user performs an operation for displaying the incoming call history after the telephone directory operating unit <NUM> deletes the caller number from the telephone directory <NUM> after the call ends. The incoming call history display unit <NUM> acquires caller text information from the incoming call history information <NUM>, and displays the caller text information acquired from the incoming call history information <NUM> as a name of a caller in the display of the incoming call history.

More specifically, when the user performs an operation for displaying the incoming call history, the incoming call history display unit <NUM> determines whether or not the incoming call number recorded in the incoming call history information <NUM> is registered in the telephone directory <NUM>. When the incoming call number is not registered in the telephone directory <NUM>, the incoming call history display unit <NUM> acquires the caller text information recorded in the LocalizeCallerName from the incoming call history information <NUM>. The incoming call history display unit <NUM> displays the caller text information acquired from the incoming call history information <NUM> as the name of the caller. On the other hand, when the incoming call number is registered in the telephone directory <NUM>, the incoming call history display unit <NUM> acquires name information stored in association with the incoming call number. The incoming call history display unit <NUM> displays the name information acquired from the telephone directory <NUM> as the name of the caller.

Here, a case is considered in which the telephone directory operating unit <NUM> does not delete the caller number from the telephone directory <NUM> after the call ends, and the incoming call history recording unit <NUM> does not record the caller text information in LocalizeCallerName. <FIG> shows an incoming call history display in a certain situation. In <FIG>, "history number" indicates the number for identifying the incoming call history, and "caller number" indicates the number of the source of a call (caller number). "Display name" indicates the name displayed in the incoming call history, and "incoming time" indicates the date and time of the incoming call. In this situation, it is assumed that the caller number "<NUM>" corresponds to "Tanaka". When there is an incoming call from the caller number "<NUM>", the telephone directory operating unit <NUM> registers the name "Tanaka" corresponding to the number "<NUM>" in the telephone directory <NUM>. The incoming call history display unit <NUM> acquires the name "Tanaka" from the telephone directory <NUM> in the display of the incoming call history, and displays "Tanaka" for the incoming call number "<NUM>" in the display of the incoming call history. The user of the portable terminal device <NUM> can know that the incoming calls of the history numbers "<NUM>" and"<NUM>" are the incoming calls from "Tanaka" by referring to the incoming call history.

<FIG> shows an incoming call history display in another situation. In this situation, for example, a case is considered in which "Tanaka" is discharged from a hospital and a bed (hospital room) which was used by "Tanaka" is used by "Suzuki". In this situation, when there is an incoming call from the caller number "<NUM>", the telephone directory operating unit <NUM> registers the name "Suzuki" in the telephone directory <NUM> corresponding to the number "<NUM>". In the display of the incoming call history, the incoming call history display unit <NUM> acquires the name "Suzuki" from the telephone directory <NUM>, and displays "Suzuki" for the received call number "<NUM>" in the incoming call history. In this case, along with the change of the registered name in the telephone directory <NUM>, not only the display name of the history number "<NUM>" becomes "Suzuki" but also the display names of the history numbers "<NUM>" and "<NUM>" become "Suzuki". In this case, the incoming calls of the history numbers "<NUM>" and"<NUM>", which are actually the incoming calls from the "Tanaka", are all seen as the incoming calls from "Suzuki" in association with the registered contents of the telephone directory <NUM>.

To solve the above problem, in the present embodiment, the telephone directory operating unit <NUM> deletes the caller number from the telephone directory <NUM> after the call. Further, the incoming call history recording unit <NUM> records the caller text information in LocalizeCallerName in the incoming call history information <NUM>. By doing so, the display of the information recorded in the LocalizeCallerName is enabled in the display of the incoming call history, and the name of the caller at the time of receiving the call can be displayed in the incoming call history.

<FIG> shows an incoming call history display in the present embodiment. The incoming call history recording unit <NUM> records "Tanaka" in the LocalizeCallerName of the incoming call history information <NUM> when the calls of the history numbers "<NUM>" and "<NUM>" are received. When the call of the history number "<NUM>" is received, the incoming call history recording unit <NUM> records "Suzuki" in the LocalizeCallerName of the incoming call history information <NUM>.

In the present embodiment, the telephone directory operating unit <NUM> deletes the caller number in the telephone directory <NUM> after the call is received (for example, after the call ends). Accordingly, when the user performs an operation for displaying the incoming call history after the incoming call of the history number "<NUM>" ends, the information of the caller number "<NUM>" of the incoming call received by the dedicated application <NUM> is not registered in the telephone directory <NUM>. Therefore, the incoming call history display unit <NUM> displays the caller text information recorded in LocalizeCallerName in the incoming call history. In this way, with respect to the same called number "<NUM>", "Tanaka" can be displayed in the incoming call history for the history numbers "<NUM>" and "<NUM>", and "Suzuki" can be displayed in the incoming call history for the history number "<NUM>".

Next, an operation procedure in the present embodiment will be described. <FIG> shows an operation procedure of the portable terminal device <NUM> including an incoming call history display method. When the call button of the NC extension unit <NUM> (See <FIG>) is operated, the NC controller <NUM> identifies the caller number, the patient information, and the ring type information, and transmits the information on them to the private branch exchange <NUM>. The private branch exchange <NUM> transmits an incoming call signal including the caller number, the patient information, and the ring type information as accompanying data to the portable terminal device <NUM> via the access point <NUM>.

The dedicated application <NUM> in the portable terminal device <NUM> receives an incoming call signal. The incoming call signal reception unit <NUM> of the NC incoming call processing unit <NUM> in the dedicated application <NUM> determines whether or not the incoming call signal indicates an incoming nurse call (Step S101). In step S101, the incoming call signal reception unit <NUM> determines whether or not the incoming call signal indicates an incoming nurse call based on the ring type information included in the incoming call signal. When the incoming call signal reception unit <NUM> determines that the incoming call signal does not indicate the incoming nurse call, the processing ends.

When the incoming call reception unit <NUM> determines in step S101 that the incoming call signal indicates the nurse call incoming call, the incoming call signal reception unit <NUM> sends the caller number, the patient information, and the ring type information to the registration data generation unit <NUM>. The registration data generation unit <NUM> generates a patient information image based on the caller number, the patient information, and the ring type information (Step S102). The telephone directory operating unit <NUM> generates caller text information based on at least one of the patient information and the ring type information (Step S103). The telephone directory operating unit <NUM> associates the patient information image generated in step S102 and the caller text information generated in step S103 with the caller number and registers them in the telephone directory <NUM> (Step S104).

The CallKit operating unit <NUM> notifies the CallKit <NUM> of the caller number after the registration in the telephone dictionary <NUM> is completed (Step S105). The CallKit <NUM> acquires data of "name" and "image" corresponding to the notified incoming call number from the telephone directory <NUM>, and displays an incoming screen (Step S106). Steps <NUM> to <NUM> may the same as Steps S1 to S6 shown in <FIG>.

The incoming call history recording unit <NUM> records caller text information in LocalizeCallerName of the incoming call history information <NUM> in association with the incoming call number (Step S107). The incoming call history recording unit <NUM> records, for example, the caller text information generated in step S103 in the LocalizeCallerName. After the call ends, the telephone directory operating unit <NUM> deletes the caller number from the telephone directory <NUM> (Step S108). In step S108, the telephone directory operating unit <NUM> deletes, for example, the caller number, the caller image, and the caller text information registered in Step S104 from the telephone directory <NUM>.

When the user performs an operation for displaying the incoming call history, the incoming call history display unit <NUM> acquires caller text information from the LocalizeCallerName of the incoming call history information <NUM> (Step S109). The incoming call history display unit <NUM> displays the incoming call history including the caller number of the call received by the dedicated application <NUM> and the caller text information acquired from LocalizeCallerName (Step S110).

According to the present embodiment, the incoming call history recording unit <NUM> records the caller text information in the LocalizeCallerName of the incoming call history information <NUM>. The telephone directory operating unit <NUM> deletes the caller number from the telephone directory <NUM> after the incoming call is received. The data (caller text information) generated when the call is received is recoded in the LocalizeCallerName and the caller number in the telephone dictionary <NUM> is deleted after the call is received, whereby the display of the information recorded in the LocalizeCallerName is enabled in the display of the incoming call history. In this way, even when the registered contents of the telephone directory <NUM> are changed at the time of receiving an incoming call with respect to a certain number, the name of the caller at the time of receiving an incoming call can be correctly displayed in the incoming call history. Other advantageous effects are the same as those in the first embodiment.

Next, the physical configuration of the portable terminal device <NUM> will be described. <FIG> shows the physical configuration of the portable terminal device <NUM>. The portable terminal device <NUM> includes a processor <NUM>, a storage unit <NUM>, a ROM (Read Only Memory) <NUM>, a RAM (Random Access Memory) <NUM>, a communication interface (IF) <NUM>, a user interface <NUM>, a microphone <NUM>, and a speaker <NUM>.

The communication interface <NUM> is an interface for connecting the access point <NUM> (See <FIG>) to the portable terminal device <NUM> via the wireless communications. The portable terminal device <NUM> receives the incoming call signal from the private branch exchange <NUM> via the communication interface <NUM>. The user interface <NUM> includes, for example, a display device such as a display. The display device is configured as a touch panel and also serves as an input unit. The microphone <NUM> and the speaker <NUM> are used in telephone conversation. The speaker <NUM> is also used for sounding the ringtone.

The storage unit <NUM> stores various data. The ROM <NUM> is a nonvolatile memory device. The semiconductor memory device having a relatively small capacity such as a flash memory is used as the ROM <NUM>. The program executed by the processor <NUM> may be stored in the storage unit <NUM> or the ROM <NUM>.

The above-described program(s) can be stored and provided to the portable terminal device <NUM> using any type of non-transitory computer readable media. Non-transitory computer readable media include any type of tangible storage media. Examples of non-transitory computer readable media include magnetic storage media (such as floppy disks, magnetic tapes, hard disk drives, etc.), optical magnetic storage media (e.g., magneto-optical disks), optical disk media (such as CDs (compact discs) DVDs (digital versatile disks), etc.), and semiconductor memories (such as mask ROM, PROM (programmable ROM), EPROM (erasable PROM), flash ROM, RAM, etc.). Further, the program(s) may be provided to a computer using any type of transitory computer readable media. Examples of transitory computer readable media include electrical signals, optical signals, and electromagnetic waves. Transitory computer readable media can provide the program(s) to a computer via a wired communication line (e.g., electric wires, and optical fibers) or a wireless communication line.

The RAM <NUM> is a volatile memory device. For the RAM <NUM>, various semiconductor memory devices such as DRAM (Dynamic Random Access Memory) or SRAM (Static Random Access Memory) are used. The RAM <NUM> can be used as an internal buffer for temporarily storing data or the like. The processor <NUM> develops a program stored in the storage unit <NUM> or the ROM <NUM> in the RAM <NUM> and execute the program. The processor <NUM> executes programs, whereby functions such as the dedicated application <NUM> and the CallKit <NUM> shown in <FIG> are realized.

It should be noted that, although an example in which the present disclosure is applied to a nurse call is described in each of the above embodiments, the present disclosure is not limited thereto. The present disclosure can be applied to various telephone systems other than nurse calls. Further, in each of the above embodiments, an example in which the incoming call is an incoming call from an extension telephone such as a nurse call is described. However, the present disclosure is not limited to the extension telephone. The present disclosure can be applied to an incoming call from an outside line telephone as long as the caller information is included in the incoming call signal.

In the second embodiment, an example in which the caller text information registered in the telephone directory <NUM> is the same as the caller text information recorded in the incoming call history information <NUM> (LocalizeCallerName) is described. However, the present disclosure is not limited thereto. In the second embodiment, the name (caller text information) recorded in the incoming call history information <NUM> may be any information that can identify the caller, and the registered name registered in the telephone directory <NUM> may be different from the name recorded in the incoming call history information <NUM>.

In the second embodiment, an example in which the registration data generation unit <NUM> generates a patient information image and the patient information image is displayed on the incoming call screen is described. However, the present disclosure is not limited thereto. For example, the generation of the patient information image may be omitted. In this case, the telephone directory operating unit <NUM> may register the caller number and the caller text information in the telephone directory <NUM>. Even in this case, since the character string (caller text information) registered in the "name" of the telephone directory <NUM> is displayed in the area <NUM> of the incoming call screen <NUM> (See <FIG>), the user of the portable terminal device <NUM> can know to some extent who the incoming call is from.

Claim 1:
An incoming call screen display method carried out by a portable terminal device (<NUM>) configured to receive a telephone call and manage a telephone dictionary therein, and comprising a display, comprising steps of:
receiving an incoming call signal including a caller number, caller information, and ring type information when an incoming telephone call is received, and generating, using the received incoming call signal, a caller information image including at least a portion of the caller information included in the incoming call signal as character information;
generating caller text information using at least one of the caller information and the ring type information included in the received incoming call signal;
registering the caller number, the generated caller text information, and the generated caller information image in the telephone dictionary (<NUM>, <NUM>, <NUM>);
acquiring the registered caller text information and the caller information image corresponding to the caller number from the telephone dictionary (<NUM>, <NUM>, <NUM>); and
displaying an incoming call screen including the caller text information and the caller information image.