WO2015186659A1

WO2015186659A1 - Sns provision program, sns provision server, and sns provision system

Info

Publication number: WO2015186659A1
Application number: PCT/JP2015/065760
Authority: WO
Inventors: 政雄冨永
Original assignee: フィールズ株式会社; 株式会社フューチャースコープ
Priority date: 2014-06-03
Filing date: 2015-06-01
Publication date: 2015-12-10

Abstract

A social network service (SNS) program that enables a computer to function as means for associating, with a user management ID uniquely identifying a service user in a prescribed social network service, multiple personality IDs uniquely identifying the service user and recognized as the persona of one user by other service users in the service, and to function as a means for managing the associated IDs.

Description

SNS providing program, SNS providing server device, and SNS providing system

The present application relates to an SNS providing program that provides a social network service, an SNS providing server device, and an SNS providing system.

In recent years, a variety of social network services (SNS) have begun to be provided (Patent Document 1), and services that allow people with the same hobbies and sensibilities to easily connect to each other on the web are increasing. Here, the SNS is a community-type communication system for the purpose of performing wide communication while participating users share their hobbies, preferences, friends, social life, and the like. SNS has a variety of functions, including the ability to introduce one's own profile by publicizing his / her profile, the ability to register acquaintances on SNS, the ability to easily update his / her entry, and the same hobby Has the ability to create a community between people with high sensibilities and sensibilities, and has received a lot of support regardless of age, gender, nationality, occupation, etc.

JP-T 2009-521752

However, one account (one personality) is determined for each SNS account, and all the above-mentioned wide functions can be used only by one account (one personality). As a result, for example, acquaintances who interact with each other for hobbies and acquaintances who interact with each other in business gather together in one account (one personality), which leads to management of essentially different human relationships on the web. , There is a concern that the information of the connection will spread too much. That is, in the conventional SNS, although the contents to be shared differ greatly depending on the other party, there is no choice but to deal with one account (one personality). In order to eliminate such inconveniences, users create multiple accounts, create separate addresses and communities, or create various groups while using one account (one personality). There was only limited communication within the group. In this case, despite the fact that the SNS and SNS are equipped with many functions, it has been necessary to be aware of other groups.

In one aspect, an object of the present invention is to improve the convenience of a user who uses an SNS.

According to one form, the computer is uniquely identified within the service to a user management ID that uniquely identifies one service user within a given social network service and from other service users within the service. There is provided an SNS providing program that functions as a means for managing a plurality of personality IDs recognized as single-person users.

According to another aspect, a user management ID that uniquely identifies one service user within a predetermined social network service, and a unique management ID that is uniquely identified within the service and that is different from other service users within the service. A storage unit that associates and stores a personality ID recognized as a personality user, and receives a request for login to the social network service by the terminal device and information for identifying the service user from the terminal device via the network Then, all personality IDs associated with the user management ID are acquired by referring to the storage unit based on the information for specifying, and each of the screen information corresponding to each of the acquired personality IDs is SNS providing server device comprising processing unit for transmitting to terminal device It is provided.

According to another aspect, the user management ID that uniquely identifies one service user within a service that provides a predetermined social network is uniquely identified within the service and other within the social network There is provided an SNS providing system including a control unit that manages a plurality of personality IDs recognized as one-person users from service users.

It is a block diagram which shows the system configuration | structure in one Embodiment of this invention. It is a block diagram which shows the hardware constitutions of the terminal device in one Embodiment of this invention. It is a block diagram which shows the hardware constitutions of the SNS provision server apparatus in one Embodiment of this invention. It is a figure explaining the concept of SNS in one Embodiment of this invention. It is a figure explaining the concept of SNS which the SNS provision server apparatus in one Embodiment of this invention provides. It is a block diagram which shows the function structure of the terminal device and SNS provision server apparatus in one Embodiment of this invention. It is a figure which shows the internal structure of the user information storage part which concerns on one Embodiment of this invention. It is a figure which shows the internal structure of the palette information storage part which concerns on one Embodiment of this invention. It is a figure which shows the screen group containing the top screen and several pallet screen in one Embodiment of this invention. It is a figure which shows the screen group containing the top screen and several pallet screen in one Embodiment of this invention. It is a figure which shows the internal structure of the application information storage part which concerns on one Embodiment of this invention. It is a figure which shows the application top screen which concerns on one Embodiment of this invention. It is a figure which shows the work pallet screen which concerns on one Embodiment of this invention. It is a figure which shows the work pallet clip screen which concerns on one Embodiment of this invention. It is a figure which shows the pop-up screen displayed on the work palette clip screen which concerns on one Embodiment of this invention. It is a figure which shows the work palette community screen which concerns on one Embodiment of this invention. It is a figure which shows the work pallet setting screen which concerns on one Embodiment of this invention. It is a figure which shows the palette color change screen which concerns on one Embodiment of this invention. It is a figure which shows the function restriction | limiting setting screen which concerns on one Embodiment of this invention. It is a figure which shows the user setting screen which concerns on one Embodiment of this invention. It is a figure which shows the community top screen which concerns on one Embodiment of this invention. It is a figure explaining the procedure which performs user registration in the SNS provision server apparatus of one Embodiment of this invention. It is a figure explaining the procedure which performs user registration in the SNS provision server apparatus of one Embodiment of this invention. It is a flowchart which shows the process sequence of the SNS provision server apparatus when the service user of the terminal device which concerns on one Embodiment of this invention logs in to a SNS provision server apparatus.

DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. However, the present invention is not limited to the following embodiments, and the following embodiments are not departed from the scope of the present invention. Various modifications and substitutions can be made. In all the drawings, the same reference numerals are given to the same components, and the description will be omitted as appropriate.

FIG. 1 is a block diagram showing an example of a system configuration in the present embodiment.

The system includes a terminal device 10 operated by a user, a network 80 such as the Internet, and an SNS providing server device 40 that provides a plurality of users with the social network service in the present embodiment. The SNS providing server device 40 is connected to the terminal devices 10 of a plurality of users via the network 80. The terminal device 10 is an information processing device such as a mobile phone, a smartphone, a game console, a personal computer, a touch pad, and an electronic book reader. In the present embodiment, the terminal device 10 and the SNS providing server device 40 can constitute an SNS providing system.

Although not particularly limited, in the present embodiment, a mobile phone terminal called a smartphone can be used as the terminal device 10. Here, a smartphone refers to a high-function mobile phone terminal that can perform voice connection, Internet connection, shooting with a digital camera, playback of moving images and music, games, schedule management, and the like. The smartphone is equipped with a general-purpose operating system, and the user downloads and uses the application program necessary for communication according to the present embodiment. However, in the present embodiment, the terminal device 10 need not be limited to a smartphone, and can be realized even if it is a tablet terminal or a fixed terminal. When a smartphone is used, when a touch screen is touched at a predetermined timing, a keyboard screen is displayed and keyboard operation is possible.

FIG. 2 is a block diagram illustrating an example of a hardware configuration of the terminal device 10 in the present embodiment.

The terminal device 10 includes a power system 101, a main system 102, a storage unit 106, an external port 107, a high frequency circuit 108, an antenna 109, an audio circuit 110, a speaker 111, a microphone 112, a proximity sensor 113, an I / O subsystem 114, a touch A reactive display system 118, an optical sensor 119, and an input unit 120 are included. The main system 102 includes a processor 103, a memory controller 104, and a peripheral interface 105. The I / O subsystem 114 includes a display controller 115, an optical sensor controller 116, and an input controller 117.

FIG. 3 is a block diagram illustrating an example of a hardware configuration of the SNS providing server device 40 in the present embodiment.

The SNS providing server device 40 includes a CPU (Central Processing Unit) 402, a ROM (Read Only Memory) 403, a RAM (Random Access Memory) 404, an NVRAM (Non-Volatile Random Access Memory) 405, I / F (Interface) 406, I / O (Input / Output Device) 407 such as a keyboard, mouse, monitor, CD / DVD (Compact Disk / Digital Versatile Disk) drive connected to the I / F 206, HDD (Hard Disk Drive) 408, NIC (Network Card) 409, and the like.

First, the SNS provided by the SNS providing server device 40 in this embodiment will be described. FIG. 4 is a diagram for explaining the concept of SNS in the present embodiment. Usually, a person (self) will have a plurality of personalities (faces) such as, for example, self shown to a friend, self shown to a hobby companion, self shown to a family, self shown to a business person. In the present embodiment, the SNS providing server device 40 identifies each user with respect to each service user (also simply referred to as “user”) so as to correspond to a plurality of personalities of a single person ( A user management ID) and a plurality of personality IDs associated with the user management ID. That is, for a certain user, there are a user management ID for identifying the user and a plurality of personality IDs associated with the user management ID. Thus, each user can act as a plurality of users who look like different personalities from other users in the social network using each of the plurality of personality IDs.

In the following description, the SNS provided by the SNS providing server device 40 is also referred to as “SNS_Color”, “color”, or “Color”, and is referred to as “pallet ID” as a specific example of the personality ID assigned to each service user. Use terminology. Each service user can create a plurality of “pallets” that indicate personalities within the service and are associated with each palette ID. In the example illustrated in FIG. 4, one service user (self) can create a plurality of palettes (personality) such as a friend palette, a hobby companion palette, a family palette, and a work palette.

FIG. 5 is a diagram illustrating the concept of SNS_Color provided by the SNS providing server device 40 according to this embodiment. A conceptual diagram of an existing SNS is displayed on the left side of FIG. 5, and a conceptual diagram of SNS_Color in the present embodiment is displayed on the right side. In the existing SNS conceptual diagram on the left side, all friends and communities are registered in association with one account (one personality).

On the other hand, in the conceptual diagram of SNS_Color in the present embodiment on the right side, four pallets A to D are associated with each member information, and friends and communities are separately associated with each pallet and registered. Yes. In other words, one account (one service user) is associated with multiple personalities (multiple palettes), and the service user creates a separate community with other users registered as friends for each palette. Can do. For users other than service users, it is not known that palette A, palette B, palette C, and palette D are the same person. Each member information (account) is managed by a user management ID, and each palette is managed by a palette ID. In the present embodiment, as an example, a unique palette ID is assigned to each of the palettes A to D. That is, for example, ID1 is associated with palette A, ID2 is associated with palette B, ID3 is associated with palette C, and ID4 is associated with palette D. Further, each of ID1, ID2, ID3, and ID4 is associated with a user management ID.

FIG. 6 is a block diagram illustrating an example of functional configurations of the terminal device 10 and the SNS providing server device 40 in the present embodiment.

The SNS providing server device 40 manages the provision of SNS_Color in the present embodiment. The SNS providing server device 40 includes an SNS control unit 41, a user information management unit 42, an access management unit 44, a screen provision processing unit 46, an information collection unit 52, a user information storage unit 60, a pallet information storage unit 62, and an SNS information storage unit. 64.

The SNS control unit 41 controls the entire SNS providing server device 40 and also controls communication with other devices such as the terminal device 10 of the service user using the SNS_Color provided by the SNS providing server device 40.

The user information management unit 42 manages user information of service users who use SNS_Color. The access management unit 44 manages access to the SNS providing server device 40 by a user who uses SNS_Color, that is, access to SNS_Color. Specifically, the access management unit 44 performs processing such as user authentication when there is an access request from the terminal device 10 to the SNS providing server device 40 (SNS_Color). The screen providing processing unit 46 provides various screen information to be displayed on the terminal device 10 of the user who uses SNS_Color. The information collection unit 52 collects information in the SNS_Color.

The user information storage unit 60 stores user information of service users. The pallet information storage unit 62 stores information related to the pallet created by the service user. The SNS information storage unit 64 stores various types of information necessary for providing SNS_Color. The SNS information storage unit 64 stores, for example, communities created in SNS_Color, information such as topics and comments posted to each community. Note that a community is one in which users having a common hobby, topic, interest, purpose, and the like participate, and can be created by each user in this embodiment. The topic is created in each community, and is used for discussing a specific topic or the like among users who participate in each community. Each user posts a comment within each topic.

The terminal device 10 includes an SNS control unit 12, a screen providing processing unit 14, an operation input receiving unit 16, and an application information storage unit 20. The functional configuration of the terminal device 10 can be realized, for example, by installing an SNS application program (hereinafter also simply referred to as “SNS application_Color”) provided by the SNS providing server device 40 in the terminal device 10.

The SNS control unit 12 controls communication with other devices such as the SNS providing server device 40 and controls the entire terminal device 10 with respect to provision of SNS_Color. For example, the SNS control unit 12 accesses the SNS providing server device 40, transmits a request to the SNS providing server device 40, and receives a processing result and the like as a response.

The screen providing processing unit 14 displays various screens (pages linked to each palette ID (Web page, hereinafter also referred to as “pallet screen”)) on the touch panel of the touch-responsive display system 118 (see FIG. 5) of the terminal device 10, the user A user-specific homepage (Web page, hereinafter referred to as “top screen”) associated with the ID is provided. The operation input receiving unit 16 receives an operation input from a user who operates the terminal device 10. Specifically, the operation input receiving unit 16 receives user operations on various screens through operations on the touch panel. The operation input receiving unit 16 can also receive a user operation from an operation unit other than the touch panel.

The application information storage unit 20 stores various information related to the SNS application_Color. The application information storage unit 20 stores, for example, information on the target user, information on friend users registered as friends of the target user, and the like. The application information storage unit 20 stores various screen information necessary for the screen providing processing unit 14 to provide various screens.

In this embodiment, the user information management unit 42 of the SNS providing server device 40 can uniquely identify one service user in the SNS providing server device 40 as a service user who newly registers a user in the SNS providing server device 40. A valid user management ID. The user information storage unit 60 stores various information related to the service user in association with the user management ID.

FIG. 7 is a diagram illustrating an example of an internal configuration of the user information storage unit 60. The user information storage unit 60 includes items (fields) such as “user management ID”, “token information”, “authentication information”, and “user registration information”.

“User management ID” is information for identifying the service user. “Token information” is information indicating a token to be described later. “Authentication information” is information used to authenticate the service user, such as a password or a consumer key described later. “User registration information” is information relating to the service user, such as the name, address, and e-mail address of the service user. In the present embodiment, the token information and the authentication information are information for specifying a service user, and are used for communication between the terminal device 10 and the server device 40. Note that the user management ID itself may be used as information for specifying the service user.

Returning to FIG. 6, the user information management unit 42 further associates a plurality of palette IDs that are uniquely identified in the service and recognized as one-person users from other service users in the SNS_Color. Manage. For example, when a service user who has been issued a user management ID creates a new palette, the user information management unit 42 assigns a palette ID to the palette created by the user. Here, the pallet ID can be recognized as an ID of a personalized user from other service users in SNS_Color. That is, the palette ID corresponds to what is used as the user ID or nickname in the existing SNS as shown in FIG. 5, for example. On the other hand, although one user management ID is given to each service user using SNS_Color, it is an ID that is not recognized by other users in SNS_Color, that is, an ID that should also be referred to as unpersonal.

The user information management unit 42 may assign two information, ie, information not shown to the user and information shown to the user, as the palette ID. As information not shown to the user, a unique numerical value (which may include letters such as alphabets) automatically issued on the SNS providing server device 40 side is used, and information shown to the user can be set by, for example, a service user It may be a unique character string (however, a numerical value may be included). In this embodiment, for example, information that is not shown to the user is used for managing and extracting information on a specific palette on the database, and the information that is shown to the user is identified by the user on the service. Can be used for

