US20200162857A1 - Terminal devices, information processing methods, and computer readable storage mediums - Google Patents
Terminal devices, information processing methods, and computer readable storage mediums Download PDFInfo
- Publication number
- US20200162857A1 US20200162857A1 US16/750,484 US202016750484A US2020162857A1 US 20200162857 A1 US20200162857 A1 US 20200162857A1 US 202016750484 A US202016750484 A US 202016750484A US 2020162857 A1 US2020162857 A1 US 2020162857A1
- Authority
- US
- United States
- Prior art keywords
- user
- mobile terminal
- group
- users
- relationship
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
- 238000003860 storage Methods 0.000 title description 27
- 230000010365 information processing Effects 0.000 title description 6
- 238000003672 processing method Methods 0.000 title description 4
- 230000004044 response Effects 0.000 claims abstract description 74
- 238000004891 communication Methods 0.000 abstract description 36
- 238000012545 processing Methods 0.000 description 62
- 230000007423 decrease Effects 0.000 description 34
- 238000000034 method Methods 0.000 description 31
- 230000008569 process Effects 0.000 description 24
- 238000010586 diagram Methods 0.000 description 22
- 238000005304 joining Methods 0.000 description 16
- 230000005540 biological transmission Effects 0.000 description 7
- 230000006870 function Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000003825 pressing Methods 0.000 description 3
- 238000013500 data storage Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000005530 etching Methods 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000010079 rubber tapping Methods 0.000 description 1
- 230000001131 transforming effect Effects 0.000 description 1
- 238000002604 ultrasonography Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
- H04W4/08—User group management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/15—Setup of multiple wireless link connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W8/186—Processing of subscriber group data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/005—Discovery of network devices, e.g. terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
- H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
Abstract
Description
- This application is a Continuation of U.S. application Ser. No. 16/148,149, filed on Oct. 1, 2018, which is a Divisional Application of U.S. application Ser. No. 14/837,748, filed on Aug. 27, 2015, which claims priority under 35 U.S.C. § 119 to Japanese Patent Application No. 2015-074149, filed on Mar. 31, 2015, in the Japanese Patent Office, the entire contents of all of which are incorporated herein by reference.
- One or more example embodiments relate to terminal devices, information processing methods, and/or computer readable storage mediums.
- Within services enabling transmission and reception of messages between registered users, users are able to search for other users located nearby using Global Positioning System (GPS) functions installed at users' mobile terminals. The users are then allowed to register each other.
- In addition, a mobile terminal is able to identify another mobile terminal by using short-range wireless communication.
- When users perform a registration operation (e.g., registration of a friend relationship) to transmit and receive messages using services such as an instant messaging (IM) service, which enables transmission and reception of messages between users, each of the users performs an operation for registering the other user. Accordingly, in the case of registering a plurality of users, each user needs to perform the registration operation with each of the other users. The same applies to the case where a plurality of other users are found through a search using GPS functionality. More specifically, even in situations where a plurality of other users are found through a search using GPS functionality, a user needs to perform the registration operation for each of the other users whom the user wishes to register. The user is not allowed to collectively register a plurality of other users at one time.
- At least one example embodiment enables registration of relationships and/or associations with a plurality of users using relatively short-range wireless communication.
- At least one example embodiment provides a terminal device connected, via a network, to a server device configured to manage a relationship between users configured to utilize a message transmission-reception service, and including a display unit and a transmission unit. The display unit is configured to display a list of other terminal devices identified to be located within a threshold (or alternatively given, desired or predetermined) range from the terminal device via short-range wireless communication. The transmission unit is configured to transmit to the server device, upon selection of a plurality of other terminal devices from among the other terminal devices included in the list, a request to establish a relationship with users of the plurality of selected other terminal devices.
- According to at least one example embodiment, a relationship with a plurality of users may be registered by using short-range wireless communication.
- At least one example embodiment provides a terminal device comprising: at least one processor configured to execute computer readable instructions to generate a list of a plurality of other terminal devices located within a threshold range from the terminal device via short-range wireless communication; and a transceiver configured to transmit, in response to selection of a set of terminal devices from among the plurality of other terminal devices included in the list, a request to establish an association with users corresponding to terminal devices in the selected set of terminal devices.
- According to at least some example embodiments, the transceiver may be further configured to transmit, in response to the selection of the set of terminal devices, a request to establish a group of users, the group of users including a user of the terminal device and the users corresponding to the terminal devices in the selected set of terminal devices.
- The transceiver may be further configured to transmit, in response to the selection of the set of terminal devices, a request to establish an association between a user of the terminal device and each of the users corresponding to the terminal devices in the selected set of terminal devices.
- The transceiver may be further configured to transmit, in response to the selection of the set of terminal devices, a request to establish an association between pairs of users, each pair of users including a user of the terminal device and a user from among the users corresponding to the terminal devices in the selected set of terminal devices.
- The at least one processor may be configured to execute computer readable instructions to generate a list of users corresponding to the plurality of other terminal devices based on user IDs received via the short-range wireless communication.
- The at least one processor may be configured to execute computer readable instructions to: receive a response to the request to establish the association; and display a request to agree to establish the association.
- The short-range wireless communication may be based on Bluetooth Low Energy.
- At least one other example embodiment provides an information processing method implemented in a terminal device, the information processing method comprising: generating a list of a plurality of other terminal devices located within a threshold range from the terminal device via short-range wireless communication; and transmitting, in response to selection of a set of terminal devices from among the plurality of other terminal devices included in the list, a request to establish an association with users corresponding to terminal devices in the selected set of terminal devices.
- At least one other example embodiment provides a non-transitory computer readable medium including computer-readable instructions that, when executed on a terminal device including at least one processor, cause the terminal device to perform a method comprising: generating a list of a plurality of other terminal devices located within a threshold range from the terminal device via short-range wireless communication; and transmitting, in response to selection of a set of terminal devices from among the plurality of other terminal devices included in the list, a request to establish an association with users corresponding to terminal devices in the selected set of terminal devices.
- According to at least some example embodiments, the method may further include: transmitting, in response to the selection of the set of terminal devices, a request to establish a group of users, the group of users including a user of the terminal device and the users corresponding to the terminal devices in the selected set of terminal devices.
- The method may further include: transmitting, in response to the selection of the set of terminal devices, a request to establish an association between a user of the terminal device and each of the users corresponding to the terminal devices in the selected set of terminal devices.
- The method may further include: transmitting, in response to the selection of the set of terminal devices, a request to establish an association between pairs of users, each pair of users including a user of the terminal device and a user from among the users corresponding to the terminal devices in the selected set of terminal devices.
- The generating may generate a list of users corresponding to the plurality of other terminal devices based on user IDs received via the short-range wireless communication.
- The method may further include: receiving a response to the request to establish the association; and displaying a request to agree to establish the association.
- The short-range wireless communication is based on Bluetooth Low Energy.
- At least one other example embodiment provides a messaging system comprising a messaging server. The messaging server includes a memory and at least one processor. The memory is configured to store computer readable instructions. The at least one processor is configured to execute the computer readable instructions to: generate a group relationship table based on a received group relationship registration request from a first terminal device, the group relationship registration request including a user identifier associated with the first terminal device and a user identifier of at least one second terminal device, the group relationship table being indicative of an association between the first terminal device and the at least one second terminal device; register the group relationship table in a group relationship database; and update the group relationship table based on an agreement response received from the at least one second terminal device, the agreement response indicating whether the at least one second terminal device has agreed to be associated with the first terminal device.
- The messaging server may further include a transceiver. The transceiver may be configured to: receive the group relationship registration request from the first terminal device; transmit a group relationship registration notification to the first terminal device in response to generation of the group relationship table by the at least one processor; transmit an agreement request to the at least one second terminal device, the agreement request including a group identifier associated with the group relationship table and user identifiers stored in the group relationship table, and the agreement request requesting to associate the at least one second terminal device with the first terminal device; and receive the agreement response from the at least one second terminal device.
- The system may further include the at least one second terminal device. The at least one second terminal device may include a transceiver and at least one processor. The transceiver may be configured to: receive the agreement request from the messaging server; and transmit the agreement response to the messaging server. The at least one processor may be configured to execute computer readable instructions to determine whether to accept the request to associate the at least one second terminal device with the first terminal device in response to the agreement request from the messaging server.
- The system may further include the first terminal device. The first terminal device may include at least one processor and a transceiver. The at least one processor may be configured to execute computer readable instructions to: generate a list of a plurality of other terminal devices located within a threshold range from the first terminal device via short-range wireless communication, the plurality of other terminal devices including the at least one second terminal device. The transceiver may be configured to: transmit, in response to selection of a set of terminal devices from among the plurality of other terminal devices included in the list, the group relationship registration request to the messaging server, the set of terminal devices including the at least one second terminal device.
-
FIG. 1 is a diagram of an example configuration of a service providing system according to an example embodiment. -
FIGS. 2A and 2B are diagrams of an example of a hardware configuration of the service providing system shown inFIG. 1 . -
FIG. 3 is a diagram of an example of a functional configuration of the service providing system shown inFIG. 1 . -
FIG. 4 is a diagram illustrating an example of a group relationship database. -
FIG. 5 is a flowchart of a search process according to an example embodiment. -
FIG. 6 is a conceptual diagram of an example of a search result list screen. -
FIG. 7 is a sequence diagram illustrating a group relationship registration process according to an example embodiment. -
FIGS. 8A and 8B are conceptual diagrams of an example of a group-joining agree/decline screen. -
FIG. 9 is a diagram of an example of a functional configuration of a service providing system according to another example embodiment. -
FIG. 10 is a diagram illustrating an example of a friend relationship database. -
FIG. 11 is a flowchart of a search process according to another example embodiment. -
FIG. 12 is a sequence diagram illustrating a friend relationship registration process according to an example embodiment. -
FIG. 13 is a diagram illustrating an example of a social graph. - Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to like elements throughout. In this regard, the example embodiments may have different forms and should not be construed as being limited to the descriptions set forth herein. Accordingly, some example embodiments are described below, by referring to the figures, to explain aspects of the present description. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items. Expressions such as “at least one of,” when preceding a list of elements, modify the entire list of elements and do not modify the individual elements of the list.
- Example embodiments may be embodied in various different forms, and should not be construed as being limited only to the illustrated example embodiments. Rather, these embodiments are provided as examples so that this disclosure will be thorough and complete, and clear to those skilled in the art. Accordingly, known processes, elements, and techniques are not described with respect to some example embodiments. Unless otherwise noted, like reference numerals denote like elements throughout the attached drawings and written description, and thus, descriptions will not be repeated. In the drawings, the sizes and relative sizes of layers and regions may be exaggerated for clarity.
- It will be understood that, although the terms “first”, “second”, “third”, etc., may be used herein to describe various elements, components, regions, layers and/or sections, these elements, components, regions, layers and/or sections should not be limited by these terms. These terms are only used to distinguish one element, component, region, layer or section from another region, layer or section. Thus, a first element, component, region, layer or section discussed below could be termed a second element, component, region, layer or section without departing from the teachings of inventive concepts.
- Spatially relative terms, such as “beneath”, “below”, “lower”, “under”, “above”, “upper” and the like, may be used herein for ease of description to describe one element or feature's relationship to another element(s) or feature(s) as illustrated in the figures. It will be understood that the spatially relative terms are intended to encompass different orientations of the device in use or operation in addition to the orientation depicted in the figures. For example, if the device in the figures is turned over, elements described as “below” or “beneath” or “under” other elements or features would then be oriented “above” the other elements or features. Thus, the example terms “below” and “under” can encompass both an orientation of above and below. The device may be otherwise oriented (rotated 90 degrees or at other orientations) and the spatially relative descriptors used herein interpreted accordingly. In addition, it will also be understood that when a layer is referred to as being “between” two layers, it can be the only layer between the two layers, or one or more intervening layers may also be present.
- The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items. Also, the term “exemplary” is intended to refer to an example or illustration.
- It will be understood that when an element or layer is referred to as being “on”, “connected to”, “coupled to”, or “adjacent to” another element or layer, it can be directly on, connected, coupled, or adjacent to the other element or layer, or intervening elements or layers may be present. In contrast, when an element is referred to as being “directly on,” “directly connected to”, “directly coupled to”, or “immediately adjacent to” another element or layer, there are no intervening elements or layers present.
- Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and/or the present specification and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein. Moreover, example embodiments are described herein with reference to cross-sectional illustrations and/or plane illustrations that are idealized example illustrations. Accordingly, variations from the shapes of the illustrations as a result, for example, of manufacturing techniques and/or tolerances, are to be expected. Thus, example embodiments should not be construed as limited to the shapes of regions illustrated herein but are to include deviations in shapes that result, for example, from manufacturing. For example, an etching region illustrated as a rectangle will, typically, have rounded or curved features. Thus, the regions illustrated in the figures are schematic in nature and their shapes are not intended to illustrate the actual shape of a region of a device and are not intended to limit the scope of example embodiments.
- Although corresponding plan views and/or perspective views of some cross-sectional view(s) may not be shown, the cross-sectional view(s) of device structures illustrated herein provide support for a plurality of device structures that extend along two different directions as would be illustrated in a plan view, and/or in three different directions as would be illustrated in a perspective view. The two different directions may or may not be orthogonal to each other. The three different directions may include a third direction that may be orthogonal to the two different directions. The plurality of device structures may be integrated in a same electronic device. For example, when a device structure is illustrated in a cross-sectional view, an electronic device may include a plurality of the device structures, as would be illustrated by a plan view of the electronic device. The plurality of device structures may be arranged in an array and/or in a two-dimensional pattern.
- Example embodiments disclosed herein may include hardware configured to execute program code including program instructions, software components, software modules, data files, data structures, and/or the like. Examples of program code include both machine code produced by a compiler and higher level program code that is executed using an interpreter. The hardware devices may include one or more processors or processing circuitry. The one or more processors are computer processing devices configured to carry out the program code by performing arithmetical, logical, and input/output operations. Once the program code is loaded into the one or more processors, the one or more processors may be programmed to perform the program code, thereby transforming the one or more processors into special purpose processor(s) or processing circuitry.
- Alternatively, or in addition to the processors discussed above, the hardware devices may include one or more Central Processing Units (CPUs), digital signal processors (DSPs), application-specific-integrated-circuits (ASICs), SoCs, field programmable gate arrays (FPGAs), or the like. In at least some cases, the one or more CPUs, SoCs, DSPs, ASICs and FPGAs, may generally be referred to as processing circuits, processing circuitry, and/or microprocessors. The hardware devices may be configured as special purpose processing circuits, processing circuitry, and/or hardware devices, to perform functions illustrated in one or more of the flow charts or sequence diagrams discussed herein.
- The hardware devices may also include one or more storage devices. The one or more storage devices may be tangible or non-transitory computer-readable storage media, such as random access memory (RAM), read only memory (ROM), a permanent mass storage device (such as a disk drive), and/or any other like data storage mechanism capable of storing and recording data. The one or more storage devices may be configured to store computer readable instructions (such as program code) for one or more operating systems and/or computer readable instructions (such as program code) for implementing the example embodiments described herein. The computer readable instructions may also be loaded from a separate computer readable storage medium into the one or more storage devices and/or the one or more processors using a drive mechanism. Such separate computer readable storage medium may include a USB flash drive, memory stick, Blu-ray/DVD/CD-ROM drive, memory card, and/or other like computer readable storage medium (not shown). The computer readable instructions may be loaded into the one or more storage devices and/or the one or more processors from a remote data storage device via a network interface, rather than via a computer readable storage medium. Additionally, the computer readable instructions may be loaded into the one or more storage devices and/or the one or more processors from a remote computing system that is configured to transfer and/or distribute the program code over a network. The remote computing system may transfer and/or distribute the computer readable instructions via a wired interface, an air interface, and/or any other like tangible or intangible medium. The one or more processors, the one or more storage devices, and/or the computer readable instructions may be specially designed and constructed for the purposes of the example embodiments, or they may be known devices that are altered and/or modified for the purposes of the example embodiments.
- It will be apparent to those skilled in the art that various modifications and variations can be made to the example embodiments without departing from the spirit or scope of this disclosure. Thus, it is intended that the example embodiments cover the modifications and variations of the example embodiments provided they come within the scope of the appended claims and their equivalents.
- Referring first to
FIG. 1 , aservice providing system 1 according to an example embodiment will be described. -
FIG. 1 is a diagram of a system configuration of aservice providing system 1 according to an example embodiment. Theservice providing system 1 illustrated inFIG. 1 includes a plurality ofmobile terminals 10 and aserver device 20. Themobile terminals 10 and theserver device 20 are connected to each other wirelessly and/or with a cable via a wide-area network N (e.g., the Internet) so as to be able to communicate with each other over wired and/or wireless connection. - The
mobile terminals 10 are terminal devices, such as smartphones, mobile phones, notebook personal computers (PCs), wearable terminals, game consoles, or other electronic devices, used by users. AnIM application 11 is installed on themobile terminals 10. TheIM application 11 enables messages to be exchanged via the network N by an IM service between themobile terminals 10 used by users registered (e.g., pre-registered) at theserver device 20. The user can transmit and receive messages to and from other users by using theIM application 11 installed on themobile terminal 10. That is, for example, the user of themobile terminal 10 is able to exchange messages with other users registered in the same group, or with other users registered as friends of the user's. - As a result of registering a plurality of users in the same group, a user included in the group becomes able to transmit messages to the other users included in the same group. As a result of registering other users as a user's friends, the registered users are added to a list, such as a contact list (e.g., friend list), and the user may more easily transmit and receive messages to and from the users registered as friends.
- Hereinafter, a group including a plurality of users is referred to as a “group relationship” or “group association”. Likewise, a relationship (or association) between two users who are friends is referred to as a “friend relationship” or “friend association”.
- Each of the
mobile terminals 10 is capable of searching for the othermobile terminals 10 located within a threshold (or, alternatively, given, desired or predetermined) range (e.g., several centimeters to several tens of meters) from themobile terminal 10 via short-range wireless communication. The user of each of themobile terminals 10 may request that theserver device 20 register other users whom the user wishes to register from among users of the othermobile terminals 10 found through the search. That is, for example, each of themobile terminals 10 is capable of requesting theserver device 20 to register a group relationship or friend relationship with one or more users. - Hereinafter, the plurality of
mobile terminals 10 are also referred to as a “mobile terminal 10A”, a “mobile terminal 10B”, a “mobile terminal 10C”, and so on when they are distinguished from one another. In addition, at least this example embodiment is described with regard to a case where a user of themobile terminal 10A registers a group relationship with a plurality of other users at theserver device 20. - A
server program 21 is installed on theserver device 20. Theserver device 20 is an information processing device that executes the server program to manage group relationships (or associations) of users who utilize the IM service. - Note that the
service providing system 1 illustrated inFIG. 1 is merely an example and may have another configuration. For example, theserver device 20 may be constituted by a plurality of information processing devices. In addition, the service utilized by users by using themobile terminals 10 is not limited to the IM service, and may be a social networking service (SNS), a blog service, etc. That is, for example, at least this example embodiment is applicable to a service in which users who utilize the service are associated with one another to have a certain relationship (or association), such as a group relationship or a friend relationship, and data such as a message is transmitted and received between the associated users. - Referring next to
FIGS. 2A and 2B , an example embodiment of a hardware configuration of theservice providing system 1 will be described. -
FIGS. 2A and 2B are diagrams of an example embodiment of a hardware configuration of theservice providing system 1. - As illustrated in
FIG. 2A , themobile terminal 10 includes a central processing unit (CPU) 101, a read-only memory (ROM) 102, a random access memory (RAM) 103, and astorage device 104. Themobile terminal 10 also includes aninput device 105, adisplay device 106, acommunication device 107, and a short-rangewireless communication device 108. These hardware components are connected to one another via a bus, for example. - The
CPU 101 is a processing device that reads a program, computer readable instructions, and data, from a memory such as theROM 102 or thestorage device 104 to theRAM 103, and executes the program and/or computer readable instructions to perform one or more processes causing theCPU 101 to implement the overall control and functions of themobile terminal 10. TheROM 102 stores a program, computer readable instructions, and/or data such as a Basic Input/Output System (BIOS) executed when themobile terminal 10 is booted, operating system (OS) settings, and various settings. TheRAM 103 is a volatile semiconductor memory that temporarily holds a program, computer readable instructions, and/or data. Thestorage device 104 may be a nonvolatile memory that stores a program, computer readable instructions, and/or data. Examples of the program and computer readable instructions stored in thestorage device 104 include theIM application 11. - The input device 105 (e.g., a touchscreen or the like) is used by a user to input various operation signals. The display device 106 (e.g., a display or display unit) displays a processing result obtained by the
mobile terminal 10. Thecommunication device 107 is an interface for connecting themobile terminal 10 to the network N. In at least one example embodiment, thecommunication device 107 may include one or more interfaces, antennas, and corresponding circuitry, for transmitting/receiving data over a wired and/or wireless connection. Thecommunication device 107 may also be referred to as a transceiver. - The short-range wireless communication device 108 (e.g., a Bluetooth Low Energy (BLE) chip) is an interface for communicating with the other
mobile terminals 10 by short-range wireless communication. The short-rangewireless communication device 108 may include one or more interfaces, antennas, and corresponding circuitry, for transmitting/receiving data over a short-range wireless link. The short-rangewireless communication device 108 may also be referred to as a short-range wireless transceiver. - Note that short-range wireless communication performed between the
mobile terminals 10 is not limited to BLE. For example, infrared, ultrasound, or the like may be used. Short-range wireless communication may be performed with the othermobile terminals 10 over a radio wave by using, for example, Radio Frequency Identifier (RFID) technology, such as an IC tag or RFID tag. - As illustrated in
FIG. 2B , theserver device 20 includes aCPU 201, aROM 202, aRAM 203, astorage device 204, aninput device 205, adisplay device 206, and acommunication device 207. These hardware components are connected to one another via a bus, for example. - The
CPU 201 is a processing device that reads a program, computer readable instructions, and/or data, from a memory such as theROM 202 or thestorage device 204 to theRAM 203, and executes the program and/or computer readable instructions to perform one or more processes causing theCPU 101 to implement the overall control and functions of theserver device 20. TheROM 202 stores a program, computer readable instructions, and/or data such as BIOS executed when theserver device 20 is booted, OS settings, and various settings. TheRAM 203 is a volatile semiconductor memory that temporarily holds a program, computer readable instructions, and/or data. Thestorage device 204 may be a nonvolatile memory that stores a program, computer readable instructions, and/or data. Examples of the program and computer readable instructions stored in thestorage device 204 include theserver program 21. - The input device 205 (e.g., a touch screen, keyboard, mouse, etc.) is used by a user to input various operation signals. The display device 206 (e.g., a display or display unit) displays a processing result obtained by the
server device 20. Note that theinput device 205 and/or thedisplay device 206 may be connected and used when they are needed. Thecommunication device 207 is an interface for connecting theserver device 20 to the network N. Thecommunication device 207 may include one or more interfaces, antennas, and corresponding circuitry, for transmitting/receiving data over a wired and/or wireless connection. Thecommunication device 207 may also be referred to as a transceiver. - The
mobile terminals 10 and theserver device 20 according to at least this example embodiment include the hardware components described above and are capable of executing programs and/or computer readable instructions to implement various processes, which are discussed in more detail later. - Referring next to
FIG. 3 , an example embodiment of a functional configuration of theservice providing system 1 will be described.FIG. 3 is a diagram of an example embodiment of a functional configuration of theservice providing system 1. - As illustrated in
FIG. 3 , theIM application 11 of themobile terminal 10 includes aninput unit 12, asearch processing unit 13, adisplay unit 14, aregistration requesting unit 15, and a respondingunit 16. - The
input unit 12 may be implemented by theinput device 105, and execution of a program and/or computer readable instructions by theCPU 101. Theinput unit 12 accepts an operation input by a user. Examples of the operation input by a user include an operation for searching for the othermobile terminals 10 located within a threshold (or alternatively given, desired, or predetermined) range from the user'smobile terminal 10. - The
search processing unit 13 may be implemented by the short-rangewireless communication device 108 and execution of a program and/or computer readable instructions by theCPU 101. In response to an instruction from theinput unit 12, thesearch processing unit 13 transmits information (response request information) for searching for the othermobile terminals 10, within the threshold range from themobile terminal 10. - In addition, upon receipt of response request information from the other mobile terminal 10, the
search processing unit 13 transmits information (response information) containing, for example, a user ID and a user name identifying the user of themobile terminal 10 to theserver device 20 and/or to the other mobile terminal 10 that has transmitted the response request information. - The
display unit 14 may be implemented by thedisplay device 106 and execution of a program and/or computer readable instructions by theCPU 101. Thedisplay unit 14 causes thedisplay device 106 to display a processing result, in response to an instruction from another unit. For example, thedisplay unit 14 causes thedisplay device 106 to display a list (search result list) of the othermobile terminals 10 found within the threshold range from themobile terminal 10 by thesearch processing unit 13. In addition, for example, upon receipt of an agreement request requesting the user to join a group from theserver device 20, thedisplay unit 14 causes thedisplay device 106 to display an agree/decline screen that allows the user to agree or decline to join the group. - The
registration requesting unit 15 may be implemented by thecommunication device 107 and execution of a program and/or computer readable instructions by theCPU 101. Theregistration requesting unit 15 transmits, to theserver device 20, a group relationship registration request. The group relationship registration request contains information concerning users of the othermobile terminals 10 selected from among the users included in the search result list. That is, for example, theregistration requesting unit 15 transmits, to theserver device 20, a group relationship registration request for setting the user of themobile terminal 10 and a plurality of users selected by the user of the mobile terminal 10 from the search result list in a group. - The responding
unit 16 may be implemented by thecommunication device 107 and execution of a program and/or computer readable instructions by theCPU 101. Upon the user selecting “Agree” or “Decline” on the agree/decline screen displayed by thedisplay unit 14, the respondingunit 16 transmits a response based on the user's selection to theserver device 20. - As illustrated in
FIG. 3 , theserver program 21 of theserver device 20 includes aregistration processing unit 22 and anagreement requesting unit 23. In addition, theserver program 21 of theserver device 20 utilizes a group relationship database (DB) 24. - The
registration processing unit 22 may be implemented by thecommunication device 207 and execution of a program and/or computer readable instructions by theCPU 201. Upon receipt of a group relationship registration request from themobile terminal 10, theregistration processing unit 22 creates a group relationship table on the basis of the user IDs and the user names contained in the group relationship registration request and registers the group relationship table in thegroup relationship database 24. - In addition, upon receipt of a response indicating agreement (agreement response) from the
mobile terminal 10 in response to an agreement request that has been transmitted by theagreement requesting unit 23, theregistration processing unit 22 updates information concerning the user who has transmitted the agreement response from among the users included in the registered group relationship table. As a result, the user who has made the group relationship registration request and the users who have made the agreement response among the users included in the registered group relationship table become able to transmit and receive a message to and from each other. - As described above, a group relationship table including users assigned the user IDs contained in a group relationship registration request is created by the
registration processing unit 22 upon receipt of the group relationship registration request. However, at this point, the users included in the group relationship table are not able to transmit and receive a message to and from each other. With such a configuration, transmission of a message to a user who has not agreed to join the group from the other user included in the group relationship table is suppressed and/or prevented. - The
agreement requesting unit 23 may be implemented by thecommunication device 207 and execution of a program and/or computer readable instructions by theCPU 201. After the group relationship table has been registered by theregistration processing unit 22, theagreement requesting unit 23 transmits an agreement request to themobile terminals 10 of the users included in the group relationship table except for the user who has made the group relationship registration request. - The
group relationship database 24 may be implemented by thestorage device 204. Thegroup relationship database 24 manages, for each group ID, a group relationship constituted by a plurality of users. - Referring now to
FIG. 4 , an example embodiment of thegroup relationship database 24 will be described.FIG. 4 is a diagram illustrating an example embodiment of thegroup relationship database 24. - As illustrated in
FIG. 4 , thegroup relationship database 24 stores, for each group ID, a group relationship table in which a group constituted by a plurality of users is managed. The group ID is information that uniquely identifies a group relationship table. The group ID is issued when theregistration processing unit 22 receives a group relationship registration request, for example. Each group relationship table has data fields, such as fields for the user ID and the user name of each user constituting the group relationship and an agreement field indicating whether or not the user has agreed to join the group. This configuration allows the user of themobile terminal 10 to transmit and receive, by using theIM application 11, a message to and from users having an associated agreement field storing “AGREED”, which indicates that the user has agreed to join the group. The group relationship table is created by theregistration processing unit 22 with the agreement field for the user who has made the group relationship registration request initially set to “AGREED”, and is registered in thegroup relationship database 24. - Details of processes performed in the
service providing system 1 according to an example embodiment will be described in more detail below. - Referring first to
FIG. 5 , a process performed when the user (assigned the user ID “uid001” and the user name “satoh”) of themobile terminal 10A searches for the othermobile terminals 10 located within a threshold (or alternatively, given, desired or predetermined) range from themobile terminal 10A will be described.FIG. 5 is a flowchart illustrating a search process according to an example embodiment. - Referring to
FIG. 5 , at S501 themobile terminal 10A performs an operation to search for the othermobile terminals 10 located within the threshold range (e.g., several centimeters to several tens of meters) from themobile terminal 10A. Theinput unit 12 of themobile terminal 10A accepts the operation, and requests thesearch processing unit 13 to search for the othermobile terminals 10. Thesearch processing unit 13 of themobile terminal 10A transmits response request information within the given range from themobile terminal 10A for a given (or alternatively, desired or predetermined) period (e.g., one to several seconds). - The
search processing unit 13 of the other mobile terminal 10 that has received the response request information from themobile terminal 10A transmits response information to themobile terminal 10A or theserver device 20. The response information contains the user ID and the user name of the user of themobile terminal 10 that has transmitted the response information. Upon receipt of the response information from themobile terminals 10, theserver device 20 transmits a list of the user IDs and the user names contained in the received response information to themobile terminal 10A that has transmitted the response request information. In the case where theserver device 20 receives response information, the response information need not contain the user name. In such a case, theserver device 20 may obtain the user name corresponding to the user ID contained in the received response information from a given (or alternatively, desired or predetermined) storage area. - It is assumed hereinafter that the
mobile terminal 10A has received the user IDs and the user names of the users of themobile terminals mobile terminal 10A has received the user ID “uid002” and the user name “suzuki” of the user of themobile terminal 10B, the user ID “uid003” and the user name “tanaka” of the user of themobile terminal 10C, and the user ID “uid004” and the user name “yamada” of the user of themobile terminal 10D. - Still referring to
FIG. 5 , at S502 thesearch processing unit 13 of themobile terminal 10A determines whether or not the othermobile terminals 10 are located within the threshold range from themobile terminal 10A. More specifically, thesearch processing unit 13 of themobile terminal 10A determines whether or not the user ID and the user name of the user of the other mobile terminal 10 have been received. If thesearch processing unit 13 of themobile terminal 10A has received the user ID and the user name of the user of the other mobile terminal 10, then the process proceeds to S503. If thesearch processing unit 13 of themobile terminal 10A has not received any user ID and any user name of the user of the other mobile terminal 10, then the process proceeds to S504. - At S503, the
display unit 14 of themobile terminal 10A causes thedisplay device 106 to display, for example, the searchresult list screen 1000 illustrated inFIG. 6 on the basis of the received user IDs and user names of the users of the othermobile terminals 10. -
FIG. 6 is a conceptual diagram of an example searchresult list screen 1000. On the searchresult list screen 1000 illustrated inFIG. 6 , a list of the user IDs and the user names of the users of the othermobile terminals 10 that have been received by thesearch processing unit 13 of themobile terminal 10A from the othermobile terminals 10 is displayed. As described above, the user IDs and the user names of the users of the othermobile terminals 10 located within the given range from themobile terminal 10A are displayed as a list on the searchresult list screen 1000. - On the search
result list screen 1000 illustrated inFIG. 6 , acheckbox 1001 allows the user to select users who constitute a group relationship to be created. More specifically, the user of themobile terminal 10A selects, using a touch screen to select thecheckbox 1001, users whom the user wishes to select and presses a “Create Group”button 1002. Consequently, themobile terminal 10A requests theserver device 20 to register a group relationship for the user of themobile terminal 10A and the users selected with thecheckbox 1001. Note that thecheckbox 1001 is merely an example, and the user may select users who constitute a group relationship to be created, for example, by tapping user names displayed as a list. - At S504, the
display unit 14 of themobile terminal 10A causes thedisplay device 106 to display a message indicating that no othermobile terminals 10 are located within the threshold range from themobile terminal 10A, for example. In this way, the user of themobile terminal 10A can be informed that there are no other users sufficiently near the user. - As described above, the
mobile terminal 10 according to at least this example embodiment searches for the othermobile terminals 10 located nearby by using short-range wireless communication, such as BLE, and displays the search result as a list. The user of themobile terminal 10 can select users whom the user wishes to select from among users of the othermobile terminals 10 displayed in the list, and can register a group relationship including the user and the selected users, details of which will be described later. - For example purposes, it is assumed that the user of the
mobile terminal 10A has selected the user (assigned the user ID “uid002” and the user name “suzuki”) of themobile terminal 10B and the user (assigned the user ID “uid004” and the user name “yamada”) of the mobile terminal 10D on the searchresult list screen 1000 illustrated inFIG. 6 . - Referring to
FIG. 7 , an example embodiment of a process performed in response to the user of themobile terminal 10A pressing the “Create Group”button 1002 will be described. -
FIG. 7 is a sequence diagram illustrating a group relationship registration process according to an example embodiment. - Upon the “Create Group”
button 1002 being pressed on the searchresult list screen 1000 as described above, theregistration requesting unit 15 of themobile terminal 10A transmits a group relationship registration request to theserver device 20 at S701. The group relationship registration request contains the user ID and the user name of the user of themobile terminal 10A and the user IDs and the user names of the users selected with thecheckbox 1001 on the searchresult list screen 1000. More specifically, in at least one example embodiment, the group relationship registration request contains the user ID “uid001” and the user name “satoh”, the user ID “uid002” and the user name “suzuki”, and the user ID “uid004” and the user name “yamada”. - Upon receipt of the group relationship registration request, the
registration processing unit 22 of theserver device 20 creates a group relationship table on the basis of the group relationship registration request and registers the group relationship table in thegroup relationship database 24 at S702. - More specifically, the
registration processing unit 22 creates a group relationship table indicating a group relationship of a group including the user IDs and the user names contained in the received group relationship registration request, by generating and/or issuing a group ID that uniquely identifies the group relationship table. Theregistration processing unit 22 then registers the created group relationship table in thegroup relationship database 24. At this time, theregistration processing unit 22 sets the agreement field for the user of themobile terminal 10 that has transmitted the group relationship registration request (e.g., the user assigned the user ID “uid001”) to “AGREED” and sets the agreement field for the other users (e.g., the users assigned the user IDs “uid002” and “uid004”) to “PENDING”. It is assumed that the group relationship table registered at this time is assigned a group ID “G001”. - Still referring to
FIG. 7 , at S703 theregistration processing unit 22 of theserver device 20 transmits a notification (group relationship registration notification) indicating completion of registration of the group relationship to themobile terminal 10A that has transmitted the group relationship registration request. In this way, the user of themobile terminal 10A can be informed that a group including the users selected on the searchresult list screen 1000 has been created and registered. - At S704-1, the
agreement requesting unit 23 of theserver device 20 transmits, to themobile terminal 10B, an agreement request to request the user to join the group indicated by the registered group relationship table. - Similarly, at S704-2, the
agreement requesting unit 23 of theserver device 20 transmits an agreement request to themobile terminal 10D. As described above, theagreement requesting unit 23 transmits an agreement request to users other than the user who has transmitted the group relationship registration request among the users included in the registered group relationship table. The agreement request contains the group ID of the group relationship table registered at S702 and the user IDs and the user names included in the registered group relationship table. - Upon receipt of the agreement request from the
server device 20, at S705-1 thedisplay unit 14 of themobile terminal 10B causes thedisplay device 106 to display a group-joining agree/decline screen. An example group-joining agree/decline screen 2000 is illustrated inFIG. 8A . - Referring to
FIG. 8A , the group-joining agree/decline screen 2000 is a screen displayed on thedisplay device 106 of themobile terminal 10B so as to allow the user of the mobile terminal 10B to select whether to join the group indicated by the registered group relationship table. Note that information concerning the other members of the group indicated by the registered group relationship table is displayed on the group-joining agree/decline screen 2000. As shown inFIG. 8A , the group-joining agree/decline screen 2000 also includes an “Agree”button 2001 and a “Decline”button 2002. - Likewise, upon receipt of the agreement request from the
server device 20, at S705-2 thedisplay unit 14 of the mobile terminal 10D causes thedisplay device 106 to display a group-joining agree/decline screen. An example of this group-joining agree/decline screen is illustrated inFIG. 8B . - Referring to
FIG. 8B , the group-joining agree/decline screen 3000 is a screen displayed on thedisplay device 106 of themobile terminal 10D so as to allow the user of the mobile terminal 10D to select whether to join the group indicated by the registered group relationship table. Note that information concerning the other members of the group indicated by the registered group relationship table is displayed on the group-joining agree/decline screen 3000. As shown inFIG. 8B , the group-joining agree/decline screen 3000 also includes an “Agree”button 3001 and a “Decline”button 3002. - It is assumed in at least this example embodiment that the user of the
mobile terminal 10B presses the “Agree”button 2001 to agree to join the group indicated by the registered group relationship table on the group-joining agree/decline screen 2000. In contrast, it is assumed that the user of the mobile terminal 10D presses the “Decline”button 3002 to decline to join the group indicated by the registered group relationship table on the group-joining agree/decline screen 3000. - Upon the user pressing the “Agree”
button 2001 on the group-joining agree/decline screen 2000, at S706-1 the respondingunit 16 of themobile terminal 10B transmits, to theserver device 20, an agreement response indicating that the user has agreed to join the group indicated by the registered group relationship table. The agreement response contains the group ID of the group relationship table indicating the group relationship registered at S702. - Upon the user pressing the “Decline”
button 3002 on the group-joining agree/decline screen 3000, at S706-2 the respondingunit 16 of the mobile terminal 10D transmits, to theserver device 20, a decline response indicating that the user has declined to join the group indicated by the registered group relationship table. The decline response contains the group ID of the group relationship table indicating the group relationship registered at S702. - Upon receipt of the agreement response or the decline response from the
mobile terminal 10, theregistration processing unit 22 of theserver device 20 updates the group relationship table assigned the group ID contained in the agreement response or the decline response at S707. - More specifically, upon receipt of the agreement response from the
mobile terminal 10B, theregistration processing unit 22 updates the agreement field for the user (assigned the user ID “uid002” and the user name “suzuki”) of the mobile terminal 10B to “AGREED” in the group relationship table assigned the group ID “G001” contained in the agreement response. Upon receipt of the decline response from themobile terminal 10D, theregistration processing unit 22 deletes information concerning the user (e.g., assigned the user ID “uid004” and the user name “yamada”) of themobile terminal 10D from the group relationship table assigned the group ID “G001” contained in the decline response. As a result, a message can be transmitted to, and received from, themobile terminal 10 of the user who has transmitted the agreement response, but themobile terminal 10 of the user who has transmitted the decline response can be suppressed and/or prevented from joining the group. - The
registration processing unit 22 deletes information concerning the user of themobile terminal 10 that has transmitted a decline response from the group relationship table assigned the group ID contained in the decline response upon receipt of the decline response; however, the configuration is not limited to this example, and the agreement field may be updated to “DECLINED”, for example. - As described above, the
server device 20 according to at least one example embodiment can register a group relationship constituted by a plurality of users in accordance with a group relationship registration request transmitted from themobile terminal 10. Consequently, the user of themobile terminal 10 according to at least this example embodiment can transmit and receive a message to and from users included in the registered group relationship. - According to at least this example embodiment, the case of registering a group relationship for a group constituted by a plurality of users has been described; however, the configuration is not limited to this example, and a friend relationship between a user and users selected by the user on the search
result list screen 1000 may be registered, for example. - In addition, in the above-described example embodiment, the
server device 20 transmits an agreement request to themobile terminals 10 of the users selected on the search result list screen 1000 (e.g., S704-1 and S704-2); however, transmission of an agreement request may be omitted. For example, in the case where a setting for omitting agreement is set in themobile terminal 10 of the user selected on the searchresult list screen 1000, theserver device 20 may execute a program and/or computer readable instructions to be configured not to transmit an agreement request to themobile terminal 10 having such a setting. Alternatively, theserver device 20 may execute a program and/or computer readable instructions to be configured not to transmit an agreement request by respectively setting the period for which and the range within which themobile terminal 10 performs a search at S501 inFIG. 5 to be relatively short and/or narrow. - Another example embodiment of the
service providing system 1 will now be described. In theservice providing system 1 according to at least this example embodiment, friend relationships between a user of themobile terminal 10 and users of the othermobile terminals 10 among users of the othermobile terminals 10 located within a threshold (or alternatively, given, desired, or predetermined) range from themobile terminal 10 is registered on the basis of a social graph. For the sake of brevity, only differences between the above-described example embodiment and this example embodiment will be described. Functional configurations that are the same or substantially the same as that of the above-described example embodiment are denoted by reference numerals similar to, or the same as, those used in the description of the above-discussed example embodiment, and a detailed description thereof is omitted. - Referring first to
FIG. 9 , a functional configuration of theservice providing system 1 according to at least this example embodiment will be described. -
FIG. 9 is a diagram of an example of a functional configuration of theservice providing system 1 according to another example embodiment. - As illustrated in
FIG. 9 , an IM application 11A of themobile terminal 10 includes aregistration requesting unit 15A. Theregistration requesting unit 15A transmits, to theserver device 20, a friend relationship registration request requesting registration of friend relationships between a user of themobile terminal 10 and users of the othermobile terminals 10 included in the search result list. - A
server program 21A of theserver device 20 includes aregistration processing unit 22A, agraph creating unit 25, and a whether-to-register determining unit 26. In addition, theserver program 21A of theserver device 20 utilizes a friend relationship database (DB) 27. - The
registration processing unit 22A updates a friend relationship registered in thefriend relationship database 27 on the basis of the user IDs and the user names contained in the friend relationship registration request received from themobile terminal 10 and the determination result obtained by the whether-to-register determining unit 26. - The
graph creating unit 25 may be implemented by execution of a program and/or computer readable instructions by theCPU 201. Upon receipt of a friend relationship registration request, thegraph creating unit 25 creates a social graph, which sets a user assigned a specified user ID at the center and has a distance N (N is an integer of 2 or greater) from the center, on the basis of thefriend relationship database 27. A social graph is a graph in which each user is denoted by a node and a friend relationship between users is denoted by a link. A link is also referred to as an “edge”. In addition, the term “distance” refers to the minimum number of links to reach a target node from the central node. - The whether-to-
register determining unit 26 may be implemented by executing computer readable instructions by theCPU 201. The whether-to-register determining unit 26 determines the user ID for which a friend relationship is to be updated to “FRIEND” from among the user IDs contained in the received friend relationship registration request on the basis of the social graph created by thegraph creating unit 25. More specifically, if a social graph having a distance of N or less from the user name “satoh” set at the center includes the user ID corresponding to the user name “suzuki”, the whether-to-register determining unit 26 determines that a friend relationship between the user names “satoh” and “suzuki” is to be updated to “FRIEND”. If the social graph does not include the user ID corresponding to the user name “suzuki”, the whether-to-register determining unit 26 determines that the user names “satoh” and “suzuki” are not to be associated as “FRIEND”. For example, when the distance N is set to 2 or 3, such a setting indicates that users who have a “mutual friend” or a “friend of a mutual friend” are set as friends. - The
friend relationship database 27 may be implemented by thestorage device 204. Thefriend relationship database 27 stores, for each user ID, a friend relationship table in which users who are registered as friends of the user's are managed. Referring now toFIG. 10 , an example embodiment of thefriend relationship database 27 will be described. -
FIG. 10 is a diagram illustrating an example embodiment of thefriend relationship database 27. - As illustrated in
FIG. 10 , thefriend relationship database 27 has, for each user ID, data fields such as fields for the user ID and the user name of each user who is set as a friend of (has a friend relationship with) the user assigned the user ID. The example illustrated inFIG. 10 indicates that the user assigned the user ID “uid001” (user name “satoh”) is a friend of the user assigned the user ID “uid005” (user name “sasaki”) and the user assigned the user ID “uid007” (user ID “nakamura”), for example. As described above, thefriend relationship database 27 stores, for each user, a friend relationship table in which users registered as friends (e.g., users having a friend relationship) are managed. - Details of processes performed in the
service providing system 1 according to at least this example embodiment will now be described. - Referring to
FIG. 11 , a process performed when the user (assigned the user ID “uid001” and the user name “satoh”) of themobile terminal 10A searches for the othermobile terminals 10 located within a threshold (or alternatively, given, desired, or predetermined) range from themobile terminal 10A will be described, as in the other example embodiment discussed above. -
FIG. 11 is a flowchart illustrating a search process according to another example embodiment. - Referring to
FIG. 11 , at S1101 the user of themobile terminal 10A performs an operation to search for the othermobile terminals 10 located within the threshold range (e.g., several centimeters to several tens of meters) from themobile terminal 10A. Theinput unit 12 of themobile terminal 10A accepts the operation and requests thesearch processing unit 13 to search for the othermobile terminals 10. Thesearch processing unit 13 of themobile terminal 10A transmits response request information within the threshold range from themobile terminal 10A for a threshold (or alternatively, given, desired, or predetermined) period (e.g., one to several seconds). - The
search processing unit 13 of the other mobile terminal 10 that has received the response request information from themobile terminal 10A transmits response information for the received response request information to themobile terminal 10A or theserver device 20. The response information transmitted at this time contains the user ID and the user name of the user of themobile terminal 10 that has transmitted the response information. - Upon receipt of the response information from the
mobile terminals 10, theserver device 20 transmits a list of the user IDs and the user names contained in the received response information to themobile terminal 10A that has transmitted the response request information. In the case where theserver device 20 receives response information, the response information need not contain the user name. In such a case, theserver device 20 may obtain the user name corresponding to the user ID contained in the received response information from a given (or alternatively desired or predetermined) storage area. - It is assumed hereinafter that the
mobile terminal 10A has received the user IDs and the user names of the users of themobile terminals - At S1102, the
search processing unit 13 of themobile terminal 10A determines whether or not the othermobile terminals 10 are located within the threshold range from themobile terminal 10A. More specifically, thesearch processing unit 13 of themobile terminal 10A determines whether the user ID and the user name of the user of the other mobile terminal 10 have been received. If thesearch processing unit 13 of themobile terminal 10A has not received any user ID and any user name of the user of the other mobile terminal 10, then the process proceeds to S1103. - At S1103, the
display unit 14 of themobile terminal 10A causes thedisplay device 106 to display a message indicating that no othermobile terminals 10 are located within the threshold range from themobile terminal 10A. In this way, the user of themobile terminal 10A can be informed that there are no other users near the user. - As described above, the
mobile terminal 10 according to at least this example embodiment searches for the othermobile terminals 10 located nearby by using short-range wireless communication, such as BLE. - Returning to S1102, if the
search processing unit 13 of themobile terminal 10A receives user IDs and user names of users of the other mobile terminal 10, then a friend relationship registration process is performed. An example embodiment of a friend relationship registration process will be discussed in more detail below. - Unlike the example embodiment discussed above, the
mobile terminal 10 according to this example embodiment does not display the search result list because a friend relationship is registered for users having a “mutual friend” or a “friend of a mutual friend” as a result of appropriately setting the distance N as described later in detail. Note that, in at least this example embodiment, the search result list may be displayed as in the above-described example embodiment so as to allow the user to select users for whom the user wishes to register a friend relationship. - Referring next to
FIG. 12 , a process performed after the above-described search process will be described. -
FIG. 12 is a sequence diagram illustrating a friend relationship registration process according to an example embodiment. - Referring to
FIG. 12 , at S1201 theregistration requesting unit 15A of themobile terminal 10A transmits a friend relationship registration request to theserver device 20. The friend relationship registration request contains the user ID and the user name of the user of themobile terminal 10A and the user IDs and the user names of the users of the othermobile terminals 10 that have been received at S1101 ofFIG. 11 . More specifically, in one example, the friend relationship registration request contains the user ID “uid001” and the user name “satoh”, the user ID “uid002” and the user ID “suzuki”, the user ID “uid003” and the user name “tanaka”, and the user ID “uid004” and the user name “yamada”. - Upon receipt of the friend relationship registration request, the
graph creating unit 25 at theserver device 20 creates (or generates), for each of the user IDs contained in the friend relationship registration request, a social graph of a threshold (or alternatively, given, desired, or pre-set) distance of less than or equal to N at S1202. - A social graph that sets the user ID “uid001” at the center and has a distance N of less than or equal to 3 from the center is illustrated in
FIG. 13 . -
FIG. 13 is a diagram illustrating an example embodiment of a social graph. The social graph illustrated inFIG. 13 is constituted by nodes of the user IDs for which the number of links from the user ID “uid001” located at the center is less than or equal to 3 (the distance N is less than or equal to 3). Thegraph creating unit 25 creates (or generates), for each of the user IDs contained in the friend relationship registration request, a social graph on the basis of the given distance N. More specifically, in at least this example embodiment, thegraph creating unit 25 creates social graphs for the user IDs “uid001”, “uid002”, “uid003”, and “uid004” on the basis of the given distance N. Note that the distance N may be set to an identical value for all users, or to different values for different users. In addition, the user of themobile terminal 10 may be allowed to set the distance N to a desired value. - Returning to
FIG. 12 , at S1203 the whether-to-register determining unit 26 of theserver device 20 determines, for each of the user IDs contained in the friend relationship registration request, whether to register friend relationships for the user ID and the other user IDs contained in the friend relationship registration request. - More specifically, the whether-to-
register determining unit 26 determines whether the social graph created for the user ID “uid001” in step S1202 includes each of the other user IDs “uid002”, “uid003”, and “uid004” contained in the friend relationship registration request. The whether-to-register determining unit 26 determines that a friend relationship is to be registered for each of the other user IDs included in the social graph for the user ID “uid001”. For example, in the example embodiment illustrated inFIG. 13 , the social graph for the user ID “uid001” includes the user IDs “uid002” and “uid004”. Accordingly, the whether-to-register determining unit 26 determines that the user IDs “uid001” and “uid002” and the user IDs “uid001” and “uid004” are to be registered to have friend relationships. In contrast, the whether-to-register determining unit 26 determines that the user IDs “uid001” and “uid003” are not to be registered to have a friend relationship. - Likewise, the whether-to-
register determining unit 26 determines whether the social graph for the user ID “uid002” includes each of the user IDs “uid003” and “uid004”. Also, the whether-to-register determining unit 26 determines the social graph for the user ID “uid003” includes the user ID “uid004”. - As described above, the whether-to-
register determining unit 26 determines whether a social graph for each of the users whose user IDs are contained in a friend relationship registration request includes each of the other users whose user IDs are also contained in the friend relationship registration request. In other words, for example, the whether-to-register determining unit 26 determines whether a distance between a user whose user ID is contained in a friend relationship registration request and each of the other users whose user IDs are also contained in the friend relationship registration request is less than or equal to the given value N. The whether-to-register determining unit 26 then determines that users having a distance of less than or equal to N are to be registered to have a friend relationship. - Still referring to
FIG. 12 , at S1204 theregistration processing unit 22A of theserver device 20 updates the friend relationship tables for the users ID for which it has been determined at S1203 that a friend relationship is to be registered, in thefriend relationship database 27. - For example, in the case where it is determined at S1203 that the user IDs “uid001” and “uid002” are to be registered to have a friend relationship, the
registration processing unit 22A adds a record of the user ID “uid002” to the friend relationship table for the user ID “uid001” in thefriend relationship database 27. Likewise, theregistration processing unit 22 adds a record of the user ID “uid001” to the friend relationship table for the user ID “uid002” in thefriend relationship database 27. As a result, the user assigned the user ID “uid001” and the user assigned the user ID “uid002” have a friend relationship and become able to transmit and receive a message to and from each other. - If the user IDs for which it has been determined at S1203 that a friend relationship is to be registered have been set as friends (if a friend relationship has been registered), then the
registration processing unit 22 may not perform any processing at S1204. - At S1205-1, the
registration processing unit 22A of theserver device 20 transmits a friend relationship registration result obtained at S1204 to themobile terminals 10B to 10D. - Likewise, at S1205-2, the
registration processing unit 22A of theserver device 20 transmits a friend relationship registration result obtained at S1204 to themobile terminal 10A. As described above, theregistration processing unit 22A transmits a friend relationship registration result to themobile terminals 10 associated with the user IDs contained in a friend relationship registration request. The friend relationship registration result transmitted by theregistration processing unit 22A contains the user IDs and the user names of users who have been set as friends with the user of themobile terminal 10 serving as the transmission destination (e.g., for whom a friend relationship has been registered). In this way, the user of themobile terminal 10 can be informed of the other users set as friends of the user's. - As described above, upon receipt of a friend relationship registration request containing a plurality of user IDs from the
mobile terminal 10, theserver device 20 according to at least this example embodiment is configured to execute a program and/or computer readable instructions to create social graphs for the respective user IDs on the basis of the given distance N. Then, theserver device 20 according to at least this example embodiment is configured to execute a program and/or computer readable instructions to register a plurality of users to mutually have friend relationships on the basis of the created social graphs. Such a configuration makes it possible to register friend relationships between a plurality of users at one time (e.g., concurrently and/or simultaneously) in theservice providing system 1 according to at least this example embodiment. - In at least this example embodiment, it is determined whether to register friend relationships for the user IDs contained in a friend relationship registration request; however, the configuration is not limited to this example. For example, it may be determined whether to register the user of the
mobile terminal 10A and each of the users of themobile terminals 10B to 10D to have a friend relationship, for example (in this case, the users of themobile terminals - In at least this example embodiment, the case of registering a plurality of users to have friend relationships has been described; however, the configuration is not limited to this example, and a group relationship including a plurality of users may be registered on the basis of social graphs.
- More specifically, for example, at S1201 in
FIG. 12 themobile terminal 10 may transmit, to theserver device 20, a group relationship registration request containing the user IDs and the user names of a plurality of users constituting a group. In this case, theserver device 20 may register a group relationship including the user of themobile terminal 10 that has transmitted the group relationship registration request and users included in this user's social graph having a distance of less than or equal to N, from among the plurality of users contained in the group relationship registration request. - Note that example embodiments are not limited to those described herein, and various modifications and alterations can be made without departing from the scope of the claims.
Claims (1)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/750,484 US10841752B2 (en) | 2015-03-31 | 2020-01-23 | Terminal devices, information processing methods, and computer readable storage mediums |
US17/069,298 US11405756B2 (en) | 2015-03-31 | 2020-10-13 | Terminal devices, information processing methods, and computer readable storage mediums |
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2015-074149 | 2015-03-31 | ||
JP2015074149A JP6533085B2 (en) | 2015-03-31 | 2015-03-31 | Terminal, information processing method, and program |
US14/837,748 US20160295353A1 (en) | 2015-03-31 | 2015-08-27 | Terminal devices, information processing methods, and computer readable storage mediums |
US16/148,149 US10582344B2 (en) | 2015-03-31 | 2018-10-01 | Terminal devices, information processing methods, and computer readable storage mediums |
US16/750,484 US10841752B2 (en) | 2015-03-31 | 2020-01-23 | Terminal devices, information processing methods, and computer readable storage mediums |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/148,149 Continuation US10582344B2 (en) | 2015-03-31 | 2018-10-01 | Terminal devices, information processing methods, and computer readable storage mediums |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/069,298 Continuation US11405756B2 (en) | 2015-03-31 | 2020-10-13 | Terminal devices, information processing methods, and computer readable storage mediums |
Publications (2)
Publication Number | Publication Date |
---|---|
US20200162857A1 true US20200162857A1 (en) | 2020-05-21 |
US10841752B2 US10841752B2 (en) | 2020-11-17 |
Family
ID=57017728
Family Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/837,748 Abandoned US20160295353A1 (en) | 2015-03-31 | 2015-08-27 | Terminal devices, information processing methods, and computer readable storage mediums |
US16/148,149 Active US10582344B2 (en) | 2015-03-31 | 2018-10-01 | Terminal devices, information processing methods, and computer readable storage mediums |
US16/555,493 Active US10555135B2 (en) | 2015-03-31 | 2019-08-29 | Terminal devices, information processing methods, and computer readable storage mediums |
US16/750,484 Active US10841752B2 (en) | 2015-03-31 | 2020-01-23 | Terminal devices, information processing methods, and computer readable storage mediums |
US17/069,298 Active US11405756B2 (en) | 2015-03-31 | 2020-10-13 | Terminal devices, information processing methods, and computer readable storage mediums |
Family Applications Before (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/837,748 Abandoned US20160295353A1 (en) | 2015-03-31 | 2015-08-27 | Terminal devices, information processing methods, and computer readable storage mediums |
US16/148,149 Active US10582344B2 (en) | 2015-03-31 | 2018-10-01 | Terminal devices, information processing methods, and computer readable storage mediums |
US16/555,493 Active US10555135B2 (en) | 2015-03-31 | 2019-08-29 | Terminal devices, information processing methods, and computer readable storage mediums |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/069,298 Active US11405756B2 (en) | 2015-03-31 | 2020-10-13 | Terminal devices, information processing methods, and computer readable storage mediums |
Country Status (2)
Country | Link |
---|---|
US (5) | US20160295353A1 (en) |
JP (1) | JP6533085B2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2022015050A1 (en) * | 2020-07-14 | 2022-01-20 | Samsung Electronics Co., Ltd. | Methods and systems for updating group information |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP6533085B2 (en) | 2015-03-31 | 2019-06-19 | Line株式会社 | Terminal, information processing method, and program |
JP2021192469A (en) * | 2018-09-06 | 2021-12-16 | ソニーグループ株式会社 | Wireless communication device and wireless communication method |
JP6738518B1 (en) * | 2019-07-30 | 2020-08-12 | O−Box合同会社 | Management server, matching system, and matching method |
CN111614759B (en) * | 2020-05-20 | 2023-02-17 | 抖音视界有限公司 | Resource sharing method and device, electronic equipment and computer readable medium |
JP7413933B2 (en) | 2020-06-09 | 2024-01-16 | トヨタ自動車株式会社 | Wallet server, wallet system, and program |
US20230237605A1 (en) * | 2020-06-24 | 2023-07-27 | Nec Corporation | Trustability analyzing system, trustability analyzing method, and non-transitory computer-readable medium |
CN113765682A (en) * | 2021-09-13 | 2021-12-07 | 三星电子(中国)研发中心 | Method and system for performing group functions |
US11630551B1 (en) * | 2021-10-28 | 2023-04-18 | Dallen Yu Chao | Smart keychain or accessory devices, systems, and methods |
US20230136741A1 (en) * | 2021-10-28 | 2023-05-04 | Apple Inc. | User equipment association |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6957229B1 (en) * | 2000-01-10 | 2005-10-18 | Matthew Graham Dyor | System and method for managing personal information |
US20090292799A1 (en) * | 2008-05-23 | 2009-11-26 | Research In Motion Limited | Remote administration of mobile wireless devices |
US20100016006A1 (en) * | 2006-04-13 | 2010-01-21 | Kyocera Corporation | Group Communication Method and Communication Terminal |
US20120020238A1 (en) * | 2009-05-19 | 2012-01-26 | Junji Suetsugu | Network system, communication terminal, communication method, and communication program |
US20170150330A1 (en) * | 2014-04-13 | 2017-05-25 | Lg Electronics Inc. | Method for managing d2d terminal group in wireless communication system and apparatus for same |
US20190387367A1 (en) * | 2015-03-31 | 2019-12-19 | Line Corporation | Terminal devices, information processing methods, and computer readable storage mediums |
Family Cites Families (127)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001520425A (en) * | 1997-10-09 | 2001-10-30 | ウオーカー ディジタル、エルエルシー | Sales point system and group reward management method |
JP2001333451A (en) | 2000-05-22 | 2001-11-30 | Sharp Corp | Method for inter-terminal communication service and inter-terminal communication service system |
JP2002247052A (en) | 2001-02-21 | 2002-08-30 | Casio Comput Co Ltd | Communication network system, constructing method of communication network and program |
WO2003034660A1 (en) * | 2001-10-16 | 2003-04-24 | Sony Corporation | Communication system and method, information processing apparatus and method, and information processing terminal and method |
JP2003150529A (en) | 2001-11-19 | 2003-05-23 | Hitachi Ltd | Information exchange method, information exchange terminal unit, information exchange server device and program |
AU2002235742A1 (en) * | 2001-11-28 | 2003-06-10 | Nokia Corporation | Instructional method and system using wireless communication |
US8611919B2 (en) * | 2002-05-23 | 2013-12-17 | Wounder Gmbh., Llc | System, method, and computer program product for providing location based services and mobile e-commerce |
FI20021259A0 (en) * | 2002-06-27 | 2002-06-27 | Nokia Corp | A mechanism for forming a communication group |
US7917748B2 (en) | 2002-10-25 | 2011-03-29 | Pine Valley Investments, Inc. | Secure group secret distribution |
US20050023940A1 (en) * | 2003-07-28 | 2005-02-03 | Van Beusekom Thomas J. | Sound minimizing apparatus |
US7647024B2 (en) * | 2005-10-03 | 2010-01-12 | Sellerbid, Inc. | Method and system for improving client server transmission over fading channel with wireless location and authentication technology via electromagnetic radiation |
KR100864296B1 (en) | 2004-08-16 | 2008-10-23 | 콸콤 인코포레이티드 | Methods and apparatus for managing group membership for group communications |
FI20050092A0 (en) | 2004-09-08 | 2005-01-28 | Nokia Corp | Group details for group services |
FI20041169A0 (en) | 2004-09-08 | 2004-09-08 | Nokia Corp | Group Services Group Information |
US7266383B2 (en) * | 2005-02-14 | 2007-09-04 | Scenera Technologies, Llc | Group interaction modes for mobile devices |
JP4983005B2 (en) * | 2005-04-12 | 2012-07-25 | 富士通株式会社 | Electronic device, priority connection device, priority connection method, and priority connection program |
JP4632439B2 (en) * | 2005-08-05 | 2011-02-16 | 株式会社スクウェア・エニックス | Communication control program and computer terminal |
US7702341B2 (en) * | 2005-10-03 | 2010-04-20 | Yahoo! Inc. | Shortcut for establishing a communication channel with a remote device over a network |
CN100464537C (en) * | 2005-12-30 | 2009-02-25 | 华为技术有限公司 | Method and system for sharing presented information |
US7780909B2 (en) * | 2006-03-22 | 2010-08-24 | Zimek Technologies Ip, Llc | Ultrasonic sanitation and disinfecting methods |
US8989778B2 (en) * | 2006-06-01 | 2015-03-24 | Green Dot Corporation | Secure and private location sharing for location-aware mobile communication devices |
EP1921577A1 (en) * | 2006-11-10 | 2008-05-14 | Yamaha Corporation | Social networking system |
US8024328B2 (en) * | 2006-12-18 | 2011-09-20 | Microsoft Corporation | Searching with metadata comprising degree of separation, chat room participation, and geography |
WO2008126259A1 (en) | 2007-03-30 | 2008-10-23 | Fujitsu Limited | Communication system, server device, communication terminal device, and computer program |
US9037632B2 (en) * | 2007-06-01 | 2015-05-19 | Napo Enterprises, Llc | System and method of generating a media item recommendation message with recommender presence information |
US9003488B2 (en) * | 2007-06-06 | 2015-04-07 | Datavalet Technologies | System and method for remote device recognition at public hotspots |
JP2009025747A (en) * | 2007-07-23 | 2009-02-05 | Sharp Corp | Toner, two-component developer, and image forming device using it |
KR20090021796A (en) * | 2007-08-28 | 2009-03-04 | 삼성전자주식회사 | Terminal and method for controlling device thereof |
JP5222573B2 (en) | 2008-01-29 | 2013-06-26 | 株式会社日立製作所 | Server computer and network processing method |
JP5109905B2 (en) * | 2008-09-29 | 2012-12-26 | 富士通モバイルコミュニケーションズ株式会社 | Communication device |
KR20100039622A (en) * | 2008-10-08 | 2010-04-16 | 삼성전자주식회사 | Apparatus and method for providing digital broadcasting service information in portable communication system |
US20100088367A1 (en) * | 2008-10-08 | 2010-04-08 | Research In Motion Limited | Mobile wireless communications device and system providing dynamic management of carrier applications and related methods |
US20100164685A1 (en) * | 2008-12-31 | 2010-07-01 | Trevor Pering | Method and apparatus for establishing device connections |
JP2010193935A (en) * | 2009-02-23 | 2010-09-09 | Konami Digital Entertainment Co Ltd | Terminal device, communication system, terminal method and program |
WO2010121205A1 (en) * | 2009-04-16 | 2010-10-21 | Nearverse, Inc. | Method and apapratus for distributed communication using short range and wide range communication links |
US9307184B2 (en) | 2009-07-31 | 2016-04-05 | Echostar Technologies L.L.C. | Multi-user recording allocation |
CN105282866B (en) * | 2010-02-26 | 2019-07-16 | Lg电子株式会社 | Electronic equipment and its operating method |
JP2011197776A (en) * | 2010-03-17 | 2011-10-06 | Sony Corp | Information processor, information processing method and program |
KR101877733B1 (en) | 2010-06-01 | 2018-08-09 | 삼성전자주식회사 | Method and system of securing group communication in a machine-to-machine communication environment |
US8725672B2 (en) * | 2010-06-11 | 2014-05-13 | Avira B.V. | Method for detecting suspicious individuals in a friend list |
KR101199401B1 (en) * | 2010-06-23 | 2012-11-09 | 엘지전자 주식회사 | METHOD FOR delivering and Storing Message based on CPS service and server thereof |
US8397274B2 (en) * | 2010-07-13 | 2013-03-12 | Research In Motion Limited | Method for authenticating device capabilities to a verified third party |
TWI407806B (en) * | 2010-07-20 | 2013-09-01 | Gemtek Technology Co Ltd | Wireless network system and wireless access point device and wireless terminal device thereof |
KR101407942B1 (en) * | 2010-08-17 | 2014-06-17 | 한국전자통신연구원 | Method for pairing of device using milimeter wave band and apparatus for performing the same |
KR101761613B1 (en) * | 2010-10-04 | 2017-07-26 | 엘지전자 주식회사 | Mobile terminal and Method for transmitting image thereof |
KR20120052599A (en) * | 2010-11-16 | 2012-05-24 | 삼성전자주식회사 | Fast device searching method based on a short range communication module and portable device supporting the same |
JPWO2012111251A1 (en) | 2011-02-14 | 2014-07-03 | パナソニック株式会社 | Group generator |
JP6302614B2 (en) | 2011-02-25 | 2018-03-28 | 任天堂株式会社 | Communication system, information processing apparatus, program, and information processing method |
US9369663B2 (en) * | 2011-03-10 | 2016-06-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Remote-controlled recording |
US9495077B2 (en) | 2011-04-26 | 2016-11-15 | Sharp Kabushiki Kaisha | Display device, display method, and non-transitory computer-readable recording medium |
AU2011202182B1 (en) * | 2011-05-11 | 2011-10-13 | Frequency Ip Holdings, Llc | Creation and presentation of selective digital content feeds |
EP2724309A4 (en) * | 2011-06-24 | 2015-02-25 | Monster Worldwide Inc | Social match platform apparatuses, methods and systems |
US8855562B2 (en) * | 2011-06-29 | 2014-10-07 | Infosys Limited | Method and system for enabling discovery of services and automated exchange of data between bluetooth devices |
KR101314424B1 (en) * | 2011-08-24 | 2013-11-13 | 주식회사 팬택 | Terminal, ims server and method for transmitting/receiving presence information |
KR101562081B1 (en) | 2011-08-31 | 2015-10-21 | 라인 가부시키가이샤 | Social network service providing system, user terminal and relationship setting method for setting relationship between users of mobile terminal |
US9800688B2 (en) * | 2011-09-12 | 2017-10-24 | Microsoft Technology Licensing, Llc | Platform-enabled proximity service |
JP5873278B2 (en) * | 2011-09-26 | 2016-03-01 | 任天堂株式会社 | Information processing apparatus, server apparatus, data communication system, data communication method, and data communication program |
US9451383B2 (en) * | 2011-10-21 | 2016-09-20 | Nokia Technologies Oy | Method and apparatus for maintaining one or more communication sessions |
US9814085B2 (en) * | 2011-10-28 | 2017-11-07 | Qualcomm, Incorporated | Systems and methods for fast initial network link setup |
JP5825118B2 (en) * | 2012-01-25 | 2015-12-02 | 富士通株式会社 | Release range determination method, release range determination apparatus and program |
JP5894819B2 (en) | 2012-02-02 | 2016-03-30 | 株式会社コナミデジタルエンタテインメント | Message exchange system, control method, and program |
US9544075B2 (en) * | 2012-02-22 | 2017-01-10 | Qualcomm Incorporated | Platform for wireless identity transmitter and system using short range wireless broadcast |
JP2013214808A (en) * | 2012-03-30 | 2013-10-17 | Brother Ind Ltd | Image processing device and information processing terminal program |
KR101886058B1 (en) * | 2012-04-08 | 2018-08-07 | 삼성전자주식회사 | User terminal device and information providing method using the same |
KR101883703B1 (en) * | 2012-04-16 | 2018-07-31 | 삼성전자 주식회사 | Method and system for providing service for searching friends |
EP3897016A3 (en) * | 2012-04-27 | 2021-11-24 | Interdigital Patent Holdings, Inc. | Method and apparatus for provisioning of d2d policies for a wireless transmit receive unit (wtru) |
US9305196B2 (en) * | 2012-05-22 | 2016-04-05 | Trimble Navigation Limited | Entity tracking |
US20140032304A1 (en) * | 2012-07-27 | 2014-01-30 | Google Inc. | Determining a correlation between presentation of a content item and a transaction by a user at a point of sale terminal |
WO2014025217A1 (en) * | 2012-08-08 | 2014-02-13 | Samsung Electronics Co., Ltd. | Apparatus and method of connecting service according to user intention |
US9462066B2 (en) * | 2012-08-21 | 2016-10-04 | Facebook, Inc. | Social action by quick response (QR) code |
WO2014031713A1 (en) * | 2012-08-21 | 2014-02-27 | Interdigital Patent Holdings, Inc. | Enhanced higher layer discovery methods for proximity services |
CN103907379B (en) * | 2012-09-07 | 2017-06-30 | 松下知识产权经营株式会社 | The control method of communication terminal, communication system and communication terminal |
US9820262B2 (en) * | 2012-09-20 | 2017-11-14 | Panasonic Intellectual Property Management Co., Ltd. | Control device, communication system, and method for registering terminal devices and scanning for other control devices |
EP2887753B1 (en) * | 2012-09-24 | 2020-04-22 | Sony Interactive Entertainment Inc. | Communication device and communication method |
JP2014082756A (en) * | 2012-09-25 | 2014-05-08 | Toshiba Corp | Wireless communication apparatus and method |
KR102022042B1 (en) * | 2012-09-28 | 2019-09-18 | 삼성전자주식회사 | Data transfer method and system thereof |
KR101947652B1 (en) * | 2012-09-28 | 2019-04-25 | 삼성전자 주식회사 | Operation method for low energy blue-tooth communication in terminal and device thereof |
EP2915351A1 (en) * | 2012-10-31 | 2015-09-09 | Nokia Solutions and Networks Oy | Discovery of proximity services in cellular system |
GB2507546B (en) * | 2012-11-02 | 2015-06-10 | Broadcom Corp | Mobile communications networks |
WO2014094836A1 (en) * | 2012-12-19 | 2014-06-26 | Telefonaktiebolaget L M Ericsson (Publ) | Extending global operator device id to aggregated devices |
AU2013276983B2 (en) * | 2012-12-26 | 2017-05-18 | Samsung Electronics Co., Ltd. | Terminal device and method for controlling thereof |
US9414422B2 (en) * | 2013-01-08 | 2016-08-09 | Broadcom Corporation | Proximity detection for mobile communication devices using geo-fencing |
JP5693622B2 (en) | 2013-01-09 | 2015-04-01 | ヤフー株式会社 | Social networking service system, server, processing method and program |
US20140214933A1 (en) * | 2013-01-28 | 2014-07-31 | Ford Global Technologies, Llc | Method and Apparatus for Vehicular Social Networking |
KR102109400B1 (en) * | 2013-02-22 | 2020-05-12 | 삼성전자 주식회사 | Method and apparatus for creating communication group of terminal |
US9532400B2 (en) * | 2013-02-28 | 2016-12-27 | Intel Deutschland Gmbh | Radio communication devices and cellular wide area radio base station |
US20140269557A1 (en) * | 2013-03-14 | 2014-09-18 | Mobilesphere Holdings II LLC | Verified emergency group communications |
US20160366214A9 (en) * | 2013-03-15 | 2016-12-15 | Jean Alexandera Munemann | Dual node network system and method |
KR101744750B1 (en) * | 2013-03-28 | 2017-06-09 | 가부시키가이샤 코나미 데지타루 엔타테인멘토 | Management device, management method, and storage medium |
US11188989B2 (en) * | 2013-04-23 | 2021-11-30 | Sung Kwan Hong | Method for providing social network service |
KR102092063B1 (en) * | 2013-04-26 | 2020-03-23 | 삼성전자 주식회사 | Method And Apparatus For Performing Communication Service |
WO2014176736A1 (en) * | 2013-04-28 | 2014-11-06 | Tencent Technology (Shenzhen) Company Limited | Method and apparatus for establishing chat group |
KR20140133735A (en) * | 2013-05-10 | 2014-11-20 | 한국전자통신연구원 | Method for content transfer by using social information |
US9654960B2 (en) * | 2013-05-31 | 2017-05-16 | Qualcomm Incorporated | Server-assisted device-to-device discovery and connection |
JPWO2015005158A1 (en) * | 2013-07-09 | 2017-03-02 | シャープ株式会社 | COMMUNICATION CONTROL METHOD, TERMINAL DEVICE, AND BASE STATION DEVICE |
JP5680153B2 (en) * | 2013-08-06 | 2015-03-04 | シャープ株式会社 | Wireless communication system, pairing device, method for pairing a plurality of devices, and program for causing computer to realize the method |
US9819503B2 (en) * | 2013-08-07 | 2017-11-14 | DeNA Co., Ltd. | Server device for exchanging messages |
US9538452B2 (en) * | 2013-08-23 | 2017-01-03 | Google Technology Holdings LLC | Management of ad-hoc peer-to-peer connections to provide data network access using a plurality of heterogeneous wide area networks |
EP2846603A3 (en) * | 2013-08-30 | 2015-06-03 | Vodafone IP Licensing limited | Reducing the number of radio interfaces by using a mobile terminal as signalling relay for other mobile terminals |
JP6264815B2 (en) * | 2013-09-30 | 2018-01-24 | ブラザー工業株式会社 | Communication device |
WO2015068988A1 (en) * | 2013-11-06 | 2015-05-14 | 엘지전자(주) | Method for transmitting and receiving data in wireless communication system and apparatus for performing same |
CN104640172A (en) * | 2013-11-08 | 2015-05-20 | 电信科学技术研究院 | D2D (device to device) discovery signal transmitting method and D2D discovery signal transmitting device |
KR20150060128A (en) * | 2013-11-26 | 2015-06-03 | 삼성전자주식회사 | Method, storage medium and apparatus for peer to peer service using contact information |
JP2015106388A (en) | 2013-12-02 | 2015-06-08 | 株式会社東芝 | Information processing method, information processor and program |
US9585177B2 (en) * | 2013-12-11 | 2017-02-28 | At&T Intellectual Property I, L.P. | Cellular connection sharing |
US10292086B2 (en) * | 2013-12-26 | 2019-05-14 | Sony Corporation | Information processing device and information processing method |
KR102117049B1 (en) * | 2013-12-30 | 2020-05-29 | 삼성전자주식회사 | mobile terminal, and method for operating the same |
CN104144110B (en) * | 2014-01-24 | 2016-11-09 | 腾讯科技(深圳)有限公司 | The method and system of PUSH message |
US9942751B2 (en) * | 2014-01-29 | 2018-04-10 | Netiq Corporation | Audio proximity-based mobile device data sharing |
JP6405658B2 (en) * | 2014-03-18 | 2018-10-17 | 株式会社リコー | Information sharing system, information sharing method, terminal device, communication method, and program |
KR20150110330A (en) * | 2014-03-21 | 2015-10-02 | 삼성전자주식회사 | Method for collection multimedia information and device thereof |
US9686285B2 (en) * | 2014-03-24 | 2017-06-20 | Verizon Patent And Licensing Inc. | Securely transmitting authentication information |
US9210192B1 (en) * | 2014-09-08 | 2015-12-08 | Belkin International Inc. | Setup of multiple IOT devices |
KR102270007B1 (en) * | 2014-05-07 | 2021-06-28 | 삼성전자주식회사 | Terminal device and method for remote control thereof |
JP6053719B2 (en) * | 2014-05-14 | 2016-12-27 | シャープ株式会社 | Network system, server, terminal, information processing method, and program |
US10453023B2 (en) * | 2014-05-28 | 2019-10-22 | Fedex Corporate Services, Inc. | Methods and node apparatus for adaptive node communication within a wireless node network |
US20160061472A1 (en) * | 2014-09-02 | 2016-03-03 | Samsung Electronics Co., Ltd. | Method and device for controlling room temperature and humidity |
KR102011472B1 (en) | 2014-09-05 | 2019-08-16 | 라인 가부시키가이샤 | Social network service providing system, user terminal and relationship setting method for setting relationship between users of mobile terminal |
MX2017004469A (en) * | 2014-10-07 | 2017-06-19 | Wal Mart Stores Inc | Apparatus and method of scanning products and interfacing with a customer's personal mobile device. |
US9716788B2 (en) * | 2014-11-13 | 2017-07-25 | Verizon Patent And Licensing Inc. | Multiple secondary device call controls and protocols |
JP2016126445A (en) * | 2014-12-26 | 2016-07-11 | Line株式会社 | Server, control method thereof, and program |
US9668194B2 (en) * | 2015-01-30 | 2017-05-30 | Huawei Technologies Co., Ltd. | System and method for coordinating device-to-device communications |
CN105930040A (en) * | 2015-02-27 | 2016-09-07 | 三星电子株式会社 | Electronic device including electronic payment system and operating method thereof |
US10250073B2 (en) * | 2015-03-22 | 2019-04-02 | Powermat Technologies Ltd. | System and methods of centrally managing a wireless power outlet for powering electrical devices |
US20160284011A1 (en) * | 2015-03-25 | 2016-09-29 | Facebook, Inc. | Techniques for social messaging authorization and customization |
US9762392B2 (en) * | 2015-03-26 | 2017-09-12 | Eurotech S.P.A. | System and method for trusted provisioning and authentication for networked devices in cloud-based IoT/M2M platforms |
US9407624B1 (en) * | 2015-05-14 | 2016-08-02 | Delphian Systems, LLC | User-selectable security modes for interconnected devices |
-
2015
- 2015-03-31 JP JP2015074149A patent/JP6533085B2/en active Active
- 2015-08-27 US US14/837,748 patent/US20160295353A1/en not_active Abandoned
-
2018
- 2018-10-01 US US16/148,149 patent/US10582344B2/en active Active
-
2019
- 2019-08-29 US US16/555,493 patent/US10555135B2/en active Active
-
2020
- 2020-01-23 US US16/750,484 patent/US10841752B2/en active Active
- 2020-10-13 US US17/069,298 patent/US11405756B2/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6957229B1 (en) * | 2000-01-10 | 2005-10-18 | Matthew Graham Dyor | System and method for managing personal information |
US20100016006A1 (en) * | 2006-04-13 | 2010-01-21 | Kyocera Corporation | Group Communication Method and Communication Terminal |
US20090292799A1 (en) * | 2008-05-23 | 2009-11-26 | Research In Motion Limited | Remote administration of mobile wireless devices |
US20120020238A1 (en) * | 2009-05-19 | 2012-01-26 | Junji Suetsugu | Network system, communication terminal, communication method, and communication program |
US20170150330A1 (en) * | 2014-04-13 | 2017-05-25 | Lg Electronics Inc. | Method for managing d2d terminal group in wireless communication system and apparatus for same |
US20190387367A1 (en) * | 2015-03-31 | 2019-12-19 | Line Corporation | Terminal devices, information processing methods, and computer readable storage mediums |
US10582344B2 (en) * | 2015-03-31 | 2020-03-03 | Line Corporation | Terminal devices, information processing methods, and computer readable storage mediums |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2022015050A1 (en) * | 2020-07-14 | 2022-01-20 | Samsung Electronics Co., Ltd. | Methods and systems for updating group information |
Also Published As
Publication number | Publication date |
---|---|
US11405756B2 (en) | 2022-08-02 |
JP6533085B2 (en) | 2019-06-19 |
US10841752B2 (en) | 2020-11-17 |
US20190037364A1 (en) | 2019-01-31 |
US10555135B2 (en) | 2020-02-04 |
US20190387367A1 (en) | 2019-12-19 |
US20210029518A1 (en) | 2021-01-28 |
JP2016194797A (en) | 2016-11-17 |
US10582344B2 (en) | 2020-03-03 |
US20160295353A1 (en) | 2016-10-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11405756B2 (en) | Terminal devices, information processing methods, and computer readable storage mediums | |
US10003929B2 (en) | Location based assisting apparatuses, methods and computer readable mediums | |
US10064025B2 (en) | Offline peer-assisted notification delivery | |
US10942972B2 (en) | Query processing method, electronic device, and server | |
US20150120502A1 (en) | Supporting guaranty provisioning via user attribute proffering | |
US20230005083A1 (en) | Method, system and recording medium for managing official account | |
US20130024576A1 (en) | Proximity-Based Detection | |
WO2015066023A1 (en) | Supporting guaranty provisioning via user attribute proffering | |
US11317258B2 (en) | Methods, systems, and non-transitory computer readable record media for grasping nearby friend based on short-range wireless communication | |
AU2015337278A1 (en) | Device and method for secure connection | |
US10548178B2 (en) | Method and device for establishing communication connection | |
US20150072704A1 (en) | Mechanism for facilitating dynamic detection and communication of geo-locations for devices | |
US9654929B2 (en) | System and method for providing notification based on location deviation | |
US20170324586A1 (en) | Methods and systems for service interworking between servers using different user identification systems | |
KR102290755B1 (en) | Method and apparatus for providing information based on proximity | |
US20190149942A1 (en) | Location-based wireless device presentation and connection | |
US10382414B2 (en) | Method, system and recording medium for service account authentication | |
KR102514593B1 (en) | Method and Apparatus for Building RF Fingerprint | |
US20190274115A1 (en) | Electronic device and method for determining entry of region of interest of electronic device | |
US11393578B2 (en) | Method and system to facilitate patient care | |
JP6788704B2 (en) | Servers, information processing methods and programs | |
JP7153703B2 (en) | Program, terminal, information processing method, and system | |
Liu et al. | Book searching navigation in libraries based on iBeacon technology | |
KR20230040851A (en) | method of performing land control based on drone operation through an application |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: LINE CORPORATION, JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:A HOLDINGS CORPORATION;REEL/FRAME:058597/0303 Effective date: 20211118 Owner name: A HOLDINGS CORPORATION, JAPAN Free format text: CHANGE OF NAME;ASSIGNOR:LINE CORPORATION;REEL/FRAME:058597/0141 Effective date: 20210228 |
|
AS | Assignment |
Owner name: A HOLDINGS CORPORATION, JAPAN Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE THE CITY SHOULD BE SPELLED AS TOKYO PREVIOUSLY RECORDED AT REEL: 058597 FRAME: 0141. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNOR:LINE CORPORATION;REEL/FRAME:062401/0328 Effective date: 20210228 Owner name: LINE CORPORATION, JAPAN Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE SPELLING OF THE ASSIGNEES CITY IN THE ADDRESS SHOULD BE TOKYO, JAPAN PREVIOUSLY RECORDED AT REEL: 058597 FRAME: 0303. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNOR:A HOLDINGS CORPORATION;REEL/FRAME:062401/0490 Effective date: 20211118 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
AS | Assignment |
Owner name: Z INTERMEDIATE GLOBAL CORPORATION, JAPAN Free format text: CHANGE OF NAME;ASSIGNOR:LINE CORPORATION;REEL/FRAME:067069/0467 Effective date: 20231001 |
|
AS | Assignment |
Owner name: LY CORPORATION, JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:Z INTERMEDIATE GLOBAL CORPORATION;REEL/FRAME:067096/0431 Effective date: 20240329 |