CN111262780A - User type limiting application method in instant messaging, client, terminal, device, server and storage medium - Google Patents

User type limiting application method in instant messaging, client, terminal, device, server and storage medium Download PDF

Info

Publication number
CN111262780A
CN111262780A CN202010120962.6A CN202010120962A CN111262780A CN 111262780 A CN111262780 A CN 111262780A CN 202010120962 A CN202010120962 A CN 202010120962A CN 111262780 A CN111262780 A CN 111262780A
Authority
CN
China
Prior art keywords
user information
application
user
information type
sub
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
Application number
CN202010120962.6A
Other languages
Chinese (zh)
Other versions
CN111262780B (en
Inventor
胡桂标
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Yunyu Intelligent Technology Co ltd
Original Assignee
Shanghai Yunyu Intelligent Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shanghai Yunyu Intelligent Technology Co ltd filed Critical Shanghai Yunyu Intelligent Technology Co ltd
Priority to CN202010120962.6A priority Critical patent/CN111262780B/en
Publication of CN111262780A publication Critical patent/CN111262780A/en
Application granted granted Critical
Publication of CN111262780B publication Critical patent/CN111262780B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H04L12/1822—Conducting the conference, e.g. admission, detection, selection or grouping of participants, correlating users to one or more conference sessions, prioritising transmission
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/52—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail for supporting social networking services

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The invention relates to the field of instant messaging, and discloses a user type limiting application method, a client, a terminal, a device, a server and a storage medium in instant messaging, wherein the method comprises the following steps: presetting a user information type limiting sub-application in an instant messaging application program; acquiring a trigger instruction of a user to the child application; displaying at least one user information type restriction mark for selection; or sending a request for starting the sub-application to the server, and receiving and displaying at least one user information type limiting identifier; obtaining a selection result of the user information type limitation identifier, and sending a request for running the sub-application to a server; and if the feedback information or the operation instruction for operating the sub-application is received, operating the sub-application. The communication environment, particularly the business communication environment, of a specific scene is created for the user through the user type limiting application preset in the communication tool, so that the communication requirement under a specific background is met, and the communication efficiency among the users is greatly improved.

Description

User type limiting application method in instant messaging, client, terminal, device, server and storage medium
Technical Field
The invention relates to the field of instant messaging, in particular to a user type limitation application method, a client, a terminal, a device, a server and a storage medium in instant messaging.
Background
Currently, instant messaging tools have become essential application tools in work, study and life of people. Because the communication of the text, the voice and the picture information is carried out by utilizing the secondary telecommunication channel of the network, the communication cost of the user is greatly reduced. Different instant messaging tools are widely used for different target groups due to different market positioning, such as WeChat, QQ, strange feeling, pulse, and the like.
At present, popular application scenes are generally divided into social contact among acquaintances with WeChat, social contact among strangers with strangers, and social contact among workplaces which are biased to real-name authentication pulse veins and the like. But only one type of user information is set therein, regardless of what type of social interaction its location is with. The user carries out information remark description on the concerned user through remark, or carries out real identity description through self real-name authentication, and in the whole application, the embodiment is only one user information type. Of course, in order to distinguish users, in most applications users are usually divided and labeled by the function of user grouping. In the sub-applications included in these applications, user information is not managed separately.
However, in the real world, there are different social needs. The need of real name and real identity is emphasized for employment sites and business activities, while in private life, social needs for ensuring personal privacy exist, private users have the need of protecting privacy when in private shopping or communicating with organizations, and real identity information needs to be provided for companies or organizations or sellers, so that trustworthy user information is displayed for the private users. At present, a single user type of an instant messenger in the market cannot guarantee instant communication in a multi-scene environment, and cannot meet different privacy protection requirements of different users in the same communication occasion.
Disclosure of Invention
The purpose of the invention is as follows: aiming at the problems in the prior art, the invention provides a user type limiting application method, a client, a terminal, a device, a server and a storage medium in instant messaging, which can create a communication environment with a specific scene, particularly a business communication environment for a user by limiting application of a user type preset in a communication tool, meet the communication requirements under a specific background and greatly improve the communication efficiency among users.
The technical scheme is as follows: the invention provides a using method of multi-scene application of an instant messaging tool, which comprises the following steps: s1: presetting a user information type limiting sub-application in an installed instant messaging application program; wherein the user information type limit sub-application is an application program which runs by depending on the instant messaging application program; the user information type limiting sub-application limits the user information types and/or user information data related to the user information types displayed, viewed, inquired or inquired in the participating terminal users after the user information type sub-application is operated; the same terminal user in the instant communication application program has at least two user information types, each user information type limits the sub-application to be associated with different user information types after running, and each user information type is associated with the user information data which are not completely the same for the same terminal user; s2: acquiring a trigger instruction of a terminal user to the user information type limiting sub-application; s3: displaying at least one user information type restriction identifier for selection by an end user; or, sending a request for starting the user information type limitation sub-application to a server, and receiving and displaying at least one user information type limitation identifier selected by the terminal user; s4: acquiring a selection result of the user information type limitation identifier by the terminal user, and sending a request for running the user information type limitation sub-application to a server; s5: and if receiving feedback information or an operation instruction sent by the server for operating the user information type limiting sub-application, operating the user information type limiting sub-application.
Further, in S4, after obtaining the result of selecting the user information type restriction identifier by the end user, before sending the request for running the user information type restriction sub-application to the server, the method further includes the following steps: and judging whether the request meets a preset condition, and if so, sending the request to a server.
Preferably, the preset conditions are: whether the number of the contact person identifications selected by the terminal user meets the number requirement of starting and running the user information type limiting sub-application or not; or whether the contact corresponding to the contact identification selected by the terminal user really exists or not; or whether the contact corresponding to the contact identification selected by the terminal user agrees to participate in the user information type definition sub-application or not.
Further, in S4, after obtaining the result of selecting the user information type restriction identifier by the end user and before sending the request for starting the user information type restriction sub-application to the server, at least two contact identifiers selected by the end user are also displayed, and the result of selecting the contact identifier by the end user is obtained.
Further, in S5, after receiving the feedback information or the start instruction and before starting and running the user information type defining sub-application, at least two contact identifiers selected by the end user are also displayed, and a selection result of the end user on the contact identifiers is obtained.
Preferably, the contact identification is a contact identification consistent with the user information type associated with the user information type defining sub-application.
Preferably, the same end user only stores one user information type of another end user and/or user information data associated with the user information type at the same time.
Preferably, after the user information type definition sub-application is run, all terminal users participating in the user information type definition sub-application can present, view, query, browse and/or download therein the user information types of other participating terminal users and/or the user information data associated with the user information types.
The invention also provides a client, comprising: the first display module is used for displaying a label of the user information type definition sub-application at the client; the first acquisition module is used for acquiring a trigger instruction of a terminal user to the user information type limiting sub-application; the second display module is used for displaying at least two user information type limit identifications for the terminal user to select; a second obtaining module, configured to obtain a selection result of the user information type restriction identifier by the terminal user; a sending module, configured to send, to a server, a request to start the sub-application of the user information type restriction after the second obtaining module obtains the selection result of the user information type restriction identifier; the receiving module is used for receiving feedback information or a starting instruction which is sent by the server and accords with the preset condition for starting the user information type limiting sub-application; and the starting module is used for starting and running the user information type limiting sub-application after the receiving module receives the feedback information or the starting instruction that the user information type limiting sub-application meets the preset starting condition.
Further, the client further comprises: and the judging module is used for judging whether the request meets a preset condition or not before the sending module sends the request for starting the sub-application of the user information type limitation to the server after the second obtaining module obtains the selection result of the user information type limitation identifier.
Further, the client further comprises: the storage module is used for storing the contact information; in the storage module, the same terminal user only stores one user information type of another terminal user and/or user information data related to the user information type at the same time.
Further, the client further comprises: the third display module is used for displaying at least two contact person identifications for the terminal user to select after the second acquisition module acquires the selection result of the terminal user on the user information type limitation identification and before the sending module sends the request for starting the user information type limitation sub-application to the server; a third obtaining module, configured to obtain a result of selecting the contact identifier by the end user after the third displaying module displays at least two types of contact identifiers for the end user to select and before the sending module sends the request for starting the user information type limitation sub-application to the server.
Further, the client further includes: the fourth display module is used for displaying the contact person identification which can be selected by the terminal user after the receiving module receives the feedback information or the starting instruction and before the starting module starts and runs the user information type limiting sub-application; and the fourth acquisition module is used for acquiring the selection result of the terminal user on the contact person identifier after the fourth display module displays the contact person identifier and before the starting module starts and runs the user information type limiting sub-application.
Further, the client further includes a presentation module, a viewing module, a query module, a browsing module and/or a downloading module, configured to enable all terminal users participating in the user information type definition sub-application to present, view, query, browse and/or download user information types of other participating terminal users and/or user information data associated with the user information types therein after the starting module runs the user information type definition sub-application.
The invention also provides a terminal, which comprises a memory, a processor and the client, wherein the memory is used for storing the relevant programs and instructions of the client, and the processor is used for executing the steps of the method and running the relevant programs and instructions of the client.
The present invention also provides an apparatus comprising: the receiving module is used for receiving a request for starting the user information type limiting sub-application sent by the terminal; and the sending module is used for sending feedback information or a starting instruction whether the user information type limiting sub-application is started or not to the terminal.
Further, the device further comprises a judging module, configured to judge whether the user information type definition sub-application meets a preset condition for starting.
The present invention also provides a server, comprising: a processor and a memory; the memory is used for storing relevant programs and instructions of the device, and the processor is used for executing the instructions of the device.
The present invention also provides a non-transitory computer readable storage medium, wherein the instructions of the storage medium, when executed by a processor of a server, enable the server to execute or run the above apparatus.
Has the advantages that: aiming at the problems in the prior art, the invention provides a user type limiting application method, a client, a terminal, a device, a server and a storage medium in instant messaging, which can create a communication environment with a specific scene, particularly a business communication environment for a user by limiting application of a user type preset in a communication tool, meet the communication requirements under a specific background and greatly improve the communication efficiency among users.
Drawings
Fig. 1 is a flowchart of a user type restriction application method in instant messaging according to embodiment 1;
fig. 2 is a concrete case diagram illustrating a user type definition application method in instant messaging according to embodiment 1;
fig. 3 is a flowchart of a user type restriction application method in instant messaging according to embodiment 2;
fig. 4 is a flowchart of a user type restriction application method in instant messaging according to embodiment 3;
fig. 5 is a concrete case diagram of the user type definition application method in instant messaging according to embodiment 3;
fig. 6 is a flowchart of a user type restriction application method in instant messaging according to embodiment 4;
fig. 7 is a concrete case diagram of the user type definition application method in instant messaging according to embodiment 4; fig. 8 is a flowchart of a user type restriction application method in instant messaging according to embodiment 5;
fig. 9 is a block diagram of a user type definition application client in instant messaging according to embodiment 6;
fig. 10 is a block diagram of a user type definition application client in instant messaging according to embodiment 7;
fig. 11 is a block diagram of a user type definition application client in instant messaging according to embodiment 8;
fig. 12 is a block diagram showing a user type definition application client in the instant messaging according to embodiment 9;
fig. 13 is a block diagram of a user type definition application client in the instant messaging according to embodiment 10;
fig. 14 is a block diagram of a terminal of a user type definition application in instant messaging according to embodiment 11;
fig. 15 is a block diagram showing an apparatus for user type definition application in instant messaging according to embodiment 12;
fig. 16 is a block diagram showing an apparatus for user type definition application in instant messaging according to embodiment 13;
fig. 17 is a block diagram of a server for a user type definition application in instant messaging according to embodiment 14.
Detailed Description
The present invention will be described in detail with reference to the accompanying drawings.
Embodiment 1:
the embodiment provides a user type limited application method in instant messaging, which comprises the following steps, and the flow chart is as shown in figure 1:
s1: presetting a user information type limiting sub-application in an installed instant messaging application program;
the sub-application is an application program running depending on an instant messaging application program; the user information type limiting sub-application limits the participating terminal users to display, view, inquire or inquired user information types and/or user information data related to the user information types after the user information type sub-application is operated; the same terminal user in the instant communication application program has at least two user information types, each user information type limits that the sub-application is associated with different user information types after running, and each user information type is associated with the user information data which are not completely the same for the same terminal user; the same end user stores only one user information type of another end user and/or user information data associated with the user information type at the same time.
S2: acquiring a trigger instruction of a terminal user for a user information type limiting sub-application;
s3: displaying at least one user information type restriction identifier for selection by an end user;
s4: acquiring a selection result of a terminal user on a user information type limitation identifier, and sending a request for running a user information type limitation sub-application to a server;
s5: and if receiving feedback information or an operation instruction sent by the server for operating the user information type limiting sub-application, operating the user information type limiting sub-application.
After the user information type definition sub-application is operated, all terminal users participating in the user information type definition sub-application can display, view, query, browse and/or download the user information types of other participating terminal users and/or the user information data associated with the user information types.
The present embodiment will be described more specifically below with reference to a specific example:
referring to fig. 2, two user information types, i.e., a friend information type and a friend information type, are set in the instant messenger. The system is characterized in that a 'creating blog' sub-application is further arranged, the blog of the business friend is used for information of posts, businesses, society and the like issued by instant messaging users and user evaluation and discussion concerning the information, the creator is required to be created according to the user information type identity of the business friend, and after the creation, the user information of the information type of the business friend of the creator is displayed and browsed by the business friend of the creator. And the friend blog is used for the instant messaging user to release life, private, family and other life trends and information and for the friend to browse and watch. The method comprises the steps that a user triggers a control for creating a blog in a terminal interface, the terminal interface pops up two controls of a friend and a friend, the terminal user triggers a commercial control, an instant communication tool obtains an instruction for creating the friend blog of the user, instant communication (a client) sends a request to a server, the server judges whether the request user fills in the requirement including name, unit, job or real-name system authentication according to a preset requirement, if the requirement is met, an instruction for starting the creation of the friend and the blog is sent to the client, the client starts the creation work after receiving the instruction sent by the server, and a page for writing the friend and the blog is displayed on a user terminal. If the requesting user only fills in a nickname, does not fill in a name, an organization, a post or is not authenticated by a real name system, the method receives 'your creator friend blog, and needs to fill in effective information such as your real name, organization, post and the like in personal data' sent by a server.
When the user finishes content editing and sending to the server and finishes creating the friend blog, all users who can browse the blog content can check the user information corresponding to the user information type of the friend user of the user. Meanwhile, when the users participating in the comment submit the comment to the blog, the server also judges whether the content in the user data associated with the information type of the friends and the traders meets the requirement, if not, the comment users receive the requirement for requesting to fill in the information data of the friends and the traders, and if so, the comment is published in the blog.
The remaining users can view the information of the business friends of the rating users who comment on the blog.
Embodiment 2:
this embodiment is substantially the same as embodiment 1, and is different in that in S3, a request for starting a user information type restriction sub-application is transmitted to the server, and at least one user information type restriction flag to be selected by the end user is received and displayed. As shown in fig. 3.
For example, also in the example of embodiment 1, after the user triggers the control of "create blog" in the terminal interface, the client first sends the request to the server, after the server sends the two user information type restriction sub-applications of the available friend and friend to the client, the server sends the user information type restriction sub-application that can be used to the client according to the preset judgment, and the client pops up the two controls of "friend and friend" on the terminal interface.
Otherwise, this embodiment is identical to embodiment 1, and will not be described herein.
Embodiment 3:
as shown in fig. 4, in embodiment 2, after obtaining a result of selecting the user information type restriction identifier by the end user, it is further determined whether a request to send a request to the server to run the user information type restriction sub-application meets a preset condition, and if so, the request to run the user information type restriction sub-application is sent to the server.
The preset conditions are as follows:
whether the number of the contact person identifications selected by the terminal user meets the number requirement of starting and operating the user information type limiting sub-application or not; contact identification means information such as a nickname, name, or avatar of the contact.
The present embodiment will be described more specifically below with reference to a specific example:
presetting a friend group chat creating application and a friend group chat creating application in software of the mobile phone for creating the group chat, as shown in figure 5, triggering an instruction of creating the group chat by a user A, as shown in figure 5a, after receiving the triggering instruction, the client displays the mark of creating friend group chat application and creating friend group chat application for user A to select, as shown in fig. 5b, after the selection result of the user a for creating the buddy group chat application is obtained, it is first determined whether the request for operating the buddy group chat application to be sent to the server meets a preset condition, if the buddy group chat needs to have at least 2 buddy contacts, if only one or no business friend contact persons exist, the number of business friend contact persons is not up to the condition of creating the business friend group chat, the function cannot be used, the prompt information shown in the figure 5c is displayed, and a request for creating the business friend group chat is not sent to the server. And if the chat request is matched with the chat request, sending a request for starting the friend group chat application to the server.
Otherwise, this embodiment is identical to embodiment 2, and will not be described herein.
Embodiment 4:
the present embodiment is a further improvement of embodiment 3, and is mainly improved in that, as shown in fig. 6, in S4, after obtaining a selection result of the user information type restriction identifier by the end user, at least two contact identifiers for the end user to select are displayed first, and the selection result of the contact identifier by the end user is obtained, and then it is determined whether a request to send a request to the server to run the user information type restriction sub-application meets a preset condition, and if so, a request to start the user information type restriction sub-application is sent to the server.
For example, as an example in embodiment 3, after obtaining the selection result of the user a for creating the buddy group chat application, as shown in fig. 7, information such as nicknames, names, or head portraits of chenlili, sundao, and Zhujie is displayed, the selection result of the terminal user for chenlili, sundao, and Zhujie is obtained, it is determined whether the request for starting the buddy group chat application to be sent to the server meets the preset condition, and if so, a request for starting the buddy group chat application is sent to the server.
Otherwise, this embodiment is completely the same as embodiment 3, and will not be described herein.
Embodiment 5:
the present embodiment is a further improvement of embodiment 4, and the main improvement is that, as shown in fig. 8, in the present embodiment, after receiving the feedback information or the operation instruction and before operating the user information type limiting sub-application, at least two contact identifiers selected by the end user are displayed, and a selection result of the end user for the contact identifiers is obtained.
The present embodiment will be described more specifically below with reference to a specific example:
also as an example in embodiment 4, after obtaining the selection result of the user information type restriction identifier by the end user, instead of displaying the nicknames or head portraits of chenoli, grand mahogany, and pig sika that can be selected by the user a, and obtaining the selection result of the user a for chenoli, grand mahogany, and pig sika, a request for starting the buddy group chat application is directly sent to the server; and after the client of the user A receives an operation instruction sent by the server for starting the friend group chat sub-application, displaying the nicknames or head portraits of Chenalice, Sunday and Zhujie which can be selected by the user A, acquiring the selection results of the user A on Chenalice, Sunday and Zhujie, and then starting and operating the friend group chat sub-application. Compared with the embodiment 4, the method emphasizes the prior judgment of the server on the user identity for starting the application, saves the network flow and is also beneficial to reducing the unnecessary calculation amount of the server.
Otherwise, this embodiment is completely the same as embodiment 4, and will not be described herein.
Embodiment 6:
the present embodiment provides a client, as shown in fig. 9, including:
the first display module is used for displaying a label of the user information type definition sub-application at the client;
the first acquisition module is used for acquiring a trigger instruction of a terminal user for the user information type limiting sub-application;
the second display module is used for displaying at least two user information type limit identifications for the terminal user to select;
the second acquisition module is used for acquiring a selection result of the user information type limitation identifier by the terminal user;
the sending module is used for sending a request for starting the user information type limiting sub-application to the server after the second obtaining module obtains the selection result of the user information type limiting identifier;
the receiving module is used for receiving feedback information or a starting instruction which is sent by the server and accords with the preset condition for starting the user information type limiting sub-application;
and the starting module is used for starting and running the user information type limiting sub-application after the receiving module receives the feedback information or the starting instruction that the user information type limiting sub-application meets the preset starting condition.
The display module, the viewing module, the query module, the browsing module and/or the downloading module are used for enabling all terminal users participating in the user information type limiting sub-application to display, view, query, browse and/or download user information types of other participating terminal users and/or user information data associated with the user information types after the starting module runs the specific user information type limiting sub-application.
Embodiment 7:
the present embodiment is a further improvement of embodiment 6, and the main improvement is that, as shown in fig. 10, the client in the present embodiment further includes a storage module, configured to store contact information; the same end user stores only one user information type of another end user and/or user information data associated with the user information type at the same time.
Otherwise, this embodiment is completely the same as embodiment 6, and will not be described herein.
Embodiment 8:
the present embodiment is a further improvement of embodiment 6, and a main improvement is that, as shown in fig. 11, the client in this embodiment further includes a determining module, configured to determine whether the request meets a preset condition after the second obtaining module obtains the selection result of the user information type restriction identifier and before the sending module sends the request for starting the user information type restriction sub-application to the server.
Otherwise, this embodiment is completely the same as embodiment 5, and will not be described herein.
Embodiment 9:
this embodiment is a further improvement of embodiment 6, and the main improvement is that, as shown in fig. 12, the client in this embodiment further includes:
the third display module is used for displaying at least two contact person identifications for the terminal user to select after the second acquisition module acquires the selection result of the terminal user on the user information type limitation identification and before the sending module sends a request for starting the user information type limitation sub-application to the server;
and the third acquisition module is used for acquiring the selection result of the terminal user on the contact person identification after the third display module displays at least two contact person identifications for the terminal user to select and before the sending module sends a request for starting the user information type limiting sub-application to the server.
Otherwise, this embodiment is completely the same as embodiment 6, and will not be described herein.
Embodiment 10:
this embodiment is a further improvement of embodiment 6, and the main improvement is that, as shown in fig. 13, the client in this embodiment further includes:
the fourth display module is used for displaying the contact person identification which can be selected by the terminal user after the receiving module receives the feedback information or the starting instruction and before the starting module starts and runs the user information type limiting sub-application;
and the fourth acquisition module is used for acquiring the selection result of the terminal user on the contact person identifier after the contact person identifier is displayed by the fourth display module and before the starting module starts and runs the user information type limiting sub-application.
Otherwise, this embodiment is completely the same as embodiment 6, and will not be described herein.
Embodiment 11:
this embodiment provides a terminal, which includes a memory, a processor, and a client as described in embodiments 6 to 10, where the memory is used to store relevant programs and instructions of the client, and the processor is used to execute the method steps as described in embodiments 1 to 5 and run the relevant programs and instructions of the client.
As shown in fig. 14, the terminal 900 can be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.
Referring to fig. 14, terminal 900 can include one or more of the following components: processing components, memory 904, power components 906, multimedia components 908, audio components 910, input/output (I/O) interfaces 912, sensor components 914, and communication components 916. Processing component 902 generally controls overall operation of terminal 900, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. Processing component 902 may include one or more processors 920 to execute instructions to perform all or a portion of the steps of the methods described above. Further, processing component 902 can include one or more modules that facilitate interaction between processing component 902 and other components. For example, the processing component 902 can include a multimedia module to facilitate interaction between the multimedia component 908 and the processing component 902.
Memory 904 is configured to store various types of data to support operation at terminal 900. Examples of such data include instructions for any application or method operating on terminal 900, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 904 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
The power components 906 provide power to the various components of the terminal 900. The power components 906 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the terminal 900.
The multimedia components 908 include a screen providing an output interface between the terminal 900 and the user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 908 includes a front facing camera and/or a rear facing camera. The front camera and/or the rear camera may receive external multimedia data when the terminal 900 is in an operation mode, such as a photographing mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio component 910 is configured to output and/or input audio signals. For example, audio component 910 includes a Microphone (MIC) that is configured to operate when terminal 900 is in an operational mode, such as a call mode, a record mode, and a voice recognition mode
Is arranged to receive an external audio signal. The received audio signals may further be stored in the memory 904 or transmitted via the communication component 916. In some embodiments, audio component 910 also includes a speaker for outputting audio signals.
I/O interface 912 provides an interface between processing component 902 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
The sensor component 914 includes one or more sensors for providing various aspects of state assessment for the terminal 900. For example, sensor assembly 914 can detect an open/closed state of terminal 900, a relative positioning of components, such as a display and keypad of terminal 900, a change in position of terminal 900 or a component of terminal 900, the presence or absence of user contact with terminal 900, an orientation or acceleration/deceleration of terminal 900, and a change in temperature of terminal 900. The sensor assembly 914 may include a proximity sensor configured to detect the presence of a nearby object in the absence of any physical contact. The sensor assembly 914 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 914 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
Communication component 916 is configured to facilitate communications between terminal 900 and other devices in a wired or wireless manner. Terminal 900 can access a wireless network based on a communication standard, such as WiFi, an operator network (e.g., 2G, 3G, 4G, or 5G), or a combination thereof. In an exemplary embodiment, the communication component 916 receives a broadcast signal or broadcast associated information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 916 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the terminal 900 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described methods.
Through the above description of the embodiments, those skilled in the art can clearly understand that the technical solution for executing the external command of the system provided by the present invention can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
Embodiment 12:
this embodiment provides an apparatus for user type restriction application in instant messaging, as shown in fig. 15, the apparatus includes: the receiving module is used for receiving a request for starting the user information type limiting sub-application sent by the terminal;
and the sending module is used for sending feedback information or a starting instruction whether to start the user information type limiting sub-application to the terminal.
Embodiment 13:
the present embodiment is a further improvement of embodiment 12, and the main improvement is that, as shown in fig. 16, the apparatus in the present embodiment further includes a determining module, configured to determine whether the user information type definition sub-application meets a preset condition for starting.
Embodiment 14:
this embodiment provides a server for user type defined application in instant messaging, and as shown in fig. 17, the server 1000 may be provided as a server. The server 1000 includes a processing component 1022 that further includes one or more processors, and memory resources, represented by memory 1032, for storing instructions, such as application programs, that are executable by the processing component 1022. The application programs stored in memory 1032 may include one or more modules that each correspond to a set of instructions. Further, the processing component 1022 is configured to execute instructions to execute the user-type defined application method in instant messaging.
The server 1000 may also include a power component 1026 configured to perform power management for the server 1000, a wired or wireless network interface 1050 configured to connect the server 1000 to a network, and an input/output (I/O) interface 1058. Server 1000 may operate based on an operating system stored in memory 1032, such as a Windows Server, MacOS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.
The sequence of the above embodiments of the present invention is only for description, and does not represent the advantages and disadvantages of the embodiments.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.

Claims (19)

1. A method for using multi-scenario application of instant communication tool is characterized by comprising the following steps:
s1: presetting a user information type limiting sub-application in an installed instant messaging application program;
wherein the user information type limit sub-application is an application program which runs by depending on the instant messaging application program; the user information type limiting sub-application limits the user information types and/or user information data related to the user information types displayed, viewed, inquired or inquired in the participating terminal users after the user information type sub-application is operated; the same terminal user in the instant communication application program has at least two user information types, each user information type limits the sub-application to be associated with different user information types after running, and each user information type is associated with the user information data which are not completely the same for the same terminal user;
s2: acquiring a trigger instruction of a terminal user to the user information type limiting sub-application;
s3: displaying at least one user information type restriction identifier for selection by an end user; or, sending a request for starting the user information type limitation sub-application to a server, and receiving and displaying at least one user information type limitation identifier selected by the terminal user;
s4: acquiring a selection result of the user information type limitation identifier by the terminal user, and sending a request for running the user information type limitation sub-application to a server;
s5: and if receiving feedback information or an operation instruction sent by the server for operating the user information type limiting sub-application, operating the user information type limiting sub-application.
2. The method for user-type restricted application in instant messaging according to claim 1, wherein in S4, after obtaining the result of selecting the user information type restriction identifier by the end user, before sending the request for running the user information type restriction sub-application to the server, the method further comprises the following steps:
and judging whether the request meets a preset condition, and if so, sending the request to a server.
3. The method of claim 2, wherein the predetermined condition is:
whether the number of the contact person identifications selected by the terminal user meets the number requirement of starting and running the user information type limiting sub-application or not;
or whether the contact corresponding to the contact identification selected by the terminal user really exists or not;
or whether the contact corresponding to the contact identification selected by the terminal user agrees to participate in the user information type definition sub-application or not.
4. The method as claimed in claim 1, wherein in S4, after obtaining the result of selecting the user information type restriction application by the end user and before sending the request for starting the user information type restriction application to the server, at least two contact identifications for the end user to select are displayed, and the result of selecting the contact identification by the end user is obtained.
5. The method as claimed in claim 1, wherein in S5, after receiving the feedback information or the start instruction and before running the user information type defining sub-application, at least two contact identifiers for the end user to select are displayed, and the result of selecting the contact identifier by the end user is obtained.
6. The method for using the instant messenger multi-scenario application of any of claims 3 to 5, wherein the contact identifier is a contact identifier consistent with a user information type associated with the user information type definition sub-application.
7. The method of any of claims 1 to 5, wherein the same end-user only stores one user information type of another end-user and/or user information data associated with the user information type at the same time.
8. The method for using the instant messenger multi-scenario application according to any of the claims 1 to 5, characterized in that after the user information type definition sub-application is run, all the terminal users participating in the user information type definition sub-application can show, view, query, browse and/or download the user information types of other participating terminal users and/or the user information data associated with the user information types therein.
9. A client, comprising:
the first display module is used for displaying a label of the user information type definition sub-application at the client;
the first acquisition module is used for acquiring a trigger instruction of a terminal user to the user information type limiting sub-application;
the second display module is used for displaying at least two user information type limit identifications for the terminal user to select;
a second obtaining module, configured to obtain a selection result of the user information type restriction identifier by the terminal user;
a sending module, configured to send, to a server, a request to start the sub-application of the user information type restriction after the second obtaining module obtains the selection result of the user information type restriction identifier;
the receiving module is used for receiving feedback information or a starting instruction which is sent by the server and accords with the preset condition for starting the user information type limiting sub-application;
and the starting module is used for starting and running the user information type limiting sub-application after the receiving module receives the feedback information or the starting instruction that the user information type limiting sub-application meets the preset starting condition.
10. The client according to claim 9, further comprising:
and the judging module is used for judging whether the request meets a preset condition or not after the second acquiring module acquires the selection result of the user information type limitation identifier and before the sending module sends the request for starting the user information type limitation sub-application to the server.
11. The client according to claim 9, further comprising:
the storage module is used for storing the contact information; in the storage module, the same terminal user only stores one user information type of another terminal user and/or user information data related to the user information type at the same time.
12. The client according to claim 9, further comprising:
the third display module is used for displaying at least two contact person identifications for the terminal user to select after the second acquisition module acquires the selection result of the terminal user on the user information type limitation identification and before the sending module sends the request for starting the user information type limitation sub-application to the server;
a third obtaining module, configured to obtain a result of selecting the contact identifier by the end user after the third displaying module displays at least two types of contact identifiers for the end user to select and before the sending module sends the request for starting the user information type limitation sub-application to the server.
13. The client of claim 9, further comprising:
the fourth display module is used for displaying the contact person identification which can be selected by the terminal user after the receiving module receives the feedback information or the starting instruction and before the starting module starts and runs the user information type limiting sub-application;
and the fourth acquisition module is used for acquiring the selection result of the terminal user on the contact person identifier after the fourth display module displays the contact person identifier and before the starting module starts and runs the user information type limiting sub-application.
14. The client according to any one of claims 9 to 13, further comprising a presentation module, a viewing module, a query module, a browsing module and/or a downloading module, configured to enable all end users participating in the user information type definition sub-application to present, view, query, browse and/or download user information types of other participating end users and/or user information data associated with the user information types therein after the start module runs the user information type definition sub-application.
15. A terminal, characterized in that it comprises a memory for storing the relevant programs, instructions of the client, a processor for executing the method steps of claims 1-8, and the client according to claims 9-14, and the relevant programs, instructions of the client are executed.
16. An apparatus, comprising:
the receiving module is used for receiving a request for starting the user information type limiting sub-application sent by the terminal;
and the sending module is used for sending feedback information or a starting instruction whether the user information type limiting sub-application is started or not to the terminal.
17. The apparatus according to claim 16, further comprising a determining module for determining whether the user information type definition sub-application meets a preset condition for starting.
18. A server, comprising:
a processor and a memory;
the memory is used for storing relevant programs and instructions of the device according to the claim 16 or 17, and the processor is used for executing the instructions of the device.
19. A non-transitory computer readable storage medium, wherein instructions in the storage medium, when executed by a processor of a server, enable the server to perform or run the apparatus of claim 16 or 17.
CN202010120962.6A 2020-02-26 2020-02-26 User type limiting application method in instant messaging, client, terminal, device, server and storage medium Active CN111262780B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010120962.6A CN111262780B (en) 2020-02-26 2020-02-26 User type limiting application method in instant messaging, client, terminal, device, server and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010120962.6A CN111262780B (en) 2020-02-26 2020-02-26 User type limiting application method in instant messaging, client, terminal, device, server and storage medium

Publications (2)

Publication Number Publication Date
CN111262780A true CN111262780A (en) 2020-06-09
CN111262780B CN111262780B (en) 2022-05-17

Family

ID=70946123

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010120962.6A Active CN111262780B (en) 2020-02-26 2020-02-26 User type limiting application method in instant messaging, client, terminal, device, server and storage medium

Country Status (1)

Country Link
CN (1) CN111262780B (en)

Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101374148A (en) * 2008-09-18 2009-02-25 腾讯科技（深圳）有限公司 Method and system for managing blog intimate authority
CN102158581A (en) * 2011-04-02 2011-08-17 北京互通无线科技有限公司 Contact sequencing method and communication terminal
CN102801650A (en) * 2012-08-10 2012-11-28 上海量明科技发展有限公司 Method, client and system for displaying scenes in instant messaging interaction interface
CN103179026A (en) * 2013-04-11 2013-06-26 腾讯科技（深圳）有限公司 Communication method and system in user interactive system, server and client
CN103188130A (en) * 2011-12-29 2013-07-03 中兴通讯股份有限公司 Social network user information correlation method and correlation device
WO2016082513A1 (en) * 2014-11-28 2016-06-02 小米科技有限责任公司 Method and device for prompting call request
CN107302486A (en) * 2016-04-15 2017-10-27 张志华 The information receiving and transmitting and methods of exhibiting and system of instant messaging application
CN107766432A (en) * 2017-09-18 2018-03-06 维沃移动通信有限公司 A kind of data interactive method, mobile terminal and server
US20190050594A1 (en) * 2014-05-12 2019-02-14 Tencent Technology (Shenzhen) Company Limited Access control method and terminal device
CN109616222A (en) * 2018-11-23 2019-04-12 杭州普利复健科技有限公司 Information interacting method and system
CN110069355A (en) * 2019-04-22 2019-07-30 北京字节跳动网络技术有限公司 Customer relationship shows, customer relationship method of converting, device, equipment and medium
CN110138848A (en) * 2019-04-30 2019-08-16 上海掌门科技有限公司 A kind of release information method for pushing and equipment

Patent Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101374148A (en) * 2008-09-18 2009-02-25 腾讯科技（深圳）有限公司 Method and system for managing blog intimate authority
CN102158581A (en) * 2011-04-02 2011-08-17 北京互通无线科技有限公司 Contact sequencing method and communication terminal
CN103188130A (en) * 2011-12-29 2013-07-03 中兴通讯股份有限公司 Social network user information correlation method and correlation device
CN102801650A (en) * 2012-08-10 2012-11-28 上海量明科技发展有限公司 Method, client and system for displaying scenes in instant messaging interaction interface
CN103179026A (en) * 2013-04-11 2013-06-26 腾讯科技（深圳）有限公司 Communication method and system in user interactive system, server and client
US20190050594A1 (en) * 2014-05-12 2019-02-14 Tencent Technology (Shenzhen) Company Limited Access control method and terminal device
WO2016082513A1 (en) * 2014-11-28 2016-06-02 小米科技有限责任公司 Method and device for prompting call request
CN107302486A (en) * 2016-04-15 2017-10-27 张志华 The information receiving and transmitting and methods of exhibiting and system of instant messaging application
CN107766432A (en) * 2017-09-18 2018-03-06 维沃移动通信有限公司 A kind of data interactive method, mobile terminal and server
CN109616222A (en) * 2018-11-23 2019-04-12 杭州普利复健科技有限公司 Information interacting method and system
CN110069355A (en) * 2019-04-22 2019-07-30 北京字节跳动网络技术有限公司 Customer relationship shows, customer relationship method of converting, device, equipment and medium
CN110138848A (en) * 2019-04-30 2019-08-16 上海掌门科技有限公司 A kind of release information method for pushing and equipment

Also Published As

Publication number Publication date
CN111262780B (en) 2022-05-17

Similar Documents

Publication Publication Date Title
CN110460578B (en) Method and device for establishing association relationship and computer readable storage medium
CN106170004B (en) Method and device for processing verification code
CN109521918B (en) Information sharing method and device, electronic equipment and storage medium
CN106775202B (en) Information transmission method and device
CN107959757B (en) User information processing method and device, APP server and terminal equipment
CN107423386B (en) Method and device for generating electronic card
CN110737844B (en) Data recommendation method and device, terminal equipment and storage medium
CN107147815B (en) Call processing method and device based on taxi taking
US20220391446A1 (en) Method and device for data sharing
CN108011990B (en) Contact management method and device
CN112434338A (en) Picture sharing method and device, electronic equipment and storage medium
US10079787B2 (en) Method and apparatus for creating group and exiting group
CN113259226A (en) Information synchronization method and device, electronic equipment and storage medium
CN107295167B (en) Information display method and device
CN109842543B (en) Instant messaging method and device and instant messaging message storage method and device
CN111368329B (en) Message display method and device, electronic equipment and storage medium
CN106447747B (en) Image processing method and device
CN106506808B (en) Method and device for prompting communication message
CN110213062B (en) Method and device for processing message
CN110764847A (en) User information processing method and device, electronic equipment and storage medium
CN111262780B (en) User type limiting application method in instant messaging, client, terminal, device, server and storage medium
CN107169042B (en) Method and device for sharing pictures and computer readable storage medium
CN107239490B (en) Method and device for naming face image and computer readable storage medium
CN106712960B (en) Processing method and device of verification code information
CN111262882B (en) User type limiting application method, device and storage medium in instant messaging

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant