WO2014187288A1

WO2014187288A1 - Call log invoking method and device

Info

Publication number: WO2014187288A1
Application number: PCT/CN2014/077754
Authority: WO
Inventors: 王雅辉; 郜文美; 范姝男; 吕小强; 井皓
Original assignee: 华为终端有限公司
Priority date: 2013-05-23
Filing date: 2014-05-19
Publication date: 2014-11-27
Also published as: CN104184771A; CN104184771B

Abstract

Provided are a call log invoking method and device, which can realize call log invoking across applications. The method comprises: receiving a call log invoking request sent by a client, wherein the call log invoking request comprises: an action field used for indicating an invoking operation and a type field used for indicating that a data type is a call log; according to the call log invoking request, determining a serving end which can provide the call log; sending a call log acquisition request to the serving end; and receiving a response message sent by the serving end according to the call log acquisition request, wherein the response message comprises: a call log conforming to a predefined format, or a wrong response indicating an error type.

Description

Call record calling method and device

The present invention relates to the field of communications, and more particularly to a call record calling method and apparatus. Background technique

Web Real Time Communication (WebRTC) is a communication technology designed to support web browsers for real-time voice conversations or video conversations. Different from traditional multimedia communication methods based on local client or browser plug-in, WebRTC integrates core modules such as audio and video processing (acquisition, encoding, enhancement), network transmission, and session control necessary for multimedia communication into the browser. This allows third-party application developers to get real-time audio and video communication capabilities with a simple JavaScript API call.

Nowadays, social applications are popular, WebRTC can facilitate user communication, and many browser vendors, operators, and especially social networking sites will launch their own WebRTC services. At that time, the user can select any service provider's WebRTC application for voice or video calls, so that users will have a lot of call records in different WebRTC applications, and users often cannot remember these call records, so users have a need. It is possible to call the call log at any time for query or management.

However, current local applications or web applications only support local import/export of call records, and it is not possible to call call records across applications or web pages. Summary of the invention

The embodiment of the invention provides a call record calling method and device, which can implement a call record call across an application or a webpage.

The first aspect provides a call record calling method, including: receiving a call record call request sent by a client, where the call record call request includes: an action field for indicating a call operation and indicating that the data type is a call record a type field; determining, according to the call record invocation request, a server that can provide a call record; sending a call record acquisition request to the server; receiving a response message sent by the server according to the call record acquisition request, The response message includes: a call record that conforms to a predefined format, or an error response indicating an error type.

With reference to the first aspect, in a first implementation manner, the call record call request further includes an additional request condition, where the additional request condition includes at least one of the following: String; a numeric value indicating the limit on the number of calls returned; a string indicating the search criteria. With reference to the first aspect and the foregoing implementation manner, in the second implementation manner, the determining, by the call record invoking request, the server that can provide the call record, includes: sending the call record call request to the registration center And determining, by the registration center, a server list capable of providing a call record calling service according to the action field and the type field; receiving the server list sent by the registration center; determining, in the server list A server that can provide a call record.

With reference to the first aspect and the foregoing implementation manner, in the third implementation manner, the determining, by the server, the server that can provide the call record, includes: determining a user in the server list The used server is the server that can provide the call record; or the server that can provide the call record is determined in the server list or the server used by the user according to the user's selection.

With reference to the first aspect and the foregoing implementation manner, in a fourth implementation manner, the call record invoking request further includes: indicating one or more of the selected call records that are selected by the user at the client Server-side information.

With reference to the first aspect and the foregoing implementation manner, in a fifth implementation manner, the call record acquisition request includes an additional request condition, where the additional request condition includes at least one of the following: a string for indicating a search object ; A numeric value used to indicate the limit on the number of call records returned; a string used to indicate the search criteria.

With reference to the first aspect and the foregoing implementation manner, in the sixth implementation manner, after the receiving, by the server, the response message sent by the call record acquisition request, the method further includes: sending the message to the client The call record is to display, import or store the call record at the client.

With reference to the first aspect and the foregoing implementation manner, in a seventh implementation manner, the predefined format of the call record includes at least one of the following: a unique identifier of the call record; an identity of the call user; a display of the call user Name; call occurrence date; call duration; location information during the call; attachment during the call; screenshot during the call; recording or recording during the call; conference call or video conference information.

In a second aspect, a user equipment is provided, including: a first receiving unit, configured to receive a call record invocation request sent by a client, where the call record invocation request includes: an action field for indicating a call operation, and an indication The data type is a type field of the call record; the determining unit is configured to determine, according to the call record call request, a server that can provide a call record, where the client and the server The server is different from the server; the sending unit is configured to send a call record acquisition request to the server; the second receiving unit is configured to receive a response message sent by the server according to the call record obtaining request, where the response message includes : The call log in a predefined format, or an error response indicating the type of error.

With reference to the second aspect, in a first implementation manner, the call record call request further includes an additional request condition, where the additional request condition includes at least one of the following: a character string used to indicate a search object; The call record returns the value of the limit; the string used to indicate the search criteria.

