JP2006244171A - Communication system, method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a communication system, a method and a program capable of changing the construction of an operation menu, menu items, a display order or design displayed on a display means on a receiving side based on menu generation information transmitted from a transmitting side, and capable of changing contents of the operation menu, and a method of display on the receiving side. <P>SOLUTION: A communication terminal is provided with a party on the other end information extracting means for receiving and extracting presence information regarding an identifier and a state transmitted from a communication party on the other end, and the menu generating information for displaying the operation menu desired by the communication party on the other end on a menu display means; a template storage means for storing a plurality of kinds of templates related to the display of the operation menu; and a template information providing means for selecting the corresponding template from the template storage means and providing it to the menu display means based on presence information and menu generation information extracted by the party on the other end information extracting means. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a communication system, a method, and a program related to an operation menu display technique for selecting and executing an operation in mutual communication.

  With the spread of computers, communication terminals that can use a graphical user interface that is easy to understand intuitively for users, such as mobile phones, have increased. Not only personal computers (hereinafter referred to as PCs) that implement IP telephone functions, but also some non-IP fixed telephones are equipped with a display, and the user can operate the terminal through a graphical user interface. .

  As a graphical user interface of such a communication terminal, a menu selection method in which a terminal operation is performed by performing a desired operation from options is common. For example, in a conventional multi-function phone such as a business phone (registered trademark), a number of buttons to which a function to be operated by the user is assigned are arranged. For example, in order for the user to perform a transfer operation, “ The user himself / herself had to learn a predetermined procedure including a button press assigned with the function “transfer”.

  An advantage of such a menu selection method is that a list of operations that can be executed is presented to the user, and it is not necessary to memorize different button operations for each operation by selecting a desired operation from the list.

In order to respond to various needs of users, it is necessary to implement many functions in a communication terminal. However, frequently used functions are different for each user. For this reason, with the increase in the number of functions of communication terminals, menu items that are less frequently used and less important also increase, and the problem arises that the operability is lowered contrary to the intention. Therefore, it is necessary to devise display methods such as narrowing down menu items. For example, a method for switching the operation menu to an optimal one based on the user ID of the terminal user is disclosed (see Patent Document 1 and Patent Document 2).
JP-A-5-346902 JP-A-5-20006

  However, in the operation menu switching method based on the user ID of the user (sender) of the communication terminal as implemented in the prior art, information regarding the communication partner (receiver) is not considered and It is difficult for a person to present an operation menu in accordance with the communication partner or the state of the communication partner.

  Further, in a real-time two-way communication application such as Instant Messenger (registered trademark) in the prior art, by referring to the presence information (see RFC 2778) of the communication partner, for example, whether the communication partner is currently connected to the network. If not, the operation menu is switched so that the communication means presented to the user is instant messenger or e-mail.

  However, in the operation menu display method, the operation menu to be presented according to the communication partner is not switched, and the user himself / herself must select a desired operation from the operation menu in consideration of the communication partner. There wasn't.

  The present invention has been made in view of the above problems, and its object is to configure the operation menu and menu items displayed on the display means on the reception side based on the menu generation information transmitted from the transmission side. Another object of the present invention is to provide a communication system, method, and program that can change the display order and design, and can change the contents and display method of the operation menu on the receiving side.

  In order to solve the above-mentioned problem, the present invention according to claim 1 is a communication capable of communicating with each other by a plurality of communication terminals provided with a menu display means for displaying an operation menu related to its function. In the system, the communication terminal receives presence information regarding an identifier and a state transmitted from a communication partner, and menu generation information for causing the menu display unit to display an operation menu desired by the communication partner. Destination information extracting means, template storage means for storing a plurality of types of templates related to the display of the operation menu, presence information extracted by the destination information extracting unit, and the menu generation information On the basis of the template storage means, the corresponding template is selected and provided to the menu display means. And a template information providing means for.

  According to a second aspect of the present invention, in the first aspect, the communication terminal communicates with a self-information storage unit for storing the presence information and the menu generation information related to the communication terminal. Self-information transmission means for transmitting the presence information and the menu information stored in the self-information storage means during communication with the other party.

  Also, in the present invention described in claim 3, in any one of claims 1 and 2, the communication terminal determines menu generation information corresponding to the identifier of the communication partner and its correspondence. The attribute information storage means for storing the corresponding relationship information as attribute information, and the menu stored in the attribute information storage means based on the identifier included in the presence information transmitted from the communication partner. Conversion information acquisition means for acquiring generation information.

  According to a fourth aspect of the present invention, in the third aspect of the present invention, the attribute information storage means is a correspondence relationship for arbitrarily changing the correspondence relationship information for determining a relationship between the identifier and the menu generation information. Information changing means is provided.

  According to a fifth aspect of the present invention, in any one of the third or fourth aspects, the communication terminal associates the identifier of the communication partner with its own operation history as operation history information. Operation history information storage means for storing, and attribute information generation means for generating the attribute information based on the operation history information stored in the operation history information storage means.

  The present invention according to claim 6 is the communication terminal according to any one of claims 4 and 5, wherein the communication terminal includes user group information in which a use condition of the communication terminal is defined, and the user group information. User authentication information storage means for storing user information of users constituting a user group belonging to the group, group attribute information storage means for storing menu generation information set for each user group, and communication Menu generation information assigning means for identifying the user group to which the user belongs from the user authentication information storage means based on the identifier of the user who is the other party, and assigning menu generation information corresponding to the user group. .

  Further, the present invention according to claim 7 is a communication method in which a plurality of communication terminals provided with a menu display means for displaying an operation menu related to its function can communicate with each other. The destination information extracting means receives presence information on the identifier and state transmitted from the communication partner, and menu generation information for causing the menu display means to display an operation menu desired by the communication partner. Extracting the plurality of types of templates related to the display of the operation menu by the template storage means, the presence information extracted by the destination information extraction unit by the template information providing means, and the menu generation Based on the information, the corresponding template from the template storage means It has a step of providing by selecting over preparative to the menu display means.

  Further, the present invention according to claim 8 is a communication program capable of communicating with each other between a plurality of communication terminals provided with a menu display means for displaying an operation menu related to its function. The destination information extracting means receives presence information on the identifier and state transmitted from the communication partner, and menu generation information for causing the menu display means to display an operation menu desired by the communication partner. Extracting the plurality of types of templates related to the display of the operation menu by the template storage means, the presence information extracted by the destination information extraction unit by the template information providing means, and the menu generation Based on the information, the corresponding template storage means It has a step of providing by selecting Plates to the menu display means.

  The present invention according to claim 9 is operable by installing the communication program according to claim 8 on a server arranged on the network.

  According to the present invention, the configuration, menu items, display order, and design of the operation menu displayed on the display unit on the reception side can be changed based on the menu generation information transmitted from the transmission side, and the operation menu can be changed. It is possible to provide a communication system, a method, and a program that can change the contents and display method on the receiving side.

  In an embodiment of the present invention, a communication terminal is an information communication system capable of executing transmission / reception of various data including voice information, image information, text information, and the like between a plurality of communication terminals, and the information communication system Includes application software that runs on the above.

  Such communication terminals include at least information processing means such as a computer capable of operating a communication application such as a fixed phone, a mobile phone, and an instant messenger.

