JP4853290B2 - Telephone, communication system using the same, and call history registration / display method used therefor - Google Patents

Description

  The present invention relates to a telephone set, a communication system using the telephone set, and an outgoing / incoming call history registration / display method used therefor, and more particularly to registration and display of outgoing call history and incoming call history and redial in the telephone.

  In recent years, VoIP (Voice over IP) telephones that use IP (Internet Protocol) instead of circuit-switched telephone calls have become widespread (see, for example, Patent Documents 1 and 2).

  A telephone that performs call control using this SIP (Session Initiation Protocol) uses an address format [SIP URI (Universal Resource Identifier) to uniquely identify a terminal instead of a telephone number, but a SIP URI is a telephone number. Unlike the user part, it consists of a user part and a host part.

JP 2006-014092 A JP 2004-235755 A

  However, the conventional telephone recognizes that the user makes a call by telephone number (user part) by convention, and does not recognize the host part. This is because the telephone number entered by the user in the SIP telephone is used as the SIP URI, and when only the user part is entered in the actual call, the telephone makes a call by complementing the host part. It is.

  In addition, the telephone has a function that allows the phone to be reused by storing a call history and registering it in the telephone directory or making a call again. Also, it is common practice to search for the number registered in the phone book function from the phone number notified at the time of incoming call, display the registered name, or refer to the display name of outgoing or incoming call history. ing.

  Here, in the VoIP phone, there is a difference between the outgoing call made by the user and the outgoing / incoming call history actually made by the telephone. When the user refers to or uses the incoming / outgoing call history, There is a sense of incongruity in the difference between the operation and the display on the device.

  SUMMARY OF THE INVENTION Accordingly, an object of the present invention is to solve the above-mentioned problems and to make a VoIP telephone call / call history the same display as a circuit-switched call, a communication system using the same, and a call / call history registration / To provide a display method.

A telephone according to the present invention uses a VoIP (Voice over Internet Protocol) that performs call control using a SIP (Session Initiation Protocol) URI (Universal Resource Identifier) comprising a user part and a host part, and the user part is used for outgoing calls. A phone that complements the host part when making a call ,
Display processing means for controlling the presence or absence of display of the host unit according to the user's selection setting ,
The user's selection setting is a host part valid setting for setting whether to validate the host part,
The display processing means switches display contents of the outgoing / incoming call history according to the host unit valid setting .

  A communication system according to the present invention includes the telephone set described above.

The call history registration / display method according to the present invention uses VoIP (Voice over Internet Protocol) that performs call control using a SIP (Session Initiation Protocol) URI (Universal Resource Identifier) consisting of a user part and a host part. The call history registration / display method used for a telephone that makes a call by complementing the host part when only the user part is input in outgoing call,
The telephone executes a display process for controlling presence or absence of display of the host unit according to a user's selection setting ,
The user's selection setting is a host part valid setting for setting whether to validate the host part,
In the display processing, the telephone switches display contents of the outgoing / incoming history according to the host unit valid setting .

  That is, the telephone of the present invention is a VoIP (Voice over IP) by controlling whether or not the host part of the URI (Universal Resource Identifier) is displayed in a telephone using IP (Internet Protocol) according to a user's selection setting. ) The present invention is characterized in that the display operation of the call origination / reception history and the redial function is realized in the same manner as a conventional telephone.

  More specifically, the telephone of the present invention uses SIP to perform call control and uses an address format to uniquely identify a terminal instead of a telephone number. A “host part valid setting” menu is added to set whether or not to enable the URI host part when setting the URL. The display processing unit switches the screen display or the like depending on whether this “host unit valid setting” is ON (valid) / OFF (invalid).

  The apparatus operation at the time of VoIP outgoing / incoming call and telephone call is an operation that handles only the user part when the “host part valid setting” is set to OFF (invalid) (the host part is invalidated). However, the host part is also stored in the VoIP history regardless of the ON (valid) / OFF (invalid) setting of the “host part valid setting”. Only the contents displayed on the screen are switched here.

  At the time of VoIP transmission, the contents displayed on the display unit at the time of transmission are stored. When registering a history of incoming VoIP calls, the history is stored in the SIP URI format [user section @host section].

  The redial and outgoing call history store character strings for digit input and SIP address input display. However, if you make a call by supplementing the current domain name of the current profile, save up to your own domain.

  As described above, in the telephone of the present invention, it is possible to realize a display operation similar to that of a conventional telephone in a VoIP telephone by switching the display of the URI host part in accordance with the setting from the user.

  By adopting the above-described configuration and operation, the present invention provides an effect that the VoIP telephone call / incoming history can be displayed in the same way as a circuit-switched call.

  Next, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing a configuration of a communication system according to an embodiment of the present invention. In FIG. 1, a communication system according to an embodiment of the present invention performs an external line call using a public line network (hereinafter referred to as a public network), and performs an internal line call using VoIP (Voice over Internet Protocol). A mobile phone 1-1 to 1-3, an access point (AP) 2, a server 3, fixed telephones 4-1, 4-2, gateways 5-1, 5-2, and an exchange 6; -1,6-2, RNC (Radio Network Controller) 7, and base station 8.

  The access point 2 and the server 3 are arranged in an extension telephone network [for example, a wireless LAN (Local Area Network)] 100, the exchanges 6-1 and 6-2 are arranged in the public network 200, the RNC 7 and the base station 8 is disposed in the mobile phone network 300.

  The access point 2 and the server 3 provide an extension call service using VoIP to the cellular phones 1-1, 1-2 and the fixed phone 4-1 in the extension telephone network 100. The server 3 uses the gateways 5-1 and 5-2, the exchanges 6-1 and 6-2, the RNC 7, and the base station 8 to use the mobile phones 1-1 and 1-2 in the public network 200 and the mobile phone network 300. And provide an outside line call service to the fixed telephone 4-1.

  FIG. 2 is a block diagram showing the configuration of a mobile phone according to an embodiment of the present invention. In FIG. 2, a mobile phone 1 according to an embodiment of the present invention includes a wireless LAN antenna 10, a mobile phone antenna 11, a control unit 12, a memory 13, a wireless LAN radio unit 14, and a mobile phone radio. A unit 15, an operation unit 16, and a display unit 17 are provided.

  Here, the control unit 12 includes a wireless LAN wireless unit 14, a mobile phone wireless unit 15, an outgoing / incoming command reception processing unit 121 that performs an incoming / outgoing command reception process input via the operation unit 16, and a wireless LAN wireless unit 14. And a calling / calling processing unit 122 for performing calling / calling processing through the mobile phone radio unit 15, and a calling / calling number registration processing unit for registering the calling / calling number (extension number, telephone number, etc.) used in the calling / calling processing unit 122 in the memory 13. 123 and a display processing unit 124 that performs display processing on the display unit 17.

  The memory 13 includes a telephone directory data storage unit 131 that stores telephone directory data, and an outgoing / incoming history data storage unit 132 that stores outgoing / incoming call history data such as outgoing / incoming numbers registered by the outgoing / incoming number registration processing unit 123. ing.

  1 has the same configuration as that of the mobile phone 1 shown in FIG. In the following description, the cellular phone 1 will be described, but this embodiment can also be applied to the fixed phone 4-1.

  In this embodiment, the mobile phone 1 performs call control using SIP (Session Initiation Protocol), and uses an address format [SIP URI (Universal Resource Identifier) to uniquely identify a terminal instead of a telephone number. Yes. Here, unlike the telephone number, the SIP URI is composed of a user part and a host part. Therefore, in the mobile phone 1 described above, when the display of the mobile phone 1 is set in the display processing unit 124. Added the "Host part valid setting" menu. The display processing unit 124 switches the screen display or the like depending on whether the “host unit valid setting” is ON (valid) / OFF (invalid).

  At the time of VoIP outgoing / incoming call or call at the outgoing / incoming call processing unit 122, the operation is handled only for the user part when the “host part valid setting” is set to OFF (invalid) (the host part is invalidated). However, the host part is also stored in the VoIP history regardless of the ON (valid) / OFF (invalid) setting of the “host part valid setting”. Only the contents displayed on the screen are switched here.

  At the time of VoIP outgoing call in the outgoing / incoming call processing part 122, the contents displayed on the display part 17 at the time of outgoing call are stored. When a VoIP incoming call history is registered in the outgoing / incoming call history data storage unit 132, the history is saved in the SIP URI format [user (host) @host (host)].

  The redial and outgoing call history of the outgoing / incoming call history data storage unit 132 stores character strings for digit input and SIP address input display. However, if you make a call by supplementing the current domain name of the current profile, save up to your own domain. For example, when “host part valid setting” is set to OFF (invalid), when a call is made with “09012345678@sip.com”, the display content of the outgoing call history is “09012345678”, but the saved content of the history is “09012345678”. @ Sip.com ”.

In this embodiment, since the “host part valid setting” menu is added to the display processing unit 124, the “host part valid setting” set in the “host part valid setting” menu is turned ON (enabled) / OFF (disabled). )
・ Display contents of VoIP history (including name display)
・ VoIP call from VoIP history ・ Phone book registration from VoIP history ・ Incoming / outgoing VoIP, display contents during call (including name display)
・ Display contents of message memo (including name display)
-Messenger name display (transmission / reception BOX etc)
The functional operation of the mobile phone 1 is changed.

  A terminal such as the cellular phone 1 refers to the telephone book data registered in the terminal at the time of outgoing / incoming call, and simultaneously displays the name registered in the telephone book on the same screen together with the telephone number and SIP URI.

  FIG. 3 shows the search priority of name display by referring to the telephone directory performed when the mobile phone 1 makes / receives calls. In FIG. 3, at the time of outgoing / incoming of the public network 200, the phone book data storage unit 131 is searched by the operation when the “host part valid setting” at the time of incoming / outgoing VoIP is set to OFF (invalid). When the VoIP call with the user = phone parameter specified is received, the phone book data storage unit 131 is searched by the operation when the “host unit valid setting” is set to OFF (invalid). However, it is handled as a telephone number only when the local user = phone parameter setting of the WLAN (Wireless Local Area Network) profile is ON (valid), and when it is OFF (invalid), it is handled as a SIP address.

  If “Host part valid setting” is set to OFF (invalid) and the phonebook search field is “phone number”, “phonebook phone number” and “calling / receiving data” (calling / receiving data is SIP address) In this case, if the search character string matches only the user part), the search priority is given first. Incidentally, the collation with the telephone number of the telephone directory is equivalent to the telephone directory search in the public network.

  However, the telephone number reference is prioritized only when an external line is received in the case of a VoIP call on a basic extension or an extension. In addition, the priority of the telephone number reference is also targeted when a PWLAN is received. When calling / receiving VoIP, if the outgoing / incoming data includes characters other than digits, +, and p (pause) (such as English letters including p (characters)), the telephone number column is not searched.

  If “Host part valid setting” is set to OFF (invalid) and the search field of the phone book search is “SIP address”, “SIP address of phone book” and “calling / receiving data” (calling / receiving data is SIP address) If the search character string matches only with the user part), the search priority is second and "the user part of the SIP address in the phone book" and "the outgoing / incoming data" (the outgoing / incoming data is the SIP address) In this case, if the search character string matches only the user part), the search priority is set to the third.

  When a PWLAN call is received or a VoIP external line call is received at a basic extension or an extension, if the head of the incoming data is “0” in each search, the search is performed again except for “0” at the head of the incoming data.

  In the above telephone number reference priority, when “0xxxx” is received, the telephone number reference priority is “complete match”> “1840xxxx”> “1860xxxx”> “# 31 # 0xxxx”> “* 31 # 0xxxx”> “ + 81xxxx ”, and the priority of the telephone number reference when receiving“ + 81xxxx ”is complete match>“ 0xxxx ”>“ 1840xxxx ”>“ 1860xxxx ”>“ # 31 # 0xxxx ”>“ * 31 # 0xxxx ” .

  If “Host part valid setting” is set to ON (valid) and the phonebook search field is “telephone number”, “phonebook phone number” and “calling / receiving data” (calling / receiving data is SIP address) In this case, if the search character string matches only the user part), the search priority is given first. Incidentally, the collation with the telephone number of the telephone directory is equivalent to the telephone directory search in the public network.

  However, the telephone number reference is prioritized only when an external line is received in the case of a VoIP call on a basic extension or an extension. In addition, the priority of the telephone number reference is also targeted when a PWLAN is received. If the user part of outgoing / incoming data includes characters other than digits, +, and p (pause) (such as English letters including p (characters)), the telephone number field is not searched.

  In the above telephone number reference priority, when “0xxxx” is received, the telephone number reference priority is “complete match”> “1840xxxx”> “1860xxxx”> “# 31 # 0xxxx”> “* 31 # 0xxxx”> “ + 81xxxx ”, and the priority of the telephone number reference when receiving“ + 81xxxx ”is complete match>“ 0xxxx ”>“ 1840xxxx ”>“ 1860xxxx ”>“ # 31 # 0xxxx ”>“ * 31 # 0xxxx ” .

  When “Host part valid setting” is set to ON (valid) and the search field of the phone book search is “SIP address”, “SIP address of phone book” and “Sending / receiving data” [Sending / receiving data is SIP address] If the search character string matches with the full address (user part @ host part format)], the search priority is given first.

  When a PWLAN call is received or a VoIP external line call is received at a basic extension or an extension, if the head of the incoming data is “0” in each search, the search is performed again except for “0” at the head of the incoming data.

  An example of the processing flow of name display by referring to the telephone book is shown in FIGS. An example of a name display processing flow according to an embodiment of the present invention will be described with reference to FIGS. 4 and 5, the search (a) indicates a complete match by comparing “phone number in the phone book” with “calling / receiving data (only the user part)”, and the search (b) indicates “phone book The match between the SIP address and the outgoing / incoming data (user part only) indicates a complete match, and the search (c) is "the user part of the SIP address in the phone book" and "outgoing / incoming data (user part only)". The search (d) indicates a complete match by comparing "SIP address of phone book" with "calling / receiving data (full address format)".

  The control unit 12 of the cellular phone 1 displays the name (step S4 in FIG. 4) when there is a match in the search (a) in the outgoing / incoming public network / VoIP (step S1 in FIG. 4). Here, when a plurality of matches are found in the search (a), they are displayed in the priority order of [1] space, [2] 50 sounds, [3] alphabet, [4] numbers, and [5] symbols. In addition, when a plurality of matches are made in the same phone book, data having a higher priority in the phone book is displayed.

  In the search (a), when VoIP is made / received, if the incoming / outgoing data includes characters other than digits, +, and p (pause) (such as English letters including p (characters)), Do not search for. The priority of the telephone number reference when the incoming call is “0xxxx” is complete match> “1840xxxx”> “1860xxxx”> “# 31 # 0xxxx”> “* 31 # 0xxxx”> “+ 81xxxx”, “+ 81xxxx” In the case of an incoming call, the priority of reference to the telephone number is complete match> “0xxxx”> “1840xxxx”> “1860xxxx”> “# 31 # 0xxxx”> “* 31 # 0xxxx”. In the priority of the above telephone number reference, in the case of an extension call, it is performed only when an outside line is received, and is also applied when a VoIP call other than an extension call is received.

  The control unit 12 of the cellular phone 1 does not correspond to the search (a) (step S1 in FIG. 4), and the VoIP outgoing / incoming and the host part valid setting is not ON (valid) [public network incoming / outgoing, host part valid setting VoIP incoming / outgoing when is set to OFF (invalid), VoIP incoming / outgoing when the host unit valid setting is set to ON (valid) (when the user = phone parameter is specified in the SIP URI)] (step S2 in FIG. 4), If there is a match in the search (b) (step S3 in FIG. 4), the name is displayed (step S4 in FIG. 4). In addition, when two or more correspond, it is the same as the above. In the search (b), when the head of the incoming data is “0” when the VoIP outside line is received, the search is performed again except for “0” at the head of the incoming data.

  When the search (b) is not applicable (step S3 in FIG. 4) and the search (c) is applicable (step S5 in FIG. 4), the control unit 12 of the mobile phone 1 displays the name (step S4 in FIG. 4). If the search (c) is not applicable (step S5 in FIG. 4), outgoing / incoming data is displayed (step S6 in FIG. 4). In addition, when two or more correspond, it is the same as the above. In the retrieval (b) and (c), when the incoming data head is “0” when the incoming VoIP line arrives, the retrieval is again performed except for the leading “0” of the incoming data. Furthermore, the outgoing / incoming data display follows the ON (valid) / OFF (invalid) setting of the “host part valid setting”.

  The control unit 12 of the cellular phone 1 makes and receives VoIP and when the host unit valid setting is ON (valid) [VoIP call when “host unit valid setting” is set to ON (valid)] (step S2 in FIG. 4). If the search (d) is applicable (step S7 in FIG. 5), the name is displayed (step S4 in FIG. 4). If the search (d) is not applicable (step S7 in FIG. 5), the outgoing / incoming data is displayed. (Step S6 in FIG. 4). In addition, when two or more correspond, it is the same as the above. In the search (d), when the head of the incoming data is “0” when the incoming VoIP line arrives, the search is performed again except for “0” at the head of the incoming data. Furthermore, the outgoing / incoming data display follows the ON (valid) / OFF (invalid) setting of the “host part valid setting”.

  As shown in FIG. 6, the display of the VoIP incoming call history is changed by “host part valid setting”. When the “host part valid setting” is set to ON (valid), both the display contents and saved contents are “user part @ host part”, but when it is set to OFF (invalid), “user part @ host part” is selected. Only the “user part” is saved and displayed.

  FIG. 7 shows the contents of outgoing calls when making a VoIP telephone call from the incoming call history. Since the public network cannot accept anything other than digits, it displays a warning notifying that it cannot make a call and does not make a call.

  In FIG. 7, when “host part valid setting” is set to ON (valid) and the configuration of “user part” is only digits (0-9, *, #), +, public network transmission is made “user part ”And VoIP transmission is performed at“ user part @ host part ”.

  In addition, when “Host part valid setting” is set to ON (valid) and the “User part” configuration includes characters other than digits (0-9, *, #) and +, a warning is displayed when calling the public network. VoIP transmission is performed at “user part @ host part”.

  On the other hand, when the “host part valid setting” is set to OFF (invalid) and the configuration of the “user part” is only digits (0-9, *, #), +, the public network transmission is made by the “user part”. VoIP transmission is performed at the “user part”. In this case, in the VoIP transmission, the “host part” of the self SIP address is complemented.

  Also, when “Host part valid setting” is set to OFF (invalid) and the “User part” configuration includes characters other than digits (0-9, *, #) and +, a warning is displayed when the public network is transmitted. VoIP transmission is performed at the “user part”. In this case, in the VoIP transmission, the “host part” of the self SIP address is complemented.

  Furthermore, when registering the phone book from the VoIP incoming call history, when “Host part valid setting” is set to ON (valid), the phone book is registered with “User part @ host part” and set to OFF (invalid). The phone book is registered only by the “user part”. The operation of the VoIP outgoing / incoming history is shown in FIGS. 8 (a) and 8 (b). FIG. 8A shows the history (VoIP transmission system), and FIG. 8B shows the history (VoIP incoming system).

  In FIG. 8 (a), “Host part valid setting” is OFF (invalid) setting, and the operation at the time of VoIP call is “Specify a phone number and make a call (digit entry, phone number of phone book, PSTN call history, "Specify the display contents and make a call"), and if the internal operation of the mobile device is "phone number @local (the local part uses the contents of the current domain name of the current profile)" “User name”, redial / outgoing history display content is “user name”, and the saved content is “user name @ host name”, and “user name” is registered in the phone number column as phonebook linkage from the history , “User name” is registered in the SIP address field. In this case, the contents of the telephone number are used for the user name portion.

  “Host part valid setting” is set to OFF (invalid), and the operation at the time of VoIP call is “Specify the phone number and make a call (digit entry, phone number in the phone book, display contents of the incoming / outgoing calls from the public network” ) ", And the internal operation of the mobile device is" phone number @local (use local domain name of current profile for local part) ", the display content being sent is" user name ", The displayed contents of the redial / outgoing history are “user name”, the stored contents are “user name”, “user name” is registered in the telephone number field as phonebook linkage from the history, and “user name” is registered in the SIP address field. ". In this case, if the content of the telephone number is used for the user name portion, the WLAN profile → “the other party user = phone parameter” is ON, and the user is specified by specifying the user = phone parameter in the SIP URI, the user name portion As a phone number.

  “Host part valid setting” is set to OFF (invalid), and the operation at the time of VoIP call is “Specify the SIP address of only the user name and make a call (input the SIP address of only the“ user part ”, the phone book of only the“ user part ”) If the mobile device internal operation is “username @ local (the local part uses the contents of the current domain name of the current profile)” The displayed content is “user name”, the displayed content of the redial / outgoing history is “user name”, and the stored content is “user name @ host name (the host name part uses the local content)”. “User name” is registered in the telephone number column and “User name” is registered in the SIP address column.

  “Host part valid setting” is set to OFF (invalid), and the operation at the time of VoIP call is “Specify the SIP address of only the user name and make a call (input the SIP address of only the“ user part ”, the phone book of only the“ user part ”) In the case of "send by specifying the display content of the SIP address of"), the internal operation of the mobile device is "send with user name @local (local part uses the contents of the current domain name of the current profile)" The displayed content during a call is “user name”, the displayed content of the redial / outgoing history is “user name”, and the stored content is “user name”. And “user name” is registered in the SIP address field. When the WLAN profile → "other party user = phone parameter" is ON and a call is made by specifying the user = phone parameter in the SIP URI, the user name portion is handled as a telephone number.

  “Host part valid setting” is set to OFF (invalid), and the operation at the time of VoIP call is “Specify the SIP address in the user name @ host name format and make a call (user part @ host part type SIP address input, user part @ host If the internal operation of the mobile device is “call with user name @ host name”, the displayed content during call is “user name” The displayed contents of the redial / outgoing history are “user name”, the stored contents are “user name @ host name”, “user name” is registered in the telephone number field as the phone book linkage from the history, and the SIP address field is registered. Register “User Name”.

  “Host part valid setting” is set to OFF (invalid), and the operation at the time of VoIP call is “Specify the SIP address in the user name @ host name format and make a call (user part @ host part type SIP address input, user part @ host If the internal operation of the mobile device is “call with user name @ host name”, the displayed content during call is “user name” The displayed contents of the redial / outgoing history are “user name”, the stored contents are “user name”, “user name” is registered in the telephone number field as phonebook linkage from the history, and “user name” is registered in the SIP address field. ". When the WLAN profile → "other party user = phone parameter" is ON and a call is made by specifying the user = phone parameter in the SIP URI, the user name portion is handled as a telephone number.

  “Host part valid setting” is set to OFF (invalid), and the operation at the time of VoIP call is “Specify the history display of only the user name and call (Specify the display contents of VoIP call history)” When the internal operation is “user name @ local (the local part uses the content of the current domain name of the current profile)”, the displayed content during transmission is “user name” and the redial / outgoing history display content Is “user name”, and the saved content is “user name @ host name (the host name part uses the local content)”, and “user name” is registered in the telephone number column as the phone book linkage from the history. , “User name” is registered in the SIP address field.

  “Host part valid setting” is set to OFF (invalid), and the operation at the time of VoIP call is “Specify the history display of only the user name and call (Specify the display contents of VoIP call history)” If the internal operation is “Call with user name @ local (the local part uses the contents of the current domain name of the current profile)”, the displayed content during the call is “user name” and redial / call history display The content is “user name”, the stored content is “user name”, “user name” is registered in the telephone number column and “user name” is registered in the SIP address column as phonebook linkage from the history. When the WLAN profile → "other party user = phone parameter" is ON and a call is made by specifying the user = phone parameter in the SIP URI, the user name portion is handled as a telephone number.

  “Host part valid setting” is set to ON (valid), and VoIP call operation is “Call by specifying phone number (digit entry, phone number in phone book, display contents of incoming / outgoing calls from the public network) ) ", And the internal operation of the mobile device is" phone number @ local (use local domain name of current profile for local part) ", the display content being sent is" user name @ host " Name ", redial / outgoing history display content is" user name @ host name ", the saved content is" user name @ host name ", and" user name "is registered in the phone number column as phonebook linkage from the history Then, “user name @ host name” is registered in the SIP address field. In this case, the contents of the telephone number are used for the user name portion.

  “Host part valid setting” is set to ON (valid), and VoIP call operation is “Call by specifying phone number (digit entry, phone number in phone book, display contents of incoming / outgoing calls from the public network) ) ", And the internal operation of the mobile device is" phone number @local (use local domain name of current profile for local part) ", the display content being sent is" user name ", The displayed contents of the redial / outgoing history are “user name”, the stored contents are “user name”, “user name” is registered in the telephone number field as phonebook linkage from the history, and “user name” is registered in the SIP address field. ". In this case, if the content of the telephone number is used for the user name portion, the WLAN profile → “the other party user = phone parameter” is ON, and the user is specified by specifying the user = phone parameter in the SIP URI, the user name portion As a phone number.

  “Host part valid setting” is set to ON (valid), and the operation at the time of VoIP call is “Specify the SIP address of only the user name and make a call (input the SIP address of only the“ user part ”, the phone book of only the“ user part ”) If the mobile device internal operation is “username @ local (the local part uses the contents of the current domain name of the current profile)” The displayed content is “user name @ host name”, the displayed content of redial / outgoing history is “user name @ host name”, and the saved content is “user name @ host name”. “User name” is registered in the telephone number column, and “user name @ host name” is registered in the SIP address column. In this case, the contents of local are used for the host name portion.

  “Host part valid setting” is set to ON (valid), and the operation at the time of VoIP call is “Specify the SIP address of only the user name and make a call (input the SIP address of only the“ user part ”, the phone book of only the“ user part ”) In the case of "send by specifying the display content of the SIP address of"), the internal operation of the mobile device is "send with user name @local (local part uses the contents of the current domain name of the current profile)" The displayed content during a call is “user name”, the displayed content of the redial / outgoing history is “user name”, and the stored content is “user name”. And “user name” is registered in the SIP address field. When the WLAN profile → "other party user = phone parameter" is ON and a call is made by specifying the user = phone parameter in the SIP URI, the user name portion is handled as a telephone number.

  “Host part valid setting” is set to ON (valid), and the operation at the time of VoIP call is “Specify the SIP address in the user name @ host name format and send the call (user part @ host part type SIP address input, user part @ host If the mobile unit's internal operation is “Send with user name @ host name”, the display content being sent is “User name @ host” Name ", redial / outgoing history display content is" user name @ host name ", the saved content is" user name @ host name ", and" user name "is registered in the phone number column as phonebook linkage from the history Then, “user name @ host name” is registered in the SIP address field.

  “Host part valid setting” is set to ON (valid), and the operation at the time of VoIP call is “Specify the SIP address in the user name @ host name format and send the call (user part @ host part type SIP address input, user part @ host If the internal operation of the mobile device is “call with user name @ host name”, the displayed content during call is “user name” The displayed contents of the redial / outgoing history are “user name”, the stored contents are “user name”, “user name” is registered in the telephone number field as phonebook linkage from the history, and “user name” is registered in the SIP address field. ". When the WLAN profile → "other party user = phone parameter" is ON and a call is made by specifying the user = phone parameter in the SIP URI, the user name portion is handled as a telephone number.

  “Host part valid setting” is ON (valid) setting, and the operation at the time of VoIP call is “Specify the user name @ host name history display and call (Specify the display contents of VoIP call history)” When the mobile device's internal operation is “Call with user name @ host name”, the displayed content during outgoing call is “user name @ host name”, the displayed content of redial / outgoing history is “user name @ host name”, The stored content is “user name @ host name”, “user name” is registered in the telephone number column, and “user name @ host name” is registered in the SIP address column as the phone book linkage from the history.

  “Host part valid setting” is ON (valid) setting, and the operation at the time of VoIP call is “Specify the user name @ host name history display and call (Specify the display contents of VoIP call history)” When the mobile unit's internal operation is “call with user name @ host name”, the displayed content during outgoing call is “user name”, the displayed content of redial / outgoing history is “user name”, and the saved content is “user name” "User name" is registered in the telephone number column and "User name" is registered in the SIP address column as phonebook linkage from the history.

  In FIG. 8B, when “host part valid setting” is set to OFF (invalid) and the mobile unit's internal operation is “user name @ host name incoming”, the display content during the incoming call is “user name”. The display contents of the incoming call history are “user name”, the saved contents are “user name”, “user name” is registered in the telephone number field as phonebook linkage from the history, and “user name” is registered in the SIP address field. Register. When the user = phone parameter is specified in the SIP URI and an incoming call is received, the User name portion is handled as a telephone number. However, the telephone number is handled only when the WLAN profile → “local user = phone parameter” is ON (valid), and when it is OFF (invalid), it is handled as a SIP address.

  If “Host part valid setting” is set to OFF (invalid) and the mobile unit's internal operation is “User name @ host name incoming”, the displayed content of the incoming call is “User name” and the incoming history is displayed. “User name”, the stored content is “user name @ host name”, “user name” is registered in the telephone number column and “user name” is registered in the SIP address column as phonebook linkage from the history.

  When “Host part valid setting” is set to ON (valid) and the mobile unit's internal operation is “User name @ host name incoming”, the incoming call content is “User name” and the incoming call history display content is “User name”, the stored content is “user name”, “user name” is registered in the telephone number column, and “user name @ host name” is registered in the SIP address column as the phone book linkage from the history. When the user = phone parameter is specified in the SIP URI and an incoming call is received, the User name portion is handled as a telephone number. However, the telephone number is handled only when the WLAN profile → “local user = phone parameter” is ON (valid), and when it is OFF (invalid), it is handled as a SIP address.

  When “Host part valid setting” is set to ON (valid) and the mobile unit's internal operation is “Incoming with user name @ host name”, the displayed content of the incoming call is “user name @ host name”, The displayed content is “user name @ host name”, the saved content is “user name @ host name”, “user name” is registered in the telephone number field as the phone book linkage from the history, and “user name” is registered in the SIP address field. Name @ hostname ”is registered.

  When making a call from a digit, it is necessary to change the call operation depending on the presence or absence of p (pause). This operation is shown in FIG.

  In FIG. 9, when “host part valid setting” is set to ON (valid), and the digit display configuration (digit input, phone book phone number, incoming / outgoing call history) does not include p (pause), Public network transmission is performed using digit data, and VoIP transmission is performed using digit data. In this case, the host part of the self SIP address is complemented.

  If "Host part valid setting" is set to ON (valid) and the digit display configuration (digit input, phone book phone number, incoming / outgoing calls from the public network) includes p (pause), the public network transmission is digit Data is used, and VoIP transmission is performed using digit data. In this case, the part after p (pause) is invalid, the part before p (pause) is treated as digit data, and the host part of the self SIP address is complemented.

  If “Host part valid setting” is set to OFF (invalid), and the digit display configuration (digit entry, phonebook phone number, incoming / outgoing call history) does not include p (pause), call the public network. Digit data is used, and VoIP transmission is performed using digit data. In this case, the host part of the self SIP address is complemented.

  If "Host part valid setting" is set to OFF (invalid), and the digit display configuration (digit input, phone book phone number, incoming / outgoing calls from the public network) includes p (pause), dial the public network Sending with data, and sending VoIP with digit data. In this case, the part after p (pause) is invalid, the part before p (pause) is treated as digit data, and the host part of the self SIP address is complemented.

  Similarly, it is necessary to change the call operation depending on the content of the call from the SIP address. This operation is shown in FIG.

  In FIG. 10, “host part valid setting” is ON (valid) setting, and the display configuration of the SIP address is “user part @ host part” (VoIP call history, user part @ host part type SIP address input, user part If the configuration of the user part is only digits (0-9, *, #) and + in the SIP address of the @ host part type phone book and the user part @ message part of the host part type) “User part” is performed, and VoIP transmission is performed by “user part @ host part”.

  “Host part valid setting” is ON (valid) setting, and SIP address display configuration is “User part @ host part” (VoIP call history, user part @ host part type SIP address input, user part @ host part type If the configuration of the user part includes characters other than digits (0-9, *, #) and + in the SIP address of the phone book, message part in the user part @ host part format) Display is performed, and VoIP transmission is performed by “user part @ host part”.

  “Host part valid setting” is set to ON (valid), and the display configuration of the SIP address is “User part only” (SIP address input only for the user part, SIP address of the phone part only for the user part, message memo only for the user part) ), If the configuration of the user part is only digits (0-9, *, #), +, public network transmission is performed by the “user part” and VoIP transmission is performed by the “user part”. In this case, the host part of the self SIP address is complemented.

  “Host part valid setting” is set to ON (valid), and the display configuration of the SIP address is “User part only” (SIP address input only for the user part, SIP address of the phone part only for the user part, message memo only for the user part) ), When the configuration of the user part includes characters other than digits (0-9, *, #) and +, a warning is displayed in the public network transmission, and the VoIP transmission is performed in the “user part”. In this case, the host part of the self SIP address is complemented.

  “Host part valid setting” is OFF (invalid) setting, and the display configuration of the SIP address is “user part @ host part” (user part @ host part type SIP address input, user part @ host part type phone book SIP Address, user part @ host part type message memo), and if the user part consists of only digits (0-9, *, #), +, the public network is sent by the "user part" and VoIP is sent Is performed at the “user part @ host part”.

  “Host part valid setting” is OFF (invalid) setting, and the display configuration of the SIP address is “user part @ host part” (user part @ host part type SIP address input, user part @ host part type phone book SIP If the user part configuration includes characters other than digits (0-9, *, #), and + in the address, user part @ host part type message memo), a warning is displayed when calling the public network, and VoIP Make a call with "User part @ Host part".

  “Host part valid setting” is set to OFF (invalid), and the display configuration of the SIP address is only “User part” (VoIP call history, SIP address input only to the user part, SIP address of the user part only phone book, user Message only), and if the configuration of the user part is only digits (0-9, *, #), +, public network transmission is performed by the "user part" and VoIP transmission is performed by the "user part" Do. In this case, the host part of the self SIP address is complemented.

  “Host part valid setting” is set to OFF (invalid), and the display configuration of the SIP address is only “User part” (VoIP call history, SIP address input only to the user part, SIP address of the user part only phone book, user Message only), and the user part contains characters other than digits (0-9, *, #) and +, a warning is displayed in the public network transmission, and the VoIP transmission is “user part”. To do. In this case, the host part of the self SIP address is complemented.

  VoIP redial and call history display contents and stored contents are shown in FIGS. 11 and 12, and VoIP redial and call origination operations from the call history are shown in FIGS.

  In FIG. 11, when “host part valid setting” is set to ON (valid) and the digit display configuration at the time of outgoing calls does not include p (pause), the contents display of the redial / outgoing history is displayed as “user part @ host”. Part "and save the contents of the redial / outgoing history at" user part @ host part ". In this case, the digit data at the time of transmission is used for the user part, and the host part of the self SIP address supplemented at the time of transmission from the digit data is used for the host part.

  When “Host part valid setting” is set to ON (valid) and the digit display configuration at the time of outgoing call includes p (pause), the contents of redial / call history are displayed at “User part @ host part”. Save the contents of the redial / outgoing call history at "User part @ Host part". In this case, since the digit data at the time of transmission is used for the user part and the part after p is not handled at the time of transmission, the part after p of the digit data is not used for the user part. As the host part, the host part of the self SIP address supplemented at the time of transmission from the digit data is used.

  If “Host part valid setting” is set to OFF (invalid) and the digit display configuration at the time of outgoing call does not include p (pause), the redial / outgoing history contents display is set to “user part only” (user part Use the digit data at the time of outgoing), and save the contents of the redial / outgoing history “user part @ host part” (the user part uses the digit data at the time of outgoing and the host part from the digit data) Use the host part of the self-SIP address supplemented at the time of outgoing).

  When “Host part valid setting” is set to OFF (invalid) and the display configuration of digits at the time of outgoing call includes p (pause), the redial / outgoing history content display is set to “user part only” (user part Since the digit data at the time of outgoing call is used and the part after p is not handled at the time of outgoing call, the user part does not use the part after p of the digit data. (The digit data at the time of outgoing is used for the user part, and since the part after p is not used at the time of outgoing, the part after the p of the digit data is not used for the user part. Use the host part of its own SIP address).

  In FIG. 12, when “host part valid setting” is set to ON (valid) and the display configuration of the SIP address at the time of outgoing call is “user part @ host part”, the contents display of the redial / outgoing history is displayed as “user part”. @Host part "and save the contents of redial / outgoing history in" User part @ host part ".

  When "Host part valid setting" is set to ON (valid) and the display configuration of the SIP address at the time of outgoing is "User part only", the contents of the redial / outgoing history are displayed at "User part @ host part" The contents of the redial / outgoing history are stored in “user part @ host part”. In this case, the host part of the self SIP address supplemented at the time of transmission is used as the host part.

  When "Host part valid setting" is set to OFF (invalid) and the display configuration of the SIP address when making a call is "User part @ Host part", the contents of the redial / outgoing history are displayed as "User part only" The contents of the redial / outgoing history are stored in “user part @ host part”.

  When “Host part valid setting” is set to OFF (invalid) and the display configuration of the SIP address at the time of outgoing call is “User part only”, the redial / outgoing history contents are displayed as “User part only” and redial / The contents of the outgoing call history are saved by “user part @ host part” (the host part uses the host part of its own SIP address supplemented at the time of outgoing call).

  In FIG. 13, the “host part valid setting” is ON (valid) setting, the history saved content is “user part @ host part”, and the history display content is “user part @ host part” [“user part”. When the configuration is a digit (0-9, *, #), + only], public network transmission is performed by the “user unit” and VoIP transmission is performed by the “user unit @ host unit”.

  “Host part valid setting” is ON (valid), history saved is “user part @ host part”, history display content is “user part @ host part” [digits (0-9, *, #) , Including characters other than +], “warning display” is performed in the public network transmission, and VoIP transmission is performed in “user part @ host part”.

  “Host part valid setting” is set to OFF (invalid), the saved contents of the history are “user part @ host part”, and the displayed contents of the history are “user part only” [digits (0-9, *, #), In the case of “+ only”, public network transmission is performed by the “user part”, and VoIP transmission is performed by the “user part” (complementing the host part of the own SIP address).

  “Host part valid setting” is set to OFF (invalid), the saved contents of the history are “user part @ host part”, and the displayed contents of the history are “user part only” [digits (0-9, *, #), In the case of “including characters other than +”], “warning display” is performed in the public network transmission, and VoIP transmission is performed in the “user part” (complementing the host part of the own SIP address).

  In FIG. 14, when “host part valid setting” is ON (valid) setting and the saved content of the history is “user part @ host part”, phone book registration is performed with “user part @ host part”. Further, when the “host part valid setting” is set to OFF (invalid) and the saved content of the history is “user part @ host part”, the phone book registration is performed with “user part only”.

15-18, in the phone book,
Name: Phonebook registration number A: 05012345678
B: 050125345678 @ local-02
C: 050125345678 @ local-01
D: 050125345678 @ host-02
E: 050125345678 @ host-01
F: 08012345678
G: 070125345678
H: 090125345678
When the number is registered, the redial and outgoing call history display image is shown.

  FIG. 15 shows a redial and outgoing history display image when the outgoing call history host portion is enabled, and FIG. 16 shows a redial and outgoing history display image when the outgoing history host portion is disabled. Yes. In this case, the host part becomes invisible. In addition, the reverse address lookup when the host part is disabled is displayed as “A” because the user part search is in the order of Iueo (in order of reading).

  FIG. 17 shows a display image of redial and outgoing call history when the redial host part is enabled. In this case, since the 9th is the same as the 3rd of the outgoing call history, the display is omitted in redial (not visible on the redial display).

  FIG. 18 shows a display image of redial and outgoing call history when the host part of redial is invalidated. In this case, since the host unit is set to be invalid, the first to fifth items in the display are regarded as the same dial, and only the first item with the newest history is displayed. Since the reverse address lookup is in the order of Iueo (phonetic order) in the user part search, “A” is displayed.

  As described above, in this embodiment, it is possible to display the same incoming / outgoing history of a VoIP telephone as that of a circuit-switched call, and it is possible to refer to data registered in the telephone directory from the SIP URI.

  It should be noted that the present invention is not limited to a telephone that supports Dual of the public network 200 and the IP network, but also a single VoIP telephone that supports only the IP network. It can be used in the same way as a telephone. Further, the present invention can be applied not only to mobile phones but also to fixed phones.

It is a block diagram which shows the structure of the communication system by one Example of this invention. It is a block diagram which shows the structure of the mobile telephone by one Example of this invention. It is a figure which shows the name display by the telephone directory reference in one Example of this invention. It is a flowchart which shows the example of a processing flow of the name display by telephone directory reference in one Example of this invention. It is a flowchart of the example of a processing flow of the name display by telephone directory reference in one Example of this invention. It is a figure which shows the incoming call history of VoIP in one Example of this invention. It is a figure which shows the outgoing call content in the case of making a VoIP telephone call from the incoming call history in one Example of this invention. (A), (b) is a figure which shows the operation | movement of the VoIP transmission / reception log | history in one Example of this invention. It is a figure which shows the transmission operation | movement in the case of making a telephone call from the digit in one Example of this invention. It is a figure which shows the transmission operation | movement in the case of making a telephone call from the SIP address in one Example of this invention. It is a figure which shows the display content of the VoIP redial in the one Example of this invention, the transmission history, and the preservation | save content. It is a figure which shows the display content of the VoIP redial in the one Example of this invention, the transmission history, and the preservation | save content. It is a figure which shows the telephone call operation | movement from the redial of VoIP and the call history in one Example of this invention. It is a figure which shows the telephone call operation | movement from the redial of VoIP and the call history in one Example of this invention. It is a figure which shows the display image of the redial and transmission log | history in one Example of this invention. It is a figure which shows the display image of the redial and transmission log | history in one Example of this invention. It is a figure which shows the display image of the redial and transmission log | history in one Example of this invention. It is a figure which shows the display image of the redial and transmission log | history in one Example of this invention.

Explanation of symbols

1,1-1 to 1-3 mobile phone
2 access points
3 servers 4-1 and 4-2 fixed telephones 5-1 and 5-2 gateways 6-1 and 6-2
7 RNC
8 base stations
10 Antenna for wireless LAN
11 Mobile phone antenna
12 Control unit
13 memory
14 Wireless LAN radio section
15 Mobile phone radio section
16 Operation unit
17 Display
100 extension telephone network
121 Calling / receiving command reception processing part
122 Call processing unit
123 Calling / Dialing Number Registration Processing Unit
124 Display processing unit
131 Phonebook data storage
132 Call history data storage unit
200 Public network
300 Mobile phone network

Claims (13)

When the SIP (Session Initiation Protocol) composed of a user part and a host part is used, and only the user part is input in outgoing calls using VoIP (Voice over Internet Protocol) that performs call control using a URI (Universal Resource Identifier). A telephone that complements the host part to make a call ,
Have a display processing means for controlling whether to display the host unit in response to a user's selection setting,
The user's selection setting is a host part valid setting for setting whether to validate the host part,
The telephone according to claim 1, wherein the display processing means switches display contents of the outgoing / incoming call history according to the host unit valid setting . 2. The telephone according to claim 1 , wherein the display processing unit handles only the user part when the host part valid setting is invalid at the time of the VoIP outgoing / incoming call and telephone call . 3. The telephone according to claim 2 , wherein the display processing unit stores the user part and the host part in the VoIP call history regardless of the validity / invalidity setting of the host part valid setting . The telephone according to any one of claims 1 to 3, wherein the display processing means stores the content displayed on the display unit when the VoIP is transmitted . Said display processing means, the telephone according to any one of claims 1 to 4, characterized in that to save the format the history in the SIP URI in the incoming call history registration of the VoIP. The telephone according to any one of claims 1 to 5, wherein the display processing means stores a character string of digit input or SIP address input display as a redial and outgoing call history . A communication system comprising the telephone set according to any one of claims 1 to 6. When the SIP (Session Initiation Protocol) composed of a user part and a host part is used, and only the user part is input in outgoing calls using VoIP (Voice over Internet Protocol) that performs call control using a URI (Universal Resource Identifier). A call history registration / display method used for a telephone that makes a call while complementing the host unit,
The telephone executes a display process for controlling presence or absence of display of the host unit according to a user's selection setting,
The user's selection setting is a host part valid setting for setting whether to validate the host part,
A method for registering / displaying an incoming / outgoing call history, wherein the telephone set switches display contents of the outgoing / incoming call history according to the host unit valid setting in the display process. The incoming / outgoing call history registration / calling according to claim 8, wherein the telephone unit handles only the user part when the host part valid setting is invalid during the VoIP outgoing / incoming call and a call in the display process. Display method. 10. The telephone set stores the user part and the host part in the VoIP call history regardless of the validity / invalidity setting of the host part valid setting in the display process. How to register / display the call history. 11. The calling / call history registration / display method according to claim 8, wherein the telephone is stored by using contents displayed on a display unit when the VoIP is transmitted in the display processing. The call history registration / registration according to any one of claims 8 to 11, wherein the telephone set stores the history in the form of the SIP URI when the VoIP reception history is registered in the display process. Display method. 13. The incoming / outgoing call history registration / calling according to claim 8, wherein the telephone stores a character string of digit input or SIP address input display as redial and outgoing call history in the display processing. Display method.

Images