For example, when assigning a unique numerical value as information that is not shown to the user, the user information management unit 42 can sequentially assign a numerical value or the like each time a new palette is created. By assigning numerical values in this way, the load on the system can be reduced. Further, for example, the user information management unit 42 may assign numerical values in order from “1” so as not to overlap each pallet for each user management ID. Also in this case, the pallet ID can be made unique within the SNS providing server device 40 by using the user management ID and this numerical value in combination as a pallet ID.

For example, as information to be shown to the user, the user information management unit 42 can assign a predetermined number of character strings as IDs to the target palette. This character string may be a random number string, or may be a character / number string in which letters and numbers are mixed. For example, as information to be shown to the user, a nickname designated by the user can be used after confirming that there is no duplication with a nickname used by another user in SNS_Color.

Thus, by using two of the information such as a numerical value that is not shown to the user and the information that is shown to the user such as a character string as the palette ID, it is possible to reduce the load on the system and It is possible to both make it difficult to recognize the scale and status of the service (number of palettes, etc.).

In the present embodiment, a nickname is used as a palette name for identifying a palette on a page (pallet screen) displayed on the touch panel of the terminal device 10 associated with the palette ID. In the present embodiment, the nickname can be freely set by the user and may be duplicated. Even if the nicknames are duplicated, since the pallet corresponding to the nickname is assigned with a unique pallet ID, the terminal device 10 and the server device 40 can identify the pallet.

The user information management unit 42 stores the assigned palette ID in the palette information storage unit 62 in association with the user management ID.

FIG. 8 is a diagram illustrating an example of an internal configuration of the pallet information storage unit 62. The palette information storage unit 62 stores items (fields) such as “pallet ID”, “user management ID”, “friend”, “participating community”, “other SNS cooperation information”, “collected information”, “login state”, and the like. Including.

“Pallet ID” is information for identifying the pallet as described above. Although only “a”, “b”, and the like are illustrated in FIG. 8, as described above, the palette ID can include information not shown to the user and information shown to the user. Note that any one of information shown to the user and information not shown to the user may be used as the palette ID.

“User management ID” is information for identifying the service user as described above. “Friend” is information indicating a user registered as a friend of the service user in the palette. “Participating community” is information indicating a community in which the service user participates in the palette. “Other SNS cooperation information” is information indicating another SNS with which the service user cooperates in the palette. As will be described later, “collected information” is information related to information collected based on the activity performed by the service user in the SNS_Color with the palette ID of the palette. “Login state” indicates a login state in the pallet. As will be described later, in this embodiment, each service user logs in to the SNS providing server device 40 based on the user management ID of the service user. At this time, all the users associated with the management ID are associated with the user. The pallet ID is logged in.

In the example shown in FIG. 8, for example, the palette IDs “a” and “c” are associated with the user management ID “u001”. That is, the palettes with the palette IDs “a” and “c” are palettes of one service user identified by the user management ID “u001”. However, in this embodiment, the fact that the pallets with the pallet IDs “a” and “c” belong to one service user is only managed by the SNS providing server device 40, and the pallets from other users are respectively It will look like a separate user's palette identified by the IDs “a” and “c”.

That is, the service user can publish a different profile with a nickname that is a different palette ID for each palette, and can register other users who are different for each palette as friends or create a community for each palette. That is, the service user can have a plurality of personalities (a plurality of palettes) with one account (one personality), and can switch between a plurality of personalities. Further, the user can manage the members registered for each pallet in a completely distinguished manner. Therefore, each user can talk with peace of mind to the user of the target pallet without being conscious of other users of the other pallets.

Returning to FIG. 6, in another example, the user information storage unit 60 may store the user's palette ID in association with the user management ID of each user.

In the terminal device 10, the screen provision processing unit 14 has a plurality of top screens and a plurality of pallet IDs respectively identified based on the information on the top screen and the information on each of the pallet screens received from the server device 40. A screen group including a palette screen (personality screen) is displayed on the touch panel. The screen providing processing unit 14 provides a screen group so that a plurality of palette screens can be identified by different colors. In the present embodiment, this screen group is generated based on screen information stored in the application information storage unit 20 and data acquired from the SNS providing server device 40 in response to an input operation as necessary. That is, the provision of the screen group is performed by the cooperation of the screen provision processing unit 14 of the terminal device 10 and the screen provision processing unit 46 of the SNS providing server device 40. However, for convenience, the screen provision processing unit 14 provides the screen group. explain.

The operation input reception unit 16 receives an operation from the service user for the screen group through an operation on the touch panel. The screen providing processing unit 14 switches the display between the top screen and the plurality of palette screens according to a swipe operation in which a finger from a service user for the screen group touches the touch panel and slides left and right. That is, it can be said that the user's personality in the SNS_Color is switched by the user's operation (intuitive operation) on the touch panel without logging out from the pallet screen being written and logging into the pallet screen for other personalities.

In the present embodiment, the SNS control unit 12 receives a palette ID corresponding to the selected palette screen when a service user requests access to the SNS_Color in a state where any palette screen is displayed and selected. To access SNS_Color. Therefore, the service user can easily switch a plurality of personalities by simply switching the palette screen displayed by the swipe operation. In other words, when a service user creates multiple accounts individually and creates separate addresses and communities, it was necessary to log out and log in to another account to switch between multiple personalities. In the embodiment, such a complicated procedure is not necessary.

On the other hand, when the service user requests access to the SNS_Color with the top screen displayed and selected, the screen providing processing unit 14 displays a notification inquiring which palette ID to access to the service user. . The SNS control unit 12 accesses the SNS_Color with the palette ID corresponding to the selected palette screen based on the selection of the service user with respect to the notification displayed by the screen providing processing unit 14.

In the SNS providing server device 40, when there is a request for access to the SNS_Color together with the designation of the palette ID from the service user at the terminal device 10, the access management unit 44 designates the service user from another service user. SNS_Color is accessed as a user recognized by the palette ID.

FIG. 9 is a diagram showing an example of a screen group including a top screen and a plurality of palette screens in the present embodiment. In the example shown in FIG. 9, a work pallet and a school pallet are set as pallets. The screen group includes a top screen (hereinafter referred to as “application top screen”) 500, a palette screen for work palette (hereinafter referred to as “work palette screen”) 502, a palette screen for school palette (hereinafter referred to as “school”). Pallet screen ”) and pallet edit screen 510.

When the service user starts the SNS application_Color, the application top screen 500 is displayed first. When the user performs a swipe operation, the screen displayed in the order of the work pallet screen 502, the school pallet screen 504, and the pallet edit screen 510 can be switched. For example, a case where the work pallet screen 502 is displayed on the touch panel of the terminal device 10 and a transition to the school pallet screen 504 by a swipe operation by the service user will be described. In this case, the application information storage unit 20 stores predetermined information about the school pallet screen 504 (for example, screen information when displayed last time). At this time, if the operation input receiving unit 16 detects a swipe operation (transition operation) from the work pallet screen 502 to the school pallet screen 504, the SNS control unit 12 displays the school pallet screen 504 that is the transition destination pallet. A request command for the latest version of the palette screen corresponding to the palette ID and the palette ID is transmitted to the server device 40. Upon receiving these pieces of information, the server device 40 acquires the latest version of the school pallet screen 504 and transmits it to the terminal device 10. When acquiring the latest school pallet screen information, the screen provision processing unit 14 stores the information in the application information storage unit 20 and displays the information on the touch panel. In this way, the transition destination palette screen is displayed for each transition of the palette screen.

Note that the palette editing screen 510 may be displayed by an operation (for example, access from the application top screen) separate from the palette screen switching operation (swipe operation). Further, a loop structure may be adopted so that after all the palette screens are switched by the palette screen switching operation such as the swipe, the screen returns to the application top screen 500.