<First Embodiment>
A configuration diagram of the present embodiment is shown in FIG.

  First, in step S1, the transmission unit (self-information storage unit) (self-information transmission unit) 1 on the communication partner side transmits the identifier, presence information, and menu generation information of the communication partner. The identifier can be a SIP-URI (see RFC 3263), a mail address or an IP address. A unique ID may be used.

  The presence information is a state indicating the current state of the communication partner, and may be in a state such as “not connected”, “communicable”, “capturing”, “leaving away”, “meeting”, “communication”.

  The menu generation information includes the menu category, menu item list, display order, layout information related to the display position on the display unit of the communication terminal, and design information such as the background color and the size and color of the characters. It is a menu generation information identifier (identifier) that includes a combination of arbitrary information or corresponds to the information.

  The menu generation information identifier may be a character string or a link such as a URI to a WWW page in which the information is described. In the present embodiment, the case where a menu generation information identifier is transmitted as menu generation information will be described below.

  The relationship between the menu generation information and the menu generation information identifier can be managed with a table as shown in FIG. 6, for example. A menu DB unit (template storage unit) 7 to be described later includes such a management table. However, the transmission unit 1 of the communication partner does not necessarily have such a management table, and the management table on the menu DB unit 7 is not necessarily provided. As long as it is a valid menu generation information identifier.

  Next, in step S2, the receiving unit 2 of the own communication terminal receives the information transmitted in the previous step S1.

  Next, in step S3, the communication terminal extracting unit (partner information extracting means) 3 extracts menu generation information based on the identifier and presence information of the communication partner from the information received in the previous step S2. Regarding the menu identification information, in the case of the present embodiment, a menu generation information identifier is extracted.

  Next, in step S4, the processing unit (template information providing means) 4 accesses the menu DB unit 7 based on the communication partner identifier, presence information, and menu generation information extracted in the previous step S2. The operation menu template presented to the terminal user is acquired and stored in the memory 5. The menu DB unit 7 holds a combination of presence information and menu generation information of a communication partner and a corresponding menu template as shown in FIG.

  A menu template may be determined for the combination of presence information and menu generation information, and the menu templates may be the same. For example, the same menu template can be associated with any combination of presence information and menu generation information.

  Further, the menu DB unit 7 may be in the communication terminal or in another terminal (server or the like) on the network. Each template includes the menu category, menu item list, display order, layout information regarding the display position on the display unit of the communication terminal, background color, character size and color, which are included in the menu generation information. This is an operation menu instance in which specific values are determined as design information.

  In addition, various templates can be associated with the menu generation information. For example, by specifying one of the “friend menu”, “family menu”, and “company menu” as the category information of the menu generation information, in the case of the “friend menu”, the operation menu of the instant messenger is set to “ In the case of “Family Menu”, the operation menu of the video phone is associated, and in the case of “Corporate Menu”, the operation menu of a multi-function phone such as a business phone (registered trademark) is associated with the emphasized operation menu template. It is conceivable.

  Further, in the present embodiment, a configuration is shown in which an operation menu to be finally presented to the terminal user is generated by acquiring a menu template and processing it, but the menu shown in FIG. 8 is obtained. Alternatively, the menu generation information may be held in the menu DB unit 7 and the operation menu may be assembled from scratch. In this example, as shown in FIG. 7, the template is acquired from the presence information and menu generation information of the communication partner. However, in addition to the presence information and menu generation information, The template may be supported.

  Next, in step S5, the processing unit 4 processes the operation menu template acquired in the previous step S4 into an operation menu that is finally presented to the user of the communication terminal. As an example of processing, it is conceivable that the presence information extracted in step S3 is used and, for example, a part of the operation menu is not displayed when the communication partner is “busy”.

  Finally, in step S6, the display unit (menu display means) 6 presents the operation menu created in the previous step S5 to the terminal user.

  The format of the data transmitted in steps S1 and S2 (FIG. 5) of the first embodiment will be supplementarily described below.

  As an example of the format of the data that includes the identifier of the communication partner, presence information, and menu generation information that is transmitted by the communication partner in step S1, a data format that extends PIDF (see FTC3863) as shown in FIG. Conceivable.

  In FIG. 17, the portion shown in bold is an expanded portion. In this format, an entity attribute value of a <presence> tag can be associated as an identifier of a communication partner, a <user-status> node as presence information, and a <menu-hints> node as menu generation information.

  FIG. 17 shows two menu categories “game” and “messenger” as an example of the menu generation information. Furthermore, “shogi” is shown as an example of the menu item of the “game” category. <Contact> in the same node indicates the address of the communication partner used when executing the menu category or menu item.

  In the first embodiment, menu generation information exists, and a <menu-hints> node exists.

  Next, a supplementary explanation will be given on the extraction of the communication partner identifier, presence information, and menu generation information in step S3 (FIG. 5) of the first embodiment.

  Step S3 is a step in which the extraction unit (extraction unit 3 in FIG. 1) extracts the communication partner identifier, presence information, and menu generation information from the data sent from the communication partner. The processing of this step when the data sent from the communication partner is in the data format shown in FIG. 17 will be described with reference to the flowchart shown in FIG.

  In step S60, the extraction unit acquires the identifier of the communication partner. In this example, the entity attribute value “peer@example.net” of the <presence> tag is acquired as the identifier of the communication partner.

  In step S61, the extraction unit acquires presence information. In this example, the character string “free” indicated by the <user-status> tag is acquired as presence information.

  In step S62, the extraction unit checks whether menu generation information exists. In this example, the determination is made based on whether a <menu-hints> node exists. If it exists, step S63 is executed, and if it does not exist, step S64 is executed. In the first embodiment, since there is a <menu-hints> node, the process proceeds to step S63.

  In step S63, the extraction unit sets a menu generation information presence flag.

  In step S64, the extraction unit clears the menu generation information presence flag.

  The processing from step S65 to step S67 is executed for each <menu> node included in the <menu-hints> node.

  In step S65, the extraction unit obtains a value sandwiched between <menu-category> tags as menu category information of the menu generation information. In this example, “game” and “messenger” are acquired.

  In step S66, the extraction unit acquires a value sandwiched between <menu-item> tags as menu item information of the menu generation information. In this example, “shogi” is acquired.

  In step S67, the extraction unit acquires a value sandwiched between <contact> tags as additional information of the menu category or menu item. In this example, “game: game@example.net” and “im: im@example.net” are acquired.

  Next, a supplementary explanation will be given for the acquisition of the menu template in step S4 (FIG. 5) of the first embodiment.

  In step S4, the processing unit (processing unit 4 in FIG. 1) accesses the menu DB unit (6 in FIG. 1) using presence information and menu generation information as keys, and displays an operation menu to be presented to the terminal user. A template is acquired and stored in the memory 5.

  FIG. 19 shows two examples of menu templates held in the menu DB. The part described as “$ {...}” In the same figure is a part corresponding to the variable, and in the subsequent step S5, a specific character string or numerical value is inserted into this part, so that the final part is obtained. The operation menu presented to the terminal user.

  As a method of selecting a menu template based on the menu generation information, for example, a method of selecting a menu category that matches is conceivable. When there are a plurality of menu templates for one menu category, it is possible to compare menu generation information such as menu items and select a matching menu template.

  By such a method, when the menu generation information of FIG. 17 is given, the menu template shown in FIG. 19 can be selected.

  Next, a supplementary explanation will be given for the processing of the menu template in step S5 (FIG. 5) of the first embodiment.

  In step S5, the processing unit (processing unit 4 in FIG. 1) processes the menu template acquired in previous step S4 to generate an operation menu to be presented to the terminal user. Menu templates are generally operation menus that have indeterminate parts that are not given specific character strings or numerical values for the menu items to be displayed, their order, font type and size, background color, etc. In this step, a menu template that does not have an indeterminate part, such as giving a specific character string or numerical value to the indeterminate part, or hiding or highlighting some menu items, etc. If so, it can be presented to the user without processing.

  As an example of the processing processing of the menu template, it is considered that a specific character string is filled in the indefinite portion of the menu template shown in FIG. 19 by using the identifier of the communication partner and the menu generation information given in FIG. It is done. By using the menu generation information acquired in steps S65 to S67 in FIG. 18, an operation menu as shown in FIG. 20 can be generated.

  In FIG. 20 of this example, “shogi” corresponding to “shogi” acquired in step S66 is inserted into $ {item1} of the menu template on the left of FIG. 19, and $ {name} of the menu template on the right of FIG. The operation menu generated by inserting “peer@example.net” acquired in step S60 and integrating the two menu templates.

  In FIG. 20, “Go” and “Chess” are inserted in the portions corresponding to $ {item2} and $ {item3}, respectively. It is good to prepare in the menu DB as a default menu item for each category displayed when there is no such designation.

