WO2014017283A1 - Dispositif de terminal, procédé de commande pour dispositif de terminal et programme - Google Patents

Dispositif de terminal, procédé de commande pour dispositif de terminal et programme Download PDF

Info

Publication number
WO2014017283A1
WO2014017283A1 PCT/JP2013/068624 JP2013068624W WO2014017283A1 WO 2014017283 A1 WO2014017283 A1 WO 2014017283A1 JP 2013068624 W JP2013068624 W JP 2013068624W WO 2014017283 A1 WO2014017283 A1 WO 2014017283A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
user
unit
sender information
terminal device
Prior art date
Application number
PCT/JP2013/068624
Other languages
English (en)
Japanese (ja)
Inventor
加藤　禎人
Original Assignee
株式会社コナミデジタルエンタテインメント
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社コナミデジタルエンタテインメント filed Critical 株式会社コナミデジタルエンタテインメント
Publication of WO2014017283A1 publication Critical patent/WO2014017283A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/57—Arrangements for indicating or recording the number of the calling subscriber at the called subscriber's set
    • H04M1/575—Means for retrieving and displaying personal data about calling party
    • H04M1/576—Means for retrieving and displaying personal data about calling party associated with a pictorial or graphical representation

Definitions

  • the present invention relates to a technique for browsing a message with sender information.
  • the present invention has been made in view of the above-described circumstances, and one of its purposes is to provide a technique that is less likely to cause a problem with sender information when a message is transmitted.
  • a terminal device is a terminal device that provides a message transmitted from each of a plurality of users so as to be viewable on a display unit, and is different for the same user.
  • a setting unit for setting a plurality of profile information corresponding to the sender information, a management unit for managing a plurality of users as transmission partners in association with each of the different sender information, and a plurality of users corresponding to the sender information
  • a transmission unit that transmits a message with the associated sender information among the different sender information, and a display control unit that displays the message on the display unit.
  • the profile information is information for specifying the sender of the message, such as the name of the sender, an image related to the person image, and the like. Therefore, different sender information corresponds to the same user (sender) but different profile information.
  • the part or all of the plurality of users may be a part of the plurality of users corresponding to the sender information, or all of the plurality of users. It is also intended to be good.
  • the management unit is capable of managing a user as a transmission partner for each group, and associates one sender information of the different sender information with one group, and the transmission unit May be configured to attach associated sender information to the users constituting the one group.
  • the display control unit may display each of the plurality of groups managed by the management unit on the display unit by dividing each group by sender information.
  • the display control unit may display each of a plurality of other users managed by the management unit on the display unit by dividing the information by sender information.
  • the display control unit displays other users classified and displayed for each sender information so as to be movable from one sender information to another sender information, and the management unit displays the display control unit.
  • the sender information associated with the other user may be changed to the other sender information.
  • the cooperation unit in the case where a cooperation unit that cooperates with an external service server that provides an external service is provided, and the user set by the setting unit is a user of the external service, the cooperation unit
  • the service profile information may be acquired, and the setting unit may set the sender information of the user to sender information reflecting the profile information acquired by the cooperation unit.
  • browsing of the message is possible between users who have passed through a predetermined procedure, and the cooperation unit allows another user of the external service to browse the message to the external service server. You may instruct them to invite you.
  • “invite” refers to prompting participation in viewing the message.
  • the information processing apparatus further includes a determination unit that can access a registration unit in which contact information for uniquely identifying the contact information of the user is registered in advance, and the determination unit includes the contact information of other users.
  • the management unit determines whether the acquired contact information is registered in the registration unit, and the management unit registers the acquired contact information of other users in the registration unit. In the case where it is determined that any one of the different sender information is set in advance or fixedly associated with the other user.
  • the present invention can be conceptualized not only by a terminal device but also by a terminal device control method and a program that causes a computer to function as a terminal device.
  • the program may be stored in a recording medium. If this recording medium is used, the program can be installed in the computer, for example.
  • the recording medium storing the program may be a non-transitory recording medium such as a CD-ROM.
  • the person is not limited to acquaintances who are acquainted with each other, but has no acquaintance and has only a network relationship (net acquaintance)
  • the chat is being used even between each other. For this reason, in the chat, communication can be enjoyed regardless of whether there is an acquaintance.
  • the terminal device is configured to switch the setting contents of the profile information in accordance with the message transmission partner like the chat partner as follows.
  • FIG. 1 is a diagram for explaining the outline.
  • sender information 1 is used when chatting with a user B who is an acquaintance
  • sender information 2 is used when chatting with a user C who is an internet acquaintance.
  • the profile information includes user name information that defines a name and user image information that is used as a profile image.
  • the real name of the user A is used as the user name information
  • an image showing the actual person image of the user A is used as the user image information.
  • the profile information of the sender information 2 a pseudonym such as the handle name or nickname of the user A is used as the user name information, and a filled image showing only the appearance of the user A is used as the user image information.
  • the user image information of the sender information 2 may be a default image prepared in advance, a deformed image obtained by abstracting the person image of the user A, or a user of the sender information 1
  • the image information may be image processed to such an extent that the person image of user A cannot be specified.
  • the message is transmitted to the management server.
  • the sender information 1 of the user A and information indicating that the other party is the user B are attached to the message.
  • the management server transfers the message together with the sender information 1 to the terminal device of user B. Accordingly, since the sender information 1 is displayed together with the message on the terminal device of the user B, the user B specifies that the sender is the user A himself and then sends the message of the user A. Can be viewed.
  • the message indicates that the sender information 2 of the user A and the partner is the user C. Is sent to the management server, and the management server transfers the message together with the sender information 2 to the terminal device of the user C. In the terminal device of the user C, the sender information 2 is sent together with the message. Is displayed. This makes it difficult for the user C to specify the real name or person image of the user A who is the message sender.
  • FIG. 2 is a block diagram showing an overall configuration of a system including the terminal device according to the first embodiment of the present invention.
  • a plurality of terminal devices 20-1, 20-2, 20-3,... are connected to the management server 10 via the mobile communication network Nb, the gateway 15, and the Internet Na. It becomes the composition.
  • the terminal devices 20-1, 20-2, 20-3,... are generally described without specifying the terminal devices, and therefore, the symbols “ ⁇ (hyphen)” and the following are omitted. It is simply “20”.
  • the management server 10 manages a chat user and group in addition to a function of transferring a message transmitted from a terminal device 20 of a user to a terminal device of a user as a counterpart. It has a function.
  • chat when a certain terminal device 20 is taken as a reference, chat between members composed of the user of the terminal device 20 and one or more other users, so-called chat, A group chat is assumed. For this reason, one group includes two or more people including the user of the terminal device 20.
  • FIG. 3 is a block diagram showing a hardware configuration of the management server 10.
  • the management server 10 includes a CPU (Central Processing Unit) 101 that controls the entire apparatus, a RAM (Random Access Memory) 102 that functions as the main memory of the CPU 101, and a ROM that stores a boot program and the like. (Read Only Memory) 103, an interface (I / F) 105 for communicating via a network, an RTC (Real Time Clock) 106 for outputting time information, and a storage unit 108 for storing various programs and data And including.
  • a database 118 managed by the CPU 101 is constructed in the storage unit 108.
  • the database 118 manages a table for registering user and group information, as will be described later.
  • management server 10 is constructed as a single unit in FIG. 2, it may be configured so that it is distributed to two or more units and is virtually seen as one unit when viewed from the outside.
  • some functions of the management server 10 may be constructed by a server that provides other services.
  • you may comprise so that the management server 10 may connect with the terminal device 20 via a relay server.
  • the terminal device 20 is, for example, a mobile phone operated by a user.
  • the terminal device 20 includes a touch panel 220 superimposed on the display panel 210, and a user can input necessary information and various instructions by touching the screen displayed on the display panel 210. It is a given configuration.
  • FIG. 4 is a block diagram illustrating a hardware configuration of the terminal device 20.
  • the terminal device 20 includes a CPU 201, a memory 202, an I / F 204, an RTC 206, a storage unit 208, a display panel 210, and a touch panel 220.
  • the CPU 201 controls the entire terminal device 20, and the memory 202 stores a basic program and an application program for executing chat in a nonvolatile manner.
  • This application program creates a message and sends it to the management server 10 or displays a message received from the management server 10 in a timeline.
  • the application program is downloaded from a specific site and installed in the terminal device 20. It has been done.
  • the I / F 204 communicates with the management server 10 via the mobile communication network Nb or the like.
  • the RTC 206 outputs time information of the current time.
  • a database 218 managed by the CPU 201 is constructed. Details of various tables and the like managed by the database 218 will be described later.
  • the display panel 210 is a flat display such as a liquid crystal display device or an organic EL (Electro Luminescence) device.
  • the touch panel 220 detects an operation position (two-dimensional coordinate value) for the screen displayed by the display panel 210 and supplies the detected position to the CPU 201.
  • the CPU 201 specifies the operation content on the touch panel 220 such as the moving direction, moving speed, and touch operation of the touch position based on the detection information.
  • the types of touch operations that can be specified include, for example, tap, flick, drag, pinch and the like.
  • tapping is an operation of tapping the display screen with a finger.
  • Flicking is an operation in which the object displayed on the screen is gently touched with a finger.
  • Dragging is an operation of moving an object displayed on the screen in contact with a finger.
  • Pinch is an operation of expanding or narrowing a display screen with two fingers in contact with each other.
  • the terminal device 20 is not limited to the mobile communication network Nb, and may be configured to be connected to a wireless LAN (Local Area Network). When connected to a wireless LAN, the terminal device 20 is connected to the management server 10 via a wireless base station (access point) and the Internet Na.
  • the terminal device 20 is not limited to a mobile phone, and may be a tablet computer or a PDA (Personal Digital Assistant).
  • the following functional blocks are constructed by executing predetermined programs and in the terminal device 20 by executing the application programs installed in advance.
  • FIG. 5 is a diagram illustrating functional blocks constructed by the management server 10 and the terminal device 20.
  • the setting unit 232 in addition to the operation detection unit 231, the setting unit 232, the management unit 233, the display control unit 234 and the transmission unit 236, a message registration table 235 and a profile registration table are stored in the database 218.
  • TB21, transmission partner management table TB22, and user information registration table TB23 are constructed.
  • the display area of the display panel 210 includes a partner list display unit 212, a message input unit 214, and a message display unit 216.
  • the operation detection unit 231 supplies operation information indicating the operation content to the display control unit 234 based on the detection signal of the touch panel 220, and when the message body is input to the message input unit 214 and a predetermined operation is performed, Various information is attached to the message and supplied to the transmission unit 236.
  • the various information includes a group ID for identifying the selected group and a user ID of the sender.
  • the setting unit 232 sets a profile for each sender information in the profile registration table TB21, and the management unit 233 manages the transmission partner in which information about the terminal device 20 and a group to be a chat partner is registered. It manages the table TB22 and the user information registration table TB23 in which user profile images are registered. Details of these tables will be described later.
  • the display control unit 234 controls the display content of the display panel 210 so that the operation information supplied from the operation detection unit 231 is reflected. Further, the display control unit 234 displays a list of transmission partners on the partner list display unit 212 or stores a message transferred from the management server 10 on the message display unit 216 in the message registration table 235, and then reads out the transmission date and time. The timeline is displayed in the order of.
  • the message registration table 235 stores messages by users and other users in association with each group (group ID) as will be described later.
  • the transmission unit 236 transmits the message supplied from the operation detection unit 231 to the management server 10 together with various attached information.
  • the user / group registration table TB11 is constructed in the database 118 in addition to the receiving unit 121, the transfer destination specifying unit 123, and the transfer unit 125.
  • the accepting unit 121 accepts a message to which various information is attached from the terminal device 20.
  • the user / group registration table TB11 is registered with information about users and groups that can participate in chat, which is the service, although details are not shown in particular. In other words, this chat can be performed only after registration in the user / group registration table TB11 through a predetermined procedure such as registration of an email address or password.
  • the user / group registration table TB11 for a user, name information of the user, a user ID for uniquely identifying the user, and information for accessing the terminal device of the user.
  • name information of the group a group ID for uniquely identifying the group, user IDs of members constituting the group, and the like are registered.
  • the transmission partner management table TB22 in the terminal device 20 information about the group that becomes a chat partner with the terminal device 20 is registered, whereas in the user / group registration table TB11 in the management server 10, The difference is that information is registered for all users and all groups.
  • the transfer destination specifying unit 123 removes the user ID from the group ID and user ID included in the various information attached to the received message, from among the members of the group specified by the group ID (use) Information for accessing the user's terminal device is acquired with reference to the user / group registration table TB11. As a result, the transfer destination of the accepted message is specified.
  • the transfer unit 125 transfers the message received by the receiving unit 121 to the terminal device 20 whose transfer destination is specified.
  • FIG. 5 for convenience of explanation, attention is paid to one terminal device 20 (one user), and transmission / reception of information and messages between the terminal device 20 and the management server 10 is illustrated.
  • the management server 10 receives a message from the plurality of terminal devices 20, and conversely transfers the message to the plurality of terminal devices 20.
  • a large number of arrows toward the reception unit 121 indicate that messages are received from other terminal devices other than the focused terminal device 20, and a large number of arrows from the transfer unit 125 indicate other than the terminal device 20. This indicates that a message is also transmitted to the terminal device.
  • the profile registration table TB21 is a table in which profile information for identifying a message sender is registered.
  • FIG. 6 is a diagram illustrating an example of the profile registration table TB21.
  • profile information about the user of the terminal device 20 is set by the sender information 1 and the sender information 2.
  • a search ID and a telephone number are added as profile information in addition to the user name information and the user image.
  • the search ID is information for identifying a user by sender information, and can be arbitrarily set as long as the user does not overlap with other users, for example. This search ID is used when another user executes the search function.
  • the telephone number is not essential as profile information, but may be used as one piece of information for identifying the user.
  • FIG. 7 is a diagram showing an example of a profile registration screen for allowing the user to register and edit profile information.
  • the profile registration screen is displayed when the user performs a predetermined operation on the partner list screen described later on the terminal device 20.
  • an input field 271 for inputting a telephone number is displayed on the profile registration screen.
  • an input field 272 for inputting user name information and an input field 273 for inputting a search ID are displayed corresponding to each of the sender information 1 and the sender information 2.
  • the input fields 271, 272, and 273 are blank in the initial state, but if the information has already been registered in the profile registration table TB 21, the registered contents are reflected and displayed. Note that input, correction, and the like in the input fields 271, 272, and 273 are executed, for example, via a software keyboard that is displayed separately.
  • a selection field 274 for selecting a user image or the like is displayed corresponding to each of the sender information 1 and the sender information 2.
  • the selection field 274 is blank in the initial state, but if information is already registered in the profile registration table TB21, the registered content is reflected and displayed.
  • a screen for registering a user image is separately displayed, for example, input of a file used as user image information, designation, selection, etc., although not particularly shown. The user is prompted to do so.
  • the image processing to be applied may be selected for the selected user image information.
  • the selected user image is displayed in the selection field 274 for confirmation.
  • buttons 275 and 276 are displayed.
  • the button 275 is a software button for designating that the information input on the profile registration screen at the present time is reflected in the profile registration table TB21 and the screen returns to the partner list screen.
  • the operation detection unit 231 supplies the information input on the profile registration screen to the setting unit 232, and the setting unit 232 registers the information in the profile registration.
  • the display control unit 234 returns to the display of the partner list screen.
  • the button 276 is a software button for instructing to add sender information at the present time.
  • the transmission partner management table TB22 is a table for managing chat partners on the terminal device 20 side in units of groups.
  • FIG. 8 is a diagram illustrating an example of the transmission partner management table TB22.
  • the transmission partner management table TB22 for each group ID for identifying a group that can chat with the terminal device 20, name information, applicable sender information, and user IDs of members constituting the group. And are registered in association with each other.
  • the group name is registered if there are three or more members who constitute the group including the person who is the user of the terminal device 20, and the other party uses if the member is two persons including the person.
  • the person's name is registered. Of course, when there are two people, the name of the other user may be changed to the name of the group afterwards.
  • the applied sender information is information that defines sender information to be applied to members of the group. Specifically, if “1”, the sender information 1 is used, and if “2”, the sender information 2 is used. It stipulates.
  • the case where the maximum value of the number of members constituting one group is “5” is shown.
  • five user IDs A to E can be registered as members.
  • Member A is registered in the order of participation from the person who opened the group.
  • the transmission partner management table TB22 manages the members of the group as viewed from the terminal device 20, the members of each terminal device 20 are always included in the members of each group.
  • the person whose user ID is “xx31” is the user himself / herself of the terminal device 20.
  • ⁇ null> indicates an unset empty state.
  • the group whose group ID is “ax17” includes the user himself / herself whose user ID is “xx31” and the other user whose user ID is “xx23” and whose name is “Caseke”.
  • the sender information 2 is defined as the sender information of the user himself / herself.
  • the group with the group ID “ay22” has the name “Shibuya-kai” and the user IDs “xx31” (user himself), “xx33”, “xx34”, “xx39” 4 It is defined that the sender information 1 is used as the sender information of the user himself / herself when chatting with the members of the group.
  • any one sender information is commonly associated with one group, chatting using different sender information for one group, that is, the same as that performed on an electronic bulletin board. It is possible to prevent a person from writing using a different account.
  • a group participating in a chat with any sender information can be prohibited from participating in sender information other than the participating sender information.
  • the maximum value of the number of members constituting the group is set to “5”. However, the purpose is not limited to this. Needless to say, there is no need to set an upper limit for the number of persons or the number of persons.
  • the user information registration table TB23 is not particularly shown, but for each user ID, name information and profile image information are registered as essential, and age, gender, date of birth, e-mail address, address, etc. are arbitrarily registered. It is a thing.
  • the user information registration table TB23 and the transmission partner management table TB22 are associated with each other by a user ID to form separate tables, but it is needless to say that one table may be used.
  • FIG. 9 is a flowchart showing the chat operation by the application program on the terminal device 20.
  • the operation detecting unit 231 Instruct the setting unit 232 and the management unit 233 as follows. Specifically, the operation detection unit 231 instructs the setting unit 232 to acquire user name information of the terminal device 20, while the management unit 233 has information on groups that can chat with the terminal device 20. The acquisition of is instructed.
  • the setting unit 232 accesses the profile registration table TB21 and reads the user name information registered for the user of the terminal device 20 for each of the sender information 1 and the sender information 2.
  • the management unit 233 accesses the transmission partner management table TB22 for the group capable of chatting, and acquires the name information and the user IDs of the constituent members together with the applicable sender information.
  • Each of the setting unit 232 and the management unit 233 supplies the acquired information to the operation detection unit 231, and the operation detection unit 231 transfers the information to the display control unit 234. Based on the transferred information, the display control unit 234 creates a partner list screen that allows chatting, and displays it on the display panel 210. Thereby, the partner list screen is displayed on the display panel 210 (step Sa11).
  • FIG. 10 and 11 are diagrams illustrating an example of a partner list screen.
  • partner names that can chat with the terminal device 20 are displayed in a list.
  • the name here is the name of the group if there are 3 or more members in the group, including the user, and the name of the other user if there are 2 members who have not been changed afterwards. is there.
  • the partner list screen is virtually one screen, but due to restrictions on the display area allocated to the partner list display unit 212, the one screen is divided into left and right parts in FIG. 10 and FIG. . Of the divided screens, the left half is shown in FIG. 10 and the right half is shown in FIG.
  • the display control unit 234 creates such a partner list screen as follows. That is, the display control unit 234 displays the name information read from the transmission partner management table TB22 whose application sender information is “1” in the left half of the partner list screen, and the application sender information is “ 2 ”is displayed in the right half of the opponent list screen.
  • the display control unit 234 displays the name of the user specified by the user name information of the profile information in the sender information 1 read from the profile registration table TB21 in the tab portion on the left half of the partner list screen. That is, the real name of the user of the terminal device 20 is displayed to inform that the other party displayed as a list in the left half corresponds to the sender information 1.
  • the display control unit 234 displays the name of the user specified by the user name information of the profile information in the sender information 2 read from the profile registration table TB21 in the tab portion on the right half of the partner list screen. That is, the handle name of the user of the terminal device 20 is displayed to inform that the other party displayed as a list in the right half corresponds to the sender information 2.
  • the display control unit 234 displays a profile image associated with the partner user in the vicinity of the name display part of the partner user on the partner list screen, and uses it near the name display part of the group.
  • a button 255 for confirming the member is displayed while indicating that the group is a group of three or more persons including the user (a group in which a message is transmitted to a plurality of members other than the user).
  • the partner list display unit 212 the partner user who can chat or the group of three or more people including the user himself / herself is classified into the sender information 1 and the sender information 2 and displayed.
  • the other users who can chat and a group of three or more groups are displayed as a list, but the other users and a group of three or more people may be displayed as a list. .
  • selection of a chat partner is performed, for example, when the user touches the display portion of the name of the partner user or the name of the group.
  • the display control unit 234 displays buttons 249, 251, and 253 under the partner list display unit 212 in common in FIGS. 10 and 11.
  • the button 249 is a software button that instructs to shift to the above-described profile registration screen.
  • the button 251 is a software button for instructing editing (new registration, deletion, etc.) of the chat partner, and the button 253 is a software button for instructing termination of the application program.
  • the operation detection unit 231 determines whether or not an appropriate operation has been performed on the touch panel 220 (step Sa12).
  • the appropriate operation is an operation within a range assumed in advance, for example, an operation on a button display portion, a name name display portion, or the like, or an operation such as the flick described above. If there is no operation, or if the operation is an invalid operation that is not expected even if there is an operation (if the determination result in step Sa12 is “No”), the processing procedure returns to step Sa11. For this reason, the display of the partner list screen continues until some appropriate operation is performed.
  • the operation detection unit 231 first determines whether or not the operation is an operation on the display portion of the button 253 ( Step Sa13).
  • step Sa13 If it is an instruction to end (if the determination result in step Sa13 is “Yes”), the operation detection unit 231 notifies the display control unit 234 to that effect and ends the application program. If it is not an instruction to end (if the determination result in step Sa13 is “No”), the operation detection unit 231 next selects the chat partner, that is, the name of the partner user or the name of the group. It is determined whether or not the operation is a touch on the display portion (step Sa21).
  • step Sa27 a process corresponding to the operation is executed (step Sa27). Examples of such processing include the following in this embodiment. That is, an operation to the buttons 249, 251 and 255, an operation to a profile image, a drag (move) of a display portion of a partner user name or a group name, and a partner list screen flick.
  • the display control unit 234 separately displays an editing screen of the chat partner so that the user can newly register a group, change a name, add a member, Deletion is instructed.
  • the chat partner is edited, the edited content is reflected in the transmission partner management table TB22 in the terminal device 20 of the user himself / herself, and is also transmitted to the management server 10 and stored in the user / group registration table TB11. In addition to being reflected, it is transferred to the terminal device 20 of the other member via the management server, and is also reflected in the transmission partner management table TB22 in the terminal device 20 of the other member.
  • the operation detection unit 231 instructs the management unit 233 to acquire information on the constituent members of the group corresponding to the button 255.
  • the management unit 233 first accesses the transmission partner management table TB22 to acquire the user IDs of the members of the group, and secondly accesses the user information registration table TB23 to correspond to the user IDs. Get name information and profile image.
  • the management unit 233 supplies the acquired information to the operation detection unit 231, and the operation detection unit 231 transfers the information to the display control unit 234. Based on the transferred information, the display control unit 234 creates and displays a screen for confirming the constituent members of the group corresponding to the button 255.
  • FIG. 12 is an example of a screen for confirming group members in the partner list screen.
  • FIG. 12 shows the configuration of the group when the button 255 corresponding to the group whose group ID is “ay22” and whose name is “Shibuya Kai” in the transmission partner management table TB22 shown in FIG. 8 is operated. This is an example in which the names and profile images of four members who have the user IDs “xx31”, “xx33”, “xx34”, and “xx39” are displayed.
  • the operation on the profile image on the partner list screen is an instruction to display detailed information other than the name and profile image for the user.
  • the operation detection unit 231 instructs the management unit 233 to acquire detailed information about the user corresponding to the profile image.
  • the management unit 233 accesses the user information registration table TB23 and acquires detailed information corresponding to the user.
  • the detailed information is supplied to the display control unit 234 via the management unit 233 and the operation detection unit 231, and the display control unit 234 displays the detailed information in the vicinity of the profile image (not shown).
  • different password locks can be applied to the left half corresponding to the sender information 1 and the right half corresponding to the sender information 2 in the partner list display unit 212. It is. For example, when the password lock corresponding to the sender information 2 is applied, a part of the right half displayed on the right side of the left half of the partner list screen shown in FIG. 10 is not displayed. Here, if a flick operation is performed in the right direction, a password input screen is displayed, and the right half of the partner list screen shown in FIG. 11 is displayed after the password is input.
  • the third party can send the transmission partner management table TB22 or the user information registration table TB23 for the other party whose display is hidden. It is impossible to determine whether or not it is registered.
  • the operation of dragging the display portion of the name of the partner user or the name of the group from one of the left half / right half in the partner list display unit 212 to the other is an operation of changing the sender information applied to the group. For this reason, when the name or the name display portion is long pressed to distinguish it from the selection of the chat partner and then an operation of moving by dragging as shown in FIG. 13 is performed, the operation detection unit 231 displays the operation status. Is supplied to the display control unit 234. The display control unit 234 displays the name or the name display part while moving the name or the name display part as shown in FIG. On the other hand, the operation detection unit 231 supplies information indicating the destination to the management unit 233 together with the group ID of the group that has been moved.
  • the management unit 233 accesses the transmission partner management table TB22 and rewrites the applicable sender information corresponding to the group ID to information corresponding to the movement destination. For example, as shown in FIG. 13, when an operation is performed to move the display part of the name “Yuko Ito” from the left half to the right half on the partner list screen, “Yuko Ito” and the user himself / herself are members. The information indicating that the destination is the right half is supplied to the management unit 233 together with the group ID “ay27” of the group. As a result, the management unit 233 rewrites the applicable sender information for the group from “1” to “2” in the transmission partner management table TB22 as shown in FIG.
  • a part of the partner whose sender information can be changed may be limited.
  • a button 241 may be displayed so that it can be distinguished from a chat partner that cannot be changed.
  • a button 243 may be displayed so that the chat partner can be distinguished from a changeable chat partner.
  • step Sa27 the processing procedure returns to the display of the partner list screen in step Sa11.
  • step Sa21 If the operation performed on the partner list screen is an operation for selecting a chat partner (if the determination result in step Sa21 is “Yes”), the operation detection unit 231 notifies the display control unit 234 of the fact, Upon receiving this notification, the display control unit 234 executes reception processing for receiving a message from the management server 10 (step Sa22).
  • a chat partner when a chat partner is selected, it is good also as a premise of a reception process that self profile information is set to profile registration table TB21 about the applicable sender information with respect to the said chat partner. If not set, the user may be prompted to move to the profile registration screen, for example, to operate the button 249, and the reception process may be executed after the sender information is registered.
  • the reception process is a process in which the display control unit 234 receives the message transmitted from the terminal device 20 of the member constituting the selected chat partner group via the management server 10.
  • the display control unit 234 stores the received message in the message registration table 235 in association with the selected group.
  • the accompanying information includes a group ID, the sender user ID, the sender name information, and the transmission date and time. Information and profile image information are attached.
  • the display control unit 234 may manage messages stored in the message registration table 235 so that messages older than the current date and time by a certain period or longer are sequentially deleted.
  • the display control unit 234 displays a message input / display screen in the display area of the display panel 210 (step Sa23).
  • FIG. 17 is a diagram illustrating an example of a message input / display screen, which includes a message display unit 216.
  • the display control unit 234 reads the message associated with the selected chat partner group from the message registration table 235 together with the accompanying information, and causes the message display unit 216 to display the timeline. Specifically, the display control unit 234 sorts the read messages in the order of the time indicated by the transmission date and time information of the incidental information, and arranges and displays the newer messages, for example, on the upper side of the message display unit 216. Let For this reason, in the figure, the timeline display in the areas (1) to (4) is the latest in the area (1) and the oldest in the order of the areas (2), (3), and (4).
  • a profile image indicating the sender is displayed at the right end of the screen, for example, and the message body is surrounded by a balloon as if it were emitted from the profile image. It is expressed. Further, the message transmission time and the sender name information are also displayed in the vicinity of the member profile image. For this reason, in a group, the place as if chatting is shared among members.
  • the timeline display of the message display unit 216 in FIG. 17 is an example when the group having the group ID “ay22” and the name “Shibuya-kai” in FIG. 8 is selected as the chat partner.
  • “1” is set in the applicable sender information as shown in FIG. 8, so the message display in the area (2), that is, the message by the user of the terminal device 20 itself. Is displayed, the sender information 1 is applied to each of the profile image and the name information.
  • this timeline display is shared among the members of the group, it is possible to easily identify the sender of the message in the chat from the viewpoint of other members familiar with the real world.
  • the terminal is based on the operation of the user among the message input / display screens displayed by the selection of the chat partner.
  • each of the profile image and the name information is displayed in the changed sender information by switching back to the message transmitted in the past.
  • the message sent based on the user's operation that is, the area (2)
  • each of the profile image and the name information is switched from the one shown in FIG. 17 to the one shown in FIG.
  • only one message transmitted based on the operation of the user is displayed, but the same applies to the case where there are a plurality of messages, and the profile image and name information in the plurality of message displays can be switched respectively. .
  • the message by itself may be displayed in a manner that can be distinguished from messages by other members.
  • the profile image may be omitted, the balloon shape of the message may be different from the others, or the display color or font of the message body may be different.
  • the message input / display screen includes a message input unit 214 in addition to the message display unit 216 and buttons 255 and 257 as shown in FIG.
  • the message input unit 214 is an area for inputting a message to be transmitted using a software keyboard or the like
  • the button 255 is a software button for confirming the content of the message input to the message input unit 214 and instructing transmission.
  • the button 257 is a software button for instructing to return to the previous partner list screen.
  • step Sa24 determines whether or not an appropriate operation has been performed. If there is no operation, or if the operation is an invalid operation that is not expected even if there is an operation (if the determination result in step Sa24 is “No”), the processing procedure returns to step Sa22. For this reason, the processing procedure circulates in steps Sa22 ⁇ Sa23 ⁇ Sa24 ⁇ (Sa22) until any appropriate operation is performed, so that the message input / display screen continues and a new message is sent via the management server 10. Etc., the message is additionally displayed in the timeline.
  • the following operations are assumed as appropriate operations for the message input / display screen. That is, firstly, an operation such as a tap on the display part of the button 255, a second operation such as a tap on the display part of the button 257, and a third operation are assumed. Other operations include a flick for scrolling a message, a pinch for enlarged display, an input operation on the message input unit 214, and the like.
  • the operation detection unit 231 When an appropriate operation is performed (when the determination result in step Sa24 is “Yes”), the operation detection unit 231 first instructs the operation to transmit a message, that is, taps on the display portion of the button 255, or the like. It is determined whether or not the operation has been performed (step Sa25). When the operation is performed on the button 255 (when the determination result in Step Sa25 is “Yes”), the operation detection unit 231 displays the message input to the message input unit 214 at the time of the operation as an instruction for the transmission. Of the time information (transmission date and time) acquired from the RTC 206, the group ID of the chat partner selected in the previous step Sa21, the own user ID, and the applicable sender information set for the group ID.
  • the user name information and the profile image information are attached as supplementary information and supplied to the display control unit 234 and the transmission unit 236.
  • the display control unit 234 stores the supplied message together with the accompanying information in the message registration table 235 in association with the selected group ID.
  • the transmission unit 236 transmits the supplied message to the management server 10 together with the accompanying information (step Sa26). Thereafter, the processing procedure returns to Step Sa22.
  • the reception unit 121 receives a message or the like, and the transfer destination specifying unit 123 specifies the transfer destination of the received message from the group ID and the user ID of the sender included in the incidental information. Specifically, as described above, the transfer destination specifying unit 123 specifies, as a transfer destination of the message, the user's terminal device excluding the sender's user ID among the members of the group indicated by the group ID. To do.
  • the reason why the sender of the message is excluded as the forwarding destination is that the message is stored in the message registration table 235 in the terminal device 20 of the sender and does not need to be forwarded. Then, the transfer unit 125 transfers the received message to the specified transfer destination terminal device 20.
  • the transfer destination terminal device 20 stores the application program in the message registration table 235 in the reception process (step Sa22), and displays the next message input / display screen (step Sa23).
  • the message will be additionally displayed in the timeline.
  • the transmitted message is shared among the members of the group.
  • step Sa25 When the operation performed on the message input / display screen is not an instruction to send a message (when the determination result in step Sa25 is “No”), the operation detection unit 231 next determines that the operation is the other party. It is determined whether or not the operation is to designate returning to the list screen, that is, an operation such as a tap on the display portion of the button 257 (step Sa28). When the operation is performed on the button 257 (when the determination result in Step Sa28 is “Yes”), the processing procedure returns to the display of the partner list screen in Step Sa11.
  • step Sa28 If it is not a return operation (if the determination result in step Sa28 is “No”), the processing procedure proceeds to step Sa29, and the processing corresponding to the performed operation, specifically, the other mentioned above as the third Processing according to the operation is executed (step Sa29). Thereafter, the processing procedure returns to Step Sa22.
  • the sender information applied to the chat partner can be easily and visually operated on the partner list screen.
  • FIG. 19 is a block diagram illustrating an overall configuration of the system 1 including the terminal device 20 according to the second embodiment.
  • each of the external service servers 30 and 40 is connected to the Internet Na as compared with the first embodiment shown in FIG.
  • the external service server 30 provides an external service A
  • the external service server 40 provides an external service B.
  • Each of the external services A and B provides a service related to a community such as SNS (Social Networking Service) different from the above chat, or provides a service of an application such as a game. Registration of account information such as name is a requirement.
  • SNS Social Networking Service
  • FIG. 20 is a diagram showing functional blocks constructed by the management server 10, the terminal device 20, and the external service server 30 when the second embodiment is applied.
  • the external service server 30 is illustrated and the external service server 40 is omitted, but the external service server 40 has the same configuration as the external service server 30.
  • the cooperation unit 240 is further constructed on the terminal device 20 side as compared with the first embodiment shown in FIG. 5.
  • the cooperation unit 240 communicates with the external service server 30 (40).
  • the cooperation unit 240 when the user of the terminal device 20 is a person who can receive the provision of the external service A (B), the use registered in the external service server 30 (40). The user's account information.
  • a communication unit 312, a control unit 314, and a user registration table TB31 are constructed on the side of the external service server 30, .
  • the communication unit 312 communicates with the illustrated terminal device 20 and other terminal devices, and controls the control unit 314 and each unit inside the server.
  • the user registration table TB31 registers member account information when providing the external service A.
  • the operation detection unit 231 notifies the display control unit 234 of the operation,
  • the display control unit 234 displays a profile registration screen in the display area of the display panel 210.
  • FIG. 21 is a diagram illustrating an example of a profile registration screen according to the second embodiment.
  • the display control unit 234 has a button 261 for each of the sender information 1 and the sender information 2 compared to the profile registration screen (see FIG. 7) of the first embodiment. 262 is displayed.
  • the button 261 is a software button for designating acquisition of account information for the external service A
  • the button 262 is a software button for designating acquisition of account information for the external service B.
  • the operation detection unit 231 notifies the cooperation unit 240 of the operation.
  • the cooperation unit 240 requests the external service server 30 that provides the external service A to return the account information of the user.
  • the control unit 314 that has received the request via the communication unit 312 accesses the user registration table TB31 and first determines whether or not the user is a member of the external service A. If it is a member, secondly, name information and a profile image are acquired from the account information of the user and returned to the cooperation unit 240 via the communication unit 312.
  • the cooperation unit 240 Upon receiving a reply such as name information, the cooperation unit 240 supplies the name information and the like to the operation detection unit 231.
  • the operation detection unit 231 transfers the name information and the like to the display control unit 234, and the display control unit 234
  • the name information is reflected in the input field 272 corresponding to the sender information 2, and the acquired profile image is reflected in the selection field 274 corresponding to the sender information 2.
  • FIG. 22 is an example of the display of the profile registration screen at this time.
  • This screen is an example in the case where “Yujiro Takahashi” who is a user of the terminal device 20 is registered in the external service A with the name “Y. Takahashi”, and is displayed in the selection field 274 corresponding to the external service A. As shown, it is an example in the case where a profile image different from chat is registered. Further, in this example, the display portion of the button 261 corresponding to the sender information 2 is inverted, and a state in which account information for the external service A is acquired is shown.
  • the display portion of the button 275 is touched by the user, the content displayed on the current profile registration screen, that is, the profile information corresponding to the sender information 2 in the profile registration table TB21 is displayed in the external service server.
  • the name information and profile image information acquired from 30 are rewritten.
  • the name information registered in the external service A as the sender information is continuously used. it can.
  • the sender since the sender is the same for the external service A and the chat, it is possible to avoid misidentification that they are different persons.
  • the case where the name information registered in the external service A is acquired has been described as an example.
  • the name information registered in the external service B can also be acquired by touching the display portion of the button 262. .
  • buttons 261 and 262 corresponding to the sender information 2 are operated has been described as an example. However, as described later, if the restriction of using the sender information 1 as a real name is relaxed, the sender information 1 is also applicable. Further, the name information acquired from the external service server and displayed in the input field 272 may be edited, or the profile image information may be changed. Note that when name information or profile image information is changed as a result of editing, the information is no longer different from the information acquired by operating the button 261 or the button 262, and thus the display part may be reversed.
  • the cooperation unit 240 requests the external service server 30 to return the account information of the user, for example, another user who has a friendship with the user in the external service A (here, E and In contrast, the external service server 30 may be instructed to be invited to the chat in the embodiment.
  • the control unit 314 that has received this instruction transmits an invitation notification to the terminal device of the user E via the communication unit 312.
  • FIG. 23 is a diagram illustrating a display example on the terminal device that has received the invitation notification.
  • the user E operates the display part of the button 264, it participates in the screen designated by the link destination of the management server 10, for example, the group composed of the user E and “Yujiro Takahashi” You may move to the screen for Further, when the user E operates the display portion of the button 265, the invitation is suspended and the state before the invitation notification is received is returned.
  • FIG. 24 is a diagram illustrating functional blocks constructed by the terminal device 20 and the management server 10 according to the third embodiment.
  • the contact information registration unit TB24 registers the contact information of the other party when used as a mobile phone or a terminal device in the terminal device 20. Specifically, it is a table in which the name of the communication partner and the contact information such as the telephone number and mail address of the partner are registered in association with each other. Note that while the transmission partner management table TB22 and the user information registration table TB23 register only those who can chat, this contact information registration unit TB24 shows the other parties that can communicate other than the chat. It differs in that it is registered.
  • the determination unit 242 determines whether or not the contact information of the other party is registered in the contact information registration unit TB24 when the contact information of the other party is acquired by a call other than chat, transmission / reception of mail, or the like. . If registered, the determination unit 242 notifies the management unit 233 of the fact and the name information of the other party. On the other hand, upon receiving this notification, the management unit 233 temporarily registers the transmission partner management table TB22 to add only the name information of the partner, and transmits the contents of the temporary registration to the management server 10. At this stage, there is a case where the other party is not registered in the user / group registration table TB11 in the management server 10, and whether or not the other party is truly in contact with the user himself / herself of the terminal device 20.
  • the management server 10 notifies the other party of an invitation notice such as “Is Yujiro Takahashi a friend?” And gives the other party a user ID after receiving the consent of the other party.
  • a group ID of a group whose members are the partner and the user is given and registered in the user / group registration table TB11.
  • the management server 10 transmits the user ID and group ID of the other party assigned at this time to the terminal device 20, while the terminal device 20 transmits the user ID to the management unit 233 via a route not shown. Supplied.
  • the management unit 233 registers the user ID of the terminal device 20 and the user ID of the partner as members of the group corresponding to the temporarily registered name information in the transmission partner management table TB22, and receives the received group ID. For example, “1” is registered as the applicable sender information. As a result, the terminal device 20 of “Yujiro Takahashi” can chat with the other party.
  • the application sender information of the additionally registered partner is fixedly registered as “1”, but this means that the contact information is acquired by calling or sending / receiving mail other than chat. The reason is that there is no problem even if the sender information 1 is registered. However, depending on the other party, there is a possibility that the sender information 2 may be registered, so whether the sender information applied to the other party is registered with the user as “1” or “2”. It is also possible to select “2” for the other party that is initially registered as “2” and is determined to have no problem even if the real name is notified. As described above, according to the third embodiment, it is possible to increase the number of chat partners when triggered by the acquisition of contact information.
  • ⁇ From information> In each embodiment, two types of sender information are used, but three or more types may be used. Further, one of the plurality of types does not necessarily have to be accompanied by a real name, and may be a common name or stage name that can be specified within a group.
  • the setting unit 232 and the profile registration table TB21 are described as separate blocks. However, an integrated unit may be considered as the setting unit. Similarly, the management unit 233, the transmission partner management table TB22, and the user information registration table TB23 may be considered as a management unit.
  • the message may be not only characters but also an audio signal, a still image, a moving image, or a combination of these as appropriate.
  • a voice signal or a moving image is included in the message, the message is viewed by reproducing them.
  • the management server 10 includes and manages the database 118, but may be managed by a server other than the management server 10, that is, managed by cloud computing.
  • the terminal device 20 is configured to include and manage the database 218, but may be managed by cloud computing using another server.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephone Function (AREA)
  • Telephonic Communication Services (AREA)

Abstract

La présente invention a pour objet de changer un contenu de réglages d'informations de profil indiquant un expéditeur en fonction de la partie à laquelle un message doit être envoyé. Un dispositif de terminal qui présente des messages envoyés de la part de chaque utilisateur d'une pluralité d'utilisateurs de telle façon qu'ils puissent être visualisés sur une unité d'affichage spécifie, par rapport au même utilisateur, des informations de profil pour des informations d'expéditeur 1 et des informations d'expéditeur 2, et gère les utilisateurs appelés à être des parties auxquelles les messages sont envoyés en association avec les informations d'expéditeur 1 et les informations d'expéditeur 2. Par rapport à une partie ou à la totalité d'une pluralité des utilisateurs correspondant aux informations d'expéditeur, les messages sont envoyés en y joignant les informations d'expéditeur associées, c'est-à-dire soit les informations d'expéditeur 1, soit les informations d'expéditeur 2.
PCT/JP2013/068624 2012-07-26 2013-07-08 Dispositif de terminal, procédé de commande pour dispositif de terminal et programme WO2014017283A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2012165617A JP5903011B2 (ja) 2012-07-26 2012-07-26 端末装置、端末装置の制御方法およびプログラム
JP2012-165617 2012-07-26

Publications (1)

Publication Number Publication Date
WO2014017283A1 true WO2014017283A1 (fr) 2014-01-30

Family

ID=49997099

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2013/068624 WO2014017283A1 (fr) 2012-07-26 2013-07-08 Dispositif de terminal, procédé de commande pour dispositif de terminal et programme

Country Status (2)

Country Link
JP (1) JP5903011B2 (fr)
WO (1) WO2014017283A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6485289B2 (ja) * 2015-08-28 2019-03-20 京セラドキュメントソリューションズ株式会社 画像処理装置、画像処理方法
KR20240054365A (ko) * 2017-12-28 2024-04-25 제트 인터미디에이트 글로벌 코포레이션 다중 프로필을 제공하는 방법 및 시스템
JP2023117058A (ja) 2022-02-10 2023-08-23 富士フイルムビジネスイノベーション株式会社 メッセージ提供システム及びプログラム

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003281043A (ja) * 2002-03-20 2003-10-03 Sharp Corp 電子メール作成装置、電子メール作成プログラム、および、記録媒体
JP2007036533A (ja) * 2005-07-26 2007-02-08 Murata Mach Ltd インターネットファクシミリ装置およびインターネットファクシミリシステム
WO2012088665A1 (fr) * 2010-12-28 2012-07-05 华为终端有限公司 Procédé et terminal mobile pour gérer des contacts

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003058482A (ja) * 2001-08-14 2003-02-28 Fujitsu Ltd エリアチャットルーム提供方法，端末側エリアチャット処理方法，エリアチャットルーム提供処理プログラム記録媒体，エリアチャットルーム提供装置
JP5291348B2 (ja) * 2007-12-21 2013-09-18 株式会社タイトー サービス提供システム、サービス提供方法、及びコンピュータプログラム
JP4579329B1 (ja) * 2009-09-24 2010-11-10 株式会社ハートビット 電子メールの送受信方法、携帯電話用電子メールプログラム、携帯電話および携帯電話用電子メールシステム

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003281043A (ja) * 2002-03-20 2003-10-03 Sharp Corp 電子メール作成装置、電子メール作成プログラム、および、記録媒体
JP2007036533A (ja) * 2005-07-26 2007-02-08 Murata Mach Ltd インターネットファクシミリ装置およびインターネットファクシミリシステム
WO2012088665A1 (fr) * 2010-12-28 2012-07-05 华为终端有限公司 Procédé et terminal mobile pour gérer des contacts

Also Published As

Publication number Publication date
JP2014026423A (ja) 2014-02-06
JP5903011B2 (ja) 2016-04-13

Similar Documents

Publication Publication Date Title
JP5631947B2 (ja) 管理装置、メッセージ管理方法およびプログラム
JP5380638B2 (ja) メンバー追加を拡張するためのメッセージングサービスシステム及びその方法
JP5706868B2 (ja) メッセンジャープラットフォームでアバタ／ゲーム／エンターテイメント機能を提供するシステムおよび方法
US20190327198A1 (en) Messaging apparatus, system and method
JP5540126B2 (ja) チャットサービス提供方法及びプログラム
JP5875493B2 (ja) ユーザ端末の画面上でスクロールバーをアップデートする方法及び画面上でスクロールバーをアップデートするユーザ端末
JP6145614B2 (ja) 端末装置、メッセージ表示システム、端末装置の制御方法およびプログラム
JP2014004134A (ja) メッセージ管理装置、メッセージ管理方法およびプログラム
JP2014502745A (ja) 通信装置用のカレンダーアプリケーション
US9516154B2 (en) Apparatus and method for managing conversational contents with contacts in a terminal
US9866505B2 (en) Configuring presence and notifications in persistent conversations
JP5894819B2 (ja) メッセージ交換システム、制御方法およびプログラム
JP5995621B2 (ja) 端末装置、システム、端末装置の制御方法およびプログラム
JP5903011B2 (ja) 端末装置、端末装置の制御方法およびプログラム
JP5654624B2 (ja) 制御装置、制御方法、プログラムおよびシステム
JP6014416B2 (ja) 端末装置、管理サーバ、端末装置の制御方法およびプログラム
JP2005050113A (ja) インスタントメッセージ利用システム，送信クライアント，中継サーバ，受信クライアント，インスタントメッセージ利用方法およびそのプログラム。
JP2013161167A (ja) メッセージ送信システム、制御方法およびプログラム
JP2014106697A (ja) メッセージ閲覧装置、メッセージ閲覧方法およびプログラム
JP7244245B2 (ja) 情報処理方法、プログラム、端末、情報処理装置、電子装置
JP7297971B2 (ja) サーバ、情報処理方法、プログラム
KR101364935B1 (ko) 캐릭터 진동 출력 방법 및 그 단말기
JP2024009091A (ja) プログラム、情報処理方法、端末
WO2023115154A1 (fr) Procédé et dispositif électronique de messagerie
JP2022025652A (ja) 通信端末、通信システム、通信方法及びプログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13822678

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13822678

Country of ref document: EP

Kind code of ref document: A1