On the palette editing screen 510, various settings can be made, such as adding, deleting, and changing the order of palettes, changing the page color for each palette, changing the text, setting the clock / region / language, and setting the external application program to be linked. ing. In the illustrated example, a screen for setting the palette color of the palette screen is displayed. Here, thumbnail images of the application top screen 500, the work palette screen 502, and the school palette screen 504 are displayed in the palette editing screen 510, and the service user performs a swipe operation on these thumbnail images in the palette editing screen 510. Thus, the image displayed at the center can be switched. In addition, color samples such as Green, Blue, and Red are displayed at the bottom of the palette editing screen 510, and the service user selects one of the color samples and swipes upward to select one of the palette screens. By overlaying the thumbnail image, the palette color of the palette screen can be set. Thereby, for example, the palette color of each palette screen can be set such that the work palette screen 502 is Green and the school palette screen 504 is Blue. The screen providing processing unit 14 displays an outer frame, a header portion, and the like of each pallet screen in a set pallet color. As a result, the service user can easily grasp which pallet screen he / she is viewing, etc., even when different pallet screens are switched and displayed by a swipe operation. That is, since a color selected so as not to overlap with each other is assigned to each palette, the user can intuitively identify the palette displayed on the touch panel of the terminal device 10.

In the terminal device 10, the SNS control unit 12 holds information on the palette screen displayed for each palette, for example, in the application information storage unit 20, and when the service user switches the display, The screen can be configured to be displayed.

In the present embodiment, the terminal device 10 has a notification function for notifying update contents for each palette before the service user starts the SNS application_Color. Thereby, it becomes possible to respond finely to writing for each palette. The notification content, notification frequency setting, and the like can be set in detail. In the present embodiment, the palette editing screen 510 is arranged as the final screen, but can be arbitrarily changed.

Referring back to FIG. 6, the screen providing processing unit 14 can provide each pallet screen including a pallet ID display area for displaying a pallet ID corresponding to each pallet screen. In this embodiment, the palette ID and nickname are displayed in the palette ID display area. Note that either the palette ID or the nickname may be displayed in the palette ID display area.

Also, the operation input receiving unit 16 can receive a setting not to display the palette ID corresponding to the palette ID display area of any of the palette screens from the service user. The screen providing processing unit 46 may be configured not to display the palette ID corresponding to the palette ID display area on the palette screen that has received the setting for not displaying the palette ID.

FIG. 10 is also a diagram illustrating an example of a screen group including a top screen and a plurality of palette screens in the present embodiment. In the example illustrated in FIG. 10, the screen group includes an application top screen 500 and three different palette screens, a work palette screen 502, a hobby palette screen 506, and a private palette screen 508. These screens can be switched by the user performing a swipe operation on the touch panel. Further, for example, when the service user operates the touch panel on the work pallet screen 502 and makes a predetermined input, the input is received by the operation input receiving unit 16, and the SNS control unit 12 displays the work pallet screen 502. The pallet ID and information regarding the input are transmitted to the server device 40. Upon receiving these pieces of information, the server device 40 identifies the service user and the corresponding palette by referring to the database shown in FIG. 8 using the palette ID, and executes a predetermined process based on the information related to the input. Next, the information after the predetermined processing is transmitted to the terminal device 10, and the terminal device 10 that has received the information displays a screen corresponding to the user input on the work pallet screen 502. Thus, when a user operation is performed on a predetermined pallet screen, the terminal device 10 transmits information (command) and pallet ID related to the operation to the server device 40. Next, based on the received information, the server device 40 recognizes what input the user has made in which pallet, executes processing according to the input, and outputs the processing result to the terminal Transmit to device 10. The terminal device 10 performs a predetermined display according to the information received from the server device 40.

On the palette screens 502, 506, and 508, a My Page is provided for each palette screen, and the contents, color scheme (palette color), font, photo, etc. can be freely set in the header for what kind of personality the page is. It is possible to distinguish. Furthermore, in each pallet screen, the updated information is simply displayed as a topic in the community participating in each pallet screen. In addition, it displays how many members have already viewed the updated community information. Thereby, it can be judged instantly whether the updated community information is useful information for me.

In the header part of each pallet screen, a pallet ID display area 520 for displaying a nickname and a pallet ID corresponding to the pallet screen is provided. By providing the palette ID display area 520 in the header portion in this way, even when the service user switches and displays different palette screens by a swipe operation, which pallet screen he / she is viewing, and the SNS providing server device 40 It is possible to easily grasp which pallet ID is used for accessing.

On the other hand, as described above, in this embodiment, each palette screen is configured to be identifiable with a different color (pallet color). Therefore, even if the service user himself / herself does not display the pallet ID, the service user can grasp which pallet screen he / she is viewing from the color of the pallet screen. In the present embodiment, the palette ID is information uniquely identified in the SNS_Color. For example, it is assumed that a certain service user has created a work pallet with a pallet ID “a” and a hobby pallet with a pallet ID “b”. In this case, the service user creates a community or topic related to his / her hobby with a palette ID “b” in SNS_Color, or posts a comment. At this time, there may be a case where it is not desired that the person involved in work know that the palette ID “b” is his / her own. However, for example, there is a possibility that the terminal device 10 is shown and the SNS application_Color is opened and shown when actually talking to a business person. In such a case, it may be preferable that the palette ID is not displayed on the palette screen. For this reason, in the present embodiment, it is configured to accept a setting for not displaying the palette ID.

In addition to community search, the application top screen 500 displays introductions of popular communities when a SNS application_Color is opened, introductions of newly created communities, and the like. The content displayed on the application top screen 500 can be set by the user himself / herself. For example, the profile of a person who has newly joined the community, the latest information of a favorite product, group, company, news, weather forecast, TV General information such as a program guide and train delay information may be used.

Further, the screen providing processing unit 14 displays information for providing to the service user selected based on the activity in the SNS_Color when the service user accesses with each palette ID on the application top screen 500. Here, the information can be community information, advertisements, or the like.

Returning to FIG. 6, the information collection unit 52 of the SNS providing server device 40 provides the service user with the corresponding pallet ID based on the activity in the SNS_Color when the service user accesses the pallet ID. Is collected from SNS_Color. For example, when a service user logs in to SNS_Color with a certain pallet ID and posts a comment or the like to a community related to fishing, the information collecting unit 52 collects information about fish fishing in association with the pallet ID.

Further, the SNS control unit 41 provides the information collected by the information collecting unit 52 to the terminal device 10 in association with the palette ID. In the terminal device 10, the screen provision processing unit 46 acquires information for providing to the service user selected based on the activity in the SNS_Color using each palette ID of the service user in association with each palette ID. . The screen provision processing unit 46 can display each information on the top screen (the application top screen 500) so that the service user can recognize the corresponding palette ID. Here, “recognizable” means, for example, that each information is provided by being surrounded by a pallet color frame set to the corresponding pallet ID, or provided with a pallet ID.

The SNS control unit 12 can accept designation of a palette ID that is treated as confidential from the service user. Further, the screen provision processing unit 14 may be configured not to display information acquired in association with the palette ID that has received the designation of confidentiality on the top screen. As described above, in the SNS_Color in this embodiment, each service user can perform an activity in the SNS_Color using a plurality of palette IDs corresponding to a plurality of personalities. Here, as described above, for example, it is assumed that a certain service user creates a work palette with a palette ID “a” and creates a hobby palette with a palette ID “b”. In this case, the service user creates a community or topic related to his / her hobby with a palette ID “b” in SNS_Color, or posts a comment. At this time, there are times when you do not want to know the hobbies of business people. However, for example, there is a possibility that the SNS application_Color of the terminal device 10 is opened and shown when actually meeting a business person. In such a case, it may be preferable that information related to hobbies is not displayed on the top screen. For this reason, in the present embodiment, a configuration in which a setting for not displaying information on the top screen is accepted.