With reference to the second aspect and the foregoing implementation manner, in a second implementation manner, the sending unit is further configured to send the call record invoking request to the registration center, so that the registry is configured according to the action field and the The type field determines a server list that can provide a call record calling service, the receiving unit is further configured to receive the server side list sent by the registration center, and the determining unit is further configured to determine, in the server side list, the A server that can provide call history.

With reference to the second aspect and the foregoing implementation manner, in a third implementation manner, the determining unit is further configured to: determine, in the server list, that the server used by the user is the service that can provide the call record Or determining, according to the user's selection, the server capable of providing the call record in the server list or the server used by the user.

With reference to the second aspect, and the foregoing implementation manner, in the fourth implementation manner, the call record invoking request further includes: one or more services that are selected by the user to be selected by the client to provide a call record. Information on the side.

With reference to the second aspect and the foregoing implementation manner, in a fifth implementation manner, the call record acquisition request includes an additional request condition, where the additional request condition includes at least one of the following: a string for indicating a search object ; A numeric value used to indicate the limit on the number of call records returned; a string used to indicate the search criteria.

With reference to the second aspect and the foregoing implementation manner, in the sixth implementation manner, the second sending unit is further configured to: send the call record to the client, to display, import, or Store the call record.

With reference to the second aspect and the foregoing implementation manner, in a seventh implementation manner, the predefined format of the call record includes at least one of the following: a unique identifier of the call record; an identity of the call user; and a display of the call user Name; call occurrence date; call duration; location information during the call; attachment during the call; screenshot during the call; recording or recording during the call; conference call or video conference information. The method provided by the embodiment of the present invention and the user equipment call the call records of other servers on any client, enhance the operability of the call record, facilitate management, and enable call record calling across applications or web pages. DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings to be used in the embodiments of the present invention will be briefly described below. It is obvious that the drawings described below are only some embodiments of the present invention, Those skilled in the art can also obtain other drawings based on these drawings without paying any creative work.

1 is a flow chart of a call record calling method according to an embodiment of the present invention.

2 is an interaction diagram of a call record calling method according to an embodiment of the present invention.

3 is an interaction diagram of a call record calling method according to another embodiment of the present invention.

4 is a schematic block diagram of a user equipment according to an embodiment of the present invention.

FIG. 5 is a schematic block diagram of a user equipment according to another embodiment of the present invention. detailed description

BRIEF DESCRIPTION OF THE DRAWINGS The technical solutions in the embodiments of the present invention will be described in detail below with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are a part of the embodiments of the present invention, rather than all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the scope of the present invention.

1 is a flow chart of a call record calling method according to an embodiment of the present invention. The method of Figure 1 is performed by a User Agent (UA).

101. Receive a call record call request sent by a client, where the call record call request includes: an action field for indicating a call operation and a type field for indicating that the data type is a call record.

102. Determine, according to the call record call request, a server that can provide a call record.

103. Send a call record acquisition request to the server.

104. The receiving server sends a response message according to the call record acquisition request, where the response message includes: a call record that conforms to a predefined format, or an error response indicating an error type.

The method provided by the embodiment of the invention invokes the call records of other servers on any client, enhances the operability of the call record, facilitates management, and can realize call record calling across applications or web pages. In the embodiment of the present invention, the user agent (UA) is a general term for a browser or an operating system, such as Microsoft Internet Explorer browser, Google's Google Chrome browser or Web-based Operating System, and the like. The client refers to an application that initiates an interactive request, where the client can be a local application ( Native Apps), or a web application (Web Apps), such as Web Real Time Communication (Web Real Time Communication). WebRTC) WebRTC Apps. More broadly, the client can also just be the page or web page that initiates the interactive request, such as pages of social networking sites such as Fa _C eb ₀₀ k, Renren.com, Tencent Friends.com, and so on. The server refers to an application that responds to a client request or provides services to a client. The server can be a Native Apps or a Web Apps, such as WebRTC Apps. Similarly, the server can also exist in the form of a page or a web page, such as a page of social networking websites such as Fa _C eb ₀₀ k, Renren.com, Tencent Friends.

For convenience of description, the embodiment of the present invention is described by taking a call record call between Web Apps as an example, but the embodiment of the present invention is not limited thereto, a web application and a local application, a web application and a webpage, a webpage and a webpage, a local application and a local Combinations of applications and the like also fall within the scope of protection of the present invention.

Optionally, as an embodiment, before step 101, the method further includes: receiving a registration request sent by the server; sending a registration request to the registration center, where the registration request is used to indicate to the registration center that the server can provide the call record calling service. That is to say, before providing the call record calling service, the server needs to register in the registration center through the browser. Of course, the server can also register directly in the registration center without using the browser. The registration request may include: an action field for indicating a call operation, and a type field for indicating that the data type is a call record. The registration center may be an application store (App Store) or a third-party registration platform, such as webintents.org, etc., which is not limited by the present invention.