<Second Embodiment>
This embodiment is a menu display method when menu generation information is not included in information received from a communication partner.

  A configuration diagram of the present embodiment is shown in FIG. 2 and will be described with reference to a flowchart shown in FIG. This is the same as the first embodiment except that the menu generation information is not included in the information received from the communication partner and that the menu generation information is acquired using the identifier of the reception communication partner.

  First, in step S10, as in step S1 in the flowchart of the first embodiment, the transmission unit 1 on the communication partner side transmits the identifier and presence information of the communication partner. However, in the present embodiment, menu generation information is not included in the transmitted information.

  Next, in step S11, similarly to step S2 in the flowchart of the first embodiment, the receiving unit 2 of the own communication terminal receives the information transmitted in the previous step S10.

  Next, in step S12, as in step S3 in the flowchart of the first embodiment, the extraction unit 3 of the communication terminal selects the communication partner identifier, presence information, and the like from the information received in the previous step S2. Menu generation information and menu generation information extraction processing are performed. Since the present embodiment deals with a case where menu generation information is not included, this information is not extracted.

  Next, in step S13, the processing unit 4 checks whether there is menu generation information in the information extracted in the previous step S12. In this embodiment, since menu generation information is not found, the identifier of the communication partner is transmitted to the conversion unit (conversion information acquisition means) 9, and the process continues to step S14. If menu generation information has been extracted, the process continues to step S16.

  In step S14, the conversion unit 9 receives the identifier of the communication partner from the processing unit 4, accesses the attribute DB unit (attribute information storage unit) 8, and obtains menu generation information corresponding to the identifier (correspondence information) ) And sent to the processing unit 4. The attribute DB unit 8 holds a correspondence table of communication partner identifiers and menu generation information or a correspondence table of communication partner identification information and menu generation information identifiers as shown in FIG. The conversion unit 9 and the attribute DB unit 8 may be inside the communication terminal or may be in another terminal on the network.

  In step S15, as in step S4 in the flowchart of the first embodiment, the processing unit 4 accesses the menu DB unit 7 based on the communication partner identifier, presence information, and menu generation information. The operation menu template presented to the terminal user is acquired.

  The menu DB unit 7 holds a combination of presence information and menu generation information of a communication partner and a template menu corresponding to the combination as shown in FIG. In the present embodiment, a configuration is shown in which a menu template is acquired and processed to generate an operation menu to be finally presented to the terminal user. The information may be stored in the menu DB unit 7 and the operation menu may be assembled from scratch.

  In this example, as shown in FIG. 7, the template is acquired from the presence information and menu generation information of the communication partner. However, in addition to the presence information and menu generation information, The template may be configured to correspond (corresponding relationship information changing means).

  Next, in step S16, as in step S5 in the flowchart of the first embodiment, the processing unit 4 finally presents the operation menu template acquired in the previous step S15 to the user of the communication short terminal. Process the operation menu.

  Finally, in step S17, the display unit 6 presents the operation menu created in the previous step S16 to the terminal user.

  Next, a supplementary description will be given of the format of transmitted data in steps S10 and S11 (FIG. 9) of the second embodiment.

  As an example of the format of the data that includes the communication partner identifier, presence information, and menu generation information that is transmitted by the communication partner in S1, a data format that extends PIDF (see FTC3863) as shown in FIG. 17 is considered. It is done.

  In FIG. 17, the portion shown in bold is an expanded portion. In this format, an entity attribute value of a <presence> tag can be associated as an identifier of a communication partner, a <user-status> node as presence information, and a <menu-hints> node as menu generation information.

  FIG. 17 shows two menu categories “game” and “messenger” as an example of the menu generation information. Furthermore, “shogi” is shown as an example of the menu item of the “game” category. <Contact> in the same node indicates the address of the communication partner used when executing the menu category or menu item.

  In the second embodiment, there is no menu generation information, and there is no <menu-hints> node.

  Next, a supplementary description will be given of the extraction of the communication partner identifier, presence information, and menu generation information in step S12 (FIG. 9) of the second embodiment.

  Step S3 is a step in which the extraction unit (extraction unit 3 in FIG. 2) extracts the communication partner identifier, presence information, and menu generation information from the data sent from the communication partner. The processing of this step when the data sent from the communication partner is in the data format shown in FIG. 17 will be described with reference to the flowchart shown in FIG.

  In step S60, the extraction unit acquires the identifier of the communication partner. In this example, the entity attribute value “peer@example.net” of the <presence> tag is acquired as the identifier of the communication partner.

  In step S61, the extraction unit acquires presence information. In this example, the character string “free” indicated by the <user-status> tag is acquired as presence information.

  In step S62, the extraction unit checks whether menu generation information exists. In this example, the determination is made based on whether a <menu-hints> node exists. If it exists, step S63 is executed, and if it does not exist, step S64 is executed. In the second embodiment, since there is no <menu-hints> node, the process proceeds to step S64.

  In step S63, the extraction unit sets a menu generation information presence flag.

  In step S64, the extraction unit clears the menu generation information presence flag.

  The processing from step S65 to step S67 is executed for each <menu> node included in the <menu-hints> node.

  In step S65, the extraction unit obtains a value sandwiched between <menu-category> tags as menu category information of the menu generation information. In this example, “game” and “messenger” are acquired.

  In step S66, the extraction unit acquires a value sandwiched between <menu-item> tags as menu item information of the menu generation information. In this example, “shogi” is acquired.

  In step S67, the extraction unit acquires a value sandwiched between <contact> tags as additional information of the menu category or menu item. In this example, “game: game@example.net” and “im: im@example.net” are acquired.

  Next, a supplementary description will be given of the determination of the presence of menu generation information in step S13 (FIG. 9) of the second embodiment.

  In step S13, the processing unit (processing unit 4 in FIG. 2) checks the menu generation information flag set in step S63 or step S64 in FIG. 18, and proceeds to step S14 if the flag is set. If the flag is cleared, the process proceeds to step S15.

  Next, a supplementary explanation will be given for obtaining the menu template in step S15 (FIG. 9) of the second embodiment.

  In step S15, the processing unit (processing unit 4 in FIG. 2) uses the presence information and menu generation information as keys to access the menu DB unit (menu DB unit 7 in FIG. 2) and present it to the terminal user. Get the operation menu template.

  FIG. 19 shows two examples of menu templates held in the menu DB. The part described as “$ {...}” In the same figure is a part corresponding to the variable, and in the subsequent step S16, a specific character string or numerical value is inserted into this part, so that the final part is obtained. The operation menu presented to the terminal user.

  As a method of selecting a menu template based on the menu generation information, for example, a method of selecting a menu category that matches is conceivable. When there are a plurality of menu templates for one menu category, it is possible to compare menu generation information such as menu items and select a matching menu template.

  By such a method, when the menu generation information of FIG. 17 is given, the menu template shown in FIG. 19 can be selected.

  Next, a supplementary description will be given of the processing of the menu template in step S16 (FIG. 9) of the second embodiment.

  In step S16, the processing unit (processing unit 4 in FIG. 2) processes the menu template acquired in the previous step S15 to generate an operation menu to be presented to the terminal user. Menu templates are generally operation menus that have indeterminate parts that are not given specific character strings or numerical values for the menu items to be displayed, their order, font type and size, background color, etc. In this step, a menu template that does not have an indeterminate part, such as giving a specific character string or numerical value to the indeterminate part, or hiding or highlighting some menu items, etc. If so, it can be presented to the user without processing.

  As an example of the processing processing of the menu template, it is considered that a specific character string is filled in the indefinite portion of the menu template shown in FIG. 19 by using the identifier of the communication partner and the menu generation information given in FIG. It is done. By using the menu generation information acquired in steps S65 to S67 in FIG. 18, an operation menu as shown in FIG. 20 can be generated.

  In FIG. 20 of this example, “shogi” corresponding to “shogi” acquired in step S66 is inserted into $ {item1} of the menu template on the left of FIG. 19, and $ {name} of the menu template on the right of FIG. The operation menu generated by inserting “peer@example.net” acquired in step S60 and integrating the two menu templates.

  In FIG. 20, “Go” and “Chess” are inserted in the portions corresponding to $ {item2} and $ {item3}, respectively. It is good to prepare in the menu DB as a default menu item for each category displayed when there is no such designation.

