WO2019119362A1

WO2019119362A1 - Method and apparatus for making friend by friend type-based filtration

Info

Publication number: WO2019119362A1
Application number: PCT/CN2017/117809
Authority: WO
Inventors: 杨琴琴
Original assignee: 华为技术有限公司
Priority date: 2017-12-21
Filing date: 2017-12-21
Publication date: 2019-06-27
Also published as: CN110622160A; CN110622160B

Abstract

Embodiments of the present application relate to the technical field of communications and provide a method and apparatus for making a friend by friend type-based filtration, capable of reducing harassment caused by a friend request not conforming to user expectations, and meanwhile improving the success rate of making friends. The method comprises that: a first user may set on a terminal that the first user is willing to receive a friend request sent by which type of users (i.e., a first friend type); a friend request received by the terminal may come from a user belonging to the first friend type (for example, a second user), or from a user not belonging to the first friend type (for example, a third user), and then, the terminal may display the friend request from the second user on an interface of received friend requests, and the friend request from the third user not conforming to the first friend type may not be displayed on the interface, so that harassment caused to the user by receiving a large amount of friend requests not conforming to user expectations is reduced.

Description

Method and device for making friends by screening friend types

Technical field

The embodiments of the present invention relate to the field of communications technologies, and in particular, to a method and device for making friends.

Background technique

With the rapid development of communication technology, many mobile social software have set up dating functions. After the user opens the dating function, he can find strangers who also open the dating function, and then make new friends. However, when using the dating feature, the success rate of the user's friends is not high.

Summary of the invention

The embodiment of the present application provides a method and device for making friends, which can reduce the harassment caused by a friend request that does not meet the user's expectation, and improve the success rate of the friend.

To achieve the above objective, the embodiment of the present application adopts the following technical solutions:

In a first aspect, an embodiment of the present application provides a method for dating, comprising: receiving, by a first terminal, a first friend type set for a first user; and when receiving, by the first terminal, a second user (the second user belongs to the first friend) When the friend of the type is requested, since the second user belongs to the first friend type, the second user meets the friend preference of the first user. Therefore, the first terminal may display the friend request of the second user on the first interface; When the terminal receives the friend request from the third user (the third user does not belong to the first friend type), since the third user does not belong to the first friend type, the third user meets the friend preference of the first user, and therefore, the first terminal The third user's friend request may not be displayed in the first interface, thereby reducing the harassment caused by the user receiving a large number of friend requests that do not meet the user's expectation when the user views the friend request, and improving the chance of subsequent friend success.

Exemplarily, the first friend type may specifically include: age, gender, education, graduate school, occupation, hobby/introduction, blood type, height, weight, constellation, hometown, marriage situation, address, and the first user. At least one option in the distance.

In a possible design method, after the first terminal receives the first friend type set for the first user, the method further includes: the first terminal sending the first friend type to the server, so that the server determines the first user At least one user belonging to the first friend type to alleviate the implementation complexity of the first terminal.

In a possible design method, the second user's friend request includes the second user's personal information, and the second user's personal information satisfies the first friend type, and the third user's friend request includes the third user's Personal profile, but the third user's profile does not satisfy the first friend type. At this time, after receiving the friend request of the second user and the friend request of the third user, the first terminal may filter out the user belonging to the first friend type (ie, the second user) according to the personal data carried by the first terminal, and then display The friend request of the second user.

In a possible design method, after the first terminal receives the first friend type set for the first user, the method further includes: the first terminal prompting the first user to add the fourth user belonging to the first friend type as a friend The distance between the first terminal and the second terminal of the fourth user is less than a threshold, so that the user can conveniently make a friend who meets his or her friends' expectations in real life.

In a possible design method, the first terminal displays the friend request from the second user, including: the first terminal displays and receives in the lock screen interface, the pull-down menu, the pull-up menu, the negative one-screen menu, the notification bar, or the desktop. To A prompt requested by a friend of the second user.

In a possible design method, the friend request of the second user is associated with the profile of the second user; wherein, after the first terminal displays the friend request from the second user, the method further includes: responding to the first user pair The first user's friend requests the input first operation, and the first terminal displays the second user's personal information, which helps the first user to fully understand the second user's related information before adding the second user as a friend.

In a possible design method, after the first terminal receives the friend request from the third user, the method further includes: the first terminal displaying the friend request of the third user on the second interface. That is to say, when receiving a friend request that does not meet the user of the first friend type, the terminal may display the friend request of the third user in other interfaces, so that the user can perform operations such as viewing or deleting.

In a possible design method, after the first terminal displays the friend request of the third user in the second interface, the method further includes: in response to the second operation of the first user requesting the friend of the third user, the first terminal Modifying the first friend type, so that the third user belongs to the modified first friend type, thereby improving the accuracy rate of the subsequent first user using the friend function to receive the friend request.

In one possible design method, the first friend type includes the hobby/introduction option, wherein the hobby/introduction option is set with: a hobby/introduction between the first user and a user belonging to the first buddy type Similarity, so you can make friends with your hobby.

In a possible design method, the method further includes: the first terminal receives the second friend type set for the first user; the first terminal sends the second friend type to the server, so that the server belongs to the second friend type The fifth user sends the friend request of the first user, so that the first user can request to become a friend with the specified type of user without the user's perception, thereby improving the efficiency of making friends, and omitting the cumbersome manual input condition of the friend each time. Settings.

In a possible design method, the method further includes: the first terminal receives a third friend type set for the first user; the first terminal sends a third friend type to the server, so that the server belongs to the third friend type The sixth user sends the first user's profile to prevent the first user's profile from being seen by other users who do not meet the expectations of the first user.

In a second aspect, an embodiment of the present application provides a method for dating, comprising: receiving, by a server, a personal data of a first user sent by a first terminal and a friend type set for the first user; and acquiring a second user by the server (second When the user belongs to the friend type) querying the first request of the first user's profile, in response to the first request, the server may send the first user's profile to the second user's second terminal; when the server acquires the third user (The third user does not belong to the friend type) When the second request for the first user's profile is queried, the server does not respond to the second request.

In a possible design method, the method further includes: the server acquiring a third request for the first user to query the personal data of the fourth user; if the first user belongs to the friend type set by the fourth user, the server is The first terminal sends the personal data of the fourth user; if the first user does not belong to the friend type set by the fourth user, the server does not respond to the third request.

In one possible design method, the friend type includes: age, gender, education, graduate school, occupation, hobby/introduction, blood type, height, weight, constellation, hometown, marriage situation, address, and first user At least one option in the distance.

In a third aspect, an embodiment of the present application provides a terminal, including: an acquiring unit, configured to: receive as a first a first friend type set by the user; receiving a friend request from the second user, the second user belongs to the first friend type; and receiving a friend request from the third user, the third user does not belong to the first friend type; the display unit uses The first user's friend request is displayed on the first interface, and the processing unit is configured to: not display the third user's friend request in the first interface.

In a possible design method, the terminal further includes a sending unit, configured to: send the first friend type to the server, so that the server determines, for the first user, at least one user belonging to the first friend type.

In a possible design method, the second user's friend request includes the second user's personal information, the second user's personal information satisfies the first friend type, and the third user's friend request includes the third user's personal information. The third user's profile does not satisfy the first friend type, and the processing unit is further configured to: screen the second user belonging to the first friend type according to the second user's personal profile and the third user's personal profile.

In a possible design method, the processing unit is further configured to: prompt the first user to add the fourth user as a friend, where the fourth user belongs to the first friend type, the first terminal and the fourth user The distance between the second terminals is less than a threshold.

In a possible design method, the friend request of the second user is associated with the profile of the second user; the obtaining unit is further configured to: acquire a first operation of the first user requesting input by the friend of the second user; The display unit is further configured to: display the personal data of the second user.

In a possible design method, the display unit is further configured to: display a friend request of the third user on the second interface.

In a possible design method, the obtaining unit is further configured to: obtain a second operation that the first user requests the third user's friend to input; the processing unit is further configured to: modify the first friend type, so that The three users belong to the modified first friend type.