Optionally, as another embodiment, in step 101, the call record call request includes: an action field for indicating a call operation and a type field for indicating that the data type is a call record. The action field and the type field in the call record call request need to be consistent with the action field and the type field in the registration request, so that the registry matches the registered server capable of providing the call record calling service according to the call record call request. Further, the call record invocation request may further include an additional request condition, wherein the additional request condition may include at least one of the following: a character string for indicating the search object; a value indicating a limit number of the call record return; A string of conditions.

Optionally, as another embodiment, step 102 includes: sending a call record invocation request to the registration center, so that the registration center determines, according to the action field and the type field, a server list capable of providing a call record invoking service; receiving the sending by the registration center Server list; determine in the server list A server that provides call records. The server that can provide the call record in the server list includes: determining, in the server list, that the server used by the user is a server capable of providing a call record; or according to the user's selection, in the server list Identify the server that can provide call history.

Optionally, in another embodiment, in step 101, the call record invoking request further includes: information indicating one or more servers that the user selects at the client to provide the call record. That is to say, the user can directly select one or more servers on the client side, so that the registry is not required to be searched by the browser to generate a list of candidate servers for the user to select.

Optionally, as another embodiment, in step 103, the call record acquisition request includes an additional request condition, where the additional request condition may include at least one of the following: a character string used to indicate the search object; Returns the number of the limit; a string that indicates the search criteria. That is, after the browser determines the server that can provide the call record, it sends the additional request condition obtained from the call record invocation request to the server to perform the call record retrieval with the qualification condition.

Optionally, as another embodiment, in step 104, the response message includes: matching a call record in a predefined format, or an error response indicating an error type. When the server can provide a call record according to the client's request, the server can return the call record to the browser in a predefined format. If any kind of error occurs, the server can return an error message. The predefined format may include at least one of the following: a unique identifier of the call record; an identity of the call user; a display name of the call user; a date of the call; a duration of the call; location information during the call; an attachment during the call ; screenshots during the call; recording or recording of the call; conference call or video conference information.

Optionally, as another embodiment, after step 104, the method further includes: sending a call record to the client to display, import, or store the call record on the client. After receiving the call record in a predefined format sent by the server, the browser may display the call record in the predefined format on the client page, and may perform subsequent import or storage operations according to the user's instruction, or may not Directly import or store operations through the display of the client page.

The method provided by the embodiment of the invention can implement the call record of other servers on any client, enhances the operability of the call record, facilitates management, and can realize call record calling across applications or web pages.

2 is an interaction diagram of a call record calling method according to an embodiment of the present invention. In Figure 2, the User Agent (UA) is a general term for a browser or operating system, such as Microsoft Internet Explorer. , Google's Google Chrome or Web-based Operating System, and more. A client refers to an application that initiates an interactive request, where the client can be a Nat ive Apps or a Web Apps, such as WebRTC Apps. More broadly, the client can also just be the page or web page that initiates the interactive request, such as pages of social networking sites such as Fa _C eb ₀₀ k, Renren.com, Tencent Friends.com, and so on. The server refers to an application that responds to a client request or provides services to a client. The server can be a Native Apps or a Web Apps, such as WebRTC Apps. Similarly, the server can also exist in the form of a page or a web page, such as a page of social networking websites such as Fa _C eb ₀₀ k, Renren.com, Tencent Friends. The registration center may be an application store (App Store) or a third-party registration platform, such as webintents.org, etc., which is not limited by the present invention.

201. The server sends a registration request to the registration center.

The server sends a registration request to the browser, and further forwards the registration request to the registration center by the browser, or the registration center directly receives the registration request sent by the server, so that the server can provide the service it can provide in the registration center. Sign up. The registration request may include an action field for indicating a call operation and a type field for indicating that the data type is a call record. For example, define the action field action : http : //webintents. org/pick ; Type Field type: http:〃 w3. org/type/cal lLog, where pick is used to indicate the call operation and cal lLog is used to indicate the call record.

When the server is registering, the registration request sent can use the following statement:

<: intent action ^=// http: //webintents. org/pick〃

Type=〃http : //w3. org/ type/ cal lLog ⁷⁷

Encoding ^=// appl ication/ json〃 >

</ intent)

The above is the call record page of the server registered in the registration center as a call record calling service of the action/type defined above, and the call record page can be identified by a Uniform Resource Identifier (URI).

It should be understood that the call log may come from multiple sources, including on the network and local to the user device (e.g., call logs on the user device). That is to say, the server to be registered can be not only an application or a webpage, but also a service on the device, for example, Cal lLog. Cal ls application provided by Android system (Appl ication Programming Interface, API) ).