The application information storage unit 20 stores each piece of information (friend, community, etc.) set in each palette in association with the corresponding palette ID. FIG. 11 is a diagram illustrating an example of the internal configuration of the application information storage unit 20. The application information storage unit 20 includes items such as “pallet ID”, “pallet color”, “ID non-display setting”, and “secret handling”.

“Pallet ID” is information for identifying the pallet. “Palette color” is information indicating a color that is a theme color set in the palette. The palette color is arbitrarily set by the service user. “ID non-display setting” is information indicating whether or not to set the palette ID not to be displayed on each palette screen described above. For example, a flag “Re” is set for a setting that does not display the palette ID. “Confidential treatment” is information indicating the above-described setting as to whether or not to be confidential. A flag of “Le” is set for a confidential item.

FIG. 12 is a diagram illustrating an example of the application top screen 500 displayed when the SNS application_Color is started (when logged in to the SNS_Color with a corresponding user management ID). The application top screen 500 includes a header, a search text input box 511 for searching for a community, and a community display area 512 from the top of the display screen. A category list button 513 for specifying a community category is displayed on the left side of the header where “Color” is displayed, and a display switching button 514 is displayed on the right side of which “Color” is displayed. Yes. The application top screen 500 is a screen that is uniquely prepared for each user management ID, and cannot be viewed when logged in to SNS_Color with an ID other than the corresponding user management ID. It is.

When the user presses the display switching button 514, the community displayed in the box format in the community display area 512 is changed to the list format and displayed. The user can search by entering a free keyword of the community to be searched in the search text input box 511.

The community display area 512 includes a new community automatically selected by the date and time of the event or set by the user, a popular community automatically selected by the number of participation and the increase or the user set by the user, an automatic selection or a recommended category set by the user. Is displayed. In the community display area 512, for example, the information collected by the information collecting unit 52 of the SNS providing server device 40 described above is displayed. In addition, from the viewpoint of youth protection, it is also possible to manage the communities to be presented automatically by providing a parental function that prevents the access by setting the user's birth date in advance, setting the community to be excluded .

In the search text input box 511, it is possible to search by entering a free keyword of a community to be searched. In the search, the search target is different when the category is already set with the category list button 513 and when it is not.

Furthermore, a user setting button 516 is displayed below the application top screen 500. Processing when the user selects the user setting button 516 will be described later.

Next, the pallet screen will be described. Here, a work palette screen 502 is shown as an example. FIG. 13 is a diagram illustrating an example of a work pallet screen 502 (work pallet new arrival screen).

The work palette screen 502 includes a header indicating that it is a “work” palette at the top, and a new tab button 535, a clip tab button 536, a community tab button 537, a notification tab button 538, and a setting tab at the bottom footer. Button 539 is included. The user can switch to the screen of each tab by selecting each tab. FIG. 13 shows a work palette screen in a state where the new arrival tab button 535 is selected. In this embodiment, the state in which the new arrival tab button 535 is selected is displayed first. However, the user can change the tab corresponding to the state displayed first, or the arrangement of each tab. It may be possible to change.

Although not shown here, as described above, the work pallet screen 502 can include a pallet ID display area indicating the pallet ID of the pallet in the header portion or the like. The work palette screen 502 is displayed so that the palette color set for the palette can be easily grasped. As an example, for example, it is a palette color in which the background color of the header is set.

13 includes a search text input box 531, a sort switching button 532, and a topic display area 533 from the top below the header. In addition, a display switching button 534 is displayed on the right side of the header where “work” is displayed. When the user presses the display switching button 534, topics displayed in the box format in the topic display area 533 are changed to the list format and displayed.

In the search text input box 531, a free keyword of a topic to be searched can be entered and searched. When the user enters a free keyword of the topic to be searched in the search text input box 531, the topic title, topic photo, topic description, number of comments, number of viewers, last comment date, community name information, etc. are displayed in a box format. Is displayed. When the user selects a topic displayed in a box format, detailed information on the topic can be viewed.

The rearrangement switching button 532 allows the user to set the order that the user wants to display in the topic display area 533, such as the update order, the comment count order, and the viewer count order.

In the topic display area 533, a topic title, a topic photo, a topic description, the number of comments, the number of viewers, the last comment date and time, a community name, and the like are displayed. In the topic display area 533, automatically selected by the date and time of establishment, newly arrived topics set by the user, automatically selected by the number of viewers and the number of increase, popular topics set by the user, or automatically selected or recommended topics set by the user Etc. are displayed. From the viewpoint of youth protection, it is also possible to manage the topics to be presented automatically by providing a parent function that prevents users from accessing them by setting the user's date of birth in advance, setting the topics to be excluded. .

When the user is not participating in any community, a display switching button for guiding to the application top screen 500 is arranged, and a screen for searching for a community can be displayed. The search for community screen is displayed when there are no participating communities, but when there is no topic that matches the search keyword, a display that prompts you to reconsider the keyword or a recommended community that approximates the keyword is displayed. You may make it do.

When the user selects the clip tab button 536 of the footer, a work palette clip screen is displayed. FIG. 14 is a diagram illustrating an example of a work pallet clip screen 502a. The work palette clip screen 502a includes a header representing a clip tab from the top, a clip classification selection button, and a clipped content display area 546. The clip classification selection button includes a palette clip button 540, a community clip button 541, a topic clip button 542, and a comment clip button 543, depending on the clipped classification target. By selecting a clip button of a category to be confirmed by the user, a clip of each category can be displayed. FIG. 14 shows a state where the palette clip button 540 is selected.

On the work palette clip screen 502a, a nickname (pallet ID) of a clipped palette user (pallet of another user), a profile image, and a message display button 545 are displayed. When the user selects the message display button 545, a message with the clipped palette user is displayed as shown in the message display screen 502b. In the message display screen 502b, the nickname of the palette user is displayed in the header, and comment text, a photograph, a link, a posting date and time, read or unread, and the like are displayed for each message with the palette user. In addition, a new message creation window 550 is displayed in the footer so that a new message can be created. When the user selects “+” in the new message creation window 550, a new message can be created and transmitted.

Further, a return button 551 is provided in the header of the message display screen 502b, and when the user selects the return button 551, it is possible to return to the work palette clip screen 502a which is the previous page. As described above, in the present embodiment, the display is switched from the pallet screen of one pallet to the pallet screen or the top screen of another pallet by the user's swipe operation. Therefore, in the present embodiment, movement between a plurality of screens related to one pallet is performed using a button such as the return button 551 instead of a swipe operation. Although it may not be shown in other drawings, a configuration in which a return button similar to the return button 551 is provided can be employed. Needless to say, the configuration may be such that movement between a plurality of screens related to one pallet is performed by a swipe operation.

As shown in FIG. 15, when the user selects the content display area 546 (pallet display area) on the work palette clip screen 502a, a pop-up screen 502c is displayed. The pop-up screen 502c includes a clipped palette user profile image, nickname, palette ID, clip release button, participation community button, and message confirmation button.

When the user selects the clip release button, the clip to the palette user is released and the palette user is not displayed on the work palette clip screen 502a. When the user selects the participation community button, a list of communities in which the palette user participates is displayed, and a community name, a community image, and the like in which the palette user participates are displayed. When a message button is selected, a message display screen 502b shown in FIG. 14 is displayed.

Returning to FIG. 14, when the user selects the community clip button 541 on the work palette clip screen 502a, a community clip display screen including a header representing a clip tab, a clip classification selection button, and a clipped community display area is displayed from the top. . In the community display area of the community clip display screen, the community name, community image, clipped time, and the like of the clipped community are displayed. When the user selects a community display area, a top screen (community top screen) of the community described later is displayed.

When the user selects the topic clip button 542 on the work palette clip screen 502a, a topic clip display screen including a header representing a clip tab, a clip classification selection button, and a clipped topic display area is displayed from the top. In the topic display area of the topic clip display screen, the topic title, topic photo, topic description, clipped time, etc. of the clipped topic are displayed. When the user selects a topic display area, the community top screen of the community in which the topic is posted is displayed. In the community top screen, the topic selected on the topic clip display screen can be displayed so as to come to the center of the screen.

When the user selects the comment clip button 543 on the work palette clip screen 502a, a comment clip display screen including a header representing a clip tab, a clip classification selection button, and a clipped comment display area is displayed from the top. The comment display area of the comment clip display screen displays the clipped comment text, images and links, clipped time, and the like. When the user selects the comment display area, the top screen (topic top screen) of the topic to which the comment is posted is displayed. In the topic top screen, the comment selected on the comment clip display screen can be displayed so as to come to the center of the screen.

When the user selects the palette clip button 540 on the work palette clip screen 502a and the user does not clip any palette, the header indicating the clip tab, the clip classification selection button, and the clip registration method are displayed from the top. A screen including a button for displaying a description, a button for displaying a description of merit obtained by clipping, and a button for displaying a palette (recommended palette) clipped to other users is displayed. When the user selects a button for displaying a recommended palette, the recommended palette is displayed. In this recommended palette, a list of palettes with a large number of clips is displayed, and by selecting the list display, detailed information of the palette is displayed, and the user can newly clip.

Further, when the user selects the community clip button 541 on the work palette clip screen 502a, if the user does not clip any community, a header indicating a clip tab, a clip classification selection button, and registration of a clip from the top. A screen including a button for displaying a description of a method, a button for displaying a description of merit obtained by clipping, and a button for displaying an application top screen is displayed. When the user selects the button for displaying the application top screen, for example, the application top screen 500 as shown in FIG. 12 is displayed, and the user searches the community using the above-described community search function or in-category search function, and clips Can do.

In this way, users with multiple palettes (multiple personalities) can clip other users' palettes, communities, topics, and comments according to their common hobbies, topics, sensibilities, and preferences in any palette (personality) By doing so, you can create your own community without being aware of other pallet (personality) members and restrictions, etc. Can be managed.

13, when the user selects the community tab button 537 on the work palette screen 502, the work palette community screen is displayed. FIG. 16 is a diagram illustrating an example of the work palette community screen 502d. The work palette community screen 502d includes a header representing a community list from the top, a community display selection button 547, and a community display area 548 selected by the display selection button 547. A new community creation button 549 is provided in the header.

In the display selection button 547, the community to be displayed can be changed by pull-down. For example, in the work palette community screen 502d, the community in which the user participates is displayed. However, for example, it can be changed so that a popular community is displayed in the clipped palette of another user. In addition, a community with a large number of participants, a community with a large number of comments, or the like may be displayed. In the community display area 548 selected by the display selection button 547, a community name, a community image, the number of participants, and the like can be displayed. When the user selects any one of the community display areas 548, a community top screen described later is displayed.

Also, when the user selects the new community creation button 549, a new community creation screen is displayed, and the user can create a new community.

When the community tab button 537 is selected, if the user is not participating in any community, a display switching button for guiding to the application top screen 500 is arranged, and a screen for searching for a community can be displayed.

13, when the user selects the notification tab button 538 on the work palette screen 502, the work palette notification screen is displayed. The user can display the notification in the palette for the user on the work palette notification screen, and can confirm the notification content. The contents, frequency, etc. of this notification can be set in detail.

When the notification tab button 538 is selected, if there is no notification, a notification setting button for finely setting the content and frequency of notification can be arranged to display the notification setting screen.

When the user selects the setting tab button 539 on the work pallet screen 502, the work pallet setting screen is displayed. FIG. 17 is a diagram illustrating an example of a work pallet setting screen 502e. The work palette setting screen 502e includes a header indicating palette settings from the top, a profile image setting area 560, a palette ID display area 561, a nickname setting area 562, a palette color setting area 563, a memo setting area 564, and Twitter (registered trademark) cooperation. A setting area 565, a Facebook (registered trademark) cooperation setting area 566, a setting area 567 for inviting friends using this palette, a friend search setting area 568, and a function restriction setting area 569 are included. From this setting screen, various information regarding the palette can be set.

When the user selects the profile image setting area 560, a profile image setting screen is displayed. The user can select and set the profile image of the palette from any image on the profile image selection screen.

When the user selects the nickname setting area 562, a nickname change screen is displayed. The user can change and save the nickname of the palette from the nickname change screen.

When the user selects the palette color setting area 563, a palette color change screen is displayed. FIG. 18 is a diagram illustrating an example of the palette color change screen 502f. The user can select, change, and save the palette color (theme color used throughout the palette) from the palette color change screen 502f. The palette color change screen 502f includes color samples 590 of a plurality of colors that can be used in the SNS application_Color in the present embodiment. When the user selects the color sample 590 of the color that he wants to use in the current palette, that color is set to the palette color of the current palette, and the palette-related screen is provided with a frame for this palette color, the header and footer The background is set to this palette color. Thus, the user can intuitively grasp which pallet he / she is logged in to when using a plurality of pallets. FIG. 18 shows a modification of the palette editing screen 510 shown in FIG.

Referring back to FIG. 17, when the user selects the memo setting area 564, a memo change screen is displayed. The user can change and save the memo on the palette from the memo change screen. This memo is invisible to other users. Although not shown, the memo of the pallet may be configured to be displayed in the header of the pallet top screen of the pallet.

When the user selects the Twitter (registered trademark) cooperation setting area 565, the Twitter (registered trademark) cooperation setting screen is displayed. The user can make settings for linking the palette and the user's Twitter (registered trademark) account from the Twitter (registered trademark) cooperation setting screen. Here, it is possible to make a setting for automatically posting to Twitter (registered trademark) when creating a community or automatically posting to Twitter (registered trademark) when creating a topic.

When the user selects the Facebook (registered trademark) linkage setting area 566, the Facebook (registered trademark) linkage setting screen is displayed. The user can make a setting for linking the palette and the user's Facebook (registered trademark) account from the Facebook (registered trademark) linkage setting screen. Here, it is possible to set to automatically post to Facebook (registered trademark) when creating a community in the palette, or to automatically post to Facebook (registered trademark) when creating a topic.

As described above, in this embodiment, the pallet ID can be recognized as an ID of a single-person user from other service users in SNS_Color. Therefore, the linkage with other existing SNS accounts such as Facebook (registered trademark) and Twitter (registered trademark) is not associated with the service user's user management ID but with the service user's palette ID. Is called. That is, any one palette ID of the service user can be associated with an account of another existing SNS. However, when a service user desires, it is good also as a structure which matches the palette ID of the said service user's several pallet with the account of the other existing SNS, for example.

When the user selects the setting area 567 for inviting friends from this palette, an e-mail message sending screen is displayed. For example, when a smartphone is used, it is a function of using an e-mail application program in the smartphone and sending an invitation message to the user's friend to use the SNS application_Color. Here, information that allows friends to use the SNS application_Color and the user's palette, such as the SNS application_Color guide, the SNS application_Color download link, and the user's palette ID, is described in advance in the message content. The user can send an e-mail by simply inputting or selecting the e-mail address of a friend to be invited. The user can also send an arbitrary message.

When the user selects the friend search setting area 568, a screen for searching for friends is displayed. The user can search for a friend using the palette ID of the friend who is looking for or the QR code (registered trademark) issued by the friend who is looking for. For example, when searching for friends by palette ID, the user can search for friends by inputting the palette ID of the friend who is looking for in the palette ID input unit.

