WO2019165683A1 - 一种召唤方法及召唤系统 - Google Patents

一种召唤方法及召唤系统 Download PDF

Info

Publication number
WO2019165683A1
WO2019165683A1 PCT/CN2018/082855 CN2018082855W WO2019165683A1 WO 2019165683 A1 WO2019165683 A1 WO 2019165683A1 CN 2018082855 W CN2018082855 W CN 2018082855W WO 2019165683 A1 WO2019165683 A1 WO 2019165683A1
Authority
WO
WIPO (PCT)
Prior art keywords
summoning
client
information
calling
server
Prior art date
Application number
PCT/CN2018/082855
Other languages
English (en)
French (fr)
Inventor
汪刚
张文明
陈少杰
Original Assignee
武汉斗鱼网络科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 武汉斗鱼网络科技有限公司 filed Critical 武汉斗鱼网络科技有限公司
Publication of WO2019165683A1 publication Critical patent/WO2019165683A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/148—Migration or transfer of sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/75—Indicating network or usage conditions on the user display
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/258—Client or end-user data management, e.g. managing client capabilities, user preferences or demographics, processing of multiple end-users preferences to derive collaborative data
    • H04N21/25808—Management of client data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/438—Interfacing the downstream path of the transmission network originating from a server, e.g. retrieving encoded video stream packets from an IP network
    • H04N21/4383—Accessing a communication channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47—End-user applications
    • H04N21/478—Supplemental services, e.g. displaying phone caller identification, shopping application
    • H04N21/4788—Supplemental services, e.g. displaying phone caller identification, shopping application communicating with other users, e.g. chatting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/65—Transmission of management data between client and server
    • H04N21/654—Transmission by server directed to the client
    • H04N21/6543—Transmission by server directed to the client for forcing some client operations, e.g. recording
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/85—Assembly of content; Generation of multimedia applications
    • H04N21/858—Linking data to content, e.g. by linking an URL to a video object, by creating a hotspot
    • H04N21/8586—Linking data to content, e.g. by linking an URL to a video object, by creating a hotspot by using a URL

