WO2016031432A1 - 情報処理装置、情報処理方法、プログラム、サーバー及び情報処理システム - Google Patents

情報処理装置、情報処理方法、プログラム、サーバー及び情報処理システム Download PDF

Info

Publication number
WO2016031432A1
WO2016031432A1 PCT/JP2015/070687 JP2015070687W WO2016031432A1 WO 2016031432 A1 WO2016031432 A1 WO 2016031432A1 JP 2015070687 W JP2015070687 W JP 2015070687W WO 2016031432 A1 WO2016031432 A1 WO 2016031432A1
Authority
WO
WIPO (PCT)
Prior art keywords
schedule
information
terminal
server
identification information
Prior art date
Application number
PCT/JP2015/070687
Other languages
English (en)
French (fr)
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 ソニー株式会社
Priority to JP2016545052A priority Critical patent/JP6601399B2/ja
Publication of WO2016031432A1 publication Critical patent/WO2016031432A1/ja

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management

Definitions

  • the present disclosure relates to an information processing apparatus, an information processing method, a program, a server, and an information processing system method.
  • Patent Document 1 discloses a technique that facilitates registration of a schedule that can be shared by a plurality of individual users and allows each user to easily view the schedules of other users. Are listed.
  • Patent Document 2 describes a technique that assumes whether or not schedule information can be received by a communication terminal on the schedule information reception side without using a server device.
  • an identification that stores identification information corresponding to the downloaded schedule sharing application that is set from a server that manages the schedule information
  • An information processing apparatus comprising: an information storage unit; and a transmission unit that transmits the identification information and the schedule information to the server when registering the schedule information with the other user's terminal in the server.
  • identification information corresponding to the downloaded schedule sharing application set from a server that manages the schedule information is stored. And providing the identification information and the schedule information to the server when registering the schedule information with the server for sharing with other users' terminals. Is done.
  • identification information corresponding to the downloaded schedule sharing application set from a server that manages the schedule information is stored.
  • an identification information issuing unit that issues identification information corresponding to a downloaded schedule sharing application in response to downloading of a schedule sharing application for sharing schedule information to the terminal, and the terminal
  • a server comprising: a registration unit that receives and registers the identification information and the schedule information transmitted from the terminal when sharing the schedule information with another user's terminal.
  • the identification information corresponding to the downloaded schedule sharing application is issued, and the terminal And receiving and registering the identification information and the schedule information transmitted from the terminal when the terminal is shared with another user's terminal, an information processing method is provided.
  • means for issuing identification information corresponding to the downloaded schedule sharing application in response to downloading of the schedule sharing application for sharing the schedule information to the terminal the terminal outputs the schedule information.
  • a program for causing a computer to function as means for receiving and registering the identification information and the schedule information transmitted from the terminal when sharing with another user's terminal is provided.
  • the identification information issuing unit that issues the identification information corresponding to the downloaded schedule sharing application in response to the download to the information processing apparatus of the schedule sharing application for sharing the schedule information
  • a server having a registration unit that receives and registers the identification information and the schedule information transmitted from the terminal when the information processing apparatus shares the schedule information with another user's terminal;
  • An identification information storage unit configured to store the identification information corresponding to the downloaded schedule sharing application, which is set from the server that manages the schedule information in response to the download of the schedule sharing application for sharing, and the schedule When registering with the server to share information with other users' terminals, the identification And a transmission section that transmits broadcast and the schedule information to the server, information processing system comprising, said information processing apparatus is provided.
  • Schedule sharing system configuration 2. Association of information on invitees and invitees based on the schedule identification ID 3. When the invitee's terminal has not downloaded the schedule sharing application If the invitee's device has downloaded the schedule sharing application
  • FIG. 1 is a schematic diagram illustrating a configuration example of a system according to the present embodiment.
  • the system according to the present embodiment includes a server 100, a terminal 200, and a terminal 300.
  • the terminals 200 and 300 are devices having a display screen and an operation unit such as a smartphone, for example.
  • the terminals 200 and 300 are terminals including a touch panel provided with a touch sensor on a display screen.
  • the terminals 200 and 300 are not limited thereto.
  • the server 100 includes a communication unit 102, an identification information issuing unit 104, a schedule registration unit 106, a schedule identification information issuing unit 108, and a database 110.
  • the terminal 200 includes a database 210, a communication unit 220, an operation input unit 222, a schedule information creation unit 224, an imaging unit 226, a display processing unit 228, and a display unit 230.
  • These components shown in FIG. 1 can be configured by a circuit or a central processing unit such as a CPU and a program (software) for causing it to function.
  • the program can be stored in a storage unit such as a memory included in the server 100 or the terminals 200 and 300, or a memory inserted from the outside.
  • the communication unit 102 of the server 100 is an interface that communicates with the terminals 200 and 300.
  • the identification information issuing unit 104 issues a UUID described later.
  • the schedule registration unit 106 registers a schedule when schedule information and UUID are transmitted from the terminal 200 in step S12 of FIG.
  • the schedule identification information issuing unit 108 issues a schedule identification ID described later.
  • the database 110 stores various types of information related to schedule sharing.
  • the database 210 of the terminal 200 is a database provided in a schedule sharing application to be described later, or a database such as a memory and a hard disk provided in the terminal 200.
  • the communication unit 220 is an interface that communicates with the server 100 or the terminal 300.
  • the operation input unit 222 is a component such as a touch sensor or an operation button that is input by a user operation.
  • the schedule information creation unit 224 creates schedule information to be described later in response to a user operation.
  • the imaging unit 226 includes an imaging element such as a CCD sensor or a CMOS sensor and an imaging optical system. The imaging unit 226 photoelectrically converts a subject image formed on the imaging surface of the imaging element by the imaging optical system, and thus image data such as a still image or a moving image. To get.
  • the display processing unit 228 performs processing for performing display on the display unit 230.
  • the display unit 230 includes a liquid crystal display (LCD) or the like.
  • each user shares a schedule without using personal information using the terminals 200 and 300 owned by each user.
  • a unique ID (hereinafter also referred to as a UUID) is assigned to a schedule sharing application (hereinafter also referred to as a schedule sharing application) downloaded by the terminals 200 and 300.
  • An event identification ID is assigned to a schedule (event) created by a shared individual, and a public event ID is assigned to a schedule (event) created by a company.
  • these event identification ID and public event ID are referred to as scheduled identification IDs. Then, information associated with these schedule identification IDs is managed on the server 100 side, and schedule sharing is realized by exchanging this schedule identification ID between users.
  • the user can perform individual schedule (event) units without going through complicated processes such as registration of personal information and login using ID / password (PW).
  • Information can be shared between any users. Once shared, the shared members can freely change or add content, and even if it is changed in the middle, the change is immediately reflected in all shared users. Since registration of personal information is not required and a process such as login is not required, users can easily share a schedule between users without performing complicated processing.
  • each user can share his / her schedule with family and friends with simple settings based on the scheduler function.
  • you can automatically distribute the latest information just by selecting the information you want, such as new product information of your favorite company, coupons for frequently-used stores, route operation information, currency exchange and stock information, etc. Connected mode).
  • it is possible to notify only the information required by the user in cooperation with the wearable device, and it is also possible to reflect the life log owned by the device on the scheduler (a mode connected to things).
  • the server 100 issues a UUID (unique identification information different for each terminal) when the schedule sharing application (schedule sharing software) is downloaded to each terminal 200, 300.
  • This UUID is not issued to the terminals 200 and 300, but is issued to the downloaded application. Therefore, even if the terminal 200 is the same, when the scheduled sharing application is downloaded again, a UUID is newly issued.
  • the UUID is transmitted to each terminal 200, 300 that has downloaded the scheduled sharing application, and stored in the databases 210, 310 of each terminal 200, 300. Note that the UUID is not notified to the user, and the user can perform subsequent operations without being aware of the issued UUID.
  • Users can create schedules using their own terminals 200 and 300.
  • the created schedule is stored in the terminals 200 and 300.
  • the users of the terminals 200 and 300 can share the created schedule with users of other terminals and can invite participation in the schedule.
  • the server 100 manages participants, non-participants, and unanswered participants in the shared schedule.
  • the server 100 issues a unique schedule identification ID to the schedule that is difficult to guess by the user.
  • each user sets a nickname so that the user can be identified when sharing the schedule.
  • One user may have one nickname, and the nickname may overlap with other users. Even when nicknames are duplicated among a plurality of users, the UUID is uniquely set for the scheduled sharing application downloaded by each terminal, and thus the user can be uniquely specified using the UUID.
  • the terminal 200 after downloading the schedule sharing application, the terminal 200 performs schedule registration in step S10.
  • the UUID issued from the server 100 by downloading the schedule sharing application is stored in the database 210 of the terminal 200.
  • FIG. 2 is a schematic diagram showing a screen of the terminal 200.
  • a screen 500 shows an initial state.
  • the button 202 presses the button 202 in a state where a check mark is added to “My schedule”, “Invited schedule”, and “A company domestic trip” as “Events to be displayed” on the screen 500, the screen transitions to the screen 502. .
  • a calendar is displayed, and below the calendar, all events related to the events selected as “display events” (“your own schedule”, “invited schedule”, “company A domestic trip”) are displayed. Event information is displayed.
  • all events including events other than the selected event can be displayed by performing a predetermined operation.
  • “My schedule” and “Invited schedule” are schedules (events) created by individuals, and “A company domestic trip” is a schedule (event) created by a company.
  • the user wants to newly register an event, when the user presses the button 204 on the screen 502 in FIG. On the screen 506, the user inputs schedule information such as “title”, “description” of the event, “start” and “end”, and “location” of the event, and presses the completion button 206 to schedule the terminal 200.
  • Register When registering an “image” (image) on the screen 506, it is possible to select and register from a plurality of images displayed on the screen 508 in FIG. Transition from the screen 506 to the screen 508 can be performed by operating a predetermined button.
  • the registered “image” is displayed on the screens 502 and 504 in FIG. 2 to indicate a schedule. Thereby, the user can visually discriminate each schedule from the displayed “image” (image) on the screens 502 and 504.
  • step S10 in FIG. 1 is completed.
  • “travel to Izu” is registered as a schedule.
  • the registered schedule is stored in the database 210 (see FIG. 1) in the schedule sharing application of the terminal 200.
  • the registered schedule is displayed below the calendar on the screen 502 in FIG. 2, and when all events are displayed, it is displayed on the screen 504 in FIG.
  • FIG. 4 is a schematic diagram showing a screen for inviting to a registered schedule.
  • the screen can transition to the screen 510 (schedule details screen) of FIG.
  • the screen 502 in FIG. 2 or an arbitrary schedule displayed on the screen 504 can be changed to the screen 510 in FIG. 4 by selecting a schedule that has not yet invited a friend.
  • the user of the terminal 200 can share the registered schedule with other users by pressing a button 208 (“Invite friends”) displayed on the lower side of the screen 510 in FIG. Can be invited to the event.
  • a button 208 (“Invite friends”) displayed on the lower side of the screen 510 in FIG. Can be invited to the event.
  • the UUID and schedule information of the terminal 200 are sent to the server 100 in step S12 in FIG. 1, and the user of the terminal 200 plans to invite another user in the server 100 ( Hereinafter, registration of “scheduled to be invited” is performed.
  • the server 100 registers the schedule information sent from the terminal 200 in association with the UUID of the terminal 200, and issues a schedule identification ID for identifying the registered schedule.
  • the schedule identification ID is returned to the terminal 200 in step S13.
  • the terminal 200 that has received the schedule identification ID stores the schedule identification ID in the database 210.
  • the schedule identification ID is not issued, and when the user presses the button 208 and the schedule to be invited is registered in the server 100.
  • the server 100 issues a schedule identification ID and returns it to the terminal 200.
  • step S14 of FIG. 1 an invitation message is transmitted to an invitee (terminal 300).
  • the invitation message to the invitee is transmitted together with the schedule identification ID.
  • the screen 514 in FIG. 4 shows a case where the invitee's terminal 300 has not downloaded the schedule sharing application.
  • SMS Short Message Service
  • SNS social network services
  • the terminal 300 of the invitee who has received the invitation message and the schedule identification ID transmits the schedule identification ID to the server 100 in step S15.
  • the server 100 receives the schedule identification ID from the terminal 300 in step S15, the server 100 transmits the schedule information associated with the received schedule identification ID to the terminal 300 in step S16.
  • the terminal 300 can acquire schedule information corresponding to the schedule identification ID together with the schedule identification ID already received from the terminal 200.
  • the schedule information of the invited schedule is displayed on the screen of the terminal 300. Further, the schedule identification ID and the schedule information are reflected (registered) in the database 310 of the terminal 300 in step S17 of FIG.
  • the user of the terminal 300 operates the terminal 300 to input whether to participate in the invited schedule. Then, when the user of the terminal 300 inputs participation or non-participation in the invited schedule, in step S18 of FIG. 1, the UUID of the terminal 300 and the schedule identification ID together with the participation or non-participation information from the terminal 300 to the server 100. Is sent. Based on the notification from the terminal 300 in step S18, the server 100 registers that the user of the terminal 300 recognized from the UUID is participating or not participating in the schedule corresponding to the schedule identification ID. If the user of terminal 300 has not answered the invited schedule, only the UUID and schedule identification ID of terminal 300 are transmitted in step S19. The server 100 registers that the user of the terminal 300 recognized from the UUID has not answered the schedule corresponding to the schedule identification ID.
  • FIG. 5 is a schematic diagram illustrating a state in which the server 100 associates the information of the invitee and the invitee based on the schedule identification ID.
  • corresponding schedule information 401 is associated with a certain schedule identification ID 400.
  • the UUID 402 of the inviter (scheduler) terminal is associated with the schedule identification ID 400
  • the nickname 404 and the photograph 406 of the inviter are associated with the UUID 402.
  • the UUID 410, 420, 430 of the invitee's terminal is associated with the schedule identification ID.
  • the UUID 410 of the invitee's terminal is associated with the invitee's nickname 414 and photograph 416.
  • the nickname 424 and the photograph 426 of the invitee are associated with the UUID 420 of the invitee's terminal
  • the nickname 434 and the photograph 436 of the invitee are associated with the UUID 430 of the invitee's terminal. .
  • the server 100 manages the participation information 418, 428, 438 of “participation”, “non-participation”, and “unanswered” according to the notification from the terminal of the invitee regarding the invitee.
  • FIG. 1 shows the association of information corresponding to one schedule identification ID 400.
  • the server 100 manages N pieces of information shown in FIG.
  • FIG. 6 is a schematic diagram showing an example of the data structure of the information shown in FIG.
  • information of FIG. 5 is rearranged and managed for each item of “schedule actors”, “schedules”, “users”, “event actors”, “events”, and “devices”.
  • schedule information is included in the schedule information.
  • user information is managed in the “users” item.
  • device information is managed in the “devices” item.
  • each item includes information (updated_at DATETIME) regarding schedule information update.
  • the schedule information is updated by the user of the terminals 200 and 300, the information is transmitted to the server 100 together with the schedule identification ID, and the server 100 updates the schedule information associated with the schedule identification ID.
  • FIG. 7 is a schematic diagram showing in detail the case where the invitee's terminal 300 has not downloaded the schedule sharing application.
  • an application e-mail, SMS, SNS or other existing communication apps
  • the schedule identification ID is sent to these other applications.
  • information related to the destination of the invitee selected by the user on the screen 512 of FIG. 4 is notified to another application such as e-mail, SMS, or SNS.
  • an invitation message is transmitted to the invitee terminal selected by the user through another application such as mail, SMS, or SNS.
  • another application such as mail, SMS, or SNS.
  • the schedule identification ID is transmitted to the terminal 300 via the invitation message.
  • the invitation message includes a download link (DL link) for downloading the schedule sharing application.
  • a download link is displayed on the screen of the terminal 300 that has received the invitation message.
  • the schedule sharing application is installed in the terminal 300 in step S26 of FIG.
  • the schedule sharing application is activated from the link in the invitation message.
  • the invitation message includes schedule identification ID information. For this reason, when the schedule sharing application is activated in step S28, the schedule identification ID is transmitted to the server 100 in step S29. Upon receiving the schedule identification ID, the server 100 transmits schedule information associated with the schedule identification ID to the terminal 300 in step S30.
  • the information of the schedule identification ID is included in the URL information of the download link in the invitation message.
  • the schedule sharing application can acquire the information of the schedule identification ID because the history of the URL is known from the cookie information of the browser after the download. Therefore, in step S29, the schedule identification ID can be transmitted to the server 100 simultaneously with the start of the schedule sharing application. Thereby, the server 100 can acquire the schedule identification ID when the schedule sharing application is activated from the link in the invitation message.
  • the subsequent processing is the same as in FIG. That is, when the terminal 300 acquires the schedule identification ID and the schedule information, the schedule information of the invited schedule is displayed on the terminal 300.
  • the schedule identification ID and the schedule information are reflected (registered) in the database 310 of the terminal 300.
  • the terminal 300 transmits the UUID and schedule identification ID of the terminal 300 together with the participation or non-participation information. If the user of terminal 300 does not input an answer for participation or non-participation, only the UUID and schedule identification ID of terminal 300 are transmitted in step S19.
  • FIG. 8 is a schematic diagram illustrating a case where the invitee's terminal 300 has already downloaded the schedule sharing application.
  • the schedule can be shared using the schedule sharing application that the terminal 300 has already downloaded.
  • the schedule can be shared through an existing communication application such as mail, SMS, or SNS.
  • the process for sharing a schedule through e-mail, SMS, SNS, etc. is basically the same as in FIG. 7, but it is necessary to perform a process (step S26) of clicking the download link to download the schedule sharing application. This is different from the process of FIG.
  • step S40 when registration of the schedule in step S10 is completed, an invitee is selected in step S40. Specifically, a button 208 (“Invite a friend”) displayed on the lower side of the screen 510 in FIG. 4 is pressed, and an invitee is selected on the screen 512 in FIG. These processes are the same as those in FIG. At this time, when the invitee is a user who has been invited in the past, the schedule sharing application of the terminal 200 recognizes the UUID of the invitee in advance.
  • a button 208 (“Invite a friend”) displayed on the lower side of the screen 510 in FIG. 4 is pressed, and an invitee is selected on the screen 512 in FIG.
  • step S42 By pressing the button 212 on the screen 512 with the invitee selected, the registered schedule can be shared with other users, and other users are invited to the schedule (step S42).
  • step S12 of FIG. 1 the UUID and schedule information of the terminal 200 are transmitted to the server 100.
  • step S42 of FIG. 7 in addition to the UUID and schedule information of the terminal 200, the UUID of the invitee Is also sent to the server 100.
  • the server 100 registers the schedule information sent from the terminal 200 in association with the UUID of the terminal 200, and issues a schedule identification ID for identifying the registered schedule.
  • the schedule identification ID is returned to the terminal 200 in step S13.
  • the server 100 also associates the schedule identification ID with the UUID of the invitee, and initially registers the invitee as an unanswered person.
  • step S44 the schedule identification ID is transmitted together with the schedule information from the server 100 to the terminal 300 having the UUID of the invitee.
  • the invitee's terminal 300 holds the schedule identification ID and schedule information. Therefore, unlike the process of FIG. 7, the terminal 300 does not need to send the schedule identification ID to the server 100 in order to acquire the schedule information.
  • the terminal 300 displays the schedule information of the invited schedule.
  • step S17 the schedule identification ID and the schedule information are reflected (registered) in the database 310 of the terminal 300.
  • step S46 When the user of the terminal 300 inputs that he / she participates or does not participate in the invited schedule, in step S46, the UUID and the schedule identification ID of the terminal 300 are transmitted from the terminal 300 to the server 100 together with information on participation or non-participation. Further, if the user of the terminal 300 does not input that he / she participates or does not participate in the invited schedule, the process of step S46 is not performed, and the server 100 still treats the terminal 300 as an unanswered person.
  • the server 100 receives the schedule identification ID and the schedule information based on the UUID of the invitee transmitted from the terminal 200. It can be transmitted to the terminal 300 of the invitee. Therefore, the invitee's terminal 300 does not need to acquire the schedule information by transmitting the schedule identification ID to the server 100, and can simplify the process.
  • a UUID can be set for the terminals 200 and 300 that have downloaded the schedule sharing application. Then, the server 100 can associate each user's terminals 200 and 300 with the schedule based on the UUID. Therefore, the user does not need to perform processing such as login, and can share the schedule with a simple procedure.
  • An identification information storage unit that stores identification information corresponding to the downloaded schedule sharing application, which is set from a server that manages the schedule information in response to downloading of the schedule sharing application for sharing the schedule information
  • a transmitter for transmitting the identification information and the schedule information to the server when registering the schedule information with the server for sharing with other users'terminals
  • An information processing apparatus comprising: (2) The information processing apparatus according to (1), further including a schedule identification information storage unit that stores schedule identification information transmitted from the server in response to registration of the identification information and the schedule information with the server.
  • an operation input unit for inputting a user's operation;
  • a schedule information creating unit for creating the schedule information according to the input operation; The information processing apparatus according to (1) or (2).
  • the schedule information and the schedule identification information are notified to the terminal of the other user, according to any one of (1) to (3)
  • the terminal of the other user has downloaded the schedule sharing application, Notification of the schedule information and the schedule identification information to the other user is performed via the server, The identification information of the other user is transmitted together with the identification information and the schedule information when the schedule information is registered with the server for sharing with the terminal of the other user.
  • Information processing device. The terminal of the other user has not downloaded the schedule sharing application, The information processing apparatus according to (4), wherein the notification of the schedule information and the schedule identification information to the other user is performed via another application different from the schedule sharing application.
  • an identification information issuing unit that issues identification information corresponding to the downloaded schedule sharing application in response to downloading to the terminal of the schedule sharing application for sharing the schedule information;
  • a schedule registration unit for receiving and registering the identification information and the schedule information transmitted from the terminal when the terminal shares the schedule information with another user's terminal;
  • Server with. (11) The server according to claim 10, further comprising a schedule identification information transmitting unit that transmits schedule identification information to the terminal in response to registration of the identification information and the schedule information in the server.
  • the terminal When the terminal invites another user to the schedule related to the schedule information, the terminal notifies the other user's terminal of the schedule information and the schedule identification information received from the terminal, (10) The server described in.
  • the other user's terminal has downloaded the schedule sharing application, The server according to (10), wherein the notification of the schedule information and the schedule identification information to the other user is performed via the server.
  • the other user's terminal has not downloaded the schedule sharing application, The server according to (12), wherein the notification of the schedule information and the schedule identification information to the other user is performed through another application different from the schedule sharing application.
  • the server according to (14), wherein the other application is any of mail, SNS, and SMS.
  • An information processing method comprising: (17) means for issuing identification information corresponding to the downloaded schedule sharing application in response to downloading to the terminal of the schedule sharing application for sharing the schedule information; Means for receiving and registering the identification information and the schedule information transmitted from the terminal when the terminal shares the schedule information with another user's terminal; As a program to make the computer function as.
  • an identification information issuing unit that issues identification information corresponding to the downloaded schedule sharing application in response to downloading of the schedule sharing application for sharing the schedule information to the information processing apparatus;
  • a schedule registration unit that receives and registers the identification information and the schedule information transmitted from the terminal when the information processing apparatus shares the schedule information with another user's terminal; Having a server and An identification information storage unit configured to store the identification information corresponding to the downloaded schedule sharing application, which is set from the server that manages the schedule information according to the download of the schedule sharing application for sharing the schedule information; ,
  • a transmission unit that transmits the identification information and the schedule information to the server when the schedule information is registered in the server for sharing with other users'terminals; and
  • An information processing system comprising:

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Economics (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephone Function (AREA)
PCT/JP2015/070687 2014-08-29 2015-07-21 情報処理装置、情報処理方法、プログラム、サーバー及び情報処理システム WO2016031432A1 (ja)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2016545052A JP6601399B2 (ja) 2014-08-29 2015-07-21 情報処理装置、情報処理方法、プログラム、サーバー及び情報処理システム

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2014-175751 2014-08-29
JP2014175751 2014-08-29

Publications (1)

Publication Number Publication Date
WO2016031432A1 true WO2016031432A1 (ja) 2016-03-03

Family

ID=55399333

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2015/070687 WO2016031432A1 (ja) 2014-08-29 2015-07-21 情報処理装置、情報処理方法、プログラム、サーバー及び情報処理システム

Country Status (3)

Country Link
JP (1) JP6601399B2 (zh)
TW (1) TWI675298B (zh)
WO (1) WO2016031432A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7450148B1 (ja) 2023-06-07 2024-03-15 株式会社令和トラベル 旅行情報共有システム、旅行情報共有プログラム及び、旅行情報共有方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003348080A (ja) * 2002-05-28 2003-12-05 Nec Corp 画像処理配信方法およびプログラム
WO2013186937A1 (ja) * 2012-06-11 2013-12-19 ユーイング株式会社 通信システム及び通信端末接続方法
JP2014021969A (ja) * 2012-07-13 2014-02-03 Line Corp メッセンジャープラットフォームのユーザ関係情報に基づいて様々なサービスを提供する方法及びシステム
WO2014073277A1 (ja) * 2012-11-09 2014-05-15 ソニー株式会社 通信端末、通信方法、プログラム、及び通信システム
JP2014106586A (ja) * 2012-11-26 2014-06-09 Nec Biglobe Ltd 管理システム、管理サーバ、管理方法およびプログラム

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003348080A (ja) * 2002-05-28 2003-12-05 Nec Corp 画像処理配信方法およびプログラム
WO2013186937A1 (ja) * 2012-06-11 2013-12-19 ユーイング株式会社 通信システム及び通信端末接続方法
JP2014021969A (ja) * 2012-07-13 2014-02-03 Line Corp メッセンジャープラットフォームのユーザ関係情報に基づいて様々なサービスを提供する方法及びシステム
WO2014073277A1 (ja) * 2012-11-09 2014-05-15 ソニー株式会社 通信端末、通信方法、プログラム、及び通信システム
JP2014106586A (ja) * 2012-11-26 2014-06-09 Nec Biglobe Ltd 管理システム、管理サーバ、管理方法およびプログラム

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7450148B1 (ja) 2023-06-07 2024-03-15 株式会社令和トラベル 旅行情報共有システム、旅行情報共有プログラム及び、旅行情報共有方法

Also Published As

Publication number Publication date
TW201633155A (zh) 2016-09-16
TWI675298B (zh) 2019-10-21
JPWO2016031432A1 (ja) 2017-06-08
JP6601399B2 (ja) 2019-11-06

Similar Documents

Publication Publication Date Title
US20170118165A1 (en) System and method for controlled sharing and synchronizing information across a plurality of mobile client application computers
JP6589869B2 (ja) 情報処理装置、情報処理方法、プログラム、サーバー及び情報処理システム
AU2023200458A1 (en) System and method for video communication
US20100088372A1 (en) Conference networking system incorporating social networking site information
US10812431B2 (en) Social platform for event creation and communication and method therefor
US8832190B1 (en) Chat-enabled social circles
US20150356468A1 (en) Mobile chat systems for real time polling, rating and rsvp'ing
WO2021205240A1 (en) Different types of text call services, centralized live chat applications and different types of communication mediums for caller and callee or communication participants
JP6194191B2 (ja) 情報処理システム
US20110283218A1 (en) Electronic Event Planner in Communication Device
JP2012003635A (ja) 情報処理装置、情報処理方法及びプログラム
JP5372288B1 (ja) サーバ装置、方法、および、プログラム
Haikio et al. 'Would You Be My Friend?'-Creating a Mobile Friend Network with'Hot in the City'
JP6601399B2 (ja) 情報処理装置、情報処理方法、プログラム、サーバー及び情報処理システム
US20200244592A1 (en) Resource reservation system, setting method, and non-transitory computer readable storage medium
US20140074972A1 (en) System and Electronic Device
JP2013105482A (ja) ビデオライブチャットシステム。
US20130024530A1 (en) Apparatus and method for providing community service in portable terminal
KR102190882B1 (ko) 커뮤니티 플랫폼 제공 방법 및 장치
JP5596094B2 (ja) システムおよび電子機器
JP2021106023A (ja) サーバ装置、携帯端末、イベント運営方法及びプログラム
JP2016201042A (ja) 情報処理システム及びそれに用いられるサーバ並びに情報処理プログラム
JP2019111399A (ja) コンピュータの制御プログラム及びメッセージ通信方法
EP3207692A1 (en) Electronic system for indirect intercommunication messaging between electronic terminals
JP2019096091A (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: 15836315

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2016545052

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15836315

Country of ref document: EP

Kind code of ref document: A1