In a possible design method, the acquiring unit is further configured to: receive a second friend type set for the first user; the sending unit is further configured to: send a second friend type to the server, so that the server The fifth user sends a friend request of the first user, and the fifth user belongs to the second friend type.

In a possible design method, the obtaining unit is further configured to: receive a third friend type set for the first user; the sending unit is further configured to: send a third friend type to the server, so that the server The sixth user sends the personal profile of the first user, and the sixth user belongs to the third friend type.

In a fourth aspect, an embodiment of the present application provides a server, including: an acquiring unit, configured to: receive a personal data of a first user sent by a first terminal, and a friend type set for the first user; and obtain a second user query a first request of a user's profile, the second user belongs to the friend type; and a second request for the third user to query the first user's profile, the third user does not belong to the friend type; and the sending unit is configured to: Transmitting, to the second terminal of the second user, the personal data of the first user; and the processing unit, configured to: not respond to the second request.

In a possible design method, the obtaining unit is further configured to: obtain a third request for the first user to query the personal data of the fourth user; and the processing unit is further configured to: determine whether the first user belongs to the fourth user setting a friend type; if the first user belongs to the friend type set by the fourth user, the sending unit is further configured to: send the fourth user's personal data to the first terminal; if the first user does not belong to the fourth user setting The buddy type, the processing unit, is further configured to: not respond to the third request.

In a fifth aspect, an embodiment of the present application provides a terminal, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer to execute an instruction, and the processor is connected to the memory through the bus. When the terminal is running, the processor executes the computer execution instruction stored in the memory to enable the terminal to execute any of the above-mentioned dating methods.

In a sixth aspect, an embodiment of the present application provides a server, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus, when the server is running The processor executes the computer-executed instructions stored by the memory to cause the server to perform any of the above-described dating methods.

In a seventh aspect, an embodiment of the present application provides a computer readable storage medium, where the computer readable storage medium stores an instruction, when the instruction is run on any one of the foregoing terminals, causing the terminal to execute any one of the foregoing friendship methods. .

In an eighth aspect, an embodiment of the present application provides a computer readable storage medium, where the computer readable storage medium stores an instruction, when the instruction is run on any one of the servers, causing the server to execute any one of the foregoing method .

In a ninth aspect, the embodiment of the present application provides a computer program product including instructions, when the terminal runs on any of the foregoing terminals, causing the terminal to perform any of the above-mentioned dating methods.

In a tenth aspect, the embodiment of the present application provides a computer program product including instructions, when the server runs on any of the foregoing servers, causing the server to execute any of the foregoing dating methods.

In the embodiment of the present application, the names of the components in the terminal or the server are not limited to the device itself, and in actual implementation, the components may appear under other names. As long as the functions of the various components are similar to the embodiments of the present application, they are within the scope of the claims and their equivalents.

In addition, the technical effects brought by the design method of any one of the second aspect to the tenth aspect can be referred to the technical effects brought by different design methods in the above first aspect, and details are not described herein again.

DRAWINGS

FIG. 1 is a schematic structural diagram 1 of a terminal according to an embodiment of the present disclosure;

2 is a schematic structural diagram of a programming module in a terminal according to an embodiment of the present application;

FIG. 3 is a schematic diagram 1 of an application scenario of a friend method according to an embodiment of the present disclosure;

FIG. 4 is a schematic diagram 2 of an application scenario of a friend method according to an embodiment of the present disclosure;

FIG. 5 is a schematic diagram 3 of an application scenario of a friend method according to an embodiment of the present disclosure;

FIG. 6 is a schematic diagram 4 of an application scenario of a friend method according to an embodiment of the present disclosure;

FIG. 7 is a schematic diagram 5 of an application scenario of a friend method according to an embodiment of the present disclosure;

FIG. 8 is a schematic diagram 6 of an application scenario of a friend method according to an embodiment of the present disclosure;

FIG. 9 is a schematic diagram 7 of an application scenario of a friend method according to an embodiment of the present application;

FIG. 10 is a schematic diagram 8 of an application scenario of a friend method according to an embodiment of the present disclosure;

FIG. 11 is a schematic diagram 9 of an application scenario of a friend method according to an embodiment of the present disclosure;

FIG. 12 is a schematic diagram of an application scenario of a friend method according to an embodiment of the present application;

FIG. 13 is a schematic diagram of an application scenario of a friend method according to an embodiment of the present application;

FIG. 14 is a schematic diagram of an application scenario of a friend method according to an embodiment of the present application;

FIG. 15 is a schematic diagram of an application scenario of a method for making friends according to an embodiment of the present application;

16 is a schematic diagram of an application scenario of a friend method according to an embodiment of the present application;

FIG. 17 is a schematic diagram of an application scenario of a friend method according to an embodiment of the present application;

FIG. 18 is a schematic diagram of an application scenario of a friend method according to an embodiment of the present disclosure;

FIG. 19 is a schematic structural diagram 2 of a terminal according to an embodiment of the present disclosure;

FIG. 20 is a schematic structural diagram 1 of a server according to an embodiment of the present disclosure;

FIG. 21 is a schematic structural diagram 3 of a terminal according to an embodiment of the present disclosure;

FIG. 22 is a schematic structural diagram 2 of a server according to an embodiment of the present application.

Detailed ways

In the following, the terms "first" and "second" are used for descriptive purposes only, and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, features defining "first" and "second" may include one or more of the features either explicitly or implicitly. In the description of the embodiments of the present application, "multiple" means two or more unless otherwise stated.

A friend method provided by the embodiment of the present application can be applied to a mobile phone, a tablet computer, a wearable device, an augmented reality (AR), a virtual reality (VR) device, a notebook computer, a super mobile personal computer (ultra) The mobile phone, the UMPC, the netbook, the personal digital assistant (PDA), and the like, are not limited in any way.

As shown in FIG. 2, the terminal in the embodiment of the present application may be the mobile phone 100. The embodiment will be specifically described below by taking the mobile phone 100 as an example. It should be understood that the illustrated mobile phone 100 is only one example of the above terminal, and the mobile phone 100 may have more or fewer components than those shown in the figure, two or more components may be combined, or Has a different component configuration.

Referring to FIG. 2, the handset 100 can communicate with other

electronic devices

102 and 104, other than the handset 100, and the server 106. The handset 100 can include a bus 110, a processor 120, a memory 130, a user input module 150, a display module 160, a communication interface 170, and other similar and/or suitable components.

Bus 110 may be circuitry that interconnects the above elements and communicates (e.g., control messages) between the elements.

The processor 120 can receive commands from the other components (such as the memory 130, the user input module 150, the display module 160, the communication interface 170, the communication configuration control module 170, etc.) through the bus 110, can interpret the received commands, and can Interpret commands to perform calculations or data processing.

Memory 130 may store commands or data received from processor 120 or other components (e.g., user input module 150, display module 160, communication interface 170, etc.) or commands or data generated by processor 120 or other components.

Memory 130 may include programming modules such as kernel 131, middleware 132, application programming interface (API) 133, applications 134, and the like. Each of the above programming modules may be implemented in software, firmware, hardware, or a combination of two or more thereof, as described in detail in the related description of FIG.

The kernel 131 may control or manage system resources (e.g., bus 110, processor 120, memory 130, etc.) for performing operations or functions implemented by other programming modules (e.g., middleware 132, API 133, and applications 134). Additionally, the kernel 131 can provide an interface that can access and control or manage the various elements of the handset 100 by using the middleware 132, the API 133, or the application 134.