Definitions

  • the present application relates to the field of Internet application development technologies, and in particular, to a calling method and a calling system.
  • the purpose of the present application includes providing a summoning method and a summoning system to improve the above problems.
  • the embodiment of the present application provides a method for summoning, which is applied to a calling system, where the calling system includes a server, and a first client and a second client respectively connected to the server.
  • the method includes:
  • the first client initiates a call request to the server when detecting that the pre-established call-in portal is clicked;
  • the server After receiving the calling request, the server sends, to the second client pointed by the calling request, the calling information corresponding to the calling request;
  • the second client After receiving the summoning information, the second client obtains a corresponding calling notification according to the calling information;
  • the second client responds to the summoning notification and jumps from the current playing interface to the target live broadcast room carried by the summoning notification.
  • the summoning portal is obtained by the following steps:
  • the first client uses the alloc function in the button class to create summon entry information
  • the step of inserting the summoning entry picture into a current playing interface to obtain a corresponding calling entry includes:
  • the belowSubview function is called to insert the summon entry image below the specified level in the current playback interface.
  • the step of the first client initiating a summoning request to the server when detecting that the pre-established calling portal is clicked includes:
  • the first client obtains the to-be-called call information to be summoned when detecting that the pre-established call-in portal is clicked;
  • the to-be-called information is spliced to form a URL, and a call request carrying the URL is sent to the server.
  • the step of obtaining, by the first client, the to-be summoned information to be summoned when detecting that the pre-established call-in portal is clicked includes:
  • the first client When the first client detects that the pre-established call-in portal is clicked, the first client initiates a query request to the server;
  • the server After receiving the query request, the server extracts, from the plurality of to-be-called objects, the to-be-called object whose activity level is at the previous preset threshold according to the pre-stored activity information of the plurality of objects to be summoned, and The information of the object to be summoned is fed back to the first client, where the object to be summoned is a second client or a group consisting of multiple second clients;
  • the first client receives the information of the object to be summoned sent by the server, and obtains the to-call information to be summoned according to the information of the object to be summoned.
  • the to-be-called information includes a plurality of sub-information
  • the step of splicing the to-be-called information to form a URL and sending the call request carrying the URL to the server, including:
  • Each of the sub-information is combined according to the URL template of the base class protocol, and a specified character is added between adjacent two sub-information to be spliced to form a URL, and the server is sent with the URL. Summon the request.
  • the to-be-called information includes a call-to-call ID and a call-to-call group name.
  • the step of obtaining a corresponding call notification according to the calling information including:
  • the second client After receiving the summoning information, the second client displays a summoning button on the current playing interface;
  • the summoning information is thrown in the form of a summoning notification using the postNotificationName function in the notification center.
  • the method before the step of the second client responding to the summoning notification and jumping from the current playing interface to the target live broadcast of the summoning information, the method further includes:
  • the second client invokes a defaultCenter function in the notification center class to obtain a management class to the notification center;
  • the intercept information for monitoring the summoning notification is set by using the addObserver function in the management class of the notification center.
  • the step of the second client responding to the summoning notification and jumping from the current interface to the target live broadcast room carried by the summoning notification includes:
  • the second client After the startup, the second client enters the listening mode according to the monitoring information, and obtains the calling information corresponding to the calling notification after monitoring the calling notification;
  • the current broadcast interface is jumped to the target live broadcast room carried by the summoning information.
  • the method further includes: before the step of jumping from the current play interface to the target live broadcast of the summoning information according to the summoning information, the method further includes:
  • the second client invokes a management class of the live broadcast window to close the live broadcast window on the current play interface.
  • the summoning information includes target live broadcast information, a jump type, and jump group information.
  • the method before the step of sending the summoning information corresponding to the calling request to the second client pointed by the calling request, the method further includes:
  • the server detects whether the account level of the first client reaches a preset summoning level, and if the preset calling level is not reached, determining that the first client does not have the calling right, and the first client The end returns the summoning failure information;
  • the preset summoning level is reached, it is determined that the client has the calling right, and the step of sending the calling information corresponding to the calling request to the second client pointed by the calling request is performed.
  • the embodiment of the present application further provides a calling system, where the calling system includes a server, and a first client and a second client respectively connected to the server;
  • the first client is configured to initiate a calling request to the server when the pre-established calling portal is clicked;
  • the server is configured to send, to the second client pointed by the calling request, the calling information corresponding to the calling request after receiving the calling request;
  • the second client is configured to obtain a corresponding call notification according to the summoning information after receiving the summoning information;
  • the second client is further configured to respond to the summoning notification and jump from the current playing interface to the target live broadcast room carried by the calling notification.
  • the first client is configured to obtain the to-call information to be summoned when detecting that the pre-established call-in portal is clicked;
  • the to-be-called information is spliced to form a URL, and a call request carrying the URL is sent to the server.
  • the first client is configured to initiate a query request to the server when detecting that the pre-established call-in portal is clicked;
  • the server is configured to, after receiving the query request, extract, from the plurality of to-be-called objects, the to-be-called object whose activity ranking is at a preset threshold according to the pre-stored activity information of the plurality of to-be-called objects to be summoned. And feeding back the information of the object to be summoned to the first client, where the object to be summoned is a second client or a group consisting of multiple second clients;
  • the first client is configured to receive information about the object to be summoned sent by the server, and obtain the to-be-called call information to be called according to the information of the object to be summoned.
  • the to-be-called information includes a plurality of sub-informations
  • the first client is configured to construct a URL template based on a base class protocol, where the URL template of the base class protocol is in a string form;
  • the URL template of the base class protocol combines each of the sub-information, and adds a specified character between two adjacent sub-information to splicing to form a URL, and sends a call request carrying the URL to the server.
  • the server is configured to detect whether the account level of the first client reaches a preset summoning level, and if the preset calling level is not reached, determining that the first client does not have the calling right, and Returning the summoning failure information to the first client; if the preset calling level is reached, determining that the first client has the calling right, and sending the calling request to the second client pointed by the calling request Corresponding summoning information.
  • the summoning method and the calling system provided by the embodiment of the present application, by establishing a calling call in advance, and initiating a calling request to the server when the calling portal is clicked, using the server to send the corresponding calling information to the second client pointed to by the calling request,
  • the second client obtains a corresponding summoning notification according to the summoning information, and after responding to the calling notification by itself, jumps to the target live broadcast room carried by the calling notification.
  • the summoning program can be automatically summoned in the live broadcast room, which realizes an automated process, and is more targeted, and the summoning drainage effect is better.
  • FIG. 1 is a structural block diagram of a calling system according to an embodiment of the present application.
  • FIG. 2 is a flowchart of a method for calling according to an embodiment of the present application.
  • FIG. 3 is a flowchart of a method for creating a call-in entry according to an embodiment of the present application.
  • step S101 of FIG. 2 is a flow chart of the sub-steps of step S101 of FIG. 2.
  • FIG. 5 is a flow chart of the sub-steps of step S1011 of Figure 4.
  • FIG. 6 is another flowchart of a method for calling according to an embodiment of the present application.
  • Figure 7 is a flow chart of the sub-steps of step S105 of Figure 2.
  • FIG. 8 is another flowchart of a calling method according to an embodiment of the present application.
  • Figure 9 is a flow chart of the sub-steps of step S107 of Figure 2.
  • Icon 100-server; 200-first client; 300-second client.
  • the calling system includes a server 100, a first client 200, and a second client 300.
  • the first client 200 and the second client 300 are communicatively connected to the server 100 through a network for data communication or interaction.
  • the first client 200 and the second client 300 may be, but not limited to, a personal computer, a tablet computer, a smart phone, a mobile internet device, and the like.
  • the video live application software is installed on the first client 200 and the second client 300 for the user to perform live video broadcast.
  • the server 100 is a background server corresponding to the video live application software installed on the first client 200 and the second client 300, and can provide a video live broadcast platform.
  • the server 100 may be a network server or a database server, and may be a separate server or a server cluster.
  • the first client 200 is configured to initiate a call request to the server 100 when the pre-established call-in portal is clicked.
  • the server 100 is configured to, after receiving the summoning request, send the summoning information corresponding to the calling request to the second client 300 pointed to by the calling request.
  • the second client 300 is configured to obtain a corresponding call notification according to the summoning information after receiving the summoning information.
  • the second client 300 is configured to respond to the summoning notification and jump from the current playing interface to the target live broadcast room carried by the summoning notification.
  • FIG. 2 is a flowchart of a method for calling a call system according to an embodiment of the present application. It should be noted that the method provided in the embodiments of the present application is not limited to the specific order described in FIG. 2 and the following. The steps shown in Fig. 2 will be described in detail below.
  • Step S101 the first client 200 initiates a call request to the server 100 when detecting that the pre-established call-in portal is clicked.
  • the first client 200 may create the calling entry by the following steps:
  • step S201 the first client 200 uses the alloc function in the button class to create summon entry information.
  • Step S203 using the imageNamed function to set the summoning entry picture according to the summoning entry information, and inserting the calling ingress picture into the current playing interface to obtain a corresponding calling entry.
  • a variable can first be defined, which can be used to save the call entry information, for example, the variable can be named _tribalEntrance.
  • the alloc function in the button class UIButton is used to create the summoning entry information.
  • the summoning entry may be initialized.
  • the calling entry may be initialized by using an init function.
  • set the coordinate value of the summoning entrance that is, set the position of the summoning portal on the live interface.
  • the location of the summoning portal can be set according to specific needs.
  • the summoning entry information includes the above initialization information, coordinate value information, and the like.
  • the image named function is used to set a summoning entry picture for the pre-added summoning entry according to the summoning entry information, and the summoning entry picture is inserted into the current playing interface to obtain a final calling entry, which is played by the outside.
  • the call entry picture can be inserted into the current play interface by:
  • the addSubView function is called to insert the summoning entry image onto a specified level in the current playback interface.
  • the belowSubView function is called to insert the summon entry image below the specified level in the current playback interface.
  • a summoning portal is added, which is the basis for the user to be able to make an autonomous call, and the calling portal can also flexibly insert the calling portal image into different levels of the current playing interface by using the addSubView function or the belowSubView function described above.
  • the conflict problem of adding a summoning entry can be effectively solved, and different hierarchical relationships can be handled well.
  • step S101 may include two sub-steps of step S1011 and step S1013.
  • step S1011 the first client 200 obtains the to-call information to be summoned when detecting that the pre-established call-in portal is clicked.
  • step S1013 the to-be-called information is spliced to form a URL, and the calling request carrying the URL is sent to the server 100.
  • the call entry picture on the play interface may be clicked.
  • the user may input the call to be summoned information to be called, and the call to call information may include the to-be-called ID and the name of the group to be summoned. Wait.
  • the first client 200 splices the above-mentioned call-to-call information to form a URL (Uniform Resource Locator).
  • a URL template based on a base class protocol may be constructed first, and the URL of the base class protocol is configured. Templates can be string types like douyuapp://DouyuMail.
  • the to-be-called information may include a plurality of sub-information, and the plurality of sub-informations included in the to-be-called information may be combined according to a URL template of the base protocol, and a specified character, such as a character, is added between two adjacent sub-informations. &, to separate each sub-information, so that the summoned information is spliced to construct a new URL.
  • the URL jump function module is used to send a call request carrying the URL, that is, the call request, to the server 100.
  • the first client 200 sends the summoning request to the server 100 to inform the server 100 to perform a subsequent summoning operation.
  • the use of the protocol URL to implement the jump can effectively reduce the coupling of the code, and the URL can conveniently carry parameters and facilitate the value transfer.
  • step S1011 may include the following sub-steps:
  • step S10111 the first client 200 initiates a query request to the server 100 when detecting that the pre-established call-in portal is clicked.
  • Step S10113 After receiving the query request, the server 100 extracts, from the plurality of to-be-called objects, the to-be-called preset threshold position to be summoned according to the pre-stored activity information of the plurality of to-be-called objects to be summoned.
  • the object, and the information of the object to be summoned is fed back to the first client 200, wherein the object to be summoned is a second client 300 or a group consisting of multiple second clients 300.
  • Step S10115 The first client 200 receives the information of the object to be summoned sent by the server 100, and obtains the to-call information to be summoned according to the information of the object to be summoned.
  • a call may be selectively initiated to a more active user.
  • the first client 200 may initiate a query request to the server 100 upon detecting that the summoning event is triggered.
  • the server 100 can sort the activity of each client in advance according to the interaction of each client, or sort and save the activity of the group including multiple clients. In this way, when receiving the query request sent by the first client 200, the server may be based on the activity information of the pre-stored plurality of to-be-called objects (the second client 300 or the group including the plurality of second clients 300).
  • the to-be-called object whose activity rank is at a preset threshold is extracted from a plurality of to-be-called objects.
  • the extracted information of the object to be summoned is sent to the first client 200.
  • the user of the first client 200 can select the object to be summoned from the received information of the object to be summoned according to the needs of the user, thereby obtaining the to-call information to be summoned, such as the to-be-called ID, the name of the group to be summoned, and the like. In this way, the problem that the user of the first client 200 randomly selects the object to be summoned and the summoning success rate is low is avoided when the user of the first client 200 is unaware of the activity of other users.
  • Step S103 After receiving the calling request, the server 100 sends the calling information corresponding to the calling request to the second client 300 pointed to by the calling request.
  • the calling function provided by the embodiment can improve the user's willingness to pay to a certain extent, in other words, the user who needs to reach a certain level can initiate the calling.
  • the calling method before performing step S103, the calling method further includes the following steps:
  • step S10 the server 100 detects whether the account level of the first client 200 reaches a preset summoning level. If the preset summoning level is not reached, the following step S20 is performed, and if the preset calling level is reached, Then the following step S30 is performed.
  • step S20 it is determined that the first client 200 does not have the calling right, and returns the summoning failure information to the first client 200.
  • Step S30 determining that the first client 200 has a calling right, and performing a step of transmitting the calling information corresponding to the calling request to the second client 300 pointed to by the calling request.
  • the first client 200 may send a summoning request to the server 100, where the calling request may carry account information of the user of the first client 200, such as an account level and an account consumption record. Wait. The higher the user's consumption amount is, the higher the account level is.
  • the summoning function provided by the embodiment is mainly for high-consumption, high-level users, and such users can have summoning rights.
  • the server 100 may pre-store the summoning level with the summoning authority, and after receiving the account information of the first client 200, the account information may be compared with the pre-stored summoning level.
  • the account level of the first client 200 reaches the preset summoning level, it indicates that it has the calling right. If the preset summoning level is not reached, it indicates that it does not have the calling right, and the calling failure information may be returned to the first client 200 to prompt the user of the first client 200. In this way, users who do not reach the summoning level can be stimulated to increase their account level.
  • the server 100 after the server 100 receives the calling request sent by the first client 200 and verifies that the first client 200 has the calling right, the server can obtain the to-call ID and the name of the group to be summoned carried in the URL, thereby obtaining The information of the second client 300 to be summoned.
  • the server 100 sends the summoning information corresponding to the calling request to the second client 300 pointed to by the to-be-called call request.
  • the calling information may be sent to the server 100 by the first client 200, or may be the first client obtained by the server 100 according to the login information, the attention information, and the like of the first client 200.
  • the obtained summoning information may include target live broadcast information, a jump type, and a jump group information.
  • the target live broadcast information includes a live broadcast room ID, a live broadcast room play type, and the like, and the target live broadcast room is a live broadcast room for which the user of the first client 200 is pre-directed.
  • the jump type may be a video chat live jump type or a game live jump type.
  • the jump group information includes information about the client to be called pointed to by the call request initiated by the first client 200, and may be, for example, all clients in a QQ group, and may be all clients in a chat group. Etc., specifically, no limitation.
  • Step S105 After receiving the summoning information, the second client 300 obtains a corresponding summoning notification according to the calling information.
  • step S105 may include three sub-steps of step S1051, step S1053, and step S1055.
  • Step S1051 After receiving the summoning information, the second client 300 displays a summoning button on the current playing interface.
  • step S1053 when the summoning button is clicked, the defaultCenter function in the notification center class is called to obtain the notification center.
  • step S1055 the summoning information is thrown in the form of a call notification by using the postNotificationName function in the notification center.
  • a bullet box may be popped up on the current playing interface, and the bullet box may be an interface.
  • a call button is displayed on the interface. If the user of the second client 300 rejects the call request, the interface can be closed directly to end the summoning process. If the user of the second client 300 pre-receives the summoning request, the call button may be clicked to respond to the summoning request. When it is detected that the summon button is clicked, a summoning notification event is triggered, and the second client 300 can throw the summoning notification.
  • the second client 300 includes a receiving module for receiving the summoning information and throwing the calling information in the form of a summoning notification, and a response module for responding to the calling notification.
  • the receiving module may call the defaultCenter function in the notification center class NSNotificationCenter to obtain the notification center when detecting that the summoning button is clicked.
  • the received summoning information is constructed as a dictionary, and the constructed dictionary is thrown in the form of a call notification by using the postNotificationName function in the notification center.
  • the server 100 may push the summoning information corresponding to the calling request to the called second client 300.
  • the summoning information is thrown in the form of a summoning notification. Calling is completed in the form of summoning notification, which ensures easy decoupling between different functional modules and improves jump efficiency.
  • Step S107 The second client 300 responds to the call notification and jumps from the current play interface to the target live broadcast room carried by the call notification.
  • the calling method before performing step S107, the calling method further includes the following steps:
  • Step S301 the second client 300 invokes a defaultCenter function in the notification center class to obtain a management class to the notification center.
  • Step S303 using the addObserver function in the management class of the notification center to set the interception information for monitoring the call notification.
  • the second client 300 may pre-establish a listening event for monitoring whether a subsequent call notification is thrown, wherein the monitoring function may be built in the foregoing response module of the second client 300.
  • the second client 300 can enter the listening mode after each booting to monitor whether there is a request that is called by another client.
  • step S107 may include two sub-steps of step S1071 and step S1073.
  • Step S1071 After the booting, the second client 300 enters the listening mode according to the monitoring information, and obtains the calling information corresponding to the calling notification after the call notification is monitored.
  • Step S1073 Jumping from the current playing interface to the target live broadcast room carried by the calling information according to the calling information.
  • the second client 300 can enter the listening mode according to the pre-established monitoring information.
  • the response module can monitor whether the receiving module has a call notification, and if the call notification sent by the receiving module is monitored, the call information corresponding to the call notification can be obtained.
  • the summoning information is in the above-mentioned dictionary form, and the response module can obtain the target live broadcast information, the jump type, and the jump group information from the dictionary. After obtaining the above summoning information, the current playing interface can be jumped to the target live broadcast room included in the summoning information. In this way, the user of the first client 200 can achieve the purpose of diverting the user of the second client 300 to his favorite live room.
  • the window of the current play interface needs to be closed.
  • the second client may invoke the management class of the live broadcast window to The live room window on the playback interface is closed.
  • the second client 300 can enter the listening mode after the booting to monitor the summoning notification, so that the all-information monitoring of all the calling notifications can be well realized.
  • the first client 200 is further configured to obtain to-be-called summoned information to be called when detecting that the pre-established calling portal is clicked;
  • the information is spliced to form a URL, and a call request carrying the URL is sent to the server 100.
  • the first client 200 is configured to initiate a query request to the server 100 when detecting that a pre-established call-in portal is clicked.
  • the server 100 is configured to, after receiving the query request, extract, from the plurality of to-be-called objects, the to-be-called object whose activity ranking is at a preset threshold according to the pre-stored activity information of the plurality of objects to be summoned. And feeding back the information of the object to be summoned to the first client 300, wherein the object to be summoned is a second client 300 or a group consisting of multiple second clients 300.
  • the first client 200 is configured to receive information of the object to be summoned sent by the server 100, and obtain the to-be-called call information to be called according to the information of the object to be summoned.
  • the to-be-called information includes a plurality of sub-information.
  • the first client 200 is configured to construct a URL template based on a base class protocol, where the URL template of the base class protocol In the form of a string; each of the sub-information is combined according to the URL template of the base class protocol, and a specified character is added between adjacent two sub-information to be spliced to form a URL, and sent to the server 100.
  • a call request carrying the URL carrying the URL.
  • the server 100 is further configured to detect whether the account level of the first client 200 reaches a preset summoning level, and if the preset calling level is not reached, determine that the first client 200 does not have Summoning the right, and returning the summoning failure information to the first client 200; if the preset calling level is reached, determining that the first client 200 has the calling right, and the second client pointed to the calling request 300 sends a summoning information corresponding to the summoning request.
  • the calling method and the calling system provided by the embodiment of the present application establish a calling call in advance, and initiate a calling request to the server 100 when the calling portal is clicked, and use the server 100 to point to the second customer that the calling request is directed to.
  • the terminal 300 sends the corresponding summoning information, and the second client 300 obtains the corresponding calling notification according to the calling information, and after responding to the calling notification by itself, jumps to the target live broadcast room carried by the calling notification.
  • the summoning program can be automatically summoned in the live broadcast room, which realizes an automated process, and is more targeted, and the summoning drainage effect is better.
  • each block of the flowchart or block diagram can represent a module, a program segment, or a portion of code that includes one or more of the Executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may also occur in a different order than those illustrated in the drawings.
  • each block of the block diagrams and/or flowcharts, and combinations of blocks in the block diagrams and/or flowcharts can be implemented in a dedicated hardware-based system that performs the specified function or function. Or it can be implemented by a combination of dedicated hardware and computer instructions.
  • the summoning program can be automatically summoned in the live broadcast room, which realizes an automated process, and is more targeted, and the summoning drainage effect is better.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • General Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Graphics (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Telephonic Communication Services (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请实施例提供了一种召唤方法及召唤系统，该召唤系统包括服务端及与服务端通信连接的第一客户端和第二客户端，该方法包括：第一客户端在检测到预先建立的召唤入口被点击时，向服务端发起召唤请求；服务端在接收到召唤请求后，向召唤请求指向的第二客户端发送与召唤请求对应的召唤信息；第二客户端在接收到召唤信息后，根据召唤信息得到对应的召唤通知；第二客户端响应召唤通知，并从当前播放界面跳转至召唤通知携带的目标直播间。该召唤方案可在直播间内自动进行召唤，实现了一个自动化的过程，且针对性更强，召唤引流效果更佳。

Description

一种召唤方法及召唤系统
相关申请的交叉引用
本申请要求于2018年02月28日提交中国专利局的申请号为2018101691857、名称为“一种召唤方法及召唤系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及互联网应用开发技术领域，具体而言，涉及一种召唤方法及召唤系统。
背景技术
在视频直播领域，常有用户为了增加自己所喜欢的主播的被关注程度，从而将喜欢的主播的直播信息分享到朋友圈或者QQ群，以人工打广告的方式为喜欢的主播集聚粉丝，以达到引流的目的。但这种方式需人工操作以分享直播信息，存在操作复杂且针对性不强的缺陷。
发明内容
有鉴于此，本申请的目的包括，提供一种召唤方法及召唤系统以改善上述问题。
本申请实施例提供一种召唤方法，应用于召唤系统，该召唤系统包括服务端，以及分别与所述服务端通信连接的第一客户端和第二客户端，所述方法包括：
所述第一客户端在检测到预先建立的召唤入口被点击时，向所述服务端发起召唤请求；
所述服务端在接收到所述召唤请求后，向所述召唤请求指向的第二客户端发送与所述召唤请求对应的召唤信息；
所述第二客户端在接收到所述召唤信息后，根据所述召唤信息得到对应的召唤通知；
所述第二客户端响应所述召唤通知，并从当前播放界面跳转至所述召唤通知携带的目标直播间。
可选地，所述召唤入口通过以下步骤获得：
所述第一客户端使用按钮类中的alloc函数以创建召唤入口信息；
利用imageNamed函数为所述召唤入口信息设置召唤入口图片，并将所述召唤入口图片插入至当前播放界面中，以得到对应的召唤入口。
可选地，所述将所述召唤入口图片插入至当前播放界面中，以得到对应的召唤入口 的步骤，包括：
调用addsubView函数将所述召唤入口图片插入至当前播放界面中的指定层级之上；或者
调用belowSubview函数将所述召唤入口图片插入至当前播放界面中的指定层级之下。
可选地，所述第一客户端在检测到预先建立的召唤入口被点击时，向所述服务端发起召唤请求的步骤，包括：
所述第一客户端在检测到预先建立的召唤入口被点击时，获得待召唤的待召唤信息；
将所述待召唤信息进行拼接以构成一个URL，并向所述服务端发送携带有所述URL的召唤请求。
可选地，所述第一客户端在检测到预先建立的召唤入口被点击时，获得待召唤的待召唤信息的步骤，包括：
所述第一客户端在检测到预先建立的召唤入口被点击时，向所述服务端发起查询请求；
所述服务端在接收到所述查询请求后，根据预存的多个待召唤对象的活跃度信息从多个待召唤对象中提取出活跃度排行处于前预设阈值位的待召唤对象，并将所述待召唤对象的信息反馈给所述第一客户端，其中，所述待召唤对象为第二客户端或由多个第二客户端组成的群体；
所述第一客户端接收所述服务端发送的待召唤对象的信息，根据所述待召唤对象的信息获得待召唤的待召唤信息。
可选地，所述待召唤信息包括多个子信息，所述将所述待召唤信息进行拼接以构成一个URL，并向所述服务端发送携带有所述URL的召唤请求的步骤，包括：
构建一个基于基类协议的URL模板，其中，所述基类协议的URL模板为字符串形式；
按所述基类协议的URL模板将各所述子信息进行组合，并在相邻两个子信息之间添加指定字符进行拼接以构成一个URL，并向所述服务端发送携带有所述URL的召唤请求。
可选地，所述待召唤信息包括待召唤ID以及待召唤群体名称。
可选地，所述第二客户端在接收到所述召唤信息后，根据所述召唤信息得到对应的召唤通知的步骤，包括：
所述第二客户端在接收到所述召唤信息后，在当前播放界面显示召唤按钮；
在所述召唤按钮被点击时，调用通知中心类中的defaultCenter函数以获取到通知中心；
利用所述通知中心中的postNotificationName函数将所述召唤信息以召唤通知的形式抛出。
可选地，所述第二客户端响应所述召唤通知，并从当前播放界面跳转至所述召唤信息携带的目标直播间的步骤之前，所述方法还包括：
所述第二客户端调用通知中心类中的defaultCenter函数以获取到通知中心的管理类；
利用所述通知中心的管理类中的addObserver函数设置用于监听召唤通知的监听信息。
可选地，所述第二客户端响应所述召唤通知，并从当前界面跳转至所述召唤通知携带的目标直播间的步骤，包括：
所述第二客户端在开机启动后根据所述监听信息进入监听模式，并在监听到召唤通知后获得该召唤通知对应的召唤信息；
根据所述召唤信息从当前播放界面跳转至所述召唤信息携带的目标直播间。
可选地，所述根据所述召唤信息从当前播放界面跳转至所述召唤信息携带的目标直播间的步骤之前，所述方法还包括：
所述第二客户端调用直播间窗口的管理类以将当前播放界面上的直播间窗口关闭。
可选地，所述召唤信息包括目标直播间信息、跳转类型以及跳转群体信息。
可选地，所述向所述召唤请求指向的第二客户端发送与所述召唤请求对应的召唤信息的步骤之前，所述方法还包括：
所述服务端检测所述第一客户端的账户等级是否达到预设的召唤等级，若未达到预设的召唤等级，则判定所述第一客户端不具有召唤权限，并向所述第一客户端返回召唤失败信息；
若达到预设的召唤等级，则判定所述客户端具有召唤权限，并执行向所述召唤请求指向的第二客户端发送与所述召唤请求对应的召唤信息的步骤。
本申请实施例还提供一种召唤系统，所述召唤系统包括服务端，以及分别与所述服务端通信连接的第一客户端和第二客户端；
所述第一客户端用于在预先建立的召唤入口被点击时，向所述服务端发起召唤请求；
所述服务端用于在接收到所述召唤请求后，向所述召唤请求指向的第二客户端发送与所述召唤请求对应的召唤信息；
所述第二客户端用于在接收到所述召唤信息后，根据所述召唤信息得到对应的召唤通知；
所述第二客户端还用于响应所述召唤通知，并从当前播放界面跳转至所述召唤通知携带的目标直播间。
可选地，所述第一客户端配置成在检测到预先建立的召唤入口被点击时，获得待召唤的待召唤信息；
将所述待召唤信息进行拼接以构成一个URL，并向所述服务端发送携带有所述URL的召唤请求。
可选地，所述第一客户端配置成在检测到预先建立的召唤入口被点击时，向所述服务端发起查询请求；
所述服务端配置成在接收到所述查询请求后，根据预存的多个待召唤对象的活跃度信息从多个待召唤对象中提取出活跃度排行处于前预设阈值位的待召唤对象，并将所述待召唤对象的信息反馈给所述第一客户端，其中，所述待召唤对象为第二客户端或由多个第二客户端组成的群体；
所述第一客户端配置成接收所述服务端发送的待召唤对象的信息，根据所述待召唤对象的信息获得待召唤的待召唤信息。
可选地，所述待召唤信息包括多个子信息，所述第一客户端配置成构建一个基于基类协议的URL模板，其中，所述基类协议的URL模板为字符串形式；按所述基类协议的URL模板将各所述子信息进行组合，并在相邻两个子信息之间添加指定字符进行拼接以构成一个URL，并向所述服务端发送携带有所述URL的召唤请求。
可选地，所述服务端配置成检测所述第一客户端的账户等级是否达到预设的召唤等级，若未达到预设的召唤等级，则判定所述第一客户端不具有召唤权限，并向所述第一客户端返回召唤失败信息；若达到预设的召唤等级，则判定所述第一客户端具有召唤权限，并向所述召唤请求指向的第二客户端发送与所述召唤请求对应的召唤信息。
本申请实施例提供的召唤方法及召唤系统，通过预先建立召唤入口，并在召唤入口被点击时向服务端发起召唤请求，利用服务端向召唤请求指向的第二客户端发送对应的召唤信息，第二客户端根据召唤信息得到对应的召唤通知，并在自身响应该召唤通知后，跳转至该召唤通知携带的目标直播间。该召唤方案可在直播间内自动进行召唤，实现了一个自动化的过程，且针对性更强，召唤引流效果更佳。
为使本申请的上述目的、特征和优点能更明显易懂，下文特举较佳实施例，并配合所附附图，作详细说明如下。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，应当理解，以下附图仅示出了本申请的某些实施例，因此不应被看作是对范围的限定，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他相关的附图。
图1为本申请实施例提供的一种召唤系统的结构框图。
图2为本申请实施例提供的一种召唤方法的流程图。
图3为本申请实施例提供的创建召唤入口的方法的流程图。
图4为图2中步骤S101的子步骤的流程图。
图5为图4中步骤S1011的子步骤的流程图。
图6为本申请实施例提供的召唤方法的另一流程图。
图7为图2中步骤S105的子步骤的流程图。
图8为本申请实施例提供的召唤方法的另一流程图。
图9为图2中步骤S107的子步骤的流程图。
图标：100-服务端；200-第一客户端；300-第二客户端。
具体实施方式
随着视频直播技术的快速发展，在客户端中为了提高用户的付费意愿，特别是为了提高有些高付费、高消费用户的粘性和特权，设计了一种给予这些用户召唤其他客户端的用户的权利，以让这些用户可以为自己喜欢的主播召唤一些粉丝到其直播间，以增加这些主播的被关注的程度。因此，本申请特开发了一种部落的召唤功能，这种召唤功能可以很快地集聚大批量的粉丝，可以达到引流的目的。同时可以提高这些高付费、高消费用户的付费意愿。将传统的用户为某个主播引流采用的分享到朋友圈或者QQ群的这种人工打广告的方式转变为在直播间内的自动进行召唤的方式，实现了一个自动化的过程，在召唤引流流程上是一个创新。
下面将结合本申请实施例中附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。通常在此处附图中描述和示出的本申请实施例的组件可以以各种不同的配置来布置和设计。因此，以下对在附图中提供的本申请的实施例的详细描述并非旨在限制要求保护的本申 请的范围，而是仅仅表示本申请的选定实施例。基于本申请的实施例，本领域技术人员在没有做出创造性劳动的前提下所获得的所有其他实施例，都属于本申请保护的范围。
应注意到：相似的标号和字母在下面的附图中表示类似项，因此，一旦某一项在一个附图中被定义，则在随后的附图中不需要对其进行进一步定义和解释。同时，在本申请的描述中，除非另有明确的规定和限定，术语“安装”、“设置”、“连接”应做广义理解，例如，可以是固定连接，也可以是可拆卸连接，或一体地连接；可以是机械连接，也可以是电连接；可以是直接相连，也可以通过中间媒介间接相连，可以是两个元件内部的连通。对于本领域的普通技术人员而言，可以具体情况理解上述术语在本申请中的具体含义。
本申请较佳实施例提供了一种召唤系统，如图1所示，所述召唤系统包括服务端100、第一客户端200和第二客户端300。所述第一客户端200和第二客户端300通过网络与所述服务端100通信连接，以进行数据通信或交互。其中，所述第一客户端200和第二客户端300可以是但不限于个人电脑、平板电脑、智能手机、移动上网设备等。所述第一客户端200和第二客户端300上安装有视频直播应用软件，以供用户进行视频直播。所述服务端100为对应于所述第一客户端200和第二客户端300上安装的视频直播应用软件的后台服务器，即可提供视频直播平台。所述服务端100可以是网络服务器、数据库服务器，可以是单独的服务器也可以是服务器集群等。
在本实施例中，所述第一客户端200配置成在预先建立的召唤入口被点击时，向所述服务端100发起召唤请求。所述服务端100配置成在接收到所述召唤请求后，向所述召唤请求指向的第二客户端300发送与所述召唤请求对应的召唤信息。所述第二客户端300配置成在接收到所述召唤信息后，根据所述召唤信息得到对应的召唤通知。所述第二客户端300配置成响应所述召唤通知，并从当前播放界面跳转至所述召唤通知携带的目标直播间。
请参阅图2，为本申请实施例提供的一种应用于上述召唤系统的召唤方法的流程图。所应说明的是，本申请实施例提供的方法不以图2及以下所述的具体顺序为限制。下面将对图2中所示出的各步骤进行详细说明。
步骤S101，所述第一客户端200在检测到预先建立的召唤入口被点击时，向所述服务端100发起召唤请求。
请参阅图3，在本实施例中，所述第一客户端200可通过以下步骤创建所述召唤入口：
步骤S201，所述第一客户端200使用按钮类中的alloc函数以创建召唤入口信息。
步骤S203，利用imageNamed函数根据所述召唤入口信息设置召唤入口图片，并将所述召唤入口图片插入至当前播放界面中，以得到对应的召唤入口。
在本实施例中，首先可定义一个变量，可用该变量来保存召唤入口信息，例如该变量可命名为_tribalEntrance。并使用按钮类UIButton中的alloc函数以创建召唤入口信息，可选地，可对召唤入口进行初始化处理，例如，本实施例中可利用init函数对所述召唤入口进行初始化处理。并设置召唤入口的坐标值，即设置召唤入口在直播界面上的展示位置。在实施时，召唤入口的位置可根据具体需求进行设置。所述召唤入口信息即包括上述的初始化信息、坐标值信息等。
本实施例中，利用imageNamed函数根据所述召唤入口信息为预添加的召唤入口设置召唤入口图片，并将召唤入口图片插入至当前播放界面中以得到最终的召唤入口，该召唤入口由外部的播放界面上的召唤入口图片以及内部的具体的召唤入口信息所构成。在本实施例中，可通过以下方式将所述召唤入口图片插入至当前播放界面中：
调用addSubView函数将所述召唤入口图片插入至当前播放界面中的指定层级之上。或者，调用belowSubView函数将所述召唤入口图片插入至当前播放界面中的指定层级之下。
通过上述设置，添加了一个召唤入口，该召唤入口是用户能够进行自主召唤的基础，并且该召唤入口还可灵活采用上述的addSubView函数或者belowSubView函数将召唤入口图片灵活插入至当前播放界面的不同层级中，能够有效地解决添加召唤入口的冲突问题，且可以较好地处理不同的层级关系。
请参阅图4，在本实施例中，步骤S101可以包括步骤S1011以及步骤S1013两个子步骤。
步骤S1011，所述第一客户端200在检测到预先建立的召唤入口被点击时，获得待召唤的待召唤信息。
步骤S1013，将所述待召唤信息进行拼接以构成一个URL，并向所述服务端100发送携带有所述URL的召唤请求。
本实施例中，当用户需要发起召唤时，可点击播放界面上的召唤入口图片，可选地，用户可输入待召唤的待召唤信息，该待召唤信息可包括待召唤ID、待召唤群体名称等。第一客户端200将上述待召唤信息进行拼接以构成一个URL(Uniform Resource Locator，统一资源定位符)，可选地，例如首先可构造一个基于基类协议的URL模板，这个基类协议的URL模板可以是字符串类型，如douyuapp://DouyuMail。而所述待召唤信息可包括多个子信息，可按所述基类协议的URL模板将上述待召唤信息包含的多个子信息进 行组合，并在相邻两个子信息之间添加指定字符，例如字符&，以将各子信息分隔开，如此将待召唤信息进行拼接以构建成一个新的URL。在将上述子信息拼接为一个完整的URL后，使用系统的URL跳转功能模块，利用该URL跳转功能模块向所述服务端100发送携带有所述URL的召唤请求，即所述召唤请求携带有上述的待召唤信息，如待召唤ID、待召唤群体名称等。所述第一客户端200将所述召唤请求发送至服务端100，以告知服务端100进行后续召唤操作。
通过上述设置，当用户发起召唤的时候，使用协议的URL的方式实现跳转可以有效降低代码的耦合性，并且URL可方便地携带参数且方便传值。
除了上述所采用的用户输入待召唤信息的方式之外，本实施例的另一实施方式中，所述待召唤信息可由所述服务端推送至所述第一客户端。可选地，请参阅图5，在本实施例中，步骤S1011可以包括以下子步骤：
步骤S10111，所述第一客户端200在检测到预先建立的召唤入口被点击时，向所述服务端100发起查询请求。
步骤S10113，所述服务端100在接收到所述查询请求后，根据预存的多个待召唤对象的活跃度信息从多个待召唤对象中提取出活跃度排行处于前预设阈值位的待召唤对象，并将所述待召唤对象的信息反馈给所述第一客户端200，其中，所述待召唤对象为第二客户端300或由多个第二客户端300组成的群体。
步骤S10115，所述第一客户端200接收所述服务端100发送的待召唤对象的信息，根据所述待召唤对象的信息获得待召唤的待召唤信息。
由于有一些用户较为活跃，即与其他用户之间互动较为频繁，而有一些用户较沉默，较少与其他用户进行互动。本实施例中，为了提高召唤引流的成功率，可选择性地向较为活跃的用户发起召唤。可选地，第一客户端200在检测到召唤事件被触发时，可向服务端100发起查询请求。服务端100可根据各客户端的互动情况，预先对各客户端进行活跃度的排序，或者是对包含多个客户端的群体的活跃度进行排序并保存。如此，服务端在接收到第一客户端200发送的查询请求时，可根据预存的多个待召唤对象(第二客户端300或者是包括多个第二客户端300的群体)的活跃度信息从多个待召唤对象中提取出活跃度排行处于预设阈值位的待召唤对象。并将提取出的待召唤对象的信息发送至第一客户端200。第一客户端200的用户可根据自身的需求从接收到的待召唤对象的信息中选择出预召唤的对象，从而获得待召唤的待召唤信息，例如待召唤ID、待召唤群体名称等。如此，则可避免第一客户端200的用户在对其他用户的活跃度不知情的情况下，随机选择待召唤对象而造成的召唤成功率较低的问题。步骤S103，所述服务端100 在接收到所述召唤请求后，向所述召唤请求指向的第二客户端300发送与所述召唤请求对应的召唤信息。
由上述可知，本实施例提供的召唤功能一定程度上可提高用户的付费意愿，换言之，则需要达到一定等级的用户才能够发起召唤。请参阅图6，本实施例中，在执行步骤S103之前，所述召唤方法还包括以下步骤：
步骤S10，所述服务端100检测所述第一客户端200的账户等级是否达到预设的召唤等级，若未达到预设的召唤等级，则执行以下步骤S20，若达到预设的召唤等级，则执行以下步骤S30。
步骤S20，判定所述第一客户端200不具有召唤权限，并向所述第一客户端200返回召唤失败信息。
步骤S30，判定所述第一客户端200具有召唤权限，并执行向所述召唤请求指向的第二客户端300发送与所述召唤请求对应的召唤信息的步骤。
本实施例中，第一客户端200检测到召唤事件被触发后，可发送召唤请求至服务端100，该召唤请求可携带第一客户端200的用户的账户信息，例如账户等级、账户消费记录等。用户的消费金额越高则其账户等级越高，而由上述可知，本实施例提供的召唤功能主要面向高消费、高等级的用户，这类用户可具有召唤权限。可选地，服务端100可预存具有召唤权限的召唤等级，在接收到第一客户端200的账户信息后，可将该账户信息与预存的召唤等级进行比对。若该第一客户端200的账户等级达到预设的召唤等级，则表明其具有召唤权限。若未达到预设的召唤等级，则表明其不具有召唤权限，可向第一客户端200返回召唤失败信息，以提示第一客户端200的用户。如此，可刺激未达到召唤等级的用户进行消费以提高其账户等级。
本实施例中，在服务端100接收到第一客户端200发送的召唤请求且验证该第一客户端200具有召唤权限之后，可获取URL中携带的待召唤ID、待召唤群体名称，从而获得待召唤的第二客户端300的信息。
所述服务端100向该待召唤请求指向的第二客户端300发送与召唤请求对应的召唤信息。其中，该召唤信息可以为所述第一客户端200发送至服务端100的，也可以是所述服务端100根据所述第一客户端200的登陆信息、关注信息等所获得的第一客户端200所喜爱的直播间信息以及与此直播间信息对应的跳转信息等。具体方式本实施例不作限制。本实施例中，所获得的召唤信息可以包括目标直播间信息、跳转类型以及跳转群体信息。目标直播间信息包括直播间ID、直播间播放类型等，该目标直播间即为第一客户端200的用户预为其引流的直播间。所述跳转类型可为视频聊天直播跳转类型或游戏 直播跳转类型。所述跳转群体信息即包括了第一客户端200发起的召唤请求所指向的待召唤的客户端的信息，例如可以为一个QQ群中的所有客户端，可以为一个聊天组中的所有客户端等，具体地不作限制。
步骤S105，所述第二客户端300在接收到所述召唤信息后，根据所述召唤信息得到对应的召唤通知。
请参阅图7，在本实施例中，步骤S105可以包括步骤S1051、步骤S1053以及步骤S1055三个子步骤。
步骤S1051，所述第二客户端300在接收到所述召唤信息后，在当前播放界面显示召唤按钮。
步骤S1053，在所述召唤按钮被点击时，调用通知中心类中的defaultCenter函数以获取到通知中心。
步骤S1055，利用所述通知中心中的postNotificationName函数将所述召唤信息以召唤通知的形式抛出。
本实施例中，在召唤请求指向的第二客户端300接收到服务端100推送的召唤信息后，可在其当前播放界面弹出一个弹框，该弹框可为一个界面。在该界面上显示一召唤按钮。第二客户端300的用户若拒绝该召唤请求可直接关闭该界面以结束召唤流程。若第二客户端300的用户预接收该召唤请求可点击该召唤按钮以响应该召唤请求。当检测到该召唤按钮被点击时，会触发一个召唤通知事件，并且该第二客户端300可将该召唤通知抛出。
可选地，所述第二客户端300包括用于接收所述召唤信息并将所述召唤信息以召唤通知的形式抛出的接收模块，以及用于响应所述召唤通知的响应模块。其中，在检测到所述召唤按钮被点击时，所述接收模块可调用通知中心类NSNotificationCenter中的defaultCenter函数以获取到通知中心。并将接收到的上述召唤信息构建为一个字典，利用所述通知中心中的postNotificationName函数将构建的字典以召唤通知的形式抛出。
通过上述设置，服务端100在接收到第一客户端200的召唤请求后，可推送召唤请求对应的召唤信息至被召唤的第二客户端300。当第二客户端300在接收到服务端100发送的召唤信息后，会将召唤信息以召唤通知的形式抛出。采用召唤通知的形式完成召唤，可保证不同的功能模块之间方便解耦，提高跳转效率。
步骤S107，所述第二客户端300响应所述召唤通知，并从当前播放界面跳转至所述召唤通知携带的目标直播间。
请参阅图8，在本实施例中，在执行步骤S107之前，所述召唤方法还包括以下步骤：
步骤S301，所述第二客户端300调用通知中心类中的defaultCenter函数以获取到通知中心的管理类。
步骤S303，利用所述通知中心的管理类中的addObserver函数设置用于监听召唤通知的监听信息。
本实施例中，第二客户端300可预先建立监听事件，以用于监听后续是否有召唤通知抛出，其中，该监听功能可构建于所述第二客户端300的上述的响应模块。通过构建监听事件，第二客户端300在每次开机启动后即可进入监听模式，以监听是否有被其他客户端召唤的请求。
请参阅图9，在本实施例中，步骤S107可以包括步骤S1071和步骤S1073两个子步骤。
步骤S1071，所述第二客户端300在开机启动后根据所述监听信息进入监听模式，并在监听到召唤通知后获得该召唤通知对应的召唤信息。
步骤S1073，根据所述召唤信息从当前播放界面跳转至所述召唤信息携带的目标直播间。
第二客户端300在开机启动后，即可根据预先建立的监听信息进入监听模式。所述响应模块可监听上述的接收模块是否有抛出召唤通知，若监听到接收模块抛出的召唤通知，即可获得该召唤通知对应的召唤信息。该召唤信息为上述的字典形式，响应模块可从该字典中获得目标直播间信息、跳转类型以及跳转群体信息等。在获得上述召唤信息后即可从当前播放界面跳转至该召唤信息包括的目标直播间。如此，第一客户端200的用户即可实现将第二客户端300的用户引流至其喜欢的直播间的目的。
可选地，第二客户端300在从当前播放界面跳转至目标直播间之前，需将当前播放界面的窗口关闭，例如所述第二客户端可调用直播间窗口的管理类的以将当前播放界面上的直播间窗口关闭。
通过上述设置，第二客户端300在开机启动后即可进入监听模式以监听召唤通知，如此可很好地实现对所有的召唤通知的无遗漏的监听。
进一步地，在本实施例所提供的召唤系统中，所述第一客户端200还被配置成在检测到预先建立的召唤入口被点击时，获得待召唤的待召唤信息；将所述待召唤信息进行拼接以构成一个URL，并向所述服务端100发送携带有所述URL的召唤请求。
在本实施例中，具体地，所述第一客户端200配置成在检测到预先建立的召唤入口被点击时，向所述服务端100发起查询请求。
所述服务端100配置成在接收到所述查询请求后，根据预存的多个待召唤对象的活 跃度信息从多个待召唤对象中提取出活跃度排行处于前预设阈值位的待召唤对象，并将所述待召唤对象的信息反馈给所述第一客户端300，其中，所述待召唤对象为第二客户端300或由多个第二客户端300组成的群体。
所述第一客户端200配置成接收所述服务端100发送的待召唤对象的信息，根据所述待召唤对象的信息获得待召唤的待召唤信息。
其中，在本实施例中，所述待召唤信息包括多个子信息，具体地，所述第一客户端200配置成构建一个基于基类协议的URL模板，其中，所述基类协议的URL模板为字符串形式；按所述基类协议的URL模板将各所述子信息进行组合，并在相邻两个子信息之间添加指定字符进行拼接以构成一个URL，并向所述服务端100发送携带有所述URL的召唤请求。
进一步地，所述服务端100还配置成检测所述第一客户端200的账户等级是否达到预设的召唤等级，若未达到预设的召唤等级，则判定所述第一客户端200不具有召唤权限，并向所述第一客户端200返回召唤失败信息；若达到预设的召唤等级，则判定所述第一客户端200具有召唤权限，并向所述召唤请求指向的第二客户端300发送与所述召唤请求对应的召唤信息。
综上所述，本申请实施例提供的召唤方法及召唤系统，通过预先建立召唤入口，并在召唤入口被点击时向服务端100发起召唤请求，利用服务端100向召唤请求指向的第二客户端300发送对应的召唤信息，第二客户端300根据召唤信息得到对应的召唤通知，并在自身响应该召唤通知后，跳转至该召唤通知携带的目标直播间。该召唤方案可在直播间内自动进行召唤，实现了一个自动化的过程，且针对性更强，召唤引流效果更佳。
在本申请所提供的实施例中，应该理解到，所揭露的装置和方法，也可以通过其它的方式实现。以上所描述的装置实施例仅仅是示意性的，例如，附图中的流程图和框图显示了根据本申请的实施例的装置、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段或代码的一部分，所述模块、程序段或代码的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现方式中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个连续的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合，可以用执行规定的功能或动作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
以上所述仅为本申请的优选实施例而已，并不用于限制本申请，对于本领域的技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。应注意到：相似的标号和字母在下面的附图中表示类似项，因此，一旦某一项在一个附图中被定义，则在随后的附图中不需要对其进行进一步定义和解释。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。
工业实用性
该召唤方案可在直播间内自动进行召唤，实现了一个自动化的过程，且针对性更强，召唤引流效果更佳。

Claims (18)

  1. 一种召唤方法，其特征在于，应用于召唤系统，该召唤系统包括服务端，以及分别与所述服务端通信连接的第一客户端和第二客户端，所述方法包括：
    所述第一客户端在检测到预先建立的召唤入口被点击时，向所述服务端发起召唤请求；
    所述服务端在接收到所述召唤请求后，向所述召唤请求指向的第二客户端发送与所述召唤请求对应的召唤信息；
    所述第二客户端在接收到所述召唤信息后，根据所述召唤信息得到对应的召唤通知；
    所述第二客户端响应所述召唤通知，并从当前播放界面跳转至所述召唤通知携带的目标直播间。
  2. 根据权利要求1所述的召唤方法，其特征在于，所述召唤入口通过以下步骤获得：
    所述第一客户端使用按钮类中的alloc函数以创建召唤入口信息；利用imageNamed函数根据所述召唤入口信息设置召唤入口图片，并将所述召唤入口图片插入至当前播放界面中，以得到对应的召唤入口。
  3. 根据权利要求2所述的召唤方法，其特征在于，所述将所述召唤入口图片插入至当前播放界面中，以得到对应的召唤入口的步骤，包括：
    调用addSubView函数将所述召唤入口图片插入至当前播放界面中的指定层级之上；或者
    调用belowSubView函数将所述召唤入口图片插入至当前播放界面中的指定层级之下。
  4. 根据权利要求1-3任意一项所述的召唤方法，其特征在于，所述第一客户端在检测到预先建立的召唤入口被点击时，向所述服务端发起召唤请求的步骤，包括：
    所述第一客户端在检测到预先建立的召唤入口被点击时，获得待召唤的待召唤信息；
    将所述待召唤信息进行拼接以构成一个URL，并向所述服务端发送携带有所述URL的召唤请求。
  5. 根据权利要求4所述的召唤方法，其特征在于，所述第一客户端在检测到预先建立的召唤入口被点击时，获得待召唤的待召唤信息的步骤，包括：
    所述第一客户端在检测到预先建立的召唤入口被点击时，向所述服务端发起查询请求；
    所述服务端在接收到所述查询请求后，根据预存的多个待召唤对象的活跃度信息从多个待召唤对象中提取出活跃度排行处于前预设阈值位的待召唤对象，并将所述待召唤对象的信息反馈给所述第一客户端，其中，所述待召唤对象为第二客户端或由多个第二客户端组成的群体；
    所述第一客户端接收所述服务端发送的待召唤对象的信息，根据所述待召唤对象的信息获得待召唤的待召唤信息。
  6. 根据权利要求4或5所述的召唤方法，其特征在于，所述待召唤信息包括多个子信息，所述将所述待召唤信息进行拼接以构成一个URL，并向所述服务端发送携带有所述URL的召唤请求的步骤，包括：
    构建一个基于基类协议的URL模板，其中，所述基类协议的URL模板为字符串形式；
    按所述基类协议的URL模板将各所述子信息进行组合，并在相邻两个子信息之间添加指定字符进行拼接以构成一个URL，并向所述服务端发送携带有所述URL的召唤请求。
  7. 根据权利要求4-6任意一项所述的召唤方法，其特征在于，所述待召唤信息包括待召唤ID以及待召唤群体名称。
  8. 根据权利要求1-7任意一项所述的召唤方法，其特征在于，所述第二客户端在接收到所述召唤信息后，根据所述召唤信息得到对应的召唤通知的步骤，包括：
    所述第二客户端在接收到所述召唤信息后，在当前播放界面显示召唤按钮；
    在所述召唤按钮被点击时，调用通知中心类中的defaultCenter函数以获取到通知中心；
    利用所述通知中心中的postNotificationName函数将所述召唤信息以召唤通知的形式抛出。
  9. 根据权利要求8所述的召唤方法，其特征在于，所述第二客户端响应所述召唤通知，并从当前播放界面跳转至所述召唤信息携带的目标直播间的步骤之前，所述方法还包括：
    所述第二客户端调用通知中心类中的defaultCenter函数以获取到通知中心的管理类；
    利用所述通知中心的管理类中的addObserver函数设置用于监听召唤通知的监听信息。
  10. 根据权利要求9所述的召唤方法，其特征在于，所述第二客户端响应所述召唤通知，并从当前界面跳转至所述召唤通知携带的目标直播间的步骤，包括：
    所述第二客户端在开机启动后根据所述监听信息进入监听模式，并在监听到召唤通知后获得该召唤通知对应的召唤信息；根据所述召唤信息从当前播放界面跳转至所述召唤信息携带的目标直播间。
  11. 根据权利要求10所述的召唤方法，其特征在于，所述根据所述召唤信息从当前播放界面跳转至所述召唤信息携带的目标直播间的步骤之前，所述方法还包括：
    所述第二客户端调用直播间窗口的管理类以将当前播放界面上的直播间窗口关闭。
  12. 根据权利要求1-11任意一项所述的召唤方法，其特征在于，所述召唤信息包括目标直播间信息、跳转类型以及跳转群体信息。
  13. 根据权利要求1-12任意一项所述的召唤方法，其特征在于，所述向所述召唤请求指向的第二客户端发送与所述召唤请求对应的召唤信息的步骤之前，所述方法还包括：
    所述服务端检测所述第一客户端的账户等级是否达到预设的召唤等级，若未达到预设的召唤等级，则判定所述第一客户端不具有召唤权限，并向所述第一客户端返回召唤失败信息；
    若达到预设的召唤等级，则判定所述第一客户端具有召唤权限，并执行向所述召唤请求指向的第二客户端发送与所述召唤请求对应的召唤信息的步骤。
  14. 一种召唤系统，其特征在于，所述召唤系统包括服务端，以及分别与所述服务端通信连接的第一客户端和第二客户端；
    所述第一客户端配置成在预先建立的召唤入口被点击时，向所述服务端发起召唤请求；
    所述服务端配置成在接收到所述召唤请求后，向所述召唤请求指向的第二客户端发送与所述召唤请求对应的召唤信息；
    所述第二客户端配置成在接收到所述召唤信息后，根据所述召唤信息得到对应的召唤通知；
    所述第二客户端配置成响应所述召唤通知，并从当前播放界面跳转至所述召唤通知携带的目标直播间。
  15. 根据权利要求14所述的召唤系统，其特征在于，所述第一客户端配置成在检测到预先建立的召唤入口被点击时，获得待召唤的待召唤信息；
    将所述待召唤信息进行拼接以构成一个URL，并向所述服务端发送携带有所述URL的召唤请求。
  16. 根据权利要求15所述的召唤系统，其特征在于，所述第一客户端配置成在检测到预先建立的召唤入口被点击时，向所述服务端发起查询请求；
    所述服务端配置成在接收到所述查询请求后，根据预存的多个待召唤对象的活跃度信息从多个待召唤对象中提取出活跃度排行处于前预设阈值位的待召唤对象，并将所述待召唤对象的信息反馈给所述第一客户端，其中，所述待召唤对象为第二客户端或由多个第二客户端组成的群体；
    所述第一客户端配置成接收所述服务端发送的待召唤对象的信息，根据所述待召唤对象的信息获得待召唤的待召唤信息。
  17. 根据权利要求15或16所述的召唤系统，其特征在于，所述待召唤信息包括多个子信息，所述第一客户端配置成构建一个基于基类协议的URL模板，其中，所述基类协议的URL模板为字符串形式；按所述基类协议的URL模板将各所述子信息进行组合，并在相邻两个子信息之间添加指定字符进行拼接以构成一个URL，并向所述服务端发送携带有所述URL的召唤请求。
  18. 根据权利要求14-17任意一项所述的召唤系统，其特征在于，所述服务端配置成检测所述第一客户端的账户等级是否达到预设的召唤等级，若未达到预设的召唤等级，则判定所述第一客户端不具有召唤权限，并向所述第一客户端返回召唤失败信息；若达到预设的召唤等级，则判定所述第一客户端具有召唤权限，并向所述召唤请求指向的第二客户端发送与所述召唤请求对应的召唤信息。
PCT/CN2018/082855 2018-02-28 2018-04-12 一种召唤方法及召唤系统 WO2019165683A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810169185.7 2018-02-28
CN201810169185.7A CN108449391A (zh) 2018-02-28 2018-02-28 一种召唤方法及召唤系统

Publications (1)

Publication Number Publication Date
WO2019165683A1 true WO2019165683A1 (zh) 2019-09-06

Family

ID=63193184

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/082855 WO2019165683A1 (zh) 2018-02-28 2018-04-12 一种召唤方法及召唤系统

Country Status (2)

Country Link
CN (1) CN108449391A (zh)
WO (1) WO2019165683A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112738539A (zh) * 2020-12-25 2021-04-30 广州博冠信息科技有限公司 直播间切换方法及装置、计算机可读存储介质、电子设备

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111343469B (zh) * 2020-02-19 2021-09-28 腾讯科技（深圳）有限公司 一种数据处理方法、装置、电子设备及存储介质
CN111385666B (zh) * 2020-03-04 2022-06-03 北京字节跳动网络技术有限公司 通信链路建立方法、装置、设备及存储介质

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101867576A (zh) * 2010-06-01 2010-10-20 中兴通讯股份有限公司 一种基于ims实现iptv业务用户推荐节目的方法、装置及系统
CN104618785A (zh) * 2014-04-16 2015-05-13 腾讯科技（北京）有限公司 音视频播放方法、装置及系统
CN105847988A (zh) * 2016-03-25 2016-08-10 合网络技术（北京）有限公司 视频分享方法和装置
CN105959207A (zh) * 2016-05-17 2016-09-21 广州酷狗计算机科技有限公司 音视频分享方法及装置
WO2016202128A1 (zh) * 2015-06-16 2016-12-22 腾讯科技（深圳）有限公司 一种消息共享方法及客户端、计算机存储介质
CN106385603A (zh) * 2016-09-12 2017-02-08 腾讯科技（深圳）有限公司 媒体文件的消息传输方法和装置
CN106658200A (zh) * 2016-12-30 2017-05-10 乐蜜科技有限公司 直播视频分享和获取的方法、装置及其终端设备

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101867576A (zh) * 2010-06-01 2010-10-20 中兴通讯股份有限公司 一种基于ims实现iptv业务用户推荐节目的方法、装置及系统
CN104618785A (zh) * 2014-04-16 2015-05-13 腾讯科技（北京）有限公司 音视频播放方法、装置及系统
WO2016202128A1 (zh) * 2015-06-16 2016-12-22 腾讯科技（深圳）有限公司 一种消息共享方法及客户端、计算机存储介质
CN105847988A (zh) * 2016-03-25 2016-08-10 合网络技术（北京）有限公司 视频分享方法和装置
CN105959207A (zh) * 2016-05-17 2016-09-21 广州酷狗计算机科技有限公司 音视频分享方法及装置
CN106385603A (zh) * 2016-09-12 2017-02-08 腾讯科技（深圳）有限公司 媒体文件的消息传输方法和装置
CN106658200A (zh) * 2016-12-30 2017-05-10 乐蜜科技有限公司 直播视频分享和获取的方法、装置及其终端设备

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112738539A (zh) * 2020-12-25 2021-04-30 广州博冠信息科技有限公司 直播间切换方法及装置、计算机可读存储介质、电子设备

Also Published As

Publication number Publication date
CN108449391A (zh) 2018-08-24

Similar Documents

Publication Publication Date Title
US11405350B2 (en) Multi-media processing and displaying method, terminal, and computer storage medium in a social networking application based on interaction information by multiple user accounts
US11362984B2 (en) Matter message notification method, apparatus, and device
US9380264B1 (en) System and method for video communication
US11032232B2 (en) Chat-based support of multiple communication interaction types
US10887657B2 (en) Message transmission method, device and storage medium for media files
US20080034040A1 (en) Method and system for embedded group communication
US20170288942A1 (en) Portal for Provisioning Autonomous Software Agents
KR20180027606A (ko) 디바이스 클라우드 관리
US10802681B2 (en) Actionable notifications
US20080123683A1 (en) Contact initialization based upon automatic profile sharing between computing devices
JP2018532283A (ja) デバイスクラウドの管理
US20170289069A1 (en) Selecting an Autonomous Software Agent
US20170288943A1 (en) Supplying Context Data to a Servicing Entity
US9503410B2 (en) Sharing of activity metadata via messaging systems
WO2019165683A1 (zh) 一种召唤方法及召唤系统
WO2017032268A1 (zh) 实现跨平台交互的方法、终端设备和应用平台
US20080263235A1 (en) Device-to-Device Sharing of Digital Media Assets
CN108377396A (zh) 一种直播录制方法、装置及设备
US9398057B2 (en) System and method for group participation in a digital media presentation
CN113760145A (zh) 一种互动方法、装置、电子设备及存储介质
CN112235594A (zh) 直播连麦的方法及装置、计算机可读介质、电子设备
US20230362115A1 (en) Image display method and apparatus, storage medium, and electronic device
CN111405310A (zh) 直播互动方法、装置、电子设备及存储介质
US20170171510A1 (en) Method and device for leaving video message
JP6618207B2 (ja) 情報処理方法、端末、およびコンピュータストレージ媒体

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18907654

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18907654

Country of ref document: EP

Kind code of ref document: A1