<Third Embodiment>
This embodiment is different from the second embodiment only in that the identifiers, presence information, and menu generation information of two or more communication terminals are used as information used for creating the operation menu.

  Therefore, the configuration shown in FIG. 2 is used in the same manner as in the second embodiment, and the following description will be made along the flowchart shown in FIG.

  The processing contents of step S20 and step S21 are the same as those of step S10 and step S11 of the second embodiment, respectively, except that the receiving unit 2 receives the identifiers and presence information of two or more communication terminals. In the present embodiment, there are N communication terminals as communication partners.

  In the processing after step S22, menu generation information for N devices is acquired, and an operation menu to be presented to the user of the communication terminal is created.

  In step S <b> 22, the extraction unit 3 checks whether the information received in the previous step S <b> 21 includes an unextracted communication partner identifier, presence information, and menu generation information. If there is, the process proceeds to step S23. If not, the process proceeds to step S27. When transitioning from step S21 to this step for the first time, there is N unextracted information.

  In step S23, the extraction unit 3 performs an extraction process of the identifier, presence information, and menu generation information of one communication partner among the unextracted information.

  Next, in step S25, the processing unit 4 checks whether menu generation information exists in the information extracted in step S23. If it exists, the process proceeds to step S26. If not, the process proceeds to step S24. Since this embodiment deals with a case where menu generation information does not exist, the process proceeds to step S24.

  In step S24, as in step S14 of the second embodiment, the conversion unit 9 receives the communication partner identifier from the processing unit 4, accesses the attribute DB unit 8, and generates a menu corresponding to the identifier. Get information. Subsequently, the conversion unit 9 passes the acquired information to the processing unit 4.

  In step S26, the processing unit 4 stores the identifier and presence information of the communication partner acquired in step S23 and the menu generation information acquired in step S23 or step S24 in the memory 5, and proceeds to step S22.

  In step S27, as in the second embodiment, the processing unit 4 accesses the menu DB unit 7 based on the identifier of the communication partner, presence information, and menu generation information, and notifies the terminal user. Get the template for the operation menu to be presented.

  However, when handling menu generation information of a plurality of communication partners, a menu template corresponding to each combination of a plurality of presence information and menu generation information is held in the menu DB unit 7.

  Next, in step S28, as in step S16 in the second embodiment, the processing unit 4 finally presents the operation menu template acquired in the previous step S27 to the user of the communication short terminal. Process to the operation menu.

  Finally, the display unit 6 presents the operation menu created in step S28 to the terminal user.

