Patent Application
20210160455
Many users have multiple telecommunication devices or mobile devices, such as cellular phones, smart phones, tablet computers, laptops, and other devices. Each device may have its own communication address, such as a telephone number, and may receive communications directed to any communication address associated with a service account.
In (IP) Multimedia Subsystem (IMS), call forking may be achieved through implicit registration sets (IRS). With IRS, when any one network identity (e.g., IP Multimedia Public Identifier (IMPU)) associated with a communication address is registered, other network identities associated with a same service account as that network identity are also registered. When a communication is received and directed to any one network identity of the registration set, it may be sent to all network identities of that registration set.
Session Initiation Protocol (SIP), as extended by RFC 3265 (“Session Initiation Protocol (SIP)-Specific Event Notification”, June 2002), utilizes a subscribe method to request a current state as well as state updates from a remote node. The specification for Open Mobile Alliance (OMA) Presence SIMPLE (SIP for Instant Messaging and Presence Leveraging Extensions) defines mechanisms for utilizing SIP to perform instant messaging and other functions. Rich Communication Services (RCS) is a GSM Association (GSMA) program that provides for inter-operability within an IP Multimedia Subsystem (IMS). One feature of RCS is the ability to discover capabilities of contacts. RCS utilizes OMA Presence SIMPLE for various features, including subscription to a presence server to obtain capability information for a list of contacts.
In some examples, users may communicate with other users via conversational video services including, but not limited to, videotelephony, videoconferencing, etc. Videotelephony enables communication via live, simultaneous two-way video and audio transmissions between two devices. Videoconferencing enables two or more locations to communicate via live, simultaneous two-way video and audio transmissions via a multipoint control unit. Various computing platforms enable conversational video services.
In at least one example, IR.94 is a GSMA program that defines an IMS profile for conversational video services to enable voice/video calling services over Long-Term Evolution (LTE) cellular networks. IR.94 is the definition of an IMS profile by listing a number of Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Evolved Packet Core, IMS core, and user equipment (UE) features, which are considered essential to launch interoperable IMS based conversational video services.
In additional and/or alternative examples, web-based applications including, but not limited to, FACETIME®, SKYPE®, GOOGLE+ HANGOUTS®, etc. may provide conversational video services. FACETIME® is an application that facilitates one-on-one video conversation via Voice over IP (VOIP). SKYPE® is an application that provides video conversation and voice call services. SKYPE® allows users to communicate over the Internet by voice, video, etc. GOOGLE+ HANGOUTS® is an application that enables two or more users to communicate via instant messaging, video conversation, Short Message Service (SMS), and VOIP features.
Embodiments of the present technology will be described and explained through the use of the accompanying drawings.
The drawings have not necessarily been drawn to scale. Similarly, some components and/or operations may be separated into different blocks or combined into a single block for the purposes of discussion of some of the embodiments of the present technology. Moreover, while the technology is amenable to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and are described in detail below. The intention, however, is not to limit the technology to the particular embodiments described. On the contrary, the technology is intended to cover all modifications, equivalents, and alternatives falling within the scope of the technology as defined by the appended claims.
Systems and methods are described herein for maintaining and/or facilitating video call continuity between devices. For example, the systems and methods support video calls or other communications between multiple devices (e.g., a mobile device providing a video call stream of content and a drone or other moving device capturing and streaming content via a camera) providing video content to a target device, such as another mobile device.
In some embodiments, the systems and methods facilitate a video call between a first mobile device and multiple, related devices, by providing information to the first mobile device, via a presence server of the network, that identifies the multiple, related devices and information indicating which of the multiple, related devices are currently available on a telecommunications network that includes the first mobile device, and facilitates the transfer of access to the video call between a first related device currently available on the telecommunications network and a second related device, such as a drone or other moving device, currently available on the telecommunications network of the multiple, related devices.
Thus, in some embodiments, the systems and methods facilitate the switching of call endpoint devices within a single established video call, to enable the provision of video content of either device (e.g., a mobile device and a drone) within the single call, without interruption and/or via a continuous call. The systems and methods, therefore, provide a continuity of provided content from multiple devices over a single video call, among other benefits.
In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present technology. It will be apparent, however, that embodiments of the present technology may be practiced without some of these specific details.
As described herein, in some embodiments, the systems and methods maintain, facilitate, support, and/or enable video call continuity, such as a seamless or continuous transfer of a video call, between devices within a telecommunications network.
In some cases, a group of related devices (e.g., paired devices) includes devices that are associated with the same subscriber account, share the same cellular telephone line, and so on. Devices sharing the same subscriber account are often associated with an international mobile subscriber identity (IMSI). Devices sharing the same telephone line may be configured to send, receive, and initiate, cellular communications using a shared identifier, communications address, and so on, such as a telephone number, MSISDN (e.g., sometimes referred to as the “Mobile Station International Subscriber Directory Number”), IP Multimedia Public Identifiers (IMPU), and so forth.
Thus, devices may be related or paired based on their being associated with the same “account” (e.g., associated with an IMSI), associated with the same “line” (e.g., associated with the same communication address), and so on. In some cases, therefore, devices that are associated with a same account and/or a same line are called “related devices” or “paired devices.” In some embodiments, related devices include devices for which incoming calls and messages (such as Short Message Service (SMS) messages) sent to the common communication address may be sent to all of the related devices.
In some embodiments, the mobile device 110 and the related devices (e.g., devices 120 and 130, or another combination of device, virtual reality or augmented reality googles, and/or drone or other associated moving capture device, such as a vehicle, peripheral, wearable device, and so on) are each communicatively coupled to the network 104 (which may be one or more networks).
As described herein, the network(s) 104 may include a cellular network, the Internet, and/or another network. In some embodiments, presence information for the various devices may be obtained from and/or stored by a presence server associated with the network 104, such as a SIP server or other server. One or more of the devices may utilize presence information (such as Internet Protocol (IP) addresses or other network address information) to establish a connection between the related devices, in order to transfer aspects of video conversations, such as which device is providing content within a conversation) between the devices.
In some cases, the devices (e.g., mobile device 110) may utilize presence information obtained from the presence server to identify one or more devices currently online and/or connected to the network 104 and available to provide content and/or other participate in video conversations with other devices. For example, the presence information may identify that the mobile device 120 and the drone 130 are both online and actively providing video content for possible consumption and/or presentation by the mobile device 110 during a video call between the devices.
In some embodiments, various aspects of the network 104 (to be discussed herein) may utilize the presence server to establish communications sessions between the devices, and/or may enforce or apply a sharing or transfer policy for sharing or transferring video conversations, such as a sharing policy that allows a video conversation to be shared between devices. Further details regarding the components and/or operation of the presence server are discussed herein.
Thus, as described herein, the systems and methods may facilitate video call continuity for a video call occurring between the mobile device 110 and the related, or paired, devices 120, 130.
In an example video call scenario, the mobile device 110 is participating in a video conversation with the other mobile device 120. For example, the device 110 and the device 120 are participating in live, simultaneous two-way video and audio transmissions. During the video call, a display 112 of the device 110 presents a user interface 114, which presents a live video feed transmitted by the device 110 via a first region 118 of the user interface 114, as well as a live video feed transmitted by the device 120 via a second region 116 of the user interface 114. For example, the second region 116 of the user interface 114 may present live video of the second user associated with the mobile device 120 and/or video or other image-based content captured by the mobile device 120 (such as via a camera or other imaging component of the device 120).
The mobile device 120 (and other similar devices, not shown) may present similar, but inversed, video content to the second user. For example, a display 122 of the device 120 presents a user interface 124, which presents a live video feed transmitted by the device 120 via a first region 128 of the user interface 124, as well as a live video feed transmitted by the device 110 via a second region 126 of the user interface 124. Thus, the two devices, as shown, facilitate, via the displayed video feeds, a two-way video call between the first user (associated with the mobile device 110) and the second user (associated with the mobile device 120).
In some embodiments, one or both of the users may wish to introduce video content captured or provided (e.g., streamed) by a related device capable of capturing and providing video content, such as the drone 130, which is related to the mobile device 120. Utilizing the systems and methods described herein, one or both of the users may provide input that indicates a request to transfer one endpoint of the video call from the second device 120 to the drone 130, which, upon completion of the transfer, captures video content (e.g., a video of a squirrel in a tree proximate to the drone 130) to be provided to the video call.
The mobile device 110, now in a video call with the drone 130, receives the content from the drone 130 without an interruption of the video call, and displays, via example user interface 115, the video content captured by the drone 130. As described herein, the systems and methods enable the mobile device 110 to engage in a video conversation with both of the related devices (device 120 and drone 130) associated with the second user, by switching or otherwise transferring control or access to the video call by the devices.
In some cases, the devices may connect to the cellular network 202 via an associated base station 208. The cellular network 202 may be responsible for routing voice communications to other networks 206, as well as routing data communications to external packet switched networks, such as the Internet 204. For example, the cellular network 202 may include a Gateway GPRS Support Node (GGSN) 210, or another equivalent node.
In some cases, the devices may be user equipment (UE). The UE may include a smart phone, a personal digital assistant, a netbook, a laptop computer, a smart appliance, a video camera, a moving capture device (e.g., drone 130), and/or another electronic device that is capable of sending and/or receiving voice, video, and/or data via the cellular network 202, the Internet 204, and/or one or more other network(s) 206 (e.g., a Wi-Fi network, another access network, and so on).
In an example where a UE is a mobile device, the mobile device may include a subscriber identity module (SIM) card, which has an international mobile subscriber identity (IMSI) stored thereon. An IMSI is a unique 64-bit number. Within a GSM network, the IMSI is associated with the MSISDN, sometimes referred to as the “Mobile Station International Subscriber Directory Number,” or more commonly as the telephone number. The MSISDN is a unique number that identifies a subscription on a GSM network and is also the number that may be used to place a call to the GSM phone. The MSISDN is not necessarily stored on the SIM card or the phone, and the MSISDN is not permanently associated with the IMSI. The MSISDN may change if the subscription changes, for example. In some cases, other devices, such as the drone 130, may include a SIM card.
In some embodiments, multiple UEs, such as paired or relate devices) are registered with a common number (e.g., MSISDN, IMPU, IMPI, and so on), line, and/or are associated with a common subscriber account (e.g., IMSI). For example, related devices may each have their own unique IMSI programmed into their respective SIM cards, and which are associated with a specific telephone number (MSISDN), which may also be unique to each related device. However, the IMSI and MSISDN pair may be associated in the network with “alias numbers” to allow for shared lines and/or shared accounts, thereby making them related devices.
In some embodiments, various line and/or account associations for related devices may be stored in a database 212, such as a database associated with a presence server 214. For example, the mobile device 110 is associated with IMSI A and MSISDN A. The mobile device 120 is associated with IMSI B and MSISDN B. The drone 130 is associated with IMSI C and MSISDN C, but also with MSISDN B and alias IMSI B. Thus, the drone 130 is associated with the same account and with the same line as the mobile device 120.
In some cases, other devices, such as other related devices (e.g., mobile device 222), which may not capable of connecting through a base station 208 of the cellular network 202, may also register with the cellular network 202 through the Internet 204 using a unique identifier, such as an IMPI or IMPU, a globally routable user agent URI (GRUU), or other identifier. For example, these identifiers may take the form of a telephone number (e.g., they may resemble a MSISDN). The cellular network 202 forwards calls and messages to the device 222, and the device 222 may send or receive shared video conversations in a same or similar way as with related devices. The database 212 may store information (e.g., actual or alias) associated with such devices.
As described herein, one or more of the devices may access and/or utilize presence information to determine which contacts correspond to related devices. For example, the presence information may include information about telephone numbers with which the mobile devices are registered. The device, such as device 110, may utilize the presence information to establish connections with different related devices. For example, the device 110 may utilize the connection to transfer or move between devices during a video conversation, vis the established connections.
In some embodiments, the mobile device 110 may establish a connection with one or more other related devices, and receive content from other related devices via the connected device. However, the device 110 may also establish peer-to-peer connections directly between different related devices. The connections may be established via the presence server 214, such as using the SIP protocol, which enables the establishment of connections between the different devices.
For example, the presence server 214 may retrieve data that corresponds to the IMSI, IMPU/IMPI of the various devices from the database 212. The data may include information specifying the associated device number (e.g., a MSISDN, IMPI, IMPU, or the like) for which the devices are able to utilize for initiating, sending, and/or receiving communications. Thus, the presence information may indicate the shared line or account (e.g., may indicate whether and how the devices are related devices), may enable a device to recognize that devices are related devices that share the same account and/or line, and/or may to distinguish devices that are not related devices. For example, the device 110 may request from the presence server 214 a list of devices related to a certain device or devices.
In some cases, the presence server 214 may be a SIP server, and a device may be configured to utilize OMA Presence SIMPLE to obtain presence information regarding one or more contacts. In some cases, the devices may be configured to provide their presence information to the presence server 214. Further, the devices may be configured to provide capabilities or functionality information to the presence server 214. The capabilities information may indicate an ability to receive instant messages, receive shared content, receive shared video conversations, and so forth. In some cases, devices may obtain each other's presence information and/or capabilities information in other ways, such as through static configuration, peer-to-peer connections, and so on.
In various configurations, the logic to enable the transfer of a video conversation between devices may be within the devices and/or within the presence server 214, and the devices or the server 214 may enforce a transfer policy to enable certain video conversations to be transferred between devices.
In some embodiments, the devices (e.g., via a mobile application), and/or the presence server 214 may include a call continuity system configured to facilitate the transfer of a video call between related devices, such as devices communicating different, unique captured streams of content to a single device, such as the device 110. Further details regarding the call continuity system are described herein.
Aspects of the system can be embodied in a special purpose computing device or data processor that is specifically programmed, configured, or constructed to perform one or more of the computer-executable instructions explained in detail herein. Aspects of the system may also be practiced in distributed computing environments where tasks or modules are performed by remote processing devices, which are linked through a communications network, such as a Local Area Network (LAN), Wide Area Network (WAN), or the Internet. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
Aspects of the system may be stored or distributed on computer-readable media (e.g., physical and/or tangible non-transitory computer-readable storage media), including magnetically or optically readable computer discs, hard-wired or preprogrammed chips (e.g., EEPROM semiconductor chips), nanotechnology memory, or other data storage media. Indeed, computer implemented instructions, data structures, screen displays, and other data under aspects of the system may be distributed over the Internet or over other networks (including wireless networks), on a propagated signal on a propagation medium (e.g., an electromagnetic wave(s), a sound wave, etc.) over a period of time, or they may be provided on any analog or digital network (packet switched, circuit switched, or other scheme). Portions of the system reside on a server computer, while corresponding portions reside on a client computer such as a mobile or portable device, and thus, while certain hardware platforms are described herein, aspects of the system are equally applicable to nodes on a network. In an alternative embodiment, the mobile device or portable device may represent the server portion, while the server may represent the client portion.
In some embodiments, the devices may include network communication components that enable the devices to communicate with remote servers or other portable electronic devices by transmitting and receiving wireless signals using a licensed, semi-licensed, or unlicensed spectrum over communications network, such as network 104 In some cases, the telecommunication network 104 may be comprised of multiple networks, even multiple heterogeneous networks, such as one or more border networks, voice networks, broadband networks, service provider networks, Internet Service Provider (ISP) networks, and/or Public Switched Telephone Networks (PSTNs), interconnected via gateways operable to facilitate communications between and among the various networks. The communications network 130 may also include third-party communications networks such as a Global System for Mobile (GSM) mobile communications network, a code/time division multiple access (CDMA/TDMA) mobile communications network, a 3rd or 4th generation (3G/4G) mobile communications network (e.g., General Packet Radio Service (GPRS/EGPRS)), Enhanced Data rates for GSM Evolution (EDGE), Universal Mobile Telecommunications System (UMTS), or Long Term Evolution (LTE) network), 5G mobile communications network, IEEE 802.11 (WiFi), or other communications network. Thus, the user device is configured to operate and switch among multiple frequency bands for receiving and/or transmitting data.
As described herein, in some embodiments, the presence server 214 may include and/or interact with a call continuity system or other system configured to facilitate seamless, continuous, and/or uninterrupted video calls between multiple devices, such as between a single device (e.g., device 110), and paired or related devices (e.g., device 120 and drone 130).
The call continuity system 300 may include functional modules that are implemented with a combination of software (e.g., executable instructions, or computer code) and hardware (e.g., at least a memory and processor). Accordingly, as used herein, in some examples a module is a processor-implemented module or set of code and represents a computing device having a processor that is at least temporarily configured and/or programmed by executable instructions stored in memory to perform one or more of the particular functions that are described herein. For example, the call continuity system 300 may include a presence module 310 and a transfer module 320.
In some embodiments, the presence module 310 is configured and/or programmed to provide information to a first mobile device (e.g., device 110) that identifies multiple, related devices (e.g., devices 120 and drone 1300, and information indicating which of the multiple, related devices are currently available on a telecommunications network that includes the first mobile device.
For example, the presence module 310 may provide presence server services to UEs, such as to the different devices 110, 120, and 130. The presence module 310 may be configured to register online presence information of various devices, and/or to provide presence information and/or capabilities information, as described herein, regarding the various devices. The module 310 may look up information regarding groups of related devices in the database 212, and provide presence information and/or capabilities information regarding those related devices to other ones of the related devices.
In some cases, the presence module 310 receives requests from devices for presence information, capabilities information, and/or preference information for contacts generally, including for related devices, and/or for lists of related devices. In response, the module 310 provides information indicating which, if any, devices are related devices associated with the requesting device. The presence module 310 may provide presence information and/or capabilities information using the OMA Presence SIMPLE protocol, or other similar protocols.
In some embodiments, the transfer module 320 is configured and/or programmed to transfer or allocate access to the video call between a first related device currently available on the telecommunications network and a second related device currently available on the telecommunications network of the multiple, related devices.
For example, the transfer module 320 may facilitate establishment of connections between devices, including establishment of connections between related devices and other devices, such as by following a transfer policy. The transfer policy may be based at least in part on presence information, capabilities information, and/or preference information, as described herein.
In some cases, the transfer policy may include rules for sharing content between devices, and may indicate that certain video conversations may be shared with related devices and that such video conversations may not to be shared with other devices that do not share a line or account with the device that received the live video and audio transmission. The transfer module 320, therefore, may authorize certain video conversations to be shared with certain related devices, but deny requests to establish a connection and/or transfer video conversations with other devices.
As described herein, one or more of the mobile devices may include similar modules or functionality. Although not shown in
In some embodiments, the device presence module may be configured and/or programmed to retrieve presence information for one or more devices, such as related devices, from the presence server 214 (e.g., via OMA Presence SIMPLE protocol).
In some embodiments, the video conversation module may be configured and/or programmed to facilitate video conversations between devices. For example, the video conversation module may be configured to simultaneously exchange live video and audio transmissions between devices via a computing platform such as IR.94 and/or various web-based applications including, but not limited to, FACETIME®, SKYPE®, GOOGLE+ HANGOUTS®, etc., as described herein.
In some embodiments, the user interface module may be configured to cause, via a user interface associated with the mobile device, a presentation of a list of one or more other devices that are permitted or capable of joining a video conversation with the device. The user interface may be interactive to receive user selection of at least one related device for sharing of the video conversation.
In some cases, the user interface module may call various Application Programming Interfaces (APIs) to initiate the live, simultaneous two-way video and audio transmissions between the devices participating in a video conversation, and/or call other APIs to retrieve the list of related devices, including their current online presence status (e.g., online or offline, busy, ready to stream content, and so on).
Thus, as described herein, the presence server 214, via the call continuity system 300, may perform various operations or processes to provide, facilitate, and/or manage call continuity during a video conversation when the source of content being provided to one of the endpoints of the conversations switches or is transferred between two or more related devices, such as between a mobile device and a paired drone.
In operation 410, the system 300 receives, via input received from the first user via a first mobile device, a request to establish a video call between the first mobile device and a second mobile device. For example, the system 300 may receive information from the mobile device 110 that indicates a request to established a video call with the mobile device 120.
In operation 420, the system 300 connects, via a telecommunications network that includes a first user and second user as subscribers, the first mobile device to the second mobile device via the established video call. For example, the system 300 may facilitate a video call between the devices.
In operation 430, the system 300 facilitates streaming of video content via the established video call from the second mobile device to the first mobile device via the telecommunications network. For example, the mobile device 120 streams content to the device 110.
In operation 440, the system 300 receives, via additional input received from the first user via the first mobile device, a request to transfer the video call to the drone associated with the second user. For example, the system 300 receives a new request from the device 110 to access content streamed (or available to be streamed) from the drone 130 or other moving capture device, which is, in some cases, related to the mobile device 120. As described herein, the drone 130 may include one or more network communication components configured to send and receive information over the telecommunications network 104, as well as a video capture device (e.g., camera) configured to capture video of an area within which the drone is moving.
In operation 450, the system 300 connects, via the telecommunications network, the drone to the first mobile device via the established video call. For example, the presence module 310 may provide information to the first mobile device (e.g., device 110) that identifies multiple, related devices (e.g., devices 120 and drone 1300, and information indicating which of the multiple, related devices are currently available on a telecommunications network that includes the first mobile device.
In some cases, the system 300 establishes the connection between the drone and the first mobile device via the presence server 214 of the telecommunications network, which is configured to store information identifying the first mobile device, the second mobile device, and the drone, and configured to provide information to the first mobile device that identifies the second mobile device and the drone as related devices.
In operation 460, the system 300 facilitates streaming of video content via the established video call from the drone to the first mobile device via the telecommunications network. For example, the transfer module 320, via the presence server 214, may transfer or allocate access to the video call from the first related device currently available on the telecommunications network to the drone, which is also available on the telecommunications network.
Thus, as described herein, the system 300 facilitates the switching of video streams provided by different, related devices during a single, established video call, without interruptions.
As depicted in
If the user selects the video content from the drone, the user interface 500, as depicted in
Of course, the device 120 may provide similar functionality, where the device 120 provides the user associated with the related devices with various user-selectable options to provide the different video feeds to the device 110.
Thus, as described herein, the systems and methods facilitate the switching of content provided within a single established video call, to enable the provision of video content from different, related devices (e.g., a mobile device and a drone) within the single call, without interruption and/or via a continuous call. The systems and methods, therefore, provide a continuity of provided content from multiple devices over a single video call, among other benefits.
Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof means any connection or coupling, either direct or indirect, between two or more elements; the coupling or connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.
As used herein, being above a threshold means that a value for an item under comparison is above a specified other value, that an item under comparison is among a certain specified number of items with the largest value, or that an item under comparison has a value within a specified top percentage value. As used herein, being below a threshold means that a value for an item under comparison is below a specified other value, that an item under comparison is among a certain specified number of items with the smallest value, or that an item under comparison has a value within a specified bottom percentage value. As used herein, being within a threshold means that a value for an item under comparison is between two specified other values, that an item under comparison is among a middle specified number of items, or that an item under comparison has a value within a middle specified percentage range.
The above Detailed Description of examples of the technology is not intended to be exhaustive or to limit the technology to the precise form disclosed above. While specific examples for the technology are described above for illustrative purposes, various equivalent modifications are possible within the scope of the technology. For example, while processes or blocks are presented in a given order, alternative implementations may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or subcombinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed or implemented in parallel, or may be performed at different times. Further any specific numbers noted herein are only examples: alternative implementations may employ differing values or ranges.
The teachings of the technology provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various examples described above can be combined to provide further implementations of the technology. Some alternative implementations of the technology may include not only additional elements to those implementations noted above, but also may include fewer elements.
These and other changes can be made to the technology in light of the above Detailed Description. While the above description describes certain examples of the technology, and describes the best mode contemplated, no matter how detailed the above appears in text, the technology can be practiced in many ways. Details of the system may vary considerably in its specific implementation, while still being encompassed by the technology disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the technology should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the technology with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the technology to the specific examples disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the technology encompasses not only the disclosed examples, but also all equivalent ways of practicing or implementing the technology under the claims.
To reduce the number of claims, certain aspects of the technology are presented below in certain claim forms, but the applicant contemplates the various aspects of the technology in any number of claim forms. For example, while only one aspect of the technology is recited as a computer-readable medium claim, other aspects may likewise be embodied as a computer-readable medium claim, or in other forms, such as being embodied in a means-plus-function claim. Any claims intended to be treated under 35 U.S.C. § 112(f) will begin with the words “means for”, but use of the term “for” in any other context is not intended to invoke treatment under 35 U.S.C. § 112(f). Accordingly, the applicant reserves the right to pursue additional claims after filing this application to pursue such additional claim forms, in either this application or in a continuing application.
This application is a continuation of U.S. patent application Ser. No. 16/888,579, filed on May 29, 2020, entitled VIDEO CALL CONTINUITY BETWEEN DEVICES VIA A TELECOMMUNICATIONS NETWORK, which is a continuation of U.S. patent application Ser. No. 15/632,167, filed on Jun. 23, 2017, entitled VIDEO CALL CONTINUITY BETWEEN DEVICES VIA A TELECOMMUNICATIONS NETWORK, which is related to U.S. patent application Ser. No. 15/212,760, filed on Jul. 18, 2016, entitled CROSS-PLATFORM VIDEO CONVERSATION BETWEEN RELATED DEVICES, which are hereby incorporated by reference in their entireties.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16888579 | May 2020 | US |
| Child | 17169312 | US | |
| Parent | 15632167 | Jun 2017 | US |
| Child | 16888579 | US |
