CN111262882B - User type limiting application method, device and storage medium in instant messaging - Google Patents
User type limiting application method, device and storage medium in instant messaging Download PDFInfo
- Publication number
- CN111262882B CN111262882B CN202010120956.0A CN202010120956A CN111262882B CN 111262882 B CN111262882 B CN 111262882B CN 202010120956 A CN202010120956 A CN 202010120956A CN 111262882 B CN111262882 B CN 111262882B
- Authority
- CN
- China
- Prior art keywords
- application
- user
- user information
- sub
- type
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- 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]
- H04L51/046—Interoperability with other network applications or services
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0407—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the identity of one or more communicating identities is hidden
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computing Systems (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (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 at least one user information type limiting sub-application in the installed instant messaging tool; acquiring a trigger instruction of a terminal user for a sub-application limited by a certain specific user information type; sending a request for starting the specific user information type limiting sub-application to a server; and if receiving feedback information or a starting instruction sent by the server for starting the specific user information type limiting sub-application, starting and running the specific user information type limiting sub-application. The invention establishes a communication environment with a specific scene for the user, particularly a business communication environment, through the user type limit application preset in the communication tool, meets the communication requirement under a specific background, and greatly improves the communication efficiency among the users.
Description
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 user type limited application method in instant messaging, which comprises the following steps: s1: presetting at least one user information type limiting sub-application in the installed instant messaging tool; 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 limiting sub-application runs; the same terminal user has at least two user information types, and each user information type limitation sub-application is associated with different user information types; each user information type is associated with user information data which are not completely the same for the same terminal user; s2: acquiring a trigger instruction of a terminal user for a sub-application limited by a certain specific user information type; s3: sending a request for starting the specific user information type limiting sub-application to a server; s4: and if receiving feedback information or a starting instruction sent by the server for starting the specific user information type limiting sub-application, starting and running the specific user information type limiting sub-application.
Further, after the step S2 and before the step S3, the method further comprises the following steps: and judging whether the request meets a preset condition for starting the specific user information type limiting sub-application, and if the request meets the preset condition, entering the step S3.
Further, after the step S2 and before the step S3, the method further comprises the following steps: displaying the contact person identification which can be selected by the terminal user, and acquiring the selection result of the terminal user on the contact person identification.
Further, in S4, after receiving the feedback information or the start instruction and before starting and running the specific user information type defining sub-application, the method further includes the following steps: displaying the contact person identification which can be selected by the terminal user, and acquiring the selection result of the terminal user on the contact person identification.
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, the contact identifier selectable by the end user is a contact identifier consistent with the user information type associated with the particular user information type defining sub-application.
Preferably, 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 running the specific user information type limiting sub-application; or, whether the contact person identification selected by the terminal user really exists or not; or whether the contact identification selected by the terminal user agrees to participate in the specific user information type definition sub-application.
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 acquisition module is used for acquiring a trigger instruction of a terminal user for a sub-application of a certain specific user information type limit; a sending module, configured to send a request for starting the specific user information type limited sub-application to a server; a receiving module, configured to receive feedback information or a start instruction sent by the server to start the specific user information type restricted sub-application; and the starting module is used for starting and running the specific user information type limiting sub-application after the receiving module receives the feedback information or the starting instruction.
Further, the client further comprises: the judging module is used for judging whether the request meets the preset condition for starting the specific user information type limitation sub-application or not after the first acquiring module acquires the trigger instruction of the terminal user to the specific user information type limitation sub-application and before the sending module sends the request for starting the specific user information type limitation sub-application to the server.
Further, the client further comprises: the storage module is used for storing the 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.
Further, the client further comprises: the first display module is used for displaying the contact person identification which can be selected by the terminal user after the first acquisition module acquires the trigger instruction of the terminal user to a certain specific user information type limiting sub-application and before the sending module sends a request for starting the specific user information type limiting sub-application to the server; and the second acquisition module is used for acquiring a selection result of the contact person identification by the terminal user after the contact person identification is displayed by the first display module.
Further, the client further comprises: the second 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 specific user information type limiting sub-application; and the third acquisition module is used for acquiring a selection result of the contact person identifier by the terminal user after the contact person identifier is displayed by the second display module.
Preferably, in the storage module, 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.
Further, the client further comprises a presentation module, a viewing module, a query module, a browsing module and/or a downloading module, which is configured to enable all the terminal users participating in the specific user information type limitation sub-application to present, 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 after the specific user information type limitation sub-application is run by the starting module.
The invention also provides a terminal comprising a memory for storing programs and instructions related to the client, a processor for executing the steps of the method according to claims 1 to 7 and a client according to claims 8 to 13, and for executing the programs and instructions related to the client.
The present invention also provides an apparatus comprising: the receiving module is used for receiving a request for starting a specific user information type limiting sub-application sent by a terminal; and the sending module is used for sending feedback information or a starting instruction whether to start the specific user information type limiting sub-application to the terminal.
Further, the apparatus further includes a determining module, configured to determine whether the specific user information type restriction 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 according to the claim 15 or 16, 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: the invention establishes a communication environment with a specific scene for the user, particularly a business communication environment, through the user type limit application preset in the communication tool, meets the communication requirement under a specific background, and greatly improves the communication efficiency among the 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 concrete case diagram of the user type definition application method in the instant messaging according to embodiment 2;
fig. 5 is a flowchart of a user type restriction 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 block diagram of a user type definition application client in instant messaging according to embodiment 5;
fig. 8 is a block diagram of a user type definition application client in instant messaging according to embodiment 6;
fig. 9 is a block diagram of a user type definition application client in instant messaging according to embodiment 7;
fig. 10 is a block diagram of a user type definition application client in instant messaging according to embodiment 8;
fig. 11 is a block diagram of a user type definition application client in instant messaging according to embodiment 9;
fig. 12 is a block diagram of a terminal of a user type definition application in instant messaging according to embodiment 10;
fig. 13 is a block diagram of an apparatus for user-type defined application in instant messaging according to embodiment 11;
fig. 14 is a block diagram showing an apparatus for user type definition application in instant messaging according to embodiment 12;
fig. 15 is a block diagram of a server for a user-type defined application in instant messaging according to embodiment 13.
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 at least one user information type limiting sub-application in the installed instant messaging tool;
the sub-application is an application program running depending on an instant messaging application program; the user information type limitation 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 limitation sub-application runs; the same terminal user has at least two user information types, and each user information type limits the sub-application association of different user information types; each user information type is associated with user information data which are not completely the same for the same terminal user;
s2: acquiring a trigger instruction of a terminal user for a sub-application limited by a certain specific user information type;
s3: sending a request for starting a specific user information type limited sub-application to a server;
s4: and if receiving feedback information or a starting instruction sent by the server for starting the specific user information type limiting sub-application, starting and running the specific 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 also provided with a 'commercial blog' sub-application, which is used for instant messaging users to publish information of the workplace, the business, the society and the like and to pay attention to the evaluation and discussion of the users, and requires a creator to create the information in the user information type of a friend of the creator, and the information of the user in the information type of the friend of the creator is displayed after the creator creates the information. The method comprises the steps that a user triggers a control for creating a commercial blog in a terminal interface, an instant messaging tool obtains a command for creating the commercial blog of the user, instant messaging (a client) sends a request to a server, the server judges whether the request user fills in the request including names, units and jobs or the request is authenticated by a real-name system according to preset requirements, if the request user meets the filling conditions, the server sends the command for starting the creation of the commercial blog to the client, and after receiving the command sent by the server, the client starts the creation work and displays a page for writing the commercial blog at 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 request is received, and the request is sent to 'you create a commercial blog and need to fill in effective information such as your real name, organization, post and the like in personal data' sent by the server.
When the user finishes content editing and sending to the server, and the commercial blog is created, all users who can browse the blog content can check the user information corresponding to the user information type of the user's business friends. 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:
the present embodiment is a further improvement of embodiment 1, and is mainly improved in that, as shown in fig. 3, after the trigger information is acquired in embodiment 1 and before the request for starting the specific user information type limiting sub-application is sent to the server, a contact identifier that can be selected by the terminal user is also displayed, and a selection result of the terminal user for the contact identifier is acquired.
The contact identifier selectable by the end user is a contact identifier consistent with the user information type associated with the specific user information type defining sub-application. 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:
a friend group chat application and a friend group chat application are preset in software for creating group chat in a mobile phone, for example, as shown in fig. 4a, a user a triggers an instruction for creating the friend group chat application, and after receiving the triggering instruction, a client of the user a also displays a contact identifier (such as a nickname or a head portrait of Chengli, Sunday, and Zhu Bajie) which can be selected by the user a, for example, as shown in fig. 4b, and obtains a selection result of the contact identifier by the user a, and then sends a request for starting the friend group chat application to a server, and when receiving a starting instruction for starting the friend group chat application sent by the server, the client of the user a starts and runs the friend group chat application, and jumps to a friend group chat window, for example, as shown in fig. 4 c. After the business friend group chat sub-application is operated, all users (including user A, Chenlili, Saint Sun and Zhu Bajie) participating in the business friend group chat sub-application can show, view, inquire, browse and/or download the business friend information types of other participating users and/or business friend information data related to the business friend information types.
Embodiment 3:
the embodiment is a further improvement of embodiment 2, and is mainly improved in that, as shown in fig. 5, after the trigger information is acquired, the contact identifier selectable by the terminal user is displayed, and before the selection result of the terminal user on the contact identifier is acquired, it is further determined whether a request to start the sub-application of the specific user information type limitation sent to the server meets a preset condition for starting, and if the preset condition is met, the request to start the sub-application of the specific user information type limitation is sent to the server.
The present embodiment will be described more specifically below with reference to a specific example:
still referring to the example of embodiment 2, after the client of the user a receives the trigger instruction for creating the buddy group chat application, it is determined whether the request for starting the buddy group chat application, which is to be sent to the server, meets a preset condition for starting the buddy group chat application, and if the preset condition is met, a nickname or a head portrait of Chenoli, Sunday and Zhu Bajie that can be selected by the user a is displayed, and a selection result of Chenoli, Sunday and Zhu Bajie by the user a is obtained, and then the request for starting the buddy group chat 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 running the specific user information type limiting sub-application or not;
or whether the contact person identification selected by the terminal user really exists or not;
alternatively, the contact identification selected by the end user may agree to participate in a particular user information type definition sub-application.
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 1, and the main improvement is that, as shown in fig. 6, after receiving feedback information or a start instruction in embodiment 1 and before starting and running a specific user information type defining sub-application, a contact identifier selectable by an end user is also displayed, and a selection result of the end user for the contact identifier is obtained. 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:
also in the example of embodiment 2, after the trigger information is acquired, instead of displaying the nicknames or head portraits of Chenlili, Sunzhai, and Zhu Bajie that can be selected by the user A, and acquiring the selection results of the user A on Chenlili, Sunzhai, and Zhu Bajie, a request for starting the friend group chat application is directly sent to the server; and after the client of the user A receives a starting 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 2, 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 identical to embodiment 2, and will not be described herein.
Embodiment 5:
the present embodiment provides a client, as shown in fig. 7, including:
the first acquisition module is used for acquiring a trigger instruction of a terminal user for a sub-application of a certain specific user information type limit;
a sending module, configured to send a request for starting a specific user information type limited sub-application to a server;
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 specific user information type limiting sub-application;
the starting module is used for starting and running the specific user information type limiting sub-application after the receiving module receives the feedback information or the starting instruction that the specific user information type limiting sub-application meets the starting preset 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 6:
the present embodiment is a further improvement of embodiment 5, and the main improvement is that, as shown in fig. 8, 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 5, and will not be described herein.
Embodiment 7:
the present embodiment is a further improvement of embodiment 5, and a main improvement is that, as shown in fig. 9, the client in this embodiment further includes a determining module, configured to determine, after the first obtaining module obtains a trigger instruction of the terminal user for one of the specific user information type limitation sub-applications and before the sending module sends a request for starting the specific user information type limitation sub-application to the server, whether the request for starting the specific user information type limitation sub-application, which is to be sent to the server by the sending module, meets a preset condition for starting.
Otherwise, this embodiment is completely the same as embodiment 5, and will not be described herein.
Embodiment 8:
this embodiment is a further improvement of embodiment 6, and the main improvement is that, as shown in fig. 10, the client in this embodiment further includes:
the first display module is used for displaying the contact person identification which can be selected by the terminal user after the first acquisition module acquires the trigger instruction of the terminal user to the specific user information type limiting sub-application and before the first judgment module judges whether the request meets the preset condition for starting the specific user information type limiting sub-application;
and the second acquisition module is used for acquiring the selection result of the terminal user on the contact person identification after the first display module displays the contact person identification and before the first judgment module judges whether the request meets the preset condition for starting the specific user information type limiting sub-application.
Otherwise, this embodiment is completely the same as embodiment 6, 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. 11, the client in this embodiment further includes:
the second 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 specific user information type limiting sub-application;
and the third acquisition module is used for acquiring the selection result of the terminal user on the contact person identification after the second display module displays the contact person identification and before the starting module starts and runs the specific user information type limiting sub-application.
Otherwise, this embodiment is completely the same as embodiment 6, and will not be described herein.
Embodiment 10:
this embodiment provides a terminal, which includes a memory, a processor, and the client as described in embodiments 5 to 8, where the memory is used to store the relevant programs and instructions of the client, and the processor is used to execute the method steps as described in embodiments 1 to 4 and run the relevant programs and instructions of the client.
As shown in fig. 12, 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. 12, 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.
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.
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 11:
this embodiment provides an apparatus for user type restriction application in instant messaging, as shown in fig. 13, the apparatus includes: the receiving module is used for receiving a request for starting a specific user information type limiting sub-application sent by a terminal;
and the sending module is used for sending feedback information or a starting instruction for judging whether to start the specific user information type limiting sub-application to the terminal.
Embodiment 12:
the present embodiment is a further improvement of embodiment 10, and the main improvement is that, as shown in fig. 14, the apparatus in the present embodiment further includes a determining module, configured to determine whether the specific user information type restriction sub-application meets a preset condition for starting.
Embodiment 13:
this embodiment provides a server for user type defined application in instant messaging, and as shown in fig. 15, 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 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 (18)
1. A user type limited application method in instant messaging is characterized by comprising the following steps:
s1: presetting at least one user information type limiting sub-application in the installed instant messaging tool;
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 limiting sub-application runs; the same terminal user has at least two user information types, and each user information type limitation sub-application is associated with different user information types; each user information type is associated with user information data which are not completely the same for the same terminal user;
s2: acquiring a trigger instruction of a terminal user for a sub-application limited by a certain specific user information type;
judging whether the request of the specific user information type limiting sub-application meets a preset condition for starting the specific user information type limiting sub-application, and if the request meets the preset condition, entering the step S3;
s3: sending a request to start the server;
s4: and if receiving feedback information or a starting instruction sent by the server for starting the specific user information type limiting sub-application, starting and running the specific user information type limiting sub-application.
2. The method for user-type restricted application in instant messaging according to claim 1, further comprising the following steps after S2 and before S3:
displaying the contact person identification which can be selected by the terminal user, and acquiring the selection result of the terminal user on the contact person identification.
3. The method for user-type restricted application in instant messaging according to claim 1, wherein in S4, after receiving the feedback information or start instruction and before starting and running the specific user information type restricted sub-application, further comprising the steps of:
displaying the contact person identification which can be selected by the terminal user, and acquiring the selection result of the terminal user on the contact person identification.
4. The method as claimed in claim 3, wherein the contact identifier selectable by the end user is a contact identifier corresponding to the user information type associated with the specific user information type defining sub-application.
5. The method for user-type-defined application in instant messaging according to any of claims 1 to 4, wherein the same end-user only stores one user information type and/or user information data associated with the user information type of another end-user at the same time.
6. The method for user type restricted application in instant messaging according to any of claims 1 to 4, 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 specific user information type limiting sub-application;
or, whether the contact person identification selected by the terminal user really exists or not;
or whether the contact identification selected by the terminal user agrees to participate in the specific user information type definition sub-application.
7. The method for user-type restricted application in instant messaging according to any of claims 1 to 4, wherein after the user-information-type restricted sub-application is run, all terminal users participating in the user-information-type restricted sub-application can present, 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.
8. A client for performing the method for user type restriction application in instant messaging with a server according to any one of claims 1 to 7, comprising:
the first acquisition module is used for acquiring a trigger instruction of a terminal user for a sub-application of a certain specific user information type limit;
a sending module, configured to send a request for starting the specific user information type limited sub-application to a server;
a receiving module, configured to receive feedback information or a start instruction sent by the server to start the specific user information type restricted sub-application;
and the starting module is used for starting and running the specific user information type limiting sub-application after the receiving module receives the feedback information or the starting instruction.
9. The client of the user-type defined application method in instant messaging according to claim 8, wherein the client further comprises:
the judging module is used for judging whether the request meets the preset condition for starting the specific user information type limitation sub-application or not after the first acquiring module acquires the trigger instruction of the terminal user to the specific user information type limitation sub-application and before the sending module sends the request for starting the specific user information type limitation sub-application to the server.
10. The client of the user-type defined application method in instant messaging according to claim 8, wherein the client further comprises:
the storage module is used for storing the 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.
11. The client of the user-type defined application method in instant messaging according to claim 8, wherein the client further comprises:
the first display module is used for displaying the contact person identification which can be selected by the terminal user after the first acquisition module acquires the trigger instruction of the terminal user to a certain specific user information type limiting sub-application and before the sending module sends a request for starting the specific user information type limiting sub-application to the server;
and the second acquisition module is used for acquiring a selection result of the contact person identification by the terminal user after the contact person identification is displayed by the first display module.
12. The client of the user-type defined application method in instant messaging according to claim 8, further comprising:
the second 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 specific user information type limiting sub-application;
and the third acquisition module is used for acquiring a selection result of the contact person identifier by the terminal user after the contact person identifier is displayed by the second display module.
13. The client of the method for user-type restricted application in instant messaging according to claim 8, further comprising a presentation module, a viewing module, an inquiry module, a browsing module and/or a downloading module, for enabling all end users participating in the user-information-type restricted sub-application to present, view, inquire, 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 specific user-information-type restricted sub-application is run by the starting module.
14. A terminal for user type defined application method in instant messaging, characterized in that it comprises a memory for storing the relevant programs and instructions of the client, a processor for executing the method steps of claims 1-7 and the relevant programs and instructions of the client, and the client according to claims 8-13.
15. An apparatus for defining an application method for a user type in instant messaging, comprising:
a receiving module, configured to receive a request for starting a specific user information type-limited sub-application sent by the terminal according to claim 14;
a sending module, sending feedback information or starting instructions whether to start the specific user information type restricted sub-application to the terminal of claim 14.
16. The apparatus of claim 15, further comprising a determining module for determining whether the specific ue type-specific sub-application meets a preset condition for starting.
17. A server for user type restricted application method in instant messaging, comprising:
a processor and a memory;
the memory is used for storing the relevant program and instructions of the device according to claim 15 or 16, and the processor is used for executing the instructions of the device.
18. A non-transitory computer readable storage medium for a user-type defined application method in instant messaging, wherein when instructions in the storage medium are executed by a processor of a server, the server is capable of executing or running the apparatus according to claim 15 or 16.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010120956.0A CN111262882B (en) | 2020-02-26 | 2020-02-26 | User type limiting application method, device and storage medium in instant messaging |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010120956.0A CN111262882B (en) | 2020-02-26 | 2020-02-26 | User type limiting application method, device and storage medium in instant messaging |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111262882A CN111262882A (en) | 2020-06-09 |
| CN111262882B true CN111262882B (en) | 2022-04-12 |
Family
ID=70949560
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010120956.0A Active CN111262882B (en) | 2020-02-26 | 2020-02-26 | User type limiting application method, device and storage medium in instant messaging |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111262882B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101026849A (en) * | 2006-02-24 | 2007-08-29 | 美国博通公司 | Mobile communication device and its method for managing communication |
| CN101529880A (en) * | 2006-08-29 | 2009-09-09 | 诺基亚公司 | Replying through different channels |
| CN103179026A (en) * | 2013-04-11 | 2013-06-26 | 腾讯科技（深圳）有限公司 | Communication method and system in user interactive system, server and client |
| CN103731456A (en) * | 2012-10-15 | 2014-04-16 | 腾讯科技（深圳）有限公司 | Method and terminal for achieving social networking services |
| CN106559547A (en) * | 2015-09-29 | 2017-04-05 | 小米科技有限责任公司 | Daily record sharing method, device and mobile terminal |
| CN107959757A (en) * | 2017-12-11 | 2018-04-24 | 北京小米移动软件有限公司 | User information processing method, device, APP servers and terminal device |
| CN109033299A (en) * | 2018-07-16 | 2018-12-18 | 深圳市谷熊网络科技有限公司 | It is a kind of by terminal applies to the method, device and equipment of user's recommendation information |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100850313B1 (en) * | 2006-11-01 | 2008-08-04 | 이용직 | System and method of service for providing fixed and mobile converged handwriting instant messenger service |
| US8239461B2 (en) * | 2007-06-28 | 2012-08-07 | Chacha Search, Inc. | Method and system for accessing search services via messaging services |
| GB0712880D0 (en) * | 2007-07-03 | 2007-08-08 | Skype Ltd | Instant messaging communication system and method |
| US20110061004A1 (en) * | 2009-09-04 | 2011-03-10 | Microsoft Corporation | Use of Communicator Application to Establish Communication with Experts |
| US9592442B2 (en) * | 2013-04-11 | 2017-03-14 | Tencent Technology (Shenzhen) Company Limited | Communication method, system, server and client device for user-interactive system |
| US20160014059A1 (en) * | 2015-09-30 | 2016-01-14 | Yogesh Chunilal Rathod | Presenting one or more types of interface(s) or media to calling and/or called user while acceptance of call |
| CN104009980B (en) * | 2014-05-13 | 2015-07-22 | 腾讯科技（深圳）有限公司 | Communication method and device based on social application |
| KR102249197B1 (en) * | 2014-05-31 | 2021-05-10 | 삼성전자주식회사 | User terminal apparatus, communication system and control method thereof |
| WO2017168202A1 (en) * | 2016-03-27 | 2017-10-05 | Yogesh Chunilal Rathod | Identifying & storing followers, following users, viewers, users and connections for user |
-
2020
- 2020-02-26 CN CN202010120956.0A patent/CN111262882B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101026849A (en) * | 2006-02-24 | 2007-08-29 | 美国博通公司 | Mobile communication device and its method for managing communication |
| CN101529880A (en) * | 2006-08-29 | 2009-09-09 | 诺基亚公司 | Replying through different channels |
| CN103731456A (en) * | 2012-10-15 | 2014-04-16 | 腾讯科技（深圳）有限公司 | Method and terminal for achieving social networking services |
| CN103179026A (en) * | 2013-04-11 | 2013-06-26 | 腾讯科技（深圳）有限公司 | Communication method and system in user interactive system, server and client |
| CN106559547A (en) * | 2015-09-29 | 2017-04-05 | 小米科技有限责任公司 | Daily record sharing method, device and mobile terminal |
| CN107959757A (en) * | 2017-12-11 | 2018-04-24 | 北京小米移动软件有限公司 | User information processing method, device, APP servers and terminal device |
| CN109033299A (en) * | 2018-07-16 | 2018-12-18 | 深圳市谷熊网络科技有限公司 | It is a kind of by terminal applies to the method, device and equipment of user's recommendation information |
Non-Patent Citations (1)
| Title |
|---|
| EAST即时通信系统;王兰等;《计算机系统应用》;20180815(第08期);112-117页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111262882A (en) | 2020-06-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3454192A1 (en) | Method and device for displaying page | |
| CN110460578B (en) | Method and device for establishing association relationship and computer readable storage medium | |
| CN109521918B (en) | Information sharing method and device, electronic equipment and storage medium | |
| CN106775202B (en) | Information transmission method and device | |
| CN107423386B (en) | Method and device for generating electronic card | |
| CN107959757B (en) | User information processing method and device, APP server and terminal equipment | |
| CN107147815B (en) | Call processing method and device based on taxi taking | |
| US20220391446A1 (en) | Method and device for data sharing | |
| CN105511739A (en) | Message prompting 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 | |
| CN108984098B (en) | Information display control method and device based on social software | |
| 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 | |
| CN107169042B (en) | Method and device for sharing pictures and computer readable storage medium | |
| CN111262882B (en) | User type limiting application method, device and storage medium in instant messaging | |
| CN106712960B (en) | Processing method and device of verification code information | |
| CN111865767B (en) | User display method, device, server, client, terminal and storage medium for indirectly monitoring telephone in instant messaging | |
| CN112104546B (en) | Method, device, server, client, terminal and storage medium for realizing' temporary session | |
| CN111262780B (en) | User type limiting application method in instant messaging, client, terminal, device, server and storage medium | |
| US20170316039A1 (en) | Information acquisition method, device and system | |
| CN109120499B (en) | Information processing method and device |
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 |