<Fourth embodiment>
In the present embodiment, as a method for acquiring menu generation information from the identifier of the communication partner, only the point that the operation history information of the user of the communication terminal is used is a part that is not in the third embodiment.

  Therefore, FIG. 3 shows a configuration diagram of the present embodiment. As a method for obtaining menu generation information from the identifier of the communication partner, which is not in the third embodiment, the operation history of the user of the communication terminal A part using information, more specifically, a method for constructing an attribute DB will be described with reference to a flowchart shown in FIG.

  In the following description, the attribute generation unit (attribute information generation unit) 12 and the operation history DB unit (operation history information storage unit) 11 may be located inside the communication terminal or on another terminal on the network. I do not care.

  First, in step S <b> 30, the terminal user inputs an operation to the operation input unit 10. The operation input unit 10 records the operation identifier corresponding to the input operation, the operation, and the identifier of the communication partner at that time in the operation history DB unit 11.

  Next, in step S31, the attribute generation unit 12 refers to the operation history DB unit 11 to generate menu generation information for each communication partner existing on the operation history DB. There are many methods for generating menu generation information for a communication partner. An example of obtaining a menu category as menu generation information will be described. As the menu category mentioned here, for example, categories such as “menu for friends”, “menu for family”, and “menu for workplace” can be considered.

  In the present embodiment, there are three menu categories A, B, and C. The attribute generation unit 11 refers to the association degree table as shown in FIG. 13 containing the numerical value indicating the degree of association with each menu category of each terminal operation, and the communication partner held in the operation history DB unit 11 The menu category usage is calculated for each communication partner from the record of the terminal operation, and the result is obtained in a table as shown in FIG. The menu category usage can be obtained, for example, by adding the menu category relevance for each operation recorded in the history DB.

  Finally, in step S32, the attribute generation unit 12 reflects the menu generation information for each communication partner obtained in the previous step S31 in the attribute DB unit 8. In the present embodiment, the menu category usage for each communication partner as shown in FIG. 14 obtained in the previous step S31 is reflected in the attribute DB unit 8. For example, for the communication partner, the menu category having the highest usage may be determined as the menu generation information corresponding to the communication partner, or a vector value having each menu category usage as an element may be used as the menu generation information. .