When the user selects the function restriction setting area 569, the function restriction setting screen of the palette is displayed. FIG. 19 is a diagram illustrating an example of the function restriction setting screen 502g. The function restriction setting screen 502g includes buttons for turning on / off the pallet with respect to items such as “message transmission / reception restriction”, “pallet ID search target exclusion”, “pallet ID non-display”, and “secret handling”. For example, when the user turns on “message transmission / reception restriction”, transmission / reception of messages on the palette is restricted. When the user turns on “exclude pallet ID search target”, the pallet ID is excluded from search targets by other users. When the user turns on “Hide palette ID”, the palette ID of the palette is not displayed on the palette screen of the palette. When the user turns on “Confidential treatment”, information acquired on the palette is not displayed on the top screen. The setting information is stored in the application information storage unit 20 as shown in FIG.

Referring back to FIG. 12, when the user selects the user setting button 516 on the application top screen 500, a user setting screen is displayed. FIG. 20 is a diagram illustrating an example of the user setting screen 500a. On the user setting screen 500a, various settings of the SNS application_Color can be performed. The user setting screen 500a includes a user setting header, a notification setting bar, a function restriction bar, a mail address registration bar, a passcode lock bar, an area setting bar, a language setting bar, a help bar, and a color bar. And a withdrawal bar.

When the user selects the notification setting bar, the notification setting screen is displayed. In the notification setting screen, it is possible to set whether or not to perform various notifications for the community owned by the user or the community in which the user participates. On the notification setting screen, a notification setting header and a notification bar are displayed. In the notification bar, a switch for switching on / off of the notification is displayed. When the user turns on the notification bar switch, a batch setting bar for all palettes and an individual setting bar for each palette are displayed on the notification setting screen.

When the user selects the batch setting bar for all palettes, the batch setting screen for all palettes is displayed. In the batch setting screen for all pallets, various notification settings can be collectively made for all pallets.

When the user selects the individual setting bar for each palette, the palette selection screen is displayed. On the pallet selection screen, the pallet to be individually set can be selected. On the palette selection screen, a palette selection header and each palette created by the user are displayed as bars. When one of the palettes created by the user is selected, an individual palette setting screen is displayed. Various settings can be made for the selected palette on this individual palette setting screen.

In addition to the notification setting, for example, a language may be set for each palette. The various settings described with reference to FIG. 19 may be configured on the user setting screen 500a.

Next, the community top screen will be described. FIG. 21 is a diagram illustrating an example of the community top screen 570. As shown in FIG. 21, the community top screen 570 includes a community window 571, a related community bar 572, and a topic list window 573.

The community window 571 includes a community header indicating that the screen is related to a community, a community information display area 574, and a button area. The community header includes a display of “Community”, a topic creation icon 578, and a return button 579. In the community information display area 574, a community name, a community image, a category, an explanatory note, and the number of participants are displayed. The button area includes a join / leave button 575, a clip button 576, and an invite button 577.

When the user selects the topic creation icon 578 in the community header, a topic creation screen is displayed. The user can create a new topic on the topic creation screen.

When the user selects the return button 579 in the community header, the previous page is restored. As described above, in the present embodiment, the display is switched from the pallet screen of one pallet to the pallet screen or the top screen of another pallet by the user's swipe operation. Therefore, in the present embodiment, movement between a plurality of screens related to one pallet is performed using a button such as the return button 579 instead of a swipe operation. Although not shown in other drawings, a return button similar to the return button 579 can be provided.

In the community information display area 574, a large community image is displayed. In addition, the explanatory text of the community and each button in the button area are displayed so as to be superimposed on the community image. Each button in the button area is collected near the center.

When the user selects the community information display area 574, a community details screen is displayed. Detailed information on the community selected by the user is displayed on the community detail screen.

When the user selects the participant number display bar on the community details screen, the participation palette list screen is displayed. On the participating palette list screen, palettes participating in this community are displayed, and not only the user's own palette but also all palettes participating in the community including those of other users are displayed. A participation palette list header and a participant information display area are displayed on the participation palette list screen. In the participant information display area, information on each participant's palette is displayed. This palette information includes a nickname (pallet ID) and a profile image.

When the user does not participate in the community displayed in the community information display area 574 and selects the join / leave button 575 in the button area, a palette screen of a plurality of palettes created by the user (for example, the work palette screen 502). And the like, a community participation screen 570a including thumbnail images is displayed. The thumbnail image displays the palette ID and memo of the corresponding palette. Each thumbnail image may be configured to be identifiable by the palette color of the corresponding palette. The user swipes and selects an image of a palette that the user wants to use in the community from these thumbnail images, and selects a “join” button. Thereby, the user participates in the community with the palette ID corresponding to the selected palette. However, the user can also participate in one community or the like using his / her plurality of palette IDs. In this case, the plurality of palette IDs will be visible to other service users as another person.

On the other hand, when the user is participating in the community displayed in the community information display area 574, selecting the join / leave button 575 in the button area displays a community withdrawal screen for the user to leave the community. Further, when the user participates in the community with a plurality of palette IDs, a screen for selecting a palette to leave the community is displayed from among the plurality of palettes as in the community participation screen 570a.

When the user selects the clip button 576 in the button area, the community is clipped. When the user selects the invitation button 577 in the button area, a palette selection screen to invite is displayed. In the pallet selection screen to invite, the pallet ID of the inviting person can be searched. Then, you can send invitations to this community to those who have hit the search.

When the user selects the related community bar 572, the related community screen is displayed. On the related community screen, a list of communities related to the community currently displayed on the community top screen 570 is displayed. The displayed information of each community includes a community name, a community image, an explanatory note, and the number of participants.

The topic list window 573 includes a topic list header, an order bar 580, and a topic information display area 581. When the user selects the order bar 580, the displayed topic order can be changed between the topic creation time and the number of comments. The topic information display area 581 displays a topic title, a topic photo, a topic description, the number of comments, the number of viewers, the last comment date and time, and the community name. In the topic information display area 581, for example, two topics per row may be arranged in parallel. Within each topic, topic photos are displayed in large size, and the number of participants in the topic is displayed in real time.

When the user selects any topic displayed in the topic list window 573, the topic top screen is displayed. The topic top screen displays the latest comments on the topic. When the user selects a comment, the comment is enlarged and displayed on the screen. This enlarged display includes a profile image, nickname, palette ID, comment text, image, link, number of clips, posting date, nickname of reply source, profile image of reply source, and clip button A reply button and a report button.

When the user selects a profile image in the comment displayed in the comment display area, the information about the comment contributor is enlarged and displayed on the screen. This information includes a profile image, a nickname, a palette ID, a clip / unclip button, a participating community button, and a message button.

Users can also post comments from the topic top screen. As comments, images such as photos, links to websites, stamps, etc. can also be posted.

Next, processing when user registration is performed in the SNS providing server device 40 will be described. FIG. 22 is a diagram illustrating an example of a procedure for performing user registration in the SNS providing server device 40 of the present embodiment. Here, a procedure for performing user registration using SMS (Short Message Service) is shown. In user registration via SMS, the terminal device 10 (SNS application_Color), the SNS providing server device 40, and an SMS service server 90 (for example, a twilio server) that performs SMS transmission / reception services are involved.

When performing user registration of the SNS providing server device 40 (SNS_Color), first, the SNS providing server device 40 issues a consumer key to the terminal device 10. The consumer key is a character string that serves as a key for identifying the service user, and is stored in both the SNS providing server device 40 and the terminal device 10. Based on this, the terminal device 10 transmits the information including the consumer key to the SMS service server 90 by SMS. When this information is received, the SMS service server 90 transmits the user's telephone number and consumer key to the SNS providing server device 40. The SNS providing server device 40 stores them as user information. In addition, the SNS providing server device 40 issues a user management ID to the user.

Further, when the terminal device 10 receives the consumer key from the SNS providing server device 40, for example, after 5 seconds, the terminal device 10 collates the consumer key with the SNS providing server device 40. When the consumer key is correctly verified, the SNS providing server device 40 issues a token to the terminal device 10. For example, the token has a one-day expiration date, and is issued every day based on the consumer key. The token is also stored in both the SNS providing server device 40 and the terminal device 10. The SNS providing server device 40, as user information, associates a user management ID with a telephone number, a consumer key, and a consumer key that are irreversibly encrypted, and a token that is issued every day and an SMS authentication completion flag. Memorize etc.

FIG. 23 is a diagram illustrating another example of a procedure for performing user registration in the SNS providing server device 40 of the present embodiment. Here, a procedure for performing user registration using mail is shown. In user registration via mail, the SNS providing server device 40, the terminal device 10 (SNS application_Color), mail software, and a web browser are involved.

When performing user registration of the SNS providing server device 40 (SNS_Color), the terminal device 10 first registers a mail address and a password in the SNS providing server device 40. In response to this, the SNS providing server device 40 stores user information. This user information includes an email address, password, consumer key, token, and email authentication completion flag. In addition, the SNS providing server device 40 issues a consumer key to the terminal device 10. Furthermore, the SNS providing server device 40 transmits a confirmation mail to the registered mail address. This e-mail includes a URL for confirmation of registration. When the terminal device 10 receives the mail and the user selects a registration confirmation URL, the web browser of the terminal device 10 accesses the URL. The SNS providing server device 40 detects this access and sets an e-mail authentication completion flag. In addition, the SNS providing server device 40 transmits information indicating that the flag has been changed to the web browser. As a result, the web browser displays that the user registration has been completed. Further, the web browser activates the SNS application_Color. In addition, the SNS providing server device 40 issues a user management ID to the user. The SNS providing server device 40, as user information, associates a user management ID with a mail address, irreversibly encrypted password, consumer key, token issued every day based on the consumer key, and e-mail. An authentication completion flag or the like is stored.

When the user management ID is issued, in the terminal device 10, the service user can create a palette using the SNS application_Color. That is, in the present embodiment, the palette is not created when the service user downloads the SNS application_Color or when the user management ID is issued. When the service user instructs to create a palette, the user information management unit 42 issues a palette ID in the SNS providing server device 40 and stores the palette ID in the palette information storage unit 62 in association with the user management ID of the corresponding service user. To do. By repeating this procedure, each service user can create a plurality of palettes.

As described above, in the present embodiment, the display of a plurality of palette screens is switched by a swipe operation on the touch panel of the service user terminal device 10. In the present embodiment, a procedure for enabling such a configuration will be described.

FIG. 24 is a flowchart showing a processing procedure of the SNS providing server device 40 when the service user of the terminal device 10 logs in to the SNS providing server device 40.

When the service user activates the SNS application_Color in the terminal device 10, information for specifying the service user such as a token is transmitted from the terminal device 10 to the SNS providing server device 40 together with a login request. When the SNS providing server device 40 receives a login request (YES in step S102), the access management unit 44 refers to the user information storage unit 60 and performs user authentication based on the token. When the user is authenticated (YES in step S104), the access management unit 44 refers to the palette information storage unit 62 and performs a process of setting all the palette IDs corresponding to the user management ID to the login state (step S106). . That is, the access management unit 44 acquires all palette IDs corresponding to the user management ID, the screen providing processing unit 46 acquires palette screen information corresponding to all these palette IDs, and the SNS control unit 41 Each of the acquired palette screen information is transmitted to the terminal device 10. As a result, since the service user is logged in to the SNS providing server device 40 and all the palette IDs related to the service user are logged in, the service user can swipe the screen group of the SNS application_Color in the terminal device 10. When the display is selected, SNS_Color can be accessed with the corresponding palette ID without performing user authentication each time.

In step S104, if the user is not authenticated (NO in step S104), an error notification or the like is performed.

The preferred embodiments and examples of the present invention have been described in detail above. However, the present invention is not limited to the specific embodiments and examples described above, and is based on the gist of the present invention described in the claims. Various modifications and changes can be made within the range.

In the above embodiment, the terminal device 10 having a touch panel is assumed, but the present invention is also applicable when the terminal device 10 is a personal computer (PC) or the like that does not have a touch panel. In this case, the service user can switch the display between the top screen of the screen group and the plurality of palette screens by using an input device such as a mouse instead of the swipe operation.

For example, a method of providing a screen such as the application top screen 500 displayed on the touch panel of the terminal device 10 can be either “application type” or “browser type”.

The application type downloads the SNS application_Color from the SNS providing server device 40 or the like to the terminal device 10 in advance, executes the program on the terminal device 10, and includes screen transitions included in the program stored in the terminal device 10 through the download. Screen information is generated and displayed based on information and data acquired from the server in response to an input operation. On the other hand, the browser type manages the screen transition information (View information) describing the display control contents of a series of screens on the SNS providing server device 40 side, and according to the data acquisition request accompanying the input operation from the terminal device 10, Data such as an HTML data document and an image associated therewith is transmitted to the terminal device 10 and displayed on a web browser on the terminal device 10.

In the above embodiment, the description is mainly made on the assumption that “application type” is used, but “browser type” can also be used. In that case, it is set as the structure which the SNS control part 41 of the SNS provision server apparatus 40 and the screen provision process part 46 perform the process which the SNS control part 12 and the screen provision process part 14 of the terminal device 10 performed by the above embodiment, respectively. be able to.

The processing method for storing the program for operating the configuration of the above-described embodiment so as to realize the function of the above-described embodiment in a storage medium, reading the program stored in the storage medium as a code, and executing the program on the computer is also described above. It is included in the category of the embodiment. That is, a computer-readable storage medium is also included in the scope of the embodiments. In addition to the storage medium storing the computer program, the computer program itself is included in the above-described embodiment. As such a storage medium, for example, a floppy (registered trademark) disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a magnetic tape, a nonvolatile memory card, and a ROM can be used. In addition, the processing is not limited to the single program stored in the above-described storage medium, but operates on the OS in cooperation with other software and expansion board functions to execute the operations of the above-described embodiments. This is also included in the category of the embodiment described above.

This international application claims priority based on US Provisional Application No. 62 / 007,069 filed on June 3, 2014, the entire contents of which are incorporated herein by reference.

Claims

Computer
A personal management ID that uniquely identifies one service user within a given social network service and that is uniquely identified within the service and recognized as a single user by other service users within the service A means of managing multiple associations,
SNS offer program to function as.
In the SNS providing program according to claim 1,
Computer
A top screen corresponding to the service user identified by the user management ID on a terminal device logged in to the social network service with the user management ID, and other than the user management ID with respect to the social network service Screen providing processing means for providing a screen group including a top screen that cannot be viewed when logged in with an ID and a plurality of personality screens respectively identified by the plurality of personality IDs;
SNS offer program to function as.
In the SNS providing program according to claim 2,
The SNS providing program for providing the screen group so that the screen providing processing means can identify the plurality of personality screens with different colors.
A user management ID that uniquely identifies one service user within a given social network service, and a personality ID that is uniquely identified within the service and recognized as a single user by other service users within the service A storage unit for storing
When receiving a login request to the social network service by the terminal device and information for specifying the service user from the terminal device via the network, the storage unit is referred to based on the information for specifying the information A SNS providing server device comprising: a processing unit that acquires all personality IDs associated with a user management ID and transmits each piece of screen information corresponding to each acquired personality ID to the terminal device.
A user management ID that uniquely identifies one service user within a service that provides a predetermined social network is uniquely identified within the service and recognized as a single user from other service users within the social network SNS providing system including a control unit that manages a plurality of personality IDs associated with each other.