CN104184771A - Call record calling method and device - Google Patents
Call record calling method and device Download PDFInfo
- Publication number
- CN104184771A CN104184771A CN201310196669.8A CN201310196669A CN104184771A CN 104184771 A CN104184771 A CN 104184771A CN 201310196669 A CN201310196669 A CN 201310196669A CN 104184771 A CN104184771 A CN 104184771A
- Authority
- CN
- China
- Prior art keywords
- message registration
- service end
- registration
- request
- indicate
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 45
- 230000004044 response Effects 0.000 claims abstract description 38
- 230000009471 action Effects 0.000 claims abstract description 37
- 230000006854 communication Effects 0.000 claims description 30
- 230000008676 import Effects 0.000 claims description 11
- 230000015654 memory Effects 0.000 description 18
- 238000003860 storage Methods 0.000 description 16
- 238000004891 communication Methods 0.000 description 9
- 238000012797 qualification Methods 0.000 description 7
- 230000000977 initiatory effect Effects 0.000 description 6
- 239000003795 chemical substances by application Substances 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 230000003993 interaction Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- VYZAMTAEIAYCRO-UHFFFAOYSA-N Chromium Chemical compound [Cr] VYZAMTAEIAYCRO-UHFFFAOYSA-N 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000014759 maintenance of location Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 1
- 230000035800 maturation Effects 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 239000000126 substance Substances 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
- H04L12/1818—Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
- Telephonic Communication Services (AREA)
Abstract
The embodiment of the invention provides a call record calling method and a device, which can realize cross-application call record calling. The method comprises steps: a call record calling request sent by a client is received, wherein the call record calling request comprises an action field used for indicating calling operation and a type field used for indicating the data type is the call record; according to the call record calling request, a server capable of providing a call record is determined; a call record acquisition request is sent to the server; and a response message sent by the server according to the call record acquisition request is received, wherein the response message comprises a call record in line with a predefined format or a wrong response indicating a wrong type.
Description
Technical field
The present invention relates to the communications field, and more specifically, relate to message registration call method and equipment.
Background technology
Webpage real time communication (Web Real Time Communication, WebRTC) is one and is intended to the communication technology that network enabled browser carries out real-time voice dialogue or video conversation.Different with traditional multimedia communication mode based on local client or browser plug-in, WebRTC is integrated into browser inside by the necessary audio frequency and video of multimedia communication being processed to the nucleus modules such as (gather, encode, strengthen), Internet Transmission, session control, thereby makes third party's application developer only need can obtain real-time audio/video communication ability by simple JavaScript API Calls.
Nowadays social class application is prevailing, the interchange of WebRTC between can more convenient user, and a lot of browser manufacturer, operator, especially social network sites all will be released the WebRTC business of oneself.When the time comes, user can select any one service provider's WebRTC should be used for carrying out voice or video calling, user will have a lot of message registrations in different WebRTC application like this, and user often cannot remember these message registrations, thus user to have a kind of demand be can call at any time message registration to inquire about or manage.
But the application of current this locality or web application only support this locality of message registration to import/derive, and the message registration that cannot realize across application or webpage calls.
Summary of the invention
The embodiment of the present invention provides a kind of message registration call method and equipment, and the message registration that can realize across application or webpage calls.
First aspect, a kind of message registration call method is provided, comprise: receive the message registration call request that client sends, described message registration call request comprises: be used to indicate the action field of call operation and be used to indicate the type field that data type is message registration; According to described message registration call request, determine the service end that message registration can be provided; To described service end, send message registration and obtain request; Receive the described service end response message that the request of obtaining sends according to described message registration, described response message comprises: meet the message registration of predefined format, or, the errored response of misdirection type.
In conjunction with first aspect, in its first implementation, described message registration call request also comprises additional request condition, wherein said additional request condition comprise following at least one: the character string that is used to indicate object search; Be used to indicate the numerical value that message registration returns to restricted number; Be used to indicate the character string of search condition.
In conjunction with first aspect and above-mentioned implementation thereof, in its second implementation, described according to described message registration call request, determine the service end that message registration can be provided, comprise: to registration center, send described message registration call request, so that described registration center determines the service end list that can provide message registration to call service according to described action field and described type field; Receive the described service end list that described registration center sends; In described service end list, determine the described service end that message registration can be provided.
In conjunction with first aspect and above-mentioned implementation thereof, in its third implementation, describedly in described service end list, determine the described service end that message registration can be provided, comprising: in described service end list, determine that the used service end of user is the described service end that message registration can be provided; Or according to user's selection, in described service end list or in the used service end of user, determine the described service end that message registration can be provided.
In conjunction with first aspect and above-mentioned implementation thereof, in its 4th kind of implementation, described message registration call request also comprises: be used to indicate user in the selected one or more described information that the service end of message registration can be provided of described client.
In conjunction with first aspect and above-mentioned implementation thereof, in its 5th kind of implementation, the request of obtaining of described message registration comprises additional request condition, wherein said additional request condition comprise following at least one: the character string that is used to indicate object search; Be used to indicate the numerical value that message registration returns to restricted number; Be used to indicate the character string of search condition.
In conjunction with first aspect and above-mentioned implementation thereof, in its 6th kind of implementation, after the described service end of the described reception described response message that the request of obtaining sends according to described message registration, also comprise: to described client, send described message registration, to show, import or store described message registration in described client.
In conjunction with first aspect and above-mentioned implementation thereof, in its 7th kind of implementation, the predefined format of described message registration comprises following at least one: the unique identification of this message registration; The identify label of calling user; The display Name of calling user; There is the date in call; Duration; Positional information during call; Annex in communication process; Sectional drawing in communication process; The recording of communication process or video recording; Videoconference or video conference information.
Second aspect, a kind of subscriber equipment is provided, comprise: the first receiving element, the message registration call request sending for receiving client, described message registration call request comprises: be used to indicate the action field of call operation and be used to indicate the type field that data type is message registration; Determining unit, for according to described message registration call request, determines the service end that message registration can be provided, and wherein said client is different from described service end; Transmitting element, obtains request for sending message registration to described service end; The second receiving element, for receiving the described service end response message that the request of obtaining sends according to described message registration, described response message comprises: meet the described message registration of predefined format, or, the errored response of misdirection type.
In conjunction with second aspect, in its first implementation, described message registration call request also comprises additional request condition, wherein said additional request condition comprise following at least one: the character string that is used to indicate object search; Be used to indicate the numerical value that message registration returns to restricted number; Be used to indicate the character string of search condition.
In conjunction with second aspect and above-mentioned implementation thereof, in its second implementation, described transmitting element is also for send described message registration call request to registration center, so that described registration center determines the described service end list that receiving element also sends for receiving described registration center described in the service end list that message registration calls service can be provided according to described action field and described type field; Described determining unit is also for determining the described service end that message registration can be provided in described service end list.
In conjunction with second aspect and above-mentioned implementation thereof, in its third implementation, described determining unit also for: in described service end list, determine that the used service end of user is the described service end that message registration can be provided; Or according to user's selection, in described service end list or in the used service end of user, determine the described service end that message registration can be provided.
In conjunction with second aspect and above-mentioned implementation thereof, in its 4th kind of implementation, described message registration call request also comprises: be used to indicate user in the selected one or more described information that the service end of message registration can be provided of client.
In conjunction with second aspect and above-mentioned implementation thereof, in its 5th kind of implementation, described message registration obtain request comprise additional request condition, wherein said additional request condition comprise following at least one: the character string that is used to indicate object search; Be used to indicate the numerical value that message registration returns to restricted number; Be used to indicate the character string of search condition.
In conjunction with second aspect and above-mentioned implementation thereof, in its 6th kind of implementation, described the second transmitting element also for: to described client, send described message registration, to show, import or store described message registration in described client.
In conjunction with second aspect and above-mentioned implementation thereof, in its 7th kind of implementation, the predefined format of described message registration comprises following at least one: the unique identification of this message registration; The identify label of calling user; The display Name of calling user; There is the date in call; Duration; Positional information during call; Annex in communication process; Sectional drawing in communication process; The recording of communication process or video recording; Videoconference or video conference information.
The method that the embodiment of the present invention provides and subscriber equipment, at the message registration of any one other service end of client call, have strengthened the operability of message registration, are convenient to management, and the message registration that can realize across application or webpage calls.
Accompanying drawing explanation
In order to be illustrated more clearly in the technical scheme of the embodiment of the present invention, to the accompanying drawing of required use in the embodiment of the present invention be briefly described below, apparently, below described accompanying drawing be only some embodiments of the present invention, for those of ordinary skills, do not paying under the prerequisite of creative work, can also obtain according to these accompanying drawings other accompanying drawing.
Fig. 1 is the flow chart of the message registration call method of one embodiment of the invention.
Fig. 2 is the interaction figure of the message registration call method of one embodiment of the invention.
Fig. 3 is the interaction figure of the message registration call method of another embodiment of the present invention.
Fig. 4 is the schematic block diagram of the subscriber equipment of one embodiment of the invention.
Fig. 5 is the schematic block diagram of the subscriber equipment of another embodiment of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is clearly and completely described, obviously, described embodiment is a part of embodiment of the present invention, rather than whole embodiment.Embodiment based in the present invention, the every other embodiment that those of ordinary skills obtain under the prerequisite of not making creative work, should belong to the scope of protection of the invention.
Fig. 1 is the flow chart of the message registration call method of one embodiment of the invention.The method of Fig. 1 is carried out by user agent (User Agent, UA).
101, receive the message registration call request that client sends, this message registration call request comprises: be used to indicate the action field of call operation and be used to indicate the type field that data type is message registration.
102, according to message registration call request, determine the service end that message registration can be provided.
103, to service end, send message registration and obtain request.
104, receive the service end response message that the request of obtaining sends according to message registration, this response message comprises: meet the message registration of predefined format, or, the errored response of misdirection type.
The method that the embodiment of the present invention provides, at the message registration of any one other service end of client call, has strengthened the operability of message registration, is convenient to management, and the message registration that can realize across application or webpage calls.
In embodiments of the present invention, user agent (UA) is the general designation of browser or operating system, the Internet Explorer browser of Microsoft for example, the Google Chrome browser of Google or network operating system (Web-based Operating System) etc.Client refers to the application of initiating mutual request, wherein client can be local application (Native Applications, Native Apps) or web application (Webpage Applications, Web Apps), for example, for the WebRTC Apps of webpage real time communication (Web Real Time Communication, WebRTC).More broadly, client can be only also the page or the webpage of initiating mutual request, page of social class websites such as Facebook, Renren Network, the friend of Tengxun net etc.Service end refers to the request of customer in response end or for client provides the application of service, wherein service end can be Native Apps or Web Apps, for example WebRTC Apps.Similarly, service end also can exist with the page or form web page, page of social class websites such as Facebook, Renren Network, the friend of Tengxun net etc.
For convenience of description; the message registration that the embodiment of the present invention be take between Web Apps calls as example and describes; but the embodiment of the present invention is not limited to this; web application and local application; web application and webpage; webpage and webpage, the combinations such as local application and local application also all fall into protection scope of the present invention.
Alternatively, as an embodiment, before step 101, can also comprise: receive the registration request that service end sends; To registration center, send registration request, registration request is for providing message registration to call service to registration center's indication service end.That is to say, providing before message registration calls service, service end need to be registered in registration center by browser, and service end can directly not registered in registration center by browser yet certainly.Wherein, registration request can comprise: be used to indicate the action field of call operation, and be used to indicate the type field that data type is message registration.Registration center can be application shop (App Store) or third-party registration platform, and such as webintents.org etc., the present invention does not limit this.
Alternatively, as another embodiment, in step 101, message registration call request comprises: be used to indicate the action field of call operation and be used to indicate the type field that data type is message registration.Wherein the action field in message registration call request need to be consistent with action field and type field in registration request with type field, so that registration center is according to the registered service end that can provide message registration to call service of message registration call request coupling.Further, message registration call request can also comprise additional request condition, wherein additional request condition can comprise following at least one: the character string that is used to indicate object search; Be used to indicate the numerical value that message registration returns to restricted number; Be used to indicate the character string of search condition.
Alternatively, as another embodiment, step 102 comprises: to registration center, send message registration call request, so that registration center determines the service end list that can provide message registration to call service according to action field and type field; Receive the service end list that registration center sends; In service end list, determine the service end that message registration can be provided.Wherein, in service end list, determine the service end that message registration can be provided, comprising: in service end list, determine that the used service end of user is for providing the service end of message registration; Or according to user's selection, in service end list, determine the service end that message registration can be provided.
Alternatively, as another embodiment, in step 101, message registration call request also comprises: be used to indicate user in the selected one or more information that the service end of message registration can be provided of client.That is to say, user can directly choose certain or a plurality of service end in client, thereby selects for user without generate service end list to be selected by browser searches registration center.
Alternatively, as another embodiment, in step 103, the message registration request of obtaining comprises additional request condition, wherein additional request condition can comprise following at least one: the character string that is used to indicate object search; Be used to indicate the numerical value that message registration returns to restricted number; Be used to indicate the character string of search condition.That is to say, at browser, determined and can provide after the service end of message registration, to this service end, send the additional request condition of obtaining from above-mentioned message registration call request, carry out the message registration retrieval with qualifications.
Alternatively, as another embodiment, in step 104, response message comprises: the message registration of coupling predefined format, or, the errored response of misdirection type.When service end can provide message registration according to the request of client, this service end can return to browser according to predefined form by message registration.If any wrong generation, service end can be returned to a wrong information.Wherein, predefined format can comprise following at least one: the unique identification of this message registration; The identify label of calling user; The display Name of calling user; There is the date in call; Duration; Positional information during call; Annex in communication process; Sectional drawing in communication process; The recording of communication process or video recording; Videoconference or video conference information.
Alternatively, as another embodiment, after step 104, also comprise: to client, send message registration, to show, import in client or storage message registration.Browser receives after the message registration of the predefined format that service end sends, the message registration of this predefined format can be shown on customer terminal webpage, and can carry out according to user's instruction the operations such as follow-up importing or storage, also can directly import without the demonstration of customer terminal webpage or the operation such as storage.
The method that the embodiment of the present invention provides can realize the message registration in any one other service end of client call, has strengthened the operability of message registration, is convenient to management, and the message registration that can realize across application or webpage calls.
Fig. 2 is the interaction figure of the message registration call method of one embodiment of the invention.In Fig. 2, user agent (UA) is the general designation of browser or operating system, the Internet Explorer browser of Microsoft for example, the Google Chrome browser of Google or network operating system (Web-based Operating System) etc.Client refers to the application of initiating mutual request, and wherein client can be Native Apps or Web Apps, for example WebRTC Apps.More broadly, client can be only also the page or the webpage of initiating mutual request, page of social class websites such as Facebook, Renren Network, the friend of Tengxun net etc.Service end refers to the request of customer in response end or for client provides the application of service, wherein service end can be Native Apps or Web Apps, for example WebRTC Apps.Similarly, service end also can exist with the page or form web page, page of social class websites such as Facebook, Renren Network, the friend of Tengxun net etc.Registration center can be application shop (App Store) or third-party registration platform, and such as webintents.org etc., the present invention does not limit this.
201, service end sends registration request to registration center.
Service end sends registration request to browser, and by browser, to registration center, forward this registration request further, also can directly receive the registration request that service end sends by registration center, so that this service end is registered its available service in registration center.This registration request can comprise and is used to indicate the action field of call operation and is used to indicate the type field that data type is message registration.For example, definition action field action:http: //webintents.org/pick; Type field type:http: //w3.org/type/callLog, wherein pick is used to indicate call operation, and callLog is used to indicate message registration.
Service end is when registering, and the registration request of transmission can be used following statement:
More than that the message registration that the message registration Ye registration center of service end is registered as a kind of action/type defined above calls service, this message registration page can pass through universal resource identifier (Uniform Resource Identifier, URI) and identify and locate.
Should be understood that message registration may be from a plurality of sources, comprise on network and (for example, the message registration on subscriber equipment) subscriber equipment this locality.That is to say that the service end of registering can be not only application or webpage, can be also the service on equipment, the CallLog.Calls application programming interface that for example Android system provides (Application Programming Interface, API).
In addition, WebRTC apps, except being registered as the service of calling for message registration, can also be registered as the service for conversing, and for example, definition action is call, and definition type is text/string.If there is so the effectively account such as telephone number or e-mail address in client, click " dialing " button and can recall a plurality of service ends that session services can be provided by browser and registration center, select one of them, dial number.This scene can, for contacting seller in the application of shopping at network or webpage, contact teammate etc. in online game or web game conventionally.
The above-mentioned process in the registration of application center can be carried out when application is added, also can when application is upgraded, carry out, and also can register by manually writing code, and the present invention does not limit this.
202, client sends message registration call request to UA.
When user opens a client, can be WebRTC App or common application, on the page of this application, click for triggering the button that message registration calls, for example " message registration ", buttons such as " importings ", to initiate message registration call request.This message registration call request can comprise in above-mentioned steps 201 action/type corresponding to the message registration service of calling in registration request, so that registration center has the ability to provide the service end of this service according to this action/type match search.Client sends this message registration call request to browser.
In addition, client also can not only be called message registration by a button, and client can also be by allowing user select the qualifications of some retrievals during message registrations, and for example according to number, the information such as name are retrieved, or requested part data etc. only.Can generate additional request condition by user's selection and restriction like this, by message registration call request, be carried, send in the lump browser.The qualifications that for example can select according to user generates following code:
Wherein, the search character string under DOMString territory is to provide the qualifications that is used to indicate object search to service end, for example, this character string can be defined as to name Alice, specifies and searches for and return the message registration relevant to Alice.Limit can be a numerical value for selected, so that service end is returned to the message registration entry that is no more than this numerical value, for example can define this numerical value is 10, when qualified message registration number is greater than 10, only returns to 10 of maximums.It under sequence<DOMString> territory, can be the character string array that is used to indicate search condition, for when search to service end with prompting, for example specifying region of search is name, and service end is only searched in name one hurdle.
The code that should be understood that above-mentioned additional request condition is only an example, and in the embodiment of the present invention, the territory of additional request condition is not limited to three territories in above-mentioned code, and above-mentioned three territories neither be necessary certainly, and the present invention does not limit this.If client does not directly trigger message registration invoked procedure by button by setting extra qualifications, above-mentioned additional request condition can be collected after determining the service end that message registration is provided.
Browser receives after message registration call request, to registration center, sends this message registration call request.If this message registration call request is except comprising the most basic action/type, while also including additional request condition, browser can be selected only action/type to be sent to registration center, and additional request condition is buffered in to this locality, in order to the follow-up selected service end of message registration that provides, send again afterwards.Certainly, also can send in the lump together with additional request condition.
203, registration center sends service end list to UA.
Registration center receives after message registration call request, obtain action/type field wherein, according to this action/type field, in the action/type field of application of registration before, carry out match search and determine the service end that can provide message registration to call service is provided, and generate list.This list is returned to browser for you to choose.Wherein, can provide service end list that message registration calls service can comprise the URI of the message registration page of each service end in list.
204, UA determines the service end that message registration can be provided.
Can provide after the service end list that message registration calls service receiving, browser need to be determined the service end that message registration can be provided, and really carries out the destination service end that message registration calls, and this deterministic process can be by numerous embodiments:
Execution mode one, browser can directly determine that in the service end list that can provide message registration to call service the used service end of user is as destination service end, can provide the service end of message registration, wherein destination service end can be one or more.Particularly, user logs in browser by account, browser by the historical record of this account, historical arrange and this user once the relevant information such as used service end (such as WebRTC service provider) there is high in the clouds, browser can directly obtain the used service end of this user from high in the clouds like this.Even and if user while using browser, as long as login browser account can be determined the used service end of this user equally on different subscriber equipmenies.
Execution mode two, browser can be determined the used service end of user in above-mentioned service end list, concrete grammar is identical with above-mentioned real-time mode one, the used service end list of definite user is sent to client, or in the window ejecting or directly show the used service end list of user on the page, for user, select.According to user's selection, further determine destination service end, the service end of message registration can be provided, wherein user can select one or more service end as destination service end.
Execution mode three, browser can directly send to client by above-mentioned service end list, or in the window ejecting or directly show on the page, for user, selects.According to user's selection, further determine destination service end afterwards, the service end of message registration can be provided, wherein user can select one or more service end as destination service end.
Certainly, browser also can be listed to be arranged on browser and select for user with the service end of App Store recommendation.
After having determined destination service end, browser can point out user to input account password to log in destination service end, browser also can preset the trusting relationship with special services end, do not need by user interactions directly to obtain and to log in mandate, for example user once authorized browse device remember the account password of input.Or also can integrate user ID by all service providers, as long as user logs in once, for example, to all similar application (WebRTC App) effective, i.e. single sign-on (Single Sign On, SSO).
205, UA sends message registration to service end and obtains request.
Browser is being determined the service end that message registration can be provided, and after being proved to be successful, logs in the service end that message registration can be provided, and the message registration request of obtaining is sent to this service end.Particularly, can be by step 202, browser sends to this service end by the additional request condition of buffer memory by the message registration request of obtaining.Or, in the situation that browser does not have buffer memory additional request condition, can obtain the search condition similar with above-mentioned additional request condition to user, and this search condition is passed to this service end by CallLogIntentExtras, specifically can be with reference to above-mentioned steps 202.
206, service end is returned to response.
The service end that message registration can be provided is obtained after request receiving message registration, according to additional request condition wherein or the search condition of newly obtaining, satisfactory message registration is returned to browser according to predefined format.Browser can directly show message registration on the page of client afterwards, this method service end provides the page operation of message registration but does not open, avoid the redirect between the page, but needed the postResult time automatically to trigger, for example, based on onload event, realized automatic triggering.Certainly, also can open the page that service end provides message registration at new window or Shipping Options Page, this method needs user's manual triggers postResult event, for example button click.When said process has any wrong generation, browser can return to an error message error, for example, with postFailure, return to mistake, and misdirection type.Wherein, if user selects 0 service end or cancels operation, do not do wrong processing.In addition, except showing message registration on the page of client, also can select according to user, directly in operations such as client executing importing or storages, or on the page, demonstrate after message registration, provide the button of operations such as importing or storage further to operate.
Satisfactory message registration is treated to predefined format, can be so that the message registration of the different-format of different application or webpage be treated to identical form when calling.That is to say, by predefined format, come Standard Service end to offer the consistency of client data.For example, while calling successfully, service end can be returned to the array of a CallLog object, and this CallLog object not only can comprise message registration, can also comprise text, annex, and recording, picture, the information such as video, the present invention does not limit this.For example, message registration form can be as follows:
Wherein, the id in DOMString is used to indicate the unique identification of every message registration; CallId is used to indicate the sign (for example telephone number) of using the webRTC business relevant to this message registration; DisplayName is used to indicate the other side's display Name (pet name); The positional information when location in Position is used to indicate call; Type in DOMString is used to indicate the type of call, as does not connect, and transfers to, and dials in; Date is used to indicate the date that call occurs; Duration is used to indicate the duration; Styles is used to indicate style, as audio frequency, and audio/video, word etc.; Screenshots is used to indicate the screenshotss picture that this message registration is relevant; Recordings is used to indicate one or more recording relevant to this message registration; Attachments is used to indicate one or more annex relevant to this message registration; ChatLogs is used to indicate the one or more text chat record relevant to this message registration; MeetingLogs is used to indicate the one or more videoconference record relevant to this message registration.
As a concrete example, WebRTC service end can be used predefined message registration form to create a message registration object, fills content, and uses postResult () to return results:
Above-mentioned code has carried a message registration, the other side's name Alice, and telephone number 1890000000, type of call is for dialling in, and the time is 12: 12 on the 9th February in 2013.And realize in successful situation and return to message registration (postResult) by judgement statement, in the situation of mistake, return to error message (postFailure).
In addition as an example of client code:
Wherein, action/type field shows that client-requested calls message registration, and extras lists some additional conditions or search condition, after request is sent, by call back function callLogOK and callLogFail, obtain response, receive the message registration needing, or return to error message.
The method that the embodiment of the present invention provides can realize the message registration in any one other service end of client call, has strengthened the operability of message registration, is convenient to management, and the message registration that can realize across application or webpage calls.
Fig. 3 is the interaction figure of the message registration call method of another embodiment of the present invention.In Fig. 3, user agent (UA) is the general designation of browser or operating system, the Internet Explorer browser of Microsoft for example, the Google Chrome browser of Google or network operating system (Web-based Operating System) etc.Client refers to the application of initiating mutual request, and wherein client can be Native Apps or Web Apps, for example WebRTC Apps.More broadly, client can be only also the page or the webpage of initiating mutual request, page of social class websites such as Facebook, Renren Network, the friend of Tengxun net etc.Service end refers to the request of customer in response end or for client provides the application of service, wherein service end can be Native Apps or Web Apps, for example WebRTC Apps.Similarly, service end also can exist with the page or form web page, page of social class websites such as Facebook, Renren Network, the friend of Tengxun net etc.Registration center can be application shop (App Store) or third-party registration platform, and such as webintents.org etc., the present invention does not limit this.
In Fig. 3, in the service end registration process of embodiment and above-mentioned Fig. 2, step 201 is similar, repeats no more herein.
301, the selected service end that message registration can be provided of client.
User can directly select the service end that message registration can be provided on client user's the page.Particularly, can be the preset a plurality of service ends of client, also can be that the used service end of user that client is obtained from browser presents for user and selects with the page, user can choose one or more service end therein can provide the service end of message registration the most.Should be understood that the process that user selects is not limited only to choose, also can by user, manually input the methods such as client name or URI and realize, the embodiment of the present invention is not limited to this.
302, client sends message registration call request to UA.
Client gets after user's selection, generates message registration call request, and sends to browser.Particularly, after the selected service end of user, click and be used to indicate definite button, client generates message registration call request according to user's selection, wherein similar in step 202 in the action/type in message registration call request and optional additional request condition and above-mentioned Fig. 2, repeat no more herein, difference is, message registration call request in the present embodiment also needs to carry the information of one or more specified services ends that user selectes, such as carrying the URI of specified services end or title etc.
303, UA sends message registration to service end and obtains request.
Browser is after receiving message registration call request, according to the information of the specified services end wherein carrying, directly to this specified services end, send message registration and obtain request, wherein in the message registration request of obtaining and above-mentioned Fig. 2, step 205 is similar, repeats no more herein.
304, service end is returned to response.
Specified services end obtains after request receiving message registration, according to additional request condition wherein or the search condition of newly obtaining, satisfactory message registration is returned to browser according to predefined format.Browser can directly show message registration on the page of client afterwards, or select according to user, directly in operations such as client executing importing or storages, or on the page, demonstrate after message registration, provide the button of operations such as importing or storage to carry out further operation etc.Can, with reference to step 206 in above-mentioned Fig. 2, repeat no more particularly herein.
The method that the embodiment of the present invention provides can realize the message registration in any one other service end of client call, has strengthened the operability of message registration, is convenient to management, and the message registration that can realize across application or webpage calls.
Fig. 4 is the schematic block diagram of the subscriber equipment of one embodiment of the invention.The subscriber equipment 400 of Fig. 4 comprises the first receiving element 401, determining unit 402, transmitting element 403 and the second receiving element 404.
The first receiving element 401 receives the message registration call request that client sends, and this message registration call request comprises: be used to indicate the action field of call operation and be used to indicate the type field that data type is message registration.The message registration call request that determining unit 402 receives according to the first receiving element 401, determines the service end that message registration can be provided.Transmitting element 403 sends message registration to service end and obtains request.The second receiving element 404 receives the response message that service end sends according to the message registration request of obtaining of transmitting element 403 transmissions, and this response message comprises: meet the message registration of predefined format or the errored response of misdirection type.
The message registration that the subscriber equipment that the embodiment of the present invention provides can be realized across application or webpage calls.
Alternatively, as an embodiment, the first receiving element 401 also for: receive the registration request that service end sends; Transmitting element 403, sends registration request to registration center, and registration request is for providing message registration to call service to registration center's indication service end.That is to say, providing before message registration calls service, service end need to be registered in registration center by browser.Wherein, registration request can comprise: the action field that is used to indicate call operation; Be used to indicate the type field that data type is message registration.
Alternatively, as another embodiment, message registration call request and registration request comprise: the action field that is used to indicate call operation; Be used to indicate the type field that data type is message registration.Wherein message registration call request can also comprise additional request condition, wherein additional request condition comprise following at least one: the character string that is used to indicate object search; Be used to indicate the numerical value that message registration returns to restricted number; Be used to indicate the character string of search condition.
Alternatively, as another embodiment, transmitting element 403 is also for sending message registration call request to registration center, so that registration center determines the service end list that can provide message registration to call service according to action field and type field; The service end list that receiving element 401 also sends for receiving registration center; Determining unit 402 is also for determining the service end that message registration can be provided in service end list.
Alternatively, as another embodiment, determining unit 402 also for: in service end list, determine that the used service end of user is for providing the service end of message registration; Or according to user's selection, in service end list, determine the service end that message registration can be provided.That is to say, user can directly choose certain or a plurality of service end in client, thereby selects for user without generate service end list to be selected by browser searches registration center.
Alternatively, as another embodiment, message registration call request also comprises: be used to indicate user in the selected one or more information that the service end of message registration can be provided of client.
Alternatively, as another embodiment, the message registration request of obtaining comprises additional request condition.That is to say, at subscriber equipment 400, determined and can provide after the service end of message registration, to this service end, send the additional request condition of obtaining from above-mentioned message registration call request, carry out the message registration information retrieval with qualifications.
Alternatively, as another embodiment, response message comprises: the message registration that meets predefined format; Or the errored response of misdirection type.When service end can provide message registration according to the request of client, this service end can return to subscriber equipment 400 according to predefined form by message registration.If any wrong generation, service end can be returned to a wrong information.Wherein, predefined format can comprise following at least one: the unique identification of this message registration; The identify label of calling user; The display Name of calling user; There is the date in call; Duration; Positional information during call; Annex in communication process; Sectional drawing in communication process; The recording of communication process or video recording; Videoconference or video conference information.
Alternatively, as another embodiment, the second transmitting element 404 also for: to client, send message registration, to show, import in client or storage message registration.Subscriber equipment 400 receives after the message registration of the predefined format that service end sends, it can be shown on customer terminal webpage, and can carry out according to user's instruction the operations such as follow-up importing or storage, also can directly import without the demonstration of customer terminal webpage or the operation such as storage.
The subscriber equipment 400 that the embodiment of the present invention provides can be realized the message registration in any one other service end of client call, has strengthened the operability of message registration, is convenient to management, and the message registration that can realize across application or webpage calls.
Fig. 5 is the schematic block diagram of the subscriber equipment of another embodiment of the present invention.The subscriber equipment 500 of Fig. 5 comprises processor 501 and memory 502.Processor 501 is connected by bus system 503 with memory 502.
Memory 502 makes processor 501 carry out the instruction of following operation for storing: receive the message registration call request that client sends, this message registration call request comprises: be used to indicate the action field of call operation and be used to indicate the type field that data type is message registration; According to message registration call request, determine the service end that message registration can be provided; To service end, send message registration and obtain request; Receive the service end response message that the request of obtaining sends according to message registration, this response message comprises: the message registration that meets predefined format; Or the errored response of misdirection type.
The subscriber equipment that the embodiment of the present invention provides, at the message registration of any one other service end of client call, has strengthened the operability of message registration, is convenient to management, and the message registration that can realize across application or webpage calls.
In addition, subscriber equipment 500 can also comprise radiating circuit 504, receiving circuit 505 etc.Processor 501 is controlled the operation of subscriber equipment 500, and processor 501 can also be called CPU(Central Processing Unit, CPU).Memory 502 can comprise read-only memory and random access memory, and provides instruction and data to processor 501.A part for memory 502 can also comprise nonvolatile RAM (NVRAM).In concrete application, each assembly of subscriber equipment 500 is coupled by bus system 503, and wherein bus system 503, except comprising data/address bus, can also comprise power bus, control bus and status signal bus in addition etc.But for the purpose of clearly demonstrating, in the drawings various buses are all designated as to bus system 503.
The method that the invention described above embodiment discloses can be applied in processor 501, or is realized by processor 501.Processor 501 may be a kind of integrated circuit (IC) chip, has the disposal ability of signal.In implementation procedure, each step of said method can complete by the integrated logic circuit of the hardware in processor 501 or the instruction of form of software.Above-mentioned processor 501 can be general processor, digital signal processor (DSP), application-specific integrated circuit (ASIC) (ASIC), ready-made programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic device, discrete hardware components.Can realize or carry out disclosed each method, step and logic diagram in the embodiment of the present invention.General processor can be that microprocessor or this processor can be also the processors of any routine etc.Step in conjunction with the disclosed method of the embodiment of the present invention can directly be presented as that hardware decoding processor is complete, or complete with the hardware in decoding processor and software module combination.Software module can be positioned at random asccess memory, and flash memory, read-only memory, in the storage medium of this area maturations such as programmable read only memory or electrically erasable programmable memory, register.This storage medium is positioned at memory 502, and the information in processor 501 read memories 502 completes the step of said method in conjunction with its hardware.
Alternatively, as an embodiment, by receiving circuit 505, receive the registration request that service end sends; By radiating circuit 504Xiang registration center, send registration request afterwards, this registration request is for providing message registration to call service to registration center's indication service end.That is to say, providing before message registration calls service, service end need to be registered in registration center by browser.Wherein, registration request can comprise: the action field that is used to indicate call operation; Be used to indicate the type field that data type is message registration.
Alternatively, as another embodiment, message registration call request and registration request comprise: the action field that is used to indicate call operation; Be used to indicate the type field that data type is message registration.Wherein message registration call request can also comprise additional request condition, wherein additional request condition comprise following at least one: the character string that is used to indicate object search; Be used to indicate the numerical value that message registration returns to restricted number; Be used to indicate the character string of search condition.
Alternatively, as another embodiment, radiating circuit 504 is also for sending message registration call request to registration center, so that registration center determines the service end list that can provide message registration to call service according to action field and type field; The service end list that receiving circuit 505 also sends for receiving registration center; Processor 501 is also for determining the service end that message registration can be provided in service end list.
Alternatively, as another embodiment, processor 501 also for: in service end list, determine that the used service end of user is for providing the service end of message registration; Or according to user's selection, in service end list, determine the service end that message registration can be provided.That is to say, user can directly choose certain or a plurality of service end in client, thereby selects for user without generate service end list to be selected by browser searches registration center.
Alternatively, as another embodiment, message registration call request also comprises: be used to indicate user in the selected one or more information that the service end of message registration can be provided of client.
Alternatively, as another embodiment, the message registration request of obtaining comprises additional request condition.That is to say, at subscriber equipment 500, determined and can provide after the service end of message registration, to this service end, send the additional request condition of obtaining from above-mentioned message registration call request, carry out the message registration information retrieval with qualifications.
Alternatively, as another embodiment, response message comprises: the message registration that meets predefined format; Or the errored response of misdirection type.When service end can provide message registration according to the request of client, this service end can return to subscriber equipment 500 according to predefined form by message registration.If any wrong generation, service end can be returned to a wrong information.Wherein, predefined format can comprise following at least one: the unique identification of this message registration; The identify label of calling user; The display Name of calling user; There is the date in call; Duration; Positional information during call; Annex in communication process; Sectional drawing in communication process; The recording of communication process or video recording; Videoconference or video conference information.
Alternatively, as another embodiment, by radiating circuit 504, to client, send message registration, to show, import in client or storage message registration.Subscriber equipment 500 receives after the message registration of the predefined format that service end sends, it can be shown on customer terminal webpage, and can carry out according to user's instruction the operations such as follow-up importing or storage, also can directly import without the demonstration of customer terminal webpage or the operation such as storage.
Those of ordinary skills can recognize, in conjunction with the various method steps of describing in embodiment disclosed herein and unit, can realize with electronic hardware, computer software or the combination of the two, for the interchangeability of hardware and software is clearly described, step and the composition of each embodiment described according to function in the above description in general manner.These functions are carried out with hardware or software mode actually, depend on application-specific and the design constraint of technical scheme.Those of ordinary skills can specifically should be used for realizing described function with distinct methods to each, but this realization should not thought and exceeds scope of the present invention.
The software program that the method for describing in conjunction with embodiment disclosed herein or step can use hardware, processor to carry out, or the combination of the two is implemented.Software program can be placed in the storage medium of any other form known in random asccess memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable ROM, register, hard disk, moveable magnetic disc, CD-ROM or technical field.
Although the present invention be have been described in detail by reference to accompanying drawing mode in conjunction with the preferred embodiments, the present invention is not limited to this.Without departing from the spirit and substance of the premise in the present invention, those of ordinary skills can carry out to embodiments of the invention modification or the replacement of various equivalences, and these modifications or replacement all should be in covering scopes of the present invention.
Claims (16)
1. a message registration call method, is characterized in that, comprising:
Receive the message registration call request that client sends, described message registration call request comprises: be used to indicate the action field of call operation and be used to indicate the type field that data type is message registration;
According to described message registration call request, determine the service end that message registration can be provided;
To described service end, send message registration and obtain request;
Receive the described service end response message that the request of obtaining sends according to described message registration, described response message comprises: meet the message registration of predefined format, or, the errored response of misdirection type.
2. method according to claim 1, is characterized in that, described message registration call request also comprises additional request condition, wherein said additional request condition comprise following at least one:
Be used to indicate the character string of object search;
Be used to indicate the numerical value that message registration returns to restricted number;
Be used to indicate the character string of search condition.
3. method according to claim 1 and 2, is characterized in that, described according to described message registration call request, determines the service end that message registration can be provided, and comprising:
To registration center, send described message registration call request, so that described registration center determines the service end list that can provide message registration to call service according to described action field and described type field;
Receive the described service end list that described registration center sends;
In described service end list, determine the described service end that message registration can be provided.
4. method according to claim 3, is characterized in that, describedly in described service end list, determines the described service end that message registration can be provided, and comprising:
In described service end list, determine that the used service end of user is the described service end that message registration can be provided; Or
According to user's selection, in described service end list or in the used service end of user, determine the described service end that message registration can be provided.
5. method according to claim 1 and 2, is characterized in that, described message registration call request also comprises: be used to indicate user in the selected one or more described information that the service end of message registration can be provided of described client.
6. according to the method described in any one in claim 1 to 5, it is characterized in that, the request of obtaining of described message registration comprises additional request condition, wherein said additional request condition comprise following at least one:
Be used to indicate the character string of object search;
Be used to indicate the numerical value that message registration returns to restricted number;
Be used to indicate the character string of search condition.
7. according to the method described in any one in claim 1 to 6, it is characterized in that, after the described service end of the described reception described response message that the request of obtaining sends according to described message registration, also comprise: to described client, send described message registration, to show, import or store described message registration in described client.
8. according to the method described in any one in claim 1 to 7, it is characterized in that, the predefined format of described message registration comprises following at least one:
The unique identification of this message registration;
The identify label of calling user;
The display Name of calling user;
There is the date in call;
Duration;
Positional information during call;
Annex in communication process;
Sectional drawing in communication process;
The recording of communication process or video recording;
Videoconference or video conference information.
9. a subscriber equipment, is characterized in that, comprising:
The first receiving element, the message registration call request sending for receiving client, described message registration call request comprises: be used to indicate the action field of call operation and be used to indicate the type field that data type is message registration;
Determining unit, for according to described message registration call request, determines the service end that message registration can be provided, and wherein said client is different from described service end;
Transmitting element, obtains request for sending message registration to described service end;
The second receiving element, for receiving the described service end response message that the request of obtaining sends according to described message registration, described response message comprises: meet the described message registration of predefined format, or, the errored response of misdirection type.
10. subscriber equipment according to claim 9, is characterized in that, described message registration call request also comprises additional request condition, wherein said additional request condition comprise following at least one:
Be used to indicate the character string of object search;
Be used to indicate the numerical value that message registration returns to restricted number;
Be used to indicate the character string of search condition.
11. according to the subscriber equipment described in claim 9 or 10, it is characterized in that, described transmitting element is also for send described message registration call request to registration center, so that described registration center determines the service end list that can provide message registration to call service according to described action field and described type field;
The described service end list that described receiving element also sends for receiving described registration center;
Described determining unit is also for determining the described service end that message registration can be provided in described service end list.
12. subscriber equipmenies according to claim 12, is characterized in that, described determining unit also for:
In described service end list, determine that the used service end of user is the described service end that message registration can be provided; Or
According to user's selection, in described service end list or in the used service end of user, determine the described service end that message registration can be provided.
13. according to the subscriber equipment described in claim 9 or 10, it is characterized in that, described message registration call request also comprises: be used to indicate user in the selected one or more described information that the service end of message registration can be provided of client.
14. according to the subscriber equipment described in any one in claim 9 to 13, it is characterized in that, described message registration obtain request comprise additional request condition, wherein said additional request condition comprise following at least one:
Be used to indicate the character string of object search;
Be used to indicate the numerical value that message registration returns to restricted number;
Be used to indicate the character string of search condition.
15. according to the subscriber equipment described in any one in claim 9 to 14, it is characterized in that, described the second transmitting element also for: to described client, send described message registration, to show, import or store described message registration in described client.
16. according to the subscriber equipment described in any one in claim 9 to 15, it is characterized in that, the predefined format of described message registration comprises following at least one:
The unique identification of this message registration;
The identify label of calling user;
The display Name of calling user;
There is the date in call;
Duration;
Positional information during call;
Annex in communication process;
Sectional drawing in communication process;
The recording of communication process or video recording;
Videoconference or video conference information.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310196669.8A CN104184771B (en) | 2013-05-23 | 2013-05-23 | Message registration call method and equipment |
| PCT/CN2014/077754 WO2014187288A1 (en) | 2013-05-23 | 2014-05-19 | Call log invoking method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310196669.8A CN104184771B (en) | 2013-05-23 | 2013-05-23 | Message registration call method and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104184771A true CN104184771A (en) | 2014-12-03 |
| CN104184771B CN104184771B (en) | 2017-12-15 |
Family
ID=51932857
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310196669.8A Expired - Fee Related CN104184771B (en) | 2013-05-23 | 2013-05-23 | Message registration call method and equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN104184771B (en) |
| WO (1) | WO2014187288A1 (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111277996A (en) * | 2018-12-05 | 2020-06-12 | 中国移动通信集团山东有限公司 | Call record recovery method and system |
| CN112532509A (en) * | 2019-09-18 | 2021-03-19 | 华为技术有限公司 | Cross-application communication method and related device |
| CN112668915A (en) * | 2017-07-07 | 2021-04-16 | 山东御银智慧金融设备有限公司 | Enterprise client marketing intelligent management system |
| CN113347233A (en) * | 2021-05-20 | 2021-09-03 | 深圳软牛科技有限公司 | Method, device, equipment and storage medium for extracting call and WIFI data from cloud |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3264733B1 (en) | 2016-06-29 | 2019-08-07 | Unify Patente GmbH & Co. KG | Method of providing a recent event list, software product, telecommunications device and system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101379785A (en) * | 2005-12-09 | 2009-03-04 | 易巴迪控股公司 | Contact list display system and method |
| CN101997964A (en) * | 2009-08-13 | 2011-03-30 | 中国电信股份有限公司 | Processing method of mobile communication terminal and contact records thereof |
| CN102130844A (en) * | 2010-01-20 | 2011-07-20 | 腾讯科技（深圳）有限公司 | Method and system for acquiring Web chat logs |
| CN102883077A (en) * | 2012-09-05 | 2013-01-16 | 北京讯鸟软件有限公司 | Centralized-and-distributed type recording system and record inquiring method |
| KR101360151B1 (en) * | 2011-10-17 | 2014-02-11 | 텔코웨어 주식회사 | Method of sip message transmission between gruu users in ims network, and device of the same |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102932521B (en) * | 2011-08-11 | 2014-06-18 | 汉王科技股份有限公司 | Method and terminal for displaying interaction records of contacts in mobile equipment |
-
2013
- 2013-05-23 CN CN201310196669.8A patent/CN104184771B/en not_active Expired - Fee Related
-
2014
- 2014-05-19 WO PCT/CN2014/077754 patent/WO2014187288A1/en not_active Ceased
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101379785A (en) * | 2005-12-09 | 2009-03-04 | 易巴迪控股公司 | Contact list display system and method |
| CN101997964A (en) * | 2009-08-13 | 2011-03-30 | 中国电信股份有限公司 | Processing method of mobile communication terminal and contact records thereof |
| CN102130844A (en) * | 2010-01-20 | 2011-07-20 | 腾讯科技（深圳）有限公司 | Method and system for acquiring Web chat logs |
| KR101360151B1 (en) * | 2011-10-17 | 2014-02-11 | 텔코웨어 주식회사 | Method of sip message transmission between gruu users in ims network, and device of the same |
| CN102883077A (en) * | 2012-09-05 | 2013-01-16 | 北京讯鸟软件有限公司 | Centralized-and-distributed type recording system and record inquiring method |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112668915A (en) * | 2017-07-07 | 2021-04-16 | 山东御银智慧金融设备有限公司 | Enterprise client marketing intelligent management system |
| CN111277996A (en) * | 2018-12-05 | 2020-06-12 | 中国移动通信集团山东有限公司 | Call record recovery method and system |
| CN112532509A (en) * | 2019-09-18 | 2021-03-19 | 华为技术有限公司 | Cross-application communication method and related device |
| CN113347233A (en) * | 2021-05-20 | 2021-09-03 | 深圳软牛科技有限公司 | Method, device, equipment and storage medium for extracting call and WIFI data from cloud |
| CN113347233B (en) * | 2021-05-20 | 2022-09-20 | 深圳软牛科技有限公司 | Method, device, equipment and storage medium for extracting call and WIFI data from cloud |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2014187288A1 (en) | 2014-11-27 |
| CN104184771B (en) | 2017-12-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102531745B1 (en) | Server, method for controlling server, and program | |
| CN106550004B (en) | Service object recommendation method and device | |
| KR20150043369A (en) | Communications server apparatus, calling device and methods of operation thereof | |
| CN105183513A (en) | Application recommendation method and apparatus | |
| US20150341499A1 (en) | Method and system for managing voice calls in association with social media content | |
| CN104184771A (en) | Call record calling method and device | |
| US11070659B2 (en) | Incoming voice calling method and terminal | |
| US20180343563A1 (en) | Method and system for using a plurality of accounts in an instant messaging application | |
| CN109040049B (en) | User registration method and device and electronic equipment | |
| KR20160008552A (en) | Web platform with select-to-call functionality | |
| KR20170037864A (en) | Contact record processing method and apparatus | |
| CN103986746A (en) | A method and device for establishing communication between a user and a third party | |
| AU2019100103A4 (en) | A system and method for delivering in-app content using mobile messaging | |
| EP3923524A1 (en) | Selecting a communication channel for omnichannel message delivery | |
| JP2019512984A (en) | Method, apparatus and system for checking change of telephone number | |
| JP7264964B2 (en) | Terminal, terminal control method and program | |
| JP6952399B2 (en) | Terminals, terminal control methods and programs | |
| CN104184865A (en) | Dialing method and device | |
| US20100180323A1 (en) | Stateful server based social networking using mobile devices | |
| JP6555789B2 (en) | Server, server control method and program | |
| CN109274808B (en) | Address book information management method and system, electronic equipment and storage medium | |
| CN106131820B (en) | The method and apparatus of country code are provided in international call business | |
| US20160119785A1 (en) | System and method for managing posts | |
| US12015583B1 (en) | Omnichannel communication widget | |
| KR101514294B1 (en) | Method for guiding caller information |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 518129 Building 2, B District, Bantian HUAWEI base, Longgang District, Shenzhen, Guangdong. Patentee after: Huawei terminal (Shenzhen) Co.,Ltd. Address before: 518129 Building 2, B District, Bantian HUAWEI base, Longgang District, Shenzhen, Guangdong. Patentee before: HUAWEI DEVICE Co.,Ltd. |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20181219 Address after: 523808 Southern Factory Building (Phase I) Project B2 Production Plant-5, New Town Avenue, Songshan Lake High-tech Industrial Development Zone, Dongguan City, Guangdong Province Patentee after: HUAWEI DEVICE Co.,Ltd. Address before: 518129 Building 2, B District, Bantian HUAWEI base, Longgang District, Shenzhen, Guangdong. Patentee before: Huawei terminal (Shenzhen) Co.,Ltd. |
|
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20171215 |