In addition, WebRTC apps can be registered as a service for call recording, and can also be registered as a service for calling. For example, define action as cal l and define type as text/string. In this way, if there is a valid account such as a phone number or an email address in the client, click the "dial" button to call up the server that can provide the call service through the browser and the registration center, select one of them, and dial out the call. This kind of scene can usually be used for online shopping applications or web pages to contact sellers, online games or web games to contact teammates.

The process of registering in the application center may be performed when the application is put on the shelf, or may be executed when the application is updated, or may be registered by manually writing the code, which is not limited by the present invention.

202. The client sends a call record invocation request to the UA.

When the user opens a client, it can be a WebRTC App or a normal application, and a button for triggering a call record call, such as a "call record", an "import" button, is clicked on the page of the application to initiate a call record call request. The call record invocation request may include an action/type corresponding to the call record calling service in the registration request in the above step 201, so that the registration center searches for a server capable of providing the service according to the action/type matching. The client sends the call record call request to the browser.

In addition, the client can also call the call record not only through a button, but also allows the user to select some qualification conditions for retrieving the call record, such as searching by number, person name, etc., or requesting only partial data, etc. . In this way, an additional request condition can be generated by the user's selection and limitation, and the request bearer is called by the call record and sent to the browser. For example, the following code can be generated according to the qualification conditions selected by the user:

Dictionary Cal lLoglntentExtras {

DOMString search;

Unsigned long l imit;

Sequence<D0MString> fields; where the search string in the DOMString field is a qualification condition for the search object to indicate to the search object. For example, the string can be defined as the person name Al ice , that is, the search is specified and returned related to Al ice. Call history. l imit can be used to select a value, so that the server can return a call record entry that does not exceed the value. For example, if the value is 10, if the number of eligible call records is greater than 10, only the maximum value is returned. 10 articles. The sequence <D0MString> field can be an array of strings used to indicate the search condition. It is used to prompt the server when searching. For example, if the search domain is a person name, the server only searches in the person name column.

It should be understood that the code of the above additional request condition is only an example, and is added in the embodiment of the present invention. The domain of the condition is not limited to the three domains in the above code. Of course, the above three domains are not required, and the present invention does not limit this. If the client does not trigger the call record calling process directly by the button by setting an additional qualification condition, the above additional request condition may be collected after determining the server that provides the call record.

After receiving the call record invocation request, the browser sends the call record invocation request to the registration center. If the call record call request contains the most basic action/type and includes an additional request condition, the browser may choose to only send the action/type to the registry, and cache the additional request condition locally for later selection. Send the server that provides the call record before sending it. Of course, it can also be sent along with the additional request conditions.

203. The registration center sends a server list to the UA.

After receiving the call record invocation request, the registration center obtains the action/type field, and performs a matching search in the action/type field of the previously registered application according to the action/type field to determine that the registration is a service capable of providing the call record calling service. End, and generate a list. Return the list to the browser for selection. The server list capable of providing the call record calling service may include the URI of the call record page of each server in the list.

204. The UA determines a server that can provide a call record.

After receiving the list of servers that can provide the call record calling service, the browser needs to determine the server that can provide the call record, that is, the target server that actually makes the call record call. This determination process can be implemented in various ways:

In the first embodiment, the browser can directly determine the server used by the user as the target server in the server list capable of providing the call record calling service, that is, the server capable of providing the call record, wherein the target server can be one or more One. Specifically, the user logs in to the browser through the account, and the browser stores the history record, the historical setting of the account, and the related information (such as the WebRTC service provider) used by the user in the cloud, so that the browser can directly obtain from the cloud. The server that the user has used. And even if the user uses the browser on a different user device, as long as the browser account is logged in, it is also possible to determine the server that the user has used.

In the second embodiment, the browser may determine the server used by the user in the server list. The specific method is the same as the real-time mode described above, and the determined server list used by the user is sent to the client, or the pop-up window is displayed. The list of servers used by the user is displayed in the middle or directly on the page for the user to select. According to the user's selection, the target server is determined, that is, the server capable of providing the call record, wherein the user can select one or more servers as the target server. In the third embodiment, the browser can directly send the server list to the client, or display it in a pop-up window or directly on the page for the user to select. Then, according to the user's selection, the target server is determined, that is, the server capable of providing the call record, wherein the user can select one or more servers as the target server.

Of course, the browser can also list the servers installed on the browser and recommended by the App Store for users to choose.

After the target server is determined, the browser can prompt the user to input the account password to log in to the target server. The browser can also pre-set the trust relationship with the specific server, and does not need to directly obtain the login authorization through user interaction, for example, the user has The authorized browser remembers the account password entered. Alternatively, the user ID can be integrated by all service providers. As long as the user logs in once, it is valid for all similar applications (such as WebRTC App), namely Single Sign On (SSO).

205. The UA sends a call record acquisition request to the server.

After determining that the server can provide the call record, and the verification succeeds, the browser logs in to the server that can provide the call record, and sends a call record acquisition request to the server. Specifically, in step 202, the browser sends the cached additional request condition to the server by using a call record acquisition request. Alternatively, in the case that the browser does not cache the additional request condition, the search condition similar to the above-mentioned additional request condition may be obtained from the user, and the search condition is transmitted to the server through the Cal lLoglntentExtras. For details, refer to step 202 above. .

206, the server returns a response.

After receiving the call record acquisition request, the server capable of providing the call record returns the call record that meets the requirements to the browser according to the predefined format according to the additional request condition or the newly acquired search condition. Afterwards, the browser can directly display the call record on the client's page. In this way, the server provides the call record page to run but does not open, avoiding the jump between pages, but requires the postResult time to be triggered automatically, for example, based on the onload event. Implement automatic triggering. Of course, you can also open the page that provides the call record on the server in a new window or tab. This method requires the user to manually trigger a postResult event, such as clicking a button. When any of the above procedures occur, the browser can return an error message error, such as using postFai lure to return an error and indicating the type of error. If the user selects 0 servers or cancels the operation, no error processing is performed. In addition, in addition to displaying the call record on the client's page, it is also possible to perform an import or store operation directly on the client according to the user's selection, or to provide a button such as import or store after the call record is displayed on the page. Take a further look. The call records that meet the requirements are processed into a predefined format, so that call records of different formats of different applications or web pages can be processed into the same format when called. That is to say, the consistency of the data provided by the server to the client is standardized by a predefined format. For example, when the call is successful, the server may return an array of Cal lLog objects, which may include not only a call record, but also text, an attachment, a recording, a picture, a video, etc., which is not limited by the present invention. For example, the call record format can be as follows:

Dictionary Cal lLog {

DOMString id ;

DOMString cal l ld;

DOMString displayName;

Posit ion location;

DOMString type ;

Date date;

Unsigned long duration;

Sequence<DOMString> styles;

Sequence<Cal lLogField> screenshots;

Sequence<Cal lLogField> recordings;

Sequence<Cal lLogField> attachments;

Sequence<Cal lLogChat> chatLogs;

Sequence<Cal lLogMeeting> meet ingLogs where the id in the DOMString is used to indicate the unique identifier of each call record; cal l ld is used to indicate the identity (such as the phone number) of the webRTC service associated with the call record; displayName Indicates the other party's display name (nickname); the location in the Posit ion is used to indicate the location information during the call; the type in the DOMString is used to indicate the type of the call, such as missed, dialed out, dialed in; date is used to indicate the call The date of occurrence; duration is used to indicate the duration of the call; styles is used to indicate the style, such as audio, audio/video, text, etc.; screenshots is used to indicate the screen capture related to the call record; recordings is used to indicate the call record with the call One or more related recordings; attachments are used to indicate one or more attachments associated with the call record; chatLogs is used to indicate one or more text chats associated with the call record; meetingLogs is used to indicate One or more conference call records associated with the call history. As a specific example, the WebRTC server can create a call record object using a predefined call record format, populate the content, and use postResultO to return the result:

If (window, intent) {

Var content = {};

Content, uri = ^/r http: //example. com/callLogs/^;

Var callLogOb ject = new Object ();

callLogOb ject. Name = Alice;

callLogOb ject. Num_webrtc =1890000000;

callLogOb ject. Type=IN;

callLogOb ject. State = yes;

callLogObject. Date. start= "20130209 12:12" ;

Var callLogOb jectArr ay = new Array ();

callLogOb jectArray [0] = callLogObject;

If (callLogOb jectArray) { window, intent. postResult (callLogOb jectAr ray); }

Else {window, intent. postFai lure (errorMessage); } </ script)

The above code carries a call record, the other party's name Alice, the phone number is 1890000000, and the call type is dial-in. The time is February 12, 2013 at 12:12. The call record (postResult) is returned when the judgment statement is successful, and the error message (postFailure) is returned in case of an error.

Also as an example of client code:

Var intent = new Intent ( { action: "http:// intents. w3. org/pick^, type: "http:// intents. w3. org/type/ callLog^,

Extras: { search: "Alice", limit: 10 navigator. startActivity (intent, callLogOK, callLogFai 1);

Function callLogOK (callLogOb jectArray) {

II do something useful with them} Function cal lLogFai l (err) {

II display an error to the user}

The act ion/type field indicates that the client requests to call the call record, and the extras lists some additional conditions or search conditions. After the request is sent, the callback functions cal lLogOK and cal lLogFai l are used to obtain the response, receive the required call record, or return. Error message.

3 is an interaction diagram of a call record calling method according to another embodiment of the present invention. In Figure 3, the User Agent (UA) is a generic term for a browser or operating system, such as Microsoft's Internet Explorer browser, Google's Google Chrome browser, or Web-based Operating System. A client refers to an application that initiates an interactive request, where the client can be a Nat ive Apps or a Web Apps, such as WebRTC Apps. More broadly, the client can also just be the page or web page that initiates the interactive request, such as pages of social networking sites such as Fa _C eb ₀₀ k, Renren.com, Tencent Friends.com, and so on. The server refers to an application that responds to a client request or provides services to a client. The server can be a Native Apps or a Web Apps, such as WebRTC Apps. Similarly, the server can also exist in the form of a page or a web page, such as a page of social networking websites such as Fa _C eb ₀₀ k, Renren.com, Tencent Friends. The registration center may be an application store (App Store) or a third-party registration platform, such as webintents.org, etc., which is not limited by the present invention.

The server registration process of the embodiment in FIG. 3 is similar to step 201 in FIG. 2 above, and details are not described herein again.

301. The client selects a server that can provide a call record.

The user can directly select the server that can provide the call record on the client user's page. Specifically, the server may be a plurality of servers preset by the client, or may be displayed by the server used by the client from the browser for the user to select, and the user may select one or more of the servers. The server is the server that can provide the call record. It should be understood that the process of user selection is not limited to the check, and may be implemented by a method such as manually inputting a client name or a URI by the user, and the embodiment of the present invention is not limited thereto.

302. The client sends a call record invocation request to the UA.

After the client obtains the user's selection, the client generates a call record invocation request and sends it to the browser. Specifically, after the user selects the server and clicks the button for indicating the determination, the client selects according to the user. The call record invoking request is generated, wherein the action/type and the optional additional request condition in the call record invoking request are similar to those in the above step 202 in FIG. 2, and are not described here again, the difference is that the embodiment The call record invoking request also needs to carry information of one or more specified servers selected by the user, for example, carrying a URI or a name of the specified server.

303. The UA sends a call record acquisition request to the server.

After receiving the call record invocation request, the browser directly sends a call record acquisition request to the designated server according to the information of the specified server carried therein, wherein the call record acquisition request is similar to step 205 in FIG. 2 above, where Let me repeat.

304, the server returns a response.

After receiving the call record acquisition request, the designated server returns the matching call record to the browser according to the pre-defined format according to the additional request condition or the newly acquired search condition. Afterwards, the browser can display the call record directly on the client's page, or perform import or storage operations directly on the client according to the user's selection, or provide a button such as import or store after the call record is displayed on the page. Carry out further operations and so on. For details, refer to step 206 in Figure 2 above, and details are not described herein again.

4 is a schematic block diagram of a user equipment according to an embodiment of the present invention. The user equipment 400 of FIG. 4 includes a first receiving unit 401, a determining unit 402, a transmitting unit 403, and a second receiving unit 404.

The first receiving unit 401 receives a call record invocation request sent by the client, and the call record invoking request includes: an action field for indicating a calling operation and a type field for indicating that the data type is a call record. The determining unit 402 determines the server capable of providing the call record based on the call record invocation request received by the first receiving unit 401. The sending unit 403 sends a call record acquisition request to the server. The second receiving unit 404 receives the response message sent by the server according to the call record acquisition request sent by the sending unit 403, and the response message includes: a call record conforming to a predefined format or an error response indicating an error type.

The user equipment provided by the embodiment of the present invention can implement call record calling across applications or web pages. Optionally, as an embodiment, the first receiving unit 401 is further configured to: receive a registration request sent by the server; the sending unit 403, send a registration request to the registration center, where the registration request is used to indicate to the registration center that the server can provide the call Record the calling service. That is, in the call record service Previously, the server needed to register at the registry through a browser. The registration request may include: an action field for indicating a call operation; and a type field for indicating that the data type is a call record.

Optionally, as another embodiment, the call record invocation request and the registration request include: an action field for indicating a call operation; and a type field for indicating that the data type is a call record. The call record invocation request may further include an additional request condition, wherein the additional request condition includes at least one of the following: a character string for indicating a search object; a value indicating a limit number of the call record return; a string indicating the search condition; .

Optionally, as another embodiment, the sending unit 403 is further configured to send a call record invocation request to the registration center, so that the registration center determines, according to the action field and the type field, a server list that can provide a call record invoking service; the receiving unit 401 further For receiving the server list sent by the registration center; the determining unit 402 is further configured to determine, in the server list, a server that can provide the call record.

Optionally, in another embodiment, the determining unit 402 is further configured to: determine, in the server list, that the server used by the user is a server that can provide a call record; or determine, according to the user's selection, the server list. A server that can provide call history. That is to say, the user can directly select one or more servers on the client side, so that the browser is not required to search the registry to generate a list of candidate servers for the user to select.

Optionally, as another embodiment, the call record invoking request further includes: information indicating one or more servers that the user selects at the client to provide the call record.

Optionally, as another embodiment, the call record acquisition request includes an additional request condition. That is to say, after the user equipment 400 determines the server that can provide the call record, the server requests the additional request condition obtained from the call record invocation request to perform the call record information retrieval with the qualified condition.

Optionally, as another embodiment, the response message includes: a call record that conforms to a predefined format; or an error response indicating an error type. When the server can provide a call record according to the request of the client, the server can return the call record to the user device 400 in a predefined format. If any kind of error occurs, the server can return an error message. The predefined format may include at least one of the following: a unique identifier of the call record; an identity of the call user; a display name of the call user; a date of the call; a duration of the call; location information during the call; an attachment during the call ; screenshots during the call; recording or recording of the call; conference call or video conference information.

Optionally, in another embodiment, the second sending unit 404 is further configured to: send a call record to the client, so as to display, import, or store the call record on the client. User equipment 400 receives the service After the call record of the predefined format sent by the server, it can be displayed on the client page, and subsequent import or storage operations can be performed according to the user's instruction, or can be directly imported without the display of the client page or Storage and other operations.

The user equipment 400 provided by the embodiment of the present invention can implement call records of other servers in any one client, enhance the operability of the call record, facilitate management, and can realize call record calling across applications or web pages.

FIG. 5 is a schematic block diagram of a user equipment according to another embodiment of the present invention. The user equipment 500 of FIG. 5 includes a processor 501 and a memory 502. The processor 501 and the memory 502 are connected by a bus system 503.

The memory 502 is configured to store an instruction that causes the processor 501 to: receive a call record call request sent by the client, where the call record call request includes: an action field for indicating a call operation and a data record indicating that the data type is a call record. a type field; determining, according to the call record calling request, a server that can provide a call record; sending a call record acquisition request to the server; and receiving a response message sent by the server according to the call record acquisition request, the response message includes: conforming to a predefined format Call log; or an error response indicating the type of error.

The user equipment provided by the embodiment of the present invention invokes call records of other servers on any client, enhances the operability of the call record, facilitates management, and can realize call record calling across applications or web pages.

In addition, the user equipment 500 may further include a transmitting circuit 504, a receiving circuit 505, and the like. The processor 501 controls the operation of the user equipment 500, which may also be referred to as a CPL Central Processing Unit, central processing unit. Memory 502 can include read only memory and random access memory and provides instructions and data to processor 501. A portion of memory 502 may also include non-volatile random access memory (NVRAM). In a specific application, the various components of the user equipment 500 are coupled together by a bus system 503, which may include, in addition to the data bus, a power bus, a control bus, a status signal bus, and the like. However, for clarity of description, various buses are labeled as bus system 503 in the figure.

The method disclosed in the foregoing embodiments of the present invention may be applied to the processor 501 or implemented by the processor 501. Processor 501 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 501 or an instruction in a form of software. The processor 501 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware. Component. Can be implemented or executed Various methods, steps, and logic blocks disclosed in the embodiments of the invention. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software modules can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 502, and the processor 501 reads the information in the memory 502, and completes the steps of the foregoing method in combination with hardware.

Optionally, as an embodiment, the registration request sent by the server is received by the receiving circuit 505. Then, the registration request is sent by the transmitting circuit 504 to the registration center, where the registration request is used to indicate to the registration center that the server can provide the call record calling service. . That is to say, before providing the call record calling service, the server needs to register in the registry through the browser. The registration request may include: an action field for indicating a call operation; and a type field for indicating that the data type is a call record.

Optionally, as another embodiment, the transmitting circuit 504 is further configured to send a call record invoking request to the registration center, so that the registration center determines, according to the action field and the type field, a server list that can provide a call record invoking service; the receiving circuit 505 further For receiving the server list sent by the registration center; the processor 501 is further configured to determine, in the server list, a server that can provide a call record.

Optionally, in another embodiment, the processor 501 is further configured to: determine, in the server list, that the server used by the user is a server that can provide a call record; or determine, in the server list, according to the user's selection. A server that can provide call history. That is to say, the user can directly check one or more servers on the client side, so that the browser is not required to search the registry to generate a list of candidate servers for the user to select.

Optionally, as another embodiment, the call record acquisition request includes an additional request condition. That is, after the user equipment 500 determines the server that can provide the call record, the server sends the additional request condition obtained from the call record invoking request to the server to perform the call with the qualified condition. Record information retrieval.

Optionally, as another embodiment, the response message includes: a call record that conforms to a predefined format; or an error response indicating an error type. When the server can provide a call record according to the request of the client, the server can return the call record to the user equipment 500 in a predefined format. If any kind of error occurs, the server can return an error message. The predefined format may include at least one of the following: a unique identifier of the call record; an identity of the call user; a display name of the call user; a date of the call; a duration of the call; location information during the call; an attachment during the call ; screenshots during the call; recording or recording of the call; conference call or video conference information.

Optionally, as another embodiment, the call record is sent to the client through the transmitting circuit 504 to display, import or store the call record on the client. After receiving the call record in a predefined format sent by the server, the user equipment 500 may display the call record on the client page, and may perform subsequent import or storage operations according to the user's instruction, or may not go through the client page. Display operations such as import or storage directly.

Those skilled in the art will appreciate that the various method steps and elements described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both, for clarity of hardware and software. Interchangeability, The steps and compositions of the various embodiments have been described generally in terms of functionality in the foregoing description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. Different methods may be used to implement the described functionality for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

The methods or steps described in connection with the embodiments disclosed herein may be implemented in hardware, a software program executed by a processor, or a combination of both. Software programs can be placed in random access memory (RAM), memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or technical field Any other form of storage medium known.

Although the present invention has been described in detail by reference to the accompanying drawings in the preferred embodiments, the invention is not limited thereto. Various equivalent modifications and alterations to the embodiments of the present invention may be made by those skilled in the art without departing from the spirit and scope of the invention.

Claims

Rights request

1. A call record invoking method, characterized by including:

Receive a call record calling request sent by the client, where the call record calling request includes: an action field used to indicate the calling operation and a type field used to indicate the data type is a call record;

Determine a server that can provide call records according to the call record calling request;

Send a call record acquisition request to the server;

Receive a response message sent by the server according to the call record acquisition request, where the response message includes: a call record that conforms to a predefined format, or an error response indicating an error type.

2. The method according to claim 1, characterized in that the call record calling request also includes additional request conditions, wherein the additional request conditions include at least one of the following:

A string indicating the search object;

A value used to indicate the limit on the number of call records returned;

A string indicating the search criteria.

3. The method according to claim 1 or 2, characterized in that, determining a server capable of providing call records based on the call record calling request includes:

Send the call record calling request to the registration center, so that the registration center determines a list of servers that can provide call record calling services based on the action field and the type field;

Receive the server list sent by the registration center;

The server capable of providing call records is determined in the server list.

4. The method according to claim 3, wherein determining the server capable of providing call records in the server list includes:

Determine in the server list that the server that the user has used is the server that can provide call records; or

According to the user's selection, the server capable of providing call records is determined in the server list or among the servers used by the user.

5. The method according to claim 1 or 2, characterized in that, the call record calling request further includes: used to indicate one or more services capable of providing call records selected by the user on the client. terminal information.

6. The method according to any one of claims 1 to 5, characterized in that the call record acquisition request includes additional request conditions, wherein the additional request conditions include at least one of the following: A string indicating the search object;

A value used to indicate the limit on the number of call records returned;

A string indicating the search criteria.

7. The method according to any one of claims 1 to 6, characterized in that, after receiving the response message sent by the server according to the call record acquisition request, the method further includes: The call record is sent to the client so that the call record can be displayed, imported or stored on the client.

8. The method according to any one of claims 1 to 7, characterized in that the predefined format of the call record includes at least one of the following:

The unique identifier of this call record;

The identity of the calling user;

The display name of the calling user;

The date the call occurred;

call duration;

Location information during calls;

Attachments during the call;

Screenshots during the call;

Audio or video recording of the call;

Conference call or video conference information.

9. A user equipment, characterized in that it includes:

The first receiving unit is configured to receive a call record calling request sent by the client, where the call record calling request includes: an action field used to indicate the calling operation and a type field used to indicate the data type is call record;

A determining unit, configured to determine a server capable of providing call records based on the call record calling request, where the client is different from the server;

A sending unit, configured to send a call record acquisition request to the server;

The second receiving unit is configured to receive a response message sent by the server according to the call record acquisition request, where the response message includes: the call record conforming to a predefined format, or an error response indicating an error type.

10. The user equipment according to claim 9, characterized in that the call record invocation request also includes additional request conditions, wherein the additional request conditions include at least one of the following: A string indicating the search object;

A value used to indicate the limit on the number of call records returned;

A string indicating the search criteria.

11. The user equipment according to claim 9 or 10, characterized in that the sending unit is also configured to send the call record invocation request to a registration center, so that the registration center can call the call record according to the action field and the type. The field determines the list of servers that can provide call record calling services;

The receiving unit is also configured to receive the server list sent by the registration center;

The determining unit is also used to determine the service 2 that can provide call records in the server list.

12. The user equipment according to claim 12, wherein the determining unit is further configured to: determine in the server list that the server used by the user is the server capable of providing call records; or

13. The user equipment according to claim 9 or 10, characterized in that, the call record calling request further includes: a message for instructing the user to select one or more servers capable of providing call records selected by the client. information.

14. The user equipment according to any one of claims 9 to 13, characterized in that the call record acquisition request includes additional request conditions, wherein the additional request conditions include at least one of the following: used to indicate a search object String;

A value used to indicate the limit on the number of call records returned;

A string indicating the search criteria.

15 The user equipment according to any one of claims 9 to 14, characterized in that the second sending unit is further configured to: send the call record to the client for display on the client. Import or store the call records.

16. The user equipment according to any one of claims 9 to 15, characterized in that the predefined format of the call record includes at least one of the following:

The unique identifier of this call record;

The identity of the calling user;

The display name of the calling user;

The date the call occurred; Duration of the call; Location information during the call; Attachments during the call; Screenshots during the call; Audio or video recording of the call; Conference call or video conference information