The middleware 132 can be used between the API 133 or the application 134 and the kernel 131 with API 133 or application 134 It operates in communication with the kernel 131 and exchanges data therewith. For example, the middleware 132 can be configured as an intermediary for communication between the API 133 or the application 134 and the kernel 131. Additionally, for example, regarding a work request received from one or more applications 134 and/or middleware 132, a priority may be assigned to at least one of the one or more applications 134 (where the priority may be Load balancing of work requests is performed using methods of system resources (e.g., bus 110, processor 120, memory 130, etc.) of handset 100.

The API 133 is an interface by which the application 134 can control functions provided by the kernel 131 or the middleware 132, and can include, for example, at least one interface or function for file control, window control, image processing, character control, and the like.

Applications 134 may include, for example, a home page application, a dialer application, a short message service (SMS)/multimedia message service (MMS) application, an instant messaging (IM) application, a browser application, a camera application, an alarm clock application, a contact application, voice dialing. Applications, email (e-mail) applications, calendar applications, media player applications, photo album applications, clock applications, and any other suitable and/or similar applications.

The user input module 150 can receive commands or data input from a user via input-output means (eg, sensors, keyboards, touch screens, etc.) and can transmit the received commands or data to the processor 120 or memory 130 via the bus 110. Display module 160 can display video, images, data, and the like to the user.

The display module 160 can display various information (eg, multimedia data, text data) received from the above components.

Communication interface 170 can control a short range communication connection with another electronic device 102. When the mobile phone 100 is paired with another electronic device, the communication interface 170 may stop a scanning operation of waiting for receiving a signal from a neighboring electronic device or stopping a broadcast operation of a broadcast signal. For example, in response to the handset 100 being paired with another electronic device 102, the communication interface 170 stops waiting for a scan operation to receive a signal from a neighboring electronic device or a broadcast operation to stop the broadcast signal. When the handset 100 is paired with another electronic device, the communication interface 170 can control the period of the scanning or broadcast operation.

In accordance with various embodiments disclosed herein, handset 100 can communicate with another electronic device using communication interface 170. For example, communication interface 170 can communicate with another electronic device 104, server 106, and the like. Communication interface 170 can communicate with other electronic devices 104, servers 106, etc., either directly or through network 162. For example, communication interface 170 can operate to connect handset 100 to network 162.

FIG. 3 is a block diagram showing a configuration of a programming module in accordance with an embodiment of the present disclosure.

Referring to FIG. 3, programming module 310 can be included (or stored) in handset 100 (e.g., memory 130) shown in FIG. At least a portion of programming module 310 can be implemented as software, firmware, hardware, or a combination of two or more of them. Programming module 310 can be implemented as hardware (eg, hardware 201) and can include an operating system (OS) that controls resources associated with an electronic device (eg, cell phone 100) and/or various applications executing in the OS (eg, Application 370). For example, the OS can be Android, iOS, Windows, Symbian, Tizen, Bada, and the like.

Referring to FIG. 3, programming module 310 can include kernel 320, middleware 330, API 360, and/or application 370.

Kernel 320 (e.g., kernel 131) may include system resource manager 321 and/or device driver 323. The system resource manager 321 can include a process manager (not shown), a memory manager (not shown), and a file system manager (not shown). The system resource manager 321 can perform control, allocation, recovery, and the like of system resources. The device driver 323 may include, for example, a display driver (not shown), a camera driver (not shown), blue A dental driver (not shown), a shared memory driver (not shown), a USB driver (not shown), a keypad driver (not shown), wireless-fidelity (Wi-Fi) Drivers (not shown) and/or audio drivers (not shown). Moreover, in accordance with embodiments disclosed herein, device driver 323 may include an inter-process communication (IPC) driver (not shown).

The middleware 330 may include a plurality of modules that are implemented in advance to provide functions shared by the application 370. In addition, middleware 330 can provide functionality to application 370 via API 360 to enable application 370 to efficiently utilize limited system resources within the electronic device. For example, as shown in FIG. 3, the middleware 330 (eg, the middleware 132) may include at least one of the following: a runtime library 335, an application manager 341, a window manager 342, a multimedia manager 343, a resource manager 344, and a power supply. Manager 345, database manager 346, package manager 347, connection manager 348, notification manager 349, location manager 350, graphics manager 351, security manager 352, and any other suitable and/or similar manager.

The runtime library 335 can include library modules, such as used by a compiler, to add new functionality by using a programming language during execution of the application 370. According to an embodiment disclosed herein, the runtime 335 can perform functions related to input and output, management of memory, arithmetic functions, and the like.

The application manager 341 can manage, for example, the lifecycle of at least one application 370. Window manager 342 can manage the graphical user interface (GUI) resources used on the screen. The multimedia manager 343 can detect a format for reproducing various media files, and can encode or decode the media file by using a codec suitable for the relevant format. The resource manager 344 can manage resources of at least one application 370, such as source code, memory, storage space, and the like.

The power manager 345 can operate with a basic input output system (BIOS), can manage a battery or a power source, and can provide power information for operation and the like. Database manager 346 can manage the database in a manner that enables generation, searching, and/or changing of a database to be used by at least one application 370. The package manager 347 can manage the installation and/or update of applications distributed in the form of package files.

The connection manager 348 can manage wireless connections such as Wi-Fi and Bluetooth (BT). The notification manager 349 can display or report events such as arrival messages, appointments, proximity alerts, etc. to the user in a manner that does not bother the user. The location manager 350 can manage location information of the electronic device. The graphics manager 351 can manage graphics effects to be provided to the user and/or UIs related to the graphics effects. Security manager 352 can provide various security functions for system security, user authentication, and the like. According to an embodiment of the present disclosure, when an electronic device (eg, mobile phone 100) has a phone function, the middleware 330 may further include a phone manager (not shown) for managing voice phone call functions of the electronic device and/or Video call function.

The middleware 330 can generate and use a new middleware module through various functional combinations of the internal component modules described above. The middleware 330 can provide modules specialized according to the type of OS to provide differentiated functions. The middleware 330 can also dynamically delete some of the existing components, or can add new components. Accordingly, the middleware 330 may omit some of the elements described in the various embodiments disclosed herein, and may include other elements, or some of these elements may be replaced with elements that perform similar functions and have different names.

API 360 (eg API 133) is a collection of API programming functions and can have different configurations depending on the OS. In the case of, for example, Android or iOS, one API set can be provided to each platform.

Application 370 (eg, application 134 in FIG. 2) may include, for example, a preloaded application and/or a third party application. Application 370 (eg, application 134) may include, for example, a home page application 371, a dialing application 372, an SMS/MMS application 373, IM application 374, browser application 375, camera application 376, alarm application 377, contact application 378, voice dialing application 379, email application 380, calendar application 381, media player application 382, album application 383, clock application 384, and Any other suitable and/or similar application.

At least a portion of programming module 310 can be implemented by instructions stored in a non-transitory computer readable storage medium. When instructions are executed by one or more processors (eg, one or more processors 210), the one or more processors can perform functions corresponding to the instructions. The non-transitory computer readable storage medium can be the memory 230. At least a portion of programming module 310 can be implemented (eg, executed) by, for example, one or more processors 210. At least a portion of programming module 310 can include modules, programs, routines, sets of instructions, and/or processes for performing one or more functions.

The names of the elements of the programming module (eg, programming module 310) in accordance with embodiments of the present disclosure may vary depending on the type of OS. A programming module in accordance with an embodiment of the present disclosure may include one or more of the above-described elements. Alternatively, some of the above elements may be omitted from the programming module. Alternatively, the programming module may also include additional components. The operations performed by the programming modules or other elements in accordance with embodiments of the present disclosure may be processed in a sequential method, a parallel method, a repeated method, or a heuristic method. In addition, some operations may be omitted, or other operations may be added in the operation.

In the embodiment of the present application, the application 370 may further include mobile social software with a dating function. Among them, the dating function refers to the function of the user to meet new friends on the mobile social software.

The user can send a friend request to other users on the mobile social software. When the other party requests through the friend, the user can become a friend with the user; of course, the user can also receive a friend request sent by other users on the mobile social software, and the user requests through the friend. You can become friends with it later.

Then, the user can view the personal information of the other party's photos, age, occupation, etc. before being friends with the other party, and can also view the personal data of the other party after being friends with the other party, and the embodiment of the present application does not impose any restrictions on this.

Exemplarily, the terminal may associate the user's profile information with other users in the friend request, so that other users can view the other party's personal information after receiving the friend request.

Exemplarily, the user can search for the user who uses the friend function in the mobile social software. For example, each terminal that opens the dating function can periodically report the location information of the user to the server. When the user actively searches for nearby users, the user will trigger. The terminal obtains a user closer to the server from the server. At this time, as shown in FIG. 3, the terminal may display the obtained nearby users (for example, “Sara” and “Mike” in FIG. 3) to the user in the form of a list. The user selects the friends they want to make in the list.

However, the above list generally only includes the avatars and nicknames of nearby users, that is, the user needs to rely on the user's image and nickname to judge whether they are willing to make friends with a searched user, which makes the user difficult to be fast and accurate. Get potential friends who meet their expectations. For example, if the user wants to make a friend who is similar to his age through the dating function, the search results shown in FIG. 3 are ineffective for the user to meet the user's expected invalid search results, and these invalid search results not only reduce the success rate of the friends, Adding a friend request that receives a large number of users who do not meet expectations may also cause harassment to the user, making the user's experience with the above-mentioned dating function poor.

In this regard, in the dating method provided by the embodiment of the present application, the user may set in advance on the social software to allow the terminal to receive which friend requests are sent by the user. For example, user settings are only allowed to receive Peking University 2013 graduation The user sends a friend request to it. Then, the subsequent terminal can filter the friend request sent by other terminals according to the setting, so that the friend request that meets the user's expectation (ie, the graduated from Peking University 2013) is prompted to the user, so as to prevent the user from receiving the user's expectation. The harassment requested by the friend, thereby improving the success rate of the social software.

Of course, the user can also set which users to send their own friend requests in advance on the social software. For example, the user setting automatically or manually sends a friend request associated with his or her own profile to a user whose location is Xi'an and whose occupation is an accountant. Then, only the user who is located in Xi'an and whose occupation is accountant has the right to read the personal data of the user in the above friend request, and at the same time, only the user who is located in Xi'an and whose occupation is accountant has a further chance to send the friend. The requested user becomes a friend, which not only avoids harassment from users who do not meet the user's expectations, but also reduces the risk of privacy leakage caused by the user's personal data being read by any user.

Exemplarily, as shown in (a) of FIG. 4, the mobile social software with the dating function is installed on the terminal 1: “friends” APP, and the user Sam holding the terminal 1 uses the “friends” APP for the first time, such as As shown in (b) of Figure 4, the "Friends" app will display a complete personal information interface where Sam can fill in or modify his or her personal information.

Exemplarily, as shown in (b) of FIG. 4, the personal data may include a name 1009, a personal photo option 1001, an age option 1002, an academic option 1003, a graduate college option 1004, a career option 1005, and a work location option. 1006, one or more of the hobby/introduction option 1007 and the gender option 1008.

Of course, the above personal data may also include personal information of blood type, height, weight, constellation, hometown, marriage and love, and address, etc., and this application does not impose any restrictions.

In addition, the content of some or all of the above-mentioned personal data may also be automatically generated by the terminal for the user, which will be elaborated in the following embodiments.

After Sam enters the "Friends" app, he can further set in his settings interface which kind of user he is willing to receive (which can be referred to as the first friend type in this application) to send to his friend request. For example, as shown in (a) of FIG. 5, after Sam enters the setting interface 401 of the "friends" APP, the option of "receiving who's friend request" can be selected to set which type of user to receive the friend. request.

As shown in (b) of FIG. 5, the first friend type in the “receiving friend request” may specifically include an age option 4011, a gender option 4012, an academic option 4013, a graduate college option 4014, and a career option 4015. The embodiment of the present application does not impose any limitation on one or more of the distance option 4016 and the hobby/introduction option 4017. Of course, Sam can also set a friend request that allows everyone to send it, that is, the first friend type is any type of user.

The relationship between each option in the first friend type is “and”, and each setting condition in each option is an “or” relationship.

For example, still as shown in (b) of FIG. 5, Sam selects the type of "female" in the gender option 4012, and selects the same "Tsinghua University" as the Sam alma mater in the graduate school option 4014. Type, then, the first friend type set by Sam is the user whose gender is "female" and graduated from "Tsinghua University", indicating that Sam intends to make friends with this type of user.

Then, when Sam uses the above-mentioned dating function provided by the terminal 1, it can receive it from the server, Receive broadcasts of other terminals, or establish wireless connections with other terminals (for example, Bluetooth connection, Wi-Fi connection, ZigBee connection), etc. to obtain other users' personal data. Further, the terminal 1 may select a user of the first friend type that matches the setting for Sam in the profiles, and display the user of the first friend type that meets the Sam setting in the form of a friend request.

At this time, Sam receives the friend request from the user whose gender is “female” and the graduate school is “Tsinghua University”, and the friend request that does not meet the above-mentioned first friend type does not prompt to Sam, thereby reducing the user. When a friend request is received, a large number of buddies that do not meet the user's expectations are received to harass the user, and the chances of success in subsequent friends are improved. Optionally, users who do not meet Sam's expectations can view Sam's profile, but can't make a friend request, or the user who does not meet Sam's expectations can't view Sam's profile.

For example, as shown in FIG. 6 , the Sam carrying terminal 1 enters a coffee shop and can open a friend function such as finding a friend, shaking or nearby people. At this time, the terminal 1 passes. The Bluetooth function can detect other terminals that also open the dating function within a certain distance range, such as the terminal 2 of Jean in FIG. 6 and the terminal 3 of Lucy. Among them, the personal data 1 of Jean is stored in the terminal 2, and the personal data 2 of Lucy is stored in the terminal 3. Alternatively, the terminal may also store only the identity of the user, and the corresponding personal data is stored on the server.

Then, the terminal 1 can acquire Jean's profile 1 and Lucy's profile 2 by listening to the Bluetooth broadcast or establishing a Bluetooth connection with the terminal 2 or the terminal 3. Further, the terminal 1 can determine whether there is a user who meets the Sam expectation in the personal data 1 and the personal data 2 according to the first friend type set by Sam in the "receiving friend request", that is, the gender is "female" and is in "Tsinghua" University graduated users.

For example, in profile 1, Jean's gender is "female", graduate school is "Tsinghua University", and in profile 2, Lucy's gender is "female" and the graduate school is "Peking University." Then, in conjunction with the first friend type set by Sam in (b) of FIG. 5, the terminal 1 can determine that Jean is a user of the first friend type set in accordance with Sam. Further, the terminal 1 can generate a friend request of Jean and display the friend request, so that Sam can obtain the potential friend existing nearby.

Or, when Sam carries the terminal 1 into a cafe, the terminal 1 can also obtain Jean's profile 1 and Lucy's profile 2 through the server. For example, when the terminal 1 detects that Sam opens the "friends in the vicinity" function, the terminal 1 can be triggered to send the location information of the terminal 1 to the server at this time, and request the server to obtain other similarities in the vicinity of the terminal 1 that also enable the friend function. User's profile. Then, the server can transmit the personal data 1 of Jean and the personal data 2 of Lucy reported by other terminals (such as the terminal 2 and the terminal 3) that are closer to the terminal 1 to the terminal 1 according to the location information of the terminal 1.

Of course, the server can also send the identifiers of the terminal 2 and the terminal 3 that are closer to the terminal 1 to the terminal 1, so that the terminal 1 can establish a connection with the terminal 2 and the terminal 3 according to the identifiers of the terminal 2 and the terminal 3, thereby obtaining the Jean. Profile 1 and Lucy's profile 2.

Still alternatively, the terminal 2 may broadcast an identification 1 for indicating Jean's profile in the Bluetooth broadcast, and the terminal 3 may broadcast an identification 2 for indicating Lucy's profile in the Bluetooth broadcast. Then, after the terminal 1 listens to the Bluetooth broadcast, the terminal 1 may be requested to search for personal data corresponding to the identifier 1 and the identifier 2, namely, the personal profile 1 of Jean and the profile 2 of Lucy.

In addition, when the terminal 1 displays a friend request from Jean, the terminal 1 can also indicate that the terminal 2 of the Jean rings or flashes the light through communication means such as Bluetooth, so that Sam can accurately locate and conform to it in real life. Dating the expected user Jean. Of course, Sam's terminal 1 can also ring or flash the lights so that the user who issued the friend request confirms the specific location of the user Sam who received his friend request.

Or alternatively, when the terminal 1 determines that the first friend type that meets the Sam setting, or determines one or more users that have a higher degree of matching with Sam's profile, the terminal 1 (or a wearable device connected to the terminal 1) It is also possible not to directly display a friend request from Jean, but to prompt a potential friend target near Sam by means of ringing sound, vibration frequency, or light color.

For example, the terminal 1 can determine that the Jean is a user who meets the expectations of his friends according to Jean's profile. Then, when it is detected that the distance between Jean and Sam is getting closer, the vibration frequency of the terminal 1 can be larger and larger to prompt. Sam is in line with his friends' expectations that the user is approaching.

The terminal 1 can determine the distance between the Jean and the Sam by detecting the signal strength or the GPS position between the terminal 2 and the second terminal. The embodiment of the present application does not impose any limitation on this.

Exemplarily, when the terminal 1 determines that the user of the first friend type that meets the setting is Jean, if the terminal 1 is in a lock screen or a black screen state, as shown in FIG. 7 , the terminal 1 can display a lock screen interface. And in the lock screen interface, it shows that the friend request from Jean has been received, thereby prompting Sam to become a friend with the user Jean who matches the first friend type. Of course, the terminal 1 can also display the friend request in an interface such as a drop-down menu, a pull-up menu, a desktop, a notification bar, and a negative one-screen menu, and the embodiment of the present application does not impose any limitation on this.

The negative one-screen menu may refer to an interface that slides from the desktop (or the main screen) to the right, and the interface can display the functions, applications, and subscribed services and information commonly used by the user. The negative one-screen menu is also called Desktop assistant, shortcut menu, and more.

As shown in (a) of FIG. 8 , after receiving the friend request from Jean, Sam can view the friend request in the friend push interface of the “friends” APP, and display part of Jean's profile in the friend push interface. For example, the portion of the profile that matches the first friend type set by Sam is displayed. Of course, Jean's profile may not be displayed in the friend push interface.

When Sam selects a friend request from Jean, if Jean's friend request is associated with Jean's profile, as shown in (b) of Figure 8, terminal 1 can display the complete Jean profile, where Jean's The graduation institution filled out in the personal data is “Tsinghua University” and the gender is “female”.

Of course, the "Friends" app can also be set to allow Sam and Jean to become friends before allowing them to view their profile and avoid revealing user information to users outside of their friends.

Since the terminal 1 prompts Sam to receive the friend request in accordance with the first friend type set by Sam, when the terminal 1 receives the friend request from Jean, the default Sam can receive the friend request of Jean and become a friend with Jean; Alternatively, when the terminal 1 prompts Sam to receive a friend request from Jean, Sam may become a friend with Sam after the friend requests through the friend; or, when the terminal 1 prompts Sam to receive a friend request from Jean, Sam may actively Jean sends a friend request, and when Jean sends a friend request sent by Sam, it becomes a friend with Jean. The embodiment of the present application does not limit the specific way of adding a friend as a friend.

In addition, the friend request in the friend push interface shown in (a) of FIG. 8 may also be sent by the server to the terminal 1. Specifically, after Sam selects the first friend type whose gender is “female” and the graduate school is selected as “Tsinghua University”, the terminal 1 may send the first friend type set by Sam to the server of the “friends” APP. Carry out maintenance.

In this way, when the server receives other users' personal data (such as the personal data associated with the friend request) The server may determine one or more users who meet the gender as “female” and the graduate school is “Tsinghua University” according to the first friend type set by Sam, and send the friend request of the user to the terminal 1, by the terminal. 1 Display the friend request. At this time, Sam can still view the friend request determined by the server for Sam to meet Sam's expectations in the friend push interface shown in FIG. 8.

Of course, Sam can also actively search for the user who matches the first friend type in the search interface of the "friends" APP. As shown in FIG. 9, the terminal 1 may use the personal data of the user of the first friend type set by Sam, such as Jean and GiGi's personal data, as the search result, and the search result. Display it to Sam as a list. Sam can select the corresponding user to add as a friend in the list, or view the user's profile.

Of course, the terminal 1 can also sort the users in the list according to the distance between Sam and Jean and GiGi according to the distance, in order of increasing distance, in order to improve the success rate of the friends.

The server or other terminal may not send the friend request of the user to the terminal 1 for the first friend type that does not meet the Sam setting; or the terminal 1 may automatically block the friend request of the user sent by the server or other terminal; or The terminal 1 can also display the friend requests of these users in the mask list 601 shown in FIG.

As shown in FIG. 10, the terminal 1 receives the personal data of Jean and Lucy in the coffee shop shown in FIG. 6, wherein the profile of Lucy does not conform to the first friend type set by Sam, then the terminal 1 can use Lucy's The friend request is displayed in the mask list 601 in the form of a mask message, and Sam can view or delete the Lucy friend request in the mask list 601.

Exemplarily, Sam may perform a rightward sliding operation on the masked message from Lucy in the mask list 601. At this time, as shown in (a) of FIG. 11, the terminal 1 may call the response in response to the sliding operation of Sam. The delete button 701 and the blacklist button 702 of the message are masked. Sam can delete the friend request of Lucy in the mask list 601 by clicking the delete button 701, or Sam can manually add Lucy to the blacklist by clicking the blacklist button 702. After Lucy is blacklisted, Terminal 1 will block all subsequent messages from Lucy.

Alternatively, Sam can click on the masked message from Lucy in the mask list 601 to view the full profile of the blocked Lucy. As shown in (b) of Figure 11, after Sam looks at Lucy's profile, if he wants to be friends with Lucy or has further communication, Sam can also click on the whitelist button 703 to manually add Lucy to the whitelist. After Lucy is added to the whitelist, if the terminal 1 subsequently receives the message from Lucy again, the terminal 1 will prompt the message sent by Lucy to Sam.

Further, if Sam manually adds Lucy that does not originally meet the above-mentioned first friend type to the white list, as shown in (a) of FIG. 12, the terminal 1 may prompt Sam to return to the setting shown in (a) of FIG. 5. The interface 401 resets the first friend type in the "receive friend request".

Alternatively, the terminal 1 can automatically optimize the first friend type preset by Sam according to Lucy's profile. For example, Sam’s original first friend type includes only the graduate school as “Tsinghua University”, while Lucy’s profile shown in (b) of Figure 11 shows Lucy’s graduate school as “Beijing”. the University". Then, as shown in (b) of FIG. 12, the terminal 1 can optimize the option of the graduate school in the first friend type as "Tsinghua University" or "Peking University", and prompts Sam to determine the optimization result. If Sam determines the optimization result, the terminal 1 modifies the content of the option of the graduated college in the saved first friend type to "Tsinghua University" or "Peking University", so that the subsequent graduate school is "Tsinghua University". Or "Beijing The friend request of the user of the university can be sent to the terminal 1, thereby improving the success rate of subsequent friends using the "friend" APP.

In addition, in the embodiment of the present application, the terminal may also automatically assist the user to generate one or more of his personal data according to a big data statistics, an image recognition function, or a positioning function.

For example, the terminal 1 can read the location information of the terminal 1 during the working hours (for example, from 9:00 am to 6:00 pm), so that the read location information with the highest frequency of occurrence is used as the working place of Sam. And fill in the work location option 1006 shown in (b) of FIG.

For another example, the terminal 1 may perform face recognition on the personal photos uploaded by Sam in the personal photo option 1001 of his profile, identify the gender and age of Sam according to the facial features, and fill in the identified gender and age respectively. 4 (b) shown in age option 1002 and gender option 1008.

For another example, the terminal 1 can also send the behavior data of Sam on the terminal 1 to the server of the “friends” APP, and the server generates the user's hobby/introduction by means of big data statistics, etc., and sends the generated specific hobby/introduction to the server. The terminal 1 fills in the hobby/introduction generated by the server for Sam by the terminal 1 in the hobby/introduction option 1007 of the above profile.

Exemplarily, if it is detected that the user often plays the mobile phone after 12 o'clock in the evening, the user's profile may be considered to be late sleeping; if it is detected that the user often uses the game-like APP on the terminal, the user's hobby may be considered as playing the game; If it is detected that the user often spends more than 10 hours in the company, the user's profile may be considered to be overtime; if the user is frequently browsed for technology-related programs, web pages, news or posts, the user's hobby may be considered as technology; If it is detected that the user frequently browses military related programs, webpages, news or posts, the user's hobby is considered to be military; if the user is frequently browsed to the car-related programs, webpages, news or posts, the user's hobbies can be considered. For the car; if it is detected that the user frequently browses entertainment-related programs, web pages, news or posts, the user's hobby can be regarded as entertainment; if it is detected that the user's location information often appears in the tourist attraction, the user's hobby can be considered as Travel; if it is detected that the user buys more movie tickets on the terminal, it can be considered The user's hobby is a movie; if it is detected that the user purchases more books on the terminal, the user's hobby may be regarded as reading; if it is detected that the user purchases more clothing on the terminal, the user's hobby may be considered as wearing If it is detected that the sports app installed on the terminal is active, the user's hobby is considered to be sports.

Of course, the hobby/introduction predicted by the terminal or the server for the user may include one or more, and the embodiment of the present application does not impose any limitation on this.

When the terminal 1 displays Sam's profile, it can also use a specific tag to distinguish between the option that Sam fills in the profile and the option that the terminal automatically generates for Sam. As shown in Figure 13, the age of Sam in Sam's profile and the "late sleep" and "movie" in the hobby/introduction are automatically generated by the terminal, so the terminal can use different colors or logos to mark the age. And the "sleeping" and "movie" options in the hobby/introduction. In this way, Sam can quickly find and correct the option content generated by terminal 1 from his profile.

Further, after Sam sets his own personal information, the terminal 1 can send Sam's personal data to the server of the "friends" APP, and the server determines whether the Sam matches the first friend type set by other users according to the personal data set by Sam. In turn, Sam sends the result of the user's request in the form of a friend request or responds to the search of other users to the terminal of the corresponding user, so as to improve the success rate of the friend. Among them, Sam's friend request can include Sam's profile.

In addition, as shown in (a) of FIG. 14, the setting interface 401 of the "friends" APP may include the option of "Who sends a friend request to", and the user can set which type of user to enter after this option is entered. (This can be referred to as the second buddy type in this application) to send his own friend request.

As shown in (b) of FIG. 14, the second friend type in the "Who is sent a friend request" is similar to the first friend type in the "Who receives a friend request", and may also include the age option 1411. The embodiment of the present application does not impose any limitation on one or more of the gender option 1412, the academic option 1413, the graduate school option 1414, the career option 1415, the distance option 1416, and the hobby/introduction option 1417. Of course, Sam can also set up to allow friends to be sent to everyone.

The relationship between the respective options of the second friend type is “and”, and each setting condition in each option is an “or” relationship. For example, Sam selects the type "20-30" in the age option 1411, and selects the "communication" and "IT" types in the career option 1415, then the second friend type set by Sam is Users who are between "20-30" and whose occupation is in the "communication" or "IT" field indicate that Sam intends to make friends with this type of user.

Subsequently, the terminal 1 may send the above-mentioned second friend type set by Sam to the server of the “friends” APP for maintenance. When the server receives the personal data of other users uploaded by other terminals, the server may determine whether the personal data of the user satisfies the second friend type set by Sam, and when the personal data of the user meets the age between “20-30”, When the occupation is in the "communication" or "IT" field, the server can send Sam's friend request to the user's terminal.

Or, when the terminal 1 receives the personal data of other users sent by other terminals, the terminal 1 can determine whether the personal data of the user satisfies the second friend type set by Sam, and when the personal data of the user meets the age of "20" Between the -30" and the occupation is the "communication" or "IT" field, the terminal 1 can send Sam's friend request to the user's terminal.

In this way, after Sam sets the second friend type on the terminal 1, the terminal 1 can automatically send the Sam friend request to the user matching the second friend type, and then become friends with other users, that is, the user is not aware. In this case, you can request to be a friend with the specified user, which can improve the efficiency of making friends, and at the same time save the cumbersome setting of manually adding a friend each time.

At the same time, after the second friend type is set, only the user who meets the second friend type will receive the friend request of Sam, and the user who subsequently becomes a friend with Sam is also the user who receives the friend request of Sam, and therefore does not appear. Users who do not meet Sam's expectations send Sam's request to Sam to reduce the harassment caused to Sam.

In addition, when Sam sets the hobby/introduction option 1416 in the second friend type described above, Sam can specifically set to allow the friend request to be sent to the two users when the degree of similarity of the hobby/introduction is reached.

As shown in (a) of FIG. 15, the terminal 1 can preset a plurality of levels to show the similarity degree of the hobby/introduction between the two users, for example, when the level is "some chat", it indicates that when two users are When the similarity of the hobby/introduction is greater than 30%, Sam allows to send his friend request to the other party; when the rating is "like-minded", it means that when the similarity of the hobby/profile between the two users is greater than 60%, Sam allows Sending a friend request to the other party; when the rating is "Heart has a heart", it indicates that when the similarity of the hobby/profile between the two users is greater than 80%, Sam allows to send his friend request to the other party.

Then, Sam can set the similarity of the hobby/introduction between the two users by selecting different levels, and then The terminal 1 can determine whether to send Sam's friend request to the other party according to the similarity.

The hobbies/introduction similarities of the above 30%, 60%, and 80% are only examples, and those skilled in the art can set this according to actual experience or actual application scenarios. In addition, the specific embodiment of the present application does not limit the specific algorithm for calculating the similarity of the hobby/introduction between two users.

Alternatively, as shown in (b) of FIG. 15, Sam may also manually input the specific hobby/introduction of the friend he or she wants to make in the hobby/introduction option 1416, or select from a plurality of hobbies/introductions of the candidate. The specific hobbies/introductions of the friends you want to make, so that you can make friends with specific traits that the user wants.

Of course, when Sam sets the first friend type in "Who receives friend request", as shown in (b) of FIG. 5, if Sam selects the hobby/introduction option 4017, similar to FIG. 15, Sam also A friend request to receive a user that matches his hobby/profile can be further set.

That is to say, when using the dating function provided by the embodiment of the present application, according to the matching degree of the hobby/introduction between the two users, the friend request to receive another friend or the request of the friend can be sent to others, thereby improving the follow-up friends. The chance of success.

Then, when the server queries a user (such as Jean) that meets the second friend type set by Sam, the server can send Sam's friend request to Jean's terminal. When Sam's friend request contains Sam's profile, Jean can Further check out Sam's profile.

As shown in FIG. 16, when Sam's profile is displayed to other users, it is also possible to distinguish which of these hobbies/profiles are those that Sam himself fills out, and which are Sam's terminal 1 that is automatically generated by Sam. In this way, the user Jean who receives the Sam profile can use these identities to more fully understand the user Sam who sent the friend request.

In addition, when the terminal of Jean receives the personal data from Sam, if it is detected that the terminal of Jean is connected to the wearable device (for example, the head mounted electronic device shown in FIG. 16), the user is using the headset. The electronic device, then Jean's terminal can display the received Sam's personal information on the head-mounted electronic device, so as to promptly present the received personal data to Jean.

Of course, when any of the display interfaces in FIG. 4 to FIG. 15 is displayed, if the terminal 1 is detected to be connected to the wearable device, indicating that the user is using the wearable device, the terminal may send the display interface generated in real time to the display device. The display device is displayed on the wearable device. In addition, the wearable device can also be used as a terminal to implement the above-mentioned friendship function.

In some embodiments of the present application, the above-mentioned dating function provided by the "friends" APP may also have the function of setting the "receive friend request" shown in FIG. 5 to FIG. 13 and the functions shown in FIGS. 14 to 16. Set the "To whom to send friend request" feature. That is, the user may set a friend request to receive the user of the first friend type, and may also set to send a friend request to the second friend type user (the first friend type and the second friend type may be the same or different).

In this way, the user can send his friend request to the ideal receiving object, and receive the friend request of the user who meets the criteria for adding the friend. Then, after the double screening of the first friend type and the second friend type, "APP can help users better lock potential friends who meet the user's expectations in many friend requests, avoiding providing users with a large number of invalid friend requests that do not meet the user's expectations, causing harassment to users, and increasing the chances of successful friends.

In other embodiments of the present application, the user may also set which specific users to disclose their personal photos, age, occupation, and the like in the above-mentioned "friends" APP.

Exemplarily, as shown in (a) of FIG. 18, after Sam enters the "friends" APP, he can select the option of "open to whom to open profile" in its setting interface, thereby setting which user is open to read. The rights to their profile (which can be referred to as the third friend type in this application).

As shown in (b) of FIG. 18, the third friend type in the above “Who is open to the profile” may specifically include an age option, a gender option, a qualification option, a graduate institution option, a career option, and a distance option with itself. And one or more of the hobby/introduction options. Of course, Sam can also set the right to open the reading of his personal data to everyone, and the embodiment of the present application does not impose any restrictions on this.

The relationship between each option in the third friend type is “and”, and each setting condition in each option is an “or” relationship.

Then, if the friend request sent by Sam to other people is associated with Sam's profile, then if the user who receives the Sam friend request meets the above-mentioned third friend type, the user has the right to view Sam's profile.

For example, Sam sets a friend request for Sam to a second friend type whose age is "20-30", whose academic qualification is "undergraduate" and whose occupation is "IT, communication" in the setting interface shown in FIG. In the setting interface shown in FIG. 18, Sam sets the third friend type only to the age of "20-30", the academic degree is "undergraduate", the occupation is "IT, communication" field, and the hobby is "sports". Users open their profiles. Then, among the one or more users who receive the Sam friend request, only when the user meets the third friend type described above, the friend associated with Sam can be requested from Sam's friend, thereby preventing the user's personal data from being inconsistent. Expected people to view.

Of course, the terminal 1 can also send Sam's personal data as independent data to users who only meet the above-mentioned third friend type. Alternatively, the server will send Sam's profile as independent data to users who only meet the third buddy type described above.

For example, as shown in (b) of FIG. 18, the third friend type set by Sam is age "20-30", education is "undergraduate", occupation is "IT, communication" field and hobby is " "Mobile" users. The terminal 1 can send Sam's profile and the third friend type set by Sam to the server. Then, when other users (such as Mike) use the "dating friend" app to shake or nearby people, the terminal can take the initiative. Ask the server to get Sam's profile.

However, since Sam presets the third friend type of the open profile, the server can determine whether the Mike conforms to the third friend type according to the third friend type set by Sam. If Mike matches the third friend type, the server may send Sam's photo, nickname and other personal data to Mike's terminal for display; if Mike does not meet the above third friend type, then Mike does not have permission to access Sam's profile. Then, the personal data returned by the server to Mike's terminal will not include Sam's photos, nicknames and other personal data, so that Sam's personal data is not seen by users who do not meet Sam's expectations.

Of course, the above-mentioned dating function provided by the "friends" APP can also have the function of setting the above "to whom to open the personal data", setting the "reception of who's friend request", and setting the "to whom to send the friend request" function. There are no restrictions on this.

It can be understood that, in order to implement the above functions, the above terminal and the like include hardware structures and/or software modules corresponding to each function. Those skilled in the art will readily appreciate that the embodiments of the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the embodiments of the present application.

The embodiment of the present application may perform the division of the function modules on the terminal or the like according to the foregoing method example. For example, each function module may be divided according to each function, or two or more functions may be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.

FIG. 19 is a schematic diagram showing a possible structure of a terminal involved in the foregoing embodiment, where the terminal includes: an obtaining unit 1901, a display unit 1902, a processing unit 1903, and Transmitting unit 1904.

The obtaining unit 1901 is configured to: receive a first friend type set for the first user; receive a friend request from the second user, the second user belongs to the first friend type; and receive a friend request from the third user, The third user does not belong to the first friend type; the display unit 1902 is configured to: display the friend request of the second user in the first interface; and the processing unit 1903 is configured to: not display the friend request of the third user in the first interface.

Further, the sending unit 1904 is configured to: send the first friend type to the server, so that the server determines, for the first user, at least one user belonging to the first friend type.

Further, the second user's friend request may include the second user's personal information, the second user's personal information satisfies the first friend type, and the third user's friend request includes the third user's personal data, and the third user The profile does not satisfy the first friend type. At this time, the processing unit 1903 is further configured to: select, according to the personal data of the second user and the personal data of the third user, the second user that belongs to the first friend type.

Further, the processing unit 1903 is further configured to: prompt the first user to add the fourth user as a friend, where the fourth user belongs to the first friend type, and the first terminal and the second terminal of the fourth user The distance between them is less than the threshold.

Further, the friend request of the second user may be associated with the profile of the second user; the acquiring unit 1901 is further configured to: acquire a first operation of the friend request input by the first user to the second user; The display unit 1902 is further configured to: display the personal data of the second user.

Further, the display unit 1902 is further configured to: display a friend request of the third user on the second interface.

Further, the acquiring unit 1901 is further configured to: acquire a second operation that the first user requests the friend input of the third user; the processing unit 1903 is further configured to: modify the first friend type, so that the third user belongs to the modified The first friend type.

Further, the obtaining unit 1901 is further configured to: receive a second friend type set for the first user; the sending unit 1904 is further configured to: send a second friend type to the server, so that the server sends the message to the fifth user The friend of the first user requests that the fifth user belongs to the second friend type.

Further, the obtaining unit 1901 is further configured to: receive a third buddy type set for the first user; the sending unit 1904 is further configured to: send a third buddy type to the server, so that the server sends the third buddy to the sixth user Sending the personal data of the first user, the sixth user belongs to the third friend type.

Correspondingly, FIG. 20 shows a possible structural diagram of a server involved in the foregoing embodiment, and the server includes: an obtaining unit 2001, a processing unit 2002, and a sending unit 2003.

The obtaining unit 2001 is configured to: receive a first user's personal data sent by the first terminal, and a friend type set for the first user; obtain a first request for the second user to query the first user's personal data, and the second user And the second user requesting the third user to query the second user's personal data, the third user does not belong to the friend type; the sending unit 2003 is configured to: send the first user to the second user of the second user The personal data; the processing unit 2002 is configured to: not respond to the second request.

Further, the obtaining unit 2001 is further configured to: obtain a third request for the first user to query the personal data of the fourth user; and the processing unit 2002 is further configured to: determine whether the first user belongs to the friend type set by the fourth user If the first user belongs to the buddy type set by the fourth user, the sending unit 2003 is further configured to: send the fourth user's personal profile to the first terminal; if the first user does not belong to the buddy type set by the fourth user The processing unit 2002 is further configured to: not respond to the third request.

All the related content of the steps involved in the foregoing method embodiments may be referred to the functional descriptions of the corresponding functional modules, and details are not described herein again.

In the case of using an integrated unit, as shown in FIG. 21, a possible structural diagram of the terminal involved in the above embodiment is shown, including a processing module 2101, a communication module 2102, an input/output module 2103, and a storage. Module 2104.

The processing module 2101 is configured to control and manage the action of the terminal. The communication module 2102 is configured to support communication between the terminal and other network entities. The input/output module 2103 is for receiving information input by a user or outputting information provided to the user and various menus of the terminal. The storage module 2104 is configured to save program codes and data of the terminal.

Exemplarily, the related functions implemented by the processing unit 1903 described above may be integrated into the processing module 2101, and the related functions of implementing the interaction with the user in the obtaining unit 1901, the display unit 1902, and the sending unit 1904 may be integrated into the input/output module 2103. The related functions of the acquisition unit 1901 and the transmission unit 1904 that implement interaction with other terminals or servers are integrated into the communication module 2102.

In the case of the integrated unit, as shown in FIG. 22, a possible structural diagram of the server involved in the above embodiment is shown, including a processing module 2201, a communication module 2202, and a storage module 2203.

The processing module 2201 is configured to control and manage the actions of the server. The communication module 2202 is for supporting communication between the server and other servers or terminals. The storage module 2203 is configured to save program code and data of the server.

Exemplarily, the related functions implemented by the processing unit 2002 can be integrated into the processing module 2201, and the related functions of the above-mentioned obtaining unit 2001 and the transmitting unit 2003 for realizing interaction with the terminal or other servers are integrated into the communication module 2202.

Specifically, the processing module 210 1/2201 may be a processor or a controller, and may be, for example, a central processing unit (CPU), a GPU, a general-purpose processor, and a digital signal processor (DSP). Application-Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It can be implemented or executed in conjunction with the disclosure of the present application. Various exemplary logical blocks, modules and circuits are described. The processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.

The above communication module 2102/2202 may be a transceiver, a transceiver circuit, or a communication interface or the like. For example, the communication module 1303 may specifically be a Bluetooth device, a Wi-Fi device, a peripheral interface, or the like.

The above-described input/output module 2103 may be a touch screen, a display, a microphone, or the like that receives information input by a user or outputs information provided to a user. Taking the display as an example, the display may be configured in the form of a liquid crystal display, an organic light emitting diode or the like. In addition, a touch panel can be integrated on the display for collecting touch events on or near the display, and transmitting the collected touch information to other devices (such as a processor, etc.).

The above memory modules 2104/2203 may be memories, which may include high speed random access memories (RAM), and may also include nonvolatile memories such as magnetic disk storage devices, flash memory devices, or other volatile solid state storage devices.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it may occur in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present application should be covered by the scope of the present application. . Therefore, the scope of protection of the present application should be determined by the scope of the claims.

Claims

A method of making friends, characterized in that it comprises:

Receiving, by the first terminal, a first friend type set for the first user;

The first terminal receives a friend request from a second user, and the second user belongs to the first friend type;

The first terminal displays a friend request of the second user on the first interface;

The first terminal receives a friend request from a third user, and the third user does not belong to the first friend type;

The first terminal does not display the friend request of the third user in the first interface.
The method according to claim 1, wherein the first friend type comprises: age, gender, education, graduate school, occupation, hobby/introduction, blood type, height, weight, constellation, hometown, marriage situation, At least one of an address, and a distance from the first user.
The method according to claim 1 or 2, wherein after the first terminal receives the first friend type set for the first user, the method further includes:

The first terminal sends the first friend type to the server, so that the server determines, for the first user, at least one user belonging to the first friend type.
The method according to any one of claims 1 to 3, wherein the second user's friend request includes the second user's personal information, and the second user's personal information satisfies the first a friend type, the friend request of the third user includes the personal data of the third user, and the personal data of the third user does not satisfy the first friend type, and the method further includes:

The first terminal filters out the second user belonging to the first friend type according to the personal data of the second user and the personal data of the third user.
The method according to any one of claims 1-4, wherein after the first terminal receives the first friend type set for the first user, the method further includes:

The first terminal prompts the first user to add a fourth user as a friend, where the fourth user belongs to the first friend type, and the first terminal and the second terminal of the fourth user The distance between them is less than the threshold.
The method according to any one of claims 1 to 5, wherein the first terminal displays a friend request from the second user, including:

The first terminal displays a prompt for receiving a friend request of the second user in a lock screen interface, a pull-down menu, a pull-up menu, a negative screen menu, a notification bar, or a desktop.
The method according to any one of claims 1 to 6, wherein the friend request of the second user is associated with the profile of the second user;

After the first terminal displays the friend request from the second user, the method further includes:

The first terminal displays the personal data of the second user in response to the first operation of the first user requesting input by the friend of the second user.
The method according to any one of claims 1 to 7, wherein after the first terminal receives the friend request from the third user, the method further includes:

The first terminal displays the friend request of the third user on the second interface.
The method according to claim 8, wherein after the first terminal displays the friend request of the third user in the second interface, the method further includes:

In response to the second operation of the first user requesting input by the friend of the third user, the first terminal modifies the first friend type such that the third user belongs to the modified first friend type.
The method of any of claims 2-9, wherein the first friend type comprises the hobby/introduction option,

The hobby/introduction option is set to: a similarity of the hobby/profile between the first user and the user belonging to the first buddy type.
The method according to any one of claims 1 to 10, wherein the method further comprises:

Receiving, by the first terminal, a second friend type set for the first user;

The first terminal sends the second friend type to the server, so that the server sends the friend request of the first user to the fifth user, and the fifth user belongs to the second friend type.
The method according to any one of claims 1 to 11, wherein the method further comprises:

Receiving, by the first terminal, a third friend type set for the first user;

The first terminal sends the third friend type to the server, so that the server sends the first user's personal profile to the sixth user, and the sixth user belongs to the third friend type.
A method of making friends, characterized in that it comprises:

Receiving, by the server, the personal data of the first user sent by the first terminal and the type of the friend set for the first user;

Obtaining, by the server, a first request for the second user to query the personal data of the first user, the second user belongs to the friend type; and in response to the first request, the server is to the second user Transmitting, by the second terminal, the personal data of the first user;

The server acquires a second request for the third user to query the personal data of the first user, the third user does not belong to the friend type; the server does not respond to the second request.
The method of claim 13 wherein the method further comprises:

Obtaining, by the server, a third request that the first user queries the personal data of the fourth user;

If the first user belongs to the buddy type set by the fourth user, the server sends the personal data of the fourth user to the first terminal;

If the first user does not belong to the friend type set by the fourth user, the server does not respond to the third request.
The method according to claim 13 or 14, wherein the friend type comprises: age, gender, education, graduate school, occupation, hobby/introduction, blood type, height, weight, constellation, hometown, marriage situation, At least one of an address, and a distance from the first user.
A terminal, comprising:

An obtaining unit, configured to: receive a first friend type set for the first user; receive a friend request from the second user, the second user belongs to the first friend type; and receive a friend request from the third user, The third user does not belong to the first friend type;

a display unit, configured to: display a friend request of the second user on the first interface;

The processing unit is configured to: not display the friend request of the third user in the first interface.
A server, comprising:

An acquiring unit, configured to: receive a first user's personal data sent by the first terminal, and a friend type set for the first user; and obtain a first request for the second user to query the first user's personal data, The second user belongs to the friend type; and obtains a second request for the third user to query the personal data of the first user, where the third user does not belong to the friend type;

a sending unit, configured to: send, to the second terminal of the second user, the personal data of the first user;

a processing unit, configured to: not respond to the second request.
A terminal, comprising: a processor, a display, a memory, a bus, and a communication interface;

The memory is configured to store a computer execution instruction, the processor is connected to the memory through the bus, and when the terminal is running, the processor executes the computer execution instruction stored in the memory to make The terminal performs the dating method according to any one of claims 1-12.
A server, comprising: a processor, a memory, a bus, and a communication interface;

The memory is configured to store a computer execution instruction, the processor is connected to the memory through the bus, and when the server is running, the processor executes the computer execution instruction stored in the memory to make The server performs the dating method according to any one of claims 13-15.
A computer readable storage medium having stored therein instructions, wherein when the instructions are run on a terminal, causing the terminal to perform as claimed in any one of claims 1-12 The method of making friends.
A computer readable storage medium having stored therein instructions, wherein when the instructions are run on a server, causing the server to perform as claimed in any one of claims 13-15 The method of making friends.