<Fifth embodiment>
In the present embodiment, as a method for acquiring menu generation information from the identifier of the communication partner, only the point of using an authentication database in which terminal usage conditions for each user are managed is a part that is not in the third embodiment. is there.

  Therefore, the block diagram of this embodiment is shown in FIG. 4, and as a method for obtaining menu generation information from the identifier of the communication partner, which is not a part of the third embodiment, there is a terminal usage condition for each user. A portion that uses a managed authentication database, more specifically, a method for constructing an attribute DB will be described with reference to the flowchart shown in FIG.

  In the following, the attribute generation unit 12, the authentication DB unit 13, and the group attribute DB unit 14 may be inside the communication terminal or on another terminal on the network.

  First, in step S40, the attribute generation unit 12 accesses the authentication DB unit 13, and acquires a list of all users on the database and information (user group information) of groups (user groups) to which each user belongs. .

  Next, in step S41, the attribute generation unit 12 accesses the group attribute DB unit 14 and acquires menu generation information corresponding to each group.

  Finally, in step S42, the attribute generation unit 12 builds menu generation information for the communication partner while referring to the user list acquired in step S40. As an example of the menu generation information to be generated, a menu category that requires an authority check when executing a “menu for managers”, a “menu for general users”, or the like can be considered. If such a menu category is used as menu generation information, unnecessary menu items can be hidden from unauthorized users, which is useful for restricting access to confidential information.

  Further, in the above, before the conversion unit 9 acquires the menu generation information based on the identifier of the communication partner in step S24 of the third embodiment, the attribute DB is constructed by the processing of step S40 to step S42. However, as shown below, the same operation can be realized by replacing step S24 of the third embodiment with the flowchart shown in FIG.

  In step S50, the conversion unit 9 accesses the authentication DB unit (user authentication information storage unit) 13 and checks the group to which the communication partner belongs.

  Next, in step S51, the conversion unit 9 accesses the group attribute DB unit (group attribute information storage unit) 14 and acquires menu generation information corresponding to the group to which the communication partner belongs. In order to cope with the case where the communication partner information is not in the authentication DB, menu generation information for a communication partner having no affiliated group may be prepared in the group attribute DB unit 14 (menu generation information assigning means). ).

  As described above, in the first to fifth embodiments of the present invention described above, it is transmitted when there is a certain time interval or a change in the state of the communication partner from the communication partner, or when a request is received from the own communication terminal. Additional information is added to the presence information.

  Specifically, in addition to the communication partner identifier and presence information regarding the current status of the communication partner, such as “busy”, “leaving away”, “meeting”, and “calling”, menu generation information is added. The communication terminal that receives them is configured to be used for operation menu generation.

  The menu generation information is information for presenting the operation menu to the terminal user according to the communication partner, and is the same as the conventional presence information in that it can be used as information for changing the operation menu display method. However, it differs in that the configuration of the operation menu and the display order and design of the menu items can be changed for each communication partner, and that the communication partner can change the contents and display method of the operation menu.

  Menu generation information includes menu categories, menu item lists, display order, layout information related to the display position on the display unit of the communication terminal, design information such as background color and character size and color, Any combination of information is directly described, or is indirectly described using numbers or character strings corresponding to the information combination.

  When the menu generation information is indirectly described using a menu generation information identifier such as a number or a character string, the menu generation information and the menu between the menu generation information sender terminal and the receiver terminal are used. The above-mentioned menu generation that the sender side terminal has transmitted by the configuration in which the correspondence relationship of the generated information identifier is shared in advance, the information on the correspondence relationship is held in an accessible network database, and the database is referenced. The information identifier can be converted into menu generation information by the receiver side terminal.

  Note that it is not always necessary to convert the menu generation information identifier described above into menu generation information such as a menu category, menu item list, display order, layout information, and design information.

  Furthermore, an operation menu to be presented to the user of the communication terminal is created using the menu generation information or the identifier of the menu generation information and presence information. The creation of the operation menu may be a method of generating the operation menu from the beginning each time based on the menu generation information provided from the communication partner.

  Or prepare several templates given specific values as design information such as menu item list, display order, layout information about display position on display part of communication terminal, background color, character size and color, etc. Alternatively, it may be created by selecting and processing a template based on presence information and operation menu generation information.

  Even if the menu generation information is not included in the information received from the communication partner, the menu generation information is obtained based on an identifier such as an e-mail address or SIP-URI that can identify the communication partner. Also good.

  The menu generation information obtained based on the identifier of the communication partner is fixed to the communication partner and does not change unless the menu generation information is explicitly given. The menu generation information obtained from the original can be considered as one attribute of the communication partner that does not change. The term attribute indicates menu generation information obtained based on the identifier of the communication partner.

  Further, as an example of the attribute generation means in the present invention, a method of using an operation history for each communication partner may be used. If this method is adopted, menu generation information cannot be constructed for communication partners with no operation history remaining. To deal with such cases, prepare default menu generation information. Is preferred.

  Moreover, you may utilize the authentication database currently used when using a communication terminal. In this case, it is assumed that the user is managed in units called groups on the authentication database, and the user belongs to at least one group.

  First, in order to associate the menu generation information with each group registered in the authentication database and obtain the menu generation information of the communication partner, the menu generation information corresponding to the user group to which the communication partner belongs is read. .

  If there is a possibility that the user belongs to two or more user groups, in order to obtain menu generation information of the communication partner by associating the menu generation information with each combination of user groups registered in the authentication database Is configured to read out menu generation information corresponding to a combination of one or more user groups to which communication partners belong.

  Also, by preparing menu generation information for a user group that is not registered in the authentication database, it is possible to cope with cases where the communication partner is not registered in the authentication database.

  As described above, according to the embodiment of the present invention, the configuration, menu items, display order, and design of the operation menu displayed on the display unit on the reception side can be changed based on the menu generation information transmitted from the transmission side. In addition, it is possible to provide a communication system, a method, and a program that can change the contents of the operation menu and how to display the operation menu on the receiving side.

BRIEF DESCRIPTION OF THE DRAWINGS The block diagram for demonstrating the whole structure based on 1st Embodiment of the communication system of this invention is shown. The block diagram for demonstrating the whole structure based on 2nd Embodiment and 3rd Embodiment of the communication system of this invention is shown. The block diagram for demonstrating the whole structure based on 4th Embodiment of the communication system of this invention is shown. The block diagram for demonstrating the whole structure based on 5th Embodiment of the communication system of this invention is shown. The flowchart for demonstrating operation | movement based on 1st Embodiment of the communication system of this invention is shown. An example of the correspondence table of the menu generation information identifier and the menu generation information according to the embodiment of the communication system of the present invention is shown. 6 shows an example of a correspondence table of menu templates for combinations of menu generation information identifiers and presence information according to the embodiment of the communication system of the present invention. 6 shows an example of a correspondence table of menu templates for combinations of menu generation information identifiers and presence information according to the embodiment of the communication system of the present invention. The flowchart for demonstrating operation | movement based on 2nd Embodiment of the communication system of this invention is shown. An example of the correspondence table of the communication partner identifier and menu generation information according to the embodiment of the communication system of the present invention is shown. The flowchart for demonstrating operation | movement based on 3rd Embodiment of the communication system of this invention is shown. The flowchart for demonstrating the process which builds attribute DB based on 4th Embodiment of the communication system of this invention is shown. An example of the table which shows the relevance degree of each menu category with respect to terminal operation based on embodiment of the communication system of this invention is shown. An example of the table which shows the use degree of each menu category with respect to a communication other party based on embodiment of the communication system of this invention is shown. The flowchart for demonstrating the process which builds attribute DB based on 5th Embodiment of the communication system of this invention is shown. The flowchart for demonstrating the process which acquires menu generation information from the identifier of a communicating party based on 5th Embodiment of the communication system of this invention is shown. An example of the data format based on 1st and 2nd embodiment of the communication system of this invention is shown. The flowchart for demonstrating the process based on 1st and 2nd embodiment of the communication system of this invention is shown. An example of the menu template based on 1st and 2nd embodiment of the communication system of this invention is shown. An example of the menu template based on 1st and 2nd embodiment of the communication system of this invention is shown.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Transmission part 2 Reception part 3 Extraction part 4 Processing part 5 Memory 6 Display part 7 Menu DB part 8 Attribute DB part 9 Conversion part 10 Operation input part 11 Attribute history DB part 12 Attribute generation part 13 Authentication DB part 14 Group attribute DB part

