阅读说明：本技术 机器人简档发现 (Robot profile discovery ) 是由 A·西纳尔 于 2018-06-27 设计创作，主要内容包括：提供了系统与方法,其涉及由用户设备(UE)在UE与实体呼叫建立期间发现来自实体的可用机器人功能。UE可利用会话发起协议(SIP)在通信网络中向例如商业的实体发起呼叫,并且通信网络的运营商可在SIP报头中添加由商业所提供的机器人功能的简档,以作为SIP信令的一部分而转发至UE。一旦UE对包含在简档中的信息进行处理,则UE和商业可利用机器人功能进行通信。(Systems and methods are provided that relate to discovering available robot functions from an entity by a User Equipment (UE) during a UE and entity call setup. The UE may initiate a call in the communication network to an entity, such as a business, using Session Initiation Protocol (SIP), and an operator of the communication network may add a profile of the robot functions provided by the business in a SIP header for forwarding to the UE as part of the SIP signaling. Once the UE processes the information contained in the profile, the UE and the business may communicate using the robot function.)

1. A method for a first User Equipment (UE) to discover a robot function of a second UE, the method comprising:

detecting, at a server of a communication network, a call destined for a first UE;

adding, by the server, a robot information profile associated with the robot function of a second UE to the call;

forwarding the call to the first UE; and

providing the robot information profile to the first UE.

2. The method of claim 1, further comprising:

downloading, by the first UE, the robot function based on the robot information profile.

3. The method of claim 1, wherein the call is initiated using one of:

the Session Initiation Protocol (SIP) protocol,

the telephone call is made to the telephone,

instant messaging, or

A Uniform Resource Indicator (URI).

4. The method of claim 3, wherein adding, by the server, the robot information profile associated with the second UE to the call comprises:

inserting, by the server, the robot information profile into a SIP header of the call.

5. The method of claim 4, wherein inserting, by the server, the robot information profile into a SIP header of the call comprises:

inserting a Personal Contact Card (PCC) value in the SIP header, the PCC value identifying the robot information profile,

inserting a vCard in the SIP header, the v-card identifying the robot information profile, or

Inserting a Uniform Resource Locator (URL) in the SIP header, the URL linking to the robot function downloadable for the first UE.

6. The method of claim 1, wherein:

the call is initiated by the second UE and the server is an originating telephony application server (O-TAS) in the communication network, or

The call is a response from the second UE destined for the first UE in response to an originating call received by the second UE from the first UE, and the server is a terminating telephony application server (T-TAS) in the communication network.

7. The method of claim 6, further comprising:

downloading, by the first UE, the robot function based on the robot information profile; and is

Establishing communication between the first UE and the second UE using the robot function.

8. The method of claim 6, wherein

The second UE is configured to cause an operator of the communication network to add the robot information profile to the call, or

If the call is a response from the second UE destined for the first UE, the first UE is configured to request the operator to add the robot information profile to the call.

9. A non-transitory computer storage medium storing computer-readable instructions executable by a computer, the computer-readable instructions, when executed by the computer, causing the computer to perform operations comprising:

detecting, at a server of a communication network, a call destined for a first UE;

adding, by the server, a robot information profile associated with a robot function of a second UE to the call;

forwarding the call to the first UE; and

providing the robot information profile to the UE.

10. The non-transitory computer storage medium of claim 9, wherein the operations further comprise:

when acceptance of the robot function of the second UE is detected from the first UE according to the robot information profile, causing the first UE to download the robot function according to the robot information profile.

11. The non-transitory computer storage medium of claim 9, wherein the call is initiated using one of:

the Session Initiation Protocol (SIP) protocol,

the telephone call is made to the telephone,

instant messaging, or

A Uniform Resource Indicator (URI).

12. The non-transitory computer storage medium of claim 11, wherein adding, by the server, the robot information profile associated with the second UE to the call comprises:

inserting a Personal Contact Card (PCC) value in a SIP header of the call, the PCC value identifying the robot information profile,

inserting a vCard in the SIP header, the v-card identifying the robot information profile, or

Inserting a Uniform Resource Locator (URL) in the SIP header, the URL linking to the robot function downloadable for the first UE.

13. The non-transitory computer storage medium of claim 9, wherein:

the call is initiated by the second UE and the server is an originating telephony application server (O-TAS) in the communication network, or

The call is a response from the second UE destined for the first UE in response to receiving an originating call from the first UE by the second UE, and the server is a terminating telephony application server (T-TAS) in the communication network.

14. The non-transitory computer storage medium of claim 13, the operations further comprising:

upon detecting acceptance of the robotic function of the second UE from the first UE according to the robotic information profile,

causing the first UE to download the robot function based on the robot information profile; and

establishing communication between the first UE and the second UE using the robot function.

15. The non-transitory computer storage medium of claim 13, wherein:

the second UE is configured to cause an operator of the communication network to add the robot information profile to the call, or

If the call is a response from the second UE destined for the first UE, the first UE is configured to request the operator to add the robot information profile to the call.

16. A server located in a communication network and configured to enable a first User Equipment (UE) to discover a robot function of a second UE, the system comprising:

one or more processors;

a memory communicatively coupled with the one or more processors, the memory storing computer-readable instructions executable by the one or more processors, the operations performed by the server when the computer-readable instructions are executed by the one or more processors comprising:

detecting a call destined for a first UE;

adding a robot information profile associated with the robot function of the second UE to the call;

forwarding the call to the first UE; and

providing the robot information profile to the first UE.

17. The server of claim 16, wherein the operations further comprise:

when the first UE detects that the second UE accepts the robot function according to the robot information profile, causing the first UE to download the robot function based on the robot information profile.

18. The server of claim 16, wherein the call is initiated using one of:

the Session Initiation Protocol (SIP) protocol,

the telephone call is made to the telephone,

instant messaging, or

A Uniform Resource Indicator (URI).

19. The server of claim 18, wherein adding the available robot information profile associated with the call to the call comprises:

inserting a Personal Contact Card (PCC) value in a SIP header of the call, the PCC value identifying the robot information profile,

inserting a vCard in the SIP header, the v-card identifying the robot information profile, or

Inserting a Uniform Resource Locator (URL) in the SIP header, the URL linking to the robot function downloadable for the first UE.

20. The server of claim 16, wherein:

initiating the call by the second UE, the second UE configured to cause an operator of the communication network to add the robot information profile to the call, and the server being an originating telephony application server (O-TAS) in the communication network, or

The call is responsive to receiving an originating call from the first UE by the second UE to a response from the second UE destined for the first UE, the first UE is configured to request the operator to add the robot information profile to the call, and the server is a terminating telephony application server (T-TAS) in the communication network.

Background

Modern telecommunications systems include a heterogeneous mix of second, third and fourth generation (2G, 3G, and/or 4G) cellular network radio access technologies that are cross-compatible and interoperable to provide data communication services. Examples of 2G telecommunications technologies are global system for mobile communications (GSM); examples of 3G telecommunication technologies are universal mobile telecommunications systems, while examples of 4G telecommunication technologies are long term evolution technologies including LTE Advanced and evolved high speed packet access (HSPA +). As a next generation mobile network, 5G telecommunications technology is designed to combine both evolution and innovation of existing LTE mobile networks/LTE-a mobile networks to provide higher connectivity, greater throughput, less latency, and ultra-high reliability for new use cases and applications. Certain mobile devices operating in such telecommunication systems may also operate for voice and data over WIFI networks, also known as voice over IP (VoIP) technology.

Session Initiation Protocol (SIP) may be used in modern telecommunication networks, such as Internet Protocol (IP) networks, and SIP may control multimedia communication sessions, such as video, video calls, instant messaging, social media communications, and the like. Businesses can leverage SIP capabilities to provide their clients with an option to enable the clients to communicate with the business via a bot function, such as a chat bot, which can perform automated tasks. However, the customer is not always aware of the availability of such robot functionality.

Drawings

The detailed description is set forth with reference to the accompanying drawings. In the drawings, the left-most digit(s) of a reference number identifies the drawing in which the figure first appears. The use of the same reference numbers in different figures indicates similar or identical items or features.

Fig. 1 illustrates an example flow diagram for discovering, by a User Equipment (UE), that a robot function is available from an entity during a call setup initiated by the UE to the entity in a communication network.

Fig. 2 shows an example flow diagram for discovering, by an entity, that a robot function is available from the entity during initiation of a call setup to the UE by the entity in a communication network.

Fig. 3 shows an example process for a server to provide a robot information profile during call setup.

Fig. 4 shows an example block diagram of a server providing a robot information profile for discovering, by a UE, that robot functions are available from an entity during call setup.

Detailed Description

Systems and methods are disclosed that relate to discovering, by a User Equipment (UE), that robot functionality is available from an entity during a call setup between the UE and the entity.

For example, a user of the UE may call a pizza parlor from the UE to order a pizza. Such calls may be implemented in the communication network by Session Initiation Protocol (SIP) and as part of SIP signaling, the operator of the communication network may add a profile of the robot functions provided by the pizza parlor to the SIP header to be forwarded to the UE. The pizza shop may enter into an agreement with the operator to add the robot profile of the robot function to the call. The profiles may be electronic business cards (vCard), Personal Contact Cards (PCC), Uniform Resource Locators (URL), etc., which may be used to identify the availability of the robot function to the UE. Once the UE processes the information contained in the profile, the user may be prompted to complete future orders by "chatting" with the pizza parlor, for example by downloading a chat program identified in the profile from a robotic information server. Similarly, a pizza shop with robot functionality available to a customer may also initiate a call to another UE of another customer. As part of the SIP signaling, the operator of the communication network may also add a profile of the robot functions provided by the pizza parlor in the SIP header, which will be forwarded to another UE. Once another UE processes the information contained in the profile, the other user may be prompted to complete future orders by "chatting" with the pizza parlor.

Fig. 1 shows a flow chart 100 for discovering, by a User Equipment (UE), robot functions available from an entity in a call setup procedure between the UE and the entity in a communication network. The UE may be a UE of a client, and may also be referred to as a first UE or a client UE. The entity may be another UE belonging to a robot-enabled business, and may also be referred to as a second UE or business UE, which includes any devices associated with a robot-enabled profile. The communication network may be a landline network employing Internet Protocol (IP), a wireless network, or a combination of a terrestrial and wireless network.

In 102, the customer may place a call to a business, that is, a customer UE, shown as originating UE (O-UE)104, to a business user equipment, shown as terminating UE (T-UE 106). The call is shown as being placed from the O-UE104 to the originating telephony application server (O-TAS) using a Session Initiation Protocol (SIP) INVITE (INVITE)108, but such a call may also be initiated using a telephone call, instant message, Uniform Resource Indicator (URI), or the like. The O-UE104 may be configured to request the operator of the communication network to add the robot information profile to the call, if available during call setup.

SIP INVITE108 will eventually be forwarded to the commercial UE (T-UE 106) as follows: at 114, from the O-TAS110 to the originating IP multimedia subsystem (O-IMS)112, at 118 from the O-IMS 112 to the terminating IMS (T-IMS)116, at 122 from the T-IMS116 to the terminating TAS (T-TAS)120, and at 124 from the T-TAS120 to the T-UE 106.

In response to receipt of SIP INVITE108, T-UE 106, a business UE with robotic functionality, may send a response, such as SIP183 response 126, to T-TAS120 at 182. Upon detecting the SIP183 response 126 from the T-UE 106, the T-TAS120 may add or insert a robot information profile associated with the robot function of the T-UE 106 in the SIP183 response 126 and forward the SIP183 response 126 to the T-IMS116 at 130. The T-TAS120 may insert the robot information profile in the SIP183 response 126 by inserting a Personal Contact Card (PCC) value, vCard, or Uniform Resource Locator (URL) in the SIP header, where each of the PCC value, vCard, or URL may be used to identify the robot information profile associated with the T-UE 106. The SIP183 response 126 with the SIP header carrying the robot information profile will eventually be forwarded to the O-UE104, i.e. the client user equipment, as follows: from the T-IMS116 to the O-IMS 112 at 132, from the O-IMS 112 to the O-TAS110 at 134, and from the O-TAS110 to the O-UE104 at 136.

When the O-UE104, which is a client UE, receives the SIP183 response 126, the O-UE104 may be provided with a robot information profile associated with the robot functionality of the T-UE 106, i.e., the commercial user equipment, in accordance with the SIP header of the SIP183 response 126. The call setup process may then be completed and communication may be established between the O-UE104 as the client device and the T-UE 106 as the business user equipment in the manner in which the call is initiated.

Alternatively or additionally, the O-UE104 may then request a download of an application associated with the robotic function from the robotic information server 138, for example, by submitting an HTTP GET command 140 at 142, and receiving a 200OK response 144 at 148 along with the application or program for the robotic function 146 downloaded to the O-UE 104. After the O-UE104 downloads the bot 146, the O-UE104, which is a client UE, and the T-UE 106, which is a business user equipment, may communicate with each other through the bot 146, such as chat.

Fig. 2 illustrates an example flow diagram 200 for discovering by a customer UE that a robotic function 146 from a business UE is available in a communication network during a call initiated by the business user equipment to the customer user equipment.

At 202, a business, shown as an O-UE 204, may place a call to one of its customers, shown as a T-UE 206. The call is shown as being initiated from the O-UE 204 to the O-TAS 210 using SIP INVITE 208, but the call may also be initiated by a telephone call, instant message, URI, or the like. Where the business may enter into an agreement with the operator of the communication network to add a robot information profile to the outgoing call, and at 212, the O-TAS 210 may add or insert a robot information profile associated with the robot function of the O-UE 204 (business user equipment) into the sip invite 208 and forward this SIP INVITE 208 to the O-IMS 214. The O-TAS 210 may insert the robot information profile in SIP INVITE 208 by inserting a PCC value, vCard, or URL in a SIP header, etc., where each of the PCC value, vCard, or URL may be used to identify the robot information profile associated with the O-UE 204.

SIP INVITE 208 with the SIP header of the robot information profile may be eventually forwarded to T-UE206 as follows: from the O-IMS 214 to the T-IMS216 at 218, from the T-IMS216 to the T-TAS220 at 222, and from the T-TAS220 to the T-UE206 at 224.

When T-UE206, as a client user device, receives SIP INVITE 208, T-UE206 may provide T-UE206 with a robot information profile associated with the robot functionality of O-UE 204 in accordance with the SIP header of the SIP INVITE 208. The T-UE206 may then request that the application associated with the robot function be downloaded from the robot information server 226 by issuing an HTTP GET command 228 at 230, and the T-UE206 may receive a 200OK response 232 along with the application or program for the robot function 234 downloaded to the T-UE206 at 236. Alternatively, the T-UE206 (client) may wait until a later time to request the downloading of the robot functions from the robot information server 226, or choose whether to download the robot functions.

At 240, in response to receiving the robot information via SIP INVITE 208, the T-UE206 may send a response, such as a SIP183 response 238, to the T-TAS 220. The SIP183 response 238 will eventually be forwarded to the O-UE 204 as a commercial user equipment as follows: from the T-TAS220 to the T-IMS216 at 242, from the T-IMS216 to the O-IMS 214 at 244, from the O-IMS 214 to the O-TAS 210 at 246, and from the O-TAS 210 to the O-UE 204 at 248. The call setup process may then be completed and communication may be established between O-UE 204 as a commercial user equipment and T-UE206 as a customer user equipment based on the manner in which the call was initiated. After T-UE206 downloads robotic function 146, O-UE 204, as a client device, and T-UE206, as a business user device, may communicate with each other through robotic function 146, such as chat.

Fig. 3 shows an example process 300 for a server (not shown) providing robot information profiles during call setup. The server may perform different functions depending on the user equipment from which the call originates. For example, if the call is initiated by the client user equipment 104 as shown and discussed in fig. 1, the server would be equivalent to the T-TAS 120. If the call is initiated by a commercial user equipment 204 as shown and discussed in fig. 2, the server would be equivalent to an O-TAS 210.

The server detects the call in block 302 and determines whether the call is SIP INVITE or a SIP 182 response in block 304. If the call is SIP INVITE, the server may determine in block 306 whether the caller, i.e., the originator of the sip invite, has agreed with the network operator to add a robot information profile associated with the caller to the sip invite. If no protocol exists, the call is processed normally in block 308. If a protocol exists, i.e., SIP INVITE is the originator of the business user device, the server may add the robot information profile to the SIP header of SIP INVITE in block 310. Alternatively, when the call is determined to be SIP INVITE, the server may proceed to the process in block 301 and add the caller's robot information profile (if available). As discussed in fig. 2, the server may insert the bot information profile in the SIP header by inserting a PCC value, vCard, or URL, or the like, where each of the PCC value, vCard, or URL may identify the bot information profile associated with the commercial user device. The server may then forward SIP INVITE with the robot information profile inserted in the SIP header to the called party, i.e., the client user device, in block 312.

If the call is determined to be a SIP183 response in block 304, the server may determine SIP INVITE in block 314 whether the initiator (client user device) that caused the SIP183 response to be received is configured to request a robot information profile associated with the callee. If the initiator is not configured to request the robot information profile, the call is processed normally in block 316. If the initiator is configured to request a robot information profile, the server may add the associated robot information profile to the SIP header of SIP183 in block 318. Alternatively, when the call is determined to be a SIP183 response in block 304, the server may proceed to the process in block 318 and add the bot information profile for the caller (business user device). As discussed in fig. 1, the server may insert the robot information profile in the SIP183 response by inserting a PCC value, vCard, or URL in the SIP header, each of which may identify the robot information profile associated with the commercial user device, or the like. The server may then forward SIP INVITE with the robot information profile inserted in the SIP header to the originator of SIP INVITE, i.e., the client user device, that caused the SIP183 response in block 320.

Fig. 4 shows an example block diagram 400 of a server 402, which server 402 may provide a bot information profile during call setup for discovering that bot functionality is available by a client user device from an entity (business user device). As discussed with respect to fig. 3, the server 402 may function differently depending on the user equipment from which the call is initiated. For example, if the call is initiated by a client user equipment 204 as shown in FIG. 1, the server 402 would be equivalent to the T-TAS120, whereas if the call is initiated by a commercial user equipment 204 as shown in FIG. 2, the server 402 would be equivalent to the O-TAS 210. The client user device 104 or 206 may also be coupled to a robot information server, such as robot information server 138 or 226.

The server 402 may include: one or more processors 404 and memory 406, wherein the memory 406 is communicatively coupled to the one or more processors 404. The server 402 may be coupled with a client user device, such as client user device 104 or 206, and may be coupled with a business user device, such as business user device 106 or 204, via a plurality of servers 408, such as O-TAS, O-IMS, T-IMS, and T-TAS, discussed in fig. 1 and 2.

The memory 406 may store computer-readable instructions that are executable by the one or more processors 402, which, when executed by the one or more processors 402, may cause the server 402 to perform certain operations as follows. As described with reference to fig. 3, the server 402 may detect a call destined for a user device, a client user device, or a business user device and add or insert a robot information profile associated with a robot function of the business user device into the SIP header of SIP INVITE or the SIP header of a SIP183 response, depending on the originator of the call. As discussed above, server 402 can insert a robot information profile in SIP invite 208 by inserting a PCC value, vCard, or URL into the SIP header, where each of the PCC value, vCard, or URL can identify a robot information profile associated with a commercial user device. Server 402 may then forward the call with the robot information profile, SIP invite, or SIP183 to the client user device and provide the robot information profile for the client user device.

The server 402 may also evaluate the originator of the received SIP INVITE or SIP183 response and determine whether to add or insert a robot information profile into a SIP header depending on whether the client user device is configured to request to add a robot information profile to a SIP header or whether an agreement to add a robot information profile to a SIP header is reached with a communication network operator, or whether a business user device agrees to add a robot information profile to a SIP header of SIP INVITE with an operator.

When a robotic function of an accepting business user device is detected from a client user device based on the robotic information profile, the server 402 causes the client user device to download an application associated with the robotic function, wherein the robotic function is associated with the business user device.

As described below, some or all of the operations of the methods described above may be performed by computer readable instructions stored in a computer storage medium. The term "computer readable instructions" as used in the specification and claims of this application includes: routines, applications, application modules, program modules, programs, components, data structures, algorithms, and the like. Also, these computer readable instructions may be executed on various system configurations, including: single processor systems, multiprocessor systems, minicomputers, mainframe computers, personal computers, hand-held computing devices, microprocessor-based devices, programmable consumer electronics, combinations of the above system configurations, and the like.

The computer storage medium may include: volatile memory (e.g., Random Access Memory (RAM)) and/or nonvolatile memory (e.g., Read Only Memory (ROM), flash memory, etc.). Wherein the computer storage medium may further include: other removable and/or non-removable memory devices, including but not limited to: flash memory, magnetic memory, optical memory, and/or tape storage, which may provide non-volatile storage for computer-readable instructions, data structures, program modules, and the like.

Non-transitory computer storage media may be exemplified as computer readable media. Computer-readable media includes at least two types of computer-readable media, namely computer storage media and communication media. The computer storage medium includes: volatile, nonvolatile, removable, and non-removable media for any process or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media include, but are not limited to: phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to store information for access by a computing device. In other instances, communication media may embody computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transport mechanism. And computer storage media, within the definition of this application, does not include communication media.

When executed by one or more processors, the computer-readable instructions stored on one or more non-transitory computer storage media may be used to perform the operations described in fig. 1-4. Generally, the computer readable instructions include: routines, programs, object components, data structures, etc. that may perform particular functions or implement particular abstract data types. The order of operations described in this specification should not be construed as a limitation and the operations described above can be performed in any order and/or in parallel for processing.

Conclusion

Although the subject matter of the present application has been described in language specific to structural features and/or methodological acts, it is to be understood by those skilled in the art that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Furthermore, the specific features and acts described in the specification are merely illustrative of ways to implement the claims of the present application.