Claims (9)

In a communication system capable of communicating with each other with a plurality of communication terminals provided with a menu display means for displaying an operation menu related to its own function,
The communication terminal is
Destination information extraction for receiving and extracting presence information regarding the identifier and state transmitted from the communication partner and menu generation information for displaying the operation menu desired by the communication partner on the menu display means Means,
Template storage means for storing a plurality of types of templates related to the display of the operation menu;
Template information providing means for selecting the corresponding template from the template storage means based on the presence information extracted by the counterpart information extraction unit and the menu generation information, and providing the template to the menu display means;
A communication system comprising: The communication terminal is
Self-information storage means for storing the presence information and the menu generation information related to the self;
Self-information transmitting means for transmitting the presence information and the menu information stored in the self-information storage means during communication with a communication partner;
The communication system according to claim 1, further comprising: The communication terminal is
Attribute information storage means for storing both menu generation information corresponding to the identifier of the communication partner and correspondence information for determining the correspondence thereof as attribute information;
Conversion information acquisition means for acquiring menu generation information stored in the attribute information storage means based on the identifier included in the presence information transmitted from the communication partner;
The communication system according to claim 1, further comprising: The attribute information storage means includes
The communication system according to claim 3, further comprising: correspondence information changing means for arbitrarily changing the correspondence information that determines the relationship between the identifier and the menu generation information. The communication terminal is
Operation history information storage means for associating the identifier of the communication partner and its own operation history with each other and storing them as operation history information;
Attribute information generating means for generating the attribute information based on the operation history information stored in the operation history information storage means;
The communication system according to claim 3, further comprising: The communication terminal is
User authentication information storage means for storing user group information in which usage conditions of the communication terminal are defined, and user information of users constituting a user group belonging to the user group information;
Group attribute information storage means for storing menu generation information set for each user group;
Menu generation information assigning means for identifying the user group to which the user belongs from the user authentication information storage means based on the identifier of the user who is a communication partner, and assigning menu generation information corresponding to the user group;
The communication system according to claim 4, wherein the communication system is provided. In a communication method capable of communicating with each other with a plurality of communication terminals provided with a menu display means for displaying an operation menu related to its own function,
In the communication terminal,
The other party information extracting means receives presence information on the identifier and state transmitted from the communication partner, and menu generation information for causing the menu display means to display an operation menu desired by the communication partner. Extracting, and
Storing a plurality of types of templates related to display of the operation menu by a template storage means;
Selecting the corresponding template from the template storage unit based on the presence information extracted by the counterpart information extraction unit and the menu generation information by a template information providing unit, and providing the selected template to the menu display unit;
A communication method characterized by comprising: In a communication program capable of communicating with each other with a plurality of communication terminals provided with a menu display means for displaying an operation menu related to its function,
In the communication terminal,
The other party information extracting means receives presence information on the identifier and state transmitted from the communication partner, and menu generation information for causing the menu display means to display an operation menu desired by the communication partner. Extracting, and
Storing a plurality of types of templates related to display of the operation menu by a template storage means;
Selecting the corresponding template from the template storage unit based on the presence information extracted by the counterpart information extraction unit and the menu generation information by a template information providing unit, and providing the selected template to the menu display unit;
A communication program characterized by comprising:   The communication program according to claim 8, wherein the communication program can be installed and operated on a server arranged on a network.

Images